How To Turn Off Ai Overview

General
1

I’ve started seeing these new AI Overview boxes at the top of my search results and they’re not helpful for the kind of research I do. I’d rather just see normal, traditional links instead. I’ve tried digging through settings and extensions but can’t find a reliable way to disable or hide AI Overview. Is there any confirmed method, browser setting, extension, or workaround that actually turns this off or at least minimizes it on desktop and mobile?

2

Yeah, this annoyed me too. Short version. There is no single “off” switch for AI Overviews right now, but you have a few workarounds that get close.

  1. Use “Web” filter on Google
    • On desktop, search something.
    • Under the search bar, click “More” or the little tab row.
    • Choose “Web”.
    • That view shows mostly classic blue links and hides most AI stuff.
    • You need to click it each time though, Google does not lock it in by default.

  2. Use a URL parameter
    This is nerdier but more consistent.
    • Go to:
    Google Search
    • “udm=14” is the Web filter.
    • You can set a browser bookmark like:
    Google Search
    • In Chrome, go to Settings → Search engine → Manage search engines.
    • Add a new one, like:
    Name: Google Web
    Keyword: gw
    URL: Google Search
    • Then in the address bar type:
    gw your query
    That forces Web results every time. No AI Overview on top in my tests.

  3. Use alternative frontends or engines
    If you want zero AI stuff:
    • Kagi, DuckDuckGo, Startpage, Brave Search, etc.
    These focus more on classic links. Some still experiment with AI, but they usually let you turn it off.

  4. Disable some Chrome “Search Generative Experience” flags
    This is hit or miss and Google keeps changing it.
    • Go to chrome://flags
    • Search for “AI” or “Generative”.
    • Disable anything related to “Search Generative Experience”.
    This does not always kill AI Overviews, but some people report fewer AI panels.

  5. Use mobile “Web” toggle
    On mobile Google results, there is often a “Web” tab at the top.
    Tap that for pure link view. Again, it does not stick across all searches.

  6. Use a userscript or extension
    If you use desktop Chrome or Firefox.
    • Extensions like “uBlock Origin” can hide AI blocks with custom filters.
    Example uBlock filter (paste into My filters):
    ||google.com/*$remove,xpath=//div[@data-attrid=‘ai_overview’]
    The exact selector might change, you need to tweak it when Google changes markup.
    There are also dedicated “Hide Google AI Overviews” extensions starting to appear in the stores.

Right now Google does not provide a clear “disable AI Overview” setting in regular account or search settings.
The most reliable combo for research work is: custom “udm=14” search engine plus uBlock filter. That keeps your results close to old school Google.

3

Same boat here. AI Overviews are like someone loudly summarizing a book while you’re trying to read it yourself.

@sonhadordobosque already nailed most of the practical stuff (Web tab, udm=14, extensions), so I’ll skip rehashing those and add some different angles:

  1. Use a different Google domain
    Not perfect, but some people see way fewer AI Overviews on country TLDs like:

    • google.co.uk
    • google.ca
    • google.com/ncr (no country redirect)
      Behavior changes constantly, but for certain regions Google rolls out AI stuff slower. Worth trying if you’re stuck with the .com experience.
      You can set one of those as your default search engine instead of .com.

  2. Crank your browser’s “reader” / minimal modes

    • In Firefox, try using the built-in “Reader View” on some result pages opened in a background tab. It strips a lot of cruft.
    • Some minimal-search extensions or CSS “declutter” stylesheets for Google hide all the junk including AI boxes. They’re not always marketed explicitly as “anti AI” but are more “minimal search UI” tools.
      It’s more visual hiding than actually disabling, but for research it can be enough if your eyes never see the box.

  3. Use metasearch as a front door to Google
    Instead of going to Google directly:

    • Use DuckDuckGo, Startpage, or others and set them to open results in Google only when you explicitly click.
    • Startpage in particular literally proxies Google results but without account history, experiments tied to you, etc. The AI rollout there tends to lag, so you sometimes get cleaner SERPs.
      It’s a bit of a 2‑step flow but can keep Google’s bleeding-edge experiments at arm’s length.

  4. Strip personalization & account tie-in
    AI Overviews are partly driven by experiments on “signed-in, fully tracked” users. You can reduce being in the test bucket by:

    • Logging out of your Google account in the browser you use for research.
    • Turning off Web & App Activity, ad personalization, etc. in your Google account, or using a separate “research” profile with minimal history enabled.
      This will not magically remove AI Overviews, but it often reduces how aggressively you get enrolled in new features.

  5. Old-school: use a dedicated “research browser”
    For serious work I ended up doing this:

    • One browser (or profile) is for normal life, signed into Google.
    • Another is for research, with:
      • Different user agent or a user-agent-switcher extension
      • No login to Google
      • Privacy extensions that block most experiments / tracking stuff
        Over time, that profile tends to get cleaner, less “personalized,” and you see fewer experimental UI elements. It’s not perfect, but combined with the Web filter tricks from @sonhadordobosque it’s pretty close to pre‑AI Google.

  6. Slight disagreement on flags
    Chrome flags like “Search Generative Experience” are fun to tinker with, but I honestly wouldn’t rely on them. Google flips these around constantly and sometimes ignoring a flag is part of the test. I treat them as temporary hacks, not a solution. If you want something predictable, I’d rather invest time in a custom search URL + cosmetic blocking in your adblocker than chasing flags.

  7. Mental model shift: treat AI Overview as “noise layer”
    For now, the realistic situation is: Google wants this on by default, users like you want it off, and there is no official “no AI” toggle. So the most future‑proof mindset is:

    • Accept that the AI block is just another noisy widget.
    • Use technical filters (adblock cosmetic rules, custom CSS, user scripts) to hide whatever occupies that top blob, regardless of how they rename or restructure it next month.
      That way, when they tweak markup, you only update a CSS selector or filter, instead of hunting a new hidden setting.

It’s annoying that to get “traditional links” in 2026 you basically have to out-engineer the search page, but right now the combo of: alternative Google domain, no login, privacy-focused profile, and cosmetic blocking tends to keep AI Overviews out of sight most of the time.

4

Short version: you cannot truly “turn off” AI Overview yet, but you can box it in.

A couple of angles that complement what @waldgeist and @sonhadordobosque already covered:

  1. Stop treating Google as a single product
    Use it like a backend instead of your main UI. For research, treat Google as one source in a toolkit, not the front door. For example:

    • Use a metasearch engine for the initial pass.
    • Open Google only in a separate tab when you actually need its index depth.
      This keeps AI Overviews from dominating your whole workflow.

  2. Use query patterns that reduce AI triggers
    Not perfect, but AI Overview appears more on “how to / what is / summary” queries.
    Try:

    • More keyword style: topic filetype:pdf, 'exact phrase' site:.edu, site:arxiv.org
    • Less natural language, more operator-heavy queries.
      AI is tuned to natural language questions, not classic power-user syntax.

  3. Narrow Google to specific sites
    For research on known-good domains, do:

    • site:journalname.com your terms
    • site:.gov your terms
    • site:.edu your terms
      AI Overviews show less often when Google sees the query as “niche / expert” and the result set is mostly long-form or technical docs.

  4. Treat AI Overview like an unreliable secondary source
    If you do glance at it, use it strictly as:

    • A pointer to concepts or keywords you then verify elsewhere.
    • Never as a summary you trust directly.
      That mental shift helps avoid the “someone shouting a summary over your shoulder” problem.

  5. Product-style workaround: custom “classic results” profile
    Think of it as your own private “How To Turn Off Ai Overview” setup:

    • Separate browser profile or portable browser just for research.
    • Not logged into Google.
    • History off or aggressively cleared.
    • Strict content blocker with cosmetic filters for the top block, regardless of name.
      Pros:
    • Very close to old-school link-only search.
    • Reproducible environment for serious research.
    • You can document its quirks once and reuse.
      Cons:
    • Extra friction switching profiles.
    • Needs occasional maintenance when Google changes layout.
    • Not ideal on shared or locked-down machines.

  6. Light disagreement: “Web” tab as a main solution
    I would not build your whole workflow around the Web tab filter. It is an improvement but:

    • It is not sticky everywhere.
    • Google can still experiment inside that mode.
      Better to treat it as a quick fix when you are on someone else’s device, not your primary strategy.

  7. Competitors and overlap

    • @waldgeist focused on domain, privacy, and “noise layer” thinking, which is useful if you like tweaking environments.
    • @sonhadordobosque covered hands-on hacks like URL parameters and extensions.
      The approach above leans more on search practice and query discipline, so you are less dependent on whatever interface experiments Google ships next month.

Right now the realistic target is not “off” but “contained.” A dedicated research profile plus power-user queries keeps AI Overviews mostly out of your way without needing to chase every UI tweak Google makes.