How to Write for AI in 2026: Answer the Customer's Service Question

Start with facts, not a special writing formula

Google's AI search guidance says AI Overviews use the existing search requirements. The same applies to AI Mode. A supporting page must be indexed and eligible to show a search snippet. Meeting those conditions does not guarantee inclusion.

The generative search guide rejects the idea that you need special AI text files or a prescribed page length. It says llms.txt has no positive or negative effect on Google Search visibility. Other services may use that file; Google's statement is about Google.

I'd spend the writing time on the questions a customer brings to the page. Name the jobs you accept, your travel area and the work you decline. Those details belong in visible text, where a person can read them.

Replace the slogan with an answer

Here is a made-up furnace company example. The brackets mark facts the business must supply. They are not claims about any contractor I know.

Before: We offer excellent heating solutions throughout our region.

After: We repair [furnace types you service] in [towns and counties you cover]. Call [number] with the model and symptoms. For calls outside normal hours, [state the actual response policy]. We don't handle [work you decline].

The second version tells someone whether to call. It still doesn't promise an arrival time, diagnosis or quote that the business hasn't confirmed. If you only work on gas furnaces, don't imply that an electric heating problem fits.

A replacement page needs different answers. Explain whether the quote includes removal, permits and changes to existing ducts. State what the visit needs to establish before anyone can give a firm number.

A photograph from a completed job can help, with permission and the actual place and date. Use it only if you did the work. A fictional example is useful for teaching; it is lousy evidence for a real service claim.

Put the decision beside the service

The reader should find the service area, equipment limits and contact route beside the job description. Sending them through several broad pages makes a simple question harder than it needs to be.

Use terms your customers use, with a brief explanation when a technical distinction matters. Say whether the service is repair, inspection or installation. Listing every possible synonym doesn't explain what a visit includes.

If the business is one person, write that plainly. If other people take calls or do the work, describe their roles accurately. Changing every “I” to “we” doesn't create another truck.

Short headings and separate paragraphs make the page easier to scan. I wouldn't pad an answer to reach a word count. Add the detail needed to make a decision, then stop.

Structured data is machine-readable information behind the page. It isn't a substitute for missing service details. Google's markup rules require it to represent the visible content.

A question-and-answer section can help customers. It doesn't buy a Google FAQ display: the documentation record says that feature stopped appearing on May 7, 2026. Don't pay for it on that promise.

Location pages need their own useful information. Google's spam policies address city pages that funnel readers to one destination and large amounts of low-value content. A genuine local project or a branch's details have a different purpose.

Give customers the same facts in both places

Your website and Google Business Profile should agree on the name, phone, hours, services and area covered. A person finding two different phone numbers has to guess which record is current.

Google's local search guidance connects complete, accurate business details with local visibility. That is a reason to keep the records current, not a guarantee of a particular position.

Make the next action understandable

A button should say what it does. A quote form should label its fields and explain what happens after submission. Check that a customer can finish it on a phone without guessing what an empty box means.

MDN explains the accessibility tree as a browser representation used by assistive technology. It describes controls through information such as their name, role and state.

Google's agent-friendly website guide describes systems using screenshots, HTML and that accessibility information. Clear labels and real buttons help provide usable signals.

Count the work inquiries, not just visits

Pew studied browsing in March 2025. Regular-result clicks occurred on 8% of summary pages, compared with 15% on pages without a summary. Session endings were 26% with summaries and 16% without. The study covered Google searches generally; it did not measure contractor calls.

BrightLocal's 2026 consumer survey puts self-reported AI use for local recommendations at 45%. The earlier figure was 6%. That comes from self-reports by 1,002 US adults, published by a local marketing vendor. It isn't a count of leads your business received.

Someone might call after seeing a number in a search answer without visiting the site. That is possible, not proof that fewer visits produced more calls. Track useful inquiries and booked jobs separately from website traffic.

When a caller has time, ask what led them to your business. Compare the questions they still ask with what the page explains. That's a practical way to find a missing answer, even when the search report can't show the whole path.