Meta Description Writing Worksheet Template
Most meta descriptions read like slogans. They could sit on any page, so searchers skip them and Google often ignores them.
This worksheet builds each one from the query, a benefit the page delivers and a fact the page can show. Then it checks the cut.
It also plans for the catch: Google builds most snippets from page content, so the same benefit goes in your intro too.
Inside: a fill-in worksheet, a query and benefit finder, a proof picker, a draft and length check, a snippet log, a CSV header and a fictional example.
- Format
- Editable Word .docx
- Length
- 7 variants · ~7 pages
- Price
- 100% free
- Setup
- Copy or download
Get the editable Word doc in one click.
Free · No signup · Instant download
Meta Description Writing Worksheet Template
Meta description worksheet
One worksheet per page. Work top to bottom: query, benefit, proof, draft, length check, snippet caveat. Do not write the draft until the first three rows are filled.
Page header
- Page URL: [URL]
- Page type: [product, category, guide, service, tool]
- Current meta description: [paste it, or write none]
- Owner: [name] / Due: [date]
| Step | Your entry | Where it comes from | Pass? | Checked by / date |
|---|---|---|---|---|
| 1. Buyer query | [the search the page should win, in the buyer words] | [Search Console query, keyword tool, sales call] | [yes / no] | [name] / [date] |
| 2. Actual benefit | [what the reader gets or can do after this page] | [page section that delivers it] | [yes / no] | [name] / [date] |
| 3. Proof | [a fact the page shows: price, date, count, policy, author] | [where it appears on the page] | [yes / no] | [name] / [date] |
| 4. Draft | [one or two sentences: benefit, proof, next step] | [rows 1 to 3] | [yes / no] | [name] / [date] |
| 5. Length check | [cut point on mobile and desktop preview] | [SERP preview tool] | [yes / no] | [name] / [date] |
| 6. Snippet caveat | [what Google shows today for the query] | [live search, date checked] | [yes / no] | [name] / [date] |
Per-row detail (fill for every page)
- Query intent: [learn, compare, buy, find a place]
- Benefit in page copy too: [yes, in the intro / no, add it]
- Proof still true on: [date you last checked the price, stock or policy]
- Words cut from the draft: [filler, keyword repeats, claims you cannot show]
- Snippet Google used: [your meta description / page text / other]
Next action
- Writer: [name] - action: [fill rows 1 to 4 and send for review] by [date]
- Page owner: [name] - action: confirm the proof in row 3 is on the page and still true
- SEO or developer: [name] - action: publish the tag, then re-check the live snippet on [date]
Completion check
- The query comes from real data, not a guess.
- The benefit is something the page delivers, not a slogan.
- Every fact in the draft is visible on the page today.
- The benefit and proof still read well if the preview cuts the end.
- The description is unique to this page.
- The same benefit and proof also sit in the page intro, in case Google builds the snippet from page text.
Why it works
Each page gets a unique meta description built from its real query, a benefit it delivers and proof it shows, checked for the cut and the live snippet.
- Every claim in the description points to a fact visible on the page, so nothing in the snippet overpromises.
- The draft is previewed on mobile and desktop, so the benefit stays visible wherever the snippet is cut.
- A live snippet log shows when Google uses page text, so you fix the intro too.
7 ready-to-use variants
Copy allMeta Description Worksheet (fill-in)
When to use: One page, six rows: buyer query, actual benefit, proof, draft, length check and snippet caveat, with owners and dates.
Meta description worksheet
One worksheet per page. Work top to bottom: query, benefit, proof, draft, length check, snippet caveat. Do not write the draft until the first three rows are filled.
Page header
- Page URL: [URL]
- Page type: [product, category, guide, service, tool]
- Current meta description: [paste it, or write none]
- Owner: [name] / Due: [date]
| Step | Your entry | Where it comes from | Pass? | Checked by / date |
|---|---|---|---|---|
| 1. Buyer query | [the search the page should win, in the buyer words] | [Search Console query, keyword tool, sales call] | [yes / no] | [name] / [date] |
| 2. Actual benefit | [what the reader gets or can do after this page] | [page section that delivers it] | [yes / no] | [name] / [date] |
| 3. Proof | [a fact the page shows: price, date, count, policy, author] | [where it appears on the page] | [yes / no] | [name] / [date] |
| 4. Draft | [one or two sentences: benefit, proof, next step] | [rows 1 to 3] | [yes / no] | [name] / [date] |
| 5. Length check | [cut point on mobile and desktop preview] | [SERP preview tool] | [yes / no] | [name] / [date] |
| 6. Snippet caveat | [what Google shows today for the query] | [live search, date checked] | [yes / no] | [name] / [date] |
Per-row detail (fill for every page)
- Query intent: [learn, compare, buy, find a place]
- Benefit in page copy too: [yes, in the intro / no, add it]
- Proof still true on: [date you last checked the price, stock or policy]
- Words cut from the draft: [filler, keyword repeats, claims you cannot show]
- Snippet Google used: [your meta description / page text / other]
Next action
- Writer: [name] - action: [fill rows 1 to 4 and send for review] by [date]
- Page owner: [name] - action: confirm the proof in row 3 is on the page and still true
- SEO or developer: [name] - action: publish the tag, then re-check the live snippet on [date]
Completion check
- The query comes from real data, not a guess.
- The benefit is something the page delivers, not a slogan.
- Every fact in the draft is visible on the page today.
- The benefit and proof still read well if the preview cuts the end.
- The description is unique to this page.
- The same benefit and proof also sit in the page intro, in case Google builds the snippet from page text.
Buyer Query and Benefit Finder
When to use: Pick the real query for the page and turn a feature into a benefit the reader gets on that page.
Find the query, then the real benefit
A meta description pitches one page to one search. Start from the query the page already gets or should get.
Where to find the buyer query
- Search Console Performance report, filtered to this page.
- Keyword research for the page topic and its close variants.
- Words customers use in sales calls, chats and reviews.
Pull variants and intent with Keyword Research. Pick one main query per page.
Feature or benefit?
| Feature (weak) | Actual benefit (better) |
|---|---|
| Includes 40 templates | Send your first client report today without building one |
| Open 7 days a week | Book a Sunday appointment |
| Comprehensive guide | Fix the error in four steps, with screenshots |
Benefit test
- Does it answer what the searcher wants from this query?
- Can the reader get it on this page, not three clicks later?
- Would a competitor's page say the exact same thing? If yes, make it more specific.
Benefit statement: After this page, you can [do what] [without what pain].
Proof Picker
When to use: Choose facts the page shows, like price, date, count or policy, and cut claims you cannot back.
Proof you can show
A claim in the snippet must be backed on the page. Google's own guidance suggests a description can bring together facts like author, date or price.
| Proof type | Good for | Check before use |
|---|---|---|
| Price or price from | Products, services | Matches the page and checkout today |
| Date or freshness | Guides, news, events | Visible on the page and true |
| Count (steps, items, locations) | Guides, lists, categories | Count it on the page |
| Policy (returns, shipping, trial) | Stores, SaaS | Same wording as the policy page |
| Author or credential | Advice, health, money topics | Named on the page with a bio |
| What is included | Kits, plans, downloads | Listed on the page |
Cut from the draft
- Best, top, number one, unless you can show the source.
- Ratings or review counts the page does not display.
- Prices or offers that change faster than you update the tag.
- Long strings of keywords. Google says these do not tell users what the page is about.
Check the rest of the page with the Website Audit, so the proof sits in a page that is ready to rank.
Draft Builder and Length Check
When to use: Write the draft benefit first, then check where mobile and desktop previews cut it.
Draft builder and length check
Write the draft from rows 1 to 3. Benefit first, proof second, next step last.
Draft patterns
- [Benefit for the query]. [Proof]. [Next step].
- [Question the searcher has]? [Answer in one line], with [proof].
- [Product or service] for [who]: [benefit]. [Policy or price].
Length and pixel check
Google sets no length limit for meta descriptions. It cuts the snippet as needed, usually to fit the device width.
Width, not a character count, decides the cut. Wide letters and capitals use more space than narrow ones.
- Paste the title and draft into a SERP preview for mobile and desktop.
- Mark where each preview cuts the text.
- Move the benefit and proof before the cut on mobile.
- Read only the visible part. It must still make sense on its own.
Preview the cut with the SERP Simulator, then build the tag with the Meta Tag Generator.
Need formula lists for many page types instead? Use the Meta Title and Description Template.
Snippet Caveat and Live Check
When to use: Plan for Google building the snippet from page text, and log what it shows for the query.
The snippet caveat
Google says snippets are mainly built from page content. It may use your meta description when that describes the page more accurately.
The snippet can change by query. The same page can show your tag for one search and page text for another.
What to do about it
- Put the benefit and proof in the page intro as well, in plain sentences.
- Keep the description unique. Google says identical descriptions across pages do not help.
- Make it truly descriptive of the page, not a sales slogan.
- On large database sites, generate descriptions from page data. Google encourages this when hand-writing is not practical.
Snippet controls (use with care)
| Control | What it does |
|---|---|
| nosnippet meta tag | Stops Google showing a text snippet for the page |
| max-snippet:[number] | Sets a maximum snippet length in characters |
| data-nosnippet attribute | Keeps a part of the page out of snippets |
Live snippet log
- Query searched: [query] on [device] / [date]
- Snippet shown: [paste it]
- Source: [meta description / page text]
- Fix if page text was used: [rewrite intro, add proof, nothing]
Tighten the intro copy with the Content Optimizer. Find missing or duplicate descriptions across the site with the Website Audit.
Spreadsheet Header (CSV)
When to use: A paste-ready header row and allowed values to run the worksheet for many pages in a sheet.
Paste-ready spreadsheet header
Paste this row into cell A1 of Google Sheets or Excel, then split text to columns by comma. One row per page.
page_url,page_type,buyer_query,query_source,benefit,proof,proof_location,proof_checked,draft,mobile_ok,desktop_ok,unique,in_intro,snippet_source,snippet_checked,owner,next_action,status
Allowed values
- page_type: product, category, guide, service, tool, local
- mobile_ok, desktop_ok, unique, in_intro: yes, no
- snippet_source: meta, page-text, not-ranking
- status: draft, in-review, live, re-check
Sheet tips
- Use a COUNTIF on draft to flag duplicates.
- Highlight rows where proof_checked is older than your price or policy update.
- Sort by snippet_source to find pages where Google uses page text.
- Set status to re-check after any price, policy or title change.
Reviewing the whole page, not only the tags? Use the On-Page SEO Checklist Template.
Worked Example (fictional cookware shop)
When to use: A filled-in worksheet for an invented product page, with cut claims, a length fix and an intro rewrite.
Worked example: Pellowmarsh cast-iron restoration kit
Example only. Pellowmarsh is an invented online shop. Its products, prices, URLs, people and dates are made up to show a filled-in worksheet.
- Page URL: /kits/cast-iron-restoration-kit/
- Page type: product
- Current meta description: "Pellowmarsh offers the best cast iron restoration kit. Quality products for all your cookware needs."
- Owner: Mira, content / due 12 Nov
| Step | Entry | Where it comes from | Pass? | Checked by / date |
|---|---|---|---|---|
| 1. Buyer query | cast iron restoration kit | Search Console, top query for the page | Yes | Mira / 6 Nov |
| 2. Actual benefit | Strip rust and re-season a pan in one afternoon, no power drill | Steps section on the page | Yes | Mira / 6 Nov |
| 3. Proof | Kit lists 5 items; 30-day returns | "In the box" list and returns policy | Yes | Joss, store / 6 Nov |
| 4. Draft | Strip rust and re-season a cast iron pan in one afternoon, no power drill. 5 items in the box, 30-day returns. | Rows 1 to 3 | Yes | Mira / 7 Nov |
| 5. Length check | Mobile preview cut after "5 items in the box" | SERP preview | Yes | Mira / 7 Nov |
| 6. Snippet caveat | Google showed a line from the FAQ | Live search, mobile | Fix needed | Mira / 7 Nov |
What the worksheet changed
- "Best" and "quality products" were cut. The page could not show proof for either.
- The mobile cut drops "30-day returns". The benefit and box contents come first, so the visible part still makes sense, and the returns policy also sits in the rewritten intro.
- The product intro was rewritten to carry the same benefit, since Google pulled page text for this query.
- Joss owns the proof row. If the kit contents change, the description is re-checked.
Final description
Strip rust and re-season a cast iron pan in one afternoon, no power drill. 5 items in the box and 30-day returns.
How to use this template
- Pick one page and record the main query it gets from Search Console or keyword research.
- Write the benefit the reader gets on that page, in one plain sentence.
- Find one or two facts the page shows today, like a price, date, count or policy.
- Draft the description: benefit first, proof next, next step last.
- Preview it on mobile and desktop and move key words before the cut.
- Publish, then search the query and log whether Google used your tag or page text.
- If page text was used, rewrite the intro to carry the same benefit and proof.
Pro tips
- Write the description after the page, never before. You need the proof first.
- One page, one main query. A description written for three queries fits none.
- Put the benefit and proof in the first sentence, so a cut still works.
- Keep proof that changes often, like prices, only if someone owns updating it.
- Re-check the live snippet after big page edits. What Google shows can change.
Frequently asked questions
How long should a meta description be?
Google sets no limit. It cuts snippets to fit the device width. Keep the benefit and proof near the start and check the cut in a mobile and desktop preview.
Why does Google ignore my meta description?
Google builds snippets mainly from page content and may use your tag when it describes the page better. The result can change by query.
Is this different from a meta title and description template?
Yes. That template gives formulas by page type. This worksheet walks one page through query, benefit, proof, draft, length and live snippet checks.
Can I use this for hundreds of pages?
Yes. Use the CSV header for one row per page. For large catalogues, Google encourages generating descriptions from page data when hand-writing is not practical.
Do meta descriptions help rankings?
Treat them as a click-through aid, not a ranking lever. A clear, specific snippet helps the searcher pick your page.