Home 🤖 OTTO SEO

🤖 OTTO SEO

Camilo Aponte
By Camilo Aponte
• 71 articles

💡 Why AI Agent Credits Run Out Quickly

📌 Overview Some customers see their AI agent credits fall much faster than expected, sometimes within a single day. This article explains the most common causes, how to check where your credits went, how to avoid duplicate usage, and what to do if you believe credits were used in error. 🔍 Common Reasons Credits Drop Quickly AI agent credits are used each time an agent runs a task. Usage can add up quickly in these situations: - Repeated runs: Starting the same task more than once, for example because it looked stuck, can use credits each time. - Large tasks: Tasks that cover many pages, keywords, or a whole site generally use more credits than small, focused ones. - Several tabs or sessions: If the platform is open in more than one tab or browser, the same task may be started or retried from each one. - Browser or connection problems: A tab crash, a refresh, or a dropped session does not stop a task that is already running. The agent keeps working on the server, and when you reopen the platform the conversation usually shows the finished result rather than an unfinished task. - Several team members on one account: Others working on the same project can use credits without you seeing it. 🌐 Tab Crashes and Session Disconnects If your browser tab crashes or your session disconnects while an AI agent is working, the task keeps running in the background and its result is saved to the conversation, even if that tab never showed it. If you start the task again anyway, that second run uses credits a second time. If you notice this, wait a few minutes before restarting a task. Then check whether the earlier result has appeared in your project. 📊 How to Check Where Your Credits Went 1. Log in to the platform and open the AI Agent. On the home screen, open the Activity tab. You can filter it by project or domain, but credits are shared across the whole account, not tracked per project. 2. Review your recent AI agent activity. Each entry is a deliverable or report from one of your own conversations, with its title, project, and how long ago it was created. It is not a list of credit charges, and it does not show work done by other people on the account. 3. Look for the same task listed several times in a short period. 4. Note the dates, times, and task names. You will need them if you contact support. 5. If you work with a team, ask them whether they ran any tasks during the same period. 🛡️ How to Prevent Duplicate Credit Usage - Keep the platform open in one tab while an AI agent is running. - Do not refresh the page or close the tab until the task finishes. - Before re-running a task, wait a few minutes and check whether the result is already in your project. - Use a stable internet connection for longer tasks. - Update your browser and disable extensions that may interfere with the platform. - Start with smaller tasks, such as a single page or a short list, before running larger ones. - Agree with your team on who runs which tasks so work is not repeated. 🔄 Requesting a Credit Review If you think credits were used twice because of a crash, a disconnect, or an error, you can ask our team to review your usage. Credit adjustments are reviewed case by case, and a request is not guaranteed to be approved. A review may not result in reimbursement if the tasks ran successfully or the usage matches the actions taken on your account. To help us review your request quickly, include the following: - The domain or project name - The dates and approximate times when the problem happened - The names of the tasks or agents involved - What you saw, such as a crash, a disconnect, or an error message - Screenshots of the activity or usage, if available - The number of credits you expected to use and the number actually used ✅ What to Expect After You Ask - Our team reviews the activity on your account against the details you provide. - If a duplicate or failed run is confirmed, we will tell you what options are available. - If the usage is confirmed as valid, we will explain how the credits were used so you can plan future tasks. 💬 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 instantly connected with a member of our team.

Last updated on Oct 29, 2026

🤖 AI Agent Quota Across Multiple Client Accounts

📌 Overview If you manage SEO for several clients, you may wonder whether each one needs its own AI Agent quota or whether your usage is shared. This article explains how to think about AI Agent usage across multiple client accounts, how to monitor it, and what to confirm with our team before you scale up. Note: How quota is allocated depends on your plan and how your projects are set up. Check your own account for the exact numbers that apply to you. ❓ Do I Need to Buy Extra Quota for Each Client? Not automatically. Adding a client or project does not by itself mean you must purchase separate quota for it. AI Agent usage is charged to one allowance on the account, so every client project draws from that same account balance. - Shared across your account: every client project draws from one common pool, so heavy use on one client leaves less for the others. - There is no separate allowance per project or workspace. Every client project on the same account draws from that account's AI Agent credits, so usage in one project reduces what is left for the others. A different client account has its own allowance. Open Billing to review your account’s available credits and usage. Where available, the Atlas Agent Credits row shows account-level AI Agent usage and allowance, not a separate allowance for each project. If your account uses Universal Credits, check that balance too. Contact our team if the figures are unclear. (customer-frontend/src/modules/billing/v1/components/billing/invoice-list/components/quota-topups/index.tsx:1854–1873) 🔍 How to Check Your Current Usage 1. Log in to the Search Atlas platform. 2. Open your account menu and select Billing. If Billing is unavailable for your role, ask your account administrator to check the allowance. (customer-frontend/src/components/layoutV2/user-menu/index.tsx:241–261) 3. Find the AI Agent usage information for your current billing period. 4. Note how much quota you have used and how much remains. 5. The usage view shows one account total. It does not compare AI Agent usage between client projects, so you cannot see which project used the most from that screen. Where available, the Atlas Agent Credits row shows credits used against the total available allowance, including recurring and purchased credits. Purchased credits roll over until used. Usage updates after processing, so allow time and refresh Billing if a recent task is not yet reflected. (customer-frontend/src/modules/billing/v1/components/billing/invoice-list/components/quota-topups/index.tsx:1320–1332,1862–1869; customer-frontend/src/modules/billing/v1/utils/atlas-agent-credits-topup.ts:61) 📊 Planning Your Usage Across Clients If your quota is shared, a little planning keeps one client from using everything. These habits help: - Estimate per client: decide roughly how many AI Agent tasks each client needs each month. - Prioritize high-value work: run the tasks that matter most for each client first. - Batch similar requests: group related tasks into one clear request instead of many small, repeated ones. - Avoid duplicate runs: check whether a task has already been completed before running it again. - Review mid-cycle: check your usage around the middle of the billing period so you can adjust early. ⚠️ What Happens If You Run Low? If you are close to your limit, you can usually do one of the following: - Wait for your quota to refresh at the start of the next billing period. - Reduce or reschedule lower-priority tasks. - Review your plan to see whether a higher tier or add-on better fits the number of clients you manage. Before purchasing anything, confirm how the change would apply to all of your client accounts so you only pay for what you need. 🛠️ Common Questions - Does adding a new client reset or increase my quota? Adding a client does not automatically change your quota. Check your usage page after adding one to see whether anything changed. - Can I see which client used the most? Where project-level usage is shown, compare the figures across your projects. If you cannot find this breakdown, ask our team. - Will my team members use the same quota? Team usage generally counts toward the account or plan it belongs to. Confirm this if several people run tasks on your account. 💬 Getting Help When you contact us, it helps to have these details ready: - Your current plan name. - The number of client projects you manage. - What your usage page currently shows. - Whether you are planning to add more clients soon. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

Last updated on Oct 29, 2026

🛠️ Fixing Otto Redirect Errors and Playbook Cooldowns

🔍 Overview If OTTO reported redirect errors and you then tried to reprocess your site, you may have seen a message that manual reprocessing is on cooldown. This wait is separate from crawl allowances and can remain active even if the accepted crawl later fails. This article explains the wait, how to address redirect problems, and what to do next. ⏳ Why a Playbook Cooldown Appears OTTO has two separate waiting rules. Its recommendation system places the same Playbook on cooldown for the same project for 14 days after a qualifying run. Separately, accepted manual site reprocessing requests are limited to once every 24 hours per project. Playbook runs with reserved, started, or succeeded status count toward the recommendation system’s 14-day cooldown; failed or cancelled runs do not. The 24-hour manual-reprocessing wait starts when a processing task is successfully accepted, even if that task later fails because of redirect errors. Rejected retries do not extend this wait or accumulate toward a separate retry limit. These cooldowns are system-controlled, not account preferences. If you need help with a blocked retry, contact support to investigate; an override is not guaranteed. 🔁 Common Causes of Redirect Errors Redirect errors can occur when the crawler cannot follow a redirect successfully or when your homepage redirects to a different registered domain, even if that destination loads in your browser. Possible causes include: - Redirect loops: Page A sends visitors to page B, and page B sends them back to page A. - Long redirect chains: A URL passes through several redirects before reaching the final page. - Conflicting rules: Your hosting, CMS, or a plugin redirects to a different version of the URL than another tool does, such as http vs https or www vs non-www. - Trailing slash differences: One rule adds a trailing slash while another removes it. - Cross-domain redirect: the homepage entered for your project redirects to a different registered domain. Use the final destination URL where your content is hosted when creating the audit. ✅ How to Fix Redirect Errors Before Re-Running Fixing the cause first avoids another failed run and another wait. Follow these steps: 1. Open the affected URLs in a private browser window. If the page fails to load or keeps reloading, you likely have a loop. 2. Confirm which version of your domain is your main one (https or http, www or non-www). 3. Check that the website in your Search Atlas project is the final destination URL where your content is hosted, including the right protocol and www or non-www form. 4. Review redirect rules in your hosting panel, CMS, and any redirect or security plugins. Remove duplicate or conflicting rules. 5. Shorten chains so each old URL redirects once, directly to its final destination. 6. Check that your OTTO installation is still present and working after site or plugin changes. Caching and JavaScript optimization plugins can interfere with the OTTO script even when it remains installed. 7. Clear your site cache and any CDN cache so the fixes are live. 🚀 Re-Running Your Playbook or Crawl After your fixes are live and any applicable cooldown has expired, submit one Playbook or manual-reprocessing request and let it finish. Manual reprocessing is refused while the site audit is processing. Once a manual reprocess is accepted, another is blocked for 24 hours, even if the accepted task later fails. A qualifying Playbook run places that Playbook on recommendation cooldown for the same project for 14 days. If the same errors appear after a clean run, note the exact error message and the affected URLs. This helps our team find the cause faster. 💳 If You Think Failed Crawls Were Counted If several crawls failed because of redirect errors, you may be concerned about being charged for them. Our team can review your usage history and the failed runs on your account. Review outcomes depend on what the records show, so we cannot promise a specific result in advance. 📝 What to Include in Your Request To speed up the review, have the following ready when you contact us: - The website or project name - The Playbook name and the Otto error message you saw - The approximate date and time of the failed runs - How many crawls or runs you believe were affected - Whether you need the Playbook cooldown reviewed so you can re-run it - Any redirect fixes you have already made 💬 Getting Help If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team. 💡 Tips to Avoid This Next Time - Check your redirects after any site migration, SSL change, or plugin update. - Avoid re-running a Playbook repeatedly while errors are still showing. - Keep your project domain in sync with your site's main domain. - Review Otto error reports as soon as they appear so small issues do not turn into repeated failures.

Last updated on Oct 29, 2026

🛠️ Fixing Outdated Schemas and Atlas Credit Usage

📌 Overview Two questions come up often in support: why the schema markup in OTTO looks out of date, and why Atlas Agent credits can drop quickly when the Agent returns incorrect HTML. This article explains both issues and shows you what to do about them. 🔍 What Are FOUND Schemas? OTTO groups schema markup (structured data) into two kinds: - FOUND schemas: markup OTTO detected already on your live page the last time it scanned it. - Suggested or generated schemas: markup OTTO recommends or creates for you. FOUND schemas are a snapshot of what OTTO saw during its last scan. They are not a live view of your page, so they can fall behind if your site has changed since then. 🕰️ Why Your FOUND Schemas May Look Outdated - The page changed after the last scan: prices, business details, authors, dates, or product info were updated on your site, but OTTO has not rescanned the page yet. - Old markup is still on your site: a theme, plugin, or old template may still output the previous schema. OTTO reports it correctly, but the source is outdated. - Caching: your website, CDN, or caching plugin may be serving an older version of the page to the scanner. - Duplicate schemas: several plugins or templates may each add their own markup, so old and new versions appear together. 🔄 How to Refresh Outdated FOUND Schemas 1. Open the page in your browser and confirm the information on the live page is correct and current. 2. Update the schema at its source. This might be your CMS, an SEO or schema plugin, or your theme settings. If the old markup is still published on your site, OTTO will keep finding it. 3. Clear your site cache, plugin cache, and CDN cache so the updated page is served. 4. In OTTO, use Manual reprocess on the project (it recrawls the whole site, then refreshes OTTO, and can only be run again after 24 hours). You can also use Recrawl Site in Site Audit. Recrawl Page on a single page only re-fetches that page. It does not refresh FOUND schemas. 5. Wait until the site recrawl and OTTO processing finish, then review the FOUND schemas again. They will match the markup from that crawl. A single-page Recrawl Page does not update them. 6. Check the page with a public structured data testing tool to confirm that only one correct version of each schema type appears. Tip: If you have many pages, start with your most important ones, such as your homepage, top service or product pages, and contact page. ✅ How to Keep Schemas Current - Rescan key pages after any major change to business details, pricing, or page content. - Use one source of schema markup per page. Disable overlapping plugins or templates that output the same data. - Clear caches whenever you publish important updates. - Review your schemas on a regular schedule, such as once a month. ⚡ Why Atlas Agent Credits Can Run Out Quickly Atlas Agent uses credits whenever it processes a request. If the Agent returns HTML that is incorrect or unusable and you retry several times, each attempt can use credits. A few repeated retries can use up a large part of your balance. Common causes of incorrect HTML output include: - Broad or unclear requests that cover too many things at once. - Missing context, such as the page URL, the exact section to change, or the format you need. - Very large pages or complex layouts that are difficult to edit in one pass. - Conflicting instructions across several retries in the same conversation. 🛡️ How to Protect Your Credits 1. Work on one page or one section per request instead of asking for a full-site change. 2. Be specific. State the page, the element to edit, the output you expect, and any limits, such as keeping existing classes or IDs. 3. Review the first result before retrying. If it is wrong, change your instruction instead of sending the same request again. 4. Stop after two failed attempts. Repeating the same request rarely fixes the problem and keeps using credits. 5. Start a fresh request if a conversation has become long or confusing, so earlier mistakes do not carry over. 6. Test generated HTML on a staging page or in a preview before publishing it. 📅 Understanding Credit Balances and Quota Resets - Plan quota: the usage included with your subscription refreshes according to your billing cycle. - Purchased credits: extra credits you buy are added to your balance and are used as you make requests. You can check your current balance, plan details, and billing cycle date in your account and billing settings inside the platform. If your balance looks wrong after a purchase or a reset date, note the date and the approximate number of credits you expected. 💬 What to Do If Credits Were Used on Failed Results If Atlas Agent repeatedly returned incorrect HTML and used most of your credits, our team can look into what happened. Have this information ready: - The date and time of the affected requests. - The page URL or project you were working on. - A short description of what you asked for and what the Agent returned. - Your credit balance before and after, if you know it. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team. 📝 Quick Summary - FOUND schemas show what OTTO detected at its last scan, not a live view of your page. - Fix outdated markup at its source, clear caches, then rescan. - Use specific, single-page requests with Atlas Agent, and stop after two failed attempts. - Check your billing settings for your balance and reset date, and use the chat widget if something looks wrong.

Last updated on Oct 29, 2026

⚙️ Understanding OTTO Site Slots and Top-Ups

📌 Overview OTTO works on a set number of site slots. Each site you activate with OTTO uses one slot. If every slot is in use, or a slot hasn't been released yet, you won't be able to add another site until space is available. This article explains how slots work, why a replacement site may be blocked, and what to do next. ❓ The Most Common Question Customers often tell us: I removed a site from my projects and portfolio and tried to add a new site to replace it for OTTO, but the platform won't let me add it. This is expected in some cases. Removing a site from your projects or portfolio list does not always free up its OTTO slot right away. The slot can stay assigned to the original site, so the new site is treated as an additional one. 🔍 How OTTO Site Slots Work - Your plan includes a specific number of OTTO site slots. - A slot is used when a site is activated with OTTO, not only when it appears in your projects list. - Deleting a project or portfolio entry is not the same as releasing the OTTO slot it was using. - If all slots are in use, you need to free a slot or add capacity before activating another site. 🧩 Why You May Not Be Able to Add a Replacement Site - The old slot is still assigned. The removed site may still count toward your OTTO allowance. - You've reached your plan limit. All included slots are in use, so a new site can't be added. - A top-up is required. If you need more sites than your plan includes, extra slots must be added to your account. - The change hasn't updated yet. Slot counts can take a short time to refresh after a site is removed. 🛠️ What to Try First 1. Refresh the page, or log out and back in, to make sure your account shows the latest information. 2. Check your plan and billing settings to see how many OTTO site slots you have and how many are in use. 3. Review your active OTTO sites and confirm which ones are using slots. 4. Make sure the site you removed is fully deactivated in OTTO, not just removed from the projects list. 5. Try adding the new site again. 💳 When a Top-Up Is Needed If all of your slots are in use and you want to keep every site active, you'll need a top-up to add more OTTO site slots. A top-up increases the number of sites you can run on OTTO without replacing an existing one. You'll likely need a top-up if: - You want to add a new site without removing an existing one. - Your removed site's slot isn't being released and you still need the new site active. - You are managing more sites than your current plan includes. 🔄 Swapping One Site for Another If you want to replace one site with another and stay within your current plan, follow these steps: 1. Deactivate OTTO on the site you no longer need. 2. Confirm the slot count has updated on your account. 3. Add the new site to your projects. 4. Activate OTTO on the new site. If the slot doesn't free up after these steps, the account may need a manual check by our team. 💡 Tips to Avoid Slot Issues - Check your slot usage before planning to add or replace sites. - Deactivate OTTO on a site before you remove it from your projects. - Allow a little time for your account to update after making changes. - Plan ahead if you expect to manage more sites, so you can add a top-up in advance. 🙋 Need More Help? If you still can't add your new site, or you aren't sure whether your slot was released, our team can check your account and confirm your slot usage. When you contact us, mention the site you removed and the site you're trying to add so we can help faster. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

Last updated on Oct 29, 2026

🛠️ How to Roll Back OTTO Schema Deployments

Deployed schema markup in OTTO and now want to undo it? This article explains how to roll back schema safely, what to check before you delete anything, how schema supports Answer Engine Optimization (AEO), and how to run a new audit to confirm your changes. 🔍 What Is a Schema Rollback? A schema rollback means removing structured data that OTTO has deployed to your pages, so it no longer appears in your site's code. People usually do this when: - The schema contains incorrect or outdated information (for example, wrong prices, hours, or addresses). - A page has changed and the schema no longer matches the visible content. - You want to test how a page performs with and without schema. - Another plugin or tool is already adding the same schema and you want to avoid duplicates. ❓ Should I Click Delete? Deleting a schema and rolling back its deployment are different actions. Rollback preserves the schema for reuse; deletion removes an eligible schema from the active OTTO list. - Rolling back stops OTTO from deploying the selected schema or schema changes. Schema already present on your website independently of OTTO may remain and must be changed at its original source. - Delete Schema removes an eligible schema from your active OTTO list. There is no user-facing undo for this action, so you may need to create a new schema later. FOUND schemas cannot be deleted in OTTO. Source: content-assistant/app/ca/api/v2/views/otto\_schema.py:369–385; customer-frontend/src/modules/otto/v3/overview/body/issuesTable/baseModels/schema/components/schemaDrawer/index.tsx:1115–1180. - If you are not sure which option applies to your deployment, take a screenshot of what you see and confirm with our team before proceeding. In the schema preview, click the active Deployed button to roll back deployment. For schemas deployed with validation warnings, OTTO displays an additional Undo Deployment confirmation. Source: customer-frontend/src/modules/otto/v3/overview/body/issuesTable/baseModels/schema/components/schemaDrawer/index.tsx:1043–1080,1207–1213. 📝 How to Remove Schema Deployments 1. Log in to Search Atlas and open the project for the site you want to change. 2. Go to OTTO SEO and open the schema section for that project. 3. Find the schema deployment you want to remove. You can usually identify it by the page URL and the schema type (such as Organization, FAQ, Product, or LocalBusiness). 4. Find the deployed schema, open its preview, and click Deployed to roll back its deployment while retaining the schema in OTTO. Do not choose Delete Schema if you only want to stop deployment. Source: customer-frontend/src/modules/otto/v3/overview/body/issuesTable/baseModels/schema/components/schemaDrawer/index.tsx:1043–1080. 5. Confirm the action when prompted. 6. Repeat for any other pages where you want to remove schema. Tip: If you only want to fix a mistake, editing the schema and redeploying it is often faster than removing it altogether. ⏱️ How Long Until the Change Shows Up? After you remove a deployment, the change may not appear instantly. Several things can delay it: - Your site cache: Caching plugins or a CDN may keep serving the old version of the page. Clear your cache after removing schema. - Search engine recrawling: Google and other search engines need to revisit the page before they update what they show. This can take days or longer. - Your browser: Try a private window or a hard refresh when checking the page. ✅ How to Confirm the Schema Is Gone 1. Clear your site cache and any CDN cache. 2. Open the page in a private browser window. 3. View the page source and search for application/ld+json. If the OTTO schema was removed, the related block should no longer appear. 4. You can also paste the page URL into a structured data testing tool, such as Google's Rich Results Test, to see which schema is still detected. If schema still appears, it may be coming from your theme, another plugin, or a different tool rather than OTTO. 💡 How Schema Supports AEO Answer Engine Optimization (AEO) is about helping search engines and AI-driven answer tools understand your content and present it accurately. Schema markup helps by labeling key details on a page, such as who you are, what you offer, and which questions you answer. Keep these best practices in mind: - Match your visible content. Schema should describe what people can actually see on the page. - Keep it current. Update schema when prices, services, hours, or FAQs change. - Avoid duplicates. Only one source should add the same schema type to a page. - Use relevant types. FAQ, Organization, Product, Article, and LocalBusiness are common choices, but only use those that fit the page. Schema helps search engines interpret your content, but it does not guarantee rich results or placement in AI answers. Removing schema is a valid choice if it is inaccurate or does not fit the page. 📊 Running a New Audit or Report After you roll back or change schema, run a fresh audit so you can see the current state of your pages. 1. Open your project in Search Atlas. 2. Go to the audit or reporting tool you normally use for site health. 3. Start a new audit for the site or the specific pages you changed. 4. Wait for it to finish, then review the structured data and on-page results. 5. Compare the new results with your previous report to confirm the schema changes are reflected. If the new report still shows old schema, wait for your cache to clear and run the audit again. 🧭 Troubleshooting - I removed schema but it is still on my page: Clear your cache and check whether another plugin or theme is adding it. - I deleted something by mistake: You can usually recreate or regenerate schema in OTTO. Let our team know if you need help restoring it. - The audit still shows errors: Run a new audit after caching has cleared, then review any remaining issues. - I cannot find the remove option: The layout may differ for your project, so reach out using the chat widget and share a screenshot. 🙋 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 instantly connected with a member of our team.

Last updated on Oct 29, 2026

🛠️ Fixing OTTO Scan Failures: Cloudflare vs Pixel

🔍 Quick Answer If OTTO SEO scans keep failing, open the installation diagnostics to identify the problem. OTTO supports Cloudflare and JavaScript pixel installation, among other methods. If diagnostics confirms multiple independent installations, keep one and remove the unwanted installation. Clear relevant site and browser caches after making changes, then scan again. Duplicate installations are one possible cause, not a verified most-common cause. ⚠️ Why Scans Fail When Both Methods Are Active OTTO reads your pages and applies SEO improvements on top of them. With two methods active, the following can happen: - Multiple independent OTTO installations can trigger a Duplicate Installation warning. Use diagnostics to identify the installations before removing anything; multiple OTTO markers in a page do not necessarily mean changes are being applied twice. - Cached pages can show outdated installation information. OTTO’s installation and deployment checks also inspect JavaScript-rendered pages, where OTTO modifications are expected; seeing modified content does not itself indicate a scan failure. - Cloudflare security features, such as bot protection or firewall rules, can block the scanner while the pixel still loads for regular visitors, or the other way around. - Old cached pages can keep showing the previous setup after you change methods, so the scan looks like it is still failing. 🧭 Which Installation Mode Should I Use? Choose the method that matches how your site is managed: - JavaScript pixel: Best if you can edit your site's header or use a tag manager and do not want to change DNS or Cloudflare settings. It is usually the simplest option. - Cloudflare: Best if your domain already runs through Cloudflare and you are comfortable managing it there. It needs the right access and settings in your Cloudflare account. If you are unsure, follow the installation guide’s recommendation for your website. It may recommend an automatic CMS integration or Manual Installation using a Code Snippet. Manual installation does not require connecting a Cloudflare account, although Cloudflare security on your site can still affect scanning. Keep one intended installation and investigate any Duplicate Installation warning. ✅ The Smallest Safe Fix 1. Open your OTTO project in Search Atlas and check which installation method it is set up to use. 2. Decide on a single method (see the section above). 3. Remove only the independent installation you no longer intend to use. If keeping Cloudflare, remove any separately installed OTTO snippet from the header, tag manager, or snippet-injection plugin without removing unrelated functionality. If keeping the JavaScript pixel, use the Cloudflare integration’s uninstall flow in Search Atlas to remove OTTO’s Cloudflare deployment. Then verify the remaining installation. 4. Clear your caches (see the cache section below). 5. Go back to OTTO and run a new scan. 6. Wait for the scan’s progress and results to update automatically. Review whether the check completed successfully or reported an installation or deployment problem. If it times out or fails, follow the displayed instructions; refreshing the page alone does not guarantee completion. Avoid making other changes at the same time, such as changing DNS or switching hosts. A single change is easier to verify and undo. 👀 How to Tell Whether OTTO Is Active If you cannot see an active status in your dashboard, try these checks: - Open the OTTO project for your domain and review its installation status and diagnostics. A successful result can identify the detected installation method. If you see a warning or error, read the specific finding: an unreachable page, disabled integration, incorrect UUID, or duplicate installation requires different troubleshooting. A missing result alone does not prove an incorrect installation. - Open your live homepage and inspect both View Page Source and the rendered page in browser developer tools. Look for the OTTO script identifier sa-dynamic-optimization and confirm that its data-uuid matches your project. Multiple text matches do not by themselves prove duplicate installation, and no match in raw page source does not rule out a tag-manager or client-side installation. Use OTTO diagnostics to verify the detected installation and investigate any duplicate warning. - Test in a private window: Load the page while logged out and in a private browser window to avoid cached or admin-only versions of the page. 🧹 What If I Cannot Find the Purge Option? Many customers get stuck here. The purge option is not inside Search Atlas. It lives in the tool that caches your site. Here is where to look: - Cloudflare: Log in to Cloudflare, select your domain, and open the Caching section. Look for Configuration and then Purge Cache. Menu names can vary slightly by account and plan. - WordPress or other caching plugins: Open your caching plugin's settings and look for a Clear Cache or Purge All button. - Hosting provider cache: Many hosts have their own cache. Look in your hosting control panel for a cache or performance section. If you do not see these options, one of these is usually the reason: - You have not selected the correct domain inside Cloudflare. - Your Cloudflare user role does not include cache permissions. Ask the account owner to purge the cache or upgrade your access. - Your domain does not run through Cloudflare at all, in which case there is nothing to purge there. Use the pixel method and clear your site or host cache instead. 🔒 Check for Blocking Rules If scans still fail after you have only one method active, security settings may be blocking the scanner. Check these in Cloudflare or your hosting firewall: - Bot fight mode or similar bot protection settings that challenge automated visitors. - Custom firewall or rate-limiting rules that block unknown traffic. - Password protection, maintenance mode, or login walls that stop the scanner from reaching public pages. - Redirect loops, for example between http and https or between www and non-www versions of your domain. Make small adjustments one at a time and re-scan after each change so you know which one made the difference. 📌 Common Mistakes to Avoid - Installing the pixel while Cloudflare is already deployed for OTTO, then assuming both are needed. - Removing the pixel from the site but forgetting to disable the Cloudflare connection, or the reverse. - Re-running scans before clearing the cache, which shows old results. - Adding the pixel in several places, such as the theme, a plugin, and a tag manager. 🛡️ How to Prevent This in the Future - Note which installation method you chose and where it is installed. - Before changing hosts, themes, or Cloudflare settings, check whether the OTTO setup will be affected. - After any site change, run a new OTTO scan to confirm everything still works. 💬 Still Need Help? If scans still fail after you have used a single method and cleared your cache, have these details ready: your domain, the installation method you chose, and any error message you see. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

Last updated on Oct 29, 2026

🔄 OTTO Top-Up Not Showing After Payment

