01

Begin with page meaning

Identify the primary visible entity and purpose of the page. Select a supported type only when the required information is genuinely present. Markup should describe content for machines; it should not manufacture claims or eligibility.

02

Keep visible and machine data aligned

Names, dates, authors, ratings, prices, and availability must match what visitors can see and what the business can support. Template variables reduce drift, but they also spread mistakes quickly, so validate representative pages before release.

03

Test and monitor

Use validation tools before deployment and monitor enhancement reports afterward. Warnings are not all equal; prioritize errors that make the markup invalid or misleading.

  • Eligible page type confirmed
  • Required fields visible
  • Representative URLs tested
  • Owner assigned for updates
04

Know when to skip

Skip markup when content is thin, frequently inconsistent, or not eligible for the intended feature. Structured data does not substitute for crawlability, indexing, accurate content, or a useful page.

Primary references

Sources are provided for policy and technical context. External pages can change after our review date.

Editorial note

Prepared by the SiteSignal Hub research desk. This article is educational and does not guarantee search rankings, advertising approval, or business results. Read our editorial standard.