🧭 Overview
If your site started experiencing issues after activating a Search Atlas subscription feature — such as tracking snippets, automation scripts, or plugin integrations — this guide will help you isolate and resolve the cause. In most cases, the issue is a configuration conflict, not the subscription itself, and can be fixed in minutes without cancelling your account.
⚠️ Before You Begin
Identify what changed on your site around the time the issue started. Ask yourself:
- Did the issue begin immediately after installing a Search Atlas snippet or plugin?
- Did it start after a WordPress, CMS, or theme update?
- Is the problem visible on every page, or only specific ones?
- Are you seeing a blank screen, broken layout, redirect loop, or console errors?
Your answers will point you to the most relevant section below.
🧩 Step 1 — Check for Script or Snippet Conflicts
Search Atlas tracking or automation snippets can occasionally conflict with other scripts on your page.
- Open your browser's developer tools (press F12 or right-click → Inspect) and go to the Console tab.
- Reload the affected page and look for red error messages. Note any file names or script URLs mentioned.
- If errors reference a Search Atlas script, temporarily remove the snippet from your site's
<head>or tag manager. - Reload the page. If the issue disappears, the snippet placement or a conflicting third-party script is the cause.
- Re-add the Search Atlas snippet as the last script in your
<head>section to reduce load-order conflicts.
🌐 Step 2 — Rule Out DNS or Domain Configuration Issues
Some subscription features require verified domain connections. Misconfigured DNS records can cause redirects or broken page loads.
- Go to OTTO SEO → SEO Automation in the left sidebar (URL: /seo-automation-v3) and open your project settings.
- Confirm your domain is verified and that no DNS warnings are shown on the dashboard.
- If you recently changed hosting providers or updated nameservers, allow up to 48 hours for full propagation before troubleshooting further.
- Use a free tool such as dnschecker.org to confirm your A records and CNAME records match what Search Atlas expects.
- If DNS records appear incorrect, update them through your domain registrar and re-verify the domain inside the platform.
🔌 Step 3 — Test for Plugin or Theme Compatibility
If your site runs on WordPress or another CMS, a plugin or theme update may have created a conflict.
- Temporarily switch to a default theme (such as Twenty Twenty-Four in WordPress). If the site recovers, your active theme is conflicting with the Search Atlas integration.
- Deactivate all plugins except the Search Atlas plugin. Reload the affected page.
- If the site recovers, reactivate plugins one by one, reloading after each, until the conflict reappears. That plugin is the source.
- Check that the Search Atlas plugin is on its latest version. Go to your CMS plugin manager and update if a newer version is available.
- If a specific plugin conflict is confirmed, contact its developer or reach out to Search Atlas support (see below) for a compatibility fix.
⚡ Step 4 — Check Automation Script Placement
Incorrectly placed automation scripts are a common cause of layout breaks or JavaScript errors.
- Search Atlas snippets should be placed inside the
<head>tag, not inside<body>or injected via footer scripts unless explicitly instructed otherwise. - If you are using Google Tag Manager, confirm the tag is firing on All Pages and that no blocking triggers are preventing it from loading.
- Avoid placing multiple copies of the same snippet on a single page. Duplicate snippet injections can cause infinite loops or duplicate tracking events that stress page rendering.
- After correcting placement, clear your site cache and CDN cache entirely before testing again.
🗂️ Step 5 — Isolate with a Staging Environment
If you cannot identify the conflict on a live site, use a staging or test environment to diagnose safely.
- Clone your live site to a staging URL using your hosting panel or a migration plugin.
- Remove the Search Atlas snippet or plugin from staging and confirm the site loads normally.
- Re-add each Search Atlas component one at a time, testing after each addition, until the issue reappears.
- Document exactly which component triggers the issue. This information will help our technical team resolve it faster.
✅ Quick Checklist Before Escalating
- Browser console checked for script errors
- Search Atlas snippet temporarily removed and site tested
- Snippet placement confirmed inside
<head> - DNS records verified and domain confirmed in the platform
- Plugins and theme tested for conflicts
- Site and CDN cache fully cleared after each change
- No duplicate snippets present on the page
🙋 Still Experiencing Issues?
If you have worked through all the steps above and your site is still affected, our Tier 2 technical support team can perform a deeper investigation, including reviewing your snippet configuration, domain verification status, and integration setup.
If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.
When you reach out, please share the following to speed up resolution: your site URL, a description of the exact issue you see, any browser console errors you noted, and which troubleshooting steps you have already completed. This allows our team to skip straight to advanced diagnostics and resolve your issue as quickly as possible.