Custom Domains
Serve sitemaps from your own subdomain with automatic SSL
Why Custom Domains?
We recommend serving your sitemap from a subdomain of your main website (e.g., sitemap.yoursite.com) for several reasons:
- Brand consistency - Your sitemap URL matches your domain
- Trust signals - Search engines see it as part of your site
- Professional appearance - Looks better than a third-party URL
- No vendor lock-in - Change providers without updating submissions
Setup Guide
1. Choose your subdomain
Common choices include:
sitemap.yoursite.com(most common)xml.yoursite.comseo.yoursite.com
Tip: We recommend using "sitemap" as it's descriptive and widely recognized.
2. Add CNAME record
Log into your DNS provider and add a CNAME record:
| Type | Name | Target |
|---|---|---|
| CNAME | sitemap | cname.sitemaphost.app |
DNS propagation typically takes a few minutes but can take up to 24 hours.
3. Add domain in dashboard
In your SitemapHost dashboard:
- Go to your project settings
- Click "Add Custom Domain"
- Enter your full subdomain (e.g., sitemap.yoursite.com)
- Click "Verify"
4. Wait for SSL provisioning
Once DNS is verified, we automatically provision an SSL certificate. This usually takes 1-5 minutes.
You'll see a green checkmark when your domain is fully configured and HTTPS is active.
SSL Certificates
All custom domains receive free SSL certificates, automatically provisioned and renewed. We use Cloudflare for SaaS to manage certificates, providing:
- Automatic provisioning - Certificate issued within minutes
- Auto-renewal - Renewed automatically before expiration
- Modern TLS - TLS 1.2 and 1.3 support
- Universal compatibility - Works with all browsers
You don't need to purchase or configure SSL certificates. Everything is handled automatically once your DNS is properly configured.
DNS Provider Examples
Cloudflare
- Go to DNS settings for your domain
- Click "Add record"
- Select Type: CNAME
- Name:
sitemap - Target:
cname.sitemaphost.app - Proxy status: DNS only (grey cloud)
- Click "Save"
Important for Cloudflare users: Make sure the proxy is disabled (grey cloud, not orange). Our SSL provisioning requires direct DNS resolution.
Namecheap
- Go to Domain List, then Manage, then Advanced DNS
- Click "Add New Record"
- Type: CNAME Record
- Host:
sitemap - Value:
cname.sitemaphost.app - TTL: Automatic
- Click the checkmark to save
GoDaddy
- Go to My Products, then DNS
- Click "Add" under Records
- Type: CNAME
- Name:
sitemap - Value:
cname.sitemaphost.app - TTL: Default
- Click "Save"
Verifying DNS Configuration
You can verify your DNS is correctly configured using these commands:
# Check CNAME record
dig sitemap.yoursite.com CNAME
# Or use nslookup
nslookup -type=CNAME sitemap.yoursite.comYou should see cname.sitemaphost.app in the response.
Troubleshooting
Domain not verifying -- DNS changes can take up to 24 hours to propagate. Wait and try again, or check that your CNAME record is correctly configured.
SSL certificate not provisioning -- Ensure DNS proxy is disabled (Cloudflare users) and the CNAME points to the correct target. SSL provisioning requires direct DNS resolution.
Getting 522 or timeout errors -- This usually indicates DNS isn't properly configured. Double-check your CNAME record and wait for propagation to complete.
Next Steps
- Global CDN - Learn about CDN caching and performance
- DNS Troubleshooting - Fix common DNS configuration issues