Skip to main content Scroll Top

How to Add and Check Structured Data in WordPress

Structured Data in WordPress: Add and Test Schema

By David Roche | Reviewed 18 October 2026

Structured data describes information on your pages in a format machines can interpret. In WordPress, some of it may already come from your SEO plugin, theme or shop software. The first job is to find out what is present, then check that it is relevant and accurate.

You do not need a separate schema plugin simply because a page has no stars or other enhanced search display. This guide shows how to inspect existing markup, choose an appropriate implementation, test it and maintain it without adding conflicting information.

For the background explanation, read Schema Markup Explained

Schema and Structured Data

Separate vocabulary from Google features

Schema.org supplies a vocabulary for describing things such as articles, organisations, products and people. Google supports particular search features with their own requirements. A type existing in Schema.org does not establish that it triggers a Google rich result.

Structured data can help Google understand page content and make a page eligible for supported search presentations. Eligibility is not a guarantee of display, higher rankings, more clicks or AI citations. A test result also does not establish that your business claims are true.

Choose a feature from Google’s current documentation when Google rich-result eligibility is your goal. Do not rely only on a plugin’s list of available schema types.

Google’s structured data feature gallery

Keep useful FAQs without promising expandable results

Google retired the FAQ rich-result feature from 7 May 2026. FAQPage still exists in Schema.org, but a valid FAQPage item does not restore that Google feature. HowTo markup is also not a route to a current Google HowTo rich result.

Keep visible questions and answers when they help readers. Review any plugin block or old template promising FAQ expansion, rather than removing useful content simply because Google changed its display features.

Google’s documentation changelog

Start by inspecting a representative page

Choose an important public page that is already published. Use its exact URL rather than a preview link. Start with one article, service page or product page; the output may differ across templates.

  • Open Google’s Rich Results Test and test the URL. Note the supported items it detects and any errors or warnings.
  • Test the same URL with Schema.org’s Markup Validator to inspect broader Schema.org types and properties.
  • Compare detected facts with the visible page: name, author, dates, business details, images, price or availability where relevant.
  • Record the likely source of each item. Check the SEO plugin, theme, shop software, builder blocks and any custom snippets.
  • Repeat on another relevant page type before assuming the whole website uses the same configuration.

Google Rich Results Test

Schema.org Markup Validator

View Source can help you locate JSON-LD script blocks, often identified by application/ld+json. Markup can also appear as HTML attributes or be added by JavaScript. An initial source search alone is therefore not a complete inventory. If the source is unclear, ask your developer to trace it.

Record what supplies the markup

Page or item Possible source Check before changing
Article and author SEO plugin or template Real author, relevant headline, images and genuine dates.
Business identity SEO plugin, theme or custom code Consistent name, URL and the appropriate organisation or business type.
Product and offer Shop software or an extension The actual product, currency, price and availability.
Breadcrumbs Theme or SEO plugin A sensible route through the website with working destinations.
FAQ block or custom item Editor block or snippet Relevant visible content and a clear reason to maintain the markup.

 

These are possible sources, not instructions to install another tool. A WordPress plugin can generate several related items, while a shop extension may add specialist data. Confirm the source on your setup before disabling anything.

Choose markup that matches the page

Articles and author details

For an editorial article, check relevant Article or BlogPosting information such as the headline, author, images and publication or modification dates. Use the real author and a useful author profile. Do not invent qualifications or change the publication date merely to make an old page look new.

Check the article template rather than adding identical manual code to every post. If the template supplies incorrect dates or an inappropriate author, correct the underlying mapping.

Google’s Article structured data guidance

Business identity and local details

Use business information that reflects the real organisation. LocalBusiness markup has requirements that depend on the intended feature and business details; adding it is not a substitute for maintaining a Google Business Profile.

Check names, hours, URLs, contact information and applicable locations against your pages. Do not invent a public address to satisfy a required field. If you operate as a service-area business without a public premises address, get advice on an appropriate implementation rather than publishing false or private information.

Google’s LocalBusiness guidance

Products and commercial information

For an actual product page, check the product and offer information supplied by your shop. Different Google product experiences have different requirements. A product identifier, price, stock status or variant must describe what the visitor can actually buy.

Use dynamic information from the maintained shop data where practical. A manually pasted price can become wrong as soon as the product changes. Check consistency across the visible page, generated markup and any product feed.

Google’s product structured data overview

Use the product-data checks in the Ecommerce SEO guide

Breadcrumbs and navigation

BreadcrumbList describes a route through the website. Check that its labels and URLs make sense alongside the site’s navigation. Google currently documents breadcrumb rich results as a desktop feature; useful on-page breadcrumbs can still help visitors on mobile.

An ordinary service page does not need to be labelled as a product, recipe or event to secure a more attractive display. Describe what the page contains and use supported features only where their requirements fit.

Google’s breadcrumb guidance

Reviews and ratings

Do not fabricate feedback or a rating, or attach a site-wide business rating to unrelated items. Google has specific rules about eligible review types and the relationship between the reviewed item and the reviewer.

