Troubleshooting
Verification Failed
What each verification error means and how to fix it.
When you click Verify Now, Sonar fetches your homepage and looks for the tracking snippet. If that check fails, tracking may still be working fine: the real test is whether visits show up.
403 Forbidden
Your site blocked our verification request, usually because of Cloudflare bot protection or a web application firewall.
Fix: Visit your site in a browser, then reload the Sonar dashboard. Real traffic is detected within a few minutes. See 403 Forbidden Error.
Domain not found
The domain doesn't resolve, or it's different from the one your site uses.
Fix: Check the domain in your site settings. Use example.com, not example.com/pages. See Domain Issues.
Connection timeout
Your site took too long to respond.
Fix: Make sure the site loads in a browser, then try again in a moment.
Tracking code not found
We loaded your page, but the snippet wasn't in the HTML.
Fix:
- Make sure the snippet is in the
<head>, and that you copied the whole<script>tag. - Publish your changes and clear any caching plugins or CDN cache.
- If your site renders entirely in JavaScript, the snippet may not appear in the raw HTML. Visit the site and check for real traffic instead.
Still stuck? See Tracking Not Detected.