Meta Description Examples (With Title Tags) for 14 Page Types

What a meta description does (and does not do) in 2026

The meta description is the <meta name="description"> tag in your page's HTML. Google may show it as the grey text under your title in search results. Two facts from Google's own documentation shape everything else:

1. Google writes most snippets from your page content. It uses your meta description only when it thinks the description describes the page better than text it could pull from the page (Google Search Central, snippets, updated April 20, 2026).
2. There is no length limit. Google trims snippets to fit the device width. That is why many guides say "about 155 characters": not a rule, just a safe size that usually shows in full.

Titles work the same way. Google builds the "title link" from your <title> element, but also looks at your H1, other headings, og:title and link text pointing at the page, and it may rewrite titles that are vague, stuffed, stale or don't match the page (Google, title links, updated December 10, 2025). In one third-party study of 80,959 titles, Google changed 61.6% of them in some way (Zyppy, 2022).

So the goal isn't a perfect character count. It's a title and description so accurate and specific that Google keeps them, and searchers pick you.

Meta description examples by page type

Every example below comes from the swipe file. The title is 60 characters or fewer and the description 155 or fewer.

The patterns behind the examples

Each example follows a reusable pattern. Square brackets are the blanks you fill in.

The swipe file has a pattern for all 100 examples, including homepages, integrations, alternatives, local businesses and SaaS features.

How to write a meta description that gets clicks: 8 rules

These come from Google's documentation where a source is given, and from field practice where it is not.

1. Write one for each page that matters. Google says identical descriptions across many pages are not helpful. If you can't write them all, start with your top pages (source).
2. Use facts, not adjectives. Price, hours, size, author, date. Google's own example: "Sewing supplies, yarn, colored pencils, sewing machines..." is bad; "Get everything you need to sew your next garment. Open Monday-Friday 8-5pm, located in the Fashion District." is better (source).
3. Front-load it. Phones show less text. Put the point in the first sentence.
4. Answer the question if the query is a question. "Cool-season grass: early fall" earns trust; the click comes from what they still need.
5. Name the fear and remove it. Free returns, posted prices, no card, same-day slots.
6. Match the title to the H1. Google uses headings as a title source; disagreement invites a rewrite (source).
7. Use templates only with real data. Google accepts generated descriptions for large sites if each one is page-specific and readable (source).
8. Never promise what the page doesn't have. Google may rewrite inaccurate titles, and visitors who feel tricked leave.

The swipe file has the full 20 rules, each with a bad and a good example.

Meta description length: how long should it be?

Google sets no limit. In practice, keep descriptions around 120-155 characters so they usually show in full on desktop, and make sure the first 100 or so characters work alone for mobile. Titles: about 50-60 characters. Google trims titles to the device width (roughly 600 pixels on desktop), so a title full of wide letters like W and M is cut sooner than one with narrow letters. If you want to see the cut, paste yours into our SERP preview tool. The full answer, with pixel widths and mobile vs desktop, is in our guide to meta description length.

Which pages should you rewrite first?

Not every page. Rewrite pages that already show up a lot in Google but get few clicks for their position. Google's own advice: a low CTR can mean "users see your page in Search results but don't think it answers their query," and the fix is often a better title and description (Search Console Help).

In Search Console, open Performance > Search results, turn on all four metrics, remove brand searches, open the Pages tab and export. The swipe file includes a CTR gap calculator: paste the export and it compares each page with your own site's average CTR at the same position, then ranks pages by missed clicks. No made-up industry benchmarks. Step by step: how to find low-CTR pages in Search Console.

Before rewriting, search the main query yourself. If an AI Overview, ads or a map pack sits above you, a new title won't win those clicks back.

Who it is for

Store owners, local businesses, SaaS marketers and freelancers who write their own titles and descriptions in WordPress, Shopify, Webflow, Wix or any CMS, and want a pattern instead of a blank box.

Use SEOmatic to run the title and meta description swipe file on my site, mysite.com.

1. Run check_site on mysite.com for a free first look (no sign-in needed).
2. Sign me in with connect_seomatic so you can read my Google Search Console data.
3. Run gsc_insights (action: ctr_outliers) for the last 28 days. These are pages getting far fewer clicks than their position should earn, with brand searches excluded.
4. For each of the top 10 pages, use gsc_performance (action: query_pages) to list the queries that page ranks for, and site_pages (action: analyze) to read its current title, meta description and H1. Quote numbers with their date window.
5. Before proposing any rewrite, look at the results page for the main query. If an AI Overview, ads or another search feature is likely taking the clicks, tell me and skip that page: a new title won't fix it.
6. For the remaining pages, draft a new title (about 60 characters or fewer, matching the H1 and the top query) and meta description (about 155 characters or fewer, with one real fact from the page and one reason to click). Use only facts that are on the page.
7. Stage the drafts with task_manage (action: create), then show_approval_cards so I can review old vs new side by side. Do not approve anything for me.
8. After I approve, remind me to compare clicks for each page in 28 days with gsc_performance (action: compare_periods). If a change does worse, undo it with task_manage (action: rollback).

Rules: never invent prices, ratings or results. If my CMS can't take a field, say so and give me the text to paste instead.