How to Write Meta Descriptions

Laptop search result with description lines highlighted beside a writing notebook.

To write meta descriptions, summarize the page’s useful content in natural language and include a specific reason the intended reader might choose it. The description should accurately represent what someone will find after clicking. It should not promise a service, resource, or result that the page does not provide.

A meta description is a page-level summary that search engines may use when generating a result snippet. It is not guaranteed to appear exactly as written. This guide explains how to create useful descriptions, adapt them to different page types, and review their implementation without mistaking a preview score for a search-performance guarantee.

Understand what a meta description can and cannot control

The description gives you an opportunity to summarize the page for search presentation. Google may use it when it considers it a useful description of the page, but it can also select text from the visible content that better fits a particular query. Different searches can therefore produce different snippets for the same URL.

Google’s documentation on snippets explains this selection and recommends accurate, page-specific descriptions. The practical implication is that you should improve both the metadata and the actual page, rather than expecting one field to control every search appearance.

A description is also not a substitute for a clear title or a useful answer. It can help communicate relevance, but the visitor still needs to find the promised information. Treat it as part of the page’s overall presentation, not a standalone shortcut to traffic.

Begin by reading the finished page

Write the description after you understand what the page actually contains. An early content brief may describe an ambition that the final draft does not fully deliver. Reading the page helps you choose a promise that is accurate rather than copying an outline that has since changed.

Identify the main task, the intended reader, and the most useful detail. For a tutorial, that might be the process the reader will learn. For a service page, it might be the service format or audience. For a comparison, it might be the criteria that help someone choose.

If the page is too vague to summarize, improve its purpose before polishing the description. A persuasive summary cannot make an unclear offer or an unfocused article more useful after the visitor arrives.

Write one clear sentence before optimizing the length

Start with a plain-English explanation of the page. Do not begin by counting characters or trying to include every keyword. A useful first draft might say, “Learn how to compare primary-keyword candidates using page purpose, search intent, and existing content.”

Then edit for clarity and specificity. Remove wording that could describe almost any page, such as “find out everything you need to know.” Replace it with the actual value the article provides, such as examples, a decision process, or a practical checklist.

A second sentence can be appropriate when it adds important context, but it should not repeat the first. The description has limited display space, so every phrase should help the reader understand the page or assess its relevance.

Add a distinguishing detail that the page supports

A useful detail can separate your page from a generic result. It might identify beginners, small-business owners, a specific service area, or the format of the resource. Choose the detail because it helps the right reader recognize the fit.

For example, “with examples for service businesses” is useful if those examples are genuinely present. “Includes a downloadable template” is inappropriate if the page only contains a table. The distinction may look small in the draft but materially changes the visitor’s expectation.

Keep business claims verifiable. If you mention pricing, availability, or a qualification, confirm that the page and business support it. Descriptions can become outdated when offers change, so avoid details you are unlikely to maintain unless they are essential.

Use the reader’s language naturally

Include the page’s main subject or a natural equivalent so the topic is clear. You do not need to repeat the exact phrase several times. A description should read like a helpful summary, not a collection of search terms separated by commas.

Supporting vocabulary can make the promise more concrete. An article about an on-page review might mention headings, links, and mobile usability. Those terms explain what the checklist covers without turning the summary into a list of every section.

Avoid forcing awkward query wording into the sentence. Research helps you understand how readers describe the task, but ordinary grammar and clarity still matter. The right reader should understand the description on the first reading.

Match the description to the page type

An informational article should describe the question answered and the depth or format of the explanation. A service page should summarize the actual offer and the relevant next step. A comparison should identify the decision it supports rather than declaring a winner without context.

A product page needs accurate product-specific information. Repeating the same promotional sentence across an entire catalog can make the descriptions less useful. The summary should help distinguish the page where meaningful differences exist.

The examples below demonstrate different approaches. They are hypothetical writing samples, not claims about actual services, measured click-through rates, or guaranteed search presentation.

Hypothetical description examples
Page typeSample descriptionWhat it communicates
Beginner guideUnderstand search intent through common query types and practical examples for small business websites.Subject, audience, and format
Service pageExplore individual SEO lessons, see how sessions work, and find out what to prepare before booking.Actual offer and next step
ChecklistReview your page’s content, links, headings, and mobile experience before publication.Scope of the task
ComparisonCompare ongoing and one-time maintenance by service scope, suitable situations, and questions to ask.Decision criteria

How long should a meta description be?

There is no fixed character count that guarantees complete display across all search contexts. Search engines can shorten snippets according to the available space and the experience in which they appear. Character counts are useful editing aids, but they are not a universal technical boundary.

Aim for a concise summary that makes sense even if some ending text is not shown. Put the most important subject and useful detail early. Remove repeated adjectives and introductory filler before cutting information that helps a suitable reader understand the page.

A plugin preview can reveal that a description is very long or awkward, but do not damage the wording just to reach a green indicator. The final sentence should remain accurate, readable, and specific.

Should you include a call to action?

