How to Write Meta Descriptions and Check What Search Engines Show

When you publish a page, you can add a meta description: a short summary in the page’s HTML that search engines may use to describe the page in search results. The text that appears under a result’s title is called a snippet. Search engines choose the displayed text themselves and may use your meta description as the snippet.

Write a specific, accurate summary, then check the page’s HTML, its indexed version, and actual search results. These checks show whether the description is present and what searchers see, but they do not guarantee a particular snippet or prove that an edit caused a change in clicks.

Write a summary that fits the page

A useful meta description tells a searcher what the page offers and helps them decide whether it matches their need. Describe the page that exists, rather than the broader topic or a promise the page does not fulfill. Include specific details when they help distinguish the page, such as its audience, scope, location, or product information.

For example, a page about comparing two services should say what the comparison covers. A generic description such as “Learn everything about services” gives little help to someone deciding which result to open.

Write in natural language and make each description specific to its URL. Google recommends unique, accurate descriptions and says that readable, page-specific summaries are more useful than keyword lists. If your content system generates descriptions automatically, check that the wording still describes each page accurately.

Google sets no character limit that guarantees a description will appear in full; Google shortens snippets as needed, typically to fit the device’s display width. Put the most useful information early and choose clear wording instead of aiming for a fixed character count. The Google snippet guidance explains how descriptions and page content can inform the snippet.

For example, an article about writing meta descriptions could use this illustrative summary:

Learn how meta descriptions work, write page-specific summaries, and check what Google and Bing show. See why snippets change by query and what Search Console can verify.

That wording is a candidate summary, not a promise that a search engine will display it. The page title is a separate element that usually informs the result’s title link; changing the title does not ensure that the snippet will match the meta description.

Check the tag, the indexed page, and the result

Start by checking the page itself. In your content management system or the page’s HTML, confirm that the intended URL has a meta description in the document’s <head>. Make sure the text is current, specific to that page, and not duplicated or replaced by a template. If JavaScript adds or changes metadata, check the rendered page (the page after JavaScript runs) as well as the original HTML.

Then use Google Search Console’s URL Inspection tool to check the URL. Its indexed information describes the version Google last processed, which may not match the page you see now. The live test checks whether Google can access and process the current page, but a successful test does not guarantee indexing or a particular snippet. The URL Inspection documentation explains what each view can confirm.

Finally, search for the page using its title or URL, then try a few relevant queries. Compare the displayed snippet with the meta description and with the page text that answers each query. Record the query and date if you are tracking changes. Google can select different page text for different searches, so one result is only an observation of what appeared in that search context.

For Bing, check the search results directly and use Bing Webmaster Tools to review available page and crawl information. Bing’s guidance on its data-nosnippet attribute describes controls that affect text shown in Bing snippets and AI-generated answers. Those controls concern Bing’s handling of marked page content; they do not establish a universal rule for other search engines.

Interpret checks without overclaiming

If the HTML contains your intended description, the page is offering that text to search engines. It does not show that a search engine has crawled the change or will display it. If Search Console reports the URL as indexed, Google has indexed a version of it. That does not confirm that the URL is currently appearing in results or that any particular snippet will show.

If a manual search displays your meta description, you have confirmed that the search engine used it for that query in the results shown at that time. A different query, device, or result-page context can produce different wording. If Google rewrites the snippet, that alone does not mean the tag is missing or broken: Google builds snippets primarily from page content and uses the meta description when it considers it a better summary for the search.

Search Console’s Performance report shows clicks, impressions, click-through rate (CTR), and average position. CTR is the share of impressions that resulted in clicks. Compare page and query data over a consistent period, and note when you changed the description. If CTR changes afterward, treat that as a reason to investigate, not proof that the description caused the change. The page’s position, the mix of searches that show it, and other changes to the results page also affect clicks. Google’s Search Console performance guidance describes how to use those metrics.

Fix common description problems

A missing, duplicated, generic, or inaccurate description gives search engines a weaker summary to consider and gives searchers less useful information. A string of keywords is difficult to read and does not explain what the page provides. Replace it with a concise description that matches the page’s actual content.

If a recent edit does not appear in search results, first compare the live page with the indexed version in Search Console. If Google has not processed the updated page, the old result may reflect an older version. You can ask Google to index the page after an update, but that does not guarantee an immediate recrawl or a particular snippet.

If the page is not indexed, or Google selected a different canonical URL, focus on that issue before diagnosing the description. A canonical URL is the version Google treats as the main URL when similar or duplicate URLs exist. Changing the description does not fix an indexing problem or Google’s choice of URL.

What meta descriptions mean for AI search

Google says pages must be indexed and eligible to appear with a snippet to be considered for AI Overviews and AI Mode. Its guidance does not prescribe special meta-description wording for these features or say that the description itself guarantees inclusion. Keep the page accessible and make its content useful and accurate; do not treat the description as a way to secure an AI citation. See Google’s guidance on AI features and websites.

Bing’s published guidance says its data-nosnippet attribute can keep marked page sections out of Bing Search snippets and AI-generated answers. That is a Bing-specific control. It does not establish how other search engines use meta descriptions in AI responses or show that changing a description will earn a citation.

Key Takeaways

• Write for the page’s real purpose: Use a clear, accurate summary with details that help the right searcher judge whether the page fits their need.
• Check three separate views: Inspect the live HTML, review Google’s indexed version, and search representative queries to see what appeared.
• Treat snippets as search-engine choices: Google can use page text instead of your description and can vary the snippet by query.
• Read CTR as a signal, not a cause: Compare page and query data, but account for position, query mix, and changes to the search results.
• Keep AI claims narrow: Google’s eligibility guidance concerns indexed pages that can appear with snippets; it does not promise that a meta description will appear in an AI answer.

What I'm building

Delegate tasks. Get software.

Give Vroni a GitHub issue, bug report, spec, or rough idea. It reads the repo, plans the change, writes code, runs checks, and works toward a review-ready pull request.

Take a look at vroni.com