Schema Markup Audit Template

Technical SEO Toolkit, template 6 of 6

Schema Markup Audit Template

Check presence, syntax, required fields, visible-content match and policy for every structured data type you ship.

Which pages and schema types are ready to release, and which fail on syntax, required properties, content mismatch or policy.

  • Excel workbook (.xlsx), opens in Google Sheets
  • PDF field guide, 9 to 11 pages
  • Blank and worked CSV templates
  • DataForSEO import script

Free, no email required. Version 3.0, updated November 2026.

Schema Markup Audit Template.xlsx
L13fx=IF(J13="","",IF(J13<>"Ready","n.a.",IF(K13=0,"Meets listed checks","Fix or review")))

Start HereDashboardWorkspaceDelivery QAField Guide

The formula above is the real one from cell L13. Scroll it sideways to read the whole rule.

Connected to the DataForSEO API

This template is designed around one DataForSEO endpoint. Pull the data, convert it with one command, and the workbook does the rest.

Setup steps

DataForSEO On-Page APIA crawl of your site: URLs, status codes, canonicals, inlinks and sitemap membershipon_page/task_post

Save the JSON responseThe full API response, kept as your source of truth.response.json

Run the import scriptOffline. No API calls, no credentials.dataforseo_import.py import --template 18 --csv

Paste at A13Dashboard, checks and action list update instantly.Schema Markup Audit Template.xlsx

Column map for this template:Filled by the APIAudit trail (automatic)You add

Page URLSchema typeMarkup presentSyntax validRequired fields validMatches visible contentEligibility reviewedEvidenceSource reference
2 of 9 input columns come straight from DataForSEO

What the schema markup audit template decides

Structured data fails in three ways: it's broken (syntax errors), incomplete (missing required properties), or untrue (markup says something the page doesn't). The third is the one that gets sites into trouble, and validators can't catch it.

This schema markup audit template checks each URL and schema type against five conditions: markup present, syntax valid, required fields present, values match visible content, and a policy review. It counts failed checks and marks each Meets listed checks or Fix or review, so you have a release register, not just a validator screenshot.

Who it's for

  • SEOs and developers shipping JSON-LD templates
  • Ecommerce teams with Product, Offer and Review markup
  • Publishers using Article and Organization markup
  • QA leads who need a sign-off record

Where it fits in your workflow

The schema markup audit template answers one question. These three templates answer the questions around it:

  • Brand Entity Consistency Audit: which third-party profiles state your brand facts incorrectly, and which corrections to request and from whom.
  • Programmatic SEO Checklist: which programmatically generated pages are ready to release and which to hold, with the specific checks each one fails.
  • Indexability Audit Template: which pages that should be indexed have a technical conflict, which are technically fine but still not indexed, and which were never meant to be indexed.

What's inside the download

One ZIP with the workbook, a 9-column input template (blank and filled), the PDF field guide and an offline script that converts saved DataForSEO responses into the input CSV. The workbook has five tabs.

Workspace. The working table. 9 input columns, 3 calculated columns, room for 250 rows. Dropdowns, Yes/No fields and range checks catch bad inputs as you paste.
Start Here. What it decides, a four-step setup and the colour key.
Dashboard. KPI cards, charts, a ranked Top 10 and an automatic action list.
Delivery QA. Pass, fail or exclude each validation step with evidence, owner and date.
Field Guide. Every field explained, plus each formula in plain English.

How the schema markup audit calculation works

Failed checks = 5 − (markup present + syntax valid + required fields + matches visible + policy review). Zero failures = Meets listed checks.

The key formula, exactly as it appears in the workbook

=IF(J13="","",IF(J13<>"Ready","n.a.",IF(K13=0,"Meets listed checks","Fix or review")))
Result column Plain-English formula What it tells you
Failed checks 5-SUM(Markup present,Syntax valid,Required fields valid,Matches visible content,Eligibility reviewed) Number of unmet implementation and review checks.
Schema release review IF(Failed checks=0,"Meets listed checks","Fix or review") Release review state, not a promise of rich results.

The results you will see

Meets listed checksFix or review

Green meets the checks, red needs fixing first, amber needs a human decision and blue marks an opportunity. Rows with missing or out-of-range inputs are held back in the Input check column until they're fixed, so a half-filled row never sneaks into a total.

How to use the schema markup audit template

  1. List URLs per template and typeOne row per URL and schema type. Pick the type from the dropdown.
  2. Validate syntax and required fieldsUse the Rich Results Test and Schema Markup Validator. Record 1 or 0 for each.
  3. Compare with the visible pageCheck that prices, ratings, dates and names in the markup match what users see.
  4. Review policyCheck eligibility rules, e.g. self-serving reviews and FAQ rich result restrictions. Record the outcome.

The worked example in the Workspace tab. Clear the lime input cells, paste your CSV at A13 (values only) and every result recalculates.

Fill the schema markup audit template with DataForSEO

Every template in this library is built to run on DataForSEO data. This one uses DataForSEO On-Page API: a crawl of your site: URLs, status codes, canonicals, inlinks and sitemap membership.

