usdigitalmarketingindex.com SEO
How should a meta description summarize a page answering several related questions?
Updated November 15, 2026
State the one thing the whole page is about and who it helps, name the two or three questions that matter most, and stop. A page that answers eight related questions has a single subject those questions share, and the description should summarize that subject, not list all eight. Google’s documentation describes a meta description as “a short, relevant summary of what a particular page is about” (Google’s guidance on snippets and meta descriptions). It also explains that the description is a suggestion: snippets are created primarily from page content, and the meta description is used when it gives a more accurate description than text taken from the page.
Selecting the central promise
Find the sentence that covers the page before writing anything.
- List the questions the page answers.
- Write the subject they have in common, as a noun phrase.
- Write who needs the page and at what moment.
- Combine the two into one statement of what the reader will be able to do or decide afterward.
For a page answering questions about heat pump rebates (who qualifies, how much, which equipment, how to apply, when payment arrives, whether rebates stack), the shared subject is getting a rebate for a heat pump, and the reader is a homeowner planning an installation. The central promise is that the page explains eligibility, amounts, and the application process. Stacking and payment timing are covered on the page and do not need a place in the summary.
Summarizing without stacking keywords
The temptation with a multi-question page is to compress every question into a string of phrases. Google’s documentation is direct about the result: descriptions “comprised of long strings of keywords don’t give users a clear idea of the page’s content, and are less likely to be displayed as a snippet”.
Three habits keep the summary readable.
- Write sentences. A description should read as a statement a person would say.
- Choose, do not enumerate. Name the questions that decide whether the reader has the right page.
- Use the reader’s words for the subject once. Repeating it adds nothing.
On length, the same documentation says “There’s no limit on how long a meta description can be”, and that the snippet is truncated as needed. Put the central promise first, so that whatever is cut is the least important part.
This is the work for one page. Reviewing descriptions across a whole site, and leaving alone the ones that already work, is covered in the guide to reviewing a large collection of meta descriptions without rewriting effective ones.
Examples of good prioritization
The comparison below describes two versions of a description for the rebate page by what each contains. The wording itself is left to the writer, and the point is the selection.
| Element | Weaker version | Stronger version |
|---|---|---|
| Opening | Names the topic as a keyword phrase | States what the page helps the homeowner do |
| Questions mentioned | All six, as a comma-separated list | Three: who qualifies, how much, how to apply |
| Specifics | None | The program or region the page covers |
| Reader | Not identified | Homeowners planning an installation |
| Form | Fragments | One or two sentences |
| What is left for the page | Nothing implied | Stacking and payment timing, answered on the page |
The stronger version says less and tells the searcher more, because it lets the searcher judge two things from the results page: whether the page is about their situation, and whether it will tell them what they need.
Prioritize questions by the same rule every time.
- Include the question that defines the audience, such as eligibility.
- Include the question searchers ask in the largest numbers, according to the page’s Search Console queries.
- Include the question that leads to action.
- Leave out questions that are refinements of those three.
Checking for false coverage
A summary of a multi-question page can easily promise more than the page delivers. Check each claim in the description against the page.
| Check | Pass condition |
|---|---|
| Every question named in the description has its own section on the page | Section exists with a full answer |
| Any number, date, or program name in the description appears on the page | Exact match |
| The description names the region or scope the page covers | No wider than the content |
| No question is implied that the page only mentions in passing | Each named topic gets substantive treatment |
| The description is unique to this page | Not shared with sibling pages |
Review the description whenever the page changes. A section removed from the page while its promise stays in the description turns an accurate summary into a misleading one.
Keep expectations realistic about display. Google’s documentation says Google Search “might show different snippets for different searches”, so a searcher who typed one of the eight questions may see the passage that answers it instead of the description. That mechanism is explained in the guide to why Google’s displayed snippet can differ from a page’s meta description.
The test for a finished description: a person who reads only it should be able to say what the page is for and name two things it will tell them, and both should be true.
Add your comment to this answer