Two results sit at position four. One shows a price, a star rating and a breadcrumb trail. The other shows a blue link. Structured data is the cheapest CTR gain in SEO, and it is now how AI engines decide what your page is about.
Three patterns account for most of the schema markup work we take on. If one of them is yours, the audit will confirm it in a fortnight.
Competitors show stars, we don't.
Review markup has strict eligibility rules and Google ignores it when it's self-serving or unverifiable. We implement the version that actually qualifies.
Eligibility-first buildSearch Console flags schema errors we don't understand.
Usually a plugin emitting conflicting blocks, or required properties missing. We consolidate to one clean graph per page type. Fix the template, not the four hundred URLs.
Conflict cleanupAI answers describe us incorrectly.
Language models lean on structured data to resolve entities. Wrong or absent markup means they guess, and they guess from whoever else mentions you.
Entity definitionSequenced deliberately, because each phase depends on the one before it. Numbering here means order, not decoration. The full method is written up in our nine-step schema markup audit if you'd rather run it yourself.
Benchmarks, not promises. Your starting point decides how far and how fast, and the audit gives you both numbers before you commit to anything.
Range across Google's own published case studies, from Rotten Tomatoes at the low end to Nestlé at the high end, comparing pages with rich results to pages without.
Every template passing Rich Results Test before it ships.
Consolidated markup instead of three plugins arguing with each other.
Google's figures compare pages with rich results against pages without, not the same page before and after. Treat them as directional. Structured data is not a ranking factor, and schema work will not rescue a page that ranks below position 10 — that needs relevance and authority first. Benchmarks reflect the standards we work to, not guaranteed outcomes.
No. Google has been consistent that structured data is not a ranking factor in itself. It changes how your result is displayed, which changes click-through rate, which does affect performance over time. It also helps AI engines identify and cite you correctly.
Not for rich results. Google restricted FAQ rich results to health and government sites in 2023, then removed them for all sites in May 2026. HowTo rich results went the same way in 2023. The markup stays valid and harmless, and AI answer engines still read question and answer pairs, so we keep existing implementations. We don't build new ones, and we never count FAQ coverage as a rich result win.
Three separate things. Whether the JSON-LD parses, whether the page qualifies for the rich result the markup targets, and whether Google is choosing to render it. A validator only covers the first. Most of the problems we find sit in the second and third. The full nine-step process is here.
Partly. Plugins cover the basics and often emit duplicate or conflicting blocks alongside your theme's own markup. We usually keep the plugin, disable its overlapping output, and add the custom graph it can't produce.
Google has to recrawl and then decide to show the feature. Google's own guidance says two weeks or more after a validation request, and in practice two to six weeks is normal. Eligibility is what we control. Display is Google's call.
Service schema doesn't generate a visual rich result for most service businesses, so treat it as entity clarification rather than a click-through play. It tells search engines what you offer, who provides it and where. That only works when it's connected to a properly defined Organization entity, which is where most implementations fall over.
Usually one of four reasons. The page isn't indexed yet, the schema type no longer earns a rich result, the markup doesn't match the visible page content, or the page sits below Google's quality threshold for enhancement. We check indexing first, then work down that list.
Invalid markup is generally ignored rather than penalised. The real risk is markup that misrepresents the page, such as declaring reviews or prices that aren't visible on it. That falls under Google's structured data spam policies and can cost rich result eligibility across the whole site.
Schema Markup rarely runs alone. These are the three we most often run alongside it.
Getting cited in AI Overviews, ChatGPT, Perplexity and Gemini, measured rather than guessed.
Explore →FoundationSchema issues are usually a symptom of template problems. The audit finds the cause.
Explore →GrowthCategory architecture, product templates, faceted navigation and the schema that sells.
Explore →No obligation, no sales sequence. We'll show you what's actually holding your schema markup back and what it would take to fix it.