What is a meta description, and how long should it be?

What a meta description is

A meta description is a tag in the head of a page:

<meta name="description" content="Compare plans, see what each includes and start a 14-day trial. Prices in EUR, billed monthly or yearly.">

Visitors never see it on the page. It is written for the search result: Google may display it as the snippet below the blue link, and social apps sometimes fall back to it when a page has no Open Graph description.

Does it affect ranking?

Not directly. Google has said for a long time that the meta description is not a ranking signal. Its value is in the click: a clear description that matches what the searcher wants makes the result more likely to be chosen than a vague one.

How long should it be?

Google does not set a character limit. It truncates snippets to fit the screen width, which on desktop usually lands somewhere around 150 to 160 characters and is shorter on mobile. A practical target is 120 to 160 characters, with the most important information in the first half, so a cut-off still makes sense.

Why Google rewrites it

Google chooses the snippet per query. If another passage on the page answers the searcher's words better, it shows that instead of your description. Rewrites are more likely when a description is missing, generic, duplicated across many pages, or stuffed with keywords. You cannot force Google to use your text, but a specific, accurate description is used far more often than a generic one.

How to write a good one

• Describe what the page gives the visitor, in plain words, not a slogan.
• Make every page's description unique. Duplicates across a site are usually a template default nobody replaced.
• Include the facts that decide the click: price, location, format, who it is for.
• Match the content. A description that promises something the page does not deliver costs trust and the next click.
• Skip the brand name unless it adds information. The site name already appears in the result.

Where builders and frameworks go wrong

Single-page apps built with React, Vite or AI app builders often set the description in JavaScript after the page loads, or keep one description for the whole app. Google can render JavaScript, but social apps and many other crawlers read only the served HTML, and a single description shared by every route helps none of them. Check the HTML your server returns for each important URL:

curl -s https://example.com/pricing | grep -i 'name="description"'

What a scan can and cannot tell you

WebAuditOS checks that every crawled page has a non-empty meta description in its served HTML, and flags descriptions shorter than 50 or longer than 170 characters. It reads the HTML your server sends, so descriptions added only by JavaScript count as missing.

It cannot judge whether the wording is accurate, unique in meaning or persuasive, and it cannot see which snippet Google actually shows for a given query.

A pass on length means the description fits. It does not mean it is good. Read your top pages' descriptions as a searcher would.

Short answers

Is a meta description required? No, but without one Google picks text from the page, which is often less useful.

Does Google always show my description? No. It rewrites when another passage fits the query better.

Should every page have a unique one? Yes, at least every page you want found in search.

Do keywords in the description matter? Matching words can be highlighted in bold in the result. They do not affect ranking.