Meta descriptions: content, length and search snippets

Describe the topic, offering or answer specifically. If you mention a price, include the conditions that materially affect it. Do not promise a free analysis, immediate delivery or an outcome the page does not offer.

Illustrative example for a guide: “Plan content, features and responsibilities before building a new business website.” The description states what readers will get, provided the guide actually covers those areas. “The best website at the lowest price”, by contrast, is an unsupported claim.

Give each important page a description of its own content. A service page needs to summarise the offering and relevant conditions. A guide needs to describe the question or task it helps readers with. Using the same text on several different pages makes their differences harder to understand. Google’s guidance on search snippets recommends descriptions specific to each page.

How do you write a description that distinguishes the page?

Summarise the page’s particular task and the information that helps readers decide whether it is the right destination. Write the description once the page’s content and offering are settled:

1. Identify the main task. Should readers understand a term, follow a procedure or assess a service?
2. Choose information that distinguishes this page. A guide can state what its procedure teaches; a service page can state the deliverables and relevant conditions.
3. Compare every promise with the main content. Remove any outcome, scope or cost that cannot be substantiated there.
4. Read the description alongside the title. They should concern the same page, but the description can explain a benefit or scope that the title does not cover.

These are wording examples, not two promised deliverables or a complete SOVRA offering. An attractive description that promises more than its destination contains does not help visitors choose correctly.

Write as concisely as the content allows without losing what matters. Google does not specify a fixed character limit for meta descriptions; the snippet may be shortened according to the available space and context. Read the guidance on search snippets.

A character range in an editing tool can be a practical diagnostic aid, not a universal ranking rule.

Place the topic and the most important distinction early. If the description is shortened, its first part should still help readers understand the page. Do not pad a clear description with repeated keywords because a tool requests more characters. Equally, do not remove a decisive condition to obtain a green indicator.

A preview can reveal awkward wording or important information placed too late. It is an estimate, however, not a guarantee of Google’s actual search snippet. Assess the content first and use the preview as an additional check.

The title names the page, the H1 identifies the main topic in the content, and the meta description summarises what visitors will find. These elements should support the same purpose without needing identical wording.

Illustrative example: the title “Contact forms: fields, error messages and testing” can accompany the description in the table above. The title names the topic and its parts; the description states what readers can check. Neither should claim the page includes a downloadable template if none exists.

Google also generates the result’s title link automatically and may use several parts of the page as input. Google’s title link documentation distinguishes the displayed title link from the title element you publish. Check the title and snippet as two separate parts of the search result.

First check what the page publishes, then what Google displays. These two checks answer different questions.

How do you check the meta description in the page’s code?

Check the meta description in the published page’s HTML, not only in the editing field. Open the exact page, view the page source or use the browser’s developer tools, and look for <meta name="description" content="…"> in the page’s head. The text in the content attribute should match the approved description. If the code is generated with JavaScript, the rendered version also needs to be checked.

Illustrative code: <meta name="description" content="Check fields, error messages, recipients and confirmation before publishing your contact form.">. The content attribute holds the description. This line belongs in the page’s head, not in the visible main text.

• Check the correct environment and address. A preview or a different language version may contain different text from the page you intend to publish.
• Find description in the page’s head. Compare the entire value with the approved text, including accented characters.
• If the description is missing, check which metadata field or template produces that particular page.
• If conflicting description elements appear, identify the templates or extensions creating them and make the implementation output one unambiguous value.
• If JavaScript changes the metadata after loading, also inspect the rendered page. Record the URL, version and text that were actually checked.

Google’s guidance on JavaScript and SEO covers metadata that is set or changed with JavaScript. Checking only the editing field or initial HTML response can therefore miss differences in the finished page.

Why does Google show a different search snippet?

Google may select a search snippet that fits the query better than the meta description. A different snippet therefore does not automatically mean the code is wrong. Compare the published description with the page’s main text and the relevant search query. Also check that the correct description belongs to the correct URL and that no old template text remains. You can improve the source material, but cannot determine exactly which passage Google shows for every search.

If the code is correct but Google shows different text, start with the query and the selected passage. Does that passage address a need the meta description does not cover? Is the text still accurate and relevant? Improve a misleading or outdated passage on the page itself, but do not rewrite the entire description solely because one search snippet differs.

Record the query, date and displayed URL when following up. Changed wording in one search result does not show that all users see the same text, or that the meta description itself caused a change in traffic.

If the description does not match the title, H1 or offering, the page needs to be reviewed as a whole. The on-page SEO guide shows how to compare these elements. If several pages need rewriting, SOVRA Digital’s content production explains how the work can be scoped.