Technical SEO · Supporting checklist

Structured Data Audit Checklist

A structured data audit checklist is a review of the machine-readable facts your pages publish. Compare markup with visible content, choose appropriate types, validate the live output and resolve conflicting or stale entities. Finish with a template inventory and tested examples, while keeping schema validity separate from rich-result display.

Free to useNo account neededSaved in your browser
Visible page content connected to matching structured cards inside braces, with a magnifying glass for comparison.
Compare structured data with visible content and verify supported properties and types.
Your working checklist

Work through the checklist

Click a square to mark a task as Pass. Click again to undo. Use the result menu for a problem, a blocker or a task that does not apply. You do not need to enter notes.

18 checks

Inventory Templates and Choose Appropriate Types

A structured data inventory shows what each page describes, which component creates its markup and which search feature, if any, applies. Start with the real page content before choosing a type.

List the templates, markup types and code owners

Find repeated problems at their generating source.

Use this for: Sites auditing existing structured data or planning a first implementation.

Choose representative pages from your actual templates, such as the homepage, service page, article and product page. Inspect their source or use a crawler configured to extract structured data. Look for JSON-LD script blocks, Microdata or RDFa, and check the rendered page if scripts add markup.

For each template, identify the types found and the plugin, theme, tag manager or custom component that produces them. Include a normal example and a relevant unusual state. A missing type is an opportunity to evaluate, not automatically an SEO error.

Example

Hypothetical example: An article template contains one Article block from the SEO plugin and another from the theme. The inventory identifies both owners before either is changed.

  1. Choose sample URLs across the actual page templates.
  2. Identify their markup formats, types and generating components.
  3. Include a relevant missing-field or recently changed example.
More help and optional notesHigh · SEO lead and developer
PassThe sampled templates have a clear markup inventory and an identified implementation owner or next investigation.
FailImportant templates or generating components are omitted from the inventory.

If it fails: Expand the sample and identify the component responsible for the missing coverage.

Retest: Update the inventory after theme, plugin or template changes.

Not applicable: No URLs or implementation in this task’s scope.

Optional: the affected page or template, what you observed and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Choose types that fit the page and verify current feature support

Separate descriptive vocabulary from Google search eligibility.

Use this for: Every proposed or existing structured data type.

For each page, name the main thing it actually presents: an organization, article, product, event or another entity. Check the corresponding Schema.org definition, then Google’s current supported structured data gallery and feature documentation if a Google appearance is the goal.

Check any audience, content, region or implementation limits in that feature’s documentation. Schema.org contains types that do not have a Google rich result. Do not label a service page as a product or a general list as a how-to solely because a plugin offers that option.

Example

Hypothetical example: A consulting page accurately describes a service. The team does not invent a product price or rating to make it resemble an eligible shopping result.

  1. Identify the real page entity and suitable schema type.
  2. Check current Google feature support and its specific eligibility rules.
  3. Exclude types or properties that do not describe the content.
More help and optional notesHigh · SEO lead
PassEach selected type fits the page, and any intended Google feature has been checked against current requirements.
FailA type misrepresents the page or relies on an unsupported or outdated feature promise.

If it fails: Choose an accurate type and remove an inapplicable feature target.

Retest: Recheck the type’s documentation when the implementation or feature support changes.

Not applicable: No URLs or implementation in this task’s scope.

Optional: the affected page or template, what you observed and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Compare markup facts with the content visitors can read

Catch accurate-looking code that describes the wrong facts.

Use this for: All markup that describes page-specific facts.

Open the sample page and compare important markup values with the visible content: name, identity, price where applicable, availability, author, dates and any ratings. Check the exact item and current state, rather than assuming every page on the template shares the same values.

If a mismatch appears, identify which data source is stale. The fix may belong in the page, the structured data or their shared source. Do not add unsupported claims to the visible page merely to justify an existing schema field.

Example

Hypothetical example: A product page displays a sale price while its JSON-LD still contains last month’s price. The developer aligns both outputs with the current product record.

  1. Compare the page and markup side by side.
  2. Check the current item and values that matter to the visitor.
  3. Trace a mismatch to its authoritative content source.