🔎 What This Issue Looks Like You purchased an OTTO top-up or an additional OTTO account and received a receipt, but the new quota doesn't appear in your account. Common signs include: - You were billed, but the extra OTTO project slot is not shown in your plan or usage details. - You can't add a new website project because the platform says your OTTO limit has been reached. - The new OTTO account appears to be missing from your dashboard. In most cases, the payment went through and the account just needs to catch up. The steps below resolve the majority of cases. ⏱️ Why It Can Happen - Processing delay: After payment, the system may need a few minutes to update your quota. - Outdated page data: Your browser may still be showing information from before the purchase. - Different workspace or account: The top-up may have been applied to a different account or workspace than the one you're viewing. - Add-on type mismatch: Some purchases, such as extra credits or a different add-on, don't increase the number of OTTO projects you can create. - Sync issue: In rare cases, the payment is recorded but the quota update didn't complete and needs a manual fix from our team. ✅ Step-by-Step: Quick Checks 1. Wait 10 to 15 minutes. If you just paid, give the system a little time to finish updating. 2. Refresh the platform. Reload the page. If that doesn't help, log out and log back in. 3. Clear your browser cache or try a private/incognito window to rule out stale data. 4. Check you're in the right account. Make sure you're logged in with the same email and in the same workspace you used for the purchase. 5. Review your billing details. Open the billing or subscription section and confirm the OTTO top-up or additional OTTO account appears there with the correct quantity. 6. Check your OTTO usage. Look at your OTTO project count and limit. If the limit has increased, try adding your website project again. 7. Check your receipt. Confirm the receipt lists the item you intended to buy, such as an additional OTTO account, and not a different add-on. 🌐 If You Still Can't Add the Website Project If the quota looks correct but the project still won't add, try the following: - Confirm the website URL is entered correctly, including the right domain format. - Check that the domain isn't already added as a project in another workspace or account. - Try again in a different browser or after logging out and back in. If the quota still hasn't changed, or the receipt shows a purchase that isn't reflected anywhere in your account, the quota may need to be updated manually by our team. 📋 What to Have Ready Before Contacting Us Having the following details ready helps us fix the problem faster and avoids back-and-forth: - Your receipt number (for example, the one shown on your payment confirmation). - The email address on your Search Atlas account. - The website or domain you're trying to add as a new OTTO project. - What you purchased, such as an additional OTTO account or a top-up. - A screenshot of any error message or of your OTTO usage and limit. 💬 Contacting Support If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team. Share the details above in your first message so we can verify the payment, check your quota, and apply the correct update to your account. 💡 Tips to Avoid This in the Future - After purchasing a top-up, refresh the platform and check your OTTO limit before adding the new project. - Purchase add-ons while logged in to the account and workspace where you plan to use them. - Keep your receipt until you've confirmed the new quota is active. - Add your new website project soon after the quota appears, so any issues are caught early. ❓ Quick FAQ - Was I charged twice? Not usually. A missing quota doesn't mean a duplicate charge. Check your billing section, and if you see an unexpected charge, mention it in chat. - How long should I wait? Most updates appear within a few minutes. If nothing changes after about 15 minutes and a refresh, reach out to our team. - Will I lose my payment? No. Your receipt confirms the purchase, and our team can correct the quota on your account.

Last updated on Oct 29, 2026

🧊 OTTO Project Limit Reached Due to Deep Freeze

❓ What This Message Means You may see this message when you try to add a new OTTO site: "You have hit the limit of [your plan's OTTO site allowance] OTTO projects. Please upgrade your plan to add more." The number is your plan limit, which can be 2 but is not always 2. This can be confusing if only one site looks active. The most common cause is a site in Deep Freeze. A frozen site is not actively optimizing, but for 14 days after it is frozen it still holds one of your plan's OTTO site slots. During that window the platform counts the frozen site toward your limit, so one active site plus one recently frozen site counts as two. After 14 days the slot is released automatically, and unfreezing later uses a free slot again. 🧊 What Deep Freeze Does Deep Freeze pauses a project so it stops running, without removing it from your account. This is useful if you want to keep a project's setup and history for later. - A frozen project is paused, not deleted. - It keeps its slot reserved for 14 days so you can unfreeze it without using another slot. After 14 days the slot is released, and bringing the site back requires an available slot. - A Deep Frozen site's slot counts toward your plan's OTTO site limit for 14 days after it is frozen. Once that window ends, the slot no longer counts. - You will not see it among your active projects, but it still counts against your limit. 🔍 How to Confirm a Frozen Project Is Using a Slot 1. Open the OTTO section of the platform. 2. Go to your list of OTTO projects. 3. Switch from the Active tab to the Deep Frozen tab. Sites there are marked frozen, and each one that is still holding a slot shows how many days remain until the slot is released. 4. Count every project in the list, active and frozen. If the total matches your plan's limit, the frozen project is the cause. If you cannot see a second project in your list but still get the limit message, use the chat steps at the end of this article so our team can check your account. 🔓 How to Free Up a Slot You have a few options, depending on what you want to do with the frozen project. - Option 1: Unfreeze the site you want to use. Open the frozen site and choose "unfreeze the site." If you do this within 14 days of freezing it, it becomes active again without using another slot. After 14 days its slot has already been released, so unfreezing needs a free slot and may be blocked until you remove another site or upgrade. - Option 2: Remove a site you no longer need. On the site's menu, choose Remove and confirm. Removing it releases its slot immediately. The site disappears from your lists, and this cannot be undone from the dashboard, so make sure you do not need it first. - Option 3: Upgrade your plan. If you need more projects running at once, upgrading gives you more OTTO project slots. 📝 Step-by-Step: Swap an Active Project for a Frozen One Use these steps if you want to work on the frozen project and pause the one that is currently active. 1. Open the OTTO section and find your projects list. 2. Open the OTTO site you want to pause, open its action menu, and choose Deep Freeze. The menu shows this only when the site is not already frozen. 3. Find the frozen project you want to bring back and choose the option to unfreeze it. 4. Refresh the page and confirm that the project you want is active. 5. Try adding your new project again, if that was your original goal. Note: Because a frozen project can still hold a slot, freezing one project to make room for another may not lower your project count. If you still see the limit message after freezing, you will need to remove a project or upgrade your plan. 💡 Tips to Avoid This in the Future - Check your full project list, including frozen projects, before adding a new one. - Remove projects you no longer need instead of leaving them frozen. - Remember that your plan's limit applies to all projects, not only active ones. - Review your plan details if your project needs grow. 🛠️ Still Seeing the Limit Message? Contact our team if any of these apply: - You see the limit message but cannot find a second project in your list. - You tried to unfreeze a project and nothing happened. - You removed a project and the limit message still appears. - You are not sure which project is holding the slot. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team. To help us resolve it faster, include the name or website address of the project you want to unfreeze or use, and the exact message you are seeing. ✅ Quick Summary - The limit message counts all OTTO projects, including those in Deep Freeze. - A frozen project can hold a slot even when it is not running. - To free a slot, unfreeze and swap projects, remove a project you no longer need, or upgrade your plan. - If the numbers do not add up, our team can check your account in live chat.

Last updated on Oct 29, 2026

🛠️ Fixing OTTO Project Creation Errors on New Domains

🔍 What This Error Looks Like When creating an OTTO SEO project, setup may stop with an error. Check the error message and refresh your OTTO project list before trying again, because the project or its underlying Site Audit may already have been created. Source: content-assistant/app/ca/models/otto\_project.py:2833–2864. This usually means the platform could not finish setting up the project. It does not mean anything is wrong with your website. In most cases it can be fixed with the steps below. 🤔 Why It Happens A few common causes can trigger this error: - After a plan upgrade, refresh the dashboard to see updated account information. If OTTO still reports that you have reached your project limit, check your available quota and contact support if it does not match your purchase. Signing in again does not itself update server-side quota. Source: content-assistant/app/core/quota\_v2.py:193–205; app/ca/api/v2/views/otto\_project.py:359–361. - Enter a valid website domain or homepage URL, such as example.com or https://example.com/. A page path, query string, or trailing slash is not inherently a cause of OTTO setup failure, although using the homepage address avoids confusion. Source: customer-frontend/src/shared/constants/regex.ts:17; content-assistant/app/utils/requests\_utils.py:617–625; app/utils/url\_utils.py:747–748. - A previous attempt may have created a Site Audit or OTTO project before a later step failed. Check for an existing project in the relevant account before retrying. A project belonging to another account does not, by itself, prevent creation in yours. Source: content-assistant/app/ca/models/site\_audit.py:3119–3133; app/ca/models/otto\_project.py:2833–2842. - Domain not reachable: OTTO needs to confirm the site is live. A site that is down, password-protected, or blocking automated visits can cause a setup error. - Temporary service issue: Sometimes a short-lived backend problem interrupts the request, and it clears up on its own. ✅ Step-by-Step Fixes Try these steps in order. Most customers resolve the problem within the first few. 1. Refresh your session. Log out of Search Atlas, close the browser tab, and log back in. This reloads your account and plan details, which is especially helpful right after an upgrade. 2. Confirm your plan is active. Open your account billing page and check that your upgraded plan shows as active and that you have OTTO project slots available. 3. Enter your website’s domain or homepage URL, such as example.com or https://example.com/. Use the final destination website if your address redirects elsewhere. Paths, query strings, and trailing slashes are not inherently invalid; setup normalizes the address before checking reachability. Source: customer-frontend/src/modules/otto/v3/all-sites/add-site-modal/Steps/stepOne.tsx:264–272; content-assistant/app/utils/requests\_utils.py:617–625,698–699. 4. Look for an existing project. Search your OTTO project list and any other workspaces or accounts you manage. If the domain is already there, open that project instead of creating a new one. 5. Verify your website loads. Visit the domain in a private browser window. Make sure it opens without a login, a maintenance page, or a security block. 6. Clear your cache or switch browsers. Clear your browser cache and cookies, or try a different browser. Disable extensions like ad blockers while you set up the project. 7. If the error appears temporary, refresh your project list before retrying. If it persists, contact support with the domain, exact error message, and time of the attempt. There is no guaranteed waiting period that resolves OTTO creation errors. ⚠️ Tips for Brand-New Domains - Make sure the domain is fully live, with DNS set up and a working homepage, before creating the project. - If the site just launched or moved, give it some time to settle, then try again. - Use the exact domain you want to optimize. Subdomains such as blog.example.com may be treated differently from the root domain. - Before retrying a failed setup, refresh your OTTO project list and check whether the project already exists. Setup normally reuses the existing Site Audit and its OTTO project. If the same error continues, contact support rather than repeatedly submitting the request. Source: content-assistant/app/ca/models/site\_audit.py:3292–3311; app/ca/models/otto\_project.py:2833–2842. 📋 What to Include if the Error Continues If none of the steps work, our team can investigate the failed project creation directly. Having the following details ready helps us resolve it faster: - The exact domain you are trying to add - The error message, such as HTTP 500 SERVICE_ERROR - The date and approximate time of your last attempt, including your time zone - A screenshot of the error, if possible - Whether you recently upgraded your plan, and which plan you are on - The browser you used 💬 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 instantly connected with a member of our team. ❓ Quick FAQ Does this error mean my payment or upgrade failed? No. A project creation error is separate from billing. Your upgrade can be active even while setup fails. Will I lose a project slot if setup fails? Normally no. A failed attempt does not create a working project, so your available slots should not be used. If a slot looks stuck, let our team know through the chat widget. Is there anything wrong with my website? Usually not. This error most often comes from account refresh timing, domain format, or a temporary service issue.

Last updated on Oct 29, 2026

🛠️ Fixing OTTO Site Quota Mismatch Errors

🔍 What This Issue Looks Like You are paying for enough OTTO sites, for example a Pro plan plus 9 top-ups that add up to 13 sites. When you try to add your 13th site, the platform shows a quota message and will not let you continue. The numbers on your invoice look correct, but the platform's site limit does not match what you are paying for. This is usually a syncing or billing-status issue, not a problem with your account or your sites. 🧮 How Your Site Quota Is Calculated Your total OTTO site quota is made up of two parts: - Base plan sites: the number of sites included in your plan (for example, Pro). - Active top-ups: each extra site pack or add-on you have purchased and that is currently active. Your quota is the base plan sites plus the active top-ups. Only top-ups with an active status count toward the limit. A top-up that is pending, unpaid, or waiting to renew may not be included yet, even though you are being billed for it. ⚠️ Common Causes of a Quota Mismatch - Pending renewal payment: your subscription or one or more top-ups are waiting on a renewal payment. Until it is confirmed, the platform may count a lower quota. - Failed or declined payment: an expired card, bank decline, or insufficient funds can leave a top-up in a pending state. - Billing sync delay: a recent purchase or renewal may take a few minutes to appear in your account limits. - Sites still counting toward your limit: sites you added earlier, such as test sites, duplicates, or sites you stopped using, may still be using a slot. - Mixed billing dates: if your top-ups were bought at different times, they may renew on different dates, so some are active while others are waiting on payment. ✅ Step-by-Step: How to Troubleshoot 1. Open your billing settings and review your current plan and the list of top-ups. Note how many show as active. 2. Look for any pending or failed payments. If a renewal is waiting, check that your payment method is valid and has not expired. 3. Update or re-confirm your payment method if needed, and allow the pending payment to process. 4. Count your current sites. Go to your OTTO site list and check how many sites are counted. Remove any sites you no longer need, such as test or duplicate entries, to free up slots. 5. Refresh your session. Log out, log back in, and reload the page. Wait 5 to 10 minutes after a payment completes, as limits can take a short time to update. 6. Try adding the site again. If the message no longer appears, your quota has synced correctly. 📋 Quick Example Say you have a Pro plan and 9 top-ups, which should total 13 sites. If only 8 of those top-ups are active because one is waiting on a renewal payment, your platform quota may be 12. You could add 12 sites, but the 13th would be blocked until the pending top-up is paid and activated. 💬 When to Contact Support If you have checked the steps above and still cannot add your site, our team can review your subscription and quota directly. Please have the following details ready: - Your plan name and the number of top-ups you believe you have - The exact wording of the notification you see - The number of sites currently in your OTTO account - Whether any payment shows as pending or failed in your billing settings If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team. 🚀 Tips to Prevent This in the Future - Keep your payment method current and check its expiry date regularly. - Make sure your account has enough funds before a renewal date. - Review your billing page after buying or renewing top-ups to confirm each one is active. - Remove unused or test sites so they do not take up your quota. - Wait a few minutes after any billing change before adding new sites. ❓ Frequently Asked Questions Why does my invoice show 13 sites but the platform blocks me? The invoice reflects what you are billed for, while the platform limit only counts active, paid items. A pending renewal can cause a temporary difference. Will I lose my existing sites while a payment is pending? Your existing sites are not removed because of this notice. The message only prevents adding new sites beyond the quota currently recognised. How long does it take for the quota to update after payment? It usually updates within a few minutes. If it has not changed after a short wait and a fresh login, contact our team through the chat widget. Do I need to buy another top-up? No. If your plan and top-ups already add up to the number of sites you need, you should not need to purchase more. Check that each top-up is active first.

Last updated on Oct 29, 2026

🛠️ Fix OTTO Pixel UUID Mismatch on Shopify

🔍 What a UUID Mismatch Means When you install OTTO SEO on Shopify, the OTTO pixel (a small code snippet) must be added to your store. During verification, Search Atlas checks your live website for this snippet and confirms that the UUID in the code matches the UUID of your OTTO project. A "UUID mismatch" means the platform found an OTTO snippet or tag on your site, but with a different UUID than the one expected for your project. The cause is usually something small, such as an old snippet from another project, a typo, or a cached copy of your site. ⚠️ Common Causes - The snippet was pasted into a theme that is not published (for example, a duplicate or draft theme). - An older OTTO snippet from another project or a previous attempt is still in the theme. - The UUID has extra spaces, missing characters, or was copied from the wrong project. - The snippet was added to the wrong file or the wrong place in the file. - A cache (Cloudflare, Shopify, or your browser) is serving an outdated version of your site. - The project in Search Atlas is linked to a different domain version (for example, www vs. non-www). - Your store is password-protected, so the verification check cannot see your pages. ✅ Step 1: Confirm the Correct UUID 1. Log in to Search Atlas and open the OTTO project for your domain. 2. Open the OTTO installation instructions and copy the pixel snippet again. Copy the full snippet instead of typing the UUID by hand. 3. Check that the project's domain matches the exact store address you are verifying, including www or non-www. If you manage more than one site, make sure you are not copying a snippet from a different project. This is one of the most common reasons for a mismatch. 🧹 Step 2: Remove Old or Duplicate Snippets 1. In your Shopify admin, go to Online Store, then Themes. 2. On your live (published) theme, click the three-dot menu and choose Edit code. 3. Open layout/theme.liquid. 4. Use the search function (Ctrl+F or Cmd+F) to look for "OTTO" or for the UUID you were using before. 5. Delete any old or duplicate OTTO snippets. Only one OTTO snippet should remain. Also check any custom theme files or apps that inject scripts into your store. Some of them may add an older copy of the pixel. 📌 Step 3: Add the Snippet to the Live Theme 1. Still in layout/theme.liquid, find the opening head tag near the top of the file. 2. Paste the OTTO snippet on a new line directly after the opening head tag. 3. Click Save. Make sure you are editing the theme marked as Current theme. Changes made to an unpublished theme do not appear on your live store and will fail verification. 🔄 Step 4: Clear Every Layer of Cache Clearing Cloudflare is a good first step, but it is not always enough. Work through these: - Cloudflare: Use Purge Everything in the Caching section instead of purging a single file. Wait a minute or two afterward. - Cloudflare optimizations: Temporarily turn off features that rewrite or delay scripts, such as Rocket Loader, Auto Minify, or Mirage. These can change or hide the pixel from the verification check. - Browser: Open your store in a private or incognito window. - Apps and page builders: If you use a speed optimization app, clear its cache too. 🌐 Step 5: Check What Your Live Site Shows This step confirms whether the correct UUID is really visible to the outside world. 1. Open your store's home page in an incognito window. 2. Right-click the page and choose View page source. 3. Search for "OTTO" or for your UUID. 4. Compare the UUID in the page source with the UUID shown in your Search Atlas project, character by character. What you see tells you what to fix: - No snippet found: The snippet is in the wrong theme or file, or a cache is hiding it. Go back to Steps 3 and 4. - A different UUID: An old snippet is still active. Go back to Step 2. - The correct UUID: Move on to Step 6 and try verification again. 🔐 Step 6: Check Store Access and Domain Settings - If your Shopify store has a storefront password, turn it off temporarily. Verification cannot read password-protected pages. - Check that your primary domain in Shopify matches the domain in your OTTO project. If your store redirects from one version to another (for example, non-www to www), use the final destination address. - If a Cloudflare firewall rule or bot protection is active, make sure it is not blocking automated requests to your home page. 🚀 Step 7: Run Verification Again 1. Wait 2 to 5 minutes after your last change. 2. Return to your OTTO project in Search Atlas. 3. Click the verification button again. Once the check passes, you can turn your Cloudflare optimizations back on. If verification fails again after they are re-enabled, keep Rocket Loader off for your store. 💡 Quick Tips to Avoid This Issue - Always copy and paste the snippet. Do not type the UUID by hand. - Paste the snippet only once, and only in the live theme. - After switching or updating your Shopify theme, check that the OTTO snippet is still there. - Purge your Cloudflare cache after every change to your theme code. 💬 Still Not Working? If verification still fails after these steps, have the following ready so we can help you faster: your store's domain, the UUID shown in your OTTO project, and the UUID you see 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 instantly connected with a member of our team.

Last updated on Oct 29, 2026

💡 OTTO Site Quota After Upgrading or Cancelling

If you recently upgraded to a Pro plan and your OTTO site count looks different than expected, you are not alone. This article explains how OTTO site quota works, why extra sites may not carry over after a plan change, and how to check what you will be billed after removing a site. ❓ The Question We Hear Most A common scenario looks like this: you upgraded to Pro, your previous additional OTTO quota did not seem to carry over, and you now see 5 OTTO sites. You only need 4, so you cancel one. Will you be charged for 4 sites or 5? The short answer: billing depends on the OTTO quota on your subscription, not only on how many sites you currently have connected. Removing a site frees up a slot, but it may not lower your paid quota on its own. The steps below show how to check and adjust this. 🧩 How OTTO Site Quota Works Your total OTTO site quota is usually made up of two parts: - Plan quota: the number of OTTO sites included with your plan (for example, Pro). - Additional quota: extra OTTO sites you added on top of your plan. Your total quota is the plan quota plus any additional quota. The number of connected sites cannot exceed this total. 🔄 Why Additional Quota May Not Carry Over After an Upgrade When you switch plans, the new plan starts with its own included OTTO sites. Extra quota you bought on your previous plan may not be merged into the new plan automatically. This can lead to: - A different total number of OTTO sites than you expected. - Additional quota still showing as a separate item on your subscription. - Sites that remain connected even though you no longer need them. This is why it is worth reviewing your subscription right after any plan change. 🧾 What You Will Be Billed After Cancelling a Site Removing or cancelling an OTTO site and reducing your paid quota are two separate actions. Keep these points in mind: - If you remove one site but your total quota still shows 5, you may continue to be billed for 5 slots, with one slot unused. - If you also lower your additional quota to match the 4 sites you want, your next bill should reflect 4. - Changes usually apply from your next billing cycle. Charges that have already been made are not automatically reversed. Because plan details and billing dates differ between accounts, always confirm the numbers on your own Billing page before your next renewal date. 🔍 How to Check Your Current Quota 1. Log in to your Search Atlas account. 2. Open your Billing or Subscription settings. 3. Find your current plan and note your included OTTO sites. 4. Look for any additional OTTO quota listed as a separate line item. 5. Compare the total with the number of OTTO sites you want to keep active. 6. Check your next renewal date, so you know when changes will apply. 🛠️ How to Align Your Quota With the Sites You Want 1. Open your OTTO dashboard and confirm which sites are still connected. 2. Remove any site you no longer want to optimize. 3. Return to your Billing or Subscription page. 4. Reduce your additional OTTO quota so the total matches your target (for example, 4 sites). 5. Review the updated summary and confirm that the new total and renewal amount look correct. 6. Take a screenshot of the summary for your records. If you cannot find an option to reduce additional quota, or the numbers do not match what you expect, our team can review your account and apply the change for you. 💡 Tips to Avoid Surprises - Review your subscription right after any upgrade or downgrade. - Make quota changes before your renewal date when possible. - Remember that disconnecting a site and lowering paid quota are separate steps. - Keep a note of how many OTTO sites you actually need each month. 🙋 Frequently Asked Questions Will I be charged for 5 sites if I only keep 4 connected? Possibly, if your subscription quota still shows 5. Reduce your quota to 4 and check the updated total to make sure your bill matches. Does my previous additional quota move to my new Pro plan automatically? Not always. Check your Billing page after upgrading to see whether it is still listed. Can I get a refund for a slot I did not use? Refund eligibility depends on your account and billing timing. Our team can review your situation and explain your options. Will removing a site delete my OTTO data? Removing a site stops OTTO from optimizing it. If you plan to re-add it later, check with our team first so you understand what is kept. 💬 Need Help With Your Account? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team. To help us resolve your request quickly, include your plan name, the number of OTTO sites you want to keep, and the date of your upgrade.

Last updated on Oct 29, 2026

🔍 Fix OTTO Not Found Status With WordPress

🔎 What This Issue Looks Like You have connected your WordPress site to your Search Atlas project, and the connection shows as active. But a report shows the OTTO SEO status as OTTO not found. In another project with the same settings, the same report may show OTTO SEO as Engaged (WP), which means OTTO was detected through your WordPress setup. This can be confusing, because both projects look identical. The difference is usually in what the report can detect on your live website, not in whether WordPress is connected. 💡 Why This Happens There are two separate things at work: - The connection: This lets Search Atlas communicate with your WordPress site. - OTTO detection: This is the report checking your live website to confirm OTTO is active and its changes are visible. A connection can be healthy while detection fails. Common reasons include: - The project domain does not exactly match the live site address (for example, www vs. non-www, or http vs. https). - OTTO has not been enabled or deployed for that specific project. - A caching plugin, CDN, or server cache is showing an older version of your pages. - A security plugin or firewall is blocking the check. - The report has not refreshed since the connection was made or fixed. - The connection was made to a different or staging site than the one in the project. 🛠️ Step-by-Step: How to Fix It Work through these steps in order. Most cases are solved by the first four. 1. Check the project domain. Open your project settings and confirm the domain matches your live site exactly, including https and www. If your site redirects from one version to another, use the final version that appears in the browser. 2. Check the WordPress connection. Go to the project's integrations or connection settings and confirm WordPress shows as connected. If you are unsure, disconnect and reconnect it, then confirm the connection is made to the correct site. 3. Confirm OTTO is enabled for this project. Open the OTTO SEO section for the project and make sure it is turned on and set up. Each project is managed separately, so enabling OTTO in one project does not enable it in another. 4. Clear all caches. Clear the cache in your WordPress caching plugin, then clear any CDN cache (such as Cloudflare) and any server-level cache from your hosting provider. Then open your site in a private browser window to check that it loads normally. 5. Review security settings. If you use a security plugin or firewall, check that it is not blocking Search Atlas or the OTTO connection. Temporarily relaxing a rule, or allowing the request, can help you confirm whether this is the cause. 6. Refresh or re-run the report. After making changes, refresh the report or generate a new one. Status labels may not update until a new check runs, so allow some time before testing again. ⚖️ Compare With the Project That Works If one project shows Engaged (WP) and the other shows OTTO not found, comparing them side by side often reveals the difference. Check these items in both projects: - The exact domain entered in the project (www, https, trailing paths). - Whether OTTO is turned on for the project. - The WordPress site that is connected to each project. - The caching, CDN, and security setup on each website. - The date and time of the most recent report. If the working project has a setting the other one does not, match them and refresh the report. ✅ How to Confirm It Is Fixed - The report shows OTTO SEO as detected, such as Engaged (WP), instead of OTTO not found. - The WordPress connection still shows as active in your project. - Your live pages load normally with no errors after clearing caches. 🚀 Tips to Prevent This Issue - Always enter the project domain exactly as it appears in your browser. - Clear your site cache after connecting WordPress or changing OTTO settings. - Set up each new project fully, including the connection and OTTO activation. - Re-check the connection after moving hosts, changing domains, or switching security plugins. - Wait for the report to refresh before deciding something is still broken. 💬 Still Seeing OTTO Not Found? If you have tried the steps above and the status has not changed, our team can look at your project directly. Please have your project domain and the name of the report ready, and mention whether another project shows the correct status. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

Last updated on Oct 29, 2026

🛠️ Fix OTTO Pixel Not Detected and Billing Help

🔍 What Is the OTTO Pixel? The OTTO pixel is a small piece of code that connects your website to Search Atlas. Once it is on your site, OTTO can read your pages and apply SEO improvements. If the pixel is not detected, OTTO cannot make changes, and your project will show OTTO not found, with the short status Not Installed and the diagnostic title OTTO not detected. ✅ How to Check Whether Your Website Is Connected 1. Log in to Search Atlas and open your OTTO project for the website. 2. Look at the pixel or installation status in the project dashboard. 3. If the short status says Installed, or the status says OTTO SEO is Engaged, the pixel is installed. Connected or Connected (verified) only means the WordPress plugin received its credentials. It does not by itself mean the pixel is live on your website. 4. If the status says OTTO not found, the short label says Not Installed, or the diagnostic title says OTTO not detected, follow the troubleshooting steps below. Make sure you are checking the project for the correct website. A project for one hostname will not detect a pixel on a different hostname, although www and non-www versions of the same hostname are treated as the same site. ⚙️ Why the Pixel Might Show as Not Installed These are the most common reasons: - The code was not saved or published. The pixel was pasted in but the changes were never published. - Wrong location. The code needs to be placed in the head section of your site, so it loads on every page. - Wrong script domain. If the status says Wrong Domain, the OTTO script was found but is being loaded from a domain Search Atlas does not recognize. This is not caused by your page using www while the project uses the non-www address, or the reverse. - Caching. A caching plugin, CDN, or hosting cache is still serving an older version of your site without the pixel. - Detection timing. A new installation is rechecked automatically about every 15 minutes during the first 2 hours. You do not have to wait for that schedule. Open the OTTO installation flow and click Check now or Scan to check immediately. - Blocked scripts. A security plugin, firewall, or script optimizer may be blocking or delaying the code. - Installed on the wrong site. The code was added to a staging or test site instead of the live one. 🛠️ Step-by-Step: Fix a Pixel Detection Problem 1. Copy the pixel again. Open your OTTO project in Search Atlas and copy the installation code fresh. Do not edit it. 2. Add it to your site. Paste it into the head section of your website, or use your platform's header or custom code area. Many website builders and WordPress plugins offer a place for this. 3. Save and publish. Make sure your changes are live and not saved as a draft. 4. Clear your caches. Clear any caching plugin, CDN, or hosting cache so the updated page is served. 5. Check your domain. Confirm the hostname in your project is the hostname of the live site. A www and non-www difference is acceptable, but a different hostname, preview address, or unpublished address will not match. 6. Run the check again. In the OTTO installation flow, click Check now or Scan. Search Atlas also rechecks a new installation automatically about every 15 minutes for the first 2 hours. Refreshing the project page after a few minutes does not by itself update the status. 7. Test in a private window. Open your live site in a private or incognito browser window to rule out saved data in your regular browser. If you are not comfortable editing your site, send the pixel code and these steps to your web developer. It usually takes only a few minutes to add. 🧩 Tips for Common Website Platforms - WordPress: Use a header and footer code plugin, or your theme's custom code option, and clear your cache plugin afterward. - Website builders: Look for a custom code or header code setting in your site's settings. Some plans limit this feature. - Tag managers: If you use one, publish the container after adding the pixel. - Custom sites: Ask your developer to add the code to the shared header template so it appears on every page. 💳 Billing, Cancellation, and Refund Requests If you are unable to get the pixel working and are thinking about cancelling, we recommend contacting our team first. Many detection issues can be fixed quickly with a little help, and our team can look at your specific setup. If you would still like to cancel or request a refund, let us know right away and include: - The email address on your Search Atlas account - The website domain you were trying to connect - A short description of what happened, such as the pixel showing Not Installed - Whether you want to cancel, request a refund, or both Refund requests are reviewed by our team, and eligibility depends on your account and billing details. Our team can confirm what is possible for your situation. If your request is urgent, say so in your first message so it can be prioritized. 💡 How to Avoid Problems in the Future - Install the pixel soon after you sign up so you can confirm the connection early. - Check the pixel status after any website redesign, migration, or theme change. - Keep a copy of your pixel code somewhere safe. - Tell your developer or agency that the pixel must stay in place. 🙋 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 instantly connected with a member of our team.

