Schema.org
Schema Markup for AI Search and Entity Understanding
Structured data states, in machine-readable form, who a page is about and how that entity relates to everything else you publish. The value is in the relationships being consistent — not in the size of the graph.
One company identifier
Company
/#organization- founderFoundersPerson
- makesOfferServicesService
- publisherWebsiteWebSite
Simplified view of relationships already declared in this site's JSON-LD.
Entity model
How the graph fits together
Structured data is only useful when the objects point at each other. The map below shows the relationships this site publishes today, using its own markup as the example.
The company object is the centre of the graph. Founders connect to it through founder, services through makesOffer, the website through publisher, articles through author, and external profiles through sameAs. Every relationship points back to the same company identifier.
Company
One stable identifier every other object refers back to.
- founderPerson
Founders
People connected to the company and to their own professional profiles.
- makesOfferService
Services
What the company delivers, described where the page actually describes it.
- publisherWebSite
Website
The site itself, published by the same organization identifier.
- authorBlogPosting
Articles
Posts that reuse the same author and publisher objects instead of new ones.
- sameAsURL
External profiles
Links to profiles the company controls, used to confirm identity rather than to add volume.
Markup shape
What the markup looks like
Shortened excerpts of the types this site publishes. Values are abbreviated for reading; the point is the shape and the shared identifiers, not the character count.
Sanitized excerpts for illustration. Not a schema generator and not a copy-paste template for another domain.
One organization object with a reusable identifier. Duplicated organizations are the most common source of contradiction.
{ "@context": "https://schema.org", "@type": "Organization", "@id": "https://inthemindai.com/#organization", "name": "InTheMind AI", "url": "https://inthemindai.com/", "logo": "https://inthemindai.com/brand/…", "founder": [ { "@id": "https://inthemindai.com/#ilia-onufriev" }, { "@id": "https://inthemindai.com/#artiom-cojocaru" } ], "sameAs": ["…"]}Scope
What earns a place in the graph
Each row pairs the decision we make with the failure it avoids. Most schema problems are not invalid syntax — they are valid markup describing something the page does not support.
- Identity
- One Organization and one WebSite object on the canonical domain
- Duplicate organizations with different identifiers are the usual failure
- People
- Person objects that point back at the company identifier
- Disconnected author objects describe a second, unrelated company
- Offer
- The type has to match what is actually sold
- Product properties chosen for richer output misdescribe a service
- Support
- Every property maps to something a reader can see on the page
- Markup for absent content is a contradiction, not an enhancement
What you get
A graph your team can maintain
The output is a map of your entities, the markup that expresses them and a record of which page supports each claim — so the next content change does not silently invalidate it.
- An entity map covering company, people, services and site
- Page-level markup plan with stable identifiers
- Validated JSON-LD in the production output
- An owner and a trigger for revalidation
FAQ
Frequently asked questions
Related GEO systems
Authoritative references
Next step
Ready to make your site citable by AI answer engines?
Tell us about your company and website. We will review the request and contact you to discuss the most relevant GEO and AI Visibility audit scope.