AI citations for service pages: first-screen answer

AI Overviews and other answer engines cite a service page when they can pull a clear statement of the business, the service, the area, and the offer from the first screen. If that statement lives below a hero carousel, a wall of stock photos, or a company history, the page is easy to skip. Google’s AI features draw from the same Search index as classic results, and a page is only eligible when it is indexed and allowed to show a snippet, with important copy in actual text rather than images alone.[1] For AI citations for service pages, put those four facts in the first 40 to 80 words, then support them with a unique H1, matching structured data, and FAQs that already appear on the page.

Why the first screen decides whether you get cited

People who trigger AI answers often type a question, not a brand. In Pew Research Center’s March 2025 browsing study, 60% of Google searches that began with words such as “who,” “what,” “when,” or “why” produced an AI-generated summary. About 18% of all Google searches in that dataset produced one, and 58% of the adults in the panel saw at least one AI summary during the month.[2] The typical summary was 67 words.[2] A box that short cannot quote a 900-word origin story. It quotes a sentence that already answers the query.

Google has been explicit about how those boxes are built. AI Overviews and AI Mode retrieve pages from the Search index, then review the specific information on those pages to ground a response and show supporting links. Google calls that retrieval-augmented generation, or grounding.[3] There is no separate AI index and no extra technical ritual. The page must be crawlable, indexable, and eligible to appear in Search with a snippet.[1][3] Existing SEO still applies: allow crawling, keep important copy in text, match structured data to the visible page, and keep Google Business Profile details current.[1][3]

Microsoft’s Bing Webmaster Guidelines say the same thing in plainer language for Copilot and other grounded answers. Content that is selected for citations should fully satisfy the query, stand on its own, and be easy to understand without outside context. Bing tells site owners to place essential information near the top of the URL and to avoid long introductions before the main topic. Early clarity, in Bing’s words, improves grounding visibility and reliability.[4]

That is the skip. A service page that opens with “Welcome. We are passionate about excellence” has not answered who you are, what you sell, where you work, or what a customer can buy. The retrieval step can still find the URL. The grounding step has nothing clean to quote. Our search visibility work starts with that first-screen test before we talk about anything else.

What the first 40 to 80 words should say

Write the opening as if a stranger asked, out loud, “Who does this, in my area, and on what terms?” The first screen should name four things:

1. The business name.
2. The service on this page (not a laundry list of every service you have ever offered).
3. The service area (city, county, region, or “nationwide,” if that is true).
4. The offer (what someone can book, buy, or request, plus one real differentiator you can stand behind).

Keep it in plain sentences. Forty to 80 words is enough. You are not writing a slogan. You are writing the sentence an answer engine can lift.

Here is a buried first screen, the kind we still see on otherwise decent sites:

> Welcome to Lakeside Comfort. Quality you can feel. Scroll to explore our story, our values, and why homeowners trust us.

The H1 is “Welcome.” The hero is a full-bleed photo. The real service, “furnace repair in Duluth, MN,” appears after three icon cards and a 400-word founder biography. A person who already knows the brand might wait. An AI summary will not.

Here is the same page, rewritten for the first screen:

> Lakeside Comfort provides same-day furnace repair and seasonal HVAC maintenance in Duluth and St. Louis County, Minnesota. Licensed technicians diagnose no-heat calls, replace failed parts, and leave a written summary of what they found. Book online or call for a same-day window on weekdays.

That block is 62 words. It names the firm, the service, the area, and the offer. The rest of the page can still tell the story. The difference is order. Bing’s guidance is to surface key facts early, not to delete depth.[4] Google’s guidance is to organize pages with headings people can follow, and to keep the important information in text.[3][5]

A useful test: hide the images and the navigation. Read only the first paragraph and the H1. If a new customer still cannot tell what you sell and where, the first screen is not done.

Give the page a unique H1 that matches the question

Google uses heading elements, along with the `<title>` tag and other prominent text, when it builds the title link in Search.[6] It also asks whether the main heading is a descriptive summary of the content, and whether it avoids exaggeration.[5] web.dev’s 2018 heading guidance still holds: use `h1` through `h6` to outline the page, keep a single primary headline, and do not skip levels just to match a designer’s font size.[7]

For a service page, the H1 should sound like the query a customer would type or speak:

• Weak: “Welcome,” “Our Services,” “Residential,” “What We Do.”
• Stronger: “Emergency drain cleaning in Raleigh, NC,” “Bookkeeping for dental practices in Charlotte,” “Commercial roof coating in Phoenix.”

