# How to Limit Google AI Overviews Without Removing Pages From Search - Link: https://lifeandwork.blog/how-to-limit-google-ai-overviews-without-removing-pages-from-search/ - Published: 2026-10-15T07:44:10-05:00 - Author: Bert Swope ## How to Limit Google AI Summaries Without Removing Your Blog From Search If you want to limit how Google uses text from a blog post in AI Overviews and AI Mode while keeping the page eligible for ordinary Search results, start with a search preview control, not `noindex`. Google applies its search preview controls to its AI features as well as conventional search snippets. The controls differ in scope: `nosnippet` blocks text snippets for the page, `data-nosnippet` excludes selected parts, and `max-snippet` sets a limit on the amount of text Google may show or use. `noindex` has a much broader effect: it tells Google not to include the page in Search results. None of these options guarantees that a page will keep its current rankings, appearance, or traffic. A page that remains indexed may still appear less often, attract fewer clicks, or be interpreted differently in search. ## Choose a control based on what you want to restrict Google’s preview controls are designed to limit the text available for Search previews. Google says these controls also apply to AI Overviews and AI Mode. They do not provide a separate setting that blocks AI summaries while preserving every conventional snippet exactly as it is today. | Control | What it restricts | Effect on ordinary Search | | `nosnippet` | Text snippets for the page | Prevents a text snippet from appearing | | `data-nosnippet` | Text inside selected HTML elements | Leaves other page text available for snippets | | `max-snippet` | The maximum length of text Google may use | Allows a shorter snippet, subject to Google’s discretion | | `noindex` | The page’s inclusion in Search | Removes the page from Search results when Google recrawls it | ### Use `nosnippet` to block text previews across the page Add a robots meta tag to the page’s ``: ```html ``` This prevents Google from showing a text snippet for the page and limits the page text available as direct input to AI Overviews and AI Mode. It also removes the ordinary text preview that might help a searcher decide whether to click. The page can remain indexed and may still appear as a search result, but a result without a text snippet can be less informative. Other display elements, including eligible structured-data features, are a separate matter; `nosnippet` does not disable structured data itself. Use this option when you want the restriction to apply broadly to the page and accept the loss of its ordinary text snippet. If your goal is to protect only a few passages, a page-wide rule is usually more restrictive than necessary. ### Use `data-nosnippet` to exclude selected text The `data-nosnippet` attribute marks part of the page that Google should not use in text snippets or as direct input for its AI search features. Add it to a `span`,` div`, or `section` element: ```html

This passage should not be used in a Google text preview.

``` The excluded text may remain visible to visitors and available to other crawlers. The attribute does not hide content from the page itself, and it is not an access- control or privacy feature. This can suit a post that contains useful explanatory text alongside a passage you do not want quoted in a Google preview. For example, a blogger might exclude a complete answer or a substantial excerpt while leaving the introduction and other material available. Google still decides what to display from the remaining eligible page text, so the resulting snippet may not match a blogger’s preferred description. Place the attribute around the complete passage you intend to exclude. If it is added to a large container, all text inside that element is covered. Check the rendered page to make sure the element exists in the HTML Google can process, especially if a page builder or JavaScript inserts the content. ### Use `max-snippet` to set a length limit The `max-snippet` directive sets a maximum number of characters Google may use for a text snippet: ```html ``` The number is a maximum, not a promise that Google will display a snippet of exactly that length. Google may choose a shorter excerpt or decide that a different search result presentation is more useful. The directive also limits how much page text is available as direct input for AI Overviews and AI Mode. A value of `-1` means there is no limit imposed by this directive. A value of `0` is effectively equivalent to `nosnippet`, so it blocks text snippets rather than allowing a very short one. If you want a limited preview, use a positive value and test the result over time. This control is a reasonable choice when you still want a conventional snippet but want to restrict its length. It does not guarantee that the remaining text will be used in a particular AI feature or that the page will appear there. ## Why `noindex` is different `noindex` is an indexing instruction, not a snippet-length setting. It tells Google not to show the page in Search results after Google crawls and processes the instruction. For example: ```html ``` For a page you want to keep eligible for ordinary results, `noindex` is usually the wrong tool. It can remove the page from the results entirely, along with its search visibility. It is not a way to keep a page in the index while selectively limiting the text Google can preview. The distinction between **noindex vs. nosnippet** is therefore practical: * Choose `nosnippet` if the page may remain in Search, but you do not want Google to show a text preview. * Choose `data-nosnippet` if you want to exclude particular passages while leaving other text eligible. * Choose `max-snippet` if a shorter text preview is acceptable. * Choose `noindex` only if you do not want the page included in Google Search results. Google must be able to crawl a page to read a robots meta tag or a `data-nosnippet` attribute. Blocking the page in `robots.txt` can prevent Google from seeing the instruction. If a page is blocked from crawling, Google may not be able to process the change, even if the directive appears in the site’s code. ## WordPress implementation The simplest WordPress approach is usually to use an SEO plugin’s page-level robots settings, if the plugin provides the control you need. Plugin labels and features vary, so confirm that the setting produces the intended directive in the page’s HTML. Avoid enabling `noindex` when your goal is only to limit a search preview. For a page-wide rule, the rendered `` should contain the equivalent of one of these examples: ```html ``` ```html ``` For a limited section, add the attribute to the relevant HTML element in a block or template that preserves custom HTML: ```html

Text in this section is excluded from Google text previews.

