Pixel Installation: General Setup & Verification

💡 OTTO Pixel Fixes and LLM Citation Visibility

🔍 Overview OTTO SEO automates on-site improvements by injecting fixes through a JavaScript pixel. This approach is powerful for real browsers and search engine crawlers, but it has one important limitation: large language models (LLMs) like ChatGPT, Perplexity, Claude, and Gemini cannot see JavaScript-rendered changes. This article explains why, what OTTO pixel fixes actually do, and which Search Atlas tools genuinely influence LLM citation visibility. ⚙️ How the OTTO Pixel Works When you install the OTTO pixel on your site, it runs client-side JavaScript in a visitor's browser. This allows OTTO to apply fixes such as: - Title tag and meta description updates - Schema markup injection - Internal linking enhancements - Heading structure corrections - Image alt-text additions These changes are rendered at the browser level, after the raw HTML has been delivered by your server. Traditional search engine crawlers like Googlebot can process JavaScript, which is why OTTO fixes can positively affect organic search rankings. However, LLMs work very differently. 🤖 Why LLMs Cannot See OTTO Pixel Changes LLMs such as ChatGPT and Perplexity do not browse your live website in real time when generating answers or citations. Instead, they rely on: - Pre-crawled training data — static snapshots of web pages collected before the model was trained. - Retrieval systems — some LLMs use search APIs that fetch raw HTML, not JavaScript-rendered content. - Structured data feeds — knowledge graphs, publisher feeds, and indexed structured content. Because OTTO pixel fixes only exist after JavaScript executes in a browser, they are invisible to any system that reads raw HTML. An LLM querying your page sees the same unmodified source code a user would see if they disabled JavaScript in their browser. This is not a bug in OTTO — it is a fundamental difference between browser-based rendering and how LLMs ingest web content. 📊 What Actually Influences LLM Citation Visibility Winning citations in ChatGPT, Perplexity, or similar tools depends on factors that exist in your static, server-rendered content and your broader digital footprint. Focus on the following areas: - Static on-page content quality — Well-written, authoritative, factually accurate content baked directly into your HTML (not injected by JavaScript) is more likely to be referenced by LLMs. - Server-side structured data — Schema markup added directly to your page source (not via the OTTO pixel) helps LLMs understand your content type and context. - High-authority backlinks and brand mentions — LLMs weight sources that are frequently cited across the web. Use Search Atlas's Link Building tools to grow your link profile. - Local citations — For local businesses, consistent NAP (Name, Address, Phone) data across directories strengthens your presence in LLM knowledge bases. Navigate to Left sidebar → Local → Local Citations to manage these. - LLM Visibility monitoring — Track how often your brand appears in AI-generated answers using the Search Atlas LLM Visibility report to identify gaps and opportunities. ✅ Recommended Actions 1. Audit your site's server-rendered HTML to ensure key content, headings, and schema are present without relying on JavaScript. Go to Left sidebar → OTTO SEO → Site Audit to run a crawl. 2. Add schema markup (Article, Organization, FAQPage, etc.) directly in your page source or through your CMS — not solely through the OTTO pixel. 3. Publish high-quality, original content that answers the specific questions your target audience asks LLMs. 4. Build brand authority through consistent local citations, press mentions, and backlinks from trusted domains. 5. Monitor your LLM citation performance regularly in Search Atlas and use those insights to prioritize content improvements. 🛠️ Verifying Your OTTO Pixel Installation Even though the OTTO pixel does not influence LLM citations, it remains essential for organic SEO improvements. To confirm your pixel is correctly installed and active, navigate to Left sidebar → OTTO SEO → Site Audit → Installation Guide. A correctly detected pixel ensures all browser-level and crawler-level fixes are being applied to your site. 💬 Need More Help? 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.

🔍 Verify Search Atlas Tracking Scripts

🔍 What You Are Verifying Search Atlas may use Google Tag Manager (GTM) and a dynamic optimization script to load tracking or optimization features on your website. Verification confirms that the expected code is present, loads successfully, and is connected to the correct project. A GTM container ID, such as GTM-TCCS243, identifies a Google Tag Manager container. The ID alone does not prove that the container belongs to Search Atlas. Confirm its ownership and tags in the Google Tag Manager account used for your site. 🛠️ Check the Website Source 1. Open the published version of your website in a private browser window. 2. Right-click the page and select View page source, or use your browser’s developer tools. 3. Search for the GTM container ID, such as GTM-TCCS243. 4. Search for terms related to Search Atlas, OTTO, optimization, or the project’s tracking script. 5. Check several important page types, including the homepage, a service page, and a contact or conversion page. The code may be injected through a CMS, a plugin, a tag manager, or another deployment method. It may not appear in the original HTML if it is added after the page loads. 📊 Check Loaded Scripts 1. Open your browser’s developer tools and select the Network tab. 2. Reload the page with the developer tools open. 3. Filter requests by js, gtm, script, or a recognizable Search Atlas or OTTO term. 4. Open matching requests and review the request URL, status code, and initiator. 5. Confirm that the request returns successfully, normally with a 200 status, and is not blocked by the browser, consent tool, firewall, or content security policy. Do not rely on a script name alone. Review where the script loads from and whether the request is associated with the correct website and project. 🏷️ Verify the GTM Container 1. Sign in to the Google Tag Manager account that manages the website. 2. Open the container matching the ID found on the site. 3. Review the container name, account ownership, workspaces, tags, triggers, and published version. 4. Use GTM Preview mode to confirm that the expected tags fire on page load and on the relevant visitor actions. 5. Check that the container is published and that no duplicate or outdated container is also installed. If the GTM account is managed by another agency or vendor, ask the account owner to confirm whether the container and tags were installed for Search Atlas. ⚙️ Confirm the Dynamic Optimization Script Dynamic optimization code can be loaded directly or through GTM, so its location may differ between sites. Compare the script and its request behavior with the installation details for the correct Search Atlas project. Confirm that: - The script is installed on the intended domain. - The project and domain are correctly matched. - The script loads after consent requirements are met, when applicable. - The script is not duplicated by the CMS, GTM, or another optimization tool. - It is not being removed, modified, or blocked by caching, security, or performance tools. 🚨 Troubleshoot Recurring Issues - Code appears only sometimes: Test in a private window, clear site and CDN caches, and check whether a consent banner changes script loading. - GTM is present but tags do not fire: Use GTM Preview mode and review triggers, blocking rules, consent settings, and the published version. - Requests are blocked: Check browser console errors, security headers, firewall rules, and ad or script-blocking extensions. - Changes are not visible: Confirm that the correct environment is published and purge applicable browser, plugin, and CDN caches. - Multiple scripts are present: Remove duplicate installations only after confirming which deployment is active and supported. - Site behavior changed unexpectedly: Temporarily document the affected URL, time, browser, and console or network error before changing code. ✅ Record Verification Results For recurring investigations, record the website URL, affected page types, GTM container ID, script or request URL, timestamp, browser, consent state, and any console or network errors. This information helps identify whether the issue is caused by installation, publishing, caching, blocking, or project configuration. 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.

🔄 Switch Domains on Your OTTO SEO Pixel

🔍 Overview The OTTO SEO pixel is tied to the domain set when the project is created, and an existing OTTO project's domain cannot be changed in place. If you need to move to a new domain — for example, replacing an old site with a newly launched one — you will need to create a new OTTO project for the new domain and install its pixel. This article walks you through each step. ➕ Step 1: Create a New OTTO Project for the New Domain 1. In the left sidebar, go to OTTO SEO → All Sites (SEO Automation). 2. Add the new domain as a new site/project. If the new domain has no Site Audit project yet, one is created automatically. Note: There is no option to edit the domain of an existing OTTO project, so the old project cannot be pointed at the new domain. 🛠️ Step 2: Install the New Project's Pixel Open the new project's Installation Guide and copy its pixel snippet. Each OTTO project has its own snippet, so the old project's code will not work on the new domain. Paste it inside the of your new site (or use the WordPress plugin or the Cloudflare integration described in the Installation Guide). 🧹 Step 3: Remove the Old Pixel Remove the old project's pixel code from the old site's source so the two projects do not conflict. 🗂️ Step 4: Decide What to Do With the Old Project - Delete it if you no longer need it: deleting an OTTO project frees its OTTO slot right away. - Deep Freeze it if you want to keep its data read-only: a frozen project's slot is released after 14 days. 💡 Common Questions Will I lose my OTTO optimisation history? The old project keeps its own data until you delete it. The new project starts fresh: changes applied on the old domain do not carry over, and OTTO analyses the new domain from scratch. Can I connect multiple domains to one project? No. Each OTTO project supports one active domain at a time. If you need to manage a second domain, create a separate project. How long does pixel verification take? Verification is usually instant once the code is correctly placed. If it does not verify within a few minutes, clear your site cache and try again. 🆘 Need More Help? 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.

🔐 Grant Developer Access Without Sharing Login Credentials

🧭 Overview You don't need to share your Search Atlas login credentials to have a developer install the WordPress plugin and activate the OTTO pixel. Instead, you can provide two pieces of information — your API key and your OTTO UUID — which give the developer exactly what they need, nothing more. 🔑 What You Need to Share With Your Developer Your developer only needs the following two values to complete the installation: - Search Atlas API Key — authenticates the plugin connection to your account. - OTTO UUID — links the OTTO pixel to your specific OTTO project. Neither value gives access to your account dashboard, billing information, or login credentials. They are safe to share with a trusted third-party developer. 📋 Step 1: Find Your Search Atlas API Key 1. Log in to your Search Atlas account. 2. Open the Account Menu and select Settings. 3. Navigate to the API Keys page. 4. Copy your API Key and send it to your developer securely (for example, via an encrypted message or a password manager share link). 🧩 Step 2: Find Your OTTO UUID 1. From your Search Atlas dashboard, open the OTTO section. 2. Select the OTTO project associated with the website where the plugin will be installed. 3. Locate the OTTO UUID displayed on the project overview or settings page. 4. Copy the UUID and share it with your developer alongside the API key. Tip: If you have not yet created an OTTO project for the website, create one now before proceeding. Each website requires its own OTTO project and UUID. 🛠️ Step 3: Developer Installs the WordPress Plugin Share the following instructions with your developer. They do not need access to your Search Atlas account at any point. 1. Log in to the WordPress admin dashboard for the website. 2. Go to Plugins → Add New → Upload Plugin and upload the Search Atlas plugin ZIP file provided by Search Atlas. 3. Activate the plugin. 4. Open the plugin settings page inside WordPress by navigating to Search Atlas → Settings (General tab). 5. Enter the API Key you provided in the designated field. 6. Enter the OTTO UUID you provided in the OTTO Pixel UUID field. 7. Save the settings. The plugin will verify the connection and activate the OTTO pixel automatically. ✅ Step 4: Verify the Installation Once your developer confirms the plugin is configured, verify the connection from your side: 1. Return to the OTTO section in Search Atlas. 2. Open the relevant OTTO project. 3. Check that the pixel status shows as Active or Connected. 4. If the status does not update within a few minutes, ask your developer to confirm the API key and UUID were entered without extra spaces or characters. 🔒 Security Best Practices - Never share your Search Atlas account password or the email address used to log in. - Share the API key and UUID through a secure channel, such as a password manager's share feature, rather than plain email or chat. - If you believe your API key has been exposed to unintended parties, regenerate it immediately from Account Menu → Settings → API Keys and update the WordPress plugin settings with the new key. - Each OTTO UUID is project-specific and does not provide access to other projects or account data. ❓ Frequently Asked Questions Can the developer see my Search Atlas data using the API key? The API key is used by the WordPress plugin to send data to Search Atlas, not to browse your account. However, treat it like a password — share it only with people you trust and regenerate it if needed. Do I need to create a separate Search Atlas account for my developer? No. The API key and UUID workflow is specifically designed to avoid this. Your developer needs no Search Atlas account to install and configure the plugin. What if I manage multiple websites? Each website needs its own OTTO project and UUID. Repeat Steps 2 and 3 for each site. The same API key can be used across all of them. 💬 Need Help? 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.

🔄 Remove and Replace Domains in OTTO Pixel

Overview The OTTO pixel tracks SEO automation activity for a specific domain. The domain of an existing OTTO project cannot be changed in place — the website is set when the project is created and cannot be edited in the project settings. To move OTTO to a different domain (including www vs non-www), create a new OTTO project for the new domain and install its pixel. This article explains what to expect when removing an old project and setting up a new one. Step 1: Remove an Existing Domain from the OTTO Pixel 1. Log in to Search Atlas and navigate to the OTTO SEO section in the left sidebar. 2. Locate the domain you want to remove in your project list. 3. Look for the option to remove or delete that domain from your OTTO pixel configuration. The exact control will depend on your current interface — look for a menu or action associated with the domain row. 4. Confirm the deletion when prompted to permanently remove the domain from your OTTO pixel configuration. Note: Removing a domain disconnects it from OTTO pixel tracking. Historical data associated with that domain may no longer be accessible through the pixel after removal. Step 2: Create a New OTTO Project for the New Domain 1. While still in the OTTO SEO section, create a new OTTO project for the new domain. 2. Enter the full domain name of your new project when creating the project. 3. Follow the on-screen prompts to complete the domain verification and pixel installation steps on the new domain. 4. Once the pixel is installed and the domain is verified, OTTO will begin tracking SEO automation activity for the new domain. Tip: Make sure you have access to the new domain's DNS settings or CMS before starting the addition process, as you may need to complete a verification step depending on your site setup. Confirming the Change After completing both steps, your project list in OTTO SEO should reflect the new domain. If the old domain still appears, try refreshing the page and confirming that the deletion was successfully completed. If the new domain has not yet been verified, follow the on-screen instructions to complete the verification process. Common Issues - Cannot find the remove option: Ensure you have the required account permissions to manage domains. If the option appears inactive or unavailable, contact your account admin to request domain management access. - New domain not verifying: Double-check that you have followed all on-screen verification steps and that you have the necessary access to your domain's settings. - Domain still showing after deletion: Try refreshing the page. If it persists, reach out to our support team for assistance. 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.

🔗 Change Your Domain URL in OTTO

🧭 Overview If you need to point OTTO to a different domain — for example, after a site migration or when managing multiple properties — you cannot edit the domain of an existing OTTO project in place. Instead, you must create a new OTTO project for the new domain and install its pixel. This article walks you through the correct steps and reinstalling the OTTO Pixel on your new URL. ⚠️ Before You Begin - Make sure you have the login credentials for the website you are switching to, so you can reinstall the OTTO Pixel after the domain change. - Changing your domain will disconnect OTTO from the current site. Any deployed optimisations on the old domain will no longer be managed by OTTO. - You will need to complete a new Site Audit crawl on the new domain before OTTO can generate or deploy recommendations. 🔄 Step 1 — Open OTTO in the Platform 1. Log in to your Search Atlas account. 2. In the left sidebar, click OTTO SEO, then open SEO Automation. This takes you to the OTTO dashboard at /seo-automation-v3. 3. Confirm that the domain currently connected to OTTO is shown at the top of the dashboard. 🌐 Step 2 — Navigate to Site Audit 1. In the left sidebar, click OTTO SEO, then select Site Audit. 2. You will see a list of all site projects associated with your account. 3. Find the project that corresponds to the domain you want to use going forward. If the new domain does not yet have a project, you can add the domain directly in OTTO and the Site Audit project will be created automatically. ⚙️ Step 3 — Activate OTTO on the New Project 1. Open the Site Audit project for your new domain. 2. Run a full crawl if one has not been completed recently. OTTO requires up-to-date crawl data before it can be activated. 3. Once the crawl is complete, click the Activate OTTO button within the Site Audit project. This activates OTTO for the newly created project for your new domain. 📦 Step 4 — Reinstall the OTTO Pixel After connecting OTTO to the new domain, you must install the OTTO Pixel on the new site so OTTO can deploy on-page optimisations. Choose the method that matches your setup: - WordPress: Install the Search Atlas WordPress plugin on the new site, then connect it using your API key found in your Search Atlas account settings. - Google Tag Manager: Add a new Custom HTML tag in GTM for your new domain and paste in the OTTO Pixel code snippet. Set the trigger to All Pages and publish the container. - Manual installation: Copy the OTTO Pixel code snippet and paste it into the <head> section of every page on your new site, or add it via your theme's header settings. To find your OTTO Pixel code snippet, return to the OTTO dashboard by clicking OTTO SEO in the left sidebar and opening SEO Automation, then click Setup or the pixel installation prompt, and copy the code displayed there. ✅ Step 5 — Verify the Connection 1. Return to the OTTO dashboard by clicking OTTO SEO in the left sidebar and opening SEO Automation. 2. Confirm that the new domain is now displayed as the active connected site. 3. Check that the OTTO Pixel status shows as Connected or Active. If it shows as undetected, clear your site cache and wait a few minutes before refreshing. ❓ Frequently Asked Questions - Is there a 'Change Domain' button in OTTO Settings? No. The domain of an existing OTTO project cannot be edited in place. To move OTTO to a different domain (including www vs non-www), you must create a new OTTO project for the new domain and install its pixel. - What happens to my old domain's optimisations? OTTO will no longer manage or update the optimisations deployed on the old domain. Those changes remain on the old site but will not be modified or removed automatically. - Can I connect multiple domains to OTTO at the same time? Each OTTO activation is tied to one domain per project. You can manage separate domains by creating individual Site Audit projects and activating OTTO within each one, depending on your plan limits. - Do I need to re-enter my settings after switching domains? Yes. OTTO will generate a fresh set of recommendations based on the new domain's crawl data. Previous configurations and deployed tasks are not transferred between domains. 💬 Need Help? 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.

🛠️ Install Search Atlas Pixel on Replit CMS

🔍 Why Your Old Platform Data May Still Appear When you migrate your website to a new platform — such as moving from Wix to Replit — Search Atlas continues tracking the domain you originally connected. If the JavaScript pixel is not installed on your new Replit site, the platform will either show stale data from your previous setup or stop collecting new data altogether. To ensure accurate tracking, you must retrieve a fresh pixel snippet from Search Atlas and install it directly in your Replit project's HTML. 📋 Before You Begin - You have an active Search Atlas account with OTTO SEO enabled. - Your Replit project is set up and your site is live or in development. - You have access to your project's main HTML file (typically index.html) inside the Replit editor. - Your domain in Search Atlas matches the domain your Replit site is published on. ⚙️ Step 1: Retrieve Your Pixel Snippet from Search Atlas 1. Log in to your Search Atlas account. 2. In the left sidebar, click OTTO SEO → All Sites (SEO Automation). 3. Select the project connected to your Replit website. 4. Navigate to the Pixel Installation or Site Activation section within the OTTO SEO dashboard. 5. Copy the full JavaScript pixel snippet displayed on screen. It will look similar to: <script src="https://cdn.searchatlas.com/pixel/otto.js" data-otto-uuid="YOUR\_UNIQUE\_ID">``</script> Important: Do not reuse a pixel snippet from your old Wix site. Each platform installation should use the snippet retrieved directly from your current OTTO SEO project to ensure the correct UUID is active. 🚀 Step 2: Add the Pixel to Your Replit Project 1. Open your Replit project in the Replit editor. 2. In the file tree on the left, locate and open your main HTML file — usually named index.html. 3. Paste the pixel snippet you copied from Search Atlas just before the closing </head> tag on every page you want to track. Placing it in the <head> section ensures the pixel loads as early as possible. 4. If your Replit project uses a shared layout or template file that wraps all pages (common in frameworks like Express with EJS, or similar), paste the snippet in that shared layout file instead — this way it loads site-wide automatically. 5. Save the file. ✅ Step 3: Verify the Pixel Is Firing Correctly 1. Click Run in Replit to launch your site. 2. Open your live site URL in a browser. 3. Right-click anywhere on the page and select Inspect (or press F12) to open DevTools. 4. Go to the Network tab and filter by the keyword otto or searchatlas. 5. Reload the page. You should see a successful network request to the Search Atlas pixel endpoint with a 200 status code. 6. Return to your Search Atlas OTTO SEO dashboard. Within a few minutes, the pixel status should update to Installed. If the pixel status does not update within 10–15 minutes, double-check that your snippet is placed correctly inside the <head> tags and that your Replit site is publicly accessible (not set to private). 💡 Common Issues and Fixes - Old Wix data still showing: This is expected immediately after migration. Once the new pixel is active on Replit, Search Atlas will begin collecting fresh data. Historical Wix data will remain visible but new sessions will reflect your Replit site. - Pixel not detected: Confirm your Replit project is deployed to a public URL, not just running locally. Search Atlas needs to reach the live domain to validate the pixel. - Multiple pages not tracked: If your Replit project has multiple HTML pages, ensure the snippet is added to each page's <head>, or use a shared layout/template to inject it globally. - Wrong domain connected: Verify that the domain listed in your Search Atlas OTTO SEO project exactly matches the published Replit domain (including or excluding www). 💬 Need More Help? 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.

🔌 OTTO Pixel Installation Methods and Alternatives

🧭 Overview The OTTO pixel is a small tracking script that powers your AI Visibility projects in Search Atlas. It collects the data needed to monitor how your brand appears across AI-generated responses. If your AI Visibility projects have disappeared or you cannot access Cloudflare, this article explains what may be happening and how to get help reinstating your projects. ❓ Why Did My AI Visibility Projects Disappear? AI Visibility projects require an active, verified OTTO pixel to function. If the pixel is removed, your AI Visibility project is frozen (read-only) but kept, and it will be automatically reactivated with its history preserved once the pixel is reinstalled and OTTO is detected again. Projects may become unavailable or stop tracking when the pixel is not properly installed or verified on your site. Common reasons include: - The pixel was never fully installed or confirmed on your site. - The pixel was removed from your site after initial setup. - The pixel code was present but blocked by a security policy or plugin. - Your Cloudflare integration was disconnected or its associated configuration was removed. Once the pixel is properly installed and verified again, your existing AI Visibility project will be reactivated automatically with its history preserved — you do not need to recreate it. 📋 Installation Methods The OTTO pixel can generally be installed in more than one way — Cloudflare is not the only option. Depending on your platform and technical setup, common approaches include adding the pixel script directly to your site's header code, using a tag manager, or working through your platform's built-in custom code or script management area. To get started, locate your unique pixel script from within your Search Atlas account. The exact location may vary depending on your account setup. Once you have your pixel script, you can add it to your site using whichever method suits your platform — the key requirement is that the script loads on every page of your site. If you are unsure which installation method applies to your site or are having trouble locating your pixel script, our support team can help identify the right approach for your specific setup. 🛠️ What to Have Ready When You Contact Support To help our team assist you as quickly as possible, please have the following information ready: - Your Search Atlas project name or the name of the AI Visibility project that went missing. - The domain or URL you are trying to track. - The platform your website is built on (for example: WordPress, Shopify, Wix, or a custom setup). - Whether you currently have a Cloudflare account connected to your domain. - Any error messages or screenshots related to pixel verification or project 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.

Configure OTTO Pixel and Knowledge Graph Settings

