Free meta description generator for a stronger first draft.

Ashwell Cycles is an independent bike shop with a workshop at the back. The page needing a description is the wheel building service: hand built wheels for touring and gravel bikes, built to order, usually ready in a week. The queries that reach it are things like hand built wheels, custom wheel building near me, and the occasional specific one naming a hub or rim brand. The page itself explains the process, lists the components stocked, and gives a price range.

The description drafted for it: Hand built touring and gravel wheels, laced and tensioned in our workshop, usually ready within a week. See the hubs and rims we stock, and typical prices. That is 148 characters including spaces, so the whole line survives on a desktop result and the first two thirds survive on a narrow phone.

It holds up for a few reasons. It repeats the phrase hand built, which is the term people search with and which will render in bold in the results list. It gives two facts nobody else on that results page is giving: the work happens in the shop rather than being sent away, and the turnaround is about a week. It sets an accurate expectation of what the page contains, which is a stock list and prices, so the click is not a surprise. And it front loads, so that if the tail is cut a reader still learns the product, the location of the work and the timescale.

The version that usually gets written instead: Ashwell Cycles is your local bike shop offering the highest quality wheel building services. Our expert team is passionate about cycling and dedicated to customer satisfaction. Contact us today to find out more.

That runs to about 215 characters, so the last sentence never appears. It opens with the shop name, which is already the first line of the result and does not need repeating. Highest quality, expert and passionate are claims every competing result is also making, so they do nothing to separate this listing from the nine around it. Nothing in it tells the reader what is on the page, so the click is a gamble, and a visitor who wanted prices and finds a paragraph about passion leaves immediately. The closing instruction is aimed at someone who has already decided, which is not who is reading a results page.

The rewrite took two decisions: say the specific thing, and cut everything that would be equally true of the shop three towns away.

Do not write descriptions for pages you do not want in search results. Thank you pages, internal search results, cart and checkout steps, filtered listing variants and staging URLs should be handled with a noindex tag or by not linking to them, not by writing them a nice line. Time spent on a snippet for a page that should not be indexed is time not spent on the page that should.

Do not hand write them for a catalogue in the thousands. On a site with ten thousand product variants, per page descriptions written one at a time will never be finished and will go stale as stock changes. Either build a template that assembles the description from the fields you already hold, and accept that some will read mechanically, or leave the tag off and let the search engine pull a passage from the page. An absent description is not an error, and a search engine substituting page text to match the query often produces a better snippet than a stale template would.

Do not reach for a description when the page's real problem is the title or the content. If the title does not contain the thing people are searching for, or the page does not actually answer the query it is ranking for, a better snippet will earn a click that ends in a fast return to the results. Fix the page, then write the line.

And do not write one for a page that is not yet in the results at all. If it is not indexed, or sits far enough down that it is barely served, the description has no audience. The work that page needs is content, internal links from pages that are already found, or a reason to exist that is different from the page ranking above it. Where a description does earn its time: pages that already appear in the first page or two, where the listing is competing with eight or nine near identical results and the wording is the only lever left.

The practical range is about 120 to 155 characters. Search results are truncated on pixel width rather than on a count, so a line full of wide letters is cut earlier than a line full of narrow ones, and the mobile result has less room than the desktop one. Treat 155 as a ceiling rather than a target, and write so that the sentence still makes sense if the last third disappears.

That constraint favours a particular shape. Put the distinguishing fact in the first clause, the supporting detail second, and anything optional last. Two short sentences read better in a results list than one long one, because a reader is scanning rather than reading and a full stop gives them somewhere to stop.

A few conventions save trouble. Avoid double quotation marks, which can be truncated awkwardly or escaped oddly by the system writing your tags. Avoid opening with the brand name, since it already appears above the description in the result. Skip the pipe and hyphen separators that belong in title tags. Dates and prices are useful when they are accurate and maintained, and actively harmful when the page says one thing and the snippet says another six months later.

Search engines substitute their own snippet a large share of the time, usually because a passage on the page matches the specific query better than your general purpose line does. The same page can therefore show three different snippets to three different searchers, which is not a fault to be corrected. It is the system doing what your single line cannot, which is matching the words actually typed.

This changes what you should optimise for. Your description is the fallback and the branded case: what shows when someone searches your name, or when nothing on the page is a better fit. It is worth writing well for that. But if you find yourself rewriting the same tag repeatedly because a different snippet keeps appearing, the more useful work is on the page body, since that is the text being chosen.

It also means the page should contain clean, quotable sentences. A page written entirely in fragments, bullet points and headings gives the engine poor material to extract, and the automatic snippet reads badly as a result. A page with one clear declarative sentence near the top explaining what it is tends to produce good substitutions, whatever the query.

The title tag is the link, and it carries the ranking weight of the three. It should contain the term the page is trying to be found for, and it is short, roughly the first 55 to 60 characters before truncation. The meta description does not carry direct ranking weight. Its job is entirely persuasive, and it has more room to be a sentence. Writing them as a pair works better than writing them separately: the title names the thing, the description says what is distinctive about this version of it, and neither should repeat the other's words.

The Open Graph and Twitter card descriptions serve a different audience again. Those render when the link is pasted into a social platform or a messaging app, where there is no results page of competing listings and no query terms to match. That reader has been handed the link by someone they know. A social description can therefore be warmer, can run longer since the truncation rules differ by platform, and can assume no prior context about the topic.

Many content systems fall back to the meta description for all three fields. That is acceptable, and better than leaving them empty, but on your most shared pages it is worth writing the social version separately.

Preview tools are approximations. The reliable check is to search a phrase unique to the page, in a private browsing window, on a phone as well as a desktop, and look at what is actually rendered. That will show whether the line is being used at all, where it is being cut, and whether the query terms you expected are appearing in bold.

The second check is for duplication across the site. Export every page's description, sort them, and look for repeats. Duplicated descriptions are one of the most common issues on sites built from templates, and they usually indicate the pages themselves are near identical, which is the bigger problem. The description audit is a cheap way to find it.

The third check is behavioural rather than textual. Search Console will show the queries a page is served for and how often the listing is clicked. If a page is shown often for a query and rarely clicked, the description is a reasonable first thing to change, since it is the cheapest variable on the page. Change one line, wait for it to be recrawled, and compare over a period long enough to survive normal weekly variation. Changing five descriptions at once teaches you nothing about which one mattered.