Article in English.
Structured data describes entities and page content in a machine-readable format. Use supported types that match visible information and validate the result on the published page.
A verifiable example from this website
KinetiqIT's tool pages describe the visible utility as a WebApplication and use the actual page URL. Its service pages describe the corresponding service. These can be checked in page source; they are descriptions, not evidence of customer outcomes. Review technical SEO checks alongside schema validation.
Choose a type that describes visible content
A service, an article and a software utility represent different entities. Use a relevant type and accurate properties; do not add reviews, ratings or business details that cannot be supported by visible information.
| Entity | Useful information to describe |
|---|---|
| Organisation | Accurate name, URL and public contact information |
| Article | Headline, author, publication details and the article URL |
| Product | The actual product and applicable offer details |
| Application | The visible utility, its URL and supported operating context |
| Breadcrumbs | The page's navigation hierarchy |
Schema vocabulary and Google features are different
A valid Schema.org type does not mean Google offers a corresponding search enhancement. Check the current feature documentation before promising a particular appearance.
For example, Google stopped showing FAQ rich results in May 2026. An FAQ can still be useful page content, but it should not be sold as a route to an expandable Google result. See Google's documentation changelog.
Validate the implementation
- Confirm the markup agrees with visible page content.
- Check required properties for any currently supported Google feature you are targeting.
- Inspect the rendered page rather than only the source template.
- Validate the vocabulary and applicable feature requirements using appropriate tools.
- Check the deployed URL again after a release.
Structured data does not guarantee a rich result, a ranking increase or more enquiries. Keep it accurate as content and URLs change.
Keep identity and URLs consistent
Use the actual public page URL rather than an internal message key or component name. Keep organisation references consistent across relevant pages and avoid creating several conflicting descriptions of the same entity.
Review the canonical and sitemap guide alongside structured data. Both should describe the intended public pages.