Destination responses
HTTP status, MIME and safe redirect chains for a browser and an AdsBot user-agent profile.
Google Ads landing page checker
Use this Google Ads landing page checker to inspect redirects, AdsBot access, tracking signals and rendered page cues before launch.
What the Google Ads landing page checker tests
AdsBot access
Explicit robots rules and observed response differences; no claim to originate from a Google IP.
Click identifiers
A synthetic GET checks whether click and UTM values survive each observed redirect.
Measurement signals
GTM, gtag, GA4, Ads, UET and consent call text, with event execution left unverified.
Rendered review cues
CTA candidates, privacy and contact links, password fields and dialogs for manual inspection.
Device and coverage
Selected-device render, partial evidence and explicit gaps in performance or geographic coverage.
Three-layer sample report
Fictional evidence showing how to interpret each layer.
FAIL · Destination
AdsBot profile received HTTP 403 while browser received 200. Fix: inspect access rules and use Google's own destination test.
PASS · Measurement observation
The synthetic gclid value survived both observed responses. This does not prove a conversion action fires.
REVIEW · Trust
A password field and a dialog were found. Confirm that the offer is available without an unintended login wall or intrusive overlay.
Google Ads destination requirements explained
A destination needs to be reachable and usable. We report response failures with evidence and an official reference. A public response alone cannot establish policy compliance, the accuracy of claims or Google's account-specific decision. Non-HTML destinations need review against applicable policy exceptions.
AdsBot access, redirects, and tracking parameters
We fetch with a browser profile and the selected desktop or mobile AdsBot token. User-agent emulation cannot reproduce Google's network identity. Explicit AdsBot robots groups are evaluated; the global wildcard group is ignored, as described in Google's crawler documentation. We stop after six redirects and report UNKNOWN rather than pretending a longer chain was inspected.
Measurement presence is not conversion proof
GTM container IDs and analytics tags are observable strings. Their presence, consent calls and preserved click IDs do not prove firing order, cookie storage, configured events or attribution. Use Tag Assistant and your account's diagnostics to verify the conversion lifecycle.
How it works and methodology
- Enter the final URL and select a device. Optional country and language annotate your report.
- Compare browser and AdsBot responses, explicit robots rules, a synthetic redirect test and a bounded render.
- Fix observed problems, manually review uncertain cues and recheck after deployment.
Catalog 2026-09-19.1, reviewed 19 September 2026. HTTP and parameter results are observed; DOM trust cues are heuristic. FAIL applies to observed destination failures, while incomplete network or render checks remain UNKNOWN. No field or lab speed result is fabricated when no measurement is available.
Public reports are generated for this response and not archived. Validation values may remain in your session. Page context is stored only through the monitoring continuation. Do not submit secret-bearing URLs. Synthetic parameters contain random test values and may appear in your server logs.
What this preflight cannot predict
No approval, policy clearance, Quality Score or conversion guarantee. We do not access your Ads account, submit forms, test real conversion events or emulate country-specific IPs. Render limits are 80 requests and 10 MB total; blocked resources can leave partial evidence. Known analytics collectors are blocked. A selected-device check does not stand in for both mobile and desktop testing.
Fix examples
Explicit AdsBot block → allow the intended landing path
User-agent: AdsBot-Google
Allow: /offer/
User-agent: AdsBot-Google-Mobile
Allow: /offer/Review all existing rules before changing robots.txt.
Dropped query → preserve the original query in a redirect
return 301 https://example.com$request_uri;This illustrative Nginx redirect preserves path and query. Adapt the destination and test for loops before deployment.
Frequently asked questions
Is this free, and do you need account access?
One-off public checks are free and require no signup or Ads account credentials. Rate limits apply.
Does a pass guarantee Google Ads approval?
No. Only Google can make its policy and account decisions. A pass covers one specific observed check.
Does the click-ID test send a conversion?
The tool makes a separate GET with synthetic values and follows redirects. It does not click buttons, submit forms or intentionally send conversion events. Your server may record the visit.
What data is stored?
The report is not publicly archived. Validation values can remain in your session; project continuation stores page context. Do not enter secrets.
What cannot be checked from a public URL?
Account settings, configured conversion actions, legal adequacy, geographic access and every consent scenario need separate checks.
When should I recheck?
Before launch and after changes to redirects, consent, tags, CDN rules, landing templates or forms. Test both device profiles when they matter to your campaign.