Overview After reinstalling the OTTO plugin on WordPress, two issues can appear together: the OTTO pixel shows a red status despite being engaged, and you may need to locate where to enter your business's Knowledge Graph information in Search Atlas. This article explains what to check and how to get help resolving both. Fix a Red OTTO Pixel Status A red pixel status means the OTTO tracking code has not yet been detected on your site. Because the exact troubleshooting steps depend on your specific site setup, the most reliable path is to contact our support team directly so they can verify the pixel connection for your project. Before reaching out, having the following information ready will speed up the resolution: - The name of your Search Atlas project connected to the WordPress site - The URL of the WordPress site where OTTO is installed - Confirmation of whether the OTTO SEO plugin is showing as active in Plugins → Installed Plugins - Any error messages or status indicators visible in your Search Atlas dashboard - The approximate time you reinstalled or reactivated the plugin What Is the Knowledge Graph? The Knowledge Graph is where you store structured business information for your project — such as your business name, address, social profiles, and entity type. Search Atlas uses this data to power OTTO's on-page and schema recommendations, helping search engines understand who and what your business is. Locating Knowledge Graph Settings Knowledge Graph settings are managed inside Search Atlas at the project level, not inside the OTTO plugin on WordPress. The exact location of these settings within the platform may vary, and our support team can point you directly to the correct area for your account and project setup. When contacting support, please have your project name ready so the team can guide you to the Knowledge Graph configuration area quickly. 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.

🛡️ OTTO Plugin vs. Malicious Script: What's the Difference?

🔍 Overview If your antivirus has flagged a script in your WordPress footer and you suspect the Search Atlas OTTO plugin, this article will help you quickly determine the true source and take the right action. The OTTO plugin does inject a script into your site — but it follows a predictable format. Anything that deviates from that format is not from Search Atlas and should be treated as a potential security threat. 📋 How to Check Whether the Script Is from OTTO The most reliable way to determine whether the flagged script comes from the OTTO plugin is to deactivate the plugin and observe whether the script disappears: 1. Log in to your WordPress admin panel. 2. Navigate to your installed plugins list and deactivate the Search Atlas OTTO plugin. 3. Clear your site's cache and any CDN cache. 4. Reload your website and check whether the suspicious script is still present. 5. If the script disappears after deactivating OTTO, it was injected by the plugin. If it remains, it originates from another source and should be treated as a potential malicious injection. 🚨 Signs the Script May Be External Malware (Not OTTO) The following are red flags that indicate the script is not from Search Atlas and is likely a malicious injection — including techniques used in ClickFix and similar social-engineering malware campaigns: - The script loads from an unrecognised or suspicious domain unrelated to Search Atlas. - The code contains long strings of base64 or hex-encoded text. - It uses eval(), Function(), or unescape() to execute hidden code. - The script tag is embedded deep inside theme files, other plugin files, or directly in the WordPress database (wp_options, post content). - It appears even after you deactivate the OTTO plugin. - Your antivirus names a specific threat — such as a ClickFix script, a fake CAPTCHA injector, or a clipboard hijacker — rather than flagging a generic tracking pixel. If any of these apply, the injection is likely external malware and Search Atlas OTTO is not the cause. ✅ Next Steps If You Suspect Malware If the script persists after deactivating OTTO, take the following steps: - Run a full malware scan using a trusted WordPress security plugin (such as Wordfence or Sucuri). - Review recently modified files in your WordPress installation for unexpected changes. - Check your WordPress database (particularly wp_options and post content) for injected script tags. - Consider restoring from a clean backup taken before the injection appeared. - Contact your hosting provider, as they may have server-level scanning tools available. When escalating to our support team, please have the following ready: your site URL, the exact script or code snippet that was flagged, the name of the threat your antivirus identified, and a note of whether the script persisted after deactivating the OTTO plugin. 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.

🔗 OTTO Pixel: Removing Unwanted Inserted Links

🧭 Overview If you have noticed unfamiliar links appearing on your website and suspect they were inserted by the OTTO pixel, this article will help you identify the source and work toward removing those links. These steps also apply if you believe a team member's action or a misconfigured automation may have injected links without your direct approval. ⚠️ Understanding How OTTO Inserts Links OTTO can insert internal links, schema markup, and other on-page optimizations through its pixel, which is a small JavaScript snippet installed on your website. OTTO only applies changes that have been approved and deployed inside the platform. If you see links you did not knowingly approve, one of the following may have occurred: - A team member with platform access approved and deployed an OTTO recommendation on your behalf. - A previously approved fix is still active and you no longer want it. - The OTTO pixel is conflicting with another plugin or script on your site. - A third-party script unrelated to OTTO is inserting the links. Working through each possibility in order will help you find and fix the issue quickly. 🔍 Step 1 — Confirm OTTO Is the Source Before removing anything, confirm that OTTO is actually responsible for the links. 1. Open your browser, navigate to the affected page, and right-click the suspicious link. 2. Select Inspect to open DevTools and look at the HTML around that link. 3. If the link is wrapped in a comment or attribute that references OTTO or Search Atlas, OTTO inserted it. 4. If there is no such reference, the link may be coming from a different plugin, theme, or script — investigate those sources separately. 📋 Step 2 — Audit Your Deployed OTTO Fixes Every link OTTO inserts corresponds to a deployed fix in your account. Reviewing your deployed fixes will show you exactly what OTTO has changed on your site. 1. Log in to your Search Atlas account and navigate to OTTO SEO → All Sites (SEO Automation). 2. Select the website where the unwanted link appears. 3. Locate the area that lists fixes currently active and live on your site. 4. Look for any fix related to internal linking or anchor text on the affected page. 5. Review the fix details and confirm it matches the link you want to remove. 🗑️ Step 3 — Remove the Unwanted Link Once you have identified the deployed fix responsible for the unwanted link, you will need to deactivate or remove it within the OTTO platform. The exact controls available to you may vary depending on your account configuration and permissions. 1. Within the deployed fix you identified in Step 2, use the available option to deactivate or remove that fix. 2. Confirm the action when prompted. 3. Clear your website's cache and any CDN cache if applicable. 4. Revisit the affected page to confirm the link has been removed. 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.

⚡ OG Descriptions and Schema Markup in OTTO SEO

What Is an OG Description? An OG description (Open Graph description) is a short snippet of text that controls how your page appears when shared on social media platforms such as Facebook, LinkedIn, and Slack. It is defined using the og:description meta tag inside your page's HTML <head> section. OG descriptions are not the same as your meta description or your schema markup. Each serves a distinct purpose: - OG description — controls the preview text shown in social media cards when a URL is shared. - Meta description — controls the snippet shown beneath your page title in Google search results. - Schema markup — provides structured data to search engines so they can display rich results such as star ratings, FAQs, and product details. How OG Descriptions Relate to Schema Markup in OTTO SEO In OTTO SEO, schema markup and OG tags are managed separately. Schema markup (such as Article, Product, or FAQ schemas) is structured data that helps search engines understand your content. OG tags, including og:description, are social metadata that affect how your content looks when shared on social platforms. When OTTO SEO generates or deploys schema, it does not overwrite or conflict with your OG description tags. If you noticed the term "OG description" appearing in your workflow or in OTTO's suggestions, it was likely surfaced as a related on-page element — not as part of the schema deployment itself. Bulk-Generated Schemas Disappearing in OTTO SEO If schemas you generated in bulk are disappearing or not persisting as expected, this is a known issue that our support team can investigate on your account. Because the cause may relate to your specific site connection, session state, or account configuration, there is no universal self-serve fix available at this time. To help our team resolve this as quickly as possible, please have the following information ready when you reach out: - The name of the project or site where the schemas are disappearing. - The type of schemas affected (for example, Article, FAQ, Product). - Whether you are generating schemas individually or in bulk, and approximately how many. - The approximate date and time when you first noticed schemas disappearing. - Any error messages or unexpected status indicators you have seen on screen. 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.

🤖 OTTO Now Supports AI-Assisted Installation

OTTO's installation experience has been upgraded with AI assistant shortcuts and smarter schema management, making it faster and easier to get your site fully set up. ✨ What's New OTTO now guides users through installation with built-in AI assistant support across multiple touchpoints. A dedicated Use AI Assistant tab has been added to the OTTO installation onboarding modal, along with a Copy AI Prompt button so you can hand off setup instructions to your preferred coding assistant in one click. The Installation Guide page now features a coding-assistant nudge banner with the same Copy AI Prompt option, and when you choose to email your developer, the message body automatically includes an AI assistant shortcut and a proactive prompt to streamline the handoff. Additionally, you can now bulk delete schema suggestions directly within OTTO, saving time when managing large sets of schema recommendations. 🛠️ How to Use It 1. Open OTTO and navigate to the installation onboarding modal. 2. Select the Use AI Assistant tab to access the AI-powered setup flow. 3. Click Copy AI Prompt to copy the pre-built prompt and paste it into your coding assistant. 4. Alternatively, visit the Installation Guide page and use the coding-assistant nudge banner to copy the prompt from there. 5. If emailing your developer, the AI assistant shortcut and proactive prompt are already included in the email body automatically. 6. To bulk delete schema suggestions, go to the Schema Suggestions section in OTTO, select the items you want to remove, and use the bulk delete option. 📋 What to Expect The Copy AI Prompt button is available in both the onboarding modal and the Installation Guide page — both generate the same ready-to-use prompt. The AI assistant tab and nudge banner are purely optional; existing manual installation steps remain fully accessible. Bulk delete for schema suggestions applies only to items listed in the OTTO schema suggestions panel and cannot be undone, so review your selection before confirming. A previously reported issue where the SA project selector dropdown would detach from its trigger when scrolling has also been 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.

🔌 Installing Search Atlas JavaScript Pixel on Replit

🧭 Overview If you recently migrated your site to Replit and Search Atlas is still showing data from your old platform (such as Wix), the tracking pixel needs to be installed on your new Replit project. This article outlines the general approach for adding the Search Atlas JavaScript snippet to a Replit project so that data is pulled from the correct platform. ⚠️ Why Old Platform Data Still Appears Search Atlas tracks your site using a JavaScript pixel tied to your account. When you migrate to a new platform, the pixel does not automatically follow. Until the snippet is added to your Replit project and your old site is removed or the pixel is inactive there, Search Atlas will continue reading whichever source it last detected. Installing the pixel on Replit and saving your changes resolves this. 🔑 Step 1: Find Your Unique Tracking Snippet 1. Log in to your Search Atlas account. 2. Locate the JavaScript tracking snippet associated with your site within your Search Atlas account. If you are unsure where to find it, contact the Search Atlas support team for guidance on retrieving your snippet. 3. Copy the full JavaScript snippet provided — your unique identifier is already embedded in it. Do not modify any part of it. 🛠️ Step 2: Add the Snippet to Your Replit Project 1. Open your Replit project that hosts your website. 2. Locate the main HTML file for your project. This is most commonly named index.html. If your project uses a JavaScript framework, place the snippet in the appropriate location where global scripts are loaded for every page — consult your framework's documentation for the correct placement. 3. Open the HTML file and find the closing </head> tag. 4. Paste your copied Search Atlas snippet on the line directly above </head>. 5. Save your file and ensure your live site is updated with the latest changes. ✅ Step 3: Verify the Pixel Is Active After saving and deploying, return to your Search Atlas account and check that your Replit site is being detected. It may take a short time for data from the new platform to appear. If your old platform's pixel is still active, deactivate or remove it to ensure Search Atlas reads from your Replit site only. 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.

🔁 Resolving a Persistent OTTO Pixel Duplicate Badge

🧭 Overview The Duplicate Installation badge appears on your project when Search Atlas detects more than one instance of the OTTO pixel firing on your site. Removing the extra snippet from your page source is often not enough — if the original injection method is still active in your CMS, plugin, or tag manager, the pixel continues to load twice and the badge persists even after a recrawl. 🔍 Step 1 — Verify the Frontend HTML First Before changing anything in your CMS, confirm exactly how many pixel instances are present on your live site. 1. Open any page on your website in a browser. 2. Right-click anywhere on the page and select View Page Source. 3. Press Ctrl + F (or Cmd + F on Mac) and search for your OTTO pixel ID or the script tag otto-pixel. 4. Count every match. If you see more than one result, note the surrounding code for each — this tells you which injection methods are active. 5. Repeat this check on at least two other page types (homepage, a blog post, a product page) because some injection methods are template-specific. 🗂️ Step 2 — Remove the Pixel by Injection Method Match your setup to the correct removal procedure below. Deleting code from one location while another method is still enabled will reproduce the duplicate on every page load. - WordPress plugin (e.g., Insert Headers and Footers, WPCode): Go to the plugin's settings page in your WordPress dashboard, locate the OTTO pixel snippet, and delete the entry entirely. Disabling the snippet toggle is not sufficient — remove the entry so it cannot re-enable on a plugin update. - Theme template files (functions.php, header.php, or equivalent): Access your theme's file editor or connect via FTP/SFTP, find the pixel code in your theme files, delete it, and save. If a child theme is active, check both the child and parent theme files. - Google Tag Manager: Log in to your GTM workspace, find the OTTO pixel tag, and disable or remove it before publishing a new container version. Verify the tag is no longer firing before publishing; delete the tag permanently once confirmed. - Other tag managers (Segment, Tealium, Adobe Launch): Follow the same logic — locate the tag or rule that injects the pixel script, disable or delete it, then publish the updated container. - Shopify (theme template or app embed): In your Shopify admin, access your theme's code editor and search your main layout file (e.g., theme.liquid) for the pixel snippet and remove it. Also review any installed apps that inject header scripts, and check any store preferences or script fields where pixel code may have been added. - Hard-coded HTML (static sites or custom CMS): Remove the script block directly from your base template file, then redeploy or republish your site so the change takes effect on all pages. 🔄 Step 3 — Clear Caches and Trigger a Recrawl After removing all extra instances, caches at the server, CDN, or plugin level may continue serving the old page source. Clear every cache layer you have access to before requesting a new crawl in Search Atlas. 1. Clear your hosting or server-side cache. 2. Purge any CDN cache (Cloudflare, Fastly, etc.). 3. If you use a WordPress caching plugin, purge it from the plugin's dashboard. 4. Return to Search Atlas, open the affected project, and trigger a recrawl so the platform can re-evaluate the pixel installation count. ⚠️ What to Do If the Badge Persists If the Duplicate Installation badge remains after completing all steps above, the pixel may still be loading from an injection point you haven't yet identified. Before reaching out for help, have the following ready: - Your project name in Search Atlas. - The URL of a page that still shows two pixel instances in View Page Source. - A description of every injection method you've already removed (plugin name, file name, tag manager tag name, etc.). - Screenshots or a copy of the relevant source code showing the duplicate. 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.

🔌 Otto Pixel Plugin vs Script Installation Guide

🧭 Overview The Otto pixel connects your website to Search Atlas so Otto can track performance and automate SEO tasks. There are two ways to install it: the WordPress plugin method and the script-based method. While the plugin is the quickest option, it can conflict with certain WordPress themes and plugins — most commonly causing issues on checkout pages. This article explains both methods, their limitations, and how to switch to the script method if you experience issues. ⚠️ Why the Plugin Method Can Cause Conflicts The Otto WordPress plugin injects the tracking pixel by hooking into WordPress's loading sequence. On some sites this can interfere with other plugins or theme scripts, particularly on checkout pages. Common symptoms include: - Checkout page failing to load or displaying incorrectly - Page elements breaking or becoming unresponsive after plugin activation If you activated the Otto pixel plugin and immediately noticed issues on your checkout page, the plugin method is likely conflicting with your existing setup. The fix is to switch to the script-based installation. ✅ Which Installation Method Should You Use? Use the following guidance to choose the right method for your site: - Plugin method — Suitable for simple WordPress sites with few third-party plugins and no custom checkout flow. - Script method — Recommended for sites with complex checkout pages or any site where the plugin method causes visual or functional issues. When in doubt, the script method is the safer and more universally compatible choice. It gives you more direct control over where and how the pixel loads, which can prevent conflicts with other scripts on the page. 🛠️ How to Switch to the Script Installation Method 1. Log in to Search Atlas and locate your unique Otto pixel script from within the platform. Your pixel script will be a short JavaScript snippet associated with your account. 2. Return to your WordPress dashboard and deactivate the Otto pixel plugin under Plugins → Installed Plugins. Do not delete it yet — wait until you confirm the script method is working. 3. Paste the Otto pixel script into your site's <head> section. You can do this using your theme's built-in header settings or a script management plugin that allows you to insert code into the page head. 4. Save your changes and reload your checkout page to confirm the conflict is resolved and the pixel is loading correctly. If you are unsure where to find your Otto pixel script in the platform, or if you need help identifying the right place to paste it in your WordPress setup, our support team can guide you through the process. 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.

🔌 Connect OTTO Pixel and CMS to Namecheap

🧭 Overview If your Website Studio site is published through Namecheap, you need to complete two separate steps to fully activate your site's capabilities: installing the OTTO Pixel for tracking and automation, and connecting the CMS so your content can sync correctly. This article walks you through what to prepare and how to complete each step. 🛰️ Step 1 — Install the OTTO Pixel on Your Namecheap Site The OTTO Pixel enables Search Atlas to track performance, run automations, and gather SEO data for your published site. To install it on a Namecheap-hosted Website Studio site, follow these steps: 1. Log in to your Search Atlas account and navigate to Website Studio. 2. Locate your published site and open its settings to find the OTTO Pixel snippet — this is a short JavaScript code block unique to your site. 3. Log in to your Namecheap hosting control panel (cPanel or your WordPress dashboard, depending on your hosting type). 4. If you are on WordPress, install a header/footer plugin (such as Insert Headers and Footers) and paste the OTTO Pixel snippet into the header section, then save. 5. If you are on a static or HTML site, paste the OTTO Pixel snippet just before the closing </head> tag in each page's HTML file, then re-upload the files to Namecheap via cPanel File Manager or FTP. 6. Return to Website Studio and confirm the pixel shows as active or connected for your site. If the pixel does not show as connected after completing these steps, note the exact error message and the date and time of your attempt before reaching out for help. 🗂️ Step 2 — Connect the CMS to Your Namecheap-Hosted Site Connecting the CMS allows Search Atlas to push and sync content directly to your Website Studio site. To link the CMS for a Namecheap-hosted site, follow these steps: 1. In Search Atlas, go to the left sidebar → Website Studio and open the settings for your Namecheap-hosted site. 2. Look for the CMS Connection or Integrations section and select Namecheap or Custom Host as your hosting provider. 3. When prompted, enter your site's URL and any required API key or authentication credentials. These credentials are generated from your Namecheap hosting account or WordPress admin panel. 4. If you are using WordPress on Namecheap, you may need to install the Search Atlas or OTTO WordPress plugin and authenticate it with your Search Atlas API key, which you can find in your Search Atlas account under Account Menu → Settings → API Keys. 5. Complete the connection flow and verify that your site's content sync status shows as connected in Website Studio. If you encounter a connection failure, record the exact error message and the date and time of the attempt. Also note your Namecheap hosting type (shared hosting, WordPress, static site) and your Website Studio site name or URL, as these details will be needed if you require further support. 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.

⏳ OTTO Pixel Installation: Crawl Status and Timeline

🔍 Overview After installing the OTTO pixel — either via the WordPress plugin or manual code snippet — you may notice that the pixel status inside the platform does not immediately change to confirmed. This is expected behavior. The status update depends on the completion of a site audit crawl, which may take some time depending on your site's size and structure. This article explains the difference between a successful installation and a confirmed status, and what to expect while the crawl is underway. ✅ Installation Success vs. Status Confirmation These are two separate events, and it is important not to confuse them: - Successful installation means the OTTO pixel code is correctly placed on your site, either through the activated WordPress plugin or a manually added snippet. No further action is needed on your end once this step is complete. - Status confirmation means Search Atlas has detected the pixel during a site audit crawl and has updated the dashboard to reflect it. This happens automatically — but only after the crawl finishes. If your plugin is activated and your API credentials are correctly entered, your installation is likely already successful. The pending status simply means the crawl has not yet reached and verified your pages. 🔄 Site Audit Crawl and Timing Once the OTTO pixel is installed, Search Atlas runs a site audit crawl to detect and confirm the pixel across your pages. During this crawl, the dashboard status may remain in a pending or unconfirmed state. This is normal — the status will update automatically once the crawl has completed and the pixel has been detected. The time required for the crawl to complete can vary. Larger or more complex sites with many pages will naturally take longer to process than smaller sites. If your status has not updated, the most likely explanation is that the crawl is still in progress. 📊 What to Do While Waiting While the crawl is underway, no action is required on your part. You do not need to reinstall the pixel or make any changes. Simply allow time for the crawl to complete. Once it finishes, your pixel status will update automatically in the platform dashboard. If your pixel status remains unconfirmed after an extended period and you believe your installation is correctly set up, please reach out to our support team with your project name and any relevant details about how you installed the pixel (WordPress plugin or manual snippet). 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.

🔧 OTTO Pixel, Subdomains, AI Quota & Alt Tags