More help and optional notesHigh · Site editor and developer
PassThe checked structured facts accurately describe the current visible page and its main entity.
FailMarkup includes stale, hidden, invented or wrong-item facts.

If it fails: Repair the underlying content mapping and remove unsupported claims.

Retest: Compare the same fields after the content and markup regenerate.

Not applicable: No URLs or implementation in this task’s scope.

Optional: the affected page or template, what you observed and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Validate Syntax, Properties and Entity Relationships

Use the Schema Markup Validator for the vocabulary check and the Rich Results Test for supported Google features. A green result still needs a content and policy review.

Check JSON-LD syntax and schema vocabulary

Separate a parsing failure from an eligibility decision.

Use this for: Pages with JSON-LD, Microdata or RDFa to audit.

Open the Schema Markup Validator and test the public URL or paste the page’s markup. For JSON-LD, inspect parsing errors such as broken quotes, missing commas or malformed values. Review whether the types, property names and value types describe the intended entities.

If a script generates the block, compare the tested code with the live rendered version. Ask the developer to serialize data safely rather than assemble JSON by hand, especially when content contains quotes or line breaks. Only test public markup you are authorized to share with an external validator.

Example

Hypothetical example: An article title contains quotation marks that break a hand-built JSON-LD string. The developer uses the platform’s JSON serializer and retests the output.

  1. Run the markup through the Schema Markup Validator.
  2. Inspect parse errors and invalid type/property/value combinations.
  3. Compare the tested block with the actual generated page.
More help and optional notesHigh · Developer
PassThe tested markup parses and uses appropriate vocabulary and values for the described entities.
FailA parse failure or incorrect vocabulary/value combination prevents a reliable interpretation.

If it fails: Correct the serializer, property or data mapping at its generating source.

Retest: Validate the repaired output and a sample containing unusual characters.

Not applicable: No URLs or implementation in this task’s scope.

Optional: the affected page or template, what you observed and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Test required properties for the supported Google feature

Fix critical issues without inventing optional facts.

Use this for: Markup intended for a feature supported by the Rich Results Test.

Use Google’s Rich Results Test on the public URL and open each detected supported item. Read the critical errors and non-critical warnings separately. Compare the reported properties with the current documentation for the exact feature, not a generic plugin score.

A missing required fact must be supplied truthfully or the feature may not fit the page. Add a recommended property only when it is accurate and useful. A result with no detected supported items does not by itself mean all Schema.org markup is absent or invalid.

Example

Hypothetical example: The test reports a recommended image field missing from one item. The editor checks whether an appropriate real image exists instead of inserting an unrelated placeholder.

  1. Test the live URL and inspect each supported item.
  2. Separate critical errors from recommended-property warnings.
  3. Compare the findings with the feature’s current official rules.
More help and optional notesHigh · SEO lead and developer
PassThe relevant supported items have no unresolved critical validation issues and recommended-property decisions are truthful.
FailA critical feature error remains or fabricated data was added to satisfy a warning.

If it fails: Repair the accurate data or revise the intended feature when the page cannot meet its requirements.

Retest: Repeat the URL test after the actual page output changes.

Not applicable: The markup has no feature supported by the Rich Results Test.

Keep in mind: Passing this test establishes neither rich-result display nor compliance with every content policy.

Optional: the affected page or template, what you observed and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Keep entity IDs stable and connect the right things

Make related markup describe a consistent page and organization.

Use this for: Markup that uses linked entities, @graph or repeated site-wide identities.

Review @id values with the developer. Use a stable identifier for the same organization, person or page wherever it is referenced, and distinct identifiers for genuinely different entities. A canonical URL plus a meaningful fragment can distinguish a page from the organization described on it.

Follow relationships such as publisher, author and mainEntity. Confirm that each reference points to the intended entity rather than a copied ID from another page. IDs organize meaning; adding more IDs does not create a ranking guarantee.

Example

