Most London service businesses have never touched schema markup. That’s not a guess — recent industry audits put overall adoption at roughly 31%, with professional and local services consistently among the least-covered sectors.
That gap is the opportunity. Schema markup SEO doesn’t require content changes, backlinks, or ongoing effort once it’s set up correctly — just accurate code that tells Google, Bing, and AI search tools exactly what your business is, where it operates, and why it’s trustworthy.
This is a genuine setup guide, not a conceptual overview. It includes working JSON-LD examples for the schema types that actually matter for a London service business in 2026 — and an honest account of a major change earlier this year that’s made a lot of existing schema advice out of date.
Quick Answer: What Schema Markup Actually Does in 2026
Schema markup is structured code — almost always written in JSON-LD — that tells search engines and AI tools exactly what your business, services, and reviews are, rather than leaving them to infer it from page text. For London service businesses, the highest-value types are LocalBusiness (or a specific subtype), Service, Review/AggregateRating, BreadcrumbList, and Organization. Properly implemented schema is linked to click-through rate improvements of roughly 20–30% through rich results, and it’s now a documented input to how AI tools decide what to cite.
Why Schema Markup Is Still an Underused Advantage
The numbers make the opportunity clear:
- Only around 31% of websites implement any schema markup at all, according to recent industry auditing.
- In a 2026 audit of 5,000 production sites, professional services represented just 10% of sites with schema deployed — one of the smallest shares of any sector measured, alongside publishers and agencies.
- Among first-page Google results, roughly 72% use some form of schema, according to Backlinko’s analysis — a strong correlation between structured data and visibility, even if not a direct causal ranking factor.
- JSON-LD now appears on roughly 41% of all pages, up from 34% two years earlier, per the HTTP Archive Web Almanac.
- 71% of pages cited by ChatGPT use schema markup, tying structured data directly to the AI search visibility we covered in our dedicated guide.
Expert tip: Deployment isn’t the same as quality. The same 2026 audit found a large, measurable gap between sites that have some schema and sites with valid, error-free schema — and validity correlated more strongly with AI citation rates than deployment alone. Copy-pasting a generic template isn’t enough; it needs to actually validate against your real page content.
The Schema Types That Still Earn Rich Results in 2026
Not every schema type still does what older guides claim. Here’s the current state for London service businesses specifically.
| Schema Type | Still Earns Rich Results? | Priority for Service Businesses |
| LocalBusiness / Service subtypes | Feeds Knowledge Graph, Maps, and AI grounding (not a visual SERP chip on its own) | Essential |
| Review / AggregateRating | Yes — star ratings in search results | Essential |
| BreadcrumbList | Yes — breadcrumb trail display | High |
| Organization | Feeds Knowledge Panel data | High |
| Person | No direct rich result, but supports E-E-A-T signals | Moderate |
| FAQPage | No — retired from Google Search as of May 2026 | Low (see Section 7) |
| HowTo | Largely discontinued since 2023 | Low |
Setup Guide: LocalBusiness and Service Schema
Use the most specific schema.org subtype available — Electrician, Plumber, HVACBusiness, LegalService, and dozens of others all exist as recognised subtypes of LocalBusiness. If nothing matches precisely, LocalBusiness itself is a safe fallback.
| { “@context”: “https://schema.org”, “@type”: “Electrician”, “@id”: “https://example.co.uk/#business”, “name”: “Example Electrical Services Ltd”, “url”: “https://example.co.uk”, “telephone”: “+44-20-7946-0958”, “priceRange”: “££”, “address”: { “@type”: “PostalAddress”, “streetAddress”: “12 Example Street”, “addressLocality”: “Hackney”, “addressRegion”: “London”, “postalCode”: “E8 1AB”, “addressCountry”: “GB” }, “geo”: { “@type”: “GeoCoordinates”, “latitude”: 51.5450, “longitude”: -0.0553 }, “areaServed”: [ { “@type”: “City”, “name”: “Hackney” }, { “@type”: “City”, “name”: “Islington” }, { “@type”: “City”, “name”: “Tower Hamlets” } ], “openingHoursSpecification”: [ { “@type”: “OpeningHoursSpecification”, “dayOfWeek”: [“Monday”, “Tuesday”, “Wednesday”, “Thursday”, “Friday”], “opens”: “08:00”, “closes”: “18:00” } ]} |
For a specific offering, add a Service block referencing the business as provider:
| { “@context”: “https://schema.org”, “@type”: “Service”, “serviceType”: “Emergency Electrical Repair”, “provider”: { “@id”: “https://example.co.uk/#business” }, “areaServed”: { “@type”: “City”, “name”: “Hackney, London” }} |
Expert tip: Every field in this markup should match your Google Business Profile exactly — same address format, same phone number, same hours. Mismatches between GBP and schema quietly undermine the confidence both Google and AI tools place in your data, a point we cover in more depth in our GBP checklist.
Setup Guide: Review and AggregateRating Schema
Star ratings in search results come from AggregateRating, and they’re one of the few schema-driven visuals left with genuine click-through impact.
| { “@context”: “https://schema.org”, “@type”: “Electrician”, “@id”: “https://example.co.uk/#business”, “name”: “Example Electrical Services Ltd”, “aggregateRating”: { “@type”: “AggregateRating”, “ratingValue”: “4.8”, “reviewCount”: “126” }} |
Compliance matters here. Google’s guidelines restrict self-serving review markup — you can’t fabricate ratings or mark up testimonials you wrote yourself. This data should mirror genuine reviews collected on Google, Trustpilot, or a similar third-party platform, and should update as your real review data changes rather than sitting static.
Setup Guide: BreadcrumbList, Organization, and Person Schema
BreadcrumbList — shows the page hierarchy directly in search results:
| { “@context”: “https://schema.org”, “@type”: “BreadcrumbList”, “itemListElement”: [ { “@type”: “ListItem”, “position”: 1, “name”: “Home”, “item”: “https://example.co.uk” }, { “@type”: “ListItem”, “position”: 2, “name”: “Services”, “item”: “https://example.co.uk/services” }, { “@type”: “ListItem”, “position”: 3, “name”: “Emergency Electrician Hackney”, “item”: “https://example.co.uk/services/emergency-electrician-hackney” } ]} |
Organization — feeds Knowledge Panel data and connects your social profiles:
| { “@context”: “https://schema.org”, “@type”: “Organization”, “name”: “Example Electrical Services Ltd”, “url”: “https://example.co.uk”, “logo”: “https://example.co.uk/logo.png”, “sameAs”: [ “https://www.facebook.com/example”, “https://www.linkedin.com/company/example” ]} |
Person — supports E-E-A-T by formally connecting an author or reviewer to your business, the same byline pattern used throughout this series:
| { “@context”: “https://schema.org”, “@type”: “Person”, “name”: “Jane Smith”, “jobTitle”: “Senior Electrician”, “worksFor”: { “@id”: “https://example.co.uk/#business” }} |
The FAQPage Situation: What Changed in May 2026
This is worth its own section because a lot of schema advice still circulating hasn’t caught up.
FAQ rich results — the expandable question-and-answer dropdowns that used to appear under search listings — were already restricted to “well-known, authoritative government and health websites” back in August 2023. On 7 May 2026, Google retired the feature entirely. FAQ rich results no longer appear in Google Search for any website, in any vertical.
A few things that are genuinely true, and worth separating from panic:
- FAQPage remains a valid schema.org type. It won’t cause validation errors, and Google has confirmed unused or inert structured data doesn’t harm your site.
- It’s not an AI Overview shortcut. Google’s own AI features guidance states there’s no special schema required for AI Overviews or AI Mode, and that structured data should match your visible page text rather than substitute for it.
- Google Search Console’s FAQ reporting and the Rich Results Test’s FAQ check are being phased out through mid-2026, so don’t build workflows that depend on them going forward.
The practical takeaway: stop adding FAQPage schema purely to chase SERP rich results — that use case is gone. If you already have it deployed and it’s low-cost to maintain, there’s no urgent need to rip it out. But your energy is far better spent on the Tier 1 schema types in Sections 4–6, and on writing genuinely useful, visible FAQ content in your actual page HTML rather than relying on the markup wrapper to do the work.
London-Specific Schema Considerations
- List real boroughs and neighbourhoods in areaServed, not just “London” as a single value — this mirrors the neighbourhood-first search behaviour covered in our borough-by-borough guide.
- Use accurate GeoCoordinates for your actual business location, not a rounded or approximate value.
- Format phone numbers in full UK international format (+44-20-…) for consistent machine parsing.
- Multi-location businesses need a distinct LocalBusiness block per genuinely staffed location, each with its own @id, rather than one block trying to represent several addresses at once.
How Schema Feeds AI Search Visibility
Structured data has quietly become one of the clearest bridges between traditional SEO and AI search. As covered in our AI search visibility guide, fact density and clear structure are what earn citations from tools like ChatGPT and Google AI Overviews — and schema is the most direct way to hand over that structure.
With 71% of ChatGPT-cited pages carrying some form of schema markup, and Google’s own AI systems drawing on your Google Business Profile and website together (see our GBP checklist), accurate LocalBusiness, Service, and Review schema now does double duty: supporting traditional rich results where they still exist, and giving AI tools clean, structured facts to cite.
10. Step-by-Step: How to Implement Schema This Week
- Audit what’s already on your site. Use Google’s Rich Results Test and the schema.org validator to see what’s deployed and whether it’s error-free.
- Choose the most specific LocalBusiness subtype available for your business, rather than defaulting to the generic type.
- Build your LocalBusiness and Service JSON-LD using the templates in Sections 4–6, matching your Google Business Profile data exactly.
- Add AggregateRating only with genuine review data, sourced from a real platform, not fabricated.
- Add BreadcrumbList and Organization schema sitewide, ideally via your CMS template rather than page by page.
- Deprioritise FAQPage unless you have a specific, low-cost reason to keep it — don’t invest new effort chasing rich results that no longer exist.
- Validate everything before publishing, and re-check quarterly as your business details change.
Common Mistakes
- Copy-pasting a generic template without updating it to match real business data — a leading cause of the “deployed but invalid” gap covered in Section 2.
- Letting schema drift out of sync with your actual Google Business Profile or website content over time.
- Marking up fabricated or self-authored reviews as AggregateRating data, which breaches Google’s guidelines.
- Prioritising FAQPage schema in 2026 on the assumption it still drives rich results or AI citations.
- Using one LocalBusiness block for multiple locations instead of a distinct block per genuinely staffed address.
Myths vs Facts
Myth: Schema markup is a direct Google ranking factor.
Fact: Google has stated structured data isn’t a direct ranking signal, though it strongly correlates with rich results, click-through rate, and AI citation likelihood.
Myth: FAQPage schema still helps you appear in AI Overviews.
Fact: Google’s own AI features guidance says no special schema is required for AI Overviews or AI Mode, and structured data should reflect visible content rather than substitute for it.
Myth: More schema types are always better.
Fact: A handful of correctly implemented, genuinely relevant types outperform a large volume of loosely applied ones — validity matters more than volume.
Myth: Schema markup is a set-and-forget technical task.
Fact: It needs to stay in sync with your actual business data — hours, address, reviews — or it becomes a liability rather than an asset.
A Worked Example
Consider a hypothetical heating and plumbing company in Hackney with a functional website but zero structured data. After implementing LocalBusiness, Service, Review, and BreadcrumbList schema matching their Google Business Profile exactly — and deliberately skipping FAQPage, since it no longer earns rich results — the business began showing star ratings in search results within a few weeks, once Google recrawled and validated the new markup.
The bigger shift showed up gradually in referral patterns from AI tools, as ChatGPT and Google AI Overviews began citing the business’s service pages more consistently than before. The lesson: a small, correctly validated set of schema types outperformed the instinct to add everything available, including the type that quietly stopped mattering months earlier.
Frequently Asked Questions
What is schema markup and why does it matter for SEO?
Schema markup is structured code that tells search engines and AI tools exactly what your content and business represent, rather than leaving them to infer it. It supports rich results, click-through rate, and AI search citations.
Is schema markup a Google ranking factor?
Not directly, according to Google’s own statements. It’s strongly correlated with rich results and AI citation rates, which indirectly support visibility and clicks.
What’s the most important schema type for a service business?
The most specific available LocalBusiness subtype (like Electrician or Plumber), paired with Service and Review/AggregateRating schema, covers the highest-value use cases for most London service businesses.
Does FAQPage schema still work in 2026?
Not for Google Search rich results — that feature was fully retired on 7 May 2026. The schema type remains technically valid but no longer produces a visible SERP feature.
Do I need schema markup for AI search visibility?
It helps significantly. A large share of pages cited by AI tools like ChatGPT carry schema markup, giving these systems clean, structured facts to reference.
What format should I use for schema markup?
JSON-LD is Google’s clearly preferred format. It’s separated from your visible HTML, making it easier to maintain and less error-prone than embedded microdata.
How do I check if my schema markup is working?
Use Google’s Rich Results Test for Google-specific eligibility, and the schema.org validator to confirm general structural accuracy.
Can I mark up my own testimonials as review schema?
No. Google’s guidelines restrict self-serving review markup — AggregateRating data needs to reflect genuine third-party reviews, not content you wrote yourself.
Should I remove FAQPage schema if I already have it?
Not urgently. Google confirms unused structured data doesn’t harm your site, but new effort is better spent on schema types that still produce visible results.
How often does schema markup need to be updated?
Whenever the underlying business details change — hours, address, services offered — and ideally re-validated on a quarterly basis regardless.
Is schema markup something I can set up myself?
Yes, particularly with the templates in this guide, though our DIY vs agency comparison is worth reading if you’re weighing the time investment against hiring it out.
Does every page on my site need schema markup?
No. Focus on your homepage, service pages, and location pages first — the pages most likely to appear in relevant searches — rather than applying it uniformly sitewide.
15. Summary and Key Takeaways
Schema markup remains one of the more genuinely underused levers in London local SEO — not because it stopped working, but because most competitors still haven’t implemented it correctly, if at all. The setup itself is a one-time technical task with a long payoff, provided it stays accurate and current.
Actionable takeaways:
- Prioritise LocalBusiness/Service, Review, BreadcrumbList, and Organization schema — these still earn visible results in 2026.
- Deprioritise FAQPage schema for new work; it no longer drives Google rich results as of May 2026.
- Match every schema field exactly to your Google Business Profile data.
- Validate before publishing, and re-check quarterly as business details change.
- Treat schema as infrastructure for AI search visibility, not just traditional SEO.
