Structured Data

Schema And Entity Coverage

A page-level evidence report showing structured-data coverage, JSON-LD health, sameAs references, extracted entities, and weak entity signals across important URLs.

Best for: Schema specialists, content strategists, local SEO teams, and product owners.

Try this report API docs All examples

Schema And Entity Coverage Structured Data

10Pages Audited

92Schema Score

1Invalid Blocks

5Entity Gaps

Item	Status	Evidence
/	Strong	Organization and WebSite schema with sameAs evidence.
/services/root-canal	Gap	Service entity appears in copy but not structured data.
/pricing	Invalid	One JSON-LD block failed parsing.

What It Includes

Schema type coverage by page and schema score
Invalid JSON-LD, missing sameAs, weak entity, and missing organization/person/product evidence
Entity-to-page map for local, service, product, and brand pages
Action list for structured-data cleanup and entity reinforcement

How It Is Generated

Page HTML and structured-data extraction
JSON-LD graph and microdata parsing
sameAs references and extracted page copy entities
Indexation and crawl eligibility context

API Inputs

/v1/schema/audit/v1/entities/map/v1/indexation/snapshots

MCP Uses

Ask which pages have weak organization or service entity evidence.
Draft schema cleanup recommendations for a developer.
Compare entity coverage between service pages.

Ways People Use It

Schema Debugging Structured-data specialist

Find invalid JSON-LD blocks, parse errors, schema types, sameAs gaps, and the affected page.

The specialist can fix the exact block instead of only seeing a generic schema warning.

Entity Coverage Review Content strategist

Compare service pages to see which ones mention entities in copy but lack structured data support.

Content and schema teams can reinforce the pages most likely to confuse downstream tools.

MCP Schema Assistant Non-technical operator

Ask which pages need Organization, Service, or SoftwareApplication evidence and why.

The assistant answers with URL, issue reason, and action instead of vague best practices.

Evidence Contract

The live API returns the issue plus the evidence around it: what happened, where it happened, when it was observed, why it matters, and how to act.

Question	Where It Comes From	Example
What	Issue ID, severity, message, schema, crawl, or GSC state	`jsonld_invalid`, `schema_missing`, `noindex_detected`
Where	URL, site, client, final URL, JSON-LD block index, or endpoint row	`/pricing`, block `0`
When	`generated_at`, `fetched_at`, event timestamps, and history metrics	Last observed during the current refresh.
Why	Evidence fields, parse errors, HTTP status, GSC verdict, and crawl facts	JSON parse error, noindex header, sitemap leak, or canonical conflict.
How	Recommended actions and MCP or report prompts	Fix malformed JSON-LD, remove noindex, update sitemap, or consolidate canonical.

For malformed JSON-LD, the API records the affected page, fetch time, invalid block index, parser error, issue severity, and recommended action. It intentionally avoids storing raw page payloads unless a future redacted evidence store is enabled.

Example API Flow

curl.exe -H "Authorization: Bearer YOUR_API_TOKEN" https://indexpulseapi.com/v1/schema/audit

MCP prompt example:
"Ask which pages have weak organization or service entity evidence."