Hypothetical example: Several articles reference the same real publisher’s organization ID, while each article keeps its own page-specific ID. One copied article ID is corrected.

  1. List the main entity IDs and their references.
  2. Check that repeated identities stay consistent and different entities stay distinct.
  3. Follow publisher, author and main-entity references to the right item.
More help and optional notesMedium · Developer
PassThe checked IDs consistently identify the intended entities and their relationships.
FailAn ID changes unnecessarily, identifies different entities or connects a page to the wrong item.

If it fails: Normalize the ID generation and repair the incorrect relationship.

Retest: Compare IDs across representative pages and after content updates.

Not applicable: The implementation has no linked or repeated entity identifiers to review.

Optional: the affected page or template, what you observed and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Resolve conflicting markup from themes, plugins and scripts

Remove contradictory claims without deleting useful distinct items.

Use this for: Sites with several markup-generating components or repeated entities.

Compare all markup blocks on the same page, including those added after rendering. Look for different prices, dates, names or URLs describing the same item. Identify which plugin, theme or component generates each version before changing anything.

Multiple blocks are not inherently invalid: an article, breadcrumb trail and organization can all belong on one page. The problem is conflicting or misleading output. Choose a clear owner for each fact and preserve useful relationships when removing redundant generation.

Example

Hypothetical example: A theme and plugin both output the same article with different author names. The team fixes the authoritative mapping and removes the conflicting duplicate.

  1. Inspect every structured data block on the page.
  2. Compare repeated entities and important values.
  3. Identify the owner of each conflicting output.
More help and optional notesMedium · Developer
PassMultiple items are purposeful and no checked entity has conflicting duplicate facts.
FailTwo generators describe the same entity inconsistently or attach unrelated facts.

If it fails: Repair or remove the conflicting generation while keeping appropriate distinct items.

Retest: Reload and render the page, then compare all remaining blocks again.

Not applicable: No URLs or implementation in this task’s scope.

Optional: the affected page or template, what you observed and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Check Live Rendering and Search Access

Test the markup that the public URL actually delivers. A pasted code sample cannot reveal every rendering dependency, route-state problem or access barrier.

Inspect generated markup in the rendered live page

Catch missing or stale JSON-LD after JavaScript runs.

Use this for: Pages with generated markup or suspected source/rendered differences.

Run the live URL in the Rich Results Test or an available Search Console inspection, then inspect the rendered HTML. Search for the expected entity and a distinctive property value. Compare with the page source and what a visitor sees in a fresh browser session.

For an application with client-side navigation, move between two different items and check that markup changes with the page. A correct direct load can still leave the previous item’s JSON-LD after navigation. Use URL testing for JavaScript-generated data rather than relying only on pasted code.

Example

Hypothetical example: Opening a product directly shows correct markup, but navigating from another product leaves its old identifier. The shared route component needs a state update.

  1. Test the live public URL and open the rendered HTML.
  2. Find the expected entity and compare its facts with the page.
  3. Check a second route after client-side navigation when relevant.
More help and optional notesHigh · Developer
PassThe tested rendered output contains the correct current entity and values for the route.
FailMarkup is absent, stale or describes the previous route after rendering or navigation.

If it fails: Repair the rendering dependency or route-bound data update.

Retest: Repeat direct-load and relevant navigation tests on both affected routes.

Not applicable: No URLs or implementation in this task’s scope.

Keep in mind: A single live test describes that fetch and does not prove which version is indexed.

Optional: the affected page or template, what you observed and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Check access to the marked-up page and required resources

Keep otherwise valid markup from being hidden behind a delivery barrier.

Use this for: Pages intended to qualify for a Google search feature.

For a page intended for a Google search feature, open the final public URL directly and check its response and indexing directives. Investigate login requirements, robots restrictions and accidental noindex rules with the site owner. Keep private pages protected.

Open the image or other resource used by the applicable feature and verify that it loads correctly. Use a live URL test to investigate access failures. Do not expose restricted content or remove intentional controls simply to make a validation tool fetch a page.

Example

Hypothetical example: An article’s markup is valid, but its declared image is a private preview URL. The editor chooses the appropriate published image instead.

  1. Confirm the intended public page is accessible at its final URL.
  2. Check relevant crawl and indexing restrictions.
  3. Open the feature’s declared resources and investigate failures.
