A service page that gets retrieved and cited by AI chatbots looks structurally different from one optimized for traditional Google ranking. The retrievable version leads with a direct answer in the first 60 words, uses question-shaped H2s that match how buyers actually phrase prompts, and is built out of self-contained 2–4 sentence paragraphs that can stand alone when chunked. The traditional-SEO version often does the opposite — burying the answer below brand throat-clearing, using benefit-language H2s (“Quality Service You Can Trust”), and writing in flowing paragraphs that lose meaning when separated from the page around them. Restructuring an existing service page to the retrievable pattern is one of the highest-ROI AEO moves available.
This post walks through the specific structural pattern, then shows a before/after on a representative service page. The principles apply equally to home service trades and local professionals — anywhere a buyer might ask an LLM “who does X in [city]?”
The core structural pattern
A retrievable service page has six sections, in this order:
-
The lead answer (first paragraph, bolded). A 40–80 word direct answer to the question “what is this page about and what does this business do?” Written so it stands alone — if a retrieval system chunks this paragraph and presents it without the rest of the page, it still makes complete sense.
-
The “what” detail (one or two paragraphs). Specifics of the service — scope, what’s included, what’s not, typical durations or quantities. Written as factual statements, not marketing claims.
-
Question-shaped H2s with short direct answers (3–6 of them). Each H2 is a question a real buyer might type into an AI chatbot. The answer below is 40–80 words, self-contained.
-
Process or what-to-expect section. How the service actually works from the customer’s side. Numbered list is fine here; LLMs retrieve lists cleanly.
-
Pricing posture (one paragraph). Even if you don’t publish exact prices, say something concrete about the pricing model — flat-fee vs. hourly, typical range, what affects price, whether quotes are free. The absence of any pricing signal is itself a signal that drives prospects elsewhere.
-
CTA / contact. Email, phone, scheduling link. Short.
Service pages built this way typically run 600–1,200 words. Longer often hurts — at 2,000+ words the retrieval system has too many candidate passages to choose from, and the strongest individual passages get diluted by ranking against each other.
The four shifts that matter most
If you only have time to fix four things on your existing service pages, these are the highest-leverage:
1. The first 60 words say what the service is
Most service pages open with brand throat-clearing: “At Smith Plumbing, we pride ourselves on delivering excellence to families across the Phoenix metro. With over 20 years of experience, our team is committed to…” — three sentences, zero answer to the question “what does this page describe?”
The retrievable version: “Tankless water heater installation across the Phoenix metro, typically completed in a single day for in-stock models. We work on Navien, Rinnai, and Bosch units, handle the permit and inspection, and warranty our installation labor for one year on top of the manufacturer’s coverage.”
That second version, lifted alone and presented in a chatbot answer, makes complete sense. The first one, lifted alone, conveys nothing.
2. H2s are questions, not benefit statements
A common SEO instinct is benefit-driven H2s: “Quality Service You Can Trust,” “Why Choose Us,” “Our Commitment to Excellence.” These do nothing for AEO. They’re not retrieval targets because no buyer types those phrases into ChatGPT.
The retrievable pattern: H2s that mirror how buyers actually phrase prompts. “How long does tankless water heater installation take?” “Do you work on existing tankless systems or only new installations?” “Is permit and inspection included in your quote?” These match the prompt vocabulary buyers actually use, so LLMs return your H2 as the answer to their question.
3. Each paragraph is self-contained
This is the most counterintuitive shift for trained writers. Traditional editorial paragraphs flow from one to the next — each paragraph builds on the previous one’s context. That flow is exactly what breaks down in chunk-based retrieval.
The retrievable pattern: write each paragraph as if it might be the only paragraph the reader sees. Subjects named explicitly (not “it” or “this”), dates and locations included, technical terms defined briefly. Reads slightly redundantly to a human reading top-to-bottom — but each paragraph survives extraction intact.
4. Specific facts, not adjective stacks
“Fast, reliable, professional service” is invisible to LLMs. They have no way to verify or weight the claim. “We typically respond to emergency calls within 90 minutes during business hours, and within 4 hours overnight” — that’s a fact. It can be wrong, but it can also be cited.
The pattern: every paragraph should contain at least one concrete fact (number, timeframe, brand name, geographic specificity). Adjectives can stay, but they ride on top of facts, not in place of them.
Before-and-after example
Consider a service page for “Drain Cleaning in Tempe.”
Before (traditional SEO orientation):
Quality Drain Cleaning Service in Tempe
At Smith Plumbing, we understand how frustrating a clogged drain can be. That’s why we’ve built our reputation on providing fast, reliable drain cleaning services to homeowners and businesses across Tempe and the surrounding East Valley.
Our team of experienced plumbers uses state-of-the-art equipment to clear even the toughest clogs. Whether it’s a slow-draining sink or a completely blocked sewer line, we have the expertise and tools to get the job done right the first time.
Why Choose Smith Plumbing?
- Decades of combined experience
- Family-owned and operated
- Fully licensed and insured
- Upfront, honest pricing
- Available for emergency service
Don’t let a clogged drain disrupt your day. Contact us today for fast, reliable drain cleaning service in Tempe.
Word count: ~140. Concrete facts: 0. Question-shaped H2s: 0. Retrievable passages: arguably 0.
After (retrievable orientation):
Drain Cleaning in Tempe, Arizona
Drain cleaning service across Tempe and the East Valley, typically same-day for service requests received before noon. We handle sink, tub, and shower clogs (usually under 60 minutes on site), main-line and sewer-line clogs (usually 1–3 hours with a camera inspection), and root intrusions in older Tempe properties (case-by-case, but we have the equipment for it). Flat-fee pricing — no diagnostic fees, no surprise add-ons.
What kinds of drain clogs do you handle?
We work on every common residential drain — kitchen sinks, bathroom sinks, tubs and showers, washing machine drains, floor drains, main sewer lines. The most common Tempe-specific issues we see are root intrusions in homes built before 1980 (where original clay or cast-iron lines have aged out) and grease buildup in homes with high cooking volume.
How quickly can you respond to a clogged drain?
Standard service requests received before noon are typically handled same-day. Emergency calls (full sewer backup, overflowing fixture) are usually on-site within 2 hours during business hours and within 4 hours overnight. We don’t charge an after-hours premium for true emergencies.
How much does drain cleaning cost in Tempe?
Most residential drain cleaning is flat-fee in the $150–$400 range, depending on access and severity. Sink and tub clogs are at the low end; main-line clogs requiring a camera inspection are at the high end. We give a firm quote before starting work — no diagnostic fees, no hourly billing.
Do you guarantee your drain cleaning work?
Yes. We warranty most drain-clearing work for 30 days against the same clog returning. Root-intrusion clearings are warrantied for 14 days because of how quickly roots regrow in older lines. If the same clog comes back within the warranty period, we re-clear it at no charge.
Process: what happens when you call
- Phone or text us with your address and a description of the issue. We give a same-day arrival window in most cases.
- On-site, we diagnose and quote — no charge for the diagnostic.
- If you approve the quote, we clear the clog and run a quick verification.
- We invoice on-site, accept all standard payment methods.
Word count: ~440. Concrete facts: dozens. Question-shaped H2s: 4. Retrievable passages: 5–6 strong ones.
The second version reads as slightly more clinical to a human — fewer rhetorical flourishes, more numbers. That’s correct for the use case. AI chatbots cite passages that read this way; humans browsing the page get specific information they can act on. Both audiences win.
The “would I retrieve this passage” test
For any paragraph on a service page, ask: if a retrieval system extracted this paragraph alone and presented it as an answer to a buyer prompt, would it actually answer something?
If yes: it’s a retrieval target. Keep and refine.
If no (because the paragraph requires context from elsewhere on the page, or is purely brand sentiment with no concrete content): rewrite or cut.
Running this test across an existing service page surfaces the rewrite list quickly. Most pages we audit have 60–80% non-retrievable content and 20–40% that could be retrievable with minor revision. The fastest gains come from rewriting the highest-traffic service pages first, in priority order by which services drive the most revenue.
A note on length
The instinct after reading this is often to make pages longer — add the FAQ section, add the process steps, add the warranty details. That’s correct up to a point. Past 1,500 words on a single service page, retrieval starts working against you: the page contains too many candidate passages competing for the same prompts, and individual paragraphs get diluted.
The cleaner pattern is multiple shorter focused pages — one per service or service-by-city combination — rather than one long master page covering everything. That’s a different post entirely, but worth flagging here: if your single service page is 3,000+ words, the right move is probably to split it, not lengthen it.