Home 🤖 OTTO SEO

🤖 OTTO SEO

Camilo Aponte
By Camilo Aponte
• 313 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 send your message. A member of our support team will reply in the chat.

Last updated on Nov 09, 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 send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 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 send your message. 💡 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 Nov 08, 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 send your message. 📝 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 Nov 08, 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 send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 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 send your message. A member of our support team will reply in the chat.

Last updated on Nov 09, 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 send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 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 send your message. 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 Nov 08, 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 send your message. 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 Nov 08, 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 send your message. ❓ 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 Nov 08, 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 send your message. 🚀 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 Nov 08, 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 send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 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 send your message. A member of our support team will reply in the chat. 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 Nov 09, 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 send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 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 send your message. A member of our support team will reply in the chat.

Last updated on Nov 09, 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 send your message. 💡 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 Nov 08, 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 send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 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 send your message. A member of our support team will reply in the chat. Let us know which sites you want to keep active, and we can help you align your plan.

Last updated on Nov 09, 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 send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 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 send your message. 💡 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 Nov 08, 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 send your message. A member of our support team will reply in the chat. 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 Nov 09, 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 send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 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 send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 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 send your message. A member of our support team will reply in the chat. Share the details above and we can walk you through exactly what the charge covers on your account.

Last updated on Nov 09, 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 send your message. A member of our support team will reply in the chat.

Last updated on Nov 09, 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 send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 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 send your message. 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 Nov 08, 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 send your message. A member of our support team will reply in the chat.

Last updated on Nov 09, 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 send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 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 send your message. A member of our support team will reply in the chat. 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 Nov 09, 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 send your message. A member of our support team will reply in the chat. 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 Nov 09, 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 send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 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 send your message. A member of our support team will reply in the chat. To help us resolve it faster, tell us the page URL, the suggestion text, and the name you want excluded.

Last updated on Nov 08, 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 send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 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 send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 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 send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 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 send your message. A member of our support team will reply in the chat.

Last updated on Nov 09, 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 send your message. ⏱️ 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 send your message. A member of our support team will reply in the chat.

Last updated on Nov 09, 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 send your message. A member of our support team will reply in the chat. Please include your homepage URL and a note that you suspect a hidden H1 so we can look into it faster.

Last updated on Nov 09, 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 send your message. A member of our support team will reply in the chat.

Last updated on Nov 09, 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. Send your message. 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 send your message. A member of our support team will reply in the chat.

Last updated on Nov 09, 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 send your message. A member of our support team will reply in the chat.

Last updated on Nov 09, 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 send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 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 send your message. A member of our support team will reply in the chat.

Last updated on Nov 09, 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 send your message. A member of our support team will reply in the chat.

Last updated on Nov 09, 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 send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 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 send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 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 send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 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 send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 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 send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 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 send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 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 send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 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 send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 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 send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 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 send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 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-upIf you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 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 send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 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 handIf you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 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 send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 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 send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 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 send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 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 helpIf you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 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 send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 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 helpIf you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 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 send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 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 send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 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 send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 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 platformIf you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 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 send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 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 send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 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 send your message. A member of our support team will reply in the chat.

Last updated on Nov 09, 2026

🔍 Checking OTTO Overlay Deployment and Rank Math Schema

🔍 Why Your Changes May Not Appear Live Content created with OTTO is applied to your live site through an overlay. If you have made changes but cannot see them on your published page, the deployment may not have completed, or your browser or site cache may be showing an older version. This article explains how to confirm the status of your deployment and how to avoid conflicts with Rank Math schema markup. ✅ How to Check Your OTTO Overlay Deployment 1. Log in to the Search Atlas platform and open OTTO. 2. Go to the page or content item you changed and review its deployment status. 3. Confirm the status shows as deployed or published. If it shows as pending, failed, or draft, select the option to deploy again and wait for the status to update. 4. Open the live page in a private or incognito browser window. This avoids seeing a cached copy from your own browser. 5. View the page source (right-click the page and choose View Page Source) and search for the OTTO overlay code. If it is present, the overlay is loading on the page. 6. If the overlay code is missing, check that the overlay is installed on your site and that the page URL you are viewing matches the URL you deployed to. 7. If your site uses a caching plugin or a content delivery network, clear the cache and check the page again. 🧩 Will Rank Math Schema Conflict With OTTO? Rank Math and OTTO can both add structured data (schema markup) to a page. When two tools output the same type of schema, search engines may see duplicate or conflicting information. This can lead to rich results being ignored or flagged with warnings in Google Search Console. Conflicts are most likely when: - Both Rank Math and OTTO add the same schema type, such as Article, Organization, or FAQ, to the same page. - Rank Math automatically generates schema for a page while OTTO also generates it for the same content. - Different business details, such as company name or logo, are entered in each tool. Conflicts are less likely when each schema type comes from only one source. 🛠️ How to Prevent or Fix Duplicate Schema 1. Decide which tool will manage each schema type. For example, you might let OTTO handle page-level content schema and let Rank Math handle site-wide organization details. 2. In Rank Math, review the schema settings for the affected post or page type and turn off any schema type that OTTO already provides. 3. Make sure business details such as name, logo, and contact information match across both tools. 4. Save your changes, then clear your site cache. 5. Re-deploy the OTTO content if you changed anything in the overlay. 🧪 How to Confirm Your Results 1. Copy the live page URL and run it through Google's Rich Results Test. 2. Check that each schema type appears only once in the results. 3. Look for any errors or warnings and update the matching settings in Rank Math or OTTO. 4. Allow a few days for search engines to recrawl the page before expecting changes in search results. 💡 Tips to Avoid Future Issues - Document which tool controls each schema type on your site. - Check the deployment status in OTTO after every content update. - Test important pages with the Rich Results Test after installing or updating Rank Math or OTTO. **💬 Getting Further HelpIf you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 2026

🔗 Connect Shopify to the OTTO Pixel

🔗 What this connection does Connecting Shopify to OTTO lets Search Atlas read your storefront through a small pixel that includes your site UUID. The full snippet must be saved in the published theme so it loads on your public pages. 📋 Before you start - Use a Shopify account that can edit theme code. - In Search Atlas, open your site in OTTO and copy the full installation snippet. Pasting only the UUID is not enough. - Edit the theme shoppers actually see, usually marked as the current or published theme. - Note the exact domain connected in Search Atlas, including https and www, so it matches the live store. 🛠️ Add the pixel in theme.liquid 1. In Shopify admin, go to Online Store, then Themes. 2. On the published theme, open the actions menu and choose Edit code. 3. Under Layout, open theme.liquid. 4. Find the closing head tag near the top of the file. 5. Paste the full OTTO snippet on its own lines just before that closing tag. 6. Select Save and confirm Shopify shows that the file saved. Do not place the snippet only in a product template, footer, or Custom Liquid section. Those areas do not load on every page and may not appear in the page head. 🔍 Check the live page source 1. Open your public homepage in a new browser tab. Do not check the Shopify admin or the theme editor canvas. 2. If the store is password protected, enter the password, then reload the homepage. 3. Right-click the page and choose View page source. Raw source is more reliable than the Elements panel. 4. Press Ctrl+F or Cmd+F and search for your UUID exactly as shown in Search Atlas. 5. Also search for otto. You should see the snippet you pasted. 6. If the page looks outdated, hard-refresh it or open it in a private window and check again. ⚠️ If the UUID is still missing - Wrong theme: The snippet may be in an unpublished or duplicate theme. Repeat the steps on the current theme. - UUID text only: A bare UUID in the head does not install OTTO. Replace it with the full snippet from Search Atlas. - Snippet outside the head: Move it so it sits before the closing head tag, not in the body or a section file. - Code was overwritten: A theme update, app, or restored backup can remove custom code. Open theme.liquid and confirm the snippet is still there. - Wrong URL: View source on the same domain connected in Search Atlas, including www versus non-www. - Cached page: Clear the browser cache or use a private window, then view source again. ✅ Finish the site connection 1. Return to the site in Search Atlas OTTO after the UUID is visible in the live source. 2. Run the connection or verification step shown for that site. 3. Allow a short time for the pixel to be detected, then refresh the OTTO status. 4. If it stays disconnected, confirm the domain spelling and that the snippet is on the homepage and at least one inner page. **💬 Still need helpIf you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 2026

🧹 Clear a Stale OTTO Brand Cache

🧹 Why OTTO still shows old brand text OTTO keeps brand context from earlier crawls so suggestions stay on brand. After a rebrand or a content change, that stored context can remain until it is cleared. That is why a domain may still receive phrases from a previous business name or service, even when the live site has moved on. ✅ Update your source content first A cache clear works best when the site and your OTTO brand details already match the current brand. Before you contact the team, check the following: - Replace or remove the retired brand name and outdated service phrases on key pages, including titles, headings, footers, and image descriptions. - Update the brand name, description, and any terms to avoid in your OTTO brand settings. - Write down the exact phrases that must not be suggested again, including spelling. 💬 Request a brand cache clear Stale OTTO brand cache clears are completed by our team. There is no separate customer button for this reset. Open the chat widget in the bottom-right corner of the platform and send your message. In the same chat, include: 1. The full domain that needs the clear. 2. The old text that must not appear again, such as a retired business or service name. 3. Confirmation that the live site and OTTO brand settings already use the new wording. Ask the teammate to clear OTTO cached brand data for that domain and to keep those phrases out of suggestions on the next crawl. 🚀 What happens on the next crawl Cleared context is applied when OTTO crawls the site again. Existing drafts are not all rewritten the moment the cache is cleared. After the teammate confirms the clear, wait for or start the next crawl, then review new suggestions. If an old phrase still appears, send the page URL and the exact suggestion text in chat so the team can check that domain again. 💡 How to stop the old brand from returning - Use one current brand name on the homepage, in title tags, and in the OTTO brand profile. - Remove the retired name from old service pages and other leftover copy. - List every retired phrase when you request the clear so the next crawl has a complete exclusion list. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 2026

🔍 Campaign Hub Landing Page Checks

📌 What the health checklist is showing In Campaign Hub, a red landing page status labeled not found does not always mean no page is connected. The checklist looks for a landing page URL it can match to the campaign and for conversion actions it can see in the linked Google Ads account. If either check fails, the item stays red even when a page appears connected in the campaign settings. A missing conversion message means Search Atlas did not detect an eligible Google Ads conversion action for that campaign. It is a data and connection check, not proof that your landing page is broken. 🛠️ Confirm the landing page connection Work through these checks before treating the status as a bug: 1. Open the campaign in Campaign Hub and confirm a landing page is assigned to that campaign, not only saved elsewhere in the project. 2. Compare the assigned URL with the final URL used in Google Ads. The protocol, domain, www, path, and trailing slash must match. 3. Confirm the page is published and included in the same Search Atlas project as the campaign. 4. If you recently changed the URL, save the campaign and allow the checklist to refresh. A mismatch on any of these points commonly produces a red not found status even though a page looks connected. 📊 Why conversion tracking shows as missing Clicking the missing item and seeing conversion tracking is missing for Google Ads means the checklist could not find a usable conversion action. Typical causes include: - The Google Ads account is not connected, or the connection needs to be refreshed. - The campaign is linked to a different Google Ads account than the one that contains the conversion actions. - No conversion action exists, or existing actions are removed, hidden, or not set as primary. - A recent change has not finished syncing into Campaign Hub. ✅ How to clear the red status 1. In your integrations, reconnect or refresh Google Ads and confirm the correct account is selected. 2. In Google Ads, confirm at least one relevant conversion action exists and is eligible for the campaign. 3. Return to Campaign Hub, open the campaign, and verify the landing page URL still matches the ad final URL. 4. Save any updates and wait for the next sync, then review the health checklist again. If the page is correctly assigned, the URLs match, and an eligible Google Ads conversion action is present after a fresh sync, the checklist should clear. A brief delay after connecting an account or editing a URL is expected. 💬 When to contact support If the landing page remains red after the URL and Google Ads checks above, share the campaign name, the landing page URL, and the Google Ads account name with support. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 2026

🔍 Why Atlas Agent Cannot Read GSC

⚠️ What the error means When Atlas Agent returns PRECONDITION_FAILED and says Google Search Console is not connected for this account, it cannot use Search Console data for the site it is working on. The agent stops instead of guessing. A property that looks active in Site Metrics, including a domain property such as sc-domain:eladhamdistributors.com, does not always mean the agent has a usable connection for that same site. 📊 Why Site Metrics can still look connected Site Metrics and Atlas Agent do not check the connection in exactly the same way. Site Metrics can keep showing a property that was connected earlier, while the agent requires a current authorization on the Search Atlas site you selected. The usual causes are: - The Google account that owns or can access the Search Console property is not the account currently authorized in Search Atlas. - The property is linked to a different site record than the one Atlas Agent is using. - A domain property is connected, but the agent site is a different host, protocol, or URL-prefix property. - The Google permission was removed, expired, or was not granted for Search Console when the account was connected. - The connection was updated recently and has not finished syncing. You do not add a separate Search Console product inside Google. You do need the correct Google user, the correct property, and that property selected on the same Search Atlas site. 📍 Where to Find It UI path: Settings → Integrations 🛠️ Checks before you reconnect 1. Open the site in Search Atlas that Atlas Agent is using, not only the Site Metrics view. 2. Confirm the connected property is the one you expect, such as the domain property for eladhamdistributors.com. 3. In Google Search Console, confirm that the same Google user can open that property and that it is not limited to a different domain or URL prefix. 4. If you manage more than one Search Atlas site, make sure the agent task is running on the site where this property is selected. 🔗 How to restore access 1. In Search Atlas, open the site and go to the Google Search Console connection used by that site. 2. Disconnect the current Google connection for that site if one is shown. 3. Connect again and sign in with a Google account that has access to the domain property. 4. Approve the requested Google permissions, including access to Search Console data. 5. Select the matching property, such as sc-domain:eladhamdistributors.com, and save it to this site. 6. Wait a few minutes for the sync to finish, then run Atlas Agent again on the same site. If the property is correct but the agent still reports that Search Console is not connected, repeat the connection once. A second authorization refreshes an expired or partial grant. No extra manual mapping is required beyond selecting that property on the site the agent uses. ✅ After the connection is fixed Atlas Agent should stop returning this precondition error and should be able to read the connected property. Site Metrics may update on its own schedule, so a short delay is normal. If metrics look current but the agent still fails, the site selected for the agent is still not the site that holds the active property. 💬 When to contact support If you confirmed the Google user can open the property, selected that same property on the agent site, and the error remains after a fresh connection and a short wait, contact support. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 2026

📊 Connect GA4 and Approve OTTO Changes

📊 Why GA4 and OTTO work together Google Search Console (GSC) and Google Analytics 4 (GA4) answer different questions. GSC shows how your site appears in Google Search. GA4 shows what visitors do after they arrive. Connecting GSC does not replace GA4. For the fullest picture in Search Atlas, connect both for each client. 📍 Where to Find It UI path: Settings → Integrations 🔗 How to add GA4 to a client You need access to the client’s GA4 property and permission to connect it. 1. Open the client project in Search Atlas. 2. Go to Integrations or the project’s data connections area. 3. Select Google Analytics 4. 4. Sign in with the Google account that can access that property. 5. Choose the correct GA4 account and property, then confirm the connection. 6. Wait until the status shows as connected before you review reports. If the property does not appear, confirm you are signed in with the right Google user and that you have at least Viewer access in GA4. ⚙️ Where to find OTTO settings OTTO settings live inside the same client project, not in your personal account profile. 1. Open the client project. 2. Open the OTTO or OTTO SEO section. 3. Look for Settings to control how recommendations are applied. Use these settings to decide whether OTTO only suggests changes or can publish them after you approve them. ✅ How to sign off before changes go live You do not have to publish OTTO changes right away. Keep review control turned on so nothing goes live until you approve it. 1. Open OTTO settings for the client. 2. Choose a review or approval mode instead of automatic publishing. 3. Open the list of recommended changes. 4. Review each item, then approve only the changes you want. 5. Leave the rest pending or reject them if they are not a fit. Approved items are the only ones that should be pushed. If you are unsure, leave a change unapproved until you are ready. 💡 GSC connected — do you still need GA4? Yes, if you want engagement and conversion context alongside search data. GSC alone is enough for some search reports, but GA4 adds sessions, landing page behavior, and goal data that help you judge whether OTTO changes are working. Connect GA4 even when GSC is already connected. 🛠️ If something does not connect - Use a Google account that can access the client’s GA4 property. - Confirm you selected the right property, not another client’s. - Reconnect if the status shows an error or an expired login. - Check OTTO settings again before approving any change. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 2026

🛠️ Fix OTTO Engage and Crawl Exclusions

📌 What this article covers Use this guide when OTTO appears live on your site but the Search Atlas install checker does not show it, and when you need to keep paths such as /listing/ out of both the crawl and OTTO. It also explains how to stop the current crawl and start a fresh one after exclusions are saved. 🔍 Why the checker and the live site can differ A live OTTO script does not always mean the install checker has recorded an engaged status yet. The checker looks at the pages it can reach, the project domain, and the latest crawl results. A mismatch is common when: - The script is present on some templates but missing on the homepage or other pages the checker samples. - A tag manager, consent banner, or cache is delaying the script. - The crawl is still running on an older URL list that includes pages you now want excluded. - The connected domain does not exactly match the live host, including www and https. Confirm the script on the public homepage and on one inner page, then refresh the install checker after the new crawl finishes. 📍 Where to Find It UI path: Left sidebar → OTTO SEO → Site Audit → Crawl Monitoring ⚙️ Confirm OTTO engage status 1. Open the correct site project in Search Atlas and confirm the domain matches the live site. 2. Go to the OTTO or installation area and review Engage status. 3. If status is not engaged, re-save the installation and publish the script on the site template that loads on every public page you want OTTO to manage. 4. Clear the site cache or CDN, then load the homepage in a private browser window and confirm the Search Atlas script is present. 5. Return to Search Atlas and run the install checker again. Allow a few minutes if the site cache was just cleared. Excluding a path removes those URLs from OTTO and from future crawls. It does not place the script on pages that do not already contain it. 🚫 Exclude all listing pages To exclude every URL under /listing/, add a path rule before you restart the crawl: 1. Open the site project and go to crawl settings, URL exclusions, or the OTTO page-scope settings. 2. Add an exclusion for the path pattern /listing/. Use a contains or starts-with rule if the product offers match types, so both /listing/ and deeper URLs such as /listing/example/ are covered. 3. Apply the same exclusion to OTTO so those pages are not selected for OTTO changes. 4. Save the rule and confirm it appears in the active exclusion list. Add both www and non-www variants only if your project treats them as separate hosts. 5. Do not exclude the homepage, key service pages, or other URLs you still want crawled and optimized. If listing URLs use a different folder, such as /listings/, add that exact path as its own rule. Rules are not applied to a crawl that is already in progress. 🔄 Stop the current crawl and start again Yes. You can stop the current crawl and restart it after exclusions are saved. 1. Open the crawl or site audit progress view for the project. 2. Select Stop or Cancel crawl if a crawl is running. Wait until the status changes from running to stopped or canceled. 3. Confirm the /listing/ exclusion is saved. 4. Select Start crawl or Recrawl. This starts a new crawl using the updated exclusion list. 5. When the crawl completes, open the URL list and verify that listing pages were skipped, then rerun the install checker. Stopping a crawl discards that in-progress pass. It does not remove OTTO from your website. Previously crawled listing URLs may remain visible in older results until the new crawl replaces them. ✅ After the new crawl - Engage status should reflect pages that still contain the OTTO script and were included in the crawl. - Listing URLs should be absent from the new crawl and excluded from OTTO actions. - If the checker still fails, compare the sampled page with the live homepage and confirm the script is not blocked by consent mode, a cache rule, or a template that loads only on certain sections. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 2026

🔍 How the OTTO Pixel Implements Schema

📌 What the OTTO Pixel Does Search Atlas adds schema through the OTTO pixel, a small script installed on your site. After the page loads in a browser, the pixel inserts structured data into the live page. This is how approved schema reaches your pages without editing every template by hand. 👀 Why Schema Is Missing From Page Source View Source, and tools that only read the original HTML file, show the page before JavaScript runs. The OTTO pixel writes schema into the rendered page, not into that original file. If you cannot find schema in the source, that is expected. It does not mean the markup failed. 📍 Where to Find It UI path: Left sidebar → OTTO SEO → Installation Guide ✅ How to Confirm Schema Is on the Page Use a method that runs JavaScript, then look for a script of type application/ld+json or for the schema type OTTO recommended. 1. Open the live page in Chrome. 2. Right-click the page and choose Inspect. 3. In the Elements panel, search for ld+json or the schema type you expect. 4. Or open Google’s Rich Results Test, enter the public URL, and let the test render the page. You should see the structured data in the rendered page or in the test results, even when View Source shows no schema. 🤖 What Search Engines Can Read Google renders JavaScript on many pages and can read schema added after the page loads. The pixel is built so the rendered page includes that markup. Indexing is not instant. Allow time after you approve and deploy schema in OTTO before expecting rich results. - Rich results are never guaranteed, even with valid schema. - Only schema you approved in OTTO is injected. - The pixel must be installed and allowed to load on that URL. 🛠️ If Schema Still Does Not Appear Check these items before you contact support: - Confirm the OTTO pixel snippet is on the page and is not blocked by a tag manager, consent banner, or content security policy. - Confirm schema for that URL is approved and deployed in OTTO, not only suggested. - Hard-refresh the page or test in a private window so an old cached copy is not hiding the script. - Test the public URL, not a staging page the pixel does not cover. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 2026

🔍 Understanding OTTO Deep Freeze After Cancellation

🧊 What Deep Freeze Does Deep Freeze is the OTTO feature that keeps optimizations you have already applied in their current state. Exact behavior can depend on your plan, your site setup, and the settings active when you disconnect, so review the details for your own account before you rely on them. 📍 Where to Find It UI path: Left sidebar → OTTO SEO → Overview ⚠️ What This Article Can and Cannot Confirm This article explains general behavior and a safe way to check your results. It is not a written guarantee for your account. Written confirmation about how your specific optimizations will be preserved must come from our team, not from general documentation. ✅ Before You Disconnect or Cancel 1. Record your current state. Export or screenshot the list of optimizations applied, including page URLs, dates, and any titles, meta descriptions, or on-page changes. 2. Save key performance baselines. Note rankings, organic traffic, and indexing status for your priority pages so you can compare later. 3. Review your plan terms. Check your subscription details and the cancellation terms that apply to your account. 4. Make a backup of your site. Keep a full copy of your website content and settings before making any changes. 🔗 Dependencies to Review Some changes can be affected by other systems, even if the optimization itself stays in place. Check the following before and after disconnecting: - Content management system updates: Theme changes, plugin updates, or template resets can overwrite on-page changes. - Third-party tools: Other SEO, analytics, or tag manager tools may edit the same fields. - Manual edits: Any change made by your team after the optimization was applied may take priority. - Hosting or redirect rules: Server-side changes can affect how pages and URLs appear to search engines. 🧪 Safe Validation Procedure 1. Start with a small test. If possible, test on one or two low-risk pages before reviewing your whole site. 2. Disconnect or cancel as planned. Complete the steps you need to take in your account. 3. Check the live pages. Compare the page titles, meta descriptions, headings, and on-page content against your saved records. 4. Check search engine view. Use a page inspection tool to confirm the indexed version matches what you expect. 5. Monitor over several days. Rankings and traffic can take time to reflect changes, so compare your baselines over a period rather than a single day. 6. Document any differences. Note the page, what changed, and when you noticed it. This will help if you need to escalate. 🛠️ If You Find Differences Do not make bulk edits right away. First, confirm whether a CMS update, plugin, or team member change caused the difference. Restore affected pages from your backup if needed, then review the steps above before trying again. 📩 Getting Written Confirmation If you need written confirmation that your existing optimizations will be preserved after disconnecting OTTO or cancelling, request it from our team. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 2026

🔍 Why Your OTTO Site Quota Changed

🔍 Why You May See Fewer OTTO Sites If you registered under a promotional plan and now see fewer OTTO sites than you expected, your site quota has changed. Promotional plans often include a set number of OTTO site slots for a limited time. When the promotion ends or your plan changes, the number of active site slots may be adjusted to match your new plan. 📋 Common Reasons a Site Slot Is Removed - Promotion ended: The promotional term expired, and your account moved to a standard plan with a lower site limit. - Plan change: You upgraded, downgraded, or switched plans, and the new plan includes a different number of OTTO sites. - Site limit exceeded: Your account had more sites than the current plan allows, so the extra site was removed from active use. - Site removed or archived: A site was deleted, archived, or disconnected from your account, either by you or by a team member. 📍 Where to Find It UI path: Top-right corner (avatar) → Billing → Plans & Top-ups tab 🧭 How to Check Your Current Site Quota 1. Log in to your Search Atlas account. 2. Open your account or billing settings and review your current plan name and site allowance. 3. Open your OTTO site list and confirm which sites are active. 4. Note the date your promotional plan started and the date it was scheduled to end. 🛠️ Steps to Request a Site Quota Review If the numbers do not match what you expect, our team can review your account history with you. Restoration is not guaranteed, and it depends on your current plan, eligibility, and the terms of your promotion. To speed up the review, have the following information ready: 1. The email address associated with your account. 2. Your original registration date and the promotion you signed up under. 3. The names or URLs of the sites you expected to keep. 4. Screenshots of your site list and plan details, if available. ⚙️ Preventing Future Quota Surprises - Check your renewal date: Know when your promotion ends so you are not caught off guard. - Review sites early: Before a plan change, decide which sites you want to keep and archive any you no longer need. - Confirm plan limits: Compare your current site count with your plan's allowance after every plan change. - Keep records: Save your promotion details and plan confirmation emails for reference. **💬 Getting Further HelpIf you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 2026

🔍 Fixing Google Search Console Connections for OTTO Prompts

📍 Where to Find It UI path: Settings → Integrations 🔌 Why a Search Console Connection Fails When you add a new client, the connection to Google Search Console often fails for a few common reasons. Check these first: - Wrong Google account: The Google account you sign in with must have access to the client's Search Console property. - Insufficient permissions: The account needs at least Full user access in Search Console. View-only access is not enough for a full connection. - Property mismatch: The website address in Search Console must match the client's domain. A URL-prefix property (for example, https://www.example.com) and a Domain property (example.com) are treated differently. - Property not yet verified: Search Console must show the site as verified before it can be connected. ✅ Steps to Fix the Connection 1. Sign in to Google Search Console and confirm that the site appears in the property list. 2. Check that your account has Owner or Full user permission for that property. 3. Confirm the property's address matches the domain you entered for the client in Search Atlas. 4. Return to Search Atlas, remove the existing Search Console connection for that project, and reconnect it using the account you verified in steps 1 to 3. 5. Allow a short time for data to appear. New properties can take several days to show full historical data. 🧭 Refining Your OTTO Prompt When Search Console Is Unavailable If you cannot connect Search Console for a client, you can still get useful results from OTTO. The key is to tell OTTO which data sources to use and what to do if one is missing. Vague prompts can lead OTTO to assume data is available, which produces unreliable recommendations. Use these guidelines when you write your prompt: - State the data situation: Say clearly that Search Console is not connected for this client. - Name the fallback sources: Tell OTTO which other data it can rely on, such as analytics or crawl data. - Ask OTTO to flag gaps: Request that OTTO label any recommendation that depends on missing data. - Limit the scope: Focus the task on what you can measure, such as on-page improvements, content gaps, or technical issues. - Specify the output format: Ask for a prioritised list, a summary, or a step-by-step plan so the result is easy to review. 💬 Example Prompt Use the following as a starting point and adjust it to the client's goals: Create an SEO performance summary for this client's website. Google Search Console is not connected for this project, so do not estimate or infer search query or impression data. Base your analysis on the available crawl data and on-page content. Identify the five highest-priority technical or on-page issues, and for each one explain the expected benefit and the effort required. Mark any recommendation that would normally rely on Search Console data as Needs verification once the connection is restored. Present the results as a numbered list with a short summary at the top. 📊 Tips for Client Reports - Add a note in the report explaining which data sources were used and which were unavailable. - Once the Search Console connection is working, run the same prompt again to compare results and update flagged items. - Keep a checklist of connection steps so the same issue can be resolved quickly for future clients. 🛟 Getting Further Help If the connection still fails after you have checked the steps above, or if OTTO's output does not match what you expected, please reach out for help. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 2026

🧊 OTTO Deep Freeze and Plan Changes

❄️ What OTTO Deep Freeze does OTTO Deep Freeze pauses new OTTO activity for a site. While the site is frozen, OTTO does not deploy new fixes or roll back changes that are already live. Deep Freeze does not switch the site back to Active by itself. Fixes that were already deployed stay published. Deep Freeze keeps that work in place. It does not remove pages, metadata, or other changes OTTO has already put live. 📅 What happens on the freeze end date Check the end date shown for the site in OTTO. What happens next depends on that setting: - An end date is set: the site stays frozen until that date. On the end date it returns to Active, and OTTO can resume normal activity. Deployed fixes remain live. - No end date is set: the site stays frozen until you end Deep Freeze. A calendar date alone does not unfreeze it. If purealchemydesign.com was placed in Deep Freeze with an end date of November 13, deployed fixes stay live through that date. The site returns to Active on November 13 only when November 13 remains the scheduled end date. If you change or remove that date, the updated setting applies instead. 🔄 How a plan change affects a frozen site Switching plans, including moving from Pro to Growth, does not cancel Deep Freeze and does not remove fixes that are already live. A plan change on November 4 leaves the site frozen and leaves its deployed fixes in place. - Freeze status: stays the same until the end date or until you end Deep Freeze. - Live fixes: remain published. The plan change does not roll them back. - Future OTTO actions: after the site returns to Active, new recommendations and deployments follow the features included in the plan that is active at that time. 📍 Where to Find It UI path: Left sidebar → OTTO SEO → Overview ✅ How to confirm status around your plan change 1. Open the site in OTTO and confirm the status shows Deep Freeze. 2. Note the scheduled end date, if one is shown. 3. Complete the change from Pro to Growth. 4. Return to the same site and confirm that Deep Freeze and the same end date are still shown. 5. On the end date, confirm the status changes to Active only if that end date was left in place. You do not need to redeploy existing fixes after the plan change. 💬 When to contact support If the status, end date, or live fixes do not match what you expect, contact support before the end date. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 2026

⚙️ OTTO Integration and Usage Charge Clarification

🔍 Can a proprietary WordPress site use OTTO? Yes, in most cases. OTTO does not require a standard public WordPress theme or full admin access to the plugin directory. If the site runs on WordPress but blocks plugin installs, OTTO can still work as long as you can place a small tracking snippet where pages load, or connect through an approved tag manager. A site is a good fit when you can do at least one of the following: - Add a script or pixel to the site header or footer - Publish that script through Google Tag Manager or a similar tag system - Have a developer add the snippet to the proprietary template - Install the Search Atlas WordPress plugin if plugin access is later allowed OTTO is not a fit only when the platform blocks all custom scripts, tag managers, and template edits. In that case, you can still use Search Atlas research and reporting tools, but automated on-page deployment will be limited. 🛠️ Options when the plugin cannot be installed Choose the lightest method your site owner will allow. You do not need every option at once. 1. Header or footer snippet: Ask the site owner to paste the OTTO installation code into the global template. This is the usual path for proprietary WordPress. 2. Tag manager: If Google Tag Manager or another approved container is already on the site, publish the OTTO snippet there. No plugin is required. 3. Developer handoff: Send the installation code to the agency or in-house developer who controls the template. They add it once; it then loads on the pages you select. 4. Plugin later: If plugin access is unlocked, install the Search Atlas plugin and connect the same project. Do not run duplicate install methods on the same pages. After installation, open the project in Search Atlas and confirm the site shows as connected before you approve OTTO changes. Connection alone does not publish edits. You still review and approve recommendations inside the project. 📍 Where to Find It UI path: Left sidebar → OTTO SEO → Installation Guide 📊 How to get a timestamped usage export by project Usage is recorded against the project that ran the action, with a date and time for each chargeable event. A timestamped export is the right record when you need to reconcile a bill or see which project consumed Keyword Explorer activity. To request it: 1. Open the live chat widget in the bottom-right corner of the platform. 2. Send your message. 3. Ask for a timestamped usage export by project and include the project name, site URL, and the billing dates you need. The export is organized by project and time so you can match each line to a Keyword Explorer action. It is not a public self-serve download in every account, so chat is the correct path for a formal export. 💡 What triggers the recurring Keyword Explorer charge Keyword Explorer usage is metered when the tool does new keyword work for a project. A recurring charge means that work is running again on a schedule or is being repeated, not that the site connection itself bills you. Common triggers include: - New keyword research started inside a project, including fresh seed terms or a new keyword list - List refreshes that pull updated metrics for keywords already saved to that project - Scheduled or repeated runs if the project is set to refresh keyword data on a recurring cycle - Additional projects researching the same topics separately, because usage is counted per project These actions do not by themselves create a Keyword Explorer charge: installing the pixel or plugin, connecting the site, or viewing a report that was already generated. Opening an old list without refreshing it should not start a new research run. If a charge repeats and you did not expect a refresh, check whether more than one project is researching the same site, and whether a recurring refresh is still active. Then request the timestamped export so each charge can be tied to a project and a time. ✅ How to keep usage predictable - Use one project per site unless you intentionally want separate research - Refresh keyword lists only when you need updated metrics - Approve OTTO changes only after the connection status is confirmed - Reconcile unexpected charges with a timestamped export before the next billing cycle If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 2026

🔍 Check OTTO Pixel and Shopify Ads

🔍 What this article covers This guide explains how to confirm the OTTO pixel is on your live Shopify store, what to do if the UUID does not appear in the page source, how to finish connecting Shopify, and how to create a Google ad in Search Atlas. 📌 Do you still need to find the UUID? Yes. Saving the UUID in theme.liquid only stores the code in your theme. Search Atlas can track the store and power OTTO only after the published theme outputs that snippet on the live storefront. You do not need to memorize the UUID, but you do need to confirm the installed snippet is present on the public page before you rely on data or launch ads. 🛠️ Place the pixel in the published theme In Shopify Admin, go to Online Store, then Themes. Open the theme marked Current or Live, choose Edit code, and open layout/theme.liquid. Paste the OTTO snippet from Search Atlas inside the section, ideally just before . Save the file. Editing a draft theme, a section, or an unpublished copy will not update the live page source. - Use the exact snippet from your Search Atlas OTTO installation screen, including the UUID. - Do not wrap the snippet in a comment or a Shopify liquid condition that hides it on the homepage. - If a password page is enabled, view the source on the storefront after entering the password, or temporarily disable the password while you check. 📍 Where to Find It UI path: Left sidebar → OTTO SEO → Installation Guide → WordPress Installation tab 👀 Check the live page source 1. Open your public store URL in a private or incognito window. 2. Right-click the page and choose View Page Source. Do not rely only on the Elements panel, which can show injected code. 3. Search the source for your UUID or for otto. 4. If it is missing, hard-refresh, confirm you edited the live theme, and save theme.liquid again. Shopify and your browser can cache an older theme. If the snippet is correct in the live theme but still missing, wait a few minutes and check the homepage source again. Also confirm you are viewing the primary domain, not a preview link that loads a different theme. ✅ Finish connecting Shopify After the UUID appears in the live page source, return to Search Atlas and open the OTTO installation or site-connection step for that property. Select Verify or Check installation. A successful check means the pixel was detected on the storefront. If verification fails, recheck that the UUID in theme.liquid matches the UUID shown for this site, then run the check again. Connecting the pixel is separate from granting Shopify access. If Search Atlas asks you to connect the store, approve the Shopify connection from the on-screen prompt so product and page data can sync. Wait until the site status shows connected before creating an ad. 🚀 Create a Google ad 1. In Search Atlas, open the connected Shopify site and go to the ads or campaigns area. 2. Connect your Google Ads account when prompted and choose the customer account that should receive the campaign. 3. Choose the product, collection, or landing page you want to promote. 4. Set the daily budget, location, and campaign goal, then review the ad copy and destination URL. 5. Confirm the destination is your live Shopify URL and that the OTTO pixel check has already passed. 6. Publish or submit the campaign, then confirm it appears as active or in review. Google may place a new campaign in review before it serves. Budget, billing, and account verification are managed in Google Ads. Search Atlas cannot bypass a Google billing or policy hold. 💡 If the UUID still does not appear - Confirm there is only one in theme.liquid and the snippet sits inside it. - Remove duplicate or older OTTO snippets so only the current UUID remains. - Check that an app or custom script is not replacing the head content after the theme loads. - Re-copy the snippet from Search Atlas rather than typing the UUID by hand. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 2026

🔧 Fix OTTO WordPress Posting Sync

📌 What this issue means OTTO can show your site as synced while WordPress posting still says it is not in sync. The general connection check and the publishing check are separate. A script placed only in index.html can make one page look connected while posts and pages that WordPress uses for publishing never load the script. 🔍 Why posting stays out of sync - Script on one file only: index.html is not the same as your WordPress theme. Posts, pages, and the homepage template may never include that file. - Address mismatch: The domain in OTTO must match the live WordPress address, including https and www. - Cache serving old HTML: A cache plugin, host cache, or CDN can keep a version of the site that does not include the current script. - Blocked script: Security, optimization, or consent tools can delay or remove the script before OTTO can read it. - Status confusion: A site can look synced overall while the WordPress posting link is still disconnected. 🛠️ Reconnect WordPress posting 1. In OTTO, open the site and note the exact domain shown for WordPress posting. 2. In WordPress, confirm Settings show the same address, including https and www. 3. Install the OTTO script through the recommended WordPress method, or add it to the theme header so it loads on every public page. Do not rely on index.html alone. 4. Pause minify or delay settings for the OTTO script if an optimization plugin is active. 5. Clear WordPress, plugin, host, and CDN caches. 6. Open the homepage and one published post in a private browser window. View page source on both and confirm the OTTO script is present. 7. Return to OTTO, refresh the WordPress connection, and check the posting status again. 8. Publish a short test only after posting shows in sync. Confirm the item appears in WordPress. 📍 Where to Find It UI path: Left sidebar → OTTO SEO → Installation Guide → WordPress Installation tab ✅ How to tell it is fixed The posting screen should stop saying the site is not in sync with WordPress. The script should appear in the source of the homepage and of a post, not only in index.html. A test item should leave OTTO and show in WordPress as a draft or live post, based on your publish settings. If the script is missing from posts, publishing will stay out of sync until it loads across the site. 💬 If it still will not sync Recheck the domain, clear cache one more time, and confirm the script is in the source of more than one URL. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 2026

🛠️ Fixing HTML Codes in OTTO Recommended Titles

🔍 What This Issue Looks Like Some OTTO title recommendations may display HTML codes instead of normal characters. For example, an ampersand may appear as & rather than &. This makes titles look broken and can stop you from trusting recommendations enough to turn on autopilot. ⚙️ Why It Happens HTML codes are stored text versions of special symbols. They can appear in titles when a brand name or term containing a symbol, such as an ampersand, is not handled as plain text during analysis. Our support team has seen this happen in a small number of cases, and in at least one case it could not be reproduced once the affected term was reviewed. ✅ Steps to Resolve It Yourself 1. Identify the affected recommendations. Review the OTTO title recommendations and note which ones contain code-like text, such as ampersand codes. 2. Check your Brand Vault. If the affected text is a brand name or term that contains a special character, make sure it is set up correctly in your Brand Vault. Use the exclusion option for that term if it should not be used in recommended titles. 3. Regenerate the recommendations. After updating your Brand Vault, regenerate the title recommendations so the changes are applied to new suggestions. 4. Wait for the next analysis cycle. Some changes only show up after a full crawl or the next OTTO weekly analysis has run. If your recommendations still look wrong right after the update, check again once that analysis has completed. 5. Re-check before enabling autopilot. Review several new title recommendations. Only turn on autopilot once the titles display normal characters. 🚀 If the Problem Happens Again If you still see HTML codes after completing the steps above, the issue may be a temporary glitch. Please note the page or URL, the exact title recommendation, and the date you saw it, then try the steps once more. Including these details will help our team investigate quickly. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 2026

🛠️ Fix OTTO Schema and FAQ JSON

🔍 What went wrong OTTO can suggest schema that does not match the real business or page. Examples include a service-area business shown as a physical location, a coaching site labeled as a vacation rental, and blog posts under a post path classified as a Service or Resource Hub. A separate Google Search Console FAQ error can come from invalid JSON, not from the page type. ⚠️ Do not deploy misleading schema Do not deploy schema that misrepresents the business or the page. Wrong structured data can conflict with what the site actually offers. Review each OTTO schema suggestion before you apply it. If the type does not match the business model or the content on that URL, leave it undeployed. - A service-area business should not be marked as a storefront or other physical location it does not have. - A coaching site should not use a vacation rental type. - A blog post should not be treated as a service page or a resource hub when the URL is an article. 📄 When blog pages are misclassified Blog pages are a common place for this mistake. If posts are suggested as a Service or Resource Hub, treat that as a likely misclassification by OTTO, not as a change you should publish. Skip those suggestions. If the same wrong type appears across your projects, it needs a review by the OTTO team rather than a manual deploy. 🛠️ Fix the FAQ JSON error If Google Search Console reports an FAQ schema error, check the JSON syntax. The failure seen in support was single quotes where JSON requires double quotes. That markup was not found in OTTO, so it lives in the existing FAQ schema on the site. 1. Open the page in your website editor. 2. Find the existing FAQ schema. Do not look for it inside OTTO if OTTO did not add it. 3. Replace single quotes in the JSON with double quotes so the markup is valid JSON. 4. Save the page and recheck the FAQ item in Google Search Console after it recrawls. Only property names and string values in JSON use double quotes. Leave the FAQ text itself accurate, and do not add schema that describes services or locations the page does not have. 💬 When to contact support Fix the quote syntax yourself in the website editor. For repeated wrong schema types, do not deploy them. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 2026

🛠️ Resolving OTTO Schema Validation Warnings Explained

Schema validation warnings mean that structured data on one of your pages has a problem, such as a missing property, an incorrect format, or a duplicate entry. Warnings do not always mean the same thing. This article explains where warnings come from and the steps to resolve them. 📍 Where to Find It UI path: OTTO SEO → Overview → Schema Markup → schema preview 🔍 Understanding Where Schema Warnings Come From Each schema warning falls into one of two groups: - Schema deployed by OTTO: markup that OTTO added to your site as part of an optimization. - Schema already on your site: markup that existed before OTTO was active, usually added by your theme, a plugin, a developer, or an earlier SEO tool. Check the source details shown next to each warning. They indicate which group the warning belongs to. If the source is unclear, the fix steps below will still help you narrow it down. ✅ Fixing Warnings From OTTO-Deployed Schema If a warning comes from schema OTTO deployed, follow these steps: 1. Open the affected page in your OTTO dashboard and review the warning details, including the property or field flagged. 2. Review the recent change that added the markup. Confirm whether the flagged value is accurate for that page. 3. Correct the source data. Many warnings come from missing or incorrectly formatted information, such as a blank date, an invalid URL, or a missing name. Update the page content or settings so the required information is complete. 4. Re-run validation on the page to confirm the warning is gone. If you cannot identify the cause, do not delete markup manually. Manual removal can cause OTTO to re-deploy the same schema on the next optimization cycle. 🧹 Fixing Warnings From Existing Schema If a warning comes from schema that was already on your site, follow these steps: 1. Identify the source. Check your theme settings, installed plugins, and any earlier SEO tools to find which one adds the markup. 2. Keep one schema block per entity. Duplicate blocks, such as two Organization entries on the same page, are a common cause of warnings. Decide which block to keep and disable the other at its source. 3. Update or disable the source in its own settings. For example, turn off a schema option in a plugin that overlaps with OTTO, or correct the values in your theme. 4. Re-run validation to confirm that the warning has cleared and that no new warnings appeared. Changes to themes or plugins can affect other parts of your site. Test on a single page first, then apply the change more broadly. 🛡️ Preventing Future Warnings Use these habits to keep schema clean over time: - Avoid running multiple schema tools that generate the same markup types on the same pages. - Keep page details current, including dates, prices, names, and URLs, since outdated information is a frequent source of warnings. - Review validation results after major site changes, such as a redesign, a theme update, or a new plugin installation. - Check validation regularly so small issues do not accumulate into large ones. 💬 Getting Further Help If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

🔍 Why Campaign Hub Shows Landing Page Red

📍 Where to Find It UI path: Google Ads → Campaign Hub → SETUP → Landing page 🔎 What the Red Health Checklist Items Mean The Campaign Hub health checklist shows a red status when a required item is missing or not detected. Two items commonly appear red for Google Ads campaigns: - LP (Landing Page) not found: Campaign Hub cannot match a landing page to this campaign. - Conversion tracking missing: Campaign Hub cannot detect a conversion action that records when visitors complete a goal, such as a purchase or form submission. These two items are linked. Campaign Hub uses the landing page and the conversion data together to evaluate campaign health, so a problem with one can make the other look incomplete. 🤔 Is This a Bug or a Setup Issue? In most cases, a red status comes from a setup detail rather than a platform bug. Work through the checks below before assuming something is broken. If every check passes and the item still shows red, contact our team using the steps at the end of this article. 🔗 Step 1: Confirm the Landing Page Is Connected to the Campaign 1. Open the campaign in Campaign Hub and review the landing page section. 2. Check that a landing page is selected. A page that exists in your account but is not attached to this campaign will still show as not found. 3. Confirm the landing page URL is the same as the final URL used in your Google Ads ads. Differences in http versus https, a missing or extra "www", or a trailing slash can cause a mismatch. 4. Save your changes and wait a few minutes, then refresh the health checklist. 🌐 Step 2: Check That the Landing Page Is Live 1. Open the landing page URL in a private browser window. 2. Confirm the page loads without errors and is not password-protected or set to draft or hidden. 3. If the URL redirects to another address, make sure the final destination matches the URL connected in Campaign Hub. 📈 Step 3: Verify Conversion Tracking in Google Ads 1. Sign in to Google Ads and open the Goals or Conversions section. 2. Confirm at least one conversion action exists and is set to enabled, not paused or removed. 3. Check that the conversion action is associated with the campaign you are reviewing. Campaigns that do not use the conversion action will not register conversions for it. 4. Look at the conversion status. A status of No recent conversions is normal for new campaigns, but a status showing a tag problem needs to be fixed first. 🧩 Step 4: Confirm the Tracking Tag Is on the Conversion Page 1. Make sure the Google tag or conversion code is installed on the page where the conversion happens, such as a thank-you or confirmation page. 2. Complete a test conversion yourself, such as submitting a test form or placing a test order. 3. Check Google Ads for recorded activity. Conversions can take up to 24 to 48 hours to appear, so allow time before concluding that tracking is missing. 🔐 Step 5: Check Your Google Ads Connection 1. Confirm the correct Google Ads account is connected to Search Atlas. 2. Make sure the account user who connected it still has access to the campaign and its conversion data. 3. If you recently changed Google Ads permissions or accounts, reconnect the integration and refresh the health checklist. ✅ Quick Reference: Common Causes - No landing page is attached to the campaign. - The landing page URL does not exactly match the final URL in your ads. - The landing page is hidden, draft, or redirecting elsewhere. - The conversion action is paused, removed, or not linked to the campaign. - The tracking tag is missing from the confirmation page. - Conversion data has not yet had time to appear (24 to 48 hours). - The Google Ads connection is outdated or uses the wrong account. 💬 Need More Help? If you have completed every step above and the landing page or conversion tracking item still shows red, we want to help. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

🔍 Verify Live Links and Pending Payments

🔗 What live links and pending payments mean A link is live when the page is published, publicly reachable, and shows your agreed placement. A payment stays pending until that placement is verified. Pending does not mean the order was lost. It means the link has not yet passed the live check, or the payment window has not started. 📍 Where to Find It UI path: Top-right corner (avatar) → Finance → My Orders ✅ How to confirm a link is live Review each order in your link or order list inside the platform. Open the publisher URL and confirm all of the following: - The page loads without a login, error, or “coming soon” message. - Your target URL and anchor text match the order. - The link is clickable and is not marked nofollow if the order required a dofollow link. - The article is indexed or at least publicly visible. A newly published page can take time to appear in search results. If the status still shows in progress, the publisher may not have gone live yet. Check the expected publish date on the order before requesting a payment review. 💳 When pending payments are processed Payments are released only after the link is confirmed live and matches the order. Processing is not instant at the moment a page is published. Allow the stated review window on the order to finish. If a link later goes down or the placement changes, payment can stay pending or be held until the issue is fixed. 1. Confirm the live URL in the order details. 2. Compare the live page with the anchor, target URL, and placement you purchased. 3. Wait until any shown review or publish date has passed. 4. If the link is live and the date has passed but payment is still pending, contact support with the order details. 📝 What to include in your request A complete request is reviewed faster. Have this ready: - Order or campaign name - Live page URL - Target URL and anchor text - The date you confirmed the page was public Do not send payment instructions outside the platform. Status and payout updates stay inside your account. 🛠️ If a link is not live yet Leave the payment pending. Asking for early payment before the page is public will not speed up the order. If the publish date has passed and the page is missing, broken, or different from the order, report that order so the placement can be corrected before any payment is released. 💬 Get help from the team If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

🔍 Export Internal Links That Redirect

📋 What Does Redirecting internal links Mean? An internal link that redirects is a link on your own website that points to one page, which then automatically sends visitors and search engines to a different page. Redirects are useful in some cases, but every redirect adds an extra step. Too many of them can slow down your pages and make it harder for search engines to crawl your site efficiently. Exporting this list lets you find these links and update them to point directly to the final page. 📍 Where to Find It UI path: OTTO SEO → Site Audit → Issues → Redirecting internal links → Export 🔎 Where to Find the Report The list comes from your Site Audit report. If you cannot find it, follow these steps: 1. Log in to your Search Atlas account and open the Site Audit tool from the main menu. 2. Select the project and the audit that you want to review. Make sure you choose a recent audit, since older reports may not show the same issues. 3. Open the Issues section of the report. 4. Look for the issue named Redirecting internal links. You can use the search or filter box to find it quickly. If the issue does not appear, your site may not have any internal links that redirect in that audit. Run a new audit after making changes to confirm the current status. 📥 How to Export the List Once you have found the issue, you can download the full list of affected links: 1. Click the Redirecting internal links issue to open its details. 2. Click the Export button, usually located at the top right of the list. 3. Choose the file format. A CSV file works best for spreadsheets such as Excel or Google Sheets. 4. Wait a moment for the file to generate, then download it to your computer. Export files include all affected links in the audit, not only the ones shown on your screen. If you filtered the view, check that the filters are cleared before exporting so you receive the complete list. 📊 Understanding the Columns in Your File The exported file typically includes the following information: - Source URL: the page that contains the internal link. - Linked URL: the address the link points to, which redirects. - Redirect Target: the final page where visitors land after the redirect. - Status Code: the type of redirect, such as 301 for a permanent redirect or 302 for a temporary one. Use the Source URL to find where the link lives, and the Redirect Target to find the correct address to use instead. 🛠️ How to Fix Redirecting internal links Once you have your list, you can improve your site by updating the links: 1. Sort the file by Source URL so you can work through one page at a time. 2. Open each page in your content management system or website editor. 3. Replace the redirecting link with the Redirect Target address. 4. Save your changes and publish the page. 5. Run a new Site Audit after you finish to confirm that the issue has been resolved. Some links may appear in templates, menus, or footers. Updating these once can fix many affected pages at the same time. Be sure to test the links after you make changes to confirm they load correctly. 💡 Tips for Keeping Your Links Clean - Update your internal links whenever you move or rename a page. - Link directly to the final URL rather than an older address. - Run a Site Audit regularly, such as once a month, to catch new redirects early. - Keep a record of the changes you make so you can review your progress in future audits. 🤝 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

🔍 Download Internal Links That Redirect List

📍 Where to Find It UI path: OTTO SEO → Site Audit → Issues → Redirecting internal links 📍 Where This List Lives The Redirecting internal links list is inside a completed Site Audit report. It is not a separate file on the project home page. Open the audit, then look in the issues or internal links area for redirect findings. 🛠️ Download the Redirect List 1. Sign in and open the project that contains the audit. 2. Go to Site Audit and open your most recent completed report. 3. Find the issue named Redirecting internal links. It may appear under internal links, redirects, or technical issues. 4. Open that issue to view the source pages and the URLs that redirect. 5. Choose Export or Download and save the file in the format shown, usually CSV. 💡 What the Export Shows Each row is an internal link that sends visitors through a redirect instead of straight to the final page. Update those links to the final URL so users and crawlers reach the right page in one step. - Source page is the page that contains the link. - Linked URL is the address that redirects. - Final URL is the destination after the redirect, when the audit captured it. 🔍 If You Cannot Find the List - Confirm the audit status is Completed. The list is not ready while a crawl is still running. - Search the report for redirect if the issue is grouped under another heading. - A missing list usually means this audit found no internal links that redirect. Check an earlier completed report if you expected results. - Refresh the report in your browser if the export button does not appear. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

💰 Resolve Overdue Affiliate Article Payments

💳 Why a payment can stay pending An affiliate article payment is not released the moment an article goes live. After publication, Search Atlas reviews that the article meets the agreed requirements, then queues the payout with your payment method. A status of pending means the transfer has not been completed yet. It does not mean the article was rejected. Common reasons a payout remains pending for more than a few weeks include a review that is still open, a payout method that is missing or unverified, a balance below the payout threshold, or a processing delay with the payment provider. ✅ Check these items first Before you request an update, confirm each item below. Fixing a setup issue is often what allows a pending payment to move forward. - Publication: The article is live at the agreed URL and still publicly accessible. - Requirements: The live page matches what was approved, including links, placement, and content. - Affiliate account: You are signed in to the same account that submitted the article. - Payout method: Your payment details are complete and verified. An outdated or incomplete method can hold a transfer. - Payout threshold: Your available balance meets the minimum required for a transfer. - Status label: Note whether the article shows as published, approved, pending, or on hold. 🛠️ How to request a payment update If the article has been published for more than a month and the payment is still pending, contact support with a clear request. We can confirm the processing status and tell you the next step. We cannot complete a transfer from this article, and account-specific dates are confirmed only after your payout is reviewed. 1. Open the live chat widget in the bottom-right corner of the platform. 2. Send your message in the chat. A member of our support team will reply in the conversation. 3. Share the article title or URL, the publication date, and the payment status you see. 4. Include the affiliate account email and the payout method on file, without sending full account numbers or other sensitive payment details in chat. 5. Ask the teammate to confirm whether the payout is in review, queued, or blocked, and what date or cycle applies. 📌 What to expect after you write in A teammate will look up the article and the payout record. They will tell you whether anything is still required from you, such as verifying a payment method, or whether the transfer is already queued. If a correction is needed on the live article, they will explain the change before payment can proceed. Keep the article published and unchanged while the payout is pending, unless support asks you to update it. Removing or editing required links can pause or reverse a payment that is under review. 💬 Get help in the platform If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

🛠️ Fix OTTO Homepage H1 Not Applying

🔍 What this issue looks like You approved an OTTO suggestion for the homepage H1, or you expected a homepage H2, but the live page still shows the old heading or no H2 at all. OTTO can recommend and deploy on-page changes only when the suggestion is approved, the install is active, and your site template allows that heading to be updated. 💡 Why the homepage heading may not change A suggestion that appears in OTTO is not the same as a change already published on the live site. The heading usually stays unchanged for one of these reasons: - Not approved or not deployed: the H1 or H2 is still a recommendation, or deployment has not finished. - OTTO is not active: the installation snippet is missing, blocked, or turned off, so approved changes cannot render. - Theme or page builder control: the homepage H1 is hardcoded, generated from the site title or logo, or locked inside a builder section. - No matching H2 target: OTTO cannot add an H2 when the homepage template has no editable heading or content block for it. - Cache: a plugin, host, or CDN is still serving an older version of the homepage. - Another SEO tool: a second plugin or script overwrites the same heading after OTTO applies it. ✅ Approve and deploy the suggestion 1. Open OTTO SEO → Overview and open the Headings Length category. Rows Headings Length – H1 Length and Headings Length – H2 Length show the ORIGINAL and the OTTO SUGGESTED FIX for each page. 2. Confirm the exact text you want. Edit it before approval if the wording should change. 3. Approve the heading suggestion, then deploy or publish the approved changes if your project uses a separate deploy step. 4. Wait until the status shows deployed or live. A pending or failed status means the old heading will remain. 5. If only the H1 was suggested, do not expect an H2 to appear automatically. Approve a separate H2 suggestion only when OTTO offers one. 📍 Where to Find It UI path: OTTO SEO → Overview → Headings Length ⚙️ Confirm OTTO can reach the homepage 1. Check that the OTTO installation is connected and the status is active for this site. 2. Open the live homepage in a private browser window so extensions and old sessions do not hide the result. 3. View the page source and search for the approved H1 text. Also search for your H2 text if one was approved. 4. If neither heading appears in the source, the change was not deployed or the theme is replacing it. If the text is in the source but not visible, a stylesheet, builder section, or script is hiding or swapping it. 🧹 Clear cache and recheck 1. Clear the cache in your SEO, optimization, or caching plugin. 2. Purge the host and CDN cache, including any homepage-only cache. 3. Reload the homepage with a hard refresh and compare it with the approved text in OTTO. 4. Give the deployment a few minutes, then check again before approving the same item a second time. 🛠️ Fix a theme that blocks headings Some themes print the homepage H1 from the site name and never expose an H2 field. OTTO cannot rewrite a heading that the template does not output or that another tool replaces. - In the theme or page builder, make the homepage H1 an editable text element rather than a logo-only or automatic site title. - Add a real text section where the H2 should appear, then return to OTTO and approve the H2 suggestion if it is offered. - Disable other apps that rewrite titles or headings and test one change at a time. - After the template is editable, redeploy the approved OTTO changes and purge cache again. 💬 Get help from the team If the suggestion is approved, OTTO shows a successful deployment, and the live source still has the old H1 or a missing H2, include the homepage URL and the exact suggested text when you contact support. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

🧹 Remove Former Employee White Label Details

🧹 What this article covers This guide shows where white-label settings live, how to remove a former employee's name and contact details from client-facing branding, and where to open the OTTO dashboard. White-label settings and the OTTO dashboard are separate areas of the platform. 📍 Where to Find It UI path: Top bar → Open Resources → Agency White Label → White Label Setup 🏷️ Open white-label settings White-label controls the agency name, logo, colors, and contact details that clients see. It is not inside the OTTO dashboard. 1. Sign in to Search Atlas with an account that can manage agency or white-label settings. 2. Open Settings from the main navigation. 3. Select White Label (it may also appear under Agency settings). 4. Review every field that clients can see, including display name, logo, website, email, phone, and any custom footer or support text. If you do not see White Label, your role may not include permission to edit it. Ask an account owner or admin to open Settings for you, or use the chat steps at the end of this article. ✏️ Remove the former employee's details Replace or clear any field that still shows the former employee. Saving an empty field is not always allowed; use your current agency contact instead. - Name: Change the agency or contact name to the current brand or teammate. - Email and phone: Replace the old address and number so clients are not sent to someone who has left. - Logo and photos: Upload a current logo if the old image includes the former employee. - Custom text: Check introductions, report footers, and client-portal messages for their name. - Select Save and refresh a client view or report preview to confirm the old details are gone. Changes apply to new client views after you save. Previously downloaded reports or emails already sent will still show the old details. 👤 Remove their access as well White-label branding and user access are different. Clearing a name from white label does not sign that person out or delete their login. 1. Open Settings, then Team or Users. 2. Find the former employee. 3. Remove them from the account, or change their role if they should no longer manage clients. 4. Confirm they no longer appear on projects they should not access. Do this for every workspace where they were added. Removing them from one project does not always remove them from the whole account. 📊 Find the OTTO dashboard The OTTO dashboard is not in white-label settings. Customers often look there first because both areas affect what clients see. 1. From the main navigation, open OTTO SEO or OTTO. 2. Select the website or project you want to manage. 3. The project view is the OTTO dashboard, where you review recommendations and automation for that site. Use the project switcher if you manage more than one site. White-label branding stays in Settings and does not change which OTTO project is open. 💬 Continue a closed support chat A closed chat cannot be reopened from white-label settings. Start a new conversation in the platform and mention that you are following up on a previous chat. Include the former employee's name and what still appears on screen so the teammate can locate the earlier conversation. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

🏷️ Fix White Label Name Reverting

🏷️ Why the old name comes back White-label branding is stored on your agency account and then pushed to the plugin and the white-label agent on each client site. If a former employee’s personal name was saved as that brand, or their user profile is still the source of the display name, the platform will keep applying that name when settings sync. Updating the name in only one place, such as a single client site or a personal profile, does not replace the agency brand. The next sync overwrites the site with the name still saved on the account. 📍 Where to Find It UI path: Top bar → Open Resources → Agency White Label → White Label Setup → Brand Identity → AI Assistant Name 🔍 Check where the name is set Confirm all of the following before you change client sites: - Agency or company name in your white-label or branding settings, not only a user’s first and last name. - The account you are signed in with. A former employee’s login can still own or display the old brand. - Every workspace if you manage more than one. Each workspace can keep its own white-label name. - Plugin and agent labels on a client site. These should match the agency brand after a fresh sync, not a name typed only on that site. 🛠️ Restore your company name 1. Sign in as the current agency owner or an admin, not with the former employee’s user. 2. Open your white-label or agency branding settings. 3. Replace the personal name with your company name in every brand field, including the name shown on the plugin and the white-label agent. 4. Save the settings and wait for the change to finish syncing. 5. On each affected client site, refresh or reconnect the plugin so it pulls the new brand. Do not retype the old personal name on the site. 6. Clear any site or plugin cache, then reload the client dashboard and confirm the company name appears on both the plugin and the agent. 7. Repeat the refresh for every client site that still shows the former name. 📌 If the personal name returns again A name that comes back after you save usually means another profile, workspace, or unsynced plugin is still sending the old brand. Recheck that the former employee is not the active admin, that their display name is not used as the agency brand, and that you saved the company name in white-label settings before refreshing sites. Avoid editing the label only inside a client website. Site-level text is replaced the next time the account brand syncs. 💬 Get help from the team If the company name still will not stick after you save branding and refresh the plugin, If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat. When you chat, share the company name you want, the former name that appears, and whether it shows on the plugin, the agent, or both. That lets the team check the saved brand on your account.

Last updated on Nov 03, 2026

🔍 Schema Type Not Updating After Edits

🔍 Why the schema is not in the page source Search Atlas adds schema with a script that runs after the page loads. The markup is written into the live page as JSON-LD. It is not stored as static HTML in your theme or page template, so View Source often will not show it. That is expected. Search engines and schema testers that render JavaScript can still read the markup. To confirm it yourself, open the live page, use your browser’s Inspect tool, and look for a script with type application/ld+json. A raw source check alone is not enough. ⚙️ Why the schema type stops changing Search Atlas can suggest a type, such as Service, from the page it last analyzed. After you accept or deploy that suggestion, later edits on the site do not always replace it. Changing the page in your CMS from a service page to a collection page updates your content, but it does not automatically rewrite a schema type that is already saved in Search Atlas. The type can also look stuck when an older deployment, a cached page, or a previous crawl is still what Search Atlas and search engines are reading. The suggestion and the deployed schema are separate. A new suggestion does not overwrite a deployed type until you change it and publish again. 📍 Where to Find It UI path: OTTO SEO → Overview → Schema Markup → Preview 🛠️ How to update the schema type 1. In Search Atlas, open the page that should use the new type. 2. Open its schema settings and change the type from the old suggestion, such as Service, to the correct type, such as CollectionPage. 3. Review the fields so they match the current page, then save. 4. Deploy or publish the schema from Search Atlas so the live script receives the new type. 5. Publish the page in your CMS and clear any site, CDN, or plugin cache. 6. Wait for the next crawl, or run a fresh analysis of that URL in Search Atlas. 7. Recheck the rendered page, not only the source, and confirm the JSON-LD type changed. If the page URL, canonical, or template changed, update the URL in Search Atlas first. A schema saved on the old URL will not follow the page on its own. 📊 How to confirm the new type is live - Inspect the rendered page and find one JSON-LD block for that URL. - Check that the @type value matches the type you just deployed. - Test the live URL in a renderer that executes JavaScript, such as a rich results or schema testing tool. - Compare the tested URL with the canonical URL. A mismatch can show the old schema. - Allow time after deployment. A cached copy can keep the previous type visible for a while. More than one JSON-LD block on the same page can make an old Service type appear even after you add CollectionPage. Keep a single clear type for the page unless you intentionally need more than one. 💡 If the type still does not update - Confirm you deployed from Search Atlas after changing the type, not only edited the suggestion. - Confirm the Search Atlas script is present on the live page and is not blocked by a consent tool, ad blocker, or optimization plugin. - Remove conflicting schema added by your theme, an SEO plugin, or a tag manager. - Re-analyze the exact canonical URL after cache is cleared. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

⚙️ How OTTO Schema Types Get Updated

🧩 How OTTO adds schema to a page OTTO schema is structured data that helps search engines understand what a page is about. Search Atlas suggests a schema type, such as Service or CollectionPage, and you can accept or change that suggestion before it goes live. The markup is not written into your page’s static HTML file. OTTO delivers it through the OTTO script after the page loads. That is why a normal view-source check often looks empty even when the schema is active. 🔎 Why you cannot read schema in the source View source only shows the original HTML sent by your server. OTTO schema is added in the browser, so it appears in the rendered page, not in that raw file. To confirm it is present: - Open the live page in Chrome and use Inspect, then search the Elements panel for application/ld+json. - Or use Google’s Rich Results Test on the live URL and review the detected structured data. - In Search Atlas, open the same URL in OTTO and check the schema section for the deployed type and status. A missing block in view source does not mean the schema failed. Only the rendered page or a rich-results test shows the injected markup. 🔄 How a schema type change is recognized When you change a schema type, Search Atlas must save that choice and deploy it. The label in the product updates from the saved OTTO record for that URL, not from whatever is still cached in your browser or in Google. A type change is recognized only after all of these are true: - You edited the schema on the exact page URL, not a similar URL or a template preview. - You saved or approved the new type. Closing the editor without saving keeps the old type. - Deployment for that page finished. Until then, both the live site and the Search Atlas type can still show the previous value. - You refreshed the OTTO page so the screen is not showing an older result. Older behavior that looked instant can now take a short processing cycle. The type should change in Search Atlas once the save and deployment complete. It does not change at the moment you pick a new type in a dropdown if that choice was not saved. 📍 Where to Find It UI path: OTTO SEO → Overview → Schema Markup ✅ Steps to update a schema type 1. In OTTO, open the page whose schema you want to change and confirm the URL matches the live page. 2. Open the schema drawer for the page or domain. Domain schema uses the Organization types menu (for example Organization or LocalBusiness); page schema is edited as JSON-LD, including its @type, from the drawer. There is no Service or CollectionPage option. 3. Review the fields so they fit the type you set. 4. Save or approve the change, then deploy or publish OTTO for that page if your project uses a separate deploy step. 5. Wait until the status shows the deployment is complete, then refresh OTTO and confirm the schema type now reads CollectionPage. 6. On the live URL, inspect the rendered page or run a rich-results test. Look for the new type inside the JSON-LD block. Do not judge success from view source alone. Use the rendered page plus the type shown in Search Atlas after a refresh. 🛠️ If the type still does not update Work through these checks before assuming the change was lost: - Wrong URL: www and non-www, trailing slashes, or translated URLs are separate pages. Edit the URL OTTO is actually tracking. - Unsaved edit: reopen the schema and confirm CollectionPage is the stored type, not only a selection you previewed. - Deploy still running: leave the page and return after the status is complete, then hard-refresh the browser. - Old suggestion restored: if you regenerate OTTO recommendations, a new Service suggestion can replace your manual type. Reapply CollectionPage and save again. - Script not loading: if the rendered page has no OTTO script and no JSON-LD, the install or deployment is not active on that template. Schema cannot update on the site until the script loads. - Search cache: Google can keep showing an old type for days. That does not control the type label inside Search Atlas. After a successful save, Search Atlas should show the new type on that page even if Google has not recrawled yet. If the product still shows Service after you saved CollectionPage, refreshed, and saw a completed deployment, the record did not stick and support should review that URL. 💬 When to contact support Include the exact page URL, the type you selected, the type OTTO still shows, and whether deployment is marked complete. A screenshot of the schema panel helps the team compare the saved record with the live page. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

⚙️ Stop OTTO Meta Keyword Overwrites

🔍 Why keywords appear when you did not deploy them OTTO can write meta keywords into your CMS only after a change has been deployed and then synced. If you never approved the suggestion, the keywords on the live page usually come from an earlier deploy that is still stored in the CMS, from autopilot, or from a sync that ran before you rolled the fix back. Rolling a suggestion back inside OTTO does not always erase the value already saved on the page. The next CMS sync can write that saved value again until you turn meta keywords off and clear the field. ⚙️ Turn off meta keyword deployment 1. Open OTTO SEO → Overview → Meta Keywords → Proposed Fix and find the meta keywords suggestion. 2. If the fix status is Deployed, choose Roll back. Leave suggestions you do not want as Not deployed. 3. Open OTTO deployment or automation settings for the connected site. 4. Turn off deployment for Meta keywords. If autopilot or auto-deploy is on, exclude meta keywords so new suggestions are not pushed. 5. Save the settings, then run a fresh Sync to CMS so the plugin receives the updated rules. After this, OTTO should stop placing keyword tags from that suggestion onto the page. 🛠️ Clear keywords already stored in the CMS 1. In your CMS, open the same page or post in the editor. 2. Find the SEO or meta keywords field. Delete the OTTO keywords and save or update the page. 3. Clear any CMS, SEO-plugin, or CDN cache so the old tag is not served from cache. 4. Return to OTTO and sync again. Confirm the meta keywords fix stays Not deployed or Rolled back. If your theme or another SEO plugin also outputs a keywords meta tag, turn that output off there as well. Two sources can make it look as if OTTO is still writing the tag. 📍 Where to Find It UI path: OTTO SEO → Overview → Meta Keywords 📊 Confirm the page is clean - View the published page source and search for meta name="keywords". - The tag should be gone, or it should show only keywords you typed yourself in the CMS. - In OTTO, the suggestion should not show as deployed, and a later sync should not restore it. 💡 If the keywords come back Check that only one OTTO connection is active for the site, such as one WordPress plugin install. A second connection can sync an older deployed version. Also confirm autopilot is not set to deploy all metadata, and that no bulk deploy included meta keywords after your rollback. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

💳 Fix Italy card billing declines

💳 Why the payment is declined A charge can fail even when your plan is already paid. Support has seen this on a Growth plan that remained paid through a future date. The decline came from the default card, not from an unpaid plan. If that card has no billing country, the bank falls back to the United States instead of Italy and rejects the payment. A point-of-sale default of the United States is a sign of this missing country, not a separate plan problem. 🛠️ Set the billing country to Italy Update the default card you want to keep. Do not retry with a card that is already closed, including a closed Canadian card. 1. Click the top-right avatar, then go to Finance → Billing → Plans & Top-ups → Payment Method → Manage. This opens the Manage Payment Methods screen. 2. The card editor has no billing-country field. Request a billing-address correction from support for the default card you want to keep. 3. Give support the Italian billing address the bank has for that card. Use the Rome address when that is the address on the card. 4. Retry the payment once the billing address is corrected. If the country does not stay on the existing card, add the card again at checkout and pay with Italy and the same billing address. ✅ What to avoid - Do not leave the billing country blank. A blank country makes the bank treat the charge as a United States payment. - Do not use a closed card, including a closed Canadian card. - Use the card’s real Italian billing address, not a United States address. 💬 Still need help If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

📸 GBP photo upload invitation page

📸 What this page means Customers reported that a public GBP photo upload link, which had previously worked when shared with a client, opened an invitation required page instead. Creating a new share link, including links for other accounts, showed the same page. Support reproduced the broken links and confirmed this was not caused by how the link was shared. The links failed on our side, and regenerating them did not restore access while the problem was active. ✅ What was fixed The issue was escalated and then corrected in the platform. After that correction, the same GBP photo upload links loaded normally again. No change to the client’s Google account or to the way the link is shared was required. 🛠️ What to do now 1. Reopen the shared GBP photo-upload link and confirm the upload form loads. The current error, if any, is This upload link has expired or is no longer valid — not invitation required. 2. If you prefer a fresh link, create one again and test it before sending it to your client. 3. Ask your client to open the link in a normal browser window. They should reach the public photo upload page, not an invitation page. If the invitation page is still showing, the earlier platform fix may not cover your link. Do not keep generating new links as a workaround. 💬 If the link is still blocked If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat. Include the affected account and the upload link that still shows invitation required so the team can check that specific link.

Last updated on Nov 03, 2026

🖼️ Paste Blog Images and Review Access

🖼️ When Brand Vault or ATLAS is not the best path If you already have the images and ATLAS cannot find them in Brand Vault, or adding an image from Brand Vault while editing a blog is not working, you do not need Brand Vault or ATLAS for every image. Uploading still works, but pasting is faster when the files are already on your device. 📋 Add images you already have 1. Open the blog in the article editor. 2. Copy the image from your computer or from the place where you already saved it. 3. Paste it directly into the article editor. 4. Repeat for each image you want in the post. Use this paste method instead of searching Brand Vault or asking ATLAS to insert every image. If you prefer to upload the file, that option still works; pasting is simply the quicker route when you already have the image. 👀 Who can preview and who can edit Sharing for approval works differently from editing: - Public link: Anyone with the public link can preview only. They cannot edit the content. - Editing: Editing requires the person to be a user or team member on the account. If someone only has the public link, they will be able to look at the content but not change it. Add them as a user or team member if they need to edit. 💬 Comments and product ideas Google Docs is a better place for comments than the public preview link, because the link is preview only. Collect review notes there, then apply the final edits in the article editor as a user or team member. If you want a change to how Brand Vault, ATLAS, image insert, or approvals work, submit the idea at the product portal. 💬 Need more help If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

🗑️ Bulk-delete Golden Loops and reconnect OTTO

📌 What this article covers There is no bulk option for deleting Golden Loops. Each loop is deleted individually, and a loop cannot be deleted while a run is in progress. A disconnected site can also stay offline because of a problem with its OTTO connection, such as a plugin that is not installed or is disabled. This article explains how to delete Golden Loops and how OTTO site limits work so you know your quota is expected. 🗑️ Delete Golden Loops Golden Loops are scheduled recurring routines that the platform's agent runs for you. Search Atlas does not currently offer a bulk delete for Golden Loops, so each loop is removed individually: 1. Open the Golden Loops page. 2. Click the loop you want to delete. 3. Select Delete. 4. Confirm with Yes, delete. A loop cannot be deleted while a run is in progress. Wait until the run finishes, then delete it. Repeat these steps for every loop you want to remove. 📊 Check your OTTO site quota Before treating a missing or disconnected site as a billing error, compare your plan with the sites you already have: - The PRO plan includes 4 OTTO sites. - The summit special offer adds 1 extra OTTO site on top of your plan (on PRO: 4 + 1 = 5 sites). If the number of OTTO sites on your account matches that allowance, your quota is correct. Deleting Golden Loops does not by itself add extra OTTO sites beyond the plan or summit offer. 🔌 Reconnect a site that dropped off If a site such as a client domain shows as disconnected, the cause can be the OTTO plugin not being installed or disabled, a missing or wrong plugin UUID, a stale heartbeat, or a dropped CMS connection. A site can be connected through the OTTO plugin, a pixel script, a Cloudflare worker, or a CMS gateway such as Shopify or Webflow, so the fix depends on how the site is connected. In the same chat, name the disconnected domain and say the site needs to be reconnected. If they need temporary site access to finish the connection, they will tell you. They will confirm once the site should be connected. ✅ What to expect 1. You delete each Golden Loop individually from the Golden Loops page. There is no bulk delete. 2. A loop that is running cannot be deleted until the run finishes. 3. You confirm your OTTO count matches your plan (4 sites on PRO) plus 1 extra site if the summit offer applies. 4. For a disconnected site, the cause is identified (plugin, UUID, heartbeat, or CMS connection) and the site is reconnected. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

📍 Fix Local SEO Heatmap GBP Linkage

📍 What this article covers A Local SEO heatmap can be tied to the wrong Google Business Profile even when your project, scans, and billing are otherwise fine. This article explains how that mismatch shows up and how it is corrected. 🔍 How to tell the heatmap is on the wrong listing Compare the listing behind the heatmap with the client GBP you meant to track. In the case support corrected, a 3-keyword heatmap belonged to a separate listing with 34 reviews, identified by Maps CID 6728636920081757918, not the client GBP that had 7 reviews. - Check which business the heatmap pin is actually using. - Compare review counts. A large gap, such as 34 reviews versus 7, is a strong sign of the wrong listing. - If you have it, compare the Maps CID on the heatmap listing with the client GBP. They must match the profile you intend to track. - Confirm the place you want, such as Toronto, against the pin that is currently stored. ⚙️ How the mismatch is corrected Moving the existing map pin only recenters the scan grid of the current business. It does not reassign the heatmap to a different Google Business Profile. The fix is to delete the business and create it again under the right profile, which also deletes that business's scan history. 1. Identify the correct Google Business Profile, using review count and Maps CID so it is not confused with a similar nearby listing. 2. Export or note any scan results you need to keep, because deleting the business deletes its scan history. 3. Delete the business that carries the wrong listing. 4. Create the business again under the correct Google Business Profile and rerun the heatmap. Your project and billing are not changed by this fix. 💡 After the business is recreated - Recheck that the heatmap now points at the client GBP, not the higher-review lookalike listing. - Scan history from the deleted business is gone; new scans build a new history under the correct profile. - Confirm new scans use the intended location, such as Toronto. 🛠️ If the listings still do not match If the heatmap still shows the other listing, or you cannot confirm the Maps CID and review count, ask our team to review the setup before you delete anything. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

⚙️ White Label Form Notification Emails

📧 Why form notifications still look like Search Atlas When someone submits a form, Search Atlas sends a default notification email to the Search Atlas user associated with the project. That message uses the standard Search Atlas email template. It can include Search Atlas branding, a link into the Search Atlas dashboard, and the name and contact details of the associated user. Turning on white label does not change this email. White label does not replace the sender, the template, the dashboard link, or the user details shown in the form notification. Even on a white-labeled project, form notifications stay the same. 🔗 Use a webhook instead The practical way to control how you are notified of a new submission is to set up a webhook. A webhook sends the submission data to a destination you choose, so you can deliver your own notice instead of relying on the default Search Atlas email. Open the project and go to Project Settings → Forms; email notifications are under the Configuration heading. From the forms email settings, set up a webhook for the form notifications. Use that webhook with your own system or email tool to send a message that matches your brand, your wording, and your contact details. Search Atlas will still use its default template for the built-in form notification. The webhook is the option that lets you handle the customer-facing notice yourself. 💡 Request a product change If you need the built-in form email itself to be white-labeled, submit a feature request in the Search Atlas Product Portal. Describe that form notifications should not use the default Search Atlas template, dashboard link, or associated user contact details on white-labeled projects. ✅ What to expect - The default form email goes to the associated Search Atlas user. - White label does not change that email’s template, branding, dashboard link, or shown contact details. - A webhook is the recommended way to receive submissions and send your own notification. - A fully white-labeled built-in email would need a product change requested through the Product Portal. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

🏷️ Check white label incomplete status

🏷️ What this covers Some white label setups show Configuration as incomplete even after required setup is finished. A separate issue can appear when the website look is added to your site as an iframe and the lead widget shows an invitation error. Use the checks below before contacting support. ✅ Confirm the incomplete status is only visual Open White Label setup → Review & Launch and work through its Configuration, DNS Verification, and SSL Certificate checklist — there is no Configuration section inside the branded dashboard. Support has confirmed this status can be a visual glitch when these items are already completed: - SSL is completed - DNS is completed - Branding is completed If all three are completed, you do not need to edit Configuration again just because the section still says incomplete. 🔗 Verify white label on a public report Open a public report share link and check that your white label is fully applied. When SSL, DNS, and branding are completed and the public report share link shows your white label correctly, the incomplete Configuration label can be ignored. The white label is already in effect. 🧩 Lead widget invitation error in an iframe Adding the website look to your site as an iframe is a separate issue from the incomplete Configuration status. If running that embed shows an invitation error, this has been reported to engineering as ticket WL-476 for the lead widget. There is no customer-side Configuration change that clears that error. Have these ready if you contact support: 1. A short recording of the invitation error 2. The link to the site where the iframe is installed 💬 When to contact support Contact support if SSL, DNS, or branding is not actually completed, if a public report share link does not show your white label, or if the iframe still shows the lead widget invitation error. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

💳 Credits Cannot Move Between Tools

💳 What this article covers Some customers ask whether unused credits for tools they will not use, such as Local Heatmap or OTTO, can be customized, moved, or reallocated to another tool. This article explains the answer support confirmed after checking with the team. ❌ Credits cannot be transferred between tools It is not possible to move credits from one tool to another. Each tool has its own dedicated quota allocation. Those quotas cannot be exchanged or reallocated between tools. This applies even when you do not plan to use a specific tool. Unused quota for Local Heatmap, OTTO, or any other tool stays with that tool. Support cannot customize those allocations by shifting them to a different tool. 🔄 What switching to Universal Credits does Switching to Universal Credits converts eligible recurring tool-specific entitlements into the shared Universal Credits balance. Tool quotas themselves still cannot be exchanged or moved between tools. - Tool quotas remain dedicated to the tool they were allocated to. - Quotas cannot be exchanged between tools. - Switching to Universal Credits converts eligible recurring tool-specific entitlements into the shared balance. ✅ What you can do Plan usage around the quota already assigned to each tool. If a tool such as Local Heatmap or OTTO will not be used, those credits cannot be recovered or applied elsewhere while your plan keeps separate tool quotas. The only way to use that value across tools is to switch to Universal Credits, which converts eligible recurring tool entitlements into the shared balance. For questions about how Universal Credits apply to your usage, review your plan details in the platform. 💬 Still need help If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

📧 Unexpected OTTO Site Audit Email Explained

📧 Why you received a site audit email A site audit email can look like a brand-new, one-off audit, especially if you do not remember starting one that day. In most cases it is not. When an OTTO project is created for a domain on your Search Atlas account, a Site Audit is also created for that same domain and set to recrawl about once a week. The email you receive later is the scheduled weekly recrawl of that existing project. It is not a new audit that someone started on the day the message arrived. 🛠️ What actually happened Support confirmed this pattern on a real account. An OTTO project for a domain was set up on the customer’s Search Atlas account. Creating that project started a Site Audit and scheduled it to recrawl about once a week. An email that arrived weeks later was the regular recrawl of that same audit, not a separate audit triggered that day. The domain on the email is the domain on the OTTO project, even if you do not currently think of that site as one you track. ✅ How to check it yourself 1. Note the domain named in the site audit email. 2. Review the OTTO projects on your Search Atlas account and look for that same domain. 3. If the project exists, the email is the expected weekly recrawl that was turned on when the project was created. 4. Remember that the send date is the recrawl date, not the date the audit was first created. The original audit starts when the OTTO project is set up, then repeats about once a week. 💡 If you do not recognize the domain The project was created on the Search Atlas account that received the email. Someone with access to that account set up the OTTO project for that domain, which also started the weekly Site Audit. The message is tied to that existing project. It does not mean a new audit was launched from outside your account on the day you received the email. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

🛑 Stopping Automated Reports After Account Cancellation

🔎 Why Reports May Still Be Sent Some customers who have cancelled their account still see automated reports being sent to their own clients. Cancelling or deactivating an account automatically removes the account's email address from report recipient lists, and a send-time filter also skips recipients whose accounts are no longer active. The reports stop without a separate manual process. 🛠️ How the Issue Is Resolved Report delivery stops through the automatic recipient removal and send-time filtering that apply when an account is cancelled or deactivated. No temporary reactivation or specialized manual process is involved. If reports still arrive after cancellation, support can check the affected reports. 📋 Steps to Get Your Reports Stopped 1. Open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat. 2. Tell the team that you have cancelled your account and that automated reports are still being sent to your clients. 3. Report that automated reports are still being sent to your clients after cancellation and ask the team to check them. 4. If you are being charged for an account you have cancelled, mention this in the same conversation. 🔐 If You Cannot Access Your Account If you are unable to sign in, you do not need to resolve this yourself. Share this with the team when you connect, and they will handle the account on their side. ✅ What to Expect A team member will confirm the issue and follow up with you. If the reports continue after you have been told the issue is resolved, reply in the same conversation so the team can look into it again. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

🛑 Stop automated client reports

🛑 What this article covers Use this article when you want your clients to stop receiving automated reports, but you cannot log in to change the settings yourself. This includes former users who no longer have access to the account. ✅ What actually stops the reports A support agent can disable the automated notifications on your account. Turning those notifications off stops the automated reports from being sent to your clients. This is the change that resolved the request for a customer who could not sign in. 💬 How to request this Because this change is made on the account by our team, you do not need to find a setting or update anything yourself. Contact support and ask them to disable the automated notifications so your clients no longer receive the reports. 1. Open the platform's login page — loading it does not require a completed sign-in. The account dashboard itself requires successful authentication. 2. Open the chat widget in the bottom-right corner. 3. Send your message in the chat. A member of our support team will reply in the conversation. 4. Tell the agent that you want automated client reports stopped and that you cannot log in to change it. 5. Ask the agent to disable the automated notifications from your account. 6. Confirm with the agent that this will stop reports from going to your clients. 📌 What to expect Once automated notifications are disabled on the account, clients should no longer receive those automated reports. If you later regain access and want reporting turned back on, contact support again so the account can be reviewed. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

🚀 Social posts stuck not publishing

📌 When publishing does not complete Some customers see social posts stay unpublished after they click publish. The delay can last more than an hour and can affect every connected handle for the organisation, not just one account. When this starts suddenly and hits all handles, it is treated as a possible platform bug rather than a single-account setup issue. 📸 What to capture before you report it Support needs a clear record of the failed publish so the case can be reviewed. Collect both of the following before you start a chat: - A screen recording of the publish attempt, including the post and the result after you click publish. A Loom recording, a standard video recording, or screenshots are all accepted. - Screenshots that show the post still not published and that the problem affects your organisation’s social accounts. Do not change extra settings while you record. The useful evidence is the publish action itself and the fact that the post does not go out. 🛠️ How this issue is resolved There is no customer-side setting that clears this publishing stall. After the recording and screenshots are reviewed, higher-tier support can confirm it looks like a bug and send the case to our developers. You do not need to keep retrying publish on every handle while that review is in progress. When the related ticket is marked resolved, test publishing again. Use a normal post to one of the affected accounts and confirm whether it publishes. Our team asks for that check during a 48-hour feedback period after the ticket is resolved. ✅ What to check in the feedback window 1. Wait until you are told the ticket is resolved. 2. Publish a test post to an affected social account. 3. Confirm whether the post appears on that account within a normal time, not after an hour-long stall. 4. Repeat on another handle if the first test succeeds and you want to confirm the wider fix. 5. If posts are still stuck, contact support again with a fresh recording and screenshots from the new attempt. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

🔍 Restore Free AI Visibility Queries

💡 What happened to the free preset queries If you removed the free AI Visibility queries that come preset on a project, those queries were not gone for good. Free preset queries cannot be deleted: removing one only deactivates it. This is true even if you removed them while demonstrating a site and did not save other changes. The original preset queries can be restored by our team. 📊 How credits work for AI Visibility queries Custom queries consume credits from your plan. The only queries that do not consume credits are the free ones preset by our system. After the free presets are deactivated, any queries you add yourself are treated as custom queries and will use credits. Unlike the free presets, queries you create yourself are deleted when you remove them. - Free preset queries: included by the system and do not consume credits. - Custom queries: queries you create, and they consume credits. 🛠️ How to get the free presets back Customers cannot reactivate the free presets from the project themselves. Restoration is handled by our team, which confirms the original queries are still available and reactivates them for the affected projects. 1. Open the live chat widget in the bottom-right corner of the platform. 2. Send your message in the chat. A member of our support team will reply in the conversation. 3. Name each project that is missing the free presets and say that the free AI Visibility queries were removed or deactivated. 4. Ask the team to restore the original free preset queries. Do not recreate them as custom queries if you want them to stay free of credit use. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

💳 How to Clear an Overdue Account Payment

💳 What an overdue payment means An overdue payment means Search Atlas has not yet received a successful payment for an open invoice. Access to paid features can stay limited until that balance is cleared. A payment you already sent can still show as overdue if the charge failed, the bank is holding it, or the payment was not matched to the correct invoice. 🔍 Check your billing status Before requesting a manual review, confirm what the platform currently shows: 1. Sign in to your Search Atlas account. 2. Open Billing or Account settings. 3. Review open invoices, the amount due, and the payment method on file. 4. Note the invoice number, amount, and the date you attempted payment. If the status is Paid but features are still locked, the payment may need to be applied to your account. If it is Failed, Past due, or Pending, use the steps below. 🛠️ Clear the balance yourself Most overdue balances can be cleared from the billing page: 1. Update the card or payment method if the previous one expired, was declined, or has insufficient funds. 2. Select the open invoice and choose Pay Invoice (also labeled Pay for Invoice). 3. Complete the payment and wait for a success confirmation. 4. Refresh the billing page and confirm the invoice status changes to Paid. Card payments are often confirmed within a few minutes. Bank transfers and some international payments can take several business days. Keep your bank or card receipt until the invoice shows as paid. ⚠️ Why a payment may not clear A balance can remain overdue for these common reasons: - The card was declined, expired, or blocked by the bank. - The charge is still pending with your bank or card issuer. - The payment amount does not match the open invoice. - The payment was sent without the invoice number, so it could not be matched. - More than one invoice is open and only one was paid. - A refund, chargeback, or reversed payment put the invoice back to overdue. Waiting alone does not clear a failed charge. If you have already waited several weeks, the payment likely needs a billing review rather than more processing time. 📄 Information to have ready If you need the team to locate and apply a payment, gather: - The account email address. - Each invoice number and amount. - The payment date and confirmation or transaction ID. - The last four digits of the card or the bank reference, if available. - A short note describing what still appears overdue. Do not send full card numbers or other sensitive payment details in chat. 🚀 After the payment is applied Once the invoice is marked Paid, account access is normally restored automatically. Sign out and back in if a paid feature still looks locked. If a new invoice was created after the overdue one, that separate balance must also be paid. 💬 When to contact support Contact support if a successful payment is still overdue after a reasonable processing window, you cannot update the payment method, or you are unsure which invoice remains open. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

📊 Content Genius Credits and Relevance Guide

💳 How Content Genius credits work Content Genius reserves credits from your plan quota when the generation is dispatched, before the content is created. The credits shown before you start are reserved at dispatch. Credits are tied to a dispatched generation, not to opening the tool or editing a draft by hand. Check your remaining balance in Content Genius before you generate so you know what the run will use. ⏱️ What happens when a run times out or sticks A run that never finishes should not be treated as a successful generation. If the screen stays on Review, the progress bar stops, or the page times out before content appears in your project, the generation has failed. Before you start the same request again, do the following: 1. Wait a few minutes and refresh the project page. 2. Confirm that no new article was saved under your project content. 3. Note the approximate time, the page or keyword, and whether the status was still Review. 4. Do not launch repeated retries while the first run may still be processing, because each completed result uses credits. A run that never finishes is refunded automatically. One exception: a crashed run can stay in generating until the system marks it failed, and that run is not refunded. 🎯 Why content may mention competitors Content Genius writes from the topic, keywords, and business details in your project. If those inputs are thin, or if competitor names appear in the target keyword, brief, or reference URLs, the draft can discuss those brands instead of yours. To keep the article about your business: - Add your business name, website, location, and main offer in the project or brief. - State who you serve and what you want the reader to do next. - Avoid using a competitor’s brand as the primary keyword unless you are writing a comparison you control. - Remove competitor URLs from references if you do not want those brands featured. - After generation, edit any remaining competitor mentions before you publish. A draft that finishes and is saved still uses credits, even if you later rewrite the angle. Relevance problems are fixed by clearer inputs and editing, not by treating a delivered article as a failed run. 🛠️ If a crashed run kept your credits A crashed run that stays in generating until the system marks it failed is not refunded automatically. If that happened, have the project name, keyword or title, date and time, and a short note that nothing was saved. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat. Share those details in the chat so the team can match the run and return any incorrectly deducted credits. Do not start a large batch of retries while the review is open. ✅ How to avoid repeat issues - Generate one article at a time if you have seen timeouts. - Use a stable connection and keep the tab open until the result is saved. - Put your brand and offer in the brief before you generate. - Review the saved article for competitor mentions before publishing. - Contact the team only for runs that consumed credits without delivering content.

Last updated on Nov 03, 2026

💳 Payment Processing and Delayed Payouts

💳 How payments are processed Search Atlas bills on a recurring schedule tied to your plan. When you subscribe or renew, your payment method is authorized first and then settled by your card issuer or bank. Authorization can appear immediately, while settlement often takes additional business days. A payment is considered cleared only after it moves from pending to paid on your billing record. Weekends, bank holidays, and your bank’s own review can add time. International cards and some debit methods often take longer than domestic credit cards. The status shown in your account is the source of truth, not the pending line on a bank statement. 📅 Typical timing - New subscription or plan change: access usually follows a successful charge, even if the bank still shows the amount as pending. - Renewal: charged on your billing date. Failed attempts may be retried before the invoice is marked unpaid. - Refunds: once issued, card refunds commonly take several business days to appear, depending on the issuer. - Payouts (such as partner or affiliate earnings, when your account is eligible): processed on a set schedule after earnings are approved. Bank deposit can take extra business days after we release the payout. A wait of several weeks is longer than a normal card settlement. It usually means the payment failed, is on hold for verification, or was never released because a payout requirement was not met. 🛠️ Why a payment or payout may be delayed - Card or bank decline: expired card, insufficient funds, or a bank fraud hold. - Billing details mismatch: name, address, or postal code does not match the payment method. - Unpaid invoice: a retry is still in progress or the method needs to be updated. - Payout verification: tax or identity details, or a connected payout account, are incomplete. - Minimum threshold: earnings have not yet reached the amount required for a payout. - Review hold: unusual activity can pause a payout until it is reviewed. - Bank timing: the payout was sent, but your bank has not posted it yet. ✅ What to check before you contact support 1. For charges, open Billing → Invoices and note the status, date, and amount. Earnings payouts are not shown in Billing — affiliate payouts use the separate affiliate dashboard. 2. Confirm the payment method is valid and that your billing address matches the card or bank. 3. For payouts, confirm your payout account, tax details, and that you are above any minimum. 4. Check whether the charge appears as pending, posted, or missing on your bank or card statement. 5. Look for a failed invoice or a retry date rather than assuming the original attempt is still processing. 6. Allow standard bank posting time after a status of paid or sent before treating it as lost. Have the invoice or payout reference, the amount, the date you expected it, and a short description of what your bank shows. That lets our team trace the transaction without asking you to repeat the basics. 🚀 If you have been waiting a long time If a payment has been pending for well beyond a few business days, or for about a month or more as in a delayed payout, do not submit a second payment unless your account shows the invoice is still unpaid. A duplicate charge can create a separate refund cycle. Update a failed card first, then ask us to confirm whether the original attempt settled, was reversed, or never left a review hold. We can check the processor record, explain the status in plain language, and tell you the next action. We cannot speed up your bank’s posting time after funds have already been sent. 💬 Get help in the platform If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

🚫 Fix a Published Article 403 Validation Failure

🚫 What the 403 validation error means Search Atlas checks the published article URL before it treats the page as available. A 403 status means the server understood the request but refused access. The article is not loading for our checker, so validation fails even if the link looks correct in your browser. 👀 Why the page can look live to you Your own browser may already be logged in, on an allowed network, or passing a security check that an outside request does not. A bookmark, cached page, or preview can also open while a fresh request from another location is blocked. If the public URL returns 403, the article is not fully reachable. 🛠️ Common reasons a live URL returns 403 - A firewall, CDN, or bot rule is blocking automated or unknown visitors. - The page, folder, or host requires a login or an allowlist. - Country, IP, or hotlink rules reject requests from outside your office. - File or directory permissions on the server deny public access. - The published URL points to a protected, draft, or wrong address. - A security plugin treats the checker as unwanted traffic. ✅ How to restore access 1. Do not treat a logged-out public URL as validation. In Publication Media, open the published article and click Validate Fixes. 2. Confirm the address matches the URL saved for the article, including https and the final path. 3. In your host, CDN, firewall, or security plugin, allow public GET access to that page and do not challenge or block unknown visitors. 4. Remove login walls, IP limits, and geo blocks from the article URL unless the page is intentionally private. 5. Check server permissions so the public web user can read the page. 6. Clear the CDN or site cache, then request the URL again and confirm it returns 200. 7. Republish or recheck the article in Search Atlas after the URL loads without a block. 🔍 How to confirm the fix The validation error clears only when the article URL loads successfully for an outside request. A page that opens only while you are logged in, or only from your office, will still fail. Test the same URL logged out and from a private window before you recheck it. 💬 When to contact support If the public URL returns 200 and the 403 message remains after a fresh check, share the article URL and a screenshot of the error. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

💰 How Writer PayPal Payments Are Released

💰 What a Pending Writer Payment Means A pending writer payment is earnings for published articles that have not been sent yet. After an article is published and approved, its amount is added to your writer balance and waits for the next payout batch. 📅 How Monthly PayPal Batches Work Approved payments are grouped into a monthly batch and sent to the PayPal email saved in your payment profile. A payment is included in the current batch only when it is fully approved before that batch closes. Amounts still in review, on hold, or tied to articles that are not published move to the next batch. Search Atlas pays the PayPal address on your profile. A batch cannot be redirected to a different address after it has been submitted. ✅ Check Whether Your Payment Qualifies - Confirm each article is published and approved. - Confirm the payment status is pending release, not in review or on hold. - Confirm the PayPal email in your profile is the account that should receive the funds. - Compare the amount in your writer balance with the articles you expect to be paid for. Update an incorrect PayPal email before the batch closes. Eligibility is based on the payment record, not on a requested amount alone. 🛠️ If a Payment Is Missing From This Month 1. Open the Writer Dashboard and review This Month's Remittance and the Remittance List. Note each article title, amount, Paid at date, and PayPal email. 2. Check whether approval happened before the current batch closed. Later approvals are paid in the following cycle. 3. Verify that the PayPal email is complete and spelled correctly. 4. After a batch is sent, allow extra time for the transfer to appear in PayPal. This article cannot add a specific payment to an open batch. A teammate can review the record and confirm whether it qualifies for the current release. 💬 Get Help With a Specific Payout If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat. Have the article titles, expected amount, and PayPal email from your profile ready so the review is faster.

Last updated on Nov 03, 2026

🔍 Restore a Missing Courtesy OTTO Site

🎁 What a courtesy OTTO site is Some Search Atlas accounts receive a complimentary extra OTTO site when they first join. This is a promotional slot added to the account. It is not a separate product you purchase, and it does not always stay visible as its own labeled item in billing. If you open OTTO and the platform asks you to pay before you can add another site, the courtesy slot may be missing, already used, or no longer attached to the current plan. 👀 Why the extra site may not appear A courtesy slot can disappear from view for a few common reasons: - It was already used. The extra site was connected earlier and now counts as one of your active OTTO sites. - The account changed. A plan upgrade, downgrade, renewal, or switch to a different workspace can change which slots are included. - You are in a different account. The offer was applied to the original login or workspace, not the one you are viewing now. - The promotion ended. Some signup offers are time-limited and are removed when the offer period closes. - Billing is showing paid add-ons only. The screen may list sites you can buy, even when a complimentary slot should still be available. 🛠️ Check your account before you pay 1. Sign in with the same email you used when you first joined Search Atlas. 2. Confirm you are in the correct workspace or project, if your account has more than one. 3. Open OTTO SEO → All Sites and review your current sites. Look for a site you added earlier that may already be using the complimentary slot. 4. Open your plan or billing area and note how many OTTO sites are included, how many are in use, and whether an add-on price is shown for the next site. 5. Do not purchase an extra site yet if you believe the complimentary slot should still be active. A new charge will not automatically restore a missing promotion. 💬 Ask the team to review the offer Courtesy slots are reviewed on the account that received the original offer. A teammate can check whether the extra site is still available, already in use, or no longer included, and can explain what you will see in OTTO. When you contact support, share the email on the account, the approximate date you joined, and a short note that you were given an extra OTTO site at signup and now see a payment prompt. Screenshots of the OTTO site list and the payment prompt are helpful. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

🎫 Ticket Status and Campaign Quote Limits

🎫 What this article covers This article explains how to check the status of an open support ticket and what the message campaign quote used up means. These are separate items. A usage message does not stop our team from reviewing your ticket, and an open ticket does not by itself change your campaign limits. ⏱️ How ticket status works When you contact support, your request is handled in the live chat widget in the bottom-right corner. The conversation continues in that thread until it is resolved. Time since you first wrote does not always match time spent actively working on it. Tickets are handled in the order they are received, and some need extra review before we can reply with a clear answer. Replies can take longer when volume is high or when the question needs a specialist. A slower reply does not mean your request was lost. Keep using the same conversation rather than starting a second one, because a duplicate splits the history across two threads. 🔍 How to check your ticket 1. Open the live chat widget in the bottom-right corner of the platform. 2. Look for your existing conversation rather than starting a brand-new one. 3. Review the latest reply. If we asked for a screenshot, account detail, or campaign name, send that in the same thread. 4. If there is no new reply and you only want a status check, send one short follow-up in that same conversation. Include the campaign name and a short description of what you expected to happen. Do not resend the full original message unless we ask for it. 📊 What campaign quote used up means Campaign quote used up is a limit message about campaign usage. It is not a broken page and not proof that your account is corrupted. The exact allowance it refers to depends on where the message appears, so note the page or feature you saw it on. You may see it when you try to launch, refresh, or continue campaign work. Other parts of the platform can still be available. The message alone does not tell us which campaign it concerns or whether a plan change is the right next step. 🛠️ Is this a technical issue that must be fixed first? Usually, no. The message is expected when a campaign usage limit is reached. It does not have to be fixed before we can check your ticket, and you do not need to wait for a ticket reply before you review your own usage. Treat it as something to investigate only if the message appears when you believe unused allowance should remain. In that case, tell us: - The exact wording on screen and the page or feature where it appeared. - The campaign name and what you were trying to do. - When you first saw the message. - Whether the same message appears on every campaign or only one. Our team can then confirm whether the allowance was correctly used or whether something needs to be corrected. Please do not retry the same launch many times while you wait. Repeated attempts will not restore a used allowance. 💡 What you can do next - Keep one conversation open for the ticket status. - Check whether your plan allowance for campaigns has been fully used. - Pause new campaign launches that show the same message until usage is confirmed. - Continue unrelated work that does not depend on that allowance. If your business need is urgent, say so once in the existing thread and describe the deadline. Urgency helps us prioritize context, but it does not bypass the order of review or change your plan limits by itself. 💬 When to contact support Contact support if the ticket has had no update after you already sent the details we requested, or if campaign quote used up appears even though you believe allowance should remain. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

📊 Fix Heatmaps Not Loading in Reports

📊 What this issue means When heatmaps do not load in a report, the page usually opens but the visual map stays blank, spins, or never finishes. Your other report sections may still look normal. This is a display problem in most cases, not missing SEO data. 🔍 Common reasons heatmaps stay blank - The report is still processing. Large sites and date ranges can take longer to draw the map. - Filters hide all activity. A page, device, country, or date range with no visits leaves the heatmap empty. - The browser blocked the visual. Cache, extensions, or a strict privacy setting can stop the map from rendering. - The selected page has little or no tracked traffic in the period you chose. - A temporary platform delay can interrupt loading even when the same report worked earlier. 🛠️ Steps to get the heatmap to load 1. Open the report and wait for loading to finish. Do not click away while the map is still loading, and do not rely on a one-minute refresh. 2. Confirm the date range includes days when the page received visits. 3. Clear extra filters. Set device, location, and page filters back to a broader view, then apply them again one at a time. 4. Select a page you know has traffic. If that page loads, the original page may simply have no heatmap data for that period. 5. Refresh the report with a hard reload. On most browsers, hold Ctrl and press F5 (or Cmd and Shift and R on a Mac). 6. Try a private or incognito window. If the map appears there, disable ad blockers or privacy extensions for Search Atlas and reload. 7. Sign out, sign back in, and open the same report once more. ✅ How to confirm it is fixed A working heatmap shows colored areas on the page preview and updates when you change the date range or page. If colors appear for a high-traffic page but not for another URL, the second page likely has too little activity to draw a map. 💡 If the same report fails again - Note the report name, the page URL, the date range, and whether any filter was on. - Note whether other reports load heatmaps in the same browser. - Try one other browser before you contact support so we can tell a local block from a report issue. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

🔍 Resolving Dynamic Indexing Dashboard Count Mismatches

🔍 Why the Count Looks Different The dynamic indexing dashboard and the URL list are two different views of the same job. The dashboard shows a summary count, while the URL list shows each page individually. When the two appear to disagree, it usually means they were refreshed at different moments or are counting slightly different things. 📊 Common Reasons for the Mismatch - Timing lag: The dashboard summary can update on a short delay, so a page may show as deployed in the URL list before the counter catches up. - Pages awaiting a final check: A page can be deployed but still waiting for confirmation before it is counted as complete. - Filters or status views: The URL list may show all pages, while the dashboard counts only pages in a specific state. - Retries after a temporary issue: A page that failed once and was retried may be counted differently until the retry finishes. - Stale browser data: An older view of the platform can display outdated numbers. ⚙️ Step-by-Step: Find the Incomplete Pages 1. Refresh the dynamic indexing dashboard and note the completed and total counts. 2. Open the Site Audit URL/issue list and filter by status. Pages are not marked complete — look for pages that were not crawled or still have open issues. 3. Compare the number of incomplete pages in the list with the difference shown on the dashboard. 4. Wait a few minutes and refresh both views again, since counts often settle after a short delay. 5. Clear your browser cache or open the platform in a private window if the numbers still do not match. 🛠️ What to Do If Pages Remain Incomplete If the gap persists after refreshing, review each page that was not crawled or still has open issues. Confirm that the URL loads normally and is not blocked by a redirect, access rule, or error. Fix any issues you find, then allow the job to run again so the pages can be processed. 🚀 Tips to Avoid Future Mismatches - Check the dashboard after the job has had time to finish rather than immediately after starting it. - Use the URL list to confirm individual pages instead of relying only on a summary number. - Keep your page list current so pages are not added or removed in the middle of a run. 💡 Frequently Asked Questions Does a mismatch mean my pages are not indexed? Not necessarily. It usually reflects timing or status differences between the two views. Will the counts ever match exactly? Yes. Once all pages finish processing and both views refresh, the numbers should align. 🤝 Getting Further Help If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

🗺️ Troubleshooting Heatmap Radius Settings That Won't Change

🔍 Why Heatmap Radius Changes May Not Save If you cannot change the radius setting on your heatmap, the cause is usually one of the following: your current plan or user role does not include editing this setting, the browser is showing an outdated version of the page, or the change was entered but not saved. Work through the steps below in order. ✅ Step 1: Confirm Your Access Level Some heatmap controls are limited to certain roles or plan levels. - Check that you are signed in to the correct Search Atlas account. - Confirm with your account administrator that your user role allows editing heatmap settings. - Make sure your subscription includes the feature you are using. 🔄 Step 2: Refresh and Clear Your Browser Cache An old page can display controls that no longer respond correctly. 1. Reload the page fully by holding Shift while selecting refresh. 2. If the problem continues, clear your browser cache and cookies for the platform. 3. Sign out, close the browser, and sign back in. 🌐 Step 3: Try a Different Browser or Device Browser extensions, such as ad blockers or privacy tools, can block parts of the interface. Open the platform in a private or incognito window with extensions disabled. You can also try another supported browser to see whether the issue is specific to your setup. 💾 Step 4: Enter and Save Your New Radius Value Make sure you complete the change before leaving the screen. 1. Locate the radius setting within the heatmap controls. 2. Enter the new value and confirm it is within the allowed range. 3. Select the save or apply option, then wait for the confirmation message. 4. Reload the page and check that the new value is still in place. 📊 Step 5: Check the Heatmap Data After a successful change, the heatmap may take a short time to refresh. If the map does not update, allow a few minutes and reload the page. If the radius appears to change but the results look the same, check the date range and filters you have applied, as these can affect what is displayed. 🛠️ Still Having Trouble? If none of the steps above resolve the problem, please gather the following details before contacting us so we can help more quickly: - The name of the project or domain you are working on. - The exact radius value you tried to enter. - A short description of what happens when you select save. - The browser and version you are using. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

🔍 Fix Failed Competitor Domain Adds

🔍 What this issue looks like In AI Visibility, open Manage Competitors, and paste a domain such as lccc.wy.edu. A full URL, path, query string, trailing slash, protocol, or www prefix is not converted to the bare domain. The add is rejected silently, with no error message, so the domain never appears in the list. Enter the plain domain only, such as lccc.wy.edu. ⚙️ Why a competitor domain may not save AI Visibility accepts a clean, public website domain. Prefixes and extra path text are not stripped automatically, so they cause a failed add. A save can fail when: - Hidden paste characters: Spaces, line breaks, or invisible characters copied from a browser or document can make a correct-looking domain fail. - Already on the list: The same domain, including a close variant already saved, will not be added again. - Competitor limit reached: Your plan or project may already be at the maximum number of tracked competitors. - Not a public website: Internal, login-only, or unreachable hosts cannot be tracked for AI visibility. Educational domains such as .edu are allowed when they are public websites. The extension alone does not block the add. 🛠️ Add the competitor correctly 1. In AI Visibility, open Manage Competitors. 2. Remove anything already in the domain field. 3. Enter the plain domain, for example lccc.wy.edu. Do not include protocol, www, or a path: paste or type the bare domain only. 4. Confirm the domain is not already listed, including with or without www. 5. If your list is full, remove a competitor you no longer need, then add the new domain. 6. Submit the domain once and wait until the list refreshes. Avoid clicking add repeatedly. 7. Refresh the AI Visibility page and check Manage Competitors again. Use the registrable host customers actually visit. For a site that lives only on a subdomain, enter that subdomain exactly, such as lccc.wy.edu, not a shorter parent domain that does not serve the site. 📊 Check that tracking can start After the domain appears in the list, AI Visibility still needs a publicly reachable site before competitor insights can populate. Confirm these points: - The domain opens in a browser without a login wall. - It is spelled exactly as the live site, including any required subdomain. - You added it to the correct project if you manage more than one site. - You allow a short time for data to appear. A newly saved competitor may not show metrics immediately. If the domain saves but metrics stay empty, tracking has started and results are still processing. That is different from the domain never appearing in the list. 💡 If the domain still does not appear Clear the field, enter lccc.wy.edu again, and try once more after a page refresh. Also remove one existing competitor if you may be at your limit, then add the domain again. If the list still does not update, our team can check the project, the competitor cap, and whether that host is being rejected by validation. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

🛠️ Fixing WordPress Publish Sync on Namecheap

💡 What This Issue Looks Like If your WordPress site is hosted on Namecheap, you may occasionally find that content you try to publish from Search Atlas does not appear on your site. The sync may fail silently, show an error, or hang indefinitely. This is almost always caused by a hosting-level restriction or a plugin/configuration issue on the WordPress side, and it can usually be fixed in a few minutes. 🔍 Common Causes on Namecheap Hosting - Security plugins blocking connections: Plugins like Wordfence, Sucuri, or iThemes Security can block the application password connection Search Atlas uses to publish. - Missing or revoked Application Password: Search Atlas authenticates to WordPress using an Application Password. If it was revoked or regenerated, publishing will fail. - ModSecurity firewall rules: Namecheap enables ModSecurity by default, which can sometimes block legitimate REST API requests from external services. - Outdated WordPress or PHP version: Older PHP versions on Namecheap plans may not fully support the WordPress REST API authentication method. - Caching or CDN interference: Aggressive caching can delay or block API calls to your site. ⚙️ Step 1: Verify Your Connection 1. In Search Atlas, go to your connected sites list and confirm your WordPress site shows a Connected status. 2. If it shows an error or disconnected, remove the connection and reconnect it. 3. During reconnection, make sure you enter your full site URL (including https://) exactly as it appears in your browser. ⚙️ Step 2: Check or Regenerate Your Application Password 1. Log in to your WordPress dashboard. 2. Go to Users → Profile and scroll to the Application Passwords section. 3. If an existing password for Search Atlas is listed as revoked or inactive, revoke it and create a new one. 4. Copy the new password (it is shown only once) and use it when reconnecting your site in Search Atlas. ⚙️ Step 3: Allow Search Atlas in Your Security Plugin If you use a security or firewall plugin, add Search Atlas requests to its allowlist. In Wordfence, for example, go to Wordfence → Firewall → Blocking and remove any blocks tied to your site's own domain or Search Atlas requests. Temporarily disabling the security plugin and retrying a publish is a quick way to confirm whether it is the cause. ⚙️ Step 4: Check ModSecurity in Your Namecheap Panel 1. Log in to your Namecheap cPanel or hosting dashboard. 2. Find the ModSecurity section (often under Security or Advanced). 3. Temporarily disable ModSecurity for your domain, then retry publishing from Search Atlas. 4. If publishing now works, contact Namecheap support and ask them to whitelist the blocked requests rather than leaving ModSecurity off permanently. ⚙️ Step 5: Update PHP and WordPress 1. In your Namecheap cPanel, open MultiPHP Manager (or the PHP version selector in your dashboard). 2. Set your domain to PHP 8.0 or higher. 3. In WordPress, go to Dashboard → Updates and install any pending WordPress updates. 4. Retry your publish after updates complete. 📊 How to Confirm the Fix Worked - Publish a short test post from Search Atlas and confirm it appears on your live site. - Check Posts in your WordPress dashboard to verify the post exists even if caching delays its visibility on the front end. - If a post exists in WordPress but not on your site's front end, clear your cache (both your caching plugin and any Namecheap server-side cache). 🚀 Still Not Syncing? If you have completed all the steps above and publishing still fails, gather your site URL and a description of any error message you see. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

🧊 Detaching Site Audit from Deep Freeze

💡 What This Article Covers If a client relationship has ended, you may want to keep their OTTO project preserved indefinitely in Deep Freeze while freeing up your Site Audit seat for other work. This article explains what Deep Freeze does, how it interacts with Site Audit, and the steps to detach a site from Site Audit without losing your frozen project. 🔍 Understanding Deep Freeze and Site Audit Deep Freeze is a preservation mode for OTTO projects. It pauses all active optimization work and stores the project's settings, data, and history, so you can reactivate it later without starting over. Deep Frozen projects do not consume active OTTO processing. Site Audit is a separate tool that crawls a website to identify technical SEO issues. A Site Audit seat is occupied whenever a site remains connected to the Site Audit tool, even if the associated OTTO project is Deep Frozen. This means a Deep Frozen OTTO project can still hold onto a Site Audit seat if the site stays attached. To free the seat, you need to detach the site from Site Audit while leaving the OTTO project in Deep Freeze. 🛠️ How to Detach a Site from Site Audit Follow these steps to remove the site from Site Audit while keeping the OTTO project Deep Frozen: 1. Log in to Search Atlas and open the OTTO project you want to preserve. 2. Confirm the project status shows Deep Freeze. If it does not, enable Deep Freeze first so the project is safely preserved before making changes. 3. Navigate to the Site Audit section within the project. 4. Open the OTTO project and use the control labeled unfreeze the site. or Unfreeze. 5. Confirm the detachment when prompted. This releases the Site Audit seat back to your plan. 6. Return to your project list and verify the OTTO project still shows as Deep Frozen. Once completed, the site no longer occupies a Site Audit seat, and the OTTO project remains frozen and available for future reactivation. 📊 What Is Preserved After Detaching Detaching a site from Site Audit does not delete your OTTO project or its frozen state. The following is preserved: - OTTO project status: The project remains in Deep Freeze indefinitely until you choose to reactivate it. - Project settings and history: All configurations and past OTTO activity remain stored. - Reactivation option: You can re-enable the project at any time. Note that Site Audit reports and crawl data for the detached site will no longer be accessible or updated. If you need those reports later, you can reattach the site to Site Audit, which will occupy a seat again. ⚙️ Important Considerations Before Detaching - Export reports first: If you or the former client may need past Site Audit reports, download or export them before detaching, as historical crawl data will not be recoverable afterward. - Deep Freeze stays active: Detaching from Site Audit does not unfreeze or cancel the OTTO project. No action is needed to maintain the frozen state. - Seats are freed immediately: The released Site Audit seat can be assigned to another site right away. - Reattachment uses a seat: If you later reattach the site to Site Audit, it will occupy a seat while the OTTO project can remain frozen. ❓ Frequently Asked Questions Will detaching Site Audit delete my Deep Frozen project? No. The OTTO project remains safely stored in Deep Freeze. Detaching only removes the site from the Site Audit tool. Can I keep the site frozen forever without using any seats? Yes. A Deep Frozen OTTO project with the site detached from Site Audit does not occupy a Site Audit seat and can remain frozen indefinitely. Can I reactivate the project later? Yes. Reactivating the project will resume OTTO activity. If you also want Site Audit for that site again, you will need to reattach it, which will use an available seat. 🤝 Still Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

💰 When Article Publisher Payouts Are Due

📅 How publisher payout timing works Publisher payouts are not sent on the same day an article goes live. After publication, Search Atlas reviews the placement, confirms it meets the agreed requirements, and then includes the amount in the next payment cycle. A payment can still be pending even when the article was published weeks earlier. The publish date and the payout date are different. Use the dates shown in your publisher dashboard, not only the live date on the site, when you check whether a payment is late. ⏱️ What usually happens after an article is published 1. Publication: The article goes live on the publisher site. 2. Verification: The placement is checked against the order, including the URL, content, and required links. 3. Approval: Once verified, the payout is marked as approved and queued. 4. Payment cycle: Approved amounts are paid on the next scheduled cycle, not as a separate instant transfer for each article. If several articles were published in the same month, they are often grouped into one payout after each item is approved. One article still in review can make the combined payment look overdue even when the others are already complete. 🔍 Why a payout may still be pending - The article is live, but verification or approval is not finished. - The live URL, anchor text, or content does not match the order. - The placement was edited or removed after it was first published. - Payout details, such as your payment method, are missing or need an update. - The amount is approved but waiting for the next scheduled payment run. - A minimum payout threshold has not been reached yet. A wait of more than a month after publication is a valid reason to ask for a status check. It does not always mean the payout was missed. Many delays are caused by an item still sitting in review or by payout details that need a quick update. 🛠️ How to check your payout before you escalate 1. Open Earning History (heading Earning, payout text Payouts). It lists payouts by date, article count, status, PayPal transaction ID, amount, and PayPal email. It does not list each article by order or live URL. 2. Note the status, such as published, in review, approved, queued, or paid. 3. Compare the publish date with the approval date and the expected payout date, if one is shown. 4. Confirm your payment method and account details are complete and current. 5. Check whether the articles are listed separately or combined into one payout. Gather this information before you contact support. It lets the team trace the exact placements instead of searching only by publish month. 📋 What to send if payment still looks overdue Include a short list for every article that you believe is unpaid: - Article or order name - Live URL - Publish date - Current status shown in the platform - Expected amount, if it is displayed Do not resend the full article text. The URLs and statuses are enough for a payout review. If a status says paid, also check the payment reference and the account that received it before opening a new request. 💬 When to contact support Contact support if an article has been published, the platform still shows the payout as pending well after the expected cycle, or the status does not match what is live on the site. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

📰 Request More Publication Media Orders

📌 Why orders are not guaranteed Publication Media matches buyer requests with publisher sites that fit the brief. A strong domain rating and healthy traffic help your sites qualify, but they do not by themselves create orders. Buyers also look at niche fit, price, turnaround time, content rules, and recent delivery quality. When demand in your categories is low, or your offer does not match open briefs, new orders can slow or stop even if your metrics look good. ✅ Check that your sites can receive work Before you ask for more orders, confirm each property is ready to be matched: - Active status: The site is published in Publication Media and set to accept new orders. - Complete profile: Niche, language, country, sample topics, and do-follow or no-follow rules are filled in and accurate. - Clear pricing: Guest post and any other offered placement types have current prices and realistic turnaround times. - Content guidelines: Buyers can see what you accept and what you reject, including sensitive topics and link limits. - Site status: The publication site is marked Active, not Inactive or Paused. Outdated prices, missing categories, or a paused listing are common reasons a qualified site stops receiving work. 🛠️ Improve your chance of being selected You cannot force the marketplace to send orders, but you can make your sites easier to choose: 1. Align niches with real demand. List the topics you can actually publish. Overly narrow or mismatched categories reduce matches. 2. Keep prices competitive for your metrics. Very high prices relative to similar sites in the same niche often sit unmatched. 3. Offer practical turnaround. Shorter, reliable delivery windows are easier for buyers to accept. 4. Protect quality. Publish on time, follow the approved brief, and avoid last-minute rejections after an order is accepted. 5. Update metrics when they change. If traffic, niche, or editorial focus shifts, refresh the listing so matching stays accurate. Consistent delivery matters as much as domain rating. Sites with missed deadlines or repeated disputes are less likely to be prioritized. 🚀 How to request more orders There is no self-serve button that assigns new buyer orders to your account. Our team can review your listings, confirm they are eligible, and note your request for upcoming matches. Have this ready before you contact us: - The site URLs that should receive orders - Each site’s main niches and languages - Whether you want guest posts, niche edits, or both, if those options are offered - Your current prices and maximum monthly capacity - Any recent pause, rejection, or unfinished order you want reviewed A review confirms eligibility and listing quality. It does not promise a specific number of orders or a delivery date, because volume depends on buyer demand. 💬 What to expect after you ask We will check that your sites are visible, complete, and not blocked by an account or order issue. If something is limiting matches, we will tell you what to update. If your listings are already in good shape, they stay in the pool for relevant briefs. New orders appear in your Publication Media orders area when a buyer selects your site. Check that area regularly so you can accept work before the request expires. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

💰 Inactive Publisher Accounts and Late Payouts

📌 What this article covers This article explains why a publisher account, or a teammate’s account, can show as inactive and why a payout may take longer than the week you expected. Use the checks below before opening a support chat so the team can resolve the hold faster. 🚫 Why an account shows as inactive Inactive does not always mean the account was closed. It usually means the account cannot earn, refer, or receive a payout until a requirement is finished. Common reasons include: - Setup is incomplete. Profile, payment, or tax details were never finished or were saved only in draft. - Verification is pending or failed. Identity, business, or tax information does not match, or a document was rejected. - The payment method is missing or invalid. A bank account, PayPal, or other method was removed, expired, or failed a check. - A compliance hold is in place. Unusual activity, a policy review, or a mismatch in account ownership can pause the account. - Teammate access is limited. A teammate may see an inactive or restricted view because their role cannot manage payouts, even when the main publisher account is active. ⏳ Why a payout can pass three weeks A stated window of about one week is the normal processing time after a payout is approved and all details are valid. More than three weeks without payment usually means the payout never entered that normal window. Typical causes are: - The account is inactive, so approved earnings cannot be released. - Earnings are below the minimum payout amount. - The payout date has not arrived for the current cycle. - Payment or tax details changed after the payout was created, which can restart review. - The payment provider returned or rejected the transfer. - The payout is assigned to the account owner, not to each teammate login. Teammates are not paid separately unless their own publisher account is active, verified, and has its own payable balance. Access to someone else’s account does not move that payout to the teammate. ✅ Checks to complete first 1. Open Publications and confirm whether the status is Active, Inactive, or Paused. 2. Review every required field for the account owner: legal name, business details, tax information, and payment method. 3. Correct any item marked missing, mismatched, or rejected, then save the changes. 4. Confirm the payable balance is above the minimum and that the current cycle date has passed. 5. Check the payout history for a failed, returned, or on-hold payment rather than only the expected payment date. 6. If a teammate is affected, compare their role with the account owner. Ask the owner to confirm whether the teammate has a separate publisher account. 7. Wait for verification to finish after you update details. Do not create a second account for the same payee. 🛠️ What to expect after you update details Submitting missing information does not instantly release older payouts. The account must return to an active, payable status first. A previously failed payout may then be retried or included in the next cycle, depending on why it was stopped. Keep the payment method unchanged while a review is in progress. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

📋 Publication Media Order Assignment Policy

📌 What this policy covers Publication Media matches buyer orders to publisher websites. A strong domain rating and healthy traffic help your site qualify, but they do not guarantee a steady flow of orders. Assignment depends on buyer demand, niche fit, price, quality signals, and how reliably you complete work. ⚙️ How orders are assigned Orders are placed into a matching queue. The system looks for sites that fit the buyer brief, then offers work to eligible publishers. There is no manual list that sends orders to every high-DR site. Staff can manually pick a specific site in the article admin, and a site named in the order notes is assigned directly. - Buyer demand drives volume. If few buyers need your niche, language, or country, fewer orders are available. - Relevance matters more than raw metrics. The topic, audience, and placement type must match the brief. - Price and turnaround affect selection when several sites could fulfill the same order. - Capacity is considered so one site is not overloaded while work is still open. 📊 What metrics do and do not do Domain rating and traffic are reviewed as quality signals. They are not the only factors, and a high score does not override a poor match. - Traffic should look real and relevant to the site topic. - The site should be indexed, accessible, and consistent with your listed niche. - Past delivery, content quality, and buyer feedback can raise or lower priority. - Outdated guidelines, slow replies, or repeated revisions can reduce future matches. ✅ How to improve your chances 1. Keep every site profile accurate, including niche, language, country, and accepted topics. 2. Set clear pricing and realistic turnaround times you can meet. 3. Publish only on pages that match the order and follow the buyer brief. 4. Respond quickly and deliver clean, original content on the first submission. 5. Remove or update sites that no longer have traffic, indexation, or topical focus. These steps improve eligibility. They still do not promise a minimum number of orders. 🚫 What we cannot arrange Support cannot create buyer demand. A buyer can still name your site in the order notes, which assigns the order directly. If your sites are eligible, they remain in the normal matching queue. 💬 When to contact support Contact support only if a listed site appears ineligible by mistake, a profile will not save, or a completed order is stuck. Have the site URL and any order ID ready. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

🔍 Resolving OTTO Duplicate Installation Warnings

OTTO can show a Duplicate Installation or Not Working status when it detects more than one OTTO script running on a page, even if your head script appears only once in your site code. This article explains what the status means, how to find the flagged URL, how a conditional loader can cause it, and what to expect while the status updates. 🧭 What the Status Means OTTO checks your pages to confirm that its script loads correctly. A duplicate warning means OTTO found more than one copy of its script on a page that it checked. Common causes include: - The OTTO script was added manually and also by a plugin, tag manager, or theme. - A conditional loader injects the script on pages where it is already present. - A template or page builder repeats the head section on some URLs. Your diagnostics may show Correct Installation and 7/7 deployments while the project status still shows a duplicate warning. This usually means the status has not yet refreshed after a fix, or that one specific URL still loads the script twice. 🔎 Finding the Flagged URL Start by identifying the exact page OTTO is reporting. 1. Open the OTTO project, then use Check or Open diagnostics and review Duplicate Installation Check. 2. Go to the installation or diagnostics section and look for the URL listed with the duplicate warning. 3. Copy the full URL, including any parameters or trailing slashes. 4. Open that page in a browser, view the page source, and search for the OTTO script. Count how many times it appears. The flagged URL may not be your homepage. Check category pages, landing pages, and any pages that use dynamic or conditional content. ⚙️ Could a Conditional Loader Be the Cause? Yes. A conditional loader is one of the most common reasons for duplicate warnings. It can cause the problem in these ways: - The loader adds the OTTO script even when the head script is already present. - The loader runs again after a page change, such as a single-page navigation, and adds a second copy. - The loader's condition is true on pages where the head script is also loaded. - The loader does not check whether the script already exists before adding it. To confirm, temporarily disable the conditional loader on the flagged URL and reload the page. If the duplicate count drops to one, the loader is the cause. 🛠️ Steps to Resolve the Duplicate 1. Keep one installation method. Use either the head script or the conditional loader for each page, not both. 2. Add a presence check. Before injecting the script, confirm that no OTTO script tag already exists on the page. 3. Limit the loader's scope. Make sure its conditions do not overlap with pages that already include the head script. 4. Clear caches. Clear your site cache and any CDN cache, then reload the flagged URL and confirm the script appears once. 5. Check tag managers and plugins. Make sure no other tool is also loading the OTTO script. 6. Verify the page again. Recheck the flagged URL in your browser source to confirm a single copy. ⏱️ How Long Until the Status Clears OTTO updates the status during its next verification cycle after the page changes are live. The timing can vary, so there is no fixed guaranteed duration. To speed up the update: - Make sure your fix is published and visible to the public, not only in a staging or preview version. - Clear any site or CDN cache before the next check. - Confirm that the flagged URL shows one script copy before waiting for the status to change. If the page shows one copy of the script and your diagnostics show Correct Installation and 7/7 deployments, but the duplicate status remains after a reasonable wait, the status may not have refreshed yet. This is not a problem with your site, but it does need a closer look. 💡 Preventing Future Duplicate Warnings - Document where the OTTO script is installed and who manages it. - Before adding any new loader, tag, or plugin, check whether it already loads OTTO. - After any template, theme, or script change, review the flagged URL and a sample of other pages. - Run your diagnostics after every major site update. 🤝 Getting Further Help If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

🔗 Connect Google Ads to a Project

🔗 What you are connecting Search Atlas uses a secure Google sign-in to link a project to the accounts you already manage. You can connect Google Ads, Google Business Profile (GBP), and Google Analytics 4 (GA4) from the same project. Each service must be approved separately, even if they share one Google login. A successful connection lets the project read the properties you select. It does not change campaigns, listings, or analytics settings inside Google. ✅ Before you start - Open Site Explorer for the selected domain, then open Google Ads in the sidebar. There is no control labeled Business. - Use a Google account that can access that client’s Ads account, Business Profile, and GA4 property. - You need permission to grant access. A view-only login may complete sign-in and still show no properties. - Allow pop-ups for Search Atlas in your browser. - Turn off strict blockers for the sign-in window, then turn them back on after you finish. 🛠️ Connect Google Ads, GBP, and GA4 1. Open the project and go to its integrations or connected accounts area. 2. Choose Google Ads, then select Connect. 3. In the Google window, pick the client account. Do not create a brand-new Google user unless that user already owns the Ads account. 4. Enter the email, password, and 2-step verification code when Google asks. 5. Review the consent screen and choose Allow or Continue. Closing this screen cancels the link. 6. Back in Search Atlas, select the correct Ads account and save. 7. Repeat the same flow for Google Business Profile and GA4. Pick the matching location and GA4 property for that client. 8. Refresh the project page and confirm each service shows as connected. 💡 If a new Chrome profile opens Google often opens a separate browser window or profile so you can choose an account without changing the profile you use every day. That window is still the connection flow. It is not finished until you approve access and return to the project. - Stay inside the new window until the consent screen is complete. Do not close it after the password or verification step. - On the account picker, select the Google user that manages the client. Signing into your personal account will not attach the client’s Ads, GBP, or GA4 data. - If the window is blank, allow pop-ups, disable the blocker for this site, and click Connect again. - If Chrome keeps the wrong account, open the Google window menu, sign out of the incorrect account, then sign in with the client account. - Avoid private or guest windows for this flow. Use a normal Chrome window. - After approval, look for a tab that says you can close the window or that returns you to Search Atlas. Then refresh the project. 📊 Confirm the right accounts Check three items after each connection: - Google Ads: the customer account name or ID matches the client. - GBP: the business location matches the project, not another location under the same login. - GA4: the property name matches the website for that project. If the status stays disconnected, disconnect that service, wait a moment, and connect it once more with the correct Google account. Connect one service at a time so you can see which approval failed. 💬 Still not connected If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

🔥 Why Wildfire Outbound Links Aren't Producing Backlinks

🔍 Outbound Links vs. Backlinks An outbound link goes from your website to another website. A backlink goes from another website to yours. Placing outbound links on your site does not create backlinks to it. Backlinks are earned when other websites choose to link to you, so the two results are separate. ⏳ Why Results Can Take Time Link results depend on factors outside your control. Search engines need to discover and process new links, which can take weeks or even months. Other websites may also need time to publish or update content before a link becomes visible. Not every placement will lead to a visible backlink. 📊 Checking Your Wildfire Results 1. Open Wildfire, then review Backlinks or Outlinks and confirm the expected links are Active. 2. Visit several of the pages where links were placed and confirm each link is live and working. 3. Review your backlink reports in Search Atlas for your domain to see whether any new linking websites have appeared. 4. Compare results against the date your campaign started, allowing enough time for search engines to update. 🛠️ Common Reasons Backlinks Do Not Appear - Links were not yet published: The linking page may still be pending or in review. - Links were removed: Some pages are edited or taken down after publication. - Search engines have not yet crawled the pages: New or updated pages may take time to be found. - Link types differ: Some links are treated differently by search engines, which can affect how they are counted. - Low-visibility pages: Links on pages with little traffic or authority may be slower to be noticed. 💡 Tips for Better Results - Focus on the quality of linking websites rather than the number of outbound links you place. - Check your campaign and backlink reports on a regular schedule instead of expecting instant results. - Keep your own website content useful and up to date so other sites have a reason to link to it. - Document the date each link was placed so you can measure progress accurately over time. 🤝 Getting Further Help If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

🧾 Accessing Invoice History on Cancelled Accounts

🔎 Why Billing May Be Restricted After an account is cancelled, some billing pages may be limited. This protects your account information. Your past invoices are still on record, and you can get copies of them. 🧭 How to Find Your Invoices 1. Log in to your Search Atlas account using the email address linked to your cancelled subscription. 2. Go to the Billing section. 3. If the page loads, review the invoice list and download any records you need. 4. If the Billing page is blocked, or shows a message asking you to submit a form, do not keep trying the same steps. Use the live chat option described below instead. 📄 Requesting Your Full Invoice History If you need every invoice from your start date through today, our team can prepare them for you. To help us process your request quickly, have the following ready: - Your account name and the billing email address - The date range you need, such as your first invoice through your cancellation date - The reason you need the records, such as tax, accounting, or audit purposes Requests for complete invoice histories may take some time to process, especially for accounts with many billing cycles. 🛟 Getting Help Quickly If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat. ✅ Tips to Avoid Delays - Keep copies of your invoices after each billing cycle while your account is active. - Save your account details in a secure place before cancelling. - Use the chat widget early if you need records for a deadline.

Last updated on Nov 03, 2026

💳 Understanding October Article Payout Timing and Status

📅 Payout Timing Overview Article payouts for October are processed after each article has been published and reviewed for payment eligibility. Processing times can vary depending on the review queue, your payment method, and your banking institution. Payments are not always released on the same day an article goes live. ⏳ What Pending Status Means A pending status means your payout has been recorded in our system and is waiting to move through the remaining processing steps. It does not mean the payment has been lost or rejected. Pending payouts may remain in this state while: - The payout is in the final verification queue. - Payment details need to be confirmed or updated. - Your bank is completing the transfer, which can take additional business days. 🔍 Checking Your Payout Status You can review the status of your October payouts by following these steps: 1. Log in to your Search Atlas account. 2. Open Earning History (heading Earning, payout text Payouts). 3. Find the October articles listed under your payouts. 4. Review the status shown next to each article: pending, processing, or completed. 5. Confirm that your payment details are current and match the account you expect to receive funds in. ❓ Common Reasons for Delays Most delayed payouts are caused by one of the following: - Incomplete payment details: Missing or outdated banking or payment information can hold a transfer until it is corrected. - Verification checks: Additional review may be required for certain accounts or larger amounts. - Bank processing time: Once a transfer is sent, your financial institution may take several business days to post it. - Holidays and weekends: Processing pauses on non-business days, which can extend timelines. If your payout has remained pending for an extended period, first confirm that your payment details are correct. Then contact our team for a status review, as described below. 🤝 Getting Further Help If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

💳 How Refund Processing Timelines Work

💳 What this article covers If you asked whether your refund is on its way, this article explains each stage, what “approved” means, and when the credit should appear on your original payment method. 📋 What a refund status means A refund moves through a few clear stages. The status you see tells you who is currently handling the payment. - Requested: We have your refund request and it is waiting for review. - Approved: Search Atlas has accepted the refund and will send it to the original payment method. - Sent: The refund has left Search Atlas. Your bank or card issuer now controls when it posts. - Posted: The credit appears on your statement or in your payment account. An approved or sent refund is on its way. It is not the same as money already showing in your account. ⏱️ Typical refund timeline Timing depends on review, the payment provider, and your bank. These ranges are typical, not a guarantee for every case. 1. Review: Most requests are reviewed within a few business days. Weekends and holidays are not counted. 2. Send: After approval, Search Atlas sends the refund to the same card, bank, or payment method used for the charge. 3. Bank posting: Many banks and card issuers post the credit within 5 to 10 business days after they receive it. Some take longer. Count business days from the date the refund was approved or sent, not from the day you first asked. A refund cannot be redirected to a new card or account. 🔎 How to check if your refund is on the way 1. Open your Search Atlas billing or invoice area and find the charge tied to the refund. 2. Note the refund status and the approval or sent date, if shown. 3. Check the original payment method for a credit, pending credit, or reversed charge. 4. Look at both pending and posted transactions. Some banks show the credit only after it posts. 5. Match the amount to the approved refund. Partial refunds will be smaller than the original charge. If the status is Sent and fewer than 10 business days have passed, the refund is in progress with your bank. You do not need to submit a new request. ⏳ Why a refund can take longer - Your bank or card issuer is still processing the credit. - The request was submitted on a weekend or holiday. - The original payment is still pending, disputed, or under a chargeback review. - The refund is partial, or more than one charge needs to be matched. - Statement cycles hide a credit until the next billing period. Search Atlas cannot speed up the time your bank takes to post a credit after the refund has been sent. ✅ What to do next Wait until 10 business days have passed after the sent date before treating the refund as late. Keep your approval confirmation and the last four digits of the payment method handy. Contact support if there is no status after several business days, if the status has been Sent for more than 10 business days with no credit, or if the amount does not match what was approved. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

🗺️ Troubleshooting Heatmaps That Are Not Showing

🔍 Overview If heatmaps are not showing in your Search Atlas account, the cause is usually one of a few common issues: the tracking setup is incomplete, the page has not received enough visits yet, the filters are set too narrowly, or the browser is displaying an older version of the page. This article walks you through each check in order. ⚙️ Step 1: Confirm Heatmap Tracking Is Installed Heatmaps need data from your website before they can display anything. Make sure tracking is installed on the pages you want to measure. 1. Open Local SEO Heatmaps for the website in question. 2. Go to the heatmap settings and confirm the tracking status shows as active or connected. 3. If the status shows as pending or not installed, copy the tracking code and add it to every page you want to analyze, ideally within the site header so it loads on all pages. 4. If your site uses a tag manager, check that the tag is published and firing on the correct pages. ⏱️ Step 2: Allow Time for Data to Collect Heatmaps are built from visitor activity. A newly installed tracker will not show results right away. Once installed, allow time for real visitors to view and interact with the page. Pages with low traffic may need several days or more before a clear heatmap appears. 📅 Step 3: Check Your Date Range A heatmap only shows activity from the date range you have selected. If the range is set to a period when the page had no visitors, the heatmap will appear empty. - Widen the date range, for example to the last 30 days. - Confirm the range does not fall before the tracking code was installed. 🔗 Step 4: Verify the Page URL Heatmaps are tied to specific page addresses. If the URL you are viewing differs from the one that receives traffic, no data will show. - Check for differences in http versus https, the presence or absence of www, and trailing slashes. - Check for URL parameters, such as tracking tags added to links, which can create separate page records. - Make sure you are selecting the correct domain within your project. 🧭 Step 5: Review Device and Filter Settings Filters can hide all data if they are too specific. Heatmaps are often split by device type, such as desktop, tablet, or mobile. - Set the device filter to show all devices, then narrow it down if needed. - Clear any segment or audience filters you have added. - Check whether the heatmap view is set to clicks, scrolls, or movement, and confirm that view has data for this page. 🧹 Step 6: Refresh and Clear Your Browser Cache Your browser may display an older version of the dashboard. Try the following: 1. Refresh the page with a hard reload. 2. Clear your browser cache and cookies for the Search Atlas site. 3. Try a different browser or a private browsing window. 4. Temporarily disable browser extensions such as ad blockers, which can prevent tracking scripts from loading. 🔐 Step 7: Check Your Plan and Permissions Heatmap access depends on your subscription and your user role within the account. If the heatmap option is missing or locked, confirm that your plan includes this feature. If you are a team member rather than an account owner, ask an administrator to confirm your access level. ✅ Step 8: Confirm the Fix After completing the steps above, return to the page and check the heatmap again. Remember that new data can take time to appear, so if the page is new or receives little traffic, allow additional days before reviewing results. 🆘 Still Need Help? If you have completed every step above and heatmaps still do not appear, please contact our team. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

💰 Why Publisher Payments Stay Pending

💰 Why a Payment Stays Pending A publisher payment stays pending until the article and your payout setup both meet the requirements for the next payment run. Pending does not mean the earning was lost. It means the amount is recorded but not yet released. Common reasons a payment has not arrived after several weeks include: - Article status: the piece is still in review, waiting on revisions, or not yet approved. - Payout window: approved earnings are released on the platform payment schedule, not the day the article is submitted. - Payout threshold: your balance has not yet reached the minimum amount required for a payout. - Payout details: your payment method is missing, unverified, or does not match the account on file. - Hold or review: the article or account is under a routine quality or compliance check. 🔎 What to Check in Your Account Review these items in order before you request help. Most unpaid-payment questions are resolved by one of these checks. 1. Open Earning History (heading Earning, payout text Payouts). It shows payment batches with status paid or unpaid, not article review statuses. Check an article's status under Articles (Awaiting Publication or Published). Only an approved article can move toward payment. If revisions were requested, complete them and resubmit. 2. Open your publisher earnings or payments area and note whether the amount is pending, processing, or paid. 3. Confirm the earning is tied to the correct article and that the amount matches what you expected. 4. Check that your connected payout method is active and verified. An incomplete method keeps funds pending. 5. Compare your available balance with the payout minimum. Amounts below the minimum stay on your balance until a later run. 6. Look for any in-platform notice about a hold, failed payout, or required update. ⏱️ How Long Pending Usually Lasts Submission date is not the same as payout date. Time in review, requested edits, and the gap until the next payment run can easily add up to a few weeks. A payment that has been pending for about three weeks is often still inside a normal review-plus-payout cycle, especially if the article was not approved immediately. Use this guide when you read the status: - Pending: the earning is recorded and waiting for approval, the threshold, or the next payout run. - Processing: the payout has been sent to your payment provider and may take additional business days to appear. - Paid: the platform has completed the payout. If it is not in your external account, check with that provider using the payout reference shown in Search Atlas. 🛠️ How to Update Payout Details If a previous payout could not be completed, later earnings stay pending until the details are fixed. 1. Open your publisher payout settings. 2. Confirm the payment method, account name, and any required verification are complete. 3. Save the update, then return to the earnings page and confirm the status is no longer blocked. 4. Allow the next scheduled payout run to pick up the balance. Updating details does not create an instant transfer. Do not submit the same article again to force a payment. A duplicate submission can delay review. Track the original article instead. 💬 When to Contact Support Contact support if the article has been approved, your payout method is complete and verified, your balance is at or above the minimum, and the payment is still pending well after the following payout run. Have the article title, submission date, current status, and the amount shown as pending ready so the team can look up the record. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

💳 Removing a Stored Credit Card from Your Account

💳 About This Article This guide explains how to remove a credit card saved on your Search Atlas account. Most card removals can be completed on your own in a few minutes. 🛠️ Before You Begin - Make sure you are logged in to the account that holds the card. - If the card is linked to an active subscription, add a replacement payment method first, since a subscription needs a valid payment method to continue. - Keep a backup payment method ready if you are still being billed. 📋 Steps to Remove a Stored Card 1. Log in to your Search Atlas account. 2. Open Billing → Plans & Top-ups and use the payment-method button, which opens the Manage Payment Methods drawer directly (the card action is labeled Manage payment method). 3. Find the card you want to remove and choose the remove or delete option. 4. Confirm the removal when prompted. Once removed, the card will no longer be used for future charges. Refresh the page to confirm it no longer appears in your list. ⚠️ When a Card Cannot Be Removed In some situations, the card cannot be removed right away: - The card is the only payment method on an active subscription. - A recent charge is still processing. In these cases, add a new payment method first, then remove the old card. 🕒 Speaking With a Team Member Most card removals do not require help from a team member. Team availability can change, so the live chat is the best place to check when someone is online. We cannot guarantee a specific time on a specific day, so please use the chat to confirm current availability. 💬 Getting Further Help If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

🔍 Paid Account Shows Deactivated Login

🚪 What the deactivated-login message means A deactivated login means the platform has disabled the account itself. At sign-in, the account is rejected with the message User is inactive or deleted, even when the password is correct. The message is not shown for a charge that is still processing, a failed card charge, the wrong login, or a cached session. 💳 If you already paid The disabled state reflects the account itself, not the timing of your payment. If you recently paid and this message appears, the account needs to be reactivated by our team. 🛠️ Steps to restore access 1. Confirm the email you signed in with is the account you paid with. 2. Open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat. 3. Ask for the account to be reactivated, and share the payment details below. ⚠️ What to avoid Do not create a brand-new account to get around the screen. A second login will not carry over the subscription, projects, or billing history from the paid account. Also avoid submitting the same payment again until a teammate confirms the first charge did not apply. 💬 What to share with support - The email address you signed in with - The date you paid and the amount charged - The last four digits of the card, if available If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

💳 Disputing Recurring Credit Charges

💳 Why a monthly charge can appear on a yearly plan An annual Search Atlas plan covers your core subscription for the year. It does not always include every add-on or usage-based product. A separate recurring charge, such as $120 per month, is often tied to indexer credits or another monthly add-on that was added to the account independently of the yearly plan. These charges can start after a team member enables the add-on, after a trial converts, or when credits are set to renew automatically. The charge is billed to the payment method on file even if the main plan is prepaid annually. 🔍 Check what the charge is for Before requesting a refund, confirm the line item so the review is accurate: 1. Sign in to Search Atlas and open Billing or Subscription from your account settings. 2. Open Billing → Invoices and select the invoice for the month in question, including September and October if those are the charges you want reviewed. 3. Note the product name, amount, billing date, and whether it says indexer credits, credits, or another add-on. 4. Check whether auto-renew is turned on for that add-on and which user last changed the subscription, if that history is shown. 5. Compare the charge with your yearly plan invoice so you can see they are separate line items. If the invoice clearly matches an add-on you intended to keep, the charge is expected. If you did not approve it, or the credits were not used, you can ask for a billing review. 🛠️ Request a review of September and October charges Refunds are not automatic. Each request is reviewed against the invoice, add-on status, and credit usage. To dispute the $120 monthly charges: - Gather the invoice dates, amounts, and the last four digits of the card charged, if available. - State that your main plan is yearly and that you are disputing the separate monthly credit or indexer charge. - List each month you want reviewed, such as September and October, and say whether you want a refund, a credit to the account, or the add-on canceled going forward. - Mention if no one on your team knowingly approved the add-on, or if credits were unused. Canceling the add-on stops future renewals. It does not by itself refund charges that have already posted. Ask for both actions if you want the recurring charge stopped and past months reviewed. 📊 What usually happens next Our team checks whether the charge matches an active indexer or credit subscription, whether credits were consumed, and whether the add-on can be removed. Possible outcomes include a refund of eligible unused charges, an account credit, or confirmation that the charge was valid and will remain. Processing time depends on the payment provider after a refund is approved. Keep using your yearly plan as normal while the monthly add-on is under review. Only the disputed line item is in question unless you also ask to change the main subscription. 💡 How to avoid repeat charges - Review Billing after any teammate adds credits, indexer access, or a trial. - Turn off auto-renew on add-ons you only need once. - Download invoices each month so yearly plan fees and monthly credit fees stay easy to tell apart. - Limit billing permissions to people who should approve new recurring products. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

📊 Why GSC Keyword Spikes Then Drop

📈 What customers are seeing Some projects show a sharp jump in Google Search Console keyword counts on recent dates, often the same one or two days across many sites. A common example is thousands of position 1 keywords on those dates, then a much smaller count once the data settles. These spikes can make daily reports look unreliable even though rankings did not suddenly change overnight. 🔍 Why the spike is not a data-source switch Search Atlas did not switch sources or start pulling keywords differently for those dates. The counts come from Google Search Console. Google labels recent performance data as preliminary. Early pulls often include incomplete or inflated query rows that Google later revises, merges, or removes as more complete data arrives. Because the same Google revision window affects many properties at once, the jump can look universal. A spike on dates such as 10/26 and 10/27 that later falls from 6,000-plus position 1 keywords to about 186 is consistent with preliminary GSC data, not a platform-wide ranking event. ⏱️ How preliminary GSC data behaves - Recent days move. Keyword totals, impressions, clicks, and average position for the last few days can change after the first sync. - Position buckets are sensitive. A large position 1 count is especially likely to shrink when Google finalizes which queries truly ranked first. - Older dates stabilize. Once Google finishes revising a day, later syncs usually show a steady number. - The pattern can repeat. Each new day may look high at first, then drop as that day leaves the preliminary window. 📊 How to read your reports 1. Treat the last few days as provisional. Do not use the newest dates as the final keyword or position 1 total. 2. Compare a settled date. Recheck the spiked day after several more days. The finalized count is the one to use in client reporting. 3. Avoid day-over-day conclusions on fresh data. A one-day jump shared across many projects is a data-revision signal, not proof that every site gained thousands of top rankings. 4. Use a short lag for exports. For recurring reports, exclude the most recent two to three days, or note that those days are still preliminary. 5. Refresh before you share numbers. Open Keywords again after the next sync so you are not quoting the first incomplete pull. ✅ What you should do next No project setting change is required to correct a preliminary spike. Wait for Google to finalize the affected dates, then review the same chart. If a spike remains on dates that are well outside the usual revision window, or if only one project moved while connected properties did not, check that the correct GSC property is still linked and that the date range has not shifted. Search Atlas will continue to reflect the figures Google returns. When Google revises those figures, your keyword counts update to match. 💬 Still seeing an unexplained spike If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

💳 Subscribing to a 1-Seat Plan After Pro

🎯 Who This Article Is For This guide is for customers who have canceled their Pro plan and want to subscribe to the 1-seat plan instead. The steps below show you how to sign up again and what to check before you do. ✅ Before You Start - Check your current status: Make sure your Pro plan is fully canceled. If it still shows as active, it may end at the close of your current billing period. - Have your account login ready: Use the same account you used for Pro so your projects and settings stay connected. - Confirm your payment method: Have a valid card or billing details available. 🪜 Step-by-Step: Subscribe to the 1-Seat Plan 1. Log in to your Search Atlas account. 2. Open Billing → Plans & Top-ups → Change Plan, then select the plan card labeled Starter (features list 1 team seat). 3. Select View Plans or Upgrade Plan. 4. Choose the 1-Seat plan from the list of available options. 5. Review the price, billing cycle, and included features. 6. Enter or confirm your payment details. 7. Complete the purchase and wait for the confirmation message on screen. 📧 About Email Instructions These steps are available directly inside your account, so you do not need a separate email with instructions. If you prefer to follow along later, you can bookmark this article or return to it from the Help Center at any time. 🔄 What Happens to Your Pro Data - Projects and reports: Your existing projects stay in your account. Confirm they are visible after you subscribe. - Connected integrations: You may need to reconnect some tools if access was tied to the Pro plan. Check your integration settings after the change. - Team access: The 1-seat plan supports one user. If other people were using your Pro account, they will lose access. ⚠️ Common Issues and Quick Fixes - The 1-Seat plan does not appear: Refresh the page, log out and back in, and check that you are on the correct account. - Payment was declined: Check your card details, make sure there are sufficient funds, and try a different payment method if needed. - Still seeing Pro features: Your Pro plan may not have fully ended yet. Check the end date on your canceled plan and try again after it closes. - Charged twice or unexpected charges: Review your billing history in the account settings before taking any other action. 🛟 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat. 💡 Tips to Avoid Delays - Cancel Pro and subscribe to the 1-seat plan in the same session to avoid losing access to tools. - Save your confirmation message or receipt for your records. - Review your plan details once a month to make sure your seat count matches how you work.

Last updated on Nov 03, 2026

💸 Understanding Contributor Payout Timing for Published Articles

📋 How Contributor Payouts Work Contributors are paid for articles after they are published and pass our internal review. Each payout is tied to the specific articles it covers, so one payment may include several pieces of content from the same month. ⏳ Why a Payment May Show as Pending A payment can stay pending longer than expected for several common reasons: - The article was published late in the payout cycle and is included in a later batch. - The payment is awaiting final review or a required account check. - The PayPal account linked to your profile needs to be verified or updated. - Transfers are processed through a third-party payment provider, which can add time before funds appear in your PayPal account. 🔍 How to Check Your Payout Status 1. Sign in to your contributor account. 2. Open Earning History (heading Earning, payout text Payouts) and find the payout for the relevant month. 3. Review the listed articles and their current status. 4. Confirm that the PayPal email address on your profile is correct and verified. 🛠️ What to Do If Your Payment Is Delayed If a payment has been pending longer than expected and the checks above look correct, open the chat widget and include the article titles and publication month so we can locate your payment quickly. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat. ✅ Tips to Avoid Future Delays - Keep your PayPal account verified and its email address up to date. - Check your account after each publication to confirm the articles are recorded. - Review the payments section at the start of each month to catch issues early.

Last updated on Nov 03, 2026

🔍 Fixing Cal.com Inline Booking Widget Loading Issues

🔍 What This Issue Looks Like When the Cal.com inline booking widget fails to load, the calendar area may stay blank or keep loading. Clients cannot book appointments through your page until the widget displays correctly. This article explains the most common causes and walks you through how to resolve them. ⚙️ Common Causes Most loading problems come from one of the following: - Incorrect scheduling link: The event link used in the embed does not match an active event type in your Cal.com account. - Event type disabled or hidden: The event has been turned off, made private, or its availability has been removed. - Duplicate or outdated embed code: More than one copy of the script is on the page, or an older snippet is still in place. - Script blocked by the website: A security setting, cookie consent tool, or ad blocker prevents the widget from loading. - Page caching: Your website or browser is showing an older version of the page that does not include the latest embed. - Mixed content: The page loads over secure HTTPS, but part of the embed is requested over an insecure connection, which browsers may block. 🛠️ Step-by-Step Troubleshooting Work through these steps in order. Stop when the widget loads correctly. 1. Load the page in a private window. This rules out browser extensions and cached content. 2. Try a second browser or device. If the widget loads elsewhere, the problem is likely a browser extension or a local cache. Clear your cache and disable ad blockers for your website, then reload. 3. Test the scheduling link directly. Open the Cal.com booking link in a new tab. If it does not open, the event type is the problem, not your website. 4. Confirm the event type is active. In your Cal.com account, make sure the event is turned on, is set to public, and has available time slots. 5. Check for duplicate scripts. View the page source and search for the Cal.com embed script. Remove any extra copies so that only one script and one embed container remain. 6. Check your cookie or consent tool. If your site uses a consent banner, make sure visitors who have not accepted cookies can still see the booking widget or that the widget is allowed to load. 7. Clear your website cache. If your site uses a caching plugin or content delivery network, purge the cache and reload the page. 8. Review the browser console. Press F12 or right-click and choose Inspect, then open the Console tab. Error messages that mention blocked content or security policies point to the cause. 🔗 Checking Your Scheduling Link The embed depends on the exact scheduling link you provide. Make sure the link matches the event you want to display, including the username and event slug. A small typo, a renamed event, or a link to a deleted event type will prevent the widget from loading. If you recently renamed your event in Cal.com, copy the updated embed code again from your account and replace the old code on your page. 🌐 Updating Embed Code on Your Pages When you replace an embed, follow these guidelines to avoid new problems: - Copy the latest embed snippet directly from your Cal.com account rather than reusing older code. - Place the widget container in the page section where you want the calendar to appear, and include the script only once per page. - Update every page that displays the widget, such as your homepage and contact page, so that all versions match. - Publish your changes, then clear your website cache and test each page in a private window. - Confirm that your website builder or theme does not strip out script tags. Some editors block custom code unless it is added through a dedicated code or HTML block. 💡 Preventing Future Problems A few habits will reduce the chance of the widget breaking again: - Test your booking pages after any website update, theme change, or plugin update. - Avoid renaming or deleting event types that are embedded on your site without updating the embed code first. - Keep a record of which pages contain the widget so you can check them quickly. - Schedule a periodic test of your booking flow from both desktop and mobile devices. - Review your site's security and consent settings whenever you add new third-party tools. 📊 Quick Checklist Before contacting support, confirm the following: - The scheduling link opens correctly on its own. - The event type is active, public, and has open time slots. - Only one copy of the embed script appears on each page. - The page has been tested in a private window and after clearing the cache. - The browser console has been checked for error messages. 🤝 Getting Further Help If you have completed these steps and the widget still does not load, please gather the scheduling link, the affected page addresses, and any console error messages you saw. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

🔄 Updating Citation Details and Credit Charges

📌 Why citation updates can use credits Updating a citation means changing business details that were already submitted, such as your name, address, phone number, website, hours, or categories. That work is separate from the original citation order. A past note that updates were free for a year usually referred to a plan benefit or promotion tied to the original submission. It does not make every later change free. If that window has ended, or the change is run as a new Atlas agent task, the platform shows a credit cost before anything is submitted. 💳 What the 160-credit request means When Atlas agent asks for 160 credits, that is the current cost of the update task you started. The charge is a quote for that run, not a surprise fee added after the work is done. - Credits are used only after you confirm. Closing the prompt or choosing not to continue does not spend credits. - The quote can differ by task. A small field change and a broader listing update may not have the same cost. - Older free-update messaging does not override the quote. If your screen asks for 160 credits, that is the amount required to continue with the agent. 🛠️ How to update citation details 1. Open Local Citations, then select Edit & Submit for the business listing. 2. Go to the citations or local listings area and select the business you want to change. 3. Edit only the details that are incorrect, such as name, address, phone, website, hours, or category. 4. Review the Atlas agent prompt and the credit amount shown, including a request for 160 credits. 5. Confirm the task only if you want to spend those credits. Otherwise, leave the prompt without confirming. 6. After you confirm, check the listing status to see when the update has been submitted or completed. Use the same business details everywhere. Mismatched name, address, or phone information can cause directories to reject an update or keep the old listing. ✅ How to avoid an unexpected charge - Read the credit amount on the agent prompt before you confirm. - Do not assume a previous promotion still applies. Check the quote on the current task. - Update only the fields that need to change so you do not start a larger task than necessary. - If 160 credits does not match what you expected from your plan, stop before confirming and ask support to review the quote. 💬 Need more help If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

💳 How to Switch to One-Seat Plan

💳 What a one-seat plan means A one-seat plan covers a single user. It does not start on its own when you cancel Pro. After Pro is cancelled, you still need to select and purchase the one-seat plan. ✅ Before you subscribe - Sign in with the account that owns billing. - Open Billing → Plans & Top-ups and check the Pro Plan Subscription card. A plan that will end shows Cancelling on [date] (Services lists Cancelled on [date]). There is no Canceled label. - Note whether Pro access continues until the end of the paid period. - Have a valid payment method ready. 🛠️ Subscribe to the one-seat plan 1. Sign in to Search Atlas. 2. Open account or billing settings, then go to plans or subscriptions. 3. Find the one-seat plan. It may be labeled as a single-user or starter option. 4. Select that plan and continue to checkout. 5. Check the price, billing cycle, and seat count. It must show 1 seat. 6. Confirm your payment method and complete the purchase. 7. Return to billing and verify the active plan, seat count, and renewal date. ⚠️ If you cannot see the plan A cancelled Pro subscription can remain active until the current billing period ends. A new plan may be unavailable during that time so you are not charged twice. When Pro has fully ended, open plans again and select one seat. If the option is still missing, a teammate can review the subscription status for you. 📊 Confirm the switch worked - Check that your receipt or invoice lists one seat. - Confirm available features match the plan you bought. - Remove extra users left from Pro, since this plan supports one person. - Keep your payment method up to date so renewal succeeds. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

🔍 Why Your Third OTTO Site Is Missing

📊 What the OTTO site quota means Your OTTO site quota is the number of websites you can run with OTTO on your current plan. A promotional signup from about a year ago may have included three OTTO sites. If the platform now shows two, the third slot was not randomly deleted. The number on screen follows the plan, promotion, and sites currently attached to your account. 💡 Why the third site may no longer appear Customers usually see this change for one of these reasons: - The promotion ended or the plan changed. A signup offer that added a third OTTO site applies only while that offer and plan remain active. Renewal, a plan change, or an expired promotion can return the account to a two-site limit. - A site was removed or disconnected. Deleting, archiving, or disconnecting a website frees or removes that OTTO slot, so the list can drop from three sites to two. - The third slot is still in use but hard to see. The site may be paused, under another project, or connected with a different domain than the one you expect. - Billing and the quota display are out of sync. After a plan or promotion change, the site list can briefly show the wrong limit until the subscription updates. 🛠️ How to check your current quota 1. Open the top navigation header, then the quota dropdown, and note the OTTO Sites limit. 2. Open your OTTO sites or projects and count every active, paused, and recently removed site. 3. Compare that count with any signup or promotion confirmation you saved. Look for wording that says the third site was included for a limited time or only on a specific plan. 4. If you recently changed plans, refreshed billing, or removed a domain, allow the account to finish updating, then check the limit again. If billing shows a limit of two, the promotional third site is no longer part of the active subscription. If billing still shows three but only two sites appear, the quota itself is still there and the missing site or display needs a review. ✅ What to do next - Your current plan lists two sites: the third OTTO option from the older promotion is no longer included. You can add it again by moving to a plan that includes three OTTO sites. - Your plan still lists three sites: check paused, archived, and recently disconnected projects before assuming the slot was removed. - You cannot find the site or the limit looks wrong: have your plan name and the domains you expect to be connected ready so the team can compare your original promotion with the live subscription. 💬 When to contact support Contact support if your billing page still includes three OTTO sites but only two are available, or if you believe the original promotion should still be active. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

🔍 Improving AI Visibility with OTTO Q&A

💡 What the OTTO Q&A Module Does The OTTO Q&A module, part of Knowledge-Based Trust and Factual Enhancement, structures your website content so AI engines (like ChatGPT, Perplexity, and Google AI Overviews) can easily extract facts and cite your site when answering user questions. The module adds Q&A content to your pages as on-page HTML that is hidden by default. Approving the module also adds FAQPage structured data (JSON-LD) so AI engines and search crawlers can parse the facts programmatically. 🎯 Prioritizing Non-Branded Query Visibility To appear in AI answers for non-branded queries (questions that don't mention your company name), focus on these priorities: 1. Answer real questions in plain language. Identify the specific questions your target customers ask and answer them directly, in 40-60 word snippets, near the top of relevant pages. 2. Build topical depth. AI engines favor sites that demonstrate expertise across a topic cluster, not just one page. Cover related subtopics comprehensively. 3. Add structured data. Use FAQ and HowTo schema markup so AI systems can parse your answers programmatically. 4. State facts explicitly. AI models extract entities and facts. Include clear statements (definitions, statistics, dates, prices) rather than vague marketing copy. 5. Earn third-party citations. AI answers pull heavily from widely referenced sources, so mentions on authoritative sites matter as much as your own content. 📰 Choosing Press Release Networks Press releases help AI visibility because major networks are frequently crawled and cited by AI models. When distributing releases, keep these points in mind: - Prioritize large, established networks. High-Domain-Authority distribution networks (roughly 80+ DA/DR, sometimes referenced as HDC tiers) with genuine editorial reach perform best for AI citation. - Focus on factual, newsworthy content. AI systems cite releases containing data, original research, and expert quotes — not pure promotional copy. - Use consistent entity naming. Always use your exact legal and brand names so AI models connect mentions back to your entity. - Diversify your sources. A mix of a few strong networks plus industry publications outperforms a single channel repeated many times. Because distribution network quality and pricing change frequently, review the current recommended network options within your OTTO dashboard or ask our team for an up-to-date list before committing to a package. 🛠️ Applying This to Your Site Setup Whether you manage goloans.ca or another domain, apply this checklist: 1. Enable the OTTO Q&A module and map your top non-branded questions (for a loans site, for example: "How do personal loan interest rates work?" or "What credit score is needed for a loan?"). 2. Confirm the Q&A content is present in your live page HTML and accessible to crawlers. 3. Add FAQ schema to your key money and informational pages. 4. Publish factual comparison content (rates, terms, eligibility) that AI systems can quote directly. 5. Distribute data-driven press releases on high-authority networks to build entity trust. 📊 Measuring Your Results Track progress over 4-8 weeks, since AI engines update citations gradually. Inside Search Atlas, monitor referral traffic from AI sources, branded and non-branded mention volume, and whether your pages appear as citations in AI-generated answers for your target questions. 💬 Still Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

💳 Reprocess a Declined Publisher Payment

💳 Why an article payment is not sent Publisher article payments are sent through PayPal. If PayPal declines the charge, the payment is marked for manual payment and is not sent to the publisher. A decline is usually caused by an outdated PayPal email, a restricted PayPal account, or a mismatch between the email on file and the account that should receive funds. Updating your PayPal email does not restart the payment by itself. After the correct email is saved, our team creates a new payout or issues the payment manually. ✉️ Update the PayPal email first Before you request a reprocess, confirm the receiving account is ready: 1. Sign in to the PayPal account that should receive the article payment. 2. Confirm the account is active and able to receive payments. 3. Copy the exact email address on that PayPal account. 4. In Search Atlas, open your publisher payout or billing settings and replace the old PayPal email with that address. 5. Save the change and check that the new email is shown with no extra spaces or typos. Use only an email that is already linked to a working PayPal account. A new or unverified address can cause another decline. 🔄 Request a reprocess After the correct email is saved, ask our team to send the payment again. Include these details in chat so the request can be matched quickly: - The article or order the payment belongs to - The payment amount, such as $57.50 - The date of the declined attempt, if you know it - The old PayPal email and the new PayPal email - Confirmation that the new account can receive payments Our team will create a new payout to the updated PayPal email and reply in the same chat when the new attempt has been submitted. You do not need to place a second order or pay again for the same article. 📅 When the funds should arrive Once the new payout is submitted successfully, PayPal usually shows the incoming payment within 1 to 3 business days. Weekends, holidays, and PayPal account reviews can add time. Search Atlas cannot release funds that PayPal is still holding or reviewing. Check the activity in the PayPal account tied to the updated email, not the old one. A successful new payout means the attempt was accepted. It does not mean the money is instantly available for withdrawal. 🛠️ If the payment is declined again Another decline almost always comes from the PayPal account, not from the article order. Before contacting us again, verify that: - The email in Search Atlas matches the PayPal account exactly - The PayPal account is verified and not limited - The account can receive payments in the expected currency - You are checking the correct PayPal login Then return to chat with any decline message PayPal displayed. Our team can submit a new payout only after the account issue is fixed. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

💰 Delayed Affiliate Payment Verification Guide

💵 What payment verification means Affiliate commissions are not released until Search Atlas verifies the activity behind them. Verification confirms that referred accounts, qualifying actions, and listed article IDs match our records and that the payable amount is correct. A payment shown as pending, in review, or outstanding has not failed. It is waiting for that check to finish before funds are released. 📅 Typical release timeline Most verified commissions move to payable status after the current affiliate billing cycle closes. Release usually follows these stages: 1. Accrual: commissions appear against qualifying referrals. 2. Verification: our team matches article IDs, referral records, and the payable total. 3. Approval: the confirmed amount is marked ready for payout. 4. Release: funds are sent through your saved payout method on the next payment run. A specific calendar date is set only after verification is complete. Until then, the dashboard shows status rather than a guaranteed pay date. A general article cannot confirm an account-specific amount or date. 🔎 Why a payout can be delayed Delays usually come from a mismatch or a missing requirement, not from a lost payment. Common reasons include: - Article IDs on the request do not match the commission records. - The expected amount differs from the verified payable balance. - The referral is still inside a review or refund window. - Payout details are missing, expired, or a previous transfer failed. - The balance is below the minimum payout threshold. - The payment is queued for the next scheduled release after approval. 🛠️ How to check your status Open the Writer Dashboard, then the Remittance List, and review the payout status, listed article IDs, and current payable amount. Compare those figures with your own records before requesting an update. Use this checklist: - Confirm each article ID appears on the commission line you expect to be paid. - Note the amount shown as payable, not an estimate still in review. - Check that your payout method is complete and verified. - Look for a status such as in review, approved, or scheduled. If the amount on screen differs from what you expected, verification is still reconciling the records. The amount released is the verified payable total, not an unverified estimate. ✅ What to expect after approval Once verification is finished, the status changes to approved or scheduled and a payment run date is attached. Funds are then sent to the payout method on file. Bank or processor timing after we release the payment can add a short delay that does not appear in the platform status. If a transfer fails, the amount returns to your payable balance and the status is updated so it can be sent again after you correct the payout method. 💬 When to contact the team Reach out if the same payable amount has stayed in review well beyond the normal billing cycle, article IDs are missing from your statement, or a scheduled release date has passed with no payout. Have the article IDs, the amount you believe is outstanding, and any status text from the affiliate screen ready. A teammate can verify those IDs, confirm the correct payable amount, and share the specific payment date once it has been set. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

🚀 Schedule a Team Onboarding Session

📅 Yes, your team can learn together Search Atlas does not require each person to figure out the platform alone. You can request a guided onboarding session so teammates can join, see the same workflow, and talk through your projects with a member of our team. You can request the session through the in-platform chat, and scheduling is not limited to that channel. 💬 How to request an onboarding session 1. Sign in to Search Atlas with the account you want covered in the session. 2. Open the chat widget in the bottom-right corner of the platform. 3. Send your message in the chat. A member of our support team will reply in the conversation. 4. Say that you want a team onboarding session and include how many people will join. 5. Share two or three times that work for your group, plus your time zone. 6. Wait for confirmation of the time and how everyone should join. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat. 👥 Who should attend Invite the people who will actually use Search Atlas, not only a manager. A useful group often includes: - The account owner or billing admin - The person who will set up projects day to day - Anyone who will review reports or client work - A teammate who owns your current SEO process Keep the group focused. Smaller sessions leave more time for your real projects. 📝 What to prepare before the call A short brief helps the session stay useful. Send this in chat when you request the time: - Your main goal, such as site audits, content planning, or client reporting - The websites or projects you want to walk through - Tools or workflows you already use - Questions your team has already tried to solve on their own - Any access limits, such as who can edit projects Have those sites open in Search Atlas before you join so time is spent on decisions, not setup. 🛠️ What the session can cover Onboarding is a working conversation about your account. Typical topics include: - A clear tour of the areas your team will use most - How to organize projects so everyone knows where work lives - A first pass on one real website instead of a generic demo only - Who on your team should own each recurring task - What to do in the first week after the session Come with one priority project. That keeps the call practical and easier to repeat later for new hires. ⚙️ Availability and session options Availability depends on team capacity, so the chat is the place to check open times. When you write in, you can ask for: - A first onboarding session for a new account - A follow-up focused on one project or workflow - A shorter refresher when new teammates join Share your time zone and whether you need a morning or afternoon slot. If your first choice is full, offer backups so scheduling does not stall. 💡 While you wait for a time You do not have to pause work. Before the session, explore the product with a test project, note where your team gets stuck, and collect those questions in one list. Bring that list to chat or to the session so nothing is forgotten. If plans change, message again in the same chat to update the time or the attendee list.

Last updated on Nov 03, 2026

💳 Refund After a Cancelled Subscription Invoice

💳 Why an invoice can arrive after cancellation Cancelling your Search Atlas subscription stops future renewals, but an invoice can still be created if it was generated before the cancellation was completed or if it covers a billing period that had already started. Receiving a bill does not always mean the account is still active. A refund is reviewed case by case. It is not applied automatically when an invoice is disputed, so the billing team needs a few details before they can confirm the account status and the correct next step. 🔍 Check your account before you request a refund Review these items in your Search Atlas account so the request can be handled quickly: - Subscription status: Confirm that the plan shows as cancelled and note the cancellation date. - Invoice details: Save the invoice number, invoice date, amount, and the billing period it covers. - Cancellation proof: Keep any on-screen confirmation or message that shows when you cancelled. - Payment method: Check whether the charge is pending or has already been collected. 🛠️ How to request the refund and confirm cancellation 1. Sign in to Search Atlas and open the live chat widget in the bottom-right corner. 2. Send your message in the chat. A member of our support team will reply in the conversation. 3. Say that you cancelled your account, received another invoice, and want that latest bill reviewed for a refund. 4. Share the invoice number, amount, invoice date, and the date you cancelled. 5. Ask the teammate to confirm that the subscription is fully cancelled and that no further renewals are scheduled. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat. 📊 What happens after your request The team compares the invoice date with your cancellation date and checks whether the charge matches an active billing period. If the invoice should not have been billed, they will tell you whether a refund can be issued and which charge it applies to. - Have your invoice number ready so the correct bill can be located. - Pending charges and completed charges may be handled differently by your card provider. - Refund timing, when approved, depends on the original payment method and the card issuer. - Keep the chat confirmation until you see the refund or the expected billing update. 💡 How to avoid another invoice Cancel before the next renewal date and verify that the subscription status changes to cancelled. Do not rely only on closing the browser or removing a payment card. After cancelling, review your billing page once more and save the confirmation. If another invoice appears after that confirmation, contact the team with the invoice details rather than submitting a second cancellation. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

🛑 Avoid Accidental OTTO Site Slot Purchases

📌 What OTTO site slots are Each OTTO site slot lets you add one website, also called a project, to your Search Atlas account. Your plan includes a set number of slots. If you need more projects than that set includes, you can buy extra slots during checkout or from your billing area. Slots and projects are not the same thing. A slot is the space you pay for. A project is a site you have already created. Buying eight extra slots does not create eight new projects by itself, but it does increase what you are billed for. ⚠️ Why customers buy too many slots Most extra purchases happen when the quantity is higher than the number of new sites you actually need. Common causes include: - Entering a total project count instead of only the additional slots you need. - Confirming checkout before comparing the cart total with your current plan. - Buying slots for sites you plan to add later, then deciding you do not need them yet. - More than one teammate updating the same account. For example, if you already have slots for 30 projects and only need 30, you should not add 8 more. If you have 22 projects and need 30, you need 8 additional slots, not 30. 🧮 Check your numbers before you buy Before you open checkout, write down three numbers: 1. Projects you need: the total sites you want active. 2. Slots you already have: the project limit shown on your plan or billing page. 3. Slots to add: projects you need minus slots you already have. If this number is zero or less, do not buy more slots. Use only the third number as the purchase quantity. If you need 30 projects and already have 30 slots, the quantity to add is 0. 🛒 Confirm the cart before you pay On the checkout screen, pause and review every line before you submit payment: - Read the slot quantity, not only the price. - Confirm the quantity matches slots to add, not your total project goal. - Check that the new project limit equals the number of sites you need. - Review the recurring charge so you know what future invoices will include. - If a teammate manages billing, ask them to confirm the quantity before anyone pays. If any number looks off, change the quantity or leave checkout. Do not complete payment and plan to fix it later. 🔧 What to do if you already bought too many If you meant to keep 30 projects but were charged for 38, act quickly and gather these details: - The number of projects you need. - The number of slots you had before the purchase. - The number of slots charged on the latest invoice. - The date and amount of the charge, if you have them. Do not delete active projects just to match the invoice. Removing a project does not automatically remove a paid slot. Our team needs to review the purchase and your current limit before any billing change can be made. Billing adjustments are reviewed case by case. Contact us with the numbers above so we can see whether the extra slots can be corrected. 💬 Get help with an extra slot charge If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat. Share your desired project count and the quantity you believe was purchased by mistake. Have your invoice handy so the review can start right away.

Last updated on Nov 03, 2026

💰 Reprocess a Declined Publisher Payout

💰 Why a publisher payout is declined A publisher article payout is the payment Search Atlas sends after your article is published and approved for payment. A decline usually means the payment could not reach the PayPal account on file. Common causes include an outdated PayPal email, an unverified or limited PayPal account, a mismatch between the name on the account and the payout details, or a temporary issue on PayPal’s side. Updating your PayPal email does not automatically resend a payment that already failed. The original attempt stays declined until our team reprocesses it to the corrected account. 🛠️ Fix your PayPal details first Before you ask for a reprocess, confirm the account can receive the payment. This prevents a second decline. - Sign in to PayPal and confirm the email you want to use is verified and can receive money. - Check that the account is in good standing and not limited. - Update that same email in your Search Atlas payout settings so it matches PayPal exactly. - Note the article, the declined amount, and the date of the original payment so we can find the right payout. For example, a declined payment of $57.50 can be resent only after the PayPal email on the payout record is the verified address you want us to use. 🚀 How to request a reprocess Open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat. In your message, include: 1. The article title or order reference. 2. The declined amount and approximate payment date. 3. Confirmation that you updated your PayPal email in the platform. 4. The verified PayPal email that should receive the payout. Ask clearly for the declined payout to be reprocessed. Do not send payment through another channel or share full account passwords. Our team only needs the payout details and the corrected PayPal email. 📊 What happens after you ask A teammate locates the declined payout, confirms the PayPal email on file, and sends the payment again when the details are valid. You will get an update in the same chat when the reprocess is submitted and when PayPal accepts it. - If the email is still wrong or unverified, we will ask you to correct it before sending again. - If PayPal accepts the payment, timing to see the funds depends on PayPal, not on a second approval of the article. - If PayPal declines it again, we will tell you the reason we can see and what to update. Keep the chat thread open so you can reply quickly if we need a corrected email. That is the only way to track the reprocess. 💡 If you still do not see the payment Check PayPal for a pending, held, or completed payment before opening a new request. Also confirm you are looking at the same email we reprocessed to. Pending holds are controlled by PayPal and cannot be released from inside Search Atlas. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

✅ Publisher Website Submission, Ownership Verification, and Automated Approval

📌 What this article covers This guide explains how to submit a website as a publisher in Search Atlas, how ownership is verified, and when a site can be added and activated automatically. Use it before requesting a manual review so your submission has the details needed for a clear decision. ✅ Before you submit a publisher site Prepare the site so automated checks can confirm that you control it and that it is suitable to activate. - Use a live domain that loads over HTTPS and is the exact property you want listed. - Confirm you can edit the site or its DNS, because ownership proof requires a change only the owner can make. - Match the account email to a domain, hosting, or analytics contact when possible. - Check basic quality: original content, a clear niche, working navigation, and no parked, adult, gambling, or malware warnings. - Have site facts ready: primary topic, country or language, and whether you accept relevant placements. 🚀 How to submit the website 1. Open Publications and choose Add Publication. 2. Enter the canonical domain, such as https://example.com, without tracking parameters. 3. Select the main topic, language, and audience so the listing can be categorized correctly. 4. Submit the site and stay on the verification step until the status changes. A submission is a request to list the property. It is not active for publisher use until ownership is verified and approval checks pass. 🔐 How ownership verification works Search Atlas must confirm that the account submitting the site controls that domain. Complete one available verification method and then recheck the status. - DNS record: add the exact record shown in the platform to the domain’s DNS, wait for it to propagate, then select verify. - HTML file or meta tag: place the provided file or tag on the homepage exactly as shown, publish it publicly, then select verify. - Connected property: if the platform offers a connection to an account you already use for that domain, connect the same property and confirm it. Do not remove the proof until the site shows as verified. Removing it early can fail the check or pause activation. Verification confirms control of the domain; it does not by itself guarantee approval. ⚙️ When automated approval happens After ownership is verified, automated checks review whether the site can be activated. Approval is typically automatic when all of the following are true: - The domain verifies on the first or a later successful check. - The site is publicly reachable and is not blocked, parked, or under construction. - Content and topic signals are clear enough to classify the publisher. - No policy, security, or quality warning requires a person to review the site. When those checks pass, the publisher status changes to approved and the site can be activated without a support ticket. Refresh the publisher page if the status does not update immediately. 👀 When a person still needs to review it Automated approval is skipped or delayed if ownership cannot be confirmed, the domain does not match the submitted URL, the site is new or thin, access is restricted, or a quality signal needs judgment. You do not need to send screenshots unless chat asks for them. - Recheck the domain spelling and that the verification file, tag, or DNS record is public. - Remove maintenance mode, login walls, and geo blocks that hide the homepage from the checker. - Wait for DNS changes to propagate, then run verification again. - Update the topic and language if they do not describe the live site. If the status remains pending after those fixes, contact support from the platform and include the domain and the on-screen status. Do not create a second submission for the same site. 💬 Need help with a publisher submission? If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

📊 Why Content and UX Scores Show Zero

📊 What a zero score means A Content score or UX Signals score of zero usually means the platform does not yet have enough page data to calculate a result. It does not mean your site has failed an audit. Scores stay at zero until a crawl finishes and the required signals are available for the pages in your project. 🔍 Common reasons scores stay at zero - The crawl has not finished. Content and UX scores appear only after pages are discovered and analyzed. - No pages are in scope. An empty project, the wrong domain, or a filter that matches no URLs will show zero. - The site blocked the crawler. A robots.txt rule, login wall, firewall, or bot protection can stop page collection. - Pages have little or no readable content. Thin, empty, or JavaScript-only pages may not produce a content score until rendered text is captured. - UX data is not available yet. UX Signals need page-experience measurements. New, low-traffic, or recently changed URLs often have no data at first. - A required connection is missing. If a score depends on an installed tracking pixel or a connected Search Console property, it stays at zero until that source is active. 🛠️ How to restore your scores 1. Open Site Explorer and confirm the domain matches the site you want scored. 2. Check that the latest crawl has completed. If it is still running, wait for it to finish, then refresh the report. 3. Clear filters, segments, and page-type limits so you are not viewing an empty set of URLs. 4. Confirm important pages return a normal status and are not blocked by robots.txt, a password, or a firewall. 5. Open a key page and verify it has real, visible text. If content loads only after scripts run, recrawl after the site is reachable to the crawler. 6. For UX Signals, confirm the tracking pixel is installed on the pages you care about and that any required Search Console property is connected to this project. 7. Give new or low-traffic pages time to collect experience data, then refresh the report. 💡 How to read the scores once they appear Content score reflects how complete and useful the on-page content is, including coverage of the topic, headings, and supporting detail. UX Signals reflect the page experience, such as loading, responsiveness, and visual stability. Each score is calculated per the pages included in the current view. A sitewide zero means data is missing. A zero on one URL means that URL alone lacks the inputs for that metric. 🚀 If scores are still zero Recrawl the project after fixing blocked pages, missing content, or a disconnected data source. Check one representative URL first so you can confirm scores populate before reviewing the full site. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

📚 Where to Find Search Atlas Trainings

📍 Where training sessions are listed Search Atlas training sessions are listed inside the platform so you can see upcoming classes without leaving your account. Open the platform and check these places, in order: - Features Menu, then Explore Training Calls. Look for labels such as Training, Trainings, Academy, or Webinars. - In-app announcements on your dashboard or notification bell. New sessions are often posted there with the date, time, and a join link. - Your registration email if you already signed up. The invite includes the session time and the link to join. The same area usually shows both upcoming live sessions and past recordings, so you do not need a separate site to browse the schedule. 🚀 How to join a session 1. Sign in to Search Atlas with the account you want trained on. 2. Open the training list from the Help or Resources menu, or from the announcement on your dashboard. 3. Choose the session that matches the topic you need, such as onboarding, OTTO, or reporting. 4. Select Register or Join. Register ahead of time when the button is shown so the session is saved to your list. 5. At the start time, return to that same session and select Join. Use a current browser and allow audio if the class is live. If a recording is available after the class, it appears on the same session page. Open the session and select the recording link. You can pause and replay it at any time while you are signed in. 💡 What you can expect from a training Sessions are short, practical walkthroughs of the platform. A typical class covers: - Where key tools live in the navigation - How to complete a common workflow from start to finish - Where to review results after a change - Time at the end for questions when the session is live Live classes follow the time zone shown on the session page. Join a few minutes early so you are connected before the host starts. 🛠️ If you cannot see any trainings Try these checks before you contact support: - Confirm you are signed in to the correct Search Atlas account. - Refresh the page, or sign out and sign back in, then reopen the Help or Resources menu. - Check the notification bell and your dashboard for a pinned training announcement. - Search your inbox for a Search Atlas training or webinar invite, including spam or promotions folders. - Ask a workspace admin whether trainings are limited to certain roles on your account. If the list is still empty, or a join link fails, use in-platform chat. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

📊 Inactive Publisher Websites and Metrics

🔍 Why a publisher website becomes inactive A publisher website can move from active to inactive after a routine data refresh, even if it was available before. Inactive means the site no longer meets current Search Atlas publisher requirements. It does not always mean the website is offline. Common reasons a site is marked inactive include: - Quality or policy checks: the site no longer fits publisher standards for relevance, content quality, or acceptable linking practices. - Availability: pages are down, blocked, newly restricted, or no longer accept placements. - Index or traffic changes: search visibility or audience signals dropped enough to fail the latest review. - Updated source data: metrics and site attributes were refreshed, and the new snapshot no longer qualifies. Publisher status is based on the latest review, not on a site’s past active status. A website that qualified earlier can be removed when newer data shows it no longer qualifies. 📊 Why DA and DR may not match other tools Domain Authority (DA) and Domain Rating (DR) are third-party scores. Search Atlas displays the values from its connected data sources on a set refresh cycle. Other SEO tools use their own crawls, formulas, and update times, so the same domain can show different numbers on the same day. A difference versus another tool does not, by itself, mean the Search Atlas figure is wrong or that the site should be active again. Use the metrics shown in Search Atlas as the scores tied to publisher eligibility. Small gaps are normal. Very large gaps can be reviewed if you believe the stored data is outdated. 🛠️ What to check before you request a review Gather a few details so the review can be completed quickly: 1. Confirm the exact domain, including www or non-www if that is how it is listed. 2. Note when it last appeared active and what status you see now. 3. Compare the DA and DR shown in Search Atlas with the other tool, including the date you checked. 4. Check that the site loads, is indexed, and still offers the placement type you expect. 5. Save any evidence that the site recently improved, such as recovered traffic or removed spam. If the site is down, deindexed, or clearly outside publisher guidelines, a re-evaluation is unlikely to restore it until those issues are fixed. 🚀 How to request a re-evaluation Yes. Previously active publishers can be re-evaluated. Approval is not guaranteed. The site must meet current requirements based on the latest data, not its earlier status. Open the publisher portal, then Publications → Existing Publication, and check whether the site is Active, Inactive, or Paused. Our team will review the listing against current publisher criteria and update the status if it qualifies. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

💳 Request a Refund or Cancel Subscription

💳 What this article covers This article explains how to cancel a Search Atlas subscription after a trial and how to ask for a refund review. Cancelling stops future renewals. A refund is a separate request and is not granted automatically, even if you have not logged in. 🛑 Cancel before more charges If your trial is still active, cancel before it ends so the first paid charge does not start. If you are already on a paid plan, cancel as soon as you decide you no longer need the subscription. Cancellation applies to future billing periods. It does not, by itself, refund charges that have already been processed. After you cancel, keep your confirmation and note the date. Your account remains available through the end of the current paid period unless a refund is approved and access is adjusted as part of that review. 📝 How refund requests are reviewed Refund requests are reviewed individually. Low or no login activity can be part of that review, but it does not guarantee a refund. The review looks at the full account, including trial timing, renewal dates, invoices already paid, and any use of the platform. To help the team review your request quickly, be ready to share: - The email address on the account - The months or invoices you want reviewed - Whether you want cancellation only, a refund review, or both - A short note, such as that you did not log in during those months 💬 How to submit your request Use the live chat widget inside the platform. This is the only support channel for cancellation and refund requests. 1. Sign in to Search Atlas. 2. Open the chat widget in the bottom-right corner. 3. Send your message in the chat. A member of our support team will reply in the conversation. 4. State clearly that you want to cancel, request a refund review, or both. 5. Include the account email and the billing months in question. Do not start a new subscription or change plans while a refund review is open unless a team member asks you to. Keep any on-screen confirmation until the review is complete. ⏱️ What to expect next A team member will confirm whether the subscription is set to cancel and whether your refund request can be reviewed. If a refund is approved, it is returned to the original payment method. Bank or card processing times vary and are outside Search Atlas control. If a refund is not approved, you will be told why and your cancellation status will still be confirmed so future renewals do not continue. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

🛠️ Fix a Cal.com Inline Embed

🔍 What causes the embed to stop loading? A Cal.com inline booking widget may stop appearing when its embed script is outdated, the page selector no longer matches, or a security, caching, or website plugin change blocks the script. This can affect multiple pages, including a homepage and contact page. ✅ Confirm the problem 1. Open the affected page in an incognito window. 2. Check whether the booking area is completely blank or shows an error. 3. Test the page on a different browser and device. 4. Confirm the Cal.com booking link is still active, such as nicole-diena-dobernig-uitzf2/30min. ⚙️ Replace the inline embed Remove the old Cal.com code from the affected page or reusable website section. Then add a current inline embed from Cal.com using the booking link and a unique container ID. Use this structure as a guide, and copy the latest version from Cal.com when available: <div id="my-cal-inline"></div> <script>window.Cal=function(){window.Cal.q=window.Cal.q||[];window.Cal.q.push(arguments)};Cal("init","30min",{origin:"https://cal.com"});Cal("inline",{elementOrSelector:"#my-cal-inline",calLink:"nicole-diena-dobernig-uitzf2/30min",layout:"month_view"});Cal("ui",{hideEventTypeDetails:false,layout:"month_view"});</script> Replace 30min, the container ID, and the booking link if your Cal.com event uses different values. Do not add multiple scripts targeting the same container. 📄 Add it to each website page 1. Add the container and script to the homepage. 2. Add a separate container with a unique ID to the contact page. 3. Ensure the script is placed where your website builder allows custom HTML or code blocks. 4. Publish both pages and clear any website, CDN, or browser cache. 🧪 Test the updated widget - Load each page in an incognito window. - Confirm the calendar and available times appear. - Open the widget on mobile and desktop. - Use your browser console to check for blocked scripts, content security policy errors, or JavaScript errors. - Verify that selecting a time opens the Cal.com booking flow. 🚧 If the widget is still blank Check that the container ID in the script exactly matches the ID in the page HTML. Remove duplicate Cal.com scripts, temporarily disable script-minification features, and confirm that your content security policy allows scripts and frames from cal.com. Also verify that the event has not been disabled or renamed in Cal.com. If your website uses a page builder, confirm that it permits JavaScript in published content. Some builders remove script tags from standard text blocks, so use the builder’s custom HTML or header/footer code area instead. 💬 Get help from Search Atlas If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 2026

🔍 Find Active Sites and Article Assignments

📌 What this article covers If you manage a large site list, it can be hard to see which sites are active and which ones are still receiving new articles. This guide explains how to find active sites, what Inactive means, and how article assignment works. ✅ What Active and Inactive mean Active means the site is eligible for ongoing work in the platform, including new article assignment when your plan and settings allow it. Inactive means the site is saved in your account but is not currently receiving new articles. Inactive is common when you have added many sites and only a subset is turned on for content. - Inactive does not delete the site or its history. - Inactive sites do not get new articles until they are made active and assigned. - A long gap with no new articles usually means the sites you are watching are inactive, unassigned, or outside your current content allowance. 🔎 How to find your active sites 1. Open the publisher portal, then Publications → Existing Publication for sites and Articles → Awaiting Publication for article assignments. 2. Use the status filter and choose Active. Leave search blank so every active site is included. 3. Review the status column. Only rows marked Active are currently eligible. 4. Sort or scan the list if you have thousands of sites. Filtering is faster than scrolling. 5. Open an active site to confirm its content or article settings are turned on. To review sites that are not receiving articles, switch the same filter to Inactive. 📝 How article assignment works New articles are assigned only to sites that are active and included in your content setup. Adding a site does not by itself start article delivery. - The site status must be Active. - The site must be included in the article or content assignment for your account. - Delivery follows your plan limits. When the allowance is used, new articles wait until the next cycle or until you change which sites are included. - Sites left Inactive are skipped so your allowance is not spread across every site you have ever added. 🛠️ If you have not received articles for a long time 1. Filter the site list to Active and note how many sites appear. 2. If the active list is empty, select the sites that should receive content and set them to Active. 3. Confirm those sites are included in article assignment, not only added to the account. 4. Check that you still have article allowance for the current period. 5. Give the platform time to generate the next batch after a site is activated. Older inactive sites will not show a recent article history. If most of thousands of sites show Inactive, that is expected unless you have explicitly activated them. Activate only the sites that should receive articles so delivery stays focused. 💬 Still need help If the active filter does not match what you expect, or articles still do not appear after you confirm status and assignment, contact support from inside the platform. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

🔍 Fix Campaign Hub Health Checklist Warnings

⚠️ What these health checklist warnings mean The Campaign Hub health checklist reviews whether a campaign has a reachable landing page and detectable conversion tracking. A red not found status or a missing conversion warning does not always mean you forgot to connect something. It means the checklist could not confirm that item using the URL, domain, or tracking signal it expects. A page can look connected in the campaign while the checklist still fails if the saved URL does not match the live page, or if tracking is installed somewhere the checklist cannot see. 🔗 Check the landing page connection Compare the URL stored on the campaign with the page you believe is connected. Small differences are a common cause of a false not found result. - Use the same protocol, usually https, and the same host, including or excluding www. - Match the path exactly, including a trailing slash if the live page uses one. - Remove campaign parameters such as UTM tags from the checklist URL unless that exact address is the published page. - Confirm the page is published on the campaign domain and does not redirect to a different final URL. - Open OTTO PPC → Campaign Hub → the Setup column → Health checklist. Landing-page warnings are labeled Landing page needs a fix or Landing pages need attention. - Save the campaign again after correcting the URL so the checklist reads the latest value. If the connected asset belongs to another campaign, site, or draft, reconnect the correct live page and save. 📈 Check conversion tracking A conversion warning means the checklist did not find a conversion event tied to this campaign and landing page. Installing a tag on the main site is not always enough. - Confirm the conversion action is assigned to this campaign, not only created in your ads or analytics account. - Place the tag or pixel on the same final landing page the checklist is checking. - If you use a tag manager, publish the container after adding the tag. An unpublished change will not be detected. - Allow the tag to fire for visitors. A browser extension or consent block on one test visit is not, by itself, proof that tracking is missing. - Use the same domain as the landing page. A tag on a subdomain or thank-you page will not clear a warning that expects the landing page itself. - Trigger a test conversion, then allow time for the platform to record it before judging the checklist again. 🔄 Refresh the checklist before you troubleshoot further The health checklist does not always update the moment you connect a page or publish a tag. After you save the correct URL and confirm tracking: 1. Return to Campaign Hub and open the same campaign. 2. Reload the health checklist or refresh the page. 3. Wait a short time, then review the landing page and conversion rows again. 4. If the status is unchanged, reopen the landing page and conversion settings and confirm both were saved on this campaign. A green connection on another screen does not override a failed checklist row. Both must point to the same live URL and the same conversion. 🛠️ Decide whether this is a mistake or a bug You are usually not mistaken if a page is connected, but the checklist can still be right to warn you. Treat it as a setup mismatch first. - If the final URL, domain, or conversion action did not match, correct it and refresh. That is expected behavior, not a bug. - If the live URL loads, the exact URL is saved on this campaign, tracking is published on that page, and the red warning remains after a refresh, the checklist may be out of sync. Before you escalate, note the campaign name, the exact landing page URL, where conversion tracking was installed, and the time you last saved. Those details let our team compare what you see with what the checklist is reading. 💬 Contact support from the platform If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

📊 Check Inactive Publisher Sites and Articles

📌 What Inactive means A publisher site marked Inactive is not currently eligible to receive new articles on Search Atlas. Active sites can be matched with new placements. Inactive sites are paused until ownership is verified and the site meets publishing requirements. If most of your sites show Inactive and you have not received articles for a long time, start by checking each site’s status and verification state rather than waiting for new assignments. 🔍 How to review your sites Open the publisher portal, then Publications → Existing Publication, and review each status: Active, Inactive, or Paused. Review articles under Articles. For each domain, note the status, ownership or verification state, and the date of the last article. - Look for labels such as Inactive, Pending verification, or a failed ownership check. - Confirm the domain listed is the exact property you still control, including the correct www or non-www version. - Check whether the site was removed, rejected, or left unfinished during setup. - Compare sites that still show Active with inactive ones so you can see what is missing. Only sites that are both verified and Active are considered for new articles. An inactive site will not receive placements even if it previously published content. ✅ Verify ownership Ownership must be confirmed before a site can stay or become Active. If verification fails or was never completed, the site remains Inactive and articles stop. 1. Select the inactive site and open its verification or ownership step. 2. Choose the method shown in the platform, such as a meta tag, HTML file, or DNS record. 3. Add the exact code or record to the site you control. Do not change the value. 4. Publish the change, then return to Search Atlas and run Verify. 5. Wait for the status to update. If it still fails, remove conflicting tags or old records and try again. You must be able to edit the website or its DNS. If another person or agency controls the domain, ask them to add the verification method, then complete the check in your account. Verification proves you manage the property; it does not by itself guarantee article volume. 🚀 Why new articles may have stopped New articles are assigned only to eligible Active sites. Common reasons placements pause include: - Ownership is unverified, expired, or pointing at the wrong domain. - The site status is Inactive, removed, or still in setup. - Required publishing details, such as categories or content preferences, are incomplete. - The site no longer meets quality, availability, or policy requirements. - There is currently no matching demand for that site’s topics. After a site returns to Active, new articles depend on available matches. Activation does not schedule a fixed number of posts or restore missed assignments automatically. 🛠️ What to do next 1. Export or list every site and mark each one Active, Inactive, or unverified. 2. Finish ownership verification on every domain you still want to use. 3. Remove or ignore domains you no longer control so your list stays accurate. 4. Recheck status after verification. Confirm the site now shows Active. 5. Allow time for new matching. Review the articles list later to confirm fresh assignments. If a site stays Inactive after a successful ownership check, or you cannot tell which sites are Active, use in-platform support and share the domain names you checked. 💬 Need more help If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

💳 Why a Free Trial Was Charged

💳 Why a free trial can still charge your card A Search Atlas free trial is for customers who have not already used a trial or a paid plan. If you signed up for the 7-day trial and your card was charged $99, billing treated the signup as a paid subscription instead of an eligible new trial. This commonly happens when the system recognizes a returning customer. ✅ What makes a signup eligible Trial eligibility is based on more than the email address entered at signup. We may also review: - Whether that email, or a related account, already used a trial - Whether a paid plan, cancellation, or refund is already on file - Whether the same card or billing profile was used before A second login does not reset trial history. Using a different email by itself does not guarantee another 7-day trial. 🔁 If you are a returning customer Customers who previously purchased backlinks, received a refund, or held any Search Atlas plan are generally not eligible for another free trial. A past refund stays with the original customer record. Signing up again can start the current paid plan immediately and charge the plan price, such as $99, to the card you enter. Please do not create extra accounts to try the trial again. Duplicate signups can cause additional charges and slow down a billing review. 🛠️ What to check in your account 1. Open the profile avatar, then Billing → Plans & Top-ups for the plan name, and the Invoices tab for the amount and charge date. 2. Make sure you are signed in with the email that owns the charge. 3. Do not submit another trial signup or add another card while the charge is being reviewed. 4. Keep your receipt so the payment can be matched quickly. 💬 How to ask for a billing review A specialist can review whether the trial should have applied and whether a refund or account adjustment is appropriate. A refund is not automatic. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat. Share the email on the account, the charge amount, and the date the card was billed. Our team will confirm eligibility and explain the outcome in the same chat.

Last updated on Nov 03, 2026

⚙️ MCP AI Visibility Platform Availability

📌 What this article covers MCP AI Visibility and the in-product AI Visibility experience do not always expose the same platforms at the same time. A platform can appear in quota or overview while llmv_submit_prompts rejects it. This article explains that behavior for Perplexity, Claude, DeepSeek, and Muse, and what you can request without using a project slot. 🚫 Perplexity on submit versus quota If llmv_submit_prompts returns Platforms no longer available: perplexity, Perplexity is not accepted for new MCP prompt runs right now. That rejection is a platform availability rule, not a mistake in your prompt text, filters, or project settings. get_quota can still list Perplexity after submit has stopped accepting it. Quota shows what the catalog last reported; it does not override the submit check. Do not retry the same call hoping the quota list will force acceptance. Search Atlas does not mark this change as permanent or temporary inside the MCP error. Treat Perplexity as unavailable for MCP submission until that error stops. There is no customer-side setting to turn it back on. 🔎 Claude, DeepSeek, and Muse Claude, DeepSeek, and Muse can appear in AI Visibility and in llmv_get_overview while llmv_submit_prompts and the platforms filter reject them. Overview reports platforms the product knows about. Submit and the platforms filter only accept platforms currently enabled on the MCP connector. - Seeing a platform in the UI or overview does not mean you can submit prompts to it through MCP. - A rejected platform name is expected until MCP enablement catches up with the product view. - No date is returned by these tools. Availability is added when the connector is updated, not by changing filters or creating a new project. Submit only the platform values the connector currently accepts. Remove rejected names from the platforms filter instead of resubmitting the full set. 📊 Results without using a project slot Per-platform results for auto-generated, non-branded prompts are stored on a tracked project. Tracking uses one project slot. An untracked project does not use a slot, and it does not keep that full result set. You cannot get a per-platform breakdown for only non-branded auto-generated prompts on an untracked project without using a project slot. To get those results: 1. Track the project so it uses a slot. 2. Use the auto-generated non-branded prompt set on that tracked project. 3. Read per-platform results from the tracked project after the accepted platforms finish. If you only need a one-off check, stay untracked and accept that MCP will not return the stored per-platform, non-branded-only report. Tracking is required for that report, even when you filter out branded prompts. ✅ What to do next - Use llmv_submit_prompts only with platforms it currently accepts. - Ignore Perplexity in get_quota while submit says it is no longer available. - Do not expect Claude, DeepSeek, or Muse on MCP submit just because overview lists them. - Track a project only when you need saved per-platform results. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

🔗 How to Connect GSC and Your First Site

✅ Before you connect Search Atlas reads performance data from Google Search Console (GSC). The Google account you connect must already be an owner or full user on a verified property. Open Google Search Console first and confirm the site is verified. Use that same Google account inside Search Atlas. 🔗 Connect Google Search Console 1. Sign in to Search Atlas. 2. Open onboarding or the project for your first website. 3. Choose Connect Google Search Console (it may also say Connect GSC). 4. In the Google window, select the account that can open the property. Switch accounts before you approve access if the wrong one is selected. 5. Allow the requested permissions so Search Atlas can read Search Console data. 6. Back in Search Atlas, select the matching property and save or continue. If the Google window does not open, allow pop-ups for Search Atlas and try the connection again. 🌐 Add your first website 1. Enter the site exactly as it is verified in Search Console. 2. Match the property type. A domain property such as example.com is not the same as a URL-prefix property such as https://www.example.com/. 3. Match https or http, and www or non-www, to the verified property. 4. Finish setup. New connections can take time before data appears. A short delay does not mean the link failed. 🛠️ If a property does not appear When a site you know exists is missing, Search Atlas is usually signed into the wrong Google account, or the property is not fully available yet. - Wrong Google account. Disconnect, then connect again with the account that opens the property in Search Console. - Not verified. In Google Search Console, confirm the property is verified. Unverified or removed properties are not listed. - Limited access. You need owner or full user access. A restricted user may not see the property. - Property type mismatch. Add the site with the same domain or URL-prefix format that is verified. - Just verified. Wait a short time, then refresh the property list. - Many properties. Search or scroll the list. Only properties on the connected Google account are shown. 📍 Connect a Google Business Profile Google Business Profile (formerly Google My Business) is separate from Search Console. If a listing is not found, connect the Google account that manages that verified listing. A personal account and an agency account are not interchangeable. The listing must already be verified in Google before Search Atlas can select it. 💬 Get help inside the platform A teammate can walk you through the connection from inside the product. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

💰 Request a Refund for Unused Months

💡 What this article covers This article explains how to ask Search Atlas to review charges for subscription months you did not use. It is written for customers who cancelled, or believe they cancelled, and later saw recurring charges. A review is not an automatic refund. Our team checks your account, cancellation history, and billing records before deciding. 📋 When a refund review may apply You can request a review if you were billed after you stopped using the product, or after you tried to cancel and expected billing to stop. Common situations include: - You cancelled months ago and continued to be charged. - You could not finish cancellation and billing continued. - You paid for months you did not use after access ended. Charges for time when your subscription was active and available are generally not unused months. Each request is reviewed against your account history. ⚙️ Before you request a refund Gather a few details so the review can start quickly: 1. Confirm you are signed in to the account that was charged. 2. Note the months you believe were unused and the charge dates if you have them. 3. Check whether you received a cancellation confirmation. 4. Look at your billing history for the plan name and amount of each charge. If your subscription is still active and you want future charges to stop, cancel it before or while you request the review. Cancelling prevents new charges. It does not by itself refund past charges. 🚀 How to request a review Refund reviews are handled in the platform chat. Follow these steps: 1. Sign in to your Search Atlas account. 2. Open the chat widget in the bottom-right corner of the platform. 3. Send your message in the chat. A member of our support team will reply in the conversation. 4. Say that you are requesting a refund review for unused subscription months. 5. Share the details listed below and wait for a reply in the same chat. Do not send payment card numbers, full bank details, or passwords in chat. Describe the charges by date and amount only. 🛠️ What to include in your message A clear request helps us match charges to your account. Include: - The email address on the billed account. - The approximate date you cancelled or tried to cancel. - The months you want reviewed and why you consider them unused. - Charge dates and amounts, if you know them. - Any cancellation confirmation or error you saw, described in your own words. Example: I cancelled in March and was charged for April, May, and June without using the product. Please review those months for a refund. 📊 What happens next A teammate will review your subscription status, cancellation record, and invoices. They may ask a short follow-up question if a date or account is unclear. Possible outcomes include a full refund of the reviewed months, a partial refund, or an explanation if the charges match an active subscription. Refunds, when approved, go back to the original payment method. Timing depends on your bank or card provider after we process the decision. We cannot promise a refund before the review is complete. You will receive the decision in the chat thread. 💬 If you need more help If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

📊 Check Active Publisher Sites and Articles

📋 What This Article Covers Use this guide to see which of your publisher sites are Active on Search Atlas, understand why new articles may stop, and find or create a fresh export of your site list. An Inactive status means that site is not currently receiving new article assignments. 🔍 How to Check Which Sites Are Active Open Publications. Each site card shows Active, Inactive, or Paused. Review articles separately under Articles, grouped as Awaiting Publication and Published. 1. Sign in to Search Atlas and open the section where your publisher sites are listed. 2. Look for the status next to each site. Focus on sites marked Active. 3. Use search or filters, if available, to show only Active or only Inactive sites so you do not have to scroll through thousands of rows. 4. Open an individual site to confirm its current status and any recent article assignments tied to it. Only sites shown as Active are eligible for new articles. Sites marked Inactive are paused and will not receive new assignments until they are active again. 📰 Why New Articles May Stop A long gap with no new articles usually means there are few or no eligible active sites, not that assignments were lost. Common reasons include: - Most sites are Inactive. Inactive sites are excluded from new article assignments. - No open assignments. Active sites may already have their current articles completed, with nothing new queued yet. - Site details need review. Missing or outdated site information can keep a property from staying active. - You are viewing an old export. A downloaded sheet is a snapshot. It does not update when statuses change in the platform. Always use the live site list in the platform as the source of truth. Compare it with any older sheet before assuming articles are missing. 📄 Find or Re-export Your Site List Search Atlas does not keep a separate inbox of past Google Sheet links inside support. Exports are generated from your account when you download them. 1. Go to the same publisher sites list in the platform. 2. Filter for Active if you only need sites that can receive articles. Leave the filter off to export every status. 3. Choose the export or download option and select a spreadsheet format if one is offered. 4. Save the new file. Check your browser downloads folder if you do not see it open. Also check the Google account you were signed into when you exported, including recent files and shared drives. 5. If you still cannot find an older sheet, create a new export. The new file replaces the need to recover the previous one. Name the file with the date so you can tell it apart from older downloads. The platform list remains the current record if the sheet and the product ever disagree. ✅ What to Do When Most Sites Show Inactive A large number of inactive sites is expected if those properties are paused. It does not by itself mean your account is broken. - Filter to Active and note how many sites remain. Those are the ones that can receive new articles. - Open a few inactive sites and review any on-screen reason or required fields. - Update site details where the product allows you to, then check whether the status changes to Active. - After changes, refresh the list before exporting again so the sheet matches the platform. If active sites still show no recent assignments after you confirm their status, contact support with the site names and the date you last expected an article. Do not rely on an old sheet as proof of the current status. 💬 When to Contact Support If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat. Have this ready so we can help faster: the site URLs you believe should be active, a screenshot of the status filter, and the date of your last successful export.

Last updated on Nov 03, 2026

🏢 Fix a Wrong Business or Agency Account Type

🏢 What the account type is When you create a Search Atlas account, you choose a profile category such as Agency, Brand, Site/Business Owner, Publisher, SEO Expert, Link Builder, or Other. That choice is a profile label that describes who the account is for. It does not set how the platform is organized, which features you see, or how work is grouped. 🏢 Brand versus agency Two common labels, and who they usually fit: - Brand: you manage SEO for your own company or a single brand. - Agency: you manage SEO for clients. 🛠️ How to correct it Do not create a second account to fix the label. Keep using the account you already have and request a change. 1. Stay signed in to the account that has your projects and billing. 2. Note which profile category the account should have. 3. Open the chat widget in the bottom-right corner of the platform and send your message. 4. Tell them the account type label is wrong and which one you need. 📊 What to expect after the change Our team updates the label for you. Your login email, projects, and users stay the same. Navigation and features do not change, because the label does not control them. If a feature you expected is missing, it is tied to your plan rather than the account label. Mention that in the same chat so the team can check. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

⚙️ Disable OTTO Meta and Schema

🧩 Why meta and schema get duplicated OTTO and Yoast can both write title tags, meta descriptions, and structured data. When both are active, search engines may see two versions of the same fields. That does not break your site, but it can make testing harder and leave the wrong version in control. Pick one tool as the source of truth. If Yoast already manages meta and schema, turn those outputs off in OTTO and leave Yoast enabled. ✅ Before you change anything - Confirm Yoast SEO is active and set to output titles, meta descriptions, and schema for the pages you care about. - Open a live page and view the source. Note whether you see OTTO markup, Yoast markup, or both. - Decide the split you want. Most teams keep Yoast for meta and schema and keep OTTO for other on-page work such as content, links, or technical fixes. - If several people edit the site, tell them not to re-enable OTTO meta or schema after you turn them off. 🛠️ Turn off OTTO meta and schema 1. Sign in to Search Atlas and open the project for the affected site. 2. Open OTTO SEO for that project. 3. Open the OTTO settings or deployment controls that list optimization types. 4. Find the controls for meta titles, meta descriptions, and schema (structured data). 5. Turn deployment off for each of those types. Do not disable the whole OTTO installation unless you also want to stop every other OTTO change. 6. Save the settings. If the WordPress plugin is installed, confirm the same meta and schema options are off there so the plugin does not inject them again. 7. If OTTO has already published meta or schema on specific pages, remove or roll back those deployed changes so only Yoast remains. Leave Yoast’s meta and schema settings on. Do not disable Yoast schema unless you later choose OTTO as the only schema source. 🔎 Confirm only Yoast remains 1. Clear any site, CDN, or plugin cache, then hard-refresh a few key URLs. 2. View the page source and search for the title, meta description, and JSON-LD script blocks. 3. You should see one title, one meta description, and one set of schema from Yoast. OTTO should no longer add a second set. 4. Check a homepage, a blog post, and a landing page, because templates can differ. 5. In Google’s Rich Results Test or a schema validator, confirm a single valid graph and no conflicting types for the same page. If duplicates remain, another plugin, your theme, or a cached HTML snapshot may still be printing tags. Disable extra SEO plugins one at a time and recheck the source. 💡 Keep the two tools from overlapping - Use Yoast only for titles, descriptions, and schema when that is your chosen owner. - Use OTTO for tasks Yoast is not handling, and leave those OTTO types enabled. - Avoid running a third SEO plugin that also writes meta or schema. - After theme or plugin updates, recheck one URL so a reset does not turn OTTO meta or schema back on. 💬 Need a hand with your project If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

📊 When AI Agent Credits Renew

💡 Why you see a low credit message A PRO account includes 60,000 AI Agent credits for each billing period. The Running low on AI Agent credits notice appears as the allowance is used up. Credit alerts fire when 50%, 90%, and 95% of the allowance has been consumed, so the notice can appear well before the credits are gone. It does not mean your PRO plan is broken or that AI generation is turned off. The credit meter reads remaining out of total. On a PRO plan the allowance is 60,000 credits, so a meter showing 9 / 110 is not the PRO AI Agent allowance. 🔄 Do credits renew every month Yes. On an active PRO subscription, AI Agent credits renew once each billing period. For monthly billing, that is once a month. They do not refresh every calendar day, and they do not reset for every customer on the first of the month. At renewal, your balance returns to your plan allowance (60,000 on PRO). Credits you did not use do not roll over and add to the next period. Credits you already spent are not refunded when the new period starts. 📅 Which day your credits renew Your renewal day is the same day your Search Atlas subscription bills. It is tied to your account, not to a single company-wide date. - If you subscribed on the 14th, credits typically refresh on the 14th of each billing month. - If that day does not exist in a shorter month, the charge and credit refresh follow the next billing date shown on your subscription. - A plan change, upgrade, or reactivation can move the date to the new billing cycle. The low-credit warning can appear any day of the period once a usage level (50%, 90%, or 95% consumed) is crossed. It is based on how much of the allowance has been used, not on how many days are left before renewal. 🛠️ How to check your renewal date 1. Sign in to Search Atlas and open your account or billing area. 2. Find the subscription or plan section for your PRO account. 3. Look for the next billing date or renewal date. That is the day your AI Agent credits refresh. 4. Compare it with the credit counter so you know how much of the current allowance is left before that date. If the billing date and the credit counter do not seem to match, wait until the renewal date passes and refresh the page. The new allowance should appear after the billing cycle updates. 📊 How to read the quota - The first number is your remaining balance for this period. - The meter reads remaining out of the total allowance, and the low-credit notice appears when usage crosses 50%, 90%, or 95% of the allowance. - Each AI Agent action that uses generation draws from this balance. - When the balance reaches 0, new AI Agent generations stay limited until the renewal date or until you move to a plan with a higher allowance. 🚀 How to avoid running out early - Check the credit counter before large batches of AI work. - Spread heavier generation across the billing period instead of using most credits in the first few days. - Note your personal renewal day so you know when the full allowance returns. - If your plan allowance is not enough for your workflow, review plan options in billing. A higher plan increases the allowance on its own billing cycle. 💬 Still need help If your renewal date has passed and the balance has not returned to your plan allowance, or the counter does not match your PRO subscription, If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

💰 Affiliate Payouts and Removed Articles

💰 How affiliate payouts work Affiliate earnings are tracked in your Search Atlas dashboard and paid on a regular cycle. Amounts earned in one month usually appear as pending and are included in the following month’s payout. For example, October earnings are commonly paid in November. A pending balance is not the same as a completed payment. Payout timing can shift if your account is missing payout details, a minimum threshold has not been met, or a review is still open. Always compare the payout period, the pending amount, and the paid amount before assuming a payment was skipped. 📊 Where to check your balance Open the account menu, then Earning History. Review Pending and Received payouts. Payouts are issued during the first week of each month for earnings cleared in the previous month. Review these items: - Period: Confirm you are looking at the correct month, such as October earnings scheduled for a November payout. - Pending balance: This is money recorded but not yet sent. - Paid amount: This is money already released for that cycle. - Adjustments: Look for deductions tied to removed, unpublished, or ineligible articles. - Payout status: Note whether the cycle is pending, processing, paid, or on hold. If the dashboard total does not match your own notes, list each article, its earning amount, and whether it is still live. That list makes a review faster and more accurate. 🛠️ Why live articles may be removed An article can leave your dashboard even if it was live earlier. Common reasons include: - The article no longer meets program or quality rules. - The content was unpublished, replaced, or removed by the publisher. - The placement was duplicated or attributed to the wrong account. - A review found the earning was not eligible for that period. Removal is not always a permanent loss of the content itself. It means the article is no longer counted in your current affiliate view. If it was paid or pending, the related earning may be reversed. 📉 How deductions are calculated When an article is removed after it generated affiliate credit, the credit for that article is deducted from your pending balance or from a later payout. A deduction such as a combined article adjustment only covers the earnings tied to the removed items. It does not reduce unrelated approved earnings. Check the adjustment line against the articles that disappeared. The deduction should match the total credit previously shown for those articles. If two articles were removed, add their individual credits and compare that sum with the deduction. ✅ What to do before contacting support 1. Confirm the earning month and the expected payout month. 2. Record the pending total, any paid total, and the deduction amount. 3. List the removed articles and the credit previously shown for each one. 4. Verify that your payout details are complete and that your account is in good standing. 5. Refresh the dashboard so you are not viewing an outdated balance. Do not resubmit the same payment request multiple times. One clear request with the period, expected amount, article names, and deduction amount is enough for a review. 💬 When a payment still looks missing If the numbers still do not match after you compare the period, pending balance, and article adjustments, contact support with those details. Include the payout month, the amount you expected, the deduction amount, and the names of the removed articles. Our team can then trace whether the payout is still pending, already released, or changed by a valid adjustment. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

📍 Find a Missing Google Business Profile

📍 Why the profile may not appear Manager access in Google does not always mean the business is ready to show inside Search Atlas. The profile must be linked to the Google account you connected, and it must be in a state our sync can read. This article explains the usual causes and the steps to take before you contact support. 🔍 Confirm you are looking in the right place Start with a quick check so you do not spend time on a connection problem that is only a filter or account mismatch. - Open the project or location list where Google Business Profiles are managed. - Search by the exact business name, and also try the city or street if the name is common. - Clear search filters, location groups, and status filters that might hide the listing. - Confirm you are signed into the Search Atlas account that owns this project, not a teammate workspace. ⚙️ Check the Google account and role Search Atlas can only see profiles on the Google account you authorized. Manager access on a different login will not appear. 1. In Google Business Profile, open the business and check Users or Business Profile settings. 2. Note which Google email is listed as Owner or Manager. 3. In Search Atlas, open your Google connection settings and confirm that same email is the connected account. 4. If a different email is connected, disconnect it and connect the account that actually manages the profile. 5. If the profile sits under a brand or organization account, connect the user who can see that location, not a personal Gmail that only has access to other listings. Owner access is more reliable for setup. If you are only a Manager and the Owner has not finished verification, the profile may stay hidden until that work is complete. 📊 Review the profile status in Google A profile can be missing from tools when Google has not fully published it. In Google Business Profile, check for any of these states: - Not verified. Complete verification with the method Google offers. Unverified profiles often do not sync. - Pending or under review. Wait until Google finishes the review, then refresh the connection. - Suspended or disabled. Resolve the issue in Google first. Search Atlas cannot restore a suspended profile. - Duplicate. Google may hide a listing that matches another profile. Keep the verified primary listing and remove or merge the duplicate in Google. - Newly created. Allow time after verification, then reconnect so the latest locations are pulled in. 🛠️ Refresh the connection After the correct account and a healthy profile are confirmed, force a fresh sync: 1. In Search Atlas, disconnect the Google Business Profile account. 2. Reconnect and accept every permission prompt. Declining location access will leave businesses out of the list. 3. Choose the Google account that has Manager or Owner access, especially if several accounts appear. 4. Return to the business list and search again. 5. If you manage many locations, scroll or search rather than expecting only the newest profile at the top. Do not create a second profile in Google to force a match. Duplicates make the correct listing harder to find and can lead to suspension. 💡 Still missing after these checks Gather the business name, full address, the Google email that has access, and whether the profile is verified. That context lets our team see whether the listing is blocked by account permissions, verification, or a sync gap. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

🔍 Track WWW and Non-WWW Keyword Rankings

🌐 Why the Host Version Matters Search engines can treat www and non-www as the same website when redirects and canonical tags point to one preferred version. Keyword rank tracking still needs one consistent project URL so new checks stay aligned. If one project uses a www address and another uses the same domain without www, the ranking reports can look different even when the keywords match. Tracking the host your site actually serves avoids that mismatch. ✅ Pick the Version Your Site Uses Open your website in a browser and check the address after the page finishes loading. - If visitors land on the www address, track the www version. - If visitors land on the address without www, track the non-www version. - Use https when the site loads securely. Do not keep an old http address if the site redirects to https. Use that same preferred address on every project that should report the same website. 🛠️ Match the Project URL 1. Open the project you want to keep. 2. Go to the project's Site Explorer or OTTO settings, where the website URL is saved — there is no generic project-settings page for it. 3. Replace the URL with the preferred version, including https and www only if that is the live address. 4. Save the project. 5. Repeat these steps for any other project that should track the same host. Do not create a new project only to switch between www and non-www. A new project starts a separate ranking record. 📊 Keep Your Keyword History Keyword history stays with the existing project. Updating the website URL on that project does not delete the keyword list or the rankings already stored there. - Edit the current project instead of deleting it. - Leave the existing keywords in place. - If you already have two projects, each one keeps its own history. Those histories are not combined automatically. To point both projects at the same host while keeping both histories, update each project URL in place and do not remove either project. 🔄 Refresh Rankings After the project URL matches the preferred host, refresh rankings so the next check uses the updated address. 1. Open the project. 2. Go to keyword rank tracking. 3. Start a refresh for the tracked keywords. 4. Wait until the new results finish before comparing positions. Older rows remain in the history. New rows show the refreshed check. 💬 When to Contact Support Contact the team if the URL field cannot be edited, a refresh does not start, or you need help confirming which host to track. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

⏳ Why Publisher Counteroffers Stay Pending

⏳ What Pending Means A counteroffer stays Pending while the publisher has not accepted or declined it, or while the platform is still syncing the latest status. Pending is not an error by itself. It means the negotiation is open and waiting for the next action from the publisher or from the system. 🔍 Check the Offer First Before you resend anything, confirm you are looking at the correct record. - Open the publisher portal, then Publications → Counter Offer. A pending offer is labeled Pending counteroffer. - Go to the publisher or link outreach area and open the offer thread. - Clear status filters and search by publisher domain or offer ID. - Refresh the page. A recent reply can take a short time to appear. - Review the offer date, price, target URL, and anchor so you know which counteroffer is stuck. 🛠️ Common Reasons It Stays Pending - The publisher has not responded yet. Many teams review offers only on business days. - The decision is still open. The status remains pending until they accept or decline. - An old view is cached. A cleared filter or another browser may show the updated status. - Offer details are incomplete. A missing target page, anchor, or price can delay a reply. - A newer counteroffer replaced the earlier one. Check the full thread so you are not watching an old message. ✅ What You Can Do 1. Wait through the response window shown on the offer before sending another counteroffer. 2. Open the thread and confirm your latest price, notes, and placement details are clear. 3. If that window has passed, send one polite follow-up in the same thread. Do not create a duplicate offer for the same placement. 4. If you no longer want the placement, withdraw or decline the pending counteroffer so it does not stay open. 5. Refresh and confirm the offer has left the pending view after it is accepted or declined. 💬 When to Contact Support Contact support if the counteroffer has been pending well past the response window, the status never changes after a refresh, or the thread shows a reply that does not match the status. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat. Include the project name, publisher domain, offer date, and a short note about what you already checked. This helps the team locate the record quickly.

Last updated on Nov 03, 2026

🧹 Clear Stale FAQ Schema in OTTO

📌 Why stale FAQ schema still appears OTTO labels schema as FOUND when that markup already exists in the page source. A found FAQPage record is not an editable draft, so the Knowledge-Based Trust dashboard can show nothing to change even while old questions and answers still render. If staging pages still show a financing claim such as as low as $75/mo, that text is coming from FAQ schema still published in the HTML or from the copy OTTO last crawled. Changing an empty dashboard will not remove it. 🔍 Check the page source first 1. Open OTTO SEO → Overview → Schema Markup for the site and use the FAQ Page schema type. There is no Schema Markup → FAQ menu. 2. View the page source and search for FAQPage and the outdated financing phrase. 3. Note whether the block comes from JSON-LD, microdata, a theme, a plugin, or a financing widget. 4. Search the same source for Review or AggregateRating if a review schema is also listed. 🛠️ Remove or replace the obsolete FAQ 1. In your CMS, theme, plugin, or tag manager, find the FAQ that still contains the old claim. 2. Replace it with the current offer, or delete that FAQ item if it should no longer appear. 3. Save and publish the staging page so the HTML no longer includes the stale sentence. 4. Clear any staging, CDN, or plugin cache so the next crawl sees the updated source. 📊 Clear an undeployed Review schema An undeployed Review schema is a suggestion OTTO has not pushed live. It will not appear as an editable Knowledge-Based Trust record when it was never deployed or when OTTO only detected it on the page. - In OTTO, review structured-data suggestions for the affected page. - Discard or delete the undeployed Review item so it cannot be deployed later. - If the Review markup is FOUND in the page source, remove it in the CMS the same way you remove the FAQ schema. 🚀 Reprocess the pages in OTTO 1. Open the affected staging pages in OTTO. 2. Run a fresh crawl or reprocess so OTTO reads the updated HTML. 3. Confirm the old FAQPage record updates or drops off. 4. Confirm the Review schema is no longer pending deployment. Reprocessing does not rewrite schema that your site still outputs. If the stale claim remains after a recrawl, the source page still contains it. ✅ Confirm the fix - Search the updated page source for the old price phrase and confirm it is gone. - Keep only the FAQ and review markup you intend to publish. - Wait until the new OTTO crawl finishes before comparing the dashboard again. 💬 When to contact support Contact support only after the page source no longer contains the old FAQ or Review schema and a fresh crawl still shows the stale FOUND record. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

📉 Why Organic Keyword Metrics Drop

📊 What the metric shows In Site Metrics, the organic keywords figure under GSC Performance is the number of keywords your connected property ranked for in the top 100 organic results for the selected date range, after keywords not linked to a page and duplicate or irrelevant entries are removed. It is not the raw number of Google Search Console queries, and it is not the same as clicks, impressions, or average position. Google only returns queries that meet its reporting rules. Some searches are grouped, delayed, or left out for privacy, so the keyword count can move even when your overall visibility stays steady. 🔍 Why the number can fall - A shorter or different date range compares fewer days, so fewer unique queries appear. - Privacy filtering hides low-volume queries. If those queries fall below Google’s threshold, they disappear from the count. - Seasonality reduces demand for topics that were popular in the earlier period. - Ranking changes can remove queries that no longer earn impressions, while new queries may not replace them right away. - Indexing or content changes, including removed pages, noindex tags, redirects, or a site migration, can shrink the queries Google shows. - Property or filter changes, such as switching between a domain and a URL-prefix property, or filtering by page, country, or device, change the result set. - Data delay means the latest days in Search Console are often incomplete and may revise later. 🛠️ How to read the drop 1. Confirm the date range and comparison period. Match them before treating the change as a loss. 2. Check clicks and impressions beside the keyword count. A lower query count with stable clicks usually means fewer reported queries, not necessarily less traffic. 3. Review average position for your main pages. A broad position drop is more meaningful than a change in unique queries alone. 4. Compare the same property, country, and device filters in Search Atlas and in Google Search Console. 5. Look for recent content, technical, or migration changes that could affect indexed pages. 6. Wait for the most recent days to finish processing before judging a short-term decline. 💡 What a drop does not mean A lower organic keyword count does not automatically mean your rankings collapsed, your account is broken, or Search Atlas stopped tracking keywords. It means fewer queries were included in the Search Console data for that view. Use clicks, impressions, position, and the specific pages involved to decide whether action is needed. 🚀 What to do next If impressions and clicks are also down, prioritize pages that lost visibility, restore or improve the content, and check indexing. If only the keyword count changed, keep monitoring the same date comparison rather than reacting to the query total by itself. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

💳 Confirm Downgrade Charges Before You Switch

💳 Why a downgrade can still show a higher charge Changing back to a lower plan, such as a $99 plan, and updating your credit card are two separate actions. Updating a card does not by itself change your plan price. If the higher plan is still active when payment runs, the charge can be the current plan amount, such as $199, even if you intended to move to $99. Proration means the platform adjusts what you owe based on the time left in the current billing period and the price difference between plans. A downgrade confirmation can include a credit for unused time, a smaller charge, or no new charge until the next renewal. Always read the amount on the confirmation screen before you submit. 📋 Check the plan and card before you pay - Open billing or subscription settings and confirm which plan is active right now. - Start the plan change and select the lower plan you want, such as the $99 plan. - Review the summary. It should name the new plan, the billing date, and any prorated credit or charge. - Update the credit card only after the new plan is selected, or update the card first and then complete the downgrade before the next charge. - Do not submit if the summary still lists the higher plan or a $199 charge you did not expect. 🛠️ Complete the downgrade in the right order 1. Go to your account billing area inside Search Atlas. 2. Choose the lower plan and open the change summary. 3. Confirm the displayed price, proration, and next renewal date. 4. Add or select the card you want charged going forward. 5. Submit only when the summary matches the plan and amount you expect. 6. Save or screenshot the confirmation for your records. If you update the card while the higher plan is still active, the next successful payment can bill that higher plan. The card update replaces the payment method. It does not downgrade the subscription. 📊 What to look for after the change - The active plan name matches the lower plan. - The renewal price matches that plan. - Any prorated credit appears on the invoice or billing history. - The new card is marked as the default payment method. A charge that already processed on the previous plan is not reversed automatically by selecting a lower plan afterward. Billing history is the source of truth for the amount, date, and plan on that payment. 💡 If you were charged the old plan price Check whether the downgrade was submitted before the charge and whether the confirmation listed $99 or $199. If the higher amount was charged after you completed a downgrade, or the confirmation did not match what you approved, contact support with the charge date, amount, and plan name so the team can review the invoice. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

💰 Why Publisher Remittances Stay Unpaid

💡 Why a remittance may not be released Publisher remittances are released only after earnings are approved and your payout profile is complete. If you have not received payment for the last few weeks, the balance is usually still pending, below the release rules, or blocked by a payout detail that needs an update. Approved earnings move to a payable balance on the platform payout schedule. Time in your bank after release depends on your payment method and can add several business days. 🔍 What to check first 1. Open the publisher portal, then the profile menu → Earning History (heading Earning). Each remittance row shows date, article posted, status, PayPal transaction ID, amount, and PayPal email; the summary card totals Pending and Received. 2. Review the payout period. Recent activity may still be inside the approval window and is not yet due. 3. Confirm your payment method, account holder name, and account details are saved and verified. 4. Check that any required tax or business profile is complete. Missing details can pause a release. 5. Look for a minimum payout amount. Balances under that amount stay unpaid until the next cycle after the minimum is reached. 6. Review any in-platform notice about a hold, rejected payout, or returned payment. ⚙️ Common reasons payments are delayed - Pending approval: Earnings must finish the review period before they can be remitted. - Incomplete payout profile: Unverified bank, wallet, or tax details stop the release. - Below the minimum: Smaller balances roll forward until they qualify. - Returned payment: A mismatch in account details sends the remittance back and places it on hold. - Account status: A paused or restricted publisher account can delay payouts until the issue is resolved. 🛠️ How to get the next remittance released 1. Update any incorrect payment or tax details, then save the profile. 2. Wait for the current payout cycle to close if your earnings are still pending. 3. If a previous payment was returned, correct the destination account before the next attempt. 4. Recheck the payable balance after the scheduled payout date. Do not count calendar weeks alone, because weekends, holidays, and bank processing can extend the wait. Fixing the profile does not instantly send an already missed transfer. The corrected details apply to the next eligible release. 📊 What to have ready if it still looks wrong Before you contact support, note the payout period, the amount you expected, the status shown in the platform, and the payment method on file. This helps the team trace whether the remittance is pending, held, returned, or already sent. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

🔍 How to Generate Schema Markup with OTTO

📌 What schema markup does Schema markup is structured data that helps search engines understand your pages. It can support rich results such as FAQs, reviews, products, and organization details. OTTO generates recommended schema for eligible pages so you do not have to write the code yourself. ⚙️ Before you generate schema Confirm these items first: - The correct website project is open in Search Atlas. - OTTO is installed on the site so approved changes can be published. - Key page details are accurate, including titles, descriptions, and business information. Accurate page content leads to more useful schema. OTTO uses your site data to suggest markup; it does not invent facts that are not on the page. 🚀 Generate schema with OTTO 1. Open OTTO SEO → Overview → Schema Markup → Generate Schema. 2. Review the suggested schema type, such as Organization, Article, Product, FAQ, or Local Business. 3. Check that names, URLs, and other details match the live page. 4. Approve or enable the schema you want OTTO to use. 5. Publish or deploy the approved OTTO changes. After publishing, allow time for the live site and search engines to pick up the update. Generation alone does not place markup on the site until the change is approved and deployed. 📊 Review the markup before you publish Read each suggestion before you enable it. Confirm that: - The schema type matches the page purpose. - Visible page content supports the structured data. - Business name, address, and contact details are current when those fields appear. - You are not enabling duplicate or conflicting schema for the same page. If a suggestion looks wrong, leave it disabled and correct the page content first. Then return to OTTO and generate or refresh the recommendation. 💡 Confirm schema is live 1. Open the published page in your browser. 2. View the page source or use a structured data testing tool. 3. Search for the schema type you approved. 4. Compare the live markup with the OTTO recommendation. If the markup is missing, confirm OTTO is still installed and that the schema change was published. Clear any site cache, then check the page again. 🛠️ Fix common schema issues - No schema suggestion appears: Make sure the page is in the project and that OTTO has finished scanning the site. - The wrong type is suggested: Update the page content so its purpose is clear, then refresh the recommendation. - Changes are approved but not live: Confirm OTTO installation and republish the deployment. - Details are outdated: Edit the source content or business profile, then regenerate the schema. 💬 Get help from the team If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

💬 How to Talk to a Live Agent

💬 When to ask for a live agent Use live chat when a task is blocked, a setting will not save, data looks wrong, or you have already tried the steps in a help article. For quick how-to questions, search the knowledge base first. That often solves the issue without a wait. 🛠️ What to try before you escalate A short check can fix many technical requests and gives our team the details they need if you still need help. - Refresh the page and try the same action once more. - Confirm you are in the correct project or website. - Note the exact page, button, and any error text you see. - Check whether the issue happens in another browser. 🚀 How to reach a member of our support team Live help is available only inside the platform. There is no phone number and no email address for support. 1. Open the chat widget in the bottom-right corner of the platform. 2. Describe your issue in one or two clear sentences. 3. Send your message in the chat. A member of our support team will reply in the conversation. 4. Stay in the chat so the teammate can reply without starting over. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat. 📋 Details that speed up your request Share these items in your first message so the teammate does not have to ask for them. - What you were trying to do. - What you expected to happen. - What happened instead, including any error message. - The project, site, or report name. - When the issue started and whether it happens every time. ⚙️ After you are connected Answer follow-up questions in the same chat. Do not open a second chat for the same issue. If you are asked to try a step, say whether it worked. You can return to the widget later to continue the same conversation when it is still open.

Last updated on Nov 08, 2026

💳 Request a Partial Refund After Reporting Failure

💳 When a Partial Refund Can Be Requested If reporting never worked during your current subscription period, you can ask Search Atlas to review a partial refund for the remaining part of your plan. A refund is not automatic. Our team reviews your account, the billing dates, and the reporting problem you describe. 📋 Before You Submit a Request A short, clear summary helps the review move faster. Have these details ready: - Plan and billing dates for the current subscription period. - What failed in reporting, including report names, dates, and any error messages. - What you already tried, such as refreshing, regenerating a report, or checking project settings. - Whether you want to cancel now or keep the account while the issue is reviewed. 💬 How to Request Cancellation and a Partial Refund 1. Sign in to Search Atlas. 2. Open the chat widget in the bottom-right corner of the platform. 3. Send your message in the chat. A member of our support team will reply in the conversation. 4. Say that reporting did not work and that you want to cancel and request a refund for the remaining part of your subscription. 5. Share the details you prepared, plus screenshots that show the reporting failure. Cancelling stops future renewals. It does not by itself issue a refund. Ask for both cancellation and a partial refund in the same chat so they are reviewed together. 🔎 What the Team Reviews - Whether reporting was unavailable or produced no usable results during the paid period. - How much of the current billing period remains. - Any earlier credits, plan changes, or refunds already applied to the account. The outcome depends on your account. The teammate will confirm whether a partial refund is approved, the amount, and how it will be returned to your original payment method. ✅ After Your Request Stay in the chat until you receive a clear confirmation of your cancellation status and the refund decision. If a refund is approved, the time it takes to appear depends on your payment provider. Return to the same chat if the charge is still showing after the processing window you were given. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

🏢 Set Up a Single Franchise Location Project

🏢 What this article covers This guide explains the best way to manage a Search Atlas project for one franchise location, such as Hanover, MD for CRS Services, and why a project created from a page like https://crspackout.com/hanover/ shows the parent domain https://crspackout.com. 🔍 Why the parent domain appears A folder or page on a website is not its own domain. /hanover/ is a location page that lives on crspackout.com. Search Atlas identifies the project by the root domain so sitewide data stays attached to the property that actually owns the page. - Domain: crspackout.com is the website Search Atlas tracks for technical health, crawling, and authority. - Location URL: /hanover/ is the page you want to rank for that city or service area. - Expected result: seeing the parent domain is normal. It does not mean the Hanover page was ignored or replaced. Create a separate project only when a location has its own domain or subdomain, such as hanover.example.com. A path on the main site should stay under the parent-domain project. ⚙️ Best way to manage one location Keep one project for the parent domain, then focus keywords, content, and reporting on the single location page. Do not create a second project for the same domain just to force the location path into the domain field. 1. Open or create the project from the location URL. Confirm the saved domain is the parent site. 2. Set the location page as your target URL for the Hanover market, using the full address that includes /hanover/. 3. Build a location keyword list with the city, nearby areas you truly serve, and the services offered at that location. Avoid copying another franchise’s keyword targets. 4. Optimize the Hanover page with a unique title, meta description, headings, service details, and local proof such as the address, service area, and photos. Do not duplicate the homepage or another city’s page. 5. Align your Google Business Profile and other listings with the same business name, address, phone number, and the Hanover page URL. 6. Track results for that URL by watching rankings and traffic for the location keywords, not only domain-wide totals. 📊 What to check after setup - The project domain is https://crspackout.com. - The page you are optimizing is https://crspackout.com/hanover/. - Target keywords include the Hanover location and are not shared unchanged with other cities. - The location page has unique content and a clear link from the main site. - Name, address, and phone details match the public listing for that location. 💡 Common mix-ups The project looks like the whole brand. That is correct for a folder URL. Use keywords and the location URL to keep the work specific to Hanover. You want metrics only for one page. Review the target URL and its keywords. Domain-level scores still describe the parent site because that is where the page is hosted. Several locations share one domain. Use the same parent project and separate target URLs and keyword sets for each city. Give every location its own page instead of sending all cities to the homepage. 🛠️ If the location still looks wrong Confirm you entered the full location URL, including https and the /hanover/ path, and that the page loads publicly. If the project domain is the parent site and the target URL is the Hanover page, setup is correct. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

🔍 Why Publisher Sites Show Inactive

📌 What inactive means A publisher website can be approved, then later marked inactive. Inactive means the site is no longer available for new placements. It does not delete past orders or change work that was already completed. Approval is based on the site at the time it was reviewed. Search Atlas rechecks publishers on an ongoing basis. If quality, traffic, or policy signals change, the site can be paused even if it was active before. 📉 Why a previously active site changes Common reasons a site moves from active to inactive include: - A drop in organic traffic or visibility - A large loss of referring domains or a spike in low-quality links - Thin, duplicated, or AI-heavy content added after approval - Outbound link patterns that look paid, excessive, or off-topic - Ownership, niche, or language changes - Security issues, downtime, or a domain that no longer resolves - Updated marketplace standards that the site no longer meets You will usually see the inactive status on the publisher profile or when you try to add the site to a campaign. The site will not appear as an available placement option. 📊 Why DA and DR look different Domain Authority (DA) and Domain Rating (DR) come from different companies and different crawls. Search Atlas scores are not a copy of Ahrefs, Moz, Semrush, or any other tool. A mismatch does not mean either number is broken. - Different indexes: each tool sees a different set of links and pages. - Different timing: one tool may still show older data while another has already updated. - Different formulas: the same backlink can raise one score and barely move another. - Displayed versus current data: a publisher card may show the metrics from the last successful review, not a live pull from a third-party tool. Use Search Atlas metrics to decide whether a site is eligible in this marketplace. Use other tools only as extra context. Do not expect the numbers to match. 🔄 Can the site be re-evaluated Yes. An inactive publisher can be reviewed again if the underlying issue has been fixed or if you believe the status is wrong. Re-evaluation is not automatic, and a review does not guarantee the site will be turned back on. Before you request a review, check the following: 1. Confirm you are looking at the exact domain, including www and the correct TLD. 2. Open the site and confirm it loads and is indexed. The niche is not a platform status you can verify — judge content focus manually. 3. Compare recent traffic and backlink trends, not only a single DA or DR number. 4. Note any recent redesign, migration, penalty, or ownership change. 5. Gather the publisher URL, the date it was last active, and a short reason you believe it should be active. 💬 How to request a review If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat. Include the full publisher URL, screenshots of the inactive status, the third-party metrics you are comparing, and what changed since the site was approved. A teammate can submit the site for another quality review and tell you the outcome. Continue using other active publishers while that review is in progress.

Last updated on Nov 03, 2026

💰 Track Pending Payouts and Removed Articles

💰 What this article covers This guide explains how to read a pending article payout, why a payment can stay pending longer than expected, and what happens when published articles are removed. It also shows what to check before you open a support case so payout and reinstatement questions can be resolved faster. 📊 How pending payouts work A payout marked pending means the amount is recorded in your account but has not finished processing. The balance you see, such as a specific dollar amount, is the amount currently queued. It is not the same as a completed payment. Pending does not always mean the payout is overdue. Processing can pause while placement, content, or publisher details are reviewed. The payout date is confirmed only after those checks are complete and the status changes from pending. - Open your payout or earnings area and note the amount, currency, and current status. - Check whether the related articles are listed as published, pending, or removed. - If you already opened a case, keep the case number handy so it can be matched to the payout. ⏱️ Why a payout may look overdue A payout can remain pending for several ordinary reasons: - The publication is still being verified. - One or more linked articles were removed and the payout is on hold until that review finishes. - Publisher or payment details need confirmation. - The payout window for that batch has not closed yet. Search Atlas cannot confirm a personal payout date or a specific case outcome inside this article. Status for an amount already showing as pending, including any open case, is confirmed in your account or by a teammate in live chat. 🛠️ How to check status yourself 1. Sign in and open the section where article earnings and payouts are listed. 2. Find the pending amount and review the status label next to it. 3. Open each linked article and note whether it is live or removed. 4. If you have a case number, search your support history for that number and read the latest update. 5. Compare the article list on the case with the articles currently shown in your account. Use the case number, payout amount, and article titles together. Sharing only one of these can slow the review. 📄 When articles are removed An article can be removed if it no longer meets publication requirements, the placement changed, or a quality review is in progress. Removal does not automatically mean the article is permanently rejected. Reinstatement is reviewed article by article. A removed article is put back only after it passes the same checks required for publication. If three articles were removed, each one needs its own status. Some may be reinstated while others stay removed. - Under review: the article is being checked and is not live yet. - Reinstated: the article is approved to go live again and should return to your publication list. - Not eligible: the article will not be republished, and any related payout may be adjusted. Do not resubmit the same article repeatedly while a review is open. Duplicate submissions can create extra cases and delay the original request. ✅ What to have ready for a payout or reinstatement question Before you contact support, collect: - The pending amount and currency. - Your case number, if you have one. - The titles or links of the removed articles. - The date you first saw the pending status. - Any on-screen status text for the payout and each article. A teammate can then confirm whether the pending amount is still queued, whether the case is open, and whether each removed article is being reviewed for reinstatement. 💬 Get help in the platform If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

💳 White-Label Child Account Fee Disputes

💡 What these fees cover White-label child account fees are charges for client or child accounts under your white-label setup. Each active child account can add to your invoice based on the plan in effect for that billing period, even if you did not recently change how those accounts were configured. 📊 Why an unexpected charge can appear A new or higher charge does not always mean the account structure was edited. Common reasons include: - Active child accounts were already billable under the plan for that period. - Plan or pricing updates applied at renewal, so usage that was previously included may now appear as its own line. - Billing-cycle timing can show a full period, a prorated amount, or more than one line for the same accounts. - Quantity changes from reactivated, duplicated, or newly connected child accounts increase the total. - Service interruptions do not automatically remove subscription fees. Outage credits are reviewed separately from the white-label line item. 🛠️ How to review the charge 1. Open Billing or Invoices in your Search Atlas account. 2. Find the invoice that includes the disputed amount. 3. Note the invoice date, line description, child-account quantity, and exact total. 4. Compare that quantity with the child accounts listed in your white-label or agency workspace. 5. Check whether any accounts were active, reactivated, or created during that billing period. Save the invoice number before you contact support so the team can match the exact line. 🚀 How to request a refund or outage credit Refunds and outage credits are not applied automatically. A billing specialist compares the invoice with your plan terms and any confirmed service interruption. Approval is not guaranteed. 1. Gather the invoice number, charge amount, and the child-account quantity you believe is correct. 2. If you are also asking about an outage, include the dates and what was unavailable. 3. Say clearly whether you want a refund review, an outage credit, or both. 4. Open the chat widget in the bottom-right corner of the platform and send your message. Do not create or delete child accounts only to alter a past invoice. Those changes affect future billing and can make the review harder. ⚙️ What happens after you ask - The team confirms the invoice line and the number of billable child accounts. - They check whether the fee matches the plan active on the invoice date. - They review any outage credit separately from the white-label fee. - Approved adjustments are returned to the original payment method or added as account credit, depending on how the invoice was paid. - If the charge matches active accounts and plan terms, it stays on the invoice and the reason is explained in chat. 📌 How to avoid future surprises - Review child-account quantity before each renewal. - Remove client accounts you no longer use before the next billing date. - Read invoice line items as soon as a receipt arrives. - Keep billing questions in one chat thread so the history stays attached to the invoice. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

💳 Request a Refund for Unused Add-Ons

🔍 Why Unused Add-On Charges Appear Search Atlas bills your main plan and any add-ons on a recurring schedule. An add-on stays active until it is removed, even if you are not using it. That is why a charge can repeat for a second month after you expected only your base plan, such as a $199 subscription, to remain. A refund review looks at whether an add-on was active, whether it was used, and whether it was canceled before the billing date. Not every unused charge is automatically reversible, but our team can check the invoice and explain the outcome. 📊 Check What You Are Paying For Before you request a reversal, confirm which items are on the invoice: 1. Open your account billing or subscription area in the platform. 2. Find the latest invoice and separate the base plan from each add-on line. 3. Note the add-on name, amount, and billing date for every charge you do not recognize. 4. Check whether that add-on is still listed as active. Keep the invoice date and the exact line items handy. Clear details help us review the charge faster and reduce the chance of another billing cycle. 🛠️ Request a Billing Review If a recurring add-on charge does not match what you use, ask for a billing review rather than waiting for the next invoice. - State the plan you intend to keep, such as your $199 subscription. - Name each add-on you believe was unused and the months charged. - Say whether you want the add-on removed so it does not bill again. - Ask for a refund review of the unused recurring charges. Our team will compare the subscription history with the invoice. If a refund is approved, it is applied back to the original payment method. Timing depends on your bank or card provider after we process it. If a charge cannot be refunded, we will tell you why and what was billed. 🚀 Stop Future Unused Charges Removing an unused add-on is the surest way to prevent the same charge next month. Do this as soon as you confirm you do not need the service: 1. Open the subscription or add-ons section. 2. There is no self-serve remove or cancel button for the White-Label add-on. Contact support in the chat and ask them to cancel it for you. 3. Confirm that only your intended plan remains active. 4. Save or note the cancellation date. Canceling an add-on stops future renewals. It does not, by itself, reverse a charge that has already been processed. Mention both actions when you contact us: remove the add-on and review the past charge. 💬 Get Help From Our Team If the charge has already posted and you need it reviewed today, contact us from inside the platform with your invoice details. Please do not start a payment dispute until we have had a chance to review the add-on, because a dispute can slow the correction. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

🏷️ Fix White-Label Domain Invite Issues

🏷️ What the invite message means A completed domain setup and an accepted white-label invitation are two separate steps. DNS and SSL can look finished while the platform still treats the workspace as waiting for an invitation. Until that invitation is accepted under the correct account, branding, color metrics, and shared report links can keep using the default Search Atlas experience. The message does not always mean your DNS failed. It usually means the invite was sent to a different email, expired, was opened while signed into another account, or was never accepted after the domain became active. ✅ Confirm the domain is fully connected Open your white-label or agency branding settings and check the custom domain status before changing anything else. - The domain should show as connected or active, not pending, failed, or unverified. - Both the root domain and the www version should point to the records shown in the platform. Mixing old and new records can leave the domain half connected. - SSL should show as active. A certificate that is still provisioning can make share links fail on mobile even when the domain looks complete. - Remove duplicate domains if the same hostname is attached to more than one workspace. - After DNS changes, allow time for propagation, then refresh the status inside the platform rather than only checking your registrar. If the status is anything other than active, finish or retry that connection first. An invitation cannot apply branding to a domain that is not fully live. ✉️ Accept the invitation on the right account The invite must be accepted by the same user who should own or access the white-label workspace. 1. Sign out of every Search Atlas session, including other browser profiles. 2. Open the invitation email and confirm it was sent to the address you use for this workspace. Check spam and promotions folders if you cannot find it. 3. Sign in with that exact email, then open the invite link again. Accepting it while signed in as someone else leaves the original account waiting for an invitation. 4. If the link expired or was already used, resend the invitation from the white-label or team settings and use only the newest link. 5. After accepting, return to the domain settings and refresh. The invitation prompt should clear once the account and domain are linked. Agency owners should also confirm the customer or team member was invited to the correct project. An invite to a different project will not remove the prompt on this domain. 🎨 Fix branding and color metrics Color metrics and branded interface elements load from the white-label profile tied to the active domain. If the invite is still pending, those settings are ignored and reports fall back to default colors. - After the invite is accepted, open branding settings and re-save your logo, brand name, and primary and accent colors. - Use full hex color values and save once. Partial saves can leave charts on the default palette. - Hard-refresh the report or open it in a private window so cached colors are not reused. - Check both desktop and mobile. A saved palette applies only after the custom domain serves the report, not when it is opened on a default Search Atlas URL. 📱 Repair mobile and report share links Share links must use the connected white-label domain. An older link that still points to a Search Atlas hostname, or a link created before SSL finished, will look broken or unbranded on mobile. 1. Confirm the domain status is active and the invitation prompt is gone. 2. Open the report from the project and create a new share link. Do not reuse a link copied before setup finished. 3. Check that the new link starts with your custom domain and loads over https. 4. Send that new link to a phone and open it in a private browser tab. Disable VPN or private DNS temporarily if the phone cannot resolve the domain. 5. If only some reports fail, regenerate the link for each affected report. Links are not all updated automatically when branding changes. If a new link works on desktop but fails on mobile, the phone is usually caching DNS or opening an old bookmark. Clear the mobile browser cache or try another network, then retest the new link. 🛠️ If the prompt remains Recheck three items together: domain status is active, the newest invite was accepted by the signed-in email, and a newly generated https link uses your domain. Saving branding again after those are true resolves most color and share-link issues. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

🚀 Getting Started with Search Atlas SEO Automation

🔍 Understanding SEO Automation Search Atlas SEO automation simplifies technical fixes, content deployment, and internal linking to help you scale organic traffic without manual effort. Powered by OTTO SEO, our automation engine evaluates your site architecture, identifies ranking opportunities, and prepares optimizations for your web pages. Changes are deployed after your approval, or automatically for the fields you have opted into auto-deploy with autopilot settings. ⚙️ Key Automation Features Our automation tools work quietly in the background to handle repetitive and complex SEO tasks: - Automated Technical SEO: Detect missing metadata, broken redirects, schema markup errors, and canonical tags, and prepare fixes you can approve or auto-deploy. - Dynamic Internal Linking: Suggest contextual internal links across your existing content to distribute PageRank effectively, deployed on approval or via autopilot. - Content Optimization: Receive actionable recommendations to enrich underperforming articles and deploy improvements on approval or via autopilot. - Continuous Site Auditing: Monitor your website 24/7 to catch technical errors before they harm search engine rankings. 📅 How to Schedule an Onboarding Call To help you get the most out of SEO automation, we offer personalized onboarding sessions. Follow these steps to schedule your call: 1. Log in to your Search Atlas platform dashboard. 2. Open the chat widget located in the bottom-right corner of the platform. 3. Send your message in the chat window. A member of our support team will reply in the conversation. 4. Request a walkthrough session, and our specialist will share a booking link so you can choose a convenient time. 💡 Preparing for Your Onboarding Session Maximize the value of your live onboarding session by taking a few quick preparation steps beforehand: - Integrate Your Website: Connect Google Search Console and install the OTTO pixel or WordPress plugin on your domain. - List Priority URLs: Identify your key conversion pages, core service pages, or articles that need immediate organic growth. - Prepare Technical Access: Ensure team members with CMS and DNS permissions are available if technical setup questions arise. 💬 Connecting with Support If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

🚀 OTTO Overview and Specialist Onboarding

🔍 What OTTO Is OTTO is Search Atlas’s SEO automation assistant. It reviews your site, recommends improvements, and can apply approved changes so you spend less time on repetitive SEO work. OTTO can help with technical fixes, on-page improvements, content opportunities, and ongoing monitoring. You stay in control: review recommendations before they go live and decide what OTTO should implement. ⚙️ What a Specialist Helps You Do A specialist walkthrough is for customers who want a person to guide setup step by step. It is not a replacement for OTTO. It helps you use OTTO correctly from the start. During onboarding, a teammate can help you: - Confirm your site is connected and ready for OTTO. - Explain what OTTO found and which items matter first. - Show how to review, approve, or skip recommended changes. - Set expectations for what OTTO automates versus what you still manage. - Answer questions about your goals, such as rankings, content, or technical health. 📋 How to Prepare Before You Connect A short prep list makes the session faster and more useful. 1. Sign in to Search Atlas and open the project for the site you want to discuss. 2. Confirm the correct domain is selected. 3. Note your main goal, such as fixing technical issues, improving key pages, or understanding OTTO’s recommendations. 4. List any pages, competitors, or recent site changes you want reviewed. 5. Have edit access to your site if you plan to approve implementations during the call. You do not need technical expertise. Clear goals and the right project open are enough. 🚀 How to Request a Guided Walkthrough Specialist help is available only inside the platform. There is no phone number or email queue for this request. 1. Open Search Atlas and stay on the project you want to discuss. 2. Open the chat widget in the bottom-right corner of the platform. 3. Send your message in the chat. A member of our support team will reply in the conversation. 4. Say that you need an OTTO overview and step-by-step specialist onboarding. 5. Share your domain, your goal, and any deadline or launch date. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat. 💡 What to Expect After Onboarding After the walkthrough, you should know where OTTO’s recommendations live, how approval works, and what to check next. Keep reviewing new suggestions as OTTO finds them. Approve only changes you understand, then watch results in your project over the following days and weeks. If something looks unclear later, return to the same chat widget and send your message. Mention your domain and that you already completed OTTO onboarding so the next teammate can continue from there.

Last updated on Nov 03, 2026

🛠️ Clear Stale OTTO FAQ Schema

💡 Why old claims still appear OTTO can keep FAQ and Review schema after the visible page copy has changed. That stored record is what gets rendered as JSON-LD, so an old line such as as low as $75/mo can remain on pages like service or repair URLs even after you update the page. The same can happen with Review schema that should no longer be published. Clearing the stale record and reprocessing the page replaces the old structured data. Editing only the on-page text does not always remove schema that OTTO already generated. 🔍 Check the affected pages Review both staging and live URLs. Open each page, view the page source, and search for FAQPage, Review, and the outdated phrase. Note every URL that still contains the old claim or an unwanted review block. - Confirm the offer, price, or review is no longer approved for that page. - Check FAQ answers, service descriptions, and any OTTO-generated schema for the same wording. - Repeat the check on staging before you publish changes to production. ⚙️ Remove the stale FAQ and Review records 1. In Search Atlas, open OTTO and select the site that owns the pages. 2. Open the affected URL and go to its schema or structured-data settings. 3. Find the FAQ item that contains the obsolete financing claim. Edit the answer to the current approved wording, or delete that FAQ item if the offer should not appear at all. 4. Open the Review schema for the same URL. Remove it if reviews should not be rendered, or replace it with the current approved review details. 5. Save the page settings, then use the available reprocess or regenerate action so OTTO rebuilds the schema instead of reusing the old record. 6. Publish or sync the change to the environment you are fixing. If the problem is only on staging, confirm you are viewing that staging site in OTTO before you reprocess. Do this separately for every URL that still shows the old JSON-LD, such as repair, heating, or service pages. A fix on one page does not clear records on other pages. 📊 Confirm the rendered JSON-LD After reprocessing, reload the staging page and view the source again. The old financing sentence should be gone from the FAQ JSON-LD, and unwanted Review schema should no longer appear. If a cache or CDN serves the previous HTML, purge that cache and check the page once more. - Search the source for the obsolete phrase and for Review. - Confirm the remaining FAQ answers match the current approved copy. - Check the live URL only after staging looks correct. 🚀 Prevent the claim from returning Keep financing and review language in one approved source. When an offer expires, update or delete the OTTO FAQ entry and reprocess every URL that used it. Avoid pasting old promotions into new FAQ answers, and do not leave unused Review schema enabled on pages that should not show reviews. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

💳 Refund Unused Months After Cancellation

💳 What this article covers This article explains what to do if you cancelled, or tried to cancel, and were still charged for months you did not use. It covers how cancellation and billing work, how to confirm your account is cancelled, and how to ask our team to review a refund for unused time. 📌 How billing works after you cancel Search Atlas bills on a recurring subscription. Charges stop only after cancellation is completed in your account. Starting a cancellation, closing the browser, or stopping use of the product does not end billing by itself. - Active plan: billing continues on your renewal date until cancellation is finished. - Completed cancellation: you keep access through the end of the period you already paid for, and future renewals should stop. - Unused months: time after a completed cancellation, or charges that continued because cancellation did not go through, can be reviewed for a refund. Each request is reviewed against your billing history and cancellation record. A refund is not automatic, but our team will look at charges for time you did not use. ✅ Confirm that cancellation is complete Before you request a refund, confirm the subscription is no longer set to renew. 1. Sign in to Search Atlas. 2. Open your account or billing settings. 3. Check the plan status. It should show as cancelled, or show that it will not renew. 4. Note the cancellation date and the date of each charge you want reviewed. If the plan still shows as active, finish cancellation in billing settings so no further charges are created while your refund request is reviewed. 🛠️ Request a review of unused months Refund reviews are handled by our team in live chat. Have your account email and the charge dates ready. 1. Open the chat widget in the bottom-right corner of the platform. 2. Send your message in the chat. A member of our support team will reply in the conversation. 3. Say you want a refund review for charges after cancellation or for months you did not use. 4. Share the dates you tried to cancel, the dates you were charged, and the amounts if you have them. Our team will compare those dates with your subscription record. If charges continued after a valid cancellation, or you were billed for time you could not use, they will tell you what can be refunded and how the refund is issued. 💡 What helps your request move faster - The email address on the Search Atlas account. - The date you cancelled or first tried to cancel. - A short note if the cancel button failed, you were unsure the cancellation saved, or you could not access the account. - Invoice or card statement dates for the months in question. You do not need to share your full card number. Please do not submit the same request through multiple places. One chat thread is enough, and it keeps the review in one place. 📊 What to expect after you ask - We confirm whether the subscription is cancelled and stop future renewals if it is still active. - We review each charge after your cancellation date, or after the date you can show you tried to cancel. - We tell you which months qualify and whether the refund is full or partial for a billing period. - Approved refunds go back to the original payment method. Timing depends on your bank or card provider. Access and data retention follow the plan terms for the period that remains paid. Cancelling does not remove past work already in your account unless your plan terms say otherwise. 💬 If you still need help If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

📄 Why Unpaid Articles Leave the Queue

📌 What this article explains This article explains why an article can disappear from the publication queue when its invoice is not paid in full, how to confirm payment, and how to request reinstatement. It also explains a separate issue: a missing-link flag caused by a URL that is stored in encoded form. 🚫 Why unpaid articles are removed An article stays in the publication queue only after the invoice connected to it is paid in full. Submitting an article and creating an invoice on the same day does not mean the article is paid. If the invoice is open, past due, failed, reversed, or only partly paid, the platform treats the article as unpaid and removes it from the queue. A note, screenshot, or message that the article was pending does not override the invoice status. The queue follows the paid or unpaid status recorded in your account. 💳 How to confirm the invoice is paid 1. Open Billing or Invoices in your account. 2. Find the invoice linked to the article. 3. Check that the status is Paid and the balance is zero. 4. If the status is not yet Paid, complete payment and wait until it shows as Paid. Invoice status filters are Paid, Pending, Canceled, and Refunded. Payment must be completed from your billing account. Search Atlas cannot mark an invoice paid or return an article to the queue while a balance remains. 🔁 How to reinstate a removed article 1. Pay the related invoice in full. 2. Confirm the invoice status is Paid. 3. Open Articles in the publisher portal and check whether the article has returned. 4. If it is still missing after the invoice shows as Paid, contact support with the invoice number and article ID. Have both numbers ready. Payment and queue status are reviewed together. An article is not reinstated from external proof alone. 🔗 Missing-link flags and URL encoding A missing-link flag is a separate check from payment. It can appear when a link is saved with encoded characters, such as %20 for a space or codes for symbols and non-Latin letters. The platform may treat that encoded address as different from the expected page URL, even when the page exists. - Open the article and compare the saved link with the live page address. - Replace percent-encoded characters with the normal characters in the real URL. - Save the clean, decoded URL and review the flag again. - If the page loads and the flag remains, share the article ID in chat for a review. Clearing a link flag does not restore an unpaid article. Paying an invoice does not remove a missing-link flag. Each issue must be resolved on its own. ✅ How to prevent another removal - Pay each invoice before you expect the article to remain in the queue. - Do not rely on same-day submission or a pending note as proof of payment. - Keep the invoice number and article ID together. - Use plain, fully decoded URLs when you add links. 💬 Get help with a specific article If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat. Include the invoice number, the article ID, and whether the invoice now shows as Paid. The team can confirm the queue status and review a possible false missing-link flag.

Last updated on Nov 03, 2026

🛑 Cancel Your Subscription After Low Results

📉 Why SEO results can take time Search Atlas helps you plan, create, and improve content so search engines can find and rank your pages. Rankings, traffic, and leads usually do not change overnight. Most sites need consistent publishing, technical fixes, and time for search engines to recrawl pages before results show up. If you expected faster gains, review the checklist below before you cancel. Many accounts improve after a few setup or strategy fixes. 🔍 What to review before you cancel - Site connection: Confirm your website, search console, and analytics are connected so reports reflect real data. - Target pages and keywords: Make sure you are tracking the pages and terms that matter to your business, not only broad or highly competitive keywords. - Published work: Check that recommended content and on-page changes were actually published on your site. - Technical issues: Look for crawl errors, slow pages, missing titles, or pages blocked from indexing. These can hide good content from search engines. - Time on the plan: If you started recently, allow enough time for new pages to be indexed and for reports to update. - Goals: Compare traffic, rankings, and leads against the goal you set. A flat chart does not always mean no progress if important pages are climbing. If something looks wrong in your reports, a teammate can help you read the data before you decide. 🚫 How to cancel your subscription 1. Sign in to Search Atlas with the account that owns the subscription. 2. Open your account or billing settings from the main menu. 3. Select the active plan you want to end. 4. Choose Cancel subscription (wording may appear as cancel plan or manage plan). 5. Review the end date and any notes about remaining access. 6. Confirm the cancellation. You should see a success message or an updated status such as Cancels at period end. Cancel before your renewal date so the plan does not renew. If you do not see a cancel option, your role may not include billing access. Ask the account owner to complete the steps, or use live chat for help. 📋 What happens after you cancel - Your plan stays active until the end of the current billing period unless your confirmation says otherwise. - You will not be charged for the next renewal after a successful cancellation. - Access to paid features ends when the subscription ends. Export any reports or content you need before that date. - Canceling does not automatically delete your website. Your site stays online; only Search Atlas tools and data access change. - Refunds, invoices, and plan changes follow the terms shown at checkout. Chat can review your specific billing status. You can usually reactivate later by choosing a plan again from billing settings. Historical project data may remain available depending on your account status. 💬 If you still want help before leaving Tell us which metric did not move (rankings, traffic, or leads), how long you have been on the plan, and which site you are tracking. That context lets us point you to the right report or setup fix. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

⚙️ Why Atlas Agent Credits Run Out Early

📊 Why credits disappear in the first days Atlas agent playbooks draw from your AI Agent credits based on the AI usage each run generates. An hourly routine can start many times in a day, so the same playbook can generate usage charges over and over. If several playbooks are set to hourly, usage adds up quickly and the monthly balance can be gone after the first day or two. The agent then has nothing left to spend until credits renew, which is why it can look stopped for the rest of the month. Credits are shared across Atlas agent activity. They are not reserved separately for later in the month. Early, frequent runs simply use the pool first. 🔍 What to check before you change anything Review the agent schedule and recent activity so you can see which routines caused the spike: - Frequency: Look for playbooks set to hourly rather than daily or weekly. - How many playbooks are active: Each active routine spends credits on its own schedule. - Run history: Note how many times each playbook ran in the first days of the month. - Credit balance: Confirm whether the balance hit zero and when it is set to renew. A useful estimate is runs per day times days active times the credits used per run. Hourly scheduling is the setting most likely to exhaust a monthly allowance early. 🛠️ How to make credits last the month 1. Pause any hourly playbook you do not need running continuously. 2. Change remaining routines from hourly to daily or weekly, based on how fresh the output needs to be. 3. Keep only the playbooks that support current work active. Turn off duplicates or tests. 4. Check the credit balance after the next scheduled run so you can see the new pace. 5. If the balance is already at zero, wait for the monthly renewal or ask support to review whether a plan or credit adjustment applies to your account. Changing the schedule now prevents the same spike after renewal. Hourly routines are best for short tests. For ongoing SEO work, a slower schedule usually gives you coverage all month without a large early charge. 💡 Reviewing September and October AI charges Usage is tied to playbook runs, not to a single end-of-month action. September and October charges can look high if hourly routines were left on at the start of each month. Gather the playbook names, the schedule each one used, and the dates the balance dropped. That context lets support match AI charges to specific agent activity. Support can walk through those charges with you. They cannot be reconstructed from this article alone, because balances and plan details differ by account. 🚀 Prevent the same escalation next month - After any new playbook is turned on, watch credit use for the first 24 hours. - Avoid leaving test routines on an hourly schedule. - Set a reminder a few days after renewal to confirm the balance is declining at the pace you expect. - If the agent stops working, check the credit balance before assuming the agent itself failed. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 03, 2026

🔍 Verify OTTO Pixel on Franchise Pages

📌 When the pixel is only on local pages Franchise accounts often control only local landing pages, not the main brand website. If the Search Atlas pixel is installed on those pages, Search Atlas can detect it when the project URL matches a page where the pixel actually loads. Seeing the pixel in your browser inspect tool confirms the code is present. It does not always mean the connected project is checking that same URL. ✅ Confirm the pixel on the landing page Open the exact local landing page in a browser, not the brand homepage. 1. Right-click the page and choose View page source or use Inspect. 2. Search for the Search Atlas pixel or OTTO script. 3. Confirm the script is in the page HTML and is not blocked by a consent banner, tag manager rule, or error in the console. 4. Repeat this on every local URL you expect Search Atlas to use. A pixel on one landing page does not cover other franchise pages. Use the full public URL, including https, the correct subdomain, and any path. A small difference such as www versus non-www, or a trailing slash, can point Search Atlas at a page that does not contain the pixel. 🔗 Align the project with that URL In Search Atlas, open the site or project connected to this franchise location. 1. Set the website URL to the local landing page where you confirmed the pixel, if you do not control the brand homepage. 2. Save the change, then run or wait for the next site check or crawl. 3. Give detection a short time to refresh. A newly added script may not appear immediately. 4. If you manage several locations, keep each location’s landing page tied to its own project or property so pixels are not mixed across franchises. Search Atlas looks for the pixel on the URL connected to the project. If that URL is the corporate homepage and you only installed the pixel on a local page, the project will not see it. 🛠️ Fix common reasons detection fails - Wrong page: The pixel is on a campaign URL, but the project still points to the homepage. - Script not executed: The tag exists in a tag manager but the trigger never fires on that landing page. - Blocked loading: A consent tool, ad blocker, firewall, or content security policy stops the script. - Duplicate or old code: An outdated snippet is present, or the page is served from cache. - Noindex or login wall: The landing page is not publicly reachable, so the check cannot load it. After correcting the URL or the installation, reload the landing page, confirm the script still appears, and recheck the project in Search Atlas. 💬 When to contact support Contact support if the pixel is visible on the exact public landing page, the project URL matches that page, and Search Atlas still does not detect it after a fresh check. Include the full landing page URL and the project name. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 04, 2026

🧩 How to Generate Schema Markup

📌 What schema markup does Schema markup is structured data that describes a page in a format search engines can read. It does not replace your visible content. It labels that content, such as an article, product, FAQ, organization, or local business, so search engines can understand it more clearly and may show richer results. In Search Atlas, schema is generated for a crawled page inside an OTTO project. Review the result before you deploy it, and make sure every value matches what visitors can see on the page. ✅ Before you generate schema - Open the correct Search Atlas project for the website. - Choose one page and confirm its title, URL, and main topic. - Pick the schema type that matches the page. Do not use product schema on a blog post or FAQ schema unless the page shows real questions and answers. - Have accurate details ready, such as business name, author, price, or location, if the page includes them. 🛠️ Generate schema in Search Atlas 1. Sign in to Search Atlas and open your project. 2. In the OTTO project, open Schema Markup and find the page under Page-Level Schemas. 3. Open Schema Markup in the OTTO project. Domain-Level Schema covers the sitewide organization schema, and Page-Level Schemas lists each page URL. 4. OTTO selects the schema type from the page summary. If none is available, it uses the default for that page type. You can change only the sitewide organization type under Domain-Level Schema. 5. Review the fields Search Atlas fills in. Edit any value that is missing, outdated, or different from the live page. 6. On the page-level schema row, select Generate schema, or Regenerate schema if content already exists. Search Atlas fills in JSON-LD, the format most search engines expect. 7. Read the generated markup once more. Copy it from the schema view, or deploy that schema with Deploy this Schema. Important: Only include facts that appear on the page. Misleading schema can cause search engines to ignore the markup. 🚀 Add the markup to your site To deploy a schema, select Deploy this Schema, or Deploy as-is if Search Atlas warns that validation issues remain, then confirm the change on the live URL. If you copy the markup instead, paste the JSON-LD into the page head inside a script tag with type application/ld+json, or into your site's structured data field, then publish the page. - Use one clear schema type for the page's main purpose. - Keep the script intact. Do not remove brackets or quotes. - Update the markup whenever the visible page details change. 🔍 Check that it works 1. Open the published page and confirm the content matches the schema. 2. Test the URL in Google's Rich Results Test or another public schema validator. 3. Fix any errors the test reports, regenerate or edit the markup, and test again. 4. Allow time for search engines to recrawl the page. Validation does not guarantee a rich result will appear. 💡 Fix common schema issues - Wrong type: Generate the type that matches the page, then replace the old markup. - Missing fields: Add the missing visible information on the page first, then regenerate. - Old details: Update the page and schema together so prices, dates, and names stay accurate. - Duplicate markup: Keep one current JSON-LD block for the same schema type so the signals do not conflict. 💬 Get help in the platform If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 04, 2026

🖼️ Fix OTTO Image Alt Text Not Updating

🖼️ What this article covers If you add or edit image alt text in OTTO, select deploy, and the live page still shows the old text or no alt text, use the checks below. Alt text is the short description stored on an image so search engines and screen readers can understand it. ⚙️ Why the alt text may not change - The edit was saved, but the image was not deployed. Open Image alt text, find the image, and select Deploy. Deployed means the change is being sent to the live site. - Check the image’s status in Image alt text. It should say Deployed. If it still says Deploy, select it. For a bulk deploy, wait for the completion message, which can also say that some images were skipped. - The wrong image or page was updated. Pages can contain several similar images. - The image may be decorative. OTTO hides decorative images, such as icons, arrows, and spacers, and does not add alt text to them. It also changes only standard img tags, so an image painted as a CSS background is not updated. - A cached copy is showing. Your browser, site cache, or CDN may still serve the previous page. - The page was changed again in your site after OTTO deployed, which can overwrite the update. 🛠️ Update and deploy the alt text again 1. Open OTTO, select Image alt text, and find the image. The list shows every page where that image appears. 2. Enter clear, specific alt text that describes the image. Keep it short and avoid stuffing keywords. 3. Select Save, then select Deploy for that image. When its status says Deployed, check the live page. You may need to refresh it. 4. If several images look alike, confirm you edited the correct one by matching the image preview or file name. 5. If the image still says Deploy, select Deploy again. Check its status before deploying it again. 🔍 Confirm the live page 1. Open the live page in a private or incognito window so you are not viewing an old cached copy. 2. Hard refresh the page. On most browsers, hold Ctrl and press F5, or hold Cmd and Shift and press R on Mac. 3. Right-click the image, choose Inspect, and look for the alt value on the image tag. That is the text currently published. 4. If your site uses a cache or CDN, clear that cache for the page, then check again. 5. Search results can lag behind the live page. Judge success by the page source, not by how soon Google shows the new text. 📊 If it still does not update - Check that the image is a real image element on the page, not a background image. - A later edit in your website builder or CMS can change the alt text stored on the page, but a deployed OTTO change still replaces it on the live page. If the image no longer matches, deploy the image again. - If a bulk deploy reports skipped images, review those images and deploy them again. A single image has no error status. If it does not say Deployed, select Deploy again. - Note the page URL, image file name, the alt text you entered, and the time you deployed. These details speed up a review. 💡 Good alt text habits Describe what is actually in the image, such as the product, person, or scene. Skip phrases like image of. Use empty alt text only for purely decorative images when your workflow supports that. After any successful fix, recheck one live image so you know future deploys are sticking. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 04, 2026

⚙️ OTTO Site Audit Shows In Progress

📊 What this article covers An OTTO site audit can look active while a crawl is running. The Site Audit list shows Crawling or Crawling now, with progress, while pages are being crawled. It shows Will recrawl soon only when a later crawl is waiting to start. OTTO reports the project as Crawling, Processing, Error, or Complete. Crawl Monitoring does not offer a restart control. Delete stays in the audit menu, but deleting or archiving is rejected while the audit is linked to an active OTTO project. 💡 Why the audit looks stuck An In Progress status does not always mean the crawl failed or froze. Support reviewed the site logs and found this sequence: - A manual reprocess had already started and completed successfully. - A later analysis had also completed successfully. - A regularly scheduled crawl had started afterward and was still running. A running status means the current crawl or its analysis is still underway. It is not caused by a scheduled crawl overlapping an earlier one. A working WordPress connection does not change that status. 🛠️ What you should do If a crawl is still running, let it finish. Recrawl remains visible, but another crawl cannot start until this one is done. Being unable to delete or archive the audit only means it is linked to an active OTTO project. 1. Open the Site Audit list and check whether the audit says Crawling or Crawling now. 2. Remember that a completed manual reprocess or analysis can be followed by a new scheduled crawl. 3. Leave the running crawl alone until it finishes. The status changes after that crawl and its post-processing are complete. Do not start another recrawl while the current crawl is still running. Delete and archive are also the wrong next step while the audit is linked to an active OTTO project. 💬 When to contact support If the crawl stays In Progress long after you expected a scheduled run to finish, or you are unsure whether a new crawl started after a successful analysis, contact support so the logs can be checked the same way. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 04, 2026

🔍 Confirm Your OTTO Installation Is Working

✅ What a working OTTO install looks like When OTTO is successfully installed and working, the site shows the short status Installed, or Installed (WP), Installed (Cloudflare), or Installed (CMS) depending on the method, and the success message says OTTO SEO is Engaged. The installation diagnostics for the checked page have passed, and the OTTO widget is enabled. The tag is confirmed on the project’s site. Search Atlas treats the main domain and www as the same site and does not require or report a separate detection on both. If those points are true for your project, the tag already in place is the correct one. You do not need a different OTTO tag or a new install. 🛠️ What you do not need to add A working manual installation does not need anything else: - No additional script - No Cloudflare token Keep the current manual installation. Adding another script or a Cloudflare token is not required when the tag is already present and detected on the project’s site. 🔍 If you are unsure whether detection succeeded Check that OTTO shows Engaged with an Installed status, that the installation diagnostics passed, and that the OTTO widget is enabled. When that is true, detection has already succeeded and the existing tag should stay as it is. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 04, 2026

🔌 Disconnecting Your Google Ads Account from OTTO

🔎 When You Need to Disconnect Google Ads You may want to disconnect your Google Ads account from OTTO if you no longer want OTTO to access it, or if you connected the wrong account. Disconnecting stops the link between the two platforms. 📋 Before You Start Have the following ready so the request can be handled quickly: - The name or email address of the Google Ads account you want disconnected - The email address you use to log in to OTTO - A short note on whether you want the account disconnected only, or whether you also need related information removed 💬 How to Request the Disconnection 1. Open the chat widget in the bottom-right corner of the platform. 2. Tell the support team that you need your Google Ads account disconnected from OTTO. 3. Include the account details listed above. 4. Wait for the support agent to confirm your request. The agent will check that they have the correct account before making any changes. 5. Once confirmed, the support team will disconnect the account for you and let you know in the chat when it is complete. ✅ What to Expect After Disconnection After you confirm Disconnect Account, the link between that Google login and OTTO is removed. Your Google Ads account, campaigns, and billing in Google are not affected. Back on Settings > Integrations, the Google Ads row no longer lists that account. If you still see the Google Ads account listed after the support team has confirmed the disconnection, reply in the same chat and include a screenshot. The team can check whether the change has fully applied. ⚠️ Things to Keep in Mind - Disconnecting stops OTTO from accessing the Google Ads account. Any features that depend on that connection will stop working for that account. - If you want to reconnect later, go to Settings > Integrations, open Google Ads, and choose Connect or Connect new Google account. - Anyone who can open Settings for the Search Atlas account can disconnect a connected Google login. You do not need to contact support. 🛠️ Troubleshooting If your request has been open for more than a day without a response, send a follow-up message in the same chat so the team can see it. Please do not open multiple chats for the same request, as this can slow down the process. 🤝 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 04, 2026

🛠️ Request One Extra OTTO Slot

🛠️ Why you cannot add the slot yourself OTTO site capacity is changed with a slider. On Billing, under OTTO quotas, the Sites row shows how many are used of the total. Modify opens a modal titled Top up: OTTO Sites, and the slider sets the new site total. Moving it up adds paid sites. Moving it down removes sites. There is no current product bug that stops this control from changing the count. 📊 What support checks first Support does not hold an OTTO site change because the number of sites on the account differs from the billing record. The billing entitlement is what the change uses, and a difference is recorded rather than used to block the request. There is no separate open slider-bug ticket that has to be resolved before one extra site can be added. ✅ How the extra slot is added You can add one OTTO site yourself. On Billing, open OTTO quotas, choose Modify on the Sites row, and in Top up: OTTO Sites move the slider up by one. One additional OTTO slot means one additional site you can install and activate OTTO on. Confirm the new recurring price. The site is billed as an OTTO Sites top-up. It is not added by asking chat to send a request to Billing. If a previous purchase has not appeared, say so in chat so support can check that purchase instead of starting a second one. - State that you need exactly one more OTTO slot. - Mention that you cannot add or remove slots because of the slider bug. - Include any open request you already sent so the team can check its status. 💬 What to expect The extra OTTO site is not a free slot granted after approval. It is added when you confirm the paid top-up, and the new recurring charge applies from that change. A difference between the site count shown on the account and the billing record does not by itself stop the change. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 04, 2026

🗑️ How to Completely Delete a Project and Home Summary

🔍 Understanding Project Deletion and Dashboard Summaries When removing a project from your account, deleting it from the main tool area may sometimes leave an overview summary or artifact card on your main home dashboard. To remove the project completely and ensure your dashboard metrics reflect the change, you need to remove the project from both the tool dashboard and your home page. ⚙️ Removing an OTTO Project To delete an active project from your automation dashboard, follow these steps: 1. Navigate to the OTTO SEO dashboard. 2. Locate the project you want to remove from your project list. 3. Click the three-dot menu next to the project name. 4. Select the option to delete or remove the project and confirm your choice. 🏠 Removing Leftover Project Summaries from the Home Page If your home page continues to display artifacts, overview summaries, or project cards after deleting the project from OTTO, you can clear them directly from your main dashboard: 1. Go to your Search Atlas Home page. 2. Locate the project summary section or artifact overview that still references the deleted project. 3. Find the management or removal option on the project summary card to delete it from the dashboard view. 4. Refresh the page to verify that the artifact count and project summaries have updated properly. 💬 Contact Support for Assistance If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 04, 2026

⚙️ OTTO Does Not Auto-Deploy After Smart Crawl

📌 What this article covers Customers on the Starter plan often ask whether OTTO can automatically deploy new fixes after each Smart Crawl, how Autopilot handles automatic deployments across categories, and how to get fixes live. This article explains how Smart Crawl and Autopilot work together and how to deploy your fixes. ❌ Auto-deploy after Smart Crawl is not available Smart Crawl alone does not automatically deploy new fixes; it only scans your site and drafts suggestions. However, Autopilot can automatically deploy supported fix types once enabled. This behavior is consistent across the $99 Starter plan and higher subscription tiers. Auto-deploy settings are located under OTTO Settings in the Automation tab. You can enable Autopilot to automatically deploy fixes for specific supported categories, while other categories remain manual and wait for approval. 🔄 What Smart Crawl does instead Smart Crawl recrawls and reprocesses the project on your configured schedule (7, 14, or 30 days). After processing completes, issues in categories with Autopilot auto-deploy enabled will publish automatically, while all other issues remain undeployed until you review and deploy them. - The crawl runs on your set schedule. - The project is recrawled and reprocessed. - Fixes in categories without Autopilot auto-deploy enabled are not deployed automatically. 🛠️ How to deploy fixes You only need to review and deploy issues for categories where Autopilot auto-deploy is turned off or unsupported. 1. After Smart Crawl finishes, go through the issues it found. 2. Deploy the fixes you want to apply. 3. Alternatively, you can use the Deploy All control to review and publish pending fixes across a category. Smart Crawl itself remains a scanning process across all plans, while automatic deployment is configured through the Autopilot fix-type toggles in OTTO Settings. 💬 Need more help If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 04, 2026

🔌 Fix WordPress Plugin Authentication Failure

🔌 Why authentication fails If the WordPress plugin will not authenticate, the website stays disconnected from OTTO. Uninstalling and reinstalling the plugin alone does not always fix it, because the same stored credentials and connection data can remain. Check the plugin version and update it if WordPress shows an update, clear the site caches, then run authentication again from the plugin. If it still fails, contact support. There is no plugin error to fix and no OTTO task for you to redeploy. ✅ Check the plugin version Confirm the WordPress plugin is current before you try authentication again. - In WordPress admin, review the installed plugin version. - If an update is available, update the plugin first. - A reinstall of the same version can leave the same connection problem in place. 🧹 Clear caches Cached site or plugin data can block a fresh authentication attempt. - Clear your website cache. - If you use a caching plugin or host-level cache, clear that as well. - Reload the site so the next connection attempt is not served from cache. 🚀 Redeploy the OTTO task and connect After the version check and cache clear, return to the WordPress plugin and run authentication again. There is no OTTO task to redeploy before you connect. 1. You do not redeploy an OTTO task. After checking the plugin version and clearing caches, run authentication again in the WordPress plugin. 2. Return to the WordPress plugin and run authentication again. 3. Confirm the website shows as connected and that no error appears. In the resolved case, connecting after these steps worked and no error was present. 💬 If it still will not authenticate If the site is still disconnected after you verify the plugin version, clear caches, and run authentication again, contact support from the WordPress plugin. Open Report Issue in the plugin menu, or use Contact Support. You can also email support@searchatlas.com. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 04, 2026

🛠️ OTTO Deploy Fixes Awaiting Release

📌 What this ticket is about Some open tickets ask why OTTO fixes have not appeared on the live site. Support reviewed the linked earlier conversations and confirmed the subject is OTTO deploy: selected fixes were not applied to the live site. OTTO deploy publishes approved fixes through the OTTO installation already connected to that site. It is not a platform release. ⏳ Current status There is no Awaiting release state for OTTO deploy. Fixes that are identified but not deployed stay pending until they are deployed in OTTO, or until Autopilot auto-deploy is turned on for that category. They are not waiting on a Search Atlas release, and opening another ticket does not deploy them. ✅ What happens next A recent update was already on the related conversation. Support merges the related conversations so the team has one thread, then asks the team for the latest update. For this case, the resolution is expected to be complete very soon, once the release that contains the deploy fixes goes out. - You do not need to resend the same request while the ticket remains Awaiting release. - Duplicate tickets about the same OTTO deploy delay are merged into the existing conversation. - The deploy is finished when those fixes are deployed in OTTO and the connected OTTO installation is serving them on the site. That does not depend on a Search Atlas release, and the live page can take a few minutes to show the change. 💬 If you still need an update If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 04, 2026

🛠️ Fix OTTO Wrong UUID Cloudflare Install

⚠️ What the wrong UUID error means A Wrong UUID message means the OTTO installation found on your site uses a UUID that does not match the UUID for this project, even if the value you checked looks correct. This can happen with any installation method, including Cloudflare. With a Cloudflare installation, the Worker places the UUID stored in its domain mapping onto the live page and removes other OTTO pixel scripts, so the page can show a different UUID than the one you expected. 🔍 Confirm the cause Check whether OTTO was installed through Cloudflare, using the DNS Setup tab of the installation guide. If it was, the Worker injects the UUID from its domain mapping into the live page. Wrong UUID means that injected UUID does not match this project. - The error appears even though the UUID you checked looks correct. - OTTO is installed through Cloudflare. - The code Cloudflare is serving does not match the correct installation for your project. 🛠️ Remove the Cloudflare installation If the Cloudflare installation is injecting the wrong UUID, open the installation guide's DNS Setup tab and uninstall OTTO from Cloudflare. That removes the Worker so it stops placing code on your site, but it also removes the Cloudflare installation. Reinstall it with the correct API token, or install OTTO another way, and then run Scan so the status can update. 1. Remove the Cloudflare access that is installing OTTO. 2. Confirm the correct installation code is now on the site. 3. Confirm OTTO is detected as correctly installed. 🚀 Run the scan Once the correct code is detected, run the scan so OTTO can process the site with the correct installation. 💬 Need more help If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 04, 2026

⚙️ Paid OTTO Installation Not Showing

📌 Why your paid OTTO installation may be missing If you paid for additional OTTO sites and the new capacity is still missing, the purchase is normally applied automatically as soon as payment completes. It is not waiting on an internal review. The exception is the uncapped 100-site tier, which must be approved by sales before you can buy it. If a normal purchase went through and the sites still are not available, the payment was recorded but the site quota was not applied, and support needs to fix that grant. ⏱️ How long the review usually takes There is no 48-business-hour review and weekends are not excluded from a waiting period. Site capacity should appear shortly after payment. Do not pay again. If it is still missing after you refresh, support should check that the checkout webhook applied the OTTO site quota. ✅ What to do while you wait - Do not count 48 business hours from when you reported the missing sites. The capacity is granted when the payment webhook is processed, not from the time of the support report, and weekend time is not excluded because there is no such window. - After support confirms the update, check the OTTO sites on your account. - If the sites still do not appear after the review window, ask support to follow up with the internal team. 🔍 After the OTTO sites are updated Once support confirms that the OTTO sites have been updated, review them when you have time. If something still looks incorrect, tell support about the remaining concern so it can be checked. 💬 How to reach support If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 04, 2026

🔍 Fix OTTO Title Tag Ampersand Display

💡 What you are seeing OTTO may suggest a title tag that shows the HTML code & instead of an ampersand, for example Client Events & Financial Workshops | Financial Consultants Group instead of Client Events & Financial Workshops | Financial Consultants Group. That code is stored in the suggestion text. It is not a bad title recommendation, and it does not mean your live page title is broken. The deployed title is escaped, and the browser displays a normal ampersand. ⚙️ Why it happens This is not a temporary loading state. Title suggestions appear after they are generated. Recrawling the site and reprocessing suggestions only changes the title if the new crawl or suggestion no longer contains &. A browser refresh does not decode an entity that is stored in the suggestion. 🛠️ How to fix the display 1. Clear your browser cache. 2. Refresh the page where the OTTO title tag suggestion is shown. 3. Check the title again after you refresh. If the suggestion was saved with &, the HTML code is still visible. A cache clear does not change the stored suggestion. 4. If the code is still visible, use Manual reprocess on the Recommendations header. It recrawls the site and reprocesses suggestions, once every 24 hours. Then refresh the page. It does not by itself change a stored & into an ampersand. Manual reprocess recrawls the site and reprocesses suggestions in one step. Refreshing afterward shows the saved suggestion. It does not clear a stored & from the Title Tags display. 🚀 Smart Crawl It is safe to enable Smart Crawl. The ampersand display issue does not block Smart Crawl and does not mean you should leave crawl features off. 📊 What to expect After suggestions finish loading, a refresh shows the saved title text. If that text contains &, the code remains visible. You do not need to rewrite a title only because of that. The live title still shows a normal ampersand. Edit the suggestion only if you want the suggestion text itself to show &. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 04, 2026

⚙️ OTTO Seat Upgrade Not Provisioning

🛠️ What this article covers If an OTTO site seat upgrade does not show up after you pay, or you were charged more than once for the same upgrade, start with the checks below. These are the same steps support uses before a specialist corrects the account. 💳 Upgrade from the Billing page Complete the seat upgrade from the Billing page. The same upgrade can also be started from the OTTO project area when you add a site, and starting it there does not by itself make provisioning more likely to fail. 1. Open the Billing page in the platform. 2. Start the OTTO site seat upgrade from that page and finish checkout. 3. Wait until the payment confirmation is complete before you check seats again. 🔄 Clear cache and confirm the seat count A stale browser session can keep showing the old seat count even after the upgrade succeeds. - Clear your browser cache, or open the platform in an incognito or private window and sign in again. - Return to the area where your OTTO site seats are listed. - Confirm the available seat count matches the number of seats you purchased. If the count now matches your purchase, the upgrade has provisioned and you do not need further changes. 💳 Duplicate charges If you were charged twice for the same upgrade, do not run the upgrade again. Note the charges so you can describe them in chat. Support can add non-recurring HDC credits to the account for the duplicate charge. Those credits do not expire. There is no account-wide setting you can change yourself to stop a repeat provisioning failure. If every upgrade requires the same fix, support can have the specialized team correct the account. 💬 When to contact support Contact support if, after you upgrade from the Billing page and recheck in a cleared cache or incognito window, the seat count is still wrong, or you see a duplicate charge. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat. In your message, include that you already upgraded from the Billing page, cleared cache or used incognito, and what seat count you see versus what you purchased. Mention any duplicate charge. The team can provision the seats and, when a duplicate charge is confirmed, add non-recurring HDC credits so they do not expire.

Last updated on Nov 04, 2026

🔄 When OTTO Keywords Schema Terms Reset

🔄 What this article covers This article explains what to do when OTTO keywords, schema, and terms on a site appear to have reset, and what was confirmed after support regenerated the affected recommendations. It also notes a separate Site Explorer question about Google Analytics and Google Search Console traffic. ⚙️ What support can verify Support cannot always confirm why OTTO keywords, schema, and terms reset. In the resolved case, the team did not have access to the deployment history needed to verify exactly what caused the reset. A reset on its own does not mean the rest of your OTTO work was removed. 🛠️ Regeneration and credits Missing Keywords are rebuilt from Google Search Console when it is connected. They are keywords the page ranks for but does not contain, and there is no page-analysis fallback for that category. NLP Terms are rebuilt from the page’s target keywords through Semantic Analysis and Knowledge Graph Optimization. Page-level schema suggestions are regenerated from Schema Markup, while NLP-managed WebPage and FAQ schemas are rebuilt with the NLP issue data rather than the schema AI control. AI-powered regeneration uses OTTO AI Generation points (AI Suggestions quota). Rebuilding these recommendations does not require support to waive that cost. Regenerating Missing Keywords, NLP Terms, or Schema Markup creates new recommendations. They are not deployed until you deploy them, and other OTTO categories are unaffected. 🚀 Deploy what is already generated Open each category that already has recommendations and deploy the available items. Missing Keywords and NLP Terms use Deploy or Deploy all on the page row, while Schema Markup uses its schema deploy controls. Those controls say Enable instead of Deploy until OTTO is engaged. Deploying does not require you to generate the category again, and generating again replaces the current recommendations. 📊 Site Explorer traffic that looks too low A site showing minimal traffic, or not picking up Google Analytics and Google Search Console as expected, is a separate issue from an OTTO settings reset. The completed resolution did not include a self-serve fix for analytics or Search Console data. Share the affected domain in chat so support can review that discrepancy with you. 💡 What to tell support - The site where OTTO keywords, schema, or terms reset - Which of those items changed or disappeared - Whether you need the affected recommendations regenerated and the credits handled - If you also see minimal Site Explorer traffic, the domain and that Google Analytics or Google Search Console does not look correct If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 04, 2026

🛠️ OTTO Page Type Stays Automatically Set

📌 What this article covers If the Schema Markup Tool shows the wrong page type for some URLs, this article explains how OTTO stores that type and why you cannot correct it from the dashboard. The guidance below matches what support confirmed after reviewing a live project. ⚙️ How OTTO assigns page types OTTO assigns the page type automatically. Once a type is stored for a URL, that stored type is what the platform continues to use. In the reviewed project, pages such as /pricing-payments were stored as Service Pages, even when that classification did not match what the customer expected. 🔄 Why a recrawl does not fix the type A recrawl does not change a page type that is already set. Running another crawl, or waiting for OTTO to look at the page again, will not replace the stored type with a different one. 📋 What you can and cannot change There is currently no way in the dashboard to change the page type. On Page-Level Schemas, the page type is display-only. You can see the type OTTO stored, but that field is not an editor, so you cannot select a different type there or elsewhere in the dashboard. - The page type is assigned by OTTO, not chosen manually. - An existing type stays in place after a recrawl. - Page-Level Schemas shows the type for reference only. 💡 What to do next Check the URL on Page-Level Schemas and note the page type shown. If it does not match the page, that mismatch cannot be corrected with a dashboard setting or a recrawl. Do not keep retrying the crawl expecting the type to update. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 04, 2026

⚙️ Fix OTTO Wrong UUID Status

🔍 What this status means OTTO shows Wrong UUID when the installation it found is configured with a UUID that does not match this project. The status is saved from the installation check, and a later check that finds the correct UUID replaces it. ✅ Confirm the UUID before you change anything Click Scan to open Installation Diagnostics, then click Run Diagnostics. For a signed-in project check this runs the full installation check, which saves the status. If the script UUID matches this project, the status changes away from Wrong UUID. If it stays on Wrong UUID, the script OTTO found is still using a different UUID, so reinstall it from the installation guide rather than treating the message as a stuck status. 🛠️ Clear the script and site cache This is the sequence that support used with the customer before diagnosing a stale status: 1. Remove the installation script from the site. 2. Purge the site cache. 3. Wait so the old cached copy can clear. 4. Add the same installation script back. Do not change the UUID if the scan already verified it. 5. Run the scan again and check whether the OTTO window still says WRONG UUID. 📊 If the status is still stuck Wrong UUID means the last installation check found a script UUID that does not match this project. Setting Crawl Frequency to Never only stops scheduled site recrawls; it does not freeze the UUID status. Recrawling the site or running a manual reprocess refreshes crawl data and suggestions, but the UUID status changes only when you run the installation check again and the script UUID matches. After you remove the script, purge the cache, wait, and re-add the script from the installation guide, click Scan and run the installation check again. When the script UUID matches this project, Wrong UUID is replaced. Crawl Frequency, including Never, only controls how often the site is recrawled and does not affect this status. 💬 Contact support If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 04, 2026

🛠️ Stop Runaway OTTO Footer Links

📌 What this issue is A very large number of hidden links on the homepage, such as about 14,000 footer links, is not expected OTTO behavior. Dynamic Indexing adds hidden links so Google recrawls pages that get no impressions, and lists created before the current cap can still be very long. You can remove the links yourself from the Dynamic Indexing table. The number of links served at once is capped on the server side (20 by default) and is not a setting you can change. ⏸️ Pause the deployed links Remove the injected links from the Dynamic Indexing table. There is no per-page limit to change afterwards. 1. In your OTTO project, open the Indexing group in the left sidebar and select Dynamic Indexing. 2. Turn on bulk selection and choose Select all on this page. Repeat this on each page of the table until every row is selected, since one click only covers the page you are viewing. 3. For the selected rows, click Roll back to undeploy the ones already deployed, or click Delete to remove the rows entirely. On a single row, click the green Deployed (or Enabled) pill to roll it back, or use the trash icon to delete it. 4. After the rows are rolled back or deleted, wait for the pixel cache to refresh and then recheck the homepage. The hidden links are anchors with the class otto-dynamic-indexing-module, so search the page source for that class to confirm they are gone. ⚙️ Check placement in Settings and Rules There is no placement setting to change. Dynamic Indexing links are added to the homepage footer automatically, which is why they appear on the homepage. 🔢 Limit links per page You cannot set a per-page maximum yourself. OTTO serves a limited number of these links at a time, 20 by default, and that limit is managed on the server side. If the table still grows far past that, contact support so the list can be cleaned up. ✅ Confirm the homepage is clean - Refresh the homepage after the status change. - Check that the large set of hidden footer links is no longer present. - Confirm the hidden links are gone by searching the homepage source for otto-dynamic-indexing-module after the pixel cache refreshes. There is no placement or per-page limit to verify. 💬 If the links remain If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 04, 2026

🔍 OTTO Deployments Not Showing on WordPress

❓ What this article covers Use this article when OTTO shows changes as Deployed, but those changes are not visible on your WordPress site. Deployed means the suggestion was sent to the OTTO installation for that site. It does not prove the live page is showing the change. Check the domain, the deployed suggestion types, and the affected page URLs. Then use Recrawl Site in Site Audit, and have the OTTO project reprocessed after that crawl finishes. Removing or changing an SEO plugin such as Yoast can also change the on-page elements OTTO reads, so the crawl needs to run again before the project is reprocessed. 🛠️ What was checked Before changing anything, gather the same details the agent used: - The website domain - The types of OTTO suggestions that were deployed - The specific page URLs where the changes should appear - Any recent SEO plugin change on WordPress, such as removing Yoast In the resolved case, Yoast had been removed that morning. That kind of change can affect the on-page elements OTTO expects to find, so deployments may not look correct until the site is crawled again. 🔄 How the issue was fixed The working fix has two steps. First, open the site in Site Audit and select Recrawl Site. After that crawl finishes, reprocess the OTTO project. Reprocessing rebuilds OTTO’s page data from the new crawl. It does not, by itself, confirm that the original elements were detected or that the deployments are live. - Reprocessing does not verify that OTTO detected the original on-page elements. After the new crawl, OTTO updates the current value it has stored for fields such as the title, meta description, headings, and Open Graph tags. That update is not a pass-or-fail detection check. - Reprocessing does not check that the deployments are live. Deployed means the suggestion was approved and sent to the OTTO installation. To confirm it, open the reported page URL and compare what the page shows with the deployed value. After the recrawl and reprocess, check the live page before changing the deployment. If the deployed value is already visible, do not deploy the same suggestion again. If it is still missing, redeploying the same suggestion will not fix a page that OTTO cannot change, such as a static page that bypasses WordPress. Leave the existing deployment in place until that check is done. ✅ What you can confirm After the recrawl and reprocess, open the same page URLs you reported and look for the deployed changes. If the page shows the deployed value, that change is rendering and you do not need to redeploy it. If it does not, the project still needs a follow-up. A page served outside the WordPress rendering that OTTO uses can stay unchanged even though OTTO shows the suggestion as Deployed. If a page still does not show a change, note the exact URL and the suggestion type. Do not assume every page failed if only some URLs were checked. 💬 When to contact support If your deployed OTTO changes are still missing, especially after an SEO plugin was removed or replaced, contact support with your domain, the deployed suggestion types, the affected page URLs, and what changed on the site. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 04, 2026

☁️ Fix OTTO Cloudflare token connection

☁️ What this article covers Some customers saw OTTO SEO reject a newly generated Cloudflare API token. Cloudflare’s own token instructions also did not match the screen they were looking at. Permission walkthroughs did not fix the connection. This article explains the confirmed cause and what to do now. 🛠️ What actually caused the failure Support confirmed that a migration of our hosting, from GitLab to Anvil self-hosted, affected the Cloudflare Worker that OTTO uses. The token itself was not the problem, and changing Cloudflare permissions did not resolve it. Engineering tracked the fix as an urgent platform issue: the Worker’s fetch behavior after that migration. Engineering corrected the Worker’s fetch behavior after the hosting migration (OTTO-3842). Once that fix is live in production, a normal Cloudflare API token is enough and no special setup is required to work around the old failure. Until you have confirmed the fix is released, retrying with a new token may still fail for the same reason. 🚀 What you should do 1. In your OTTO project, open the installation guide and select the DNS Setup tab. That is where you paste the Cloudflare API token. 2. Generate a Cloudflare API token as you normally would, paste it into the “Paste your API Token” field on the DNS Setup tab, and click “Validate & Connect.” 3. If OTTO accepts the token, no further action is required. Do not treat an older permission checklist as the fix for the failure that started right after the hosting migration. That break was in the Worker fetch, and permission changes did not fix it. If a token is still rejected after the fix is live, check the token itself: it must be active, created in the Cloudflare account that holds the domain, have no Client IP Filtering, and include the Workers, Workers KV, DNS, and Worker routes permissions OTTO asks for. 💡 If the token is still rejected If OTTO still will not take a valid token after you try again, the remaining issue needs a support agent. Include when you last tried, that Cloudflare’s screens do not match the usual token instructions, and that you already retried after the Worker fix. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 04, 2026

🛠️ Fix OTTO Wrong Location Meta Descriptions

📍 Why OTTO uses the wrong location OTTO can suggest meta descriptions that name a city or region you no longer use, even when Brand Vault already shows the correct location. Generating that suggestion uses one AI suggestion credit, whether or not the place name is right. Approving it does not use another credit. OTTO reads the location from the page summary first and then from the Knowledge Graph that Brand Vault syncs. If the primary location in Brand Vault, or the page summary, still carries the old city, new suggestions keep repeating that place name. There is no separate crawler-metadata location cache overriding Brand Vault. 🔎 Search your site for the old location Search the live site for the exact wrong location OTTO is writing. In the reported case, that phrase was Aurora and Aurora, ON. Use whatever city, region, or address OTTO is inserting for your project. Check these places first: - Footers - Policy pages - Old blog posts A short leftover mention of the old city in page content can still appear in the page summary and in new meta descriptions, but OTTO's configured location is the primary address synced from Brand Vault into the Knowledge Graph, not every leftover line on the site. ✏️ Remove the legacy reference Remove the outdated location from the page content, including templates, footers, and older articles, so the page summary stops repeating it. Also update the primary location in Brand Vault if it still shows the old city. Brand Vault is the source of truth for the business location, and new suggestions read the page summary first and then the Knowledge Graph. If the old city is not in the visible page content and new suggestions still use it, update the primary location in Brand Vault. Linking or re-verifying a Google Business Profile does not by itself replace that primary address. There is no separate location cache to clear. ✅ Confirm new suggestions After the primary location in Brand Vault is updated and the old city is gone from page content, regenerate the meta descriptions and read them before you deploy. They should use the Brand Vault location instead of the retired one. Regenerating spends AI suggestion credits. Approving a correct suggestion does not spend another credit. 💬 If the old location is still suggested If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat. Include the project name, the wrong location text, and where you already searched. Support can check the stored page summary and the primary location synced from Brand Vault into the Knowledge Graph. There is no separate crawler location cache to clear.

Last updated on Nov 04, 2026

📋 Review OTTO Activity and Shopify Scopes

📋 What OTTO can show about past changes OTTO does not have a customer-facing activity log that lists every action in an account over the last week or the past six weeks, and past actions cannot be replayed from a log inside OTTO. Deploy and undeploy events are stored as deployment history, including who deployed, when, the issue type, and the affected URLs. That history can be filtered by date, including the last week or six weeks, but it is used for reporting and the Work Summary export rather than shown as an activity log. You can still review the current state of your OTTO data and use reporting that is available today. 📊 Export current OTTO data and use Reports To keep a record of what is in the project now, use the Export menu on the OTTO project. Work Summary opens a Google Sheet of completed tasks and deployment history. OTTO Suggestions emails a Google Sheet of the current suggestions. Neither file is a CSV or Excel download, and neither is a history of edits over the last six weeks. 1. Export from the OTTO project’s Export menu. Work Summary opens a Google Sheet, and OTTO Suggestions sends a Google Sheet by email. There is no direct CSV or Excel download. 2. Save the file with a clear date in the name so you can compare later exports yourself. 3. OTTO does not have a Reports screen. When a project has one, the header shows a Performance Report card that opens Report Builder. The Export menu also has Work Summary, which opens a Google Sheet of completed OTTO tasks. You can export Work Summary again when you need another snapshot. Comparing those Google Sheets can show what changed between exports. OTTO also keeps deployment history of deploy and undeploy events, but that history is not shown as an activity log in the product. ⚙️ Shopify scopes for CMS Connector publishing For CMS Connector publishing, connect Shopify with an Admin API token or a custom app that has Admin API access. The connection needs the Admin API content scopes read_content and write_content. If access is denied, grant the required Admin API scopes and reconnect. The product does not offer a choice between Storefront scopes and an all-scopes option. For blog publishing, these Admin API scopes are required: - read_content - write_content If publishing fails, confirm the app or custom app is using Admin API access with those content scopes, then reconnect or update the scopes in Shopify and try CMS Connector publishing again. 💬 If you still need help If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 04, 2026

🛠️ Fix OTTO Wrong UUID Error

⚠️ What this error means A Wrong UUID message from the OTTO WordPress plugin means the site and the plugin are not using the same site identifier. The error can stay even after a normal refresh when an old plugin copy or cached data is still in use. ✅ Fix the error Work through these steps in order. They are the same checks support uses when this error persists. 1. Reinstall the plugin and confirm it is on the latest version before you continue. 2. Clear every cache that can store the old plugin response: your site cache, plugin cache, hosting or CDN cache, and your browser cache. 3. In WordPress, open Search Atlas, then Settings, then the Advanced tab (shown in the sidebar as Advanced Settings). Expand Cache Management. Use Clear All Cache Plugins, then under OTTO Transient Cache use Clear Entire Cache. 4. Turn OTTO back on with the Engaged switch on the connection status card. If it is already Engaged, switch it to Disengaged and then back to Engaged. There is no 30-second wait. 5. Do a hard refresh of the page and check whether the Wrong UUID error is gone. 🔁 If it still appears Clear the caches again from Search Atlas, Settings, Advanced, Cache Management, using Clear All Cache Plugins and OTTO Transient Cache, Clear Entire Cache. Then set the connection status switch to Disengaged and back to Engaged, and hard refresh the page. If the plugin is already current, a cached copy can keep the error showing, but if the UUID itself does not match, update the installation from the installation guide instead of only clearing cache. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 04, 2026

⚙️ OTTO Failed Generations Credit Restoration

🛠️ What this article covers Some OTTO AI generations can stay on Generating or fail, including Meta Description and OG Description generation. Quota reserved for an attempt that produces nothing, or that errors, is returned automatically. A failed attempt is kept on that row so you can still see it. This article explains what support has confirmed in these cases and what you can do before contacting the team. 🔍 Confirm the current status Pending-count problems and failed Meta Description or OG Description generation are tracked by the technical team. A ticket stays open until the reported case is fixed. A failed attempt can remain visible on that page after the failure. Before requesting a review, try the generation again on the affected page or site. If it now completes, the deployed fix has resolved the failure and no further troubleshooting is needed for that item. 📊 If a generation still fails If a new attempt still fails or remains pending after the fix, capture a short screen recording that shows the page, the generation you started, and the failed or pending result. Support has used recordings like this to confirm whether any remaining issue is separate from the fixes already deployed. - Show the site or page where generation failed. - Show the description or OG description attempt, if that is what failed. - Include the pending or failed result and the approximate time it occurred. 💡 Courtesy credit restoration Credits reserved for generations that fail or produce nothing are returned automatically. There is no self-serve control to restore them, and no fixed period such as the last two weeks. If a charge still looks wrong after the generation has finished, contact support with the details below. When you contact support, include the site name, which generations failed, the dates the credits were used, and your screen recording if the problem is still happening. The team will review the account. Credits for a failed generation are already returned automatically, so support only adjusts the account if a charge remains after that. 💬 Contact support If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 04, 2026

📍 Find Brand Vault and Knowledge Graph

🧭 What each item is These names refer to different parts of Search Atlas. They are not one menu, and the help knowledge base is not the same as the Knowledge Graph. - Brand Vault stores your brand facts: business name, logo, colors, voice, locations, products, and services. Other tools read this profile so content stays on brand. - Knowledge Graph is the structured brand record built from Brand Vault. It helps search engines and AI systems understand who you are, what you offer, and how your pages connect. It lives inside your project, not in the help center. - Knowledge base is this help library. It explains how to use the platform. It does not publish your brand data to search engines. - Trainings are lessons and walkthroughs for using Search Atlas. They teach the product. They do not replace Brand Vault or the Knowledge Graph. - Press releases are distribution content you create for announcements. They are a content tool, separate from brand storage. - RSS is a feed of published items, such as blog posts or releases. It is used to share or pull updates. It is not the Knowledge Graph. 🗄️ Where to open Brand Vault Open Brand Vault from the header Resources menu. It is not in the project's left-hand menu or in project settings. You can also open it from the Brand Vault card inside an OTTO project. Each Brand Vault is its own record, so a profile in one vault does not automatically appear in another. On the Business Information tab, fill in the business name, website, and description first, then What makes the business unique?, How should the brand be perceived?, and How does the business make money? Upload the logo on the Style Guide tab. Keep the business name and address consistent with your site and public listings. 🕸️ Where to open the Knowledge Graph Inside Brand Vault, open the Knowledge Graph tab. It is not a separate item in the left-hand menu. Review and correct the Knowledge Graph fields there, including authorship, social profiles, and top pages, then save. Changing Business Information does not automatically update the Knowledge Graph. Use the Knowledge Graph to check that your brand, locations, and offerings are represented clearly. Empty or conflicting fields usually mean Brand Vault still needs those details. 🎓 Where to find trainings Open Video Tutorials from the header Resources menu under Help, or search for it. Video Tutorials is hidden on white-label accounts. Pick the video for the tool you are using, then return to your project to apply the steps. Trainings do not change your site or your brand data. Completing a lesson only teaches the workflow. 📰 Where press releases and RSS live Press releases are under Authority Building in the left-hand menu, on the item labeled PR Distribution. Create the release for the project that owns the brand, then follow the on-screen steps to review it and publish it to a distribution channel. Publishing uses Hyperdrive Credits. Search Atlas does not put an RSS or feed link in the content or site area of a project, and publishing one item does not create a project RSS feed. ✅ Quick way to tell them apart - Need to store who the brand is? Use Brand Vault. - Need to review how that brand is structured for search and AI? Use the Knowledge Graph. - Need instructions for the product? Use the knowledge base or trainings. - Need to announce news? Use press releases. - Need a feed of published items? Use RSS. 🛠️ If a menu item is missing Confirm you are inside the correct project and that your user role can view that feature. Some items appear only on certain plans or after Brand Vault has a completed profile. Refresh the page, then check the left-hand menu again. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 04, 2026

🛠️ OTTO Changes and Google Ads Disapprovals

📌 What this article covers Google sometimes disapproves ads with a Compromised Site status when its systems see unexpected scripts, links, buttons, redirects, or content that looks hacked or cloaked. This article explains how to review OTTO deployments for the dates in question, how those changes are applied, whether AdsBot can see different content than visitors, and whether to freeze or roll back OTTO before you appeal. 📋 How to get the full change list Search Atlas stores deployment history separately for each project, but a public help article cannot list the changes on your projects, and the dashboard does not provide a dated history you can filter and export. Open each project separately. In each fix category, select Deployed and review the page URL, original content, and OTTO suggested fix for each live fix. Repeat this for both projects so nothing is missed. For each deployed fix, note the page URL, the fix category, the original content, and the OTTO suggested fix. Pay special attention to: - Links added, removed, or rewritten, including outbound and button destinations - Buttons or calls to action, including new labels and target URLs - Scripts, tags, or pixels inserted into the page or sitewide - Redirects, canonical tags, hidden text, or content shown only to some visitors If the in-product log does not show the detail you need for those dates, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat. Include both project names and the date range so the team can pull the same deployment record. ⚙️ Server-side or client-side OTTO does not use one method for every change. Each deployment is labeled by what it edits. Use that label rather than assuming every update is in the HTML source. - With the WordPress plugin, Cloudflare Worker, or CMS sync, OTTO changes are applied to the page before it is served. Visitors and AdsBot generally receive the same markup. The JavaScript installation instead applies changes in the browser. - With the JavaScript installation, OTTO adds or rewrites links, metadata, and content after the browser loads the page. A crawler that does not run that script the same way can see different content than a person. Use the installation method to judge how the changes are delivered, not words in the deployment record. The WordPress plugin, Cloudflare Worker, and CMS sync change the served page. The JavaScript installation changes it in the browser. Review any fix you cannot identify before you appeal. 🤖 What AdsBot can see Google Ads uses its own crawler, often called AdsBot, to check the landing page. It does not always execute JavaScript the same way Chrome does, and it can visit at a different time than your own test. That means client-side OTTO changes can be missing, partial, or different in the copy AdsBot stores. Compare three views of each affected landing page: 1. The live page in a normal browser, including buttons and link targets 2. The raw page source, before scripts run 3. Google’s recorded view, such as the ad destination preview or a fresh fetch after you pause new changes Look for third-party scripts you do not recognize, pop-ups, auto-downloads, cloaking, doorway pages, or links that do not match the visible button. A mismatch is a common reason a site is flagged even when the visible page looks fine to you. ⏸️ Freeze or roll back before you appeal Stop deploying new OTTO changes on both projects before you appeal. Turn off Smart Crawl so OTTO stops scanning and generating new suggestions. Also turn off Autopilot so it does not publish new fixes automatically. Leave the site stable so Google re-crawls one known version, and do not keep publishing fixes while the review is open. Do not roll back every OTTO change by default. Ordinary title, meta description, and on-page SEO edits rarely explain a Compromised Site label. In each category, open Deployed and click Deployed on only the individual fixes that add or change scripts, unexpected links, buttons to other domains, redirects, or injected content. Use Roll back all only when the whole category should be removed. Remove any code you cannot identify, then recrawl the landing page yourself. After the site is stable, appeal in Google Ads. State that you reviewed deployments on November 2–3, paused further OTTO changes, removed any unverified scripts or links, and that the current source matches what visitors see. Keep the freeze in place until the disapproval clears. 💬 If you still need the deployment record If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 04, 2026

🚀 How to Start OTTO Onboarding

💡 What this article covers This guide explains how to start OTTO onboarding in Search Atlas and how to get step-by-step help from our support team. Use it when you want a clear walkthrough before you turn recommendations into live site changes. 🛠️ What OTTO onboarding includes OTTO SEO is the Search Atlas automation that finds SEO opportunities and can apply changes you approve. It does not change your site until you approve a fix, or until you turn on Autopilot for specific fix types. Account onboarding is a separate signup flow, and the Get Started Guide is a separate checklist. A typical onboarding covers: - Confirming the correct website, project, and connected properties - Reviewing your main SEO goals, such as technical fixes, content, or local visibility - Checking that OTTO can access the pages it should update - Walking through how to review, approve, and monitor recommendations - Pointing out settings you should leave unchanged until you understand them 📋 Prepare before you ask for guidance Gather these details so the walkthrough can start right away: - The exact domain or project you want help with - Your role on the account and whether you can approve site changes - Access to your CMS, DNS, or Google properties if a connection is still missing - Your top priorities, such as fixing errors, improving key pages, or launching a new site - Any recent site launch, redesign, or migration that could affect recommendations - Questions you want answered, written in the order you want to cover them ⚙️ Start onboarding yourself Complete these steps in the platform before or during your chat: 1. Sign in to Search Atlas and open the project for the site you want to optimize. 2. In the main left navigation, open OTTO SEO. The product name can be renamed for white-label accounts. 3. If the site is not listed, choose Add OTTO Site. Enter the website, then continue through business information, where Google Search Console and Google Business connections are optional, and finish by installing OTTO. 4. When your first suggestions are ready, review them. Nothing is applied automatically. Approve the fixes you want, or turn on Autopilot for the specific fix types you want published on their own. 5. Approve only the items you understand. Leave unclear items pending until support explains them. 6. After changes are applied, check the affected pages and the OTTO activity or status views so you can see what was updated. Do not approve a large batch of changes until you know which page types they affect and whether your team must publish them in your CMS. 💬 What to send in the chat Open the chat widget in the bottom-right corner of the platform and send one message with the project name, your goal, and the step you are stuck on. A member of our support team will reply in the chat and guide you from that point. A useful first message looks like this: I need step-by-step OTTO onboarding for example.com. The project is already created. Please walk me through connections, review, and what I should approve first. You can also ask the specialist to cover: - Which recommendations are safe to approve first - How to pause or skip a change you do not want - How to confirm a change was installed - What to do if a connection or installation check fails ✅ After your walkthrough Keep a short record of what was approved, what was skipped, and any follow-up tasks for your developer or content team. Recheck key pages after updates, then return to OTTO to review new recommendations rather than approving everything at once. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 04, 2026

📍 How OTTO Handles Multiple Offices

🏢 Why two offices do not break OTTO OTTO optimizes the website you connect to Search Atlas. A law firm, or any business, with two physical offices on one site is a standard local setup. Those offices do not conflict with OTTO by themselves. What matters is clarity. Each office should have its own accurate details, and those details should match everywhere you publish them. OTTO can then work from clean pages instead of competing or duplicated signals. 📄 Set up one page per office Keep a single primary website and give each office a dedicated page. Do not publish two near-identical pages that only swap the city name. - Use a unique address, and a unique phone number when the office has one. - Add hours, a short description of that office, and the areas it serves. - Write a unique title and meta description for each location page. - Link both pages from your main menu, footer, or a locations hub so visitors and search engines can find them. - Keep firm-wide service pages separate from office pages, and point to the relevant office where it helps the reader. ✅ Keep location signals consistent Local visibility depends on the same facts appearing in the same way across your site and your business listings. - Match the business name, address, and phone number on the website and on each listing. - Do not list both offices on one page in a way that hides which address belongs to which office. - Avoid doorway pages that repeat the same copy for every city. - After you add or change a location page, update that location in Brand Vault, then let OTTO recrawl the site and regenerate suggestions. Already generated suggestions stay as they are until you regenerate them. - You can review each OTTO suggestion and skip any you do not want. If auto-deploy is turned on for a fix type, OTTO can apply new suggestions of that type without a separate review. Applying them changes the page's SEO fields. It does not merge or replace a specific office. 🚀 When you are ready to scale Two offices on one domain can stay on your current OTTO setup if the pages above are in place. Enterprise planning is for a larger footprint, such as many locations, brands, or sites that need a coordinated rollout. Search Atlas does not schedule Zoom calls, phone calls, or email threads from this article. Tell us your website, how many locations you have, and what you want to scale. A specialist can review that context and point you to the right plan. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 04, 2026

🛠️ Find the OTTO Custom Installation Prompt

💡 What the custom installation prompt is Search Atlas generates a ready-made AI install prompt for the OTTO pixel. You copy it and paste it into a coding assistant, such as Claude, Codex, Cursor, or ChatGPT, so the pixel can be added without a CMS plugin. The prompt is tied to the website you have open in Search Atlas. Always copy it from the project you want to track. 🔍 Where to find the prompt 1. Sign in to Search Atlas and open the correct website or project. 2. Open that site in Search Atlas, then open its Installation Guide. In the newer install flow the page heading is Install OTTO. In the classic guide it is Installation Guide. 3. From the site, open the Installation Guide. If the overview shows the pixel as Not Installed, use the Install link. 4. In the newer install flow, choose Let an AI assistant do it. In the classic Installation Guide, open Manual Installation and select Code Snippet. Do not use the WordPress plugin, Shopify theme steps, Google Tag Manager, or another platform method if you want the AI prompt. 5. When the prompt appears, select Copy prompt in the newer flow, or Copy AI Prompt in the classic guide. You can also select the full prompt and copy it. In the newer flow, the prompt appears only after you choose Let an AI assistant do it. In the classic guide, it appears on Manual Installation for Code Snippet, and also for Shopify. A WordPress, Google Tag Manager, or other plugin option does not show it. 🚀 Use the prompt in Lovable 1. Open the Lovable project for the same website. 2. Paste the full prompt into the chat or instruction box. Do not shorten it or remove the pixel details. 3. Ask Lovable to add the OTTO pixel using that prompt, then review the change before you publish. 4. Publish or deploy the site so the pixel is live on the public pages. 5. Return to Search Atlas and check the pixel status on the same project. Allow a short time after publishing before you recheck. ⚙️ If you cannot find the prompt - Wrong project: Switch to the site you are building. Each site has its own prompt. - Wrong install method: Open the Installation Guide again and choose Let an AI assistant do it, or in the classic guide open Manual Installation and select Code Snippet. - Pixel already connected: Open the Installation Guide for that project again. Choose Let an AI assistant do it, or in the classic guide open Manual Installation and select Code Snippet, then copy the prompt again. If the newer flow says you are set, use Show other ways in first. - Page did not load: Refresh Search Atlas, then reopen OTTO and the installation screen. - Limited access: If you cannot open this site's Installation Guide, ask the person who owns the Search Atlas project to give you access to that site. - Old copied text: Generate or copy the prompt again from the current project instead of reusing an older message. Copy the entire prompt in one piece. A partial prompt can leave the pixel out of the site or point it at the wrong project. 📊 After installation Confirm that the live site contains the OTTO pixel and that Search Atlas shows the installation as detected for that same project. If the status does not update, republish the Lovable site and check again before starting a second installation. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 05, 2026

🔓 Unfreeze Projects and Connect Analytics

🧊 What a frozen project means A Deep Frozen OTTO site keeps the site and its historical data, but pauses changes until you unfreeze it. While it is frozen, edits, deploys, playbooks, and crawls are unavailable. Google account connections are made at the account level and are not blocked by the freeze. If a screen says you do not have access, confirm you are signed into the right account and that your role can manage that site. 🚀 How to unfreeze a project Any signed-in user on the account that owns the OTTO site can unfreeze it. It is not limited to an account owner or a project manager. Public share links cannot unfreeze a site. 1. Sign in to Search Atlas and open the project that is frozen. 2. Open the OTTO site. On the frozen status banner, click unfreeze the site. The same Unfreeze action is also on the Cloudflare uninstall dialog when the site is Deep Frozen. OTTO SEO, All Sites, Deep Frozen only lists frozen sites and does not unfreeze them. 3. Click unfreeze the site. It unfreezes immediately, with no confirmation step, and shows The website has been successfully unfrozen. If the site was frozen longer than 14 days and its slot was released, unfreezing needs a free OTTO site slot. 4. Unfreeze finishes as soon as the success message appears and the frozen banner goes away. You do not need to wait before connecting a Google account. Connecting that account to this site’s Search Console property is a separate step in the site’s settings. If unfreeze the site does nothing, you are on a public share link or you are not signed into the account that owns the site. Sign in to that account and open the site from OTTO SEO. An account owner does not need to grant a separate management permission. 📊 Connect analytics integrations After the project is active, connect the analytics properties that belong to the same site. 1. Click your avatar in the top right, then Integrations. This page is for the whole account, not for one project, and it stays available while an OTTO site is Deep Frozen. 2. Choose the analytics service you want, such as Google Analytics or Google Search Console. 3. In Search & Analytics, click Connect on Google Search Console or Google Analytics. Sign in with the Google account that owns or manages that property. 4. Approve the requested permissions so Search Atlas can read reporting data. 5. Connecting Google Search Console or Google Analytics only authorizes that Google account. To attach Search Console to this site, open the OTTO site, go to Settings, then Connections, choose Connect Search Console or Change property, pick the GSC property and location, then click Update. In GSC Settings, choose the Search Console property for this site. A domain property covers the whole domain. A URL-prefix property covers only that address. If you pick a different property, reports show that property’s data, not this site’s. 🔐 When the screen does not give access A missing-access or permissions-revoked message means the signed-in Google account cannot access that property. Ask the property owner to grant access, or connect a Google account that already has it. Deep Freeze does not block the account connection. - Wrong Google account: Disconnect, then connect again with the account that has access to the property. - Insufficient access: in Google Search Console or Google Analytics, the signed-in user needs access to that property. Ask the property owner to add that user, then reconnect. - Permission not approved: When the consent screen appears, allow every requested permission. Denying access stops the connection. - Project still frozen: unfreeze the site from its frozen banner if you need to edit the site or attach its Search Console property. You do not need to unfreeze before connecting a Google account under Integrations. Refresh the page and start again if the banner is still showing. - Wrong property selected: open the OTTO site, go to Settings, then Connections, click Change property, choose the Search Console property for this site, and click Update. - Browser session: Sign out of other Google accounts or use a private window so the correct account is used. After fixing access, return to Integrations, connect again, and confirm the property name and status show as connected. ✅ Confirm data is syncing Open the project dashboard and check that analytics cards or reports load without an access error. New connections can take some time before recent data appears. If a report stays empty, verify the property has data for the selected date range and that the correct property is still selected. 💬 Get help in the platform If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 05, 2026

⚙️ Fix OTTO SEO Meta Suggestions in WordPress

💡 Why meta suggestions may be missing OTTO SEO can suggest title tags and meta descriptions for pages on a connected site. You review and deploy those suggestions in the Search Atlas OTTO project, not in WordPress. After a suggestion is deployed, the Search Atlas WordPress plugin applies it on the live page. Nothing is listed in WordPress until that deploy happens, and an empty WordPress screen is not a suggestions view waiting to fill in. A blank suggestions area usually means the connection, crawl, or display settings need a quick check. It does not mean your existing meta tags were removed. 🔍 Check the site connection Suggestions are tied to the property you connected in Search Atlas. Confirm you are viewing the same site in WordPress. 1. In Search Atlas, open the correct project and confirm the domain matches your WordPress site, including www and https. 2. In WordPress, open the Search Atlas menu. The header badge shows whether the site is Connected or Not Connected, and the admin bar shows Synced, Not Synced, or Warning. Warning means the site is connected but the OTTO UUID is missing, so deploys will not work until you reconnect. 3. If the badge says Not Connected or Not Synced, use the connect button in the Search Atlas plugin and sign in again. If it says Warning, the OTTO UUID is missing and deploys will not run until you reconnect. 4. If you manage more than one site, open Search Atlas and select the project whose domain matches this WordPress install before you look for suggestions. The plugin itself cannot be switched between projects. 📊 Confirm pages were analyzed OTTO SEO cannot suggest meta tags for pages it has not reviewed yet. New or recently changed pages may need a fresh analysis. - Open the OTTO project in Search Atlas and check the Title Tags and Meta Description sections for this site. A page gets a suggestion only after OTTO has generated one there. WordPress does not show a crawl or analysis progress state for these suggestions. - Look for the pages where you expected title or meta description suggestions. - If a page is missing, publish it in WordPress and make sure it is publicly reachable, then wait for OTTO to generate a suggestion in the Search Atlas project. Setting the page to noindex does not by itself stop OTTO from suggesting a title and meta description. - After you deploy the suggestion from the OTTO project in Search Atlas, reload the live WordPress page. The plugin applies the deployed title and meta description when the page renders. There is no separate OTTO view to refresh inside wp-admin. 🛠️ Turn on suggestions in WordPress The WordPress plugin does not list OTTO recommendations. It only applies suggestions you have already deployed from the OTTO project in Search Atlas. If a page has no deployed suggestion, the live page simply keeps its current title and meta description. 1. Update the Search Atlas WordPress plugin to the latest version, then reload the dashboard. 2. There is no meta titles, meta descriptions, or automatic suggestions toggle in WordPress. Deploy the suggestion from the OTTO project in Search Atlas. On the individual post or page, the Search Atlas SEO sidebar shows the current SEO Title and Meta Description, and a value you type there overrides the deployed OTTO suggestion. 3. Suggestions are filtered in the OTTO project in Search Atlas, not in WordPress. If you do not see a page there, clear the URL or status filter in that project. WordPress has no list of applied or dismissed suggestions to filter. 4. Confirm your WordPress user can open the Search Atlas menu. Administrators always can. Other roles can only if an administrator added them under Plugin Access Roles in Settings. A user without access will not see the menu at all. 5. Pause other SEO plugins that rewrite titles and descriptions while you test. Conflicting plugins can hide or overwrite the suggestion panel. 6. Deploy the suggestion from the OTTO project in Search Atlas, then reload the live page. If the old title or description is still there, clear the site or page cache. Nothing loads into a suggestions panel inside WordPress. 🚀 Apply a suggestion when it appears In the OTTO project in Search Atlas, review the suggested title and meta description, then deploy only the items you want. Check the live page source to confirm the new tags. A value saved in the Search Atlas SEO sidebar on the post overrides the deployed suggestion. Dismissing a suggestion in the OTTO project keeps it from coming back until OTTO generates a new recommendation for that page. Automatic display does not always mean automatic publishing. Some accounts show suggestions for review first. Applying them is a separate step inside OTTO SEO or the WordPress panel. ✅ If suggestions still do not show Recheck the domain match, plugin connection, completed analysis, and that meta suggestions are enabled. Also confirm the page is public and indexable. Private, draft, password-protected, or noindex pages are often skipped. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 05, 2026

⚙️ Stop Yoast and Search Atlas Schema Conflicts

⚠️ Why the conflict happens Yoast and Search Atlas can both add schema, titles, and meta descriptions to the same page. OTTO SEO deploys schema from Schema Markup, and title tags and meta descriptions from their own issue tables. The WordPress plugin can also publish its own JSON-LD. When both tools publish structured data, search engines may see duplicate or conflicting markup. Choose one owner for each on-page element so only one version is live. 🧭 Choose what each tool owns A clear split prevents the tools from overwriting each other: - Yoast: schema, SEO titles, and meta descriptions. - Use Site Audit, Keyword Research, and Rank Tracker for work that does not rewrite schema, title tags, or meta descriptions. Publishing from Content Genius does write the article's title and meta description. If you prefer Search Atlas to manage titles or meta descriptions, turn those features off in Yoast instead. Do not leave the same field active in both tools. 🛠️ Stop Search Atlas from pushing schema 1. Open the website project in Search Atlas. 2. Open the site's OTTO project and select Schema Markup. 3. In Schema Markup, review Domain-Level Schema and Page-Level Schemas, then deploy only the schema you want Search Atlas to publish. 4. Turn that option off and save. 5. If Yoast should own title tags and meta descriptions, do not deploy those OTTO fixes. If Sync to CMS is on, turn it off so deployed title tags, meta descriptions, and schema are not written into Yoast. 6. Deploy or undeploy the OTTO fix. Then clear your site and CDN cache yourself if you use one. Leave schema enabled in Yoast. Review Yoast schema settings for the content types you use so the markup you want is still generated. ✅ Confirm only one schema source 1. Open a live page and view its page source. 2. Search for application/ld+json. 3. Confirm the structured data comes from Yoast only. 4. Test the URL in Google Rich Results Test and fix any errors reported for your Yoast markup. Check a few templates, such as a post, a page, and a product page. After a plugin, theme, or cache update, check the source again. 💡 If markup still looks duplicated - Disable schema features in your theme or in other SEO plugins. - Confirm OTTO is not still injecting schema through an older script or cached page. - Clear every cache layer and recheck the page source. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 05, 2026

🔄 Update an OTTO Project Domain

🔄 When you need a new domain on the same project When your site address changes, OTTO cannot move the existing project onto the new address. The project's domain comes from the site audit it was created from, and an audit is tied to one address, so the new address needs its own site audit and its own OTTO project. Do not start a new OTTO project if you need that continuity. A new project is a separate record. It receives a new UUID and starts without the crawl history from the project you already have. 📌 What stays and what changes There is no domain update that keeps the existing project in place. A new address means a new OTTO project, and the items below belong to whichever project they were created with. - The original OTTO project stays in your account only while it keeps its original address. The new address becomes a separate project. - A project's identifier never changes, and it cannot be moved to a new domain. The project created for the new address gets a new identifier. - Past crawls stay stored on the project and address they were run for. They are not moved to the project you create for the new address. New crawls keep using the project's original address. Page URLs inside past crawls are not rewritten. OTTO only corrects its own record when the same domain switches between http and https or between www and non-www. 🚫 What not to do - Do not create a second OTTO project for the new domain if you need the old UUID and crawl history. - Do not delete or archive the current project if you still need its crawl history. Removing it and creating the project again for the new address starts a new project without that history. - You cannot submit a new domain for an existing OTTO project, even as a full https:// address. - Do not assume a domain edit inside another Search Atlas tool updates this OTTO project. Confirm the change on the OTTO project itself. 💬 How to request the domain update Keeping the same project, UUID, and crawl history while changing the domain is not possible. Support cannot update the existing record onto a new domain either. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat. There is no domain-change request to send. The new address needs its own OTTO project. 1. The project's name is not used to change its domain. 2. The current domain stays on the existing project. It cannot be replaced by request. 3. Entering the new address, such as https://www.portaprosoftware.com, creates a new site audit and a new OTTO project. It does not update the existing one. 4. Asking to keep the existing project, its UUID, and its crawl history cannot move the project to a new domain. The new domain gets a new project. 5. Adding the new domain always creates a new OTTO project. You cannot add it to the existing one. ✅ After support updates the domain - Open the original OTTO project and its address will be unchanged. The new address appears on the separate project created for it. - Confirm you are still in the original project, not a newly created one. - Run a new crawl when you are ready so OTTO collects current pages from the new domain. - Review key pages after that crawl. A domain move can change URLs, redirects, and which pages are available to crawl. - Keep the old project in place until you have confirmed the new domain and a fresh crawl look correct. 🛠️ If something still looks wrong Contact support again if the domain did not change, a second project was created, or crawl history no longer appears on the original project. Include the project name, the old domain, the new domain, and what you see in OTTO. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 05, 2026

🔗 Fix Internal Links Across Vaults

🔗 What this issue looks like Internal linking adds links from one article to other pages in the same brand vault. When it produces nothing, that article gets no new links, or a link is selected but cannot be placed in the article text. Each vault is handled separately. The step that does this is an editor action called inserting internal links; it is not a button or an action you apply across vaults. A problem in more than one vault usually means a shared setting, an unfinished crawl, or missing target pages, not a single page error. ⚙️ Check each affected vault Work through the vaults one at a time so you can see which ones still fail. 1. Open the brand vault for the site you are editing. A vault belongs to one site address and can be linked to the matching OTTO project, but you work in the vault itself. 2. The vault can supply link destinations from any one of these: a link you add under Content, a top page from Google Search Console, or a page published to WordPress or Website Studio. A crawled page is used only when none of those sources has a usable page. 3. Confirm the target page is available through one of the vault’s link sources. A top page already marked broken is skipped, and every selected address is checked live and must respond successfully. A crawled page must be an active HTML page that returned a successful response and has enough text. 4. Check that each address is valid and opens successfully. Pages found automatically should belong to the vault’s site. A link you add by hand is used as you entered it, so an address on another site is not rejected. 5. There is no separate exclusion list for internal links. A link is skipped when its address is empty or broken, its live check fails, or the article text contains no suitable phrase for it. Each article also has a maximum number of internal links. 6. You do not need to run a crawl first. If the vault has no added links, no top pages, and no published pages, the editor can use pages from a completed site crawl automatically. If a crawl is still running, it simply is not used yet. 🛠️ Run internal linking again Ask the editor to insert internal links in one article. The same request cannot be applied to the whole vault; repeat it for each article you want to update. - Start small. Test one source page that should link to a known related page. - The inserted link is written into the article immediately. Check that it appears in the article and points to the right address. This is separate from Save in the vault’s Content settings, which only stores the vault’s link list. - Repeat in a second vault. If it works in one vault and fails in another, compare crawl status, page count, and exclusions. - Inserting internal links finishes as part of the editing request, although the check can take up to about a minute. You do not have to wait for a background run. Repeating the request does not add the same address twice. If every vault fails in the same way after a completed crawl and valid target pages, the feature may need a support review. You do not need to keep rerunning it. 📊 Details that speed up a fix Before you contact support, note the following for each affected vault: - Vault or brand name - Source page URL and one expected target URL - Whether the crawl has finished - The approximate time the article edit failed while inserting internal links. - Whether the failure happens in every vault or only some brands - A short description of what you see, such as no links added or links not saved 💡 How to contact support If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat. Include the vault details from the list above in your first message. That lets the team check the insert internal links action across the affected brand vaults without another round of questions.

Last updated on Nov 05, 2026

🔄 Roll Back and Reinstate Deployments

⚠️ When to roll back deployments Roll back Search Atlas deployments when both tools are changing the same pages. Duplicate titles, meta descriptions, canonicals, or schema can remain until each deployed change is rolled back. Use the rollback controls in the affected OTTO SEO categories, then set the project to Disengaged so Search Atlas stops applying its changes. You can deploy the same changes again later. If the WordPress plugin writes changes into the CMS, also turn off the relevant sync settings. Turning sync off does not revert changes already written. 📋 Before you remove anything Take a few minutes to record the current setup so reinstating is straightforward. - Note which site or project is affected and which pages were deployed. - Confirm Yoast is the plugin you want to keep live during the pause. - List caches you use, including your host, CDN, and any caching plugin. - Avoid editing Yoast and deploying new Search Atlas changes at the same time. Nothing new should be published until the rollback is finished and you have checked the live pages. 🛠️ Roll back live deployments 1. Open the affected project in Search Atlas and go to OTTO SEO. 2. Set the project from Engaged to Disengaged before rolling changes back. This stops OTTO from applying further changes, but changes already deployed remain until you roll them back. 3. Roll back the live changes in OTTO SEO. Use Roll back all for a category, or select Deployed on an individual live change to roll that change back. Repeat this for every category that still has live changes. 4. On WordPress, deactivate the Search Atlas plugin if the installation is still connected. Deactivating or removing that installation stops OTTO from writing tags on the page. 5. Leave Yoast active. Do not deactivate Yoast as part of this rollback. 6. Clear your site cache, CDN cache, and any SEO or page-cache plugin cache. Pausing alone is not enough. Changes that were already deployed stay on the site until they are removed and caches are cleared. ✅ Confirm nothing stays live Check a few important URLs after the cache clear, including the homepage and one or two inner pages. - View the page source and confirm titles, meta descriptions, and canonicals come from Yoast only. - Confirm you do not see a second set of SEO tags or schema from Search Atlas. - Recheck in a private browser window so an old cached copy does not mislead you. - If duplicates remain, clear caches again and confirm the Search Atlas installation is still deactivated. Keep deployments paused until Yoast is the only plugin controlling those fields and the live source looks clean. 🚀 Reinstate deployments afterward Reinstate only after the Yoast conflict is fixed. Decide which tool owns titles, descriptions, canonicals, and schema, and turn off the overlapping Yoast output before Search Atlas publishes again. 1. Resolve the Yoast settings so it no longer outputs the same fields you want Search Atlas to deploy. 2. In Search Atlas, reconnect the site or reactivate the WordPress plugin if you deactivated it. 3. Return to OTTO SEO and turn deployments back on for that project. 4. Review the queued changes, then redeploy them. Reinstating does not happen by itself if the earlier rollout was fully removed. 5. Clear caches again and recheck the same URLs. You should see one clean set of SEO output, not two. Do not leave both tools publishing the same fields. If duplicates return, pause deployments immediately and repeat the rollback until the overlap is fixed. 💬 If you need further assistance If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 05, 2026

🔄 Roll Back OTTO Deployments Safely

⚠️ Why OTTO and Yoast can conflict OTTO can update titles, meta descriptions, canonical tags, and schema, which may overlap with Yoast’s output. Disengaging OTTO temporarily stops its script-delivered changes from appearing while preserving saved fixes. Roll back approved fixes if you also want their deployment approvals withdrawn. Changes already written directly into your CMS need separate rollback verification. Check both the page source and rendered page before relying on Yoast alone. 🛑 Pause OTTO so nothing new goes live 1. Open the website project in Search Atlas and go to OTTO. 2. Turn off automatic deployment for the relevant fix types in OTTO settings. To stop script-delivered fixes from appearing on this site, turn off the Engaged switch and confirm Disengage OTTO. Disengaging also pauses new CMS syncing, but does not remove changes already written into the CMS. 3. Confirm that the site’s OTTO switch shows Disengaged. Installation status is separate: the installation can still show Installed while OTTO is disengaged. 4. Do not approve or deploy any pending recommendations while you are rolling back. Pausing stops future publishes. It does not always remove changes that are already on the site. Complete the removal steps below as well. 🧹 Remove deployments that are already live 1. In OTTO, open the list of deployed changes for the project. 2. Select the deployed fixes you want to withdraw in each relevant issue category. For a full rollback, cover every category containing deployed fixes; do not assume selecting all rows in one view includes the entire project. 3. Use the rollback control for the selected fixes, or Roll back all for the current category, and confirm when prompted. Wait for completion, verify that the fixes are no longer marked deployed, and check the live page. If CMS syncing is enabled, verify its rollback outcome separately. 4. OTTO can run through the WordPress plugin or an installed site script. Disabling that delivery mechanism stops script-delivered fixes from being applied on subsequent page loads, but does not necessarily undo CMS-written changes. If changes were saved into the CMS, keep the required connection available until rollback is verified, then deactivate the installation if desired. 5. Clear any cache in WordPress, your host, and your CDN, then hard-refresh a few key pages. 6. View the page source and confirm OTTO titles, descriptions, canonicals, and schema are gone. Yoast should be the only SEO output left. If OTTO-related tags remain after rollback, verify the specific fixes and categories rolled back, clear applicable page and CDN caches, and inspect both page source and rendered HTML. Check whether the remaining output comes from Yoast, another plugin, or changes previously written into the CMS. A connected OTTO installation alone does not mean rolled-back fixes should remain active. 🔁 Reinstate deployments later 1. Decide which tool owns each SEO field. Use either OTTO or Yoast for titles, descriptions, canonicals, and schema. Do not let both write the same field. 2. In Yoast, turn off the outputs you want OTTO to manage, or leave OTTO paused if Yoast will remain the only source. 3. Reconnect the OTTO installation if you deactivated the plugin or script. 4. Before re-engaging OTTO, review the saved fixes and roll back any approvals you do not want restored. Restore the installation if necessary, turn Engaged back on, and deploy only the additional recommendations you want. 5. Clear cache and check the live source again so only one set of tags is present. Saved recommendations remain available without rebuilding the project. Fixes explicitly rolled back must be deployed again to restore their approval. Fixes only hidden by disengaging OTTO retain their approvals and can return when you re-engage, without another individual approval. **Code references:** - Engagement labels and restoration behavior: customer-frontend/src/modules/otto/shared/connection-status/ConnectionStatusCard.tsx:200–223. - Disengagement and CMS persistence warning: customer-frontend/src/shared/otto-widgets/disengage-confirm-modal.tsx:47–49. - Category-scoped rollback: customer-frontend/src/modules/otto/v3/overview/body/topBar/components/DeployControls.tsx:64–78. - Deployed/not-deployed filtering: customer-frontend/src/modules/otto/shared/features/issue-renderers/page-title/utils/customHooks/index.tsx:335–337. - Canonical fix support: content-assistant/app/ca/models/otto\_url.py:232–234,1139–1141. ✅ Prevent the same conflict - Keep one owner for each SEO element: OTTO or Yoast, not both. - Pause OTTO before changing Yoast settings or switching SEO plugins. - After every deploy or rollback, check the live HTML, not only the WordPress editor. - Clear site and CDN cache before you judge whether a change is live. - Roll back all deployments if you need a guaranteed clean state, then restore only reviewed items. 💬 If rollback status is unclear If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 05, 2026

🏢 Set Up OTTO for Multiple Locations

📍 What multi-location OTTO setup means Set up OTTO once for each website you want it to manage. One Search Atlas account can hold many projects, but only one project per website. Locations that use different websites should each have their own project so their pages, business details, and recommendations stay separate. Locations that share one website belong in that website’s single project. ✅ Before you start - List every location, including its website or location page URL. - Confirm the business name, address, phone number, and service area for each location. - Decide who on your team can edit each project. - Use one Search Atlas account so all locations stay together. 🛠️ Set up each location 1. Create a separate project for each website. If a location already has a project for that domain, open the existing project instead of creating another one. 2. Enter that location’s website domain, then choose the market location, language, and goal. Later, in the site’s Knowledge Graph, add that location’s business name, address, and phone number, and do not reuse another location’s details. 3. Install the OTTO pixel for the website that belongs to that project. The install is for the site, not for individually selected pages. 4. If locations share one domain, keep them in that website’s one project. Do not create a separate project for each location page. Use the Knowledge Graph to record each location’s business details. 5. After you add a website, open that project and review its recommendations. Repeat the setup for each additional website. 6. Open each project and check the OTTO status on the overview. It should show Installed for that website, or Not Installed or Not Working if the pixel is missing or failing. 🔍 Check that setup is correct - The project is identified by its website. In the project picker it appears under that domain, which is the name most projects keep. - Confirm the project’s domain is the website you intended to add. Opening it takes you to that site, not to a separately chosen location page. - Open the project’s Knowledge Graph and confirm the business name, address, and phone number match the live website. - OTTO recommendations refer to that location, not a sister site. - Give each website its own project. Locations on the same website stay in that one shared project. If two locations share a website, keep both in that site’s one project and record each location in its Knowledge Graph. If the second location has a different website, create a new project for that domain and install its own OTTO pixel. 🚀 Enterprise and larger rollouts Multi-location brands and agencies that need a larger plan can choose Contact Sales from OTTO billing, which opens the enterprise quote form. You can also use the platform’s live chat to reach support. In your request, include how many locations or sites you manage and whether you want help confirming setup. Include this in your chat message: - Use Contact Sales or live chat from your signed-in account. Give your company name, the account email if asked, and the number of locations or sites you manage. - The number of locations or sites. - Which projects are already created. - What you want to confirm, such as install status or project structure. A support teammate will reply in the chat and route an enterprise request to the right team. You do not need a Zoom call to confirm a standard setup. The checks above are enough for most locations. 💡 Common mistakes - Installing the same OTTO snippet across unrelated domains. - Using one project for many cities with different addresses. - Copying business details from the first location into every project. - Expecting a phone call or email reply instead of using in-platform chat. 💬 Get help in the platform If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 05, 2026

🛠️ Stop OTTO Crawling Noindex URLs

🚫 Why noindex URLs appear in OTTO OTTO can discover more URLs than the pages you want optimized. A crawl may follow internal links, read your sitemap, or reuse URLs from an earlier scan. Pages marked noindex can still be found even though you do not want search engines to index them or OTTO to change them. Deleting or ignoring a recommendation removes that task, but it does not stop OTTO from finding the same URL again. Exclude the URL, then run a new crawl, so it is not rediscovered. 🎯 Limit OTTO to your intended pages Set the exclusion rules before you recrawl. Use them to keep only the URLs you want optimized, such as your intended pages. 1. Open the OTTO project in Search Atlas, then open Settings and go to Crawl Parameters. 2. Add an Exclude rule for paths you do not want optimized, such as noindex, thank-you, filter, tag, and other utility URLs. Use an Include rule only when you need an exception to an exclusion. 3. Add or confirm the exact URLs you provided so the allowed set matches your intended pages. 4. Exclude the unwanted URLs if the project has an exclude or ignore option. Excluding a URL is stronger than only deleting its recommendation. 5. Check that important pages are still indexable. A page with a noindex tag can still be crawled and can still receive OTTO recommendations, so exclude it if you do not want it optimized. Keep the allowed list tight. If OTTO can crawl the whole site again, noindex URLs may return in the next task list. 🧹 Clear old technical recommendations Remove recommendations created from the wider crawl at any time. Save the exclusion rules before the next crawl so those URLs are not found again. - Open the OTTO project and select the relevant issue type in the task list. - Use Search by Page URL, or Filter by URL, to find the recommendations for pages outside your intended set, then select those rows. - Delete or ignore the selected recommendations. Ignore is the stronger task action because that issue type is not rebuilt for the page on the next crawl, but neither action changes which URLs the next crawl can discover. - Do not approve or deploy changes for excluded or noindex pages. Clearing the list removes old work items. It does not by itself change what the next crawl is allowed to discover. Always update the included and excluded URLs first. 🔄 Rescan using the corrected URL set 1. Save the included and excluded URL settings. 2. After saving the exclusion rules, open the project’s Site Audit and start Recrawl, or Recrawl Site, and wait for it to finish. 3. Wait until the scan finishes before reviewing recommendations. A scan still in progress can show a mix of old and new results. 4. Open the new task list and check that recommendations refer only to your intended pages. 5. If any noindex URL remains, exclude it and run one more scan rather than editing that page through OTTO. The new scan should rebuild recommendations from the pages still in scope. Tasks for removed URLs should not return when those URLs stay excluded. ✅ Confirm the result - Compare the recommended URLs with your intended page list. - Search the task list for a few known noindex URLs. They should not have open optimization tasks. - Check that canonical, indexable pages you want to improve still have their recommendations. - Approve only the tasks that belong to the final URL set. If the same unwanted URLs come back, check for a sitemap entry, an internal link, or a saved include rule that adds them on every crawl. Remove that source, keep the URL excluded, and rescan. 💬 When to contact support If you cannot clear the task list, the scan still includes noindex URLs after they are excluded, or you need help limiting OTTO to a specific URL set, contact support from inside the platform. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 05, 2026

💳 Review Disputed OTTO Project Charges

💳 Why an OTTO charge may look unexpected An OTTO site charge is a recurring site-capacity top-up for licensed OTTO sites beyond what your plan includes. It is not a separate fee for creating, activating, or renewing one project. $69.00 is the monthly price per site when your account has 4 to 9 licensed sites. A smaller amount can be a prorated charge for capacity added partway through a billing period, but $1.00 is not a standard companion project charge. The invoice identifies the OTTO Sites quota and its amount. It does not name the individual project that used a site slot. A charge can be disputed when the project was not meant to be activated, was created by mistake, or does not match the work you approved. This article explains how to read the invoice and request a billing review. A refund is not automatic. Our team checks the invoice, project status, and account activity before deciding. 📄 Where to find the detailed invoice Use the billing area in your Search Atlas account to review the exact breakdown: 1. Sign in to the account that owns the OTTO project. 2. Open Billing from your account menu. On the Billing page, use the Invoices tab. Plans & Top-ups and Services are separate tabs on the same page. 3. Find the invoice by its ID or by the created or paid date in the Invoices table. The row shows the invoice type, details, status, and total amount. 4. Read the invoice row's details, amount, and dates. Download the invoice for the stored breakdown. That breakdown names the quota, such as OTTO Sites, rather than a specific project. 5. Download or save the invoice if you want a copy for your records. Download the invoice for the detailed breakdown. Use it instead of the card statement, which can group or shorten the charge description. Match the OTTO Sites line and any prorated amount to the quota description. The invoice does not include a project name. 🔍 How to confirm the charge before you dispute it Check these points before requesting a reimbursement: - Date: Compare the invoice date with the date on your card or bank statement. - Amount: Confirm whether the two amounts are separate lines on one invoice or two separate charges. - Open OTTO SEO and review your sites. A site that is still being set up shows the time it was started. A finished site does not show a creation or activation date that you can match to the charge. - Note whether the site is on the Active tab or the Frozen tab. A site that is still being installed shows Continue installation. Deleted sites are removed from the list. There is no paused, canceled, or in-setup status. - Account user: Check whether another user on the account started the project. If the invoice matches an OTTO Sites top-up that your team bought or that renewed, the charge is expected. Creating a site uses one of those licensed slots, but it is not itself the billed event. If you cannot find a matching top-up, or the capacity was not supposed to be billed, continue with a refund review. 🛠️ What to send with your refund request A complete request helps the team review the charge without extra back-and-forth. Include: - The invoice date and each disputed amount, such as $69.00 and $1.00. - The last four digits of the card or the payment method shown on the invoice. - The OTTO project name, or a note that you cannot find a matching project. - A short explanation of why the charge was not expected. - A screenshot of the invoice line items and, if useful, the card statement. Do not send full card numbers, passwords, or security codes in the chat. ✅ What to expect from the review Our support team will compare your invoice with the OTTO project record. If the charge was applied in error, the team can explain the correction and any reimbursement that applies. If the charge matches an activated project, the team will show which line items account for it. Refund timing depends on the review outcome and your payment provider. Search Atlas cannot change how quickly a bank posts an approved credit. Keep the invoice until the review is finished. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 05, 2026

🔍 Diagnose MetaSync WordPress Publishing Failures

🔌 What a failed publish means MetaSync enables Search Atlas to publish articles to WordPress through the connected plugin. If publishing reports a failure, check WordPress for an existing post or draft before retrying. Signing back into Search Atlas does not necessarily repair the WordPress publishing connection. Source: metasync/public/class-metasync-rest-api.php:1705–1707; customer-frontend/src/modules/content-assistant/shared/components/cms/CMSModal.tsx:289–295. ✅ Confirm you are still connected Check the connection before you try the same article again. 1. Open the project or site that owns the article. 2. In Search Atlas, open Settings → CMS Connectors, then locate your website’s WordPress connection. Source: customer-frontend/src/modules/settings/v1/components/settings-page/navigation/index.tsx:46–49. 3. Confirm the saved address matches your live site, including https and the correct domain. 4. Look for an active or connected status. Missing, expired, or error status means the site is not fully connected. 5. If you manage several sites, confirm the article belongs to the property you intend to update. Signing in to the plugin only proves that login worked. Publishing also needs an active link between that WordPress site and Search Atlas. 🛠️ Check WordPress before retrying - Plugin: In WordPress, confirm the Search Atlas or MetaSync plugin is installed and active. - Permissions: The linked WordPress user must be allowed to create and publish posts. - Site address: Confirm that the WordPress connection points to the correct WordPress installation and a reachable publishing address. Use the installation’s canonical address, including any required subdirectory. Do not assume a www/non-www difference alone causes the failure; headless sites may use a different WordPress backend address from their public website. Source: content-assistant/app/ca/models.py:24523–24532,36499–36509. - Permalinks: Open WordPress permalink settings and save them once so site routes refresh. - Blockers: Security plugins, a firewall, a CDN, or host rules can stop the publish request. Your host may need to allow Search Atlas. 🚀 Publish one test article 1. In Settings → CMS Connectors, locate the affected WordPress connection and use Sync to check it. If Reconnect is available, follow that flow to restore access. For a plugin-based connection, verify the plugin’s connection in WordPress. Do not delete the connector as a routine troubleshooting step. Source: customer-frontend/src/modules/settings/v1/components/settings-page/components/cms-connectors-list/index.tsx:280–285,522–529. 2. Select one short draft instead of a batch of articles. 3. Publish that draft and wait until the status finishes. 4. Open the post on your website and confirm the title and content arrived. If the test post appears, publish the original article again. If it fails, copy the full error shown in Search Atlas before you retry. ⚠️ Common causes after re-authentication - Old link: The plugin was signed in again, but Search Atlas still uses a previous site connection. - Wrong site: The link points to staging, an old domain, or the wrong www version. - Limited user: The WordPress user can log in but cannot publish posts. - Blocked request: A security tool or host rule stops MetaSync from delivering the article. - Plugin conflict: Another publishing or security plugin interferes with the connection. 💬 What to send if it still fails If the status shows connected, the plugin is active, and one test article still fails, contact support with the site address, article name, attempt time, and the complete error text. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 05, 2026

⚙️ Disable OTTO Modules That Clash With Yoast

⚠️ Why OTTO and Yoast can clash OTTO and Yoast can both write the same on-page fields. When both tools manage titles, meta descriptions, canonical tags, Open Graph data, or schema, search engines may see duplicate or conflicting signals. You do not need to remove OTTO or undo every optimization. Turn off only the modules that overlap with Yoast and leave the rest active. 🧭 Decide what each tool should own Before you change anything, choose one owner for each field. A simple split that avoids clashes is: - Leave with Yoast: SEO titles, meta descriptions, canonical URLs, Open Graph and Twitter tags, and schema or structured data. - Title Tags, Meta Descriptions, Headings Length, Heading Optimizations, Image Alt Texts, and Internal Linking Opportunities are all real OTTO issue categories under Onpage Optimizations and Link Optimization. Headings, alt text, and internal links do not write Yoast's title, meta description, schema, Open Graph, or canonical fields, so they can stay deployed. Title Tags and Meta Descriptions write the same title and description fields Yoast owns, so do not leave those deployed if Yoast should own them. There is no per-module on/off switch for any of these categories. If Yoast already outputs a field, disable the matching OTTO module. Do not let both tools publish the same tag. 🛠️ Turn off conflicting OTTO modules 1. Open your project in Search Atlas and go to OTTO SEO. 2. Open the OTTO project, then use the issue categories in the sidebar. To stop a category from being deployed again, open Settings and use Deployment Rules, then Never deploy, and block that issue type. On a WordPress site using the MetaSync plugin, overlapping output is controlled separately in WP Admin under Search Atlas, Settings, General, Post/Page Editor Settings, not in the Search Atlas project settings. 3. The categories that write the same output as Yoast are Title Tags and Meta Descriptions under Onpage Optimizations, Schema Markup (Organization Schema, Domain-Level Schema, and Page-Level Schemas), Open Graph and Twitter Card under Miscellaneous, and Canonical Link under Link Optimization. Social metadata is not one module, and canonical is its own category. 4. You cannot turn a category off. Either click the green Deployed pill on each fix so it returns to Deploy, or use Roll back all for that category. Both ask you to confirm. To stop new deploys, block the issue type under Settings, Deployment Rules, Never deploy. On WordPress with MetaSync, check the matching boxes in Post/Page Editor Settings: Disable SEO Meta Box only hides the editor box and does not stop title or description output; Disable Schema Markup Meta Box, Disable Social Media & Open Graph Meta Box, Disable Canonical Meta Box, Disable Common Robots Meta Box, and Disable Language Alternates Meta Box stop MetaSync emitting those tags and stop it suppressing Yoast. Saved values are kept. Leave headings, image alt text, internal links, missing keywords, and NLP fixes deployed if you still want them. 5. Save your settings, then review a few important pages in WordPress to confirm Yoast is the only source for those fields. Clicking Deployed, or Roll back all, undeploys those fixes and removes them from what visitors see. It does not delete the suggestions. Adding an issue type to Never deploy also rolls back that type's live fixes and then blocks new deploys. The WordPress Post/Page Editor Settings checkboxes stop MetaSync emitting and suppressing those tags immediately, but they do not delete saved values, and they do not undeploy the OTTO suggestions. After either change, purge the plugin, host, and CDN cache and recheck the page while logged out. ↩️ Roll back deployments that are already live Roll back only the deployments that conflict with Yoast. You do not have to undo the whole OTTO installation. 1. There is no history page. In the OTTO project, open the issue category in the sidebar, search for the page URL, and use the Deployed filter to see the fixes that are live. 2. Each sidebar category is already one issue type. Open that category and filter the table to Deployed. There is no cross-site history to filter. 3. In the category table, click the green Deployed pill on a fix to undeploy it, or select several rows and choose Roll back in the bulk bar. For the whole category, use Roll back all. The confirm dialog says Confirm Undeploy all and asks you to proceed. The pill returns to Deploy. This removes the live change. It does not delete the suggestion. 4. Clear any site, CDN, or page cache, then view the page source. 5. Check that each rolled-back field now comes from Yoast only, with one title, one meta description, one canonical, and one schema block. If you do not want OTTO to put a change back, undeploy it first, then block that issue type under Settings, Deployment Rules, Never deploy. On WordPress, also check the matching Post/Page Editor Settings box so MetaSync stops emitting that output. Then clear the plugin, host, and CDN cache and recheck the page while logged out. Blocking the type rolls back fixes that are still live, so a missing rollback action is not the normal case. ✅ Keep pages optimized after the change - Confirm Yoast still has the target title, meta description, and focus keyphrase on priority pages. - Keep non-conflicting OTTO modules enabled so recommendations and safe optimizations continue. - Do not install a second metadata plugin alongside Yoast. - Recheck a sample of templates, not only one page, because theme or archive templates can still print old tags. 🔁 Turn the modules back on later You can reinstate modules when you are ready for OTTO to own those fields again. Plan a clean handoff so both tools are not active at the same time. 1. In Yoast, stop outputting the fields you want OTTO to manage, or disable the matching Yoast features. 2. Return to OTTO SEO and switch the paused modules back on. 3. Review the suggested changes, then deploy only the modules you restored. 4. Clear cache and confirm the live page shows a single, correct value for each field. Your earlier rollback does not delete the module. Turning it on again makes it available for a new deployment. 💬 Need a hand with a live clash If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 06, 2026

⚠️ False Instant Indexing Warning Explained

⚠️ What this warning means Some accounts saw a warning in OTTO saying Google stopped accepting recrawl requests for the project, even after the Google Search Console connection was checked again. In the case our support team reviewed, the stored rejection was stale: rechecking the connection did not clear it, but the banner does not stay up when a fresh live check shows the indexing account has access. The banner does not mean the whole Search Console connection is broken or that Google reported a problem with that connection. 🔍 What support confirmed A support agent reviewed the account and found that re-checking instant indexing in OTTO and in Google Search Console did not clear the stored message, because the message was not caused by a broken connection. The warning was a stale display issue on our side. Nothing on the account needed to be changed. The issue was escalated to the product team, and the warning was updated so an Owner-access banner appears only when a fresh live check confirms the indexing account does not have access. A separate blocked warning can still appear when Google is blocking the requests even though access is working. After that fix, the banner no longer showed on the account. ✅ What you should do If you already confirmed your Search Console connection and you still see the instant indexing warning, you do not need to disconnect, reconnect, or change settings just to clear that old message. Reload the OTTO view and check whether the banner is still there. - If the banner is gone, your connection was already fine and no further action is required. - Do not treat a banner that was already identified as a display issue as proof that indexing or Search Console access failed. - A genuine warning should now appear when a fresh check confirms the indexing account lacks Owner access in Search Console, or when Google is blocking the requests. The blocked warning tells the customer to contact support. 🛠️ If the warning is still visible If the instant indexing warning is still on screen after you reload, it may need a fresh look at your account rather than another round of the same verification. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 06, 2026

⚙️ Resolving Blocked OTTO Meta Tag Deployments

🔍 Understanding Blocked Meta Deployments OTTO SEO can automate title-tag and meta-description updates. If these fixes are marked as blocked, check the account-level and project-level Deployment Rules. A blocked issue type remains available for review but cannot be deployed. If an approved change is missing from the live site, investigate the installation, connection, and caching separately. [A] ⚙️ Common Causes of Deployment Blocks Before troubleshooting, distinguish between a fix blocked by Deployment Rules, a missing or disconnected installation, and an approved fix that is not appearing on the live page. These conditions require different checks. - Third-Party SEO Plugins: Rank Math, Yoast SEO, and All in One SEO can generate titles and meta descriptions alongside OTTO. The Search Atlas WordPress plugin includes compatibility handling for overlapping SEO output, so another SEO plugin being active does not automatically mean deployment is blocked. Investigate an actual output conflict before changing plugin settings. [B] - Deployment Toggles Disabled: The global deployment settings for meta tags inside OTTO may be turned off. - Aggressive Caching: WordPress page caches, hosting caches, and CDN caches can serve an older version of a page after an OTTO change. This may make an approved fix appear missing. Check fresh page output after clearing the relevant caches; caching is separate from an issue type being blocked by Deployment Rules. [C] - Installation or Connection Problems: If the OTTO code is missing, cannot run, or the site integration is disconnected, fixes may not reach the live site. Review the installation status and the installation guide or diagnostics available for your integration. Do not interpret a connection problem as a Deployment Rules block. [D] 🛠️ Step-by-Step Fixes for Blocked Deployments Follow these steps to restore your meta tag deployments and resolve the blocked state: 1. Check for Conflicting SEO Output: On WordPress, first confirm whether another plugin is actually interfering with OTTO’s titles or meta descriptions. Keep the Search Atlas plugin updated and inspect the resulting page output. Do not deactivate Yoast or Rank Math solely because it is installed. If a conflict is confirmed, adjust the relevant output using that plugin’s supported controls or ask support for integration-specific guidance. [B] 2. Verify Deployment Rules in OTTO: Open your site’s Settings, choose Automation, and find Deployment Rules. Open Never deploy and ensure the title-tag and meta-description issue types are not selected for blocking. Review inherited account rules and any project-specific overrides, then save your changes. Clearing a block allows deployment; it does not itself deploy pending fixes. [A] 3. Clear Site and Server Caches: Clear all layers of caching on your website. This includes your WordPress caching plugins (such as WP Rocket or LiteSpeed), hosting-level caches (such as Kinsta or WP Engine), and your CDN cache (such as Cloudflare). 4. Verify the OTTO Installation: Open the site’s Settings and choose Connections to review its installation status and installation guide. Use the diagnostics available for your installation method. For WordPress, also confirm that the Search Atlas plugin is active, updated, and connected to the intended site and OTTO project. Follow the installation-specific instructions rather than assuming every integration uses the same connection test. [D] 5. Deploy Eligible Fixes: After removing the relevant deployment blocks and resolving installation problems, return to the title-tag or meta-description fixes, select the eligible changes, and use Deploy. Review the deployment result and refreshed counts, then verify the live page. Removing a block does not automatically deploy fixes or guarantee that pending counts increase. [E] **Code references** - **[A]** content-assistant/app/ca/models/otto\_deploy\_block.py:1–6; customer-frontend/src/modules/otto/shared/components/settings-modal/sections.ts:11–15; customer-frontend/src/modules/otto/shared/components/settings-modal/automation-section.tsx:98–112; customer-frontend/src/modules/otto/shared/deploy-rules/ProjectNeverDeploySection.tsx:56–105; AccountDeploymentRulesSettings.tsx:105–109. - **[B]** metasync/includes/class-metasync-seo-conflict-handler.php:1218–1222,1272–1274,1405–1406; metasync/otto/metasync-otto-seo-functions.php:987–1002. - **[C]** metasync/otto/Otto\_pixel\_class.php:243–258,300–333. - **[D]** customer-frontend/src/modules/otto/shared/components/settings-modal/connections-section.tsx:45–59; customer-frontend/src/modules/otto/shared/installation-guide/components/ottoStatusCard.tsx:49–67. - **[E]** customer-frontend/src/modules/otto/shared/features/issue-renderers/page-title/utils/customHooks/index.tsx:112–158. 💬 Contact Support for Assistance If you have verified your settings, deactivated conflicting plugins, cleared your cache, and your meta updates still fail to deploy, our team can review your account directly. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 06, 2026

🔍 Verify OTTO Pixel on Local Landing Pages

🔍 What this article covers If you manage a franchise and only control local landing pages, Search Atlas can only detect the OTTO Pixel on pages where the pixel script actually loads. This article explains how to check those pages, fix the most common gaps, and confirm detection. 📌 Before you start You need the public URL of each local landing page and permission to view or edit that page’s header, tag manager, or theme. If a corporate or agency team owns the site template, you may only be able to request the change rather than install it yourself. - Open the local page in a normal browser window, not only inside a page builder preview. - Use the live URL customers see, including the correct domain and path. - Disable aggressive ad blockers for this test, because they can hide the pixel from your browser. 🛠️ Check that the pixel is on the page 1. Open the local landing page. 2. View the page source or use your browser’s developer tools and search for the OTTO Pixel script provided in Search Atlas. 3. Confirm the script is in the page head or loads through a tag that fires on that exact URL. 4. Reload the page once and check the Network tab for a request from the pixel. A blocked or failed request means the page is not sending data. 5. Repeat the check on at least one other local page. A script on the homepage does not cover franchise pages unless those pages use the same template. If you cannot find the script, the pixel is not installed on that landing page. Search Atlas cannot detect a pixel that never loads. ⚙️ Why detection often fails on franchise pages - Template gap: The main site has the pixel, but local landing pages use a different header or builder. - Tag rules: A tag manager fires only on the corporate domain or homepage, not on local URLs. - Wrong property: The script belongs to another Search Atlas project or an old install. - Caching: A CDN or page cache is still serving an older version without the script. - Consent or blockers: A cookie banner or security tool stops the script before it runs. - Draft versus live: The pixel was added in a draft, but the published page was not updated. ✅ Confirm detection in Search Atlas 1. Publish the page after the script is added. 2. Clear the site cache if your platform or CDN caches HTML. 3. Open the live local URL and load it fully. 4. In Search Atlas, open the OTTO Pixel or installation status for the project tied to that site. 5. Wait a short time, then refresh the status. Detection follows a real page view that successfully loads the pixel. Check the exact URL you tested. A visit to a different city page, a staging link, or a URL with a typo will not verify the page you care about. 💡 What to send your web team If you cannot edit the template, ask the team that controls the franchise pages to add the OTTO Pixel script from your Search Atlas project to every local landing page template, then publish and clear cache. Ask them to confirm the tag fires on the live local URLs, not only the main website. 💬 Still not detecting If the script is visible on the live page, the page has been published, cache has been cleared, and Search Atlas still does not detect it, gather the live page URL and a short note that the script is present. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 06, 2026

⚙️ Fix Site Quota, GSC, Analytics, and Visibility

📌 What this article covers Use this guide when an OTTO site is still using a site slot because it is Deep Frozen, Google Search Console or Google Analytics will not connect, or AI Visibility was created for the United States instead of the United Kingdom. You can connect Search Console and Analytics without installing an OTTO pixel. 🧊 Why a site looks frozen A Deep Frozen site holds its OTTO site slot for 14 days. The project is paused, and changes stay frozen until you unfreeze it. Freezing does not remove the site. After 14 days the slot is released on its own. To free the slot sooner, unfreeze is not required: choose Remove on the site card, or wait for the release date. - Open OTTO SEO, then All Sites, and select the Deep Frozen tab. A frozen site shows a Frozen until date and the days remaining. - Confirm you are in the account that owns the site. OTTO sites on that account keep Settings and Remove. A site on another account will not appear in your All Sites list. - If you only need the slot back, remove the unused site instead of keeping it frozen. 🗑️ Delete a site and free the quota To delete a site such as Nomadic and make room for another property: 1. Open OTTO SEO, then All Sites, and open the menu on the site you want to remove. 2. You do not need to unfreeze the site first. Open the site card menu and choose Remove. Delete stays available while the site is Deep Frozen. Unfreeze the site from the project header only if you want to keep it and start work again. 3. On the site card, open the menu and choose Remove. Confirm Are you sure you want to delete? 4. Confirm the deletion. The site leaves All Sites and its slot is released immediately. If you leave it Deep Frozen instead, the slot is released after 14 days, on the Frozen until date. 5. Add the new site, such as Vehicle Solutions, with Create on OTTO SEO → All Sites. Unfreeze is on the frozen project’s header, and Remove is on the site card in All Sites. If the site is not in your All Sites list, it belongs to another account. An admin on that account must remove it. Otherwise the Deep Frozen slot is released automatically after 14 days. 📍 Free a Search Console location Each active Search Console country uses one GSC location. A property with several active countries uses one location per country. Turn off countries you no longer track before you activate a new one. 1. Open GSC Sites List and choose the control that opens the sites drawer. 2. In the sites drawer, switch off the property, or open Select location(s) and clear the countries you no longer want active. 3. Return to GSC Sites List and confirm the GSC locations count has dropped. 4. In the GSC sites drawer, switch on the correct property and choose its locations. This does not require an OTTO project. Connecting Search Console does not require an OTTO pixel. The pixel is only for on-site OTTO tracking. Search Console uses your Google account and the property you select. 🔗 Connect Search Console and Analytics For Vehicle Solutions, or any site without an OTTO pixel: 1. To connect or disconnect the Google account, open the account menu and go to Integrations. To attach Search Console to an OTTO site, open that site’s Settings, then Connections. 2. Choose Google Search Console, sign in with the Google account that owns the property, and pick the matching site. 3. Choose Google Analytics, use the same or the correct Google account, and select the Analytics property and data stream for that site. 4. Save and wait for the status to show Connected. Use the Google account that already has access in Search Console and Analytics. A successful Google sign-in on the wrong property will not attach data to this project. 📊 Analytics still says Connect A stale status can remain after a successful update. Work through these checks in order: 1. Refresh the project page. Do not rely on an old browser tab. 2. Confirm the connected Google account and the exact Analytics property. The names must match Vehicle Solutions, not another site. 3. Choose Disconnect, then connect again and reselect the property and stream. 4. If more than one Google account is signed in, sign out of the extra accounts in the browser and repeat the connection. 5. Check that your Google user still has at least Viewer access on that Analytics property. After a clean reconnect, the button should change from Connect to Connected. New Analytics data can take a short time to appear. The label itself should update as soon as the property is saved. 🚀 Add the site to AI Visibility AI Visibility is separate from the OTTO pixel. You can enable it for a site that has no pixel. 1. Remove the old site, such as Nomadic, if it is using the quota and you no longer need it. 2. Add or open the correct project. 3. Open AI Visibility and create or select the brand profile for that domain. 4. Save the profile, then run or refresh visibility so results use the new brand. 🇬🇧 Set the brand profile to the United Kingdom If results or the profile show the United States, the market was saved incorrectly. Change it on the brand profile, not in Search Console. 1. Open AI Visibility and select the brand. 2. Open profile or market settings. 3. Set Country or Market to United Kingdom. 4. Save, then refresh the report so new checks use the UK market. Existing US results stay in older runs. New runs should use the United Kingdom after you save. ✅ Quick checklist - Unfreeze a site before you try to delete it. - Delete unused sites and disconnect unused Search Console properties to free quota and locations. - Connect Search Console and Analytics from Integrations. An OTTO pixel is not required. - If Analytics still says Connect, disconnect, confirm the property, and connect again. - Set the AI Visibility brand market to the United Kingdom and refresh. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 06, 2026

🚫 Exclude Unwanted URLs from OTTO Scans

🚫 Why unwanted URLs appear in OTTO OTTO uses discovered and crawled pages to build recommendations. Accessible archives, parameter URLs, and other unwanted paths can enter that set. Crawl exclusions control which URLs participate; a recrawl refreshes crawl data but does not replace every existing recommendation wholesale. You do not need to delete each recommendation by hand. Exclude the URLs you do not want, then rescan. After the new scan finishes, the task list should reflect only the included pages. 📋 Before you change the scan - List the real pages you want scanned, such as your 136 live URLs. - List the URLs or path patterns you want left out, such as /tag/, /cart/, or query-string pages. - Confirm those pages are not required for navigation or important internal links. - Wait until any scan already in progress has finished before you start a new one. ⚙️ How to exclude URLs and rescan 1. Open the site in Search Atlas and go to OTTO. 2. Open the scan or crawl settings for that site. 3. Under Crawl Parameters, find URL Exclusion conditions and click + Add condition. Choose Exclude, select Contains or Start With, and enter the unwanted URL path or matching path text, such as /tag/. Add additional conditions as needed. (customer-frontend/src/modules/otto/shared/components/settings-modal/ottoSettings.tsx:839–845,1197–1256.) 4. Use Include only when you need an exception to an Exclude condition. OTTO requires an Exclude condition before enabling Include; this is not a separate list of pages to review. (customer-frontend/src/modules/otto/shared/components/settings-modal/ottoSettings.tsx:1217–1224.) 5. Click Update Settings to save the exclusion conditions. Then open the linked Site Audit and choose Recrawl or Recrawl Site. (customer-frontend/src/modules/otto/shared/components/settings-modal/ottoSettings.tsx:1287–1300; src/modules/site-audit/v2/shared/recrawl-button/index.tsx:30.) 6. When the scan completes, review the task list. Recommendations for excluded URLs should no longer appear. Excluding a URL stops it from driving new OTTO tasks. It does not delete the page from your website, change its content, or remove it from Google by itself. 🔁 Can you purge the task list? You do not need a delete-all action to exclude unwanted pages from active recommendations. Save the exclusion conditions and recrawl the linked Site Audit. OTTO marks matching existing URLs as excluded and filters them from active results; the recrawl updates existing page data rather than deleting and rebuilding every recommendation. (content-assistant/app/ca/models/otto\_project.py:7913–7953; app/ca/pipelines/otto\_v2.py:7060–7064.) If old tasks for excluded URLs are still visible after the new scan shows as complete, refresh the OTTO view. If they remain, use the chat widget so support can check that scan. 🔍 Does OTTO follow noindex rules? No. A noindex tag is not a reliable way to keep a URL out of an OTTO scan. Noindex tells search engines not to index a page. It does not always stop a site audit from crawling that page or creating technical recommendations for it. - Use OTTO exclusions when you want a page left out of scans and the task list. - Use noindex when you want search engines to drop a page from their index. - A robots.txt disallow blocks crawling only when Respect robots.txt is enabled. It does not immediately erase previously stored OTTO recommendations. Use URL Exclusion conditions for explicit OTTO scope control, then recrawl and review the results. (content-assistant/app/ca/models/site\_audit.py:706–717; app/ca/models/otto\_project.py:7913–7943.) Pages you want audited should remain accessible to the crawler. They may use noindex when that matches your indexing policy. For pages you want excluded from OTTO, configure URL Exclusion conditions even if those pages already use noindex. (content-assistant/app/ca/models/otto\_url.py:118–131.) ✅ After the new scan - Check that the page count is close to your real set, not the old larger set. - Open a few excluded URLs in the results and confirm they no longer have open tasks. - Spot-check important live pages to confirm their recommendations were regenerated. - Keep the exclusion list updated when you add new template, filter, or parameter URLs. 💬 Need help with a scan If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 06, 2026

🏢 Multi-Location OTTO for Agencies

🏢 Overview OTTO supports agencies managing multiple client websites. Organize work by website project, connect the relevant business profiles and integrations, and monitor results across your portfolio. 📍 Managing Multiple Locations 1. Create or open the OTTO project for the client’s website. Locations sharing that website do not automatically need separate projects. 2. Connect the correct website and relevant integrations to its OTTO project. When connecting Google Business Profiles, select the appropriate business locations. 3. Review OTTO settings for each project before publishing changes. 4. Use project-level reporting to evaluate each client website’s performance. Use location-specific reporting where available to assess individual business locations. Keep different client websites in their appropriate projects, and verify connected business profiles, settings, and deployment scope before applying changes. ⚙️ Agency and Enterprise Support Agency and enterprise customers can request assistance with multi-location setups, account structure, access, OTTO configuration, and troubleshooting. Support requests are handled through the platform so the team can review the relevant account context and respond in one conversation. When requesting help, include the client or project name, affected location, the task you are trying to complete, and any error message or screenshot. This helps the support team understand the issue and provide more targeted guidance. 💬 How to Request Assistance 1. Open the Search Atlas platform. 2. Select the live chat widget in the bottom-right corner. 3. Send a clear description of your question or issue. 4. Include relevant project, client, and location details. 5. Continue the conversation in the chat while the team reviews your request. For complex agency accounts, explain the full workflow you want to achieve. For example, state whether you need help structuring projects, configuring OTTO across locations, or reviewing a publishing issue. ✅ Best Practices for Faster Resolution - Use clear project and location names. - Submit one request per main issue when possible. - Describe what you expected to happen and what happened instead. - Share the steps that already failed or were attempted. - Do not include passwords or other sensitive information in chat. 🛠️ Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 06, 2026

🔄 Reinstate Safe OTTO Features With Yoast

🔄 What this article covers This article explains how to use Search Atlas with Yoast after an OTTO rollback. You can turn OTTO features back on when they do not write the same on-page SEO tags that Yoast already manages. ⚠️ Why the two tools can conflict Both OTTO and Yoast can control titles, meta descriptions, canonical links, schema, and social tags. If both publish those items, search engines may see duplicate or changing signals. A rollback stops OTTO from publishing so Yoast stays in control. ✅ What to keep with Yoast Leave these items managed by Yoast only: - SEO titles and meta descriptions - Canonical URLs - Schema and structured data - Open Graph and Twitter cards - Robots and index settings Do not re-enable any OTTO automation that writes or replaces these fields. 🚀 Features you can reinstate These OTTO and Search Atlas features usually do not conflict with Yoast: - Site audits and technical issue reports - Keyword and rank tracking - Content ideas and on-page recommendations you apply yourself - Internal link suggestions that stay off the live page until you click Deploy on each suggestion, or choose Deploy all in this section. - Reporting and task lists inside Search Atlas Use manual review. Do not let OTTO auto-deploy changes to pages Yoast already optimizes. 🛠️ How to turn safe features back on 1. Open your project in Search Atlas and go to OTTO SEO. Work in each fix category rather than one settings screen. 2. Review each fix category. Leave Page Title, Meta Description, Canonical Link, Schema Markup, Open Graph, and Twitter Card suggestions undeployed, or add those issue types to Never deploy under Deployment Rules. On WordPress, also leave the Canonical, Schema Markup, and Social Media & Open Graph disable boxes checked in the plugin’s Post/Page Editor Settings. 3. Use Site Audit, keyword and rank tracking, Content Genius ideas, and undeployed OTTO suggestions. Those show recommendations and do not publish on-page tags until you deploy an OTTO suggestion. 4. Nothing goes live until you click Deploy on a suggestion or Deploy all in this section. To keep selected issue types from ever being deployed, add them under Deployment Rules, Never deploy. 5. Save Deployment Rules if you changed them. For other fixes, use Deploy or Roll back all deploys in this section. Then check one live page while logged out, and clear the site and CDN cache if the old tags still appear. 🔍 How to confirm there is no conflict 1. View the page source or use your browser inspect tool. 2. Confirm there is only one title, one meta description, and one canonical tag. 3. Confirm schema and social tags match what Yoast shows in WordPress. 4. Clear any cache or CDN, then check the page again. If you see two versions of the same tag, turn off the matching OTTO automation and recheck. 💬 Need more help If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 06, 2026

🔁 Fix Deleted OTTO Project Setup Loop

🔍 Why the deleted project screen returns After you remove an OTTO site, go back to OTTO SEO → All Sites to work on another site. A setup loop happens when an open tab, bookmark, or saved setup link still opens the removed site's setup page at /seo-automation-v3/create-project. That page can still load the removed site, because removal does not make the setup link fail. Use All Sites instead of that link. This usually comes from an open tab, a bookmark, the browser Back button, or a saved setup link for that site. It is not a sign that the removed site is still active. An unfinished site that is still in the list shows Continue installation, not Continue setup. ✅ Leave the old screen safely Do not fill in step 2 again, and do not keep refreshing that screen. Use these steps in order: 1. Close every Search Atlas tab that shows the deleted project's setup. 2. Open a fresh browser tab and sign in to Search Atlas. 3. Open OTTO SEO from the left navigation, then stay on All Sites. Do not use a bookmark, email link, or browser history item that points at the removed site's setup page. 4. Check that the deleted project is not in the list. If it is gone, the deletion succeeded. 5. Click the site you want to work on, or click Create to add a new OTTO site. Do not click Continue installation on the site you meant to remove, and do not reopen its saved setup link. 🛠️ Clear a stuck setup session If a normal visit still opens step 2 of the deleted project, clear the saved session in your browser: 1. Sign out of Search Atlas. 2. Close the browser completely, then open it again. 3. Sign in and go directly to the project list. 4. If the loop remains, open a private or incognito window, sign in there, and open the project list. 5. Remove any bookmark that opens OTTO setup or a project URL you no longer use. A private window is only a test. If the project list works there, the problem is saved data in your regular browser, not the deleted project itself. Clear cached site data for Search Atlas in your browser settings, then sign in again in a normal window. 📊 Start or open the next project Once the project list loads normally: - Existing project: select its name from the list and continue from its current page, not from an old setup link. - For a new site, click Create on the OTTO SEO All Sites page and complete Add a website, Setting up, and Install OTTO Pixel for that new site only. - Avoid old links: do not paste a previous setup address into the browser. Each project has its own setup. Completing step 2 on a new project does not require the deleted project, and deleting one project does not remove your other projects. 💬 If the loop still appears If you still land on the deleted project's step-2 screen after a fresh sign-in, tell support which project was deleted, which project you are trying to open, and whether a private window has the same problem. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 07, 2026

🛠️ Fix OTTO Script Detection

🔍 Why OTTO Is Not Detected OTTO may show as not detected when its dynamic optimization script is missing, placed incorrectly, or not published on the live version of your website. Changes made in a website editor or staging environment may also be unavailable to OTTO until they are published. 📋 Check the Script Installation 1. Open the OTTO setup instructions in Search Atlas and copy the complete dynamic optimization script. 2. Paste the script into your website’s global code area, usually inside the section of every page. 3. Save the changes and publish the website. Saving a draft is not enough. 4. Confirm that the script was added to the live domain connected to your OTTO project. 🌐 Verify the Live Website Open your website in a private or incognito browser window. View the page source and search for a unique part of the OTTO script. Make sure you are checking the public URL, not a preview, staging, or editor URL. If your website redirects between versions, check the final URL that loads in the browser. The script must be available on that live version, including the correct HTTP or HTTPS version of the domain. ⚙️ Check Common Installation Issues - The script was pasted into page content instead of the global header or head section. - Only part of the script was copied. - The website changes were saved but not published. - A caching, security, or consent tool is preventing the script from loading. - The script was added to a different domain, subdomain, or staging site. - A content management system removed the script after an update. 🔄 Clear Caches and Recheck After publishing the script, clear your website, hosting, CDN, and caching plugin caches if applicable. Then open the live website again and check the page source. Return to Search Atlas and run the OTTO detection check again. Detection may not update immediately after installation. Allow a short period for the platform to recheck the website before making repeated changes. ✅ What to Send Support If OTTO is still not detected, confirm that the script appears in the live page source and note the exact website URL being checked. Include any recent changes to your website, caching setup, consent banner, or security settings. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 07, 2026

🛠️ Update Deployed OTTO SEO Recommendations

✅ What to expect when you edit a live recommendation Editing an already-deployed OTTO SEO recommendation updates that recommendation's live value as soon as you save it. The recommendation stays deployed, and saving does not remove your other optimizations. After you save, the recommendation stays Deployed. The new value replaces the previous live value for that recommendation, while your other deployed optimizations remain unchanged. 🛠️ Publish the updated value safely 1. Open the correct project in Search Atlas and go to OTTO SEO. 2. Locate the deployed recommendation. Filter by Deployed or search by page URL so you edit the right item. 3. Open the recommendation and change only the values you want to update. 4. Select Save. Saving updates that recommendation immediately. If it is already deployed, the new value becomes the live value. Saving does not undeploy your other live optimizations. 5. You do not need to publish or redeploy the recommendation after saving. Avoid Deploy all in this section, Roll back all deploys in this section, and Deploy all fixed suggestions, because those actions change many recommendations at once. 6. The recommendation remains Deployed after you save. Refresh the live page to confirm the new value. 📊 How the previous optimization is handled Saving replaces the live value for that deployed recommendation. Titles, descriptions, content, links, schema, and any other recommendations you did not edit continue running as before. - Save updates the stored recommendation and, when it is already deployed, replaces the old live value. There is no separate publish step. - Saving one recommendation updates only that recommendation. It does not change recommendations you did not edit. - Bulk actions: may change many optimizations at once, so do not use them for a single correction. 💡 Check the result before and after publishing - Confirm the project, page URL, and recommendation type before saving. - Review accuracy, length, and branding in the new value. - Make sure your OTTO installation remains connected so the update can go live. - After publishing, refresh the recommendation status and spot-check the page. - The recommendation remains Deployed after saving. The live page may still show the previous value until the page or site cache is refreshed. ⚠️ If the new value does not appear If the live page does not reflect your edit, refresh the page and clear your browser cache or site cache. Confirm that you saved that specific recommendation and that OTTO remains installed and engaged. Do not roll back unrelated recommendations while troubleshooting. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 2026

🔗 Wildfire Links After Cancel or Disable

🔗 How Wildfire links work Wildfire places links through the OTTO pixel. Approved outbound links can appear on your pages while Wildfire is enrolled. Partner sites that are also enrolled can place approved links to you the same way. These links are served by the pixel. They are not written into your page content or CMS. ⚙️ If you turn Wildfire off Turning Wildfire off and saving the change removes your approved outbound links and the approved links partner sites gave you. The pixel rebuilds the affected pages and then stops inserting those links. You do not need to edit each page. A page that is already open, or a cached copy, can still show an old link until it loads again. Turning Wildfire off also removes the approved Wildfire links partner sites placed to you. Their pixels stop serving those links after the affected pages are rebuilt. A page that was already open, or a cached copy, can still show an old link until that page loads again. Wildfire does not delete links that were added outside Wildfire. 📊 If you cancel and stay enrolled Leaving Wildfire enrolled does not keep links active permanently after you cancel, but they do not stop the moment you cancel. The subscription continues through the paid period. After the account is no longer active, there is about a 24-hour grace period, and then an automated freeze removes the Wildfire links. Until that happens, outbound links can still be inserted on your site and partner sites can still serve approved Wildfire links to you. After the grace period, the automated freeze removes Wildfire links in both directions, with the same end result as turning Wildfire off. The links end when the pixel stops serving them after the pages are rebuilt, not by a separate cleanup of your CMS or of partner websites. A cached or already-open page can still show an old link until it loads again. 💡 What stays in place - Links you added yourself in your content - Backlinks that did not come from Wildfire - Your own site content, menus, and footer links Wildfire link tables are part of the OTTO project and can be viewed while you can still sign in, including during the paid period after cancellation. After the account is deactivated, dashboard access ends, so those tables are no longer available. 🛠️ Before you cancel 1. Turn Wildfire off first if you want links to stop before the subscription end date. 2. Keep the pixel installed so your site can load the updated setting. 3. Open a few pages and confirm the outbound Wildfire links no longer appear. 4. Allow partner pages time to load again before you expect every old backlink to disappear. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 09, 2026

🛠️ Sitewide twitter:site and sameAs Markup

📌 What these signals do twitter:site is a meta tag in the page head. It tells X (formerly Twitter) which account represents the whole website, and it is meant to appear on every public page. sameAs is different. It is a list of official profile URLs inside Organization JSON-LD. It connects your brand entity to X and other profiles. It is not a replacement for the twitter:site meta tag. 🧭 Where the X link is set There is no separate plugin version or legacy screen that sets twitter:site on its own. The source is Brand Vault. The current Search Atlas connection on your site (WordPress plugin, OTTO script, or other supported install) reads that Brand Vault profile. Keep the install updated from your platform’s plugin or app screen so it can publish the latest brand data. 1. Open Brand Vault in Search Atlas. 2. Add the full X profile URL in the social or brand links field (for example, https://x.com/yourbrand). 3. Save the brand profile. 4. In OTTO, publish or sync so the live site receives the updated meta and schema. 5. Clear any site, plugin, or CDN cache, then recheck the live page source. 🌐 Why sameAs shows only on the homepage This is expected. Search Atlas defines the Organization entity, including sameAs, on the homepage so the brand is declared once. Inner pages use their own page schema and do not repeat the full Organization block. Seeing the X URL inside homepage JSON-LD, and not inside JSON-LD on every other URL, does not mean the social profile failed to save. The twitter:site meta tag is separate. After the Brand Vault link is saved and OTTO is published, that meta tag should be present in the head of the homepage and of inner pages. ✅ How to confirm both signals 1. On the homepage, view source and find the Organization JSON-LD. Confirm sameAs includes your X URL. 2. On an inner page, view source and search for twitter:site. It should be in the head, not inside the homepage JSON-LD. 3. Do not expect sameAs on that inner page. Its absence there is normal. 4. If a social preview tool still shows an old result, recheck the raw source. Many preview tools cache cards. 🔧 If twitter:site is missing on inner pages - Confirm the X URL is saved in Brand Vault and that OTTO has been published again after the change. - Confirm the Search Atlas plugin or OTTO script loads in the head of that template, not only on the homepage. - Clear cache and exclude the page head from optimization tools that strip meta tags. - Remove a conflicting SEO plugin or theme field that outputs a different twitter:site or blocks head injection. - Check that the inner page is not excluded from OTTO or set to noindex in a way that skips head output. Homepage-only sameAs plus sitewide twitter:site is the correct result. If the meta tag is still missing on inner pages after a fresh publish and cache clear, the install on that template needs a review. 💬 Need more help If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 09, 2026

🔄 How to Trigger an OTTO Smart Crawl

🔄 What an OTTO Smart Crawl does A Site Audit crawl visits your live website and refreshes the pages, content, and structure OTTO uses for SEO recommendations and automation. Running one manually is useful after a redesign, a new page launch, or major URL or content changes, so OTTO is not working from an older version of your site. 📋 Before you start the crawl Confirm these items so the crawl can see your updated site: - Publish the changes on the live domain connected to your OTTO project. - Check the correct project if you manage more than one website. - Allow crawling in your robots.txt file and remove any temporary noindex tags from pages you want included. - Submit or update your sitemap if important new URLs are not linked from existing pages. 🚀 Start a manual Smart Crawl 1. Sign in to Search Atlas and open Site Audit for the project. From an OTTO project, use the project menu and choose Open Site Audit. 2. Select the website project you revamped. 3. Open the Site Audit project and go to its Website Overview page. The same control is also on the Crawl Logs page, which you can reach with "View most recent crawl log". 4. Click Recrawl Site. While a crawl is already running, the button reads "Crawling…" and cannot be clicked again. 5. Leave the crawl running. You can stay on the page or return later to check progress. 6. When the crawl finishes, the "Crawling…" button returns to "Recrawl Site" and the progress ring returns to a health label. The updated page list is available then. OTTO recommendations are rebuilt in a separate step that starts after the crawl, so give them a little longer to reflect the new content. Run only one crawl at a time for the same project. Starting another crawl while one is in progress can delay results. ⏱️ What to expect after it finishes A completed crawl does not change your live site. It only refreshes Search Atlas's understanding of your pages, and OTTO recommendations are rebuilt from that afterward. Pages the crawl can reach — by following links on your site or by reading your sitemap — should then appear in the project, unless a crawl exclusion rule skips them. Large sites take longer than small sites. If a page is missing, confirm it is live, linked from your site or listed in your sitemap, and not blocked from crawlers or excluded by a crawl rule. 🛠️ If the new site still does not appear - Clear any maintenance mode, password protection, or firewall rules that block the crawler. - Make sure redirects from old URLs point to the correct new pages. - Wait until the current crawl shows complete, then run one new Smart Crawl. - Check that you selected the project for the redesigned domain, not an older property. 💬 Need more help If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 10, 2026

🔗 Wildfire Link Removal and OTTO Exports

🔍 Understand the Two Types of Wildfire Links Before turning off Wildfire or canceling your subscription, distinguish between these two types of links: - Outbound Wildfire links: Links placed on your website that point to partner websites. - Partner backlinks: Links placed on partner websites that point to your website. Do not assume that both types of links follow the same removal process or timeline. ⚙️ Confirm What Happens Before Canceling Leaving Wildfire enrolled does not establish whether links will remain after cancellation. Before canceling, request confirmation of what will happen to your outbound links and partner backlinks, including when any removal would occur. Likewise, do not assume that switching Wildfire off immediately removes both types of links. Confirm the removal process and timing before making the change. Links on partner websites should not be treated as removed simply because you have changed a setting on your own account. 1. List the domains affected by your planned change. 2. Specify whether you intend to disable Wildfire, cancel your subscription, or both. 3. Ask whether outbound Wildfire links will remain or be removed, and on what timeline. 4. Ask the same questions separately for partner backlinks. 5. Request confirmation of how removal can be verified. 📊 Request a CSV of Deployed OTTO Fixes For a record of your OTTO work, open the OTTO project, then the actions menu, and choose Export, then Work Summary. This creates a Google Sheet for that project and opens it when it is ready. The Deploy Changelogs sheet lists every deploy and undeploy action, marked Deployed or Undeployed, so it is not limited to fixes that are currently deployed. Recommendations and pending changes are a separate export called OTTO Suggestions, which is emailed to you. Run the export once for each domain you need. For the domains in this example, specify: - thehomesdirect.com - cliffyoungltd.com - mikegingerich.com Ask for all available deployment history and, where available, the affected URL, fix type, deployed change, deployment date, and current status. Specify whether you prefer one combined CSV or a separate file for each domain. Export availability, included fields, and historical coverage need to be confirmed. Request your records before canceling so you can clarify the scope while you still have platform access. A CSV is a record of changes; it does not itself preserve, remove, or reverse deployed fixes. 💬 Send a Complete Request Use the following message to provide the details needed for review: “We are considering disabling Wildfire and/or canceling our subscription. For thehomesdirect.com, cliffyoungltd.com, and mikegingerich.com, please confirm what happens to outbound Wildfire links and partner backlinks in each case. Are they retained or removed, what is the removal timeline, and how can we verify completion? Please also confirm whether you can provide a CSV of all deployed OTTO fixes for these domains, including available deployment details and historical coverage, before cancellation.” If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 10, 2026

🛠️ OTTO Code Changes After Cancellation

🔍 What happens to OTTO changes? When OTTO applies an SEO change, it is either written into your site (through a CMS integration or a merged code change) or delivered at page-render time through the OTTO connection (the installation script, the WordPress plugin, or a Cloudflare Worker). If you stop using OTTO, what happens to existing changes depends on which of those two ways they were applied. After your subscription is cancelled, OTTO freezes the project about 24 hours later. Freezing stops autopilot and all new processing, so no new recommendations, fixes, or automatic optimizations are generated, but the changes already deployed keep being served through the installed connection. OTTO fully stops serving, monitoring, and maintaining those changes only when the project is deleted or the connection is removed. ⚙️ What happens when OTTO is disconnected? Disconnecting OTTO stops its access to your website. It does not automatically remove every change that was previously published. The exact result depends on how the change was implemented. - Changes OTTO wrote into your CMS, and code changes that were merged into your repository, stay on your site until someone edits or reverts them. OTTO does not remove them when you disconnect. - Changes delivered through an OTTO connection or script: These may stop displaying when the connection is removed. - Changes that were written into your CMS, or merged into your code repository, have to be removed in that system. OTTO does not undo them. The exception is community backlinks: links OTTO placed are removed automatically when the project is deleted or when the subscription cancellation freezes it. ↩️ Can previous changes be removed? Yes. Changes can typically be removed or reversed by editing your website, restoring a backup, or undoing the related settings. Before removing changes, review their SEO impact and keep a backup of your current site. If you want to preserve the improvements, no action may be necessary. If you want to remove them, ask your website administrator or developer to review the published changes and remove them individually. 📋 What should I do before cancelling? 1. Review the OTTO changes currently published on your site. 2. Save a backup or copy of important pages and settings. 3. Record which changes you want to keep or remove. 4. Check how OTTO was installed on your site. It will be one of the installation script (the OTTO pixel), the WordPress plugin, a CMS integration, or a Cloudflare Worker. Separately, some approved changes may have been merged into your code repository. 5. Plan how future SEO updates will be managed after cancellation. 💡 Key takeaway Cancelling your subscription freezes OTTO about 24 hours later and stops all future updates, but it does not undo anything already applied, and the installed connection keeps serving the existing changes. Deleting the project or removing the connection stops the script, plugin, and Cloudflare Worker changes from rendering, while changes written into your CMS or merged into your repository stay in place. Check how OTTO is installed before you disconnect it. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 10, 2026

⚙️ Why Schema Edits Do Not Change Page Type

📌 What this article covers You can still edit schema in OTTO, but the page type may stay the same after you save. This article explains how those two settings work today and how to update the page type when you need it to change. 🔗 How schema and page type work together Schema and page type are related, but they are saved as separate settings. - Schema is the structured data OTTO prepares for the page, such as Article, Product, or FAQPage. - Page type is the label OTTO uses to classify the page and choose related recommendations. In the past, changing the schema could also change the page type. That automatic link is no longer applied. Editing or replacing schema now updates the schema only. The existing page type is kept so a schema change does not overwrite a classification you already set or that OTTO already assigned. 🛠️ Why the page type stays the same The page type remains unchanged in these common cases: - You edited the schema, and schema edits do not change the stored page type. - The page already has a page type that OTTO assigned. That stored page type is kept. - You added or edited a schema. Page type is the page's classification, so changing any schema does not change it. - The new schema was saved, but it does not match the page’s current type. - Changes are saved in OTTO but have not finished processing on the page yet. Being able to edit the schema confirms that schema editing is working. It does not mean the page type will update on its own. ✅ How to update the page type If you want a different page type, set it directly: 1. Open the page in OTTO. 2. Find the Page Type shown separately from the schema editor. It is display only, so you cannot change it there. 3. You cannot select a page type. OTTO assigns one automatically, such as Blog Page, Product Page, or another detected type. 4. Review the schema and keep the main schema aligned with that page type. 5. Save the schema. The page type stays as OTTO assigned it. 6. Allow OTTO to finish processing the schema, then refresh the page view. The page type remains the type OTTO assigned. If the detected page type is not the one you expected, keep it. You can still edit the schema so it describes the page accurately. 🔍 How to confirm the change After saving, check three things: - The page type field shows the type you selected. - The main schema matches that page type. - The updated values are still there after you leave the page and open it again. If the schema saved but the page type returned to the old value, set the page type again and save before leaving the page. Do not rely on a schema edit alone to change it. 💬 When to contact support Contact support if you selected and saved a new page type, the schema is valid, and the page type still reverts after processing. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 10, 2026

🔥 Wildfire Zero Backlinks After Outbound Links

🔍 Why backlinks may not appear immediately Wildfire does not guarantee that backlinks will appear as soon as outbound links are approved. An approved outbound link is placed by the OTTO pixel and then checked to confirm it is present, and a suitable partner must be available. Matching depends on topicality, authority, and an available page, so backlinks are not immediate. Adding 20 outbound links does not always result in 10 backlinks immediately. The exchange depends on the campaign requirements, link quality, available opportunities, and successful verification. ✅ Check whether your links qualify - Confirm that each outbound link is placed on the website and page connected to Wildfire. - Make sure the links are live, clickable, and point to the correct destination. - Wildfire does not reject an outbound link because it is nofollow, sponsored, or has a similar attribute. An approved link is placed by the OTTO pixel and confirmed by a pixel check that the link is present. - Verify that the linked pages are accessible to search engines and are not blocked by robots.txt or other restrictions. - Ensure the links meet Wildfire requirements. Suggestions are matched on topical relevance and authority, and an approved link must have an available page to be placed on. There is no separate anchor-text rule. 📊 Review your Wildfire status Open OTTO and go to the Wildfire section to review your inbound and outbound links. A link can be Request (not yet requested), Pending (awaiting the other site owner's review), Active (approved), or Reproved (declined by the site owner). Only Active links count as completed. If the Wildfire lists are empty, no link suggestions were generated for your project. That usually means no partner currently matches your site on topicality and authority. It does not by itself mean your website setup is incorrect. 🛠️ Steps to improve detection 1. Keep the outbound links live and unchanged while Wildfire processes them. 2. Confirm that the pages containing the links return a normal status and are publicly accessible. 3. Remove duplicate, broken, redirected, or irrelevant links. 4. Allow time for crawling and verification after making changes. 5. Refresh the Wildfire status later to check for newly detected opportunities. ⏳ What to expect about timing Backlink availability depends on crawling, verification, partner participation, and campaign inventory. Because these factors change over time, there is no fixed schedule for receiving backlinks. A campaign promise such as 10 backlinks in exchange for 20 outbound links describes the campaign arrangement, not an instant delivery time. If your links have remained eligible and unchanged for an extended period but Wildfire still shows zero backlinks, review the link details and campaign status before requesting assistance. 💬 Get help with an unresolved campaign When contacting support, include the Wildfire campaign name, your website, the affected page URLs, the date the outbound links were added, and screenshots or status details. This helps the team review the issue faster. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 10, 2026

🔄 Following Up on WordPress Sync Issues

🔍 Understand Sync and Publishing Issues If your WordPress content is not syncing with Search Atlas or a publishing action does not complete, the issue may need technical review. An escalated report does not necessarily mean a fix has been released. Support can check your existing report and share any confirmed updates. ✅ Check What Is Still Affected Before following up, confirm the current behavior so support can assess whether the original issue is still occurring. 1. Confirm the website: Check that you are working with the intended OTTO project and the matching WordPress website under Settings, then CMS Connectors. 2. Check WordPress directly: Look for the affected page or post and confirm whether it is missing, saved as a draft, or published. 3. Review the content: Compare the affected content in Search Atlas with the version in WordPress. 4. Record any message: Copy the exact error text or capture a screenshot, including where the problem appears. A missing sync update and a failed publishing action may have different causes. Note which action failed and what you expected to happen. 🛠️ Avoid Duplicate Publishing Attempts Before retrying a publish action, check whether WordPress already created the post or page. A normal retry updates the post Search Atlas already recorded. It can create another post or page only if the first request succeeded in WordPress without Search Atlas recording it, or if you explicitly choose to create a new post. If the issue has already been escalated, avoid disconnecting the integration or making broad configuration changes unless support recommends them. These changes can make the original behavior harder to investigate. 💬 Follow Up on Your Existing Report Use your existing chat conversation when available so the team has the earlier troubleshooting details. Include: - The affected WordPress website and Search Atlas project. - The page or post title and URL, if available. - Whether syncing, publishing, or both are affected. - The date, time, and time zone of the most recent failed attempt. - The exact error message and any screenshots. - Any changes made since the original report, such as WordPress, plugin, or permission updates. - Your existing report reference, if one was provided. Suggested message: “I’m following up on my WordPress sync issue for [website]. The problem still occurs when I [action]. My latest attempt was [date, time, and time zone], and the result was [error or behavior]. Has a fix been confirmed, and is there a recommended workaround?” If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat. 📋 Verify a Confirmed Fix Once support confirms that a fix is ready, follow any testing instructions provided. Test one affected item first, then check both Search Atlas and WordPress to confirm the expected content and publishing status. If the problem continues, reply in the same chat with the new test result and timestamp. Do not assume the issue is resolved until the affected action works as expected.

Last updated on Nov 10, 2026

💳 Resolve Extra OTTO Project Charges

💡 Why an extra OTTO charge can appear Each OTTO project uses one licensed site slot. Extra site capacity is a recurring OTTO Sites top-up, not an automatic extra-project fee added whenever the account briefly goes over its limit. That top-up is billed by the site quantity on the subscription when billing runs, not by the domain you intend to keep. Switching a site from one domain to another updates the same OTTO project. It does not leave the old domain as a second project. A project continues to count until it is deleted, or, if it is only frozen, until its site slot is released 14 days later. 🛠️ Check the project change before you request a refund Confirm these points in your account: 1. Open OTTO and confirm the site you no longer need has been deleted, not merely frozen. A frozen site still uses its slot for 14 days. 2. Confirm the replacement domain is the only active project for that site. 3. Count projects that still use a site slot, including frozen projects whose slot has not yet been released, and compare that number with the site capacity included in your plan and top-ups. Removing one project does not by itself put every account at or below a six-site limit. 4. Note the date and time you removed the extra project. If the extra site capacity was removed from the OTTO Sites top-up before the renewal was created, that renewal may be eligible for review. If the top-up quantity was still active when the renewal was created, the charge can be valid for that period even if a project was deleted later. 📊 Find the detailed invoice breakdown Use these steps to see each amount: 1. Sign in to Search Atlas. 2. Open your account menu and go to Billing or Invoices. 3. Select the invoice that shows the unexpected charge. 4. Open the invoice and review its line items. Extra site capacity appears as an OTTO Sites top-up line, not as a fee named for an individual project. 5. Record the invoice number, charge date, and both amounts. The invoice line items are the detailed breakdown. A card statement usually shows only the total, so compare the statement with the invoice inside the platform before you dispute a charge. ✅ How refund reviews work Changing a domain or deleting a project does not automatically create a refund. Support compares the invoice with the OTTO Sites top-up and project history, including whether the extra capacity was still active, when the project was removed, and whether the top-up should already have ended. - Eligible for review: the extra OTTO Sites capacity was removed before the renewal charge was created, or the same OTTO Sites quantity was billed twice. - May not be refundable: the project was still active on the billing date, or the charge covers time already used during that period. Approved adjustments are returned to the original payment method. Timing depends on your card provider after the adjustment is issued. 💬 What to send so we can review faster If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat. Include the invoice number, the charge amounts, the date you removed the extra project, and the old and new domain names. Screenshots of the project list and the invoice line items help us confirm the change without another round of questions.

Last updated on Nov 11, 2026

💳 How to Clear a $180 Payout

💳 What clearing a $180 payout means A payout is money Search Atlas owes a publisher for posted publication work, or commission owed on a referral. Clearing $180 means staff release that publisher remittance, usually to the PayPal email on the publisher account. Referral commission is handled separately from bank details stored on the referral record. It is not an instant transfer, and it is not released from customer billing. You cannot force a payout from the public site or by sending payment details in a message. Publisher remittances and referral commissions are released by Search Atlas staff, not by a payout request inside the account. 📊 Check the payout before you ask Confirm these details so support can match the correct payment: - Amount: exactly $180, or the closest balance if fees changed the total. - Status: for a publisher remittance, pending, paid, unpaid, pay manually, or hold. PayPal may separately show pending, success, failed, unclaimed, returned, on hold, blocked, denied, refunded, or reversed. A referral commission invoice is pending, paid, error, canceled, rejected, failed, scheduled, or refunded. - Date: when the balance became available. - Payout method: for a publisher, the PayPal email saved on the publisher account. For a referral, the bank account details stored on the referral record. PayPal is not a referral payout method. - Account email: the email tied to the Search Atlas login that earned the payout. If the status already shows paid, the payout has been released. Allow the normal deposit time for PayPal or the bank. There is no second review to request in Search Atlas. 🛠️ Common reasons a payout stays pending A $180 payout is often held for a routine reason: - A publisher payout can be blocked when the PayPal email is missing or blocklisted, or while an enforced site-verification hold is active. An expired method or a name that does not match the account is not a payout hold. Missing referral bank details do not automatically pause a commission payment. - Billing or tax details are incomplete. - There is no payout date the balance must reach. Publisher remittances are scheduled for the upcoming Tuesday, end of day, and staff release them. The payment date on a remittance records when it was processed. - A previous payout attempt failed and needs a new method. - The account needs a quick ownership check before money is sent. These checks protect your payout. They are not a rejection of the $180 amount. 🚀 How to request clearance 1. Sign in to the Search Atlas account that owns the payout. 2. Open the publisher Remittances tab to see the amount, paid date, PayPal email, and transaction ID. Do not use customer billing. The affiliate dashboard shows referred accounts and their signup status, not a payout entry. 3. A publisher can update the PayPal email in publisher account settings, up to two changes in a year. Referral bank details are maintained by staff and cannot be updated from the affiliate dashboard. 4. Open the chat widget in the bottom-right corner of the platform. 5. Send a short message that includes the amount, the payout date, and the account email. Example: “Please review and clear my $180 payout from [date] on [account email].” 6. Stay in the chat so you can confirm any follow-up question from the team. Do not send full bank account numbers, card numbers, or passwords in chat. Share only what the agent asks for, and update sensitive payout details inside the billing screens. 💡 What happens after you request it A member of our support team will reply in the chat and either clear the payout or tell you the one item still blocking it. After clearance, the status should move from pending to processing and then to paid. Bank and wallet providers can take additional business days to show the deposit. If the same $180 entry was already paid, support will point you to that record instead of sending it again. ✅ If you need further assistance If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 11, 2026

🛠️ OTTO SEO Elementor Technical Evaluation

📋 What this evaluation covers This article explains how OTTO SEO behaves on an Elementor site: where changes are stored, how they sync, how to validate them, what Googlebot should see, how to export and measure results, how conflicts are avoided, how to use OTTO for research only, and how to leave OTTO safely. 💾 How OTTO persists changes Approved OTTO changes are stored in your Search Atlas project. Elementor continues to store page layout and visible content in WordPress. OTTO does not replace your Elementor library. For most SEO fields, such as title, meta description, canonical, and schema, OTTO adds the approved output when the page is served. Your Elementor design remains the source for body content you edit in the builder. Deployed OTTO changes are managed in your Search Atlas project. Editing a page in Elementor does not itself delete that project record. To stop applying a change, undeploy it and verify the live page after caches refresh. On WordPress, persistence and SEO-plugin sync settings can retain selected values after OTTO is paused or removed, so review those settings separately. Evidence: metasync/otto/class-metasync-otto-persistence-settings.php:5–16,39–54. 🔄 How sync works Sync has two directions: - From OTTO to the site: only approved or deployed items are applied. Draft recommendations do not change the live page. - From the site to OTTO: a fresh crawl reads the current Elementor URL, including content and head tags, so later recommendations reflect the latest page. Give one field one owner. If Elementor, your SEO plugin, and OTTO all set the same title or canonical, the live page can show duplicates or an unexpected value. After you publish in Elementor, recrawl that URL before approving a new OTTO change for it. ✅ How to validate a change Use this order: 1. In OTTO, confirm the item is approved and the target URL is correct. 2. Open the live URL in a private window and view the page source, not only the visual builder. 3. Check the title, meta description, canonical, and schema in the HTML head. 4. Clear any WordPress, Elementor, or CDN cache if the old tags remain. 5. Compare the live HTML with the approved value in OTTO. Elementor editor preview is not a reliable check. Preview can omit the front-end injection that visitors and Googlebot receive. 🤖 Rendering for Googlebot With the Search Atlas WordPress plugin’s server-side rendering or the Cloudflare Worker integration, verify that deployed OTTO tags appear in the initial HTML response. A browser-only installation may apply changes after JavaScript runs, so do not treat browser inspection alone as proof of what Google receives. In Google Search Console, use URL Inspection’s live test and inspect the tested page’s HTML, checking its title, description, canonical, and main content. Evidence: metasync/otto/otto\_pixel.php:83–92; otto-pixel-cf-worker/worker.js:2349–2355. If the inspected HTML is stale, purge the cache and request indexing again. Heavy Elementor animations do not block indexing by themselves, but the important text and tags must exist in the fetched HTML. 📤 Export and measurement Before a major edit or a move away from OTTO, export or copy the approved titles, descriptions, and other deployed values you want to keep. Use your project export where it is available, or record the values from the deployment list. Measure results on the same URLs over several weeks. Compare Search Console impressions, clicks, and indexed status, plus rank and traffic trends in Search Atlas. A single crawl, or one day of data, is not enough to judge the change. ⚠️ Conflicts with Elementor Common conflicts are duplicate titles, two canonicals, repeated schema, and a cache serving HTML from before deployment. An SEO plugin inside WordPress can also overwrite OTTO, or OTTO can overwrite that plugin. - Keep a single SEO plugin active, or turn off its meta output for URLs that OTTO manages. - Do not place a second title or meta description in an Elementor HTML widget. - Exclude the OTTO installation from optimization tools that strip unknown head tags. - After each Elementor publish, clear cache and recheck the source. 🔍 Research-only use You can use OTTO for research without changing Elementor. Leave recommendations in draft, and do not approve or deploy them. While deployment is paused, OTTO can still suggest keywords, metadata, and content ideas, but those ideas stay inside Search Atlas. If any installation is already active, pause deployment and confirm the live source no longer contains OTTO-managed tags before you treat the site as untouched. 🚀 Safe migration off OTTO Follow this path so rankings are not left without metadata: 1. Export or copy every deployed value you still want. 2. Add those values in Elementor or in one SEO plugin. Match titles, descriptions, canonicals, and schema. 3. Publish those pages and confirm the new tags in the HTML source. 4. Pause OTTO deployment for the site. Do not remove the installation yet. 5. Clear Elementor, plugin, and CDN caches. 6. Check key URLs for a single title, one meta description, and one canonical. 7. Remove the OTTO plugin or script only after the replacement tags are live. 8. Recheck the same URLs in Search Console and watch performance for several weeks. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 11, 2026

🛠️ Fix OTTO Manual WordPress Steps

📌 Why OTTO Asks for a Manual Change Some website updates are applied by OTTO when you deploy or enable them. On WordPress they are served by the OTTO pixel or the Search Atlas plugin. Sync to CMS can also copy supported fields, such as the title, meta description, and schema, into WordPress or into Yoast, Rank Math, or All in One SEO. OTTO does not show a separate set of manual steps for changes it cannot write. 🔍 Why the Listed Options May Be Missing Manual steps describe a common WordPress layout. Your screen can look different for several reasons: - User role: Editors and authors do not see every menu that administrators see. - Theme or builder: Elementor, Divi, Gutenberg, and classic themes place the same setting in different places. - Title, meta description, and schema fields often live in the Search Atlas SEO box, or in Yoast, Rank Math, or All in One SEO, rather than in core WordPress. - Hidden menus: A plugin or custom admin menu may rename or remove the option named in the steps. 🛠️ How to Apply the Change Anyway 1. Open the OTTO task and note the outcome, such as a new title, meta description, heading, or alt text. Focus on that result, not only the button name. 2. Sign in to WordPress with a user who can edit that page or post. Use an Administrator for Appearance, Settings, or the Search Atlas plugin. 3. Open the page or post named in the recommendation. For a sitewide Search Atlas setting, open the Search Atlas menu in WordPress. Appearance and Settings are only for theme and WordPress settings, and they require an Administrator. 4. Use the Pages or Posts screen to open the item, then use the editor or your page builder’s own search to find the matching field. The WordPress admin search box finds screens, not fields inside a page. 5. Enter the exact text or setting OTTO recommended, then update or publish the page. 6. Clear any cache plugin and refresh the live page to confirm the change is visible. 💡 Match the Step to Your Editor If a step tells you to open a menu you cannot find, use the closest match below: - Block editor: select the block, then check the right-hand settings panel. - Classic editor: use the main content box and the boxes under the editor. - Page builder: edit with the builder, open the element settings, and update the same field there. - SEO fields: on the edit screen, use the Search Atlas SEO box, or the Yoast, Rank Math, or All in One SEO box, rather than the main WordPress menus. ✅ After You Save the Change You do not mark the change complete in OTTO. If the live page already shows the recommended change, leave it. To make Search Atlas re-read the page, turn on Smart Crawl or run the site crawl. A new crawl may have to wait until 24 hours after the last one. 💬 If the Steps Still Do Not Match If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat. Include the OTTO task name, a short note about which step is missing, and whether you use a page builder or SEO plugin. That helps the team point you to the correct screen.

Last updated on Nov 11, 2026

🛠️ Fix OTTO Google Ads URL Parameters

🔍 What is happening OTTO can update the tracking template and final URL suffix on campaigns it creates in a connected Google Ads account. It adds a parameter such as otto_prod followed by a product ID, along with its own UTM parameters. Those values appear in the tracking template and the final URL suffix and can interfere with your existing attribution. Support confirmed the root cause. The issue is tracked as PPC-3547. OTTO no longer adds the parameter when a campaign is imported, and existing imported campaigns are cleaned up by a backfill. If the parameter is still present, use one of the two options below. 🛠️ Option 1: Remove otto_prod yourself You can clear the bad parameter on the affected campaigns without waiting for a platform change. 1. Open the affected campaigns in Google Ads Editor. 2. On those campaigns, remove otto_prod= from the tracking template. 3. Also remove otto_prod= from the final URL suffix on the same campaigns. 4. Post the changes from Google Ads Editor so the cleaned URLs go live. If you are not sure which campaigns were changed, open the chat widget and ask support for the campaign list. Do not add the parameter back after you remove it. ⚙️ Option 2: Reconnect Google Ads so we can remove it If you would rather have support remove the parameter, reconnect the Google Ads account first. 1. In the platform, open Settings from the profile menu, then go to Integrations. 2. Reconnect Google Ads. 3. Under Advertising, choose Google Ads and click Connect to authorize the account. 4. Then contact support in the chat widget and ask them to remove otto_prod=. With that permission in place, the team can remove it for you. 📊 After you clean the URLs - Check the tracking template and final URL suffix again and confirm otto_prod= is gone. - Watch attribution in Google Ads after the next clicks so you can confirm tracking is visible again. - Leave any remaining cleanup to the tracked fix (PPC-3547). Do not add the parameter back after it is removed. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 11, 2026

📊 Check OTTO Change Dates and Times

📊 What you can confirm yourself You can check when OTTO last deployed or removed SEO titles, meta descriptions, and link fixes by exporting the OTTO Work Summary for the site. It opens as a Google Sheet. Use the Deploy Changelogs tab, where each row is one deployment or removal. A later fix, such as a broken-link update, does not mean your title or meta description changed on that same date. 📄 Open the OTTO Work Summary export Open the OTTO Work Summary export for the site you are reviewing. Use that sheet as the source for deployment dates and the type of change, instead of guessing from the live page alone. - Find rows for title and meta description changes. - Find rows for other OTTO work, such as broken-link fixes. - Note the newest date for each type of change separately. 🕒 Read the times as UTC All times in the Deploy Changelogs tab are US/Pacific. Convert them to your local time before comparing them with a calendar date. For example, a late-evening Pacific timestamp can fall on the next calendar day in Sydney time. When you report a date to your team, say both the UTC time from the sheet and your local time so the dates are not mixed up. ⚙️ Check whether Autopilot is off Autopilot publishes selected new fixes without approval. In OTTO settings, under Automation, it is controlled separately for Title tags, Meta descriptions, Meta keywords, Heading length, Open Graph, and Twitter cards. Broken links are not in that list. If a type is off, OTTO does not publish new fixes of that type automatically, but you can still deploy them manually. Manual and automatic deployments are separate events. The Deploy Changelogs tab shows the change type and timestamp. A blank User cell can indicate an automatic deployment, but Autopilot settings—not the sheet alone—show whether title and meta updates are being published automatically. 🔗 Separate title and meta dates from link fixes OTTO can update broken links without touching the homepage title or meta description. Read each change type on its own row and date. - A broken-link fix can be the latest OTTO change even when the title and meta are older. - If the title and meta rows stop on an earlier date, those tags have not changed since that date. - Only title and meta rows in a given month count as title and meta changes for that month. Read the dates from the current Deploy Changelogs tab after converting its US/Pacific timestamps to local time. A broken-link row can be the newest change while the latest homepage title and meta description rows remain on earlier dates. Only the rows for each field establish when that field changed. ✅ How to answer an exact date question 1. Export the OTTO Work Summary. 2. Convert the Deploy Changelogs times from US/Pacific to your local time. 3. Record the latest title change, the latest meta description change, and the latest other change, such as broken-link fixes. 4. In OTTO settings, under Automation, check the Autopilot switch for each change type. A type that is off is not being published automatically, while manual deployment remains available. 5. If a tag has no newer deployment row in the export, OTTO has not recorded a newer change to that tag. This does not by itself prove the live page is unchanged, so check the live page before relying on it. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 11, 2026

⚙️ OTTO Autopilot Deploy and Rollback

🔍 Why autopilot can look on while Autopilot is Off MCP can show autopilot_active as true even when Autopilot is Off in your settings. Developers confirmed these are different controls. autopilot_active is the background crawl switch. It does not mean fixes are being auto-deployed. The Off settings on each fix type are what control auto-deploy. If those fix types are Off, Autopilot is not approving and publishing those fixes for you. 📅 What deployed the 6 November items The items that deployed on 6 November were not necessarily from a new OTTO analysis or a fresh Autopilot approval. They can also come from a manual or API action, which is recorded as source api, or from a programmatic change. Autopilot's own deploys are recorded separately as autonomous, and those only happen during a new analysis for fix types with auto-deploy on. The log stores that source, but the dashboard does not show it, so you cannot see which path created that batch. 🔗 Were the WILDFIRE links removed Turning WILDFIRE off removes every WILDFIRE link for the project, in both directions, not only the INITIAL ones. Approved links are unapproved and the rest are returned to INITIAL, except links that were denied. You do not need to turn WILDFIRE off again for links that removal already returned to INITIAL. 📋 How to review what changed The arrow at the top left is Back to Sites List. It returns you to the sites list. It does not open deployment history. - OTTO Suggestions is an export, not a history view. Open the header menu, choose Export, then OTTO Suggestions, and the suggestion list is emailed to you as a download. - Work Summary is an export in the same Export menu. Choosing it downloads a summary of the work. It does not open an on-screen change log. Use the suggestion table to see which fixes are currently deployed, or download OTTO Suggestions or the Work Summary from the Export menu. None of these names the source of the 6 November batch. The source is stored on the deployment log, but it is not shown in the dashboard. ↩️ How rollback fits in Roll back from the suggestion table, not from an export. Use the rollback control on a deployed row, or Roll back all deploys in this section from the section menu. The bulk Roll back button asks you to confirm before it undeploys. There is no deployment-history screen for this, and OTTO Suggestions and Work Summary only download files. 💬 If you still need help If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 11, 2026

✅ Confirm Project Migration and Quota Removal

✅ What this covers This article explains how Search Atlas confirms that a project has been turned over to a client, and what that means for the original account’s project count and OTTO quota. 🔄 How migration is confirmed Handoff is confirmed by our team, not by a setting you change yourself. Support looks up the project domain and checks internally whether the migration was completed as previously requested. When that internal check shows the migration is done, the project has been turned over. You do not need to take extra steps on the original account to “release” it. 📊 How quota is affected Once the project is no longer deployed on the original account, its OTTO Sites usage should be removed from that account. A project that is still frozen and inside the 14-day quota hold can continue to count until that hold ends. It should no longer count against the original account’s OTTO Sites quota. OTTO Sites quota follows the account that owns the project. After a successful handoff, the original account should not keep the project in its OTTO Sites count unless the project remains in its frozen quota-hold period. 🛠️ If it still looks counted If the project still appears on the original account or still seems to use quota after you believe the handoff is complete: 1. Note the project domain so support can look it up. 2. Open the Intercom messenger and ask us to confirm whether the migration was completed and whether the project is still deployed on the original account. 3. If we need to see what you still see on screen, we may ask you for a screen recording. We will confirm the migration internally. If the project is no longer deployed on the original account, it should be removed from that account’s OTTO Sites quota unless it remains in its frozen quota-hold period. 💬 Need help If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 11, 2026

🛠️ Restore Promotional OTTO Site Slots

📌 What this article covers Some annual promotional plans add one extra OTTO site on top of the plan allowance. After a provisioning error, the account can show one fewer slot than you paid for. This article explains how to confirm the mismatch and how our team restores the missing allocation so you can add the extra client site. 🔍 Check the slot count you see Before you contact support, confirm what the platform is showing: 1. Open your Search Atlas account and go to the area where you add or manage OTTO sites. 2. Note the number of sites already connected and the number of slots the plan still allows. 3. Compare the total shown under Billing, Plan Limits, OTTO Sites with the plan plus the promotional site you purchased. The total should be the plan allowance plus one promotional site. 4. If the total is one below the plan allowance plus the promotional site, or adding a site is blocked at that lower total, the promotional allocation was not applied correctly. A common example is an annual promo that should add one OTTO site while the account is still on the lower plan allowance. That is an entitlement issue. Removing a client does not fix a site that was never provisioned, and a Deep Frozen site keeps its slot for 14 days. ⚙️ Why the extra slot can be missing Promotional site counts are applied when the plan is provisioned. If that step fails or only part of the promo is written to the account, billing can show the annual promo while OTTO still uses the lower slot count. Refreshing the page, signing out, or reconnecting an existing site does not restore a slot that was never provisioned. - Paid promo: Your order included one extra OTTO site. - Account view: Billing, Plan Limits, OTTO Sites shows the lower plan total without the extra promotional site. - Fix: Support corrects the slot allocation on the account. ✅ What to send so we can correct it Have these details ready. They let support match the promo to your account and restore the fifth slot: - The account or workspace name where OTTO is used. - The plan or promo name, and that it is an annual promotion for one extra OTTO site. - The slot count you see now, for example four available or four total. - Whether you are blocked from adding a fifth client site. - The approximate purchase or renewal date, if you know it. You do not need to remove existing client sites to receive the missing promotional slot. Support restores that slot. A site you remove normally frees its slot immediately, unless it is Deep Frozen, in which case the slot stays held for 14 days. 🚀 After the allocation is restored Once the correction is applied, refresh Billing, Plan Limits, or the OTTO SEO Automation page. The account should show the plan allowance plus the extra promotional site. You can then add the next client the same way you added the others. If the total is still one short after you refresh, tell support in the same chat so they can recheck the entitlement. Restoring slots does not change content already published on connected sites. It only updates how many OTTO sites the promotional plan allows. 💬 When to contact support Contact support if a paid promo for five OTTO sites shows only four, if you cannot add the next client, or if the count is still wrong after a refresh. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 11, 2026

🛠️ Fix Campaigns Using Wrong Brand Vault Assets

🔍 Why the campaign uses the wrong assets A local Google search campaign builds its copy and sitelinks from the OTTO PPC Business and Product, including the business name, website, description, and crawled page content, not directly from Brand Vault. Brand Vault details are copied onto the Business only when you link the brand. Editing the vault afterward does not change a campaign that was already generated, and an old campaign keeps the assets it was created with. Sitelinks that look locked are campaign assets, or account-level assets already stored in the Google Ads account. Updating only the ad preview does not replace them. Edit or remove them on the campaign, or in Google Ads if they belong to the account. ✅ Confirm the Brand Vault is current Before you create the campaign, check the business name, website, description, and location on the OTTO PPC Business. Saving changes in Brand Vault alone does not update that business or the campaign. 1. Open the Brand Vault for the website, or open the OTTO PPC Business that is linked to that vault. Locations are listed inside the vault and as targeting on the business, not as separate vaults. 2. Check the business name, website, phone, address, descriptions, and sitelinks. 3. Remove test links, placeholder text, and assets from old experiments. 4. Sitelinks are not stored in Brand Vault. They are generated from the business and product pages when the campaign is built, or reused from sitelinks already on the Google Ads account. Add or edit them on the campaign. Make sure you are working in the live project, not a test property or an older duplicate of the same business. 🚀 Create the campaign from the updated vault 1. Create a new Search campaign for the correct business and product. Do not use the old campaign's retargeting copy, and do not expect a duplicate of the old campaign to pick up new business details. 2. Choose the OTTO PPC Business that is linked to the correct Brand Vault and website. Set the campaign's location targeting on that business. You do not pick the vault again during campaign generation. 3. Generate the campaign after the business name, website, description, and location are saved on the OTTO PPC Business. Saving the Brand Vault does not by itself update the campaign. 4. Review the campaign preview. The business name, descriptions, and sitelinks should match the business and product used to generate the campaign, not the latest unsynced Brand Vault edit. Regenerating an existing campaign rebuilds its copy from its own business and product. It does not pull assets from another campaign. Assets copied into a retargeting campaign stay on that campaign until you edit them there. To leave a test setup behind, create a new campaign and pause or remove the old one. 🔗 Replace sitelinks you cannot delete If you cannot remove a sitelink from the campaign, check whether it is an account-level sitelink in Google Ads. Remove or replace it there. Brand Vault is not the source of the link. - Edit or remove the sitelink on the campaign. If the same link appears on every campaign in the account, edit the account-level sitelink in Google Ads instead. - Return to the campaign and generate its sitelinks again, or edit them directly. Regeneration uses the business and product, not the Brand Vault. - If the old links remain after you edit the campaign, they are stored on that campaign or on the Google Ads account. Create a new campaign if you want a clean set, and leave the old campaign paused or delete it if it is still a draft. - Confirm the preview shows only the current links before you publish. Editing sitelinks in Google Ads changes the account that Search Atlas syncs from. Editing Brand Vault does not update those sitelinks. Change campaign sitelinks in the campaign, and change account-level sitelinks in Google Ads. 📋 Check before you publish - Use the OTTO PPC Business that is linked to the live website's Brand Vault, and set that business's location targeting to the live location. The vault, the business, and the Google Business Profile location are linked separately. - No test campaign is selected as the source or template. - Every sitelink URL, label, and description is current. - The preview matches the vault with no leftover test copy. 💬 Get help in the platform If the new campaign still uses old assets after you update the Brand Vault and create a fresh campaign, If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat. Include the website, location, campaign name, and which sitelinks are wrong so the team can trace the asset source.

Last updated on Nov 11, 2026

🛠️ Apply Website Updates Manually

🛠️ What this article covers Some OTTO recommendations can be deployed automatically once OTTO is installed and engaged on the site. If OTTO is not installed or not engaged, the control says Enable instead of Deploy. If a change is not deployed, copy the suggested value and add it in your CMS or page editor yourself. This article explains why a change may not go live and how to apply it yourself. 🔍 Why a change may not transfer A recommendation stays a suggestion in OTTO until you deploy or enable it. It will not change the live page until OTTO is installed and engaged. - The site, CMS, or installation script is not connected, or the connection expired. - OTTO can deploy a recommendation on any crawled page once it is installed and engaged. If the pixel or plugin is not serving that page, copy the suggested value and add it in your CMS or page editor. - You do not have permission to edit that page in your website platform. - A cache, CDN, or security plugin is serving an older version of the page. - A generated or edited suggestion stays under Not Deployed until you deploy or enable it. It is not a separate approved or unpublished state. If any of these apply, use the manual steps below. Search Atlas support cannot log in to your website and publish changes for you. ✅ Before you edit your site 1. Open the OTTO project, select the issue type, and find the page URL in that table. 2. Check the status. Deployed means OTTO is already applying it. Not Deployed means you still need to deploy or enable it, or copy it into your CMS. 3. Copy the exact title, meta description, heading, content, or other field shown in Search Atlas. 4. Note the live page URL so you edit the correct page. 5. Check that you can edit that page in your CMS or website builder. 🚀 How to implement the update by hand 1. In Search Atlas, open the recommendation and copy only the fields you plan to change. 2. Sign in to your website platform and open the same page. 3. Paste each value into the matching field. For example, put the meta title in the SEO title field, not in the visible page heading, unless the recommendation says to change the heading. 4. Save or update the page, then publish it if your platform keeps drafts separate from the live site. 5. Clear the page cache in your CMS, caching plugin, or hosting panel if the old version still appears. 6. Open the live URL in a private browser window and confirm the new text is visible or present in the page source for meta fields. 7. Return to OTTO and run Smart Crawl, or recrawl the site in Site Audit. When the new crawl finds that the page already matches, the suggestion moves to Fine Pages and is no longer listed as an open issue. There is no button to mark the task complete. 📊 How to confirm it worked - The live page shows the new heading or body content. - View source or your SEO plugin shows the new title and meta description. - Hard-refreshing or using a private window does not bring back the old version. - Search Atlas no longer lists that item as waiting for implementation after the next check. Search engines may take time to recrawl the page. A successful save on your site does not mean rankings change immediately. 💡 If it still does not update - Re-copy the value and check for extra spaces or an unfinished draft. - Confirm you edited the canonical URL, not a duplicate or staging page. - Ask your developer or site admin to allow edits if a template locks the field. - Reconnect the site in Search Atlas if automatic publishing is supposed to be available, then try publishing again before editing by hand. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 11, 2026

⚠️ Manual OTTO WordPress Changes Not Possible

⚠️ Why the manual options are missing Some OTTO changes are applied with Deploy or Enable in the OTTO project. If a help step names a button you do not see, that control is not part of this screen. It does not mean the recommendation cannot be completed, and it does not mean you missed a hidden menu. OTTO suggests SEO updates and, once the site is installed and engaged, deploys supported updates through the OTTO script, the WordPress plugin, or a Cloudflare Worker. A change is not served when that installation is missing, broken, or disengaged. Sync to CMS can also write supported fields, such as title and meta description, into the connected CMS. 🔍 Check the connection before you edit 1. Open the correct website project in Search Atlas. 2. Open the site in OTTO and check its installation status. If WordPress is not installed, disabled, or needs a reconnect, use Install or Reconnect in OTTO. If suggestions are out of date, turn Smart Crawl on so OTTO analyzes the site again. 3. Open the recommendation again and read its control. It says Deploy before you apply it and Deployed after, or Enable and Enabled when the site is not installed and engaged. A row can also say Review or No terms, or show a spinner while OTTO is still generating the suggestion. 4. Reload the page in Search Atlas. A stale screen can still show old steps after the action was removed. 5. In WordPress, confirm you are an Administrator or Editor and that you can open the same page. If the WordPress plugin, script, or Cloudflare Worker is not installed and engaged, OTTO cannot serve the change. Reconnect or reinstall first. An existing recommendation still needs Deploy. It does not deploy by itself just because the site is connected again, unless Autopilot is on for that type. 🛠️ What you can do when transfer fails - Use Deploy in OTTO to apply the suggested title, meta description, heading, or other supported change. If you would rather edit the page yourself, copy that suggested text into the matching field in WordPress, save the page, and clear your cache plugin. The OTTO suggestion can remain until you deploy or roll it back and Smart Crawl checks the page again. - Do not expect a separate manual-apply button. Schema that needs attention shows Review. Other technical fixes, including redirects and sitewide settings, use the same Deploy or Enable control, or Autopilot when it is turned on for that fix. - Do not force a missing control. Browser extensions, a narrow window, or an old cached page will not create a button that the product does not offer for that change. - After you publish in WordPress, return to the OTTO project. The suggestion remains until you deploy or roll it back, or until Smart Crawl runs again and no longer finds that issue. Editing the page in WordPress does not by itself remove the OTTO suggestion. 📋 Common reasons a change will not transfer - The Search Atlas WordPress plugin (Search Atlas SEO - OTTO AI SEO Automation for WordPress, also called MetaSync) can be missing, disabled, waiting for sign-in, or not engaging. Those states appear on the OTTO site, and the plugin can also be deactivated or deleted in WordPress. - The page is a draft, password protected, or not the URL OTTO is optimizing. - A page builder, SEO plugin, or theme overwrites the field after you save. - Caching or a CDN is still serving the old version. - The recommendation type cannot be applied manually. 💳 If you are considering canceling A missing manual button is not always a failed account. Many customers can still publish the suggested on-page edits directly in WordPress. If the connection cannot be restored or the changes you need are not supported, you can ask support to review the site before you cancel. Plan cancellation is done in Search Atlas under Billing, where you choose Cancel Your Plan and confirm. OTTO installation or recommendation buttons do not manage billing. 💬 Get help in the platform If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat. In your message, include the website URL, the OTTO recommendation name, and what you expected to click. A screenshot of the screen where the option is missing helps the team confirm whether the change can be deployed, done in WordPress, or is not supported.

Last updated on Nov 11, 2026

⚙️ Resolving OTTO Deployment Issues and Plan Cancellations

🔍 Why OTTO Deployment Prompts Manual Updates OTTO SEO applies approved page optimizations through the Search Atlas WordPress plugin or the OTTO pixel script. If an install or deployment does not go through, use the project's installation guide or deployment check. You do not need to apply those optimizations as manual WordPress edits, and you can cancel the subscription from Billing if you do not want to continue. - Missing or inactive plugin: the Search Atlas WordPress plugin is deactivated, outdated, or not connected because its plugin auth token is missing or rejected. An administrator can refresh that token in the plugin settings. - Installation can fail for other reasons, including an unreachable site, a Cloudflare or DNS setup problem, or more than one OTTO installation. Run Installation Diagnostics on the project to see the actual result. - OTTO does not ask you to copy individual recommendations into WordPress theme or custom-field settings. Use the WordPress plugin or the OTTO pixel, then review the deployment result in OTTO. 🛠️ Troubleshooting Missing Options in WordPress If the manual instructions guide you to settings or menus that do not appear in your WordPress dashboard, follow these verification steps: 1. Check user permissions: administrators can always open the Search Atlas WordPress plugin. Other roles, including Editor and Author, can open it only when an administrator grants their role under plugin access settings. 2. Verify Plugin Version: Navigate to Plugins > Installed Plugins in WordPress. Confirm the Search Atlas plugin is updated to the latest release. 3. Clear Server and Site Cache: Aggressive caching can prevent dashboard menu items from rendering properly. Purge your site cache, CDN cache, and browser cache. 4. If a security plugin blocks WordPress REST API requests, the Search Atlas plugin cannot communicate with Search Atlas. Check that plugin's REST API or firewall rules, then run Installation Diagnostics again. 🚀 Alternative: Using the Header Pixel If your WordPress setup conflicts with the plugin, you do not need to apply changes by hand. You can install the OTTO Header Script instead. This single line of JavaScript handles deployments dynamically without touching WordPress page templates: 1. Open your Search Atlas dashboard and navigate to OTTO SEO. 2. Open the OTTO project and its installation guide. Select Manual Installation, then Code Snippet. 3. Copy the provided code snippet. 4. Paste the script into the <head> section of your site using your theme settings or a header injection plugin. 🛑 How to Cancel Your Plan If you do not want to continue, an account admin can cancel from Billing. Open your profile menu, select Billing, then Plans & Top-ups. 1. Log in to the Search Atlas platform. 2. Click your profile avatar in the navigation bar and select Billing. 3. On the Billing page, open the Plans & Top-ups tab. 4. Select Manage Subscription, open the plan's action menu, and select Cancel. Confirm Cancel Your Plan? when prompted. 5. Follow the on-screen prompts and confirm the cancellation. You will not be billed again. Access normally stays live until the end of the current billing period, but an overdue subscription can end immediately. 💬 Contact Search Atlas Support If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 11, 2026

📦 Export Data from a Deep-Frozen OTTO Site

❄️ Why a deep-frozen site cannot be exported A deep-frozen OTTO project cannot be exported while it stays frozen. There is no way to export data from the project unless you unfreeze it first. Unfreezing is required for any export, including a full work summary. Plan the unfreeze when you are ready to pull the reports you need. ⏱️ What happens to the 14-day clock Unfreezing restores the project to active status immediately. It releases any freeze hold and allows you to run exports, without starting or resetting any 14-day timer on the active site. If you unfreeze only to export and then freeze the project again, a new 14-day quota-hold period begins from the date of refreezing. 📄 What to export after you unfreeze After the project is unfrozen, use these reports: - Work Summary is the most complete deployments report available for the project. - Report Builder can add related local and metrics data alongside that summary. Start with the Work Summary for the fullest view of deployments, then use Report Builder if you also need related local and metrics data. 📌 If content looks missing Exports only include what is still available on the unfrozen project. If the project was removed, some items, such as GBP posts, may no longer be available to export. Unfreezing does not restore content that was already removed with the project. ✅ Steps to get your data 1. Unfreeze the deep-frozen OTTO project. Export is not available until you do this. 2. Once the project is unfrozen, it returns to active status immediately so you can access and export your data. 3. Open the Work Summary and export it. This is the most complete deployments report. 4. If you need related local and metrics data, add it through Report Builder. 5. Freeze the project again only after you have saved the exports you need, keeping in mind that refreezing will initiate a new 14-day quota hold for that slot. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 12, 2026

🎁 Why Your Complimentary OTTO Site Is Missing

🎁 What a complimentary OTTO site means A complimentary OTTO site is an extra site slot added to your plan at no charge. It lets you connect one additional website to OTTO without buying another paid site. The slot belongs to the account that received the offer. It is not a separate login, a discount code, or a credit you enter at checkout. 🔍 Why you may be asked to pay If the free slot is not on the customer account you are signed in to, that account’s OTTO site limit does not include it. Once the sites already allowed on this account are in use, OTTO treats the next site as a paid add-on and opens the OTTO Sites top-up, where you pay to add site quota. - The offer was discussed but never applied to the account. - The slot was added to a different customer account, which may use a different email address. Signing in as another team member on this account does not change which account received it. - The complimentary site was already used on another domain. - A complimentary OTTO site grant does not expire on its own. If the slot is still active and unused, you can add the site later. The slot remains until Support removes it. - You are signed in to a different Search Atlas account than the one that received the offer. 🛠️ Check your account before you pay 1. Confirm you are signed in with the same email that received the complimentary site. 2. Open Account, then Billing, and review the OTTO section. The Sites row shows how many OTTO sites are used and the total number allowed, such as “2 used of 5.” 3. In OTTO, open All Sites and review the connected sites. If the free slot is already used, removing or uninstalling that site does not free the slot immediately. The removed site stays in Deep Freeze and continues to count toward the limit until the freeze period ends. 4. Refresh the page, or sign out and back in, so the latest quota loads. 5. Do not complete checkout if you believe a free slot should still be available. Paying adds a separate paid site to your plan. 📋 What to send in chat Have these details ready so support can match the offer to your account: - The email address on the account. - The date you were told the extra site was added, and who confirmed it if you remember. - The domain you are trying to add. - A short note that checkout is asking for payment and the free site is not visible. Support can confirm whether the slot is active, already used, or on another customer account. A complimentary OTTO site grant does not expire. Support can apply a valid offer that was not added to the account. 💬 Contact support If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 12, 2026

🛠️ Fix a Stuck Domain Knowledge Network Rebuild

📌 What a stuck rebuild means The Domain Knowledge Network is the map OTTO builds from your site so recommendations stay accurate. While a rebuild is running, the Domain Knowledge Network section shows "Preparing your knowledge network". If it makes no progress for 30 minutes, that screen changes to "This is taking longer than usual" and offers a Retry button. The project still exists, and the current network stays in place until a rebuild finishes. 🔍 Common reasons it stays stuck - A rebuild that is still running blocks a new one. If the rebuild never finishes, it stops blocking after it has made no progress, and you can start it again with Retry. - The site was slow to crawl, blocked the crawler, or returned many errors. - The domain, protocol, or trailing slash does not match the project URL. - Several rebuilds were started close together on the same project. - A temporary platform delay left the status unchanged after the work finished. ✅ Check the project before you retry 1. Open the affected project and confirm the domain matches the live site, including https and the correct host. 2. Note the current rebuild status and how long it has been unchanged. 3. Confirm the site is publicly reachable and is not blocking crawlers. 4. Avoid starting another rebuild until you finish the steps below. 🚀 Clear a stuck rebuild 1. Refresh the project page. If the Domain Knowledge Network table and overview are showing instead of "Preparing your knowledge network", the rebuild has finished and no further action is needed. 2. Wait at least 30 minutes if the rebuild started recently. Large sites can take longer. 3. If the screen still says "Preparing your knowledge network" after that wait, refresh the project page. When it changes to "This is taking longer than usual", choose Retry once. Do not use Sync with Brand Vault for this, because that rebuilds a finished network and replaces it. 4. Leave the project idle while the new job runs. Do not click rebuild again. 5. Return later and confirm the "Preparing your knowledge network" screen is gone and the Domain Knowledge Network table and overview are showing. ⚠️ If it stays stuck after one retry Do not queue repeated rebuilds. Extra attempts can keep the same job blocked. Check that the homepage loads, DNS points to the correct site, and important pages are not behind a login or hard block. If the domain recently changed, confirm the project URL was updated before you retry. Share the project domain, the stuck status text, and roughly when the rebuild started when you contact support. That lets the team inspect the job without another customer-side retry. 💬 Contact support If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 12, 2026

🛠️ Restore Accidentally Undeployed Page Schemas

🔍 What Happened Sometimes a sitewide undeploy removes page schemas from pages that should still have them. In OTTO, this happens when you use Roll back all on the Page-level schema category, which rolls back every page in that category rather than only the pages you meant to change. Your schemas are not deleted. Their deployment is switched off, so they stop appearing on your live pages. This article explains how to find the affected pages and turn their schemas back on safely. ✅ Before You Begin Gather the information you need before making any changes. This will help you restore only what was affected. - Site name or domain: Confirm which site was affected. - Approximate time: Note when the sitewide undeploy happened, as closely as you can. - Intentional undeploys: List any pages you removed schemas from on purpose, either before or after the accidental change. - Later updates: Note any schema changes or recoveries made after the incident, so they are not overwritten. 🛠️ Steps to Restore Schemas 1. There is no activity or change history in the product that shows the sitewide undeploy event and its time. Use the Page-level schema category instead, and open the Not Deployed tab to see schemas that are currently off. 2. You cannot see which schemas were active just before the undeploy. In Page-level schema, use the Deployed and Not Deployed tabs to see which schemas are on or off now, and confirm the affected pages against your own list. 3. Remove pages you meant to keep off. Exclude any page you undeployed on purpose, both before and after the incident. 4. Check for later recoveries. If someone already restored a page after the incident, leave it as it is. 5. Redeploy the schemas on your confirmed list. Open each affected schema and choose Deploy this Schema, or select those schemas and use Enable. The button says Enable instead of Deploy until the OTTO SEO Widget is installed and engaged. 6. Verify the results. Check a sample of restored pages to confirm the schema appears correctly and that pages you meant to keep off remain off. 🛡️ Protecting Intentional Undeploys Restoring schemas should never undo decisions you made on purpose. Pages removed from schema deployment for valid reasons, such as being retired, being in testing, or having a different markup strategy, should stay undeployed. Always check your records before restoring a page. 🚫 Avoid Blanket Deployments Do not redeploy schemas across the entire site as a shortcut. A blanket deployment can turn on schemas for pages that were intentionally left off, and it can overwrite recent fixes or custom settings. Restoring only the confirmed list of affected pages is safer and keeps your site accurate. 💡 Preventing Future Issues A few habits can reduce the risk of accidental sitewide changes: - Double-check scope before running any action that affects multiple pages. - Test on a small set of pages before applying changes sitewide. - Keep notes on intentional undeploys so they are easy to find later. - Review deployment history regularly, especially after team changes or bulk edits. 💬 Getting Further Help If you need the exact list of affected pages pulled from audit logs or backups, or you are unsure which pages to restore, we can help. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat. To speed things up, include your site name, the approximate time of the undeploy, and any pages you want to keep undeployed.

Last updated on Nov 12, 2026

🔄 Sync WordPress to OTTO SEO

🔗 What MetaSync does The WordPress plugin is listed as "Search Atlas SEO - OTTO AI SEO Automation for WordPress." Its admin menu is "Search Atlas." When the connection is healthy, Search Atlas can read the site and apply approved OTTO changes. In WordPress, a healthy connection shows "Synced," which means the heartbeat reached Search Atlas and the API key and OTTO UUID are stored. "Not Synced" means the heartbeat is not responding, and "Warning" means an API key exists but the OTTO UUID is missing. Search Atlas must also match the site to an OTTO project. If it cannot, the connection fails with "Domain not found for customer or no Otto Project found." ✅ Before you connect - You are an administrator on the WordPress site. - The correct project is open in Search Atlas and the site URL matches the live WordPress address, including https and www if you use them. - WordPress, your theme, and MetaSync are updated. - Security, cache, or firewall plugins are not blocking Search Atlas from reaching the site. 🛠️ Connect the plugin 1. In WordPress, go to Plugins, install "Search Atlas SEO - OTTO AI SEO Automation for WordPress" if it is not already there, and activate it. 2. Open the MetaSync settings screen. 3. You do not copy anything from Search Atlas. In WordPress, click "Connect to Search Atlas." A popup opens the Search Atlas sign-in page and sends the site address automatically. Allow popups if the window does not open. 4. Sign in through the popup and select the OTTO project for this site. Search Atlas returns the API key and OTTO UUID automatically. WordPress then shows "Synced" when the heartbeat succeeds. If the API key arrives without an OTTO UUID, it shows "Warning" and "Partial Connection (Missing OTTO UUID)." Use "Complete Authentication Setup" or "Re-authenticate with Search Atlas" to finish it. 5. Return to the same OTTO project in Search Atlas. Its installation status updates from the plugin heartbeat and from Search Atlas checks. It is not refreshed by a button. Depending on the result, it can say "OTTO SEO is Engaged (WP)," "Connecting — waiting for plugin," "Plugin Detected — Connection Needed," "Connection Incomplete," or "Connection failed." 📊 Confirm the sync Check both places, not only WordPress. In Search Atlas, the project should show a successful WordPress installation state such as "OTTO SEO is Engaged (WP)," not a pending or failed connection state. In WordPress, Search Atlas should show "Synced," not "Not Synced" or "Warning." The plugin does not display the project domain, so compare the WordPress site address with the project URL yourself. If either side disagrees, the sync is not complete. 🔍 Fix connected in WordPress but not working in Search Atlas This mismatch is usually a URL, project, or blocked-request issue. Work through these checks in order: 1. Search Atlas ignores www, the URL scheme, and a trailing slash when it matches the WordPress site to an OTTO project. The connection is rejected when no OTTO project exists for that domain, with the message "Domain not found for customer or no Otto Project found." A genuinely different hostname will not match. 2. Use one project. Disconnect MetaSync, then reconnect it to the project that should own this domain. Do not leave the plugin tied to an old or duplicate project. 3. Refresh both sides. Save MetaSync again, then reload the Search Atlas project page. Allow a short time for the status to update. 4. Clear caches. Purge any WordPress, plugin, or host cache, then recheck the status. 5. Allow Search Atlas through security tools. Temporarily pause a firewall, bot blocker, or maintenance mode and test again. If the status becomes working, add an allow rule and turn protection back on. 6. Reinstall cleanly if needed. Deactivate MetaSync, delete it, install the current version, activate it, and connect it again to the correct project. 💡 After the status is working Open OTTO for the project and review its recommendations. Deploy or sync only the changes you have approved. Do that from the OTTO project in Search Atlas, not from a suggestions list in WordPress. If the site's hostname changes to a domain owned by a different OTTO project, disconnect the plugin and connect it to the correct project, then confirm that WordPress shows "Synced" and Search Atlas shows the WordPress installation as engaged. 💬 Still not syncing If WordPress stays connected and Search Atlas still says not working after these checks, gather the site URL, the project name, a screenshot of the MetaSync status, and a screenshot of the Search Atlas status. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 12, 2026

⏳ Wait for crawl before OTTO verification

🔍 Why the pixel can look missing If the OTTO script is already in the of your Shopify store and it loads in the browser, the setup wizard can still say it cannot see OTTO or identify a platform. That message does not always mean the script is missing. OTTO installation verification is separate from the full site crawl. You can retry verification while the crawl is running; you do not need to wait for every indexable URL to be crawled. ⏳ What to do while the crawl is running Do not treat a failed check during an active crawl as a broken install. Leave the OTTO script in place and wait until the crawl of your indexable URLs is finished. Larger catalogs take longer, so a store with thousands of URLs may stay in this state for a while. - Confirm the script remains in the page head and still loads in the browser. - Avoid removing or replacing the script only because the wizard has not detected it yet. - Wait until the site crawl is complete before you try validation again. ✅ Re-scan after the crawl finishes Return to the OTTO installation flow and click Check again to retry installation verification. You can do this while the site crawl is running. Review the new result to confirm whether OTTO is detected. 1. Confirm the crawl of your indexable URLs has finished. 2. Return to the OTTO setup wizard. 3. Run the detection check again so the platform can re-scan and validate the script. 4. If detection succeeds, the installation is complete and no further script change is required. 💬 If it still is not detected If the crawl has finished and a new scan still cannot see OTTO, contact support with your site URL and a note that the script is live in the head. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 13, 2026

🛠️ Fix a Stuck OTTO PPC Campaign Import

🔍 What Is a Stuck Campaign Import? When you start the OTTO PPC campaign-import flow, Search Atlas fetches available campaigns and products in the background. The business status is importing\_campaigns while the import is being prepared, and it normally advances when processing completes. An import may be stuck when the business remains in the import workflow without progress and its product and campaign counts remain zero. Check the status and counts before contacting Support. ⚠️ Signs Your Import Is Stuck - The profile status has shown importing_campaigns for a long time without changing. - The number of imported products and campaigns is still 0. - The status does not change after you refresh the page or log out and back in. - While the import is still being fetched, **Continue Setup** is disabled. If it remains unavailable without progress, contact Support rather than repeatedly restarting the import. ⏱️ How Long Should an Import Take? Import time depends on the size of your ad account. Small accounts often finish within a few minutes. Large accounts with many campaigns, ad groups, and products can take longer. Before treating the import as stuck, consider these points: - If the import started only a few minutes ago, give it more time. - If either count is above zero, some import data has been received. Refresh and monitor the status; contact Support if the status remains unchanged for an unusually long time. - If the status and counts remain unchanged for an unusually long period, the import may be stuck and should be reviewed by Support. ✅ Steps to Try Before Contacting Support These checks solve many import problems and take only a few minutes. 1. Refresh the page. Do a hard refresh in your browser, or log out and back in, to make sure you are seeing the latest status. 2. Check your ad account connection. Confirm the ad account you connected is the correct one and that the connection has not expired or been disconnected. 3. Check account permissions. The login you used to connect must have access to the ad account. If it has limited or read-only access, the import may not be able to read your campaigns. 4. Confirm the ad account has data. If the account has no active or paused campaigns, there may be nothing to import. 5. Avoid repeated import attempts. Starting several imports for the same profile can cause conflicts and may make the lock harder to clear. 6. Wait and recheck. If the account is large, check again after some time to see whether the counts have started to change. 🔒 Why You Cannot Clear the Lock Yourself The lock that keeps a profile on importing_campaigns is managed by a background process on our side. It is not a setting you can change in the platform. If the process stops unexpectedly, the lock can stay in place even though no import is running. In that case, our support team needs to review the profile and manually reset the import so you can try again. 💬 What to Send to Support Giving us the right details up front helps us resolve the issue faster. When you message us, please include: - Your business name and, if you have it, your business ID (for example, 15677). - The status shown on the profile (for example, importing_campaigns). - The current counts, such as 0 products and 0 campaigns. - Roughly when the import started and how long it has been stuck. - The ad account you are trying to import from. - Any error message you saw, or a screenshot of the profile status. - A clear request, such as: please reset the background import for my profile. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat. 🔄 After the Reset Once support confirms the import has been reset, follow these steps: 1. Refresh the platform and open your business profile. 2. Confirm the status is no longer importing_campaigns. 3. Check that your ad account is still connected and reconnect it if needed. 4. Start the import again once, and give it time to finish. 5. Check that the product and campaign counts start to increase. If the import gets stuck again after a reset, tell us in the chat. Include what you did after the reset so we can look for the underlying cause. 💡 Tips to Avoid Import Problems - Connect the ad account using a login that has full access to it. - Make sure the connection is active before you start an import. - Start only one import at a time for each profile. - Do not disconnect the ad account while an import is running. - For very large accounts, plan for a longer import and check back later instead of restarting it. ❓ Quick Answers - Will I lose data if support resets the import? No. The reset clears the stuck import state on the profile. It does not change your ad account, and nothing is changed in your ad platform. - Can I just delete and re-add the profile? This is not recommended. A new profile may hit the same issue, and the original lock will remain. Contact support instead. - Does a stuck import affect my live ads? No. Your live campaigns keep running in your ad account. The import only affects what OTTO PPC can see and manage.

Last updated on Nov 13, 2026

🔍 Fix OTTO Promo Quota and Provisioning Errors

📌 What this article covers Some annual plans or promotions may include OTTO sites. OTTO provisioning can fail with a generic server error, and this article explains quota behavior and provisioning failures. 📊 How OTTO site quota works Your OTTO quota is the number of sites you can run OTTO on under your current plan or promo. A purchase that includes five OTTO sites adds five slots to your account. The number shown in the product is the count of slots that are still free, not always the full amount you paid for. - Included quota is the total number of OTTO sites your plan or promo allows. - Used quota is sites that already have OTTO enabled, including sites you set up earlier. - Available quota is included quota minus used quota. If you paid for five sites and one is already active, the screen can show four. A promo does not always create five empty slots on top of sites you already use. It sets or adds to your allowance. Check active projects before assuming a slot is missing. 🛠️ Why you might see four sites instead of five - One site already has OTTO turned on, so only four slots remain. - A site is still processing from an earlier attempt and is holding a slot. - The same domain exists in more than one project. - The yearly payment succeeded, but the promo entitlement has not finished applying yet. - A frozen project normally holds its OTTO quota for up to 14 days, unless the quota is returned earlier. A deleted project no longer counts toward quota. Payment success and site provisioning are separate steps. A charge can complete even when adding the next site fails. ⚠️ What the server error means A generic unexpected server error means provisioning did not complete at that time. It does not by itself indicate a card decline or plan cancellation; support should check pending provisioning and quota state. ✅ Steps to resolve the quota mismatch 1. Open your billing or plan page and confirm the yearly plan or promo shows as active. 2. Review every project and note which sites already have OTTO enabled. 3. Delete any OTTO project you don't intend to keep, then refresh the page so the slot returns to your available count. A frozen project keeps its slot for up to 14 days. 4. Remove duplicate projects for the same domain if you created more than one. 5. After checkout, allow time for asynchronous entitlement and provisioning updates, then refresh or reopen the OTTO page. 6. Try adding the site again only after the available count matches what you expect. 🚀 What to do when the error appears 1. Do not repeatedly submit while provisioning is pending; wait for the status to update or contact support if it remains stuck. Relevant code: app/ca/models/otto\_project.py:296-310; app/ca/api/v2/serializers/otto\_project.py:254-258. 2. Wait at least 15 minutes, refresh the page, and try once more. 3. Confirm you are not over the included quota before you retry. 4. If the error returns, note the exact site URL, the time you tried, and the full error text. Retrying later is the right first step. If the count is still short after you account for sites already in use, the entitlement may need a manual refresh from support. 💡 What to include if you contact support - The plan or promo you purchased and that it was a yearly payment. - The OTTO site total you expected, such as five, and the number you see, such as four. - The full error text and the approximate time it appeared. - The domain you were trying to add and any sites that already use OTTO. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 13, 2026

💳 Understand Additional OTTO Site Charges

🔎 Why your charge may be higher Your plan price covers the OTTO sites included in your subscription. Additional OTTO sites are purchased as a recurring "OTTO Sites" top-up, so your total increases when extra sites are added. That charge renews each billing period until the top-up is cancelled or reduced. ** For example, a $199 plan can result in a higher total if an OTTO Sites top-up for additional sites is on the subscription. That top-up is a recurring add-on and is billed as its own line. Extra sites are not added automatically. Someone on the account, or an admin on its behalf, purchased them. ** 📊 Review your billing details 1. Open Search Atlas and go to your account or billing settings. 2. Review the invoice or payment history for the affected months. 3. Compare the plan charge with any line items for additional OTTO sites, add-ons, or top-ups. 4. Open the Services tab in Billing to see the OTTO Sites line and its quantity. Compare it with the sites listed in OTTO under All sites. ** The Invoices tab and the Services tab can help you confirm that the recurring amount comes from an OTTO Sites top-up. That top-up covers your additional OTTO sites. ** 🛠️ Check active OTTO sites Review every OTTO site connected to your account, including sites added for testing, previous clients, or older campaigns. An OTTO Sites top-up keeps billing every period until you cancel or reduce it in Billing > Services, even if some of the sites are no longer used. ** Before reducing capacity, confirm that you no longer need those sites' automation, settings and campaign data. To stop or reduce the charge, go to Billing > Services, find the OTTO Sites line and choose Cancel. If you cannot find or change the line, contact support through the in-platform chat. ** 💡 What to include in a billing review - The months and amounts that appear incorrect - Your current plan name and expected monthly price - The invoice line items for those months - The OTTO sites currently active on your account - Whether you recognize any top-up or add-on transactions Providing these details helps the support team compare your subscription, site count, and billing records more quickly. 💬 Get help with a disputed charge If an invoice does not match your active plan and the OTTO Sites top-up you expect, request a billing review. Support can identify the source of the recurring amount and explain the related account activity. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 14, 2026

📊 How to Export Historical OTTO and GBP Activity

📌 Overview Agencies and business owners often need a detailed record of everything done for a client, such as OTTO optimizations and automated Google Business Profile (GBP) posts. This is common for client reports, handovers, and audits. This article explains where to find that history, how to combine it into one report, and what to do when a GBP is no longer connected. ** Available views and export options may change. If you cannot find the information you need, contact Search Atlas support for help. 🗂️ What a Complete Activity Report Can Include - ** OTTO activity may include optimization items, affected pages, and their current deployment status. A complete history of every change and its date may not be available. - ** GBP post information can include automated or scheduled posts, their content, relevant dates, and their status. The history and details visible may vary. - Project context: the client or project name, the website, and the date range you want to cover. 🔍 Step 1: Collect Your OTTO History 1. Open the platform and select the project for the client. 2. Go to the OTTO section for that project. 3. ** In the OTTO project, review the available optimization lists and deployment statuses. Record the affected pages and types of changes shown. Dates and complete historical activity may not be available. 4. If an export or download option is shown, use it to save the data as a file. If not, capture the information with screenshots or copy it into a spreadsheet. 5. Set the date range to match the period your client or report needs. 📍 Step 2: Collect Your GBP Post History 1. ** Open the Google Business Profile tools and select the client’s connected business location. 2. ** Open the posts view for the location and review the available scheduled and published posts, along with any failed posts or other statuses shown. 3. Record the post date, the post text, any image used, and the status. 4. ** If an export option is available for the information you need, use it. Otherwise, copy the visible details into a spreadsheet. 🔌 What If the GBP Is No Longer Connected? When a profile is disconnected, the platform may no longer be able to pull live information from Google for that location. This does not mean the posts disappeared. Here is what to know and what you can do: - ** Disconnecting Search Atlas does not itself delete posts already published to Google. A person with appropriate access can check the business profile on Google for posts that remain available. - Reconnect temporarily if you can. If you or the client still have access to the Google account that manages the profile, reconnecting it may let you view the post history in the platform again and capture it for your report. - ** Check the GBP tools for any information that remains visible. Availability after disconnection is not guaranteed; contact support if you cannot find the history. - Ask the client for a direct export. The profile owner can review posts directly in Google Business Profile and share screenshots or copied text. - Ask our support team. If the history is not visible in the platform, send us the client name, the location, and the date range, and we will tell you what activity data is available. 🧩 Step 3: Combine Everything Into One Report 1. Create a spreadsheet or document with one section for OTTO and one for GBP. 2. Use consistent columns: Date, Area (OTTO or GBP), Page or Location, Action, and Status. 3. Sort everything by date to build a single timeline. 4. Add a short summary at the top that covers the date range, the total number of optimizations, and the total number of posts. 5. Save a copy outside the platform so you have it if a connection changes later. 💡 Tips to Make Future Reporting Easier - Export or record activity monthly rather than waiting until a request comes in. - Before disconnecting a GBP or ending a client project, save the post history first. - Keep your report format the same each month so comparisons are simple. - Note the date a profile was connected and disconnected, so the gaps in your report are easy to explain. ❓ Frequently Asked Questions Will disconnecting a GBP delete the posts already published? No. Disconnecting stops the platform from managing the profile. Posts already published remain on the Google Business Profile unless someone removes them there. Can I get a single report of everything at once? The platform may not offer one combined export for every tool. The simplest approach is to collect OTTO and GBP activity separately and merge them as shown above. Can I see activity from before a profile was disconnected? Often yes, either in the project history or by reconnecting the profile. If you cannot find it, our support team can check what is available. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat. To help us respond faster, include the client or project name, the website, the date range you need, and whether the GBP is currently connected.

Last updated on Nov 14, 2026

🛠️ Fixing Failed OTTO Schema Deployments

🔍 Overview Sometimes a schema shows as deployed in OTTO, but you cannot find it on the live page. This can affect page-level schemas, including FOUND schemas. This article explains what to check and when to contact support. 🧩 Replacement vs. Insertion OTTO can add schema to a page in two ways: - Insertion: OTTO adds a new schema block to the page. It does not depend on anything already being there. - Replacement: For a FOUND schema, OTTO prepares a replacement using the originally detected markup and the updated schema. A deployed status does not by itself confirm that the replacement appeared on the live page. OTTO prepares FOUND schema replacements using the original detected markup. A replacement may not appear if the installation cannot apply it or if the page markup no longer corresponds to what OTTO detected. Check the live page and contact support if it remains missing. ❓ Why a Replacement May Not Appear - The original ImageObject may have changed or may be generated dynamically by a theme, plugin, page builder, or script. Compare the current page markup with the schema OTTO detected and share any differences with support. - The page was cached. Your site, CDN, or caching plugin may still be serving an older version of the page. - If the page was updated after OTTO detected its schema, the image or markup shown in OTTO may no longer match the live page. Compare the current markup with the FOUND schema and contact support if the deployment is missing. - A page may contain more than one ImageObject. Review the schema markup on the live page and compare it with the FOUND schema in OTTO. If you cannot identify the intended schema or the deployed change is missing, contact support. - Check that the OTTO installation or connected deployment method is working on the affected page. If it is missing or blocked, changes delivered through it may not appear. ✅ Step-by-Step: Check Your Deployment 1. Open the page in a private or incognito browser window so you see the version visitors see. 2. Right-click the page, choose View Page Source, and search for application/ld+json. Look for the ImageObject and check whether it matches the schema shown in OTTO. 3. Clear any caches: your site cache, caching plugin, and CDN. Then reload the page and check again. 4. Test the URL with a schema validation tool, such as Google's Rich Results Test or the Schema Markup Validator. This shows the schema a search engine would read. 5. Confirm in OTTO that the deployment status for that page and schema is marked as deployed, and that OTTO is active on the site. 6. If the schema is still missing, check the affected schema and its deployment status in OTTO. If appropriate, redeploy that schema, allow time for processing, and check the live page again. Contact support if it remains missing. 🔄 Can the Schema Be Applied as an Insertion Instead? If a replacement does not appear, contact support to review the affected schema and deployment method. Support can investigate the replacement and advise whether adding a separate schema is appropriate, including whether it could duplicate existing markup. **Code references:** Page-level insertion and replacement preparation: content-assistant/app/ca/models/otto\_url.py:746–805, 998–1004, 1064–1073. The browser pixel skips unsupported header replacement types, including scripts: customer-frontend/public/scripts/dynamic\_optimization.js:1583–1597; it processes header replacements at lines 1979–1986. This is evidence about that code path, not proof of the behavior of every installation. Keep in mind that adding a new ImageObject while the original still exists can create duplicates. Duplicate schema is not always harmful, but it is cleaner to have one accurate version per image. Check the page source after any change. 🛡️ Tips to Prevent Failed Deployments - Deploy schema after you finish editing the page, not before. - Clear your caches after every deployment and after major page changes. - Avoid having multiple plugins output ImageObject schema on the same page. - Recheck important pages after theme or plugin updates. - Validate key pages periodically, especially those with many images. 💬 What to Include When Contacting Support Sharing these details helps us resolve the issue faster: - The full URL of the affected page - The schema type (for example, ImageObject) and whether it was deployed as a replacement - The approximate date and time of the deployment - A screenshot of the deployment in OTTO - A screenshot or copy of the page source section where you expected the schema - Whether you cleared caches and retested in a private window 🙋 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 14, 2026

🛠️ How to Change OTTO Page Schema Type

🔍 What Is Page-Level Schema? ** Schema is structured data added to a page that helps search engines understand its content. OTTO can prepare and manage page-level schemas, including Service, Article, BlogPosting, Product, and FAQPage schemas. Sometimes OTTO picks a type that does not match your page. A common example is a blog post labelled as a Service. This article explains why that happens and how to correct it. 🤔 Why Does OTTO Detect the Wrong Schema Type? OTTO decides based on the signals it finds on the page. A wrong match usually happens when: - The blog post is written about a service you offer, so the wording sounds like a service page. - The page has a strong call to action, pricing details, or a list of features. - The page URL or layout does not look like a typical blog post (for example, it is not under a /blog/ path). - The page has little text, so OTTO has fewer clues to work with. - Your site already has existing schema from a theme or plugin that sends mixed signals. ✅ Before You Start - Confirm your site is connected to OTTO and the page is already in your OTTO project. - Check which schema type you want. For a blog post, BlogPosting or Article is usually the right choice. - Make sure you have permission to edit the project. ⚙️ How to Change the Schema Type 1. Log in to Search Atlas and open your OTTO project for the site. 2. Go to the Schema section of OTTO. 3. ** Find the page that has the wrong schema. You can search for it by URL. 4. Open the schema details for that page. 5. Open the schema in the Schema Preview drawer and click the Edit (pencil) icon. The editor opens with a structured view and a Raw JSON tab. To change the type, edit the schema's @type value (for example, from Service to BlogPosting) and adjust its fields to match. There is no type dropdown. The Page Type shown in the drawer is display-only and does not change. WebPage and FAQPage schemas cannot be edited this way, because Semantic Analysis and Knowledge-Based Trust & Factual Enhancement manage them. 6. ** Review and manually update the schema properties appropriate for the new type. For an article, these may include headline, author, publication date, and image. Check that the resulting JSON is valid and accurately describes the page. 7. Save your changes and apply or publish the update, if OTTO asks you to. Note: Button names and layout can look slightly different depending on your plan and the latest platform updates, but the steps above follow the same flow. 🧪 How to Check That the Change Worked 1. Wait a few minutes after saving, then reload the page on your live site. 2. Run the page URL through Google's Rich Results Test or the Schema Markup Validator. 3. Confirm the new type (for example, BlogPosting) appears and the old type (Service) is gone. 4. If you still see the old type, clear your site cache and any caching plugin or CDN, then test again. 💡 Tips to Prevent Wrong Schema in the Future - Use a clear blog structure for posts, including a title, author, date, and featured image. - Keep blog posts under a consistent URL path such as /blog/. - Avoid heavy sales language and pricing tables inside blog content when possible. - Turn off duplicate schema from other plugins or themes so they do not conflict with OTTO. - Review the schema for new pages after OTTO processes them. 🛠️ Troubleshooting - The schema type does not change after saving: Clear your site and browser cache, then check the page again. - I see two schema types on the page: Another plugin or your theme may be adding its own schema. Disable the duplicate and test again. - The type I need is not in the list: Choose the closest available type, such as Article, and let us know which type you need. - The wrong type returns after a while: OTTO may have re-scanned the page. Check that your change was saved, and report the page to our team. - I cannot find the edit option: The page may not be fully processed yet, or your role may not allow edits. Check back after a short time or ask the project owner. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat. To help us resolve it faster, include the page URL, the schema type OTTO detected, and the schema type you want.

Last updated on Nov 14, 2026

🛠️ Correct Misclassified OTTO Schema Markup

🔍 Why OTTO schema can be misclassified OTTO selects schema markup based on the page content and its detected purpose. If the page contains mixed content, unclear signals, or information that matches more than one schema type, OTTO may choose an incorrect classification. ✅ Review the selected schema 1. Open the affected project in Search Atlas. 2. Open the affected OTTO project, go to the schema issues, and find the affected page under Page-Level Schema. Open the schema’s preview to inspect it. 3. Review the schema type and the fields generated for that page. 4. Compare the markup with the page’s primary purpose and visible content. Only use a schema type that accurately describes the page. The markup should represent information that visitors can see on the page. ✏️ Correct the classification Open the schema preview and, if editing is available, use Edit to correct the JSON-LD fields. Save your changes, review any validation warnings, and deploy the corrected schema when appropriate. WebPage and FAQPage schema contents are managed by other OTTO features and cannot be edited through the same JSON editor. For example, a page focused on one service should use a service-related schema when available. A page containing a specific product, event, article, or frequently asked question should use the matching type only when the required information is clearly present. 🚫 Remove schema from a page If a schema does not accurately describe the page, do not deploy it. If OTTO has already deployed it, use Undo Deployment where available. For a deletable page-level schema, you can also use Delete Schema. If the schema is marked FOUND, correct or remove the original markup at its source on the website instead. It is better to omit a schema than to publish misleading markup. Undoing an OTTO schema deployment does not delete the page or its content, but it may not remove schema already present on the website from another source. Check the page’s markup after making the change. 🔎 Verify the update 1. Confirm that the corrected schema is saved and published. 2. Check the page source or rendered markup to ensure the old schema is no longer present. 3. Use Google’s Rich Results Test or Schema Markup Validator to review the result. 4. Fix any validation errors caused by missing or inaccurate visible content. Search engines may take time to recrawl the page and reflect the change in search results. 💬 Need help? If the correct schema type or removal option is not available, record the page URL, the selected schema type, and the correction you want to make. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 14, 2026

💳 Resolve OTTO Overbilling and Credits

🔍 Understanding OTTO billing Your plan may include OTTO Sites, and additional site capacity may be billed as a recurring top-up. If your account shows five available OTTO Sites and you see an unexpected charge, review your subscription and invoice details or ask support to investigate. An adjustment that makes your account show 5 of 5 OTTO Sites may correct the allocation, but it does not necessarily credit a charge that was already processed. Contact support to review the charge and any adjustment. ✅ Check your OTTO quantity 1. Open the OTTO section in the Search Atlas platform. 2. In OTTO SEO Automation, check the OTTO Sites quota, shown as used of total, such as 3 used of 5. That is the number of sites you are licensed to install and activate OTTO on, not a count of active OTTO projects. 3. Open Billing. Under Plans & Top-ups, open OTTO SEO and check OTTO Sites, shown as used of total. Under Services, review the recurring OTTO Sites top-up and its charge. Then open Invoices and review the list columns: ID, created date, paid date, type, details, status, and amount. You can download an invoice, but the list does not break out each charge line. 4. Compare the invoice and billing period with your plan’s included OTTO site capacity and any additional capacity you purchased. Ask support to review any discrepancy. 💰 How account credits work If an extra OTTO charge was caused by an incorrect subscription quantity, the charge may qualify for an account credit. Credit reviews depend on the account setup, billing period, and whether the charge has already been invoiced or paid. When approved, the credit is issued by support as a refund to the original payment method or applied to a future invoice. It does not change the original charge by itself, and correcting the OTTO Sites quantity does not create a credit unless support reviews the billing. 🛠️ Request a billing review Before contacting support, collect the following details: - The number of OTTOs your plan should include - The OTTO quantity currently displayed - The charge amount and date. For example, an OTTO Sites charge in the 4 to 9 site band is billed at $69 per site per month, so the invoice amount depends on how many sites you are paying for and whether the charge was prorated. - The relevant invoice or billing period - Any recent changes to your OTTO subscription If the quantity is correct but the extra charge or expected credit is still present, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat. 📌 What support will review The support team can compare your OTTO configuration with billing records, confirm whether the charge was valid, and determine whether an account credit is appropriate. Include screenshots or invoice details in the chat when possible so the review can be completed faster.

Last updated on Nov 14, 2026

🛠️ Fixing OTTO Site Quota Miscount Errors

🔍 What This Issue Looks Like You may see an OTTO site limit when you try to add another site. In Top up: OTTO Sites, enter the total number of sites you want, including your existing allowance. If the available purchase options or displayed quota do not match what you expect, contact support before purchasing. This article explains the most common reasons for this, how to check your real site count, and what to send to support if the numbers still look wrong. 🧭 Why It Happens OTTO quota counts qualifying OTTO projects on your account, including projects you may no longer actively manage. A frozen project can also count until its quota is returned. Review your OTTO projects if the count does not match your expectations. - Old or unused projects: An OTTO project you no longer use may still take up a slot if it has not been deleted. Removing a site from another list does not necessarily mean its OTTO project was deleted. - Possible duplicate projects: Check whether you have more than one OTTO project for what you consider the same site. Review each project carefully before deleting one. - Subdomains: A subdomain such as blog.yourdomain.com may count as its own site. - Other account projects: OTTO projects created by you or other team members under the same customer account may count toward that account’s total. A separate customer account or workspace should not be assumed to share the same quota. - Test or trial entries: A site added during setup or testing may still be connected. - Plan or add-on changes: After a change, compare your active plan and purchased OTTO Sites capacity with the quota shown in the dashboard. If they do not match, contact support to investigate. 📋 Step 1: Check Your Real Site Count Before you try to buy a top-up, confirm how many sites OTTO currently counts. 1. Open the OTTO section of your dashboard and review the full list of connected sites. 2. Write down every site, including subdomains and any duplicate versions of the same domain. 3. Compare your list with your plan's included site limit and any add-ons you already bought. 4. Check OTTO projects created by other team members under the same account. If you use multiple workspaces or accounts, confirm which account owns each project and which quota it uses. If your list is longer than you expected, the extra entries are probably the cause of the over-limit message. 🧹 Step 2: Remove Entries You No Longer Need If you find an OTTO project you no longer need, review it carefully and delete the OTTO project. This can free its quota slot and may clear the over-limit message after the quota updates. If the count remains incorrect, contact support. - Only remove sites you are sure you no longer need. - Keep one entry per site unless you intentionally want a subdomain managed separately. - Refresh the page after making changes and check the displayed count again. If it still does not match the remaining OTTO projects, contact support. Note: Removing a site from OTTO may stop OTTO optimizations on it. Review any site carefully before you remove it. 🛒 Step 3: Try the Top-Up Again After you clean up your list and refresh the page, return to the purchase screen and check the options again. - If the dashboard now shows you are within your limit, you should see options that match your needs. - If you still only see larger bundles, such as 11 or more sites, the system may still read your account as being over its limit, or the top-up may be offered only in set bundles. - Do not buy a larger bundle just to get around the message if you only need a few extra sites. Contact support first so the count can be reviewed. 🔄 Quick Fixes to Try First - Refresh the page or log out and back in. - Try a different browser or an incognito window to rule out cached data. - Turn off browser extensions, such as ad blockers, that may interfere with the checkout page. - Wait a few minutes after any plan or add-on change, then check again. 💬 When to Contact Support Contact support if: - Your site list shows fewer sites than the quota says you are using. - You are still told you are over your limit after removing unused or duplicate entries. - The top-up page only offers bundles much larger than you need. To help us fix it faster, include the following in your chat message: - The number of OTTO sites you expect to have and the number the dashboard shows. - The domains you currently use with OTTO. - A screenshot of the over-limit message and the top-up options you see. - How many extra sites you are trying to add. - Any recent plan, add-on, or billing changes. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat. 💡 Tips to Avoid This in the Future - Review your OTTO site list regularly and remove sites you no longer use. - Add each site once, using its main address. - Before adding a subdomain, check whether you want it managed separately, since it may use an extra slot. - Check your site count before buying top-ups, so you buy only what you need.

Last updated on Nov 15, 2026

📝 Recurring Blog Publishing on OTTO Starter

📝 Is recurring publishing available? A connected WordPress website alone does not confirm that your OTTO SEO Starter account can automatically select topics, generate German articles, and publish two posts every month. Search Atlas offers recurring Atlas Agent automations called Golden Loops, but confirm your account’s access, publishing permissions, and the complete workflow before relying on one. Before relying on it, ask support to confirm whether your current plan includes fully recurring blog publishing and, if it does, where to activate it. Do not assume that a one-time generation or scheduled publication will repeat automatically. ⚙️ What to check in your account 1. Confirm that the WordPress website is connected to the correct project. 2. Open Atlas Agent in full screen, select Golden Loops in the left navigation, and select New loop. To describe a workflow from scratch, choose Custom prompt. Confirm that your account can use the feature and that the loop can perform the publishing steps you need. A one-time publication schedule is not the same as a recurring loop. 3. Check whether the workflow supports German, two articles per month, automatic topic selection, and publishing without approval or manual scheduling. 4. Check any plan limits, credits, or approval requirements shown before activating the workflow. If you cannot find an explicit recurring setting, ask support to verify whether it is available on your plan and provide the exact activation steps. If it is not available, support can clarify which parts of the process require manual action and whether another plan offers the workflow you need. 💬 Contact support When you contact support, mention that you have OTTO SEO Starter and a connected WordPress site. Ask whether Search Atlas can automatically select topics, generate German SEO articles, and publish two per month on an ongoing basis without manual selection, generation, approval, or scheduling. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 15, 2026

⚙️ OTTO Compatibility and UK Local SEO

🔍 Does OTTO work with GoDaddy Airo? ** OTTO offers an installation method for GoDaddy websites and may work with sites built using frameworks such as React and Vite. Compatibility depends on the published site, whether an OTTO integration can be installed, and which changes that integration can apply. Test the setup and individual fixes before relying on them. ** GoDaddy hosting alone does not determine OTTO compatibility. For a GoDaddy Airo website, check which installation methods and site settings are available for your specific plan and setup. Those permissions can affect installation and which recommendations can be deployed. 🛠️ Can OTTO implement fixes directly? OTTO can apply supported on-page SEO changes after its installation has been completed and verified. Depending on the website setup, this may include title tags, meta descriptions, headings, image details, internal links, structured data, and other eligible recommendations. React/Vite websites can require special handling because some content is rendered dynamically in the browser. Search engines may still process this content, but OTTO must be able to access the published pages and apply changes through the available integration method. OTTO cannot guarantee direct implementation of every fix on a GoDaddy Airo website. Changes that require source-code access, server-side routing, build configuration, custom components, hosting settings, or third-party platform permissions may need to be completed manually by the website owner or developer. ✅ What to confirm before subscribing 1. Confirm that your GoDaddy Airo plan allows custom code or the OTTO installation method provided in Search Atlas. 2. Confirm that you can publish the required installation code across the website. 3. Check whether important pages are publicly accessible without login, blocking rules, or temporary publishing restrictions. 4. Identify whether your website uses client-side rendering, server-side rendering, or static page generation. 5. Review which recommended changes can be deployed automatically and which may require manual updates. 🇬🇧 How OTTO can help with UK local SEO OTTO can help improve local SEO by identifying and recommending changes to location pages, titles, headings, internal links, local business information, and relevant structured data. You can use it to support UK-focused targeting, such as town, city, county, or service-area terms. For the best results, keep your business name, address, phone number, opening hours, and service areas consistent across your website and business listings. Use clear UK spelling and location references where they accurately describe your services. OTTO does not replace your Google Business Profile or guarantee rankings. Profile verification, reviews, map visibility, business information, and other external listings may require separate management. 📋 Recommended next step ** Before purchasing Search Atlas Starter, prepare your website URL and confirm how your GoDaddy Airo site is published. Contact the Search Atlas team to ask about compatibility and whether they can review which OTTO recommendations may be deployable for your website. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 15, 2026

⚙️ OTTO Autopilot Page Title Changes

🔍 What OTTO Autopilot does OTTO Autopilot helps apply eligible SEO recommendations to your website automatically. Depending on the recommendations identified for your project, this may include page title updates. When Autopilot is enabled, OTTO can make supported changes without requiring you to apply each recommendation manually. It does not mean that every page title will change automatically. 📝 When page titles may change OTTO may update a page title when it identifies an SEO opportunity, such as a missing, duplicated, unclear, or poorly optimized title. Changes depend on the pages OTTO can access and the recommendations available for your project. Autopilot does not randomly rewrite all titles. Only eligible recommendations are applied, and the resulting title is based on the available page and SEO information. ⚙️ How to review Autopilot 1. Open the relevant project in Search Atlas. 2. Open the OTTO SEO section. 3. Review the Autopilot setting and its current status. 4. ** Review the available Title Tags recommendations and their deployment status before and after updates. The exact options shown may vary by project and platform version. Review the available controls before enabling or disabling automatic changes. 🛡️ How to prevent unexpected title updates - Review recommendations before enabling automatic application, when review controls are available. - ** After enabling Autopilot, review the Title Tags recommendations and their deployment status. - Compare updated page titles with your website content and SEO strategy. - ** Turn off auto-deployment for Title Tags if you want future title recommendations to wait for manual review. To stop all supported fix types from being automatically deployed, turn off each enabled Autopilot fix-type switch. Existing deployments remain in place until rolled back. ↩️ If a title was changed ** Check the page’s current title and the Title Tags recommendation’s deployment status in OTTO. If you need to confirm when the change was deployed or whether Autopilot applied it, ask support to check the project’s deployment logs. ** If you do not want the change, find the page in OTTO, open Title Tags, and roll back the deployed recommendation. Turn off auto-deployment for Title Tags if you also want future title fixes to wait for manual review. Check the live page afterward; caching or an enabled CMS synchronization may affect what you see. **Verification:** The auto-deployment implementation maps page titles to their own setting and deploys freshly generated eligible fixes (content-assistant/app/ca/pipelines/otto\_autopilot\_auto\_deploy.py:11–25, 42–66). The settings UI describes per-type automatic publishing and its status (customer-frontend/src/modules/otto/shared/components/settings-modal/automation-section.tsx:265–304). Deployment logs are available through a backend endpoint (content-assistant/app/ca/api/v2/urls.py:47). These findings are based on the available code, not a live project inspection. 💬 Need help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 15, 2026

⚙️ Fix OTTO Pixel React Hydration Errors

🔍 What causes the error? React hydration error #418 can occur when the OTTO pixel adds an empty or whitespace-only node to document.head during page loading. React may detect a difference between the server-rendered HTML and the browser-rendered page, causing hydration to fail. ✅ Checks to complete 1. Confirm that empty custom HTML blocks are disabled or removed. 2. Check for conflicting schema markup and disable duplicate or conflicting schemas. 3. Clear your site and browser caches, then test the page in a private browsing window. 4. Review the page source and browser console to confirm whether whitespace is still being added to document.head. 🛠️ Recommended resolution If the pixel continues adding whitespace after these checks, the issue may require an OTTO engine-level change. The recommended fix is for the pixel to skip empty or whitespace-only DOM insertions before adding them to the page. This type of fix is designed to prevent unnecessary head changes and can typically be made without modifying the Lovable app. However, deployment timing and compatibility must be confirmed by the Search Atlas team for the affected site. 📋 What to include when reporting - The affected page URL or project name. - The exact React hydration error, including error #418. - Whether empty custom HTML and conflicting schemas are disabled. - A screenshot or console output showing the document.head change, if available. - Confirmation that the issue remains after clearing caches and retesting. 💬 Request an engine-level review If the issue continues, ask the support team to review whether the OTTO pixel is inserting empty or whitespace-only content and to confirm whether an engine-level fix can be deployed without changing the Lovable app. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 15, 2026

🔗 Link Shopify to an OTTO Project

🔗 Overview You can link an existing Shopify connection to an OTTO project without creating a new store connection. The Shopify store and the OTTO project must use the correct account, domain, and permissions before provisioning can complete. ✅ Before you begin - Confirm that you have access to the Shopify store you want to connect. - Confirm that the OTTO project uses the website domain associated with that store. - Check that the Shopify connection is active and available in the same Search Atlas account or workspace as the OTTO project. - ** If you need to authorize Shopify, follow the Shopify window or redirect. If a window does not open, check your browser’s pop-up and redirect settings. 🛠️ Link the Shopify connection 1. Open the relevant OTTO project in Search Atlas. 2. Open the project’s integrations, connectors, or connection settings. 3. Choose the Shopify connector. 4. Select the existing Shopify connection instead of creating a new connection. 5. ** If a matching existing connection is offered, choose it. If you connect a different account or are prompted to authorize Shopify, choose the intended store and approve the requested access. 6. ** Use the offered connection and wait while OTTO links it to the project and checks whether it is live. If linking fails, follow the displayed retry instructions. ** For example, an existing Shopify connection for hyperdrivebrands.myshopify.com may be offered for the warmfuzzytoys.com OTTO project if that store serves warmfuzzytoys.com and the connection is eligible for the project. Verify the store and domain before linking; the example alone does not establish that they match. 📊 Confirm provisioning ** After linking, allow OTTO time to check the connection. In the project’s Settings → Connections, look for Shopify’s connection status, such as Connected, and follow any prompt to finish connecting or reconnect. Check sync settings and any displayed errors if fixes are not reaching Shopify. ⚠️ If the connector is not visible - Verify that you are editing the intended OTTO project, not another project or workspace. - Refresh the page and reopen the connector settings. - Check whether the Shopify connection is active and belongs to the current account. - Confirm that your user role allows you to manage integrations. - Disconnect incomplete or duplicate connection attempts only when you are sure they are not being used by another project. - Reconnect Shopify and approve all requested permissions if the previous authorization expired. 🔍 If domains show “No data available” ** If you see “No data available,” confirm that you opened the intended OTTO project and that its domain and Shopify connection are correct. Check the connection status and any displayed errors, then refresh. If the message persists, contact support rather than repeatedly creating connections; retry linking an existing connection when that option is offered. 💬 Get help If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 15, 2026

⚙️ Disable OTTO on Specific WordPress Pages

🔍 How page-level disabling works Yes. You can disable OTTO on specific WordPress pages while keeping OTTO Autopilot active on the rest of your site. When you disable OTTO for a page, OTTO stops running on that page, so its optimizations are no longer served there. Other pages remain eligible for OTTO recommendations and automations. 🛠️ Disable OTTO for a page 1. Log in to your WordPress site and visit the page you want to exclude on the front end, while logged in as an administrator. 2. Hover the OTTO item in the WordPress admin bar at the top of the page. Alternatively, open the Search Atlas plugin's Compatibility page in WordPress and find the OTTO Excluded URLs section. 3. Open the page you want to exclude on your site. Or have its URL ready to add to the Excluded URLs list. 4. In the admin bar, choose Disable OTTO. Or, on the Compatibility page, enter the URL in the Add New Excluded URL form and add it. 5. The change applies right away, and the admin bar status changes to "OTTO Disabled". If you use the Excluded URLs list, the URL appears in the list once saved. 📄 What happens after you disable a page - OTTO will no longer make new changes to the disabled page. - OTTO remains active on other enabled pages. - Disabling a page stops OTTO's changes from showing on it, but it doesn't delete them from your Search Atlas account. Turning OTTO back on restores them. - Disabling the page does not disable OTTO Autopilot for your entire website. ↩️ Re-enable a page To let OTTO manage the page again, open the page while logged in and choose Enable OTTO in the admin bar. If the page is on the Compatibility page's Excluded URLs list, remove it from the list instead. The admin-bar toggle can't override the list. OTTO then runs on the page again. ✅ Recommended checks - Confirm you selected the correct page before disabling it. - Review the page in WordPress if you want to identify or manually reverse earlier changes. - Keep important landing pages disabled when you want full manual control over their content or SEO settings. 💬 Need help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 15, 2026

☁️ Connect OTTO to Cloudflare

🔍 Before you begin ** Make sure you can access and edit the relevant OTTO project in Search Atlas and create a Cloudflare user API token with the required permissions for the website’s Cloudflare account and zone. Confirm that the website is active in Cloudflare and its DNS is managed there. ⚙️ Create a Cloudflare API token 1. Sign in to Cloudflare and open your profile. 2. Go to API Tokens and select Create Token. 3. ** On the Cloudflare user API Tokens page, select the Edit Cloudflare Workers template. Add Zone → DNS → Edit, and scope the token to the Cloudflare account and zone for your website. Review the template’s Workers permissions before creating the token. 4. Limit the token to the specific website zone whenever possible. 5. Create the token and copy it immediately. Cloudflare will not show the full token again. 🔗 Connect Cloudflare in Search Atlas 1. Open the relevant project in Search Atlas. 2. Open the OTTO settings or installation section. 3. Select Cloudflare as the connection method. 4. ** In the Cloudflare installation section of the relevant OTTO project, paste the Cloudflare user API token into the Paste your API Token field. 5. Submit the connection details and wait for the verification result. ** Make sure you opened the OTTO project for the intended website and that the token is scoped to its Cloudflare account and zone. Paste the token without extra spaces. ✅ Verify the connection ** After the process finishes, confirm that Cloudflare shows Connected in the OTTO installation guide. Check the installation or diagnostics results, then visit the website in an incognito browser window to confirm that it loads normally before publishing OTTO changes. 🛠️ Troubleshoot connection problems - ** Invalid token: Check that you created a Cloudflare user API token—not an account API token—and that it includes the Workers permissions from the Edit Cloudflare Workers template plus Zone → DNS → Edit. Confirm that its account and zone scope includes your website. If necessary, create a new token and paste it again. - ** Zone not found: Confirm that the website domain in your OTTO project belongs to a zone in the Cloudflare account and that the token includes access to that account and zone. - Permission denied: Ask a Cloudflare account administrator to create the token or grant the required permissions. - Changes are not visible: Check that the correct Cloudflare zone is connected and allow time for caching to update. - Website errors after connection: Temporarily review Cloudflare caching, security, and firewall rules, then confirm that the site still loads without OTTO changes. 💬 Get help with your setup Support availability can vary by plan and day. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 15, 2026

⚙️ Control OTTO and Rank Math by Page

🔍 How OTTO and Rank Math interact ** Rank Math and OTTO can be active on the same website, but both may affect titles, meta descriptions, schema, and other SEO elements. If both manage the same element, check the published page for competing values or duplicate markup. For predictable results, assign each page to one primary optimization system. You can use Rank Math independently on selected pages while continuing to use Search Atlas and OTTO elsewhere. 🛠️ Use Rank Math independently on a page 1. Open the page in your website editor. 2. Use Rank Math to set the page-level SEO details you want to control. 3. In Search Atlas, open the corresponding page settings or page list. 4. ** In your OTTO project settings, use the available URL exclusion rules to leave the page out of the crawl. Review any fixes already deployed to that page and verify the published result. 5. Save the settings, then review the published page source to confirm the title, description, and other elements are correct. ** Use Rank Math to manage the selected page and verify that OTTO fixes are no longer being applied there. OTTO can continue optimizing other eligible pages. 🚫 Prevent OTTO from changing a page ** To leave a page out of OTTO’s crawl, open your OTTO project settings and add an exclusion under URL rules or URL Exclusion conditions. Choose a matching rule carefully so it does not unintentionally match other pages. Review previously deployed fixes and verify the result on the published page. After disabling OTTO, allow time for the change to take effect. If a previous OTTO update remains on the page, review the page in your CMS and restore or replace the affected SEO fields as needed. ⏸️ Stop Autopilot on selected pages ** Autopilot can automatically apply eligible optimizations. To manage a page manually with Rank Math, use an appropriate OTTO URL exclusion rule and review existing deployed fixes. If you disable Autopilot for the project, that affects automation beyond the individual page and does not necessarily undo changes already published. ✅ Recommended setup - ** Use Rank Math for pages that require manual control. Add appropriate OTTO URL exclusion rules and review any fixes already deployed to those pages. - Use OTTO: Avoid changing the same SEO fields manually in Rank Math after OTTO is enabled. - Review important pages: Check the live page and its source after changing ownership of SEO settings. - Prevent conflicts: Do not run multiple automated tools against the same page elements unless you intend to test which setting is applied. 💡 If page-level controls are unavailable ** If you cannot find URL exclusion controls in your OTTO project settings, contact Search Atlas support for help with your configuration. Until the exclusion and any existing deployments have been verified, avoid having Rank Math and OTTO manage the same elements. **Verification notes:** OTTO’s settings code labels URL rules as a way to “leave pages out of the crawl” and supports **Exclude**, **URL contains**, and **URL starts with** (customer-frontend/src/modules/otto/shared/components/settings-modal/crawl-section.tsx:275–296). The deployment diagnostics also warn that fixes on pages excluded by crawl rules may not be applied or verified (customer-frontend/src/modules/otto/shared/diagnostics/DeploymentVerdictCard/index.tsx:84–85). These code findings do not establish the controls or deployment state of a particular account. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 15, 2026