More help and optional notesHigh · SEO lead and developer
PassThe intended public page and relevant resources are accessible without unintended search barriers.
FailA delivery error or unintended restriction blocks the public page or required resource.

If it fails: Repair the correct public URL, resource mapping or accidental restriction while preserving privacy controls.

Retest: Retest the public URL and relevant resource after repair.

Not applicable: No URLs or implementation in this task’s scope.

Optional: the affected page or template, what you observed and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Check Organization Markup

Organization markup should identify the real business accurately. Prefer relevant public details and stable identity over filling every available field.

Verify the business identity and public organization details

Keep business markup tied to the actual organization.

Use this for: Sites with Organization markup or an appropriate organization subtype.

Compare Organization markup with the business information on the homepage or relevant identity page. Check the name, website, logo and any supplied contact or address details. Confirm that sameAs references identify the same organization, rather than unrelated profiles or directory search pages.

Use only applicable verified properties. Google’s Organization guidance does not require every possible field, and its general Organization documentation has no required properties. Do not publish private identifiers, invent credentials or pad the list of profiles to reach an arbitrary count.

Example

Hypothetical example: A business changed its logo and public contact address, but the homepage markup still uses the old values. The editor updates the shared organization record.

  1. Compare the markup with the public business identity page.
  2. Verify supplied logo, contact and same-identity references.
  3. Remove invented, irrelevant or unnecessarily private details.
More help and optional notesHigh · Site owner and developer
PassSupplied organization details accurately identify the business and match its relevant public information.
FailThe block contains stale, wrong-entity, invented or inappropriate private details.

If it fails: Correct the shared identity record and use only relevant verified properties.

Retest: Validate and compare the organization output on representative pages.

Not applicable: No organization markup is present or being implemented.

Optional: the affected page or template, what you observed and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Check Article Markup

Article markup should describe the actual article, its real authors and its genuine dates. A routine rebuild is not a new publication or a substantive update.

Verify article authors, dates, images and page identity

Avoid publishing false attribution or artificial freshness.

Use this for: Pages using Article, NewsArticle or BlogPosting markup.

On each sampled article, compare the headline, supplied author identities, article images and dates with the visible article. An author should be the actual person or organization responsible for that article; an author URL should help identify that same author.

Check that datePublished represents the real publication and dateModified reflects a genuine update when supplied. Do not reset those fields on every deployment. Confirm that copied templates do not keep another article’s identity or an unrelated image.

Example

Hypothetical example: A blog build resets every article’s dateModified each morning without changing the content. The developer connects the date to meaningful editorial updates instead.

  1. Compare article identity and authors with the visible article.
  2. Verify the meaning and source of supplied dates.
  3. Check that images and URLs belong to the current article.
More help and optional notesHigh · Editor and developer
PassThe supplied article facts, authors, dates and images accurately describe the current article.
FailThe markup invents attribution, artificially refreshes dates or describes another article.

If it fails: Correct the editorial field mapping and preserve authentic publication/update dates.

Retest: Validate a current article and an unchanged older article after a rebuild.

Not applicable: No article markup is present or being implemented.

Optional: the affected page or template, what you observed and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Review FAQ Markup Expectations

Google stopped showing FAQ rich results on May 7, 2026. A useful questions-and-answers section can remain on your site, but it should not be sold or measured as an available FAQ rich-result feature.

Review existing FAQ markup against current support

Remove outdated feature promises while preserving useful answers.

Use this for: Sites with FAQPage markup or plans based on FAQ rich-result visibility.

Identify pages or plugins using FAQPage and check why the markup is present. Google’s current documentation updates say FAQ rich results no longer appear, superseding the earlier restriction to certain health and government sites. Do not use that old restriction as a current eligibility test.

FAQPage remains part of Schema.org. If you retain it for a real descriptive purpose, compare the questions and answers with the visible page and keep them accurate. Retaining or removing valid markup is an implementation decision; the useful FAQ content need not be deleted.

