Foundational pillar / check meta-description

Meta description (length and CTR signal)

A meta description in the 50 to 200 character range helps Google select the snippet text and gives AI engines a clean topic summary.

By Shimon Carroll, Founder, SEO for AI Agents · Last updated

What this check measures

The check verifies the meta description is present, non-empty, and falls within 50 to 200 characters. The meta description is not a ranking factor in classic Google search, but it is the primary candidate text Google uses to construct the SERP snippet (Google may rewrite, but a well-crafted meta description is selected most of the time per documented Google Search Central guidance).

Why it matters

The meta description is the CTR lever in classic Google search and the secondary topic anchor for AI engines. A missing meta description forces Google to construct a snippet from on-page text (which is often a navigation fragment or a cookie banner); a too-short description (under 50 characters) loses pixel space to whitespace; a too-long description (over 200 characters) gets truncated mid-sentence and loses the call-to-action. AI engines parse the meta description as a confirmation of the topic claim made by the title and H1.

How we score it

PASS if 50 <= length <= 200 AND non-empty. FAIL otherwise. Severity defaults to MEDIUM (foundational pillar). Vertical adapters do not currently override this severity.

Confidence-flag rules

Confidence is HIGH for all outcomes; the meta description is in the document <head> and is server-rendered in essentially every real-world stack. We have not observed a real-world case where the meta description appears only after JS hydration.

Common mistakes

  • Leaving the meta description empty so Google constructs the snippet from the navigation or footer text.
  • Duplicating the same meta description across every page in the site, which prevents per-page differentiation in the SERP.
  • Stuffing keywords into the meta description without a call to action (Google may rewrite or replace such snippets).
  • Writing a meta description in the third person ("This page describes...") instead of speaking to the reader directly.

How to fix it

Write a single sentence of 110 to 160 characters that names the page intent and includes one specific concrete detail (a number, a date, a named entity). End with a soft call-to-action that does not over-promise. For Next.js, set the description in the route metadata; for content-management systems, populate the per-post description field and never let it fall back to a global default.

Primary sources

Changelog

  • · Initial publication. Length range set to 50 to 200 characters to cover both mobile and desktop SERP snippet widths.
← Back to the methodology indexRun an audit