Mastering AnswerThePublic: Turning Customer Questions into Content That Wins UK Business

A repeatable monthly workflow a busy owner can actually stick to

The owners who get value from question research are not the ones who do a huge session once and then forget about it. They are the ones who fit a small routine around the real job. Here is a four-week rhythm that takes a couple of hours a week at most.

Before week one: set the tool up for the UK

Most disappointing AnswerThePublic results come from the settings, not the tool. Before you type anything, check the language and country. Choose English and United Kingdom. If you leave it on the US default, you will get questions about "gas furnaces", "attorneys" and "realtors", and you will waste an hour sorting out American phrasing that no Worthing customer would ever type.

It also helps to know what the result groups mean, because each one suits a different job:

• Questions (who, what, when, where, why, how, can, will, are, which) are your blog and FAQ material. "How much does a new boiler cost" belongs here.
• Prepositions (for, with, near, without, to) often show who is buying. "Boiler repair for landlords" and "boiler repair without a callout fee" tell you about specific audiences and worries.
• Comparisons (versus, or, and, like) show people deciding between options. "Combi boiler vs system boiler" is a classic late-stage question, and people asking it are close to buying.
• Alphabeticals and related terms are useful for spotting wording you had not thought of, such as "boiler pressure low" when you would have written "boiler losing pressure".

Plans change, so check the current limits on your account before you plan around them. Free use has historically been capped to a few searches a day, which is one reason to choose your seed terms carefully rather than typing in everything you can think of.

Week one: search and export

Run two or three seed searches. Pick your main service, one secondary service, and perhaps a problem your customers describe (for example "boiler repair", "emergency plumber" and "no hot water"). Export each one to a spreadsheet and keep everything in a single file with a tab per month, so you can see what you have already covered.

Choose seed terms the way a customer would say them, not the way your trade describes them. A web designer might think "responsive design", but the customer types "website for my business" or "website not showing on Google". If you are not sure, read your last ten enquiry emails and use the words people actually wrote.

Here is what a realistic first session looks like for a heating engineer. A search on "boiler repair" might return well over a hundred questions across the groups. Most are noise: questions about other countries, questions you could never answer in a useful way, near-duplicates such as "how much is boiler repair" and "how much does boiler repair cost". That is normal. You are not looking for a hundred posts. You are looking for six to ten that are genuinely worth writing, and the sorting step in week two is where you find them.

When you export, add three extra columns straight away: Cluster, Action (post, FAQ or bin) and Page (the URL where the answer will live). Filling those in later is far harder than doing it while the list is fresh.

Week two: sort and cluster

Go through the export and group similar questions together. Mark each cluster as a full post, a short FAQ answer, or something to bin. Ten questions about the cost of a job are one cluster and one strong page, not ten thin ones.

Using the boiler example, a sorted list might end up looking like this:

• Cost cluster ("how much does a boiler repair cost", "is it worth repairing a 15 year old boiler", "boiler repair cost UK"): one full post, with a price range table and an honest note on what changes the price.
• Fault-finding cluster ("why is my boiler losing pressure", "why is my boiler making a banging noise"): one post per common fault if you can add real experience, otherwise a single "common boiler problems" guide.
• Quick practical questions ("how long does a boiler repair take", "do I need to be in for a boiler repair", "are you Gas Safe registered"): FAQ answers on the service page, two or three sentences each.
• Out of scope (questions about a boiler brand you do not fit, or about a different country): bin.

Three checks stop you wasting time at this stage.

Check intent. Ask what the person wants at the moment they type the question. Someone asking "how to bleed a radiator" wants to do it themselves, and they may never hire you. That is still worth answering if it builds trust and you can link to a related service, but it should not be your priority over "emergency plumber near me" style questions. Rank clusters by how close they sit to a purchase, then by how often you are asked them.

Check what you already have. Search your own site on Google with site:yourdomain.co.uk boiler repair cost. If a page already covers the topic, improve that page instead of writing a second one. Two pages that answer the same question compete with each other, which is known as cannibalisation, and usually both end up ranking worse than one strong page would.

Check you can add something. If the top results are all long guides from national brands, a 300 word post from you will not break in. Look for questions where you can add local knowledge, real prices, photos from your own jobs or a clear opinion. That is where a small business has an edge.