Last updated on Oct 29, 2026

⏱️ OTTO New Site Processing Time Expectations

👋 Overview When you add a new site to OTTO, the platform needs time to scan your website and prepare it for optimization. Many customers ask whether a site that has been processing for a few hours is stuck. In most cases, it is not. This article explains what is happening behind the scenes, what affects timing, and what to do if you think something is wrong. ⚙️ What Happens During Processing After you add a site, OTTO works through several preparation steps before the site is ready to use: - Discovering your pages: OTTO finds the pages on your site so it knows what it can work with. - Analyzing your content and structure: OTTO reviews page content, titles, headings, links, and other on-page elements. - Preparing recommendations: OTTO organizes what it found so your dashboard can show accurate insights. Until these steps are complete, some sections of your dashboard may be empty or show a processing status. This is expected behavior for a new site. ⏳ Is 3 Hours Normal? A processing time of a few hours is not automatically a sign of a problem. Processing time is not the same for every site, and it can be longer when several sites are added at around the same time. If you added two sites together and both still show as processing after about three hours, the best first step is to check for progress and review the factors below before taking any action. As a general guide: - Smaller sites with fewer pages usually finish sooner. - Larger sites with many pages or complex structures usually take longer. - Multiple new sites added at once may take longer than adding a single site. 🔍 What Can Affect Processing Time - Number of pages: The more pages your site has, the more OTTO has to review. - Site speed: If your website responds slowly, scanning takes longer. - Security settings: Firewalls, bot protection, or security plugins can slow down or block OTTO from reaching your pages. - Site complexity: Sites that rely heavily on scripts or dynamic content can take more time to analyze. - Number of sites added at once: Adding several sites in a short period can extend the wait for each one. ✅ What You Can Do While You Wait 1. Confirm the site URL is correct. Check that you entered the right domain, including the correct version (with or without www) and the correct protocol (http or https). 2. Make sure your site is live. Open the site in a browser and confirm it loads normally and is not password protected or in maintenance mode. 3. Review your security settings. If you use a firewall or security plugin, check that it is not blocking automated visitors. 4. Refresh the page. Reload your dashboard to see whether the status or progress has changed. 5. Give it more time. Check back later instead of making changes right away. 🚫 What to Avoid - Do not repeatedly remove and re-add the site. This can restart the process and make the wait longer. - Do not add many extra sites at once while your first sites are still processing. - Do not make major changes to your site's structure during processing unless necessary. 🚩 When to Contact Support It is a good idea to reach out if any of the following apply: - Your site has shown no change in status for a full day (24 hours). - You see an error message on the site or in the dashboard. - You confirmed that your site is live and accessible, but processing still does not move forward. - Only some pages or sections appear to be missing after processing finishes. To help us resolve it faster, have the following ready: - The full URL of each affected site - The approximate time you added each site - Any error message you saw, or a screenshot if possible - Whether your site uses a firewall or security plugin If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team. 💡 Quick Summary - Processing a new site takes time, and a few hours is not necessarily a problem. - Site size, speed, security settings, and the number of sites added at once all affect timing. - Check that your URL is correct and your site is accessible, then wait and refresh. - Avoid removing and re-adding the site, since that can restart the process. - If there is no progress after a full day, or you see an error, contact us through the chat widget.

Last updated on Oct 29, 2026

🔍 Login Redirects to Plan Selection and Duplicate Charges

📌 Overview Some customers who log in are taken to the Choose Your Plan page because the account they signed in with has no paid plan. This can happen with a new or unfinished account, or an account that was never given a paid plan. This article explains the common causes and what to do next. These two issues are often connected, so it helps to check them together. 🔁 Why Login Sends You to Plan Selection The Choose Your Plan page appears when the account you logged in with has no paid plan. Common reasons include: - A different login method or email: Logging in with a different email address, or with Google instead of email and password, can open a separate, empty account. - An expired or cancelled subscription: While a cancellation is still pending, you keep access until the end of the paid period. Once the account is deactivated, login shows an account-deactivated page rather than asking you to pick a plan. - A failed renewal: If a renewal payment did not go through, you see a payment-failed notice and can open Billing to update your payment method. This does not send you to plan selection. - A new account created by mistake: Starting a sign-up flow instead of logging in can create a second account. Important: Do not select a plan or enter payment details on this screen if you only want to cancel. Doing so may start a new subscription. 🔑 How to Confirm You Are in the Right Account 1. Log out completely and close the login page. 2. Open the login page and use Log In, not Create an account, Start free trial, or Start your free trial. 3. Try each email address you may have used with Search Atlas. 4. If you originally signed up with Google, use the Google sign-in option. 5. Check your inbox and spam folder for your original welcome or receipt emails. The address that received them is usually your main account email. If you reach a dashboard with your projects and data, you are in the correct account. 🛑 How to Cancel Your Subscription After you are in the correct account, follow these steps: 1. Open the account menu and select Billing. 2. On the Billing page, open the Services tab. 3. On the plan row, open the menu and select Cancel, then follow the prompts. 4. Look for a confirmation message or email once the cancellation is complete. Keep the confirmation. On screen it shows when your access ends. The email confirms the cancellation, but it does not state when access ends. If you cannot reach the billing section because you are stuck on plan selection, use the chat widget described at the end of this article. Our team can help with cancellation. 💳 Why You May See Two Charges Close Together Two charges in a short period can look like a duplicate, but there are several possible causes: - Two accounts or subscriptions: A second account created with another email or login method may have its own subscription and payment. - A new sign-up after a lapse: Choosing a plan on the plan selection screen can create a new charge in addition to an earlier renewal. - A plan change or upgrade: Changing plans or adding features can create an additional charge. - A retried payment: If a payment failed at first, it may have been retried and processed later. - A temporary authorization hold: Some banks show a pending hold alongside the final charge. The hold usually drops off after a few days. 🧾 How to Review Your Charges 1. Open the Billing section of your account and look at your invoice history. 2. Check your email for receipts and match each one to a charge on your statement. 3. Note the date, amount, and last four digits of the card used for each charge. 4. Check whether you have more than one Search Atlas account under different email addresses. 5. Ask your bank whether either charge is listed as pending or completed. Having this information ready helps our team review your charges faster. 💡 Tips to Avoid This Issue - Use the same email and login method each time you log in. - Do not choose a plan unless you want to start or renew a subscription. - Cancel before your renewal date. Renewals are processed automatically. - Save cancellation confirmations and receipts. - Check your statement after any plan change or failed payment. 💬 Need Help With a Charge? If you are stuck on the plan selection screen, cannot find your subscription, or think you were charged in error, our team can review your account and billing history. Please have the email addresses you may have used, the dates and amounts of the charges, and the last four digits of your card ready. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

Last updated on Oct 29, 2026

💡 Understanding OTTO Billing: Sites, Not Pixels

🔍 The Short Answer OTTO billing is based on the number of sites you have OTTO enabled for. It is not based on the number of pixels installed. Each site uses one OTTO pixel, so the two numbers often match. Billing follows the site, not the pixel. 🧩 Why Sites and Pixels Can Seem the Same A pixel is a small snippet of code that connects your website to OTTO. In most cases, one site has one pixel. That is why it can look as if you are paying per pixel. The pixel is just how OTTO connects to the site. The site is what is counted on your plan. - One site = one OTTO project on your plan - One pixel = the connection that lets OTTO work on that site - Billing = based on how many sites are active in OTTO ⚠️ What Happens If You Only Remove the Pixel Removing the pixel code from your website stops OTTO from making changes on that site. However, it does not automatically lower your plan. If the site is still active in your account, it can still count toward your OTTO billing. To avoid paying for a site you no longer use, update the site in your Search Atlas account. Removing the code from your website is not enough on its own. ✅ How to Make Sure You Are Not Billed for Unused Sites 1. Make a list of the sites you are actively using OTTO on. 2. Open your Search Atlas account and review the sites or projects that have OTTO enabled. 3. Identify any sites where OTTO is no longer needed, such as old projects, test sites, or sites you have stopped working on. 4. Remove or deactivate OTTO on those sites in your account. 5. Remove the pixel from those websites if you no longer want OTTO to run on them. 6. Check your billing or subscription settings to confirm the site count matches the sites you want to keep. If you are not sure how many sites your plan includes, or if the numbers do not look right, ask our team to review your account before making changes. 🔄 Matching Your OTTO Plan to Your Active Sites If you have fewer active sites than your plan covers, you can ask to reduce your plan to match. Before you do, keep these points in mind: - Reducing your plan may mean some sites no longer have OTTO enabled. - Billing changes may apply from your next billing cycle. Confirm the timing before you make the change. - If you plan to add the site back later, you may need to reinstall the pixel and re-enable OTTO for it. 💡 Tips to Avoid Surprises - Review your active OTTO sites every month, especially if you manage client sites. - When a project ends, remove OTTO from the site in your account and remove the pixel from the website. - Keep a simple list of which sites are active and which are paused or retired. - Ask for a billing review before you remove several sites at once. ❓ Frequently Asked Questions Am I charged for each pixel I install? No. Billing is based on the number of sites with OTTO enabled, not the number of pixels. If I remove a pixel from my website, will my bill go down? Not automatically. You also need to update the site in your Search Atlas account so it no longer counts toward your plan. Can I pay for only the sites I am actively using? Yes. Your plan should match the number of sites you want OTTO to run on. Our team can help you adjust it. Will I lose my OTTO data if I remove a site? Removing OTTO from a site can affect the optimizations running on it. Ask our team what to expect before you remove a site you may want to use again. 💬 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 instantly connected with a member of our team. Let us know which sites you want to keep active, and we can help you align your plan.

Last updated on Oct 29, 2026

🛠️ Fixing the OTTO Wrong UUID Status

🔍 What Does the Wrong UUID Status Mean? Each OTTO project has a UUID, a unique ID made up of letters and numbers. OTTO uses it to match the installation on your website to the correct project in Search Atlas. A Wrong UUID status means the ID OTTO finds on your website does not match the ID of the project you are viewing. In short, the mismatch is between your website and your OTTO project. ❓ Whose UUID Is It? This is the most common question, so here is a plain answer: - It is not a Google UUID. It has nothing to do with your Google account, Google Search Console, or Google Analytics connection. - It is the OTTO project UUID that Search Atlas generates for each project. - The status appears when the UUID in the OTTO installation on the website differs from the UUID of the project in your dashboard. 🧩 Why Does This Happen? These are the most common causes: - Wrong project's code installed. The OTTO script or snippet was copied from a different project, often when you manage several clients or sites. - Old code left behind. A previous OTTO installation, such as one from a past project or a test, is still active on the site. - Duplicate installations. The code was added in more than one place, for example in a plugin and also in the theme header. If every copy uses a UUID from a different project, the status is Wrong UUID. If one copy uses this project's UUID, the status is Duplicate Installation instead. - Project recreated. The project was deleted and re-added, so the old UUID no longer matches. Moving the project to a different domain does not change its UUID. - Cached pages. A caching plugin, CDN, or hosting cache is still serving an older version of the page with the old code. ✅ How to Fix the Wrong UUID Status 1. Open the OTTO project for the affected website in Search Atlas. Make sure you are in the correct project and domain. 2. Go to the OTTO installation instructions and copy the code or UUID shown for that project. 3. Check your website for the OTTO code in your plugin settings, theme header, tag manager, or any other place where scripts are added. 4. Compare the UUID on your site to the one in the project. If they differ, replace the old code with the correct one. 5. Remove duplicates. Keep only one OTTO installation on the site. 6. Clear all caches, including your website plugin, hosting, and CDN caches. 7. Return to the OTTO project and run Scan in the installation guide, or choose Check again on the connection status. The scan can take a few minutes, and a recently fixed status can take up to 2 minutes to update. 👥 Tips for Agencies Managing Multiple Clients - Always confirm the project name and domain before copying installation code. - Keep a simple record of each client's domain and its OTTO project. - Do not reuse installation code from one client's site on another. - When migrating a site or changing domains, re-check the OTTO installation afterward. 📄 What About Content Genius Document Uploads? Content Genius document uploads are a separate feature from the OTTO installation. If you see a UUID-related message while uploading or opening a document, the document may be linked to a different project or site than the one you are working in. Try these steps: - Confirm you are in the correct project or account. - Refresh the page and sign out and back in if needed. - Re-open Content Genius from the correct project and try the upload again. - Check that the file is in a supported format and is not corrupted. If the message persists, take a screenshot of it, including the project name, so our team can review it faster. 💡 How to Prevent It in the Future - Install OTTO only once per website. - Remove old OTTO code before adding a new installation. - Clear caches after any change to your site's scripts. - Avoid deleting and recreating a project unless necessary, since this generates a new UUID. 💬 Still Seeing the Error? If the status does not clear after following these steps, gather the project name, the website URL, and a screenshot of the status message. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

Last updated on Oct 29, 2026

🔍 Hyperdrive Credits Missing After Monthly Renewal

📌 Overview Your Search Atlas plan includes a monthly allotment of Hyperdrive Credits. On each successful renewal the monthly usage counter is reset, so the plan amount is available again without you requesting it. The on-screen balance can still look lower than the full monthly amount, for example after a billing date if credits were already used or purchased credits are separate. This article explains the common reasons and how to check them. ⚡ What Are Hyperdrive Credits? Hyperdrive Credits are the usage units included with your plan for Hyperdrive features. Each time you use a Hyperdrive feature, credits are deducted from your balance. When your plan renews successfully, monthly usage is reset so your plan allotment is available again. Purchased Hyperdrive Credits are separate and are not reset. The number of credits included depends on your plan. Check your plan details to confirm the exact monthly amount before comparing it to your balance. 🔎 Why Your Credits May Look Missing Most cases come from one of the reasons below. - The renewal payment is still processing. Credits are tied to a successful renewal. If your bank or card provider is still confirming the payment, the credits may appear a little later. - Credits were already used. If you ran Hyperdrive actions after renewal, your balance shows what is left, not the full monthly amount. - Unused monthly credits from last month do not carry over. Monthly credits reset to your plan allotment instead of being added to the previous balance, which can make the total look lower than expected. Hyperdrive Credits you purchased separately do roll over until they are used. - You are viewing a different account or workspace. If you manage more than one project, account, or login, you may be looking at a balance that does not belong to the subscription you were billed for. - Your plan or billing date changed. An upgrade, downgrade, or changed billing date can shift when credits are applied. - The page has not refreshed. A cached page can show an older balance. ✅ How to Check Your Credit Balance Follow these steps to confirm what your account shows. 1. Log in to the Search Atlas platform with the account that was billed. 2. Refresh the page, or log out and back in, to clear any outdated display. 3. Open the Billing page from your user menu and confirm your current plan and your next billing date. The billing cycle also shows when you last paid. 4. Check that the renewal payment shows as successful, not pending or failed. 5. Look at your Hyperdrive credit balance and compare it with your plan's monthly allotment. 6. Think about any Hyperdrive actions you ran since renewal, as these reduce the balance. 🧮 Quick Math Check To see whether the balance is correct, use this simple comparison: - Your current balance is the monthly credits you have left this period plus any purchased Hyperdrive Credits you still have. It is not only the monthly allotment minus what you used since renewal. - Do not add unused monthly credits from the previous month. Monthly Hyperdrive Credits reset instead of carrying over. Only Hyperdrive Credits you purchased separately remain until you use them. If the numbers do not match, move on to the next section. 🛠️ What to Do If Credits Are Still Missing If your balance is still lower than expected after the checks above, gather the following details. They help our team review your account faster and fix the issue in one conversation. - The email address on your Search Atlas account - Your plan name - The date you were billed - How many Hyperdrive credits you expected and how many you see - A screenshot of your credit balance and, if possible, your billing or renewal confirmation If you have seen this happen after more than one renewal, mention that as well. A pattern across several billing cycles helps our team check whether credits are being applied correctly to your account. 💬 How to Contact Support If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team. 💡 Tips to Avoid Confusion Next Month - Note your balance a day or two before your renewal date so you have a clear starting point. - Check that your payment method is up to date so renewals go through on time. - Look at your balance after renewal, before running large Hyperdrive tasks. - Keep a screenshot of your balance if it looks wrong. It speeds up any review. - Make sure you are logged in to the same account that holds your subscription. ❓ Frequently Asked Questions Do I need to request my credits every month? No. Credits included in your plan should be added automatically after each successful renewal. If they are not, reach out through the chat widget so our team can review it. How long after billing should credits appear? Credits normally appear soon after your payment is confirmed. If a day or more has passed and your balance still looks wrong, follow the steps above and contact our team. Can credits be missing even though my payment went through? It is rare, but it can happen. Confirm that you are viewing the right account and that your usage does not explain the difference. If it still does not add up, our team can look into it. Will I need to message support every month? You should not. If you do have to contact us repeatedly for the same issue, tell our team so they can review your account for a lasting fix.

Last updated on Oct 29, 2026

🛠️ Fix OTTO Shopify Pixel Not Detected

🔍 Overview This article covers three things Shopify customers often ask about together: OTTO showing not installed even though the script is in your theme, an error page that says please wait when you click Change Plan, and how to give someone view-only access to a single site. ⚠️ Why OTTO Says the Pixel Is Not Installed Adding the script to theme.liquid under the tag is the correct method. If OTTO still can't find it, the cause is usually one of these: - The script was added to a theme that is not published (for example, a duplicate or draft theme). - The change wasn't saved in Shopify's code editor. - The script sits outside the head section, or is inside a comment or another block of code. - Your storefront is password protected, so OTTO can't reach it. - The domain in OTTO doesn't match the domain your store uses publicly. - Your store is cached, so the old version of the page is still being served. - Your store uses a headless setup, which doesn't use theme.liquid. - The script was copied incompletely, with a missing character or an extra space. ✅ Step-by-Step: Check Your Pixel Installation 1. In Shopify, go to Online Store and then Themes. Confirm the theme you edited is the one labeled Current theme. 2. Click Edit code and open theme.liquid in the Layout folder. 3. Check that the OTTO script sits between the opening and closing tags. Place it near the top of the head section. 4. Compare it with the script shown in your OTTO project. Copy it again if anything looks different, then click Save. 5. Open your live store in a private or incognito browser window, right-click, and choose View page source. Search for the OTTO script. If you can find it, it is live. 6. Return to OTTO and click the option to re-check or verify the installation. 🌐 Check Your Domain and Store Access - Make sure the website URL in OTTO matches the domain visitors use, such as your custom domain rather than the .myshopify.com address. - If your online store has a password page, remove the password temporarily while OTTO verifies the installation. - If you use a caching or page-speed app, clear its cache after saving your theme changes. - Ad blockers can interfere with your own browser checks, so use a private window with extensions turned off when you view the source. Detection can take a few minutes after you save. If the script is visible in the page source and OTTO still shows not installed after about 15 minutes, move on to the support steps below. 💳 Fixing the Error Page When You Change Plans If clicking Change Plan takes you to an error page that says please wait, the page usually failed to load your billing details. Try the following in order: 1. Wait one to two minutes, then refresh the page. 2. Log out of Search Atlas, log back in, and try again. 3. Open the platform in a private window or a different browser. 4. Turn off browser extensions such as ad blockers or privacy tools for the session. 5. Check that you are logged in as the account owner or an admin. Only these roles can change billing. Plan changes and pixel detection are separate. You don't need to fix one before the other, and an upgrade will not install or remove the OTTO script. 👁️ Inviting a Viewer to a Single Site If you want a client or teammate to see one site without access to your other projects, send them an invite with limited access. 1. Open your account or team settings in the platform and go to the section for inviting users. 2. Enter the person's email address. 3. Choose a viewer role, which allows viewing without editing. 4. Select only the site they should see, instead of all sites. 5. Send the invite and ask them to accept it from the email they receive. If you don't see a way to limit access to one site, your plan or role may not include it. Open the chat widget and our team can confirm what is available on your account and set it up with you. 💡 Tips to Avoid This Issue Next Time - Always edit your published theme, or re-add the script if you switch to a new theme. - Keep a copy of your OTTO script, since theme updates can overwrite theme.liquid. - Re-check the installation in OTTO after any major theme change. - Use an incognito window to confirm changes, so you see what visitors see. 💬 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 instantly connected with a member of our team. To help us resolve it faster, tell us your store domain, the theme you edited, and what you see on the error page.

Last updated on Oct 29, 2026

🛠️ Fix OTTO Shopify Install Status Not Updating

🔍 What This Message Means When you run the OTTO diagnostic on a Shopify store, you may see a message saying the code is installed, but deployed fixes are not verified. This means OTTO can see its script on your site, but it has not yet confirmed that the changes it deployed are showing on your live pages. In most cases the store is set up correctly. The status is out of date because of an old cached version of your page, or because the script is not on the theme your visitors see. The steps below fix most cases. 🧭 Common Causes - Browser cache: Your browser may be showing an older copy of your page that does not include the latest OTTO changes. - Store or CDN cache: Shopify and other caching layers can serve a saved version of a page for a short time after you make changes. - Script added to the wrong theme: The script may be in a theme that is not currently published. - Script in the wrong place: The script may be outside the head section of the theme, or it may have been changed when the theme was saved. - Recent theme change: Switching, duplicating, or updating a theme can remove custom code. - Blockers: Ad blockers, privacy extensions, or a store password page can stop the check from seeing your pages. - Timing: Newly deployed fixes can take a little while to appear and be verified. 🧹 Step 1: Clear Your Browser Cache Start here, because it is the quickest fix and the most common one. 1. Open your store page in a new private or incognito window. This loads the page without saved data. 2. If you want to use your normal browser, do a hard refresh. On Windows, press Ctrl + Shift + R. On Mac, press Command + Shift + R. 3. If the status still has not changed, clear your browser cache and cookies for your store and for the Search Atlas platform in your browser settings. 4. Close the tab, reopen the platform, and run the OTTO diagnostic again. ✅ Step 2: Confirm the Script Is on Your Live Theme 1. In your Shopify admin, go to Online Store and then Themes. 2. Check which theme is marked as the current (published) theme. 3. Open the code editor for that theme and look at the theme.liquid file. 4. Confirm the OTTO script appears once, inside the head section of the page, before the closing head tag. 5. If it is missing, paste it back in exactly as shown in your OTTO setup instructions and click Save. If the script appears more than once, remove the extra copies and keep a single one. Duplicate scripts can cause unexpected results. 🔄 Step 3: Check for Theme Changes - If you recently switched or updated your theme, add the OTTO script to the new published theme. - If you use an app or page builder that changes your theme files, check that it did not overwrite your edits. - If you work with a developer, ask whether any recent changes were made to the theme code. 🚫 Step 4: Rule Out Blockers - Turn off ad blockers and privacy extensions in your browser, or test in a clean private window. - If your Shopify store has a password page turned on, the check may not be able to reach your pages. Remove the password protection if your store is ready to be public. - Make sure the store domain connected to OTTO matches the domain your visitors use, including the www or non-www version. ⏱️ Step 5: Wait, Then Re-Run the Diagnostic After you save changes or clear your cache, give the system some time to update. This can take from a few minutes to a few hours, depending on how your store caches pages. Then: 1. Go back to the OTTO diagnostic in the platform. 2. Run it again. 3. Check that the status now shows your fixes as verified. Also check that fixes have actually been deployed on the pages you are testing. Verification only applies to pages where OTTO has deployed changes. 🔎 How to Check the Result Yourself 1. Open one of the pages you expect OTTO to have changed, in a private window. 2. Right-click the page and choose View Page Source. 3. Search for OTTO or for the change you expect, such as an updated title or meta description. 4. If you can see the change, the fix is live, and the status should update soon. 💡 Tips to Avoid This Next Time - Always add the script to the published theme. - Re-check the script after any theme update or change. - Test changes in a private window so you see the current version of your site. - Allow some time after deploying fixes before you run the diagnostic. 💬 Still Seeing the Message? If you have cleared your cache, confirmed the script is on your live theme, and waited before re-running the diagnostic, our team can take a closer look. Have your store URL ready and note which pages you checked. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

Last updated on Oct 29, 2026

🔍 OTTO SEO Compatibility With Custom AI-Built Sites

✅ The Short Answer In most cases, yes. OTTO SEO is not limited to one website builder. If your site is custom-coded or created with an AI website builder, OTTO can usually be added as long as you can place a small piece of code on your site or make a change at your hosting or DNS level. Whether it works for your site depends on how the site is built and what access you have, so it helps to check a few things first. 🧩 What Counts as a Custom or AI-Built Site? These terms cover many different setups. Common examples include: - Sites generated by AI tools and then exported or hosted elsewhere - Sites hand-coded in HTML, CSS, and JavaScript - Sites built with frameworks such as React, Next.js, Vue, or similar - Sites on a custom content management system (CMS) built for one business Because the underlying technology varies, the question is not "Is it AI-built?" but "Can we add code to it, and how does it deliver its pages?" 📋 What You Need to Know About Your Site Before you set up OTTO, gather the answers to these questions. They determine which installation method fits your site. 1. Where is the site hosted? Examples include a hosting provider, a cloud platform, or the AI builder's own hosting. 2. Can you edit the site's code? You need access to the page header (the section) or to a template shared across all pages. 3. Do you have access to a tag manager? If the site uses Google Tag Manager, that may be another way to add code. 4. Do you control the domain's DNS settings? Some setups need a change at the DNS or CDN level instead of a code snippet. 5. How are pages delivered? Some sites send finished pages from the server. Others build the page in the visitor's browser with JavaScript. 6. Is there a staging or test version? Testing there first is a safe way to confirm everything works. 🔎 How to Check Your Site Step by Step 1. Log in to your hosting account or AI builder and confirm you have edit or admin access. 2. Find where you can add custom code to the header of all pages. Many builders call this "custom code," "head scripts," or "site settings." 3. If you cannot find this option, ask your developer or the builder's support team whether custom header code is allowed on your plan. 4. Open your site in a browser, right-click, and choose View Page Source. If you see your page text in the source, your pages are likely delivered from the server. If you see mostly empty containers and many script files, your site likely builds pages in the browser. 5. Note your findings. You will need them if you contact our team. 🛠️ Common Ways to Connect OTTO Depending on your setup, OTTO can be connected in one of several ways: - Code snippet: a small script added to the header of your site. This is the most common option for custom sites. - Tag manager: the same snippet added through a tool such as Google Tag Manager, if your site already uses one. - Platform plugin or app: available for some popular platforms, but usually not needed for custom sites. - Hosting or DNS-level setup: used when you cannot edit the code directly but control the domain or CDN settings. The options shown inside your OTTO setup screen may change over time, so always follow the instructions displayed in the platform for your project. ⚠️ Things That Can Limit Compatibility - No code access: some AI builders or locked hosting plans do not allow custom header code. Upgrading the plan or moving the site may be needed. - Browser-built pages: if a site builds all its content in the browser, search engines may see changes differently. Ask our team to confirm the best approach for your site. - Security rules: strict content security settings can block outside scripts. Your developer may need to allow the OTTO script. - Caching: a cache or CDN may keep showing old versions of pages. Clear it after installation. - Multiple environments: make sure you add the code to your live site, not only to a draft or preview. 🚀 After Installation: Confirm It Is Working 1. Return to your OTTO project in Search Atlas and run the connection or installation check. 2. Clear your site and CDN cache. 3. Open a page on your live site and view the page source to confirm the OTTO code is present. 4. Wait a short time for OTTO to scan your pages and begin showing recommendations and updates. 💡 Tips for a Smooth Setup - Ask your developer or AI builder's support team to confirm that custom header code is permitted before you begin. - Install on a test version first if you have one. - Keep a note of where you added the code so it is easy to find later. - If several people manage the site, tell them about OTTO so the code is not removed during a redesign or redeploy. 💬 Need Help Confirming Compatibility? If you are unsure whether your site can support OTTO, share the details you collected above: your hosting provider or builder name, whether you can edit the header code, and how your pages are delivered. Our team can review them and advise on the best setup. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

