Skip to main content

Web Edge Sessions

Your DNS hasn’t propagated yet, or the record doesn’t match what’s shown. Compare the host and value in the DNS setup panel against your DNS provider, character for character. Watch especially for the doubled-domain issue: many providers, including AWS Route 53, treat the Host/Name field as relative to your domain, which can create a doubled record like _acme-challenge.pages.yourbrand.com.yourbrand.com. Then click Sync again after a few minutes.If a record still shows Not yet found an hour later, and you’ve confirmed it matches exactly, contact allGood support. Include your hostname and which record is failing.
Bot protection provisions only after your domain reaches active and you click Sync. If your domain is already active, click Sync once more. If it’s still propagating, resolve that first — see Set up Web Edge Sessions for your site.
The origin serving that page probably isn’t in your Allowed origins list, or doesn’t match exactly — scheme included, no wildcards. Add the exact origin and try again. See Set up Web Edge Sessions for your site.

Landing Page

Not yet. Robots posture applies to every live landing page on your domain — a per-page override isn’t available. See Manage your landing page settings.
The default subdomain shown on Landing Page settings is read-only there; it’s managed on Web Edge Sessions. Register or update your subdomain from Set up Web Edge Sessions for your site — it will then appear on the Landing Page settings page for reference.

Web Tracking

Start with the browser console on the affected page. An unlisted-origin error there means the fix is adding that origin under Web Edge Sessions — see Set up Web Edge Sessions for your site.
Check that Send events to allGood is on, in the What the tag does section of the Web Tracking page. If it’s already on, events may be stuck waiting on visitor consent. See Set up Web Tracking on your site for how to confirm that. If everything checks out and events still aren’t arriving, contact allGood support with the page URL and your tracking key’s short ID so they can check delivery on their end.
Tracking is off, or your key is wrong or has been revoked. Check that Send events to allGood is on, then re-copy your tag from Set up Web Tracking on your site in case the key changed.
Your site probably routes using the URL hash, which the tag doesn’t treat as navigation. Turn off Automatic page views and record page views from your own route handler instead. See Set up Web Tracking on your site.
Settings changes take a moment to reach allGood’s edge network. Wait for the status chip next to the setting to read Live at the edge — until then, the previous setting is still enforced.

DNS & Propagation

These apply to any DNS record allGood asks you to add — for Web Edge Sessions or for an email domain. Questions specific to email domain verification, or to SPF/DKIM/DMARC/BIMI authentication, are in the Email FAQ instead.
DNS changes are cached at several points — your DNS host, your ISP’s resolver, and any public resolver you check from. Each one only refreshes once its TTL (time to live) expires. Lowering the TTL only speeds up future changes; it won’t speed up a change you already made.To check the record directly instead of a cached copy, purge it at the resolver you’re testing from. Google’s public DNS has a cache-flush tool at dns.google/cache, Cloudflare’s is at one.one.one.one/purge-cache, and OpenDNS has one at cachecheck.opendns.com. Flushing your own computer’s local DNS cache — ipconfig /flushdns on Windows, dscacheutil -flushcache on a Mac — rules out a stale local copy too.
Yes. Cloudflare’s proxy (the orange cloud icon) rewrites a CNAME to point to Cloudflare’s own address instead of the value allGood gave you, so a proxied record never validates. Set every CNAME record allGood asks you to add to DNS only (the gray cloud icon) instead of Proxied.
Yes. MXToolbox runs free lookups for MX, SPF, DMARC, and BIMI records, and flags common configuration mistakes in each. For DKIM specifically, DKIMCore’s tools page checks a DKIM record’s syntax and key strength directly. Both read the same public DNS records anyone on the internet can already see — they don’t change anything on your domain. For a fuller walkthrough of how SPF, DKIM, DMARC, BIMI, and VMC fit together, see Authenticate your sending domain.

Getting Help

If these steps don’t resolve the issue, contact allGood support. Include your hostname for Web Edge Sessions issues, or your tracking key’s short ID and the affected page URL for Web Tracking issues.