How to Write Meta Descriptions That Actually Get Clicks

Why meta descriptions matter

Meta descriptions are not a direct ranking factor. Google has said this explicitly. But they are the single biggest lever you have over click-through rate (CTR) from search results. A page ranking #3 with a compelling description can outperform a page ranking #1 with a generic one. Higher CTR sends positive engagement signals back to Google, creating a feedback loop that can improve your position over time.

Keep it between 150 and 160 characters

Google truncates descriptions at roughly 160 characters on desktop and 120 on mobile. Going under 120 wastes space. Going over 160 means your ending gets cut off, often mid-sentence. The sweet spot is 150 to 160 characters: long enough to convey value, short enough to display in full.

The formula that works

Every effective meta description follows the same structure:

1. Lead with the target keyword (or a close variant). Google bolds matching terms in the snippet, which catches the eye.
2. State the benefit. What does the reader get from clicking? Be specific.
3. End with a call to action. Tell them what to do: "Learn how", "See the checklist", "Try it free".

Good vs. bad examples

Never duplicate descriptions across pages

Every page needs a unique description. When two pages share the same description, Google has no way to differentiate them in search results. It often drops both descriptions and generates its own. Worse, duplicate descriptions can signal thin or duplicate content. If you have hundreds of pages and cannot write unique descriptions for all of them, leave the tag empty on low-priority pages. Google will auto-generate something. That is better than the same sentence appearing on 50 pages.

How to set meta descriptions in Next.js

Next.js App Router uses the Metadata API. Export a metadata object from any page or layout file:

import type { Metadata } from "next"

export const metadata: Metadata = {
  title: "How to Write Meta Descriptions That Get Clicks",
  description:
    "Meta description best practices for 2026. Learn the optimal "
    + "length, keyword placement, and CTA formulas that improve "
    + "click-through rates. See examples.",
  alternates: {
    canonical: "/blog/meta-description-best-practices",
  },
}

For dynamic pages (like blog posts fetched from a CMS), use generateMetadata() instead:

export async function generateMetadata({ params }): Promise<Metadata> {
  const post = await getPost(params.slug)
  return {
    title: post.title,
    description: post.excerpt, // keep under 160 chars
    alternates: { canonical: `/blog/${post.slug}` },
  }
}

Quick checklist

• 150 to 160 characters.
• Target keyword within the first 60 characters.
• Specific benefit, not a vague promise.
• Ends with a clear call to action.
• Unique per page. Never duplicated.
• No keyword stuffing. One mention of the keyword is enough.
• Matches the page content. Misleading descriptions increase bounce rate.