This is a sign-off workflow. DataForSEO responses are the evidence you attach; the human checks stay manual by design.

  1. Request the dataSend this request with your DataForSEO API login (HTTP Basic auth).
    POST https://api.dataforseo.com/v3/on_page/task_post [ { "target": "yourdomain.com", "max_crawl_pages": 1000 } ]

    Post the crawl task, wait for it to finish, then request on_page/pages with {"id": "<task id>", "limit": 1000} and save that response.

  2. Save the full JSON responseSave the complete response, not just the task ID, next to the template folder.
  3. Convert it with the included scriptIt runs offline, makes no API calls and never sees your credentials.
    python3 Automation/dataforseo_import.py import --template 18 --csv --input my-filled.csv --output my-inputs.csv
  4. Add what the API can't knowSchema type, Markup present, Syntax valid, Required fields valid, Matches visible content, Eligibility reviewed, Evidence
  5. Paste at A13Clear the demo rows, paste the CSV values at Workspace cell A13 and the dashboard updates.
Fills automatically from DataForSEO You add
Page URL Schema type, Markup present, Syntax valid, Required fields valid, Matches visible content, Eligibility reviewed, Evidence

Source reference fills automatically with the task ID, endpoint, location, language, device and snapshot time, so every row is traceable. Before a big pull, estimate the cost with the DataForSEO pricing calculator. The same steps, plus an example request file, are in the download's Automation folder.

Worked example: Northbeam Outdoor

Every template ships filled with data from Northbeam Outdoor, a fictional outdoor-gear retailer that appears across all 40 workbooks, so you can see what useful output looks like before you add your own. This workbook has 12 example rows.

12Records
0Rows with input issues
9Open schema checks
6Templates passing

The example catches a Product page whose markup says $39 while the page shows $44, a syntax error on a store page, and self-serving review markup that would be ignored or worse.

Top 10 by failed checks

# Page URL Failed checks
1 https://www.northbeam.example/guides/layering/ 4
2 https://www.northbeam.example/reviews/ 1
3 https://www.northbeam.example/stores/albany-ny/ 1
4 https://www.northbeam.example/guides/boot-fit/ 1
5 https://www.northbeam.example/products/hydro-flow-filter/ 1

Input fields

Keep the columns in this order when you prepare a CSV. A missing observation stays blank; use 0 only for a measured zero or a verified No. Fields marked DataForSEO can be filled automatically by the included script.

CSV field Column Meaning and rule Source
url Page URL Exact absolute URL. Keep case and query parameters unless a documented normalization rule applies. DataForSEO: url
schema_type Schema type Actual schema.org type used for this page. Your records
markup_present Markup present 1 after inspecting rendered HTML or the relevant response. 1 = Yes, 0 = No. Your records
syntax_valid Syntax valid 1 after a schema syntax validator accepts the markup. 1 = Yes, 0 = No. Your records
required_fields Required fields valid 1 after validating fields for the intended feature, where applicable. 1 = Yes, 0 = No. Your records
matches_visible Matches visible content 1 only after a human verifies factual agreement with visible content. 1 = Yes, 0 = No. Your records
policy_review Eligibility reviewed 1 after reviewing feature eligibility and content policies. 1 = Yes, 0 = No. Your records
evidence Evidence Link to a dated crawl, screenshot, ticket or source that another reviewer can inspect. Your records
source_ref Source reference Task ID, export filename and observation scope. Retain the untouched source response separately. Optional. DataForSEO: source_ref

Reading the result honestly

A syntax-valid entity can still be factually wrong or ineligible for a feature. Review those dimensions separately.

Limits. Generic markup presence is not type-specific validation. FAQ markup is not a universal rich-result or AI-citation tactic.

Schema markup audit mistakes to avoid

Marking up content users can't seeMarkup must describe visible content. Hidden or invented values violate guidelines.
Chasing deprecated rich resultsFAQ and HowTo rich results are heavily restricted. Markup can still help understanding, but don't expect the visual result.
Validating one URL per templateData issues vary by page. Sample several URLs per template, especially products.

Tips from practice

  • Organization and LocalBusiness markup with sameAs links supports entity consistency.
  • Add schema checks to your release QA and the programmatic SEO checklist.
  • Recheck Product markup after price or stock feed changes.

Frequently asked questions

How do I audit schema markup?

Validate syntax, check required and recommended properties for each type, confirm the values match the visible page, and review eligibility policies.

What's the difference between the Rich Results Test and the Schema Markup Validator?

The Rich Results Test checks Google rich result eligibility; the Schema Markup Validator checks schema.org syntax generally.

Does structured data help AI search?

Accurate markup helps machines understand entities and facts on the page, which supports both search features and AI systems that read structured data.

Is structured data a ranking factor?

Not directly. It enables rich results and clearer understanding, which can improve click-through.

Part of the Technical SEO Toolkit

Get all 6 Technical SEO templates in one ZIP, or the complete set of 40 SEO and GEO templates with the 401-page field handbook.

Download the Technical SEO Toolkit

See the complete SEO & GEO toolkit

Jourdan Rombough

Built by Jourdan Rombough, technical SEO and GEO consultant with 15+ years in search. About Jourdan or get an SEO plan.

More on digital marketing in our blog

See all posts