In this guide, you’ll learn how to manually inspect and validate the Search Atlas pixel installation, and troubleshoot common issues reported in diagnostics.
🔍 What to do
🔍 What to do
Use your browser's Developer Tools to locate and validate the presence and configuration of the pixel on the customer’s website.
🌟 Why it matters
🌟 Why it matters
An incorrectly installed pixel can block pageviews, conversions, or dynamic optimization features. Validating the install ensures reliable performance and accurate reporting.
🛠️ How to do it
🛠️ How to do it
Run a diagnostic scan in the customer dashboard. This checks for presence, visibility, and script consistency.
Open the website in Incognito mode.
Use Developer Tools (right-click > Inspect > Elements).
Search for the Pixel UUID (use CMD+F or CTRL+F). This helps locate the script block or embedded tag.
Confirm presence of both scripts:
One in Base64 (core logic)
One visible pixel with inline params
Inspect attributes in the script tag:
id="sa-dynamic-optimization"
data uuid, src
Presence of flags like no-wp-rocket, nitro-exclude
Verify correct src path in the script tag.
Especially for white-label clients, make sure the URL matches the assigned subdomain.
Compare all data with what appears in the dashboard.
Look for discrepancies in attributes, structure, or values.
⚠️ Common mistakes to avoid
⚠️ Common mistakes to avoid
❌ Searching in the wrong part of the DOM (pixel may appear in <body>)
❌ Overlooking missing attributes
❌ Ignoring domain mismatches for white-label accounts
❌ Assuming diagnostic scans validate firing (they don’t)
💡 Pro Tip
💡 Pro Tip
For sites using Nitro, WP Rocket, or caching plugins, double-check for suppression attributes like no-wp-rocket. These prevent script delays or removals.
✅ Once done
The pixel should be traceable, structurally accurate, and the diagnostic alert should clear. Tracking and optimization should resume normally.
📚 Useful Official Resources