Scan a site
We read your sitemap, pick up to 20 URLs spread across it and request each page once. Expect 20 to 40 seconds. Results include a CSV download.
Enter your domain. The finder samples up to 20 pages from your sitemap and flags descriptions that are missing, under 70 characters, over 160 characters, or identical across pages. Fix the template behind the pattern rather than page by page, then run it again to confirm the spread is clean.
What each flag means
| Flag | Common cause | Fix |
|---|---|---|
| Missing | New post types or templates without an SEO field; pages built in a page builder that skips the plugin's box | Fill the field, or set a template in your SEO plugin that pulls a real excerpt |
| Under 70 characters | A product name or slogan used as the description | Say what the page offers and for whom, with one concrete detail |
| Over 160 characters | Excerpts or intro paragraphs pasted in full | Move the most useful detail to the front; the end is often cut |
| Same text on 2+ pages | Theme falls back to the site tagline; copied templates | Remove the fallback; give each template its own pattern |
The 70 and 160 character lines are practical guides, not Google limits. Google sets no maximum and truncates as needed. In our study of 99 SaaS pricing pages, 59 of 93 descriptions sat between 121 and 160 characters, which is where most results display in full.
How the sample is chosen
Why it is worth the hour
Search Console reports clicks per page, so you can see the effect. A template fix touches every page built from it at once, which makes it one of the few SEO changes that scales without more writing.
Fixing it at the template, by platform
- WordPress: SEO plugins let you set a default description pattern per post type. A pattern that inserts the excerpt beats an empty field, and a hand-written excerpt beats an automatic one.
- Next.js: set
descriptionin each route'sgenerateMetadata, built from the page's own data, and avoid a layout-level description that every page inherits. - Webflow and Framer: CMS collection templates can bind the description to a collection field. Add a dedicated "SEO description" field so editors fill it on purpose.
// Next.js App Router: one description per page, from the page's data
export async function generateMetadata({ params }) {
const plan = await getPlan(params.slug);
return {
title: `${plan.name} plan: features and limits`,
description: `${plan.name} costs $${plan.price}/month and includes ${plan.seats} seats and ${plan.projects} projects.`,
};
}
Once the gaps are filled, write the ones that matter well. Our study of 99 pricing pages shows that only 10 named a price, which leaves room to stand out. Check any single page in detail with the title and meta checker.
Questions people ask
Is a missing meta description bad for rankings?
Google has not said it affects rankings. Its snippet documentation says snippets are created primarily from page content, and that it may use the description when that describes the page better. Missing descriptions cost you control over the snippet, not position.
Why 20 pages and not my whole site?
Twenty URLs spread evenly across the sitemap are enough to show whether a template is broken, and the check stays fast and polite to your server. Problems that show up here usually repeat on every page built from the same template.
Why do many pages share one description?
Usually a theme or plugin fills empty fields with the site tagline. Google's snippet guidance asks for descriptions that describe the specific page, so a repeated tagline is effectively no description.
Can I generate descriptions automatically?
For large catalogues Google's guidance allows programmatic descriptions built from page data. Make them specific: pull real attributes such as price, size or plan limits rather than filling a fixed sentence.
Related
Sources
- Google Search Central: Control your snippets in search results, accessed 2026-11-12.
- Google Search Central: Build and submit a sitemap, accessed 2026-11-12.
- SiteTiller study data: meta descriptions of 99 SaaS pricing pages (CSV), accessed 2026-11-12.