Practical guide · AI search
Be clear.
Not promised.
What AI-search visibility can and cannot do for a local service business, and what a useful website should make easy to verify.
Last reviewed: 15 September 2026. This guide describes publicly documented search foundations. It does not promise a ranking, citation, recommendation, traffic, enquiries or revenue from any search engine or AI product.
Three things that are often confused
1. Discovery and indexing
A public page first has to be accessible to the crawler that a search product uses. It should have a clear canonical URL, sensible internal links, an accurate title and description, and no accidental blocking rule. This is a foundation, not a guarantee that a page will be selected.
2. Citation
An AI answer may use or link to a page when it needs evidence for a particular query. That decision changes by question, source set and product. A citation is not a stable ranking position and may not appear again for the same business.
3. Recommendation
“Who should I hire?” is the hardest outcome. A useful answer system needs enough clear, reliable information to compare a business with alternatives. It may also rely on sources beyond the business's own website. No provider can honestly guarantee that an AI product will recommend a specific business.
What a local service-business site can control
- Accurate business facts. Keep the service, service area, contact route, legal/provider identity and project process consistent across the pages that matter.
- Useful original pages. Explain real customer questions, practical decisions and limits in plain language. A short, specific guide is more valuable than a large volume of repeated AI-written copy.
- Evidence that can be checked. Use genuine project terms, authorised case information, clear examples and sources. Do not invent reviews, client names, awards or external mentions.
- Technical access. Keep intended public pages crawlable, use a sitemap and check the usual search-console tools. Do not treat a file such as
llms.txtas a magic route to inclusion. - Clear measurement. Track whether pages are indexed, which queries and pages are shown in search reporting, and whether real visitors take the intended next step. Separate those measures from a promise of AI recommendation.
What not to buy or publish
- Bulk pages written only to repeat a town, service or AI keyword.
- Fake reviews, fabricated case studies, invented publications or paid placements presented as independent evidence.
- A promise that a special schema, a directory submission or an AI file will make a business appear in every answer engine.
- Reports that treat a single screenshot or one answer as proof of long-term visibility.
These approaches can make the site less trustworthy to people and less useful to search systems. Clear, original information and real evidence take longer, but they create a base that can be checked.
A sensible monthly check
Use a fixed set of customer-like questions rather than chasing a single branded query. For example: “How do I choose a [service] provider in [place]?”, “What should I ask before a website handover?” and “What information should a [business type] website show?” Record the date, product, exact prompt, sources shown and whether the answer is accurate. Do not count an appearance as a sale or a ranking.
For the underlying website, check Google's AI-search guidance, OpenAI's crawler guidance and Bing's webmaster guidelines. These are useful foundations; none says that inclusion or a recommendation is guaranteed.
Where a practical review helps
A website review can identify unclear service information, weak mobile journeys, missing trust details and obvious crawler-access issues. It cannot turn those findings into a guaranteed result. Linshi Studio's quarterly website and AI-search review therefore delivers a prioritised action list, not an AI-placement promise.