Inspect public HTML, identify platform signals and review a small sample of site pages. Save the report, compare it with a later scan and prepare a client report.
Scan the live site
The server fetches the page and public machine-readable files. The report is based on returned data, not a generated example.
Optional, slower, and not needed on every scan.
Checks HTML metadata, social tags, canonical, headings, JSON-LD, robots.txt, sitemap.xml, llms.txt, security headers and HTTP redirects. DNS/WHOIS runs only when enabled above.
Initial page + the first four eligible links from its HTML, same origin, no query strings or recursive crawl. The initial page is reused; additional pages follow a conservative robots.txt wildcard policy.
Selected sample incomplete: {{ auditResult.page_sample.reason || 'selected_pages_incomplete' }}. Missing or truncated HTML is not treated as missing metadata.
Selected sample finished. This is not a complete site audit.
Passive evidence from this returned HTML and selected headers; no scripts executed. High confidence means a distinctive public marker, not proof of the current backend. Exported, cached or migrated pages can retain old assets. Missing signals cannot rule a platform out.
Technology data unavailable in this report. Re-scan to collect current signals.
Partial HTML observation. More technologies or conflicting signals may be missing.
No supported platform signals found. Confirm the platform manually; public HTML may contain old or cached markers.
Ranked by category weight × how bad the check is — the same weights shown in the sub-scores above, not a separate opinion. See every check, not just the top 5, in the list below.
No check changed status between the saved report and this one.
{{ auditDiff.checks.added.length }} check(s) only apply now, {{ auditDiff.checks.removed.length }} only applied to the saved report — the audit itself changed between versions of this tool or the page's own setup (e.g. it switched to HTTPS), not something either scan got wrong.
Run or view the report you want on the "after" side, then pick a saved report above to compare against it.
SEO & GEO signals {{ auditResult.checks.length }} checks
Sitemap coverage incomplete. {{ sitemapCoverage.urls }} URLs found; this is not the total number of pages on the site. Read {{ sitemapCoverage.fetched }} of {{ sitemapCoverage.children }} child sitemaps. Up to {{ auditResult.sitemap.children_limit }} child sitemaps per audit, within the shared time budget.
Sitemap XML did not parse (root type: {{ auditResult.sitemap.root_type }}).
Tree view is unavailable because this block is not valid JSON. Formatted view shows the original source.
{{ auditResult.page_available === false ? 'JSON-LD is unavailable because the initial page could not be retrieved.' : 'No JSON-LD script blocks found in the fetched HTML.' }}
Page links & resources
{{ auditResult.links.checked }} checked · {{ auditResult.links.skipped }} skipped · {{ auditResult.links.broken }} returned 404/410. Only URLs from this page with the same origin are checked.
Incomplete: {{ auditResult.links.reason }}. Restricted, rate-limited or unavailable responses are not classified as broken.
Kind
URL
HTTP
Result
{{ link.kind }}
{{ link.url }}
{{ link.status || '—' }}
{{ link.state }} ({{ link.error }})
Network facts server-side
Deep network check was not selected for this scan.
AI search loss estimate your inputs, not a site claim
Preset:{{ p.label }}
Estimated annual revenue exposed
{{ formattedLoss }}
Traffic × risk × 12 × conversion × deal value. Change the assumptions to model your own case. Blog preset uses a $0 deal value; revenue loss will be $0 until you enter a monetization value.
ReadyEnter a public URL to inspect what search engines, social crawlers and AI agents receive.
About this tool
Unlike most tools on this site, a live audit can't run entirely in your browser: reading another site's raw response headers, following its redirects and resolving its DNS all require a same-origin-restricted request that only a server can make. This tool sends the URL to this site's own backend, which fetches it (SSRF-guarded and rate-limited) and returns the parsed result — the page content itself is not stored, though request diagnostics may reach server logs like any web request. Cloudflare Turnstile runs a bot check before each audit, which loads a small script from Cloudflare.
Recent scans (a lightweight URL/score log) and Saved reports (a full snapshot of every check) are different things: history lets you quickly re-run a URL you've looked at before, but it doesn't keep what the checks actually said — re-running is the only way to see that again, and if the site changed in the meantime you're not looking at the old result anymore. Save report keeps the complete result, so Compare against a saved report can show a real diff later — which checks got fixed, which regressed, and which are still open — against the exact state the site was in when you saved it, not a guess based on the score alone. Priority fixes ranks the open checks by category weight × severity (the same weights shown in the sub-scores), so the highest-impact issue is the first thing you see, not whichever one happens to render first in its category list.
Execution: independent requests run concurrently with up to eight active connections (up to four per host). Dependent requests follow their prerequisites. The 30-second budget includes queue waits; unavailable checks keep their own errors while completed results remain in the report.
Platform signals: review detected technologies with their evidence and confidence. WordPress plugin and theme paths are stronger signals than uploads alone. Confirm the active platform before planning changes.
Site report: optionally inspect the initial page and up to four internal HTML pages. See repeated metadata, shared observations and the affected URLs, with partial or blocked pages clearly marked. This is a small sample, not a full crawl. Download a Russian or English client report in Markdown or print HTML/PDF. The main readiness score stays separate.
Privacy: only the URL you enter and selected scan options are sent to this site's server for the duration of one audit request; hostnames are resolved through Cloudflare DNS over HTTPS. Deep network checks also query DNS records and an allowlisted WHOIS server. Recent scans and saved reports stay in this browser's local storage and are never uploaded.