How to write a meta description Google might actually use

Learning how to write a meta description starts with accepting that Google may not use it. Its documentation says snippets come primarily from page content, and that the description tag gets used only when it describes the page better. So write the description as one specific claim about this one page, keep it unique across the site, and spend the rest of the effort on the title element, which Google treats very differently.

Before you start

You need to be able to edit two things per page: the <title> element and the <meta name="description"> tag. On a hosted platform these usually live in a per-page SEO panel rather than in the HTML. If your platform only offers one site-wide description, skip to the last section — the fix there is a platform problem, not a writing problem.

What Google says it does with each one

The two tags are not treated the same way, and most advice blurs them together. Google's snippet documentation, last updated 2026-04-20 and read on 2026-08-23, says: "Snippets are primarily created from the page content itself. However, Google sometimes uses the meta description HTML element if it might give users a more accurate description of the page than content taken directly from the page." The title element gets a stronger statement: "Make sure every page on your site has a title specified in the <title> element."

Both pages also say the same thing about length, and it is the opposite of what most guidance quotes. There is no character limit on either tag. What happens is truncation at display time, "typically to fit the device width" — which means the cutoff is a property of the searcher's screen, not a number you can write down.

The title element is a field you control. The snippet is a field you can only influence.

How to write a meta description that survives

Write one sentence that could only describe this page. That is the whole test. If the sentence would still be true after swapping in a different page of yours, it is boilerplate, and Google's documentation names boilerplate as the failure case: "Identical or similar descriptions on every page of a site aren't helpful."

Three habits do most of the work, and the second one is the one people skip.

1. Lead with the specific thing on the page — the product, the number, the decision the reader came to make. Not the category it belongs to.
2. Include the facts that are scattered through the page. Google's own example packs author, illustrator, price and page count into one description, because a snippet that answers before the click is worth more than one that teases.
3. Keep it unique per page. If you cannot write one for every page, the documentation's own advice is to prioritise the home page and the pages that already get traffic.

<!-- Google's example from its snippet documentation -->
<meta name="description" content="Written by A.N. Author,
  Illustrated by V. Gogh, Price: $17.99, Length: 784 pages">

Notice what that example is not. It is not a sentence, it has no adjectives, and it would be terrible advertising copy. It is a set of facts that a person deciding between ten results can read in one glance, which is the actual job.

The deliverable: a six-row check for any page

Run this before publishing. Every row maps to a line in Google's documentation rather than to a convention, so a failing row is a real problem and not a preference.

Two rows deserve a note. "No repetition" is aimed at the pattern Google names directly — "Foobar, foo bar, foobars, foo bars" — which it says "can make your results look spammy to Google and to users". And "no boilerplate" is aimed at titles that are one template with a variable slot, the example being a band-page title reading "Band Name - See videos, lyrics, posters, albums, reviews and concerts" for every band.

What large sites actually ship

We measured this on a panel of large homepages rather than guessing at it. Across 27 readable homepages, the median description ran 130 characters and four sites shipped none at all. On the title side, titles ranged from 8 to 120 characters with a median of 40, and none of the 22 sites with an h1 said the same thing in both places.

The second number is the useful one for writing. If title and h1 agreeing were important, the sites with the most SEO staffing in the sample would agree. They do not, and that is consistent with the two elements having different jobs: the title is written for a person scanning a result list, the h1 for a person who has already arrived.

Where this goes wrong

Three patterns, each of which produces a page that looks optimised and reads as generic.

• Writing to a character count. There is no limit in the documentation, and writing to 155 characters makes you pad short descriptions and cut useful facts out of long ones.
• Treating a rewritten snippet as an error. Google rewrites when it thinks the page answers the search better than your tag does. That is the system working, not a penalty.
• Generating descriptions from the first 150 characters of the body. That reliably produces navigation text, a cookie notice, or the first half of an introduction.

What this chapter cannot promise

It cannot make Google show your description. Nothing can, and any advice that implies otherwise is describing a control that does not exist. You can force the opposite — nosnippet removes the snippet entirely, and max-snippet caps its length — but there is no tag that says "use mine".

We also cannot tell you how often your descriptions get used verbatim. Search Console does not report which snippet was shown for which impression, so the only measurement available is sampling searches by hand. That is a real limit on this chapter: everything above improves the odds and none of it closes the loop. What the effort does buy reliably is a clearer title, which is the part you control outright, and a page whose value is stated somewhere machine-readable. If the wider question is why the page is not ranking in the first place, the description is rarely the cause — start with the diagnosis path instead.

Common questions

How long should a meta description be?

There is no limit. Google truncates at display time to fit the device, so aim for the description to make sense when cut in half rather than for a specific count. Across the 27 homepages we measured, the median was 130 characters, which is what convention has produced rather than what any rule requires.

Does the meta description affect rankings?

Google's documentation presents it as a snippet source, not a ranking input. It affects whether someone clicks a result they can already see, which is a different mechanism with a different payoff.

Why does Google keep rewriting my description?

Because it decided the page content answers the search better. The lever is to make the description more specific to the page, not more keyword-heavy. If the rewrite is pulling from a part of the page you would rather it did not, data-nosnippet excludes that section.

Should the title and the h1 be the same?

They do not need to be. In our panel, none of the 22 homepages with an h1 matched their own title, and those sites are not doing badly. Write the title for a result list and the h1 for someone already on the page.