How to Write Meta Descriptions: Length, Examples, and Validation

A meta description is a concise summary supplied in a page’s HTML. It is not a command that forces Google to display that exact text. Write an accurate description, check the published markup, and review the resulting search snippet separately.

Distinguish descriptions from displayed snippets

Google can generate a snippet from page content or use a meta description when it better describes the page. The text can differ for different searches. A mismatch between your description and an observed snippet is therefore not, by itself, a failed implementation. Google’s snippet guidance recommends useful, page-specific descriptions.

Keep title links separate from snippets in your checks. Google’s title-link documentation explains why a displayed title may also differ from the HTML title. Neither field guarantees clicks or a particular ranking.

Put useful information first without fixed length rules

Google does not set a fixed character limit for meta descriptions. Snippets are shortened as needed, including to fit the available display width. Avoid treating a particular desktop or mobile character count as a universal rule.

• State the page’s subject and reader task early.
• Include a concrete distinction, condition, or process that is actually covered.
• Remove repeated modifiers and lists of keywords.
• Make the opening useful even if later text is omitted.

Brevity is an editorial choice. Do not pad a clear description to reach a target or remove essential meaning to fit an arbitrary number. Write naturally for the page’s language rather than applying Japanese full-width character guidance to English.

Write from page content and reader intent

Before drafting, identify what the page genuinely provides. A tutorial can name the task and scope; a service page can identify eligible customers and the consultation process; a product page can describe relevant specifications. Do not add free downloads, completion times, or outcome claims that the page cannot support.

Concrete language is more useful than a generic promise to explain everything. Numbers help only when they accurately describe the content. Matching a search term does not guarantee bold display or higher CTR. Use the SEO article production workflow to check the underlying content before summarizing it.

Compare article, service, and product examples

These are fictional examples for demonstrating editing decisions, not offers of products or assets. Adapt the final wording to the actual page.

The improved version still needs evidence in the page. A worksheet shown in an article is not automatically a downloadable asset. Make descriptions distinct enough to explain each page rather than repeating the same copy across the site.

Validate HTML and CMS output

A simple implementation looks like <meta name="description" content="Review backup storage and restore checks for a small team.">. It belongs in the HTML head. A CMS may generate it from a dedicated field, so check that field’s output instead of pasting a tag into the article body.

1. Save the CMS value and inspect the published head.
2. Check for duplicate description tags.
3. Confirm quotation marks and special characters are output correctly.
4. Compare the description with the page’s real scope and conditions.

A missing description alone does not establish an indexing failure or penalty. Start with important pages where a useful summary adds value. The HTML for SEO guide covers the wider markup checks.

Review snippets and CTR with comparable data

A search preview is a writing aid, not a promise of the live snippet. Record the query, date, device, and text you observed. For performance comparisons, keep the page, country, device, search type, and period length consistent.

CTR is clicks divided by impressions. In a fictional example, 8 clicks from 200 impressions is 4%. Use Search Console’s metric definitions and report counts alongside rates. Query reporting limitations mean not every query is visible. A change in CTR cannot establish that editing the description caused it.