If Google shows a different description for your product or category page, don’t panic or reflexively replace the meta description. Google builds snippets from page content and chooses text that best matches the user’s query and context. That means the same page can show different snippets for different searches or devices. Google’s snippet guidance explains this behaviour and why a single meta description can’t be guaranteed to appear for every query.
Contents
Quick decision
If the snippet is merely different but accurate, leave the meta description in place and focus on improving the page content or title for the queries that matter. Change the meta description now only if the shown snippet is inaccurate, exposes sensitive/incorrect information, or your meta description is obviously duplicated and low-quality.
Why Google may use a different snippet
Google generates snippets dynamically to match the user’s query and context; the engine prefers on-page content it considers more relevant for that search. A meta description is only one signal and will be used when it helps, but there’s no deterministic public rule guaranteeing use for every query or device. For technical details on how snippets are created and presented, see Google’s snippet documentation.
What to do right now
- Confirm the exact snippet and query. Search the query that produces the undesirable snippet and save the SERP screenshot and the query text so you’re clear what you’re fixing.
- Decide if it’s harmful or simply different. If the snippet is factually wrong, legally risky, or reveals private/pricing details you didn’t intend, treat it as urgent.
- Edit the source of the snippet. Update the visible page content (the paragraph or heading quoted in the snippet) and, if helpful, the <meta name=”description”> so it’s accurate and specific. Keep meta descriptions unique per page—duplicate descriptions raise the chance Google will ignore them. The snippet guidance covers this: Google’s snippet guidance.
- Request reindexing in Search Console. After publishing edits, use the URL Inspection tool to view the live page and request indexing so Google can refresh the snippet it pulls. See URL Inspection and reindexing.
- Monitor the results. Watch the Performance report in Search Console for impressions and clicks on the affected query and page; changes can take a few days to appear. Guidance for using Performance reports is available at Search Console Performance report.
Technical controls and examples
If you need to stop specific text appearing in snippets, two HTML-level controls are useful. Use them carefully—these are page-level decisions.
Prevent any snippet or featured-snippet text for a page
Use nosnippet in robots meta
Guaranteed: Google will not show a snippet for that page (includes AI Overviews/AI Mode use). See the robots meta docs: robots meta tag.
Stop a specific paragraph (e.g. private price) appearing
Add data-nosnippet to that element
That element won’t be used in snippets, but Google may use other page text.
Request a maximum snippet length
Use max-snippet:[number] in robots meta
Best-effort limit—device/layout may still truncate differently; max-snippet:0 is equivalent to nosnippet.
Copyable examples (paste into your page head or HTML):
<!-- Block all snippets for this page (add an appropriate robots directive in the page head) -->
<!-- Example: add a googlebot directive that prevents snippets (shown here as a descriptive example rather than a literal head tag) -->
<!-- Limit snippets to 160 characters (best-effort). Use a robots directive in the head such as max-snippet:160 -->
<!-- Example: specify a max-snippet value via a head-level robots directive (not shown literally here) -->
<!-- Prevent a pricing line from being used in snippets -->
<div data-nosnippet>Wholesale price: contact for quote</div>Reference: Google documents the robots directives and the data-nosnippet attribute at Google’s robots meta documentation.
How to test and monitor
- Observe the live SERP for your query. This is the definitive test for that audience and device.
- Use Search Console to inspect the URL. The URL Inspection tool shows how Google currently sees the page; after edits, request indexing. URL Inspection.
- Watch the Performance report. Filter the report by page and query to see whether impressions and clicks change after your edits. Learn how at Search Console Performance report.
- Allow time and record changes. Keep a simple log: date, edit made, query checked, screenshot, and Search Console observations. Small sample sizes can be noisy—recording allows you to see direction over time.
When to use nosnippet vs. editing
Prefer editing the page when the snippet is simply a poor choice of excerpt: better content and a clear meta description often fix the problem without removing all snippets. Use nosnippet only when you must prevent any snippet for a page (for example, private legal text or content you never want to surface in search results).
For broader readiness and snippet strategy (how pages should support AI features and discovery), our short checklist in AI search readiness: what small shops should check first can help prioritise which pages to tidy first.
Decide now: if the snippet is inaccurate or sensitive, fix the page and apply a data-nosnippet or nosnippet as required; if it’s merely different but accurate, improve content and monitor Search Console. Record your action and check back in a week for changes in the Performance report.