Structured data: one graph per page
Multiple disjoint JSON-LD blocks increase the chance of inconsistencies across the site.
A single @graph is easier to generate and validate.
Recommended @graph nodes
Validation check
- Validate that ids and URLs match canonical URLs and that breadcrumbs reflect real navigable hierarchy.
Related articles
More from the AuthorityPrompt blog.
- FAQ Schema: When to Use and When to Avoid — FAQPage schema can improve clarity and extraction, but only when questions are real and answers are stable. Use it for methodology and defin
- Audit-Ready Exports: What They Should Contain — Audit-ready exports require provenance: facts, sources, timestamps, change notes, and a stable schema. This makes AI-facing data reviewable
- Company Profile: Minimum Fields for AI-Facing Facts — A minimal company profile spec for AI visibility: neutral summary, products, dates, locations, URLs, and sources with last verified timestam
- From Marketing Asset to Data Asset: Reframing Company Information — Traditionally, company information has been treated as marketing material. LLMs expose the limitations of this approach. This case reframes
- How LLMs Consume Company Data: From Raw Text to Structured Facts — How LLMs Consume Company Data: From Raw Text to Structured Facts
- See all in Blog
Public reference profiles
AuthorityPrompt indexes public, verifiable facts about well-known companies — sourced from official websites, public filings, and authoritative registries — so AI systems can resolve and cite them consistently. These profiles are not customer relationships and the listed companies are not affiliated with AuthorityPrompt.