Why Google says a destination is not crawlable
Direct answerGoogle disapproves an ad when AdsBot cannot crawl the destination. The destination not crawlable page names robots.txt rules that block most or all of the site, a robots.txt file Google cannot read, and site settings that allow less crawling than the volume of ads requires. A warning is issued at least 7 days before suspension.
What “not crawlable” means on this page
Google says the destination and its contents have to be crawlable so AdsBot can check that the click matches the ad. The disapproval examples are:
- Exclusion files such as robots.txt that restrict the majority or the entirety of the site.
- Site settings that allow less crawling than the number of ads you are running.
The robots.txt section adds two common reasons for the more specific line “Destination not crawlable due to robots.txt”: the file disallows access, or Google could not read it because it was unreachable or the read timed out. The page points site owners to Search Console to confirm pages are accessible and to look for crawl errors or a low crawl rate. It does not publish a sample robots.txt. Do not add a Disallow rule from memory.
Best practice, from the same note: even a site that is not blocking AdsBot can limit crawls without meaning to, especially after a large upload. If you use a click tracker, check whether it is affecting crawl capacity. If the site cannot take the crawl, split the submissions across several days.
Labels that look the same in the account
A page AdsBot can request, and that then returns an error, a login wall, or a redirect loop, is destination not working. A page that loads and is only ads, a copy, or a bridge is insufficient original content. A destination removed from Google Search by a manual action is search spam. Use the label in the disapproval. Opening robots.txt will not fix a manual action.
After AdsBot can read the URL
- Allow AdsBot to fetch the destination. If you cannot change the site, choose a different final URL that is crawlable.
- Edit the ad and save. Re-review typically takes 24–48 hours.
- Appeal if the URL is fetchable and you believe the label is wrong.
Sources
Reviewed October 8, 2026. Policies change. This is not legal advice.
Frequently asked questions
Is a 404 this label?
No. HTTP errors, DNS failures, redirect loops, and login walls are destination not working. This label is about AdsBot being blocked or throttled, most often by robots.txt or by crawl settings that cannot keep up with the ads you submitted.
Can robots.txt block one folder?
The disapproval examples are exclusion files that restrict the majority or the entirety of the site, a robots.txt that disallows access, and a robots.txt Google could not read because it was unreachable or timed out. The page does not say every Disallow line is a violation. If the final URL is inside a blocked path, treat that URL as blocked.
Will editing the headline clear it?
Only if the new destination is one AdsBot can crawl. Google also says a large batch of new ads can exceed crawl capacity, and that a click tracker can affect that capacity. Splitting submissions across several days is the page’s suggestion when the site cannot take the crawl. Re-review after an edit typically takes 24–48 hours.
Check the landing page before the next upload
LaunchGuarding can scan a destination for thin or mismatched content before an ad is submitted. It does not edit robots.txt.