Last updated on Oct 29, 2026

💳 Understanding OTTO Site Top-Up Charges on Agency

If you manage clients on an Agency plan, you may see a charge for additional OTTO site capacity. This is a recurring top-up, although its first payment may be prorated. This article explains what the charge covers and how to review it. 💡 What Is an OTTO Site Top-Up? Your Agency plan includes an OTTO SEO site allowance. If you need more capacity, you can purchase a recurring OTTO site top-up without changing your base plan. When your available allowance is exhausted, adding another OTTO site is blocked until additional capacity becomes available. 🔍 Why Did I Receive a Charge Like $686? A larger top-up amount usually happens because one or more of the following occurred during your billing cycle: - Multiple sites were added at once. The charge is a combined total, not a price for a single site. - Additional OTTO site slots were purchased beyond your included allowance. Those purchased slots are billed as recurring top-ups, whether or not every slot is currently being used. - The initial top-up payment may be prorated when you purchase additional OTTO site capacity mid-cycle. It covers the remaining portion of the top-up’s monthly billing period; subsequent payments cover the recurring capacity. - A single top-up purchase can cover several additional OTTO site slots. Do not assume that separate purchases were combined because they happened close together; review the invoices and purchased quantities to identify what each charge covers. The amount depends on the additional capacity purchased, your applicable OTTO pricing tier or negotiated rate, any discounts, and any first-payment proration based on when the capacity was purchased. 🧮 How the Amount Is Typically Calculated While exact rates depend on your plan, a top-up generally follows this logic: 1. The platform checks OTTO site usage against your available allowance, including purchased capacity. Recurring top-up charges are based on the capacity you purchased, not an automatic count of sites exceeding your base plan. 2. Additional OTTO site capacity is priced using your applicable OTTO site-count tier or negotiated rate. Included and eligible complimentary sites can contribute toward the pricing tier without becoming paid top-up sites. 3. The total is adjusted for the days left in your current billing cycle, if applicable. 4. The final amount is charged to your payment method on file. 📋 How to Review What Your Charge Covers 1. Open your billing or subscription settings inside the platform. 2. Find the invoice or payment entry that matches the charge date and amount. 3. Check the line item description for references to OTTO or additional sites. 4. Compare the charge date with the dates you added or activated sites in your account. 5. Review your OTTO site list and available allowance to understand capacity usage. To verify the charge, check the purchased OTTO top-up quantity under Services and compare it with the invoice. Purchased capacity can remain billable even when some slots are unused. **Code references** - Quota gate: content-assistant/app/ca/api/v2/views/otto\_project.py:356–361. - Recurring purchase, quantity and proration: linkgraph/app/customer/api/payment/serializers.py:9330–9412. - Monthly billing and proration: linkgraph/app/core/billing/topup\_pricing.py:34–79,98–116. - Tier pricing: linkgraph/app/core/billing/otto\_tier\_pricing.py:15–26. - Billing tabs: customer-frontend/src/modules/billing/v1/components/billing/invoice-list/index.tsx:218–231. ✅ Tips to Avoid Unexpected Charges - Check how many OTTO sites your plan includes before activating OTTO on a new site. - Review your site list regularly and remove any sites you no longer manage. - Let your team know before they add new client sites, since each activation may affect your billing. - Keep your billing contact details current so you receive invoices and notifications. 🧾 What to Have Ready if You Need a Closer Look If the charge still doesn't make sense after reviewing your account, gather the following so the review goes faster: - The exact charge amount and date - The last four digits of the payment method used - The names of any sites you recently added or activated OTTO on - Whether anyone else on your team has access to add sites 💬 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 instantly connected with a member of our team. Share the details above and we can walk you through exactly what the charge covers on your account.

Last updated on Oct 29, 2026

🛠️ Fix OTTO Google Ads Optimize Campaign Error

🔍 What This Error Means If you purchased the OTTO Google Ads add-on and see the message 'Required playbook not available' when you click Optimize Campaigns, OTTO cannot find the set of instructions (the playbook) it needs to optimize your campaign. This usually happens because of a setup or access issue, not because anything is wrong with your campaigns. In most cases, the cause is one of the following: - The add-on has not finished activating on your account yet. - Your Google Ads account is not connected, or the connection has expired. - You are viewing a project or workspace that the add-on is not enabled for. - Your browser is showing an outdated version of the page. - The Google Ads account you connected does not have the right access level. ✅ Step 1: Confirm the Add-On Is Active First, make sure your purchase is applied to the account you are logged into. 1. Log in to the Search Atlas platform. 2. Open your account or billing settings. 3. Check that the OTTO Google Ads add-on is listed as active. 4. Confirm you are logged in with the same user account that made the purchase. If you just bought the add-on, allow some time for it to activate, then log out and back in before trying again. 🔗 Step 2: Check Your Google Ads Connection OTTO needs a working connection to your Google Ads account to optimize campaigns. 1. Go to the Google Ads section of OTTO in your project. 2. Check that your Google Ads account appears as connected. 3. If it is not connected, or you see a warning, disconnect and reconnect it. 4. When Google asks for permission, approve all of the requested access. Make sure the Google account you sign in with has Standard or Admin access to the Google Ads account you want to optimize. Read-only access may prevent OTTO from working. 📁 Step 3: Make Sure You Are in the Right Project Add-ons and connected accounts can be tied to a specific project. If you manage several projects or sites, check the following: - You have selected the project that has your Google Ads account connected. - The campaign you want to optimize belongs to the connected Google Ads account. - The campaign has finished loading in the platform. New or recently changed campaigns can take a little while to appear. 🔄 Step 4: Refresh Your Browser and Session Sometimes an outdated page can keep showing an error after the problem is already fixed. Try these quick steps: 1. Refresh the page with a hard refresh (Ctrl + Shift + R on Windows or Cmd + Shift + R on Mac). 2. Log out of Search Atlas and log back in. 3. Clear your browser cache and cookies for the Search Atlas site. 4. Try again in a different browser or a private (incognito) window. 🚀 Step 5: Try Optimizing Again After completing the steps above, go back to your campaign and click Optimize Campaigns again. If the playbook is available, OTTO will start analyzing your campaign and show its recommendations. 💡 Tips to Avoid This Issue - Connect your Google Ads account before trying to run optimizations. - Use the same login for purchasing the add-on and managing your projects. - Keep your Google Ads connection up to date. Reconnect it if you change your Google password or permissions. - Make sure you have the correct access level in Google Ads. ❓ Frequently Asked Questions I just purchased the add-on. Why is the button not working? Newly purchased add-ons may take a little time to activate. Log out, log back in, and check that the add-on shows as active in your account settings. Will I lose my campaign data if I reconnect Google Ads? No. Reconnecting only refreshes the permission between Search Atlas and Google Ads. Your campaigns stay in your Google Ads account. The error is still showing after all the steps. What should I do? The playbook may need to be enabled on your account by our team. Please contact support using the steps below, and include the project name and the Google Ads account you are trying to optimize so we can resolve it faster. 💬 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 instantly connected with a member of our team.

Last updated on Oct 29, 2026

📊 Understanding Your OTTO AI Suggestions Monthly Quota

📌 Overview If you are on a monthly plan, you may notice that your OTTO AI Suggestions quota shows 500. Some customers remember a higher number in the past and ask why it changed. This article explains what the quota is, why the number you see may differ from what you remember, and how to check your current allowance. 🤖 What Are OTTO AI Suggestions? OTTO AI Suggestions are AI-generated recommendations that help you improve your pages and content. Each time OTTO generates a suggestion for you, it counts toward your quota. The quota controls how many suggestions you can generate within your plan's usage period. 📅 How the Monthly Quota Works - Plan-based: Your quota depends on the plan you are subscribed to. - Usage-based: Every AI suggestion generated uses part of your allowance. - Per billing period: On a monthly plan, usage is tracked across your monthly billing period. - Separate from other credits: The OTTO AI Suggestions quota is tracked on its own and is not the same as other credits or limits in your account. 🔄 Why Your Quota May Look Different Than Before Several things can cause the number to differ from what you saw earlier: - Plan allowances can be updated. As Search Atlas adjusts plans, features, and usage limits, the quota included with a plan can change. - Plan type matters. Monthly, annual, and legacy plans may have different allowances. If your plan changed, your quota may have changed with it. - Different quota types. You may be comparing the AI Suggestions quota to another limit, such as a different credit type, which can have a different number. - Remaining vs. total. The number shown may be what you have left this period, not your total allowance. We cannot confirm the exact reason behind a change on an individual account from this article. A member of our team can review your account and explain what applies to you. 🔍 How to Check Your Current Quota 1. Log in to your Search Atlas account. 2. Open the OTTO section of the platform. 3. Look for the AI Suggestions usage or quota indicator to see how many suggestions you have used and how many remain. 4. Open your plan and billing settings to confirm which plan you are on and what it includes. Take note of both the quota number and your plan name. This makes it easier to compare against what you remember. 💡 Tips for Getting the Most From Your Quota - Prioritize key pages. Generate suggestions first for the pages that matter most to your traffic and goals. - Avoid repeat generations. Review a suggestion before regenerating it, since each generation uses quota. - Monitor usage mid-month. Checking your usage regularly helps you avoid running out before your period ends. - Review your plan. If you regularly reach your limit, compare your options in your plan settings to see whether another plan fits your needs better. ❓ Frequently Asked Questions Why does my quota say 500 when it used to be higher? Plan allowances can change over time, and the quota depends on your current plan. Check your plan and billing settings to confirm what your plan includes. Did I lose suggestions I had before? Usage is tracked per period, so what you see now reflects your current allowance and usage. If you believe your balance is incorrect, contact our team so they can review your account. Can I get a higher quota? Your quota is tied to your plan. Review the available plans in your account settings, or ask our team about options that fit your usage. Is the quota the same on every plan? No. Different plans can include different allowances. 🛠️ When to Contact Support Reach out if any of the following applies: - Your quota does not match what your plan says it includes. - Your usage count looks higher than expected. - Your quota changed without any change to your plan. - You want to discuss options for a higher limit. When you contact us, include your plan name, the quota number you see, and what you expected to see. This helps us resolve your question faster. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

Last updated on Oct 29, 2026

🔄 How OTTO SEO Recrawls and Reanalyzes Your Site

🔍 Overview OTTO SEO regularly re-scans your website to find new pages, detect content changes, and update its recommendations. If you have just made a lot of changes, such as new pages, rewritten content, a redesign, or a migration, you may want OTTO to pick them up right away instead of waiting for the next scheduled run. This article explains how OTTO's recrawl works, what to check if your changes are not showing up, and how to ask for a faster refresh. ❓ Can I Force an Immediate Recrawl? OTTO normally re-processes your site on its own schedule. For most projects, you do not need to do anything to start a recrawl. The timing of a re-run can vary depending on the size of your site, how many pages changed, and how busy the system is. If you need results sooner, for example after a large update, the best path is to ask our team to review your project and check whether an earlier reprocess can be started. The steps for contacting us are at the end of this article. Before you do, the checks below resolve many cases where changes seem to be ignored. ⏱️ Why Changes May Not Appear Yet If OTTO has not reflected your edits, one of these is usually the cause: - The next scheduled run has not happened yet. OTTO works from its last completed crawl until the next one finishes. - A crawl is still in progress. Larger sites take longer to process, and results may update only when the crawl completes. - Your changes are not live yet. OTTO can only see what is publicly available on your site. Drafts, staging pages, and unpublished edits will not be picked up. - Caching is serving older pages. Site, plugin, or CDN caches can show OTTO an outdated version of your page. - Pages are blocked from crawling. A robots.txt rule, a noindex tag, a login requirement, or a firewall can stop OTTO from reaching your pages. - OTTO is not installed correctly. If the OTTO script or connection is missing or broken, changes may not be detected or applied. ✅ Steps to Take Before Requesting a Recrawl Work through this checklist so your site is ready when the next crawl runs, or when our team starts one for you. 1. Publish your changes. Make sure every updated page is live and visible when you open it in a private or incognito browser window. 2. Clear your caches. Purge any caching plugin, server cache, and CDN so crawlers get the newest version of each page. 3. Check that pages are crawlable. Confirm your robots.txt file, noindex tags, password protection, and firewall or security settings are not blocking the pages you changed. 4. Confirm your sitemap is current. Make sure new and updated URLs are included in your XML sitemap and that it loads without errors. 5. Verify your OTTO installation. Open your OTTO project’s Overview page and confirm that the installation status shows Installed. If it shows Not Installed or Not Working, use Install or See why to investigate. Source: customer-frontend/src/modules/otto/shared/connection-status/ConnectionStatusCard.tsx:35–38,80–90. 6. Check the project status. Look for any crawl or processing indicator in your OTTO project. If a crawl is already running, allow it to finish before expecting updates. 🛠️ Preparing a Large Update If you are about to make many changes, a little planning helps OTTO process them smoothly: - Finish and publish the full batch of changes before asking for a refresh, so OTTO does not scan a half-finished site. - Avoid changing URLs unnecessarily. If you must change them, set up proper redirects. - Keep a short list of the key pages you changed so you can verify them after the recrawl. - Note the date and time you finished your changes. This helps our team understand what OTTO should be picking up. 📊 How to Confirm the Recrawl Worked After the next crawl completes, check these items in your OTTO project: - New pages appear in your page list. - Updated content is reflected in the recommendations and analysis for those pages. - Recommendations you have already addressed no longer appear as open issues. - Any status or last-updated information for your project shows a recent date. If some pages update and others do not, make a note of the specific URLs. This makes it much faster to find the cause. 💬 Need a Faster Refresh? Contact Our Team If you have worked through the checklist and OTTO still has not reprocessed your site, or you need an urgent refresh after major changes, our team can look into your project directly. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team. To help us resolve your request quickly, include the following in your message: - The domain or project name. - A short description of what you changed and when. - Example URLs that are not showing the updates. - Any steps from the checklist above that you have already completed. 💡 Quick Tips - Make changes in batches rather than a little at a time, so each crawl captures more. - Always clear caches after publishing important updates. - Keep your sitemap and OTTO installation healthy so crawls run without interruption. - Be patient with large sites, as a full reanalysis can take longer than a small one.

Last updated on Oct 29, 2026

🔄 Make OTTO Changes Permanent with Sync to CMS

❓ The Short Answer If you want OTTO's optimizations stored in your site, use OTTO Persistence. It copies the change types you turn on into your CMS so they can remain after you stop using OTTO. It is off until you enable it, and it applies to change types, not to individual pages. 🧩 How OTTO Applies Changes by Default By default, OTTO applies optimizations through a lightweight script on your site. When a page loads, the script adds the improvements, such as updated titles, meta descriptions, headings, or schema. This makes changes fast to deploy and easy to adjust, and you don't need to edit your CMS by hand. The trade-off is that these changes depend on OTTO being active. If you remove OTTO or its script, changes that were not synced to your CMS will no longer appear on your pages. 💾 What Sync to CMS Does OTTO Persistence copies the change types you enable into your site's own fields and SEO-plugin settings. After a successful sync: - The enabled changes are stored in your site's SEO fields, alongside the values those plugins already keep. - They appear in your site's source code without relying on the OTTO script. - They stay in place if you pause or disable OTTO. If you uninstall the plugin, they remain only when Delete data on uninstall is off. ✅ Before You Sync - Connect your CMS. Your site must be connected to Search Atlas with permission to edit content. - Review the change types. Persistence saves the values OTTO is currently deploying for each type you enable, so enable only what you want to keep. - Back up your site. A backup or restore point lets you undo changes if needed. - Check supported changes. Which change types can be synced may vary by CMS and by page. The Sync to CMS option in your project shows what is available for your site. 🛠️ How to Sync Changes to Your CMS 1. Open the site's OTTO project in Search Atlas, or the MetaSync settings in WordPress. 2. Review the optimizations applied to your pages and make sure they are what you want on your site. 3. Enable OTTO Persistence for each change type you want to keep. 4. Choose the change types to write to your CMS. The sync applies each enabled type across the site, not to selected pages. 5. Confirm the sync and wait for it to finish. The layout differs by CMS, but the flow is the same: review the change types, enable OTTO Persistence for the ones you want, and save. 🔍 How to Confirm the Changes Are Permanent 1. Open a synced page on your live site. 2. View the page source (right-click and choose View Page Source) or check the page in your CMS editor. 3. Look for the updated title, meta description, headings, or other elements you synced. 4. If the content is there and your CMS shows it as part of the page, the change is saved on your site. Your site may use caching. If you don't see the update right away, clear your site cache and check again. ⚠️ Important Things to Know - Sync before you stop using OTTO. Don't remove OTTO or cancel until you have confirmed your changes are saved in your CMS. - New changes need a new sync. Optimizations OTTO makes after your sync are not saved to your CMS until you sync again. - Some changes may not be supported. If a particular change type can't be synced for your CMS, it will keep depending on OTTO. Ask our team if you're unsure about a specific item. - Manual edits can overlap. If you or a plugin edit the same fields later, the newest edit may overwrite the earlier one. 🧯 Troubleshooting - Sync option is unavailable: Check that your CMS is connected and that the connection has permission to edit content. - Changes don't show after syncing: Clear your site and browser cache, then check the page source again. - Some changes are missing: The change type may not be supported for your CMS, or it may not have been selected during the sync. Try syncing again and check the selection. - Your SEO plugin shows different values: Another plugin or theme setting may be overriding the synced content. Check those settings for the same page. 💬 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 instantly connected with a member of our team.

Last updated on Oct 29, 2026

🔍 Finding and Disabling OTTO FAQ Modules

❓ Does OTTO Add Hidden Keywords to My Website? This is one of the most common questions we hear. OTTO is built to follow search engine guidelines, and it is not designed to hide keyword text from your visitors. Hidden or invisible keyword text is a practice search engines penalize, and it is not part of how OTTO improves your site. What OTTO can add are optimizations that help search engines understand your pages. Some of these are not obvious when you look at the page, which can make them seem hidden. The most common are: - FAQ content: question-and-answer sections added to a page. - FAQ schema (structured data): code in the page that describes your FAQs to search engines. It is not displayed as visible text. - Optimized page elements: updated titles, meta descriptions, headings, image alt text, and similar items. If you saw FAQ or keyword-related code in your page source, it is most likely one of these items. 🧭 Where These Modules Come From OTTO applies changes to your site through its deployment connection, so you will not see them as edits inside your website editor (WordPress, Shopify, Wix, and so on). That is why you may not find them in your site's back end. They are managed from your Search Atlas account instead. 🔎 How to Find the FAQ Module in Search Atlas Menu labels may vary slightly depending on your platform version, but the general path is: 1. Log in to your Search Atlas account. 2. Open OTTO SEO and select the website (project) you want to review. 3. Open the list of optimizations or deployed changes for the site. 4. Find the page where you saw the FAQ section. You can search by page URL or filter by optimization type. 5. Look for items labeled FAQ, schema, or structured data. 6. Open the item to see exactly what OTTO added, including the questions and answers. 🛑 How to Disable or Remove the FAQ Module 1. Follow the steps above to open the FAQ item for the page. 2. Choose the option to turn off, undo, or revert the change. If you only want to change the wording, edit the content instead. 3. Confirm the action and save. 4. Repeat for any other pages where you want the FAQ removed. If you want to stop all OTTO changes on a specific page, look for the option to pause or exclude that page from optimization. ⏱️ Confirm the Change Is Live After you disable a module, it may take a short time before your site shows the update. To make sure you are seeing the latest version: - Clear your website cache, including any caching plugin or CDN you use. - Reload the page in a private or incognito browser window. - Wait a few minutes and check again if the old content still appears. 🧪 How to Check Your Page Source Yourself If you want to see exactly what is on a page, you can inspect it: 1. Open the page in your browser. 2. Right-click and choose View page source. 3. Press Ctrl+F (Cmd+F on Mac) and search for FAQPage or a question from the FAQ. 4. If it appears inside a block of structured data, it is FAQ schema rather than hidden keyword text. You can also paste your page URL into Google's free Rich Results Test to see which structured data is detected. 💡 Helpful Tips - FAQ schema helps search engines understand your content and can support richer search results, so consider editing it rather than removing it if the answers are accurate. - Review FAQ answers to be sure they match your business and services. - Keep a note of the pages you changed so you can compare performance later. 💬 Need More Help? If you cannot find the module, or you see content on your site that you do not recognize, we are happy to take a closer look with you. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

Last updated on Oct 29, 2026

💡 Understanding OTTO Overage Charges and HDC Credits

Seeing an unexpected invoice can be confusing, especially if you believe your plan includes more OTTO projects than you were billed for. This article explains why an OTTO overage invoice can appear, how to check your plan allowance, and what happens when a disputed charge is refunded as an HDC credit. ❓ Why Did I Receive an Invoice? An OTTO overage invoice is generated when the number of OTTO projects active on your account is higher than the number your plan includes. Each plan has an OTTO allowance, and any projects above it may be billed as extra. Common reasons for an overage invoice include: - You added a new OTTO project after reaching your plan limit. - A project you thought was removed or paused was still active when the billing cycle closed. - Your plan changed (for example, from monthly to yearly) and the allowance on your account did not update as expected. - A project was added by a team member with access to your account. 📦 Why Your Plan Allowance May Look Different Some customers expect a different number of OTTO projects than the one shown on their account. For example, a yearly subscription may include 5 OTTO projects while your account shows 4. This can happen when: - You switched to a yearly plan, and the new allowance has not been applied to your account yet. - The invoice was created before the plan change was fully processed. - You are looking at a previous plan's limit instead of your current one. If the allowance on your account does not match what you purchased, that is a billing discrepancy and we can review it for you. 🔍 How to Check Your Plan and Invoice 1. Open your account and go to the Billing or Subscription section. 2. Check your current plan and billing period (monthly or yearly). 3. Note the number of OTTO projects your plan includes. 4. Open the invoice in question and read the line items. An overage charge is listed separately from your regular subscription fee. 5. Compare the number of active OTTO projects on your account with your plan allowance. Write down any differences. This will help us resolve your question much faster. 🛠️ What to Do If You Think the Charge Is Wrong If your invoice does not match what you purchased, follow these steps: 1. Review the invoice date. Check whether it was issued before or after your plan change or yearly purchase. 2. Confirm your active projects. Make sure each OTTO project on your account is one you intend to keep. 3. Gather details. Have your plan name, billing period, invoice number, and the number of OTTO projects you expected ready to share. 4. Contact our team through chat. Our team can review your subscription, confirm the correct allowance, and correct the invoice if needed. 💳 How Refunds Issued as HDC Credit Work When a disputed OTTO overage charge is found to be incorrect, the amount may be returned to you as an HDC credit instead of a refund to your original payment method. Here is what that means: - The credit is applied to your Search Atlas account. - It can be used toward future charges, so you do not need to take action to apply it. - It is not sent back to your card or bank account as a separate payment. After a credit is issued, we recommend that you: 1. Check your Billing section to confirm the credit appears. 2. Verify that your plan allowance now shows the correct number of OTTO projects. 3. Review your next invoice to confirm the credit has been applied correctly. If you would prefer a different refund method, or the credit does not appear on your account, let our team know so they can review your options. ✅ How to Avoid Unexpected OTTO Overage Charges - Check your plan allowance whenever you upgrade, downgrade, or switch billing periods. - Review your active OTTO projects before each billing cycle ends. - Remove or pause projects you no longer need. - Check with your team members before anyone adds new projects. - Open your invoices when they are issued and review the line items. 💬 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 instantly connected with a member of our team. To help us resolve your request quickly, please include your invoice number, your plan type, and the number of OTTO projects you expected to have.

Last updated on Oct 29, 2026

🛠️ OTTO on Wix and Website Studio Designs

🔍 Overview This article covers two common questions: how to connect OTTO to a website built on Wix, and whether a design made in an outside AI tool (such as Claude) can be sent to Website Studio to be built and hosted. 📌 Before You Start - You need admin access to your Wix account and site. - Wix only allows custom code on sites with a Premium plan and a connected custom domain. Free Wix sites cannot run the OTTO pixel. - Have your OTTO pixel code ready from your Search Atlas project. It is a short snippet that starts with a script tag. 📋 Step 1: Copy Your OTTO Pixel 1. Log in to Search Atlas and open the project for your Wix website. 2. Go to OTTO SEO and open the installation or setup area. 3. Choose the pixel installation option and copy the full code snippet. Copy all of it, including the opening and closing tags. ⚙️ Step 2: Add the Pixel to Wix 1. Log in to Wix and open your site dashboard. 2. Go to Settings, then find Custom Code (in some accounts it is under Advanced). 3. Click Add Custom Code and paste your OTTO pixel into the code box. 4. Name it something easy to recognize, such as "OTTO Pixel". 5. Under Add Code to Pages, choose All pages. 6. Under Place Code in, choose Head. 7. Click Apply, then Publish your Wix site so the change goes live. Menu names in Wix can change over time. If you cannot find Custom Code, search for it in the Wix dashboard search bar. ✅ Step 3: Confirm the Pixel Is Working 1. Return to your OTTO project in Search Atlas. 2. Check the pixel status or run the verification option, if one is shown. 3. If it does not show as connected right away, wait a few minutes and refresh. Then clear your browser cache or test in a private window. 🧰 Troubleshooting the Wix Install - Custom Code option is missing or locked: Check that your site has a Premium plan and a connected domain. - Pixel not detected: Make sure you clicked Publish after applying the code. Wix does not push code changes live until you do. - Code placed in the wrong spot: The pixel should be in the Head and set to load on All pages. - Incomplete code: If part of the snippet was cut off when copying, paste it again from OTTO. - Wrong project or domain: Confirm the pixel you copied belongs to the same website you are installing it on. - Browser extensions: Ad blockers and privacy tools can hide the pixel during testing. Try a private window with extensions off. 🎨 Using a Claude Design with Website Studio Many customers create a layout or concept in an outside AI tool like Claude and want to reuse it in Website Studio. Here is what to expect. - Direct import: We cannot confirm a one-click way to send a design from an outside tool into Website Studio to be built and hosted. Do not rely on one until our team confirms it for your account. - Website Studio builds from your input: It creates pages from the business details, content, and instructions you provide in the platform. 💡 Recommended Way to Reuse Your Design Ideas 1. Save your design as a screenshot or PDF so you have a clear visual reference. 2. Write down the page structure: for example, hero section, services, testimonials, FAQ, and contact form. 3. Copy the text, headlines, and calls to action from your design. 4. Gather your logo, brand colors, fonts, and images. 5. Enter these details in Website Studio and describe the layout and style you want, then review and adjust the result. This gets you close to your original design while keeping your site hosted and managed in Search Atlas. 🔗 Using Both Together If your site is hosted in Website Studio, you do not need to follow the Wix steps above. The Wix steps apply only to sites that stay on Wix. If you plan to move from Wix to Website Studio, tell our team first so they can advise you on the order of steps and on your domain and OTTO setup. 🙋 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 instantly connected with a member of our team. To help us resolve your request faster, include your website address, a note on whether you are on Wix or Website Studio, and a screenshot of any error you see.

Last updated on Oct 29, 2026

🔍 Fixing Missing GSC Domain Property Data

