How to Write Meta Descriptions That Earn the Click

If you own a page that shows up in search but doesn't get the clicks you'd expect, the description under the title is one of the few things you can change in about ten minutes. This guide walks you through meta description writing one page at a time, so you end up with a short, accurate description that tells a searcher what they'll find on the page and gives them a reason to open it. It works for articles, product pages, category pages, service pages, and your homepage.

The short version is this. Write a page-specific description that says what the searcher will find, why that's useful, and what to do next. Put the most important part near the start, use the language of the search naturally, and check a desktop and mobile preview before you publish. For most pages, about 120 to 155 characters is a good range to draft in, and it helps to make the main promise clear within the first 110 to 120 characters.

You'll need access to the page you're writing for, the field in your CMS where the SEO description goes, and, if the page is already live, Google Search Console. This guide doesn't cover why a search engine sometimes shows different text than the one you submitted, and it doesn't cover title tags. Those are separate jobs.

What a meta description does, and what it doesn't

A meta description is the short summary in a page's HTML, usually written as <meta name="description" content="A concise description of this page.">. Most content management systems give you a field that creates this tag, so you rarely need to touch the code.

Its job is to help a searcher recognize that this page answers their need and to give them a believable reason to pick it over the other results. Your result also shares the page with more than plain links these days, which is covered in how the modern SERP crowds out organic clicks. Google describes a good one as a short, relevant summary that informs and interests people, a bit like a pitch for the page.

It helps to be clear on what it doesn't do. A strong SEO meta description can help you win a click, but writing one isn't a direct shortcut to a higher ranking, so you shouldn't expect keywords in the description or a better click-through rate to move you up on their own. It's also worth knowing that the text a searcher sees under a result can differ from what you submitted, because your description informs that text rather than guaranteeing it. That's all this guide will say about it, and it doesn't change how you write the description.

Two more ideas sit behind everything below. The first is that accuracy matters more than cleverness. Whatever you promise, whether that's a guide, a feature, a price, an offer, a location, or a next step, has to exist on the page. The second is that each page gets its own description. A homepage can summarize the whole site, but an article, a product, a service, a collection, or a pricing page each needs its own promise.

Step 1: Pick one page and name the searcher's intent

Work on one URL at a time. Write down its page type, its main topic, who it's for, and the question or decision that brings that person to search. If the page is already live, open Google Search Console's Performance report and look at the queries it appears for. Those tell you what people are actually looking for when they see your result.

Then decide what kind of thing the searcher wants. It might be an explanation, a comparison, a product detail, a category to browse, a price, or a way to contact a business. That choice shapes everything you write next. If you want more background on this, our guide to SEO content for different search intent types covers how intent changes what a page should do.

You're done with this step when you can finish this sentence without any vague words: "Someone searching for ___ should click this page because they'll find ___."

The most common mistake here is starting from a keyword list or the company slogan. Neither one tells you why this specific URL is the right place to land. If the page answers several needs, pick the one main promise and let the rest go for now.

Step 2: Pull two or three provable details from the page

Open the page and read it as if you'd never seen it. Note the main thing it delivers and the strongest detail that qualifies it. On a how-to page, that might be the task and a checklist that's included. On a product page, it could be a specification or an availability detail you can verify. On a service page, it's the work that gets delivered. On a category page, it's the kind of products and the criteria that help someone choose.

Only pick details that are current and that are visible on the page, or clearly supported by it. Each claim you might use should be something you can check against the page in a few seconds, and at least one detail should set this page apart from the other pages on your site.

This is also the step where a stored source of brand context earns its keep. Deep IQ holds your product, audience, and brand voice details in one place, so descriptions produced through DeepSmith start from what your company actually says about itself. You still need to check the description against the finished page, because stored context can't tell whether an offer has changed or a claim has gone stale.

Where people go wrong is promising things the page doesn't have. That might be a free template that doesn't exist, an old price or offer, a page called "complete" when it only handles one part of the topic, or the same company description pasted onto unrelated pages. Any one of these sets up a searcher who clicks and then feels misled.

Step 3: Draft a direct, page-specific value statement

Now write one sentence that leads with the topic or outcome the searcher came for and then names the specific value the page delivers. A formula that works well for a first draft is "Find or do [the task] with [the distinguishing detail or deliverable]." Use the main query's wording where it makes the sentence clearer, and skip it where it would just be repeated.

