How to write and diagnose title tags and snippets

A title is not a bag for every keyword variant. It is a concise, page-specific label. A meta description is not guaranteed advertising copy. It is one possible source for a search snippet, alongside the visible content of the page.

That distinction changes the work. First make the page's purpose unambiguous. Then write source material that represents it accurately. If the result appears differently, compare what Google generated with the page and the query before rewriting the tag again.

Know which surface you are looking at

<title>

The document title in the HTML. It is an important source for the search result, browser tab, and other interfaces.

Title link

The clickable heading Google generates for a result. It can draw from the title element, main visual title, headings, prominent text, anchor text, and other sources.

Meta description

A page-specific summary in the HTML head. It can be used when it describes the page better than the visible passage selected for the query.

Snippet

The query-dependent summary shown with a result, usually generated from page content and sometimes from the meta description.

These definitions come directly from Google's documentation on title links and snippets. They also explain why a result that does not repeat the supplied tags verbatim is not automatically an error.

Write one sentence about the page before writing the title

Complete this sentence in plain language: “This page helps [reader] reach [specific outcome] with [material distinction].” The title usually needs the outcome and the distinction. It rarely needs the whole sentence.

Include an audience, location, format, product attribute, or year only when it changes the answer. Keep the page-specific information ahead of repeated brand material. Use ordinary grammar. If the title becomes a sequence of near-synonyms separated by pipes, the page's purpose has probably been replaced by a keyword export.

There is no universal character count that makes a title compliant. Google's title-link guidance says title links are truncated as needed to fit the device. Brevity protects the useful distinction, but a counter cannot decide which words carry it.

Worked example: from vague label to useful source material

Imagine a fictional lender has built a calculator for estimating monthly payments on a construction loan. The current page uses this source material:

The three labels are consistent only in being vague. A reader cannot tell which calculation the page performs, and the prominent heading gives Google's title-link system little better source material.

The revision names the tool, states the inputs and output, and aligns the main visible heading with the document title. It does not add unsupported claims about rates, approval, or accuracy. If the calculator uses different assumptions, the copy must reflect those actual assumptions instead.

example.test › construction-loan-calculator Construction loan payment calculator | Example Lending

Estimate interest-only construction payments from the loan amount, rate, and build term.

This preview is a writing check, not a promise. Google may generate a different title link or select a page passage that better answers a particular query.

Give the snippet useful passages to choose from

Write a description that accurately summarizes the whole page and contains the distinction a qualified reader needs before clicking. Then inspect the visible page for concise passages that answer the likely questions. Google says snippets are primarily generated from page content and may vary by search, so the page itself cannot delegate clarity to a hidden tag.

There is no fixed meta-description length that guarantees a complete snippet. Google truncates snippets as needed for the device and can choose a different passage for each query. Put the consequential distinction early because it helps the reader, not because a character counter predicts the final display.

For a product page, useful description material may include the product type, meaningful specifications, availability, or price if those facts are current on the page. The price and review stars that can appear beside a product result come from its structured data, which has to match the visible page; schema markup examples shows valid markup that still gets those facts wrong. For a guide, state the question answered and the scope. Avoid generic endings such as “learn more” when the preceding sentence still does not say what will be learned.

Diagnose the generated result before changing it

Measure the page and the queries the edit was meant to affect

Before publishing, record the old title, description, prominent heading, change date, intended queries, and the reason for the change. After recrawling, compare page and query data rather than only the site's average click-through rate. A page can gain impressions for a new query and lower its average while becoming more useful.

If the generated result keeps exposing that the page lacks a distinct subject, stop iterating on tags. Return to the broader on-page SEO audit and URL decision. Titles can represent a distinction, but they cannot create one the page does not contain.