🔎 Overview Some customers connect Google Search Console (GSC) to Search Atlas and then can't find their property in the list. Others find it, but no data appears. This is common with domain properties, which look like sc-domain:yourwebsite.com. This article explains why it happens and how to fix it. 🌐 What Is a Domain Property? In Google Search Console, there are two kinds of properties: - Domain property: Covers every version of your site, including all subdomains and both http and https. It appears as sc-domain:yourwebsite.com. - URL-prefix property: Covers only one exact address, such as https://www.yourwebsite.com/. If you see sc-domain: followed by your domain name, that is the same site as your domain property in GSC. It is the correct property to use for tracking your whole website. ❓ Why Your Property May Not Appear or Show Data These are the most common causes: - The wrong Google account is connected. Search Atlas can only see properties that the connected Google account can access. - Permissions may be limited. Search Atlas lists every verified Search Console property the connected account can access, including Owner, Full, and Restricted access. An unverified property is not listed. Restricted users can still share the performance data their permission allows. Owner access is required only for actions that specifically check ownership. - Search Console permission was not granted. Search Atlas requests read-only Search Console access as part of the Google sign-in. If that permission is denied, or does not appear in the granted scopes, no properties load. There is no separate Search Console checkbox to leave unchecked. - The connection has expired. Google sign-ins can expire or be revoked, especially after a password change or security update. - The property is new. GSC can take a few days to begin collecting data for a newly added or newly verified property. - The date range has no data. If the site had little or no search traffic during the selected period, reports may look empty. - The property is not linked to the right project. Search Atlas matches the project domain to a verified Search Console property for that hostname, including a domain property, a www or non-www version, or a parent or subdomain. Choose that match and finish linking it to the project. Connecting the Google account alone does not attach the property. ✅ Step 1: Confirm the Property in Google Search Console Start by checking that the property is healthy in Google itself. 1. Go to Google Search Console and sign in with the Google account you plan to use in Search Atlas. 2. Open the property selector in the top-left corner. 3. Look for your domain property, for example sc-domain:yourwebsite.com. 4. Open the property and check the Performance report. Set the date range to the last 28 days. If the property is missing here, the account you are signed in with does not have access. Try another Google account that manages the site. If the Performance report is empty in GSC, Search Atlas will not have data to show either. 🔐 Step 2: Check Your Permission Level 1. In GSC, select your domain property. 2. Go to Settings, then Users and permissions. 3. Find the Google account you connected to Search Atlas. 4. Make sure its permission is Owner or Full. If the account is not listed or has restricted access, ask a property Owner to upgrade it. You can also connect Search Atlas using the Google account that owns the property. 🔄 Step 3: Reconnect Google Search Console in Search Atlas Reconnecting refreshes the connection and reloads your list of properties. 1. In Search Atlas, open the Google Search Console connection settings for your project or account. 2. Disconnect the current Google account if one is connected. 3. Select the option to connect Google Search Console again. 4. Choose the Google account that has Owner or Full access to your domain property. 5. When Google asks for permissions, approve all requested access, including Search Console data. 6. Return to Search Atlas and select your domain property from the list. If you manage several Google accounts, double-check which one you picked in the Google sign-in window. Choosing the wrong one is the most common reason a property doesn't appear. 🧩 Step 4: Make Sure the Domain Matches Your Project Check that the domain in your Search Atlas project matches your GSC property. For example, a project for yourwebsite.com should use sc-domain:yourwebsite.com or a URL-prefix property for the same site. If your project uses a different domain, subdomain, or spelling, the data may not line up. If you track a specific subdomain, such as blog.yourwebsite.com, the domain property still works because it includes all subdomains. You may only need to filter your reports. ⏳ Step 5: Allow Time for Data to Load Even when everything is connected correctly, data may not appear right away. Keep these timing points in mind: - Google typically reports Search Console data with a delay of 2 to 3 days. - A newly verified property may take several days to show its first data. - After reconnecting, Search Atlas may need some time to sync your historical data. - Google only provides about 16 months of past data, so older ranges will be empty. If your property was added to GSC very recently, check back after a few days. 💡 Tips to Avoid This Issue - Connect with the Google account that owns the property, not a restricted user. - Always approve all permission requests during the Google sign-in step. - Keep your DNS verification record in place. Removing it can cause GSC to lose verification of a domain property. - Reconnect GSC after major Google account changes, such as a password reset. - Use consistent domain names across your projects and GSC. 🛠️ Still Not Working? If you've followed the steps above and your domain property still doesn't appear or show data, our team can look into it. Have these details ready: - The exact property name, for example sc-domain:yourwebsite.com - The Google account email you used to connect - Whether the property shows data when you open it directly in GSC If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

Last updated on Oct 29, 2026

🛠️ Fix Names and Truncated Alt Text in OTTO

🔍 Overview OTTO SEO builds its suggestions from the content already on your website. Some customers notice two things: their personal name appears in suggested titles, descriptions, or alt text, and some alt text suggestions look cut off. This article explains why both happen and what you can do about them. 🧐 Why Your Name Appears in OTTO Suggestions OTTO reads the text and headings on your pages, plus the business name and author name saved in the project's Knowledge Graph, so a name can show up in a suggestion when it appears in one of these places: - The author name saved in the project's Knowledge Graph, or a name written in the page text that OTTO crawled. - Your business or brand name, especially if it includes your own name (for example, a personal brand or a practice named after you). - Any crawled page whose text mentions you prominently, including About, Contact, and team pages. - Existing titles and descriptions that already include your name. - Text near the image on the page, or the page summary, when it contains your name. In many cases this is intended. Including a brand name in a page title is a common SEO practice. If you would rather not have your name appear, you can control it. ✅ How to Keep Names Out of Suggestions 1. Review before you approve. Check each suggestion and edit the text to remove your name before accepting or publishing it. 2. Check the source. If your name keeps coming back, look at the page it came from. Bylines, image captions, and file names are common sources. 3. If you change the wording on your page, such as swapping a personal byline for your company name, recrawl the site and regenerate the suggestions. Also update the author name in the project's Knowledge Graph if it is saved there. 4. Rename images. If a file name contains your name, upload a version with a descriptive name that describes the image instead. 5. Add your own instruction in OTTO Settings under Additional AI instructions, for example "Never use the name [REDACTED]." It applies to future suggestions, up to 1,000 characters, and it guides the wording rather than guaranteeing the name is removed. Check each new suggestion before you approve it. ✂️ Why Alt Text Can Look Truncated Alt text describes an image for screen readers and search engines. Good alt text is short and to the point, usually around 125 characters or fewer. Suggestions can look cut off for a few reasons: - Length limits. Long descriptions may be shortened to keep alt text concise. - Long generated descriptions are shortened to about 15 words, or about 5 words for a logo. - The stored suggestion is already the shortened text. A long value may be clipped by the width of the list, but opening it shows the full stored text. 🛠️ How to Fix Truncated Alt Text 1. Open the suggestion and read the full stored text. If it ends abruptly, the description was shortened when it was created, so edit it into a complete phrase before you approve it. 2. Rewrite it manually. Describe what is in the image in one clear sentence, ending with a complete thought. 3. Put the key detail first. If any part is trimmed, the most important words will still be there. 4. Skip filler. Avoid phrases like "image of" or "picture of," and do not stuff in keywords. 5. Check your result. After you save, confirm the full alt text appears on the page. 💡 Best Practices - Use your brand name where it helps people recognize your business, and keep personal names out of alt text unless the image shows that person. - Keep alt text specific, for example "Plumber repairing a kitchen sink," rather than generic. - Review suggestions in batches so you can spot repeated patterns, such as a name appearing across many pages. - Give images descriptive file names before uploading. 💬 Still Need Help? If your name keeps appearing in suggestions, or alt text still looks cut off after you have tried the steps above, we can help. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team. To help us resolve it faster, tell us the page URL, the suggestion text, and the name you want excluded.

Last updated on Oct 29, 2026

🛠️ Fix Deployed Meta Tags Not Showing Live

Your OTTO SEO dashboard may show a change as Deployed while your live website still shows the old title, description, or other meta tags. Caching is one possible cause, but installation or delivery problems can also prevent updates from appearing. This guide explains how to check the live page and troubleshoot the mismatch. 🔎 What 'Deployed' Means A Deployed status means the change is approved for deployment while OTTO is installed and the project is active. It does not by itself confirm that the updated tag is present on the live page or visible to every visitor or search engine. Caching or installation and delivery problems can prevent the update from appearing. 🧩 Common Causes - Browser cache: your browser is showing a saved copy of the page. - Website caching plugin: tools such as WP Rocket, W3 Total Cache, LiteSpeed Cache, or similar plugins store static copies of pages. - Server or host cache: many hosts add their own page cache on top of your CMS. - CDN cache: services such as Cloudflare, Fastly, or Akamai may serve an older copy from their network. - Conflicting SEO plugin or theme: another plugin or theme setting may be writing its own title or description and overriding the new one. - Wrong URL or version of the site: the change may have been checked on a different version of the page, such as www vs. non-www, http vs. https, or a staging copy. - Search engine delay: the page is correct, but Google has not yet recrawled it, so search results still show the old text. ✅ Step 1: Check the Live Page Source Do not rely on how the page looks in search results. Check the page code directly. 1. Open the affected page in a private or incognito browser window. 2. Right-click the page and choose View Page Source. 3. Press Ctrl+F (Cmd+F on Mac) and search for <title or meta name=description. 4. Compare the title and meta tag values on the live page with the values you deployed in Search Atlas. Use your browser’s developer tools to inspect the rendered page after OTTO has loaded; View Page Source alone may not show JavaScript-applied changes. If the new values appear in the source, the deployment is live. Any remaining issue is with search engine results, which are covered in Step 5. If the old values appear, continue to Step 2. 🧹 Step 2: Clear Your Browser Cache 1. Do a hard refresh: Ctrl+Shift+R on Windows or Cmd+Shift+R on Mac. 2. If the old tags still appear, clear your browser cache fully, or test in a different browser or device. ⚙️ Step 3: Purge Your Website Caches If the page source still shows old tags, purge each caching layer your site uses. Work from the inside out, and check the page after each step. 1. CMS or caching plugin: open your caching plugin settings and choose the option to clear or purge all cache. If possible, purge just the affected URLs. 2. Hosting cache: many hosts have a cache clearing option in their control panel. Clear it there as well. 3. CDN cache: log in to your CDN and purge the affected URLs. Purging everything also works, but it may briefly slow your site while the cache rebuilds. 4. Re-check the page source in a private window after each purge. Tip: For agencies managing many client sites, repeat these steps on each client's site. Each one may use a different plugin, host, or CDN. 🔁 Step 4: Look for Conflicts and Overrides If the old tags remain after purging, something may be overriding the new ones. - Check whether another SEO plugin (for example Yoast, Rank Math, or All in One SEO) is active and set to output its own title and description. - Check your theme or page builder for built-in SEO fields that may take priority. - Search the page source for duplicate title or description tags. If you see more than one, a second source is adding tags. - Confirm you are checking the correct domain version and not a staging or development copy. - Confirm the page is not password protected, redirected, or blocked in a way that serves a different page to visitors. If you find a conflict, disable the extra source of tags or adjust its settings, then purge your caches again. 🌐 Step 5: Allow Time for Search Engines If the page source shows the correct tags but Google still shows the old text, the page just needs to be recrawled. Search engines also sometimes rewrite titles and descriptions in results based on the search query, even when your tags are correct. - Use the URL Inspection tool in Google Search Console and request indexing for the updated page. - Allow several days to a few weeks for search results to update. - Avoid making repeated changes to the same page while you wait. This can slow down the process. 📋 Quick Checklist - Open the page in a private window and view the source. - Confirm you are testing the correct live URL. - Purge your caching plugin, host cache, and CDN. - Check for another SEO plugin or theme setting overriding your tags. - Request a recrawl in Google Search Console. 💬 When to Contact Support If the page source still shows old tags after you have purged all caches and ruled out conflicts, our team can investigate further. To speed things up, have these details ready: - The project or website name in Search Atlas - Two or three example URLs where the changes are not showing - What the page source currently shows compared to what you deployed - The caching plugin, host, and CDN your site uses - The steps you have already tried If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

Last updated on Oct 29, 2026

🛠️ Deep Freeze Sites and Your OTTO Quota

🔍 Overview You paid to add another OTTO site to your plan, but the platform still asks you to upgrade. In many cases the new slot is not missing. It is already being used by a site you did not expect, such as a site in Deep Freeze. This article explains why that happens and how to check it. ❄️ What Is Deep Freeze and Why Does It Matter for Quota? A site in Deep Freeze is one you have set aside or paused in OTTO. It is not being actively optimized, but it can still be attached to your account. Sites that remain attached to your account may still count toward your OTTO site limit, even if you are not working on them. That means your available slots can look full even though you only use a few sites. When you buy an extra site, it can be taken by a Deep Freeze site, so you still see the upgrade prompt when you try to add a new one. 🧮 Why You May Still See an Upgrade Prompt After Purchase These are the most common reasons: - Deep Freeze sites are using your slots. The added slot fills a spot already used by a frozen site. - The page has not refreshed. Your browser may still show your old plan details. - The purchase is still processing. Payments can take a short time to appear on your account. - Confirm that you purchased the additional OTTO capacity for the same customer account you are currently using. An individual OTTO project does not have its own separate site-capacity add-on. Evidence: content-assistant/app/ca/models/otto\_project.py:293–298. - The add-on type does not match. Check that you bought an additional OTTO site and not a different add-on. ✅ Step-by-Step: Check Your OTTO Site Count 1. Refresh the page, or log out and log back in, so your latest plan details load. 2. Open your OTTO section and review the full list of sites connected to your account. 3. Look for any sites marked as Deep Freeze or that you no longer need. 4. Open Billing and review Active Services for the purchased add-on. Confirm that you are viewing the customer account used for the purchase, then check its OTTO Sites allowance and usage. Evidence: customer-frontend/src/modules/billing/v1/components/billing/invoice-list/components/active-services/index.tsx:200–245; customer-frontend/src/modules/billing/v1/components/billing/otto-section/index.tsx:69–78. 5. Compare your total OTTO Sites allowance, including purchased capacity, with your reported usage. Count active projects and frozen projects whose quota has not yet been returned; exclude frozen projects whose slots have already been released. Evidence: content-assistant/app/ca/models/otto\_project.py:293–298. 6. Try adding your new site again. 🔧 How to Free Up a Slot If frozen sites are taking up your quota, you have a few options: - Remove sites you no longer need. Removing a site you will not use again can free up its slot. - You can keep your Deep Freeze sites without them permanently occupying OTTO slots. Their slots are held for 14 days and then returned through the scheduled release process. Purchase additional capacity only if you need more available slots before release or for additional active projects. Evidence: content-assistant/app/ca/tasks/otto.py:2981–3014. - Before deleting an OTTO project, confirm that you no longer need to access it in your project list. Deletion removes the project from normal access; use Deep Freeze instead if you want to preserve it as a frozen project. Evidence: content-assistant/app/ca/models/otto\_project.py:2937–2975. - Review your site list regularly and remove sites you no longer need. - Before buying an add-on, count all connected sites, including Deep Freeze sites. - After purchasing, refresh the platform before adding your new site. - Keep track of which login and workspace your plan is on. ⏱️ Is There a Delay After Purchase? After purchasing additional OTTO capacity, refresh and check both the billing service and your OTTO Sites allowance and usage. If the allowance has not increased, or you still cannot add a project despite having available capacity, contact support with your receipt and account details. An active add-on and an upgrade prompt alone do not establish the cause. 💡 Tips to Avoid This in the Future 💬 Still Seeing the Upgrade Prompt? If you have refreshed, checked your site list, and confirmed your add-on is active but still cannot add your site, our team can review your account directly. Have the name of the site you are trying to add and the approximate time of your purchase ready. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

Last updated on Oct 29, 2026

🔑 Create a Cloudflare API Token for OTTO

🔍 Overview To connect your website to OTTO through Cloudflare, create a Cloudflare user API token and provide it to Search Atlas. The token authorizes OTTO to configure the Cloudflare integration. Invalid tokens or insufficient permissions can cause connection errors. [Guide:641–655] The provided Cloudflare API token is invalid or has insufficient permissions. Please check your token and ensure it has Workers and Zones permissions. This guide shows you how to create a token with the right permissions and how to fix the error if it appears. ✅ Before You Start - You need a Cloudflare account that manages the DNS for your website. - Your domain must already be added to Cloudflare and show as Active. - Sign in as a Cloudflare user with access to your website’s account and zone and sufficient permissions to authorize the OTTO integration. [Cloudflare docs] - You need an API Token, not the Global API Key. These are different things, and the Global API Key will not work for this connection. 🛠️ Step-by-Step: Create the API Token 1. Log in to your Cloudflare dashboard. 2. Open https://dash.cloudflare.com/profile/api-tokens while signed in to Cloudflare. Use the user API Tokens page, not Account API Tokens. [Guide:650–655] 3. In the left menu, click API Tokens. 4. Click Create Token. 5. Click Create Token and select the Edit Cloudflare Workers template. Then add Zone → DNS → Edit. Do not switch to Account API Tokens. [Guide:650–674] 6. In Token name, enter something easy to recognize, such as Search Atlas OTTO. 7. Under Permissions, retain the Workers Scripts, Workers Routes, and Workers KV Storage permissions supplied by the Edit Cloudflare Workers template, and add Zone → DNS → Edit. [Guide:660–674] 8. Zone - Workers Routes - Edit 9. Zone - Zone - Read 10. Under Account Resources, choose Include and select the Cloudflare account that holds your website. 11. Under Zone Resources, choose Include and then either All zones from an account or Specific zone and pick your domain. 12. Leave Client IP Address Filtering empty. Restricting by IP can block the connection. 13. For TTL, leave the dates blank so the token does not expire, or choose a far-future end date. 14. Click Continue to summary, review the permissions, and click Create Token. 15. Copy the token right away. Cloudflare shows it only once. Note: If the OTTO connection screen lists any additional permissions, add those too. The list shown in the platform always takes priority. 🔗 Add the Token to OTTO 1. Open your project in Search Atlas and go to the OTTO setup or Cloudflare connection screen. 2. Paste the token into the API token field. 3. Check that there are no extra spaces before or after the token. 4. Click the button to connect or verify. ⚠️ Why You See the Invalid Token Error This error almost always comes from one of these causes: - Missing Workers permission. The token does not include Workers Scripts (Account) or Workers Routes (Zone) with Edit access. - Missing Zone permission. The token cannot read your zone because Zone - Zone - Read is not added. - Wrong resource scope. The token is limited to a different account or a different domain than the one you are connecting. - Read instead of Edit. Permissions set to Read where Edit is needed. - Global API Key used by mistake. The Global API Key is not the same as an API Token. - Copy and paste problems. The token was cut off or has a space at the start or end. - Expired or deleted token. The token passed its end date or was rolled or deleted in Cloudflare. - IP restrictions. The token only works from specific IP addresses. 🧰 Troubleshooting Checklist 1. In Cloudflare, go to My Profile and then API Tokens, and find your token. 2. Click Edit and compare the permissions with the list in this article. 3. Confirm the status is Active and that it has not expired. 4. Check that Account Resources and Zone Resources include the right account and domain. 5. Remove any IP address filtering. 6. Save your changes. If you are unsure, use Roll to generate a new secret, or create a fresh token with the steps above. 7. Copy the token again carefully and paste it into OTTO. 8. Try the connection again. 💡 Tips for a Smooth Connection - Create a dedicated token for OTTO instead of reusing one from another tool. - Do not delete or roll the token after connecting, or OTTO will lose access. - If you manage several domains, use All zones from an account so you do not need a new token for each site. - Store the token somewhere safe, and never share it publicly. 💬 Need More Help? If you still see the error after checking the steps above, we are happy to take a look. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

Last updated on Oct 29, 2026

🔍 Clearing OTTO Trust Questions After Answering

You added the recommended questions to your page, answered them, and ran a new scan. The same questions still appear in OTTO's Knowledge-Based Trust recommendations. This article explains why that can happen and what to do about it. ❓ Should Answered Questions Disappear? No. Putting the question and its answer on the live page does not clear the recommendation, even if both are published before the scan starts. OTTO builds the Knowledge-Based Trust list from the page's target keywords, and a scan does not check the page for those questions. The questions stay listed until you answer and approve them inside OTTO, or ignore or delete the recommendation. 🔎 Common Reasons Questions Still Appear - Whether your edits are published does not decide this. The scan reads the published page, but it does not look for the recommended questions in the page content, so publishing the answers does not remove them from Knowledge-Based Trust. - Caching is not the cause. A caching plugin, hosting cache, or CDN can make the scan read an older copy of the page, but the scan does not compare the page content with the recommended questions, so clearing the cache will not remove them. - Matching the recommended wording does not matter. OTTO does not read the questions on your page, so writing the question exactly as recommended, or phrasing it differently, does not change whether it stays in the list. - Placement does not decide this. Putting the answer directly under the question, under its own heading, or in a marked paragraph does not make OTTO drop the recommendation, because the list is not built by reading the page. - Hidden or script-loaded content is not the cause. Questions inside tabs, accordions, pop-ups, or content loaded by scripts are not checked against the Knowledge-Based Trust list, and making them visible in the page HTML will not clear the recommendations. - Finishing a new scan does not clear them. The recommendations list is not rebuilt from the scanned page, so questions you answered on the site stay listed after the scan completes. - Using the exact scanned URL does not fix this. OTTO does not remove a recommended question when it finds that question and answer on the scanned page, so editing the exact URL, a similar page, a staging copy, or a URL with different parameters all leave the recommendation in place. 🛠️ How to Fix It Step by Step 1. Check the live page. Open the exact URL in a private or incognito browser window and confirm that both the question and its answer are visible without clicking anything. 2. Compare the wording. Place the recommended question next to the one on your page. Match it as closely as makes sense for your content, keeping the meaning the same. 3. Place the answer right under the question. Use a heading for the question and a short paragraph beneath it. Aim for a clear, direct answer in the first sentence or two. 4. Make the content visible in the page text. If the question is in a tab, accordion, or pop-up, test moving it into the main body of the page. 5. Clear your caches. Purge any caching plugin, hosting cache, or CDN so the updated page is served to the scan. 6. Run a new scan. Wait until the changes are live and the cache is cleared before starting it. Then allow the scan to finish completely. 7. After the scan, review the list in OTTO rather than on the page. Questions that appear on the page are still recommended. Open each question in Knowledge-Based Trust, add or confirm its answer, and approve it, or ignore or delete the ones you do not want. Wording and placement on the live page do not decide what remains. 💡 Tips to Prevent This in the Future - Publish and verify your page edits before starting a scan. - Keep each question and its answer together in one clear section. - Use plain, natural phrasing that closely follows the recommended question. - Avoid hiding important answers behind interactive elements. - Wait for a scan to fully complete before judging the results. - Rescan after any significant page change so the recommendations stay current. 🔄 What If It Still Shows After a Fresh Scan? If you have confirmed that the page is live, the wording matches, the answer sits directly under the question, caches are cleared, and a new scan has completed, the question may still be listed. In that case, the content may not be detected as expected, and our team should take a closer look. To speed things up, have this information ready: - The exact page URL that was scanned - The question text that still appears in the recommendations - The approximate time you published the changes and the time you ran the scan - A screenshot of the question and answer on your live page 🙋 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 instantly connected with a member of our team.

Last updated on Oct 29, 2026

🛠️ Unwanted OTTO Changes and Refund Requests

📌 Overview OTTO SEO can apply automated changes to your website, such as updates to titles, descriptions, headings, and other on-page elements. If you manage client websites, an unexpected or inappropriate change can be serious. This article explains what to do right away, how to report the problem, and how to request a review of your annual subscription. Refund decisions depend on your plan terms and the details of your situation. This article does not guarantee a refund, but it will help you get your case reviewed quickly and with the right information. 🔍 Why This Can Happen OTTO generates and deploys optimizations based on your site content, your settings, and SEO best practices. Sometimes the result does not fit your brand, industry, or audience. Common causes include: - Wording that does not match your brand voice or is unsuitable for your audience - Changes to sensitive or regulated topics where precise language matters - Automatic deployment turned on before the suggestions were reviewed - Unclear or limited content on the page, which gives OTTO less to work from 🚨 Step 1: Stop Further Changes Right Away If content on a live website looks offensive, inaccurate, or harmful, protect your site first. 1. Open the OTTO project for the affected website. 2. Pause or turn off automatic deployment so no new changes go live. 3. Review the changes that have already been applied to your pages. 4. Undo or revert any change you do not want. If you cannot find the option, ask the support team to help. 5. Clear your site cache and any CDN cache so visitors see the corrected version. Tip: If you manage multiple client sites, repeat these steps for each affected project. 📸 Step 2: Document the Issue Clear evidence helps our team investigate quickly. Before you reach out, gather the following: - The website URL and the specific pages affected - Screenshots showing the content you consider offensive or incorrect - The date and time you first noticed the change - What the page looked like before OTTO changed it, if you have it - The name of the project or client account involved - Any impact on your clients, such as complaints or lost traffic 💬 Step 3: Report the Problem and Request a Review To make sure your request is tracked against your account, please use the in-platform chat. In your message, include: - A short description of what happened - The documentation from Step 2 - Whether you are asking for a refund, a plan change, or help fixing the content - Your subscription type, such as annual, and roughly when you purchased it If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team. ⏱️ What to Expect After You Report - Our team will review the affected pages and the changes OTTO made. - We will help you correct or roll back any content that should not be live. - Your subscription and refund request will be reviewed against your plan terms and the circumstances you describe. - You will be told the outcome and any next steps in the chat conversation. Including full details in your first message usually shortens the process and avoids repeated questions. 🛡️ How to Prevent Unwanted Changes in the Future - Review before publishing: Check OTTO suggestions before they go live, especially on new client sites. - Start small: Apply changes to a few key pages first and check the results. - Protect sensitive pages: Exclude pages where exact wording matters, such as legal, medical, or financial pages. - Check regularly: Look over recent changes on a schedule, such as weekly, for each client site. - Tell us about your brand: Share tone and content guidelines with the support team so they can help you configure your projects. ❓ Frequently Asked Questions Can I get a refund on my annual subscription? Refund eligibility is reviewed on a case-by-case basis using your plan terms and the details of the issue. A team member can look at your account and explain your options. Will OTTO changes be removed from my site? Yes. You can pause OTTO and revert changes you do not want. If you need help, our team can guide you through it. Should I contact someone outside the platform? No. The live chat widget inside the platform is our only support channel. Using it ensures your account details and history are attached to your request. Does reporting an issue pause my subscription? Reporting an issue does not change your billing by itself. Ask the team in chat about your billing options while your case is being reviewed. 🤝 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 instantly connected with a member of our team.

Last updated on Oct 29, 2026

🛠️ Fix OTTO Homepage H1 Not Updating

🔍 What This Issue Looks Like You have approved an OTTO suggestion for your homepage H1 (and sometimes the H2). You have recrawled, reprocessed, and redeployed, but the live page still shows the old heading, or the new one never shows up in the page source. One common cause is a hidden H1 already on the page. Your site may contain an H1 tag that visitors cannot see, and this can stop the new heading from appearing where you expect it. 🤔 Why a Hidden H1 Blocks the Change Every page should have one main H1 heading. Some themes and page builders add an extra H1 behind the scenes. It can be hidden with styling, or it can sit in a header, logo, slider, or banner area. When that happens, the following can occur: - OTTO finds the existing H1 in the page code, which may be the hidden one rather than the one visitors see. - The new heading is applied to, or conflicts with, an element that is not visible on the page. - The visible heading on your homepage stays the same, so it looks like nothing changed. - The page may end up with two H1 tags, which can confuse search engines. This is why recrawling and redeploying do not help. The problem is the page structure, not the deployment. 🧪 How to Check for a Hidden H1 You can confirm this in a few minutes with your web browser. 1. Open your homepage in a browser such as Chrome. 2. Right-click anywhere on the page and choose View Page Source. 3. Press Ctrl+F (Cmd+F on Mac) and search for <h1. 4. Count how many H1 tags appear and read the text inside each one. 5. Compare them with the main heading you see on the page. For a more precise check, right-click the heading on your page and choose Inspect. Then search the code for H1 tags in the Elements panel. You likely have a hidden H1 if you see any of these: - An H1 whose text does not match anything visible on your homepage. - An H1 inside a logo, menu, slider, or header section. - An H1 with styling that hides it, such as display none or a tiny font size. - More than one H1 on the page. 🛠️ How to Fix It The goal is to leave one visible H1 on the homepage. Choose the option that fits how your site is built. 1. Remove the hidden H1. In your theme, page builder, or editor, find the hidden heading and delete it. Many builders let you set the heading level on each element. 2. Change its heading level. If you want to keep the text, change its tag from H1 to a paragraph or a lower heading such as H2 or H3. 3. Make the visible heading the H1. If your visible headline is currently an H2 or styled text, set it to H1 in your editor so it is the only H1 on the page. 4. Check theme and plugin settings. Some themes add an H1 to the logo or site title on the homepage. Look for a setting that changes this. 5. Clear your caches. Clear any caching plugin, hosting cache, or CDN cache so the updated page is served. If you are not sure which element is the hidden H1, share the page with your web developer. Ask them to make sure the homepage has only one visible H1. 🚀 Re-Apply the OTTO Suggestion After you have fixed the page structure, let OTTO pick up the changes. 1. Open your project in Search Atlas and go to OTTO SEO. 2. Find the homepage H1 (and H2) suggestion. 3. Trigger a fresh crawl or reprocess of the homepage. 4. Review the suggestion and deploy it again. 5. Wait a few minutes, then reload your homepage in a private or incognito window. ✅ How to Confirm It Worked - View the page source and search for <h1. You should find exactly one H1 with the new text. - Check that the heading is visible on the page and matches the suggestion. - If you also deployed an H2, confirm it appears in the page source. - Test in an incognito window to rule out your own browser cache. 💡 Other Things That Can Delay Changes If you have only one H1 and the heading still has not changed, check these points: - Caching: Your site, hosting, or CDN may still serve an older version of the page. - Page builder content: Some builders load headings with JavaScript after the page opens. Check that the heading is present in the page source. - Several homepage versions: Check that the URL OTTO is working on matches your live homepage, including www or non-www and the trailing slash. - Deployment status: Confirm the change shows as deployed in OTTO and not as pending. 🧭 Best Practices Going Forward - Use only one H1 per page, and make sure visitors can see it. - Keep your H1 consistent with the page topic and main keyword. - Recheck your page source after changing themes, plugins, or page builders. - Clear your caches after every major page change. 💬 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 instantly connected with a member of our team. Please include your homepage URL and a note that you suspect a hidden H1 so we can look into it faster.