Write it in plain language for a person scanning a list of results. Someone who reads only that one sentence should be able to tell what the page is about and what they'd get from visiting.

Here's a before and after using a page that supplies a checklist and examples. The weak version is "SEO meta description, meta description writing, SEO tips, descriptions." It's a pile of terms and it doesn't say what's on the page. The stronger version is "Write a meta description that previews your page's value and gives searchers a reason to click. Follow a short checklist with examples." That one names a task and says what the reader will have when they're done. It should only be used on a page that really contains that checklist and those examples.

Google's own good and bad examples lean the same way. They favor a specific summary of the page over a list of terms or a generic welcome.

The usual mistakes are opening with "Welcome to our website," stacking up variations of the same keyword, or writing an intriguing sentence that never says what's on the page. If you catch yourself doing any of these, go back to the sentence from Step 1 and start again from it.

Step 4: Add a reason to choose the result and a next action

A description that only says what a page is about can still leave the searcher unsure. So ask what would make a click worthwhile right now. It could be a worked example, a clear set of steps, a comparison framework, a product attribute that matters, buying criteria, or concrete business information like hours or a location.

Where it fits, you can end with an action such as "See the examples," "Compare the options," or "Explore the plans." The benefit does most of the persuading, so the action is optional. If the sentence is already full, leave it out.

You're done when the description answers two questions without claiming anything the page can't back up. What's here, and why should I open it?

Common mistake: A call to action can't make up for a missing preview of the page. "Discover more today" says less than naming the guide, the comparison, the product detail, or the decision the visitor will actually find.

Other things to avoid are "Learn more" attached to an otherwise empty sentence, a discount or result the page doesn't support, and superlatives used in place of a useful detail. If you're tempted, see whether clickbait can drive sustainable organic traffic.

If you produce articles with DeepSmith, the Content Studio Writer generates publish-ready metadata as part of the writing pipeline, so each article starts with a description grounded in the page itself. That gives you a page-based starting point, and it doesn't tell you a particular description will earn a particular click-through rate. The click reason is still yours to check before it goes out.

Step 5: Trim to a version that survives the display

Count the characters in your description, then look at a preview on both desktop and mobile. Google publishes no maximum number of characters for the tag, and the text shown in results may be shortened to fit the device. That's why every meta description length recommendation you'll see is a working heuristic and not a rule.

Here's how those heuristics compare, starting with what Moz recommends.

Width isn't the same as character count, since letters differ in width and the search interface can change. So treat all of these as estimates. A useful way to work is to draft the shortest complete version first, aim for roughly 120 to 155 characters when a full description fits, and put the page's subject and main benefit in the first 110 to 120 characters. A shorter complete sentence is better than padding.

If the essential promise has to survive a small mobile display, write a shorter description and check it in the preview. Since the shift to mobile search changed click behavior, the mobile preview deserves as much attention as desktop. Don't assume 120 to 155 characters will always show in full on a phone.

When you need to cut, remove repeated terms, broad adjectives, and a redundant closing call to action before you remove any useful detail. Then read the shortened version as a standalone message. If the part that stays visible still gives a true subject and a benefit, you're done.

Pro tip: Spend any leftover space on one concrete detail, such as a number of steps or a kind of example, and not on one more variation of your target keyword.

The mistakes to watch for are treating 160 as a guaranteed allowance, chasing a character count while ignoring how wide the text looks in the preview, and leaving the one really persuasive detail for the end of the sentence, where it's the first thing to get cut.

Step 6: Check uniqueness, enter the field, and review the finished page

Compare your description with the ones on nearby URLs. If two of them could swap places without anyone noticing, the page's distinguishing fact isn't visible enough yet. Check spelling, brand voice, any offer, and whether the item you promised shows up on the page.

Then enter the text in the page's SEO metadata field, save, and look at the preview. Where that field lives depends on your tool. In Shopify, a standard page has a search engine listing preview with an edit control and a description field, and you save after entering the text. The homepage description is set under online store preferences, and you can also set descriptions for products, collections, and blog posts. In Yoast SEO, the search appearance preview gives you a description editor and a length indicator, and you can review both the mobile and desktop views.

