🔍

GEO & Schema Compliance Inspector

Last updated:

Enter any public URL to check its Schema.org JSON-LD validity, indexability, and semantic HTML structure. You get a 0-100 score, plus a list of concrete, specific fixes — not a vague grade.

The URL is fetched by our server to read its HTML — it is not stored, and nothing about the page is shared with third parties.

—

Structured data found
    Recommendations

    What this tool actually checks

    This inspector runs a fixed set of deterministic, rule-based checks against the live HTML of the URL you provide: whether valid Schema.org JSON-LD is present, whether the page is blocked from indexing by a noindex robots tag, whether title/description/canonical tags exist, and whether the page uses semantic structure (a single <h1>, <h2> sections, real <table> markup for comparable data) that both search engines and AI answer engines can parse cleanly.

    It does not call Google, ChatGPT, or any AI model to check whether your specific page currently appears in AI Overviews or any other answer engine — no tool can guarantee that, and a high score here is not a promise of citation. What it measures are the structural signals that Google's own documentation associates with machine-readability and eligibility for rich results and AI summarization.

    How to use it

    1. Paste the full URL of a public page (must start with http:// or https://).
    2. Press Scan Page. The page is fetched once, server-side, and analyzed — nothing is stored.
    3. Read the score breakdown and the recommendation list, ordered from critical to informational.
    4. Fix the critical items first (missing schema, noindex, missing title) — those block visibility outright.

    Score breakdown

    • Structured data (up to 30 pts) — presence and completeness of JSON-LD Schema.org blocks.
    • Meta essentials (up to 20 pts) — title, meta description, canonical link.
    • Indexability (10 pts) — the page is not set to noindex.
    • Semantic structure (up to 20 pts) — a single <h1>, real <h2> sections, and semantic <table> markup where relevant.
    • Content signals (up to 20 pts) — an FAQ-style section and a visible author byline.

    Frequently asked questions

    Does my URL or its content get stored anywhere?

    No. The page is fetched once to run the checks and the response is returned to your browser; nothing about the scanned page is written to a database.

    Does a 100 score guarantee my page will appear in Google AI Overviews?

    No. This tool checks technical readiness signals only. Whether any specific page is cited by an AI answer engine also depends on relevance, ranking, and factors outside any single page's control.

    Why does this need to fetch the page on a server instead of in my browser?

    Browsers block cross-origin page reads for security (CORS), so a client-side script generally cannot read another site's raw HTML directly. Fetching it server-side is the only reliable way to read arbitrary public pages.

    What URLs are rejected?

    Non-http(s) URLs, localhost/internal hostnames, and private IP ranges are rejected outright, since scanning those would not test a real public page.

    Related SEO tools