(On-page)

Meta Description

A Click Factor, Not a Ranking Factor

A meta description is a meta tag placed in the head of an HTML document to specify the page summary shown as a search result snippet. The bottom line: it is a tag that earns clicks, not one that raises rankings. In a 2009 post on its official blog, Google stated clearly that it uses the description meta tag to display snippets but not to calculate rankings. Google (official)

Rankings come from the title tag and content quality. At a given ranking, the snippet shown on the SERP is what decides whether people actually click. According to a 2019 Backlinko study of about 4 million Google search results, pages with a meta description got about 5.8% more clicks on average than pages without one. Backlinko data

Even When You Write One, Google Rewrites More Than Half

This is where Google’s official guidance and field measurements part ways. The official documentation says a well-written description helps it get shown as is. But large-scale studies of real search results find that many have been replaced with sentences Google pulled from the page body.

Google’s official positionGoogle uses the description meta tag as the snippet when it describes the page more accurately than the body text; snippets are primarily generated from page content. Google (official)
Expert measurementsA study of about 20,000 keywords found Google rewrote about 62.78% of written meta descriptions to match the query. Ahrefs data

The gap comes from different criteria. Google judges by how relevant the snippet is to the query, and the more queries a page ranks for, the harder it is for one pre-written sentence to fit them all. So when Google decides a description is not relevant enough, it pulls a better-matching passage from the body. The same Ahrefs study reported a lower rewrite rate of about 59.65% for high-volume head keywords (fat-head) and a higher rate of about 65.62% for long-tail queries. Ahrefs data The practical takeaway: you don’t need to obsess over a perfect sentence for every page, but the more traffic a key page gets, the more likely your own description is shown as is, so those pages are worth writing by hand.

How to Add It and How Long to Make It

Put exactly one per page inside the head of the HTML document. The markup looks like this.

<head>
    <meta name="description" content="A guide to custom WordPress theme development and SEO consulting. Learn how to design for search performance from the build stage onward.">
</head>

On length, Google’s documentation says there is no fixed limit on meta description length; snippets are truncated in search results as needed, typically to fit the device width. Google (official) So rather than hitting an exact character count, the more important principle is “put the key point first so it still makes sense if cut off.”

CriterionGoogle’s documentation
Length limitNo fixed limit. Snippets are truncated as needed
How it is truncatedTypically to fit the device width (shown shorter on mobile)
Practical rulePut the core message up front so it still makes sense when cut off

Google’s official documentation lays out the writing principles. First, write a sentence that accurately summarizes each page. Second, make it different for every page. Google says that having the same or similar descriptions on every page of a site doesn’t help individual pages appear in search. Google (official) Third, don’t just string keywords together. According to Google, a description that lists keywords doesn’t clearly convey what the page is about, so it is less likely to be shown as a snippet.

Practical Checkpoints at the Build Stage

When you are the one building the site, the meta description is “a matter of building the output structure” before it is “a matter of writing well.” WordPress does not output a meta description by default. A theme or plugin has to output it on the wp_head hook, and you need to design both a per-page field for editors and fallback logic for when it is left empty. On sites with many pages, writing them all by hand is hard. Google says that for large, database-driven sites such as product aggregators, generating descriptions programmatically is appropriate and encouraged. Google (official)

// functions.php - example of outputting a per-page meta description
add_action( 'wp_head', function () {
    if ( ! is_singular() ) {
        return;
    }
    $desc = get_post_meta( get_the_ID(), '_jt_meta_description', true );
    if ( ! $desc ) {
        // If empty, generate a fallback from the excerpt
        $desc = wp_trim_words( get_the_excerpt(), 25, '…' );
    }
    echo '<meta name="description" content="' . esc_attr( $desc ) . '">' . "\n";
} );
  • Always escape the output with esc_attr(). If quotation marks slip in from the content, the attribute breaks and the whole tag becomes useless.
  • Make sure only one is output per page. It is common for the theme and an SEO plugin to each output one, creating duplicates.
  • Split your output rules in line with Google’s recommendation: site-level descriptions for aggregate pages such as the home page and archives, and page-level descriptions for individual content. Avoid giving every page the same text.
  • Adding a character counter to the editor input field noticeably raises quality once the site is in operation.

Common Mistakes

  • Same text on every page – The site introduction is hard-coded in the theme, so every page has the same description. Google says the same or similar descriptions don’t help individual pages appear in search.
  • Keyword lists – It is not a ranking factor, and according to Google’s documentation, descriptions that only list keywords are less likely to be shown as snippets. The standard is a sentence people want to read and click.
  • Exaggerated copy unrelated to the page – This goes against Google’s advice to summarize the page accurately and makes a rewrite more likely.
  • Mistaking it for a ranking factor – Expecting ranking changes from editing the description means the goal is set wrong. The metric to measure is CTR, not rankings.
  • Missing escaping – A build-stage mistake where strings taken from the content are output as is, breaking the markup.

References

Jul.2026By Studio JT

More from On-page

Like this term?
Give it a like!

(230)