Schema Markup Explained: What Still Helps Your Website

Schema Markup Explained: Uses, Limits and Testing

What is schema markup

Schema.org provides a shared vocabulary for describing things on the web. A type identifies the thing being described, such as a Product. Properties describe its details, such as its name or price.

Structured data is the organised information added to a page. Schema markup is the common name for structured data using the Schema.org vocabulary.

Schema.org’s introductory guide

Think of a fictional shop selling a desk lamp. Its page explains the lamp’s features, price and availability to customers. Structured data can label the same information so a search engine does not have to infer every detail from the page’s wording.

The page still needs to do its job for a person deciding whether to buy. Accurate labels cannot compensate for an unclear description or a confusing checkout.

Schema.org and Google features are different things

Schema.org describes a broad vocabulary. Google’s documentation specifies the types and properties it supports for particular Search features. A type existing in Schema.org does not mean Google provides a dedicated rich result for it.

A rich result is a search appearance with additional information, such as product details or recipe information. Google’s supported-feature gallery is the starting point for choosing a feature, rather than a list of everything available in Schema.org.

Google’s supported structured data features

What changed for FAQ markup

Google’s documentation changelog states that FAQ rich results stopped appearing in Google Search from 7 May 2026. The FAQ feature documentation was subsequently removed in June.

An FAQ section on your website therefore should not be sold or implemented as a way to obtain expandable FAQ results in Google Search. The Schema.org vocabulary and Google’s support for a Search feature are separate matters.

Google’s documentation changelog

Keep questions and answers that help customers. For example, a furniture shop might explain delivery areas, assembly options and how to report a damaged item. Those answers remain useful even when they do not receive a special search appearance.

Our recommendation is to review the content and the markup separately. Improve useful answers and remove redundant ones. If your website generates FAQ markup, decide whether there is another supported use for it before spending time maintaining it. Its former Google display benefit is no longer a reason to add it.

The same distinction applies to step-by-step content: Google’s HowTo rich result has also been retired. Clear instructions can still help readers without that feature.

Which types are worth considering

Choose according to the page’s purpose. These are practical starting points, with eligibility and appearance determined by the relevant Google documentation.

For a typical service business, we would begin by checking business identity information and the markup already generated for its pages. An online shop has a stronger reason to prioritise accurate product data. Neither needs to invent an event, recipe or product simply to use another schema type.

Be careful with review stars

Google’s review rules exclude self-serving reviews for LocalBusiness and Organization, including reviews displayed through an embedded third-party widget on the business’s own site. Adding customer testimonials does not make your business eligible for organic review stars under those types.

Keep genuine testimonials for readers. Product review eligibility is a separate matter with its own requirements. Never invent ratings or convert general business feedback into reviews of a specific product.

Google’s review snippet guidelines

Eligibility does not guarantee display

For a supported feature, a page must satisfy its technical requirements and content policies. Required properties must be present; recommended properties can add useful detail. The information must accurately represent the page and be available to readers.

A technically valid result does not prove that the content complies with every policy, nor does it guarantee that Google will show a rich result. Google makes the final display decision.

Google’s structured data guidelines

For our fictional lamp shop, adding a price to the markup is only part of the task. The team must also check that customers see the same current price and that updates to stock or product options do not leave conflicting information behind.

This is why we recommend making maintenance part of the implementation. Decide which system supplies the data and who checks it after changes. An inaccurate automated output is still inaccurate.

Does schema guarantee better rankings or AI citations

Treat schema as descriptive information and a route to eligibility for appropriate features, rather than a ranking promise. A more informative result might help a person judge its relevance, but you should measure your own results instead of assuming a higher click-through rate.

Google states that structured data is not required for generative AI search and there is no special Schema.org markup you need to add for it. Existing supported markup can still be useful for Google’s rich results.

Google’s guidance on generative AI features

Do not promise that FAQ, Article or business markup will make an AI service cite you. That outcome cannot be established simply by passing a schema test. Continue improving the evidence, clarity and usefulness of the page itself.

Adding schema to a WordPress website

Google supports several formats and generally recommends JSON-LD when the website setup permits it. JSON-LD places the structured information in a script block; it can be included in the page’s head or body.

WordPress tools can generate this information from settings and content. Before adding another plugin or code snippet, inspect what your SEO plugin, theme and ecommerce tools already produce.

Google’s introduction to structured data

Our suggested workflow is:

1. Choose one page type to work on first, such as product pages or articles. Make a note of the business or reader need you are addressing.
2. Check the existing output. Identify which plugin or template owns it and whether another tool produces conflicting descriptions of the same item. Multiple related items on a page can be legitimate; conflicting facts need investigation.
3. Configure the relevant settings and supply real information. Avoid filling fields with invented values just to make a test look complete.
4. Test a representative page before rolling out a template change. Include an example with unusual details, such as a sale price or an article without a featured image.
5. Check the live output after publishing and clearing any relevant cache. Confirm that the visible page and the structured information agree.
6. Retest after changes to templates, plugins or business information. For a larger shop or complex implementation, involve a developer who can manage the data consistently.

Start with your existing tools where they meet the need. More schema plugins do not automatically create better structured data, and a custom snippet is only useful if someone can keep it accurate.

Testing schema with the right tools

Google Rich Results Test

Use Google’s Rich Results Test to check structured data for supported Google rich results. It can identify eligible items, report problems and provide previews for supported features. It is not a general test of every Schema.org type.

Open Google’s Rich Results Test

Schema Markup Validator

Use the Schema Markup Validator for general Schema.org validation. It checks the markup without applying Google’s feature-specific requirements. Passing this test does not establish Google rich-result eligibility.

Open the Schema Markup Validator

Google’s explanation of the two testing tools

Checking the published page

Test the live URL as well as any draft code. A valid snippet does not show whether the website actually publishes that snippet correctly. Google’s URL Inspection and applicable rich-result reports in Search Console can help you check the deployed page.

Read the issue description before making a change. Missing required information can prevent eligibility. A recommendation or non-critical warning is not automatically the same as a blocking error. Add accurate information where available; do not fabricate it to remove a warning.

A short checklist for business owners

• Does the markup describe what is really on this page?
• Is the selected Google feature still supported?
• Have the relevant requirements and content policies been checked?
• Do prices, dates, business details and other facts match the visible content?
• Does the published page pass the appropriate test?
• Is someone responsible for keeping the data current?

Questions business owners often ask

Should I delete my FAQ section

Keep it if it answers useful questions. For example, a customer deciding whether to book may need information about cancellation or preparation. Remove repetitive answers that add little, rather than removing the whole section solely because a search feature ended.

Do I need to add custom code

First check what your existing WordPress tools publish. If the required information can be configured there, that may be easier to maintain. Use custom code when there is a clear need and someone can take responsibility for it.

How should I decide what to fix first

Prioritise misleading information and problems affecting important page types. For a shop, an incorrect price deserves attention ahead of an optional detail on an old article. Record the correction and test a live example before applying it more widely.

Our recommendation

Use schema where it accurately describes your content and supports a relevant, current use case. Keep helpful FAQs, choose the correct testing tool and plan for maintenance.

For a small business, a modest implementation with dependable information is more useful than a large collection of markup added without a clear purpose.

Sources and further reading

Schema.org — Getting started

Google — Supported structured data features

Google — Structured data guidelines

Google — Review snippet guidelines

Google — Structured data testing tools

Google — Introduction to structured data

Google — Search documentation changelog

Google — Generative AI search guidance

Guidance and feature availability reviewed on 11 October 2026.