Schema markup is structured code added to web pages that describes their content in a standard vocabulary search engines understand: this page is a product with this price and availability, this business has these opening hours, this article was written by this person on this date. Used well, it helps search engines interpret pages accurately and makes them eligible for rich results — enhanced listings with star ratings, prices, breadcrumbs, event dates or other details — that can make a listing stand out and attract more clicks.
Most UK businesses handle it in one of two ways. Many skip structured data entirely, missing rich results they are eligible for. Others install a plugin or theme feature that generates generic markup automatically, then never check what it produces. The result is often markup that is incomplete, inconsistent with the page, duplicated by several plugins, or aimed at rich result types that Google no longer shows for most sites. At best it achieves little; at worst it attracts warnings, suppressed rich results or, for deliberately misleading markup, manual action.
This guide starts with what structured data actually does and what it cannot do, then covers which schema types are worth prioritising for different business types in 2026, how to implement JSON-LD correctly, the common markup mistakes that get rich results suppressed or trigger manual actions, and how to validate and monitor markup over time. Earlier guides on this blog to schema markup and structured data and rich snippets introduce the vocabulary; this guide updates the picture and focuses on prioritisation and quality.
What structured data actually does, and what it cannot do
Structured data is widely misunderstood, partly because it is often sold as a ranking shortcut. It is better understood as a way of describing your content precisely.
What it does
- Helps search engines understand pages. Explicitly identifying entities — products, organisations, people, events, locations — reduces ambiguity about what a page is about.
- Makes pages eligible for rich results. Many enhanced search features require specific structured data with particular properties.
- Supports other surfaces. Structured data can feed knowledge panels, merchant listings, event and job features and other search experiences where they are available.
- Keeps key facts consistent. Marking up business details, prices and dates in one standard format encourages accuracy across the site.
What it cannot do
- It is not a direct ranking factor. Google has stated that structured data helps it understand pages but does not, by itself, boost rankings. Indirect benefits come through rich results and better understanding.
- It does not guarantee rich results. Valid markup makes a page eligible; whether a rich result appears depends on Google’s systems, the query and the page’s overall quality.
- It cannot describe content that is not there. Markup must reflect what users can see on the page. Describing invisible or misleading content is against Google’s guidelines.
- It does not compensate for weak content. A thin page with perfect markup remains a thin page.
Before adding more markup, run your ten most important pages through Google’s Rich Results Test and the Schema Markup Validator. Many businesses discover markup they did not know they had, generated by plugins or themes, often duplicated or contradictory. Fixing what exists is usually the best first step.
Structured data on UK business sites — the numbers
The figures below are indicative, drawn from SEO audits we carry out for UK business websites. They are not a formal survey.
The third figure deserves attention. In 2023 Google significantly restricted FAQ rich results, saying they would generally be shown only for well-known, authoritative government and health websites, and removed how-to rich results. FAQ markup is not harmful and can still help search engines understand question-and-answer content, but most businesses adding it for the sake of expanded listings will not see them. Effort is better directed at rich result types that remain widely available.
Plugin defaults versus deliberate markup
The comparison shows the difference between relying on automatically generated markup and implementing structured data deliberately.
Plugin defaults, unchecked
Markup generated automatically and never reviewed
Deliberate structured data
Types chosen for the business, implemented and monitored
Plugins are not the problem in themselves; many generate good markup when configured properly. The problem is leaving them unchecked. A deliberate approach often uses the same tools, configured carefully, with duplicates switched off and gaps filled.
What structured data audits find
The chart shows how often each problem appears in the structured data audits we carry out on UK business websites. Most sites have more than one, so figures add up to more than 100%.
Duplication and missing properties are the most common issues, and both stem from automatic generation without review. The fifth and sixth items carry the most risk: markup describing content that is not visible, and businesses marking up reviews of themselves on their own pages, are the patterns most likely to lead to rich results being withheld or, in deliberate cases, manual action.
Rich results in 2026: a reality check
The set of rich results Google shows has changed considerably in recent years, and much advice written earlier is out of date. Google has restricted or retired several features as it has simplified search results, so check its current structured data documentation before investing in any particular type. As a broad guide:
Still widely valuable
- Product and merchant listing markup for e-commerce: price, availability, shipping and returns information, and product review ratings, supporting product rich results and shopping experiences.
- Review snippets for eligible content types such as products, recipes, software and books, where reviews are genuine and visible on the page.
- Breadcrumbs, which help search engines understand site structure and can display a clearer path in results.
- Organisation markup (the schema.org Organization type) including logo, name and contact details, which supports how the business is represented in search.
- Article markup for news and blog content, supporting correct dates, authors and images.
- Video markup where pages feature video, supporting video results and key moments.
- Event markup for businesses that run public events with dates and venues.
- Job posting markup for businesses advertising vacancies on their own sites.
- Local business markup, which supports understanding of location details, though local results rely heavily on your Google Business Profile.
Restricted or retired for most businesses
- FAQ rich results, now generally shown only for authoritative government and health sites.
- How-to rich results, removed.
- Several niche types that Google has phased out as part of simplifying search results.
What this means in practice
Prioritise the types that match your content and remain supported. Markup for restricted types is not harmful and may still aid understanding, but do not expect visual enhancements from it. Above all, avoid investing heavily in a type because an older article said it delivered dramatic click-through gains.
The main schema types explained
A short description of the schema types most UK businesses are likely to use, and what each needs to be useful.
Organisation and local business
Describes the business itself: legal or trading name, logo, website, contact details, social profiles and, for local businesses, address, opening hours, geographic coordinates and service area. Usually placed on the home page and contact page. Accuracy and consistency with the Google Business Profile and other listings matter more than completeness for its own sake.
Breadcrumbs
Describes the page’s position in the site hierarchy, matching the breadcrumb trail shown on the page. Simple to implement through most content management systems and widely supported.
Product and offers
Describes a product with its name, image, description, brand and identifiers, and an offer with price, currency and availability. Recommended properties such as shipping, returns and review ratings enrich product results. Accuracy and freshness are essential, since prices and stock change frequently.
Review and aggregate rating
Describes individual reviews or an overall rating for an eligible item, such as a product. Ratings must come from genuine reviews visible on the page.
Article
Describes news, blog and editorial content, including headline, images, publication and modification dates and author. Helps search engines show correct dates and attribute content properly.
Event
Describes events with name, dates, location or online status, organiser, ticket offers and status such as cancelled or postponed. Must be removed or updated once an event has passed.
Job posting
Describes vacancies with title, description, location, employment type, salary where provided and closing date. Must be removed when the role is filled.
Video
Describes video content with title, description, thumbnail, upload date and duration, and can support key moments within longer videos.
Scoring schema priorities by business type
The value of each schema type depends on what a business does and what its pages contain. The score grid compares priorities for three common business types; a high badge means a high priority.
Local service businesses benefit most from accurate organisation and local business markup, consistent with their Google Business Profile, as covered in our guide to local SEO and the local pack. E-commerce retailers should prioritise complete product and offer markup and breadcrumbs. B2B and professional services firms, which often rely on content to attract prospects, gain from organisation and article markup, and from event markup if they run webinars or seminars. Video markup applies to any business publishing video on its pages.
What structured data costs
The table compares indicative costs of different approaches to structured data for a UK business website. Figures are broad ranges and depend on the size of the site, the platform and the number of templates.
| Approach | Indicative cost | What it delivers | Main risk |
|---|---|---|---|
| Plugin or theme defaults, unchecked | Free or included | Generic markup on some pages | Duplication, gaps and outdated types |
| Structured data audit and clean-up | £500 to £2,000 | Duplicates removed, errors fixed, gaps identified | Needs follow-through to implement |
| Template-level implementation | £1,000 to £5,000 depending on templates | Accurate markup generated from real page data | Must be maintained when templates change |
| E-commerce product markup with feed alignment | £2,000 to £8,000 | Complete product, offer and review data | Price and stock must stay in sync |
| Ongoing monitoring | An hour or two a month, or part of an SEO retainer | Errors caught and fixed quickly | Neglect lets problems accumulate |
For most businesses, the best value comes from an audit and clean-up followed by template-level implementation of a few well-chosen types, so markup is generated automatically from real data on every relevant page. That is more reliable than hand-coding individual pages and far more reliable than unchecked defaults.
Structured data maturity — where most UK business sites sit
Combining choice of appropriate types, completeness of properties, alignment with visible content, absence of duplication and regular monitoring gives an indication of structured data maturity. The gauge reflects a typical UK business website.
A score in the low thirties usually reflects a site with some automatically generated markup, often duplicated across plugins, missing key properties, partly aimed at rich results that are no longer widely shown, and never monitored. Some rich results may appear, mostly by accident.
An audit, clean-up and template-level implementation of the right types typically lifts maturity into the seventies, after which light monthly monitoring keeps it there.
Correct JSON-LD implementation
Structured data can be written in several formats, but JSON-LD — a block of structured data placed in the page, separate from the visible content — is the format Google recommends, and the easiest to implement and maintain. A few principles determine whether a JSON-LD implementation works well.
Generate it from real data
The most reliable markup is generated by the website’s templates from the same data that produces the visible page: the product’s actual price and stock level, the article’s real publication date and author, the business’s current address and opening hours. Hand-written markup on individual pages tends to drift out of date as content changes.
Match the visible content
Everything in the markup should be visible to users on the page, or clearly reflected by it. Prices, ratings, dates and descriptions in markup must match what people see. Discrepancies, deliberate or accidental, can lead to rich results being withheld.
Use the most specific appropriate type
Schema.org offers broad types and more specific ones. Use the most specific type that accurately describes the content, such as a specific kind of local business rather than the general type, where it genuinely applies.
Populate required and recommended properties
Google’s documentation lists required properties for each rich result type and recommended properties that improve eligibility and presentation. Missing required properties prevent rich results; missing recommended ones may limit them.
Connect entities
Markup is more useful when entities link together consistently: the organisation that publishes articles, the brand that makes products, the business that runs events. Using consistent identifiers for the organisation across pages helps search engines connect them.
One source per page
Make sure only one system generates each piece of markup on a page. If a theme, an SEO plugin and an e-commerce plugin all output product or organisation markup, switch off the duplicates and keep the most complete source.
Keep it in sync
For e-commerce, product markup should reflect the same price and availability as product feeds and the page itself. Changes in one place should flow through to all. Our e-commerce SEO guide covers product data more broadly.
Protecting structured data through redesigns and platform changes
Structured data is often lost or broken when a website is redesigned, migrated to a new platform or has its theme changed. New templates may not output the same markup, plugins may be swapped, and data fields may move. Businesses sometimes see rich results disappear a few weeks after a relaunch without realising why.
Treat structured data as part of any redesign or platform change. Record what markup each template currently outputs and which rich results pages earn, build equivalent or better markup into the new templates, and test representative pages on staging before launch. After launch, watch Search Console enhancement reports closely for drops in valid items. The same applies to smaller changes: a plugin update or theme change can alter markup without anyone noticing.
Implementing structured data step by step
The timeline sets out a practical sequence for auditing and implementing structured data on an existing UK business website.
Template-level implementation means the work scales: once the product template generates correct markup, every product page benefits. Rich results can take weeks to appear after deployment as search engines recrawl pages, and appearance is never guaranteed, so judge results over months rather than days.
Structured data practices in place
The progress bars show how often each structured data practice is in place across the UK business websites we audit. Figures are indicative.
Structured data practices in place
Presence of markup is common; quality is not. Fewer than a third of sites have complete required properties, a single clean source per page and markup generated from live data, and very few review it against current guidance or measure its effect. That gap is where most of the opportunity lies.
Markup mistakes that suppress rich results or trigger manual actions
Google can choose not to show rich results for markup it considers inaccurate or misleading, and for deliberate abuse it can apply a manual action for spammy structured markup, reported in Search Console, which removes rich result eligibility until fixed. The patterns that cause most problems are well documented in Google’s guidelines.
- Marking up content users cannot see. Reviews, prices, questions or details present in markup but not on the page.
- Self-serving reviews. Businesses adding review markup about themselves on their own site for local business or organisation types, which Google does not show as review rich results.
- Fabricated or aggregated reviews without basis. Ratings that are not genuinely collected from users, or copied from elsewhere.
- Misleading prices or availability. Markup showing a lower price or stock that the page does not offer.
- Marking up irrelevant content. Using a schema type that does not match the page, such as event markup on a page that is not about an event.
- Applying page-specific markup site-wide. For example, the same review or product markup on every page.
- Outdated information. Event dates that have passed, jobs that are filled, prices that have changed.
Most businesses do not set out to mislead; these issues usually arise from plugins, templates or old markup nobody revisited. Regular review against Google’s structured data guidelines prevents them.
Structured data for content, authorship and expertise
For businesses that rely on content to attract and convince prospects, structured data can help make authorship and publication details explicit. Article markup can identify the author, linking to an author page that describes their expertise, and the organisation that publishes the content. Accurate publication and update dates help search engines understand how current information is.
This does not replace genuine expertise or quality content, which search engines assess in many other ways. But for professional services, healthcare, finance and other fields where credibility matters, consistently identifying who wrote content, their qualifications and the organisation behind it supports the broader picture of trustworthiness. Make sure author pages exist, are accurate and are linked from the content they describe.
How often sites carry structured data errors
Across the UK business websites we audit that have structured data, the proportion with at least one error or invalid item reported in Search Console enhancement reports is high.
The figure is indicative rather than a formal survey. Errors usually mean a required property is missing or a value is in the wrong format, which makes those pages ineligible for the affected rich result. Many are simple to fix at template level, but they persist because nobody looks at the reports. Our guide to using Google Search Console shows where to find them.
Case study: from plugin clutter to product rich results
A UK online retailer of outdoor equipment, with around 2,500 products, had used three plugins over the years that each output structured data: its theme, an SEO plugin and a reviews plugin. Product pages carried three separate product markup blocks, two with different prices, one missing availability, and review markup on the home page describing the business itself. FAQ markup had been added to every product page in the hope of expanded listings. Search Console showed thousands of product markup errors, and product rich results appeared only sporadically.
An audit identified which source generated each block. The retailer kept the e-commerce platform’s product markup, configured to output price, currency, availability, shipping and returns information and genuine product review ratings from the platform’s own review data, and switched off product markup in the theme and SEO plugin. The self-serving review markup on the home page was removed. FAQ markup was left only where pages had genuine visible question-and-answer content, with no expectation of rich results. Breadcrumb and organisation markup were standardised through the SEO plugin. Product markup was aligned with the shopping feed so price and stock matched everywhere.
Over the following two months, product markup errors in Search Console fell to near zero, and the share of product pages showing price, availability and rating information in results rose substantially. Click-through rates on affected product pages improved, though the retailer was careful to note that seasonal demand and other changes also played a part.
“We had more structured data than anyone needed and almost none of it was right. Cleaning it up was mostly a matter of switching things off and configuring one source properly. Our product listings now show the information customers actually want to see.” — E-commerce Manager, UK outdoor equipment retailer
The lesson is not that plugins are bad. It is that structured data needs one deliberate source per page, populated from real data and checked against current guidance.
The 12-point structured data checklist
The checklist covers the essentials for structured data that earns rich results and stays out of trouble.
- Audit what already exists. Test key templates and review Search Console enhancement reports.
- Find every markup source. Theme, plugins, scripts and tag managers.
- Remove duplicates. One source per markup type per page.
- Choose types for your business. Prioritise supported rich result types matching your content.
- Check current Google guidance. Some types are restricted or retired.
- Use JSON-LD. Google’s recommended format.
- Generate from real data. At template level, from the same data as the page.
- Complete required and recommended properties. For each type used.
- Match visible content. Nothing in markup that users cannot see.
- Avoid self-serving reviews. Use review markup only where eligible and genuine.
- Validate before and after deployment. Rich Results Test and Schema Markup Validator.
- Monitor monthly. Enhancement reports, rich result appearance and click-through.
A small number of well-chosen schema types implemented accurately across every relevant page will achieve more than a long list of types applied inconsistently. Start with organisation, breadcrumbs and the one or two types most relevant to your business, get them right, then expand.
Common structured data mistakes
The mistakes below account for most of the structured data problems we find.
- Installing a plugin and never checking it. Defaults are often incomplete or duplicated.
- Running several plugins that output markup. Conflicting data confuses search engines.
- Expecting FAQ rich results. Now restricted to a narrow set of sites.
- Marking up invisible content. Against guidelines and a route to suppressed rich results.
- Self-serving business reviews. Not shown as rich results and best avoided.
- Missing required properties. Pages become ineligible for the rich result.
- Hand-coding pages individually. Markup drifts out of date as content changes.
- Prices and stock out of sync. Markup, feeds and pages disagree.
- Treating schema as a ranking hack. It aids understanding and eligibility, not rankings directly.
- Never reviewing enhancement reports. Errors accumulate unnoticed.
Structured data that describes content users cannot see, invents reviews or shows prices and availability the page does not offer can lead Google to withhold rich results and, in serious cases, apply a manual action for spammy structured markup. If a manual action appears in Search Console, fix the markup across the site, then request reconsideration with an explanation of the changes.
Validating and monitoring markup over time
Structured data is not a one-off task. Templates change, plugins update, products come and go and Google’s supported features evolve. A light monitoring routine keeps markup working.
Validation tools
- Rich Results Test from Google shows whether a page is eligible for supported rich results and highlights errors and warnings for those types.
- Schema Markup Validator checks markup against the wider schema.org vocabulary, including types Google does not use for rich results.
- Search Console enhancement reports show valid and invalid items across the site for each supported rich result type, with examples of affected pages.
- URL inspection in Search Console shows how Google sees a specific live page, including detected structured data.
A monthly routine
Once a month, review enhancement reports for new errors or sudden drops in valid items, test one page of each main template, and check that recently changed templates still output correct markup. After any site update, plugin change or redesign, test representative pages immediately.
Measuring impact
In Search Console, compare click-through rates for pages before and after rich results begin appearing, and use the search appearance filter, where available, to see performance for specific rich result types. Treat the results cautiously: rankings, seasonality and competitor changes also affect click-through, so look at trends over several months rather than individual weeks.
Structured data and AI-driven search
Search increasingly includes AI-generated summaries and answers alongside traditional results. How these systems use structured data is not fully documented, and claims that particular markup guarantees inclusion in AI answers should be treated with scepticism.
What can be said with more confidence is that clear, accurate, well-structured information helps any system interpret a page: consistent organisation details, explicit product attributes, clear authorship and dates, and content that answers questions directly. Structured data contributes to that clarity alongside good headings, clear writing and authoritative content. The sensible approach is to implement structured data well for its established benefits, and to treat any effect on AI-driven features as a possible bonus rather than the goal.
Who should own structured data
Structured data sits between marketing, content and development, which is why it is often neglected. Marketing or SEO teams usually understand which rich results matter and can monitor enhancement reports; developers implement and maintain template-level markup; content and product teams keep the underlying data accurate.
Agree a named owner, often whoever is responsible for SEO, who reviews enhancement reports monthly, checks markup after site changes and raises issues with developers. Include structured data in the acceptance criteria for new templates and features, so it is considered at build time rather than bolted on afterwards.
At a glance: structured data and rich results
| Topic | Key point | What to do |
|---|---|---|
| Purpose | Helps understanding and rich result eligibility | Do not treat it as a direct ranking factor |
| Rich results | Eligibility, not a guarantee | Judge results over months |
| Supported types | Product, review, breadcrumb, organisation, article, video, event, job and others | Check current Google documentation |
| Restricted types | FAQ rich results limited; how-to removed | Do not expect visual enhancements from them |
| Format | JSON-LD recommended | Implement at template level |
| Data source | Real page and product data | Generate markup automatically, not by hand |
| Accuracy | Markup must match visible content | No hidden or misleading information |
| Reviews | Self-serving business reviews not shown | Use review markup only where eligible and genuine |
| Duplication | Multiple plugins create conflicts | One source per markup type per page |
| E-commerce | Price and stock must stay consistent | Align markup, feeds and pages |
| Validation | Rich Results Test and Schema Markup Validator | Test before and after deployment |
| Monitoring | Search Console enhancement reports | Review monthly and after site changes |
| Manual actions | Possible for spammy structured markup | Fix across the site and request reconsideration |
How Cloudswitched approaches structured data
We treat structured data as part of technical SEO rather than an add-on. Every engagement starts with an audit of existing markup across your key templates, identifying which tools generate it, where it duplicates or conflicts, which required properties are missing and whether it targets rich results that are still supported.
We then choose the schema types that fit your business and content — organisation and local business details, breadcrumbs, product and offer data, articles, events, jobs or video as appropriate — and implement them at template level in JSON-LD, generated from the same data as your pages so markup stays accurate as content changes. Duplicates are removed, entities are connected consistently, and for retailers, product markup is aligned with shopping feeds. We validate on staging and live, and monitor enhancement reports and rich result performance monthly.
No implementation can guarantee rich results, which Google shows at its discretion, but accurate, well-chosen structured data gives your pages the best chance of standing out where those features are available.
Is your structured data helping or just there?
Talk to us about a structured data audit, clean-up and template-level implementation for your website.
Talk to an SEO SpecialistFrequently Asked Questions
What is schema markup?
Structured code added to web pages, using the schema.org vocabulary, that describes content in a standard way search engines understand, such as products, businesses, articles and events.
Does structured data improve rankings?
Google has said it does not directly boost rankings. It helps search engines understand pages and makes them eligible for rich results, which can improve click-through rates.
What are rich results?
Enhanced search listings that show extra information, such as prices, availability, star ratings, breadcrumbs, event dates or video thumbnails, generated partly from structured data.
Does FAQ schema still produce rich results?
For most businesses, no. Since 2023 Google has generally shown FAQ rich results only for well-known, authoritative government and health sites. FAQ markup may still help understanding but should not be expected to create expanded listings.
What is JSON-LD?
A format for adding structured data to a page as a separate block of code, rather than woven into the visible HTML. It is Google’s recommended format and the easiest to implement and maintain.
Which schema types should a local business use?
Typically organisation and local business markup with accurate name, address, phone, opening hours and logo, consistent with the Google Business Profile, plus breadcrumbs and article markup where relevant.
Which schema types matter most for e-commerce?
Product markup with offers, including price, currency, availability, shipping and returns where supported, genuine product review ratings, and breadcrumbs, all kept consistent with product feeds.
Can we mark up reviews of our own business?
Google does not show review rich results for self-serving reviews of local businesses or organisations on their own websites. Review markup is appropriate for eligible types such as products, with genuine reviews visible on the page.
Can structured data get us penalised?
Markup that is misleading or describes content users cannot see can lead to rich results being withheld and, in serious cases, a manual action for spammy structured markup, shown in Search Console.
How do we test our structured data?
Use Google’s Rich Results Test for rich result eligibility, the Schema Markup Validator for wider schema.org validity, and Search Console enhancement reports and URL inspection for live site status.
How long do rich results take to appear?
Often several weeks after deployment, as search engines recrawl pages, and appearance is never guaranteed. Judge results over months.
Are SEO plugins good enough for structured data?
Many generate good markup when configured carefully. Problems arise when several plugins output overlapping markup or defaults are left unchecked. Configure one source per type and validate the results.
Related reading
More guidance for UK businesses from the Cloudswitched blog:
- Website redesign planning: avoiding the mistakes that tank SEO rankings
- Virtual CIO onboarding: what the first 90 days should look like
- Network capacity planning: forecasting growth before your network becomes the bottleneck
- Office downsizing and consolidation: moving to a smaller office without losing IT capability
- Microsoft 365 Copilot adoption: why most deployments fail to change how people work
Stand out in search with accurate structured data
Cloudswitched audits, cleans up and implements structured data for UK business websites, focused on the rich results that are still worth winning.
Talk to an SEO Specialist
Cloudswitched
London-based managed IT services provider offering support, cloud solutions and cybersecurity for SMEs.
