Overview
Domain verification ensures you have permission to crawl a website. This protects site owners from unauthorized scanning and ensures you’re the rightful administrator of domains in your account.Verification is a one-time process. Once verified, a domain remains verified unless you remove it from your account.
How DNS Verification Works
DNS verification requires adding a TXT record to your domain’s DNS settings:| Field | Value |
|---|---|
| Type | TXT |
| Host/Name | _seocrawler-verify |
| Value | seocrawler-verification=<your-token> |
Step-by-Step Instructions
Add TXT Record
Create a new TXT record with:
- Name/Host:
_seocrawler-verify - Value/Content: Your verification token
- TTL: 300 or lowest available
Wait for Propagation
DNS changes can take up to 48 hours to propagate, though most complete within 15 minutes.
Provider-Specific Instructions
- Cloudflare
- GoDaddy
- Namecheap
- AWS Route 53
- Google Domains
- DigitalOcean
Log into Cloudflare
Go to dash.cloudflare.com and select your domain.
Add Record
Click Add record and configure:
| Field | Value |
|---|---|
| Type | TXT |
| Name | _seocrawler-verify |
| Content | seocrawler-verification=<token> |
| TTL | Auto |
Leave the proxy status as DNS only (gray cloud). TXT records aren’t proxied.
Verifying Your DNS Record
Before clicking Verify in SEO Crawler, confirm your DNS record is active:Using Command Line
- macOS/Linux
- Windows
Using Online Tools
Enter_seocrawler-verify.example.com (with your domain) and select TXT record type.
DNS Propagation
DNS changes don’t take effect instantly. When you create a TXT record:- Your DNS provider updates their servers
- The change propagates to DNS resolvers worldwide
- Cached records at intermediate servers expire
Typical Propagation Times
| Provider | Typical Time |
|---|---|
| Cloudflare | 1-5 minutes |
| GoDaddy | 15-30 minutes |
| Namecheap | 15-30 minutes |
| Route 53 | 5-15 minutes |
| Google Domains | 5-15 minutes |
While full global propagation can take up to 48 hours, most verifications succeed within 30 minutes.
Speeding Up Propagation
- Use the lowest TTL available when creating the record
- Clear your local DNS cache before testing
- Use
8.8.8.8or1.1.1.1as DNS resolver for testing
Why Verification is Required
Domain verification serves important purposes:Security
Prevents unauthorized parties from scanning websites they don’t own.
Resource Protection
Ensures crawl resources are used by legitimate owners.
Privacy
Results and reports are only accessible to verified owners.
Trust
Website owners trust that only they can analyze their sites.
Subdomain Verification
For subdomains, add the TXT record at the subdomain level:| Domain | TXT Record Host |
|---|---|
example.com | _seocrawler-verify |
blog.example.com | _seocrawler-verify.blog |
app.example.com | _seocrawler-verify.app |
Keeping Verification Active
You can safely remove the TXT record after verification. We don’t re-check DNS after the initial verification.
- Faster re-verification if you remove and re-add the domain
- Proof of ownership for auditing purposes