Schema Markup: Which Structured Data Types Are Actually Worth Adding
Structured data does not make you rank higher. It changes how your result looks when you do rank, which affects how many people click, which is often worth more than a position. A handful of types deliver almost all of that value.
What it does and does not do
Structured data is machine-readable information about a page: that this is a product with this price, that this is an article by this author, that this business is at this address. Search engines use it to understand the page and to build enhanced results.
It is not a ranking signal in itself. Adding markup will not lift a page up the results. What it can do is make your listing larger and more informative, with a price, a rating, an image, breadcrumbs or an event date, and that reliably improves click-through from the same position.
Eligibility is not entitlement. Valid markup makes you eligible for an enhanced result; search engines decide whether to show one, and what they show changes over time. Several types that once produced prominent results now rarely do, which is why chasing every available type is wasted effort.
The types worth the effort
Organisation or LocalBusiness markup, once, describing who you are, where you are and how to contact you. For a business with premises this is the foundation for local results and should match your other listings exactly.
Breadcrumbs on every page, because they change the ugly URL line in search results into a readable path. This is the cheapest improvement on the list and applies site-wide.
Product markup on ecommerce pages, which drives price, availability and rating detail in results and has a direct commercial effect. Article markup on editorial content. FAQ markup where you genuinely have questions and answers on the page. And for a business with premises, accurate opening hours and location.
Beyond those, add types only when they describe something real about the page. Recipe, Event, Course, Job Posting and Video markup are valuable for the sites they apply to and pointless everywhere else.
Implementation details that matter
Use JSON-LD in a script tag rather than markup woven into the HTML. It is what search engines recommend, it survives template changes without breaking, and it can be updated without touching the visible page.
The rule that catches people out: the markup must describe what is actually on the page. FAQ markup for questions that do not appear visibly, ratings that exist nowhere on the site, or a price that differs from the displayed price are all violations, and the penalty is usually quiet, with enhanced results simply disappearing.
Keep the visible text and the markup identical rather than paraphrased, since a mismatch between the two is the most common cause of markup being ignored. Generate it consistently with our schema markup generator rather than editing by hand, where a missing brace silently invalidates the whole block.
Test it, then watch it
Two checks are worth running. A validator tells you whether the syntax and required properties are correct, and a rich results test tells you whether the page is actually eligible for an enhanced result, which is the question you care about.
After deployment, watch the enhancement reports in Search Console. They show what search engines found across the whole site rather than on one page, which is how you catch a template change that broke markup on four hundred pages at once.
Then leave it alone. Structured data is set-up work, not ongoing work, apart from keeping prices and availability accurate on commercial pages. Time is better spent on the content that has to rank before any of this matters. Our technical SEO service covers implementation and monitoring together.
Key takeaways
- Structured data is not a ranking factor. It changes how your result looks, which changes click-through.
- Valid markup makes you eligible for an enhanced result; search engines still decide whether to show one.
- Organisation, breadcrumbs, product and article markup deliver most of the value. Add other types only where they describe something real.
- Markup must match the visible page exactly. Invisible FAQs, invented ratings and mismatched prices get enhancements removed.
- Use JSON-LD, validate with a rich results test, then monitor the enhancement reports for template breakages.
Frequently asked questions
Does schema markup improve rankings?
Not directly. Search engines have said repeatedly that structured data is not a ranking factor, and adding it to a page will not move that page up the results. What it does is make your listing eligible for enhanced presentation such as review stars, prices, breadcrumb paths or event dates, which typically increases how many people click your result from the same position. That extra traffic can indirectly help over time, but the mechanism is click-through and not a ranking boost.
Which schema types should I add first?
Start with Organisation or LocalBusiness markup describing who and where you are, and BreadcrumbList across the site because it improves the URL line in every result at almost no cost. If you sell products, Product markup next, since price and availability in the result have a direct commercial effect. Article markup on editorial content and FAQ markup where genuine questions and answers appear on the page. Ignore types that do not describe something actually present.
Should I use JSON-LD or microdata?
JSON-LD, in almost every case. It is the format search engines recommend, it sits in a single script block separate from your visible HTML, and it can be changed without touching the page layout. Microdata requires attributes scattered through the markup, which breaks easily when a template changes and is far harder to audit. The only reason to keep microdata is that it already exists and works, and even then migrating is usually worthwhile.
Can I add FAQ schema to any page?
Only where the questions and answers genuinely appear on the visible page, in the same wording. Adding FAQ markup for content that is not shown to users is a guidelines violation, and the usual consequence is that enhanced results stop appearing rather than any dramatic penalty. It is also worth knowing that search engines have substantially reduced how often FAQ enhancements are displayed, so the type is now more useful for helping machines understand the page than for winning extra space.
How do I test my structured data?
Use two checks. A schema validator confirms the syntax is correct and that required properties are present. A rich results test confirms whether the page is actually eligible for an enhanced result, which is the question that matters commercially, since valid markup can still be ineligible. After deploying, watch the enhancement reports in Search Console, because those show problems across the whole site and will catch a template change that silently broke the markup on hundreds of pages.
Why is my rich result not showing even though the markup is valid?
Valid markup makes you eligible, not guaranteed. Search engines decide independently whether to show an enhancement based on the query, the device, competing results and their own assessment of the site. Enhancements also appear less often for lower-ranking pages and for some types that have been scaled back over time. Give it a few weeks after deployment, confirm the page is being crawled, and check the enhancement report for warnings, but accept that some pages will never show one.