FAQs on Location Pages Without Creating Duplicate Content
An FAQ block is the easiest thing to copy across a set of town pages, which is exactly why it so often becomes the part Google ignores. The same five questions, the same five answers, the town name swapped in the heading. It reads like content. It behaves like filler.
The repeated-block mistake
Here is how it happens. You write a good FAQ for your main service page: how much it costs, how long it takes, whether you are insured, what happens if it rains. Then you build a page for each town you cover, and the FAQ comes along for the ride. Forty pages later, the same block sits on every one of them, identical word for word.
The questions were never the problem. A roofer in Harrogate and a roofer in Ripon field the same questions. The problem is that an answer which says nothing about the place adds nothing to the page about the place. It is the clearest signal you can send that the page was assembled, not written, and it feeds straight into the wider duplicate content problem on location pages: text that exists in forty near-identical copies, distinguished only by a swapped noun.
Localise the answer, not just the question
An FAQ earns its place when the answer could only have been written for that town. That does not mean stuffing the place name into every sentence. It means the answer carries information that changes from one location to the next.
Take a question every trade gets: “How quickly can you get to me?” A generic answer says “usually within a few days”. A local one says where you are based, how far that is, and what it means for this town:
- Generic: “We aim to respond within 48 hours.”
- Local: “We work out of Otley, so Guiseley is a fifteen-minute run. For weekday call-outs there we can usually be on site the same day.”
The second answer is still about response time. It now also tells the reader something true and specific: the base, the distance, the realistic timing for that place. Other questions localise the same way. Parking and access differ between a terraced street and a village with a single lane. Permit and conservation rules differ by council. The kind of property you mostly work on differs by area. Each of those is a genuine answer that could not be lifted onto the next town’s page without becoming false. That is the test. If you can move the answer to another page and nothing about it is now wrong, it was never local. The same discipline runs through the rest of your local landing page content, and the FAQ is simply the section where the shortcut is most tempting.
You do not need a dozen unique questions per page to do this. Three or four genuinely localised answers do more than ten recycled ones. If a question has the same answer everywhere, such as whether you take card payments, it belongs on a central page, not repeated across every town. A workable location page template keeps the shared, company-wide answers in one place and reserves the on-page FAQ for what actually changes by location.
Only mark up what is visible on the page
If you add FAQPage structured data, Google’s rule is plain: every question and answer in the markup must appear as visible content on the page. You cannot mark up a question that only exists in the code, and you cannot put a longer or different answer in the schema than the one a visitor reads. The markup is meant to describe the page, not to smuggle in extra text. Google’s structured data policies also rule out using FAQPage for advertising or for content the reader cannot see.
This connects back to duplication in a way that is easy to miss. If your visible FAQ is identical across forty pages, your structured data is identical across forty pages too. Localising the answers fixes both at once. It also keeps your local business schema honest, because the schema describes a page that genuinely differs rather than dressing up forty copies of the same one.
Why this is hygiene, not a snippet tactic
It is worth being clear about what FAQ markup buys you, because the answer has changed. In August 2023 Google restricted FAQ rich results to well-known, authoritative government and health sites, which removed the visible FAQ snippet for almost every business. As of May 2026 Google has stopped showing FAQ rich results in Search altogether and marked the feature documentation as deprecated. For an ordinary local business, marking up your FAQ will not produce a rich result. It has not done so for years, and now it cannot.
So treat localised FAQs as content hygiene, not as a play for snippets. The reason to write a real answer for each town is that it makes the page worth ranking, helps a reader decide to call you, and removes a block of duplicate text that would otherwise drag on the whole set. The markup, where you use it, simply has to match. None of that depends on a rich result, which is the right footing to build on: the page has to stand up on its own merits whether or not search engines decorate it.