Make the H1 unique to that URL. Google’s title-link documentation warns against repeated or boilerplate titles that make two pages indistinguishable.[6] The same problem shows up in H1s. If every service URL says “Premium solutions from [Brand],” neither a person nor a retrieval system can tell the HVAC page from the plumbing page.

Match the H1 to the first paragraph. If the heading promises emergency drain cleaning in Raleigh, the opening copy should say that you do emergency drain cleaning in Raleigh, not “full-service home care across the Triangle.” Query fan-out (Google’s term for the extra related searches an AI feature may run) can still pull supporting details from later sections. It cannot invent a service area you never stated.[3]

Question-shaped searches are the ones most likely to grow an AI summary, which is why the H1 should answer the question instead of repeating a brand line.[2] You do not need a question mark in the heading. You need the nouns the question would have used.

Stop hiding the offer in a hero

Hero-only layouts fail this test in a predictable way. The visible “message” is a background image, a five-word headline, and a button that says “Learn more.” The real service list, pricing model, cities, and hours sit two folds down, or they exist only inside the image.

Google’s AI-features documentation says to make sure important content is available in textual form, and to support that text with images and video when they help.[1] Google’s page-experience questions include a direct one: is the page designed so visitors can easily distinguish the main content from everything else?[8] A full-screen slider that auto-rotates three stock photos does the opposite. It competes with the answer.

Two concrete fixes:

• Put the 40-to-80-word answer in HTML text immediately under the H1, in the first viewport, not only in alt text or a caption.
• Treat photos as evidence (a truck, a job site, a finished install), not as the only place the service is named.

Google’s snippet documentation adds a related point for in-result deep links: make the content immediately visible to a person, not hidden behind an expandable panel or a tabbed interface.[9] If your “real” service description lives in an accordion titled “More,” you have buried the offer twice, once visually and once in the DOM.

Design can stay. It should not delay the sentence that should have been first.

Mark up the facts that are already on the page

Structured data does not replace the first-screen rewrite. Google’s own generative-AI guide is blunt about what you can ignore: you do not need special machine-readable files, AI-only markup, or a new writing dialect just for AI features.[3] What Google does ask is that any structured data you add matches the visible text.[1][10] Bing says the same: markup may support clearer grounding, but it does not guarantee a citation, and it must accurately reflect what people see.[4]

For a local or regional service page, three schema.org types earn their keep because they describe the page, not because they are a trick:

LocalBusiness. schema.org defines a LocalBusiness as a particular physical business or branch, with properties for name, address, telephone, opening hours, and `areaServed` (the geographic area where a service is provided).[11] Google’s LocalBusiness structured-data documentation is the implementation path for hours, address, geo, and related details in Search and Maps.[12] Claim and update the matching Google Business Profile so the name, address, and phone on the page agree with what Google already stores for the listing.[13] A mismatch is a trust problem, not the whole reason a page fails to get cited. Still, if the page says one city and the Profile says another, you have given two systems two different answers.

Service. schema.org’s Service type is “a service provided by an organization,” with `provider`, `areaServed`, `serviceType`, `description`, and `offers`.[14] Use it on the service URL, not as a dump of every offering on the homepage. The `description` in JSON-LD should be a compressed version of the first-screen paragraph, not a slogan that never appears in the HTML.

FAQPage. schema.org defines a FAQPage as a WebPage that presents one or more frequently asked questions.[15] Add FAQPage JSON-LD only for questions and answers that are actually on the page. Google’s general structured-data rules forbid marking up content that readers cannot see.[10] Do not invent five FAQs in the `<script>` tag and hide them. Do not mark up questions that live only in a PDF.

One more FAQ caveat, because the old advice is now stale: Google deprecated the FAQ rich result and stopped showing it in Search as of 7 May 2026, then removed that documentation in June 2026.[16] FAQPage is still a schema.org type. It is not a Google dropdown ticket, and it is not a substitute for a first-screen answer. Write the questions people actually ask (“Do you serve Cary?”, “What is included in a diagnostic visit?”, “How do we book after hours?”), put the answers in visible HTML, then mark up those pairs.

JSON-LD is the format Google recommends.[10] Validate it. If the markup says you serve three counties and the page copy says “nationwide,” fix the page or the markup. The mismatch is the bug.

Keep the offer honest

A first-screen rewrite that overclaims is worse than a slow one. U.S. truth-in-advertising rules apply to website copy the same way they apply to other ads. Advertising must be truthful and non-deceptive, advertisers must have evidence for the claims, and ads cannot be unfair.[17] The FTC looks at express claims and implied ones, and at whether a claim is material (important to the decision to buy), including claims about performance, features, price, or effectiveness.[17]

