How to write page titles and meta descriptions

Write a page title that names the page's actual subject, then a meta description that explains its useful answer. Keep each page distinct, put the important information first and make the visible heading deliver the same promise. Google can choose different title and snippet text, so treat your wording as a clear preference rather than a guaranteed search-result preview.

Give every page one job before writing its title

A title is difficult to write when the page is trying to answer several unrelated questions. Start with the reader's task. A service page helps someone evaluate an offer. A comparison helps them choose between options. A tutorial helps them complete a process. Those jobs need different promises.

Write a sentence in your planning notes: “This page helps this person make this decision or complete this task.” If you cannot finish it without adding several more tasks, narrow the page or revisit your site structure. Our website structure guide explains how to separate the main destinations.

For an illustrative bookkeeping business, a service page might help a shop owner decide whether the company can manage monthly bookkeeping. A guide about preparing records for a bookkeeper serves a different reader task. Giving both pages the same title would hide that distinction.

Separate the title, heading and description

The HTML title identifies the document and can be used for a search result's title link. The H1 is the main visible heading on the page. The meta description is a short summary supplied in the page metadata. They should agree, but they do not have to repeat exactly the same sentence.

Google's title-link documentation explains that its systems can use several sources, including the HTML title and visible headings. Make those sources consistent instead of trying to compensate for a misleading page with more persuasive metadata.

Imagine an illustrative studio publishing a practical theme-selection guide. Its title might be “Choose a WordPress theme for a business website | Example Studio.” The H1 can use the more conversational “How to choose a WordPress theme for your business.” The description can identify the actual comparison criteria: content fit, editing, mobile behavior and maintenance. Each piece contributes something useful.

Draft a title around the useful distinction

Start with the subject and the decision the page supports. Add the qualifier that makes the page meaningfully different, then use a short brand suffix when appropriate. This is an editorial starting point, not a required formula.

• A service page can identify the service and the audience it actually serves.
• A tutorial can identify the task and any essential platform or prerequisite.
• A comparison can name the alternatives and the decision being made.
• A downloadable resource can name the artifact and what the reader can use it for.

For a fictional repair company, “Services | Example Company” says little. “Commercial refrigeration repair in Leeds | Example Company” is more informative if the company really provides that service there. Adding a city the company does not serve would make the title less accurate, even if it sounded more searchable.

Avoid stacking near-identical phrases such as “website design, web design, website designers.” Use the phrase that describes the page, then spend the remaining attention on a real distinction. Do not add “best,” “award-winning” or an outcome unless the page can substantiate it.

Write the description after the page exists

Read the finished page and explain why the intended reader would find it useful. Name the subject, the actual coverage and any meaningful boundary. Leave out benefits that the page never demonstrates.

For a fictional website-launch resource, a vague description would be: “Everything you need for the best website. Contact us today.” A more useful draft is: “Review content, mobile layouts, forms and indexing before your business website launches. Use the checklist to assign owners and record unresolved issues.” That is an original example, not a promised search snippet.

The second version helps someone decide whether the resource fits their task. It also sets a standard for the page: the checklist must genuinely cover those areas. If it has no way to assign owners, remove that promise or improve the resource first.

Google's snippet guidance says snippets are primarily drawn from page content, and a meta description may be used when it provides a better summary. Write a helpful opening and clear sections as well as a good description.

Use length previews as editing aids

There is no universal character count that guarantees a complete title or description in every Google result. Both can be shortened to fit the available display space. A device, query and result presentation can change what is visible.

Put the necessary subject and distinction early. Remove filler before cutting the words that explain what the page is about. Read the result aloud: does it still sound like a human description rather than a list of search phrases?

A plugin's green indicator can help a team apply its own editing convention. It cannot guarantee Google's displayed wording or a ranking. If a preview cuts off a crucial qualification, rewrite the sentence so the qualification appears sooner.

Use a page inventory to prevent duplicates

Collect your important URLs in one worksheet. For each, record the primary reader question, proposed title, description, visible H1 and useful next step. Compare neighboring rows before reviewing them individually.

This catches a problem that isolated editing misses: five service pages can each sound reasonable while all promising the same answer. Make the real differences visible. If you cannot identify a difference, consider whether the pages should be combined rather than forcing new wording onto duplicate content.

Start with your homepage, core services, main resources and existing pages people actually visit. Then expand the inventory. Use the SEO page planning worksheet for a copyable structure and worked example.

Publish the metadata with the page

Use the title and description fields provided by your CMS, SEO extension or build system. Field names vary. Check the rendered page after publishing: the browser's source should contain the intended title and description in the head, rather than only displaying them inside an editor preview.

Also inspect the visible H1, main content, canonical destination and links to the page. A title describing a checklist should not lead to a generic contact form. A well-written description cannot fix a missing page, blocked crawl or accidental noindex instruction.

Before a redesign goes live, include metadata and redirects in the release review. The website launch checklist covers the wider journey from content to forms and discovery.

Review results without chasing every variation

After search engines have had time to revisit a changed page, compare the relevant page and query data in Search Console. Record when you changed the metadata and what else changed at the same time. A small change in clicks is not proof that the title caused it.

Look for useful mismatches. If the queries suggest a different task from the one the page answers, investigate intent and content before rewriting the title again. If Google displays different wording, compare the visible heading and page content with the submitted metadata. Do not assume every rewrite is an error.

Keep a record of the question the page serves. The goal is a result that helps the right reader choose an accurate answer, followed by a page that fulfills it.

Sources and next steps

• Google Search Central: title links.
• Google Search Central: snippets and meta descriptions.
• Use the SEO page planning worksheet to review several related pages together.
• Write a website brief if the audience, offer or purpose is still unclear.

Platform guidance was checked on 27 October 2026. Business names and sample copy in this guide are illustrative. The cover is an AI-generated editorial photograph.

The Blitz Studio team

We design brands, build websites and engineer digital products.

Talk about your next project