Describe the useful part first

A short summary should help a reader decide whether opening a page is worth their attention. State the question the page answers, the kind of information it contains, and any important limit. Avoid listing every topic on the site. The summary belongs to one destination.

For a guide to repairing a loose cupboard handle, a useful summary could mention identifying the fixing, tightening it, and checking whether the material is damaged. A vague promise of the 'ultimate solution for everyone' provides less information and is harder to justify. Specific language gives the reader a clearer basis for choosing.

Make the promise verifiable

Compare each phrase with the body. If the summary mentions a checklist, the checklist should be present. If it promises a comparison, the page should explain the alternatives rather than simply name them. Remove numbers, credentials, and claimed results unless they are supported by evidence you can inspect.

A metadata description is one possible source for a search snippet; it is not a command that every search interface must display verbatim. Evaluate whether your description is accurate and useful before interpreting changes in clicks. Query wording, competing results, and the search interface can also influence the observed response.

Use repetition selectively

Shared project wording can provide context, but it should not replace the page-specific explanation. Two pages with different jobs usually deserve different summaries. When two summaries are identical, review the underlying pages before deciding whether to rewrite text or reconsider their separate purposes.