How to Write a Meta Description That Describes the Page

A meta description is a short HTML attribute that summarizes a page. Search engines may use it in a search result, but they can also select other page content when that better matches a query. Your goal is therefore not to force a particular snippet: it is to give readers and search engines a clear, accurate summary of the page.

Start with the reader's decision

Before writing, look at the actual page and identify what someone is trying to accomplish. A tutorial should say what problem it helps solve. A service page should explain the service and relevant conditions. A product category should describe the selection and useful differences between items.

Write one or two natural sentences. Put the key information first, add a detail that distinguishes the page, and check that every claim is supported by the page itself. Include a relevant phrase when it fits naturally, but avoid repeating keywords or turning the description into a list.

The page title and the description have different jobs. A title identifies the page; a description can explain what makes that page useful. Repeating the title word for word wastes that opportunity.

Where the description lives

In HTML the tag appears in the document head:

Your CMS may provide an SEO field that generates this markup. After publishing, inspect the rendered source and verify the actual tag, not just the value in the editor. Escape quotation marks correctly inside the attribute, and investigate conflicting duplicate description tags.

Google explains how its search snippets are generated in its snippet documentation. Its systems can use page content as well as the meta description; a particular tag is not guaranteed to appear unchanged for every query.

How long should it be?

There is no universal character count that guarantees full display on every device and for every query. A rough editorial range such as 120–160 characters can help you draft, but it is not a required technical limit. The available space and the selected snippet vary.

Lead with the information the reader needs. Do not pad a short, clear description with generic phrases just to reach a count. Conversely, don't remove a useful qualifier simply to meet an arbitrary maximum. Read the opening on its own: if the end is truncated, does it still describe the page accurately?

Examples by page type

These examples are illustrative. Replace the details with claims verified on the actual page.

Tutorial: “Choose a bike helmet that fits: check size, ventilation, and the signs that it is time for a replacement.”

The description names the task and the questions covered. Compare that with “Bike helmets, helmet guide, best helmet, bike helmet tips,” which repeats terms without describing what the reader will learn.

Service: “Bike repair and maintenance: explore brake checks, gear adjustments, and how to book an assessment.”

Use it only if those services and booking details are actually available. Do not claim a fixed price when the price depends on an inspection.

Category: “Compare city bike helmets by fit, construction, and ventilation; use the sizing guide to narrow your choices.”

Product: “Model A bike helmet: see specifications, available sizes, and fitting guidance before choosing.”

The category helps someone compare options; the product page identifies a particular item. Check that model, attributes, and availability are accurate. Avoid identical descriptions for every product when the pages have meaningful differences.

Handle descriptions at scale

Inventory important URLs with their page type, existing description, template, and source data. Flag empty, duplicated, and mismatched text. Prioritize pages that are important to your audience and have enough search visibility to assess changes meaningfully.

Templates can be useful for a large catalog if they incorporate reliable distinguishing data. For example: product type + model + verified attribute + next action. Build a fallback for missing fields and sample several categories, including unusual names and absent attributes. A template that outputs awkward repetitions or invents availability needs correction.

AI can produce draft variants, but a human should verify claims against the page and authoritative product data. A plausible sentence about a discount, a specification, or delivery is still incorrect if it is unsupported. For high-impact pages, writing or reviewing descriptions individually is often worthwhile.

Measure carefully

A compelling description may help a person understand a result and choose to click, but a change to the tag does not guarantee higher rankings or click-through rates. Search position, query mix, seasonality, device, and competing results also affect outcomes.

Record the date of the change and compare suitable periods for the same URL and comparable queries. Review impressions, clicks, CTR, and average position together. If the page has few impressions, random variation can dominate the result. If rankings changed at the same time, avoid attributing the whole difference to the description.

A practical preflight checklist

• Does the description summarize this specific page and match its visible content?
• Is the reader's main benefit clear near the beginning?
• Are prices, locations, dates, and availability verifiable?
• Does it complement the title instead of repeating it?
• Is the HTML tag present, valid, and free from conflicting duplicates?
• Have you checked meaningful queries after search engines recrawl the page?
• Are measurement comparisons cautious about position changes and seasonality?

Start with one important page, check its actual content and search intent, and write an accurate summary. Then apply the same process to related page types without treating a character counter as the goal.

Russian source: https://morlix.ru/blog/meta-description-kak-napisat-opisanie-stranitsy

Original article (Russian)