In short: Structured data can help Google understand a page and make it eligible for a supported search feature. Choose a feature that matches the page, describe information readers can see, and validate the markup before release. A passing test confirms technical checks; Google still decides how a result appears.
Adding markup because a competitor has a search enhancement can create work without a clear reader benefit. Start with the page’s job and the search features Google currently supports. Then decide whether structured data can describe that page accurately and whether the team can keep the information current.
1. Start with a supported feature and a clear page type
Review Google’s structured-data gallery before choosing a type. The gallery describes the features Google supports and the content each one is designed for. For example, editorial articles and breadcrumb navigation have separate guidance. A schema type that exists elsewhere may not qualify for a Google Search feature.
Write down what the page is and what information the markup should clarify. An article should describe the article readers see; breadcrumbs should reflect the site’s actual navigation hierarchy. If a page does not fit a supported feature, keep the page useful and focus on accurate titles, headings, links, and visible content.
2. Match every field to visible, current information
Structured data should be a faithful description of the page. Use details that a visitor can verify in the content, such as the article headline, author, date, or the page’s place in a breadcrumb trail. Keep values consistent with the visible page and update them when the page changes.
Avoid marking up hidden claims, invented reviews, or attributes that do not describe the page. Google’s general guidelines require relevant markup and explain that misleading or invisible content can prevent rich-result eligibility or lead to a manual action. The same check applies to comparisons: the comparison-page guide covers how to keep public claims tied to verifiable evidence.
3. Check what the site already outputs
Before adding a plugin setting or code snippet, inspect the page for existing markup. A theme, SEO plugin, or page builder may already provide it. Keep one clear source of truth for each page field so a later title or date change does not leave contradictory values in the markup.
Google supports JSON-LD, Microdata, and RDFa for structured data and recommends JSON-LD for most implementations. Choose a format the site team can maintain, then use the required properties in the documentation for the feature you selected. Required fields determine eligibility; optional fields should be included only when they add accurate context.
4. Validate the page before expanding the rollout
Test a representative page with Google’s Rich Results Test. Resolve critical errors and review warnings against the feature documentation. Automated tests catch many technical issues, but they cannot decide whether a claim is accurate, visible, or appropriate for the page.
After deployment, use URL Inspection to see how Google fetched the page and whether it can access the markup. Confirm the URL is crawlable and indexable; the indexing diagnosis guide covers those checks. Roll out across similar pages only after the representative page’s markup matches its visible content and the team has a way to maintain it.
5. Set a realistic success measure
Track whether the markup remains valid and whether Search Console reports eligibility for the relevant feature. Compare search appearance and traffic over a suitable period, while keeping page edits and other changes in view. Search features can vary, and Google may show a standard result even when markup passes its test. Plan for accurate implementation and maintenance; treat any enhanced appearance as a possible outcome rather than a deliverable.
Structured-data release worksheet
- Page type and intended reader task: ______
- Google-supported feature that fits the page: ______
- Visible facts represented by the markup: ______
- Current theme, plugin, or builder output checked: ______
- Required properties and documentation reviewed: ______
- Rich Results Test errors and warnings reviewed: ______
- URL Inspection and page accessibility checked: ______
- Markup owner and content-update process: ______
- Success measure and review date: ______
Use structured data to describe a real page clearly. Keep the visible content, markup, and maintenance process aligned.
If search visibility depends on several technical and editorial signals, request a marketing diagnostic to review page quality, markup, and qualified outcomes together.
Request a marketing diagnostic
Sources and scope
- Google Search Central: Structured data markup that Google Search supports — lists supported search features and their content types.
- Google Search Central: General structured data guidelines — covers format, relevance, visible content, validation, eligibility, and the limits of rich-result display.
- Google Search Central: Article structured data — explains markup guidance for news, blog, and sports articles.
- Google Search Central: Breadcrumb structured data — covers markup for a page’s place in a site hierarchy.
This is an implementation review guide, not a promise of enhanced search appearance or additional traffic. Google may change supported features and their requirements. Verify the current feature documentation before deployment. Accessed October 9, 2026.
How did this article land?
Choose one reaction. You can change it anytime.