On-Page SEO
Chapter 02 / 08
Meta descriptions
Meta descriptions do not rank, but they decide whether the people who see your snippet click through. Here is how to write the second-most-important 160 characters on your page.
Meta descriptions occupy a strange place in SEO mythology. They do not rank — Google has said so for over a decade — and yet writing them well is one of the highest-ROI activities on a content page. The reason is simple: every CTR point you earn from the SERP compounds into more sessions, more conversions, and more downstream ranking signals. The meta description is the second title, the second pitch, and increasingly the second citation in AI answer engines. Treating it as an afterthought is one of the cheapest mistakes a content team makes.
“Meta descriptions don’t rank you. They decide whether the people who already saw your ranking click through. The compound effect over a year of pages adds up to more traffic than a 5-position ranking lift on a single keyword.”
What a meta description is
A meta description is the <meta name="description"> tag in the document head. Its job is to summarise the page in one or two sentences for the SERP snippet, the OpenGraph share preview (when not overridden), and increasingly the AI answer engine retrieval prompt. It does not affect ranking directly. It affects everything downstream of ranking.
The ranking myth, briefly
Meta descriptions are not a ranking factor. They have not been since 2009. Repeating the myth (“put your keyword in the meta to rank”) is one of the easiest ways to spot SEO advice that has not been updated in a decade.
What is true: a query-matched keyword in the meta description gets bolded in the SERP, the bolded text earns more clicks, and higher CTR is a quality signal Google uses indirectly. So the keyword belongs in the meta — for CTR, not ranking. The distinction matters because it changes how you write: keyword presence is a means to a click, not a means to a ranking.
Length: 140–160 characters, front-loaded
Google truncates desktop snippets around 158 characters and mobile snippets around 120. The practical rule:
- Aim for 140–160 characters total.
- Put the most important content (keyword + value prop) in the first 120 characters so it survives mobile truncation.
- Treat 155 as the safe ceiling. Going past 160 risks truncation mid-word.
- Going under 100 leaves SERP real estate on the table — Google often pads short metas by pulling body copy you did not vet.
The structure that earns the click
A meta description that converts has three parts in this order:
- Primary keyword in the first half. Bolded in the SERP, matches the query the user just typed.
- Specific value or differentiator. What makes this answer worth clicking versus the nine others on the page.
- Action verb or implicit CTA. “Learn how”, “See the framework”, “Get the checklist”. Not always literal, but the meta should imply a clear next step.
Example: “Title tags in 2026: the H1 = URL = Title rule, pixel-width truth, multi-locale handling, and the four mistakes that kill CTR. Read the full breakdown.” Keyword first, value middle, action implicit. 156 characters.
Why Google rewrites your meta (and how to win the rewrite)
Google rewrites meta descriptions roughly 70% of the time, more frequently than it rewrites titles. The reasons are nearly always one of these:
| Trigger | Why it fires | Fix |
|---|---|---|
| Meta missing entirely | No tag at all means Google must invent something | Set a meta description on every indexable page |
| Meta doesn't match the specific query | Google grabs body copy that better answers the searched intent | Write metas that mirror the primary keyword's intent, not generic page summaries |
| Meta is too short or too long | Truncation or padding both trigger rewrites | Stay between 140 and 160 characters |
| Meta is keyword-stuffed | Spam-pattern detection rewrites to body copy | Use the keyword once, write the rest in human language |
| Meta is generic | 'Welcome to our blog' has lower relevance than any specific body sentence | Be specific: name the framework, the takeaway, the differentiator |
When you write a focused, query-matched meta of the right length, Google leaves it alone over 60% of the time on long-tail queries — well above the 30% baseline.
The meta as the “second title” in AI search
AI answer engines (ChatGPT search, Perplexity, Gemini, Claude) treat the meta description as a high-weight signal at two stages of their retrieval pipeline:
- Document selection. When the engine decides which 5–20 pages to actually read for a query, the title and meta description are the strongest hints. A vague meta gets the page deprioritised.
- Citation summary. Some engines display the meta as the snippet text alongside your citation. A clear meta becomes the version of your page the user sees first.
The implication is the same as for titles: write a meta that reads as a standalone, query-matched summary. The user (or the engine) has not seen the page yet. The meta is the bridge.
Multi-locale meta descriptions
Each locale needs a meta description written from the localised keyword research, not translated from the EN source. The same rule that applies to title tags applies here: the meta should match the query the localised audience actually types, with the localised keyword in the first half.
For Spanish (Mexico) deliverables, that often means the meta keeps a few industry terms in English (title tag, meta description, anchor text, snippet) while the surrounding language is real Mexican Spanish — never pocho calques. The bolded match still happens because Spanish-speaking users in Mexico search those English terms verbatim.
Common meta description mistakes
- Letting the CMS auto-generate from body. Auto-generated metas are usually the first 160 characters of body copy, which rarely reads as a summary.
- Duplicate metas across templated pages. Programmatic location pages with one shared meta dilute the signal across the whole page set.
- Keyword stuffing. Repeating the keyword three times triggers rewrites.
- Marketing fluff. “Discover our award-winning solutions” tells neither the user nor Google what is on the page.
- No meta at all. Forcing Google to invent one is the most expensive mistake — you have zero control over the snippet for that page.
- Translating EN metas literally for other locales. Same problem as titles; the localised query is different.
The OpenGraph relationship
By default, the meta description is also used as the og:description when sharing to social or chat. If you want a more conversational tone for shares, set og:description separately. Many teams skip this and end up with metas that read fine in Google but stiff in Slack or LinkedIn previews. The fix is two minutes of work per page; the impact on share-driven traffic is meaningful.
The bottom line
Meta descriptions are not a ranking lever. They are a CTR and citation lever, which is the same outcome by a different path. Write them in 140–160 characters with the primary keyword in the first half, the specific value in the middle, and an implicit next step at the end. Mirror the localised query in each locale. Override the OG description when the share context calls for a softer tone. And stop letting Google invent the snippet for you — every meta you do not write is a click you do not earn.
Common questions
Common questions
Quick answers to what we get asked before every trial signup.
Not directly. Google has confirmed for over a decade that meta descriptions are not a ranking factor. They affect rankings indirectly through CTR — a snippet that earns more clicks signals query satisfaction, which can lift the page over time. The ranking myth persists because the indirect effect is real, just one step removed from the tag itself.