Weeks three and four: write and publish

Aim for two to four locally relevant posts a month. That matches what typical local SEO content plans suggest for the months after the foundations are in place, and it is a pace most small teams can actually keep up. Mention your town, the areas you cover and local details where they are genuinely useful.

A structure that works well for question-led posts:

1. Title that matches the question. "How much does a boiler repair cost in West Sussex?" beats "Boiler Repair Pricing Guide".
2. A direct answer in the first two or three sentences. For example: "Most boiler repairs in our area cost between £150 and £400, depending on the part and how long the job takes. A new pump or PCB at the top end can cost more." Only quote figures you stand behind, and say when they were last checked. Then explain.
3. Subheadings that are themselves the related questions from your cluster, such as "What affects the price?" and "When is a new boiler better value?".
4. A short, honest next step. A phone number, a quote form or a link to the relevant service page. One clear action is enough.
5. Two or three internal links to related posts and the main service page, using descriptive link text rather than "click here".

Length should follow the question. A simple question may need 500 words. A comparison or cost guide may need 1,200 to 1,800. Do not stretch a post to hit a number. Readers on a phone, often in the middle of a problem, want the answer quickly.

Local detail is what separates your post from a national one. Name the areas you cover (Worthing, Littlehampton, Lancing, Shoreham and so on if that is your patch), mention local housing stock such as older properties with specific boiler types, or note how weather and hard water in your area affect the work. Do not just paste a list of town names at the bottom of a page, which reads as spam to visitors and to search engines alike.

If you use the Content Studio inside AnswerThePublic, treat it as a starting point. Its suggested topics and brand voice settings can give you a sensible first draft structure. Then edit hard. Check every fact, price and claim, add your own experience, and rewrite anything that does not sound like you talking to a customer.

A quick editing test: read the draft aloud and delete any sentence you would never say to a customer on the doorstep. Then add one thing a generic draft could not know, such as a mistake you often see, a price you charged last month or a photo of a typical fault. Regulated trades should be especially careful. Gas, electrical and legal advice must be accurate and should not encourage unsafe DIY, so say clearly when to call a professional.

Every month: feed the FAQs

Keep a running note of questions that arrive by email, phone and reviews. Once a month, add the best ones to the relevant service pages as new FAQs, with a short, direct answer. These are real questions from real buyers, so they often beat anything a tool throws up.

A simple way to capture them is a shared note on your phone, or a column in the same spreadsheet headed "Heard this month". Ask whoever answers the phone to jot down any question that comes up twice. When you see a question three times, it earns a place on the page. Questions about price, timing, guarantees, payment and what happens on the day are nearly always worth including, because they are the things that stop someone picking up the phone.

Tie it together with Search Console

Open Google Search Console and look at the Performance report. Filter for queries containing words like "how", "how much", "can" or "does", and note which ones bring impressions to your pages. Then leave pages alone for 8 to 12 weeks after publishing, and come back to update them. Tighten the opening answer, add the extra questions Google is showing you, and refresh anything out of date.

In practice, use the query filter with a custom regular expression such as how|what|why|can|does|cost|price. Sort by impressions, then look for queries where you are showing but not getting clicks, typically with an average position between 8 and 20. Those are your quickest wins. The page is almost good enough, and a clearer title, a sharper first paragraph or one extra section answering the exact wording can move it up. Search Console is free, so make it the second tab you open after AnswerThePublic.

Turning questions into FAQs and schema markup

Question research pays off twice when you also present the answers in a way that search engines and AI assistants can read easily. That means well-structured FAQ sections, and where it makes sense, schema markup behind them.

Where an FAQ belongs, and where it does not

Put short FAQs on service pages and location pages, directly below the main content and above the final call to action. Keep each answer to roughly 40 to 100 words, with the answer in the first sentence. Longer answers belong in a blog post, and the FAQ can link to it.

Avoid one giant FAQ page with 80 questions. It is hard to read, hard to keep updated, and it detaches each answer from the service it relates to. Five to eight well-chosen questions on each key page does far more work. Do not repeat the same FAQ block across every page either. If "Are you insured?" appears word for word on 20 pages, it adds nothing to any of them.

What FAQ schema is, and an honest view of the benefit

