Suggest meta descriptions that summarize what a page actually offers. Give searchers a clear reason to read without adding unsupported promises.
How to use
Sign in and paste the page content or a precise summary. Add the main question and audience in context. Choose a description that matches the page.
Example
For a guide to freezing herbs, mention preparation and storage steps instead of claiming it covers every preservation method.
FAQ
Will Google use the exact description?
Google can generate a different snippet for a query. Keep descriptions accurate and distinct rather than forcing a fixed character count.
Related tools
A practical task
Summarize the page's actual answer, not the whole site's mission. A tool page description should name its operation and an important distinction, such as local processing or supported input. Leave out a feature that the page does not provide.
Another useful question
Should I repeat the same description on related tools?
No. State the different task and result for each page. Similar subject matter does not make the searcher's intent identical.
Details for interpreting the result
| Detail | Explanation |
|---|---|
| Metadata and page content | A title and description should summarize the page a visitor will actually find. Search engines can choose other wording for a query. Clear, distinct summaries are more useful than repeating a keyword in every available field. |
| Canonical signals | A canonical tag indicates a preferred URL among duplicate or similar pages. It is a signal rather than a command. Internal links, redirects, sitemaps, and actual content should agree about the preferred address. |
| URL components | A URL contains structure such as scheme, host, path, query, and fragment. Characters that separate those parts differ from characters inside a value. Encode the right component rather than transforming the full address blindly. |
| Query values | Query separators connect parameter names and values. An ampersand inside a value must not be confused with the separator between parameters. Build the URL with correct component encoding before sharing it. |
| URL fragments | A fragment points to a location within a resource and is normally not sent as part of the server request. It differs from a query parameter. Changing it does not necessarily create a different document for canonical selection. |
| Structured data | Structured data describes entities and facts in a machine readable format. It must match visible page content. A valid JSON document is not proof of eligibility for a search feature or a promise of richer display. |
| Source boundaries | A summary or rewrite works from the material you provide. A URL alone does not supply the full article in this interface. Include the relevant passage and keep citations attached to the claims they support. |