Example

Hypothetical example: A plugin advertises FAQ stars or expanded Google answers as a benefit. The site removes that promise while keeping its helpful delivery questions visible.

  1. Find existing FAQPage output and its stated purpose.
  2. Replace outdated Google rich-result expectations.
  3. Verify any retained questions and answers against the visible page.
More help and optional notesMedium · SEO lead and editor
PassThe implementation has no obsolete FAQ rich-result expectation, and retained markup describes the visible answers accurately.
FailThe site relies on a retired feature promise or marks up different questions and answers.

If it fails: Update the feature expectation and repair or retire the markup deliberately.

Retest: Recheck the actual FAQ output and future official feature updates.

Not applicable: No FAQPage markup or related feature plan is in scope.

Optional: the affected page or template, what you observed and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Review HowTo Markup

HowTo remains a Schema.org type, but Google’s HowTo rich results are deprecated. Review semantic accuracy without treating a how-to label as a search-feature shortcut.

Check that retained HowTo markup describes a real procedure

Avoid assigning procedural markup to unrelated lists.

Use this for: Sites with HowTo markup or an implementation proposal using that type.

Find HowTo output and confirm that the page actually gives instructions for achieving a defined result. Compare the supplied steps, tools, materials and duration with the visible procedure. A list of tips, products or questions is not automatically a how-to.

Google no longer offers HowTo rich results. If the type is retained for another descriptive use, validate it as vocabulary and keep its facts accurate. Do not invent timings, tools or completed results to fill a generator’s fields.

Example

Hypothetical example: A general buying-tips list was labeled HowTo even though it teaches no single procedure. The editor chooses an accurate description instead.

  1. Confirm the page contains a genuine step-by-step procedure.
  2. Compare any supplied steps and attributes with the visible instructions.
  3. Remove the expectation of a Google HowTo rich result.
More help and optional notesMedium · Editor and developer
PassRetained HowTo markup accurately describes a real visible procedure and carries no deprecated Google feature promise.
FailThe type describes a non-procedure, invents attributes or relies on deprecated search visibility.

If it fails: Correct the type and attributes or retire the markup where no useful descriptive purpose remains.

Retest: Validate the final markup and compare it with the revised procedure.

Not applicable: No HowTo markup or proposal is in scope.

Optional: the affected page or template, what you observed and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Review Misleading or Irrelevant Markup

Structured data needs a human policy review as well as a validator. The markup must not make claims the page cannot support.

Remove hidden, invented and ineligible structured claims

Catch policy problems that a syntax test can miss.

Use this for: All structured data, especially review, rating and commercial claims.

Review the marked-up claims as a reader: are the subject, ratings, reviews, prices and other important facts actually relevant and supportable on this page? Check the specific policy for the type used. A valid JSON block can still describe misleading content.

For review snippets, do not expect stars from self-serving reviews of your own Organization or LocalBusiness, including an embedded third-party review widget. Do not invent ratings, aggregate unrelated reviews or add unrelated types merely to pursue a feature.

Example

Hypothetical example: A company adds its own service-rating average to its Organization block hoping to receive review stars. The team checks the review policy and removes the ineligible feature plan.

  1. Compare consequential markup claims with the visible evidence.
  2. Read the applicable type-specific policy.
  3. Remove unsupported claims and correct ineligible feature expectations.
More help and optional notesHigh · SEO lead and editor
PassThe reviewed claims are truthful, relevant and consistent with the applicable structured data policies.
FailMarkup is hidden, invented, irrelevant or used for an ineligible feature claim.

If it fails: Correct the facts and applicable type usage at the generating source.

Retest: Repeat the human policy review alongside the validator after repair.

Not applicable: No URLs or implementation in this task’s scope.

Optional: the affected page or template, what you observed and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Retest Template Changes and Read Reports Carefully

Finish with tested examples and a clear owner for each repair. Search Console helps find real-world issues, but its reports are not a complete schema inventory.

Test realistic missing-field and changed-content states

Make the template reliable beyond its best-looking example.

Use this for: Templates generating structured data from changing or optional fields.

