Schema markup

Schema markup describes information in a structured form using a shared vocabulary, commonly Schema.org. It can identify what a page represents and explain relationships between things such as an organisation, an article or a product.

It complements the visible content. A clear description for machines is useful when it accurately represents an equally clear page for people.

Structured data versus schema markup

Structured data is the broader idea of organising information in a defined format. Schema.org supplies a vocabulary of types and properties that can be used to describe many kinds of content.

Schema markup is the application of that vocabulary to a page or resource. The terms are often used together in website projects, but they describe slightly different parts of the implementation.

A practical brief should identify what the page represents, which vocabulary is appropriate and how the information will remain accurate as content changes.

What is JSON-LD?

JSON-LD is one format used to express linked structured information. On websites it is often included in a script element containing structured data rather than executable page behaviour.

Google supports several structured data formats and recommends JSON-LD for its supported uses. The format does not remove the need to choose accurate types and supply appropriate information.

For a business owner, the main question is whether the implementation reflects the actual content and can be maintained reliably. The choice should be explained in the context of the website.

What can schema markup describe?

Schema.org includes many types, including organisations, people, articles and defined terms. Each type has properties that express relevant information.

A glossary term can use the DefinedTerm type to describe its name, definition and relationship with a term set. That is a semantic description of the content, rather than a promise that a special search feature will appear.

Choose types that fit the page. Adding every available type does not make the information more accurate and can introduce contradictions.

Does schema markup improve rankings?

Correct markup does not guarantee higher rankings or a rich result. Google's search features have their own supported types, requirements and eligibility rules.

It is useful to distinguish three questions: whether the structured data is syntactically valid, whether it accurately describes the content, and whether it meets the requirements of a particular search feature.

A tool can confirm part of the first question without resolving the others. A valid description can still be irrelevant, incomplete or unsupported for the intended feature.

What are rich results?

Rich results are enhanced search presentations supported by a search engine. The available features and their requirements can change.

Not every Schema.org type corresponds to a Google rich result. A business should therefore ask which feature, if any, the implementation is intended to support.

Avoid treating markup as a guaranteed visual upgrade to the listing. It provides information that may support eligibility where the search engine's requirements are met.

How should markup connect with the CMS?

Structured data should use the correct values for each page. A shared template can draw on fields such as the article name, description and page address.

This is where a content management system can help. Maintaining the information once reduces the risk of the visible page and its structured description drifting apart.

The binding still needs testing. A copied template that repeats the same name or URL across every article creates a misleading result, even if the code format is valid.

Accuracy and visible content

Describe what the page actually contains. Do not invent reviews, credentials, authors or other details to make the markup appear more impressive.

The same principle applies to content that changes frequently. A product's displayed information and its structured description should be kept aligned.

Establish who owns those values and how updates reach the published page. Accurate maintenance matters more than a large block of code added once and forgotten.

How do you test schema markup?

Use an appropriate validator to check structure and vocabulary. For a supported Google search feature, use its Rich Results Test and review the current feature documentation.

Then inspect the actual published page. Confirm that values are unique where they should be and that the markup matches the visible content.

Test several representative CMS entries, including unusual names or punctuation. Content can expose escaping and formatting problems that a short demonstration record does not reveal.

Common implementation mistakes

One mistake is duplicating several conflicting blocks from different plugins or templates. Another is describing the website as a type that does not fit the page.

Hard-coded URLs and copied descriptions can also spread through a collection. These are maintenance problems as much as coding problems.

Finally, avoid promising a search outcome based solely on a clean validation result. Validation is a check on the implementation, not an agreement from a search engine to display a feature.

Where should a business begin?

Start with the content types that actually exist on the website. Identify a small number of accurate descriptions and how their information will be supplied.

Review the implementation alongside technical SEO, page content and template testing. A coherent page is a stronger foundation than adding markup to an unclear offer.

For primary guidance, see Google's structured data introduction and general policies. For a glossary example, see Schema.org's DefinedTerm documentation.