Schema Markup Every UK Small Business Should Ship in 2026

Schema markup for small business sounds like a developer-only job, and for years it was treated that way. The reality in 2026 is simpler and more urgent. Search results are denser, AI answers sit above the blue links, and the businesses that label their pages clearly are the ones that get pulled into both. The good news for a UK small business is that the high-value markup is a short list, the format is readable, and you can test it before anything goes live.

This guide covers what to ship, what to skip, and how to verify it, with every figure tied to Google's own documentation.

What is schema markup, in plain terms?

A web page is just text and images to a person. To a machine, "£45" could be a price, a phone extension or a postcode fragment. Schema markup removes the guesswork by wrapping content in a shared vocabulary from schema.org. According to Google Search Central, Google Search supports three formats, JSON-LD, Microdata and RDFa, and it recommends JSON-LD because it is the easiest solution to implement and maintain at scale. JSON-LD sits in a single <script type="application/ld+json"> block in the page head, so it never disturbs your layout. That separation is why it is the sensible default for a small site you want to keep tidy.

Does schema markup actually move the needle for a small business?

The honest framing matters here, because plenty of advice oversells it. Schema does not promise a higher rank. It improves how your listing looks and how confidently machines read it, which drives clicks.

Those three figures come straight from Google's structured data documentation↗. They are large-brand examples, so treat them as the ceiling rather than your guaranteed result. For a local UK business the gain is usually a more complete listing, your star rating or opening hours showing in search, and fewer mistakes when an AI tool summarises you.

Which schema types should a UK small business ship first?

The list of available schema types is long, but most of it is irrelevant to a plumber, salon or accountancy practice. Concentrate effort here:

• LocalBusiness: name, address, telephone, opening hours, geo-coordinates and service area. This is the backbone for any business with a physical location or a defined patch. It pairs naturally with the work in our Google Maps SEO guide for the UK.
• Organization: your legal name, logo URL and links to your social and review profiles, which helps Google connect the dots about your brand identity.
• Product: name, price in GBP, currency and availability, only on genuine product pages.
• Review and AggregateRating: only where real ratings appear on the same page. Marking up invented or off-page reviews breaks Google's guidelines.
• Breadcrumb: cheap to add and gives a cleaner path in the result.

If you serve a single trade in one area, the focused approach in our local SEO playbook for UK plumbers shows how LocalBusiness markup fits alongside your Google Business Profile.

How do you write JSON-LD without breaking the page?

A basic LocalBusiness block names the type, then lists the properties as key and value pairs: business name, full UK address with postcode, telephone in international format, opening hours and a URL. The two rules that prevent most problems are simple. First, one clean block per thing you are describing, rather than several conflicting versions. Second, never mark up a fact that is not visible on the page, because Google treats hidden or contradictory markup as a quality violation. Draft it with a free generator if you like, but read every line afterwards. Generators happily insert placeholder hours or the wrong country format, and a wrong postcode in your markup is worse than no markup at all.

What about FAQ and HowTo schema in 2026?

This is the biggest change to plan around. Per Google's FAQ documentation↗, FAQ rich results are now reserved for well-known government and health sites, so a typical UK business no longer sees the expandable FAQ listing in Search. HowTo rich results were wound down in the same way and no longer feature in the current gallery. The practical takeaway is to stop building pages around these two types and to keep any FAQ content as plain, helpful text.

How do you test schema markup before it goes live?

Testing is non-negotiable, because invalid markup is common and silent. The Rich Results Test takes a URL or a code snippet and tells you whether the page qualifies for a rich result and which required properties are missing. The URL Inspection tool inside Search Console is the better check for live pages, since it shows the rendered markup Google saw rather than what you hope it saw. Work through the warnings, correct any blank required field or mismatch between code and visible content, then request indexing. After that, the relevant Search Console report will show how the markup performs over the following weeks.

Does schema help you get found by AI search and ChatGPT?

AI answer engines read the open web and prefer sources they can parse with confidence. When your name, address and prices are labelled, a model is far less likely to invent details about you. Structured data is one of several signals that feed this, alongside consistent business information across the web and clear on-page text. The broader visibility picture sits in our AI visibility hub, and if your goal is to appear in Google's AI summaries, the tactics in our guide to ranking in Google AI Overviews build directly on clean markup.

What are the common mistakes that get schema ignored?

The patterns repeat across sites. Markup that describes hidden or absent content is the classic error, and it can cost you eligibility entirely. Missing a required property, such as a price on a Product block, quietly disqualifies the page. Review markup pointing at ratings that do not appear on the same page is a guidelines violation that can trigger a manual action. Finally, duplicate or contradictory blocks confuse the parser. Keep one accurate block per entity, mirror only what a visitor can see, and you avoid almost all of these.

How long does it take to see results from schema markup?

There is no fixed timeline, because it depends on how often Google crawls your site and whether the markup passes validation. A small site updated rarely may wait longer than a busy one. Once a page is corrected and re-crawled, eligibility can appear within a few weeks, though Google still chooses when to show a rich result. Treat schema as foundational plumbing that pays off steadily, not a switch you flip for instant traffic.

Ship the short list, skip the retired features, and test before you publish. That sequence is what separates markup that earns a better listing from code that sits in your head doing nothing.