Someone searches “website design Nottingham”. They do not stop there. The next questions are already forming — what does it cost, how long does it take, do you cover my town, what happens after I enquire, and should I even hire you. If those answers only live in a sales call, the page that brought them in has already failed half the job.
I am Harry Ashton. Hashton is a Nottinghamshire studio. I write service pages the way I answer calls: plain, specific, and honest about when we are not the right fit. This post is about the follow-up questions your service page should answer on the page itself — not on a dozen thin synonym URLs — because Google’s own generative AI features fan out into related searches before they assemble an answer.
Follow-up questions belong on the service page, not on a separate thin FAQ farm. Photo: fauxels / Pexels.
What Google means by query fan-out
In Google’s Search Central guide on optimising for generative AI features in Search, the company describes query fan-out: a set of concurrent, related queries the model generates to fetch more results while answering the original ask. AI Overviews and AI Mode are not separate internets. They still pull from indexed, crawlable pages grounded in core Search systems.
That matters for a local firm in Nottingham, Derby, or Leicester. A visitor — or an AI summary — may start with your service head term, then immediately need price shape, area, timeline, process, and proof. Google’s guide also says not to manufacture a separate page for every fan-out variation just to chase rankings or AI responses. Doing that to manipulate Search can fall under scaled content abuse. Non-commodity content that answers real follow-ups beats a swarm of near-duplicate “guide” URLs.
Practical takeaway: put the real follow-ups on the service page in clear headings. One strong URL. Honest answers. No synonym spam.
Start with the service page, not a content farm
If you sell website design, your money page is something like website design in Nottingham — not twenty blog posts that restate the same paragraph with a different town in the title. Blog posts still earn their keep when they teach a decision. They should not replace the service page’s job of answering “what happens if I enquire tomorrow”.
I have written before that if it has no URL, search cannot find it. The flip side is also true: if every mild rephrase gets its own thin URL, you dilute the one page that should carry proof, process, and next steps.
The follow-ups I expect a local service page to answer
These are the questions I hear on calls with East Midlands independents. They belong under clear headings on the service page, written in the same voice as the rest of the site.
What do you actually deliver?
Not “digital excellence”. Say whether you rebuild, redesign, or fix. Say what ships: templates, forms, analytics, Search Console access, training, leaveable code. If you only do brand and hand off to someone else for build, say that. Vague hero copy makes people invent a scope you never meant.
Who is this for — and who should look elsewhere?
Name the buyer: independent clinics, trades, studios, professional services. Also name when not to hire you — marketplace apps, huge retainers, or a same-week brochure with no content ready. “When not to hire us” is trust, not negative SEO. It stops the wrong enquiries burning both calendars.
Where do you work?
Service-area clarity beats a fake street address on every page. Say Nottinghamshire and the towns you will travel to. If Derby and Leicester work are normal, say so without inventing a second headquarters.
What happens after I enquire?
Spell the first steps: a short call or walkthrough, what you need (hosting login, goal of the site, who buys), and what they get back (scope note, timeline shape, yes/no). People are asking whether they will be ghosted after the form submit.
How long does a typical project take?
Give ranges only when they are honest. A brochure rebuild is not a multi-location booking site. Name what slows things down: missing copy, no photos, committee approvals, waiting on domain access. Timelines without dependencies are theatre.
What about price — without fake package theatre?
If you cannot publish fixed packages without lying, do not invent them. Say what drives cost: templates, migrations, integrations, content readiness. Ranges are fine when they are real. Invented “from £X” banners that never match the quote train people to distrust every agency in the city.
What proof do you show?
Case notes, before/after URLs, outcomes you can stand behind — not a wall of logos you cannot explain. Sharper buyer questions are covered in what a Nottingham business should ask a web designer. Your service page should survive those without a pitch deck.
Will the new site be findable?
Say whether you handle redirects, titles, sitemap, indexing basics, and a sane information architecture. Redesigns that ignore URLs lose equity. If the brief is still a mood board, fix that first — see a redesign brief before you open Figma.
How this helps AI Overviews without gaming them
When generative features fan out into related questions, they look for grounded passages on real pages. Clear headings that match how people ask — process, area, timeline, fit — give those systems something specific to cite. That is not a hack. It is the same structure a tired human wants on mobile between jobs.
What does not help: spinning a separate cost page, a “near me FAQ”, and a “best web designer” page that all say the same three paragraphs. Google’s guide warns against manufacturing pages for every variation primarily to manipulate rankings or AI responses. Write the answers once on the service URL that should rank.
A simple structure I use on service pages
- Who it is for — then who should not enquire.
- What you get — deliverables in plain English.
- How it works — enquiry → discovery → build → launch → handover.
- Area and working style — towns, remote vs on-site.
- Time and cost drivers — ranges only if honest; name dependencies.
- Proof — concrete examples with links where possible.
- FAQ-shaped sections — real leftover questions, not keyword stuffing.
- One clear next step — call, email, or short walkthrough.
Leicester and Derby firms hit the same pattern — template sites that never get owned, or redesigns that chase “modern” without a brief. The service-page rule stays the same.
FAQ-shaped answers worth putting on the page
Do I need a separate FAQ page for every service?
Usually no. Keep service questions on the service URL under clear headings. A sitewide FAQ can cover studio topics — invoicing, support windows — without duplicating every answer.
Should I write a blog post for each follow-up question?
Only when the answer needs depth a service page cannot hold — a full redesign brief, or a comparison people genuinely research. Otherwise you are building a content farm. Teach on the blog; close the loop on the service page.
Does answering price ranges hurt conversions?
Hiding every number and surprising people on a call hurts more. Honest drivers and ranges filter wrong leads. If work is custom, say what moves the quote instead of publishing a fake menu.
Is this the same as “AEO” or “GEO”?
Google’s guide treats optimisation for generative AI features as still SEO: crawlable, useful, non-commodity pages grounded in Search. You do not need a new acronym stack or a page per fan-out query. You need the answers a careful buyer already asks.
What if my current page is mostly adjectives?
Replace adjectives with decisions. Swap “passionate creatives” for what ships in week one. Swap “bespoke solutions” for whether you migrate content, set up forms, and leave the repo. Then add the follow-ups above. That rewrite usually beats a new visual theme.
If your service page still reads like a brochure and the real answers only appear on Zoom, that is the gap. Put the follow-ups where search — and people — can read them.
Nottingham independents — if the site sells the service but never answers what happens after enquire, I’ll walk through a rebuild in 20 minutes. hashton.agency or 07545 850764.