Sitewide structured-data governance

Cross-Page Schema Entity Conflict Auditor

Join JSON-LD from many pages into one explainable entity graph. Find shared IDs with conflicting values, duplicate Product emitters, broken references, unstable Organization IDs, repeated blocks, and canonical mismatches.

Browser-only processingNo paid APIEvidence and provenanceCSV, JSON, Markdown exports
  1. 1Add data
  2. 2Map and review
  3. 3Configure
  4. 4Analyze
  5. 5Review and export

Add data

Choose files or paste an export

Accepts HTML files, a ZIP of supported files, crawl CSV, JSON, JSONL, and NDJSON. Limits: 100 MB expanded, 2,000 files, and 1,000,000 property assertions per analysis.

Evidence detail

What this cross-page audit can and cannot prove

Identity and conflicts

Compares normalized IDs and selected property assertions while preserving each page, block, source, and template.

Conservative matching

Suggests strong-key candidates but does not merge anonymous entities or guess which plugin is at fault.

Not an eligibility test

Separates parse validity and structural evidence from Schema.org or Google feature eligibility.

Supported inputs and deliberate limits

HTML extraction supports inert application/ld+json scripts containing one object, arrays, and @graph. Crawl exports can map URL, canonical, title, template, status, indexability, date, source signature, and multiple JSON-LD columns. JSON and NDJSON records can use url plus jsonld or blocks.

This version does not parse Microdata or RDFa, execute JavaScript, fetch live URLs, repair JSON5 syntax, inspect encrypted archives, or claim that a reported conflict is a search-engine violation.

Frequently asked questions

No. It analyzes HTML, ZIP, CSV, JSON, and NDJSON data that you choose locally. It does not fetch live pages or connect to Search Console, analytics, or a crawling service.
No. File reading, JSON-LD parsing, graph construction, filtering, and exports happen in your browser after the page assets load. A normal refresh clears the working data.
Not necessarily. The auditor separates JSON parse errors from structural observations and cross-page governance findings. It does not replace Schema.org Validator or Google rich result testing.
Anonymous entities remain separate. The auditor only offers conservative candidate matches when strong keys such as an exact GTIN, SKU plus brand, canonical URL, or normalized address plus phone agree. It never merges candidates automatically.
Standard ZIP archives containing HTML, JSON, NDJSON, JSONL, or CSV files are supported when entries use stored or deflate compression. Encrypted archives and ZIP64 are deliberately unsupported.
Reviewed Jul 2026 · Sources and limitations

Review details: 2026-07-13 · Marc LaClear · v1.0

Reference sources:

Known limits:

  • This tool analyzes only the files and extracted fields you provide. It does not fetch live pages, execute JavaScript, inspect CMS configuration, or prove which component is responsible without supplied provenance.
  • Findings describe conflicts and implementation evidence; they do not guarantee indexing, rankings, rich results, or Google feature eligibility.
  • Anonymous entity matches remain candidates until a person confirms identity. Weak similarity is deliberately excluded.
  • Encrypted ZIP, ZIP64, Microdata, RDFa, JSON5 comments, trailing commas, and automatic repair of invalid JSON-LD are not supported in this version.

Report an issue with this tool