How to Write Meta Descriptions: Examples, Review and Measurement

May 28, 2026

Author: Shusaku Yosa

A meta description should help a reader understand what a page contains. This guide focuses on drafting and editing that copy, rather than the HTML implementation. Start with the actual answer in the body, then express its scope and conditions without inventing offers or results.

Use a Description to Summarize the Page

Use the description to add information that the title cannot carry on its own. A reader should be able to judge whether the page fits the question. Repeating the title and adding “the ultimate guide” contributes little. Google’s snippet guidance describes useful page-specific summaries.

Google may display other text from the page, so the field does not lock every search snippet. Nor should it be treated as a ranking score. The editorial goal is an accurate, useful promise about the page.

Start with the Reader, Question, and Actual Answer

Read the body first and complete four fields. The final field—what the page does not promise—is particularly useful for avoiding invented downloads, guarantees, and automated features. This is a fictional brief for an enquiry-form article.

Field	Example
Reader	A person responsible for an enquiry form
Problem	Unclear completion-rate measurement and input-error priorities
Answer in the body	Definitions for views, starts, accepted submissions, and error checks
Promises absent from the body	Revenue guarantees, downloadable templates, automated diagnosis

A possible description is: “Measure enquiry-form completion by separating views, starts, and successful submissions. Follow a practical process for reviewing input errors and confusing interactions.” It names the work rather than merely praising the article.

Blog Description Examples: Weak vs. Useful

The following is a fictional editing example, not a claim about a published study or its performance. Start with the content summary and explain each change.

Item	Blog example
Body summary	Counts users, sessions, and page views, then explains why daily unique-user counts are not additive
Before	What are unique users? This essential guide explains everything you need to know.
After	Compare unique users, sessions, and page views with one visit example. Learn which GA4 user metric to use and why daily user counts do not simply add up.
Reason	Replaces vague praise with the actual metrics and worked explanation

Do not add an improvement percentage that the article never establishes. Use relevant terms naturally instead of filling the description with variations of the same keyword.

State Conditions Clearly for Services and Products

Service and product readers often need conditions more than promotional adjectives. Both examples below are fictional; the scope and specifications are not descriptions of an actual offer.

Item	Service example	Product example
Body summary	A business consultation, with a preliminary discussion before scope and quotation	A 500mL insulated bottle that must not be put in a dishwasher
Before	The best consulting service solves every problem instantly.	A bestselling premium bottle. Buy now!
After	Explore a business consultation process, from the initial discussion to confirming the scope and quotation. Review who the service is intended for.	Review a 500mL insulated bottle’s dimensions, use, and care. Check purchase considerations, including its dishwasher restriction.
Reason	Removes a guarantee and describes the process	Replaces unsupported popularity with specifications and limitations

If prices or specifications change, assign ownership for updating both the body and the description. Mention a free plan or included asset only when its existence and conditions have been verified.

Write Naturally in Japanese and English

Do not translate to satisfy a Japanese character count. Rebuild the sentence around the natural vocabulary, actions, and conditions of the English page. The purpose is equivalent information, not identical word order.

For example, a Japanese explanation of UU should become an English description using unique users and the relevant GA4 metric names. A service restricted to Japan needs that condition preserved. Keep necessary limits rather than compressing the sentence until its meaning changes. A fixed length does not guarantee complete display or a higher CTR.

Review Before Publishing and Evaluate Afterward

Before publishing, verify that the summary matches the body and that every promise is supported. After publishing, check HTML output separately from observed snippet wording and search metrics.

No invented research, expert review, free asset, or guaranteed result.
Correct page, language, specification, price, and verification date.
Essential information is not hidden behind a long introduction.
Change date and wording are recorded.

Fictional period	Impressions	Clicks	CTR
Before	20	1	5%
After	30	1	About 3.3%

CTR falls in this example while the number of clicks remains the same. It does not establish that the description became worse. Check period lengths, query mix, and positions in the Search Console performance report, and defer conclusions when evidence is sparse. If different text appears in search, use the implementation guide before rewriting the field again.

Fill in the four-part brief and write one description. Use the technical guide if the published description does not appear as expected.