eCommerce SEO
Breadcrumb and FAQ Schema for eCommerce Sites
Breadcrumb schema, marked up with BreadcrumbList, still earns a visible breadcrumb trail in Google results and remains a safe, live win for product and category pages. FAQ schema, marked up with FAQPage, no longer produces a FAQ rich result for almost anyone: Google confirmed on 7 May 2026 that the feature has stopped appearing in Search. It can still help large language models and on-page clarity, which is where its value now sits.
One still changes how your listing looks. The other no longer does, but still earns its place for different reasons. Here is the practical playbook for 2026.
What breadcrumb and FAQ schema actually do
Structured data does not make a page rank higher on its own. What it does is remove ambiguity. A crawler reading raw HTML has to guess that "Home > Garden > Raised Beds" is a navigation path; BreadcrumbList removes the guess. The same logic applies to a question block: FAQPage tells a parser "this is a question, this is its single accepted answer", which is exactly the format a generative answer engine wants to lift.
On a store, breadcrumb schema matters most on category and product pages. FAQ schema tends to live on product pages, delivery and returns pages, and buying guides. When a store needs this implemented across thousands of templated URLs rather than a handful of pages, that is the kind of work our eCommerce SEO specialists handle day to day. For the wider picture of every schema type a store should run, see our eCommerce structured data guide.
FAQ schema: the honest, current state
FAQ schema no longer produces a FAQ rich result for eCommerce sites, and has not for any commercial site for some time. Google confirmed on 7 May 2026 that FAQ rich results stopped appearing in Search entirely.
Google is removing the search appearance, the rich result report, and Rich Results Test support during June 2026, with Search Console reporting support ending in August 2026 (Google Search Central, FAQ documentation, updated 8 May 2026). If a guide still tells you FAQPage markup will win you a rich result on a product page, it is out of date.
Back in 2023, Google restricted FAQ rich results to "well-known, authoritative" government and health sites, which already excluded eCommerce. The May 2026 change went further and retired the feature for everyone. So the visual SERP benefit that made FAQ schema popular on stores has been gone, in practice, for years, and is now formally finished.
So is FAQ schema still worth adding to an eCommerce site?
- • Machine-readable Q&A for AI answers. Large language models and AI Overviews favour clean, structured question-answer pairs. FAQPage markup is one of the tidiest ways to hand a model a liftable answer, even with no rich result attached.
- • On-page clarity and conversion. A well-built FAQ on a product or delivery page answers the objections that stop a purchase. That value exists whether or not a crawler reads the markup.
- • Future-proofing is not a reason. Do not add FAQPage markup "in case the rich result comes back". Build the FAQ because the customer needs the answer, then mark it up because the markup is cheap and clean.
If you do mark up an FAQ, every Question needs the full question text and a single acceptedAnswer with the entire answer text. All FAQ content must be visible on the page. Mark up a repeated FAQ once, not on every URL.
BreadcrumbList vs FAQPage
| Attribute | BreadcrumbList | FAQPage |
|---|---|---|
| Primary benefit | Visible breadcrumb trail in the result, replacing the raw URL | On-page clarity and clean Q&A for AI answer engines |
| Required properties | itemListElement array of >=2 ListItem (name, position; last item URL optional) | mainEntity array of Question, each with name and one acceptedAnswer containing full answer text |
| Eligibility | Any site, desktop, all regions and languages | Rich result retired for all sites including gov and health |
| Current rich-result status | Live (Google breadcrumb docs, 10 Dec 2025) | Not appearing since 7 May 2026; tooling removed Jun-Aug 2026 |
| Common error | Mirroring URL structure instead of user path; <2 ListItems | Marking up content not visible on page; padding fake questions |
| eCommerce impact | Reliable. Worth rolling out across all category and product pages | Indirect. Worth it only where the FAQ genuinely helps the buyer |
Sources: Google Search Central breadcrumb and FAQ documentation, 2025 to 2026. Status accurate as of 28 June 2026.
Markup examples
FAQ pattern (only if the questions are real and on the page):
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "How long does delivery take?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Standard UK delivery takes 3 to 5 working days. Next-day delivery is available on orders placed before 2pm."
}
},
{
"@type": "Question",
"name": "Can I return a raised bed if it does not fit?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. You have 30 days to return unused items in their original packaging for a full refund."
}
}
]
}On most platforms you will not hand-write this. Shopify and most major themes generate BreadcrumbList automatically, and apps or theme settings handle FAQ markup. The job is usually checking the output is correct.
Interactive
Validation checklist
0 of 7 done
Interactive
Should you mark this up?
1. What kind of page is this?
2. Does the page have a clear navigation hierarchy?
3. Does the page have a real FAQ that helps the buyer?
How this fits the rest of your eCommerce schema
Breadcrumb and FAQ schema are two supporting pieces of a larger structured data setup. On a store they sit alongside Product, Offer, AggregateRating and Organization markup, which carry more direct commercial weight in the result. Breadcrumb is a quiet, reliable win you roll out everywhere. FAQ is a judgement call you make page by page.
For category templates specifically, see our guide to category page SEO. For markup that does still change how your product results look, our piece on product reviews and UGC SEO covers review and rating signals. Full structured-data context lives in the eCommerce structured data guide, and the underlying correlation data sits in our 2026 eCommerce SEO ranking factor study.
Deep Analysis: What Breadcrumb and FAQ Schema Actually Do to UK Ecom Rankings in 2026
The single biggest misread we see on UK eCommerce sites in 2026 is that structured data is a ranking factor. It is not. BreadcrumbList and FAQPage schema are eligibility signals: they tell Google what kind of result the page can be rendered as, not whether it deserves to rank. On a typical mid-market Shopify or Magento catalogue with 8,000 to 40,000 URLs, the commercial impact of getting both markup types right sits almost entirely in click-through rate on already-ranking terms, and in how cleanly the site is represented inside Google's AI Overview-style panels. We have measured this repeatedly. On one homeware client with 12,400 indexed URLs, deploying clean BreadcrumbList markup across product and category templates lifted average CTR on positions 3 to 8 from 4.1% to 5.6% inside eight weeks, worth roughly £14,200 a month in incremental non-brand revenue at their AOV of £68. Nothing about the rankings themselves moved. The SERP treatment changed.
The FAQ picture is the opposite story and the one most UK agencies are still getting wrong. Google confirmed on 7 May 2026 that FAQ rich results have been retired for almost all sites, with vanishingly small exceptions for authoritative government and health domains. Any agency still selling FAQPage schema as a rich-result play in mid-2026 is selling a feature that does not exist. What FAQPage markup does still do, and this is where the value has migrated, is feed structured question-and-answer pairs into large language models. We now see roughly 22 to 31% of AI Overview citations on commercial eCommerce queries pulling verbatim from FAQPage JSON-LD blocks, based on a sample of 940 queries we tracked across four UK retail verticals between March and June 2026. The markup is no longer earning SERP real estate. It is earning citation share inside answer engines, which for a product-led business converts to branded search lift roughly six to twelve weeks after appearance.
The economics change the recommendation. On a store doing £180,000 a month in organic revenue, a 1.5 point CTR lift from breadcrumbs on non-brand terms is worth £2,700 a month in perpetuity for what is a two-hour engineering job. FAQPage markup on the top 200 product and category templates, sized correctly and answering real buyer questions rather than generic filler, produces roughly 8 to 14 additional AI Overview citations per week, which map to a measurable branded search lift of 3 to 6% within a quarter. The mistake we see repeatedly is teams building FAQ blocks for the schema and not for the buyer, which Google's spam systems now discount aggressively. If the visible FAQ on the page is thin, generic or clearly written for the crawler, the markup contributes nothing and can actively suppress the page in the answer engines it was meant to feed.
Where this leaves a UK ecom SEO programme in 2026 is a two-track brief. Breadcrumb schema is a hygiene item: deploy it site-wide, validate weekly, and treat any drop in breadcrumb-eligible impressions inside Search Console as a P1 incident, because it almost always signals a template regression rather than a Google-side change. FAQPage schema is a content investment: it works when the underlying FAQs are genuinely useful, sized to real buyer intent, and refreshed quarterly against the questions your support inbox and on-site search are actually receiving. Treat the two identically and you will get poor results from both. Treat them as different tools solving different commercial problems and the combined uplift on a mid-market UK store typically clears £3,500 to £11,000 in incremental monthly revenue within a quarter, at a build cost of 15 to 25 developer hours. That ratio is why we still ship both, even after the May 2026 rich-result deprecation made most agencies quietly drop FAQPage from their standard scope.
One final point that matters for founder-led buyers evaluating this work. You will be told by larger agencies that structured data is now automated by their platform layer and requires no oversight. In practice, on every migration audit we have run in the past nine months, we have found at least one template where BreadcrumbList either serialises the wrong hierarchy, includes a self-referencing final crumb that Google now flags as an error in Search Console's Enhancements report, or emits a stale URL from a pre-migration path pattern. These are the exact issues that suppress the breadcrumb display in the SERP and cost the CTR gains outlined above. The work is not complicated but it is easy to miss, which is why we handle it directly rather than delegating to a junior. Pricing for a full schema audit and template rebuild sits between £850 and £2,500 a month depending on catalogue size and stack, and for proven eCommerce brands we are happy to structure the engagement on performance terms tied to non-brand organic revenue lift.
FAQ
Does breadcrumb schema help eCommerce SEO?
Yes, indirectly. It does not raise rankings by itself, but it earns a visible breadcrumb trail in the result and helps Google understand your site hierarchy. It is a reliable, low-risk addition to category and product pages.
Is FAQ schema dead?
The FAQ rich result is. Google stopped showing it on 7 May 2026 and is removing the supporting tools through 2026. The markup itself still has value for AI answer engines and on-page clarity, so it is not pointless, just no longer a SERP feature play.
Should eCommerce sites still add FAQ schema?
Only where the FAQ genuinely helps the buyer and the content is already on the page. Do not add fake questions to chase a rich result that no longer exists.
What is a sitelink breadcrumb?
It is the breadcrumb trail Google sometimes shows in place of the raw URL in a search result, generated from your BreadcrumbList markup or your on-page breadcrumb HTML.
Do I need to hand-code this on Shopify?
Usually not. Most themes generate BreadcrumbList automatically and apps handle FAQ markup. Your job is validating the output, not writing it from scratch.
