Proxy for Google
Two very different jobs share this name. Running Google Ads accounts, where a proxy earns its money in a way we can defend. And collecting search results, where the first thing to read is the line Google wrote about it in its own robots file.
What Google actually says and counts
- It disallows search in robots.txt, for everyone. Under the wildcard user agent the file carries Disallow: /search, with narrow exceptions that allow only /search/about, /search/howsearchworks and map results. Whatever anyone sells you for scraping results, that line is Google addressing your crawler directly, and no address changes it.
- It counts the Ads API against your developer token, not your connection. Google publishes daily operation limits by access level: 2,880 operations a day against production accounts at Explorer level, 15,000 a day at Basic. The documentation ties usage to your Cloud project.
- It is withdrawing the documented alternative. The Custom Search JSON API is closed to new customers, and Google gives existing customers until 1 January 2027 to move to something else. The official route into search data is being narrowed, not widened.
- It weighs the address on account work, like everyone else. An ads account signing in from a new country gets verification rather than a shrug, and that is where a proxy genuinely changes the outcome.
Which of our products fits which Google job
The first two rows are the ones we can stand behind without qualification.
| What you are doing | What we would use | Why that one |
|---|---|---|
| Running Google Ads accounts | ISP, one address per account, fixed | Accounts hold spend and payment methods. A fixed consumer-looking address is what keeps an account boring, and boring is the goal. |
| An agency with many client accounts | ISP, one per account or per client | The link between accounts you manage is the thing worth breaking. This is the clearest case for buying on this page. |
| An Ads API or Search Console integration | Datacenter IPv4, or nothing | Quotas are counted against your developer token and Cloud project. Buy a cheap stable address only if something on your side needs a fixed one. |
| Collecting search results | Read the robots.txt line first, then decide | Disallow: /search is Google stating its position to automated clients. We would rather point at it than sell around it. |
Rank tracking sits in that last row and we know it is a large part of why people arrive here. Our own position is that the line in the robots file is the relevant fact, and that anyone budgeting for search collection should weigh it and the closing Custom Search API together before deciding.
Setting it up
Google has no proxy setting. The proxy goes into the browser profile holding the account, or into the client making the calls.
# Antidetect browser profile for an ads account, one session number each:
Type SOCKS5
Host proxy.sotaproxy.com
Port 10000
Username login_c_US_s_17_ttl_1h
Password your password
# On ISP, point the profile at the address you own:
Host 198.51.100.20
Port 50100
# An API client through a fixed outbound address:
export HTTPS_PROXY="http://login:password@198.51.100.20:50100"
# Their position on automated clients, in two lines:
curl https://www.google.com/robots.txt | head -20- One address per ads account, and keep it in the country the account bills from. An account that moves country is an account in review.
- Never share an address between a client account and your own. The connection is the easiest link an audit can draw.
- For API work, add a proxy only where you need a predictable outbound address. It changes no quota, because quotas follow the developer token.
- If you are planning any collection, read their robots.txt yourself rather than taking our summary of it. It is short.
What to buy for Google
Ads accounts are the case we can defend without caveats. Prices are entry prices and fall with volume.
ISP proxies
from $2.30 per IP per month, 24 countries
For Google Ads accounts, and for agencies keeping client accounts apart.
- Registered to a consumer provider, so signing in reads as a person rather than a server
- Fixed for the whole term, which is what an account holding spend needs
- Cheap enough per month to give every client account its own
- 24 countries, so a specific billing country may not be covered
- The address is yours alone, so everything from it points at you
Residential proxies
from $2.00 per GB, 220+ countries
For checking how results and ads look from a given country, and for account countries ISP does not cover.
- Household addresses in more countries than anything else we sell
- Country selection down to the market you are buying for
- Billed by traffic, so occasional checks cost very little
- A session ends when the household device drops, one hour at most
- Does not change what the robots file says about automated clients
Datacenter IPv4
from $1.50 per IP per month, 41 countries
For API clients that need one predictable outbound address for an allow-list.
- The cheapest stable address we sell
- Traffic is not metered
- 41 countries
- Recognisable as a datacenter, which is the wrong signal on an ads account
- Moves no quota, because the Ads API counts against your developer token
We have not put a large rotating pool at the top of this page, and that is deliberate. If search collection is your plan, the two documents in the sources below should inform the budget before we do.
Where people go wrong
Budgeting for search collection without reading the robots file
Disallow: /search has been sitting there the whole time, addressed to exactly the software people are about to build. Read it first, then decide, rather than discovering it later.
Assuming the official API is a fallback
The Custom Search JSON API is closed to new customers and existing ones have until 1 January 2027. Planning around it as a safe alternative no longer works.
Buying proxies to raise Ads API quotas
Limits are 2,880 operations a day at Explorer level and 15,000 at Basic, counted against your developer token and Cloud project. Addresses are not in that calculation.
Running an agency from one address
Client accounts sharing a connection is the simplest possible link between businesses that are meant to be unrelated.
What a proxy will not do here
It will not change what Google wrote in its robots file, it will not reopen an API that is closing, it will not raise a quota counted against your developer token, and it will not restore a suspended ads account. What it does is keep ads accounts separate and stable, and let you see a market the way someone in that market sees it. Those are narrow uses and they are real ones. On the collection side we would rather hand you the two documents than the invoice.
Questions people actually type
Can I scrape Google search results with proxies?
The technical answer is beside the point until you have read the relevant line. Google’s own robots.txt carries Disallow: /search for the wildcard user agent, with narrow exceptions for a few informational pages and map results. That is Google telling automated clients its position, and rotating addresses does not engage with it.
What is the official way to get Google search data?
It has been the Custom Search JSON API, at 100 queries a day free and $5 per thousand above that up to 10,000 a day. Note the current status: it is closed to new customers, and existing customers have until 1 January 2027 to move to an alternative.
Do proxies help with Google Ads API limits?
No. Google publishes daily operation limits by access level, 2,880 a day against production accounts at Explorer and 15,000 at Basic, and ties usage to your Cloud project and developer token. More addresses under one token change nothing.
Which proxy is best for Google Ads accounts?
ISP, one per account, in the country the account bills from. The address stays fixed for the term and reads as a consumer connection, which is what keeps an account uninteresting to review.
Can I check search results from another country with a proxy?
Yes, and this is the clean version of the geo question. A residential address in the market you are buying for shows you what someone there sees. It is a check you run occasionally, which is why it costs almost nothing by the gigabyte.
Will a proxy stop my Google Ads account being suspended?
No. Suspensions follow the account, the billing details and the ads. A proxy stops your accounts being linked to one another through the connection, which is a different problem and a real one.
Where the claims above come from
Four primary documents. The first one takes a minute to read and is the most important thing on this page.
- Google robots.txtUnder the wildcard user agent: Disallow: /search, with narrow Allow exceptions for /search/about, /search/howsearchworks and map results. Around 260 lines in total. This is Google addressing automated clients directly, and it is the first thing anyone planning search collection should read.
- Google, Custom Search JSON API overviewThe documented route into search data, with 100 queries a day free and $5 per thousand above that up to 10,000. It also carries the notice that the API is closed to new customers and that existing customers have until 1 January 2027 to move on. Worth reading before treating it as a fallback.
- Google Ads API, quotasDaily operation limits by access level, 2,880 against production accounts at Explorer and 15,000 at Basic, with usage tied to your Google Cloud project. Confirms that no purchase on this page moves an Ads API limit.
- Google Terms of ServiceThe general terms that sit above all of the above. Relevant to anyone deciding what they are permitted to automate rather than what they are technically able to.