A page interpretation debugger: paste any URL — or raw HTML — and see exactly what search engines and social platforms can read. The report shows the response (status, redirects, headers), what the page declares (title, meta, Open Graph, structured data, hreflang), where those signals conflict, and the exact fix — with the raw evidence behind every finding.
What the URL actually returns
Before any tag matters, the transport must be healthy. The report shows the HTTP status, every redirect hop (a 301 is fine; five hops are not), the final URL, content type, and response headers such as X-Robots-Tag and Cache-Control. A 404 page or a slow redirect chain explains a lot of "why does Google show the wrong thing" problems before you ever look at a meta tag.
What the page declares
The debugger extracts everything a crawler would read: title, meta description, canonical, robots directives, Open Graph and Twitter tags, JSON-LD structured data types, hreflang, images, and headings. Each value is shown as raw evidence — the exact tag and content that was found, so you can compare it against what you think you published.
Where the signals disagree
Most ranking and preview problems are conflicts, not missing tags: a canonical pointing at a different page than the one served, a canonical paired with noindex, an og:title that contradicts the <title>, a relative og:image URL (Facebook rejects them), or duplicate title and description tags where crawlers silently use the first. The report surfaces these conflicts explicitly instead of scoring them away.
The fix, in plain language
Every finding includes a plain-English explanation and the copy-ready repair: generate the corrected tags in the studio, verify an Open Graph image with the OG image checker, or validate a JSON-LD block before redeploying. Then re-run the debugger after deployment — that is the workflow it is built for.