Skip to main content

SEO guide

Add structured data that matches the facts on the page

By MultiZest · · 4 min read

Structured data gives a machine-readable description of a page’s subject. It is most useful when it agrees with the information a visitor can see. Filling every field, inventing a rating or copying another site’s business details does not make the page more trustworthy; it creates a different story from the actual content.

The practical takeawayChoose a type that fits the page, include accurate visible facts and verify the deployed output. Syntax validation, feature eligibility and the decision to show a search appearance are separate questions.

Choose the type before filling in the fields

Read the page as a visitor. Is it an article, an organization profile, a product description or another supported subject? Choose the generator’s type that represents that actual content. A utility page should not be forced into a product review because an unrelated competitor received a richer search appearance.

A type provides a vocabulary for particular facts; it does not create the underlying subject. If the website has no physical business location, do not invent one to complete an address field. If it contains no customer reviews, do not add an aggregate rating from an imaginary sample.

Collect facts from the page and publisher

Use the actual title, public URL, publisher name and relevant images. For commercial information, confirm that values such as price and availability match the visible offering. For an article, preserve its real publication date and update the modification date only when a substantive edit occurs.

Write down where each fact comes from. That small record is useful when content changes or someone asks why a value appears in the markup. A copied JSON-LD example may contain demonstration domains and dates that are easy to overlook if you replace only the headline.

Generate a clean JSON-LD block

Use the supported fields and inspect the output before copying. Quoted strings, arrays and nested objects must remain valid JSON. The generator handles structure, but you still need to check that each value belongs to the page where the script will be installed.

Keep a stable URL or identifier for the subject when connecting related entities. Do not point the article to one canonical page and describe a different URL in its structured data. Consistent identities help systems understand how the website, publisher and page relate to one another.

Test the feature rather than only the syntax

A JSON parser can establish that the block is syntactically readable. The test relevant to a Google search feature can additionally report supported properties and eligibility issues. Use the relevant official documentation because requirements differ across feature types and can change.

A valid block does not guarantee a displayed rich result or better ranking. Search systems also assess the page, policy requirements and the context in which an appearance is useful. Treat test warnings as questions to investigate rather than an invitation to invent extra fields.

Check the actual deployed page

Install the block in the page’s document and inspect the rendered output or source used by the site. Check for duplicate conflicting entities added by another plugin or layout. A local generator result and a deployed page can differ if the publishing system modifies or replaces the script.

Compare every important structured value against the visible page. Hidden prices, outdated availability and answers removed from the article can create discrepancies even while the JSON remains valid. Test a direct URL load and the deployment environment that visitors will reach.

Keep the markup in the content maintenance workflow

When an article is rewritten, an offering changes or contact details move, review the structured data as part of the same edit. Prefer a shared source for visible content and machine-readable fields where the website architecture permits it. That reduces the chance of one copy changing while another stays stale.

Keep the goal practical: describe the page accurately. Structured data supplements a useful accessible page; it does not replace clear headings, good instructions or trustworthy facts. A modest block that matches the content is easier to maintain than a large collection of speculative claims.

  • Use real facts and relevant types.
  • Preserve truthful publication and modification dates.
  • Test syntax and the intended feature separately.
  • Inspect the deployed page and keep it consistent with future edits.

Try the tools used in this guide

Sources and further reading

Continue reading