A gentle action phrase can fit when it reflects the page’s purpose. “Compare the options,” “See the checklist,” or “Explore the lesson format” can tell readers what they will do. The phrase should be useful rather than an automatic addition to every description.

For an educational article, a hard sales command may feel mismatched. Someone searching for a definition may want an explanation before considering a service. Describe the answer first and let the page provide a relevant commercial continuation where appropriate.

For a booking page, a clear action can be more central. Even then, avoid urgency that the business cannot substantiate. A description should not invent limited availability or a deadline simply to increase the chance of a click.

Avoid descriptions that repeat the title without adding value

The title identifies the page, while the description has room to explain what makes the resource useful. Repeating the exact title as a complete sentence can waste that opportunity. Add detail about the audience, process, examples, or decision criteria instead.

For a title such as “How to Choose a Primary Keyword for a Page,” a useful description could explain that the guide compares intent, page type, and existing ownership. That helps the reader judge whether the article addresses their uncertainty.

Do not go to the opposite extreme by introducing an unrelated promise. The description and title should work together. If they seem to describe different articles, revise them around the page’s actual main task.

Give important pages distinct descriptions

A generic sitewide description may be accurate at the business level but unhelpful for individual pages. A service page, an introductory guide, and a technical troubleshooting article answer different needs. Their descriptions should reflect those differences.

If many pages have identical text, determine whether the cause is a template, an import, or repeated editorial copy. A template can be useful when it combines accurate page-specific information, but a fixed sentence applied everywhere may hide meaningful distinctions.

Prioritize important pages if you have a large backlog. Start with core service pages and resources that matter to the audience. Do not assume that rewriting every description is more urgent than correcting inaccurate content or a broken inquiry path.

Be careful with dates, prices, and changing claims

Specific details can improve a description when they help the reader, but they also create a maintenance obligation. A price change, discontinued offer, or new service boundary can make the summary inaccurate even if the rest of the article remains useful.

For an evergreen educational page, adding a year may be unnecessary unless the content is genuinely reviewed for that period. A current-looking date does not establish that the instructions have been verified. Use dates to communicate real relevance, not as decoration.

When updating an offer, include its descriptions in the review. The metadata, visible page, and booking destination should tell a consistent story. A searcher should not see one promise in the result and discover different conditions after clicking.

Write descriptions from evidence, not promotional habits

Avoid claims such as “the best guide,” “guaranteed rankings,” or “proven to double traffic” unless the page contains credible evidence supporting the exact statement. Most educational descriptions do not need such language to be useful.

Instead, identify the concrete material the reader receives. A worked example, a comparison table, a review process, or an explanation of common mistakes can be an honest reason to choose the page. Specificity makes the value clearer without exaggeration.

This approach also helps maintain trust. A description that accurately previews a substantial article gives the reader a consistent experience. A dramatic claim followed by generic advice can undermine confidence in the entire website.

Add the description through the correct CMS field

Most SEO-enabled content management systems provide a field for the page’s meta description. Enter the chosen text there and save through the normal publishing workflow. Do not assume the post excerpt and meta description are always the same field or used in the same way.

Review the page’s actual output if a theme or plugin may override the setting. Multiple plugins or templates can create conflicting behavior. If the saved field does not match what is generated, investigate the implementation rather than repeatedly retyping the text.

Keep the description separate from the article body unless the same sentence naturally belongs there. It is a summary for presentation, not a paragraph that must be inserted solely to make a plugin recognize the exact phrase.

Why might Google show different text?

Google may choose visible page text that better addresses a specific search. That can happen even when you have written a reasonable description. A different snippet is not automatically evidence that the description is broken or that the site has been penalized.

First check whether the supplied description is accurate and whether the page’s prominent content is clear. If the description is vague, outdated, or misleading, improve it. If it is already appropriate, repeated edits may not be the most useful response to one observed result.

Remember that a screenshot shows a particular query and context. Do not assume it captures every way the page appears. Look for a meaningful pattern before deciding the page needs a broader revision.

Can you test whether a new description performs better?

You can observe performance before and after a change, but a simple comparison does not isolate causation. Position, query mix, competing results, device, seasonality, and other page changes can all affect clicks. Record the change date and review the context alongside any metric movement.

For a small site with little data, the numbers may be too limited for a confident conclusion. You can still evaluate whether the description is clearer and more accurate. That editorial improvement is worth recognizing without inventing a statistically proven traffic effect.

If the page is struggling more broadly, consider the larger diagnostic picture. The guide on why content is not getting traffic helps distinguish a presentation issue from other possible causes.

Can AI help draft meta descriptions?

AI can propose alternatives from a supplied page, but each option needs human review. It may introduce benefits, resources, or claims that are not actually present. Check every meaningful promise against the content before using the text.

Give the tool the actual audience and page purpose, then compare its suggestions with your own plain-English summary. Keep the option that is most accurate and useful, not necessarily the one with the strongest promotional wording.

The final responsibility remains the same: describe the page honestly and clearly. If you want feedback on a set of descriptions, one-on-one SEO coaching with Marium can help you review page fit, wording, and the practical reasons behind each choice.