FAQ schema is a piece of code, usually in a format called JSON-LD, that tells search engines which text on the page is a question and which is its answer. In simple terms, the structure is a FAQPage that contains a list of Question items, each with a name (the question) and an acceptedAnswer with the answer text.

There is one important caveat. Since August 2023, Google has limited the expandable FAQ results in its listings to well-known, authoritative government and health websites. For most small UK businesses, you should not expect those extra dropdowns under your listing. The markup is still valid, and it does no harm when it matches the visible content, but it is not a magic ranking switch. The real reward for writing clear question and answer content is that your pages answer what people ask, and that tends to help in standard results, in featured snippets and in the answers AI tools pull together.

So the priority order is simple. Write good visible answers first. Add schema second, if it is cheap to do.

How to add it without breaking your site

1. If you use WordPress, SEO plugins such as Yoast SEO and Rank Math include FAQ blocks that add the markup automatically as you type the questions and answers into the editor. This is the safest route for most owners.
2. If you have a custom or bespoke site, ask your developer to add the JSON-LD to the page template, so each page outputs its own questions. Hand-pasting code into pages is where mistakes creep in.
3. Test every page in Google's Rich Results Test and in the Schema Markup Validator at schema.org. Both are free. Paste the URL, and look for errors (which need fixing) and warnings (which are usually optional).

The mistakes that come up again and again are these. The schema contains questions that are not visible on the page, which breaks Google's guidelines. The answer text in the code differs from the answer on the page. A plugin adds the markup twice, once through a block and once through a site-wide setting. Or someone edits the visible FAQ months later and forgets that the code still holds the old price. Add "check FAQ answers match" to your quarterly review.

Other schema worth having

Before you spend time on FAQ markup, check that the more basic types are in place. LocalBusiness (or a more specific subtype such as Plumber or ProfessionalService) tells search engines your name, address, phone number, opening hours and service area, and it should match your Google Business Profile exactly. Service markup can describe the individual jobs you offer. Article or BlogPosting markup on posts adds the author and the dates. Review markup is risky if you mark up your own testimonials, because Google generally does not show self-serving review stars, so leave that unless your developer is sure of the rules.

Consistency matters more than quantity. A clean LocalBusiness block that matches your business details everywhere beats five half-correct schema types that contradict each other.

Measuring what worked and knowing when to ask for help

Look at results page by page, not just overall traffic. For each page tied to a question, record impressions, clicks and enquiries in your spreadsheet. A post can have modest traffic and still bring in the best leads.

A simple tracking sheet needs only these columns: page URL, target question or cluster, publish date, impressions, clicks, average position, enquiries and notes. Update it once a month from Search Console, and take the enquiry numbers from your contact form, call tracking or just asking new customers where they found you. To see an enquiry source in Google Analytics, set up the contact form submission and the click on your phone number as key events, so you can see which pages people were on beforehand.

Here is an example of how to read the numbers. A post on "How much does a boiler repair cost in West Sussex?" gets 40 clicks a month, whereas a general post on boiler maintenance tips gets 400. Yet the cost post brings in three phone calls a month and the tips post brings none. The cost post is the better page, and the next piece of content should be another price or decision question, not another tips article.

Good signs are rising impressions on question-style queries, and customers saying things like "I read your guide on..." or asking about a topic you have just covered.

Be patient and realistic about timing. A new page on a small site commonly takes a few weeks to be indexed and several months to settle in its position, and local competition changes the pace a lot. Judge a page after three months, not three days. Changing titles and rewriting copy every week stops you learning which change made the difference.

Some common reasons a question page does not perform:

• It does not answer the question in the first few lines, so visitors leave and the page never earns its place.
• It targets a question where every result is a national giant, and there is no local angle to separate you.
• It is not linked from anywhere. A post that no other page links to is hard for visitors and search engines to find, so link it from the related service page and from other posts.
• It is a near-copy of another page on your site, so the two compete.
• The page loads slowly on mobile or the contact details are hard to find, so interested visitors never make contact.

Consider bringing in an agency if you have no time to keep the routine going, if schema throws errors you cannot fix, or if rankings stall even though the content is good. Those are usually technical or authority problems, and they are quicker to solve with an expert looking at the site.

Here is your simple next step: run one search today for your top service, then pick three questions and answer them this week.