On a service page that means:

• Do not write “#1 in the city” unless you can show the ranking and the method.
• Do not write “saves 40%” unless you have the comparison.
• Do not imply a 24-hour crew if the phone rolls to voicemail after 5 p.m.
• If price depends on inspection, say so in the same block as the offer.

Answer engines quote what you wrote. Write the offer as a customer would hear it on the phone.

A rewrite pass you can finish this week

You do not need a new site. You need a pass on the service URLs that already attract commercial questions.

1. Pick one service URL. Choose a page that matches a real query, such as a city-plus-service search, not the homepage.

2. Write the H1 as the query’s answer. One H1. Specific service. Specific area. No “welcome.”

3. Write a 40-to-80-word opening. Business name, service, area, offer, one differentiator you can prove. Place it in HTML under the H1, in the first viewport.

4. Move the biography down. History, awards, and team photos can stay. They should follow the answer, not precede it.

5. Make the main content obvious. Cut autoplay sliders that hide the first paragraph. If a section is the actual offer, it should not sit in a tab labeled “More.”[8][9]

6. Align name, address, and phone with Google Business Profile. Put NAP on the page in text. Update the Profile if the page is right and the listing is stale.[13]

7. Add visible FAQs that a customer would ask. Three to six is enough. Answer in a complete sentence, then add FAQPage JSON-LD for those pairs only.[10][15]

8. Add LocalBusiness and Service JSON-LD that repeats the same facts. `areaServed` and `serviceType` should match the opening paragraph.[11][14]

9. Check that images are not the only copy. If you disable CSS and images, the answer should still be readable.[1]

10. Recrawl when you are done. Google and Bing both need a fresh fetch before the new first screen can be cited.[1][4]

If you manage location pages, repeat the same answer pattern, swap the place name, and keep each URL focused on one service in one area. Google warns against scaled pages whose only purpose is to cover every query variation.[3] Bing asks you to focus each URL on a single topic and to align title, heading, and intent.[4]

You do not need a new file format for large language models, and you do not need to chop the page into tiny chunks. Google says those tactics are unnecessary for its generative features.[3] Keep the depth for the person who clicks through. Change the order: name the firm, the service, the area, and the offer, in text, first.

Practical takeaways

• Put the business name, the service, the service area, and the offer in the first 40 to 80 words of HTML, not in a hero image.
• Write one unique H1 per service URL that matches the question a customer would ask, then make the first paragraph agree with it.
• Keep important facts in text. Images and video can support the answer. They cannot be the only place it exists.
• Add LocalBusiness, Service, and FAQPage JSON-LD only for facts and questions that are visible on the page, and keep NAP aligned with Google Business Profile.
• Do not treat FAQ markup as a Google rich-result tactic. Google stopped showing FAQ rich results in May 2026. Visible Q&A still helps people and other parsers.
• Write claims you can substantiate. Answer engines will quote the first screen you actually published.

How we can help

Have more questions or want to get in touch? Contact our team and we will look at a live service URL with you. If you want a fuller pass on how those pages show up in search and AI answers, start with our search visibility work. We rewrite the first screen so a person, and the systems that quote people, can tell what you do before they scroll.

Citations

1. Google Search Central, "AI features and your website" (2025-12-10)
2. Pew Research Center, "Google users are less likely to click on links when an AI summary appears in the results" (2025-07-22)
3. Google Search Central, "Optimizing your website for generative AI features on Google Search" (2026)
4. Bing Webmaster Tools, "Webmaster Guidelines" (2026)
5. Google Search Central, "Creating helpful, reliable, people-first content" (2025-12-10)
6. Google Search Central, "Influencing your title links in search results" (2025-12-10)
7. web.dev, "Headings and landmarks" (2018-11-18)
8. Google Search Central, "Understanding page experience in Google Search results" (2025-12-10)
9. Google Search Central, "Control your snippets in search results" (2026-04-20)
10. Google Search Central, "General structured data guidelines" (2026-07-10)
11. schema.org, "LocalBusiness" (vocabulary page, retrieved 2026-09-17)
12. Google Search Central, "Local business (LocalBusiness) structured data" (2026-09-08)
13. Google Search Central, "Establish your business details with Google" (2025-12-10)
14. schema.org, "Service" (vocabulary page, retrieved 2026-09-17)
15. schema.org, "FAQPage" (vocabulary page, retrieved 2026-09-17)
16. Google Search Central, "Latest Google Search documentation updates" (FAQ rich result deprecation, 2026-05-08 and 2026-06-12)
17. Federal Trade Commission, "Advertising FAQ's: A Guide for Small Business"