AlgoRadar analyzes the content already published on your WordPress site and calculates two indicative scores:

Core Exposure Score — exposure to content-quality factors typically involved in core updates (thin content, duplicates, weak internal linking, technical issues).
Spam Exposure Score — exposure to patterns typical of spam updates (risky outbound links, keyword stuffing, doorway pages).

Both scores come from a local, configurable heuristic model, never from Google’s actual algorithm: AlgoRadar is not a Google product, does not replicate its inner workings, and does not predict real penalties. Every factor that contributes to a score is shown transparently (data point, reason, weight, suggestion), so the score is never a number without an explanation.

Built to go easy on your hosting

Where possible, AlgoRadar reads data directly from the WordPress database (content, internal links, metadata) instead of scanning the site over HTTP. Actual HTTP requests are reserved only for the signals that genuinely need them, such as real response time. The background scan uses WP-Cron with chained batch execution, with a browser-driven fallback for hosting environments where background execution isn’t reliable.

No paid services

AlgoRadar works exclusively with data already present on your site and, if you connect it, with the official, free Google Search Console API to compare scores against real clicks and impressions. No integration with paid SEO services.

External services

AlgoRadar connects to one third-party service, and only if you explicitly turn it on: the official Google Search Console API. It is off by default and every scoring feature works without it.

What it’s for: if you choose to connect your Google account, AlgoRadar fetches your site’s real clicks and impressions from Search Console to show them alongside its own scores (Compare), to find pages with no traffic (Pagine zombie), to show traffic around Google’s core updates (Core update) and to find pages competing for the same search (Concorrenza interna).

What is sent, and when:

Connecting: when you click “Connect” in AlgoRadar > Settings, your browser is redirected to Google’s OAuth consent screen (https://accounts.google.com/o/oauth2/v2/auth) to authorize read-only access to your Search Console data. No site data is sent at this step, only the standard OAuth request.
Token exchange/refresh: after you authorize, the plugin exchanges the authorization code (and later, silently, the refresh token) for an access token by calling Google’s token endpoint (https://oauth2.googleapis.com/token). This request includes the OAuth credentials you entered (Client ID/Secret) and the token/code itself; no content from your site is sent.
Fetching data: when you open the Compare, Pagine zombie, Core update or Concorrenza interna pages with a connected account, the plugin calls the Search Console API (https://www.googleapis.com/webmasters/v3, read-only scope) to request clicks, impressions and positions for your own site’s property: per page, per day, or per search query and page, for the date range the page shows. This happens only when one of those pages is opened (results are cached for 12 hours), only for a connected account, and never during the background scan itself.

No content, personal data of your visitors, or site data other than your own page URLs and the date range being queried is ever sent to Google. You can disconnect at any time from AlgoRadar > Settings, which deletes the stored tokens.

This integration is governed by Google’s own terms: Google APIs Terms of Service and Google Privacy Policy.