Google Ads destination not crawlable Google's ad crawler cannot read your page.

What Google means by "Destination not crawlable"

Destination not crawlable is part of Google's Destination requirements policy. Google's short version: "Google requires that your ad destination and contents are crawlable by Google AdsBot web crawlers."

AdsBot is the crawler Google uses to check ad landing pages. Google says it needs to crawl the page so it can confirm the page is relevant to the ad. If it cannot get in, the ad does not run.

Google lists these as reasons for the disapproval:

• Using robots.txt or a similar exclusion file to block most or all of a site.
• Site settings that allow less crawling than needed for the number of ads you run.

Google says these violations do not cause an instant suspension. You get a warning at least 7 days before any account suspension.

Common landing page causes

Google names two robots.txt causes behind "Destination not crawlable due to robots.txt":

• The robots.txt file disallows crawl access.
• The robots.txt file cannot be reached or times out when Google tries to read it.

On contractor and agency sites, a few things tend to set this off:

• A "discourage search engines" or "hide from search" setting left on after a site was built.
• A staging or test copy of the site that was built to stay private, then used as the live ad page.
• A security plugin, firewall, or bot filter that treats AdsBot as a bad bot.
• A slow or overloaded server that times out when Google asks for robots.txt.
• A big launch with many new ads at once. Google says submitting many ads at once can limit crawling, and click trackers can affect crawl capacity.

The fix order

1. Read your robots.txt. Open yourdomain.com/robots.txt in a browser. Make sure it does not block most of your site, and that it loads quickly.
2. Turn off any "hide from search engines" setting on the page or site your ad uses.
3. Check Search Console. Google suggests using Google Search Console to check accessibility, crawl errors, and crawl rate.
4. Test as AdsBot. Google documents a Chrome DevTools check. Open DevTools, open Network conditions, turn off caching, clear the browser default user agent, and paste the AdsBot user agent string from Google's help page. The page should render the same as it does for you.
5. Ask your developer to let AdsBot in. Google's advice is to make the site open to AdsBot. Have them check firewall and security plugin rules for the AdsBot-Google and AdsBot-Google-Mobile user agents.
6. Spread out big launches. If crawl capacity is the problem, Google suggests splitting ad submissions into smaller batches over several days.

If you cannot fix the site fast, Google's other option is to point the ad at a different page that meets the policy.

Fix the robots.txt first. It is the cause Google names by name, and it is often a single setting. Firewall and plugin rules take longer, so hand those to your developer while you check the rest.

Ask for a new review

Go to Campaigns, then Ads. Hover over the ad or asset, select Edit, make the change, and select Save. Google says the ad is reviewed again automatically, usually within 24 to 48 hours. Check the status on the Ads and assets page.

If you think Google got it wrong, appeal from your account. Go to Troubleshooting in the Tools menu, open Policy manager, select Appeal, and pick "Dispute decision" or "Made changes to comply with policy." Each ad gets 3 appeals. Wait at least 24 hours between appeals for the same ads.

Where ClickMend fits

ClickMend does not read your robots.txt as AdsBot or show your policy status. Clear this disapproval with Search Console and the DevTools test above.

After the fix, a free ClickMend scan of the final URL checks the rest of the page. It gives a 0 to 100 score built on Google PageSpeed Insights performance, Core Web Vitals, SEO basics, best practices, and accessibility. It also checks tracking: whether a Google Ads conversion tag is on the page and actually loaded, and whether the conversion linker is turned off.

Robots settings get flipped by accident when a site is edited or rebuilt. Agencies with many client pages can use weekly landing page monitoring on a paid plan, which sends an alert when a page gets worse. For a full pre-launch list, see the Google Ads landing page audit.

Frequently asked questions