Google Ads lets you exclude up to 500 IP addresses per campaign. That sounds generous until you start blocking seriously, at which point it becomes the ceiling that ends the strategy. This article is about what happens when you reach it — and why hitting that wall is usually a sign you are solving the problem from the wrong end.
The limit, and the other constraints around it
The 500 figure is per campaign, not per account, which cuts both ways. Running eight campaigns means maintaining the same exclusion list eight times over, by hand, forever. There is no account-level IP exclusion that cascades down.
You can enter individual addresses or ranges, and a range counts as one entry — which is the only reason the limit is workable at all for anyone doing this at scale.
Why 500 runs out faster than you would expect
Three reasons, all of them structural rather than bad luck.
Residential IP addresses rotate. Most home and mobile connections in India are assigned dynamically. The address you block today may belong to an entirely different household next week — so you are simultaneously failing to block the person you meant to and quietly blocking someone who never did anything.
Mobile networks share addresses at enormous scale. Carrier-grade NAT means thousands of subscribers can appear from one address. Blocking it to stop one bad actor takes out everyone else behind it. On a mobile-first market like India this is not a theoretical risk.
Anyone automating this has more addresses than you have slots. Someone running clicks through a proxy pool can cycle through thousands. You are filling 500 slots by hand while they rotate through inventory they buy by the hour. That arithmetic does not improve.
The cost of a wrong block is invisible. When you exclude an IP, the people behind it simply stop seeing your ads. There is no report of customers you never reached, no complaint, no line item. You will never learn that you blocked a genuine buyer — which is precisely what makes aggressive blocking feel safer than it is.
What to do as you approach the cap
Prune before you add
Exclusions do not expire. A list built over two years is mostly addresses that stopped mattering long ago. Review it periodically and remove anything you added more than a few months back unless you have current evidence — this is also how you avoid slowly blocking a growing slice of the internet.
Block ranges, not addresses
If the traffic clearly originates from hosting or datacenter infrastructure, exclude the range rather than picking off members one at a time. One entry, far broader coverage. Genuine customers rarely browse from a datacenter — see datacenter and VPN traffic in Google Ads leads for how to tell the difference and where that reasoning breaks down.
Reserve the slots for what only they can fix
IP exclusion is the only mechanism that stops the ad being shown, which makes it the right tool for a genuine repeat offender clicking your most expensive keyword. It is the wrong tool for general low-quality traffic, and spending your 500 slots on the latter means having none left for the former.
The two defences that do not have a cap
1. Stop bad submissions at the form
Blocking an IP stops the click. Filtering the submission stops the junk lead. The second scales without limit because it judges behaviour rather than identity: a submission completed faster than a human can type, or one that filled a hidden honeypot field, is rejected no matter which address it came from and no matter how many addresses the sender rotates through.
This does not recover the click cost. It does protect your team's time and stop your pipeline filling with noise, which on most days is the larger of the two costs.
2. Change what your bidding learns from
This is the one that actually ends the problem rather than managing it. If Google Ads optimises toward form submissions, every fake submission is a success signal and your budget follows it. If it optimises toward customers who paid, fake traffic produces nothing the algorithm values, and it stops attracting spend — automatically, at any volume, from any address.
You are not blocking the bad traffic. You are making it irrelevant to where your money goes. That requires reporting real outcomes back to Google, which is what offline conversion imports do and what Claudphic Ads sends automatically when a lead is marked Won.
We ship IP exclusion too, and it is genuinely useful for the specific case it fits. But if you are approaching 500 entries on a campaign, the honest reading is that blocking has stopped being your answer and something upstream needs to change.