Titles and search summaries
Describe the page a reader will actually find.
Titles and summaries should communicate the page’s real purpose. Write useful alternatives, check their fit to the finished answer and distinguish your authored fields from search-generated output.
Free learning from Semantec SEO.
Make the page’s promise accurate.
The title should let a reader recognize the subject and the useful task before opening the page. Start from the finished answer, not a list of attractive phrases. Name the distinction that makes this page different from its neighbors, and avoid promising a result, tool or service that the page does not provide.
A page title, visible heading and short description can use different wording while describing the same task. A practical heading may explain the decision in a sentence; the title can name the subject more directly. Check them together for contradictions. A reader who follows the search promise should find the promised answer without having to infer that it is somewhere else.
Before drafting alternatives, write a one-sentence task statement and a short list of material inclusions and exclusions. This prevents a title from quietly expanding the scope. If the page teaches a planning method through a fictional example, the description should not imply that it contains measured client results or a working software tool.
Write a descriptive title without padding.
Google’s title link documentation recommends descriptive, concise title text and avoiding repetition. Search titles can be shortened to fit the available display width; a fixed character target is not a guarantee of the final presentation.
Choose the wording a relevant reader needs to distinguish the page. A broad topic alone can be too vague; a stack of synonyms can bury the distinction. Include a condition such as the audience, method or comparison only when the content truly depends on it. A beginner’s explanation and an advanced troubleshooting procedure should not share an indistinguishable generic title.
Keep branding proportionate to recognition needs and the site’s established title pattern. If a title template already appends the organization name, do not manually repeat it in the authored field. Inspect the final HTML because a stored title field and the output generated by a theme or SEO system may differ.
Use the description for a useful summary.
The meta description is an authored summary, not a place to introduce missing claims. State what the page helps the reader do, then add a relevant condition, example or limit. Avoid vague promotional language that could describe any page, and avoid a sequence of search phrases that does not form an informative summary.
Google’s snippet documentation explains that result summaries are commonly drawn from page content and may use a suitable meta description. A search summary can vary with the query. The supplied description should be accurate even when it is not selected verbatim.
Do not use the description to conceal a material limit. If a page offers an illustrative plan, describe the plan. If a service has an eligibility condition, avoid a summary that implies unrestricted availability. A short excerpt may be read without the rest of the page, so preserve the qualification that changes its meaning.
Expect search-generated variation without inventing a cause.
Google automatically constructs title links from sources that can include the title element, prominent page headings and link text. Its displayed title can differ from the authored field. This does not identify a single ranking cause or prove that the whole page is poor.
When a result differs from your intended description, record the query, date, language, device context and observed text. Compare that observation with the public page output. Keep the observed result separate from an explanation you have not tested. A single query sample does not establish that every visitor sees the same title or summary.
Check for a stale page title, a conflicting heading, duplicated brand text or a description left over from an earlier page purpose. These are inspectable defects. A changed result can also reflect the search context; do not keep rewriting an accurate page merely to force one exact phrase into every observed display.
Worked brief: describe the page that actually exists.
This example is fictional editorial work. The page teaches a small agency how to decide if a new topic needs a separate page. It contains a decision method, a worked service-topic example and limits concerning evidence and overlap. It does not offer an automated map builder, client results, prices or a promise about search performance.
| Alternative | Fit to the page | Decision |
|---|---|---|
| Page or Passage? Choosing a Home for a New Topic | Names the decision in plain language and preserves the possibility of using an existing page. | Strong fit when the intended reader understands the page versus passage distinction. |
| Content Page Ownership: A Decision Method for Small Agencies | Names the subject, format and audience that the page actually addresses. | Strong fit for the stated agency audience; slightly more formal wording. |
| A New Page for Every Keyword: Get Better Rankings | Promises a universal rule and search effect that the example does not support. | Reject; the problem is false scope and an unsupported outcome, not just its length. |
| Alternative description | Fit and limit |
|---|---|
| Decide if a new topic needs its own page or belongs in an existing answer. A worked agency example covers scope, evidence and overlap. | Matches the method and example; does not imply an automated service or measured result. |
| Use a page ownership check for new service topics. Compare reader tasks, current content and evidence before assigning another URL. | Emphasizes the practical decision and prerequisite inventory review. Use it if those checks are fully covered on the page. |
| Build a complete automatic topical map and double traffic with our proven agency system. | Reject. The fictional page has no working builder or evidence for the performance and proof claims. |
The preferred pair in this brief is the second title and the first description: the title identifies the intended agency audience while the summary explains the choice and example. The first title is a defensible alternative for an audience that recognizes the terms. Preference here is an editorial decision, not a result of a click-through experiment.
Check the candidate against the whole page.
Read the opening, headings, examples, tables, images and next action before accepting a summary. A page can retain an old title after a rewrite has changed its purpose. A title can also become misleading when the promised example or tool is removed. Reopen metadata review whenever a material content change affects the promise.
Compare neighboring pages as well. Two distinct tasks with the same generic title may be hard to distinguish. Two different titles can also conceal duplicate answers. Resolve the ownership problem rather than trying to make repetitive content look unique through adjectives.
Describe generated illustrations truthfully in their own filenames and alt text, but do not confuse those fields with the page title. An image of an editorial planning desk is not evidence of a real client project. The text describing the page must remain accurate independently of decorative art.
Verify the public output without treating a mockup as a result.
Inspect the public HTML for the title and description being served, including duplicated tags or stale values emitted by another owner. Confirm that the canonical URL and visible page correspond to the intended content. An editor panel showing the right text does not prove a custom template or cache serves it.
A preview of a possible search card can help judge clarity, but it is not an observed search result. Record it as an illustration. If you later sample a real result, preserve its context and avoid claiming universal display. Do not invent click-through gains from a more appealing mockup.
After a meaningful change, allow the search system to reprocess the page before drawing conclusions from an old result. Keep evidence dates so a stale observation is not mistaken for a failed current edit. An authored title or description does not guarantee a particular display, indexing time or performance effect.
Keep a small title and summary decision record.
Record the page task, finished-content version, candidate title, description, rationale, rejected claims, reviewer and public output check. If alternatives were compared through a real test, record the method used and limits separately from editorial preference. A choice made in a review meeting is not a measured visitor result.
Use a review trigger such as a changed page purpose, updated service condition, removed tool, new canonical owner or conflicting public output. Revisit the promise when those inputs change. Do not revise a truthful title just because a tool asks for an arbitrary number of words or repeated mentions.
Continue with the content writing hub, content audit and rewrite decisions or the learning overview. The official sources above explain search output behavior; the candidate exercise is an original teaching example.