LEYUN · SITE LAUNCH CHECKLIST独立站上线自查清单库

Structured Data Self-Check for an Own-Brand Site

Sections: Entity & Compliance · Reviewed: 2026-11-21 · 12 items

Key takeawayStructured data restates information already on the page in a machine-readable form. It cannot create content, and when written wrongly it creates contradictions, so the review focuses on consistency and convention.

Industries and use cases

  • After a new template is built
  • After adding product, article or Q&A page types
  • When Search Console reports markup errors
  • After a CMS migration loses markup

Checklist

Checklist: structured data self-check
Check itemPass criteriaRisk levelFix hint
Format choiceJSON-LD only, placed in head or at the end of body and not mixed with other formatsHighKeep one JSON-LD block per page for easier maintenance and debugging.
Type matchPage type matches markup type: Product for products and Article for postsHighDo not stack types unrelated to the business, which can read as misleading.
Required fieldsAll required fields for the chosen type are filled with no empty values or placeholdersHighCheck against the official type documentation, since one gap invalidates the item.
Values match the pageName, price, rating and dates are identical to the visible contentHighRender markup from page data rather than hard-coding it.
URL formatURLs are absolute and image addresses resolve directlyMediumRelative paths fail in some contexts, so output complete addresses.
Date formatISO 8601 with a timezone or consistently in UTCMediumFormat at template level to avoid several conventions coexisting.
Price and currencyPrice is a number and currency uses a three-letter code such as USDHighInclude price validity so outdated prices do not stay on display.
Organization declarationOrganization data is declared once, on the home or about pageMediumSeveral organisation declarations confuse entity resolution.
NestingProduct, brand, review and offer nesting is structurally correctMediumSplit deeply nested structures into separate types for stable parsing.
No unrelated typesNo markup for content that is not shown, such as ratings without reviewsHighInvented ratings are a serious violation, so absence is better than fabrication.
ValidationThe rich results test shows no errors and warnings are assessed individuallyHighCheck three page types after every template release.
OwnershipMarkup templates have a named maintainer and a traceable change historyLowInclude markup in code review so temporary edits do not break it.

Common misjudgements

  • Assuming more markup is better: types unrelated to the page are ignored and can lower overall credibility.
  • Chasing a clean tool report only, when valid syntax with invented values is the more serious problem.
  • Expecting markup alone to produce rich results, which depend on the system and are only partly influenced by markup.

How to use this checklist

  • Pair with the rich results workflow: one sheet covers fields, the other covers process.
  • Run after template changes and validate everything quarterly.
  • Link with the brand entity sheet so Organization data comes from the same source.

FAQ

How can markup be maintained without a technical team?
Use the structured data module built into the CMS and fill in fields rather than editing code by hand.
Can one page carry several types?
Yes, provided each type has real matching content and they do not conflict.
Will markup errors penalise a site?
Usually not directly, but rich results fail or the markup is ignored.
Version notes2026-11-21: first release, compiled from official Google documentation and public sources; updated as engine rules and regulations change.

If you prefer not to verify each item yourself, a pre-checked B2B template site package is available as an alternative.

Note: this checklist is a self-check reference only. Search-engine behaviour and regulations follow the latest official documentation of each provider and jurisdiction.