How to check if a website has schema markup?

Max Schwertl
May 11, 2026

Schema markup is structured data embedded in a website’s code that helps search engines and AI systems understand what your content actually means, not just what it says. Checking whether your site has schema markup correctly implemented is one of the most practical technical SEO tasks you can do, and it takes less time than most people expect.

This guide walks you through every method available in 2026, from Google’s official testing tools to manual browser inspection and site-wide monitoring in Google Search Console. By the end, you will know exactly what schema markup your site carries, whether it is valid, and what to fix if it is not.

Why schema markup matters for SEO and AI visibility

Schema markup gives search engines and generative AI systems a structured, machine-readable description of your content. Without it, Google, Bing, ChatGPT, and Perplexity must infer meaning from raw text alone. With it, they receive explicit signals about entities, relationships, and content type.

The practical benefit in traditional search is well documented. Rich results, the visual enhancements like star ratings, product prices, and event dates that appear in Google Search, are only available to pages with valid schema markup. Research from IgniteVisibility published in January 2026 found that rich results attract around 58 clicks per 100 searches, compared to 41 for non-rich results. That gap in click-through rate compounds over time.

The benefit for AI visibility is real but more nuanced. SearchVIU’s tests in October 2025 confirmed that ChatGPT, Claude, Perplexity, and Gemini all actively process schema markup when they access content directly. Microsoft’s Principal Product Manager Fabrice Canel stated at SMX Munich in March 2025 that schema markup helps Microsoft’s LLMs understand content. However, a Search/Atlas study cited by Search Engine Land in March 2026 found no direct correlation between schema coverage and AI citation rates, which means schema is a signal worth having but not a guarantee of AI visibility on its own.

The schema types that deliver the most consistent value across both traditional and generative search include Organization, Article, BlogPosting, Product, Person, and FAQPage. Google has deprecated HowTo and general FAQPage rich results for most sites, so focus your efforts on the types that still generate active rich result eligibility.

What schema markup looks like in a website’s code

Schema markup appears in three formats: JSON-LD, Microdata, and RDFa. Google recommends JSON-LD for all new implementations because it sits inside a dedicated script block, completely separate from your HTML content, which makes it easier to manage and validate.

A JSON-LD block looks like this in your page source:

It opens with <script type=”application/ld+json”>
Every block contains an @context field declaring the vocabulary, almost always https://schema.org
Every block contains an @type field declaring the entity type, such as Article, Product, or LocalBusiness
The remaining fields are key-value pairs describing properties of that entity
The block closes with </script>

JSON-LD can be placed anywhere in the <head> or <body> of a page. Microdata and RDFa, by contrast, are woven directly into HTML attributes alongside visible content tags, which makes them harder to update without touching the page layout. The schema.org vocabulary contains more than 800 structured definitions, but Google only supports roughly 30 of those types for rich results, so not every valid schema block will produce a visible SERP enhancement.

Knowing what you are looking for makes every checking method below faster and more reliable. The key strings to search for are application/ld+json, @context, and @type.

Check schema markup with Google’s Rich Results Test

Google’s Rich Results Test is the official starting point for checking schema markup on any live page. It tells you which Google rich result types your page is eligible for, flags errors and warnings in your structured data, and previews how your rich results might appear in Google Search.

Go to Google’s Rich Results Test tool at search.google.com/test/rich-results.
Enter the full URL of the page you want to test and click Test URL. Alternatively, paste raw JSON-LD directly into the Code Snippet tab if you want to validate markup before publishing it.
Wait for the tool to fetch and render the page as Googlebot would. This typically takes a few seconds.
Review the results panel. The tool lists every schema type it detected and shows whether each one is Valid, contains Warnings, or contains Errors.
Click into any detected schema type to see the full property breakdown and the specific field causing each error or warning.
Use the desktop and mobile preview tabs to see how your rich results would appear in Google Search on each device type.

After running the test, you should see a clear list of detected schema types. Errors appear in red and indicate missing required fields that prevent rich result eligibility. Warnings appear in orange and flag optional improvements. A green Valid status means the schema meets Google’s requirements for that rich result type.

One important limitation to understand: the Rich Results Test validates schema against Google’s supported rich result types only, not the full schema.org vocabulary. If your page uses schema types that Google does not support for rich results, such as a custom or niche entity type, the tool will not flag them. Pages behind login walls, authentication, or staging environments blocked by robots.txt cannot be tested in URL mode. Use the Code Snippet mode for those.

Validate structured data with Schema.org’s validator

The Schema Markup Validator at validator.schema.org checks your structured data against the full schema.org vocabulary, not just the subset Google uses for rich results. Use it after the Rich Results Test to catch syntax errors and vocabulary issues that Google’s tool does not cover.

Go to validator.schema.org.
Enter the URL of the page you want to validate, or paste the raw markup directly into the text input field.
Click Run Test.
Review the structured data graph the validator extracts. It displays every entity it found, the properties attached to each, and any syntax mistakes.
Check for errors in property names, missing required fields for specific schema types, and any vocabulary terms that do not exist in the schema.org specification.

The Schema Markup Validator also extracts structured data injected by JavaScript, which makes it useful for pages where schema is added dynamically by a plugin or widget rather than hardcoded into the HTML. This is a meaningful advantage over manual source code inspection, which may miss JavaScript-rendered markup.

