How to View and Capture Google Search Results from Different Countries

To view Google Search results for another country, change Google’s Region Settings, save the choice, then run your query. If language matters, set the Results Language Filter separately. To preserve the result page, print it to PDF or save the page in Chrome, and record the query, region, language filter, device, browser, and capture time.

Changing the country-code domain alone is not a reliable way to switch Google’s country service. Google’s current instructions point to Search settings for choosing a different region. The setting may not be available in every location. Google’s help page explains how to see results for a different country.

1. Choose a country region in Google Search

On desktop

Open Google Search and go to Search settings.
Find Region Settings.
Select the country or region whose results you want to view.
Save the setting.
Run your query and note the selected region with the results.

Use the country region control even if you can open a country-specific Google domain. Google’s 2017 explanation said that entering a country-code domain no longer switches users to that country’s service; the operational guidance is to select the country in Search settings. Because that explanation is historical, verify the current region setting rather than relying on the old post’s details.

In the Google app on Android

Tap your profile picture or initial.
Tap Settings → Language & region → Search region.
Choose the country or region.

If the region you want is missing, Google says the feature is not available for your location. The Android steps apply to the Google app; they are not a general instruction for every mobile browser.

2. Set language separately from region

Region and language affect different parts of the search experience. The display-language setting changes Google’s interface language and may inform results, but it does not require every result to be in that language. Google uses multiple signals for result languages, including the query, content usefulness, display language, device language preferences, and location.

To filter web results by language, open a results page and choose Tools → Any language, then select the Results Language Filter you need. The control may not appear when English is the only selected language. You can select multiple languages together, but this does not create separate result sets for each language in one selection. The filter may not apply to some Search features, and Google may not be able to classify the language of every page. See Google’s help for language settings and the Results Language Filter.

Control	What it changes	What it does not guarantee
Search region	The country or region used for the Search experience	An identical, fixed result set on every run
Display language	Google interface language; it can also inform results	That all results use that language
Results Language Filter	Filters web results to selected languages when supported	Filtering every feature or every unclassifiable page
Country-code domain	May open a Google domain associated with a country	Switching the country service by itself

Google Programmable Search Engine documents parameters such as gl, hl, lr, and cr. Those belong to that product’s API: gl supplies a country signal that boosts matching origins, hl identifies interface language, lr restricts document language, and cr restricts country-of-origin subcollections. They are not evidence that adding parameters to an ordinary consumer Google Search URL guarantees a particular country result set. See the Programmable Search Engine reference.

3. Make country comparisons repeatable

Search results can vary with location, language, device, and other conditions. For a useful comparison, hold the query and the rest of the setup steady, changing one setting at a time. This makes the comparison interpretable; it does not guarantee Google will return identical results on another run.

Write down the query exactly, including punctuation and spelling.
Choose the region and record it.
Choose and record any Results Language Filter. Leave it unchanged when comparing regions.
Use the same device or app, browser, and capture method for each run.
Record the date and time, including time zone if the record will be shared across locations.
Capture each result page and label the file with region, language, query, and capture date.

To compare language behavior instead, keep the region fixed and vary only the language filter. Keep the query, device or app, and capture method stable in either comparison.

4. Save or print the results page

Save a PDF in Chrome

Open the results page after confirming the selected region and language filter.
Open Chrome’s print dialog using the browser menu or your system’s print command.
Choose Save as PDF as the destination and save the file.
Name the PDF so the region, query, language, and capture date are clear.
Keep a note of the device, browser, and time with the PDF if those details matter to the comparison.

Save a web-page copy in Chrome

Open the results page.
Choose More → More tools → Save page as.
Select a destination and save the page.
Keep the saved page’s accompanying files together if Chrome creates them.

A PDF is convenient to share as one document; a saved page keeps a web-page copy. Neither method is documented as preserving every dynamic Search feature exactly as it appeared on screen. Treat the saved output as a record of what rendered during capture, not proof that results are universal or stable. See Chrome’s help for printing from Chrome and saving a page.

5. Capture a rendered page with a browser

If you need an image rather than a PDF or saved page, a browser automation tool can open the Search results page and save a screenshot. The examples below use Playwright with Chromium. They capture what the browser renders; they do not set Google’s Search region for you. Set and verify the region in Google Search first, then use the same browser profile and conditions for each comparison.

Node.js with Playwright

Install Playwright and its Chromium browser:

npm install playwright
npx playwright install chromium

Save as capture-search.mjs and run with node capture-search.mjs. Replace the query and URL with the search you intend to record.

import { chromium } from 'playwright';

const query = 'electric vehicles';
const searchUrl = `https://www.google.com/search?q=${encodeURIComponent(query)}`;
const browser = await chromium.launch({ headless: true });
const page = await browser.newPage({ viewport: { width: 1440, height: 1000 }, deviceScaleFactor: 1 });

try {
  await page.goto(searchUrl, { waitUntil: 'domcontentloaded', timeout: 60000 });
  await page.screenshot({ path: 'google-results.png', fullPage: true });
  console.log(`Saved results for: ${query}`);
} finally {
  await browser.close();
}

This minimal script does not silently accept consent dialogs or bypass bot checks. If Google presents a consent or verification page, handle it through an authorized interactive session and capture the page only when the intended results are displayed. A new headless browser context may not share your normal browser’s saved region or sign-in state.

