Why test schema markup on a live URL

Schema you wrote in your CMS is one thing. Schema that actually renders on the live page is another. Plugins fight each other, theme updates strip script tags, server-side rendering can fail to inject JSON-LD on certain page types, and CDN caching can serve stale markup for hours. A live URL test confirms what Google and AI crawlers actually see.

This schema markup tester fetches the URL the same way Googlebot does, parses every script tag with type="application/ld+json", extracts any Microdata or RDFa annotations, validates each one against schema.org and Google's documented requirements, and reports errors and warnings per schema block.

What the test actually checks

Three layers of validation. First, JSON syntax: does each schema block parse as valid JSON. A trailing comma or stray quote breaks the entire block, and Google silently ignores invalid schemas without telling you in Search Console. Second, schema.org compliance: are the @type values real types from the vocabulary, are required fields present, are types nested correctly. Third, Google rich-result eligibility: are the Google-specific recommended fields present, are values formatted the way Google expects (ISO 8601 dates, ISO 4217 currencies, valid URLs).

The third layer is where most tools stop short. schema.org might say Article only requires headline and image. Google additionally requires author, datePublished, and a publisher with a logo to qualify for Top Stories or AI Overviews. This tester flags the Google requirements explicitly so you know whether the rich result will actually show up.

The most common errors we see in production

Missing @context is by far the most frequent. Without "@context": "https://schema.org" at the top of the JSON, the entire block is meaningless. Google ignores it. This usually happens when someone copies a partial example from a tutorial.

Wrong date formats follow closely. "January 15, 2026" or "01/15/2026" is not valid. Schema dates must be ISO 8601: "2026-01-15" for dates, "2026-01-15T14:30:00Z" for datetimes. Google's parsers reject anything else. Same for currency: "USD" works, "$" or "dollars" does not.

Image fields without an actual image URL are another classic. Article schema requires an image, but many sites pass an empty string or a relative path. Image must be an absolute https URL pointing to a real file with valid dimensions (Google prefers at least 1200px wide).

JSON-LD versus Microdata versus RDFa in your test results

This tester reports all three formats but treats JSON-LD as primary because that is what Google recommends. If you have both Microdata and JSON-LD on the same page (common with WordPress sites running overlapping plugins), Google may pick whichever it parses first, and the two can disagree. Pick one format, remove the other, and standardize.

Microdata embedded in your visible HTML can break if your front-end framework re-renders elements (React, Vue, Svelte). The itemprop attributes might survive, or they might not, depending on hydration order. JSON-LD avoids the issue entirely because it lives in a static script tag.

Schema and AI Overviews

Schema is one of the strongest signals for AI Overviews eligibility. Pages with valid Article, FAQPage, HowTo, and ProductSchema markup appear in AI-generated answer summaries far more often than pages without. The reasoning is simple: structured data tells the AI exactly what kind of content this is, what the key claims are, and how to attribute them.

ChatGPT, Perplexity, and Claude's web tools all parse JSON-LD explicitly. Brand mentions inside schema (Organization with same-as links to your social profiles) help these systems associate the content with your brand entity, which feeds citation accuracy.

What to do after running the test

For each error, fix the underlying field in your CMS or template, not just on the rendered page. A patched render that does not survive a cache flush or template update is not a fix. Then run this tester again to confirm. Then run Google's official Rich Results Test for the specific result type you are targeting (Article, Product, Recipe, etc.) since Google's tester sometimes catches policy issues this one does not.

For warnings, prioritize by how visible the rich result is. Missing recommended fields on a Product schema (review aggregateRating, brand) directly reduce search-result attractiveness. Missing recommended fields on a HowTo schema may quietly disqualify the carousel display. Required fields are non-negotiable; recommended fields are where you win the click-through-rate game.