Features
Domain Ownership Verification
Verify you own your tracked domains to keep scheduled sweeps, indexing submission, and site-scoped API tokens running.
Why Verification Exists
ReachSurge runs scheduled jobs against the domains you add (citation sweeps, competitor tracking, digests, autopilot work) and takes outbound actions on your behalf (indexing submission, serving your content API). Those cost money and touch the claimed domain, so we ask you to prove you control it once, per site. The one-off stuff (crawls, audits, manual checks) works unverified, so the demo and first-run flows are never blocked.
Three Ways to Verify
From any site's page (Websites → your site), pick whichever is easiest:
- Google Search Console: connect GSC and a matching property verifies the site automatically. The strongest method (Google already verified you).
- IndexNow key file: confirm your IndexNow key file in the SEO Agent; a confirmed key counts.
- Verification file: we give you a small text token to serve at a fixed URL on your domain; we fetch it and compare it exactly.
What the Badge Means
A verified site shows how and when it verified (for example, "Verified via Google Search Console · 22 Sep"), never a bare tick. An unverified site shows a named state with the list of what verification unlocks. It is not treated as suspicious, just not yet confirmed.
What Verification Unlocks
Scheduled sweeps: citation tracking, competitor monitoring, the weekly digest, content refresh, autopilot planning and publishing, calendar generation, agentic-readiness scans, brand probes, RSS autoblog generation, SEO-fix autopilot and verification, and Search Console sync. Also automatic indexing submission when you publish, and minting site-scoped Content API tokens (all-sites tokens are unaffected).
When a Badge Can Change
If the evidence a badge was granted on goes away (you disconnect Google Search Console, remove the key file, or edit the site's domain), the badge is re-evaluated honestly: downgraded to whatever evidence still holds, or removed. It never outlives its evidence.
One Honest Gap
If you can inject JavaScript on your site but cannot serve a file at its root (some hosted platforms), none of the three methods fits you yet. DNS verification is on the list; tell us if that is you.