How to Hide Google’s AI Overviews From Your Search Results
Step-by-step ways to hide Google AI Overviews in Chrome, Safari, and mobile—plus troubleshooting tips and what it means for Citation Confidence.
How to Hide Google’s AI Overviews From Your Search Results
Google’s AI Overviews can be useful, but they also add clutter, push organic results down the page, and sometimes feel unreliable for research. The practical reality is: most people can’t “turn off” AI Overviews globally—so the best options are client-side workarounds that hide or collapse the module in your browser (desktop) or reduce how often you encounter it (mobile). This guide walks through the fastest methods (extensions), the cleanest advanced method (uBlock Origin cosmetic filters), mobile-specific options, and a troubleshooting flow that won’t break your SERP.
Hiding AI Overviews changes what you see in your browser—not what Google shows other users. If you’re evaluating visibility or Citation Confidence (the likelihood your content is cited in AI answers), don’t use a “hidden” SERP as your measurement baseline.
Prerequisites: What you can (and can’t) control about AI Overviews
What “hide” means: remove the module in your browser vs. disable Google features
In most regions, Google does not provide a universal, user-facing “off switch” that permanently disables AI Overviews for all searches. So when people say “hide AI Overviews,” they typically mean one of these:
- Client-side hiding: A browser extension or content blocker removes/collapses the AI Overview container using CSS/DOM rules.
- Workflow avoidance: Adjusting how you search (query phrasing) or switching search engines so the module appears less often or not at all.
Wired notes you can sometimes avoid AI summaries by adjusting your query—or by switching search engines when you need a “clean” results page. Source.
Before you start: devices, browsers, and permissions you’ll need
Pick the approach that matches your constraints:
- If you can install extensions: use an AI Overview hiding extension (fastest).
- If you want fewer moving parts: use uBlock Origin cosmetic filters (advanced, very controllable).
- If you’re on iPhone/iPad: Safari content blockers can help, but behavior varies by blocker and by Google markup changes.
Quick definition: AI Overviews in 1–2 sentences
Definition
Google’s AI Overviews are AI-generated summary modules that appear at the top of some search results, often with links/citations to supporting sources. They’re designed to answer the query quickly, but they can reduce attention to traditional organic listings.
Estimated share of searches showing AI Overviews (third-party estimate)
A simplified snapshot based on a third-party claim that AI Overviews expanded to over 70% of searches. Use as directional context; actual rates vary by region, query type, and account state.
Why this matters for teams tracking AI visibility: if AI Overviews appear frequently for your topic, hiding them locally can make you underestimate how often users are seeing AI answers (and whether your pages are being cited).
Method 1 (Fastest): Use a browser extension to hide AI Overviews
Extensions are the quickest approach because they typically ship prebuilt selectors that remove or collapse the AI Overview container. The tradeoff is trust: you’re granting code access to your browsing context.
Prefer extensions that are well-reviewed and transparent about how they work (e.g., simple CSS/DOM hiding). Review permissions carefully, and test first in a separate browser profile or incognito mode (where supported). Avoid tools asking for broad “read and change all data on all websites” permissions unless clearly necessary.
Step-by-step: Chrome/Edge extension install and settings
Choose a reputable extension
Open the Chrome Web Store (Chrome) or Edge Add-ons store (Edge) and search for an extension specifically designed to hide or collapse “AI Overviews” or “SGE/AI summaries.” Prioritize: high install count, recent updates, and clear changelogs.
Install and verify permissions
Click Add to Chrome / Get, then review what sites it can run on. If possible, restrict it to only run on google.com and your local Google domain (e.g., google.co.uk).
Configure behavior (hide vs. collapse)
If the extension offers modes, choose collapse first (safer), then switch to full removal if it doesn’t break other SERP components like Top Stories, People Also Ask, or local packs.
Hard refresh and test
Run a hard refresh (Windows: Ctrl+F5, macOS: Cmd+Shift+R) on a Google results page to ensure cached markup isn’t being used.
Step-by-step: Firefox add-on install and settings
Use Mozilla Add-ons
Open Mozilla Add-ons and search for an add-on that hides AI Overviews/AI summaries on Google. Prefer add-ons with recent maintenance and clear descriptions.
Install and limit site access if possible
Install the add-on, then check its permissions and options. If the add-on supports per-site controls, limit it to Google Search pages only.
Validate with a controlled query set
Test 3–5 queries where you commonly see AI Overviews (often informational “how to…”, “what is…”, “best way to…”). Confirm the module is gone or collapsed and that organic results still render normally.
Verify it worked: what the SERP should look like after hiding the module
- The top-of-page AI Overview block is removed or reduced to a small placeholder you can expand manually.
- Organic results move up, and other SERP features (ads, Top Stories, PAA, local pack) still display.
- Scrolling and clicking results behaves normally (no blank gaps or broken layout).
| Approach | Typical time to implement | Reliability over time | Best for |
|---|---|---|---|
| Dedicated “hide AI Overviews” extension | 2–5 minutes | Medium (depends on maintainer updates when Google markup changes) | Non-technical users who want the fastest fix |
| uBlock Origin cosmetic filters | 5–15 minutes | High (you can self-maintain rules quickly) | Power users who want control + minimal extra extensions |
If you want a solution that is transparent, reversible, and doesn’t rely on a niche extension staying maintained, use filters instead.
Method 2 (No extension): Hide AI Overviews with uBlock Origin filters (advanced but clean)
uBlock Origin can hide page elements using “cosmetic filtering” rules. This is often the most durable approach because you can update selectors yourself when Google changes the SERP markup.
Step-by-step: install uBlock Origin (or similar) and open My filters
Install uBlock Origin from the official store
Install uBlock Origin from your browser’s official add-on store (Chrome/Edge/Firefox). Avoid similarly named clones.
Open the dashboard
Click the uBlock Origin icon → open the dashboard (settings).
Navigate to My filters
Go to the My filters tab. This is where you’ll add cosmetic rules.
Add filters: cosmetic rules to target AI Overview containers
Because Google frequently changes classes/structure, there isn’t a single “forever” selector. The safest workflow is to use uBlock’s element picker to generate a rule, then tighten it so it only applies on Google Search pages.
Trigger an AI Overview on purpose
Search a query that often shows an AI Overview (informational queries are more likely than navigational/transactional).
Use Element Picker
Click uBlock Origin → use the Element picker tool → click the AI Overview container. uBlock will propose a cosmetic filter.
Constrain the rule to Google Search
Ensure the rule begins with a Google domain scope like google.com## so it doesn’t affect other websites.
Add one rule at a time and test
Apply the rule, refresh the SERP, and confirm only the AI Overview is hidden. If other sections disappear, undo the rule and re-pick a narrower element.
Before adding filters, copy your current “My filters” content into a note. If something breaks, you can revert instantly by restoring the previous text and re-applying changes.
Maintain filters: what to do when Google changes markup
When AI Overviews reappear, it usually means Google changed the container structure or identifiers. The fix is straightforward: re-run the element picker on the new container and replace the old rule. In practice, this can happen periodically as Google iterates on the SERP.
Typical filter maintenance cadence (directional estimate)
Directional estimate of how often cosmetic selectors may need updating as Google changes SERP markup. Actual frequency varies by region and account experiments.
If you don’t want to maintain rules at all, you’ll likely prefer Method 1 (an extension that updates selectors for you) or Method 3 (avoidance/fallback workflows on mobile).
Method 3 (Mobile): Reduce AI Overviews in the Google app and mobile browsers
Mobile is trickier because the Google app is a controlled environment and many “hide” techniques depend on browser extensions. Your best options are: (1) use a mobile browser with content blocking, (2) adjust your workflow (queries, signed-out testing), or (3) switch search engines when you need consistency.
Android: Google app settings, Labs/experiments, and search experience controls
Depending on region and account, Google may expose experimental toggles (often under Labs/experiments). If you see an AI-related experiment toggle, turning it off may reduce AI features—but availability is inconsistent and can change without notice.
- Try searching while signed out (or in a private tab) to compare whether your account is enrolled in experiments.
- If you need a consistently “clean” SERP, run searches in a browser where you can apply content blocking rather than inside the Google app.
iPhone/iPad: Safari content blockers and Google app settings
On iOS/iPadOS, Safari supports content blockers via App Store extensions. While these are typically used for ads/trackers, some can also hide page elements. If you rely on this approach, expect occasional maintenance when Google changes markup.
Install a reputable Safari content blocker
Choose a well-known blocker with transparent policies and frequent updates.
Enable it in Safari settings
Go to Settings → Safari → Extensions / Content Blockers (wording varies) and enable the blocker for Safari.
Test on a known AI Overview query
Run the same query set with the blocker on/off to confirm it’s affecting the AI Overview module and not hiding other critical features.
Fallback: use an alternate search front-end or switch default search engine
If your goal is simply to avoid AI Overviews during research, the simplest fallback is to use a different search engine for that session. Wired explicitly calls out switching engines as a straightforward way to avoid AI summaries.
If you’re exploring AI-first browsing experiences, note that some newer browsers integrate AI directly into navigation (which is a different tradeoff than removing AI from Google). For background on one example, see:
Directional comparison: AI Overview appearance by mobile surface
Illustrative comparison for the same query set across common mobile surfaces. Actual results vary by region, account, and time; use this as a testing template rather than a universal truth.
Common mistakes + troubleshooting (so you don’t break your SERP)
Common mistakes: hiding the wrong container, conflicting extensions, cached SERPs
- Conflicting blockers/extensions: two tools try to rewrite the same SERP nodes, causing layout gaps or the module to reappear.
- Over-broad cosmetic rules: a selector hides a parent container that also contains People Also Ask or other modules.
- Cached SERPs or service worker artifacts: you think the rule failed, but you’re viewing a cached variant.
- Signed-in experiments: your account is enrolled in a variant where the AI Overview markup differs from what your rule targets.
Troubleshooting checklist: when AI Overviews still appear
Test in a clean environment
Open a private/incognito window (or a fresh browser profile) and run the same query. This isolates account state and extension conflicts.
Disable all extensions, then re-enable one by one
If you use multiple blockers, disable them all, confirm AI Overviews appear, then enable only one tool at a time until you identify what works (or what conflicts).
Hard refresh + clear site data
Hard refresh the SERP. If it still fails, clear site data for Google (cookies/cache) and retest (note: this may sign you out).
Check domain and language
If your rules are scoped to google.com but you search on google.ca or another ccTLD, the rule won’t apply. Update scope accordingly.
Re-target the element (filters) or update the extension
If you use uBlock filters, re-run the element picker and replace the selector. If you use an extension, check for updates or switch to a maintained alternative.
| Symptom | Likely cause | Fix |
|---|---|---|
| AI Overview still appears after install | Extension not enabled on google domain / wrong domain scope | Enable for the correct Google domain; hard refresh; test signed-out |
| Blank gap where AI Overview was | Rule hides content but doesn’t collapse layout space | Switch to a different selector; try “collapse” mode if available |
| Other SERP features disappear | Selector too broad (parent container) | Undo and re-pick a narrower element; add one rule at a time |
When to stop hiding and start measuring: impact on Citation Confidence workflows
If you’re hiding AI Overviews because they’re distracting during research, that’s fine. But if you’re doing SEO or AI visibility work, hiding them can distort what you’re trying to learn. A better workflow is to keep a controlled query set, test in clean profiles (signed-out + signed-in), and track whether your pages are cited in AI answers directly—separately from your personal browsing preferences.
Key Takeaways
Google generally doesn’t offer a universal “off” switch for AI Overviews; most solutions are client-side hiding or workflow avoidance.
Fastest fix: use a reputable browser extension, but practice permission hygiene and validate with a small query checklist.
Cleanest power-user fix: uBlock Origin cosmetic filters + element picker, with occasional selector maintenance when Google changes markup.
For Citation Confidence and AI-citation work, don’t measure performance on a “hidden” SERP—use controlled tests and track citations directly.
FAQ
Further reading and context: Wired’s walkthrough of avoidance and switching strategies is a useful complement to the technical methods above.
Wired: How to Hide Google’s AI Overviews From Your Search Results
Founder of Geol.ai
Senior builder at the intersection of AI, search, and blockchain. I design and ship agentic systems that automate complex business workflows. On the search side, I’m at the forefront of GEO/AEO (AI SEO), where retrieval, structured data, and entity authority map directly to AI answers and revenue. I’ve authored a whitepaper on this space and road-test ideas currently in production. On the infrastructure side, I integrate LLM pipelines (RAG, vector search, tool calling), data connectors (CRM/ERP/Ads), and observability so teams can trust automation at scale. In crypto, I implement alternative payment rails (on-chain + off-ramp orchestration, stable-value flows, compliance gating) to reduce fees and settlement times versus traditional processors and legacy financial institutions. A true Bitcoin treasury advocate. 18+ years of web dev, SEO, and PPC give me the full stack—from growth strategy to code. I’m hands-on (Vibe coding on Replit/Codex/Cursor) and pragmatic: ship fast, measure impact, iterate. Focus areas: AI workflow automation • GEO/AEO strategy • AI content/retrieval architecture • Data pipelines • On-chain payments • Product-led growth for AI systems Let’s talk if you want: to automate a revenue workflow, make your site/brand “answer-ready” for AI, or stand up crypto payments without breaking compliance or UX.
Related Articles
Google's Gemini 3.1 Pro: Redefining AI Search with 1M Token Context Windows (How to Adapt Your Knowledge Graph Strategy)
Learn how to adapt Knowledge Graph and structured data for Gemini 3.1 Pro’s 1M-token context—improve grounding, retrieval, and AI search visibility.
Perplexity AI's 'Incognito Mode' Under Legal Scrutiny: Privacy Concerns in AI Search (and What It Means for Citation Confidence)
Perplexity AI’s Incognito Mode faces legal scrutiny. Analyze privacy claims, logging risks, and how trust signals affect Citation Confidence in AI search.