Last updated on Oct 29, 2026

🔄 Replace GHL with Vercel and Install OTTO

📌 Overview If you moved your website from GoHighLevel (GHL) to Vercel, your old GHL integration in Search Atlas no longer points to your live site. To keep OTTO SEO working, you need to disconnect GHL and connect your Vercel site. This article walks you through both steps and explains how to confirm everything works. Note: Screen labels may differ slightly depending on your account and platform version. If something looks different from the steps below, use the chat option at the end of this article. ✅ Before You Start Have the following ready so the process goes smoothly: - Your website is already live on Vercel and loads on your domain. - You can sign in to your Vercel account with permission to manage the project. - You can sign in to Search Atlas as the account owner or an admin. - You know which domain or project in Search Atlas was linked to GHL. 🔌 Step 1: Disconnect the GHL Integration Disconnect GHL first so the old connection does not conflict with your new setup. 1. Sign in to Search Atlas and open the project or domain that was connected to GHL. 2. Go to the OTTO section and open its installation or integration settings. 3. Find the GoHighLevel (GHL) connection. 4. Select Disconnect (or Remove) and confirm. 5. Refresh the page and check that GHL no longer shows as connected. If you also want to stop any leftover OTTO code on your old GHL site, remove any OTTO script or snippet you added there. This is only needed if that GHL site is still online. 🚀 Step 2: Connect Vercel and Install OTTO 1. In the same project, return to the OTTO installation settings. 2. Choose Vercel as your installation method or platform. 3. Follow the on-screen prompts to authorize access to your Vercel account. You may be asked to sign in to Vercel or provide an access token. 4. Select the Vercel project that hosts your website. 5. Confirm the installation and wait for the setup to finish. 6. If prompted, redeploy your Vercel project so the changes go live. Tip: Make sure the domain in Search Atlas matches the domain on your Vercel project exactly, including whether it uses www or not. 🔍 Step 3: Confirm OTTO Is Working After setup, check that the connection is active: - In Search Atlas, confirm the OTTO status shows as Connected or Installed. - Visit your live website and make sure it loads normally. - Allow some time for OTTO to detect your site and apply optimizations. This can take a little while after a fresh install. - Re-run the installation check in OTTO if the platform offers one. 🛠️ Troubleshooting Common Issues - OTTO still shows as not installed: Redeploy your Vercel project, wait a few minutes, and check again. - GHL still appears as connected: Refresh the page or sign out and back in. If it stays connected, try disconnecting again. - Vercel project does not appear in the list: Check that you authorized the correct Vercel account or team, and that you have access to the project. - Domain mismatch: Check that your project domain in Search Atlas matches the live domain on Vercel. - Old changes are missing: Optimizations applied while you were on GHL do not move automatically. OTTO will re-apply them once it is installed on your Vercel site. 💡 Best Practices - Complete your site migration and DNS changes before reconnecting OTTO. - Keep only one active integration per domain to avoid conflicts. - Redeploy your Vercel site after any major change to your setup. 💬 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 instantly connected with a member of our team.

Last updated on Oct 29, 2026

💡 Adding an Extra OTTO Site on Starter

🔍 Overview Many customers on the Starter plan want to test OTTO on more than one domain before deciding how to grow. This article explains how OTTO site limits work, what your options are for adding a second site, and how to ask about custom pricing. 📌 How OTTO Site Limits Work Each Search Atlas plan includes a set number of sites that can have OTTO activated. Starter is built for smaller projects, so its OTTO site allowance is limited. If you want OTTO on another domain and you have already used your included site, the platform will not let you activate it until your plan changes. - OTTO site limits apply to the number of active OTTO domains on your account. - Upgrading your plan, including a recent upgrade, does not always change the OTTO site allowance. It depends on the plan you moved to. - Other features, such as reports and research tools, may have separate limits from OTTO. ✅ How to Check Your Current OTTO Allowance 1. Log in to your Search Atlas account. 2. Open your account or billing settings and review your current plan details. 3. Open the OTTO section and check how many sites are currently active. 4. Compare the active sites against your plan's included allowance. If you have a free slot, you can add your second domain right away from the OTTO section. 🚀 Options for Testing OTTO on a Second Domain If you have used all your OTTO slots, you generally have these options: - Upgrade your plan: A higher-tier plan typically includes more OTTO sites and additional features. - Swap sites: If you only need to compare results over time, you can deactivate OTTO on one domain and activate it on another. Keep in mind that changes OTTO has already applied to the first site may be affected, so confirm what you want to keep before switching. - Request a custom arrangement: If neither option fits your needs, you can ask our team whether an additional site is possible for your account. 💬 Can I Get Custom Pricing for an Additional OTTO Site? You are welcome to ask. Custom requests are reviewed case by case by our team, so we cannot guarantee a specific outcome or price in advance. Availability may depend on your plan, your account history, and what you want to accomplish. Standard published pricing is always the baseline, and any custom option would be confirmed with you in chat before you are charged. 📝 How to Make a Request 1. Open the chat widget in the bottom-right corner of the platform. 2. Type human teammate to be connected with a member of our team. 3. Share these details to speed things up: - The domain you currently use with OTTO. - The additional domain you want to test. - Your reason for testing, such as comparing results across two sites. - How long you plan to evaluate OTTO. 4. Review the options our team presents and confirm the one that works for you. 💡 Tips for Evaluating OTTO on Two Domains - Pick comparable sites: Similar size, niche, and traffic levels make the results easier to compare. - Set a baseline first: Note your rankings, traffic, and key pages before activating OTTO. - Give it time: SEO changes can take weeks to show results, so avoid judging too early. - Track changes: Keep a simple log of what OTTO applied and when. ❓ Frequently Asked Questions Does a recent upgrade automatically add more OTTO sites? Not necessarily. Check your plan details to see what your current plan includes. Will I be charged without confirming? No. Any change to your plan or pricing is discussed with you first. Can I switch OTTO between my domains? In many cases, yes. Confirm the impact on your existing optimizations before switching. 🛠️ 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 instantly connected with a member of our team.

Last updated on Oct 29, 2026

🔍 Understanding OTTO Deployments and Deployed Changes

💡 The Short Answer OTTO does more than make suggestions. It finds SEO opportunities on your site, and when a change is deployed, OTTO applies it to your live pages for you. Whether a change goes live right away or waits for your approval depends on your deployment settings for the project. ⚙️ How OTTO Deployment Works OTTO works in three stages: 1. Analyze: OTTO scans your site and identifies improvements, such as page titles, meta descriptions, headings, image descriptions, schema markup, and internal links. 2. Recommend: Each improvement appears as a recommendation, grouped by type so you can see what it plans to change. 3. Deploy: Once a change is deployed, OTTO applies it to your live page through its connection to your website. You do not need to edit each page by hand. A recommendation that has not been deployed is only a suggestion. Your site stays unchanged until it is deployed, either by you or automatically. 🎛️ Automatic vs. Manual Deployment - Manual: You review each recommendation and choose which ones to deploy. This gives you the most control. - Automatic: OTTO deploys approved types of changes without waiting for you to click each one. If you are unsure which mode your project uses, check the deployment settings in your OTTO project. If you only see recommendations and no applied changes, your changes are probably waiting for approval. 📊 Where to See What OTTO Has Done To see the breakdown of deployed changes, especially within playbooks, follow these steps: 1. Open your project in Search Atlas and go to OTTO SEO. 2. Select the playbook or recommendation group you want to review. 3. Look at the status of each item. Items are shown as deployed or not yet deployed (pending). 4. Open an individual item to see the page it affects and the change that was made, such as the old and new version of a title or description. Use this view to compare how many changes are live and how many are still waiting. It also shows you exactly which pages were touched. ✅ How to Confirm a Change Is Live on Your Site 1. Open the affected page in your browser. 2. Right-click the page and choose View Page Source, then search for the updated title, description, or schema text. 3. Compare it with the change shown in OTTO. Many changes, such as title tags and meta descriptions, are not visible on the page itself. You will only see them in the page source, in the browser tab title, or in search results once Google updates its listing. 🛠️ If You Do Not See Your Changes - The change is still pending. Check that the item is marked as deployed, not just recommended. - Caching. Your website, plugin, or CDN may be showing an older saved version. Clear your site cache and reload the page. - Connection not complete. OTTO needs to be properly connected to your site to apply changes. Confirm the installation steps for your project were completed. - Search results take time. Even after a change is live on your page, Google may take days or weeks to show it in search results. - Different page version. Make sure you are checking the exact page URL listed in the OTTO item, including any www or trailing slash differences. 🚀 Tips for Getting the Most From OTTO - Review each playbook regularly so nothing stays pending longer than you intend. - Deploy in small batches at first, and verify a few pages to build confidence. - Track results in your rankings and traffic reports over several weeks, since SEO changes take time to show an effect. 💬 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 instantly connected with a member of our team.

Last updated on Oct 29, 2026

🛠️ Fixing OTTO and Yoast Title Conflicts

If you use both Yoast SEO and Search Atlas OTTO, you may see different page titles in each tool, or an old title that will not update. This article explains why that happens, how to check what visitors and search engines actually see, and how to get your OTTO title deployments live. 🔎 Why Titles Can Differ Between Yoast and OTTO Yoast and OTTO can both control the SEO title (the title tag) of a page. When both are active, they can disagree for a few common reasons: - Two sources of truth: Yoast stores its own title for each page, and OTTO stores a separate, optimized title. By default OTTO does not change Yoast's stored title, so the two dashboards can show different values. If Meta Title persistence and Sync to Other SEO Plugins are both enabled, OTTO copies its title into Yoast's SEO title field. - Caching: Your website, a caching plugin, or a CDN may be serving an older copy of the page, so new titles do not appear right away. - Duplicate title tags: On a WordPress site, Yoast normally outputs the single title tag, and OTTO replaces the text inside that tag rather than adding a second one. If both tools temporarily produce a title tag, OTTO's final processing keeps only one, so browsers and search engines should not see two. - Search engine rewrites: Google sometimes shows a different title in search results than the one on your page. This can look like an old title even when your site is correct. - Deployment not completed: The change may be queued, paused, or not yet applied to that specific page. ✅ Step 1: Check What Your Page Actually Shows Before changing any settings, confirm which title is really live on the page. 1. Open the affected page in a private or incognito browser window. 2. Right-click the page and choose View Page Source. 3. Search for in the source. 4. Note which title appears, and whether there is more than one title tag. If the live title matches OTTO, that is what you expect after a successful deployment, but a page cache or a manually entered Search Atlas title can produce the same result. If the live title matches Yoast, OTTO's change may not be applied to that page yet, or OTTO may be turned off for that page or URL. Seeing two title tags on a WordPress page is not the normal result of this conflict, because OTTO is built to leave only one title tag. 🧹 Step 2: Clear Your Caches Old titles are often caused by cached pages. Clear every layer you use: - Your WordPress caching plugin (for example, a page cache or performance plugin). - Your CDN or hosting-level cache, if you use one. - Your browser cache, or test in a private window. After clearing, reload the page and check the page source again. ⚙️ Step 3: Choose One Tool to Control Each Title The most reliable way to avoid conflicts is to decide which tool controls the title for each page. - If you want OTTO to control the title, approve and deploy the title change for that page, and make sure OTTO is enabled for the page and its URL is not excluded. A title entered manually in the Search Atlas SEO sidebar will override OTTO, so clear that field if you want OTTO's title to win. Yoast may still show its own stored title unless Meta Title persistence and Sync to Other SEO Plugins are enabled. - If you want Yoast to control the title: Do not deploy OTTO title changes for that page. Keeping Yoast and OTTO in sync, or letting only one of them manage titles, prevents most mismatches. If you update a title in OTTO and want Yoast to match, update the same title in Yoast as well so both dashboards show the same value. 🚀 Step 4: Check Your OTTO Deployment Status If your OTTO deployments have not gone live after many days, check the following: 1. Open OTTO in your Search Atlas project and find the affected pages. 2. Confirm the title changes show as deployed, not just suggested or pending. 3. Confirm OTTO is still properly installed and connected to your website. A site migration, theme change, or plugin change can disconnect it. 4. Check for security or firewall settings on your site that might block OTTO from applying changes. 5. Redeploy the change for one affected page, then clear your cache and recheck the page source. If one page works after redeploying but others do not, note the page URLs. This helps our team investigate faster. 📌 Should You Select the Indexing Option? The indexing option is optional. It is meant to help search engines notice your updated pages sooner. It does not decide whether a title is applied on your website. - Use it if you want search engines to recrawl the page and pick up the new title faster. - Skip it if you are still testing or have not confirmed that the live title is correct. Verify the title in the page source first, then request indexing. Otherwise, search engines may pick up an outdated or conflicting title. ⏱️ How Long Until Search Results Update? Even after your page shows the correct title, search results can take days or weeks to change. Google may also choose to display a different title than the one you set. If the page source shows the correct title but search results still look old, this is usually a search engine timing issue, not a deployment issue. 📋 Quick Troubleshooting Checklist - View the page source and confirm which title is live. - Check for duplicate title tags. - Clear plugin, CDN, and browser caches. - Decide whether OTTO or Yoast controls the title for each page. - Match the title in both tools if you use both. - Confirm the OTTO deployment is active and redeploy if needed. - Use the indexing option after the live title is correct. 💬 Need More Help? If titles are still not updating after these steps, please have the affected page URLs, the title you expect, and the title you see ready. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

Last updated on Oct 29, 2026

🔄 OTTO Still Showing GHL After Vercel Migration

🔍 What Is Happening? You moved your website from GoHighLevel (GHL) to Vercel and deleted the old GHL project. OTTO can still show GHL as the detected CMS. Deleting the project in GHL does not tell Search Atlas the site moved, so the label stays until the site is crawled again. This is common after a migration and is usually easy to fix. Deleting the project in GHL does not tell Search Atlas that your site has moved. OTTO stores the CMS it detected from the last crawl of your homepage, and that label stays until a new crawl reads the live site and updates it. 🧠 Why OTTO Still Shows GHL There are a few common reasons: - Detected CMS: Search Atlas still has GHL saved because the last crawl of your homepage matched GoHighLevel. It is a detection result, not a site type or connection method you selected. - DNS has not fully updated: Your domain may still point to GHL servers, or the change has not spread across the internet yet. This can take up to 24-48 hours. - Cached pages: Your browser, a CDN, or a caching service may still serve an older version of your site that was built on GHL. - Leftover GHL code: Old GHL scripts, tracking snippets, or links may still be in your new site's code or templates. - Old integration still connected: The GHL integration may still be linked to your Search Atlas account, even though the GHL project no longer exists. ✅ Before You Start: Quick Checklist Check these first so you can rule out the most common causes: - Your site loads correctly on Vercel at your live domain (not just the Vercel preview URL). - Your domain's DNS records point to Vercel. - Your domain has an active, valid SSL certificate in Vercel. - You can open your site in a private or incognito window and see the new Vercel version. 🛠️ Step-by-Step: How to Fix It 1. Confirm your domain points to Vercel. In your Vercel dashboard, open your project's domain settings and make sure the domain shows as valid and configured. If it shows an error, fix the DNS records first. 2. Wait for DNS to finish updating. If you changed DNS recently, allow up to 48 hours. You can check with a free DNS lookup tool to see whether your domain now points to Vercel. 3. Clear your caches. Clear your browser cache, and purge any CDN or caching tool you use. In Vercel, you can also redeploy your project to make sure the newest version is live. 4. Remove leftover GHL code. Check your site's header, footer, and templates for old GHL scripts, embed codes, or links, and remove anything you no longer need. 5. Recrawl the site in Search Atlas. Open Site Audit for this project and choose Recrawl or Recrawl Site. OTTO reads the live homepage and replaces the GHL label when the page no longer matches GoHighLevel. There is no CMS setting to change, and Vercel is not an OTTO CMS option. 6. Delete the old GHL connector. Go to Settings, open CMS Connectors, find the GoHighLevel connector, and choose Delete. This stops Search Atlas from publishing content to GHL. It does not change the CMS label OTTO shows. 7. Reinstall OTTO on the new site. Open the OTTO installation guide and add the OTTO script to the site now hosted on Vercel, then run the installation check so OTTO can verify the new site. Moving the site does not carry the old installation with it. 8. Re-check your project. Refresh the page in Search Atlas and confirm the CMS or connection status no longer shows GHL. 💡 Tips to Avoid This Issue in Future Migrations - Update your Search Atlas project settings before deleting your old CMS project. - Keep the old site live until the new one is fully working and DNS has finished updating. - After any migration, test your site in an incognito window to avoid seeing cached content. - Remove old integrations and scripts as part of your migration checklist. - Keep the same domain if you can. A domain change may need a new project setup. ⚠️ If OTTO Still Shows GHL If you have followed every step and OTTO still shows GHL, gather the following details so we can resolve it faster: - Your domain name (for example, yourdomain.com) - The date you moved to Vercel - Whether your domain now points to Vercel in DNS - A screenshot of the project or CMS setting that still shows GHL 💬 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 instantly connected with a member of our team.

Last updated on Oct 29, 2026

🛠️ How to Add a New OTTO Project

🔍 Overview If you try to add a new client site and the platform keeps showing your previous project, you are not alone. This is a common point of confusion. OTTO and Site Audit each open the site you last worked on in that tool, so starting in the wrong place can look as if you are still on the old client. This article explains the difference between the three places customers usually try, and walks you through adding a new project the right way. 🧭 Why the Old Project Keeps Appearing Search Atlas remembers the last project you worked on. When you open a tool such as OTTO or Site Audit, it loads that project automatically. This saves time, but it can look as if the platform is blocking you from setting up a new site. In most cases, nothing is broken. You just need to create a new project first, or switch the active project, before you continue. 📌 OTTO Project vs Site Audit vs Project Button These three areas look similar, but each does something different: the Home project picker, an OTTO project, and Site Audit. - OTTO project: The workspace where OTTO analyzes one website and applies optimizations. Each website or client needs its own OTTO project. - Site Audit: A tool that scans the site of the selected project and reports technical issues. Running a Site Audit does not create a new OTTO project. It only audits the project that is already active. - Home project picker: the control on the Home tab that shows "All Projects" or the selected project name. Open it to switch projects, or choose Create project at the bottom to add a client. Tip: If you start from Site Audit while your old project is selected, the audit will run on the old site. Always check the project name first. 🚀 How to Add a New Client Project 1. On Home, open the project picker and check which project is active. It shows All Projects when none is selected, or the selected project name. 2. Choose the option to add or create a new project, rather than selecting an existing one from the list. 3. Enter the new client's domain, such as yoursite.com. The form already shows https:// in front of the field. Do not include a page path. 4. Choose a primary goal and market location. If you continue with guided setup, you can also choose a language. Then select Create project, or Create project & continue. 5. After the project is created, confirm that its name appears as the selected project in the Home project picker. 6. Open OTTO and follow the on-screen steps to connect and install OTTO on the new website. 7. Optionally, open Site Audit and run a scan to get a technical baseline for the new site. 🔄 How to Switch Between Projects Once you manage several clients, you will switch often. Use these steps each time: 1. On Home, open the project picker. 2. Select the client project you want to work on. 3. The page updates without a full refresh. On Home, confirm the project name in the project picker. In OTTO, confirm the site name and domain in the project header. In Site Audit, confirm the domain in the site selector. 4. Open the tool you need, such as OTTO or Site Audit. Always confirm the active project before making changes. This prevents optimizations or audits from being applied to the wrong site. ⚠️ Troubleshooting - The new project is not saved: Check the domain for typos and make sure the required fields are filled in. Then try again. - The platform says the site already exists: The domain may already be in a project on your account. Open the project selector and look for it before creating a duplicate. - Site Audit shows the wrong website: The old project is still active. Switch to the correct project and run the audit again. - OTTO does not show the new site: Refresh the page, then confirm the new project is selected. Make sure you have finished the OTTO installation steps for that site. - You cannot add more projects: Your plan may have a limit on the number of projects. Check your plan details in your account settings. 💡 Best Practices - Create one project per website so reports and optimizations stay organized. - Use clear project names, such as the client or business name. - Check the active project before you run any audit or approve any OTTO changes. - Finish the OTTO setup for each new project before moving on to the next client. 💬 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 instantly connected with a member of our team.

Last updated on Oct 29, 2026

⚙️ Extra OTTO Account Not Available

🔍 Why your OTTO account may be missing After you buy additional OTTO sites, the extra capacity is added to the OTTO site quota on your existing Search Atlas account. It does not create a separate OTTO account, and nothing new appears in an account selector. ✅ Check your purchase and account access 1. Confirm that the purchase was completed successfully and was not left pending or cancelled. 2. Make sure you are signed in with the Search Atlas login used to purchase the extra OTTO account. 3. Open Billing and check OTTO Quotas, or Billing and then Plan Limits. The Sites row should show a higher “used of” total. The OTTO project selector will not list a new account. 4. Refresh the page, then sign out and back in if the account is still not visible. ⏳ Avoid duplicate purchases Do not start another OTTO Sites purchase while the first checkout is still processing. You will be told it is already being processed or, once the same purchase has completed, that it has already been purchased. Buying a different quantity later adds another recurring charge and does not speed up the first purchase. 🛠️ What to do if it is still unavailable If your payment succeeded but the OTTO Sites total under OTTO Quotas or Plan Limits does not increase, contact support and include the purchase date, the email address on your Search Atlas account, and your payment or order confirmation. There is no separate OTTO account to provision. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

Last updated on Oct 29, 2026

🔍 Find a Missing OTTO Subscription

🔎 Why OTTO may be missing OTTO is not a separate subscription from your Search Atlas plan. On Billing, open the Services tab. Your PRO plan appears as the base plan, and extra OTTO capacity appears on the same page as an OTTO Sites top-up or add-on. Both belong to the same customer account. ✅ Check your subscription 1. Confirm you are signed in to the correct Search Atlas account. 2. If you manage more than one customer account, open the account where the OTTO Sites top-up was purchased. Use the account menu to switch into that customer account. OTTO is tied to the customer account, not to a workspace. 3. Open the platform’s billing or subscription settings. 4. On the Services tab, look for an OTTO Sites top-up or add-on listed with your plan. It is not a separate OTTO subscription. 5. Refresh the page and sign out and back in if the subscription still does not appear. 🧾 Verify your billing details On Billing, open Invoices and look for an OTTO Sites charge. If you can open more than one customer account, check the invoices on each account. The OTTO Sites top-up is on the same customer account as the plan it was added to, not on a different workspace or user account. ⚠️ If OTTO is still not listed Gather the account email, workspace name, approximate purchase date, and any OTTO invoice or payment details. Do not share full payment card information. This information helps our team locate the correct subscription and confirm its billing status. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

Last updated on Oct 29, 2026

💳 Find a Missing Monthly Payment ID

💳 What this article covers Search Atlas does not show customers a monthly payout transaction ID for partner payouts, referral rewards, or approved credits. If you are a Publication Media publisher, a PayPal Transaction ID is created only after a payout is actually sent. This article explains where that ID appears and what to share if you still cannot find the payment. 🔎 Where to find the transaction ID Start inside your Search Atlas account before requesting a manual lookup. The transaction ID is the reference that your bank or payment provider uses to match an incoming transfer. 1. Sign in to Publication Media and open Earning History from your profile menu. 2. On Earning History, review the remittance list. The earnings summary can be filtered by All, Today, Weekly, Monthly, or Yearly. 3. Find the remittance row for the payment you are checking. 4. Copy the value in the PAYPAL TRANSACTION ID column. It is present only after the payout has been sent successfully. 5. Check the STATUS column. Paid means the payout was sent. Unpaid means it has not been sent yet. Also check the email inbox for your Publication Media account, including spam or promotions. The Payment Sent email includes the amount, Transaction ID, and PayPal email. ⏱️ Why a payment may not show yet A missing deposit does not always mean the payment failed. These are the most common reasons: - Processing time: After a payment is marked sent, banks and payment providers can take several business days to post it. Weekends and holidays can add delay. - There is no minimum balance you must reach. Eligible posted-article earnings are grouped into an unpaid remittance, and staff sends the payout. The portal says payouts are issued during the first week of each month for earnings cleared in the previous month. - Publisher payouts are sent to the PayPal email in Account Settings. A missing PayPal email blocks payment, and an unsuccessful PayPal payout is not marked paid. - Confirm that the PayPal email in Account Settings is the email that should receive the payout. The profile name is not checked against the PayPal account name. - Earning History is a list of remittances, not a calendar of the months when the work happened. Use the DATE column to identify the remittance. ✅ What to check before contacting support Use this short checklist so the payment can be traced quickly: - In Account Settings, confirm that the saved PayPal email is current. - Review the last two monthly entries, not only the latest one. - Search your bank or payment-provider activity for Search Atlas and for any reference you already copied. - Note the expected amount, currency, and the month you believe the payment covers. - If the row says unpaid, or paid with an empty PAYPAL TRANSACTION ID, include a screenshot of the full row when you contact support. Do not share full bank account numbers, card numbers, or passwords in chat. A transaction ID, the last four digits of an account, the amount, and the payout month are enough. 🛠️ If the ID is missing or the payment never arrived If the history shows no payment for that month, or the status says sent but nothing has posted after several business days, contact support with the month, expected amount, payout method, and any partial reference you found. Our team can confirm whether a transaction ID was issued and resend the reference. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

Last updated on Oct 29, 2026

💰 Custom OTTO Pricing and Growth Discounts

💡 What this article covers Some customers want to evaluate OTTO on more than one domain, add another OTTO site after a recent upgrade, or ask whether a discount is available on the Pro or Growth plan. This article explains how those requests are handled and what you can expect. 📊 How OTTO pricing normally works OTTO access is tied to your Search Atlas plan and to the sites included with that plan. Published plan prices are the standard rates. There is no self-serve trial that adds two or three extra domains. Sites beyond your plan are added as paid OTTO site top-ups, which you can buy yourself. A custom price is a separate offer created by our team. - Pro plan: Flexibility is not automatic. A recent upgrade does not by itself unlock extra OTTO sites or a temporary test rate. - Extra domains: Each OTTO site you want to run should be listed in your request so the team can match it to the right plan. - Evaluation use: connecting a site for learning still uses a plan-included or paid OTTO site. There is no separate short-test rate or review. It is billed the same way as a production site. 🚀 When a Growth plan discount may apply If you need a price below the published plans, our team can review a custom offer. For Growth, the published price is $199 per month for 2 OTTO sites. A lower price, such as $150 per month, is set only on an individual account by our team. It is not a public coupon and it is not applied automatically. - A custom Growth price is considered only when our team agrees that the published plan price does not fit your account. A recent upgrade or a short evaluation does not by itself qualify you for a $150 rate. - Approval depends on your current plan, billing status, and how many OTTO sites you need. - A custom plan price applies only to the plan and site count our team confirms. It does not unlock unlimited domains. Additional OTTO sites are billed as top-ups unless the agreement includes them. There is no free trial for two or three extra domains. - A custom price applies only to the account our team updates. It continues on the normal billing cycle until our team changes it. It does not change the public price list. Ask our team to confirm any end date, because the product does not end it automatically. 🛠️ What to include when you ask A complete request is usually resolved faster and avoids a second escalation. Have these details ready before you open chat: 1. The domains you want to connect. Our team will confirm how many are included in your plan or custom agreement. Any others are paid OTTO site top-ups. 2. Whether each domain is for learning only or for ongoing SEO work. 3. Your current plan and the date of your recent upgrade, if you have one. 4. How many OTTO sites you already have and how many you want to add. 5. Whether you are asking about your current Pro plan or a custom Growth plan price. Growth's published price is $199 per month. Any other amount has to be confirmed for your account. ⚙️ What happens after your request A teammate reviews the account and confirms what will change: stay on your current plan, move to a published plan, or apply a custom price. You will see the price and the number of OTTO sites before it is applied. Do not buy extra sites or assume a discount is active until that change is confirmed. If a custom Growth price is approved, our team applies it to your subscription. After it is active, connect only the OTTO sites included in that agreement. Additional sites are paid top-ups. The custom price keeps billing until our team changes it, so ask for a new review before assuming it has ended. 💬 How to request a pricing review Pricing exceptions are handled only inside the product. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

Last updated on Oct 29, 2026

📊 Why OTTO Shows Missing Analysis