🧭 Overview This article covers four interconnected OTTO issues that are often reported together. Work through each section that applies to your situation. 📡 OTTO Pixel Detection: Why Your Pixel May Show as Not Installed Even if your OTTO pixel is firing correctly in Google Tag Manager (GTM), the Search Atlas platform may still display a Not Installed status. This is expected behaviour and does not mean your pixel is broken. Why this happens: OTTO verifies pixel installation by cross-referencing data collected during a completed site audit. The pixel status will not update to Installed until a full site audit cycle has finished processing. What to do: 1. Confirm the pixel tag is published and firing in GTM using GTM Preview mode or a browser tag inspector. 2. Navigate to OTTO SEO in the left sidebar, then open SEO Automation (URL: /seo-automation-v3) and open your OTTO project. 3. Check whether a site audit is currently running or queued. If a previous audit has not completed, the pixel status will remain pending. 4. Trigger a new site audit if none is in progress. Audit completion typically takes 2–24 hours depending on site size. 5. Once the audit completes, return to the OTTO dashboard. The pixel status should update automatically within 1 hour of audit completion. Important: Do not remove and reinstall the pixel tag if GTM is already firing it correctly. Re-installation is unnecessary and will not speed up detection. 🌐 Setting Up OTTO Projects for Subdomains OTTO treats each subdomain as a separate project. A pixel installed on www.example.com will not be detected for a project configured against blog.example.com, even if both are on the same root domain. Architecture requirements: - Create a dedicated OTTO project for each subdomain you want to optimise. - Each project requires its own pixel installed on the corresponding subdomain. - Site audits run independently per project, so subdomain audits do not share credit or progress with the root domain project. Steps to set up a subdomain project: 1. Go to OTTO SEO in the left sidebar and open SEO Automation. 2. Click Add New Project and enter the full subdomain URL (e.g., https://blog.example.com). 3. Copy the pixel code generated for this new project and install it exclusively on the subdomain — do not reuse the pixel from your root domain project. 4. Publish the tag in GTM (or add it directly to your subdomain's <head>), then run a fresh site audit for the subdomain project. If you manage multiple subdomains, repeat this process for each one. ⚡ AI Generation Quota: Limits, Top-Ups & Upgrade Paths OTTO's AI content and automation features draw from a shared AI generation quota tied to your Search Atlas subscription plan. When quota is exhausted, AI-powered actions (such as generating meta descriptions, titles, or content suggestions) will pause until quota is restored. How quota works: - Quota resets automatically on your monthly billing date. - Quota is consumed across all OTTO SEO V3 features, including OTTO suggestions, bulk AI writing, and automated fixes. - You can monitor your remaining quota from Avatar → Billing → Plans & Top-ups (Billing) under the Total Quota list. Quota limits by plan tier: - Starter: 25,000 AI words per month - Growth: 100,000 AI words per month - Pro: 300,000 AI words per month Topping up mid-cycle: If you exhaust your quota before your billing date, you have two options: 1. Purchase a quota top-up add-on — available in blocks directly from your billing settings. Top-up blocks are added instantly and do not affect your renewal date. 2. Upgrade your plan — if you regularly exhaust quota, upgrading to the next tier is more cost-effective than recurring top-ups. To purchase a top-up or upgrade, navigate to the top-right corner (avatar) → Billing (Plans & Top-ups tab) and select the relevant option. Changes take effect immediately. 🖼️ Alt Tag Detection Failures: Why OTTO Flags Already-Fixed Images If OTTO is reporting missing alt tags on images where you have already added alt text, the issue is almost always a recrawl timing delay, not a detection error. Why OTTO still shows the flag: OTTO's alt tag checks are based on the most recent completed site audit. If you added alt text after the last audit ran, OTTO has not yet seen the updated markup and will continue displaying the old finding until the page is recrawled. CMS-specific considerations: - WordPress, Webflow, and similar CMS platforms sometimes cache rendered HTML. Even after you save alt text in the CMS, the live page may serve cached content without the alt attribute for several hours. - For JavaScript-rendered images, alt attributes added via JS may not be read by the crawler. Ensure alt text is present in the static HTML or the server-side rendered output, not injected client-side after page load. Steps to verify and resolve: 1. Open the affected page URL directly in a browser and use View Page Source (not browser DevTools) to confirm the alt attribute is present in the raw HTML. 2. If the alt text is visible in the source, the fix is confirmed on your end. You now need to trigger a recrawl. 3. Go to OTTO SEO in the left sidebar, open SEO Automation, then navigate to your OTTO project and initiate a new site audit. 4. Allow up to 7 days for a full recrawl cycle to complete across large sites. Most standard sites recrawl within 24–72 hours. 5. Once the audit completes, return to the OTTO issues list. The alt tag flag should be cleared automatically. If the flag persists after recrawl: Re-check the raw HTML source to confirm the alt attribute is genuinely present and not empty (alt="" is treated as decorative and will still trigger a flag if OTTO expects descriptive alt text). Make sure alt text is descriptive and contains at least a few meaningful words. 💬 Need More Help? 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.

🚗 Search Atlas Pixel Compatibility With Car Dealer Platforms

🔍 What Is the Search Atlas Pixel? The Search Atlas pixel is a small snippet of JavaScript code you place on your website. It tracks visitor behaviour, measures campaign performance, and helps Search Atlas deliver accurate SEO and analytics data. For the pixel to work, your website platform must allow you to add custom JavaScript to your site's pages. 🚗 Do Car Dealer Platforms Support Custom Pixels? Car dealer website platforms vary widely in how much control they give you over your site's code. Compatibility depends entirely on whether your specific platform allows third-party JavaScript snippets. Here is a general breakdown: - Compatible platforms: Platforms that let you insert custom HTML or JavaScript into the <head> or <body> of your pages will work with the Search Atlas pixel without any issues. - Partially compatible platforms: Some platforms restrict where scripts can be placed or require approval before adding third-party code. In these cases the pixel may still work, but you may need to work with your platform provider to get it installed. - Incompatible platforms: Fully closed or proprietary dealer platforms that block all custom code additions will not support the Search Atlas pixel. The most reliable way to find out is to contact your car dealer platform's support team directly and ask: "Can I add a custom third-party JavaScript pixel to my website pages?" ✅ How to Check Compatibility Before Installing 1. Log in to your car dealer website platform's admin panel. 2. Look for a section labelled Custom Code, Header Scripts, Tracking Codes, or Integrations. 3. If you find one of these sections, your platform is likely compatible. You will be able to paste the Search Atlas pixel code there. 4. If you cannot find such a section, reach out to your platform provider and ask whether they support custom JavaScript snippets or third-party tracking pixels. 🛠️ How to Install the Search Atlas Pixel on Your Website 1. In Search Atlas, navigate to Website Studio using the left sidebar (or go to /website-studio). 2. Locate the pixel or tracking code section within Website Studio and copy your unique Search Atlas pixel snippet. 3. Log in to your car dealer website platform. 4. Paste the pixel snippet into the custom code or header scripts area of your platform. 5. Save your changes and publish or update your site. 6. Return to Search Atlas and verify that the pixel is firing correctly using the built-in verification tool. ⚠️ Common Issues and How to Resolve Them - Platform requires approval for third-party scripts: Submit a request to your platform provider with the Search Atlas pixel code and explain it is an analytics tracking script. Most providers approve standard JavaScript pixels. - Pixel is installed but not detecting traffic: Confirm the snippet was placed inside the <head> tag and that it appears on all pages, not just the homepage. Clear your browser cache and test again. - Platform uses a tag manager (e.g. Google Tag Manager): If your dealer platform supports Google Tag Manager, you can deploy the Search Atlas pixel as a Custom HTML tag inside GTM instead of editing the site code directly. - Platform does not allow any custom code: Unfortunately, Search Atlas cannot override platform-level restrictions. In this situation, consider asking your platform provider about upgrading to a plan that includes custom code access, or discuss migrating to a more flexible website solution. 💡 Using Search Atlas Website Studio as an Alternative If your current car dealer platform is too restrictive, Search Atlas Website Studio (left sidebar → Website Studio) offers a fully flexible website builder where the Search Atlas pixel works natively with no setup required. This eliminates compatibility concerns entirely and gives you full control over your site's code and performance. 🙋 Need More Help? 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. Additional Notes DealerSocket/CDK/Tekion, DealerInspire, Dealer.com (Cox Automotive), Sincro, Gubagoo/Widewail widgets (pixel goes on underlying site, not widget), WordPress dealer sites — named platform-specific instructions not present in keeper.

🔄 OTTO Recrawl Timing, Pixel Verification, Multi-Site Strategy

📋 Overview After making changes to your WordPress site — or any connected property — you may wonder whether your Search Atlas pixel is still firing correctly and when OTTO will pick up the latest updates. This article explains how OTTO recrawl timing works, how to verify pixel status, how to manually trigger a recrawl, and when it makes sense to expand OTTO across multiple brands or domains. 🔍 How to Verify Your Search Atlas Pixel Your pixel must be active for OTTO to collect on-site data accurately. After WordPress theme updates, plugin changes, or migrations, always confirm the pixel is still installed and firing. 1. Go to OTTO SEO → All Sites (SEO Automation) in the left sidebar (URL: /seo-automation-v3). 2. Select the project you want to check and open its Settings. 3. Locate the Pixel Status indicator. A green status means the pixel is firing correctly. A red or unverified status means it is not detected. 4. If the pixel shows as inactive, copy the pixel snippet from the settings panel and re-add it to your WordPress site. The most reliable placement is via your theme's header.php file or a header/footer plugin such as Insert Headers and Footers. 5. After re-adding the snippet, return to OTTO SEO → All Sites (SEO Automation) and click Verify Pixel to confirm detection. Tip: WordPress updates and theme switches are the most common reasons a pixel stops firing. Check pixel status any time you make significant site changes. ⏱️ Understanding OTTO Recrawl Timing OTTO follows an automated crawl schedule to keep your site analysis current. Understanding this schedule helps you set accurate expectations for when changes appear inside the platform. - Initial crawl: Runs automatically when you first activate OTTO on a project. Depending on site size, this can take anywhere from a few minutes to several hours. - Recurring weekly crawl: OTTO re-analyses your site on a weekly cycle. New recommendations, updated issue counts, and refreshed on-page data are all generated during this cycle. - Change detection window: Content or technical changes you publish on your site will typically be reflected in OTTO within the next scheduled crawl. If you publish a fix on Monday and the weekly cycle runs on Wednesday, you will see the updated status by Wednesday. Because OTTO operates on a weekly analysis cycle, it is a best practice to review your OTTO dashboard each week, address the highest-priority recommendations, and then allow the next cycle to confirm the impact of your changes. ▶️ How to Trigger an OTTO Recrawl Manually If you need OTTO to reflect changes immediately — for example, after resolving a batch of technical issues or confirming your pixel is back online — you can request a manual recrawl rather than waiting for the next scheduled cycle. 1. Go to OTTO SEO → All Sites (SEO Automation) in the left sidebar. 2. Select the relevant project from your project list. 3. Navigate to OTTO SEO → Site Audit → Overview (Website Overview) and locate the Recrawl Site button. 4. Click the button to queue a new crawl. OTTO will begin re-analysing your site and update recommendations once the crawl is complete. 5. Larger sites may take longer to process. You can continue using other parts of the platform while the crawl runs in the background. Note: Manual recrawls count toward your plan's crawl allowance. Use them after meaningful site changes rather than repeatedly in short intervals. 🌐 Multi-Site Strategy: When to Scale OTTO Across Multiple Brands Search Atlas supports managing multiple domains and brands within a single account. Knowing when to activate OTTO on additional sites — rather than focusing exclusively on your primary domain — is key to getting the most out of your plan. ✅ Start With Your Primary Site First Before enabling OTTO on secondary domains, ensure your primary site is stable and producing results. Specifically: - Your pixel is verified and collecting data consistently. - OTTO's highest-priority recommendations (critical errors, missing metadata, Core Web Vitals issues) have been addressed. - You have completed at least two to three weekly review cycles and can see measurable progress in Keywords → Rank Tracker (Keyword Rank Tracker). Spreading OTTO across multiple sites too early can dilute your focus and make it harder to attribute ranking improvements to specific actions. 📈 When to Enable OTTO on Additional Sites Expand to secondary brands or domains when the following conditions are met: - Your primary site's OTTO implementation is stable and recurring crawls are running without issues. - You have enough crawl quota on your current plan to support additional projects without compromising existing ones. - The secondary site has a working pixel installation confirmed before you activate OTTO. - You have a team member or workflow in place to review recommendations for each additional project on a regular cadence. To add a new site, go to OTTO SEO → All Sites (SEO Automation), click Create, enter the domain, install the pixel on that site, verify it, and then activate OTTO. Repeat the same weekly review process you established for your primary site. 📊 Using Site Metrics Alongside OTTO After a recrawl, cross-reference OTTO recommendations with data in Site Metrics to build a complete picture of performance: - Keywords → Rank Tracker (Keyword Rank Tracker): Confirm whether fixed pages are gaining or holding positions after a recrawl confirms changes. - Keywords → Keyword Magic: Identify new keyword opportunities to feed back into OTTO's on-page optimisation tasks. - Site Metrics → Keyword Gap: For multi-site accounts, compare keyword coverage across your domains to decide where to prioritise OTTO actions next. 💡 Quick Reference: Post-WordPress Change Checklist 1. Re-verify your pixel in OTTO SEO → All Sites (SEO Automation) → Project Settings. 2. Trigger a manual recrawl from the OTTO dashboard. 3. Wait for the crawl to complete, then review updated recommendations. 4. Address priority issues and monitor progress in Keywords → Rank Tracker (Keyword Rank Tracker). 5. Repeat weekly as part of your standard SEO workflow. 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.

🛠️ Share OTTO Plugin Credentials With Your Developer

🔍 Overview When you activate OTTO SEO for a website, Search Atlas generates a pixel plugin that your developer needs to install on your site. The platform includes an Email my developer button, but this button launches your device's default mail client (such as Outlook). If your team does not use that mail client, the button will not work as expected. This article explains how to copy and share the installation details manually so your developer receives everything they need regardless of the email tool you use. 📍 Where to Find the OTTO Plugin Details All the information your developer needs is available directly inside the OTTO SEO setup screen. To get there: 1. Log in to Search Atlas and select your workspace. 2. From the Home page, locate the website you want to connect. 3. In the per-project actions menu, click the Create OTTO Project button, or open an existing OTTO session. 4. Follow the on-screen steps until you reach the Install the OTTO Pixel section. 5. You will see the plugin package download link, your unique Site Key, and step-by-step installation instructions. 📋 How to Share the Details Without Outlook Once you are on the install screen, use any of the following methods to send the information to your developer: - Copy the Site Key manually: Click the copy icon next to your Site Key, then paste it into any messaging tool — Slack, Teams, WhatsApp, a project management ticket, or any other platform your team uses. - Download the plugin file: Click the download button to save the plugin package to your computer, then attach it to an email composed in Gmail, Apple Mail, or any webmail service, or share it via Google Drive, Dropbox, or a similar file-sharing tool. - Screenshot the instructions: Take a screenshot or screen recording of the full install section and share it with your developer so they can follow every step exactly as shown in the platform. - Share your screen: If you are working with a developer in real time, screen-sharing via Zoom, Google Meet, or Teams is a quick way to walk through the steps together. 📦 What to Include When You Share Make sure your developer has all of the following before they begin: - The OTTO pixel plugin file (.zip download). - Your unique Site Key — this links the plugin to your specific OTTO session. - The installation steps from the platform (upload the plugin to WordPress, activate it, and enter the Site Key in the plugin settings). - Access to the WordPress admin panel for the target website (your developer will need this independently). ✅ Confirming a Successful Installation After your developer installs and activates the plugin and enters the Site Key, return to the OTTO SEO screen in Search Atlas. The connection status will update automatically once the pixel is detected on your site. If the status does not update within a few minutes, ask your developer to confirm the Site Key was entered exactly as copied — no extra spaces or characters. 💡 Tips to Avoid Common Issues - The Site Key is unique to each website — do not reuse a key from a different domain. - The plugin must be both installed and activated in WordPress for the connection to register. - If your site uses a security or firewall plugin, ask your developer to whitelist the OTTO pixel script to prevent it from being blocked. 🙋 Need More Help? 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.

🔧 OTTO Pixel UUID Duplication After Platform Upgrades

What Is Happening and Why After a Search Atlas platform upgrade, your OTTO Pixel may display a duplicated or incorrect UUID in the dashboard. This is a known issue that can occur when a platform upgrade affects the existing pixel configuration. Because this issue involves the relationship between your Search Atlas account and your Google Tag Manager (GTM) setup, the exact steps to resolve it depend on your specific account state and configuration. Generic steps like clearing your cache will not resolve this issue. The root cause is a mismatch between the UUID in your GTM container and the UUID currently active in your Search Atlas account. Resolving it requires locating your current active OTTO Pixel UUID in Search Atlas and ensuring your GTM tag reflects that same UUID. How to Identify This Issue You are likely experiencing this problem if you notice any of the following after a platform upgrade: - Two different UUIDs appear under your OTTO Pixel settings in Search Atlas. - The OTTO Pixel status shows as disconnected or unverified despite the script being present on your site. - GTM is still firing a UUID that no longer matches what appears in your Search Atlas dashboard. - OTTO automations are not triggering or tracking correctly. What to Prepare Before Contacting Support Because the specific resolution for UUID duplication depends on your account configuration and cannot be completed without account-level access, our support team will need to assist you directly. To help us resolve this as quickly as possible, please have the following ready when you reach out: - The name of the affected OTTO project. - The UUID or UUIDs currently showing in your OTTO Pixel settings (screenshot helpful). - The UUID currently in your GTM tag for the OTTO Pixel (screenshot helpful). - The date or approximate time the duplication was first noticed, especially if it followed a platform upgrade. - Whether OTTO automations have stopped triggering or tracking since the issue appeared. 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.

🖼️ OTTO Alt Text Appearing as Google Meta Descriptions

🔍 What Is Happening? After OTTO deploys image alt text to your site, you may notice that Google is displaying that alt text as the meta description snippet in search results — even after you have rolled back the alt text or updated your meta descriptions. This is a known behavior tied to how Google selects page snippets, not a bug in OTTO itself. Google does not always use the meta description tag as the snippet. Its algorithm dynamically picks the text it considers most relevant to a searcher's query. If your page has prominent, keyword-rich alt text and a weak or missing meta description, Google may prefer the alt text as the displayed snippet. ⚙️ Why OTTO Alt Text Gets Selected by Google There are three common reasons Google chooses alt text over your meta description: - Alt text is keyword-dense. OTTO generates descriptive, SEO-optimized alt text. If that text closely matches a user's search query, Google's snippet algorithm may rank it as the most relevant excerpt. - Meta description is too short, too long, or missing. If your meta description is under 70 characters, over 160 characters, duplicated across pages, or absent, Google is more likely to override it with on-page content — including alt attributes. - Crawl cache lag. Even after rolling back alt text or editing your meta description, Google may still be serving a cached version of the page. Full re-indexing can take days to weeks depending on your crawl frequency. 🛠️ How to Resolve This 1. Verify the rollback was applied correctly. In Search Atlas, confirm that any OTTO alt text deployment has been rolled back and that the changes are no longer active for the affected pages. If you are unsure whether the rollback completed successfully, contact support using the instructions at the bottom of this article. 2. Audit your meta descriptions. For the affected URLs, ensure each page has a unique meta description between 120–160 characters that clearly summarises the page content. A strong, specific meta description significantly reduces the chance Google will substitute other on-page text. 3. Check that alt text is fully removed from the live page. Use your browser's View Source (Ctrl+U / Cmd+U) or a tool like Google's URL Inspection to confirm the OTTO-generated alt text no longer appears in the page's HTML. If it still appears, the rollback may not have propagated — contact support using the instructions at the bottom of this article. 4. Request re-indexing via Google Search Console. Once the meta description is correct and the alt text is removed from the live page, submit the URL for re-indexing in Google Search Console using the URL Inspection tool. This signals Google to re-crawl and update its cached snippet sooner than the natural crawl cycle. 5. Allow time for Google to update. Even after re-indexing is requested, it may take several days for the new snippet to appear in search results. Monitor the affected URLs in Google Search Console to track when the updated snippet is reflected. 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.

🔍 Verify OTTO Pixel Installation & Compare Plans

🧩 Why the OTTO Pixel May Not Appear in View Source After pasting the OTTO pixel code in Shopify, many customers check their live site using Ctrl+U (View Page Source) and cannot find the code. This is expected behaviour and does not mean the installation failed. Shopify's storefront rendering pipeline can modify, defer, or inject scripts in ways that make them invisible in the raw HTML returned by View Source. The pixel is typically loaded asynchronously or injected by Shopify's script engine after the initial HTML is parsed, so it will not appear in a static source view. ✅ How to Correctly Verify Your OTTO Pixel Is Active Use one of the following methods to confirm the pixel is firing correctly on your Shopify store: 1. Browser DevTools (Recommended): Open your store in Chrome or Firefox. Press F12 to open DevTools, go to the Network tab, reload the page, and search for otto in the filter bar. If you see a network request related to the OTTO pixel, it is active. 2. DevTools Console check: In the same DevTools panel, open the Console tab and type window.otto or the pixel's global variable name. A returned object (not undefined) confirms the script has loaded. 3. Search Atlas Dashboard: Navigate to OTTO SEO in the left sidebar, then open SEO Automation inside it (or go to /seo-automation-v3). If your site shows as connected and OTTO is receiving data, the pixel is working correctly. 4. Tag Assistant or PixelMe extensions: Third-party browser extensions designed to detect tracking pixels will scan the rendered DOM — not just the raw source — and will surface your OTTO pixel if it is present. Important: Never rely solely on Ctrl+U / View Page Source to verify JavaScript-based pixels on Shopify. This method only shows the initial HTML document, not dynamically injected scripts. 🛠️ Troubleshooting: Pixel Still Not Detected If none of the methods above confirm the pixel is active, work through these steps: - Confirm the pixel code was saved in the correct Shopify location: Online Store → Themes → Edit Code → theme.liquid, placed just before the closing tag. - Check that your Shopify theme uses theme.liquid as its base layout. Some headless or custom themes use a different layout file. - Disable any active browser extensions (ad blockers, privacy shields) that may suppress pixel requests during your test. - Clear your browser cache and reload the page before re-testing. - Ensure your Shopify store is published and not password-protected during verification. 📊 OTTO Plan Comparison: $99 vs $199 Search Atlas offers two popular OTTO subscription tiers. Here is a side-by-side summary of what each plan includes: - Starter plan: Includes OTTO SEO automation, core OTTO SEO V3 features, on-page optimisation, and schema automation, with a site-slot allocation set by your tier. Suited for individual site owners or small businesses. - Growth plan: Includes everything in the Starter plan plus a larger site-slot allocation, making it ideal for agencies or businesses running multiple domains. Management level included in both plans: Both plans provide full OTTO SEO management capabilities — automated technical fixes, content optimisation suggestions, and real-time SEO monitoring — for each site slot included in your plan. Check your Billing page (top-right avatar menu → Billing) for the exact number of site slots your tier includes. To view your current plan details or upgrade, go to the top-right avatar menu → Billing (Plans & Top-ups) in the Search Atlas platform. 💡 Quick Reference Summary - View Source (Ctrl+U) cannot detect asynchronously loaded pixels — use DevTools Network tab instead. - The Search Atlas dashboard at /seo-automation-v3 is your most reliable confirmation that OTTO is connected. - Site-slot allocation varies by plan tier — check your Billing page (top-right avatar menu → Billing) for your exact allocation. - Full OTTO management features are included at both plan levels. 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.

🔌 Reconnecting Search Atlas After Website Migration

Overview If you have recently migrated your website to a new platform — such as Lovable, a custom CMS, or any non-standard builder — you will need to reinstall the OTTO pixel to resume SEO automation. Custom CMS platforms and Lovable builds do not always have a dedicated plugin or settings field for tracking scripts. The recommended approach is to install the OTTO pixel via Google Tag Manager (GTM). Step 1: Locate Your OTTO Pixel Code The OTTO pixel is unique to each website project. To find it, log in to Search Atlas and open your OTTO project. If you are not sure where the pixel snippet is located within your account, note your project name and reach out using the instructions at the bottom of this article — a teammate will confirm the exact location for your account. Keep this tab open while you complete the installation on your new site. Step 2: Install the OTTO Pixel via Google Tag Manager Using GTM is the most reliable method for custom CMS platforms and Lovable sites, since it does not require direct access to the site's source code. Log in to your Google Tag Manager account, open the workspace for the migrated website, and add a new tag using the Custom HTML tag type. Paste the full OTTO pixel code snippet into the HTML field, set the trigger so the tag fires on all pages of your site, then save and publish the container. You can use GTM's preview functionality to verify the tag is firing correctly before closing your session. Confirming the Pixel Is Active After installation, allow a short time for data to begin flowing. If you confirmed the tag is firing via GTM's preview functionality, the pixel is active. 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.

🔍 Verify OTTO Pixel on MoPro Sites

If you've installed the OTTO Pixel on a MoPro site and want to confirm it's working, this guide walks you through how to check the installation status, understand what each status means, and troubleshoot common issues. 🚀 What the OTTO Pixel Does The OTTO Pixel is a lightweight tracking script that connects your website to Search Atlas. It allows OTTO to monitor your site's SEO health, run automated optimizations, and report accurate data back to your dashboard. Without a verified pixel, OTTO cannot fully manage or analyze your site. ✅ How to Check Your Pixel Status To verify whether the OTTO Pixel is installed and detected on your MoPro site: 1. Log in to your Search Atlas account and navigate to your project. 2. Check whether the system has detected the pixel on your site. 3. If the pixel is not detected, follow the troubleshooting steps below. If your pixel is detected, it is installed correctly and no further action is needed. 🛠️ Understanding Detection Issues Sometimes the OTTO Pixel is installed but still shows as not detected. This can happen for several reasons: - Caching layers — CDNs like Cloudflare or other caching systems may serve a delayed or stale version of your pages. The pixel may be present but not yet reflected in the live scan. - Script-blocking plugins — Browser extensions or site security settings may block third-party scripts from loading. - Placement errors — The pixel code may have been added to the wrong section of your site or only on certain pages. - Recent installation — If you just added the pixel, it can take up to 30 minutes for the system to detect it. 🔧 Steps to Troubleshoot on MoPro If your pixel is not being detected, try the following steps: 1. Confirm the pixel code is placed correctly. Make sure the OTTO Pixel script is added in a location that loads on every page of your site. 2. Republish your site. After adding or adjusting the pixel code, republish your site to ensure the latest version is live. 3. Check for Cloudflare or CDN caching. If your site uses Cloudflare, purge the cache and wait 10–15 minutes before re-checking. 4. Use your browser's developer tools. Right-click on your live site, select Inspect, and search the page source for otto or your unique pixel key. If it appears in the HTML, the code is present. 5. Allow time for re-scan. After making changes, allow time for the system to re-scan your site and update the pixel status. 📝 Still Not Detected? If you have completed the troubleshooting steps above and the pixel is still not detected, our team can help investigate further. Please have the following information ready: - Your MoPro site URL - The date and time you installed the pixel - Any status messages or errors you are seeing 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.

🔌 Search Atlas Pixel Integration With Lofty.com

🌐 Overview Search Atlas can integrate with websites built on Lofty.com through a tracking pixel. This article explains how the integration works, what it can and cannot do automatically, and whether Search Atlas needs access to your Lofty.com editor. 🔍 What Is the Search Atlas Pixel? The Search Atlas pixel is a small snippet of JavaScript code that you place in your website's header or footer. Once installed, it allows Search Atlas to track site performance data and connect your Lofty.com website to your Search Atlas dashboard. The pixel is used for: - Tracking visitor behavior and traffic sources - Connecting your site to Search Atlas reporting tools - Enabling certain automated SEO features tied to your domain 🛠️ How to Add the Pixel to Your Lofty.com Website Lofty.com's website editor allows you to inject custom code into your site's header. Follow these steps to install the Search Atlas pixel: 1. Log in to your Search Atlas account and locate your pixel code. You can find this inside your account settings or within the relevant Search Atlas tool that requires tracking. 2. Copy the full pixel code snippet provided by Search Atlas. 3. Log in to your Lofty.com account and open your website editor. 4. Navigate to your site's Settings or Header/Footer Code section — the exact location may vary depending on your Lofty.com plan and editor version. 5. Paste the Search Atlas pixel code into the header code field. 6. Save your changes and publish your site. 7. Return to Search Atlas and verify the pixel is detected on your domain. If Lofty.com does not provide a custom code injection field on your current plan, you may need to upgrade your Lofty.com subscription or contact Lofty.com support directly to enable this feature. ✍️ Does Search Atlas Need Access to My Lofty.com Editor? This is one of the most common questions about this integration. The short answer is: it depends on the feature you want to use. Here is a breakdown by use case: - Pixel tracking only: No editor access is required. You install the pixel yourself by pasting the code into your Lofty.com header settings. Search Atlas does not need login credentials or direct access to your editor for this. - Automated page editing: If you want Search Atlas to automatically update or optimize existing pages on your Lofty.com site, you would need to grant access or use a supported integration method. Lofty.com is a closed proprietary platform, which means Search Atlas cannot push content changes directly unless Lofty.com supports a compatible API or plugin connection. - Automated blog creation: Similarly, for Search Atlas to publish blog posts automatically to your Lofty.com site, a direct integration between the two platforms must be supported. At this time, Lofty.com does not offer an open API or native Search Atlas plugin, so fully automated publishing to Lofty.com is not available. Content created in Search Atlas would need to be manually copied and published in your Lofty.com editor. 📋 What You Can Do With the Pixel on Lofty.com Even without a full two-way integration, connecting your Lofty.com site via the pixel gives you access to valuable Search Atlas features, including: - Monitoring your site's SEO performance inside Search Atlas - Tracking keyword rankings using Left sidebar → Keywords → Rank Tracker - Identifying keyword opportunities using Left sidebar → Keywords → Keyword Magic - Reviewing competitive keyword gaps using Left sidebar → Keywords → Keyword Gap ⚠️ Important Limitations to Know - Search Atlas cannot log in to or control your Lofty.com editor on your behalf without explicit access being granted by you. - Lofty.com's closed platform architecture limits the degree of automation available compared to open platforms like WordPress. - Any content generated by Search Atlas tools (such as AI-written blog posts) will need to be manually transferred into your Lofty.com editor until a deeper integration is available. 💬 Need More Help? 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.

🖼️ OTTO SEO: Disable Image Schema and Remove Conflicting JavaScript

🔍 Overview OTTO SEO can automatically inject ImageObject schema markup into your WordPress pages. If OTTO generates schema using inline data:image/svg+xml URLs, Google Search Console (GSC) will flag these as Invalid Image Metadata errors because Google cannot crawl or index base64-encoded inline images. This article explains what causes this issue and how to get it resolved. ⚠️ Before You Begin - You need Administrator access to your WordPress dashboard. - You need access to your Search Atlas account with OTTO SEO activated for your domain. - GSC errors may take 24–72 hours to clear after schema is removed. This is normal. 🛠️ What This Issue Involves The root cause is OTTO SEO injecting ImageObject schema that references inline base64-encoded SVG images, which Google cannot validate. The fix requires disabling OTTO's image schema output for your domain so that these invalid entries are no longer generated. Because the exact location of image schema controls within OTTO SEO settings may vary depending on your account configuration, the specific toggle or setting name is best confirmed with the Search Atlas support team, who can guide you to the correct control for your setup and disable it on your behalf if needed. 📋 Steps to Request Resolution 1. Log in to your Search Atlas account and navigate to the OTTO SEO section. 2. Review your current OTTO settings to see if there is any schema-related configuration visible for your domain. 3. If you cannot locate an image schema setting, or if the Invalid Image Metadata errors persist after any changes you attempt, contact the Search Atlas support team directly. 4. When reaching out, have the following ready: - Your domain name (e.g., the site where OTTO SEO is activated) - A screenshot or list of the specific GSC errors you are seeing - The date the errors first appeared in Google Search Console - Confirmation of whether you have already made any changes to OTTO settings A support teammate can identify the correct schema setting for your account, disable image schema output, and confirm whether any JavaScript tag adjustments are needed on the WordPress side. 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.

🔍 Verify Your Pixel and Trigger OTTO Recrawls

🧩 What This Article Covers After making changes to your WordPress site — such as updating themes, plugins, or page content — you may notice that OTTO SEO has not yet reflected those updates. This guide walks you through verifying that your Search Atlas pixel is installed correctly and shows you how to trigger a fresh OTTO recrawl so your latest changes are recognised and actioned. ⚙️ Step 1: Verify Your Search Atlas Pixel The Search Atlas pixel is a lightweight script that must be present on your site for OTTO to read and interact with your pages. If your WordPress site has recently been updated, it is worth confirming the pixel is still in place. 1. Go to OTTO SEO in the left sidebar, then open SEO Automation (URL: /seo-automation-v3). 2. Select the site you want to check from the site selector at the top of the page. 3. Look for the pixel status indicator near the top of the OTTO dashboard. A green status confirms the pixel is active and communicating correctly. 4. If the status shows as inactive or unverified, proceed to re-verify your pixel installation (see Step 2 below). 🛠️ Step 2: Re-Verify the Pixel After WordPress Changes WordPress theme updates, plugin conflicts, or caching layers can sometimes remove or block the pixel script. Follow these steps to troubleshoot and re-verify. 1. In the OTTO SEO section, open the OTTO Settings or Site Setup panel for your site. 2. Copy the pixel snippet provided by Search Atlas. 3. In your WordPress admin, navigate to your theme's header.php file or use a plugin such as Insert Headers and Footers to paste the snippet into the <head> section of every page. 4. If you use a caching plugin (e.g. WP Rocket, W3 Total Cache), clear your cache after saving the snippet. 5. Return to the OTTO SEO dashboard in Search Atlas and click Verify Pixel. The status should update to green within a few seconds. Tip: If you recently changed your WordPress theme, always re-check the pixel immediately afterwards, as theme switches typically overwrite header files. 🔄 Step 3: Trigger an OTTO Recrawl Once your pixel is verified, you can prompt OTTO to recrawl your site and pick up any content or structural changes you have made. 1. In the left sidebar, go to OTTO SEO, then open SEO Automation (/seo-automation-v3). 2. Select the relevant site from the site selector. 3. Navigate to Site Audit → Overview (Website Overview) and locate the Recrawl Site button. 4. Click Recrawl Site. OTTO will queue a fresh crawl of your site — this typically completes within a few minutes for smaller sites, but may take longer for larger sites. 5. Once the crawl is complete, OTTO's recommendations and applied changes will update to reflect your latest site content. Note: Recrawls are rate-limited to prevent excessive server load. If the option is temporarily unavailable, wait a short period and try again. 🌐 Managing Multiple Sites With OTTO If you manage several websites under one Search Atlas account, it is important to keep the pixel verified and recrawls up to date across all of them — not just your primary domain. - Use the site selector at the top of the OTTO SEO dashboard to switch between your connected sites. - Check the pixel status for each site individually after any WordPress updates, as changes on one site do not affect others. - Schedule periodic recrawls for all active sites — especially after publishing significant new content or running a site migration. - Use Site Metrics (Site Explorer) in the left sidebar (/site-explorer/list) to monitor organic performance across your sites and identify which properties may need attention after a recrawl. ❓ Common Issues and Quick Fixes - Pixel shows inactive after a plugin update: Deactivate recently updated plugins one at a time to identify conflicts, then re-verify the pixel. - Recrawl does not reflect new pages: Confirm the new pages are publicly accessible (not set to draft or password-protected) and that your sitemap is up to date. - OTTO recommendations appear outdated: Always trigger a manual recrawl after significant content changes rather than waiting for the next scheduled crawl. - Pixel verification fails repeatedly: Disable browser extensions or test pixel verification from an incognito window to rule out client-side interference. 💬 Need More Help? 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.

🔌 Pixel Status During Site Audit Installation

🧭 Overview After installing the Search Atlas pixel on your website, you may notice that its status appears as Disconnected inside the platform. This is expected behaviour during the initial site audit crawling phase and does not mean something has gone wrong. This article explains why this happens and what you should do. 🤔 Why Does the Pixel Show as Disconnected? When you first install the pixel, Search Atlas needs to crawl your website before it can verify that the pixel is live and firing correctly. During this crawling process, the platform has not yet confirmed the pixel's presence on your pages, so the status is temporarily displayed as Disconnected. This is a normal part of the setup sequence. The disconnected status does not mean the pixel was installed incorrectly — it simply means verification is still in progress. ⏱️ How Long Does Verification Take? Pixel verification is completed once the initial site audit crawl finishes. The timeline depends on the size of your website. You do not need to reinstall the pixel or take any action during this window. The status will update automatically once the crawl is complete. ✅ How to Confirm Your Pixel Is Installed Correctly Before waiting for the crawl to finish, it is worth doing a quick check to make sure the pixel code is in place. Follow these steps: 1. Log in to Search Atlas and navigate to the Site Audit section of the platform. 2. Locate your pixel installation code inside the platform and copy it. 3. Open your website and inspect the page source (right-click the page and select View Page Source). 4. Use your browser's search function (Ctrl+F or Cmd+F) to search for the pixel ID or a unique portion of the pixel script. 5. Confirm the pixel code appears in the <head> section of your page. If you find the pixel code in your page source, the installation is correct and you can simply wait for the crawl to complete. 🔄 What to Do If the Pixel Remains Disconnected If the pixel status still shows as Disconnected after the initial crawl has had time to complete, contact our support team for assistance. When reaching out, please have the following ready: - Your project or property name as it appears in Search Atlas - The date and time you installed the pixel - Confirmation of whether the pixel code appears in your page source 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.

🔧 Installing Search Atlas Pixel Without Head Access

🗺️ Overview The standard Search Atlas pixel installation places a script tag inside the <head> section of your website. However, if you manage a franchise site, a locked-down CMS, or a platform where your parent organisation controls template access, you may not be able to edit the <head> directly. 📋 Before You Start Gather the following before attempting any method below: - Your Search Atlas pixel snippet (copy it from your Search Atlas dashboard). - Login credentials for whatever CMS access level you do have — even limited access may be enough. - Contact details for your franchise web administrator, in case you need to escalate a formal request. 🔍 Where to Find Your Pixel Snippet If you have not copied your snippet yet, log in to Search Atlas and navigate to your dashboard to locate the pixel snippet. If you are unsure where to find it, contact your Search Atlas account administrator or reach out to our support team for guidance. What to Do When You Cannot Access the Head Tag Because the specific steps for installing the Search Atlas pixel when head access is unavailable depend on your CMS, hosting environment, and account configuration, our support team will work with you directly to identify the correct approach for your setup. To help us resolve this as quickly as possible, please have the following ready when you contact us: - The name of your CMS or platform (e.g. a franchise-managed system, a proprietary CMS, etc.). - A description of what access level you currently have (e.g. page editor only, no template access). - Any error messages or limitations you have encountered when attempting installation. - Your Search Atlas account name or project name. 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.

🔍 Understanding Your Schema Markup Detection Ratio

🧩 What Does the Schema Detection Ratio Mean? When Search Atlas audits your site, it checks every crawled page for valid schema markup. The ratio displayed — for example, 1/124 — means that out of 124 pages crawled, only 1 page was found to have detectable, properly implemented schema markup. This does not necessarily mean your schema deployment failed entirely. It means the tool found schema on fewer pages than expected based on your total crawled page count. ⚠️ Common Reasons for a Low Detection Ratio - Schema applied to one page only: If you deployed schema to a single page (such as your homepage) but not site-wide, only that page will register. - JavaScript-rendered schema: Schema injected via JavaScript may not be picked up if the crawler processes pages before the script executes. Search Atlas recommends implementing schema in raw HTML or via server-side rendering. - Incorrect placement: Schema must be placed inside a <script type="application/ld+json"> tag within the page's HTML. Incorrect tag types or malformed JSON will cause detection to fail. - Noindex or blocked pages: Pages blocked by robots.txt or marked noindex may be crawled but schema on those pages will not count toward your accessible inventory. - Plugin or CMS conflicts: If you are using a WordPress plugin or CMS extension to deploy schema, conflicts with caching plugins or theme code can strip the markup before the page is served. - Schema only on specific page types: If your schema is scoped to product pages, blog posts, or FAQs and your site has a large number of other page types, the ratio will appear low by design. 🛠️ How to Diagnose the Issue 1. Open Search Atlas and navigate to OTTO SEO → Site Audit in the left sidebar to view your report. 2. Locate the schema markup finding and click through to see which specific URLs have schema detected versus which do not. 3. Pick a sample URL that should have schema and paste it into Google's Rich Results Test (search.google.com/test/rich-results) to confirm whether schema is visible to crawlers. 4. View the raw page source (right-click → View Page Source in your browser) and search for application/ld+json. If it does not appear, the markup is either missing or rendered client-side only. 5. Validate your schema JSON using Schema.org's validator (validator.schema.org) to catch syntax errors or missing required properties. ✅ How to Improve Your Schema Coverage - Deploy schema site-wide where appropriate: Add Organisation or WebSite schema globally, and use page-specific schema types (Article, Product, FAQPage, BreadcrumbList) on the relevant templates. - Use server-side or static HTML implementation: Avoid relying solely on JavaScript to inject schema. Ensure the markup is present in the initial HTML response. - Update your CMS template files: If your site uses a CMS like WordPress, Shopify, or Webflow, add schema to your theme templates so it applies to all pages of a given type automatically. - Re-crawl after changes: Once you have made updates, trigger a new crawl in Search Atlas so the tool picks up your changes and recalculates the detection ratio. - Prioritise high-value pages first: If a full site-wide rollout is not immediately possible, focus on your top landing pages, product pages, and blog posts to increase coverage quickly. 📊 What Is a Healthy Schema Ratio? There is no single universal benchmark, as the ideal ratio depends on your site's content and goals. However, as a general guide: - Most pages that are publicly accessible and indexable should carry at least one schema type. - A ratio below 10% on a content-heavy site typically indicates a deployment gap worth addressing. - Purely functional pages such as login, cart, or account pages do not require schema, so some gap is normal and expected. The goal is to ensure that every page where schema would add value to search engines — product pages, articles, local business pages, FAQs — is covered. 💬 Need More Help? 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.

🛠️ Pixel Removal, Investigations & Refund Requests

🔍 Overview If you are experiencing unexpected traffic drops and have an open investigation with our team, we understand how stressful this can be. This article explains how to remove the Search Atlas tracking pixel from your site, what to expect during an active investigation, and how to request a refund if your issue remains unresolved. 🛠️ How to Remove the Search Atlas Pixel You can remove the Search Atlas pixel from your website at any time. The steps depend on how it was originally installed. If you added the pixel manually to your site's code: 1. Log in to your website's CMS or hosting file manager. 2. Open the file where the pixel snippet was placed — typically the site-wide header or footer template (e.g., header.php, a theme file, or a tag manager container). 3. Locate the Search Atlas pixel script. It will be a short <script> tag referencing Search Atlas or a tracking domain provided during setup. 4. Delete the entire script snippet. 5. Save the file and clear your site's cache. 6. Verify removal by viewing your page source (Ctrl+U or Cmd+U) and confirming the script is no longer present. If you installed the pixel via Google Tag Manager (GTM): 1. Log in to your GTM account and open the relevant container. 2. Navigate to Tags and locate the Search Atlas pixel tag. 3. Click the tag, select Delete, and confirm. 4. Click Submit to publish the updated container. If you used a WordPress plugin or third-party integration: 1. Go to your WordPress dashboard and open Plugins. 2. Deactivate and delete any plugin that was used to inject the Search Atlas pixel. 3. Clear your site cache after removal. 📊 Understanding the Investigation Process When a traffic issue is reported, our team opens a formal investigation to identify the root cause. Here is what typically happens during this process: - Initial review (24–48 hours): Our team examines your account data, pixel activity, and any reported anomalies. - In-depth analysis: Complex cases — particularly those involving significant traffic drops or potential data conflicts — require deeper review across multiple data sources, and timing varies by case complexity. - Resolution and update: Once findings are confirmed, our team contacts you with a summary and any corrective actions taken. If your investigation has been open for more than 5 business days without a meaningful update, you are entitled to escalate the case and request a resolution timeline or a refund consideration. 💡 What to Do If Your Investigation Is Taking Too Long If your case has been open for over a week and you are continuing to experience traffic loss, take the following steps: 1. Remove the pixel immediately using the steps above to eliminate any potential ongoing impact to your site. 2. Document your traffic data — take screenshots from Google Analytics, Google Search Console, or any other analytics platform showing the drop and its timeline. 3. Contact our support team through the live chat widget and reference your investigation case or ticket number so the team can prioritise your escalation. 💰 How to Request a Subscription Refund Search Atlas reviews refund requests on a case-by-case basis. You may be eligible for a full or partial refund if: - Your issue was directly caused by a Search Atlas product or pixel and remained unresolved for an extended period. - You experienced measurable harm (such as verified traffic loss) during an active investigation. - You request the refund within a reasonable timeframe after identifying the issue. To submit a refund request: 1. Open the live chat widget inside the Search Atlas platform. 2. Type human teammate to connect with a support agent. 3. Provide your account email, a brief description of the issue, your investigation case reference (if available), and any supporting evidence such as traffic screenshots. 4. Our team will review your request and respond with a decision as soon as possible; response time varies by case complexity. Note: Refunds are not automatically issued when an investigation is opened. You must submit a formal request via chat for our team to begin the review process. 🚀 Preventing Future Issues To minimise the risk of tracking conflicts or unexpected traffic changes going forward: - Only install the Search Atlas pixel on pages where tracking is required. - Avoid running multiple conflicting tracking scripts from different SEO platforms simultaneously. - Regularly audit your tag manager containers and remove any unused or outdated scripts. - Monitor your site's performance weekly in Google Search Console to catch drops early. 💬 Need Further Help? 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.

🔄 Change Your OTTO Project Domain (Non-www to www)

🧭 Overview OTTO projects in Search Atlas are tied to a specific domain at the time of creation. If your site uses www.example.com but your OTTO project was created with example.com (or vice versa), OTTO will not apply optimisations to the correct version of your site. Updating a canonical tag or adjusting plugin settings will not fix this — the only correct resolution is to delete the existing project and recreate it with the right domain. This article walks you through that process safely and clearly. ⚠️ Before You Begin Take note of the following before making any changes: - Deleting a project removes all OTTO settings and deployed optimisations linked to that project. OTTO will stop managing your site until the new project is active. - Make a note of any custom configurations, priorities, or rules you have set inside the existing project so you can restore them after recreation. - Confirm which domain version your site actually resolves to. Open your site in a browser and check the address bar — it will show either www or non-www. Use that version when recreating the project. - Ensure your Google Search Console property matches the domain version you plan to use, as OTTO uses this connection to validate and deploy changes. 🗑️ Step 1 — Delete the Existing OTTO Project Navigate to OTTO SEO → All Sites (SEO Automation) in your Search Atlas account and locate the project associated with the incorrect domain. Use the available project management options to delete that project and confirm the deletion when prompted. The project and all its deployed configurations will be removed. Your site content is not affected — only the OTTO management layer is deleted. ➕ Step 2 — Recreate the Project with the Correct Domain From OTTO SEO → All Sites (OTTO SEO Projects), create a new project. When entering the domain, type the correct version — include or omit www to match exactly how your site resolves in a browser. During setup, reconnect your Google Search Console property and select the property that corresponds to the correct domain version. If you use the OTTO WordPress plugin, verify that the site URL inside the plugin matches the new domain you entered and confirm the connected domain is consistent. Allow OTTO to re-crawl and re-analyse your site once setup is complete. 🔁 Step 3 — Restore Your Previous Settings Once the new project is active, reapply any custom configurations you noted before deleting the original project. Verify that OTTO is actively managing the correct domain version by checking that optimisations are being applied as expected. 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.

🔌 Search Atlas Pixel Compatibility with Website Platforms

🧩 What Is the Search Atlas Pixel? The Search Atlas pixel is a small JavaScript snippet you place on your website. It tracks visitor behaviour, conversion events, and campaign performance — feeding data back into your Search Atlas dashboard so you can measure ROI accurately. Whether the pixel works on your site depends on whether your website platform allows custom JavaScript or third-party tracking scripts. 🚗 Car Dealer Platforms — Compatibility Overview Car dealership websites are often managed by specialist automotive platforms. Pixel acceptance varies by provider. The table below summarises the most common platforms and their compatibility status. - DealerSocket / CDK Digital (now Tekion): Supports third-party pixels via the Tag Manager section in the admin panel or through a dedicated script injection field. Custom JavaScript is permitted on most package tiers. - DealerInspire: Allows third-party tracking scripts. You can add the Search Atlas pixel in the site's global header/footer script area. Contact your DealerInspire account rep if the option is not visible — it may need to be enabled on your account. - Dealer.com (Cox Automotive): Supports pixel installation through their third-party tag management interface. Access is usually available in the Settings → Tracking & Analytics section of your Dealer.com dashboard. - Sincro (formerly Digital Air Strike): Permits custom scripts. Use the script injection option in the platform's admin area or request placement assistance from Sincro support. - Gubagoo / Widewail / other chat/lead widgets: These are add-ons, not full CMS platforms. The pixel must be placed on the underlying site platform, not inside these widgets. - WordPress-based dealer sites: Fully compatible. Install the pixel via a header plugin (e.g., Insert Headers and Footers) or directly in the theme's <head> section. If your platform is not listed above, the key question to ask your platform provider is: "Can I add a custom JavaScript snippet to the global header or footer of my site?" If the answer is yes, the Search Atlas pixel will work. 📋 General Platform Compatibility — Other Common Providers - Shopify: Add the pixel under Online Store → Themes → Edit Code → theme.liquid before the closing </head> tag, or use the Custom Pixel feature under Settings → Customer Events. - Wix: Use the Marketing Integrations → Custom Code section in the Wix dashboard. Paste the pixel in the Head section, set it to load on All Pages. - Squarespace: Go to Settings → Advanced → Code Injection and paste the pixel into the Header field. - Webflow: Open Project Settings → Custom Code → Head Code and paste the pixel there. Publish after saving. - Search Atlas Website Studio: Fully compatible and natively integrated. No manual pixel installation is needed if you built your site inside Search Atlas. Navigate to the left sidebar and select Website Studio (URL: /website-studio) to manage your site settings. ⚙️ How to Find and Copy Your Search Atlas Pixel 1. Log in to your Search Atlas account. 2. Navigate to the relevant project or campaign dashboard. 3. Locate the Tracking or Pixel settings section within your project. 4. Copy the full JavaScript snippet provided. 5. Paste it into the global header of your website platform (before the closing </head> tag) following the steps for your specific platform above. 6. Save and publish your changes. 7. Return to Search Atlas and use the pixel verification tool (if available) to confirm the pixel is firing correctly. 🚫 What If My Platform Doesn't Allow Custom Scripts? Some platforms — particularly highly managed or white-labelled automotive platforms — restrict custom JavaScript for security or compliance reasons. If your provider does not allow script injection, here are your options: - Ask your platform provider for a tag manager integration. Many restricted platforms still allow Google Tag Manager (GTM). If GTM is permitted, you can deploy the Search Atlas pixel as a custom HTML tag inside GTM without touching the site's code directly. - Request an exception from your provider. Some platforms can whitelist specific third-party domains. Provide them with the Search Atlas pixel domain and ask if they can permit it. - Use UTM parameters as an alternative. If pixel placement is not possible, you can still track campaign performance using UTM parameters on your ad URLs. This provides session-level data inside Search Atlas without requiring a pixel on your site. - Switch to Search Atlas Website Studio. If you have flexibility over your website infrastructure, building or migrating your site to Search Atlas Website Studio (left sidebar → Website Studio, URL: /website-studio) removes all compatibility concerns, as tracking is built in natively. ✅ Quick Compatibility Checklist - Does your platform allow custom JavaScript in the site header or footer? - Does your platform support Google Tag Manager? - Do you have admin-level access to your website's code or settings? - Has your platform provider confirmed they do not block third-party tracking domains? If you answered yes to any of the first three questions, the Search Atlas pixel can be deployed on your site. 💬 Need Help With Your Specific Platform? 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.

🔍 Identify Your Search Atlas Dynamic Optimization Snippet

🧩 What Is the Dynamic Optimization Snippet? When you activate OTTO SEO in Search Atlas, a small JavaScript code snippet is automatically injected into your website. This snippet powers dynamic on-page optimizations — such as title tag and meta description updates — without requiring manual changes to your site's source code. If you or your development team spot an unfamiliar script on your website, this article will help you confirm whether it belongs to Search Atlas. 🔎 How to Recognise the Search Atlas Snippet The Search Atlas dynamic optimization snippet has several identifying characteristics. Look for the following when inspecting your site's source code or a tag manager: - Script source domain: The snippet loads from a Search Atlas domain. The script src attribute will reference searchatlas.com or a subdomain associated with the platform. - Snippet label or comment: The code block may include an inline comment or attribute identifying it as the OTTO SEO dynamic optimization script. - Placement: The snippet is typically injected in the <head> section of your page HTML, which is standard practice for SEO-related scripts. - Asynchronous loading: The script tag will usually include an async or defer attribute to avoid blocking page rendering. ✅ How to Confirm the Snippet Is from Your Search Atlas Account Follow these steps to verify the snippet is connected to your specific Search Atlas account and was not added by an unknown source: 1. Log in to your Search Atlas account. 2. In the left sidebar, navigate to Site Metrics and select the website you are investigating. 3. Look for the OTTO SEO section within your project settings. If OTTO SEO has been activated for that site, the dynamic optimization snippet will be present on your website. 4. Compare the site ID or token embedded in the script on your website with the identifier shown inside your Search Atlas OTTO SEO settings. A matching ID confirms the snippet belongs to your account. If OTTO SEO is shown as active for your site in Search Atlas, the snippet you found is legitimate and intentional. ⚠️ What If OTTO SEO Is Not Activated in Your Account? If you find the snippet on your website but OTTO SEO does not appear to be active in your Search Atlas account, consider the following scenarios: - Another user on your account activated OTTO SEO. Check with other team members or admins who have access to your Search Atlas workspace. - OTTO SEO was previously activated then deactivated. In some cases, deactivating OTTO SEO may not automatically remove the snippet from your site if it was added manually or via a plugin. - The snippet belongs to a different service. If the script source domain does not reference searchatlas.com, the code was not added by Search Atlas and should be investigated separately with your development team. 🛠️ How to Remove the Snippet If Needed If you want to remove the Search Atlas dynamic optimization snippet from your website, follow these steps: 1. Log in to Search Atlas and go to Site Metrics in the left sidebar. 2. Open the relevant site project and locate the OTTO SEO settings. 3. Deactivate OTTO SEO for that site. Search Atlas will stop applying dynamic optimizations. 4. If the snippet was added manually to your site's code or through a plugin, ask your developer to locate and remove the script tag from the <head> section of your site template. Always make a backup of your site before editing theme files or removing scripts directly from your codebase. 💬 Still Not Sure? Get Help From Our Team If you have reviewed the steps above and still cannot determine whether the snippet belongs to Search Atlas or another service, our team is ready to help. 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. Additional Notes Element ID: id='sa-dynamic-optimization'; Domain: dashboard.atlascoremarketing.com; Base64-encoded loader pattern. Search tip: Ctrl+F for 'sa-dynamic-optimization' in page source to instantly locate the snippet.

🔧 OTTO Script Installation and Logo Positioning Guide

Overview Two of the most common OTTO setup issues are locating the installation script and correcting logo positioning on H1 elements. This guide walks you through how to retrieve your OTTO script from the Search Atlas UI, install it correctly, and resolve logo H1 conflicts in your theme before escalating to support. Before You Begin - Make sure you have editor or admin access to your website's theme or CMS. - Confirm your Search Atlas account has an active OTTO session for the target website. - Have your website URL and project name ready in case you need to escalate. OTTO Script Installation The OTTO script is unique to each website you connect. To retrieve your script, follow these steps inside Search Atlas: 1. Log in to Search Atlas and open OTTO SEO → All Sites (SEO Automation) from the left sidebar. 2. Select the target website from your list of connected projects. 3. Locate the area within the OTTO dashboard where your unique script snippet is displayed — the script is tied to that specific website and should be visible once you have selected your project. 4. Copy the full script snippet. Key installation guidance: - Paste the script inside the <head> tag of your website, as high up as possible. - It must be pasted as a single unbroken line — do not split it across multiple lines. - Save and publish your changes after pasting the script. After installation, return to the OTTO dashboard and re-run diagnostics to confirm the script is detected. If diagnostics continue to fail, note the exact error message and the timestamp before escalating. Logo Positioning on H1 Elements A frequent issue during OTTO setup is the site logo being detected as or wrapped in an <h1> tag rather than a standard image or link element. This can interfere with OTTO's on-page analysis and may trigger logo-related warnings in your diagnostics. Try the following self-serve fixes based on your CMS or page builder before contacting support: - WordPress (Classic Theme / custom header.php): Access your theme's header template file through your theme editor or file manager. Locate the logo markup and confirm it is wrapped in a <div> or <a> tag, not an <h1>. If it is inside an <h1>, change that tag to a non-heading element such as a <div>, then save your changes. - Page builders and other CMS platforms: Check your theme's header or logo settings for an option that controls the HTML element used to wrap the logo. Some themes output the logo inside an H1 on the homepage by default. If your theme or page builder does not offer a native option to change this, you can apply a custom CSS rule that suppresses the H1 styling on the logo element without removing it from the page structure. - General approach: Use your browser's Inspect Element tool to view the live HTML around your logo. If it is wrapped in an <h1>, identify the theme file or setting responsible and update accordingly. After making changes, re-run OTTO diagnostics to confirm the issue is resolved. If you are unable to locate the script in your OTTO dashboard, or if logo H1 warnings persist after trying the steps above, have the following information ready before contacting support: your project name, the exact diagnostic error message, and a timestamp of when the issue occurred. 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.

🔍 What Happens When You Remove the OTTO Pixel

🧩 What Is the OTTO Pixel? The OTTO pixel is a small snippet of code placed on your website that allows OTTO SEO to monitor your pages, trigger automations, and apply on-page optimizations in real time. It acts as the communication bridge between your site and the OTTO SEO engine inside Search Atlas. 💡 Does Removing the Pixel Undo Past SEO Work? It depends on how the changes were applied. OTTO applies most changes through the OTTO pixel script at page load, so if the pixel is removed or the OTTO project is deleted, those pixel-served changes will stop showing on the site. Changes that were written directly into the site's CMS — for example through the WordPress plugin — can remain in place after the pixel is removed. Think of the pixel as an active connection that serves most optimizations. Only changes written directly into your CMS exist independently of the pixel. ⚙️ What Does Stop Working After Removal While your past optimizations are preserved, removing the pixel does disable OTTO's ongoing and future capabilities. Here is what will no longer function once the pixel is removed: - Real-time monitoring: OTTO will no longer be able to detect changes on your pages or identify new issues as they arise. - New automations: Any optimization tasks that have not yet been executed will not be applied. - Dynamic updates: OTTO will be unable to push additional improvements or respond to changes in your site structure. - Page crawling triggers: New or uncrawled pages will not be discovered and queued for optimization. 📋 What Stays Intact After Removal The following remain unaffected when you remove the pixel: - Changes that were written directly into your site's CMS (for example through the WordPress plugin) - Your historical data and reports inside Search Atlas 🚀 Should You Remove the Pixel? Before removing the OTTO pixel, consider why you want to take this step. Common reasons and recommendations include: - Temporary pause: If you want to pause OTTO activity without losing your setup, consider using the Freeze option inside OTTO SEO instead of removing the pixel entirely. Navigate to Left sidebar → OTTO SEO → All Sites (SEO Automation) and use the Freeze sites action to pause activity while keeping the pixel in place. - Site migration or redesign: If your site is undergoing major structural changes, removing the pixel temporarily is reasonable. You can reinstall it once the work is complete and reactivate OTTO from the same screen. - White-label or client handoff: If you are managing a site on behalf of a client and handing it over, be aware that pixel-served changes will stop showing once the pixel is removed; only changes written directly into the CMS will remain. 🛠️ How to Remove or Reinstall the Pixel 1. Go to Left sidebar → OTTO SEO → All Sites (SEO Automation) (URL: /seo-automation-v3). 2. Locate the site you want to manage in your active or frozen site list. 3. Follow the pixel removal or reinstallation instructions provided within the OTTO SEO interface for your specific site setup (WordPress, custom HTML, or tag manager). 4. If reinstalling, allow OTTO a short period to re-crawl your pages and resume monitoring before expecting new optimizations to trigger. ❓ Still Have Questions? 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.

🔍 OTTO Pixel Removal and SEO Work Preservation

🧩 What Is the OTTO Pixel? The OTTO pixel is a small JavaScript snippet you install on your website to connect it to Search Atlas's OTTO SEO automation engine. It allows OTTO to detect your site's technical environment, deploy on-page optimisations, and monitor implementation status in real time. ❓ Will Removing the Pixel Undo My SEO Work? It depends on how the changes were applied. OTTO applies most changes through the OTTO pixel script at page load. If the pixel is removed or the OTTO project is deleted, those pixel-served changes will stop showing on your site. However, changes that were written directly into your site's CMS (for example through the WordPress plugin) can remain in place independently of the pixel. ⚙️ What Does the Pixel Actually Do? Understanding the pixel's role makes it easier to see why its removal is safe for existing work. The pixel is responsible for: - Site detection: Helping OTTO identify your CMS, plugins, and technical setup so it can deploy the right optimisations. - Status monitoring: Reporting back to Search Atlas so the platform can confirm which optimisations are active on your site. - Ongoing automation: Enabling OTTO to continue pushing new or updated recommendations to your site in real time. Because most changes are served through the pixel at page load, removing the pixel will stop those pixel-served changes from appearing. Changes written directly into your CMS (for example via the WordPress plugin) can remain in place. ⚠️ What You Will Lose Without the Pixel While your existing optimisations stay intact, removing the pixel does affect OTTO's ability to work going forward. Specifically, you will lose: - The ability for OTTO to deploy new SEO recommendations to your site automatically. - Real-time implementation status updates inside the Search Atlas platform. - OTTO's ability to detect changes in your site's technical environment and adapt accordingly. - Access to certain monitoring and reporting signals that rely on pixel data. In short, removing the pixel pauses OTTO's active automation and stops pixel-served changes from displaying, though changes written directly into your CMS can remain. 🔄 How to Reinstall the Pixel If Needed If you removed the pixel and want to resume OTTO automation, reinstalling it is straightforward: 1. Open the OTTO SEO section of the Search Atlas platform. 2. Select the relevant site you want to reconnect. 3. Follow the on-screen instructions to copy and reinstall the pixel snippet on your website. 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.

⚡ OTTO Installation Methods Compared: Plugin vs. Script

Overview OTTO can be installed on your website using three methods: the WordPress plugin, a script placed in your header or footer, or via Google Tag Manager (GTM). A common question is whether these methods perform identically and whether the WordPress plugin is mandatory for certain features like automatic updates. This article outlines the general differences between each method and when each may be the right choice for your site. Are All Installation Methods Equivalent? For core OTTO functionality — including on-page SEO automation, schema deployment, and real-time optimizations — the three installation methods are designed to get OTTO active on your site. The method used to load the script may affect certain aspects of how OTTO is managed, so it is worth understanding the differences before choosing one. - WordPress Plugin: Installs and manages the OTTO script automatically within your WordPress environment. - Header/Footer Script: A manually placed JavaScript snippet added directly to your site's <head> or before the closing </body> tag. - Google Tag Manager (GTM): The OTTO script is deployed as a custom HTML tag through your GTM container. Once the script is active on your site and your OTTO session is enabled in Search Atlas, OTTO will begin working on your pages. If you are unsure which method is best suited to your site's setup, our support team can help you determine the right approach. Automatic Updates: Plugin vs. Script One frequently asked question concerns how updates are handled across installation methods. - WordPress Plugin: The plugin receives updates through the standard WordPress update mechanism, just like any other WordPress plugin — automatically or with a single click in your WordPress dashboard. - Header/Footer Script: The JavaScript snippet references an externally hosted script. How and when updates to that script are applied may vary — contact our support team to confirm the current update behavior for this method. - GTM: Similar to the header/footer script method, the tag in GTM references an externally hosted script. Please confirm with our support team how updates are handled for GTM-deployed instances. If you have questions about whether you need to take any manual action to keep your OTTO installation current, reach out to our team for confirmation specific to your setup. When to Use Each Method - WordPress Plugin — Recommended for WordPress sites where you want the simplest setup experience, built-in script management, and compatibility checks handled automatically. - Header/Footer Script — A flexible option for non-WordPress sites or situations where you have direct access to your site's theme or template files. - GTM — Useful when your team manages multiple tags through GTM and prefers a centralized deployment workflow. 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.

🔧 Installing OTTO Tracking on a Website Studio Site

If you built your site from scratch in Website Studio and want to track it with OTTO, you do not need a separate plugin or integration. Website Studio includes a built-in option for adding custom scripts directly in the project settings, and this is where your OTTO tracking script goes. Where to Find the Setting Open your project in Website Studio and navigate to the project settings area. Look for a section dedicated to custom scripts or code embeddings — this is where you can inject code into your site's page header. How to Install the OTTO Script Within the custom scripts or embeddings section of your project settings, locate the field for header code — this is where scripts injected into the page's <head> belong. Tracking pixels such as OTTO are meant to go in the header area rather than the footer. To install OTTO, copy the OTTO tracking script from your OTTO project and paste it into the header code field in your Website Studio project settings, then save your changes. What to Expect This is a general-purpose custom code field rather than a dedicated, one-click OTTO integration. There is no automatic site detection step for Website Studio the way there might be for some other platforms, so double-check that the full script tag is pasted correctly before saving. Once saved, OTTO will begin tracking the site the same way it does on any other website where the script has been added to the header. 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.

📝 Bulk Update and Deploy Meta Descriptions in OTTO SEO

🔍 Overview OTTO SEO lets you update and deploy meta descriptions in bulk — no special settings required. You can review AI-generated suggestions, edit them as needed, select all pages at once, and deploy everything in a single action. This article walks you through the full process. 🧭 How to Navigate to Meta Descriptions in OTTO SEO 1. Log in to your Search Atlas account. 2. In the left sidebar, click OTTO SEO → All Sites (SEO Automation) (or go to /seo-automation-v3). 3. Select the project you want to work on. 4. In the OTTO dashboard, locate the Meta Descriptions issue type — it is listed under the on-page SEO recommendations section. 5. Click on Meta Descriptions to expand the full list of pages with suggestions. ✏️ How to Review and Edit Meta Description Suggestions Before deploying, take a moment to review the AI-generated suggestions. You can accept them as-is or customise them for any page. 1. With the Meta Descriptions issue type open, you will see a table listing every page that has a suggestion ready. 2. Click the suggestion text for any individual page to open the inline editor. 3. Make your edits, then click outside the field or press Enter to save the change. 4. Repeat for any other pages you want to customise before deploying. Tip: OTTO automatically generates suggestions based on your page content and target keywords. If a suggestion looks good, you do not need to edit it — simply leave it as-is and include it in your bulk selection. ✅ How to Select All Meta Descriptions at Once You do not need to enable any special setting to select multiple pages. The bulk-select feature is available by default. 1. In the Meta Descriptions table, check the checkbox in the header row (top-left of the table). This selects all pages currently visible in the list. 2. If your list spans multiple pages, use the page size control to show more rows per page so you can select all at once. 3. Confirm the total number of selected items shown in the bulk action bar that appears at the bottom or top of the table. 🚀 How to Deploy All Selected Meta Descriptions 1. With your pages selected, click the Deploy button in the bulk action bar. 2. A confirmation prompt will appear showing the number of changes about to be deployed. Review this and click Confirm. 3. OTTO will push all selected meta descriptions to your connected CMS or website simultaneously. 4. Once complete, the status column for each deployed page will update to reflect the change. Note: Deployment requires your site to be connected to OTTO SEO. If your site runs on WordPress, make sure the Search Atlas WordPress plugin is installed and active. If deployments succeed but changes do not appear on your live site, clear your site cache and allow a few minutes for the update to propagate. ⚠️ Troubleshooting Common Issues - Meta descriptions are not updating on the live site after deployment: Clear your WordPress or hosting cache. If the issue persists, verify the Search Atlas plugin is up to date and that OTTO has write permissions for your CMS. - The Deploy button is greyed out: Ensure at least one page is selected using the checkboxes. Also confirm your site connection is active under your OTTO project settings. - Some pages are missing from the list: OTTO only surfaces pages that have been crawled and have an actionable suggestion. Run a fresh crawl from the OTTO dashboard to pick up newly published pages. - Changes show as deployed in OTTO but are not visible on the website: This is a known sync issue with certain WordPress configurations. Check that the plugin has the correct API credentials and retry deployment for the affected URLs. 💡 Tips for Faster Bulk Editing - Use the filter and sort controls in the Meta Descriptions table to prioritise high-traffic pages first. - Accept OTTO's AI suggestions for lower-priority pages and focus manual editing time on your most important URLs. - After deploying, use Search Atlas's rank tracking tools to monitor whether the updated meta descriptions improve click-through rates in search results. 🙋 Need More Help? 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.

🔗 Share OTTO Installation Link With Your Developer

🧭 Overview If you want a developer or team member to install OTTO SEO on your website, you don't need to walk them through the platform yourself. Search Atlas gives you a direct installation link and the credentials they need — all in one place. This guide shows you exactly where to find and share that information. 🛠️ What Your Developer Will Need To install OTTO SEO, your developer needs two things: - The OTTO installation link — a unique URL that connects your website to OTTO SEO - Your site credentials — such as your WordPress login or FTP/hosting access, which you manage and share securely outside the platform Search Atlas provides the installation link directly inside the OTTO SEO section. You are responsible for sharing your site credentials with your developer through a secure channel of your choice (for example, a password manager or encrypted message). 📋 How to Find and Copy Your OTTO Installation Link 1. Log in to your Search Atlas account. 2. In the left sidebar, click OTTO SEO, then All Sites (SEO Automation). You can also navigate directly to /seo-automation-v3. 3. Select the website project you want to install OTTO on. 4. Look for the installation link or setup instructions displayed on the OTTO dashboard. This is your unique link tied to that specific site project. 5. Click the copy icon or highlight the link and copy it manually. 6. Paste the link into an email, message, or shared document and send it to your developer. 📨 How to Share the Link Securely Once you have copied the installation link, you can share it through any channel you normally use to communicate with your developer — such as email, Slack, or a project management tool. Keep the following best practices in mind: - Share the OTTO installation link only with trusted individuals who are working on your site. - Send your site login credentials (WordPress username and password, for example) separately and through a secure method such as a password manager sharing feature. - Avoid sharing sensitive credentials in plain text over unencrypted channels. ✅ What Happens After Your Developer Uses the Link Once your developer visits the installation link and completes the setup steps on your website, OTTO SEO will be connected to your Search Atlas project. You can then return to the OTTO SEO section in the left sidebar to confirm the connection is active and begin running automations. ❓ Frequently Asked Questions - Can I generate a new installation link? The installation link is tied to your specific site project. If you need a fresh link or suspect the link was shared with the wrong person, contact support using the chat widget below. - Does my developer need a Search Atlas account? No. Your developer only needs the installation link and access to your website backend (such as WordPress) to complete the setup. - Can I install OTTO on multiple sites? Yes. Each site project in Search Atlas has its own unique installation link. Repeat the steps above for each site. 💬 Need Help? 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.

🔌 Remove OTTO SEO From Your Website Completely

🧭 Overview If you want to stop OTTO from managing SEO on your website, you need to complete two steps: disengage OTTO SEO automation and remove the OTTO pixel from your site. If you are unsure which option or button to use to disengage OTTO in the current interface, contact our support team — they can confirm the exact control name and location for your account. ⚠️ Before You Begin - Make sure you are logged in to your Search Atlas account. - Confirm you have admin access to the website you want to remove OTTO from. - If your site runs on WordPress, you will also need access to your WordPress admin dashboard to remove the OTTO pixel plugin. 🛑 Step 1: Disengage OTTO SEO Automation This step stops OTTO from making automated SEO changes to your website. 1. Log in to your Search Atlas account and navigate to the OTTO SEO section of the platform. 2. Locate the website you want to remove OTTO from — for example, www.mrperfectplumbing.com. 3. Look for the option to disengage or disconnect OTTO's automation for that site. The exact label may vary depending on your account view — if you cannot locate it, please reach out to our support team before proceeding. 4. Select the disengage option and confirm the action when prompted. Once completed, OTTO will stop applying automated SEO changes to your website. Your existing content and any previously applied changes will remain in place until you manually update them. 🧹 Step 2: Remove the OTTO Pixel From Your WordPress Site The OTTO pixel is a small piece of code that connects your website to Search Atlas. After disengaging OTTO, you should also remove the pixel to fully disconnect your site. If you installed the OTTO pixel using the Search Atlas WordPress plugin: 1. Log in to your WordPress admin dashboard. 2. Go to Plugins → Installed Plugins. 3. Find the Search Atlas or OTTO SEO plugin. 4. Click Deactivate, then click Delete to remove it completely. If you installed the OTTO pixel by manually adding code to your theme or header: 1. Log in to your WordPress admin dashboard. 2. Go to Appearance → Theme File Editor (or use a header plugin such as Insert Headers and Footers). 3. Locate the OTTO pixel script tag in your header.php file or the relevant header section. 4. Delete the OTTO pixel script snippet. 5. Save your changes. If you used a third-party tag manager such as Google Tag Manager: 1. Open your tag manager account. 2. Find the tag associated with the OTTO pixel or Search Atlas. 3. Pause or delete the tag, then publish the updated container. 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.

🔍 Verify OTTO Pixel After Website Rebuild

🧭 Overview When you rebuild your website on the same domain — for example, migrating from WordPress to a platform like Lovable — the OTTO pixel may no longer be present on the new site, even though Search Atlas still shows a previously verified status. This article walks you through how to confirm the pixel is correctly installed on your new site and that Search Atlas is actively tracking it. ⚠️ Why This Happens Search Atlas stores pixel verification based on a previous successful check. When you rebuild your site, the new platform replaces all existing code, which means the OTTO pixel snippet is removed along with the old site's files. Because the domain itself has not changed, Search Atlas may not automatically detect that the pixel is missing. You need to manually re-install and re-verify the pixel on the new site. 🛠️ Step 1 — Locate Your OTTO Pixel Snippet 1. In the left sidebar, click OTTO SEO → All Sites (SEO Automation) to open the OTTO SEO dashboard. 2. Find your website in the list and click on it to open its settings. 3. Navigate to the pixel installation section and copy your unique OTTO pixel snippet. Keep this snippet ready — you will paste it into your new website in the next step. 💻 Step 2 — Install the Pixel on Your New Site The exact steps vary by platform, but the goal is the same: place the OTTO pixel snippet in the section of every page on your new site. - Lovable or similar no-code builders: Look for a custom code or HTML injection setting, typically found in your project settings under "Custom Code" or "Head Tags." Paste the pixel snippet there so it loads site-wide. - Google Tag Manager: Create a new Custom HTML tag, paste the pixel snippet, and set the trigger to fire on All Pages. Publish the container after saving. - Direct HTML: If you have access to the site's source files, paste the snippet inside the tag of your base template or layout file. ✅ Step 3 — Verify the Pixel Is Firing After installing the pixel, confirm it is actually loading on your live site before triggering re-verification in Search Atlas. 1. Open your website in a browser and go to any page. 2. Right-click the page and select Inspect (or press F12) to open Developer Tools. 3. Go to the Network tab and reload the page. 4. In the filter bar, search for otto or your domain's pixel identifier. You should see a network request confirming the pixel fired successfully. 5. Alternatively, use a browser extension like Tag Assistant or PixelMe to detect tracking pixels on the page. If no pixel request appears, double-check that the snippet was saved correctly in your platform's settings and that the code is not blocked by a cookie consent tool or Content Security Policy. 🔄 Step 4 — Re-Verify the Pixel in Search Atlas 1. Return to OTTO SEO → All Sites (SEO Automation) in the left sidebar. 2. Open your website's OTTO settings. 3. Locate the pixel status indicator and click the option to re-verify or check pixel status. 4. Search Atlas will make a live check of your domain. Once the pixel is detected, the status will update to active and tracking will resume for your new site. Important: If the status shows as verified but you suspect it is stale from your old site, trigger a manual re-verification anyway. A green status is only reliable when it reflects a recent, successful check against your current live site. 🚨 Common Issues and Fixes - Pixel not detected after installation: Confirm the snippet is placed inside the tag, not the body. Some builders place custom code in the footer by default — check your platform's settings carefully. - Status stays "verified" but site is new: This is a stale status from your previous site. Always manually trigger re-verification after a rebuild. - Cookie consent blocking the pixel: Make sure your cookie consent tool is configured to allow analytics and tracking scripts to load, or whitelist the OTTO pixel domain. - Pixel fires on some pages but not others: Your snippet may be placed on a specific template rather than a global layout. Add it to a site-wide header or use Google Tag Manager with an All Pages trigger. 💬 Need More Help? 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.

🔍 Why OTTO Schema Isn't Detected by Static Validators

📋 Understanding OTTO Schema Deployment OTTO deploys schema markup by injecting it into the page using client-side JavaScript after the initial HTML loads. This means the schema code does not exist in the static HTML source that most validation tools fetch and analyze. 🛠️ Why Static Validators Show 'No Items Detected' Tools such as Google Rich Results Test and Schema.org Validator operate by requesting the raw HTML of a URL and parsing it immediately. They do not execute JavaScript, so any schema added dynamically after page load remains invisible to them. This is expected behavior for client-side schema injection. ✅ Correct Ways to Verify OTTO Schema 1. Open the live page in Chrome and use Inspect Element (right-click → Inspect) to view the rendered DOM. Search for application/ld+json or your schema type to confirm injection. 2. Use Google Search Console URL Inspection tool and click Live Test. This runs a headless Chrome instance that executes JavaScript, allowing it to see the deployed schema. 3. Check the OTTO dashboard under OTTO SEO → All Sites (SEO Automation) → Active to confirm the schema deployment status shows Deployed for the target URL. 🚫 Common Misdiagnoses to Avoid - Caching issues – Clearing cache or regenerating schema will not make static validators detect client-side code. - CMS or generator errors – The schema is not rendered server-side, so CMS rendering problems are unrelated. - NLP-disabled errors – These are unrelated to schema visibility in static validators. 📌 Key Takeaway If OTTO shows schema as Deployed but static validators report No items detected, the schema is working as designed. Verify using browser DevTools or Google Search Console Live Test instead. 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.

🔍 Why OTTO Flags Fewer Meta Description Pages

🧭 Overview When OTTO audits your site, you may notice that the number of pages flagged for missing meta descriptions is lower than the total number of pages crawled for title tags. This is expected behaviour, not a bug or a crawl limit issue. This article explains exactly why the counts differ and where your pages go after OTTO processes them. ⚙️ How OTTO Detects Missing Meta Descriptions OTTO crawls your site and checks every eligible page for a meta description. When it detects a page with a missing or empty meta description, it does two things in sequence: 1. It flags the page as needing a meta description. 2. It automatically generates an AI-powered meta description suggestion for that page. Once the AI suggestion is generated, the page is moved out of the main flagged issues list and into a separate task queue called Meta Description Replacements. This is an intentional part of OTTO's workflow — it signals that the page no longer needs detection attention because a suggested fix is already waiting for your review. 📋 Understanding the Two Separate Queues It helps to think of OTTO's meta description workflow as two distinct stages: - Flagged Issues queue: Pages where a missing meta description has been detected but an AI suggestion has not yet been generated. The count here reflects pages still awaiting processing. - Meta Description Replacements queue: Pages where OTTO has already generated an AI meta description suggestion and the change is ready for you to approve or edit. These pages are no longer shown in the main flagged count. This is why your flagged count (for example, 136 pages) appears lower than the total crawled count (for example, 220 pages). The remaining pages have already progressed to the Replacements queue — they are not missing from detection. 🔢 Why the Counts Differ from Title Tag Crawls Title tag audits and meta description audits run as separate checks within OTTO. Each check has its own flagging logic, queue, and processing state. A page crawled for title tags is counted independently from a page processed for meta descriptions. The two numbers are not expected to match, and a difference between them does not indicate a crawl limit problem or a missed detection. If you crawled 220 pages for title tags and only 136 appear flagged for missing meta descriptions, the most likely explanations are: - Some of the 220 pages already have valid meta descriptions and were never flagged. - Some flagged pages have already had AI suggestions generated and moved to the Meta Description Replacements queue. - A small number of pages may have been excluded based on page type or crawl rules you have configured. 🗂️ How to Find Pages in the Meta Description Replacements Queue To review all pages where OTTO has generated AI meta description suggestions, follow these steps: 1. In the left sidebar, click OTTO SEO, then open All Sites (SEO Automation). 2. Locate the Meta Description Replacements task section within your active OTTO project. 3. Review each suggestion. You can approve, edit, or dismiss individual recommendations before they are deployed to your site. Pages in this queue are fully tracked and actioned — they have not been lost or skipped. ✅ What to Do If You Believe Pages Are Genuinely Missing If after checking both queues you still believe specific pages with missing meta descriptions are not being detected, consider the following: - Check your crawl scope: Confirm that the pages in question fall within the URLs included in your OTTO project crawl settings. - Re-run the crawl: Trigger a fresh crawl from your OTTO project settings to capture any recently published or updated pages. - Check page indexability: Pages blocked by robots.txt, set to noindex, or excluded via crawl filters will not be audited by OTTO. - Review crawl page limits: If your plan has a crawl page cap and your site exceeds it, some pages may not be reached. You can review your current limit inside the OTTO project settings. 📌 Key Takeaway A lower flagged count does not mean OTTO missed your pages. Pages with missing meta descriptions that have received an AI suggestion are intentionally moved to the Meta Description Replacements queue. Always check both the flagged issues list and the Replacements queue together to get a complete picture of your meta description coverage. 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.

📊 Find OTTO Pixel Data Options in Search Atlas

📋 Overview Once the OTTO code is installed and active on your website, Search Atlas unlocks pixel data options that give you deeper insight into your site's SEO performance. A common point of confusion is where to find these options inside the platform. This article walks you through the exact location. 🔍 Prerequisites - You have an active Search Atlas account. - The OTTO code has been successfully installed on your website and is confirmed as active. - Your site has been connected inside Search Atlas. 📍 Where to Find OTTO Pixel Data Options Follow these steps to locate the OTTO pixel data options after your OTTO code is active: 1. Log in to your Search Atlas account. 2. In the left sidebar, click OTTO SEO, then open SEO Automation inside it. This takes you to the OTTO SEO dashboard (/seo-automation-v3). 3. Select the website you have connected and for which the OTTO code is active. 4. Once inside that site's OTTO dashboard, look for the pixel data options section. This section becomes visible and interactive only after Search Atlas confirms the OTTO code is live on your site. If the pixel data options do not appear, the most common reason is that the OTTO code has not yet been detected as active. Double-check that the code snippet is correctly placed in your website's <head> tag and that the site has been crawled. ⚙️ What Are OTTO Pixel Data Options? OTTO pixel data options allow Search Atlas to collect and surface real-time behavioural and performance signals directly from your website. These signals help OTTO make smarter, data-driven SEO recommendations tailored to your actual visitor activity. Options may include: - Pixel tracking status — confirms whether the pixel is firing correctly. - Data collection preferences — control what types of on-site signals are captured. - Signal reporting — view aggregated pixel data feeding into your SEO automation. 🛠️ Troubleshooting: Options Still Not Visible If you have confirmed the OTTO code is active but still cannot see the pixel data options, try the following: - Refresh the page — detection can take a few minutes after the code goes live. - Verify code placement — the OTTO snippet must be in the <head> section of every page, not just the homepage. - Check for conflicting scripts — ad blockers or tag managers can sometimes prevent the pixel from firing during verification. - Re-run the OTTO code check — inside the OTTO SEO dashboard, use the verify or re-check option if available for your connected site. 💬 Need More Help? 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.

📊 Understanding OTTO Open Graph Description Suggestions

🔍 What Is an Open Graph Description? An Open Graph (OG) description is a specific HTML meta tag (og:description) that controls how your page appears when shared on social platforms like Facebook, LinkedIn, and X (Twitter). It is separate from your standard HTML meta description, and it has its own recommended character limits. ⚙️ Why OTTO Uses Different Character Limits You may notice that OTTO suggests a fix even when your description appears to fall within the commonly cited 120–160 character range for standard meta descriptions. This happens because Open Graph descriptions follow a different standard: - Standard meta description: 120–160 characters recommended for search engine snippets. - Open Graph description: 55–200 characters is the accepted range, but social platforms typically display only the first 55–100 characters before truncating. OTTO is optimised for social sharing performance. Its suggestions prioritise descriptions that display fully and clearly on the widest range of social platforms — not just the technical maximum allowed. 📋 Understanding the 59-Character Suggestion If OTTO flags a 159-character OG description and recommends something closer to 59 characters, it is not an error. Here is what is happening: - Your original description may be technically valid but risks being cut off mid-sentence on platforms like Facebook, which truncates OG descriptions aggressively on mobile. - OTTO targets the safe display threshold — the length most likely to render completely across all major platforms and devices. - A shorter, complete description often outperforms a longer, truncated one for click-through and social engagement. In short, OTTO is optimising for visibility and impact, not just technical compliance. 🛠️ What You Should Do You have two options when OTTO raises this suggestion: 1. Accept the suggestion: Apply OTTO's recommended description if social sharing performance is a priority for that page. The shorter text is crafted to display fully on all major platforms. 2. Keep your original and dismiss the suggestion: If you have a specific reason to retain the longer description — for example, platforms you target support longer previews — you can dismiss the OTTO recommendation without affecting your other optimisations. Neither choice will break your page. This is an optimisation recommendation, not a critical error. 🚀 How to Review OTTO Suggestions in the Platform 1. Go to OTTO SEO in the left sidebar, then open All Sites (SEO Automation) (or navigate to /seo-automation-v3). 2. Select the page or URL flagged by OTTO. 3. Locate the Open Graph section within the suggestions panel. 4. Review the current value and OTTO's recommended replacement. 5. Click Apply to accept or Dismiss to keep your existing description. 💡 Best Practices for Open Graph Descriptions - Keep OG descriptions between 55 and 100 characters for the safest cross-platform display. - Lead with the most important information — do not bury your key message near the end where it may be cut off. - Write in active voice and make the description compelling as a standalone sentence. - Remember that your OG description and your HTML meta description can — and often should — be different texts optimised for their respective purposes. 🙋 Need More Help? 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.

🔄 Migrate Your OTTO Tracking Script Between Websites

🔍 What Is the OTTO Tracking Script? The OTTO tracking script is a small piece of JavaScript code that connects your website to OTTO, Search Atlas's OTTO SEO automation engine. It must be installed on any site you want OTTO to monitor and optimize. When you move to a new website, you need to migrate this script to keep OTTO working correctly. 📍 Step 1: Locate Your OTTO Tracking Script Follow these steps to find the tracking script for your site: 1. Log in to your Search Atlas account. 2. In the left sidebar, click OTTO SEO, then open SEO Automation (URL: /seo-automation-v3). 3. Select the website project that currently has OTTO activated. 4. Navigate to the OTTO Settings or Site Settings section within your project dashboard. 5. Locate the Tracking Script panel. Your unique script snippet will be displayed there. 6. Copy the full script code to your clipboard or a temporary text file — you will need it in Step 4. 🔕 Step 2: Deactivate OTTO on the Old Website Before migrating, deactivate the script on your old site to avoid duplicate tracking, conflicting data, or billing issues tied to an inactive domain. 1. In the same OTTO Settings panel, look for the option to Deactivate OTTO or Disconnect Site. 2. Confirm the deactivation when prompted. OTTO will stop collecting data from the old site immediately. 3. Remove the tracking script from your old website's source code. Depending on your CMS: - WordPress: Remove it from your theme's header.php file, or deactivate the plugin/snippet that injected it. - Shopify: Remove it from the theme.liquid file in your theme editor. - Other CMS or custom site: Delete the script tag from the global <head> section of your site template. 4. Save and publish the changes on your old site. 🌐 Step 3: Add Your New Website to Search Atlas If your new website does not yet have a project in Search Atlas, create one before installing the script. 1. In the left sidebar, click OTTO SEO, then open SEO Automation. 2. Click Add New Site or + New Project. 3. Enter your new website's URL and complete the setup prompts. 4. Once the project is created, open it and navigate to OTTO Settings. 5. Click Activate OTTO to generate a tracking script for the new site. Each site receives its own unique script — do not reuse the script from your old site. 📋 Step 4: Install the Tracking Script on Your New Website Copy and paste the new script into your website's code as close to the top of the <head> section as possible. - WordPress: Paste the script using a header plugin such as Insert Headers and Footers, or add it directly to header.php in your active theme. - Shopify: Go to Online Store → Themes → Edit Code, open theme.liquid, and paste the script inside the <head> tag. - Other CMS or custom site: Paste the script inside the global <head> template file that loads on every page. Save and publish your changes after pasting the script. ✅ Step 5: Validate the Installation After installing the script, confirm that OTTO is receiving data from the new site: 1. Return to Search Atlas and open the new site's project under OTTO SEO > SEO Automation. 2. Check the OTTO Settings panel for a connection status indicator. It should show Connected or Active. 3. If the status shows Not Detected, wait up to 10 minutes and refresh the page, as propagation can take a short time. 4. If the script is still not detected after 10 minutes, use your browser's developer tools (View Source or the Elements tab) to confirm the script tag is present in the <head> of your new site. 5. Correct any copy-paste errors and re-save if needed, then check the status again. ⚠️ Important Notes - Each OTTO tracking script is unique to a specific website project. Never copy a script from one site and paste it on a different domain. - Deactivating the old site first prevents your analytics from mixing data between two domains. - If you are migrating to a subdomain or a staging environment, create a separate project for each to keep data clean. 💬 Need More Help? 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.

🔧 OTTO Installation UUID Configuration by CMS

🧭 What Is the OTTO UUID and Why Does It Matter? When you activate OTTO SEO on your website, Search Atlas generates a unique identifier called a UUID (Universally Unique Identifier). This UUID must be installed on your site so OTTO can communicate with your pages, apply SEO automations, and track implementation status. Without the UUID correctly placed, OTTO cannot deploy changes to your site. Navigate to Left sidebar → OTTO SEO → SEO Automation (URL: /seo-automation-v3) to find your UUID. It will appear during the OTTO onboarding flow or inside your active OTTO project settings. Copy it before following the steps below. ⚙️ WordPress Installation Use one of the two methods below depending on your access level. Method 1 — Header/Footer Plugin (Recommended) 1. Install and activate a plugin such as Insert Headers and Footers from the WordPress plugin directory. 2. Go to Settings → Insert Headers and Footers. 3. Paste the following code into the Scripts in Header field, replacing YOUR_UUID_HERE with your actual UUID: <meta name="otto-site-verification" content="YOUR_UUID_HERE" /> 1. Click Save. 2. Visit your homepage, right-click, select View Page Source, and confirm the meta tag appears inside the <head> section. Method 2 — Theme functions.php 1. In your WordPress dashboard go to Appearance → Theme File Editor. 2. Open functions.php. 3. Add the following code before the closing ?> tag, replacing YOUR_UUID_HERE with your UUID: function otto_uuid_meta() { echo '<meta name="otto-site-verification" content="YOUR_UUID_HERE" />'; } add_action( 'wp_head', 'otto_uuid_meta' ); 1. Click Update File and verify in page source. 🛍️ Shopify Installation 1. From your Shopify admin, go to Online Store → Themes. 2. Next to your active theme, click Actions → Edit Code. 3. Under Layout, open the file named theme.liquid. 4. Locate the opening <head> tag and paste the following line directly after it, replacing YOUR_UUID_HERE with your UUID: <meta name="otto-site-verification" content="YOUR_UUID_HERE" /> 1. Click Save. 2. View your storefront source to confirm the tag is present inside <head>. 🏪 Magento 2 Installation 1. Log in to your Magento Admin Panel. 2. Go to Content → Design → Configuration. 3. Click Edit next to your active store view. 4. Expand the HTML Head section. 5. In the Scripts and Style Sheets field, add the following, replacing YOUR_UUID_HERE with your UUID: <meta name="otto-site-verification" content="YOUR_UUID_HERE" /> 1. Click Save Configuration. 2. Flush the Magento cache under System → Cache Management → Flush Magento Cache. 3. Verify the tag appears in your page source. 💻 Custom HTML / Headless / Any Other CMS If your site is built on a custom stack, a headless CMS (such as Webflow, Next.js, Nuxt, or similar), or any platform not listed above, the installation method is the same — place the UUID meta tag inside the <head> element of every page, or at minimum on your homepage. Add this tag, replacing YOUR_UUID_HERE with your UUID: <meta name="otto-site-verification" content="YOUR_UUID_HERE" /> - Webflow: Go to Project Settings → Custom Code and paste into the Head Code field. - Wix: Go to Settings → Custom Code, add the tag to the Head section and apply to All Pages. - Next.js / Nuxt: Add the meta tag inside your global <Head> component so it renders on every route. - Squarespace: Go to Settings → Advanced → Code Injection and paste into the Header field. ✅ How to Validate Your UUID Installation 1. Open your website in a browser and navigate to your homepage. 2. Right-click anywhere on the page and select View Page Source (or press Ctrl+U / Cmd+U). 3. Press Ctrl+F / Cmd+F and search for otto-site-verification. 4. Confirm the meta tag is present and your UUID value is correct. 5. Return to Search Atlas at Left sidebar → OTTO SEO → SEO Automation and check your OTTO project status — it should update to Connected within a few minutes. ⚠️ Common Issues and Fixes - Tag not appearing in source: A caching plugin or CDN may be serving a cached version. Clear all caches and check again. - OTTO still shows as disconnected: Allow up to 10 minutes after installation for the verification to complete. If the issue persists, double-check that the UUID matches exactly what is shown in your OTTO project settings — no extra spaces or characters. - Multiple store views (Magento): Repeat the configuration steps for each store view that OTTO should manage. - Headless CMS with server-side rendering: Ensure the meta tag is rendered in the initial HTML response, not injected only by client-side JavaScript, as OTTO reads the raw page source. 💬 Need More Help? 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.

🛠️ View and Edit Deployed OTTO Page Titles and Meta Descriptions

🔍 Overview After OTTO SEO deploys optimisations to your site, you may need to review what was published or make changes to live page titles and meta descriptions. This article explains how to find your deployed metadata and edit it directly within Search Atlas. ⚙️ Before You Start Make sure the following conditions are met before attempting to view or edit deployed metadata: - OTTO is connected to your site and has successfully deployed at least one optimisation. - Your crawler settings are saved — if you recently updated crawler settings, wait for the next crawl cycle to complete before reviewing new data. - You have the Editor or Admin role on your Search Atlas workspace. 🚀 How to View Deployed Page Titles and Meta Descriptions 1. In the left sidebar, click OTTO SEO, then open All Sites (SEO Automation). 2. Select the site you want to review from the site selector at the top of the page. 3. Navigate to the Deployments section or the relevant task category (for example, Title Tags or Meta Descriptions). 4. Click on any task row to expand it. You will see two values side by side: - Original — the metadata that existed on the page before OTTO made changes. - Deployed — the metadata currently live on your page as deployed by OTTO. 5. Use the Status column to confirm that the task shows Deployed. Tasks showing Pending or Approved have not yet been pushed to your site. ✏️ How to Edit a Live Deployed Title or Meta Description If you need to change a page title or meta description that OTTO has already deployed, follow these steps: 1. In the left sidebar, click OTTO SEO, then open All Sites (SEO Automation). 2. Select your site from the site selector. 3. Locate the deployed task you want to update. You can use the search bar or filter by Task Type to find title tag or meta description tasks quickly. 4. Click the three-dot menu (⋮) next to the deployed task, then select Edit. 5. Update the title or meta description text in the edit field. Keep titles under 60 characters and meta descriptions under 160 characters for best results in search results pages. 6. Click Save to confirm your changes. 7. Click Deploy (or approve the updated task through your site's approval workflow) to push the new value live to your site. Note: Editing a deployed task creates a new version. The previous deployed value is preserved in the task history so you can always reference what was live before your update. 🔄 What Happens After Changing Crawler Settings If you recently updated your crawler settings (such as changing which pages are crawled or updating crawl frequency), keep the following in mind: - OTTO will re-crawl your site on the next scheduled cycle. New recommendations will appear after the crawl completes. - Previously deployed metadata remains live on your site until you explicitly edit and redeploy it — crawler setting changes do not automatically roll back or overwrite existing deployments. - Once the new crawl finishes, review the updated task list to see whether any pages now have fresh title or meta description suggestions based on your new settings. - If a page you expected to see is missing from the task list, confirm that the URL is included in your crawler scope and that the page returns a 200 HTTP status. 💡 Tips for Managing Metadata at Scale - Use the Bulk Select checkbox to approve or deploy multiple updated tasks at once, saving time across large sites. - Filter tasks by Page Type (posts, pages, products) to manage metadata for specific sections of your site. - After deploying edits, allow 24–48 hours for search engines to re-crawl and reflect the updated metadata in search results. - Cross-reference your titles and meta descriptions in the Content → On-Page Audit section (left sidebar → Content → On-Page Audit) for additional optimisation insights on individual URLs. 🆘 Need More Help? 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.

🔍 Why OTTO Suggests Short Open Graph Descriptions

🤔 What Is Happening? OTTO has two separate checks running when it reviews your Open Graph (OG) description: a compliance check and an optimization suggestion. These are independent processes, and understanding the difference explains why you may see a suggestion that appears to contradict your existing, compliant description. - Compliance check: Validates whether your current OG description falls within the recommended 120-160 character range. - Optimization suggestion: Generates a new draft description based on your page content, meta signals, and target keywords — independent of your current description's length. If OTTO's generated suggestion happens to be 59 characters, it does not mean your 139-character description is wrong. It means OTTO drafted an alternative that is shorter than ideal. Your original description is compliant and does not need to be replaced. ✅ How to Confirm Your Description Is Already Compliant 1. Go to OTTO SEO in the left sidebar, then open SEO Automation (URL: /seo-automation-v3). 2. Locate the page in your task list and open the Open Graph section. 3. Check the character counter displayed next to your current OG description. A count between 120 and 160 characters confirms your description is within the recommended range. 4. If the status indicator shows Compliant or No action needed, you can safely disregard the generated suggestion. 🛠️ How to Improve OTTO's Suggestion Using the Refine Prompt If you want OTTO to generate a better alternative — one that is closer to the optimal 120-160 character length — use the Refine Prompt feature to give OTTO specific instructions before it regenerates the suggestion. 1. In the Open Graph section, find the suggestion OTTO generated. 2. Click the Refine Prompt option (pencil or edit icon next to the suggestion). 3. Add a clear instruction in the prompt field. Examples: - "Write an OG description between 130 and 150 characters." - "Keep the description close to 140 characters and include the primary keyword." 4. Click Regenerate (or Apply) to produce a new suggestion based on your instruction. 5. Review the updated suggestion and apply it if it meets your requirements, or refine again until satisfied. You can run the refine-and-regenerate cycle as many times as needed. Each iteration gives OTTO tighter guidance, resulting in more accurate and on-target suggestions. ⚡ When Should You Accept or Ignore a Suggestion? - Accept the suggestion if your current description is missing, too short (under 120 characters), or too long (over 160 characters), and OTTO's suggestion is an improvement. - Ignore or refine the suggestion if your current description is already within the 120-160 character range and serves your SEO and brand goals. A compliant description does not need to be replaced simply because OTTO generated an alternative. - Use refine prompt any time OTTO's draft does not match the length, tone, or keyword requirements you need. 📋 Quick Reference: OG Description Length Guidelines - Under 120 characters: Too short — may not display fully or convey enough context in social previews. - 120-160 characters: Optimal range — recommended for social sharing and search engine display. - Over 160 characters: Too long — content may be truncated in social and search previews. 💡 Key Takeaway OTTO's optimization suggestion and your description's compliance status are separate outputs. A short or suboptimal suggestion from OTTO does not invalidate a description that already falls within the 120-160 character range. Always check the compliance indicator first, then use the Refine Prompt feature if you want a better AI-generated alternative. 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.

🔍 Verify OTTO Installation and Deployment Status

🧭 Overview OTTO is Search Atlas's AI-powered SEO automation tool. For it to work properly, it must be installed on your website and actively deployed to your pages. If you see a message saying OTTO is not installed properly — or you're unsure whether it's running — this article will walk you through how to verify and resolve the issue. ⚙️ Step 1: Open the OTTO Dashboard 1. Log in to your Search Atlas account. 2. In the left sidebar, click OTTO SEO, then open SEO Automation inside it. This will take you to the OTTO dashboard at /seo-automation-v3. 3. Select the website project you want to check from the project list. 🔎 Step 2: Check the Installation Status Once you're inside your project, OTTO will display an installation status indicator near the top of the dashboard. Look for one of the following statuses: - Installed & Active — OTTO is correctly connected to your site and is running. - Not Installed — OTTO has not been connected to your site yet. - Installation Error — OTTO was set up but something went wrong with the connection. If your status shows Not Installed or Installation Error, continue to Step 3. 🛠️ Step 3: Install or Reinstall OTTO OTTO connects to your website using either a JavaScript snippet or a WordPress plugin. Follow the method that applies to your site: Option A — JavaScript Snippet 1. In the OTTO dashboard, click Get Installation Code. 2. Copy the JavaScript snippet provided. 3. Paste the snippet into the section of every page on your website, or add it through your tag manager (such as Google Tag Manager). 4. Save and publish the changes on your site. 5. Return to the OTTO dashboard and click Verify Installation. Option B — WordPress Plugin 1. In your WordPress admin panel, go to Plugins → Add New. 2. Search for the Search Atlas plugin and install it. 3. Activate the plugin, then open its settings. 4. Enter your Search Atlas API key, which you can find in your account settings. 5. Save the settings, then return to the OTTO dashboard and click Verify Installation. 📊 Step 4: Check Deployment Status Across Pages Being installed is only the first step. OTTO also needs to be deployed to specific pages to apply SEO optimisations. To review which pages OTTO is active on: 1. From the left sidebar, navigate to OTTO SEO → All Sites (SEO Automation). 2. Review the list of URLs. Each page will show one of these statuses: - Deployed — OTTO's recommendations are live on this page. - Pending — Changes have been queued but not yet applied. - Not Deployed — OTTO has not applied any changes to this page. If important pages show Not Deployed, select them and click Deploy to push OTTO's optimisations live. ✅ Step 5: Confirm OTTO Is Running on Your Live Site You can do a quick manual check to confirm OTTO is active on a specific page: 1. Open the page in a web browser. 2. Right-click anywhere on the page and select View Page Source (or press Ctrl+U on Windows / Cmd+U on Mac). 3. Press Ctrl+F (or Cmd+F) to search within the source code. 4. Type searchatlas or otto in the search box. 5. If the script appears in the results, OTTO is successfully installed on that page. 💡 Common Reasons for Installation Issues - The snippet was placed in the instead of the section. - A caching plugin is serving an old version of the page — clear your site cache after installation. - The snippet was only added to the homepage and not to other pages or templates. - The WordPress plugin API key was entered incorrectly — double-check for spaces or typos. - A Content Security Policy (CSP) on your server is blocking the OTTO script — ask your developer to whitelist the Search Atlas domain. 💬 Still Need Help? If you have followed all the steps above and OTTO still shows as not installed, or if deployment is not working as expected, we are here to help. 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.

🔁 OTTO Pixel IDs Across Multiple PRO Versions

🔍 Overview Each OTTO pixel ID is unique and permanently tied to the PRO workspace where it was first generated. If you install a website in one PRO version and then try to add the same website to a different PRO version, you cannot reuse or overwrite the existing pixel ID. A brand-new pixel ID will be generated for that second workspace instead. Understanding this behavior will help you plan your workspace setup and avoid confusion when managing multiple PRO accounts or client projects. 🧩 How OTTO Pixel IDs Work When you connect a website to OTTO for the first time, Search Atlas generates a unique pixel ID specifically for that website within your current PRO workspace. This pixel ID is the identifier that links your site's data to your workspace. - One pixel ID per workspace per website: Each PRO workspace issues its own pixel ID for a given domain. - Pixel IDs are not transferable: A pixel ID created in Workspace A cannot be moved to, reused in, or overwritten by Workspace B. - Workspace isolation: Data collected under one pixel ID stays within that workspace. It will not carry over if you generate a new pixel ID for the same domain in another workspace. ⚠️ What Happens When You Add the Same Website to Another PRO Version If you attempt to install a website that already has an OTTO pixel in one PRO workspace into a second PRO workspace, the following will occur: 1. Search Atlas detects the domain as new within the second workspace. 2. A fresh, unique pixel ID is generated for that workspace. 3. You will need to replace the pixel code on your website with the new pixel ID if you want the second workspace to collect data. 4. Any historical data tied to the original pixel ID remains in the first workspace and is not accessible from the second. In short, you cannot overwrite an existing OTTO pixel ID from another workspace. The two pixel IDs will exist independently, and only the one currently installed on your website will collect data. 🛠️ Recommended Workaround If you need to manage a website under a different PRO version, follow these steps: 1. Go to the left sidebar and select OTTO SEO, then open SEO Automation (URL: /seo-automation-v3) inside the PRO workspace where you want to add the site. 2. Create a new project for the domain in that workspace. 3. Copy the new OTTO pixel ID that is generated for this workspace. 4. Update the pixel code on your website by replacing the old pixel ID with the new one. 5. Verify that the new pixel is firing correctly before removing or archiving the project in the original workspace. Important: Once you switch the pixel on your website to the new ID, the original workspace will stop receiving data for that domain. Make sure you export or note any reports you need from the first workspace before making the switch. 📋 Key Rules to Remember - OTTO pixel IDs are workspace-specific and cannot be shared or transferred between PRO versions. - Adding the same domain to multiple workspaces simultaneously is technically possible, but only the pixel ID installed on your website will actively collect data. - Historical data does not migrate between workspaces when you switch pixel IDs. - Always update the pixel code on your website after switching workspaces to ensure accurate data collection. 💬 Need More Help? 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.

🔄 Re-Add Your Site to OTTO SEO Correctly

🧭 Overview If OTTO SEO is not detecting your head tag after you have added it to your website, the most effective fix is to remove your site from OTTO and re-add it. This forces OTTO to perform a fresh verification check and pick up the tag correctly. Follow the steps below carefully to complete this process without losing your progress. ⚠️ Before You Begin - Confirm that your OTTO head tag is already placed in the <head> section of your website before re-adding your site. - Make sure the tag is present on every page of your site — ideally added at the theme or template level, not page by page. - If you are unsure whether the tag is live, open your site in a browser, right-click the page, select View Page Source, and search for your OTTO tag in the <head> block. 🗑️ Step 1: Remove Your Site from OTTO SEO 1. In the left sidebar, click OTTO SEO and then open SEO Automation to access the OTTO SEO dashboard. 2. Locate the site you need to fix in your list of connected properties. 3. Open the site options (usually a three-dot menu or settings icon next to the site name). 4. Select Remove Site or Disconnect Site and confirm the action when prompted. Your site will be removed from OTTO. No SEO recommendations or historical data in other areas of Search Atlas will be affected by this action. ➕ Step 2: Re-Add Your Site to OTTO SEO 1. From the same SEO Automation page, click the Create button (or the equivalent prompt displayed on screen). 2. Enter your website URL exactly as it appears — include https:// and match the www or non-www version your site uses. 3. Follow the on-screen prompts to proceed to the head tag step. 4. OTTO will display your unique head tag. Because you already placed this tag on your site, you do not need to add it again — simply proceed to the verification step. 5. Click Verify or Confirm Tag. OTTO will crawl your site and confirm the tag is detected. If verification succeeds, your site will be reconnected and OTTO will begin analysing your pages. 🔍 Troubleshooting: Verification Still Failing If OTTO still cannot detect your head tag after re-adding the site, check the following: - Caching: Your website or hosting provider may be serving a cached version of the page without the tag. Clear your site cache and try verifying again. - Tag placement: The tag must be inside the <head> element, not inside <body>. Some page builders place scripts in the wrong location. - Plugin or theme conflicts: On WordPress, a caching or security plugin may be stripping custom head code. Temporarily disable these plugins and re-test. - Partial deployment: If your site uses a staging environment, confirm the tag has been pushed to the live site, not just staging. 💡 Tips to Avoid This Issue in the Future - Use a tag manager (such as Google Tag Manager) or your theme's global header settings to ensure the OTTO tag loads site-wide from a single location. - After any theme update or migration, re-check that the head tag is still present in the page source. - Verify your site in OTTO immediately after placing the tag, before launching any caching or minification tools. 🙋 Need More Help? 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.

⏳ OTTO Pixel Verification After Site Audit

🔍 What Is Happening? If you have installed the OTTO pixel through Google Tag Manager (GTM) and confirmed it fires correctly in GTM preview mode, but Search Atlas still shows the pixel as not installed, this is expected behaviour. OTTO pixel verification is tied directly to your site audit. Search Atlas can only confirm the pixel is present after the audit crawl has finished scanning your website. ⚙️ Why Verification Depends on the Site Audit OTTO verifies pixel installation by detecting the tracking script during a crawl of your site's pages. Until that crawl completes, the platform has no data to confirm whether the pixel exists in your page source. This means: - A pending or in-progress site audit will leave the pixel status showing as unverified, even if the pixel is correctly installed. - GTM preview mode confirms the tag fires in your browser session, but it does not update Search Atlas verification — these are two separate systems. - Once the site audit finishes, Search Atlas re-evaluates the crawled page data and updates the pixel status automatically. 🚀 How to Check Your Site Audit Status 1. In the left sidebar, click OTTO SEO, then open All Sites (SEO Automation) (URL: /seo-automation-v3). 2. Locate your OTTO project and look for the site audit progress indicator on the project card. 3. If the audit is still running, wait for it to complete — crawl time varies depending on site size. 4. Once the audit status shows complete, return to the OTTO pixel section and refresh the page to see the updated verification status. ✅ Confirming Your Pixel Is Installed Correctly While waiting for the site audit to finish, you can double-check your GTM setup to make sure the pixel will be detected correctly during the crawl: - Confirm the OTTO pixel tag is set to fire on All Pages (or at minimum your homepage), not just specific triggers. - In GTM preview mode, load your homepage and verify the OTTO tag appears under Tags Fired. - Publish your GTM container if you have made any recent changes — unpublished changes are not visible to the Search Atlas crawler. - Ensure no consent management or cookie banner is blocking the tag from firing for non-consented visitors, as this can prevent crawl-time detection. ⏱️ How Long Does the Site Audit Take? Audit duration depends on the number of pages on your website. Small sites (under 500 pages) typically complete within a few minutes. Larger sites can take significantly longer. You do not need to keep the platform open — Search Atlas runs the audit in the background and updates your project automatically when it finishes. 🛠️ What to Do If Verification Still Fails After the Audit If your site audit has completed and the pixel is still showing as unverified, work through the following checks: - Confirm your GTM container is published, not just saved in draft. - Check that the OTTO pixel snippet is the correct one for your project — copying the snippet from another OTTO project will not verify correctly. - Temporarily disable any script-blocking plugins or performance optimisations (such as script delay or lazy loading) that may prevent the tag from appearing in the page source at crawl time. - Trigger a new site audit from your OTTO project to force a fresh crawl with your latest GTM configuration. 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. Additional Notes Manual recrawl: If you trigger a manual recrawl after installing the pixel, allow up to 24 hours for the crawl to finish and for the pixel status to refresh. Scheduled crawl: verification will update automatically once that scheduled crawl completes. The unverified status is a display limitation tied to crawl availability, not a signal that the pixel has stopped working.

🛠️ Install OTTO Tracking Pixel on Any Website

🔍 Overview If your website is self-hosted — for example, on a provider like home.pl, a custom VPS, or any shared hosting environment — you can still connect it to OTTO SEO in Search Atlas. Instead of relying on Cloudflare, a WordPress plugin, or other third-party integrations, you simply add the OTTO tracking pixel directly to your HTML. This method works on any website where you can edit the source code. ⚙️ Before You Begin Make sure you have the following ready before starting: - Access to your website's HTML files (via FTP, SFTP, your hosting control panel's file manager, or a code editor) - The ability to edit your site's main template file or every page's section - Your OTTO project already created inside Search Atlas (see the OTTO SEO section) 🚀 Step 1 — Find Your OTTO Pixel Code 1. Log in to Search Atlas and navigate to OTTO SEO using the left sidebar. 2. Open your OTTO project or create a new one for your website. 3. Within your OTTO project, find the pixel code snippet provided for your project. 4. Copy the pixel code snippet. 📄 Step 2 — Add the Pixel to Your HTML The pixel must be placed inside the section of every page you want OTTO to monitor. The most reliable way to do this on a self-hosted site is to edit your global template or layout file — the single file that wraps all pages on your site. 1. Connect to your hosting via FTP/SFTP or open the File Manager in your hosting control panel (e.g., cPanel, DirectAdmin, or your provider's custom panel). 2. Locate your main template file. This is commonly the file that contains the shared section rendered on every page of your site. 3. Open the file in a text editor. 4. Paste the OTTO pixel code snippet immediately before the closing tag. 5. Save the file and upload it back to your server if you edited it locally. ✅ Step 3 — Verify the Connection 1. Return to Search Atlas and go to OTTO SEO in the left sidebar. 2. Open your OTTO project and follow the on-screen instructions to confirm the pixel has been detected on your site. 3. If the connection is confirmed, your website is now connected and OTTO will begin crawl monitoring. If the connection is not confirmed immediately, wait 1–2 minutes and try again. Browser caches or server propagation delays can sometimes cause a brief lag. 💡 Tips for Common Issues - If your site uses a PHP-based custom build, add the pixel snippet to the PHP file that outputs the shared section. - Make sure the pixel code is pasted in the section and not in the section, as placement in the body may prevent proper detection. - If you manage multiple pages without a shared template, you will need to add the pixel code to each page's section individually. 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.

🔍 Rescan Your Site and Run SEO Diagnostics

🤖 What Is the OTTO Pixel? The OTTO Pixel is a lightweight tracking script you install on your website. It allows Search Atlas to continuously monitor your site's SEO health, detect technical issues, and verify that fixes have been applied correctly. Without the OTTO Pixel, rescanning and diagnostics are limited to surface-level checks. With it installed, OTTO can perform deep, real-time analysis directly tied to your live site. 🧭 Where to Find the Scan and Run Diagnostics Feature The diagnostics and rescan tools are located inside the OTTO SEO section of Search Atlas. Follow these steps to get there: 1. Open Search Atlas and look at the left sidebar. 2. Click OTTO SEO, then All Sites (SEO Automation). This takes you to the SEO automation dashboard (/seo-automation-v3). 3. Locate your website in the list of active sites. You will see options such as Active and Deep Frozen alongside your connected domains. 4. Click on your site to open its OTTO dashboard. 5. Inside the site dashboard, find the Scan or Run Diagnostics button. Click it to trigger a fresh crawl and diagnostic check of your site. Once the scan is complete, OTTO will update your issue list and mark any previously flagged items as resolved if the fixes have been detected. 📦 How to Install the OTTO Pixel on Your Site If you have not yet installed the OTTO Pixel, follow these steps before running a diagnostic scan: 1. From the OTTO SEO dashboard, select the site you want to connect. 2. Look for the OTTO Pixel setup prompt or the pixel installation option within the site settings. 3. Copy the provided pixel snippet. 4. Paste the snippet into the <head> section of every page on your website. If you use a CMS such as WordPress, you can add it via your theme's header file or a header injection plugin. 5. Return to the OTTO SEO dashboard and click Verify Installation to confirm the pixel is live and communicating with Search Atlas. Tip: The pixel only needs to be installed once. After verification, OTTO will begin collecting data automatically. 🔄 How to Rescan Your Site to Verify SEO Fixes After making changes to your site — such as adding meta tags, fixing broken links, or resolving crawl errors — you should run a rescan to confirm those changes are registered by Search Atlas. 1. Go to OTTO SEO → All Sites (SEO Automation) in the left sidebar. 2. Click on the site you have made changes to. 3. Click the Scan or Run Diagnostics button inside the site dashboard. 4. Wait for the scan to finish. Depending on your site size, this may take a few minutes. 5. Review the updated diagnostics report. Fixed issues will be marked as resolved, and any remaining or new issues will be clearly listed. Note: If a fix is not being detected, double-check that the change is live on your published site and not only saved in a draft or staging environment. 📊 Using Site Metrics Alongside Diagnostics For a broader view of your site's performance after a rescan, you can also review data inside Site Metrics: - Go to Site Metrics in the left sidebar (/site-explorer/list). - Use the Overview sub-page to check platform connections and AI settings. - Visit Pages to review individual page-level performance following your fixes. - Use Keywords to monitor ranking changes tied to the SEO improvements you have made. Together, OTTO SEO diagnostics and Site Metrics give you a complete picture of your site's health before and after making SEO changes. 💬 Need More Help? 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.

🔍 OTTO Pixel Shows Not Installed After Crawl

🤔 Why These Two Statuses Are Independent When you check your dashboard and see that your site crawl has not run in several days and OTTO shows as not installed, it is easy to assume these are the same problem. They are not. The site crawl and the OTTO pixel installation are two completely separate systems with different triggers, verification methods, and root causes when something goes wrong. - Site crawl — Search Atlas crawls your website to collect technical SEO data such as broken links, missing meta tags, and page speed signals. Crawl status is managed inside OTTO SEO → Site Audit (Crawl Monitoring) and runs on a scheduled or manually triggered basis. - OTTO pixel — OTTO is the OTTO SEO automation layer. For OTTO to apply and monitor SEO changes on your site, a lightweight pixel (code snippet) must be installed on your website. OTTO checks independently whether that pixel is present and firing correctly. A completed crawl does not confirm that the OTTO pixel is installed. Likewise, a missing or delayed crawl does not mean OTTO is broken. You need to troubleshoot each issue separately. 📋 Step 1 — Check Your Site Crawl Status If your site has not been crawled in four or more days, follow these steps to investigate. 1. Open Search Atlas and navigate to your project's crawl or site audit area. 2. Look for the last crawl date displayed on the project overview. If the crawl is overdue, use the option available on screen to trigger a fresh crawl manually. 3. Crawls on large sites can take anywhere from a few minutes to several hours depending on the number of pages. Wait for the crawl to reach 100% before reviewing results. 4. If the crawl fails to start or gets stuck, check that your website is publicly accessible and that no firewall or bot-protection rule is blocking the Search Atlas crawler. Common reasons a crawl may be delayed or missing include a temporarily inaccessible site, a paused project, or a recently changed domain or subdomain setting inside the project configuration. ⚙️ Step 2 — Verify OTTO Pixel Installation Independently Even if your crawl completes successfully, OTTO will still show as Not Installed if the pixel has not been placed on your site or is not firing correctly. Follow these steps to verify the pixel separately. 1. Open your project inside Search Atlas and locate the OTTO setup or installation area. 2. Find and copy the OTTO pixel code snippet displayed for your project. 3. Paste the snippet into the <head> section of every page on your website. You can do this through your CMS theme files, a tag manager such as Google Tag Manager, or by asking your developer to add it directly to your site template. 4. Once the snippet is in place, return to Search Atlas and use the pix 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.

🔌 Extract and Use OTTO Pixel Code on Any Website

🧩 What Is the OTTO Custom Integration Pixel? OTTO's custom integration pixel is a small JavaScript snippet that lets you connect OTTO to any website — even platforms that don't support WordPress plugins or direct integrations. Once the code is placed on your site, OTTO can deliver its on-page SEO recommendations automatically. This method works on platforms such as Squarespace, Wix, Webflow, Shopify, custom-built HTML sites, and any other CMS that allows you to inject code into the site's or footer section. 🗺️ Where to Find Your OTTO Pixel Code 1. Log in to your Search Atlas account. 2. In the left sidebar, click OTTO SEO → All Sites (SEO Automation) (URL: /seo-automation-v3). 3. Locate the website project you want to connect and open it. 4. Within the project, look for the section related to website connection or integration options. The exact label may vary — if you are unsure which option to select, contact the support team for guidance on your specific account view. 5. Once you locate the pixel code for your project, copy the full JavaScript snippet to your clipboard. Note: Each website project has its own unique pixel code. Do not share or reuse a pixel between different website projects — doing so will cause tracking and automation errors. 📋 How to Add the Pixel to Your Website Once you have copied your pixel code, you need to paste it into your website. The exact steps depend on your platform, but the goal is always the same: place the script inside the section of every page on your site. General steps (apply to most platforms): 1. Open your website platform's admin panel or settings area. 2. Navigate to the section that allows you to add custom code, scripts, or header injections. This is often labelled Custom Code, Header Code, Inject Scripts, or Advanced Settings. 3. Paste the copied OTTO pixel code into the head code field. 4. Save or publish your changes. 5. Return to Search Atlas and check whether your website project now shows as connected. If connection is not confirmed, ensure the script was pasted into the head section and that your changes were published. 🛠️ Platform-Specific Quick Reference - Squarespace: Settings → Advanced → Code Injection → paste into the Header field. - Wix: Settings → Custom Code → Add Custom Code → select "Head" and "All Pages". - Webflow: Project Settings → Custom Code → Head Code section → paste and publish. - Shopify: Online Store → Themes → Edit Code → open theme.liquid → paste before the closing tag. - Custom HTML site: Open each page's HTML file and paste the pixel code inside the tags, then re-upload or redeploy the files. 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.

🔄 OTTO Pixel Installation After Whitelabel Domain Updates

🧭 Overview When you update your whitelabel domain in Search Atlas, any previously installed OTTO pixels tied to your old domain may stop reporting as active. The pixel code is domain-specific, so a domain change typically requires obtaining a fresh pixel code and reinstalling it. If you are working inside HighLevel (GoHighLevel), this article explains what to do and what information to have ready. ⚠️ Why Your OTTO Pixel Shows as Not Installed After a whitelabel domain update, the pixel code previously installed on your site may no longer be recognized as valid because it was associated with your previous domain. Any site still carrying the old pixel code may show a not installed status because: - The old pixel references your previous domain and may no longer be valid. - Search Atlas may not be able to verify ownership or activity through a domain it no longer recognizes as yours. - HighLevel sites can cache scripts, which may cause the status to appear stuck even after an update. Obtaining your updated pixel code and reinstalling it is typically required after a domain change — this is expected behavior, not a bug. 🛠️ How to Reinstall the OTTO Pixel After a Whitelabel Domain Change Because the exact steps for retrieving an updated pixel code may vary depending on your account setup, we recommend the following approach: 1. Log in to Search Atlas and navigate to the OTTO SEO or OTTO section of your dashboard. 2. Open the OTTO workspace for the relevant client or project. 3. Locate the OTTO Pixel area within your workspace settings and retrieve the current pixel code associated with your updated whitelabel domain. 4. Copy the full pixel script that appears. 5. In HighLevel, open the site or funnel where the pixel needs to be installed and paste the new pixel code into the appropriate tracking code field at the site or funnel level. 6. Save your changes and allow time for the status to update in Search Atlas. If you are unsure where to find the pixel code in your dashboard or how to add it in HighLevel, please reach out to our support team with your project name, your old and new whitelabel domain names, and a description of where the pixel is currently showing as not installed. This will allow us to confirm the correct steps for your specific 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.

🔍 View and Edit Deployed Titles and Meta Descriptions in OTTO

🗺️ Overview When OTTO deploys optimizations to your site, it keeps a record of every page title and meta description it has pushed live. If you change your crawler settings or want to review what is currently deployed, this article explains how to locate that historical data and how to properly rescan your pages so OTTO reflects the latest state of your site. 📋 Where to Find Previously Deployed Titles and Meta Descriptions OTTO stores a log of every optimization it has deployed. To view previously deployed page titles and meta descriptions: 1. Go to OTTO SEO → All Sites (SEO Automation) in the left sidebar. 2. Select the site you are working on to open its OTTO dashboard. 3. Navigate to the section within OTTO that lists your deployed optimizations. Here you can review the page titles and meta descriptions that OTTO has pushed live, including the URLs they were applied to. 4. Locate the specific page whose deployed title or meta description you want to review. If you are unable to find the deployed values for a specific page or the data does not appear as expected, please escalate to the support team with the following information ready: your project/site name, the URL(s) you are checking, and a description of what you expected to see versus what is shown. ✏️ How to Edit Live Titles and Meta Descriptions You can update a deployed title or meta description inside OTTO. Navigate to your deployed optimizations within the OTTO dashboard, locate the page you want to update, and use the available editing option for that page's title or meta description. Once you save your changes, OTTO will push the updated value to your live page. Important: If your site uses a plugin or theme that also controls meta fields, changes made through OTTO may be overridden on the next plugin save if OTTO does not have write priority over those fields. 🔄 Rescanning Pages After Changing Crawler Settings When you update your crawler settings — for example, changing which URL patterns OTTO should include or exclude — the existing optimization data may no longer reflect the current state of your pages. A rescan tells OTTO to re-crawl the affected URLs and refresh its recommendations. 1. Go to OTTO SEO → All Sites (SEO Automation) in the left sidebar and open the relevant site's OTTO dashboard. 2. Locate the crawler settings area and confirm your updated settings are saved. 3. Trigger a rescan for the affected pages so OTTO re-crawls those URLs and updates its data accordingly. If the rescan does not complete as expected or deployed values are still not reflecting your crawler changes, have the following ready when you contact support: your site/project name, the crawler settings you changed, the URLs affected, and any error messages or unexpected behavior you observed. 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.

📡 Find OTTO Pixel Data Options After Activation

🔍 Overview Once the OTTO code is active on your website, OTTO begins collecting pixel data to power its SEO automation. To access and manage your OTTO pixel data options, you need to navigate to the OTTO SEO section of Search Atlas. This article walks you through exactly where to find these settings and what to expect. 🧭 How to Access OTTO Pixel Data Options 1. Log in to your Search Atlas account. 2. In the left sidebar, click OTTO SEO. This takes you to the OTTO automation dashboard at /seo-automation-v3. 3. On the OTTO SEO page, locate the site for which the OTTO code is already active. Active sites will display a status indicator confirming the code is installed and firing correctly. 4. Click on the relevant site to open its OTTO settings panel. 5. Within the site panel, look for the Pixel Data section or tab. This is where all OTTO pixel data options are displayed, including tracking status, collected signals, and data configuration controls. ✅ What You Will See in the Pixel Data Section Once you open the Pixel Data section for your active site, you can expect to find the following options and information: - Pixel status — Confirms whether the OTTO pixel is actively firing on your website. - Data collection settings — Controls for what user interaction and on-page signals OTTO is collecting. - Signal history — A log of pixel events and data points captured over time. - Integration details — Information about how the pixel connects to OTTO's automation engine to drive SEO recommendations. ⚠️ Pixel Data Options Not Appearing? If you have navigated to OTTO SEO but the Pixel Data section is not visible, check the following: - Confirm the OTTO code is active. The pixel data options only appear after the OTTO code has been successfully installed and verified on your website. If the code was just added, allow a few minutes for the status to update. - Check the correct site is selected. Make sure you have selected the specific site where OTTO is installed. Pixel data is site-specific and will only show under the matching property. - Refresh the page. A hard refresh (Ctrl + Shift + R on Windows or Cmd + Shift + R on Mac) can resolve display delays after a recent code activation. - Verify your account permissions. Pixel data options are available to account owners and users with full access. If you are on a restricted role, contact your account administrator to confirm your permission level. 🔗 Related Sections in Search Atlas While working with OTTO pixel data, you may also find the following areas of Search Atlas useful for monitoring your site's overall performance: - Site Metrics — Accessible from the left sidebar, this section gives you a broad view of your site's SEO health, including keyword rankings and traffic insights. - Rank Tracker — Navigate via Left sidebar → Keywords → Rank Tracker to monitor how your target keywords are performing alongside OTTO's automation activity. - Keyword Gap — Navigate via Left sidebar → Keywords → Keyword Gap to identify opportunities that OTTO's pixel data can help you act on. 💬 Still Need Help? 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.

🔍 Otto Pixel: Understanding 'Not Installed' During Audit

🧩 Overview After installing the Otto pixel plugin on your WordPress site, you may notice that Otto still displays a "Pixel Not Installed" message. This is expected behavior and does not mean something went wrong. This article explains why this message appears and what happens next. ⚙️ Why Otto Shows 'Pixel Not Installed' When you first connect your site to Otto, the platform automatically checks whether the pixel is installed on a schedule based on the project's age: every 15 minutes for projects under 2 hours old, every hour from 2 to 24 hours old, every 6 hours from 1 to 7 days old, after which automatic checks stop. A correctly installed pixel on a new project is normally detected within about 15 minutes. Until the next scheduled check runs, Otto may still display "Pixel Not Installed" as a temporary placeholder status. This is a normal part of the setup workflow, not an error. ✅ What You Should Do Right Now 1. Confirm the plugin is installed and active. In your WordPress dashboard, go to Plugins → Installed Plugins and verify the Otto pixel plugin is listed and has the status Active. 2. Confirm the plugin is connected to the correct site. Make sure the API key or site URL inside the plugin settings matches the property you added in Search Atlas. 3. Do nothing further — wait for the next automatic check. On a new project this is typically within about 15 minutes. Otto will automatically update the pixel status. No manual refresh or reinstallation is needed. 🔎 How to Check Your Pixel Status 1. In the left sidebar, click OTTO SEO, then open SEO Automation to access the Otto dashboard. 2. Locate your connected site and review the pixel status indicator. 3. If the automatic check has run and the pixel was detected successfully, the status will update to Pixel Installed. 4. If the status still shows "Pixel Not Installed" well beyond the expected check interval, proceed to the troubleshooting steps below. 🛠️ Troubleshooting: Still Not Installed If the pixel has not been detected after the expected automatic check, check the following common causes: - Plugin deactivated or deleted: Return to Plugins → Installed Plugins in WordPress and confirm the Otto plugin is still active. - Caching plugin interference: A caching plugin may be serving old page versions that do not include the pixel code. Clear your site cache and any CDN cache, then allow a few hours for Otto to re-crawl. - Theme or page builder conflicts: Some themes or page builders prevent scripts from loading in the expected location. Try deactivating other plugins temporarily to identify a conflict. - Incorrect API key: Open the Otto plugin settings in WordPress and verify the API key matches the one shown in your Search Atlas account. - Site not publicly accessible: Otto's crawler cannot scan password-protected, maintenance-mode, or staging sites. Ensure your site is publicly reachable. 📋 Quick-Reference Summary - The "Pixel Not Installed" message right after setup is normal and temporary. - Automatic pixel checks run every 15 minutes for projects under 2 hours old, every hour from 2 to 24 hours, every 6 hours from 1 to 7 days, and stop after 7 days. - A correctly installed pixel on a new project is normally detected within about 15 minutes. - Use the troubleshooting checklist above if the status has not updated as expected. 💬 Need More Help? 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.

Why OTTO Schema Isn't Detected by Validators Despite Correct Deployment

Overview If your OTTO schema deployments show a Connected or Deployed status inside Search Atlas but the schema is not appearing in external tools like validator.schema.org, Google Rich Results Test, or Google Search Console — and your other OTTO-managed sites are working correctly — you may be experiencing a schema generation or validation issue that requires investigation by our support team. This article explains how to identify the issue on your site. Because the resolution may depend on factors specific to your account and deployment configuration, please contact our support team so we can investigate and apply the appropriate fix. Common Root Causes Several technical issues can cause valid-looking schema deployments to fail external validation. Understanding these will help you diagnose the situation quickly. - Schema validation blocking deployment: In some cases, internal validation may prevent schema from being fully pushed to the page even though the deployment status appears as connected in the UI. - Unrecognized or malformed fields: Certain fields in OTTO-generated schema output may not be structured in a way that external validators recognize, causing the schema to be present on the page but not parsed correctly. - Schema not yet propagated: There may be a delay between when OTTO marks a deployment as connected and when the schema is fully live and detectable by external tools. How to Identify the Issue on Your Site 1. Navigate to OTTO SEO → All Sites (SEO Automation) inside Search Atlas and select the affected site. 2. Review which schema types are deployed on the affected pages. 3. Copy the raw schema JSON from the deployed page by right-clicking the page in a browser, selecting View Page Source, and searching for application/ld+json. 4. Paste the raw JSON into validator.schema.org and review any errors or warnings returned. Pay close attention to field-level errors, as these often indicate the root cause. 5. Also test the live page URL directly in the Google Rich Results Test to see whether Google can detect and parse the schema. Next Steps If your schema is still not being detected after reviewing the steps above, please reach out to our support team with the following information so we can investigate further: - The affected site URL and the specific pages where schema is not being detected - A screenshot of the OTTO deployment status for the affected pages - Any errors or warnings returned by validator.schema.org or the Google Rich Results Test Our team will review your deployment configuration and work with you to resolve the issue. If you need assistance, please contact us via the chat widget in Search Atlas or reach out to our support team directly.

🔎 Where’s My OTTO SEO Pixel?

How to Locate Your OTTO Pixel UUID and Script in Search Atlas Before installing OTTO on your website, you need to retrieve your unique OTTO Pixel identifier. This Pixel connects your website to the OTTO engine so Search Atlas can begin scanning, validating, and optimizing your SEO automatically. 🛠️ Step-by-Step Instructions 1. 🔐 Log In to Search Atlas Go to searchatlas.com and sign in with your account credentials. ​ 2.🧭 Navigate to OTTO SEO Automation From the left-hand sidebar, click: OTTO SEO → All Sites (SEO Automation) This is where all your OTTO-connected projects live. 3.🏗️ First-Time Setup: How to Create Your OTTO Project and Retrieve Your Pixel 1. Click the blue**+ Create** button 2**. Enter** your full website URL (e.g., https://yourdomain.com) 3. Wait for the green verification checkmark 4. Click****Continue. 5. Setup Fields (Optional) Complete Business Info, GSC, GBP, or use Autofill with AI. This step is not necessary to access the Pixel Script. 6. Click****Continue. 🧬 Access Your Pixel Code In the Installation Guide: 1. Select your CMS from the CMS Grid 2. Select****Video Guide and find the Pixel Code located right under the Video Guide**.** 3. Copy the Pixel Code. 5. ✅ How to Locate Your OTTO Pixel (for Users With an Existing Site Added) Go to OTTO SEO → All Sites (SEO Automation) 1. From the left-hand navigation panel, click: OTTO SEO → All Sites (SEO Automation) This opens your full list of OTTO-connected projects. 2. Click on the Site You Already Added Find your domain in the list and click its name. 3. This takes you into the OTTO Overview for that specific site. 3. Open “OTTO Settings” At the top right of the site overview, locate the control section and click: OTTO Settings 4. Open the “Pixel & Integrations” Section Inside OTTO Settings, you’ll see several modules. Click: OTTO Installation This is where the Pixel lives. 5. Copy Your Pixel Script and UUID Scroll down, then you’ll see the Pixel Script: Inside the script, you can also find your UUID if you need it. It’s the value that appears after data-uuid="..." and before src=. ⚠️ Your Pixel is unique to your domain and must not be reused across different sites. ❌ Common mistakes to avoid - Installing multiple methods at once (Pixel + Plugin + Cloudflare) → This can cause duplicated scripts or tracking inconsistencies. - Placing the script outside of <head> when doing a manual install. - Using the wrong UUID when configuring WordPress. - Embedding the Pixel into template areas that get cached incorrectly (e.g., footer injection, outdated builders). - Not validating installation after adding the Pixel. Always run a Scan from the project’s main dashboard to confirm OTTO is detected and active. By installing the OTTO Pixel correctly and validating it across your platform, you’ve unlocked the foundation for AI-powered SEO with Search Atlas. Whether you're using WordPress, GTM, GHL, Shopify, or another CMS, you now have a diagnostic-ready site capable of real-time audits, technical fixes, and automated optimizations. Remember, precision in placement and avoiding duplicate methods is key. If you ever encounter problems, our troubleshooting guide is here to walk you through platform-specific solutions step by step. From this point forward, OTTO can begin learning from your site structure, enhancing your visibility, and automatically powering insights that drive search performance. 📚 Useful Official Resources How Do I Install the OTTO Pixel on My Website? (Search Atlas Help Center)

🔍 Inspect and Validate the Search Atlas OTTO Pixel Manually

Use this guide to manually inspect and validate your OTTO pixel on any platform — WordPress, Shopify, Wix, Webflow, GoHighLevel, Lovable, and custom-coded sites. A missing, duplicated, or UUID-mismatched pixel prevents OTTO from crawling, activating, and deploying on-page optimisations. 🛠️ Step 1: Run the Official Diagnostic Scan (Always Do This First) The Diagnostic Scan confirms: - Pixel presence - Correct UUID - Duplicate installs - Engagement status - Partial installs - Improper placement Navigate to the Diagnostic Scan OTTO SEO → All Sites → select your site → click Scan → click Run Diagnostics Scan You can scan: - The homepage - Any specific URL - Recently added pages - Subdomains Important: Diagnostics confirms whether the pixel is detected. It does not confirm whether the pixel fires — that requires manual browser inspection in Step 3. Known limitation (as of May 2026): OTTO may display as installed even when the project UUID does not match the UUID embedded on the site. If OTTO reports a wrong_uuid status or shows the feature as not connected, the live site likely contains a stale UUID from a previous project — even if you recently installed a new snippet. Proceed to Step 3 to verify the UUID in the script tag matches the UUID in your current OTTO project dashboard. If they differ, follow the fix in the UUID Mismatch section below. 🌐 Step 2: Open the Website in a Clean Environment To avoid login-based suppression or cached versions, access the site using: - Incognito / Private Mode - All browser extensions disabled - The exact domain variant configured in Search Atlas: https vs http, www vs non-www, correct subdomain, no staging URLs OTTO cannot detect a pixel installed on a different domain variant. You now have a clean session that reflects exactly what OTTO's crawler sees. 🔎 Step 3: Inspect the Pixel in DevTools (Manual Validation) Open DevTools Right-click anywhere on the page → Inspect → open the Elements panel. Search the Page for OTTO Code Press CTRL + F (Windows) or CMD + F (Mac), then search for: - sa-dynamic-optimization - searchatlas - data-uuid Expected Pixel Locations - Inside the <head> - Injected dynamically in the <body> on render Both locations are valid depending on your CMS. Note on rendering layers: Browser DevTools and Google's URL Inspection tool confirm JS-rendered output. Some OTTO edge-level changes (e.g., H1 deployments) may not appear in raw HTML fetched by AI crawlers or non-JS bots (ChatGPT, Perplexity, Claude). To verify raw HTML output, use curl or a server-side fetch tool and inspect the response body directly. If you find the script tag, the pixel is present in the rendered DOM. ✅ Step 4: Confirm the Pixel Structure The OTTO Pixel always includes two components. Verify both are present. A. The Loader Script <script src="https://cdn.searchatlas.com/otto/loader.min.js" data-noptimize></script> Verify all of the following are intact: - id="sa-dynamic-optimization-loader" present on the script tag - Correct UUID in the data-uuid attribute — must match the site's current project in Search Atlas - CDN path intact with no corruption from minifiers - Both attributes present: data-noptimize and data-cfasync="false" B. The Base64 Script Block (Core Logic) Search Atlas injects a Base64-encoded script block that initialises OTTO's core tracking and optimisation logic. Verify the block is present and not truncated — a partial or corrupted block prevents OTTO from activating even when the loader script is correctly placed. 🔑 Fix a UUID Mismatch on a Lovable-Hosted Site If OTTO reports a wrong_uuid status or shows the feature as not connected on a Lovable-hosted site, the most common cause is a stale script tag from a previous project still embedded in index.html. Follow these steps to replace it. 1. Open your project at lovable.dev and sign in. 2. Click Code editor in the left sidebar. 3. Navigate to the public/ folder and open index.html. 4. Search the file for the existing OTTO script tag — search for searchatlas or sa-dynamic-optimization. 5. Delete the old script tag entirely. 6. In Search Atlas, go to OTTO SEO → All Sites → select your site → OTTO Pixel and copy the current pixel snippet. 7. Paste the new snippet into index.html inside the <head> tag. 8. Save and commit — Lovable automatically redeploys on save. After the redeploy completes, return to Search Atlas and run the Diagnostic Scan again to confirm OTTO detects the correct UUID. Alternative: If you have a previously verified project that already has the correct UUID embedded on the live site, switch to that project in Search Atlas under OTTO SEO → All Sites instead of updating the pixel. ⚠️ Common UUID Mismatch Causes (All Platforms) If OTTO reports a UUID mismatch or wrong_uuid status on any platform, check these common causes: - A previous OTTO project's pixel snippet was never removed before installing a new one. - A page builder or caching plugin preserved the old script tag after you updated it. - The snippet was installed on a staging environment instead of the production domain. - The UUID in the pixel does not match the current project — compare the data-uuid value visible in DevTools against the UUID shown in your OTTO project dashboard in Search Atlas. The issue is resolved when the Diagnostic Scan shows the UUID matches and OTTO status changes to connected. 🎯 You now know how to inspect, validate, and fix your OTTO pixel on any platform, including Lovable-hosted sites. If OTTO still reports a UUID mismatch after following these steps, contact Search Atlas support with your project UUID and domain so the team can diagnose the issue directly.

Install OTTO AI Pixel on PrestaShop

What Is the OTTO AI Pixel? The OTTO AI Pixel is a small script that connects your PrestaShop website to Search Atlas. It allows OTTO to read your site's structure, gather SEO data, and automate on-page optimizations. The pixel must be present in the <head> section of every page on your site. Before You Begin - You have an active Search Atlas account with OTTO AI enabled. - You have administrator access to your PrestaShop back office. Step 1: Copy Your OTTO AI Pixel Script 1. Log in to Search Atlas and navigate to the OTTO AI section of your account. 2. Select the project that matches your PrestaShop website. 3. Locate your OTTO AI Pixel script within the project settings. 4. Copy the entire pixel script to your clipboard. Keep this tab open in case you need to copy it again. Step 2: Add the Pixel to Your PrestaShop Site You need to add the pixel script to the <head> section of your PrestaShop site. The exact method will depend on your PrestaShop version, theme, and available modules. Common approaches include using a module that supports injecting code into the <head> section, or editing your active theme's template files directly to paste the script before the closing </head> tag. If you are unsure which method is appropriate for your specific setup, please reach out to our support team for guidance tailored to your configuration. Step 3: Confirm the Pixel Is Working After adding the pixel script to your site, verify it is active by following these steps: 1. Return to your Search Atlas project and navigate to the OTTO AI section. 2. Check your project's pixel status within Search Atlas to confirm the script has been detected on your site. 3. To independently verify the pixel is present on your pages, open your PrestaShop homepage in a browser, right-click, and select View Page Source. Search the source code for your pixel script to confirm it appears inside the <head> section. If you need help installing the OTTO AI Pixel on your PrestaShop site or confirming it is working correctly, please contact our support team through the chat icon in your Search Atlas dashboard. We are happy to help.