Test a normal page and relevant edge states from the same template: a missing optional image, an author name with punctuation, an updated item or unavailable inventory where applicable. Compare generated markup with the visible state and rerun the appropriate validator.

Check that empty fields are omitted or handled correctly instead of becoming fabricated defaults. When facts change, confirm the visible page and markup update together. Use controlled test data or existing examples; do not alter live business facts just to run the audit.

Example

Hypothetical example: A product template falls back to an old price when inventory data is missing. The developer removes the false fallback and handles the unavailable state accurately.

  1. Choose relevant edge states for the template.
  2. Compare visible facts and generated output for each.
  3. Validate unusual characters, missing values and changed facts.
More help and optional notesMedium · Developer and content owner
PassThe sampled normal and edge states produce accurate, valid markup without fabricated defaults.
FailAn edge state breaks parsing, leaks a stale value or invents missing information.

If it fails: Repair the serializer or conditional field mapping and use appropriate missing-data behavior.

Retest: Repeat the same edge-state sample after the shared component changes.

Not applicable: No URLs or implementation in this task’s scope.

Optional: the affected page or template, what you observed and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Use Search Console reports without treating them as a census

Separate reported item issues from total site coverage.

Use this for: Sites with Search Console access and structured data under review.

In Search Console, review available reports under Enhancements, or Shopping for relevant product reports. Open a reported issue and inspect its example URLs and affected item type. Compare the report’s timing with your most recent live test.

Reports show samples of detected supported items, and counts refer to items rather than pages. An absent report or missing URL is not proof that the site has no schema. Use URL Inspection and your own template inventory for gaps, and read any reported manual action before deciding the next repair.

Example

Hypothetical example: A page contains two supported items, so its report contributes more than one item count. The team does not interpret that count as two separate pages.

  1. Open available rich-result reports and inspect issue examples.
  2. Check the item type and report timing against a live test.
  3. Use the inventory and URL Inspection to investigate missing examples.
More help and optional notesMedium · SEO lead

Before you begin: Search Console access for the relevant property.

PassAvailable reports have been interpreted by item, type and timing, with gaps investigated rather than assumed.
FailReported findings are dismissed or item samples are mistaken for complete page-level coverage.

If it fails: Correct the interpretation and investigate the actual affected item and template.

Retest: Review reports after Google processes the repair and compare with live tests.

Not applicable: No URLs or implementation in this task’s scope.

Keep in mind: Use Blocked when required report access is missing; do not treat the absence of a supported report as a failed schema implementation.

Optional: the affected page or template, what you observed and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Retest repaired templates and assign ongoing ownership

Close the original defect only when the live output is correct.

Use this for: Structured data implementation changes and repaired reported issues.

Fix the generating template, plugin setting or shared data mapping, then retest the original failing URL and another page using that component. Repeat the syntax, content, supported-feature and rendering checks affected by the change. Confirm that another valid item was not removed accidentally.

Assign an owner to recheck the markup after relevant content, theme or plugin changes. If Search Console offers Validate fix for the issue, use it after the affected examples are corrected. Its processing time and eventual display remain separate from your live validation result.

Example

Hypothetical example: A shared Article repair passes on the original page but removes the breadcrumb block elsewhere. The release remains open until both affected outputs pass.

  1. Retest the original failure on the published output.
  2. Check another affected template example and neighboring valid items.
  3. Assign the ongoing owner and use available report validation after repair.
More help and optional notesHigh · SEO lead and developer
PassThe affected live outputs pass their repeated checks, with no observed regression in related items.
FailThe original defect remains or the fix removes or corrupts another relevant item.

If it fails: Correct the remaining shared-output issue and repeat the affected tests.

Retest: Recheck when markup generation or the underlying business facts change.

Not applicable: No structured data fix or implementation change has been made yet.

Optional: the affected page or template, what you observed and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Reset this checklist?

This removes saved statuses, evidence and result dates for the checks on this page. Other checklists keep their records. Export a CSV first if you need a copy.

A useful result, every time

Check a task. Choose a result.