📊 What missing analysis means OTTO does not mark individual dates as missing analysis. Traffic results in OTTO come from a connected Google Search Console property. If Search Console is not connected, OTTO tells you to connect it. Google Analytics 4 is connected separately and feeds sessions, conversions, and the UX score. A gap is a connection or property problem, not a loss of your live website. 🔍 Common reasons analytics do not appear - Google Analytics 4 must be linked to the Search Console property for this project's domain. Authorizing a Google account alone does not connect analytics for the project. - The wrong GA4 property can be linked, so another site's data, or no data, is used. Search Atlas does not ask you to pick a data stream. It uses the first web data stream on the property you select. - The date range has no data yet, including future dates or days before tracking was installed. - Permissions changed after the Google account owner removed access or switched accounts. - The tracking snippet is missing or blocked, so visits are not recorded. - A new connection does not need 24–48 hours before OTTO charts fill. Analytics reports are requested from Google when you open them. Google's own data can lag, and Search Console data usually trails by about a day. 🛠️ Check the project and date range 1. Open the affected project in Search Atlas and confirm its domain is the site you expect. Then link the GA4 property that belongs to that domain. 2. In OTTO, check whether Search Console is connected and whether traffic results are showing. OTTO does not flag individual dates as missing analysis. 3. Set the report range to a recent period that should already have traffic, such as Last Month, and refresh the page. 4. If the flagged date is in the future, or before the site was tracked, OTTO cannot show analysis for it. Choose dates after tracking went live. ⚙️ Reconnect analytics 1. Go to Settings, then Integrations, and open Google Analytics. To attach analytics to this project, choose the GA4 property for its domain. Connect Search Console for that domain first, because the GA4 link is saved against that property. 2. Disconnect the current analytics account if it shows an error, expired access, or the wrong property. 3. Connect again with a Google account that has at least read access to the correct property. 4. Select the GA4 property that matches this domain. Do not select a test, staging, or unrelated property. You are not asked to choose a data stream. 5. Save the property, then return to the project and refresh. Reports load from Google Analytics when you open them. They are not held for 48 hours. 💡 Confirm tracking on the website Analytics can only sync if the site records visits. Ask your developer or site owner to confirm the measurement ID is installed on all public pages, including the homepage and key landing pages. Cookie banners, tag managers, and ad blockers can prevent hits. After a fix, browse the site yourself, then check the analytics property for a new session before expecting OTTO to update. 🚀 After data returns Once data is available, OTTO uses Search Console traffic and GA4 engagement to inform SEO work, including the UX score. Recheck the same report range. If only one day is empty but nearby days have data, that day may have had no measurable visits. Gaps across many days usually mean Search Console or the linked GA4 property still needs attention. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

Last updated on Oct 29, 2026

🔄 Switch GHL Site Connection to Vercel

🔄 What this article covers Use this guide after you move a website from GoHighLevel (GHL) to Vercel and need OTTO to follow that change. You will disconnect the old GHL site connection, connect the Vercel project, and confirm OTTO is pointed at the new site. 📋 Before you switch A site can stay tied to its previous host until you update the connection. Complete these checks first so rankings data and OTTO settings stay attached to the correct property. - Confirm the live site is already deployed on Vercel and the public domain loads correctly. - Note the exact domain you want OTTO to manage. It should match the domain used in Search Atlas. - Make sure you can sign in to the Vercel account that owns the project. - Keep the GHL connection in place until the Vercel site is ready. Disconnecting first does not move the website by itself. 🔌 Disconnect the GHL connection 1. Open the site or project in Search Atlas. 2. Go to the integrations or connected-sites area for that property. 3. Find the GoHighLevel or GHL connection. 4. Choose disconnect or remove, then confirm. This stops OTTO from using the old GHL site. It does not delete your GHL account or your Vercel project. 5. Refresh the page and check that GHL no longer shows as connected for this site. If the old connection still appears, wait a moment and refresh again. Do not add Vercel until GHL is fully removed, or OTTO may stay linked to the previous host. 🚀 Connect the Vercel site 1. In the same site or project, open the option to add or connect a site host. 2. Select Vercel. 3. Sign in with the Vercel account that owns the project and approve access when prompted. 4. Choose the Vercel project and the production domain that matches your Search Atlas site. 5. Save the connection. OTTO should now use the Vercel site instead of GHL. Use the production domain, not a temporary preview URL, unless that preview address is the only domain you want OTTO to manage. ✅ Confirm the switch worked - The site shows Vercel as the connected host. - GHL is no longer listed as connected for this property. - The domain in Search Atlas matches the live Vercel domain. - OTTO pages and recommendations load for that domain. Existing keyword and site history usually stays with the Search Atlas project when you only change the host connection. If you created a brand-new project instead, history will not move automatically. 🛠️ If the connection does not update - GHL still appears: disconnect it again, refresh, and confirm you are viewing the correct site. - Vercel project is missing: sign in with the account that owns the project and check that the deployment is in production. - Wrong domain is selected: remove the Vercel connection and reconnect using the live domain. - OTTO still references the old site: verify the domain match, then reopen OTTO after the new connection is saved. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

Last updated on Oct 29, 2026

🔍 Why OTTO Edits Miss the Live Site

🔍 What Deployed Means in OTTO When OTTO shows an edit as deployed, Search Atlas has published that change to the OTTO installation connected to your site. Deployed does not always mean your browser, a content delivery network, or a page cache is already serving the newest version. Compare the live page with the exact URL listed in OTTO, including https, www, and any trailing slash. ⚠️ Why the Live Page Can Look Unchanged Most cases come from a saved copy of the page, not from a failed deploy. Check these causes before you redeploy the same edit: - Browser cache: your browser may still show an older copy of the page. - Site or host cache: a caching plugin, server cache, or CDN can keep the previous HTML. - Wrong page: the live URL may differ from the URL OTTO updated, such as a trailing slash, www, or a similar slug. - Different field: OTTO may have changed a title, meta description, heading, or schema item that is not obvious in the page design. - Script not loading: the OTTO script may be missing, blocked, or not included on that template. - Static build: OTTO does not rewrite your site's saved HTML files. On a static site the edit appears only when the OTTO script loads in the browser, so you do not publish a new HTML build to make a deployed edit show. If the script is missing from that page, install it in the site template instead. 🛠️ Check the Live Page Step by Step 1. In OTTO, find the deployed edit in its issue table and use the PAGE URL column. Click the path to open that live page, and compare it with the path shown, including www and any trailing slash. 2. Note what changed, such as the title, meta description, heading, alt text, or internal link. 3. Open that same URL in a private or incognito window. 4. Use your browser view-source tool and search for the new text. Do not rely only on the visual design. 5. If the new text is in the source but not on screen, clear the browser cache and check any on-page script or styling that hides it. 6. If the new text is missing from the source, purge your site cache, host cache, and CDN, then recheck the source. 7. Confirm the OTTO script is present in the page source on that URL. If it is missing, the install may not cover that template. 8. After caches are cleared, reload the live page. If the source still shows the old content, return to OTTO and confirm the edit still says Deployed. Clicking Deployed undeploys it, so only click Deploy again if the edit has been undeployed. 🧹 Clear Cache Before You Retest Wait a few minutes after a purge, then reload the exact URL in a private window. If your host or CDN has a separate purge for HTML and for images, purge HTML first. A hard refresh on one computer is not enough when a CDN still holds the old page for other visitors. ✅ Confirm the Right Change and URL Match the live result to the field OTTO edited. A new meta description will appear in the page source and in search results later, but it may not change the visible layout. Also confirm you are checking the production domain, not a staging copy, and that no firewall, consent tool, or optimization app is blocking the OTTO script on that page only. 💬 When to Contact Support Contact support if the exact URL matches, caches are purged, the OTTO script is present, and the new text is still missing from the 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 instantly connected with a member of our team.

Last updated on Oct 29, 2026

🚀 How OTTO Deploys and Shows Results

🤖 What OTTO does with its suggestions OTTO does more than list ideas. It recommends SEO improvements and can deploy the ones you approve to your live site. A suggestion stays a recommendation until it is approved and deployment is active. After that, OTTO applies the change for you. Deployment works through the OTTO installation on your website, usually the OTTO script or pixel added to the site. If that connection is missing or paused, OTTO can still show recommendations, but it cannot place them on the pages visitors see. What gets deployed depends on the playbook and your settings. Common changes include page titles, meta descriptions, headings, on-page content updates, internal links, and structured data. Each item should show a clear status so you can tell a suggestion from a live change. - Suggested: OTTO found an opportunity, but nothing has been applied yet. - Approved: You accepted the change, and OTTO is ready to deploy it. - Deployed: OTTO has applied the change through the site installation. - Needs attention: The installation, page, or approval is blocking deployment. 🌐 Where changes appear on your website Deployed changes are meant to appear on the live page OTTO targeted, not only inside Search Atlas. Open that URL in a browser and review the element OTTO changed, such as the title in the browser tab, the meta description in the page source, a heading, body copy, or a new internal link. Check the public page rather than only your website editor. OTTO applies many updates at the point of delivery through its installation, so the original page in your CMS may look unchanged even when visitors receive the deployed version. 1. In OTTO, open the completed or deployed item and note the exact page URL. 2. Visit that URL in a private or incognito window so an old cached copy does not mislead you. 3. Compare the live element with the change described in OTTO. 4. If the page looks stale, refresh once, then allow a short delay for cache or CDN updates. Search engines do not show every update instantly. After OTTO deploys a change, Google and other engines still need to recrawl the page before rankings, snippets, or rich results reflect it. 📊 How to review what playbooks have done Use OTTO’s playbook and activity views for a breakdown of work so far. Open the site in Search Atlas, go to OTTO, and review each playbook that has run. A playbook groups related SEO actions, and its detail view should list the pages touched, the type of change, and whether each action was suggested, approved, or deployed. - Filter or sort by playbook to see one workflow at a time. - Open a deployed item to see the page, the before-and-after change, and its current status. - Use status filters to separate suggestions from changes already on the site. - Check the installation or connection status if many approved items are not deployed. That history is the source of truth for what OTTO has done. It is more reliable than judging progress only from the live website or from search results, which can lag behind deployment. 🛠️ If a result is missing Confirm four things before assuming the change failed: the OTTO installation is active, the item is approved rather than only suggested, the target URL is correct, and enough time has passed for cache to clear. Then recheck the page in a private window. If the status says deployed but the live page still does not match, note the playbook name, page URL, and change type before contacting support. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

Last updated on Oct 29, 2026

🔄 Fix the Cursor MCP Authorization Loop

🔁 What the authorization loop means The MCP CLI Proxy lets Cursor use Search Atlas through a secure sign-in. A normal connection opens the authorization page once, you approve access, and Cursor returns to work. A loop means that page keeps appearing and the connection never finishes. Your account and projects stay safe. The proxy is waiting for a completed approval that Cursor is not receiving. 🧭 Why the page keeps returning The loop usually comes from a sign-in that starts more than once, or from an approval that cannot return to Cursor. Common causes include: - Several authorization tabs or browser windows open at the same time - An old proxy session still running in the background - A browser popup, redirect, or localhost callback that was blocked - Saved sign-in data for a different Search Atlas account - An MCP entry in Cursor that was added again before the first approval finished 🛠️ Stop the loop and connect once 1. Close every authorization tab. Quit the browser window that the proxy opened, and leave Cursor open. 2. Stop the MCP CLI Proxy completely. If it is running in a terminal, end that process, then start it again only once. 3. In Cursor, open your MCP settings and remove the Search Atlas MCP entry. Do not add it back yet. 4. Restart Cursor so it drops the unfinished approval. 5. In the browser you use for sign-in, sign out of Search Atlas. If more than one account is saved, choose the account that owns the project before you continue. 6. Allow popups and redirects for that browser, and do not block localhost callbacks. Use one normal browser window, not a private window and not a second profile. 7. Start the MCP CLI Proxy one time. Add the Search Atlas MCP entry in Cursor again and approve the authorization page only once. 8. Wait on that page until it confirms the connection or closes on its own. Do not refresh it and do not open a second approval. ✅ Confirm the connection is stable The loop is fixed when the authorization page no longer returns and the Search Atlas MCP server shows as connected in Cursor. Send a simple request that you already use, such as asking for a project summary. A successful response means the approval was saved. If the page appears one more time immediately after approval, close it without signing in again and check Cursor first. Approving a second time can restart the loop. 🚫 What to avoid while reconnecting - Do not click the authorization link repeatedly - Do not keep an old proxy terminal running beside a new one - Do not sign in with a different Search Atlas account during the same attempt - Do not reinstall Cursor before trying the single clean approval above 💬 When to contact support If a single clean approval still returns you to the same page, tell us what you see: whether the page reloads by itself, whether Cursor shows a connection error, and whether the proxy was started more than once. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

Last updated on Oct 29, 2026

📊 Fix Google Ads Conversion Sync Issues

📊 Why conversions may not show in Ads If conversions are not appearing in the Ads area, Search Atlas is not receiving conversion data from the linked Google Ads account, or the events have not been matched to a campaign yet. This is usually a connection, permission, or tracking setup issue rather than a lost sale. New conversions can take up to 24 hours to appear. Check the date range in the Ads view before treating a delay as a failed sync. 🔍 Confirm the Google Ads connection Start with the account link, because an expired or incomplete connection stops all conversion data. 1. Open Integrations and select Google Ads. 2. Confirm the status shows Connected and that the correct Google account is listed. 3. If the status is disconnected or expired, select Reconnect and sign in with the Google user who manages the Ads account. 4. Choose the same Google Ads customer account that runs the campaigns you want to report on. 5. Return to the Ads area and refresh the page. If you manage more than one Google Ads account, verify you did not link a manager account without selecting the child account that owns the campaigns. ⚙️ Check conversion actions and permissions Search Atlas can only sync conversion actions that exist in Google Ads and that your Google user is allowed to view. - In Google Ads, open Goals and then Conversions and confirm the action is Active, not removed or paused. - Confirm the action records the event you expect, such as a purchase, lead, or phone call. - Make sure the Google user used for the connection has at least read access to that Ads account. - If a teammate recently changed account access, reconnect Google Ads so the new permissions are picked up. 🛠️ Review website tracking Google Ads must record the conversion before Search Atlas can display it. Use this checklist on the site that should send the event: - The Google tag or conversion tag is installed on the confirmation or thank-you page, or the event is sent through Google Tag Manager. - The tag fires only after the real conversion, not on every page load. - Auto-tagging is turned on in Google Ads so clicks can be tied to later conversions. - Consent or cookie settings are not blocking the tag for the visits you are testing. - The landing page domain matches the domain linked in Search Atlas. Complete one test conversion yourself, then wait for Google Ads to show it in that conversion action. If Google Ads does not show the test, the issue is on the website or in Google Ads, not in the Search Atlas sync. 🚀 Refresh the sync and compare totals After the connection and tags look correct: 1. Open the Ads area and set the date range to include the day of the test conversion. 2. Use Sync or Refresh data if that control is available. 3. Compare the conversion total in Search Atlas with the same conversion action and date range in Google Ads. 4. Allow up to 24 hours for late conversions and for Google to finish processing. Small differences can happen when Google Ads attributes a conversion to a different day than the click. Large gaps after 24 hours usually mean the wrong account, the wrong conversion action, or a broken tag. 💡 Common causes and quick fixes - Wrong account linked: reconnect and select the Ads account that owns the campaigns. - Expired Google access: reconnect the integration. - Conversion action inactive: turn it back on in Google Ads. - Tag missing on the success page: add or republish the tag, then retest. - Date range too narrow: expand the range to cover both the click and the conversion. - Brand-new setup: wait 24 hours after the first successful conversion. 💬 When to contact support Contact support if the correct Google Ads account is connected, the conversion appears in Google Ads, and it is still missing in Search Atlas after 24 hours. Include the Ads account name, the conversion action name, the date of the test, and a screenshot of the Google Ads total. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

Last updated on Oct 29, 2026

💳 Understanding and Removing OTTO SEO Top-Ups

💡 What an OTTO SEO top-up is An OTTO SEO top-up is an add-on on your Search Atlas subscription. It increases what your plan includes, such as extra site capacity, pages, or OTTO usage, and it is billed in addition to your base plan. A top-up can be a one-time purchase or a recurring add-on that renews with your billing cycle. Seeing a top-up does not always mean you currently have more than two active sites. The charge follows the add-on on the account, not only the sites you are using today. 📊 Why you may be charged when you use only two sites Extra OTTO SEO charges usually come from one of these situations: - A top-up is still active. Someone on the account added it earlier, and it keeps renewing even if you later removed sites or stopped using the extra capacity. - The top-up is not only for sites. Some add-ons cover pages, keywords, or OTTO actions. Two sites can still exceed the allowance included in your plan. - A site was connected, then removed. Removing a site from OTTO does not always cancel a purchased top-up. The add-on stays until it is turned off. - More than one workspace or user. A teammate may have bought the top-up on a shared billing account. - Timing of the invoice. A charge can be a renewal, a prorated add-on from mid-cycle, or a previous top-up that posted after you reduced usage. 🛠️ How to review the charge 1. Open your account Billing or subscription area and find the latest invoice. 2. Look for a line that mentions OTTO SEO and top-up, add-on, or extra capacity. Note the date, amount, and whether it is recurring. 3. In OTTO SEO, confirm how many sites are connected and whether any extra capacity is still assigned. 4. Check who has billing access. Ask teammates if they added a top-up. 5. Compare the invoice period with when you reduced usage. A charge inside a period you already paid for may be a renewal of an add-on that was still on. If the invoice line does not match any active add-on or any usage you recognize, treat it as a billing review, not as proof that you need more sites. ⚙️ How to remove a top-up 1. Go to Billing or your subscription settings and open active add-ons. 2. Select the OTTO SEO top-up you do not want. 3. Choose Remove or Cancel so it does not renew on the next cycle. 4. Confirm the change and check that the add-on shows as canceled or scheduled to end. 5. Keep a copy of the invoice and the date you canceled. Future invoices should no longer include that top-up after the current period ends. Canceling a top-up stops future renewals. It does not always refund a charge that has already been collected for the current period. Unused time and eligibility for a credit are reviewed case by case. 🚀 What to include if you want the charge reviewed Have these details ready so the review is faster: - The invoice date and the exact top-up amount - How many sites you actively use in OTTO SEO (for example, two) - Whether you or a teammate added the top-up - The date you removed extra sites or asked to cancel the add-on - What you want: stop future renewals, remove the add-on, or review a charge already posted Our team can confirm what the line item covers, remove an unwanted recurring top-up, and tell you whether that specific charge can be credited. Do not dispute the charge with your bank before we review it. A bank dispute can interrupt your subscription while the invoice is still open. 💬 Get help with a top-up If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

Last updated on Oct 29, 2026

💳 Clear a $180 Payment Request

💳 What the $180 payment request means A $180 payment request is a billing item on your Search Atlas account. It can be a subscription charge, an add-on, a plan change, or an unpaid invoice. Clearing it means the balance is paid or our billing team removes or adjusts the request after review. You cannot delete a valid charge from the invoice list yourself. 🔍 Check the charge before you pay Open your account billing area and review the request so you know exactly what you are clearing. 1. Sign in to Search Atlas. 2. Open Billing or Subscription from your account menu. 3. Find the open item for $180. 4. Note the date, plan or product name, and status (due, failed, or pending). 5. Compare it with your current plan and any recent upgrades. If the description matches your plan, pay it with the steps below. If the amount or product looks wrong, do not ignore it. Ask our team to review it before you pay. ✅ Pay the $180 request Use these steps when the charge is correct and you want to clear it by payment. 1. In Billing, open the unpaid $180 invoice or payment request. 2. Confirm the payment method on file. Update the card if it is expired or was declined. 3. Select Pay now or the equivalent pay action. 4. Wait for a success message. Refresh the billing page if the status does not change right away. 5. Download or save the receipt for your records. A successful payment should move the request from due or failed to paid. Access that was limited because of an unpaid balance is usually restored after the payment is confirmed. 🛠️ If payment failed A failed attempt leaves the $180 request open. Common causes are an expired card, insufficient funds, a bank decline, or a billing address that does not match the card. - Update the card or billing address, then try Pay now again. - Ask your bank to allow the charge, then retry. - Do not submit the payment many times in a row. Wait for one attempt to finish. 💡 Ask us to clear or adjust the request Contact our team when you were charged in error, you already paid, you cancelled before the billing date, or you need the $180 item removed. Have your account email, the invoice date, and a short reason ready. Our team can confirm whether the request can be cleared, credited, or left as a valid balance. We cannot promise a refund or removal in this article. Each request is reviewed against your plan and payment history. 📊 After the request is cleared - The billing page should show the item as paid, voided, or credited. - Keep the receipt or confirmation. - Check that your plan and renewal date look correct. - If the same $180 item appears again, contact our team with the new date so we can trace it. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

Last updated on Oct 29, 2026

🚀 Using Search Atlas OTTO on Replit

✅ What works on a Replit site Site audit, keyword research, competitor analysis, and rank tracking all work on a custom-coded Replit site. These tools look at your public domain and search data. They do not need WordPress or any other CMS. Search Console and Analytics connections also work normally. You connect the Google account that owns the property for your live site. The platform reads that data the same way it does for any other website. 🛠️ Install OTTO without a CMS Yes. OTTO can be installed on a non-CMS site. You add the OTTO script to the HTML that visitors receive. No plugin is required. 1. In Search Atlas, open the project for your live site and copy the OTTO installation script. 2. In Replit, open the file that builds the public page head. A simple HTML app usually uses index.html. A React-style app usually uses the main template, such as public/index.html. 3. Paste the script inside the head tag so it loads on every public page you want OTTO to manage. 4. Deploy or republish the Repl. The script must be on the live URL, not only in the editor preview. 5. Return to Search Atlas and confirm that OTTO detects the script on that URL. 📌 Replit details that matter - Track the production address visitors use, including a custom domain if that is your public site. - Keep the site publicly reachable. Private or password-protected Repls cannot be crawled or audited. - Put the script in HTML that is sent with the page. If your app is fully client-side, still include it in the main HTML template. - Republish after code changes so the script stays in the live build. - Connect Search Console and Analytics to the same verified property as the URL in your project. 💡 Is a Replit site a headache No. Research, audits, competitor analysis, and rank tracking feel the same as on any other site. The only extra step versus a CMS is placing the script in your code and republishing. After OTTO detects it, recommendations apply to your live pages like any other website. If a page is not detected, check that it is public, that the script is in the live HTML, and that you republished the latest version. 💬 Need a hand If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

Last updated on Oct 29, 2026

📊 Expectations When SEO Results Lag

📉 Why results can look small SEO is not instant. Following OTTO recommendations is the right start, but Google still has to recrawl pages, reassess quality, and compare you with stronger competitors. Flat average position with fewer clicks often means rankings did not move enough to earn more traffic, or that fewer people searched those queries. Small early gains are normal, especially on competitive finance topics such as loans and credit. A useful check is 8 to 12 weeks after meaningful changes go live. Look at impressions, clicks, average position, and indexed pages together. One flat metric does not mean the work failed. ⏱️ What to realistically expect Most sites should expect gradual movement, not a sudden jump. Reasonable signs of progress include more pages indexed, steadier impressions, and small position gains on a subset of queries. Large click growth usually follows only after several pages move into stronger positions for queries people actually search. - Weeks 2 to 6: crawl and index changes, title and content updates reflected in search. - Weeks 6 to 12: early position movement on less competitive pages. - 3 to 6 months: clearer traffic trends if technical issues, content, and authority all improve. Finance sites often move slower because trust, regulation, and established competitors raise the bar. OTTO cannot guarantee rankings or a specific click increase. 🚀 OTTO actions with the biggest impact Not every recommendation moves results equally. Prioritize items that help Google understand and trust the page, then items that make the page more relevant for a clear query. 1. Indexing and technical health: fix blocked pages, broken links, slow templates, and missing canonical or sitemap coverage so important URLs can rank. 2. Search intent match: one primary topic per page, with titles and headings that match how people search. 3. Title and meta improvements: clearer titles can lift clicks even when position is flat. 4. On-page depth: answer the query fully, add unique proof, and remove thin or duplicate copy. 5. Internal links: point relevant pages to the URLs you most want to rank. Low-priority wording tweaks matter less than indexation, intent, and internal linking. Complete high-impact OTTO tasks first, then republish and request a fresh look at those URLs in the platform. 🛠️ What to do beyond on-page fixes On-page work is necessary but rarely enough on its own. If clicks are down and position is flat, widen the plan: - Query focus: target fewer, more realistic keywords instead of competing head terms immediately. - Content gaps: add pages for questions competitors rank for that you do not cover. - Authority: earn relevant mentions and links from real industry or local sources. Avoid paid link schemes. - Experience signals: improve speed, mobile layout, and page clarity so visitors stay. - Measurement: compare the same date ranges, separate brand and non-brand queries, and note seasonality. For sites such as goloans.ca and creditpulse.ca, treat each domain separately. Different templates, content depth, and link profiles will not move on the same schedule. 📝 What a written site review covers A useful written review is a snapshot, not a promise of rankings. It should state what is working, what is blocking progress, and what to do next. For each site, the review should cover index coverage, whether priority pages match search intent, title and content quality, internal linking, obvious technical issues, and which OTTO tasks are still open. It should also explain the traffic picture in plain language: if average position is flat, clicks will usually stay flat or fall when search demand dips. The review should name the next three actions with the largest likely impact and a timeframe to recheck results. Search Atlas does not publish private audit findings for a specific domain inside a general help article. Share both domains, the date range you are viewing, and screenshots of clicks and average position so the review matches your data. ✅ How to use the review Implement the top three actions, wait for recrawl, and compare the next 4 to 8 weeks with the prior period. Judge success by indexed priority pages, impression growth, and position on target queries, not by one week of clicks. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

Last updated on Oct 29, 2026

🚀 Connect OTTO Pixel on Vercel

🔗 Yes, Vercel sites can use OTTO You do not need a traditional CMS to use Search Atlas. Vercel hosts the front end of your site, and the OTTO pixel is a small script that can run on any public page you control. Once the script loads on your live pages, OTTO can read on-page signals and surface recommendations inside Search Atlas. A CMS connection is only one installation path. For Vercel, install the pixel in your site code or through your tag setup, then publish a new deployment so the script is on the live domain. 🛠️ Add the pixel to your Vercel project 1. In Search Atlas, open your project and copy the OTTO pixel snippet from the installation or pixel section. 2. In your Vercel project, add that snippet to the shared layout or document head so it loads on every public page you want OTTO to review. For a Next.js app, place it in the root layout or _document equivalent for your framework version. 3. Do not place the pixel only on a draft, preview, or password-protected page. OTTO needs the public production URL. 4. Commit the change and deploy to production in Vercel. Preview deployments are useful for testing, but confirm the script is also present on the production domain. 5. Open the live site, view the page source or use your browser developer tools, and confirm the OTTO script is present. 6. Return to Search Atlas and check that the pixel shows as connected or receiving data. Allow a short delay after the first production deploy before you recheck. If your site uses a consent banner, allow the pixel according to your privacy policy and regional rules. Blocking the script in production will stop OTTO from collecting page data. ✅ Confirm the connection before local work - The pixel appears on your homepage and on key service or location pages. - The domain in Search Atlas matches the live Vercel domain, including www or non-www. - Important pages are indexable and not blocked by a noindex tag or robots rule. - Your project in Search Atlas lists the correct business name, address, phone number, and service area. A connected pixel does not by itself raise local rankings. It lets OTTO guide on-site fixes. Local visibility also depends on your business profile, citations, reviews, and location pages. 📍 Next steps that support local rankings 1. Claim and complete your Google Business Profile. Use the same business name, address, and phone number as your website. Add categories, hours, services, photos, and a link to your live site. 2. Keep your name, address, and phone consistent. Match that information on your site footer, contact page, and major directories. Small differences can weaken local trust. 3. Publish a clear location or service-area page. Include the city or region you serve, your services, a short proof of local experience, and a visible call to action. Link to it from the main navigation or footer. 4. Add local signals on existing pages. Mention the areas you serve in natural language, add unique copy for each location if you have more than one, and avoid copying the same page for every city. 5. Ask recent customers for reviews. Respond to reviews on your Google Business Profile. Reviews are a strong local signal and also help click-through. 6. Build or correct core citations. List the business on relevant directories with the same name, address, phone, and website. Fix duplicates instead of creating more listings. 7. Apply OTTO recommendations. After the pixel is connected, review titles, headings, content gaps, internal links, and technical issues inside Search Atlas. Prioritize pages that already target local services. 8. Make local pages fast and mobile-friendly. Vercel performance helps, but large images, blocked scripts, and layout issues can still hurt engagement. Check your key pages on a phone. 📊 What to expect after you publish On-site fixes can be deployed quickly through Vercel, but local ranking changes usually take time. Google needs to recrawl your pages, and profile or citation updates are not instant. Track impressions and calls from your Google Business Profile, plus rankings and OTTO task progress in Search Atlas, rather than judging results from a single day. Revisit OTTO after each production deploy if you change templates, routes, or consent settings. A new layout can drop the pixel from some pages even when the homepage still looks correct. 💬 When to contact support If the pixel is in your production deployment and still does not connect, or if you are unsure which local tasks to do first, If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

Last updated on Oct 29, 2026

🔍 Why OTTO Meta Differs From Shopify

