How Specific Should Service, Location, and Customer Pages Be for AI to Understand a Business?

Why does specificity matter for AI?

People describe their situation to assistants. They ask "who can repair a leaking flat roof on a commercial unit in Leeds this week?", not "roofing". The assistant looks for sources that match each part of that question: the service, the property type, the place, the urgency. A page that only says "we offer all roofing services across Yorkshire" matches none of them precisely. A page about flat roof repairs for commercial buildings, naming Leeds and stating response times, matches all four.

Search data points the same way. In Whitespark's May 2025 study of 540 local queries in three US cities, AI Overviews appeared on 97% of searches that mixed a question with a place, such as costs or rules in a named town. In the US, Google reports that searches in AI Mode run to about triple the length of a traditional query. Specific questions reward specific pages.

What does a specific service page include?

Each specific statement gives an assistant a fact to match and quote. Each vague one gives it nothing.

When does something deserve its own page?

Use three tests:

1. Do buyers ask about it separately? Check search data, enquiries and sales calls. If people ask about "flat roof repair" and "pitched roof repair" as different things, they are different pages.
2. Do the facts genuinely differ? Different prices, processes, materials, timelines, regulations or requirements justify separate pages. If only the name changes, they do not.
3. Can you show experience? A page needs proof, such as projects, customers or credentials, specific to its topic.

If all three are yes, create the page. If not, add a clear section with its own heading to a broader page.

How specific should location pages be?

Location pages cause the most trouble, because the temptation is to make one per town with the same text and a different name. Google's spam policies describe that as doorway abuse: multiple pages targeted at specific regions or cities that funnel users to one page, and substantially similar pages that sit closer to search results than a browsable hierarchy.

Create a location page when you have something real and different to say about that place:

• A physical branch, with its own address, hours, team and phone number.
• Different services or prices in that area.
• Local specifics: permits, regulations, travel times, common property types, local projects.
• Reviews and case studies from customers there.

If you serve an area from one base, a single service-area page listing the towns you cover, with response times and examples, is usually better than twenty thin town pages. Google Business Profile works the same way. A service-area business uses one profile listing up to 20 service areas. How to handle city pages in more depth is covered in how to create city-specific service pages for local AI search visibility.

How specific should customer and industry pages be?

Create a page for a customer type or industry when its needs differ: different requirements, regulations, workflows, integrations or budgets. Each should state:

• The specific problems that customer type has.
• How your service or product addresses them, including anything you do differently for them.
• Relevant compliance or standards.
• Examples or case studies from that segment, with results.
• Who within the segment you do not suit, such as by size or specialism.

"Accounting for restaurants" is worth a page if restaurants have distinct needs, such as tips, stock and VAT on food, and you have restaurant clients. "Accounting for every industry" pages with swapped nouns add nothing.

How should the pages connect?

• A hub page for each main service linking to its specific variants, locations and customer types.
• Links back from each specific page to the hub.
• Consistent terms for services across pages, profiles and listings, so assistants recognise the same service everywhere.
• Structured data that matches the page, such as LocalBusiness and Service details. It supports the text; it does not replace it, as covered in whether LocalBusiness or Service schema helps AI understand business details.

How do you check whether the pages work?

Ask assistants questions that combine service, place and customer type, such as "flat roof repair for a warehouse near Wakefield". Record whether you are named and which page is cited. If a broader page is cited instead of a specific one, the specific page may be too thin or too similar to others. If a competitor is named, compare their page's specifics with yours. For multi-location businesses, check that answers cite the right branch, as covered in which pages a multi-location business should fix when AI cites the head office instead of the branch.

What might an illustrative case look like?

Consider an illustrative commercial cleaning company with 60 location pages, one per town within 50 miles, each with the same 300 words and a different town name. Assistants described it as "a cleaning company in Yorkshire" and rarely recommended it for specific questions. The company merged the town pages into one service-area page listing the towns and response times. It then wrote separate, detailed pages for its four main services: office, medical, school and post-construction cleaning. Each had its own checklists, standards, prices and client examples. Within three months, assistants recommended it for questions such as "medical practice cleaning with infection control in Leeds", citing the medical cleaning page.

What do people ask about page specificity?

Can a page be too specific?

Yes, if hardly anyone asks about it or the facts are the same as a broader page. Then it is thin, and a section would do.

Should prices go on every service page?

Ranges, yes, where you can give them honestly. Price is one of the first things buyers and assistants look for.

How long should a specific page be?

Long enough to cover the facts in the table above. For most services, that is a few hundred to a thousand words plus a table.

Do we need separate pages for every combination of service and town?

No. Combine only where both the service and the place change the facts. Otherwise that creates doorway pages.