Fix Missing Meta Description: Write One Per Indexable Page

What's happening

The meta description is the tag in the document head. It is the snippet Google may show under the title on the SERP. Google does not always honor it — for ~60-70% of queries Google generates the snippet from the page's body content, picking the passage most relevant to the query.

When the tag is missing entirely, Google has nothing to fall back on except body content. Snippet quality depends on how scannable your page intro is. For pages that bury the answer in the third paragraph, the resulting snippet is often a navigation menu, a cookie banner, or boilerplate footer text.

Meta description has not been a direct ranking signal since Google announced this in 2009, but it remains one of the most important CTR signals. A well-crafted description that previews the answer can lift CTR by 20-30% over an auto-generated snippet that misses user intent.

Why it matters

CTR loss compounds across every impression. For a page ranking #4 with 10,000 monthly impressions, a 25% CTR uplift from a good description is worth 250 extra clicks per month — material on competitive head terms.

Brand voice disappears. Without a description, the SERP listing looks generic. Sites with a consistent description format (problem-promise-CTA) build CTR and recall over time relative to competitors with raw page content scrapes.

Social sharing fallbacks suffer too. Many social platforms read the meta description when no og:description is set — a missing meta description means uglier link previews on every chat and social platform that lacks dedicated OG tags.

Common causes

• The CMS description field is left blank by default and authors forget to fill it.
• Programmatic pages do not derive a description from the entity data model.
• The framework's metadata API was wired for title only.
• An import script created pages without populating the description column.
• The description is only set client-side after hydration, so the SSR HTML is missing it.
• A character limit was respected too aggressively (e.g. 80 chars) leaving short, weak descriptions that get rewritten anyway.

Detect this on your site

Run a quick scan with the SEO Auditor. The tool surfaces this exact issue with the records and context needed to apply the fix below.

How to fix it

1. 1

   Identify pages without a description

   Crawl the site and flag URLs where the tag is absent, empty, or under 70 characters. The SEO Auditor produces a list grouped by URL template.

2. 2

   Write descriptions in 140-160 characters

   Target 140-160 characters. Shorter wastes SERP real estate; longer gets truncated with an ellipsis. The structure that performs best is: state the problem, preview the answer, hint at depth (numbers, year, format).

3. 3

   Match the user query and intent

   Mirror the language users type. If your target query is 'how to fix robots.txt error', your description should say 'how to fix the robots.txt error' verbatim. Verbatim phrase matches are bolded by Google in the snippet, which lifts CTR.

4. 4

   Generate descriptions programmatically when possible

   For product pages, blog archives, and other templated pages, derive the description from structured data (product name + price + availability for ecommerce; article excerpt + read-time for blog). Generic descriptions are rewritten by Google anyway.

5. 5

   Avoid duplicate descriptions

   Every indexable URL should have a unique description. Duplicates trigger a 'Duplicate meta descriptions' warning in Search Console and signal templated content. See also the duplicate-meta-description fix.

6. 6

   Confirm in View Source

   Verify the description is in the SSR HTML, not injected post-hydration. Googlebot's renderer is more forgiving than it once was, but the initial HTML is still the most reliable signal source.

Example

<meta
  name="description"
  content="Compare 12 espresso machines under $500 on extraction temperature, tank size, and warranty. Updated monthly with current prices and availability."
/>

Description that previews the answer in 158 characters

Related fixes