Skip to main content

​
Overview

Domain verification is straightforward, but DNS can be tricky. This guide covers the most common verification issues and how to resolve them.

​
Common Issues

​
”TXT record not found”

Solution: Wait 15-30 minutes and try again.DNS changes take time to propagate. While some providers update in minutes, others can take longer. Use an online DNS checker to verify the record exists before retrying.
# Check if record exists
dig TXT _seocrawler-verify.example.com +short
Symptoms:
  • Record exists but verification fails
  • Dig returns empty or wrong value
Common mistakes:
MistakeEnteredShould Be
Wrong host_seocrawler-verify.example.com_seocrawler-verify
Added to www_seocrawler-verify.www_seocrawler-verify
Full URL_seocrawler-verify.example.com._seocrawler-verify
Solution: Delete the incorrect record and create a new one with just _seocrawler-verify as the host/name.
Symptoms:
  • All DNS lookups for your domain fail
  • Website isn’t accessible
Causes:
  • Domain nameservers not configured
  • DNS hosting expired
  • Domain not pointing to correct DNS provider
Solution:
  1. Verify your domain’s nameservers are correct
  2. Ensure your DNS hosting is active
  3. Check that DNS zone exists with your provider

​
”Invalid verification token”

Symptoms: Record exists but token doesn’t matchCommon issues:
  • Extra spaces before or after token
  • Missing part of the token
  • Wrong token from different domain
Solution:
  1. Go back to the verification page
  2. Click the Copy button to copy the exact token
  3. Update the TXT record value
The correct format is:
seocrawler-verification=abc123xyz789
Not:
seocrawler-verification= abc123xyz789    (extra space)
seocrawler-verification=abc123           (incomplete)
abc123xyz789                           (missing prefix)
Symptoms: Works in some DNS tools but not othersSome DNS providers require quotes around TXT values, others don’t:
ProviderQuotes Required
Route 53Yes (add them)
CloudflareNo (automatic)
GoDaddyNo
NamecheapNo
If your provider auto-adds quotes, don’t add extra ones:❌ ""seocrawler-verification=abc123""
✅ seocrawler-verification=abc123

​
”Verification timed out”

Symptoms: Verification works sometimes but not consistentlySolution:
  1. Wait a few minutes and try again
  2. If persistent, check with your DNS provider for issues
  3. Try lowering the TTL on the record
Symptoms: Local dig works but verification failsPossible cause: Your DNS provider may be blocking queries from certain IPs.Solution:
  • Check DNS provider firewall settings
  • Ensure no geographic restrictions on DNS queries
  • Try a different DNS provider if issues persist

​
Debugging Steps

​
Step 1: Verify Record Exists

Check that your TXT record is queryable:

​
Step 2: Compare Token Values

If the record exists, verify the value matches:
  1. Copy the value from your DNS provider
  2. Copy the expected value from SEO Crawler
  3. Compare character by character
Use a diff tool or this command: 
# Compare strings (should output nothing if identical)
diff <(echo "copied-from-dns") <(echo "copied-from-lhm")

​
Step 3: Check DNS Provider Settings

Verify your DNS configuration:
CheckWhat to Look For
NameserversDomain points to correct DNS provider
Zone existsDNS zone is active for your domain
Record savedTXT record shows in your DNS dashboard
No conflictsNo duplicate or conflicting TXT records

​
Step 4: Test from Multiple Locations

DNS can propagate at different speeds globally: 
# Test from different DNS servers
dig TXT _seocrawler-verify.example.com @8.8.8.8 +short      # Google
dig TXT _seocrawler-verify.example.com @1.1.1.1 +short      # Cloudflare
dig TXT _seocrawler-verify.example.com @9.9.9.9 +short      # Quad9
dig TXT _seocrawler-verify.example.com @208.67.222.222 +short # OpenDNS
If some return the record and others don’t, propagation is still in progress.

​
Provider-Specific Issues

TXT records shouldn’t be proxied (orange cloud). If you see proxy options:
  1. Set to DNS only (gray cloud)
  2. TXT records are informational and don’t need proxying
GoDaddy sometimes has UI issues:
  1. Clear browser cache and retry
  2. Try a different browser
  3. Wait 5 minutes before checking if record saved
  4. Contact GoDaddy support if issues persist
If using Namecheap’s BasicDNS:
  1. Some advanced records may not be supported
  2. Consider using Namecheap’s PremiumDNS or third-party DNS
  3. Ensure you’re editing the correct domain
Route 53 requires specific formatting:
  • TXT values must be in quotes
  • Multiple strings need separate quotes
  • Don’t escape internal characters
Correct: "seocrawler-verification=abc123"
Wrong: seocrawler-verification=abc123
In cPanel hosting:
  1. Look for Zone Editor or DNS Zone Editor
  2. Not to be confused with Simple DNS Zone Editor (may lack TXT support)
  3. If neither works, contact your host about DNS access

​
Alternative Verification Methods

If DNS verification isn’t working, contact support for alternative options:

HTML File Upload

Upload a verification file to your domain root.

Meta Tag

Add a meta tag to your homepage HTML.
Alternative methods require contacting support. DNS verification is preferred and most secure.

​
Still Having Issues?

If you’ve tried everything above:
1

Gather Information

Collect:
  • Your domain name
  • Screenshot of your DNS settings
  • Output of dig TXT _seocrawler-verify.yourdomain.com
  • Your DNS provider name
2

Contact Support

Email support@seocrawler.app with:
  • Subject: “DNS Verification Issue - [your domain]”
  • Information gathered above
  • Steps you’ve already tried
3

Expect Response

Our team typically responds within 2 hours during business hours.

​
Next Steps

DNS Verification Guide

Review the step-by-step verification process.

Start Crawling

Successfully verified? Start your first crawl!