Markup That Merits Attention: A Relevance-Led Schema Review for UK Small Firms
Photo: Siarhei Besarab, CC BY-SA 4.0, via Wikimedia Commons
Structured data is often installed at launch, then left untouched for years. The result is a familiar pattern among UK small businesses: technically valid markup on some templates, invalid or duplicated markup on others, and a lingering assumption that more schema means more visibility. In 2026, that assumption deserves scrutiny. A relevance-led audit asks not 'how much schema can we add?' but 'which markup earns its keep?' For most UK SMEs, the answer is a small set of types tied to visible content and real search features.
More markup is not more visibility
Schema.org is a broad vocabulary. Google's rich results are narrower and conditional. A page can carry technically valid JSON-LD and still receive no enhanced treatment. Markup that describes invisible content, duplicates conflicting entities or claims features not supported by the page adds maintenance burden and potential risk. In 2026, Google continues to restrict or retire rich result types, so an annual review is prudent.
For most UK small businesses, useful markup is entity-based and page-specific. Organization or LocalBusiness describes the business. BreadcrumbList describes site hierarchy. Article or BlogPosting describes editorial content. Product and Offer describe ecommerce items. Event describes a real event. VideoObject describes video content. These types are more likely to support clarity and eligibility than a long tail of speculative types.
FAQPage deserves particular caution. Google has restricted FAQ rich results to a small set of authoritative government and health sites. For a typical UK SME, FAQ markup may be valid but invisible. HowTo rich results are no longer displayed. Sitelinks search box markup has been retired. Keeping these types 'just in case' is not a neutral act; it adds code to maintain and can create misleading expectations.
A four-stage audit
First, inventory. Export the site's URLs and list the schema types and properties present. A crawl tool can help, but a sample of key templates is often enough: home page, service pages, location pages, blog posts, product pages and contact pages. Record where the markup is generated, whether by a plugin, theme or hand-coded template.
Second, validate. Use Google's Rich Results Test and the Schema Markup Validator. Check Search Console's Enhancements reports for errors and warnings. Validation is not the same as eligibility: a valid FAQPage may still not produce an FAQ rich result. The audit should distinguish between technical validity and practical value.
Third, test relevance. For each type, ask whether it describes content visible on the page, whether it matches the page's purpose, and whether it supports a search feature the business can use. LocalBusiness markup on a contact page is relevant. LocalBusiness markup on every blog post is probably not. AggregateRating markup on a service page without visible reviews is a risk.
Fourth, monitor. Record changes in a log, re-test after template updates, and review enhancements monthly. Structured data drifts when content changes. Opening hours, prices and addresses are common sources of decay.
A short worked example
An accountancy firm in Leeds has inherited a site with five schema types: LocalBusiness, Organization, FAQPage, HowTo and BreadcrumbList. The HowTo markup describes a guide to preparing records, but Google no longer displays HowTo rich results. The FAQPage markup is valid, but the firm is not an eligible government or health site, so no FAQ feature appears. LocalBusiness and Organization overlap, with different phone numbers on some pages. BreadcrumbList is accurate.
The audit recommendation is not to add more types. It is to remove HowTo, consolidate LocalBusiness and Organization into a single consistent entity, keep BreadcrumbList, and add Article markup to the firm's guides. The aim is a smaller, more accurate set of statements that search engines can trust.
What to keep and what to remove
Keep markup that is visible, accurate and tied to a supported feature. For a local service business, that usually means Organization or LocalBusiness, BreadcrumbList, and Article or BlogPosting for editorial pages. For ecommerce, Product and Offer remain important, but only where price, availability and reviews are genuinely displayed. For venues and event organisers, Event markup can be valuable when dates and locations are maintained.
Remove or simplify markup that is invalid, invisible, contradictory or unsupported. Do not mark up reviews that are not on the page. Do not use FAQPage as a generic content label. Do not duplicate business entities across plugins. Do not treat schema as a ranking lever; it is a description layer.
The relevance test
The final question is commercial, not technical. Does this markup help a search engine understand a page that matters to the business? If the answer is unclear, the markup probably does not earn its keep. A relevance-led schema audit for UK SMEs is therefore an exercise in subtraction as much as addition. In 2026, the goal is not more structured data. It is better-described content, fewer contradictions and a lower risk of invalid markup.
