How to Screenshot Google Search Results Without Cookie Banners
Dismiss Google’s consent prompt using its available choices, then capture the visible results. Learn when Incognito helps, how to troubleshoot screenshots, and how to automate clean captures.
To screenshot Google search results without a cookie banner, open Google Search in a regular browser window, use the consent choices Google shows if a prompt appears, wait until the results are visible, and take a screenshot with your device’s built-in capture function. Incognito can provide a fresh local session, but it does not guarantee that the prompt will disappear.
This works for a one-off screenshot. For repeatable captures, use browser automation or a screenshot API; those approaches can wait for the page and save the image without requiring you to capture the screen manually.
1. Take a screenshot manually
- Open Google Search in a regular browser window and run your search.
- If a consent prompt appears, choose from the controls it actually presents. If reject or settings options are shown, you can use them; accepting is not a requirement for following this workflow.
- Wait for the prompt to close and the results to become visible. If it remains, use the page’s available choices or retry in a regular window.
- Use your operating system’s built-in screenshot function to capture the visible page. Screenshot shortcuts vary by device, so use the capture method documented for your operating system.
This captures the visible viewport. If you need results farther down the page, scroll and take additional screenshots, or use a browser’s full-page capture feature if your browser provides one.
2. Should you use Incognito?
Incognito is an optional troubleshooting attempt when you want a separate local session. It is not a banner-removal setting. Google Chrome Help says third-party cookies are blocked by default in Incognito, and Chrome warns that sites may not work as expected when cookies are blocked. That behavior can change how a page works without making its consent prompt go away.
Chrome’s desktop Incognito guidance says the session does not retain site data or a browsing record after all Incognito windows close. During the session, temporary data is available to support site functionality. Incognito does not make browsing anonymous: visited sites and network administrators may still observe activity.
| Workflow | Use it when | What to expect |
|---|---|---|
| Regular window | You want the simplest capture and normal site behavior. | Follow the consent prompt shown, then capture the visible results. |
| Incognito window | You want to try a separate local session. | The consent prompt may still appear, and blocked third-party cookies may affect site behavior. |
Chrome lets you manage third-party cookies and site-specific exceptions, but changing cookie storage is not a documented universal way to dismiss a visible consent prompt. Cookie controls can affect site behavior, so use the choices shown by the page first.
3. Capture Google results with browser automation
For recurring captures, Playwright can open the search page, wait for the results, and save a screenshot. The example below uses Chromium and saves the full page. It does not attempt to accept, reject, or bypass consent. If a prompt blocks the results, stop and handle the choices presented by the page before capturing.
npm install playwright
npx playwright install chromium// save as google-search-shot.mjs
import { chromium } from 'playwright';
const query = process.argv.slice(2).join(' ') || 'website screenshot API';
const url = new URL('https://www.google.com/search');
url.searchParams.set('q', query);
const browser = await chromium.launch({ headless: true });
try {
const page = await browser.newPage({ viewport: { width: 1440, height: 1000 } });
await page.goto(url.toString(), { waitUntil: 'domcontentloaded', timeout: 30000 });
await page.locator('body').waitFor({ state: 'visible', timeout: 10000 });
// Google may show a consent prompt. Do not assume results are unobscured.
await page.screenshot({ path: 'google-results.png', fullPage: true });
} finally {
await browser.close();
}Run it with node google-search-shot.mjs "your search terms". Before relying on unattended captures, inspect the saved image and add an explicit check for the result page state your workflow expects. Search pages and consent prompts can vary by region and session; a successful navigation alone does not prove that the results are unobscured.
4. Or skip the browser setup
ScreenshotNeo is a website screenshot API and MCP server. One GET request can return a screenshot; its clean-capture flow accepts cookie or consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture. Each step can be turned off. Bot checks and CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and the response identifies the page verdict and billing status in headers.
Use the API key from your ScreenshotNeo account. The endpoint and options are documented in the ScreenshotNeo API documentation.
curl -G "https://api.screenshotneo.com/v1/shot" \
-d access_key=YOUR_API_KEY \
--data-urlencode url=https://www.google.com/search?q=website+screenshot+API \
-o google-results.webpThis Python example uses the same endpoint and saves the returned bytes:
import requests
r = requests.get(
"https://api.screenshotneo.com/v1/shot",
params={
"access_key": "YOUR_API_KEY",
"url": "https://www.google.com/search?q=website+screenshot+API",
},
timeout=90,
)
r.raise_for_status()
with open("google-results.webp", "wb") as image:
image.write(r.content)Node.js example using built-in fetch:
const q = new URLSearchParams({
access_key: 'YOUR_API_KEY',
url: 'https://www.google.com/search?q=website+screenshot+API',
});
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
const image = Buffer.from(await res.arrayBuffer());
await import('node:fs/promises').then(fs => fs.writeFile('google-results.webp', image));ScreenshotNeo removes cookie banners, popups, and chat widgets before the shot; bot checks, blank pages, and failed loads are never billed. Its MCP server lets AI agents use take_screenshot, get_page_info, and capture_pdf. The free plan includes 1,000 screenshots a month with no card, and paid plans start at $5 for 3,000 shots. Sign up for 1,000 free screenshots a month, with no card required.
5. Troubleshooting
| Problem | Likely cause | What to do |
|---|---|---|
| The consent prompt still covers results | The prompt is tied to the page, region, or current session; Incognito is not a universal dismissal mechanism. | Use the choices shown by the prompt, wait for it to close, or retry in a regular browser window. |
| The page changes or behaves unexpectedly in Incognito | Third-party cookies are blocked by default in Chrome Incognito, and cookie blocking can affect site behavior. | Try a regular window. Review Chrome’s cookie controls only if you need to troubleshoot a specific site behavior. |
| Android says screenshots are not allowed in Incognito | Chrome Help says an app or organization may disallow screenshots in Incognito. | Open the page in a regular tab and capture it there. |
| The automated screenshot contains the consent panel | Navigation completed, but the prompt was not dismissed and the results may be obscured. | Inspect the output. Handle the prompt’s available choices in a supported workflow, then capture only once results are visible. |
| The screenshot is blank or incomplete | The page may not have finished rendering, or the capture may have happened before its visible content appeared. | Wait for a visible page element and inspect the output. For manual capture, wait until the results are unobscured. |
6. Reliability, privacy, and cost
- Manual capture: best for an occasional screenshot. It has no API usage cost, but requires a person to handle the prompt and confirm the results are visible.
- Incognito: useful for a separate local session, but not a reliable way to remove consent prompts. It changes cookie behavior and is not anonymity.
- Automation: repeatable, but the consent experience and search page can vary. Treat each capture as a result to validate, especially before using it in a report or workflow.
- ScreenshotNeo: billed only for clean shots; the response includes page verdict and billed-status headers. Plans start with 1,000 free shots per month without a card; paid plans begin at $5 for 3,000. Other plans are Growth at $15 for 15,000, Pro at $39 for 60,000, Scale at $99 for 250,000, and Business at $249 for 1,000,000. Yearly billing gives two months free, and every feature is available on every plan.
7. FAQ
Does deleting cookies remove Google’s consent banner?
Do not rely on it as a universal fix. Cookie controls manage stored or third-party cookies; the visible prompt should be handled using the options the page presents.
Does Incognito make my search private from Google?
No. Incognito limits what is retained locally after the session closes, but visited sites and network operators may still observe activity. Google also notes that sites may collect information when you are not signed in.
Can I capture a full Google results page?
For a manual screenshot, capture the visible viewport and scroll for more. With Playwright, set fullPage: true to save the page beyond the initial viewport.
Can a screenshot API guarantee Google will show the same results?
No. This workflow captures the page returned for the request. Results and consent screens can vary by region and session, so inspect captures when consistency matters.
Where can I find ScreenshotNeo’s supported capture options?
See the API documentation for parameters and configuration.
