Structured data: match schema to your website content
Choose appropriate article and breadcrumb markup, match visible content, validate JSON-LD and avoid invented review or business data.
Updated: · AI-generated editorial illustration
Structured data describes content in a machine-readable format. It can help systems understand an article, product or navigation hierarchy, but it cannot make a fact true merely by encoding it. Adding markup does not guarantee a rich result or repair an unclear page.
A small business website should start with the content it actually has and supported documentation rather than enabling every type offered by a plugin. This guide focuses on selection, data and validation rather than ranking promises.
1. Select markup from the page's purpose
An educational article may use Article or BlogPosting, and its navigation hierarchy can use BreadcrumbList. A product page needs product information and the applicable conditions. Do not attach LocalBusiness to an invented location or Product to an article simply in the hope of extra visibility.
Google's structured-data introduction explains its use in search, while Schema.org documents the broader vocabulary. A type existing in Schema.org does not mean Google provides a rich result for it. Review the feature-specific documentation before deciding what the markup should claim.
2. Keep data consistent with visible content
Article headline, author, publication date, modification date and image should match the displayed page. The image URL must be accessible and relevant; a generic image for every article is less appropriate when each has its own cover. Update modification dates when meaningful content or information changes, not merely whenever the server renders.
Do not add review, aggregateRating or customer counts without valid evidence and applicable feature conditions. A self-written testimonial does not become evidence because it is encoded in JSON-LD. Read Google's structured-data quality policies before implementation. Accuracy matters more than the number of properties added.
3. Keep URLs, language and identity coherent
Canonical, mainEntityOfPage, breadcrumb destinations and article URL should identify the correct content version. If Vietnamese and English have distinct addresses, set inLanguage for the displayed version and maintain accurate alternates. Do not place Vietnamese-only article information on an English page.
Stable @id values can connect entities in a graph, but a small website does not need unnecessary data complexity. Author and publisher identities should represent the actual person or organisation. Link an appropriate introduction page instead of a social profile that does not belong to the entity. Coherence across metadata and visible content helps avoid contradictory signals.
4. Check syntax and feature requirements separately
Valid JSON is only the first step. Next check required properties, image access, value types and feature conditions. The Rich Results Test tests supported search features; a type absent from that tool is not automatically invalid JSON. Use a suitable vocabulary validator for broader schema checks.
Inspect server HTML and the loaded DOM when JavaScript generates data. A screenshot does not reveal JSON-LD, and correct local JSON does not prove it was published to the intended domain. Record URL, time, result and remaining issues so someone else can repeat the validation. Distinguish syntax success from eligibility and actual search appearance.
5. Avoid contradictory markup from multiple sources
The theme, SEO plugin, commerce plugin and custom code may all emit markup. Inspect the actual page for multiple Article or Product entities giving different information. Do not blindly delete blocks merely because they look similar; establish the owner and purpose of each source.
When covers or metadata change, update the shared source so social images and schema remain consistent. Recheck a sample of every template and language variant after modifications. The technical SEO checklist connects markup review with canonical URLs, sitemap entries and accessibility to crawlers. Maintenance should target contradictory data rather than pursue a larger schema graph for its own sake.
6. Monitor after release with appropriate limits
Verify the public page and relevant Search Console reports where access is available. If a tool reports valid, state validity within that tool's scope. Do not turn it into a promise that Google will display stars or that rankings improved. Search appearance depends on the system and feature-specific conditions.
Maintain an update checklist covering title, excerpt, image, dates, URL, language and creator. If a source fact changes, update the visible text and markup together. Structured data is useful when it clarifies trustworthy content, not when it decorates unsupported claims. A maintenance owner is therefore as important as the initial implementation.
Frequently asked questions
Should every article have FAQ markup?
Use it only when the content and current feature conditions fit. A useful question section does not automatically make the site eligible for a FAQ rich result. Check feature documentation rather than adding markup to increase the type count.
References and further reading
To apply this to your current website, explore the SEO optimisation service or contact Dean Vu to define a scope around your existing site and actual evidence.