Write a meta description as a short, accurate introduction to one specific page. State what readers can find or do there, add a useful detail, and put the essential information early. Check every promise against the page before saving it.
A strong description helps someone judge whether to visit. It doesn't make up for a page that lacks the answer or a service that hasn't confirmed its offer.
Understand what your description can influence

A page can have different snippets for different searches.
The meta description is summary text supplied in a page's metadata. Google's search snippet is the summary Google chooses to display. Google primarily builds snippets from page content and sometimes uses the meta description; the snippet can differ by search query. See Google's snippet guidance.
That distinction matters when reviewing an edit. The description you saved and the text you see in one search result may differ. A search result isn't a direct preview of a CMS field.
The title is a separate part of the result. Google also generates title links using several sources, including the page title and visible headings. Its title-link guidance explains that process.
Write the title and description to work together: let the title identify the page, then use the description to add the detail that helps someone decide whether it fits. Our guide to page titles that match the page covers the title itself.
How long should a meta description be?
Use enough space to explain the page clearly, then remove repetition. Google sets no fixed meta-description length limit and truncates displayed snippets as needed, typically for the device width. See the length guidance.
Treat a length indicator in your editor as a drafting aid. Put the useful information first so the description still makes sense if the end isn't displayed. Don't pad a clear sentence just to fill a recommended range.
Match every promise to something on the page

The description should reflect details the page actually provides.
Before writing, identify the page's purpose and the details that support it. A guide might explain a decision with examples. A category page might let visitors compare products. A service page might invite an enquiry.
Those are different visits. Give each page a description that reflects its actual role. Google recommends descriptions specific to individual pages, rather than repeating the same summary across a site.
The following exercise shows how that works for a fictional notebook business. All page contents, product details, and proposed descriptions are invented for this example. They aren't an audit of a real shop or evidence of search results.
Example 1: a guide to notebook layouts
What the page contains: An explanation of lined, dotted, and plain pages, with sample photographs and examples of using them for notes, sketches, and planning.
Weak draft: “Discover amazing notebooks for every creative journey. Find inspiration and explore our collection today.”
That could introduce almost any page in the shop. It doesn't tell someone that this page helps them choose a layout.
Proposed description:
Compare lined, dotted, and plain notebook pages, with examples that help you choose a layout for notes, sketches, or planning.
The description names the choices and the useful material available. A reader expecting a comparison can recognize it before visiting. It doesn't claim the guide identifies one layout that's best for everyone.
If the guide only names the three layouts without explaining them, the description overpromises. Add the useful comparison or narrow the description to what the page actually provides.
Example 2: a collection of lined notebooks
What the page contains: A collection of lined softcover notebooks. Product cards show sizes, page counts, and cover photographs; individual product pages contain the full specifications.
Weak draft: “Notebooks, lined notebooks, softcover notebooks, writing notebooks, best notebooks.”
The repeated terms give the reader little help choosing a destination.
Proposed description:
Browse lined softcover notebooks and compare their sizes, page counts, and covers. Open a product for its full specifications.
This describes browsing and comparison, which fit the collection page. It doesn't promise a buying guide, a discount, or a delivery service absent from the stated page contents.
The practical check is simple: can a visitor find each named detail where the description suggests they can? If page counts only appear on individual product pages, revise the description or improve the product cards.
Example 3: an enquiry page for custom covers
What the page contains: Photographs of example custom notebook covers and an enquiry form. It doesn't state prices, delivery times, artwork requirements, or an instant ordering process.
Unsupported draft: “Design your notebook online, get an instant price, and enjoy free next-day delivery.”
None of those promises follows from the page inventory.
Proposed description:
Ask about custom notebook covers. View examples and use the enquiry form to discuss your project.
The narrower description is useful because it sets the right expectation: a visitor can inspect examples and enquire. They aren't being sent to a self-service design and checkout tool.
If the business wants to advertise prices or a delivery commitment, confirm the offer and explain it on the service page first. Metadata shouldn't become the only place a material promise appears.
Use the exercise as an editing check
For your own page, write down its purpose, the useful details visible there, and any claims you still need to verify. Draft from the confirmed details.
Then underline the phrases in your description that make a promise: “compare sizes,” “download a checklist,” “book online,” or “see prices.” Open the page and find the evidence for each phrase. A missing promise points to either a copy edit or unfinished page work.
Our guide to writing a useful content brief explains how to record those requirements before writing. If the page's answer itself is hard to find, the answer-first content guide covers that problem.
Check the saved description and the live page

Check the saved copy against the published page.
After saving the copy, verify that it belongs to the intended public page. Don't stop at a successful save message.
Check these points:
- The correct field: You edited the page's meta description, rather than a title, internal note, or unrelated social caption.
- The published value: The live page's metadata contains the saved wording. A developer or site administrator can inspect it if your CMS doesn't expose that check.
- The destination: The description and page still agree about the task, available detail, and next step.
- The neighboring pages: A shared default hasn't replaced distinct descriptions across the site.
- The changing facts: Prices, dates, availability, and service promises remain accurate wherever you've included them.
For the fictional shop, that means checking the guide, collection, and custom-cover enquiry page separately. Three correct sentences in an editorial document don't establish that the right values reached the right URLs.
Read each description once without the page title, then read the pair together. The description should remain understandable on its own and add useful information beside the title. Remove repeated slogans before cutting the detail that distinguishes the page.
Review performance without assuming a cause
Record the previous description, the new wording, and the date it went live. Note any changes to the title or page content made at the same time.
Google Search Console's Performance report shows clicks, impressions, click-through rate, and average position, with page and query views. Use relevant pages and queries over comparable periods to investigate what changed.
Treat a change in click-through rate as an observation to examine. A before-and-after comparison doesn't isolate the description from changes in the queries, title, search position, or the result shown to each person.
If you record a displayed snippet, save the query and date alongside it. One search result doesn't show what every searcher saw. Revisit the page and the saved copy before deciding on another edit.
For the fictional custom-cover page, an accurate enquiry description is a completed improvement in expectation-setting. Claiming that it increased orders would require separate evidence.
