In-Depth Guide
The Complete Guide to Schema Markup
Our specialists have written a comprehensive guide covering strategy, best practices, and the exact approaches we use for our clients.
Two businesses can rank in the exact same position on Google and get wildly different click-through rates. Star ratings, prices, FAQ dropdowns, and event dates sitting right there in the search result before anyone’s even clicked. That’s schema markup doing its job, and it’s one of the most underused levers in UK SEO right now.
We scope this as strategy and markup selection specifically, working out which schema types actually apply to your business and building the JSON-LD to support them, while broader technical implementation across the site sits under our wider technical SEO work.
What Schema Markup Actually Does
Schema markup is structured code, almost always JSON-LD these days, added to a page to explicitly tell Google what your content means rather than leaving it to infer. A recipe page without schema is just paragraphs and images to a crawler. With schema, it explicitly states the cook time, the ratings, the ingredients, the calories, and everything else laid out in a format search engines can lift directly into a rich result.
It doesn’t guarantee a rich result. Google decides that. But without valid schema present, you’re not even in the running.
Where Most UK Sites Get This Wrong
In our audits across client sites, three mistakes come up constantly.
- Schema copied wholesale from a template site with fields that don’t match the actual page content
- Multiple conflicting schema types stacked on one page, confusing the crawler about what the page is really for
- Markup that was correct at launch but never updated as prices, reviews or stock levels changed
That third one catches out a lot of e-commerce sites specifically. Google’s guidelines are fairly strict on this. Schema has to reflect what’s genuinely visible and accurate on the page, not a snapshot from eighteen months ago.
Schema Types Worth Prioritising by Business Type
Different businesses benefit from different schema, and spreading effort thin across everything rarely pays off compared to nailing the two or three that actually matter.
| Business Type | Priority Schema | What It Unlocks |
|---|---|---|
| Local service business | Local Business, Review | Star ratings, address, opening hours in results |
| Ecommerce | Product, Offer, Aggregate Rating | Price, stock status, review stars |
| Content or blog site | Article, FAQPage, How-To | Rich snippets, FAQ dropdowns |
| Event or venue | Event | Dates, ticket links, and location directly in SERP |
| Professional services | Service, Organization | Trust signals, service listings |
A plumbing business chasing a product schema is wasted effort. Getting the LocalBusiness and Review schema properly configured tends to move the needle far more for that kind of site.
Building and Validating Schema Properly
Writing the JSON-LD is only step one. Validation is where a lot of otherwise solid work falls apart.
Every schema implementation we put live goes through Google’s Rich Results Test before anything gets pushed to a production site. Warnings get investigated even when they don’t block eligibility outright, because a warning today can quietly become a hard error after Google updates its schema requirements, which happens more often than people expect.
We’ve picked up client sites before where the schema had been sitting broken for months, technically present in the code, but throwing errors that meant none of it was being read. Nobody noticed because the page still looked fine to a normal visitor. Rich results simply never appeared, and revenue that should have come from those extra SERP features never showed up either.
Auditing Existing Schema Before Adding More
If a site already has schema in place, and plenty do thanks to page builders and SEO plugins bundling in generic markup, the first job isn’t writing new code. It’s finding out what’s actually there, whether it’s valid, and whether it even matches the business.
This audit work often runs alongside a broader SEO audit, since schema problems rarely exist in isolation. A site with outdated or conflicting schema usually has other technical issues sitting alongside it that are worth catching in the same pass.
Try Our Schema Opportunity Finder:
To find your own markup gaps, use our Schema Opportunity Finder below. Simply paste your URL to receive a prioritised list of eligible schema types your page is currently missing, helping you target the highest-impact rich results first.
Keeping Schema Accurate Over Time
Schema isn’t a set-and-forget job, which is something a lot of agencies gloss over when quoting for the work. Prices change, reviews accumulate, and stock goes in and out. Markup that doesn’t keep pace with the actual page content risks Google treating it as unreliable, which can affect trust in your structured data more broadly, not just on the one outdated page.
For businesses running multiple product or service pages, this usually means building schema into the content workflow itself rather than treating it as a one-off technical task. We handle this as part of ongoing SEO support for a number of clients through Webranko, keeping schema reviewed alongside regular content and technical checks rather than left to drift.