Google Ads has added examples to its “Destination not working” policy guidance, Search Engine Land reported on October 1. Google labels the change a September 2026 documentation update. In the words Search Engine Roundtable quoted from the page: “This does not change enforcement of the policy.”
The new examples cover server and DNS errors, redirect loops, timeouts, private IP addresses, malformed responses, and pages that require a login. Google also cites pages showing “Site Under Construction” and destinations that return 403, 404, or 500 errors to AdsBot, its ad-landing-page crawler.
Search Engine Roundtable, via Barry Schwartz, flagged one added line about asset groups. A campaign with none configured may produce an “invalid final URL” error during setup, even when the destination works.
A landing page that loads in your browser can still fail for AdsBot. Test pages with the AdsBot user agent, and confirm every campaign has an asset group before blaming the page.
Search Engine Land, Anu Adegbola, October 1, 2026, with additional detail from Search Engine Roundtable.
