Your Shopify FAQ Page Is Invisible to Google. Here's the Fix.
Alexander Mercer
Sep 2, 2026
Most Shopify stores have an FAQ page. Almost none of them get anything from it in search.
The content is usually fine — real questions, real answers, written by someone who knows the products. What is missing is the machine-readable layer that tells Google what those questions and answers are. Without it, an FAQ page is a page with some text on it. With it, the page becomes eligible for search results that display the questions themselves.
The difference is a block of JSON in the page source, and most merchants have no idea it exists.
What structured data actually is
Search engines read your page the way a person does — they see text and try to work out what it means. Structured data removes the guessing. It is a block of JSON, invisible to visitors, that states plainly: this is an FAQ page, here are the questions, here is the answer to each one.
The format is JSON-LD, and the vocabulary is schema.org. For an FAQ the type is FAQPage, containing a mainEntity list of Question objects, each with an acceptedAnswer.
It sits in a script tag in the page head or body. It does not change how the page looks. It changes what a machine reading the page can be certain about.
What it gets you
Eligibility, not a guarantee. That distinction matters and is worth being clear about, because plenty of SEO content is not.
Correct FAQPage markup makes your page eligible for an expanded search result that shows some of your questions directly, with expandable answers. Google decides whether to show it, based on the query, the page and its own judgement. You cannot force it.
What you can do is make it possible. A page without the markup is not eligible at all. And there is a second benefit that is becoming more valuable than the first: AI answer engines read structured data to work out what a page states. Clean FAQPage markup makes your answers straightforward to quote.
How to add it to a Shopify store
Check what you have first
Paste your FAQ page URL into Google's Rich Results Test. It will tell you whether any structured data is detected and whether it is valid. Do this before changing anything — some themes and apps already emit it.
Decide where it should live
Three options: hand-written into the theme template, generated by your FAQ app, or added by an SEO app. Hand-written is fine for a static FAQ that rarely changes. It becomes a maintenance problem the moment the content does.
Generate it from the content, not alongside it
This is the decision that matters. If the markup is written separately from the visible FAQ, the two drift apart the first time someone edits a question and forgets the JSON. Generated from the same source, they cannot disagree.
Only mark up what is visible
Google requires the marked-up content to be present on the page for users. Marking up questions that are not visible is a violation, and it is the most common way stores get their rich results removed.
Validate, then check back
Re-run the Rich Results Test after publishing, then look in Search Console under the enhancement reports a week later to see what Google actually picked up.
“Marking up content that is not visible on the page is the fastest way to lose the rich result you were trying to earn.”
HelloDevs
The mistakes we see most
Markup that has drifted from the content is the big one. A merchant updates their returns policy on the page, and the JSON-LD still describes the old one. Google now has two contradictory statements about the same page, and the one it trusts is the machine-readable one.
Duplicated markup is the second. An SEO app adds FAQPage schema, the theme already emitted some, and the page ends up with two competing blocks. Validators will usually flag this, which is why testing before you add anything matters.
The third is marking up things that are not FAQs. Product specifications, feature lists and shipping tables are not questions and answers, and dressing them as such to chase a rich result is exactly the behaviour the guidelines exist to prevent.
What good FAQ content looks like
The markup is the easy half. The reason most FAQ pages underperform is that they answer the questions the merchant wishes people asked.
Look at your support inbox. The five questions that arrive most often are your FAQ, in that order, whether or not they are flattering. "Why is delivery so slow to Europe" is a better FAQ entry than "What makes your products special", because one is a real query and the other is marketing.
Write the answer the way you would say it to a customer. Structured data will happily carry a hedged, corporate non-answer into a search result, where it will be read by people deciding whether to buy from you.
Doing it without an app
You do not need software for this. If your FAQ content is stable, a developer can add the JSON-LD to the theme template in under an hour, generated from the same page content so the two stay aligned.
An app earns its place when the content changes often, when several people edit it, or when you want the markup generated automatically rather than maintained. The failure mode of the manual approach is not that it is hard — it is that it silently goes stale.
Either way, the important part is the same: the markup should be produced from the content, not maintained beside it.
We build this into what we ship — our own FAQ app generates FAQPage markup on publish, and it is the same approach we take on client stores. See Shopify theme development or AI integrations.
Check yours now
Open Google's Rich Results Test, paste your FAQ page URL, and see what comes back. It takes fifteen seconds.
If nothing is detected, you have an FAQ page doing none of the work it could be doing — and the fix is an afternoon, not a project.
If something is detected, read it carefully and check the questions still match what is on the page. Stale markup is more common than missing markup, and harder to notice.
Our free storefront audit covers structured data across the whole store, not just the FAQ — send us your URL.
Alexander Mercer
Senior Tech Writer at HelloDevs
Alexander covers software engineering culture, design systems, and frontend developer experience. When not writing, you can find him debugging React or exploring typography design.
Stay Updated
Get raw, honest dev-first tutorials and tech blog articles delivered straight to your inbox once a week.
Our guide
- A Shopify development agency builds and maintains the parts of a store Shopify does not give you out of the box. That means custom themes, apps, integrations with your other systems, and ongoing fixes. HelloDevs does all of this and also publishes its own Shopify apps.
- Yes. We work with merchants across North America, Europe, and Asia. Our process is async-first with scheduled overlap hours, so time zones have never been a blocker for a project.
- It depends on scope. Theme customisations typically start in the low four figures; custom apps and full builds range higher. After a free audit we give you a fixed quote — no hourly surprises.
- Absolutely. Private (custom) apps are a large part of our work — from small workflow automations to full ERP integrations that only your store uses.
- Every project ships with a support window, and most clients stay on a maintenance retainer: monitoring, Shopify update compatibility, and a direct line to the same developers who built it.
- Continuity and coverage. An agency gives you review processes, backup when someone is unavailable, and accumulated platform experience across many stores — with one point of accountability.
Didn't Got your answer?
If you still have questions or need further assistance, feel free to reach out to our team. We're here to help you every step of the way.
Our talk
Let's Connect!
Tell us your requirements and get a professional developer response.