``` Do not paste a robots meta tag into the visible body of a post and expect it to work. It belongs in the document’s ``. If your plugin, theme, or another tool already outputs a robots meta tag, check how it handles multiple directives. Conflicting or duplicated tags can make the result harder to interpret. Changes to theme files and global header templates can affect many pages. Before applying a control sitewide, check whether your intention is to limit previews for one post, a category, or the whole blog. ## Structured data is a separate consideration ![Google AI Overviews controls illustration for How to Limit Google AI Overviews Without Removing Pages From Search](https://i0.wp.com/lifeandwork.blog/wp-content/ uploads/how-to-limit-google-ai-overviews-without-removing-pages-from-1792068169. jpg?resize=790%2C790&ssl=1) Search preview controls do not switch off structured data. If a page has valid structured data and qualifies for a Google search feature, Google may still use that data for an eligible rich result. The data must follow Google’s structured-data policies and match content that visitors can see on the page. This creates an important distinction: a rule that limits ordinary text snippets does not automatically prevent every possible Search presentation. Structured data is not a workaround for controlling AI use, either. Use the preview directive for the text restriction you intend, and treat structured data as a separate feature with its own eligibility and display rules. Google can change which search features appear, and eligibility never guarantees that a rich result will be shown. Review Google’s documentation on [preview controls](https://developers.google.com/search/docs/appearance/snippet) and [structured data](https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data) when a particular feature matters to your site. ## Google-Extended does not control Search previews `Google-Extended` is a separate robots.txt product token. It concerns certain uses of site content for Google’s generative AI systems and services. It is not interchangeable with the Search preview controls, and it is not the way to limit text in ordinary Search snippets, AI Overviews, or AI Mode. A rule for `Google-Extended` does not replace `nosnippet`, `data-nosnippet`, or ` max-snippet`. If your concern is how a page may be previewed in Google Search and its AI search features, use the relevant page-level preview control. If you are considering `Google-Extended`, read Google’s current documentation for the specific services and uses it covers; do not assume it controls Search visibility or ranking. ## Verify the change and request a recrawl After publishing a change, check the page Google can access rather than relying only on what the WordPress editor displays. 1. **Confirm the live HTML.** View the page source or use your site’s inspection tools to check that the robots meta tag is in the `` or that `data-nosnippet` appears on the intended element. 2. **Check for conflicts.** Make sure another plugin or template has not added a contradictory directive, such as `index` alongside an unintended `noindex`. 3. **Run URL Inspection in Search Console.** Enter the exact URL and use the live URL test. Review the page information and rendered HTML where available to confirm that Google can access the page and see the change. 4. **Request indexing.** If the live test is successful, request indexing from URL Inspection. This asks Google to recrawl the URL; it does not force an immediate update or guarantee a particular search appearance. 5. **Allow time, then check again.** Google must recrawl and process the page before the updated control takes effect in Search. The timing varies. Recheck the URL’s indexing status and the page after Google has had time to revisit it. URL Inspection can help verify crawl access and indexing information, but it does not report whether a page will appear in an AI Overview or how much traffic it will receive. Search results also vary by query, location, device, and other factors. A preview directive is a control over eligible text, not a promise of a fixed result. ## Set expectations for visibility and traffic Keeping a page indexed is not the same as keeping its previous visibility. A page with `nosnippet` may still be eligible for ordinary results, but its result will lack a text excerpt. A shorter or selectively restricted preview may also give searchers less information, affecting whether they choose to click. Google’s systems continue to decide which pages to show and how to present them. For many bloggers, `data-nosnippet` offers the narrowest intervention when only a specific passage is a concern. `max-snippet` is useful when a shorter preview is acceptable, while `nosnippet` applies the restriction across the page. Reserve` noindex` for pages you genuinely want removed from Search. After making a change, evaluate both the technical result and the effect on the page’s search performance. ### Share this: * [ Print ](https://lifeandwork.blog/how-to-limit-google-ai-overviews-without-removing-pages-from-search/#print?share=print) * [More](https://lifeandwork.blog/how-to-limit-google-ai-overviews-without-removing-pages-from-search/#) * [[ * [Share on Tumblr](https://www.tumblr.com/share) * [ Email ](https://lifeandwork.blog/how-to-limit-google-ai-overviews-without-removing-pages-from-search/?subject=%5BShared%20Post%5D%20How%20to%20Limit%20Google%20AI%20Overviews%20Without%20Removing%20Pages%20From%20Search&body=https%3A%2F%2Flifeandwork.blog%2Fhow-to-limit-google-ai-overviews-without-removing-pages-from-search%2F&share=email) * [Tweet](https://twitter.com/share) * [ Telegram ](https://lifeandwork.blog/how-to-limit-google-ai-overviews-without-removing-pages-from-search/?share=telegram) * [ WhatsApp ](https://lifeandwork.blog/how-to-limit-google-ai-overviews-without-removing-pages-from-search/?share=jetpack-whatsapp) * [ Reddit ](https://lifeandwork.blog/how-to-limit-google-ai-overviews-without-removing-pages-from-search/?share=reddit) * [ Threads ](https://lifeandwork.blog/how-to-limit-google-ai-overviews-without-removing-pages-from-search/?share=threads) * [ Mastodon ](https://lifeandwork.blog/how-to-limit-google-ai-overviews-without-removing-pages-from-search/?share=mastodon) * [ Nextdoor ](https://lifeandwork.blog/how-to-limit-google-ai-overviews-without-removing-pages-from-search/?share=nextdoor) * [Post](https://x.com/share) * [ Bluesky ](https://lifeandwork.blog/how-to-limit-google-ai-overviews-without-removing-pages-from-search/?share=bluesky) ### _Related_