Use structured data to describe accurate facts already presented to readers. Choose an appropriate type, keep each value consistent with visible content and avoid unsupported reviews, credentials or relationships. Validate the published markup, maintain it when facts change and report search presentation separately from technical correctness.
Begin with a visible fact inventory
Structured data is a machine-readable description of page content. Start with an inventory of what the page actually says about the professional, service or article. For each proposed value, record its visible location and supporting basis. If a fact cannot be shown accurately to a visitor, adding it to hidden markup does not make it more appropriate or more credible.
Distinguish identity details, professional history and service claims. A name and profile address have different evidence needs from a qualification, client relationship or numerical result. Avoid copying a demonstration’s sample values into production. A fictional practice project must not acquire an invented organization, review or award simply because a schema generator includes fields for those properties.
Choose only relevant descriptive properties
Use the type and properties that genuinely fit the content and the search feature being considered. A broadly available vocabulary is not the same as support for every search presentation. Review the relevant current documentation rather than assuming that a valid property creates a badge, panel or special result. Do not add unrelated types simply to make the markup look more complete.
An external profile link can help describe identity when it truly concerns the same person, but it should not imply endorsement or verification by that platform. Similarly, an organization reference must reflect a real, accurately described relationship. Do not turn a past project into current employment or a course attendance into an awarded professional credential. Preserve material qualifiers in visible content and machine-readable values.
Validate the actual published page
Check syntax and the requirements relevant to the chosen markup using appropriate tools. Then inspect the published address, because a local file or editor preview may differ from the deployed page. Shared components can produce duplicate blocks, stale values or unexpected URLs. Record the tested address, date and issues found so a later maintainer can understand exactly what passed.
Google’s structured data guidelines require content alignment and explain that correct markup does not guarantee a rich result. A technical pass is therefore a limited statement: the tested markup met the tool’s checks in that context. It does not independently confirm the professional history, establish eligibility for unrelated features or prove that a search result currently displays enhanced information.
Maintain one accountable source of facts
Where the site supports it, derive visible information and markup from the same reviewed content source. This reduces the chance that a changed service title leaves old data elsewhere. Still inspect the rendered result after significant edits. Automated generation can repeat inaccurate source information very consistently, so the editorial review must happen before values become part of a shared template.
Include markup in the retirement and correction process. If a credential expires, a service closes or a contact address changes, review both the reader-facing page and its machine-readable description. Keep a short mapping of important properties to their content owner. Remove unsupported values instead of retaining them for perceived search benefits. Accuracy is the maintenance criterion even when no special search appearance is observed.
Fictional example: a template with imaginary ratings
A fictional consultant imports a profile template containing a five-star rating and a sample employer. Neither is supported by her actual page. She removes those values and builds a small fact inventory containing only her published name, professional description and public profile address. An illustrative workshop sample remains clearly described as practice material, without an invented customer review.
Her developer validates the resulting published markup and records the tested address and date. The review note states that the technical checks passed for the selected content; it does not label her professional claims independently verified or promise an enhanced search result. The example shows removal of misleading machine-readable claims and a narrower, maintainable representation of visible facts.
A checklist for your next step
- Map each value to visible content.
- Review the relevant current schema guidance.
- Remove sample reviews and relationships.
- Validate the published address.
- Update markup when facts change.
Common questions
Can hidden markup include extra credentials?
Do not use markup to introduce unsupported claims. Keep professional facts accurate, appropriately evidenced and consistent with what readers can see.
Does a successful validation guarantee a rich result?
No. Validation checks technical requirements in a particular context; search engines separately decide eligibility and whether to display a feature.
Further reading
These primary resources provide related background. They do not validate the illustrative example or endorse AliveProfile.
AI-assisted drafting and automated technical checks. Examples are illustrative; no independent expert review or real-world outcome validation is claimed. Read our editorial policy.