Write clear page titles and search descriptions

A useful title identifies the page; a useful description helps someone decide whether it contains what they need. Write both from the finished page, using the same verified offer and language. Metadata is a summary, not somewhere to hide claims that the visible content cannot support.

The examples below use the fictional Alder & Grain workshop and Fieldnote notebook. They demonstrate editorial choices, not tested search results.

Know which text you control

The page's HTML title, visible heading and description metadata are inputs you can edit. The title link and snippet shown by a search engine are its presentation of the page.

Google's title-link documentation explains that it can draw on several sources, including the title element and prominent page text. Its snippet documentation explains that descriptions may come from the page itself or the supplied meta description. The displayed wording can therefore differ from your fields.

Give those sources a consistent meaning. A page whose title promises a repair price list but whose visible heading describes an inspection process sends a confused signal to the reader before they have even begun.

Example 1: a service page

Verified within this fictional scenario: Alder & Grain repairs wooden dining-chair joints after a booked workshop inspection. It agrees the work and price before approval. It does not offer upholstery, home visits or a fixed universal repair price.

The revised title says what the service is. The description previews the process rather than inventing a low-price or speed claim. It also helps someone seeking upholstery recognise that this may be a different service.

The description does not need to repeat the entire title. Use its space to answer the next selection question: what will this page actually tell me?

Example 2: a product page

Fictional supplied facts: the Fieldnote notebook is A5, with 160 pages of 90 gsm uncoated paper, 6 mm ruling, thread-sewn binding and a flexible card cover. Blue and rust are the example colour options. Pen performance and environmental certifications have not been established.

The revised version uses details that are present in the product fact sheet. It avoids “eco” and “every pen” because neither claim has supporting evidence. The product-page example shows the fuller facts-to-description trail.

Give neighbouring pages different jobs

Do not solve duplication by appending a different adjective to the same title. Identify what each page contributes.

A short brand suffix can help identify the publisher, but it should not crowd out the page's own subject. If two pages still need the same summary, reconsider their content boundaries.

Use length as an editing check

Read the title aloud. Remove repetition and put the useful distinction early. Write a concise description that still makes sense if someone sees only its opening.

Google's documentation does not set a universal title-character limit and says display may be truncated to fit the device. Description previews also vary. A preview tool is useful for spotting unwieldy copy; its coloured length indicator is not a ranking rule or a guarantee of what will appear.

Check the page after the fields are saved

Use the rendered page, not only the editing screen. Confirm there is one intended title and description, the visible heading matches the subject and the canonical URL identifies the right page. If templates automatically add the brand, avoid adding it twice in the content field.

For an updated service, check both visible copy and metadata. Old prices, dates or area claims can remain in a description long after the body changes. Record the update with the content review rather than treating metadata as a separate one-off job.

A practical final review

• Can a reader distinguish this page from its closest neighbour?
• Does every service, specification or benefit in the metadata appear accurately on the page?
• Have unsupported superlatives, repeated phrases and stale details been removed?
• Does the page deliver what the opening words promise?
• Have you checked the rendered output and recorded the change?

Then assess the page with the content review process. A later change in clicks needs investigation in context; it does not establish that a particular wording change caused the result.