For a large set of similar pages, such as many products or many locations, a template filled with verified page-specific facts can serve you better than one shared generic sentence. Templates are fine when every description stays distinct, readable, and accurate, but they aren't permission to repeat one line across every URL. Whenever descriptions are generated in bulk, read a sample for accuracy and duplication, and check that the page-specific data actually landed in the right place. If you're building a repeatable format for many pages, reusable article templates show how to standardize the structure and keep the content specific.

DeepSmith's Produced Content is where you review and revise an article's metadata before it publishes. Think of it as an editing checkpoint. It gives you the place to make changes, and comparing the proposed description with the finished page is still your job.

You're done when the saved page has a specific, accurate description, a usable preview on mobile and desktop, and no conflicting promise in the body of the page.

The mistakes here are editing the visible introduction when you meant to edit the SEO description field, pasting one sitewide sentence into every page, and approving generated descriptions in bulk without checking whether the page-specific data went in correctly.

Step 7: Watch page-and-query CTR and revise when needed

Once a page has been live for a while with its new description, go back to Google Search Console. Open the Performance report for search results and look at clicks, impressions, and CTR. Search Console defines click-through rate as clicks divided by impressions, so 40 clicks from 1,000 impressions would be a 4% CTR. That's only an arithmetic example and not a benchmark or a result you should expect. If AI answers appear above your results, read the click data about AI Overviews before you judge a description on CTR alone.

Note a baseline before you edit, then compare a later period that's as similar as you can make it. Look at the page and at the queries it appeared for. Prioritize pages that have plenty of impressions and whose descriptions could say more clearly what the page really offers. Come back to the text whenever the page's content, an offer, or the reader's need changes.

If you want to go further into reading these reports, our piece on diagnosing a CTR-driven traffic drop shows how to separate click problems from ranking problems. The guide to reading the AI Overview signature in Search Console explains why impressions and clicks can drift apart for reasons that have nothing to do with your wording.

You're done when your team has recorded the page, the description, the queries it's meant for, the date of the change, and a comparable before and after view of clicks, impressions, and CTR.

The main mistake is treating one week's movement as proof that the new wording caused it. Query mix, ranking position, seasonality, device mix, and other changes on the site can all shift the numbers. So use the report to spot opportunities and judge direction, and don't treat it as a controlled test. Searchers seeing more results but clicking less is a wider trend, covered in why impressions keep rising while clicks fall. There's no verified figure for how much a rewrite improves clicks, and it's better to not promise your team one.

Meta description examples for different page types

The examples below are illustrative drafts. They aren't observed search results, and the hypothetical pages don't belong to a real business. Any real page would need to actually contain everything its description promises, and you'd check the final character count and previews in your publishing workflow. The counts shown are the length of each draft.

Each one gives a reason to click for a different reason. The how-to example names the task and promises steps plus examples. The homepage states the platform's purpose and offers a next step without promising a result. The feature page says what the feature shows and doesn't re-describe the whole company. The product-detail example uses the details a shopper compares, and the category example describes the range someone can browse. The service example previews scope and a concrete next step, the comparison example names its criteria and the decision it supports, and the pricing example helps a reader decide without listing prices that could go stale. The local example shows why practical, accurate information matters when someone is deciding whether to visit.

You'll also notice that not every description follows one sentence pattern. Google's guidance allows facts such as an article's author or a product's price or manufacturer when they're relevant and accurate, so a description can sometimes lead with structured facts instead of a conventional marketing sentence. A call to action is also optional. "Compare plans" is helpful on a pricing page, while on a page with an important specification, that limited space may be better used on the specification.

If you'd like something to hand your team along with these meta description examples, here's a drafting card you can copy. It's a proposed workflow and not an industry benchmark.

1. URL and page type
2. Main query or intent
3. The actual on-page deliverable
4. One distinguishing detail
5. A one-sentence description
6. The mobile opening (the first 110 to 120 characters)
7. Preview and accuracy check
8. Publication date and a later CTR review

What to do next

Pick one page that already gets a good number of impressions, and work through the steps above for that page only. Write the sentence from Step 1, gather the details from Step 2, draft and trim the description, preview it on both screens, and note the date and your baseline numbers in Search Console. Then check back after a similar period and decide whether the promise needs another edit.

Once you've done this for one page, the drafting card makes the next ten much faster, and it gives anyone else on your team the same starting point. If you'd like to produce articles with metadata included as part of the writing process, you can start a 7-day free trial of DeepSmith and review each description in Produced Content before anything publishes.