iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Structured data helps search engines interpret what a page is about by labeling its content in a standardized, machine-readable format. For Google Search, it can make a page eligible for a supported rich result, but it does not guarantee a special display or a ranking boost. The right approach is to mark up accurate, visible page content, follow the documentation for a feature the page genuinely qualifies for, and verify the deployed implementation.
What structured data does for SEO
Structured data provides explicit clues about the meaning of page content. For example, Recipe markup can identify details such as ingredients and cooking time. Search engines may use those clues to understand a page; Google may also use eligible markup to display supported enhanced search features.
Schema.org is the vocabulary commonly used to describe that information. A vocabulary term being available at Schema.org does not mean Google uses it for a particular search feature. For Google Search, its Search Central documentation is the authority on supported features, required properties, and eligibility rules.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteMarkup is not a direct promise of better rankings, increased traffic, or inclusion in AI-generated answers. Google explains: “Using structured data enables a feature to be present, it does not guarantee that it will be present.” A technically correct page may still not be selected for an enhanced appearance.
#1 Best Overall
Choose markup that fits the page
Start with the content visitors can see and the Google Search feature that best describes it. Google’s structured data feature gallery covers documented types including Article, Breadcrumb, Product, Recipe, Software app, Video, and Organization. Availability and requirements vary by type, and the gallery is not a guarantee that a page will receive a special display.
Read the current type-specific documentation before implementation. Check its required properties, content policies, and page-level rules; do not add a type solely because it appears in the gallery.
Rank #2
Two examples with specific placement rules
- WebSite site name: Google says this markup belongs on the domain or subdomain home page. Site names are not supported at a subdirectory level. The required properties are
nameandurl;alternateNameis optional. See Google’s site name documentation. - Organization: Organization markup on an organization’s home page can help Google understand administrative details and distinguish the organization from others. Google lists no required properties for this type and recommends using applicable properties. See Google’s Organization markup documentation.
Pick a markup format
Google supports JSON-LD, Microdata, and RDFa. The best fit depends on how your CMS or codebase manages page content; Google recommends JSON-LD when the site’s setup permits it because it is generally easier to implement and maintain at scale.
Free tools Windows power users keep installed
One-click scans. No signup required.
| Format | How it fits implementation | Google Search support |
|---|---|---|
| JSON-LD | Usually the simplest format to maintain when the site’s system supports it; can be added in page markup or generated dynamically. | Supported for rich-result eligibility. |
| Microdata | An alternative to consider when it better fits the site’s existing markup and maintenance process. | Supported for rich-result eligibility. |
| RDFa | An alternative to consider when it better fits the site’s existing markup and maintenance process. | Supported for rich-result eligibility. |
Google can process JSON-LD added with JavaScript when it is present in the rendered page DOM. That makes it important to verify what the deployed page renders, rather than assuming code in a template or script is available to Google. See Google’s guidance on generating structured data with JavaScript.
Keep markup accurate and eligible
Structured data should describe relevant content that is visible on the page it describes, unless that feature’s documentation specifies otherwise. Keep the values current and specific. Do not mark up hidden material, fabricate reviews, attach unrelated details, or make claims that misrepresent a person or organization.
Google must be able to access the page. If you are seeking rich-result eligibility, avoid blocking it with robots.txt, a noindex directive, or access controls. Follow the applicable feature policies as well as the technical property requirements.
Rank #4
An automated test can identify many technical problems, but it cannot establish that the content is truthful, useful, and policy-compliant. Google says, “Google does not guarantee that your structured data will show up in search results, even if your page is marked up correctly according to the Rich Results Test.” A passing test therefore confirms neither display nor all aspects of eligibility. A structured-data manual action removes rich-result eligibility; Google’s guidelines say it does not affect ordinary web-search ranking. See Google’s General Structured Data Guidelines, last updated July 10, 2026.
How to add and validate structured data
- Identify the page’s visible content. Select the feature that accurately describes it, rather than choosing markup first.
- Check the feature documentation. Record its required properties, content policies, and any restrictions on placement.
- Implement the markup. Use JSON-LD if it fits your CMS or codebase; Microdata and RDFa are also supported. Ensure each value reflects the page’s visible content.
- Check crawl access. Confirm the page is not inadvertently blocked by robots.txt,
noindex, or access controls when rich-result eligibility is the goal. - Test the deployed URL. Use Google’s Rich Results Test for supported features. Google recommends testing a URL because JavaScript limitations may affect code-input testing.
- Inspect unsupported features differently. If the feature is not covered by the Rich Results Test, inspect the rendered HTML to confirm the markup is present.
- Monitor after release. Use relevant Search Console rich-result reports, when available, and URL Inspection. Recheck after CMS, plugin, or template changes that could alter generated markup.
Google’s overview of formats, implementation routes, and testing is available in Intro to How Structured Data Markup Works.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.CMS settings, plugins, or custom code?
A CMS integration or SEO plugin can be a practical way to generate markup, but the choice should depend on the accuracy and maintainability of its output—not its marketing claims. Check whether it supports the relevant page type, emits page-specific values, gives editors appropriate control, avoids duplicate or conflicting markup, and fits a test-and-monitor workflow. Custom code can offer control but still needs validation and maintenance when templates or content models change.
Whichever route you choose, inspect the markup on the deployed page. A setting that appears correct in an editor does not prove that the rendered page contains accurate, crawlable structured data.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