Reviews about a LocalBusiness or Organization are ineligible for the star review feature when the reviewed business controls those reviews on its own site, including through an embedded third-party widget. Genuine testimonials can still help visitors, but do not promise Google stars from adding a ratings plugin.

Google’s review snippet policies

Configure WordPress before adding custom code

Open the documentation for the SEO or shop tool you already use. Find its site identity, content-type and structured data controls; names and locations vary by product and version. Check any existing setup before running a wizard again.

Confirm whether the site represents a person or an organisation. Enter accurate details, choose relevant defaults for actual content types and review page-level exceptions. If a post has been assigned the wrong type, correct that assignment rather than adding a second description over it.

Assign responsibility for each output. For example, your SEO plugin may describe articles and business identity while the shop supplies product offers. Test the combined result. Separate tools can coexist when their output is accurate and coordinated.

Choose and manage tools with the Best SEO Plugins guide

JSON LD is convenient but other formats are supported

Google supports JSON-LD, microdata and RDFa, subject to the relevant feature documentation. It generally recommends JSON-LD because it is easier to implement and maintain. JSON-LD can appear in the page’s head or body; it is not restricted to a manual header insertion.

The presence of both microdata and JSON-LD is not automatically an error. Investigate contradictory facts or duplicated descriptions of the same thing. Several different, relevant items on one page can also be legitimate.

Google’s introduction to structured data and supported formats

Use custom code only for a defined gap

If existing tools cannot describe a necessary item, ask a developer to implement and maintain it through an appropriate template or scoped plugin mechanism. Establish which pages receive it, where its values come from and who updates it.

AI and generators can help draft code, but do not publish the output without checking syntax, current feature requirements and every business fact. Replace example URLs and placeholders, avoid unsupported properties and confirm that the snippet is not being inserted across irrelevant pages.

Test syntax and eligibility separately

Tool What it helps check What it does not prove
Schema.org Markup Validator Schema.org types, properties and parsing across the detected markup. Google rich-result eligibility or the truth of the information.
Google Rich Results Test Detected items and requirements for supported Google rich-result features. That all Schema.org vocabulary is assessed or a result will display.
Search Console What Google reports about supported enhancements and inspected URLs. Every schema item on the website, an AI citation or a commercial result.

 

A “no items detected” result in the Rich Results Test does not necessarily mean there is no structured data. The page may contain vocabulary outside that tool’s supported feature set. Check the broader validator and the actual implementation.

For a detected feature, fix required-property errors before expecting eligibility. Review recommended-property warnings for useful information you can accurately provide; do not invent a value just to clear a warning. A syntactically valid item can still fail a policy requirement.

Recheck the published URL after the change. Testing code before publication is useful, but it cannot confirm what the final WordPress page outputs after templates, plugins and caches have acted on it.

Example of an article with conflicting author details

This is a fictional example. Willow Heating publishes an advice article. The SEO plugin supplies BlogPosting data with the real author, but an old custom snippet supplies another Article item naming a different author and an outdated business URL.

The owner records both items and asks the maintainer to identify their sources. They confirm that the old snippet is unnecessary, keep a backup of its configuration and remove it from the affected template. They do not disable every structured data feature on the website.

After clearing the relevant cache, they retest the article URL and a second article using the same template. They check the visible byline, dates, business information and remaining markup. The aim is a consistent description, not the largest possible count of detected items.

Publish in a controlled way and monitor

For a template or site-wide change, back up files and the database and keep a rollback route. Test a representative sample on a protected copy first. Record the affected pages, previous settings, changes and validation results.

After publication, ensure that intended public pages are accessible for crawling and indexing. Structured data does not override robots.txt, a noindex instruction or a login requirement. Use URL Inspection when access or indexing is unclear.

Investigate access with Indexing and Sitemaps

Where Search Console provides a relevant enhancement report, review its errors and examples. After correcting the affected instances, use the validation process offered by that report. Changes are not necessarily reflected immediately, and not every type has a dedicated report.

Google’s guidance on rich result status reports

Monitor relevant pages and available search-appearance reporting alongside completed enquiries or sales. Keep a record of content and template changes. A change in click-through rate after publication does not, by itself, prove that the markup caused it.

Connect checks to the SEO measurement guide

What structured data does not guarantee in AI search

Google says no special schema.org markup is needed for its generative AI Search features. Accurate existing markup can remain part of your overall SEO work, but adding FAQ, HowTo, Service or another type is not a guaranteed route to an AI citation.

Keep business facts clear in visible content and maintain the pages customers need. More markup cannot repair misleading advice or make a service available in a location you do not serve.

Google’s guidance for generative AI Search features

A short maintenance checklist

  • Inspect output after changing the theme, SEO plugin, shop extension or a shared template.
  • Update source information when authors, business details, products or availability change.
  • Retest representative public URLs and compare facts with visible content.
  • Record which system owns each item and preserve the setup for future maintainers.