🧐 Why Duplicate Warnings Appear
Search Atlas detects a duplicate when your WordPress site sends two separate tracking signals at the same time. This happens when both installation methods are active simultaneously:
- The Search Atlas WordPress plugin — installed and active in your WordPress dashboard
- The manual tracking script — added directly to your theme files, a header/footer plugin, or Google Tag Manager
Because each method independently reports data to Search Atlas, the platform flags the account as a duplicate to prevent inflated metrics and reporting errors. Simply clearing cache or running a scan will not remove the warning unless the underlying duplicate installation is fully resolved first.
🗑️ Step 1 — Remove One Installation Method
You only need one active installation method. Choose the option that best fits your workflow and fully remove the other.
Option A: Keep the WordPress plugin, remove the manual script
- Log in to your WordPress dashboard.
- Navigate to Appearance → Theme File Editor (or open your child theme's
header.phpfile). - Locate the Search Atlas tracking script — it typically begins with a comment such as
<!-- Search Atlas -->or contains your unique site token. - Delete the entire script block and save the file.
- If you added the script via a header/footer plugin (e.g., Insert Headers and Footers, WPCode), go to that plugin's settings and delete the Search Atlas script entry.
- If you used Google Tag Manager, open your GTM workspace, find the Search Atlas tag, and either pause or delete it, then publish the updated container.
Option B: Keep the manual script, remove the WordPress plugin
- Log in to your WordPress dashboard.
- Go to Plugins → Installed Plugins.
- Locate the Search Atlas plugin.
- Click Deactivate, then click Delete and confirm.
- Verify no plugin files remain under wp-content/plugins/search-atlas/ via FTP or your hosting file manager if needed.
🗄️ Step 2 — Clear Your Cache
After removing one installation method, clear all cache layers so the change is reflected immediately. Follow the steps for your environment:
- WP Rocket: Go to Settings → WP Rocket and click Clear Cache.
- W3 Total Cache: Go to Performance → Dashboard and click Empty All Caches.
- LiteSpeed Cache: Go to LiteSpeed Cache → Dashboard and click Purge All.
- WP Super Cache: Go to Settings → WP Super Cache → Delete Cache.
- Cloudflare: Log in to Cloudflare, select your domain, go to Caching → Configuration, and click Purge Everything.
- SiteGround (SG Optimizer): Go to SG Optimizer → Supercacher and click Flush Cache.
- WP Engine: In your WP Engine portal, click Flush All Caches from the site's overview page.
- Kinsta: In the Kinsta dashboard, select your site, go to Tools, and click Clear Cache.
If you are unsure which caching layer is active, clear caches at the plugin level, the hosting level, and the CDN level to be thorough.
✅ Step 3 — Verify the Duplicate Warning Is Resolved
Clearing cache alone does not confirm the fix. Complete these verification steps to ensure the duplicate warning is fully removed:
- Log in to Search Atlas and open the affected client account.
- Check whether the Duplicate label is no longer displayed next to the account name. Allow up to 10–15 minutes for the platform to re-evaluate the installation after cache is cleared.
- Go to your WordPress site's front end and open your browser's developer tools (F12 → Network tab or Sources tab). Reload the page and search for Search Atlas in the loaded scripts. Confirm only one instance of the tracking script or plugin output is present.
- Return to Search Atlas, navigate to the affected account's settings, and run a fresh site scan if the option is available. Confirm the scan completes without a duplicate flag.
- If you manage multiple client accounts, repeat steps 1–4 for each account showing the duplicate label, as each WordPress site requires its own fix.
⚠️ Common Mistakes to Avoid
- Deactivating the plugin without deleting it — an inactive plugin can still register with the platform in some configurations. Always delete it if you are switching to the manual script method.
- Clearing only one cache layer when multiple are active — caches stack, so an old cached page can still serve duplicate scripts.
- Assuming the warning clears instantly — the platform may take up to 15 minutes to update after the duplicate is resolved.
💬 Still Seeing the Duplicate Warning?
If you have followed all the steps above and the duplicate label persists after 15 minutes, there may be a secondary script injection point (such as a page builder, third-party plugin, or server-side include) that is not yet resolved. 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.