Cheap Market Insight

How to Use Schema Markup to Win Rich Results

Schema markup remains one of the more misunderstood parts of technical SEO. Site owners often add it hoping for an automatic rankings boost, then feel misled when nothing visibly changes. Understanding what schema markup actually does — and which schema types still translate into visible search features in 2026 — makes it much easier to use well.

What Schema Markup Actually Does

Schema markup (structured data) is a standardized vocabulary, defined at schema.org, that labels the content on a page in a machine-readable way — identifying that a block of text is a recipe, a product with a price, a review with a star rating, or an event with a date and location. Google recommends implementing it using JSON-LD, a script format placed in the page’s head or body that doesn’t alter the visible page content.

Crucially, schema markup is not a direct ranking factor. Google has repeatedly clarified that adding structured data doesn’t improve your position for a given query on its own. What it can do is make you eligible for certain visual search features — rich results — that can improve click-through rate for pages that already rank.

Which Schema Types Still Generate Rich Results in 2026

This is the part that has changed meaningfully in recent years, and it’s worth being precise about, because outdated advice is common. Google discontinued HowTo rich results in 2023, and in May 2026 it deprecated FAQ rich results as well — the expandable question-and-answer dropdowns that used to appear under organic listings no longer display, with Search Console reporting and the Rich Results Test following in June 2026 and API support ending in August 2026.

Importantly, this doesn’t mean the underlying schema types are invalid or harmful to keep on your pages — FAQPage and HowTo remain valid schema.org types, and Google has stated unused structured data doesn’t cause problems. It simply no longer produces a visible SERP feature for standard content.

Schema types that continue to generate rich results in Google Search include:

How to Implement Schema Markup Correctly

  1. Choose the schema type that actually matches your content. Don’t mark a generic blog post up as a Product or Review just because that schema type happens to be more visually prominent — mismatched markup risks a manual action.
  2. Use JSON-LD format. It’s Google’s recommended format because it keeps structured data separate from the visible HTML, making it easier to maintain and less error-prone than inline microdata.
  3. Validate before publishing. Use Google’s Rich Results Test (search.google.com/test/rich-results) to confirm the markup is both syntactically valid and eligible for a rich result.
  4. Monitor ongoing status in Search Console. The Enhancements section under Search Console reports errors, warnings, and valid item counts across your whole site, which is the most reliable way to catch markup that breaks after a template update.
  5. Keep markup accurate and current. Structured data that misrepresents the actual page content — outdated prices, fabricated ratings — violates Google’s structured data guidelines and risks losing rich result eligibility entirely.

Should You Still Add FAQ or HowTo Schema?

Given the 2026 deprecation, this is a fair question. The honest answer: it depends on your goal. If the goal was purely to win the FAQ dropdown in Google Search, that incentive is gone. But FAQPage markup is still crawled and used by other search engines and by the retrieval systems many AI assistants use to find and cite content, so it may still have value as a signal of clear, well-organized content — just not as a guaranteed visual feature in Google specifically. The safest approach is to keep FAQ and HowTo markup if it’s already well-implemented and accurately reflects genuine Q&A or step-by-step content, but not to treat adding it as a growth tactic on its own.

Frequently Asked Questions

Will adding schema markup improve my rankings?
Not directly. It can improve click-through rate on pages that already rank, by making the listing more visually distinct, but it isn’t a ranking signal by itself.

Can schema markup hurt my site?
Markup that’s inaccurate, spammy, or doesn’t match the visible page content can result in a manual action removing rich result eligibility. Correctly implemented, accurate markup carries no downside.

Do I need a developer to implement schema markup?
Many CMS platforms and SEO plugins support common schema types out of the box. More complex or custom implementations, especially for e-commerce catalogs, typically benefit from developer involvement to keep the markup automatically in sync with the underlying data.

Final Thoughts

Schema markup is a supporting tactic, not a growth lever on its own — it makes genuinely good, relevant content easier for search engines to understand and display attractively, but it can’t substitute for that underlying content quality. Focus implementation on the schema types that still produce visible rich results in 2026, keep the markup accurate, and treat validation as an ongoing maintenance task rather than a one-time setup.

References

Want help auditing your structured data and prioritizing the schema types that still move the needle in 2026? [Link to your contact/services page here.]