📌 What customers usually see You update a meta description in OTTO for a Shopify page, such as a collection, but the same text does not appear in Shopify admin. Viewing the page source may also show no meta description. That does not mean the update failed. OTTO and Shopify store and display SEO fields in different places. ⚙️ Why Shopify admin stays unchanged Shopify admin shows the SEO title and description saved in Shopify itself. OTTO does not replace those Shopify fields when it publishes an overlay. Your store backend can keep the old text, or show a blank field, while OTTO serves a different description on the live site. - Shopify admin is the store’s own saved SEO data. - OTTO applies its approved meta data through the Search Atlas overlay on the public page. - Editing one place does not automatically copy the text into the other. 🔍 Why page source can look empty View page source shows the HTML sent by Shopify before scripts finish running. OTTO adds its meta description in the browser after the page loads, so that raw source often will not include it. This is expected for an overlay and is not proof that the description is missing. 📍 Where the description sits The live description sits in the page after OTTO’s script runs, not in the Shopify SEO box and not always in the initial source. It is tied to the URL you optimized in OTTO, such as a collection URL. If the page is cached, a theme app changes head tags, or the OTTO script is blocked, the overlay may not appear until that issue is fixed. ✅ How to confirm it is live 1. Open the exact public URL you updated in OTTO, not a preview inside Shopify admin. 2. Hard-refresh the page so you are not looking at an old cached copy. 3. Right-click the page, choose Inspect, and search the Elements panel for meta name="description". 4. Compare that content with the description saved in OTTO. A match means the overlay is active. 5. Ignore the Shopify SEO field unless you intentionally want Shopify’s own stored value to match. Search engines that execute the page can read the rendered description. A raw source check alone is not a reliable test. 🛠️ Keep the two sources consistent - Treat OTTO as the source of truth for pages it manages. - Do not expect Shopify admin to mirror OTTO automatically. - Avoid putting a conflicting description in Shopify if you want one clear message. - Confirm the OTTO installation is present on the theme and that cookie or script blockers are not stopping it. - Recheck after theme changes, app changes, or cache clears. 💬 When to contact support If Inspect still shows no OTTO description after a hard refresh, the script may not be loading on that template. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

Last updated on Oct 29, 2026

📉 How to Reduce OTTO SEO Licenses

📌 What reducing OTTO licenses means Each OTTO SEO license covers one website. If you currently have 17 licenses and only need 15, you must stop using OTTO on two sites first, then lower the license quantity on your subscription. The platform will not reduce the paid count while more sites are still using OTTO than your new total allows. ✅ Check your current usage Before you change billing, confirm which sites should keep OTTO. 1. Open OTTO SEO from the main platform menu. 2. Review the list of sites with OTTO installed or active. 3. Count the active sites and decide which two you want to remove so you end at 15. 4. Make sure you are signed in as an account owner or a user who can manage billing and sites. 🗑️ Remove OTTO from sites you no longer need Remove OTTO from each extra site before you lower the license count. 1. In OTTO SEO, open the site you want to remove. 2. Go to that site’s OTTO settings. 3. Choose the option to remove, uninstall, or deactivate OTTO for that site. 4. Confirm the removal when prompted. 5. Repeat for every extra site until the number of active OTTO sites is 15 or fewer. Removing OTTO stops new OTTO work on that site. It does not delete the website from your account, and it does not automatically change your bill until you update the license quantity. 📉 Lower the license quantity 1. Open your account or billing area from the platform menu. 2. Find the OTTO SEO subscription and the current site license quantity. 3. Edit the quantity and set it to 15, or to the lower number you need. 4. Review the updated total and confirm the change. 5. Return to OTTO SEO and confirm the active site count matches the new license total. If the quantity field will not go below your current active sites, one or more sites still have OTTO assigned. Remove those sites first, refresh the page, and try again. 💡 What to expect after the change - The sites you kept continue to use OTTO as before. - Removed sites no longer consume a license. - Your subscription should show the new quantity after you confirm it. - Billing changes follow your current plan terms. The next invoice reflects the lower quantity; this article cannot promise a specific refund or proration amount. 🛠️ If the count still will not decrease - Refresh OTTO SEO and recount active sites. Pending or recently removed sites may still appear until the page reloads. - Check that you removed OTTO from the site itself, not only archived a project or hidden it from a view. - Confirm no other team member reinstalled OTTO while you were editing billing. - Try the change again in a private browser window if the old quantity remains on screen. - If you need fewer licenses than the minimum shown for your plan, the plan itself may need a change rather than a quantity edit. 💬 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 instantly connected with a member of our team.

Last updated on Oct 29, 2026

⚙️ Using OTTO on Custom Replit Sites

✅ What works on a custom Replit site Search Atlas and OTTO work on a custom-coded Replit website when the live site is public, uses a stable URL, and can be crawled. Audits, rank tracking, Google Search Console, and Google Analytics do not require WordPress or another CMS. They use your live domain and the accounts you connect. OTTO can review the site and recommend fixes. On a custom Replit project there is no CMS connector that writes those fixes into your code and republishes them for you. You apply approved changes in Replit, then publish the project as you normally do. 📊 Audits, rank tracking, and Google data Add the production domain, not a private editor preview, as the project website. Then connect the matching properties: - Site audit: OTTO crawls public pages, status codes, titles, meta descriptions, headings, links, indexation signals, and page speed signals it can see from the live response. - Rank tracking: Tracking follows the keywords and locations you set. It does not depend on how the site was coded. - Google Search Console: Connect the property that exactly matches the live domain, including https and www or non-www. - Google Analytics: Connect the property that already receives traffic from that same domain. If Google cannot see the site, OTTO cannot use that data either. Confirm the Replit deployment is public, the custom domain points to it, and the live pages are not blocked by a login, noindex, or a disallow rule in robots.txt. 🛠️ Install the OTTO pixel The pixel is a small script you place in the site code. Add it to the shared HTML head or layout so it loads on every public page, including pages you add later. Do not place it only on the homepage. 1. Open the pixel installation instructions inside your Search Atlas project and copy the script. 2. In Replit, open the shared layout, head partial, or base HTML file used by all pages. 3. Paste the script inside the head, before the closing head tag, and publish the site. 4. Open a few live pages and confirm the pixel shows as detected in Search Atlas. Check both the homepage and an inner page. If your app is a single-page app, the script must remain present after client-side route changes. Putting it in the root HTML file usually covers that. A preview URL that changes on every run is not a reliable installation target. 💡 JavaScript content and what OTTO can see Content that exists in the initial HTML is the safest content for audits and search engines. If titles, descriptions, headings, or body copy appear only after JavaScript runs, OTTO and Google may see a thin or empty page. - Keep the title, meta description, canonical tag, H1, and main copy in the server response whenever you can. - Use one public URL per page, and keep that URL stable after you republish. - Avoid blocking CSS, JavaScript, or important routes in robots.txt. - If the site is fully client-rendered, use server rendering or a prerendered HTML response for the pages you want indexed. 🚀 Automatic recommendations versus manual fixes OTTO still generates recommendations for a custom site. The difference is deployment. - Automatic on supported CMS connections: approved fixes can be published by the connector. - Manual on custom Replit sites: you copy the recommended title, meta description, heading, content, schema, or internal link into the relevant file, template, or route, then publish from Replit. Treat OTTO as the source of the change, and your Replit repo as the place the change is saved. After publishing, request a fresh crawl or wait for the next audit so Search Atlas can confirm the live page changed. 📝 Publishing new pages without a headache OTTO does not create or upload new Replit pages for you. You add the route or file in the project, publish it, and make sure it is linked and indexable. A simple template keeps this predictable: 1. Duplicate an existing page template that already contains the pixel, title, meta description, canonical, and H1. 2. Write the new copy and publish the deployment. 3. Add an internal link from a related page already in the site. 4. Include the URL in your XML sitemap if you maintain one. 5. Submit or let Search Console discover the URL, then check it in the next OTTO audit. New pages are not harder because the site is on Replit. They become difficult only when each page is hand-built differently, the URL changes after every deploy, or the content never appears in the HTML response. 🔍 Quick checklist - The production site is public on the final domain. - Search Console and Analytics properties match that domain. - The pixel is in the shared head and detected on inner pages. - Important content is in the HTML, not only injected by JavaScript. - Approved OTTO fixes are applied in Replit and republished by you. - New pages reuse one template, stay linked, and keep stable URLs. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

Last updated on Oct 29, 2026

🔍 Verify OTTO Schema and Link Deployment

🔍 What this article covers After OTTO deploys schema and internal links, you can confirm the change on the live site and in the project. This guide explains how to check a deployment (for example on your own domain), why markup may not show in raw source, and what happens to deployed content when a project is unbound. ⚙️ Check status inside the project Open the site project in Search Atlas and go to OTTO. Review the deployment or changes list for the page you updated. - A Deployed or equivalent completed status means OTTO finished sending that change. - Pending, failed, or paused items are not live yet. Open the item for the error or wait until the status completes. - Confirm the target URL matches the page you are checking, including https, www, and trailing slash. - Confirm the OTTO installation (pixel or supported integration) is still connected for that domain. 📄 Confirm schema on the live page OTTO often adds schema through its installed script, so it appears in the rendered page, not always in the server’s raw HTML. 1. Open the exact deployed URL in a private window so cached pages do not mislead you. 2. View the rendered page (browser developer tools, Elements panel) and search for application/ld+json or the schema type OTTO added. 3. If you only use View Source, the block may be missing even when deployment succeeded. Check the rendered DOM before treating it as a failure. 4. Hard-refresh the page. If a CDN or cache plugin is active, purge that URL and check again. 5. Optional: test the same URL in Google’s Rich Results Test. Processing can lag behind a successful deploy. Schema that is missing from both the rendered page and a completed OTTO status usually means the install is absent, blocked, or the change targeted a different URL. 🔗 Find the deployed internal link Internal links are placed in the page body or in an OTTO-managed block, depending on the recommendation. - On the live URL, use the browser Find tool for the anchor text or destination path OTTO listed. - Search the rendered HTML, not only the CMS editor. Links injected by the script will not appear as a saved CMS edit. - Check the same URL variant you deployed. A www and non-www page are different targets. - Give caches a few minutes, then recheck. A failed or rolled-back item will not show the link. 🧹 If schema or the link is still missing - Recheck that OTTO shows the item as deployed for that exact URL. - Confirm the OTTO script loads on the page and is not blocked by consent tools, ad blockers, or a firewall. - Purge CDN, server, and plugin caches for the URL. - Compare the public page with the page OTTO edited. Drafts and noindex duplicates will not match. - Redeploy the item from OTTO if status is failed or the install was fixed after the first attempt. 📦 Unbinding a project Unbinding or disconnecting the project stops OTTO from serving its injected changes. Schema and internal links that exist only through the OTTO installation are removed from the live page. That is expected, not a partial rollback of your CMS history. - Content OTTO injected via the script disappears after the project is unbound and the script no longer runs. - Copy you manually saved in the CMS stays unless you delete it yourself. - Rebinding and redeploying is required to publish those OTTO changes again. - Search engines may keep an old cached copy until they recrawl the URL. 💬 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 instantly connected with a member of our team.

Last updated on Oct 29, 2026

🚀 Fix a Stuck Press Release Step 1 Button

📌 What this article covers If you filled out step 1 of Buy Press Release and still cannot move to step 2, the continue control is usually disabled because a required field is empty, invalid, or not saved. This article shows how to find the blocker and move forward. ✅ Why the button stays stuck Step 1 does not advance until every required item passes validation. The button can look unavailable even when the form appears complete. Common causes include: - A required field is blank, including fields below the visible area of the page. - A website, email, or phone value is not in a valid format. - Text is shorter or longer than the allowed limit. - A required choice, such as a category or distribution option, was not selected. - A checkbox for terms or confirmation is still unchecked. - An edit was typed but the field was not left, so the value did not register. - The page is outdated after a long session or a browser extension is blocking the form. 🛠️ How to unlock step 2 1. Stay on step 1 and scroll from the top of the form to the bottom. 2. Look for red text, highlighted borders, or helper messages under each field. 3. Fill every field marked required. Do not leave placeholders in place of real details. 4. Check links start with https://, emails include an @ symbol and a domain, and phone numbers use only the expected characters. 5. Click or tab out of the last field you edited so the entry is saved. 6. Select any required category, location, or distribution option, then confirm any required checkbox. 7. When every item is valid, the continue or next control should become available. Select it to open step 2. 🔄 If it is still disabled - Refresh the page once, then review step 1 again before re-entering missing details. - Try a private or incognito window, or another supported browser, with extensions turned off. - Clear only this site’s cache if the form looks frozen, then sign in again. - Avoid clicking the button repeatedly while the page is still loading. - If you use autofill, replace any incomplete company, contact, or address values manually. 💡 Before you contact support Note which fields you completed, the exact button label, and whether any error text appears. A screenshot of the full step 1 form helps a teammate see what is blocking the next step. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

Last updated on Oct 29, 2026

🚀 How OTTO Deploys Playbook Suggestions

💡 What OTTO does with suggestions OTTO reviews your site and builds suggestions inside SEO playbooks. A suggestion is a recommended change, such as a title, meta description, heading, internal link, or other on-page improvement. Making a suggestion does not change your live site by itself. The change goes live only after it is deployed. Think of suggestions as a draft plan. Deployment is the step that applies the approved work. ⚙️ How deployment works You stay in control of what is published. For each playbook you can: - Review the suggested changes before anything is applied. - Deploy the items you want OTTO to implement. - Leave other suggestions undeployed so they stay as recommendations only. If deployment or autopilot is turned on for a playbook, OTTO can apply the changes that playbook is allowed to publish. If it is off, OTTO will keep showing suggestions and wait for you to deploy them. Only deployed items should appear on the live site. 📊 Where to see playbook results Open OTTO in your project, then open the playbook you want to check. The playbook view is the breakdown of what OTTO has done. Use it to see: - Which suggestions were created - Which items are deployed, pending, or not deployed - The pages or URLs included in that playbook - The type of change OTTO recommended or applied Review one playbook at a time if you want a clear record of that playbook’s work. Deployed items are the visible results. Undeployed items are still suggestions only. 🔍 How to confirm results on your site 1. Open the playbook and note the pages marked as deployed. 2. Open one of those pages on your live site. 3. Compare the live element, such as the title or description, with the change shown in the playbook. 4. Allow a short time for the site and any cache to refresh if the update is not visible immediately. If a suggestion still shows as not deployed, OTTO has not applied it yet. Deploy that item, or enable deployment for the playbook, and check the status again. 🛠️ If the breakdown does not match what you expected Confirm that the correct project and playbook are open, and that the items you care about show a deployed status. Then recheck the matching live URL. A suggestion that was never deployed will not show as a live change. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

Last updated on Oct 29, 2026

📉 How to Review an Organic Traffic Drop

📉 What this review covers An organic traffic drop review looks at whether fewer people are finding your site in unpaid search, which pages changed, and which actions are most likely to help next. It is not a promise of rankings or a fixed timeline. Results depend on competition, search demand, site history, and how completely recommendations are implemented. If you manage more than one site, review each property on its own. Two domains can share a topic and still have very different authority, content depth, and technical health. 📊 Check the drop before changing strategy Start with a clear picture of what changed so you do not treat a normal fluctuation as a sitewide problem. - Compare the same date ranges and note seasonality, holidays, or campaign pauses. - Separate branded and non-branded queries. A brand dip and a content dip need different fixes. - See whether the loss is sitewide or limited to a few URLs, folders, or topics. - Check impressions, average position, and click-through rate together. Fewer clicks with stable impressions often points to titles and snippets. Fewer impressions often points to rankings, indexing, or demand. - Confirm important pages are still indexed and that recent redirects, noindex tags, or template changes did not remove them from search. 🎯 Set realistic expectations At an early or recovery stage, the first signs of progress are usually cleaner indexing, more relevant impressions, and better positions on priority queries. Meaningful traffic growth often follows later, commonly over several weeks to a few months after changes are live and recrawled. - Near term: priority pages are indexed, recommendations are deployed, and impression trends stabilize. - Medium term: target queries move closer to competitive positions and click-through rate improves. - Later: traffic and leads grow if content, internal links, and site authority support those pages. On-page fixes alone rarely overcome stronger competitors. Expect the largest gains on pages that already earn impressions or sit just outside strong ranking positions, not on every URL at once. ⚙️ Prioritize OTTO actions by impact Use OTTO to fix the highest-confidence issues on pages that already get impressions or support your main services. Work in this order: 1. Indexing and technical blockers: resolve issues that stop important pages from being crawled or indexed. 2. Priority URLs: update titles, headings, and on-page copy so they clearly match the query and the page offer. 3. Click-through rate: improve titles and meta descriptions on pages with impressions but weak clicks. 4. Internal links: point relevant pages to your most important URLs with clear anchor text. 5. Supporting content: fill gaps where searchers need an answer your site does not yet cover well. Deploy a focused batch, then wait for recrawling before judging results. Changing every page at once makes it harder to see what helped. 🚀 Go beyond on-page fixes After OTTO on-page work is in place, strengthen the pages that should earn traffic: - Match search intent with useful, specific content rather than repeating the same keywords. - Improve page experience, including speed, mobile layout, and clear calls to action. - Build topical depth with supporting articles that link to core service or product pages. - Earn relevant mentions and links through useful resources, partnerships, and digital PR. Avoid paid or spam link schemes. - Track leads or conversions, not rankings alone, so you invest in pages that create business value. 📝 Request a written account review You can ask a teammate to review your account, explain which OTTO actions matter most right now, and outline realistic next steps. Include the domain for each site, the date the drop started, your main goal, and the pages or queries you care about most. A useful written review summarizes findings, priority actions, and what to expect. It will not guarantee positions or traffic. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

Last updated on Oct 29, 2026

🔍 Fix OTTO Not Connected on Static HTML

🔍 Why OTTO still shows not connected OTTO only shows as connected after it can load its script on the live public page for the domain in your project. Pasting the script into a local index.html file is not enough if that file is not the page visitors (and OTTO) actually open. A not-connected status usually means the script is missing from the served HTML, blocked before it runs, or present on a different URL than the one being checked. 📄 Place the script on the page that is served 1. In Search Atlas, open your OTTO project and copy the install script exactly as shown. Do not rewrite or shorten it. 2. Open the HTML file that your host serves for the site root. On many static sites that file is index.html, but your host may use another file or a build output folder. 3. Paste the script inside the head of that file, before the closing head tag. Keep it on its own so it is easy to find later. 4. Save, then publish or deploy the site. Editing a copy on your computer does not update the live site until you upload or redeploy. 5. Open the exact domain from your OTTO project in a browser, including the correct www or non-www version and https. If your site is generated from a template or build step, add the script to the source template and rebuild. Putting it only in a local preview file will not connect OTTO. 🛠️ What to look for in Inspect On the live homepage, right-click the page and choose Inspect (or View Page Source). Check these items in order: - Elements or Page Source: Search for the OTTO script. You should see the same script tag you copied, inside the head of the HTML that the browser received. If it is missing, the live file was not updated. - Network: Reload the page, filter by the script name or by JS, and find the OTTO script request. A successful load shows status 200. Status 404 means the address is wrong or the file was changed. (blocked) or a failed request means a browser extension, firewall, or content rule stopped it. - Console: Look for red errors that mention the OTTO script, a blocked request, or a content-security-policy violation. Those errors explain why the tag is present but OTTO still stays disconnected. - Correct page: Confirm the address bar matches the domain in OTTO. A script on index.html for one domain will not connect a project set to another domain or to a page you have not published. View Page Source shows the HTML from the server. The Elements panel can also show changes made by other scripts. If the tag is only in Elements and not in Page Source, another tool injected it after load, which is not a reliable install. ⚙️ Common reasons a static site stays disconnected - The script was saved locally but never uploaded to the host or redeployed from your static-site builder. - You edited index.html in the project folder, while the host serves a built copy from a dist, public, or build folder. - The tag sits in the body, is commented out, or was split across lines so the browser cannot read it. - An old cached copy is still being served. Hard-refresh the page, then purge your host or CDN cache and check again in a private window. - An ad blocker or privacy extension blocks the script. Test in a private window with extensions off. - A content security policy on the host allows only approved script sources, so the browser refuses the OTTO file. - The project domain uses www and the live site does not, or the opposite. Match the domain exactly. ✅ Confirm the connection 1. Reload the live homepage after the deploy and cache clear. 2. In Inspect, confirm the script is in the served head and its network request returns 200 with no console error. 3. Return to OTTO and refresh the installation or connection status. 4. Wait a short time and check again. Posting and other OTTO actions stay unavailable until the status shows connected. Once the script loads on the live domain, content actions that were blocked by the not-connected state can run. If posting still fails after the status is connected, note the exact page URL and the error on screen before you contact support. 💬 Get help in the platform If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

Last updated on Oct 29, 2026

🛠️ Fix a Duplicate OTTO Pixel

🔍 What a duplicate OTTO Pixel means OTTO Pixel should load once on each page. A duplicate warning means OTTO found more than one installation, usually because the pixel was added through both a website plugin and a manual code snippet, or through multiple tools such as Google Tag Manager and a theme file. The warning can prevent OTTO from working correctly, even when the pixel is not visible in the page content. Pixel code usually runs in the page source or through a tag manager. 🧭 Find all OTTO Pixel installations 1. Open the affected website in an incognito browser window. 2. Right-click the page and select View page source, then search for OTTO or the OTTO Pixel ID. 3. Use your browser’s developer tools and open the Network tab. Reload the page and search for requests containing OTTO. 4. Check common installation locations: the website’s SEO or marketing plugin, the theme header or footer, Google Tag Manager, and any custom code or scripts added by your hosting provider. 🧹 Remove the extra installation Keep one OTTO Pixel installation and remove every duplicate copy. The safest option is usually to keep the installation created through the recommended Search Atlas connection and remove manually added copies. - Disable the OTTO Pixel in any duplicate plugin or integration. - Remove duplicate code from the website header, footer, or theme files. - In Google Tag Manager, pause duplicate OTTO tags and publish the updated container. - Check staging, caching, and security tools that may inject the same script. Do not remove the only active pixel. If you are unsure which installation to keep, pause duplicates one at a time and check the result after each change. ✅ Confirm the pixel is working 1. Clear the website, CDN, and browser caches. 2. Open the website in a private browser window. 3. Reload a few pages and confirm that only one OTTO Pixel request appears in the browser’s Network tab. 4. Return to Search Atlas and check the OTTO Pixel status after the website has been crawled or the status has refreshed. Cookie consent tools may delay the pixel until visitors accept marketing or analytics cookies. Test with consent enabled when validating the installation. 💬 Get help with a persistent warning If the duplicate warning remains after removing extra installations, check whether your cache is serving an older version of the site or whether a tag manager container is still publishing 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 instantly connected with a member of our team.

Last updated on Oct 29, 2026

📉 Expectations When Organic Traffic Declines

📉 Why clicks can fall while position stays flat A drop in weekly clicks with a steady average position is common. Average position near 30 means most queries still sit around page three, where small changes in the results page can cut clicks without moving the average much. Clicks can fall when impressions drop, when click-through rate falls, or when more of the traffic mix comes from lower-intent queries. Seasonality, new competitor pages, ads, and extra result features (such as maps or answer boxes) often explain the change. One or two weeks of data is not enough to call a trend. An OTTO SEO score and a partial deploy also do not promise a traffic rebound. If only part of the issue list is live, many fixes are still waiting. The score measures site health, not guaranteed clicks. ⏱️ What results you should realistically expect Set expectations against where the site ranks today, not against a full recovery in the next report. - Indexing lag: After a fix is deployed, Google still has to crawl and refresh the page. Many changes show in data over 2 to 8 weeks. Competitive terms can take longer. - Partial deploys: If roughly a third of issues are deployed, treat results as early, not final. Finish the high-impact items before judging OTTO. - Position still outside the top 10: Most clicks go to the first page. Holding an average near 30 usually means on-page cleanup alone will not restore a large share of lost clicks. - Week-to-week noise: A swing of a few hundred clicks can be normal. Compare at least 4 to 8 weeks, and the same period last year if you have it. A realistic near-term goal is healthier pages, more of the right URLs indexed, and a slow move of important queries toward the first two pages. A full return to a prior click peak is not guaranteed. 🚀 OTTO actions with the biggest impact Not every open issue moves traffic. Work in this order: 1. Index and crawl blockers: Wrong canonicals, noindex tags, robots rules, soft 404s, and sitemap gaps. If Google cannot keep the right URL, other fixes will not show. 2. Titles and descriptions on pages that already get impressions: These can lift click-through rate without a ranking jump. Match the wording to the query and the page promise. 3. Internal links to priority pages: Point relevant pages to the URLs you want to rank, using clear anchor text. 4. Thin or off-intent content on money pages: Expand pages that rank but do not answer the search. This matters more than polishing pages with almost no impressions. 5. Speed and mobile issues only when they are clearly poor: Large gains help users and crawling. Tiny score tweaks rarely restore hundreds of clicks. Lower priority for a traffic drop: minor image text, small heading edits, and schema on pages that barely appear in search. Schema can help eligibility for rich results, but it is rarely the main reason clicks fell. 🛠️ What to do beyond on-page fixes Use Google Search Console for the same property and date range as the drop. - Split impressions from clicks and average position. If impressions fell, demand or coverage changed. If only clicks fell, look at titles and the results page. - List the queries and pages that lost the most clicks. Fix or expand those URLs first. - Check coverage, manual actions, and page experience so a technical problem is not hiding under the OTTO list. - Compare branded and non-branded queries. A brand dip and a rankings dip need different work. - Review competitors in the live results for your top lost queries. If they answer the question more clearly, add that depth. - Build authority with relevant links and mentions. On-page work cannot replace trust on competitive terms. - Confirm tracking: correct property, no sudden filter changes, and no removed pages or redirects that dropped URLs out of the index. 📝 What a written review of your sites covers A useful review is a short priority note, not a promise of recovered traffic. It should name both domains, the date range, clicks versus impressions versus position, how many OTTO issues are deployed versus still open, the pages that lost the most clicks, and the next five actions in order. Have this ready: both domain names, the Search Console date comparison, a note of any redesign or content cuts, and which OTTO projects are connected. We review what the data shows. We do not invent a ranking forecast from the SEO score alone. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

Last updated on Oct 29, 2026

🔄 How to Refresh Deployed OTTO SEO Edits

🔍 Why Updated Values May Not Appear Live When you edit OTTO SEO values on a page that is already deployed, the new values must be sent to your live site before visitors and search engines see them. If your live page still shows the old title, meta description, or H1, the most common causes are: - The edits were saved but never marked for deployment. - A previous deployment already sent these exact values, so the redeploy found nothing new and reported zero deployments. - The edits were made to a different page or URL than the one that is live. - A browser or CDN cache is still showing the previous version of the page. ✅ Before You Start Take a few minutes to confirm the basics. This avoids repeated redeploys that will not fix the problem. - Confirm you are working in the correct site, for example Illumination Consulting. - Confirm the page URL in OTTO SEO matches the live URL exactly, including the trailing slash and any subfolders. - Write down which other optimizations are active on that page so you can check them after the refresh. 🛠️ Steps to Refresh Deployed Edits 1. Open OTTO SEO for the correct site and locate the page you updated. 2. Check that the new title, meta description, and H1 appear in the edit view. 3. Look for any unsaved or pending change indicator. If one is present, save the changes first. 4. Start a new deployment for this page only. Limiting the deployment to one page keeps your other optimizations untouched. 5. Review the deployment result. A successful refresh should list the fields that were updated. ⚙️ Understanding a Zero-Deployment Result A result of zero deployments means the platform did not detect any new changes to send. This usually happens when the values were already deployed earlier, or when the edits were saved to a different page or version than the one you deployed. Running the same deployment again will not change the result. Instead, check the edit view and confirm the values you see there are the ones you intended to publish. 🔎 Confirm the Change Is Live Deployment and visibility are not always instant. Use these steps to verify the update: 1. Open the live page in a private or incognito browser window to avoid your own cached copy. 2. View the page source and check the title tag, the meta description tag, and the H1 heading. 3. If the old values still appear, clear your browser cache and wait a few minutes, since caching layers may take time to refresh. 4. If the values are correct in the source but not in search results, allow additional time, because search engines re-crawl pages on their own schedule. 🛡️ Protecting Your Other Optimizations Refreshing edits on one page should not change your other active optimizations on that page or on other pages. After each refresh, check the following: - Any other titles, descriptions, or headings you did not intend to change still show their expected values. - Pages you did not edit remain unchanged. - Your recent deployment history shows only the page and fields you meant to update. Keeping each refresh focused on one page at a time makes it easier to spot any unexpected changes quickly. 📊 Tips to Prevent Future Issues - Save and review every change before starting a deployment. - Use the deployment result to confirm the fields that were sent. - Verify the live page after each deployment rather than waiting for a support request. - Keep a simple log of major edits, including the date and the page URL. 💬 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 instantly connected with a member of our team.

Last updated on Oct 29, 2026