What kind of thing is this?
Use the narrowest accurate schema type for the page: Person, Organization, WebSite, Article, Product, or LearningResource. Generic markup blurs the node the engine is trying to resolve.
GEO pathway · foundation 02
Markup is a claim, not decoration.
Structured data gives machines a compact version of the entity graph. If that graph is incomplete, contradictory, or disconnected from the visible page, it can make retrieval confidence worse instead of better.
Learning boundary. This lesson teaches an operating model. It is not a guarantee of ranking, citation, or inclusion in any specific engine's output.
Learning objective
Separate five implementation checks.
By the end of this lesson, you should be able to review a JSON-LD implementation, identify whether it resolves the intended entity, and explain why schema has to match the page a crawler can actually read.
Which node should engines merge?
Give the entity a durable @id and reuse it consistently across pages. Changing identifiers across pages fragments authority into separate nodes.
What corroborates the identity?
Connect profiles, canonical author pages, repositories, and social identities with sameAs only when they truly represent the same entity.
Can the page support the markup?
Every material schema claim should be visible or directly supported on the page. Hidden claims that humans cannot inspect create trust and quality problems.
Does the graph still parse?
Validate JSON-LD after each edit and update date fields when claims change. Broken syntax or stale dates can suppress the very signal the markup was meant to provide.
Practice lab · evidence before confidence
Score a founder profile schema.
A founder bio page includes Person schema with a name, job title, and three sameAs links. One link points to an old portfolio, one to the current company author page, and one to an unrelated company profile with a similar name. The visible page says the founder is a systems architect, but the schema still says "interim CMO" from a previous role. The JSON-LD has not been validated since launch.
- Score each dimension from 0: absent, 1: documented, or 2: tested.
- Name every claim that requires evidence before awarding a point.
- Identify the contradictions that could confuse entity resolution.
- Write the smallest safe next experiment.
Answer rationale
Entity type is 1 if Person is appropriate, but stable identifier and sameAs cannot score well while one link points to an unrelated entity. Visible claim match is 0 because the job title in schema contradicts the page. Validation is 0 if no one has parsed the JSON-LD after launch. The next step is to remove the unrelated profile, align the title with the visible bio, add or confirm a stable @id, and run validation before resubmitting the URL.
STOP → ALIGN