How to Write a Good Meta Description

The meta description is the short paragraph search engines often show under your blue link. It is not a direct ranking lever on Google, but a clear snippet improves click-through when it matches what the searcher wanted. Treat it as ad copy for your page, not a keyword dump. Snippets also appear in some AI overview and link-preview contexts that reuse meta tags, so clarity still pays even when traffic mixes sources.

Length and display reality

Aim for about 120–160 characters in English so the snippet is less likely to truncate mid-sentence on desktop. Mobile may show fewer characters. There is no fixed guarantee — Google sometimes rewrites snippets from on-page text if it thinks another passage fits the query better. Desktop and mobile SERPs use different widths; write the first 120 characters as a complete mini-pitch so truncation hurts less. Write one complete thought: benefit, scope, and a gentle call to action. Avoid ALL CAPS, excessive punctuation, and repeating the title verbatim.

Match search intent

A how-to page should promise steps; a tool page should name the input and output (for example, HEIC to JPG). If the page solves a narrow problem, say so in plain language. Misleading snippets increase bounces, which hurts performance over time even when rankings hold. Scan the H1 and first paragraph — your description should align with them so users are not surprised after the click. For programmatic SEO at scale, parameterize one sentence template but keep a human review step so every URL mentions a distinct task or noun.

Write it by hand in your CMS

WordPress (Yoast or Rank Math), Webflow, Ghost, and static site front matter usually expose description or summary fields. Save after editing and view page source to confirm the tag rendered. For Next.js or React, set metadata.description in your layout or page export. When you ship many similar tool pages, a shared template ('Free online … — no install, works in your browser') is fine if each description names the specific task. Staging environments should block indexing but still let you view-source meta tags before production cutover.

Draft and tighten with AI assistance

Open /tool/ai-meta-description, paste your page title or a bullet summary of the content, and generate a few options. Pick one, shorten manually, and read it aloud. AI drafts can be wordy or generic — your edit is what makes it trustworthy. Do not publish ten near-identical descriptions across unrelated URLs; search engines may ignore duplicates.

Technical checklist

One meta description per URL. Avoid leaving it empty on indexable pages — Google will invent text, sometimes from nav boilerplate. Noindex pages do not need polished snippets. Pair descriptions with a solid title tag and canonical URL.

Review checklist before publish

Read the description on a phone-sized screen: the first sentence should stand alone if the rest truncates. Confirm it does not repeat the title word-for-word and that it names the primary task or outcome. View page source on staging and search for name="description" or property="og:description" depending on your stack. When you maintain hundreds of tool pages, spot-check new URLs weekly so a layout regression does not ship empty tags across a template. If Search Console shows rising impressions but flat clicks, test a clearer verb in the first clause — open, convert, calculate, merge — matched to the query intent you see in the performance report. Keep a short internal doc of approved patterns for tool, blog, and hub pages so contractors and automation do not invent new boilerplate every sprint.

Hub pages and category indexes deserve the same care as money pages: say what the reader can do on that URL in one sentence, then name the format (free, browser-based, no install) only if true. Avoid duplicate descriptions across paginated series — page 2 of a blog list should not reuse page 1 verbatim; either noindex later pages or write a distinct line about older posts. When you translate, hire or review descriptions with a fluent speaker; machine-translated snippets show up as awkward in SERPs and hurt clicks even when rankings hold. For seasonal landing pages, date-stamp in the body, not necessarily in the meta line, unless freshness is the hook. Audit competitors only to calibrate clarity, not to copy phrases. Store approved description text in git beside the page component so diffs show marketing changes during code review.

FAQ

Does Google always use my meta description? No. It chooses snippets dynamically; a good description still helps when your text is used.

Should I include the brand name? Optional at the end if space allows; lead with the user task first.

Can the AI tool see my whole site? It works from what you paste in the session; it does not crawl your domain automatically.

Is meta description the same as og:description? They can differ — meta targets search, Open Graph targets social cards. Align them when possible.