Run the live URL of the affected page through both Google’s Rich Results Test (opens in a new tab) and the Schema Markup Validator (opens in a new tab) today. Each tool answers a different question, so one green result proves little. This is how to validate schema markup after an SEO plugin change or a Search Console error email.
Key takeaways
- Use the Rich Results Test for Google rich result eligibility and the Schema Markup Validator for schema.org syntax.
- Test the live URL, then open view-source and search for
application/ld+jsonto count every block. - Fix errors first. Warnings only flag missing recommended properties.
- After a fix, click Validate fix in the Search Console enhancement report. The report lags behind your change.
How to validate schema markup: pick the tool for your question
The Rich Results Test checks the required and recommended properties of the rich result types Google supports. The Schema Markup Validator checks your JSON-LD against the schema.org vocabulary and says nothing about Google eligibility. For rich results in Google, start with the first tool. For valid schema.org syntax for any consumer, use the second.
| Question | Tool | What it does not tell you |
|---|---|---|
| Can this page qualify for a Google rich result? | Rich Results Test | Whether types outside Google’s supported list are valid |
| Is my JSON-LD valid schema.org? | Schema Markup Validator | Whether Google will show a rich result |
| Which pages in my site have problems? | Search Console enhancement reports | Anything on pages Google has not crawled yet |
Schema markup is structured data, usually written as JSON-LD, that describes a page with types such as Article, Product or FAQPage. Google’s introduction to structured data (opens in a new tab) lists the supported types and their properties.
If the test cannot fetch your page, check that robots.txt and any login requirement are not blocking access. If you edit robots.txt for AI crawlers, this guide on blocking AI crawlers while staying in Google Search shows rules that leave Googlebot alone.
Test the live URL in the Rich Results Test and read what it detected
Paste the live page URL into the Rich Results Test, not a code snippet. A snippet skips what your theme and plugins actually output, which is where most problems start. The result lists the rich result types Google detected on the rendered page.
- Open the Rich Results Test and choose the URL tab.
- Paste the full live URL and run the test.
- Open each detected item and confirm the type you expect is listed (Article, Product, FAQPage).
- Click View tested page, then the HTML tab, to read the rendered HTML Google fetched.
- Note every error and warning with its property name.
A type you added is missing from the list? Then the markup is not valid for Google, is not rendered, or is not a supported type. Check the rendered HTML first. Schema injected by JavaScript can be absent from the raw source but present in the rendered version.
If you keep a coding agent on your theme repository, add this routine to your AGENTS.md file so the agent runs the same check after every schema change.
Run the same URL through the Schema Markup Validator
The Schema Markup Validator, hosted at validator.schema.org, parses the JSON-LD and reports syntax and vocabulary problems. It accepts a live URL or pasted code. Use the URL tab for the published page and the code tab for a snippet you are still drafting.
This tool accepts types and properties the Rich Results Test ignores. A page can pass here and still show no rich result in Google, because the type is outside Google’s supported list or a required Google property is missing. That mismatch is why two tools disagree on the same page.
A minimal Article block looks like this. Run it through both tools to see what each reports:
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "How to Validate Schema Markup",
"datePublished": "2026-03-14T09:00:00+05:30",
"author": { "@type": "Person", "name": "Jane Doe" }
}Fix errors first, then decide on warnings
Errors block eligibility for that rich result, so fix them first. Warnings flag missing recommended properties and block nothing. Add a recommended property only when the data exists on the page. Inventing values to silence a warning creates a bigger problem.
These five errors cover most failed checks:
| Error | Exact fix |
|---|---|
| Missing required field | Open Google’s docs page for your type to see which properties it lists as required, then add the missing one. |
| Wrong type | Match the expected value type. Write "price": "29.99" with a separate "priceCurrency": "USD", and "ratingValue": 4, not a word. |
| Invalid date | Use ISO 8601, such as 2026-03-14 or 2026-03-14T09:00:00+05:30. Strings like "March 14" fail. |
| Duplicate or nested FAQPage | Keep one FAQPage per page and put every question in its mainEntity array. Remove the second source. See Google’s FAQPage docs (opens in a new tab) for current eligibility. |
| Markup does not match visible content | Every question, price, rating or author in the JSON-LD should appear on the page, so check Google’s structured data guidelines (opens in a new tab) for the exact wording. |
After you fix and redeploy, retest the live URL before you touch Search Console. The rich result reports in Search Console only reflect pages Google has crawled, so they lag behind your fix. Once the live test is clean, open the report, select the issue and click Validate fix.
Warning: A clean Search Console report does not mean the page is clean today. It shows the last crawl. The live test shows the current state.
Count the JSON-LD blocks in view-source to catch duplicates
Open view-source on the page, search for application/ld+json, and list every block with its @type. Tools can report one valid item while the page carries three. On WordPress, an SEO plugin, the theme and an FAQ block can each output the same type. That produces the duplicate FAQPage error from the table above.
You can count blocks from a terminal. This reads the raw HTML only, so it misses schema added by JavaScript:
curl -s https://example.com/your-page/ | grep -o 'application/ld+json' | wc -lList the types in those blocks:
curl -s https://example.com/your-page/ | grep -oE '"@type": ?"[A-Za-z]+"'FAQPage shows up twice? Find the second source, turn off schema output in the theme or the block, and keep the one that matches the visible content. Two plugins that each add markup will leave the page with duplicate blocks, so check how a plugin’s schema output interacts with your theme before you rely on it.
If your fetch script returns 401 on a protected staging site, the WordPress REST API 401 guide covers the usual causes. Google’s tools cannot reach a login-protected page either. Paste the rendered HTML into the Schema Markup Validator code tab instead.
Next step: pick one page with a Search Console structured data error, run its live URL through both tools, count the blocks in view-source, and fix the first error in the list.
Frequently Asked Questions
How to check for schema markup on a page?
Open view-source and search for application/ld+json. Each match is one JSON-LD block. Then paste the URL into the Rich Results Test to see which types Google detected.
How to check schema markup of a website?
Test the URLs of your key templates one by one: a post, a product, the home page. The Search Console enhancement reports show detected types and errors across crawled pages. They update only after Google recrawls.
How to test schema markup before publishing?
Paste the JSON-LD into the code tab of the Schema Markup Validator for syntax checks. The Rich Results Test also accepts a code snippet. You still need a live URL test after publishing, because plugins and themes change the final output.
Why does the Schema Markup Validator pass but the Rich Results Test shows errors?
The two tools check different rules. The validator checks schema.org syntax. The Rich Results Test checks the properties Google requires for its own rich result types, so a missing required property fails there only.
How long until Search Console shows my fix?
The report updates after Google recrawls the page, and the timing is not fixed. Test the live URL first, then click Validate fix in the report.
