SEO tools
Schema Markup Validator: Check a Page's Structured Data
Parses the structured data on the page you enter, lists the schema.org types it finds, and flags blocks that fail to parse or are missing the properties their type requires.
What this schema markup validator tests
It reads the served HTML rather than a rendered DOM. That is deliberate: markup injected by JavaScript is the single most common reason a page validates in a browser-based tool and reports nothing to a crawler.
- Whether any structured data is present in the served HTML.
- Which schema.org types are declared, so you can confirm the right one is used.
- Whether each block is syntactically valid and parseable.
- Whether the properties a type requires are actually populated.
Validation is not eligibility, and eligibility is not display
Three separate things get conflated. Valid syntax means the block parses against the schema.org vocabulary. Eligibility means Google supports that type for a rich result and your required properties are present. Display means Google chose to show it for a given query — which it decides per query, and never promises.
This tool answers the first two. Nothing can answer the third in advance.
Failures that pass every validator
Each of those is a guidelines problem rather than a syntax problem, and only the last is machine-detectable. For the vocabulary and working examples see schema markup explained , and for what Search Console reports afterwards see structured data errors .
- Values that disagree with the visible page, such as a marked-up price the page does not show.
- Review ratings with no visible reviews, or self-serving ratings on the business's own page.
- FAQ markup applied to content that is not genuinely a question and answer pair.
- Correct markup on a page that is noindexed, blocked, or canonicalised elsewhere.
- Does schema markup improve rankings?
- Not directly. It makes a page eligible for richer presentation, which can lift click-through rate on a position you already hold.
- Which format should I use?
- JSON-LD. Google recommends it, and because it lives in its own script block a template change is far less likely to break it.
Start with one visible, truthful JSON-LD block
Use the structured data SEO guide to select a type that fits the page, then run the indexability checker if valid markup still does not appear in Search Console. A noindex or conflicting canonical prevents the page itself from becoming eligible.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "How to test structured data",
"datePublished": "2026-09-20",
"author": {"@type": "Organization", "name": "Example"}
}
</script>
Every value must agree with visible page content. Do not add
a type only because it has a rich-result name.Other tools
Fetches the robots.txt file for the host you enter, reports whether it exists and whether it blocks every crawler, and reads the page-level robots directives alongside it.
Looks for the sitemap the way a crawler does — the robots.txt declaration first, then the conventional locations — then confirms it parses as XML and counts the URLs inside it.
Reads the canonical URL a page declares, then fetches that URL to confirm it resolves, is not redirected, and is not noindexed — the three ways a canonical silently becomes inert.
Follows the URL you enter through every hop, reporting the status code at each step and the final destination — the detail a browser hides once the address bar settles.
Fetches the page you enter, takes a sample of the internal links it points at, and requests each one — reporting the status code that comes back instead of the colour of the link.
Checks every signal that decides whether a page is allowed into the index — the status code, robots.txt access, meta robots, the X-Robots-Tag header, and the canonical.
Queries the live DNS for the domain you enter and reports the records it publishes: the addresses it resolves to, where its mail goes, and whether the TXT records email authentication depends on are present.
Queries the registry over RDAP — the structured successor to classic WHOIS — and reports when the domain was registered, how old it is now, who the registrar is, and when the registration lapses.
Enter a domain to find when it was registered, how old it is today, when it expires, and which registrar holds it. Domain age is context for a diagnosis, not a Google ranking factor.
Opens a TLS connection to the host you enter and reports the certificate it presents — the issuer, the validity window, the days remaining, and the negotiated protocol version.
Requests the URL you enter and reports what the server sends back in its headers — the security headers present, the caching policy, whether the response is compressed, and which HTTP version was negotiated.