Google Search Result De-clutter

WHAT IT DOES

This script cleans up Google search results pages by removing or collapsing distracting elements that push organic results down the page. When you search on Google, the results page often includes "People also ask" sections, "Related searches" boxes, knowledge panels on the right side, shopping carousels, video carousels, and featured snippets at the top—all of which can clutter the page and make it harder to find the actual organic search results you're looking for. This script lets you selectively hide any of these elements with a single toggle. The result is a cleaner, more focused search experience that prioritizes organic results. A counter in the bottom-right corner shows how many elements have been hidden, giving you immediate feedback on the script's activity.

WHERE IT RUNS

The script runs on all major Google domains, including .com, .co.uk, .ca, .de, .fr, .it, .es, .com.au, and .co.jp. It works on search results pages (/search?q= or /webhp?q=). It handles both desktop and mobile views, and updates dynamically as new results load via infinite scroll.

HOW TO USE

After installation, the settings panel appears on the left side of the screen with the gear emoji (⚙️). Open the panel to configure the script:

- The "Enable de-cluttering" toggle turns the script on or off. When enabled, selected elements are hidden automatically.

- In the "Elements to Hide" section, toggle individual elements on or off: "People also ask," "Related searches," "Knowledge panel," "Shopping results," "Video carousel," and "Featured snippet."

- Click "Refresh page" to manually re-apply hiding if new elements appear.

- Click "Reset all settings" to restore all defaults.

The script works automatically—just search as usual and the selected elements will be hidden. A small counter in the bottom-right corner shows how many elements were hidden on the current page.

TECHNICAL SECTION — REAL MECHANISM

The script detects search results pages by checking the URL for /search? or ?q=. It identifies distracting elements using Google's CSS class names and DOM structure. "People also ask" sections are detected using selectors like .related-question-pair, .wQiwMc, and .related-question. "Related searches" are found via .suggestions, .related-searches, and .rMhrTe. Knowledge panels are detected with .knowledge-panel, .kp-wholepage, and .kp-header. Shopping results are identified by .sh-dgr, .sh-container, and .sh-sr__shop-results. Video carousels are found using .ULSxyf, .video-carousel, and .n9Gvwd. Featured snippets are detected with .Hc3ZCf, .kno-ftr, and .kp-wholepage. When an element is marked for hiding, the script applies CSS display:none, visibility:hidden, height:0, overflow:hidden, and zero padding/margin/border to completely collapse it from the page layout. Each hidden element is tracked with a WeakSet to avoid duplicate processing and marked with a data attribute for later restoration. The script uses a MutationObserver to watch for new elements being added to the page and queues processing with a debounce to handle rapid DOM mutations during scrolling. The counter is updated in real time as elements are hidden.

THE PANEL

The settings panel is built with BotGentz's BGPanel component. It is draggable via its header, allowing you to reposition it anywhere on the screen. The panel snaps to the left edge by default but can be moved freely. Click the gear emoji to collapse the panel into a small bubble, and click the bubble to expand it again. The panel remembers its position per page session. Press the Escape key to quickly close or minimize the panel. The panel includes a status flash bar that provides visual feedback when settings are changed or actions are performed. All settings save automatically via GM_setValue.

PLEASE NOTE

This script requires the free BotGentz browser extension to run. It does not function as a standalone Chrome extension and does not use chrome.* APIs. Google frequently updates its search results page structure and CSS class names, which may break the selectors used to detect elements. If elements stop being hidden, please check for script updates. The script hides elements visually but does not block them from loading—they are hidden using CSS after they render. The script stores only your preference settings via GM_setValue. No data is sent externally—all data is stored locally in your browser. The script never reads or writes password fields, hidden inputs, or file inputs. All DOM operations use safe methods (style properties, classList) and never use innerHTML.