Meta Description Example

Think of a meta description as the free ad copy that appears under your page title in Google. It does not help you rank — Google has said so repeatedly — but it can make or break the click. I aim for 150 to 160 characters, lead with the primary keyword, and write a clear summary of what the page delivers. For example, a page about pruning roses might use: 'Learn how to prune roses the right way. Avoid common mistakes and keep your garden blooming all season.' That tells the searcher exactly what they get and includes the key phrase. I write descriptions after the page content so I know what to summarise. Every page gets a unique one; Google ignores duplicates and pulls random text instead. A strong call to action — 'Read the guide', 'Shop now', 'Get started' — can lift click-through rate, especially in competitive SERPs. But don't trick: the description must match the content or users bounce. I have seen pages lose rankings because high bounce rates from misleading snippets signal poor relevance. The best descriptions answer the search query's implied question in a sentence. For a page on [on-page SEO](/on-page-seo/), I might write: 'Optimise your page structure, headings, and content for better rankings. Includes a checklist you can copy.' That tells the user what they will find and sets an accurate expectation.

In competitive SERPs where the top results look similar, the meta description is your differentiator. I tracked a client's product page for 'organic dog food': the original description read 'Buy organic dog food online' — bland. I rewrote it to 'Made with free-range chicken and no fillers. Try our grain-free organic dog food with a 30-day satisfaction guarantee.' Clicks jumped 18% in three weeks. For blog posts, the description often becomes the featured snippet if it answers the query directly. For example, a page titled 'How to Clean a Cast Iron Skillet' with description 'Scrub with coarse salt and oil, rinse with hot water, and dry immediately. Avoid soap.' That concise answer can appear as a rich result. I also pay attention when users are comparison shopping: highlight a unique benefit, price guarantee, or specific offer. On e-commerce pages, a good description reduces friction. One mistake I see: writing descriptions that repeat the title. That wastes space. You have 150 characters to add information the title does not cover. Use them. This ties into good [SEO copywriting](/seo-copywriting/): every word earns its place. For a [blog SEO](/blog-seo/) page, the description should complement the title, not echo it. If the title says '10 Email Marketing Tips', the description might say 'Avoid these three common mistakes that kill open rates. Get a free template too.' That added value encourages the click.

I used to write the same meta description for every page on a site. It took me a while to realise Google just ignores those and pulls random text. I also stuffed keywords, thinking more matches meant more bolding — but it made the description read like a robot and nobody clicked. Another error: I wrote descriptions before writing the page, guessing what I would cover. Often the final content did not match, so the snippet misled users. I also made descriptions too long. My early ones were 200+ characters; Google would truncate them awkwardly. Now I aim for 150 to 160 and check the preview. Perhaps the biggest lesson: the description is not a ranking factor, so optimising it purely for keywords instead of user intent is a waste. I now treat it as micro-copy for the SERP, not another SEO field to fill. For affiliate pages, I test different calls to action to see which lifts CTR. On a recent test, 'Read the full review' outperformed 'Learn more' by 6%. I also stopped copying the [AIDA model](/aida-model/) blindly — it works for sales pages but not for informational queries where a direct answer beats a hook. The [SEO title](/seo-title/) and meta description must work together: the title draws the eye, the description seals the click. Getting that pairing right took me years of trial and error.