This is a manual SEO workflow. It helps you decide what to investigate and keep a usable record. It does not crawl your website or verify your answers automatically.

  1. Choose your scope. Pick the relevant task group and representative pages you are authorized to inspect.
  2. Run the stated check. Follow the steps, then choose your result. Click the square for Pass, or use the result menu for another status. You do not need to type anything.
  3. Assign the next action. Fix a problem when you can, or ask the right person for help. Optional notes can remind you what to do next. Check the result again after a fix.

What your progress means

Review progress counts passes and failures against applicable checks. Failed work still counts as reviewed. Blocked and untested checks remain unfinished. This is not an SEO score.

Untested
You have not checked this yet.
Pass
You checked it and it works as described.
Fail
You checked it and found something to fix.
Blocked
You need access, information or someone’s help.
Not applicable
This task does not apply to your website.

Export CSV downloads the checks currently shown and any optional notes. Print expands the instructions for that view. Saved results stay in this browser; there is no account sync.

Apply the workflow

What Should You Do With the Structured Data Audit Results?

Group findings by their generating template, fix the truthful source data and retest the affected live examples before closing the issue.

What Should a Structured Data Inventory Include?

A structured data inventory connects each page template to its main entity, markup generator, intended use and test result. It helps you fix one shared cause instead of editing the same issue on many pages.

Use these hypothetical examples as a starting point in your existing spreadsheet or issue tracker. Optional checklist notes can hold a short finding, but they are not required to save a result. Export CSV saves this checklist’s current view; it does not fetch markup or create a site inventory.

Hypothetical schema inventory entries and the checks they require.
TemplateMarkup and ownerMain checkNext action
Business homepage.Organization from the SEO plugin.Current public name, logo and contact details.Correct the shared identity record if stale.
Article.Article from the theme; BreadcrumbList from navigation.Real author and dates; accurate breadcrumb destinations.Keep distinct items and remove conflicting duplicate claims.
Product.Product from the store template.Current visible product facts and applicable feature rules.Follow the relevant product requirements and test changed states.
Questions page.FAQPage from a content block.Visible answers and a clear descriptive purpose.Remove obsolete Google FAQ rich-result expectations.

Which Structured Data Test Should You Use?

Use the Schema Markup Validator to inspect schema vocabulary and the Rich Results Test to check features that Google supports. Use the rendered live output to investigate JavaScript behavior, then review the page itself for truthful and relevant claims.

Each test answers a different question. Passing one does not replace the others, and a code-only test cannot establish that the live page serves the same markup.

Choose a test by the question you need to answer.
QuestionUseful checkWhat it cannot prove
Does this block parse and use schema vocabulary?Schema Markup Validator.Eligibility for every Google feature or factual accuracy.
Does a supported Google item meet tested requirements?Rich Results Test on the public URL.Guaranteed display or every policy condition.
What markup exists after scripts run?Rendered HTML from an available live URL test.That the same version is indexed.
Does the markup tell the truth about the page?Human comparison with visible content and type policies.Future visibility or a ranking improvement.

Why Can Valid Structured Data Have No Rich Result?

Valid structured data can have no rich result because syntax validity, feature support, policy eligibility and actual search display are different stages. A validator cannot promise how a result will appear for a particular search.

Check the supported type, access, current feature rules and content alignment before adding more markup. If those checks pass, the absence of a rich result alone does not establish a technical defect.

Are Multiple JSON-LD Blocks Always a Problem?

Multiple JSON-LD blocks are not automatically a problem. A page can legitimately describe an article, its publisher and its breadcrumb trail. Check whether the items have accurate relationships and whether repeated descriptions conflict.

When two generators disagree about the same entity, fix their ownership and data mapping. Counting blocks alone cannot distinguish useful related entities from duplicate contradictory output.

Which Checklist Handles the Related Page or Rendering Issue?

Fix the underlying page problem with its specialist workflow, then return to the same structured data samples for a final test.

A clear process, with honest limits.

Follow the steps, choose the result that matches what you found, and check again after changes. Notes are optional. A completed check does not guarantee indexing, traffic or rankings. How the checklists work.