Google’s own documentation recommends a two-tool workflow: start with the Rich Results Test to check Google-specific eligibility, then use the Schema Markup Validator for broader schema.org compliance. Running both gives you complete coverage. The Rich Results Test tells you what Google will do with your schema. The Schema Markup Validator tells you whether your schema is technically correct at the vocabulary level.

Inspect schema markup manually in browser source code

Manual inspection is the fastest way to confirm whether any schema markup exists on a page without using an external tool. It is also useful for checking competitor pages or any URL you cannot submit to a testing tool.

Using View Page Source

Open the page in your browser.
Right-click anywhere on the page and select View Page Source (Chrome, Firefox, Edge) or the equivalent in your browser.
Press Ctrl+F (Windows) or Cmd+F (Mac) to open the find function.
Search for application/ld+json. Any match confirms JSON-LD schema markup is present on the page.
Search for @context or @type to locate the specific schema blocks and read their content.

View Page Source shows the raw HTML delivered by the server. It does not show content rendered by JavaScript after page load. If your schema is injected dynamically by a plugin or CMS, it may not appear here. In that case, use the browser’s Inspect Element panel and check the rendered DOM instead, or use the Schema Markup Validator, which handles JavaScript-rendered markup.

Using a browser extension

Browser extensions remove the need to read raw code. Two reliable options for Chrome are the Schema Markup Viewer by Egochi and the SEOMarkup Structured Data Schema Inspector. Both detect JSON-LD, Microdata, and RDFa simultaneously, display schema types found on the page with a count, and show the full structured data with syntax highlighting. The Schema Markup Viewer runs entirely locally with no data collected, which makes it safe for use on staging environments and internal pages.

Install either extension from the Chrome Web Store, then navigate to any page and click the extension icon. You will see a formatted summary of every schema block on the page in seconds. This method is particularly useful when auditing competitor sites to understand what schema types they are implementing.

Fix common schema markup errors and warnings

Errors in schema markup prevent rich result eligibility entirely. Warnings reduce your chances of appearing with enhanced features but do not block indexing. Fixing errors first delivers the most immediate impact.

The most common errors to fix

Missing required properties: A Product schema without a name, price, or description field will fail validation. Each schema type has a specific set of required properties listed in Google’s developer documentation.
Invalid JSON-LD syntax: Missing commas, unclosed brackets, or unescaped quotation marks break the entire schema block. Run your JSON-LD through a JSON validator to catch these before submitting to Google’s tools.
Deprecated schema types: Google retired HowTo rich results in August 2024 and restricted FAQPage rich results to government and health authority sites. Using these types on ineligible sites will not generate rich results.
Case sensitivity errors: Schema.org property names are case-sensitive. Writing DatePublished instead of datePublished causes a validation error. Always match the exact casing shown in the schema.org specification.
Duplicate schema from plugin conflicts: If your WordPress theme and an SEO plugin like Yoast SEO or Rank Math both output schema for the same entity, you may end up with conflicting or duplicate blocks. Check your source code for multiple @type: Article or @type: Organization declarations on the same page.
Schema that describes content not visible on the page: Google’s guidelines prohibit structured data that misrepresents the visible page content. This can trigger a manual action.

After fixing errors

Once you have corrected the errors, re-run the Rich Results Test to confirm the issues are resolved. Then open Google Search Console, navigate to the relevant Enhancement report, and click Validate Fix to request that Google recrawls and revalidates the affected URLs. Allow one to four weeks for Google to process the changes and reflect them in the Enhancement reports. Requesting reindexing via the URL Inspection tool in Search Console can speed up this process for individual pages.

Monitor schema markup across your entire website

Checking individual pages is useful for auditing and fixing specific issues. Monitoring your entire site over time requires Google Search Console and, for larger sites, a dedicated SEO audit tool.

Using Google Search Console

Log in to Google Search Console and select your property.
In the left sidebar, scroll to the Enhancements section. This section only appears if Google has detected structured data on your site.
Click any rich result type listed, such as Article, Breadcrumb, Product, or Event, to open its Enhancement report.
Review the trend graph showing valid items, warnings, and errors over time.
Click through to the list of affected URLs for any error or warning category.
After fixing issues, use the Validate Fix button to notify Google.

Google Search Console sends email alerts when new structured data issues are detected, but it does not send alerts when an existing issue worsens. Schedule a monthly manual check of the Enhancements section to catch regressions caused by theme updates, plugin conflicts, or CMS template changes. The URL list in each Enhancement report is capped at 1,000 URLs. For pages not included in that list, use the URL Inspection tool to review schema status individually.

Measuring schema impact on performance

In the Search Console Performance report, filter by Search Appearance > Rich Results to isolate the clicks, impressions, click-through rate, and average position driven specifically by rich results. This filter lets you measure the before-and-after impact of schema fixes and additions with real traffic data.

For larger sites, third-party tools like Ahrefs Site Audit and Semrush Site Audit include schema validation within their crawl reports, which makes it easier to identify structured data errors at scale without manually checking hundreds of URLs. If you are managing WordPress SEO across a large content library, the WP SEO Agent within WP SEO AI automates schema generation and monitors structured data health continuously, removing the need for manual audits on a page-by-page basis.

Schema markup is only effective when it is valid, current, and accurately reflects your page content. Regular monitoring through Google Search Console, combined with periodic validation using Google’s Rich Results Test and the Schema Markup Validator, keeps your structured data working as intended and your pages eligible for the rich results and AI visibility signals that schema enables.

Are you visible to ChatGPT & Google AI Overviews?