Which one belongs on the page you just finished? Start with what a visitor can see, then check for a matching Google Search feature. Use the one-page selection checklist to record your choice, supporting facts and test result.

Structured data is code that describes a page in a standard format. Schema.org supplies a broad vocabulary; Google documents the types and properties it uses for particular Search features. Valid code, feature eligibility and actual display are different questions. Markup does not guarantee a rich result, ranking or an AI citation. Google's introduction and general guidelines explain the distinction.

Google's AI features guidance says AI Overviews and AI Mode need no special schema.

Step 1: Write down what the page contains

Open the page as a visitor. Note its main task, headline, author or organisation, displayed dates and any details the code might describe. If the page has no visible rating, do not add one to the markup. If it is an explanation of a service, do not label it Recipe because that option appears in a plugin.

Illustrative example, invented page: A bakery publishes “How to store sourdough bread.” The page shows an author and publication date. It compares storage choices but has no measured ingredients or cooking method. This is an article to assess, not a recipe. The bakery and its data are fictional; no test or search result is claimed.

Step 2: Choose a feature that fits

Open Google's supported-feature gallery, then the guide for the feature you are considering. Ask whether the page's main content fits that feature. Separately check its required and recommended properties. Some features require particular fields; Article has no required properties. Article markup helps Google understand an article so its title, images and dates may be displayed better across Search, Google News and Google Assistant; it does not guarantee that display. For the bakery example, the useful decision is which recommended Article facts the page can support: headline, author, datePublished and, only if there was a genuine update, dateModified. A Breadcrumb can be considered separately if the site's visible navigation supports it.

Choose no additional feature markup when no documented Google feature fits. A Schema.org type can still describe a page to other systems. Record the reason.

Step 3: Compare visible content with the code

Make two columns: what the visitor sees and what the markup says. For the bakery article, compare its headline, author and publication date. If the code says it was modified today, check that an actual update happened and that the page communicates the change appropriately. Do not add a date merely to make a validator happy. Google's quality guidelines say structured data must represent the page and should not describe content hidden from readers.

List every JSON-LD block on the final rendered page and compare blocks that describe the same item.

What I found on my own site

My 28 October 2026 schema audit examined this live article. It found no critical mismatch: its BlogPosting headline matched the visible H1, its publication date matched the visible date, and its canonical and article URL agreed. The built HTML also contains a BreadcrumbList matching Home → Blog → article. The audit did not run Google's Rich Results Test or check whether Googlebot could fetch the social image. Those remain unknowns, not proven defects.

Step 4: Validate the right question

For the bakery's Article markup, use Google's Rich Results Test on code during drafting and on the URL after publication. Google's Article guide explicitly recommends that test for Article. Record detected items, errors, warnings and the test date. The tool checks supported Search features and technical issues; it cannot confirm every content-quality rule or whether a result will appear.

If you use a Schema.org type that Google does not list as a rich-result feature, use the Schema Markup Validator to extract the markup and identify syntax mistakes. It can examine JSON-LD, RDFa and Microdata, including markup injected by JavaScript. It does not decide Google feature eligibility. For either tool, compare the output with the rendered page yourself. After release, check the relevant Search Console report when one exists; use URL Inspection for a specific page-access or indexing question.

Failure modes to check before signing off

  • Plugin and theme: Check whether both emit duplicate or conflicting JSON-LD about the same page.
  • JavaScript: Check whether it injects markup after the initial source loads.
  • Invisible claims: Check whether the markup describes something the visitor cannot see.
  • FAQPage and HowTo: Check Google's current feature gallery before adding either. Google's documentation updates say FAQ rich results are no longer shown and How-to rich results were removed. Do not use either type as a shortcut to an enhanced result.

Leave a decision record

Save the page URL, chosen type or “none,” the visible facts that support it, the feature guide, test date and result, owner and next action. For the bakery example: “Assess Article with the visible headline, author and publication date; omit Recipe; test the final URL.” That is a plan, not a test result. Before handing it off, check that any required properties for the chosen feature are present, resolve mismatches and record what remains unverified.

For a wider content review, use the existing-page improvement guide; if the concern is indexing or a Search Console change, start with the diagnosis guide. For a focused page and markup review, ask about SEO consulting.

Reviewed 19 November 2026. Sources: Google structured data introduction and guidelines; Article and Breadcrumb guides; Schema.org Markup Validator documentation.

Vishnu Sudevan

Senior SEO, AEO & GEO consultant and practitioner. I write about search strategy, the tools I build and lessons from hands-on work.

More about my work →