Resources · Content for AI Search

Should H1s, Titles and Meta Descriptions Use the Exact Question for AI Search?

H1s, titles and meta descriptions should use the question when a page exists to answer one specific question, such as "How long does a heat pump last?". Match the main wording buyers use, not every variation. For hub pages, product pages and category pages, a clear descriptive title works better than a question. These elements matter for AI search because search results pass the title and a snippet to assistants. Those decide which pages to read before answering, just as people scan results before clicking. The title shows the page is about the question. The description and first paragraph show it answers it. Chasing exact phrasing across many near-identical pages does not help, and Google warns against it.

Why do titles and descriptions matter for AI search?

When an assistant searches the web, it receives a list of results. Each has a title, a URL and a short description or snippet, much like a search results page. It then chooses which pages to open and read. A title that clearly matches the question, and a snippet that shows the page answers it, make selection more likely. Once the page is read, the heading and first paragraph shape which passage is used.

Google's own guidance on titles applies directly. It asks for descriptive, concise title text and warns against keyword stuffing and boilerplate. It uses several sources, including the title element and the main visible heading, to decide the title shown in results. For snippets, Google says it mainly uses page content. It uses the meta description when that describes the page better.

When should you use the exact question?

Page type Title or H1 approach Example
Single-question answer The question, in buyers' wording "How Long Does a Heat Pump Last?"
Guide covering one task Task-based title "How to Bleed a Radiator"
Hub or topic page Topic title, questions as H2s "Heat Pumps: Costs, Lifespan and Installation"
Product page Product name and key attribute "EcoHeat 12kW Air Source Heat Pump"
Category page Category and qualifier "Air Source Heat Pumps for Older Homes"
Comparison "X vs Y" with the decision "Heat Pump vs Gas Boiler: Running Costs Compared"

For question pages, use the most common phrasing as the H1, and answer related phrasings in the body. Do not create separate pages for "how long do heat pumps last", "heat pump lifespan" and "how many years does a heat pump last". Google's guidance on generative AI search warns that creating separate content for every search variation, mainly to manipulate rankings or AI responses, can breach its scaled content abuse policy.

Should page titles and meta descriptions directly answer AI search queries?

The title should signal the answer's topic clearly, and sometimes the answer itself. The meta description should summarise the answer.

  • Titles: keep them descriptive and concise. A title can include the key fact where it fits naturally, such as "Heat Pump Lifespan: 15–20 Years, and What Shortens It". But the main job is to show what the page covers.
  • Meta descriptions: write one or two sentences that answer the question and say what else the page covers. For example: "Most air source heat pumps last 15 to 20 years. This guide explains what affects lifespan, maintenance costs and when replacement makes sense." Google may choose its own snippet, but a clear description is used when it describes the page best, and other search engines often show it.
  • The first paragraph: make it a direct, self-contained answer that still makes sense if quoted on its own, whatever the title says.

Writing the opening answer is covered in how to write direct-answer-first content for AI search.

Should the H1 and title be identical?

They can be the same or slightly different. The title often includes the brand name or a short qualifier, while the H1 is the plain question or topic. What matters is that they agree on what the page is about. Google notes that confusion arises when several headings on a page carry the same visual weight. Make the main heading clearly the most prominent.

How should local and multilingual pages handle titles?

Local service pages answer an implied question: who can do this job here? A title that names the service, the place and one differentiator works better than a question, for example "Emergency Plumber in Leeds, 24/7 Call-outs". Keep question titles for local pages that answer a real question, such as "How Much Does a Boiler Service Cost in Leeds?". Put the price range in the description and the first paragraph.

Pages in other languages should use the phrasing native speakers actually use, not a word-for-word translation of the English title. Questions are phrased differently across languages and regions. A title translated literally may match nobody's wording. Check local search suggestions or ask a native speaker before settling on the title and description, and link language versions with hreflang tags.

What should you avoid?

  • Stuffing variations into titles: "Heat Pump Lifespan, How Long Do Heat Pumps Last, Heat Pump Life Expectancy".
  • Boilerplate titles that differ by one word across hundreds of pages.
  • Clickbait questions the page does not really answer.
  • Question titles on pages that are not answers, such as product pages titled "Looking for the best heat pump?".
  • Meta descriptions that only sell, with no information about the answer.
  • Duplicate titles across pages, which make it harder for crawlers to tell pages apart.
  • Dates in titles that go stale, such as a year that is never updated when the content is.

How do you test changes?

Pick a set of question pages, rewrite titles, H1s and descriptions to match the main buyer wording and summarise the answer, and leave a similar set unchanged. After recrawling, compare AI citations and organic click-through for the two sets over a few weeks. Bing's AI Performance report can show whether the changed pages start being cited in Copilot answers, and the grounding queries the AI used to retrieve them.

What might an illustrative change look like?

Consider an illustrative home energy company whose guide titled "Everything You Need to Know" was rarely cited. Its H1 was "Our Guide", and its meta description was "Read our expert guide". The team retitled it "How Long Does a Heat Pump Last? Lifespan, Maintenance and Replacement". They set the H1 to the question and wrote a meta description that gives the 15-to-20-year range. They also moved a direct answer into the first paragraph. After recrawling, the guide began appearing as a source for lifespan questions in several assistants. Organic click-through also rose, because the result now showed what the page answered.

What do people ask about titles and AI search?

Do AI assistants read meta descriptions?

Many receive titles and snippets from search results before choosing pages. The page's own content matters most once it is read.

Should every H2 be a question?

Question-style H2s work well where each section answers a distinct question. Use plain headings where they read better.

How long should titles be?

Concise enough to be read at a glance. Google gives no fixed limit, but long titles are often shortened in results.

Should we rewrite all existing titles as questions?

No. Rewrite titles for pages that answer a single question, and keep descriptive titles for other page types.

Published by The Kovmere Team · updated Sep 29, 2026 · More resources