Give each entity a clear home
Start with the facts a visitor can see: the organisation name, the service, the author, the product and the relationship between them. Use the narrowest valid schema type, stable identifiers where they genuinely exist, and links that a person could follow. If the visible page says one thing and the JSON-LD says another, the markup is creating doubt rather than clarity.
Write for the person first
A schema block cannot repair a vague page. Use a direct heading, answer the obvious question near the top, explain the limits of the service, and make the important information available in server-rendered HTML. Then use structured data to label that information—not to invent a stronger claim.
- Match every schema property to visible, supportable copy
- Avoid ratings, awards or claims that cannot be substantiated
- Use descriptive internal links between related entities and pages
- Keep important answers in accessible, server-rendered HTML
Measure the signals that are actually available
Watch indexation, rich-result eligibility, query coverage, qualified enquiries and the pages people use before contacting you. Treat an AI mention as directional evidence, not a guaranteed channel. Clear pages and consistent entities make the site easier to interpret; they do not give anyone control over a third-party answer system.