Connected subdomain
My subdomain's DNS record shows Not yet found. What do I do?
My subdomain's DNS record shows Not yet found. What do I do?
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 select Sync again after a few minutes.If a record still shows Not yet found an hour later, and it matches exactly, contact allGood support. Include your hostname and which record is failing.A form that requires a bot check won't register on my subdomain. Why?
A form that requires a bot check won't register on my subdomain. Why?
Bot protection provisions only after your domain reaches active and you select Sync. If your domain is already active, select Sync once more. If it is still propagating, resolve that first. See Connect a subdomain.
Visitors' browsers refuse form submissions, or tracking events don't arrive. Why?
Visitors' browsers refuse form submissions, or tracking events don't arrive. Why?
The origin serving that page probably isn’t in your Allowed origins list, or doesn’t match exactly. The scheme counts and there are no wildcards. Add the exact origin and try again. See Set your allowed origins.
Landing Page
Will my preview links show up in search results?
Will my preview links show up in search results?
No. Preview links are never indexed, no matter what your Robots posture is set to. That setting only affects live pages. See Manage your landing page settings.
Can I set a different indexing policy for one specific page?
Can I set a different indexing policy for one specific page?
No. Robots posture applies to every live landing page on your domain. See Manage your landing page settings.
My default subdomain is wrong, or there isn't one. How do I fix it?
My default subdomain is wrong, or there isn't one. How do I fix it?
The default subdomain shown on Landing Page settings is read-only there; it is managed where you connect your subdomain. Register or update it in Connect a subdomain, and it then appears on the Landing Page settings page for reference.
Web Tracking
Page views aren't showing up. Where do I start?
Page views aren't showing up. Where do I start?
Start with the browser console on the affected page. An unlisted-origin error there means the fix is adding that origin. See Set your allowed origins.
There's no console error, and events still aren't arriving. What next?
There's no console error, and events still aren't arriving. What next?
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 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.
My requests are returning a 403 . What does that mean?
My requests are returning a 403 . What does that mean?
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 in case the key changed.
I changed a Web Tracking setting, but it doesn't seem to have taken effect
I changed a Web Tracking setting, but it doesn't seem to have taken effect
Settings changes take a moment to reach all of allGood’s servers. 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 a Web Edge subdomain or an email domain. Questions specific to email domain verification, or to SPF/DKIM/DMARC/BIMI authentication, are in the Email FAQ instead.It's been more than a day and a record still shows Not detected yet. What's wrong?
It's been more than a day and a record still shows Not detected yet. What's wrong?
DNS changes are cached at several points: at 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 rules out a stale local copy too.
I use Cloudflare for DNS. Is there anything different I need to do?
I use Cloudflare for DNS. Is there anything different I need to do?
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.
Is there a tool to check my domain's DNS records directly, without going through allGood?
Is there a tool to check my domain's DNS records directly, without going through allGood?
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.