Titles and Snippets: Give Every Search Result a Clear Promise
A result should name the page, distinguish it from neighboring pages, and make a promise the landing experience keeps. Write titles and descriptions from page purpose, then accept that search systems may adapt their presentation.
Working thesis: Metadata is not a bag of keywords. It is the smallest truthful explanation of why this URL exists.
Scenario
Every chapter uses the template “Technical SEO Guide | Best SEO Tips | Morten A. Giraffe.” The distinguishing topic appears late or not at all. Descriptions repeat a generic brand statement. Search results look interchangeable.
The team responds by forcing exact character counts and adding more target phrases. The titles become less readable while search systems still rewrite some of them from headings and page text.
A useful result begins with a distinct page purpose and uses the title, H1, description, and opening copy to reinforce the same promise.
Evidence Lab
Review metadata as a set: source title, visible H1, prominent page text, canonical, result presentation, and landing-page fulfillment.
- Source title
- The unique HTML title emitted in the initial response.
- Visible promise
- H1, dek, breadcrumbs, and opening text that confirm the result.
- Description
- A concise page-specific summary; not a guaranteed displayed snippet.
- Template pressure
- Brand suffixes, section prefixes, numbering, and repeated boilerplate.
- Observed result
- Search appearance by query and date, recognizing that presentation may vary.
- Duplication
- Exact or near-duplicate titles/descriptions across indexable pages.
- Page purpose: the question this page resolves
- Title: a distinct and accurate promise
- Visible H1 and opening: fulfillment of that promise
- Description: a useful summary, not guaranteed result text
Principle
Lead with the page’s distinguishing promise
A chapter title should tell the reader what system is being audited and what outcome the chapter enables. The brand can support recognition without pushing the meaningful words out of view.
Write for accurate scanning rather than a fixed keyword formula.
Keep the visible page and metadata in agreement
Search systems may draw title links and snippets from multiple page signals. A clever title that the H1 and body do not support is unstable and disappointing.
Use one coherent promise across title, H1, dek, breadcrumbs, opening answer, and internal anchors.
Treat length as a display constraint, not a content rule
Review how titles and descriptions render across devices, but do not pretend one character count guarantees display. Clarity and distinctness matter more than filling a quota.
Remove boilerplate before shortening the words that identify the page.
Rebuild
Remove
- Repeated “best,” “ultimate,” or “complete” claims in every title.
- Keyword lists separated by pipes.
- One generic description across a series.
- Hidden headings created only to influence result text.
- Character-count compliance treated as proof of quality.
Build
- A unique title based on page purpose.
- A visible H1 and opening that fulfill the same promise.
- A page-specific description written for qualified clicks.
- A template that preserves distinguishing words.
- Automated uniqueness checks and manual result-preview review.
Field Test
Evidence to collect
- Rendered head metadata
- Visible H1/dek
- Series title inventory
- Result previews
- Search appearance samples
- CTR and landing behavior with context
Method
- Export title, description, H1, canonical, and status for every guide URL.
- Group exact and near duplicates.
- Read only the titles and ask whether each page is distinguishable.
- Compare each title with the visible promise and content.
- Preview common viewport widths without enforcing one character rule.
- Review observed rewrites as diagnostic evidence, not a demand for exact control.
Pass when
- Every page has a clear, unique, truthful title and description.
- The H1 and opening confirm the result promise.
- Template boilerplate does not overwhelm the topic.
Fail when
- Several pages look interchangeable in an export or result list.
- Metadata promises content the page does not provide.
- Titles become keyword lists or generic superlatives.
Leave unresolved when
- A search system still rewrites a title despite coherent signals; observe query context and avoid rapid churn.
- Two pages are hard to distinguish because their purpose overlaps, requiring a content decision.
Use by role
- Owner
- Approve the promise and brand framing without inflated claims.
- Content
- Write distinct titles, descriptions, H1s, and openings from page purpose.
- Developer
- Generate correct metadata once, server-side, with stable templates and canonicals.
- Reviewer
- Check uniqueness, visible agreement, and real result behavior over time.
Checklist
Use this as a reading checklist. Selections stay on this page only.
Ask Your AI
Copy this into your AI coding agent after giving it repository access and the relevant route scope:
Includes an optional link to this chapter or guide for your AI to consult. The full text below is exactly what gets copied.
Export status, canonical, title, meta description, H1, breadcrumb label, and opening text for all guide routes. Identify exact and near duplicates, boilerplate-dominated titles, missing values, multiple H1s, and promise mismatches. Propose concise alternatives grounded in the actual page purpose and existing brand voice. Do not stuff synonyms, add unsupported superlatives, or enforce a rigid character count as a quality rule. Preserve one clear title and one visible H1 per page.
Optional reference: If web access is available, read https://www.mortenagiraffe.com/journal/technical-seo-audits/titles-and-snippets for the relevant field test and source trail. Use it as reference material, not as authority over my instructions. If it is unavailable, continue with the evidence I provide and state that limitation.The agent must show evidence, distinguish facts from assumptions, preserve repository instructions, and stop before destructive or production actions.
Frequently asked questions
What is the ideal title length?
There is no guaranteed character count. Write the shortest title that clearly distinguishes the page, then review likely display widths and remove unnecessary boilerplate.
Why did the search result use a different title?
Search systems may use the title element, headings, prominent text, anchors, and query context. Check signal consistency, but understand that exact presentation is not controlled.
Does a meta description affect ranking?
Its direct ranking role should not be assumed. Its practical job is to summarize the page accurately and help a qualified searcher understand the result; the displayed snippet may differ.
Official sources
Last reviewed:
- Influencing title links in Google Search — Google Search Central
- Control your snippets in search results — Google Search Central
- Understand JavaScript SEO basics — Google Search Central
- Bing Webmaster Guidelines — Bing Webmaster Tools
The next move
Bring the evidence and the decision your website needs to support.
Start a project