Schema markup: winning rich results in search
Schema markup does not move your ranking, but it changes what your result looks like. For a remodeler, review stars, breadcrumbs, and service snippets win more of the screen and lift organic click-through rate by roughly 30%.
Schema markup tells Google what your page means, not just what it says. It does not raise your ranking, John Mueller has confirmed that repeatedly, but it makes you eligible for rich results: the review stars, breadcrumbs, and sitelinks that pull eyes and clicks when a homeowner searches "kitchen remodeler near me." Backlinko found 72.6% of pages on Google's first page already use schema, so the gap is closing. Done right, structured data widens your snippet and lifts organic click-through rate by about 30%. Done wrong, it earns a manual action that strips your rich results entirely. This guide covers the schema types that still pay off, JSON-LD over microdata, and how to test before you ship.
Rich results win the screen, not the ranking
Structured data does not change where you rank. Google has said so directly: it is used to support search features, not to score pages. What it changes is how your listing looks once it ranks. A plain blue link competes on a headline and two lines of text. A result with star ratings, a breadcrumb trail, and sitelinks occupies more vertical space and signals more before the click.
That extra real estate moves the only number you control at a given position: click-through rate. Industry studies cited across Moz and Milestone put the CTR lift from review-star snippets at roughly 30%, and some report 35% with no change to the page copy. Because Backlinko measured the #1 result at 27.6% average CTR versus single digits down the page, a few points of CTR at a fixed position compounds into real traffic.
Use JSON-LD, skip microdata
Three formats exist, but only one is worth your time. JSON-LD sits in a single script tag in the head or body, separate from your visible HTML, so it is easy to template, easy to audit, and easy for Google to parse without rendering the full DOM. Microdata and RDFa interleave attributes through your markup, which makes nested data brittle and changes risky. Google explicitly prefers JSON-LD, and new schema features ship for it first.
Adoption follows. The 2024 Web Almanac found JSON-LD on 41% of pages, up from 34% in 2022, while microdata keeps sliding. If you have legacy microdata, migrate it to JSON-LD rather than maintain both. One caveat that catches teams off guard: Google reads structured data from the HTML the server returns. If your markup is injected by client-side JavaScript after load, it may never be seen. WellBuilt renders schema server-side for exactly this reason.
Pick the schema types that still earn results
Not every schema type produces a rich result anymore, and chasing dead ones wastes effort. Google narrowed the field hard. In August 2023 it limited FAQ rich results to authoritative government and health sites and dropped HowTo on mobile. It finished the job in 2026: FAQ rich results were deprecated on May 7, 2026, with the Search Console report and Rich Results Test support removed by that summer. The FAQPage type is still valid markup, it just no longer renders a rich result for most sites.
Focus on the types that still pay. For a residential contractor, that means LocalBusiness with accurate name, address, phone, and hours, Organization for the brand entity, Service for what you offer, kitchen remodels, home additions, basement finishes, and AggregateRating and Review to earn stars, backed by reviews a homeowner can actually see on the page. Breadcrumb schema replaces the raw URL line with a clean clickable trail.
Schema types worth implementing for service and local businesses:
- LocalBusiness: name, address, phone, hours, and service area for Map Pack and Knowledge Panel signals
- Organization: the brand entity, logo, and social profiles, with each location linked via parentOrganization
- Service: the specific offerings, nested inside LocalBusiness
- AggregateRating and Review: star ratings, backed by reviews visible on the page
- BreadcrumbList: a clickable trail that replaces the URL line and reinforces site structure
Schema markup never moves your ranking. It moves what your result looks like once you rank, and that decides the click.
Eligibility is not a guarantee
A clean Rich Results Test means your page qualifies for a feature. It does not promise the feature will show. Google's algorithms decide per query whether to render a rich result, a plain result, or something else, weighing content quality, site authority, search intent, device, and location. Mark up a page perfectly and stars may still not appear, because Google judged a text result better for that searcher.
Treat schema as a precondition, not a lever. The work that makes the feature likely to show is the same work that earns rankings: genuine reviews behind your AggregateRating, real prices behind Product, content that matches the query. Structured data makes you eligible. Quality and relevance decide whether Google spends the screen space on you. Mark up the pages that already rank or are close, where a richer snippet has somewhere to surface.
Test before you ship, and keep markup honest
Validate every type before it goes live. Google's Rich Results Test parses your JSON-LD, renders the page the way Googlebot does, and reports which features you are eligible for plus any errors and warnings. Errors block the rich result and must be fixed; warnings are optional fields that can strengthen it. After launch, the structured-data reports in Search Console show eligibility and rendering at scale across the site, not one URL at a time.
The hard rule is that markup must match what the user sees. Google's structured-data policy is explicit: do not mark up content that is invisible, irrelevant, or misleading. Declare a price in JSON-LD and that price must appear on the page; claim a 4.8 rating and real reviews must back it. Break this and you risk a spammy structured-data manual action, which strips rich-result eligibility from the affected pages. It does not drop your web ranking, but you lose the snippet that justified the work.
Breadcrumbs and the rest of the SERP surface
Smaller features compound. Breadcrumb schema is one of the lowest-effort wins: it swaps the raw URL for a readable, clickable path and signals a well-organized site. SearchPilot's split test of mobile breadcrumbs paired with server-side schema produced a statistically significant 5% lift in organic traffic. The reverse is just as real: one documented case saw CTR fall from 6.6% to 4.1%, nearly 40%, after a template change dropped breadcrumb schema, then recover to 7% within three weeks of restoring it.
Beyond breadcrumbs, WebSite schema with a SearchAction can enable a sitelinks search box, and consistent Organization markup feeds the Knowledge Panel. None of these rank you. All of them claim more of the result page and more of the searcher's attention. WellBuilt ships these as a bundle, validated and rendered server-side, so the snippet works in production rather than only in the test tool.
Key takeaways
- Use JSON-LD, render it server-side, and migrate any legacy microdata; Google prefers JSON-LD and reads markup from the server's HTML.
- Drop effort on FAQ and HowTo rich results, deprecated in 2026 and 2023; invest in LocalBusiness, Organization, Service, Review, Breadcrumb, and Product.
- Earn star ratings with real, visible reviews behind AggregateRating; review snippets lift organic CTR by roughly 30%.
- Run every type through the Rich Results Test before launch and monitor the Search Console structured-data reports after.
- Keep markup matched to visible content; mismatched or hidden data risks a manual action that strips rich-result eligibility.
SourcesBacklinko, schema markup and organic CTR research, 2024 · HTTP Archive Web Almanac, Structured Data chapter, 2024 · Schema.org, adoption figures (45M+ domains), 2024 · Google Search Central, Changes to HowTo and FAQ rich results, 2023 · Search Engine Land / Search Engine Journal, FAQ rich results deprecation, 2026 · Google Search Central, General Structured Data Guidelines and policies, 2024 · Search Engine Journal, Google confirms structured data is not a ranking factor, 2023 · SearchPilot, mobile breadcrumbs and server-side schema case study, 2024; Dave Ashworth, breadcrumb schema CTR case study · Moz / Milestone, rich snippet CTR lift figures (cited), 2024
Questions, answered straight.
Does schema markup improve my Google ranking?
No. Google has confirmed structured data is not a ranking factor; it makes you eligible for rich results like stars, prices, and breadcrumbs. Those richer snippets lift click-through rate, which can indirectly help over time, but the markup itself does not raise your position. Treat it as a visibility lever, not a ranking shortcut.
Is FAQ schema still worth adding in 2026?
Not for rich results. Google restricted FAQ rich results to government and health sites in 2023 and deprecated the feature entirely on May 7, 2026, removing the Search Console report and Rich Results Test support by that summer. The FAQPage type is still valid markup and will not harm you, but it no longer renders an FAQ rich result for most sites, so do not prioritize it.
Why are my rich results not showing even though the test passes?
Passing the Rich Results Test confirms eligibility, not display. Google decides per query whether to show a rich result based on content quality, site authority, intent, and device, and it may choose a plain result instead. Make sure the page genuinely ranks, has real visible content behind the markup, and matches the query, then give Google time to recrawl.
Can schema markup get my site penalized?
Markup that does not match visible content can trigger a spammy structured-data manual action. It does not drop your web ranking, but it removes rich-result eligibility from the affected pages, so you lose the snippet. Keep every declared value, prices, ratings, content, present and visible on the page, and validate with the Rich Results Test before publishing.
SEO
Want this run for you, not just read about?
Own the searches your buyers make right before they act, and compound the traffic over time.