Python with Playwright

Install the package and Chromium:

python -m pip install playwright
python -m playwright install chromium

Save as capture_search.py and run python capture_search.py.

from urllib.parse import urlencode
from playwright.sync_api import sync_playwright

query = "electric vehicles"
search_url = "https://www.google.com/search?" + urlencode({"q": query})

with sync_playwright() as p:
    browser = p.chromium.launch(headless=True)
    page = browser.new_page(viewport={"width": 1440, "height": 1000}, device_scale_factor=1)
    try:
        page.goto(search_url, wait_until="domcontentloaded", timeout=60_000)
        page.screenshot(path="google-results.png", full_page=True)
        print(f"Saved results for: {query}")
    finally:
        browser.close()

cURL: retrieve the HTML response

cURL can save the HTTP response body, but it does not render JavaScript or produce a screenshot. Use it when you need the returned HTML for inspection, not as a visual capture of the rendered results page.

curl --location --max-time 60 \
  --output google-results.html \
  --get 'https://www.google.com/search' \
  --data-urlencode 'q=electric vehicles'

Google may return a consent, verification, or other page instead of ordinary search results. A successful HTTP transfer alone does not establish that the intended results were returned.

Or skip the browser setup

ScreenshotNeo captures a URL through one API request. Set Google’s region in Search settings first, then pass the resulting search URL to the API. A screenshot records the page that loads for the API request; it does not configure Google’s country setting for you. See 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=electric%20vehicles -o shot.webp

import requests

url = "https://www.google.com/search?q=electric%20vehicles"
r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": url},
    timeout=90,
)
r.raise_for_status()
open("shot.webp", "wb").write(r.content)

const target = 'https://www.google.com/search?q=electric%20vehicles';
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: target });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', Buffer.from(await res.arrayBuffer())));

Cookie and consent banners, newsletter popups, and chat widgets from supported platforms are handled before the shot; each cleanup step can be turned off.
Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing. Response headers identify the page verdict and whether the shot was billed.
An MCP server provides take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients.
The free plan includes 1,000 screenshots per month with no card. Paid plans start at $5 for 3,000 screenshots; all features are on every plan.

Troubleshooting

Symptom	Likely cause	What to do
The results still look tied to the previous country	The region was not saved, or the country-code domain was mistaken for a region switch.	Return to Search settings, select and save the region, then check it before repeating the query.
The language filter is missing	The filter may not appear when English is the only selected language.	Check the available language settings and remember that display language and the Results Language Filter are separate controls.
Some results are still in another language	The display language does not force all results into one language; the filter has classification and feature limitations.	Apply the Results Language Filter and record it. Interpret exceptions as a limitation of the control, not evidence that region was ignored.
A country is unavailable in Search region	Google says the region control may not be available in some locations.	Use the options available in your location and document that limitation; do not treat a domain change as an equivalent setting.
The saved PDF or page differs from the live results	Search content can be dynamic, and the browser save methods do not promise an exact preservation of every dynamic module.	Capture promptly after verifying the results, use the same method for each comparison, and include the conditions and capture time.
Playwright captures a consent or verification screen	The automated browser received a consent or bot-check page rather than the intended results.	Use a permitted interactive browser session to resolve the page, then capture the visible results. Do not treat a verification page as a search-results capture.
Playwright times out or the screenshot is blank	The page may not have rendered, network access may be unavailable, or the script may have captured before useful content appeared.	Check the URL and network, inspect the page before saving, and use a longer timeout or wait for a visible page element when appropriate.
cURL output is not a screenshot	cURL downloads an HTTP response; it does not render the page.	Open the saved HTML for inspection or use a browser capture for a rendered image.

Performance, reliability, and cost

For a small number of manual comparisons, Search settings plus Chrome’s print or save commands have no additional capture-service setup. Browser automation adds browser installation, page-load time, and maintenance when page behavior changes. cURL is lightweight but provides response HTML rather than a rendered visual record. A screenshot API avoids maintaining browser capture code, but the captured result still depends on the target URL and the conditions Google applies to that request.

For a reliable record, verify that the expected results are visible before saving, note any consent or verification interstitial, and keep the capture conditions beside the file. Google Search output can vary, so a capture is evidence of one rendered page at a particular time and setup. For repeated capture, use consistent viewport dimensions and capture settings. ScreenshotNeo offers caching with a configurable TTL and bulk capture for up to 100 URLs per call; account for cache behavior when deciding whether you need a fresh page. Its response includes billing and page-verdict headers, and failed loads and cache hits are not billed.

FAQ

Does changing Google’s display language change the search country?

No. Use Region Settings to choose the country; display language is a separate setting.

Can one Results Language Filter selection give me separate pages for each language?

No. It can include multiple selected languages together. Run separate captures if you need distinct language comparisons.

Does a screenshot prove what every user in that country sees?

No. It records one rendered page under recorded conditions at one time. It is useful for comparison, not proof of a universal or permanent result set.

Can I use Programmable Search Engine parameters on regular Google Search?

The cited parameters are documented for Programmable Search Engine. They should not be treated as guarantees for ordinary consumer Search results.