Businesswoman reviewing graphs and charts with colleagues, analyzing financial data in a modern office setting.

Google’s Structured Data Gallery Changed: Audit Obsolete Schema

BySplinternet Marketing

Google’s structured-data gallery was updated on June 15, 2026. For WordPress and WooCommerce site owners, the practical takeaway is not to add more schema. It is to inventory what the site already emits and decide what still has a defensible purpose.

The Google Search structured-data gallery is narrower than the full Schema.org vocabulary. Schema.org can support broader semantic, internal, or third-party data uses, but not every type creates a Google rich-result opportunity. Structured data also makes a page eligible for supported search features; it does not guarantee that Google will display the feature or improve rankings.

Need help checking this on your WordPress, Google Ads, Analytics, local SEO, or website setup? Splinternet Marketing can review the issue and help you prioritize the next fix.

Why a schema audit matters now

Structured data is often assembled by several systems: an SEO plugin, theme, WooCommerce, a review plugin, a local-business tool, a Google integration, and custom code. That can produce duplicate Organization or Product graphs, conflicting business identities, stale prices, invalid availability, or review markup that does not match visible page content.

Those problems create maintenance work even when there is no corresponding Search benefit. A plugin setting can remain enabled long after a feature changes, a template can emit markup for content visitors cannot see, or two systems can publish different versions of the same offer.

Google also announced that support for certain structured-data types in Search Console and its API would begin being removed in January 2026. A missing older enhancement report is therefore not proof that all related markup is invalid. The Search Console rich result report overview says these reports cover supported rich-result types and show samples of detected items rather than a complete inventory of every structured-data item on a site.

Start with an inventory, not another plugin setting

Crawl representative URLs and inspect the rendered source for JSON-LD. Review the homepage, organization or contact page, local landing page, service page, category archive, product page, variable product template, review page, and checkout-adjacent templates where applicable.

Record each item in a worksheet with:

  • URL pattern and template
  • Schema type and important properties
  • Emitting source: plugin, theme, WooCommerce, custom code, or integration
  • Whether the data matches visible page content
  • Related Google feature or Search Console report, if any
  • Validation status, owner, and next action

For local businesses, compare the emitted LocalBusiness and Organization data with the business name, address, telephone number, hours, logo, and identity links shown on the site. For ecommerce, compare product identity, offers, price, availability, reviews, variants, shipping, and return-policy information with the storefront and any product feed. The page, feed, and JSON-LD should not describe different versions of the same offer.

What to do next

  1. Classify the markup. Put each item into one of four groups: Google-supported, beta or availability-limited, semantic-only, or cleanup candidate.
  2. Consolidate ownership. Remove duplicate Organization, LocalBusiness, Product, Offer, and review graphs where possible. Choose one authoritative source for each identity.
  3. Validate supported features. Use Google’s Rich Results Test for feature eligibility, then use URL Inspection to review the live page and indexed version.
  4. Check Search Console carefully. Product snippets and Merchant listings reports appear under Shopping when Google finds valid supported markup. Treat report data as monitoring evidence, not a complete site inventory.
  5. Document semantic-only markup. If a Schema.org type supports an internal workflow or another documented consumer but not a current Google rich result, record that purpose and owner.
  6. Recheck after deployment. Search Console validation can take two weeks or more depending on crawl frequency. Do not close a cleanup task solely because the live source changed; confirm that Google has processed the affected URLs.

The maintenance decision is straightforward: keep markup that supports a current Google feature or a documented semantic purpose, and simplify everything else. A smaller set of accurate, owned graphs is usually easier to test and maintain than a plugin-generated schema pile that no one understands.

Sources

Need help checking this on your WordPress, Google Ads, Analytics, local SEO, or website setup? Splinternet Marketing can review the issue and help you prioritize the next fix.

This article is for informational purposes only and reflects general marketing, technology, website, and small-business guidance. Platform features, policies, search behavior, pricing, and security conditions can change. Verify current requirements with the relevant platform, provider, or professional advisor before acting. Nothing in this article should be treated as legal, tax, financial, cybersecurity, or other professional advice.

Editorial note: Splinternet Marketing articles are researched from cited platform, documentation, regulatory, and industry sources. AI may assist with drafting and review; final content is checked for source support, practical usefulness, and platform/date accuracy before publication.

Related Posts

Splinternet Marketing