📖 Features & How-To

🤖 Exclude Pages from OTTO Crawl Settings

🖥️ Front-End vs. Back-End Changes

🚀 OTTO: Smarter, Faster, and Built for Scale

🏷️ How to Optimize Meta Tags for SEO

🔧 OTTO Setup, Functionality, and Deployment

📘 Domain Knowledge Network (DKN) + Vibe Coding in OTTO

📊 Understanding Scholarly Scoring Content Classification and Factuality

🔍 What Is Scholarly Scoring? Scholarly Scoring is a feature inside the Scholar tool (Left sidebar → Content → Scholar) that evaluates your content against trusted sources. It assigns scores based on two key dimensions: content type classification and factuality evaluation. Understanding how these work helps you interpret your scores accurately and make smarter optimization decisions. 🗂️ How Content Type Classification Works When Scholar analyzes a page, it determines the content type by reading signals from three layers of your page in the following priority order: 1. Metadata — The tool first reads your page's meta title, meta description, and structured data (schema markup). If your schema type is set to Product or your meta title includes commercial terms like "Buy" or "Shop," the tool will classify the page accordingly. 2. Headings — If metadata signals are ambiguous, Scholar scans your H1 and H2 tags for topic and intent cues. Headings with action-oriented or transactional language push the classification toward product or commercial pages. 3. Body Content — As a final signal, the tool analyzes the density and structure of your main body text, looking at keyword patterns, sentence structure, and topical focus. This layered approach means the classification reflects the strongest available signal, not just the overall page topic. ⚠️ Why Blog Posts Sometimes Get Classified as Product Pages This is one of the most common classification issues. A blog post can be misclassified as a product page when any of the following are true: - Your page uses Product schema markup even if the content is editorial. - Your meta title or meta description includes commercial phrases such as "best," "buy," "price," "deals," or branded product names. - Your H1 or H2 headings are written in a transactional style (e.g., "Top 10 [Product] to Buy in 2025"). - The body content contains a high density of affiliate links, pricing mentions, or product comparisons. To fix a misclassification, audit your metadata and schema markup first — these carry the most weight. Update your schema type to Article or BlogPosting and ensure your meta title reflects an informational intent. After making changes, re-run the Scholar analysis to refresh the classification. ✅ How Factuality Scores Are Evaluated Factuality scoring measures how well the claims in your content are supported by credible, authoritative sources. Scholar cross-references your content against a curated index of scholarly and high-authority publications. The score is influenced by: - Claim density — How many verifiable statements your content makes relative to its total length. - Source alignment — Whether the facts in your content match or contradict data found in trusted references. - Citation presence — Whether your content links to or references external authoritative sources directly. - Specificity — Vague or generic statements score lower than precise, data-backed claims. A higher factuality score signals to both Scholar and search engines that your content is trustworthy and well-researched. 📍 Factuality Scoring for Venue-Specific SEO Content Venue-specific content — such as pages optimized for a specific restaurant, hotel, event space, or local business — presents a unique challenge for factuality scoring. Because much of this content relies on proprietary or hyper-local information (e.g., seating capacity, operating hours, unique amenities), it may not appear in Scholar's reference index. Here is how to maximize factuality scores for venue-specific pages: 1. Add verifiable, public-record details — Include information that exists in external sources, such as official business directories, Google Business Profile data, or local government records. 2. Support unique claims with citations — If you state a venue has won an award or holds a specific certification, link directly to the awarding body's page. 3. Use structured data accurately — Apply LocalBusiness, FoodEstablishment, or relevant schema types so Scholar can correctly interpret the content context before scoring. 4. Avoid unsubstantiated superlatives — Phrases like "the best venue in the city" without supporting evidence will lower your factuality score. Replace them with specific, provable claims. Note that factuality scores for highly localized content will naturally be lower than scores for content covering well-documented topics. This is expected behavior, not a tool error. 🛠️ Quick Troubleshooting Checklist - Misclassified content type → Check and correct your schema markup first, then update meta tags. - Low factuality score on a blog post → Add citations, increase claim specificity, and reduce unsubstantiated opinions. - Low factuality score on a venue page → Link to public-record sources and apply the correct LocalBusiness schema. - Score did not update after edits → Re-run the Scholar analysis manually to pull in the latest version of your page. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team. Additional Notes Weighted signal percentages (~45% metadata, ~35% structural/heading, ~20% body content) and the 70% confidence threshold rule, below which the tool falls back to closest match and may flag a low-confidence indicator.

🔄 Reset OTTO SEO for a New Website Build

🧭 Overview When you launch a new website build — such as switching to a new Shopify theme or rebuilding your site from scratch — OTTO SEO may continue surfacing recommendations and issues based on your old site structure. Resetting your OTTO SEO project tells the system to re-crawl and re-evaluate your site fresh, so all recommendations align with your new build. This article explains when a reset is needed, what to have ready when you contact support, and what to expect after the reset is completed. ⚠️ When Should You Reset Your OTTO SEO Project? A project reset is recommended when: - You have launched a new website theme (e.g. a new Shopify theme) and OTTO is still showing errors from the old design. - Your site URL structure has changed significantly due to a rebuild. - OTTO SEO recommendations no longer match the pages or content on your live site. - You have migrated your site to a new platform or CMS. If your site content and structure are mostly unchanged and you are only seeing a small number of outdated issues, a full reset may not be necessary. In that case, re-running a crawl may be sufficient. 🛠️ How to Get Your OTTO SEO Project Reset Resetting an OTTO SEO project is a backend action performed by the Search Atlas support team — it cannot be completed independently through the customer-facing dashboard at this time. To get your project reset as quickly as possible, please have the following information ready before reaching out: - Your project name and associated domain (e.g. trendygardenclub.com) so the team can locate the correct project. - A brief description of the change — for example, "switched to a new Shopify theme" or "rebuilt site on a new CMS" — so the team understands the scope of the reset needed. - Confirmation that your new site is live, since the reset will trigger a fresh crawl of your current live pages. ⏱️ What to Expect After the Reset After the support team completes the reset and a new crawl runs: - All previous issues and recommendations tied to your old site will be cleared. - OTTO SEO will generate a new set of recommendations based on your current live pages and content. - Any automated actions OTTO had applied to your old site will no longer be active, and new recommendations will be queued for your updated build. - You can review updated on-page recommendations, meta descriptions, page titles, and other automated actions from your OTTO SEO dashboard once the crawl is complete. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🗺️ Choosing the Right Search Atlas Tool for Content

🧭 Overview Search Atlas offers several tools for content optimization and creation. Knowing which tool to use — and when — saves time and produces better results. This article explains the key differences between Scholar and the On-Page Audit tool, then walks you through a clear decision framework based on your specific goal. 🔬 Scholar vs. On-Page Audit: Key Differences Both tools improve content quality, but they serve different purposes and work best at different stages of your workflow. - Scholar (Semantic Grader) is a content scoring tool that grades a page for a target keyword. It returns an Overall score plus component scores for Content clarity, Factuality, Human effort, Information gain, Content freshness, User intent, Entity, Contextual flow, Numerical, Query relevance and Readability. Use Scholar when you want to evaluate how well a page performs against a target keyword. - On-Page Audit evaluates a live URL on your site against its current ranking keyword. It identifies technical and on-page issues such as missing or weak title tags, thin content, poor keyword placement, and internal linking gaps. Use On-Page Audit when you want a diagnostic report on a page that already exists and is indexed. In short: On-Page Audit diagnoses problems on live pages; Scholar grades page content against a target keyword. They are complementary — run the audit first to identify issues, then open Scholar to action the fixes. 📋 Tool Selection by Use Case Use the scenarios below to quickly identify the right tool for your situation. Scenario 1 — You have an existing page that ranks but underperforms 1. Run the On-Page Audit to get a full diagnostic of what is holding the page back. 2. Use Scholar with the same target keyword to grade the page and identify which scoring areas (e.g., clarity, factuality, information gain) need improvement. 3. Use Site Explorer to cross-reference organic traffic trends and confirm the page is worth prioritising before investing time. Scenario 2 — You have an existing page with GSC data showing impressions but low clicks 1. Review Google Search Console data to identify the keyword driving impressions. 2. Run the On-Page Audit against that URL and keyword to find gaps in title tags, meta descriptions, and content relevance. 3. Use Scholar to grade the page against the target keyword and pinpoint which scoring components need attention. Scenario 3 — You want to create new content for a keyword your site does not rank for yet 1. Start in Content Planner to build a structured content strategy around your target topic. Content Planner maps out clusters of related keywords and suggests which pages to create to build topical authority. 2. Use Scholar to grade each new page against the target keyword and see how it scores across components like query relevance, entity, and content clarity. 3. Once pages are published and indexed, run the On-Page Audit periodically to catch any on-page issues and keep content competitive over time. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚡ Bulk Edit AI-Suggested Title Changes at Scale

Overview If Deployment AI has surfaced a large number of title suggestions, reviewing and applying them one by one is not practical. Deployment AI includes a bulk action workflow that lets you select, review, and deploy AI-suggested title changes in batches — saving you hours of manual clicking. This article explains how to approach bulk editing of AI-suggested title changes in Deployment AI, including how to work through large queues and what to do if you encounter a generation or workflow limitation. Before You Begin - Make sure you are working inside a Deployment AI project that already has AI title suggestions generated. - You will need sufficient permissions in your workspace to deploy changes. How to Bulk Edit AI-Suggested Title Changes 1. Open your Deployment AI project. Navigate to the Deployment AI section in Search Atlas and select the project containing your title suggestions. 2. Go to the Title Changes queue. Locate the list of AI-suggested title changes displayed as a queue of pending suggestions for your connected pages. 3. Select multiple suggestions in bulk. Use the bulk selection controls available in the title suggestions list to choose the suggestions you want to action. You can select all items at once or choose specific suggestions individually. 4. Review the selected suggestions. Before deploying, scan the highlighted titles to confirm the AI recommendations align with your SEO goals. Deselect any individual suggestion you want to skip. 5. Apply the bulk action. With your selections made, use the bulk action control to confirm and push all selected title changes live to your connected CMS. 6. Work through the queue in batches if needed. If your project contains more suggestions than can be actioned at once due to a generation or workflow limitation, repeat the selection and deploy steps for each batch until your full queue is processed. If You Encounter a Workflow or Generation Limit Some workspaces have a cap on how many suggestions can be generated or actioned in a single batch. If you see a message indicating a generation limit has been reached, or if bulk actions are not appearing as expected, this is a known workflow limitation. To work around it: - Process suggestions in smaller batches and re-run generation after each batch is deployed. - Refresh your project page after deploying a batch to confirm the queue updates correctly before selecting the next group. - If the bulk action controls are not visible or not functioning as expected, contact our support team for assistance — have your project name, a description of the limitation message you are seeing, and the approximate number of suggestions in your queue ready so we can investigate quickly. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚡ OTTO Sync to CMS Safe Review Workflow

Overview OTTO SEO generates on-page recommendations and can automatically push approved changes to your CMS. Understanding when to enable or disable Sync to CMS — and following a structured review process before approval — protects your live site from unintended changes. What Does Sync to CMS Do? When Sync to CMS is enabled, OTTO pushes approved recommendations directly to your connected CMS (for example, WordPress) in real time. This streamlines deployment but means changes go live as soon as they are approved. When Sync to CMS is disabled: - OTTO continues to generate and queue recommendations normally. - No changes are written to your CMS, regardless of approval status inside the platform. - You retain full control over when — and whether — any change reaches your live site. Disabling Sync to CMS does not pause OTTO's analysis or stop new recommendations from appearing. It only breaks the automatic write connection to your CMS. Best Practices for Managing SEO Changes - Disable Sync to CMS during high-traffic periods (product launches, campaigns, peak seasons) to prevent accidental live changes. - Review recommendations in batches rather than approving individual items as they appear. Batch review gives you a complete picture of cumulative impact. - Filter recommendations by type, priority, and status before approving anything, so you can assess changes systematically. - Check how pending recommendations affect individual URLs before pushing changes live. - Document your baseline — note current rankings, traffic, and Core Web Vitals before any batch approval so you can measure impact accurately. - Stage changes in small groups — approve a limited set of recommendations at a time, then monitor performance before approving the next batch. Safe OTTO Review Workflow (Step-by-Step) Follow this workflow every time you are ready to review and deploy a new batch of OTTO recommendations. 1. Disable Sync to CMS. Locate the Sync to CMS setting within the OTTO SEO section of the platform and turn it off. This ensures no changes reach your live site while you are reviewing. 2. Refresh your recommendation queue. Trigger a new scan or crawl from within the OTTO SEO section to make sure your recommendation queue reflects the current state of your site. 3. Filter and review pending recommendations. Use the available filters (such as status, type, and priority) to sort through recommendations before approving any. Focus on high-priority items first. 4. Assess URL-level impact. For each recommendation group you plan to approve, review how the changes will affect individual URLs before proceeding. 5. Approve in small batches. Enable Sync to CMS only when you are ready to push a controlled set of approved changes, then disable it again immediately after. 6. Monitor performance. After each batch goes live, track rankings, traffic, and Core Web Vitals before approving the next group. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🤖 OTTO Page Titles Validation and Agency Workflow

🔍 Overview When OTTO generates page title suggestions, it validates each one against Google's recommended character limits. If a title is too long, OTTO flags it in red to alert you before the change is deployed. This article explains why that happens and walks agency teams through the most efficient workflow for managing optimizations across multiple client sites. 📏 Why Page Titles Show as Red OTTO checks every generated page title against a strict character limit. Titles that exceed the threshold are highlighted in red because Google typically truncates titles longer than 60 characters in search results, which can hurt click-through rates and user experience. A red flag does not mean the title is rejected — it is a validation warning giving you the opportunity to review and edit before applying the change. Common reasons a generated title may run long include: - The page's original title contains a lengthy brand name or product descriptor that OTTO incorporates. - The target keyword phrase itself is unusually long. - OTTO combined the primary keyword with supporting context to improve relevance, pushing the total over the limit. To resolve a red title, click the edit icon next to the suggestion, shorten the text to under 60 characters while keeping the primary keyword near the front, then save. The indicator will turn green once the title is within the accepted range. ⚙️ How OTTO Validation Works in Practice Every OTTO suggestion goes through an automated validation layer that checks: - Character length — titles over 60 characters are flagged red. - Meta description length — descriptions over 160 characters are flagged separately. - Duplicate values — OTTO warns if the same title is detected on multiple pages. Green indicators mean the element is within optimal range and ready to deploy. Yellow indicators flag minor issues worth reviewing. Red indicators require action before the optimization is considered complete. 🚀 Agency Workflow Best Practices for Managing Optimizations at Scale Clicking through each element individually is time-consuming when you manage dozens of client sites. Use the workflow below to handle OTTO optimizations efficiently without sacrificing quality control. 1. Filter by status first. Inside SEO Automation (Left sidebar → OTTO SEO → All Sites (SEO Automation)), use the status filters to isolate all red-flagged items across a client's site. Addressing validation errors in a single focused pass is faster than reviewing every suggestion in order. 2. Bulk-review titles by page template. Group pages by template type (e.g., product pages, blog posts, location pages). Titles for the same template usually share a common structure, so you can edit one, note the pattern, and apply similar adjustments to the rest quickly. 3. Use the Accept All option for green items. Once you have resolved red flags, use the bulk accept action to deploy all green-validated suggestions in one click. This eliminates repetitive individual approvals for elements that are already within spec. 4. Set a review cadence per client. Rather than checking OTTO daily for every client, schedule a weekly or bi-weekly review session per site. OTTO queues new suggestions automatically, so batching your review reduces context-switching and speeds up each session. 5. Leave audit notes in the platform. Use any available annotation or task features to flag pages that need a copywriter's input before titles can be finalized. This keeps the workflow inside the platform and avoids back-and-forth over email. 6. Cross-check with On-Page Audit. After deploying OTTO changes, run an On-Page Audit (Left sidebar → Content → On-Page Audit) to confirm the live titles are indexed correctly and no new issues have appeared. 💡 Tips for Writing Better Page Titles If OTTO's generated titles frequently require manual editing, the following practices can reduce the number of red flags you encounter: - Keep the primary keyword under 40 characters where possible — this leaves room for brand or context modifiers without exceeding the limit. - Avoid stacking multiple keyword variations in a single title. One clear primary keyword performs better and stays concise. - Use a separator (hyphen or pipe) between the keyword phrase and the brand name rather than commas or conjunctions, which add character count. - Review OTTO's configuration settings for your client's site to ensure the brand name appended to titles is using an abbreviated version if the full name is long. 🛠️ Quick Troubleshooting Reference - Title shows red after editing: Recount characters including spaces. Punctuation and spaces both count toward the 60-character limit. - Title reverts to the original after saving: Refresh the page and re-apply the edit. If the issue persists, check whether another user on your team has a conflicting change pending. - Bulk accept button is greyed out: One or more items in the selected batch still have red flags. Resolve all validation errors before bulk accepting. - OTTO is not generating new suggestions: Confirm that the site's crawl is up to date inside OTTO SEO and trigger a manual re-crawl if the last crawl date is older than seven days. 📞 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🖼️ SVG Alt Text in Onpage Audit Explained

🔍 What Is the Onpage Audit Flagging? When you run an Onpage Audit in Search Atlas, the tool scans every image on your page — including SVG (Scalable Vector Graphics) files. If an SVG element is missing an alt attribute, the audit flags it as an actionable task, just like it would for a standard JPG or PNG image. You may notice that some of these SVG images do not display a visual preview inside the audit task panel. This is expected behaviour. SVGs are code-based graphics, and the platform may not render a thumbnail for every SVG type. The task is still valid and worth addressing. 📋 Why Alt Text Matters for SVG Images Alt text serves two important purposes: - Accessibility: Screen readers use alt text to describe images to visually impaired users. Missing alt text on SVGs can make your page non-compliant with accessibility standards such as WCAG 2.1. - SEO: Search engines read alt text to understand image content. While SVGs are often used for icons or decorative elements, providing descriptive alt text helps search engines index your page content more accurately and can contribute to image search visibility. 💡 What Alt Text Should You Write for an SVG? The right alt text depends on the purpose of the SVG on your page. Use the guidance below to decide: - Informative SVG (charts, diagrams, illustrations): Write a concise description of what the image communicates. For example: "Bar chart showing monthly organic traffic growth from January to June 2025." - Functional SVG (logos, buttons, icons that link somewhere): Describe the action or destination. For example: "Search Atlas logo — link to homepage" or "Download report icon." - Decorative SVG (purely visual, adds no information): Use an empty alt attribute: alt="". This tells screen readers to skip the image, which is the correct approach for decoration-only graphics. Keep alt text under 125 characters, avoid phrases like "image of" or "graphic of," and include a relevant keyword naturally if it fits the context — do not force it. ⚠️ Will Skipping SVG Alt Text Hurt My SEO? Yes, leaving SVG alt text empty or absent can have a negative impact in several ways: - Missed ranking signals: Search engines cannot interpret the SVG content without alt text, so you lose a potential on-page optimisation opportunity. - Accessibility penalties: Poor accessibility can indirectly affect SEO. Google has stated that it values pages that are usable by all visitors. - Audit score: Unresolved alt text tasks will continue to lower your Onpage Audit score in Search Atlas, which affects your overall site health rating. Addressing these tasks is a quick win that improves both your SEO performance and the experience for all users visiting your site. 🛠️ How to Fix SVG Alt Text Issues 1. Open your Onpage Audit report in Search Atlas and locate the task flagging missing alt text on an SVG image. 2. Visit the page in question and identify the SVG — check your page source or CMS if the preview is not visible in the audit panel. 3. Determine whether the SVG is informative, functional, or decorative (see the guidance above). 4. Add the appropriate alt attribute directly in your HTML, CMS, or page builder. For decorative SVGs, add alt="". For all others, write a descriptive, keyword-relevant phrase. 5. Save your changes, re-crawl the page, and re-run the Onpage Audit to confirm the task is resolved. ✅ Quick Reference: Alt Text Cheatsheet - Informative SVG: Describe the content clearly and concisely. - Functional SVG: Describe the action or link destination. - Decorative SVG: Use alt="" (empty, not missing). - All cases: Keep it under 125 characters and avoid keyword stuffing. 💬 Still Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🖼️ OTTO SEO SVG Images and Bulk Exclusion

🔍 Overview OTTO SEO can automatically generate alt text for images across your site, but this feature only works with specific image formats. If your site contains SVG images, OTTO SEO will flag them as missing alt text — but it cannot generate alt text for SVGs. This article explains why, and walks you through the fastest way to bulk-exclude those URLs so they stop appearing in your task list. ⚠️ SVG Format Is Not Supported OTTO SEO's alt text generation engine does not support the SVG (Scalable Vector Graphics) format. SVG files are code-based and structured differently from raster formats, which prevents OTTO SEO from analysing and describing their visual content. Supported formats for alt text generation include: - JPEG / JPG - PNG - WebP - GIF - BMP If you see SVG image URLs listed under your alt text tasks in OTTO SEO, those items will not be resolved by enabling alt text generation or using the Enable All option. Applying those actions to SVG URLs has no effect and will not fix the flagged issues. 🚫 Why You Should Not Use "Enable All" for SVG URLs A common workaround — enabling alt text generation for all flagged image URLs at once — does not apply to SVGs. Because the format is unsupported, OTTO SEO will skip SVG files during processing regardless of whether they are toggled on. This means: - SVG URLs remain unresolved in your task list - Your completion rate appears lower than it actually is - You may waste time re-checking tasks that can never be completed The correct approach is to exclude SVG URLs in bulk so they are removed from your active task queue entirely. ✅ How to Bulk-Exclude SVG URLs from OTTO SEO Follow these steps to remove SVG image URLs from your OTTO SEO task list in bulk: 1. Go to OTTO SEO → All Sites (SEO Automation) in the left sidebar of your Search Atlas dashboard (URL: /seo-automation-v3). 2. Open the OTTO SEO session for the relevant site. 3. Navigate to the Images or Alt Text task section where your SVG URLs are listed. 4. Use the filter or search function to isolate URLs containing .svg in the file path or extension. 5. Select all filtered SVG URLs using the bulk-select checkbox at the top of the list. 6. Click the Exclude or Ignore option from the bulk-action menu to remove them from your active task queue. Once excluded, these URLs will no longer appear in your task list or affect your overall completion metrics. 🕷️ Prevent SVG URLs from Being Crawled If your site has a large volume of SVG files — such as 700 or more — you can stop them from being surfaced in future crawls altogether by setting up a crawl filter. This prevents OTTO SEO from flagging new SVG images as tasks when your site is re-crawled. To set up a crawl filter for SVG files: 1. Go to OTTO SEO → All Sites (SEO Automation) at /seo-automation-v3, open your project, and click the Autopilot / Smart Crawl card to open the OTTO SEO Settings modal. 2. Under URL Exclusion conditions, click + Add condition and set it to Exclude all URLs that Contains .svg. 3. Click Update Settings and trigger a new crawl. SVG URLs matching the exclusion pattern will be skipped during the crawl and will not appear as open tasks in your OTTO SEO session going forward. 📋 Quick Reference: SVG and OTTO SEO - Can OTTO SEO generate alt text for SVGs? No. SVG is not a supported format. - Will enabling alt text generation fix SVG tasks? No. SVG files are skipped regardless. - Best action for existing SVG tasks: Bulk-exclude them from your task list. - Best action for future crawls: Add a URL Exclusion condition set to Contains .svg. - Does this affect your SEO score? Excluding unsupported formats from OTTO SEO tasks does not negatively impact your site's SEO — SVGs typically do not benefit from alt text in the same way raster images do. 💬 Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔄 OTTO's Automatic Weekly Recrawl and Reprocess Cycle

🤖 Does OTTO Recrawl My Site Automatically? Yes — OTTO automatically recrawls and reprocesses every connected project once per week. You do not need to take any action to trigger this. The weekly review runs in the background without any manual intervention required. 🕐 When Does the Weekly Recrawl Happen? OTTO runs its automatic weekly recrawl and reprocess cycle every seven days from the date your project was last processed. The crawl does not run at a fixed clock time visible to users — it is queued and executed by OTTO's internal scheduler, typically within a standard business processing window. Because exact timing can vary slightly based on server load, you may notice the updated results appear at different times of day from week to week. To check when your project was last processed, go to OTTO SEO → Site Audit → Overview (Website Overview) and look at the Last Crawled timestamp, or OTTO SEO → Site Audit → All Audits (Site Audit) where each site card shows the Last crawl timestamp. ⚡ How to Manually Trigger a Recrawl or Reprocess If you cannot wait for the automatic weekly cycle — for example, after publishing a batch of fixes or launching new content — you can manually trigger a recrawl or reprocess at any time: 1. Open the OTTO section from your Search Atlas dashboard. 2. Select the project you want to recrawl. 3. Click the Recrawl or Reprocess button located in the project toolbar at the top of the page. 4. Confirm the action when prompted. OTTO will queue the request immediately. Depending on your site size, the crawl may take a few minutes to several hours to complete. You will see the Last Crawled timestamp update once the cycle finishes. ✅ What Happens After the Recrawl Completes? Once OTTO finishes the recrawl and reprocess cycle — whether automatic or manual — the following occurs: - Issue detection refreshes: OTTO re-evaluates your site against all active SEO rules and updates any previously detected issues. - Resolved issues are marked closed: If OTTO confirms that a fix has been successfully implemented, the corresponding issue status updates automatically. - New issues are surfaced: Any problems introduced since the last crawl are flagged and added to your active issue list. - Scores and recommendations update: Your overall site health score and prioritised recommendations reflect the latest crawl data. You do not need to refresh the dashboard manually — OTTO updates your project view once processing is complete. 📋 Quick Reference Summary - Automatic recrawl: Yes, every 7 days from the last processed date. - Fixed schedule: No fixed clock time; runs on a rolling 7-day cycle. - Manual trigger: Available at any time via the Recrawl / Reprocess button in OTTO. - After recrawl: Issues are re-detected, resolved items closed, and scores updated. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Deploying custom JSON-LD via Custom HTML when automated schema tab locked

Why the Schema tab may be locked In Search Atlas, the automated schema tab is available on certain plan tiers. If your account does not include access to the automated schema generator, or if the tab appears locked or grayed out, you can still deploy valid JSON-LD structured data to your pages by using the Custom HTML block instead. This is the supported workaround for adding schema markup manually. How to deploy custom JSON-LD via Custom HTML 1. Navigate to the page editor for the page you want to add structured data to. 2. Locate the Custom HTML section or block within the page settings or editor. 3. Write or paste your JSON-LD structured data, wrapped in a standard <script> tag with type="application/ld+json", into the Custom HTML field. For example: <script type="application/ld+json"> { your JSON-LD object here } </script> 4. Save your changes and publish or update the page. 5. To verify your structured data is live and valid, paste your page URL into Google's Rich Results Test (search.google.com/test/rich-results) or the Schema Markup Validator (validator.schema.org). Tips for valid JSON-LD - Make sure your JSON-LD follows the correct schema.org vocabulary for your content type (e.g. Article, Product, FAQPage, LocalBusiness). - Only one JSON-LD script block per schema type is needed per page — duplicate types can cause validation warnings. - The Custom HTML block accepts any valid HTML, so you can add multiple separate <script type="application/ld+json"> blocks if you need to deploy more than one schema type on the same page. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚙️ OTTO MetaSync Setup, Rate Limiting, and AIOSEO Deployment

Overview OTTO MetaSync is a feature inside SearchAtlas that synchronises meta titles and descriptions between SearchAtlas and your WordPress site. When configured correctly, it can push changes to plugins like AIOSEO. However, MetaSync operates by making API calls on page load, which can contribute to rate limiting errors and slower page load times if the live connection is not managed carefully. This article explains what is known about how SearchAtlas handles meta deployment to AIOSEO, what MetaSync's runtime dependency means for your site, and what steps to take if you are experiencing rate limiting or performance issues. How SearchAtlas Deploys Meta Changes to AIOSEO When SearchAtlas pushes updated meta titles or descriptions to your WordPress site via MetaSync, those values may appear dynamically through the live API connection rather than being written permanently into your SEO plugin's database. This means: - Meta values delivered through the active MetaSync connection appear on your site as long as the connection is live, but they may not be stored inside AIOSEO's own database fields. - If you want meta values to be fully persistent and independent of the SearchAtlas connection, you need to also save them directly inside AIOSEO. To do this, open the AIOSEO settings for each page or post in your WordPress admin panel, enter the desired meta title and description into AIOSEO's own fields, and save the record. This removes the live API dependency for those fields. Key point: Saving meta values inside AIOSEO directly is the recommended approach for high-traffic sites or any site where an external runtime dependency could cause performance or reliability issues. MetaSync Runtime vs. Persistent Storage Understanding the difference between these two modes helps prevent unexpected behaviour: - Runtime (MetaSync active): Meta titles and descriptions are delivered via the live SearchAtlas API connection. Changes made in SearchAtlas can propagate quickly, but every page load may involve an external API call, which can introduce latency or trigger rate limiting under high traffic. - Persistent storage (AIOSEO direct): Meta values are saved inside the AIOSEO plugin database on your WordPress server. No external API call is required on page load. Updates need to be made in both SearchAtlas and AIOSEO separately, but your site has no external runtime dependency for those fields. For high-traffic sites or sites with strict performance requirements, persistent storage is the recommended approach. Rate Limiting Errors and Page Load Slowdowns If your site is experiencing rate limiting errors or page load slowdowns that appear related to MetaSync, the core issue is that the active MetaSync connection is generating API calls that exceed rate limits or add latency. The known resolution for this is to reduce or eliminate the runtime dependency by saving meta values directly inside AIOSEO rather than relying on the live SearchAtlas connection for delivery on each page load. To address this: 1. Identify which pages are affected — check whether the slowdowns or errors correlate with pages whose meta values are being delivered via MetaSync rather than stored in AIOSEO directly. 2. For each affected page, open the AIOSEO settings in your WordPress admin panel, manually enter the correct meta title and description into AIOSEO's own fields, and save. Once the values are stored in AIOSEO directly, those pages no longer depend on a live API call for their meta data. 3. If you are unsure whether MetaSync is contributing to the issue or need the MetaSync connection adjusted or disabled at the account level, contact the support team so they can review your specific configuration and take action on the backend if needed. When reaching out, have your site URL, a description of the symptoms (including any error messages and approximate timestamps), and your SearchAtlas account email ready. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Identify Your Search Atlas Dynamic Optimization Snippet

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

⚡ OTTO SEO Features & Metrics Beyond Standard Audits

Overview OTTO SEO is Search Atlas's AI-powered SEO automation layer. While the standard Site Auditor scans your site and surfaces issues, OTTO goes further — it monitors crawl progress in real time and gives you a suite of tools to act on findings automatically. This article explains what OTTO SEO offers beyond a standard scan and how to get the most out of it. Finding OTTO SEO and Crawl Monitoring OTTO SEO is accessible from the left sidebar in Search Atlas via OTTO SEO → All Sites (SEO Automation). Once you are inside the OTTO SEO workspace, you can monitor the status of an active or completed crawl directly from the main dashboard view. The crawl monitoring area typically displays information such as: - Crawl progress — an indicator showing how far along the current crawl is. - Pages crawled — a count of URLs processed so far. - Crawl state — whether OTTO is idle, actively crawling, or has completed its last run. - Last crawl timestamp — when the most recent crawl finished. If you are having trouble locating the crawl status information or it does not appear as expected, our support team can help you confirm the correct navigation path for your account. OTTO SEO vs. Standard Site Auditor: Key Differences Both OTTO SEO and the standard Site Auditor identify on-page and technical SEO issues across your site. The main difference is what happens after issues are found. The standard Site Auditor surfaces problems and recommendations for you to act on manually. OTTO SEO is designed to go further by providing automation capabilities that allow you to act on those findings directly within the platform, rather than having to implement changes outside of Search Atlas. If you want to understand exactly which automation features are available on your current plan or how a specific capability works, the support team can walk you through what is accessible in your account. Getting the Most from OTTO SEO To make the best use of OTTO SEO for crawl monitoring and feature comparison: 1. Log in to Search Atlas and navigate to OTTO SEO → All Sites (SEO Automation) from the left sidebar. 2. Run or trigger a crawl for your connected project. 3. Review the crawl status area to track progress and see when results are ready. 4. Once the crawl completes, explore the available tools and recommendations within OTTO SEO to see what actions can be taken on identified issues. 5. If you are unsure whether a specific feature (such as automated fixes or advanced link-building tools) is included in your plan, check your account settings or contact support for clarification. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 Add Keywords to OTTO Semantic Optimization

🎯 What This Article Covers This guide shows you exactly how to find the Semantic Optimization feature inside OTTO and add local keywords — such as Mercedes Repair Near Me — to help your pages rank higher in local search results. 🗺️ Where to Find OTTO and Semantic Optimization OTTO lives inside the OTTO SEO section of Search Atlas. Follow this exact path to reach Semantic Optimization: 1. In the left sidebar, click OTTO SEO. This takes you to /seo-automation-v3. 2. Your OTTO dashboard will load. At the top of the page, locate the tab or section labelled OTTO (it may be pre-selected by default). 3. Inside the OTTO workspace, find and click the Semantic Optimization tab. It appears in the horizontal navigation bar within the OTTO panel. Quick path summary: Left sidebar → OTTO SEO → OTTO panel → Semantic Optimization tab. ➕ How to Add a Local Keyword to Semantic Optimization Once you are inside the Semantic Optimization tab, follow these steps to add your target keyword: 1. Click the Add Keyword button. It appears near the top-right of the Semantic Optimization panel. 2. In the input field that appears, type your target keyword exactly as you want it — for example: Mercedes Repair Near Me. 3. If a location or geo-target field is shown, enter your target city or service area (for example, Los Angeles, CA) to strengthen local relevance. 4. Click Save or Confirm to add the keyword to your list. 5. Repeat for any additional local keyword variants (for example, Mercedes Service Near Me, Mercedes Mechanic [City]). OTTO will now factor these keywords into its on-page recommendations and content suggestions for the pages you have connected. 📋 How to Prioritize Keywords for Local Ranking Adding keywords is only the first step. Use the following best practices to maximize local ranking impact: - Use intent-specific phrasing: Include Near Me, city names, and service-type modifiers (e.g., Mercedes Repair Shop Dallas) to signal local intent to search engines. - Prioritize high-value keywords first: If the interface allows you to drag and reorder keywords, place your primary local keyword — the one driving the most business value — at the top of the list. - Apply OTTO's suggestions: After saving your keywords, OTTO will generate on-page optimization tasks. Click Apply or Deploy next to each recommended change to push updates to your page. - Review regularly: Local search intent shifts seasonally. Revisit your keyword list monthly and add new geo-targeted terms as your service area grows. 📍 Boosting Local Visibility with the Local Section Semantic Optimization handles your on-page signals. For a complete local SEO strategy, also use the Local section of Search Atlas to manage your Google Business Profile and citations: - Left sidebar → GBP Projects → Overview — review your local presence at a glance. - Left sidebar → Local → Local Citations — build and audit NAP citations that reinforce your location relevance. - Left sidebar → Local → Posts — publish Google Business Profile posts that reference your target keywords. - Left sidebar → Local → Reviews (GBP Reviews) — monitor and respond to reviews, which are a key local ranking factor. Combining OTTO's Semantic Optimization with a strong Local profile gives search engines consistent, location-specific signals that improve rankings for queries like Mercedes Repair Near Me. ❓ Frequently Asked Questions - I cannot see the Semantic Optimization tab inside OTTO. Ensure you are in the OTTO SEO section (left sidebar → OTTO SEO) and that a website project is selected. If the tab is still missing, your current plan may not include this feature — check your subscription or contact support. - How many keywords can I add? The limit depends on your plan tier. You will see an on-screen counter or a prompt when you approach the limit. - Will changes deploy automatically? No. OTTO generates recommendations but you must review and click Apply or Deploy for each change to go live on your site. - How long before I see ranking improvements? On-page changes typically take 2–6 weeks to be re-crawled and reflected in search rankings, depending on your site's crawl frequency. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

📊 SEO Score vs Content Score in the Editor

📖 Overview When editing an article in Search Atlas, you will notice two distinct scores: the SEO Score and the Content Score. These scores measure different aspects of your content's quality and optimization. This article explains where to find each score and what each one means. 🗺️ Where to Find Your Article Scores Both scores are accessible through the Content section of Search Atlas. Follow these steps to locate them: 1. Click Content in the left sidebar. 2. You will land on the Content Genius home page, which lists all your articles. The Content Score for each article is displayed directly in this article list. 3. To open an article and view both scores, click on the article title. 4. Once inside the article editor, look at the right-hand panel. The SEO Score and the Content Score are both displayed here at the article level. 📈 What Is the Content Score? The Content Score reflects the overall quality and depth of your written content. It evaluates factors such as: - Use of relevant terms and semantically related keywords - Coverage of key topics that top-ranking competitors address - Word count and content comprehensiveness - Readability and structure The Content Score is the value shown on the Content Genius home page next to each article, giving you a quick snapshot of content quality without opening the editor. This score updates as you make changes inside the article editor. 🔍 What Is the SEO Score? The SEO Score is a broader on-page optimization metric. It evaluates technical and structural SEO elements within the article, such as: - Keyword placement in the title, headings, and meta description - Internal and external linking - Image alt text usage - On-page SEO best practices aligned with search engine guidelines The SEO Score gives you a signal of how well the article is optimized for search engines beyond content depth alone. ⚖️ Key Differences at a Glance - Content Score — measures content quality, topical coverage, and semantic richness. - SEO Score — measures on-page technical optimization and structural SEO factors. - The Content Score is visible in the article list on the Content Genius home page. - The SEO Score is visible inside the article editor in the right-hand panel. - Both scores update in real time as you edit your article. 💡 Tips for Improving Both Scores - Use the keyword and topic suggestions in the right-hand panel to raise your Content Score by covering recommended terms. - Check the SEO recommendations panel for action items such as adding your target keyword to the meta description or adjusting heading structure to improve your SEO Score. - Aim to improve both scores together — strong content quality combined with solid on-page SEO gives your article the best chance of ranking. 🛠️ Still Have Questions? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

📊 Understanding OTTO Open Graph Description Suggestions

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

🔍 Why OTTO Suggests Short Open Graph Descriptions

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

🗂️ Schema Markup Options in OTTO SEO Onpage Optimizations

🧭 Accessing Schema Options in OTTO SEO Schema markup in OTTO SEO is managed directly inside the platform. To work with schema settings for a page, navigate to OTTO SEO → All Sites → [your project] → Overview → Onpage Optimizations (OTTO Grader) and locate the page you want to update. From there, you can view and configure the schema markup options available for that page. Any schema you may have added through WordPress plugins or theme settings is separate from what OTTO SEO manages and may conflict with OTTO SEO's schema output. It is best to manage schema from one source to avoid conflicts. 📋 Schema Types in OTTO SEO OTTO SEO provides schema markup options within the Onpage Optimizations section. The schema types available to you will depend on the page type and your site configuration. For specific questions about which schema types are supported for your use case, our support team can confirm what is currently available in your account. For a veterinary emergency services page, the most semantically appropriate schema is one that describes the service being offered — such as a Service schema type — rather than a schema type intended for FAQ or article content. FAQPage schema should not be used as the primary schema type for a services page — it is only appropriate when FAQ content is the main purpose of the page. 🏥 Choosing the Right Schema for a Veterinary Services Page If you are optimizing a page that describes a specific veterinary service — such as emergency care, vaccinations, or surgery — select a schema type that reflects a defined service offering. This helps search engines understand what the page represents and improves its eligibility for rich results. If you are unsure which schema type to apply, or if you do not see the schema option you expect in the platform, reach out to our support team for guidance on the best option for your page. 🔧 Troubleshooting Missing Schema Options If you cannot locate a schema option you expect to see, consider the following: - Confirm you are in the correct section of OTTO SEO for the page you want to optimize. - Check whether a third-party plugin or theme is already injecting schema for that page, which may affect how OTTO SEO handles schema for it. - Contact our support team to verify whether the schema type you need is available for your account and page type. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚡ OTTO SEO Bulk Deployment for Large Page Counts

Overview When deploying OTTO SEO recommendations across a large site with many pages, the process may take longer than expected or appear to stall. This article explains what to keep in mind when running bulk deployments at scale and how to get the right support if you run into issues. What to Know About Large-Scale OTTO SEO Deployments Deploying OTTO SEO recommendations across a high page count (for example, 100 or more pages) can be resource-intensive. If your deployment appears slow, unresponsive, or incomplete, this is often related to the volume of pages being processed at once rather than an error in your setup. To reduce the risk of issues during large deployments, consider the following general guidance: - Deploy in smaller groups: Rather than attempting to deploy all pages at once, work through your pages in smaller groups to give the system time to process each set before moving on. - Allow time between deployments: Wait for one group to finish processing before starting the next. Triggering multiple large deployments simultaneously can cause delays or incomplete results. - Review results after each group: After each deployment group completes, check that the pages reflect the expected changes before continuing. When to Contact Support Because the optimal batch size, available deployment controls, and expected processing times depend on your specific site configuration and account setup, our support team can review your project directly and provide tailored guidance for your situation. When reaching out, please have the following ready to help us assist you faster: - Project or website name as it appears in your Search Atlas account - Total number of pages you are trying to deploy - Description of what you are seeing — for example, whether the deployment appears stuck, returns an error, or completes but shows unexpected results - Any error messages displayed on screen, including exact wording - Approximate time and date when the issue occurred If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ How to Confirm OTTO SEO Changes Deploy to Shopify

When OTTO SEO marks a change as deployed, it means the change was pushed from Search Atlas toward your connected Shopify store — but the word alone does not confirm that Shopify accepted and saved the update. This article explains the distinction, walks you through verifying a successful write to Shopify, and tells you exactly what to check when a deployed change does not appear on your storefront. 🔍 What "Deployed" Actually Means Search Atlas uses deployed to indicate that the change has been sent through the integration. Whether that change is visible in Shopify depends on two additional conditions being true: the Shopify connection must be active and authenticated at the moment the change is pushed, and Shopify must have accepted the write without an API error. A status of deployed reflects the outbound action from Search Atlas — not a confirmed receipt from Shopify. 🛠️ Step-by-Step 1. Check your Shopify connection status. Open your project settings and look for the Shopify integration section. Confirm the store URL is correct, the access token has not expired, and the connection shows as active. A disconnected or re-authenticated store will silently drop pushes. 2. Re-verify the specific change in Shopify directly. Log in to your Shopify admin, navigate to the product, page, collection, or blog post that was updated, and inspect the field that OTTO SEO targeted (meta title, meta description, or on-page content). Compare what is in Shopify with what Search Atlas shows as the deployed value. 3. Check for Shopify theme or app conflicts. Some Shopify themes and third-party SEO apps override meta fields at render time. Even if Search Atlas successfully wrote the value, another app may be outputting its own value. Temporarily disable conflicting apps and preview the page source to confirm which value Shopify is serving. 4. Review the deployment log for errors. In your OTTO SEO project, open the activity or deployment history for the affected page. Look for any error flag, API timeout notice, or partial-success indicator next to the deployed item. If an error is logged, reconnect your Shopify integration and re-deploy the change. 5. Re-deploy the change manually if needed. If the value in Shopify does not match what Search Atlas deployed, use the re-deploy or re-publish action on the individual optimization to trigger a fresh write attempt after confirming the connection is healthy. ✅ How to Confirm It Worked A deployment is confirmed successful only when all three of the following are true: - Shopify admin matches: The field value in your Shopify admin (e.g., the SEO title or description on the product or page edit screen) exactly matches the value Search Atlas deployed. - Live page source matches: Right-click your Shopify storefront page, select View Page Source, and search for the <title> tag and og:description or meta name="description" meta tag. The rendered values should match what was deployed. - No override is active: No other Shopify app or theme snippet is replacing the value that Search Atlas wrote. If the Shopify admin shows the correct value but the live page does not, the issue is a theme or app override — not a failed deployment. If the Shopify admin still shows the old value, the write did not complete and the steps above should be repeated after reconnecting the integration. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🚀 Deploying More Than 100 OTTO Improvements at Once

Overview OTTO SEO allows you to deploy site improvements in bulk directly from the dashboard. This article explains what to expect when you have more than 100 improvements queued and how to work through large volumes efficiently. Deploying Large Batches of Improvements If you have more than 100 improvements ready to deploy in OTTO SEO, you may find that not all improvements are deployed in a single action. This is expected behaviour when working with large improvement queues. To work through a large queue of improvements: 1. Open OTTO SEO from your Search Atlas dashboard and navigate to the site you want to optimise. 2. Review your queued improvements and identify which items are ready to deploy. 3. Select and deploy your improvements. If you have more than 100 items, work through them in batches, allowing each deployment to complete before proceeding further. 4. Repeat the process for any remaining improvements until all fixes have been deployed. If OTTO reports fewer deployed fixes than the total the audit found, this is normal when dealing with high volumes — continue working through the queue in subsequent deployment actions until all improvements have been applied. Tips for Managing High-Volume Deployments - Check progress after each batch: After deploying, revisit the improvement list to confirm which items have been applied and how many remain. - Be patient with large queues: High volumes may require multiple deployment actions to fully complete. Avoid interrupting an in-progress deployment. When to Contact Support If improvements appear stuck, fail to deploy after repeated attempts, or the number of deployed fixes does not increase over time, our team can investigate further. Please have the following ready when you reach out: your site or project name, the issue types affected, and an approximate count of improvements remaining in the queue. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

📅 OTTO Topical Map Articles: Scheduling and Limitations

📋 Overview When OTTO builds a topical map for your site, it generates a structured list of recommended articles designed to improve your topical authority. A common question is whether these articles can be scheduled or automatically published. This article explains the current capabilities and limitations, and also covers how to select the right target pages when using Cloud Stacks. 🤖 Can Topical Map Articles Be Scheduled or Automated? No — scheduling and full automation are not currently available for AI-generated articles produced from topical maps in OTTO. Here is how the current workflow operates: 1. OTTO analyzes your domain and generates a topical map with suggested article topics. 2. You review the suggested topics inside the Topical Maps section. Navigate there by selecting Content > Topical Maps from the left sidebar. 3. You manually select the articles you want to generate. 4. OTTO creates the AI-written content for your chosen topics. 5. You review, edit if needed, and publish each article manually to your site. There is no built-in option to set a publish date, create a recurring content schedule, or trigger automatic publishing to your CMS directly from the topical map workflow at this time. ⚠️ What This Means for Your Workflow Because scheduling is not available, keep the following in mind when planning your content strategy: - Plan in batches: Generate a group of articles at one time, then publish them manually on your preferred schedule through your CMS. - Use your CMS scheduler: If you use WordPress or another CMS that supports scheduled publishing, paste the generated content there and set your desired publish date directly in the CMS. - Review before publishing: Always review AI-generated content for accuracy, brand tone, and any site-specific details before it goes live. - Prioritise by funnel stage: Use the topical map clusters to decide which articles to publish first — typically, pillar pages before supporting cluster content. ☁️ Cloud Stacks: How to Choose Target Pages Cloud Stacks build a network of authoritative cloud-hosted properties that link back to pages on your site, boosting their authority signals. Selecting the right target pages is essential for getting the most from this feature. To access Cloud Stacks, go to Authority in the left sidebar, then select Cloud Stacks. Good examples of target pages for Cloud Stacks include: - Homepage: Strengthens overall domain authority and brand signals. - Core service or product pages: Pages you most want to rank for competitive commercial keywords. - Pillar content pages: Long-form, high-value articles that anchor a topical cluster on your site. - Location pages: For local SEO, target city or region-specific landing pages to build geo-relevant authority. - Category pages: E-commerce or blog category pages that consolidate ranking potential across many related topics. Pages that are generally not ideal targets include: - Thank-you or confirmation pages with no ongoing SEO value. - Login or account pages that are not indexed. - Thin pages with little or no content. - Pages you are planning to delete or redirect soon. 💡 Tips for Getting the Best Results - Target pages that already have some existing authority or traffic — Cloud Stacks amplify what is already working. - Match the anchor text strategy in your Cloud Stack to the primary keyword of the target page. - Combine Cloud Stacks with articles generated from your topical map: publish the articles first, then point Cloud Stacks at the strongest ones to accelerate ranking. - Monitor performance in your rank tracker after deploying a Cloud Stack so you can measure the impact on specific target pages. 🆘 Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛡️ Exclude Pages and Roll Back OTTO Changes

🔍 Overview OTTO SEO automates on-page optimizations across your site, but there are times when you need to protect specific pages from being edited. This article explains how to exclude URLs from OTTO's scope and how to roll back changes OTTO has already applied. 🗺️ How OTTO Page Exclusions Work Exclusions are URL rules configured in your project's OTTO SEO settings. You add a condition (for example, "Exclude all URLs that contain /blog/"), and OTTO's crawler and analyzer skip every URL that matches it. Excluding a URL turns off all of OTTO's optimizations on that page, not just one feature. The rule also covers pages added to your site later, as long as they match the condition. ⚙️ Step 1 — Open OTTO SEO 1. Log in to Search Atlas. 2. In the left sidebar, click OTTO SEO, then open SEO Automation. This opens the All Sites view at /seo-automation-v3. 3. Make sure you select the correct project. ⚙️ Step 2 — Open OTTO SEO Settings 1. Open your project's overview. 2. At the top of the page, click the Autopilot / Smart Crawl card (it shows the gear icon and the next-analysis countdown). This opens the OTTO SEO Settings modal. You can also reach it from the All Sites table by clicking the Smart Crawl status text on your site's card. 🚫 Step 3 — Add URL Exclusion Conditions 1. In the settings modal, scroll to the section titled URL Exclusion conditions. 2. Click + Add condition. 3. Set the fields: - First dropdown: Exclude. - Match type: Contains or Start With. - Text field: type the part of the URL to match, for example /blog/. 4. Click Update Settings to save. OTTO will no longer scan or optimize any URL that matches the condition. Repeat for additional rules if needed (each rule is its own condition). ↩️ Step 4 — Roll Back Changes OTTO Already Made If OTTO has already deployed changes to a page, exclusions alone do not undo them. Roll the changes back first: To roll back a specific page: 1. In the project overview, open Filter by URL and enter the page's URL to see every recommendation OTTO made for it. 2. On each row, click the green Deployed (or Enabled) button in the Status column. This immediately un-deploys OTTO's modification for that item. To roll back a whole category (for example all Page Titles): 1. Open the category table in the project overview. 2. Click Roll back all at the top right of the table and confirm. This reverts every deployed suggestion in that category. 💡 Things to Keep in Mind - Excluding disables everything on that page. OTTO will not apply any new optimization to an excluded URL, and existing deployments are not automatically reverted — roll them back manually as described in Step 4. - Exclusions persist until removed. To let OTTO work on a page again, delete the matching condition in OTTO SEO Settings and click Update Settings. - Rollback only affects OTTO changes. Manual edits you made outside OTTO are not affected. 🆘 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔌 Deploy OTTO Schema Without a Plugin

Overview OTTO can generate and deploy schema markup for your website without requiring a plugin. Instead, you connect your site using a plugin-free verification method. Once connected, OTTO handles schema generation automatically and gives you full control over deployment. Step 1: Connect Your Website Without a Plugin To connect your site to OTTO, navigate to the OTTO SEO section of the platform. If your site is not yet connected, you will be prompted to add it. Search Atlas supports plugin-free site verification methods — check the on-screen instructions when adding your site for the specific options available to you. Follow the prompts to complete verification before proceeding. Step 2: Generate Schema With OTTO After your site is verified and connected, OTTO will begin auditing your pages and identifying schema opportunities. Navigate to your connected site within the OTTO SEO area and look for the schema-related options presented in the interface. Review the schema types OTTO recommends for your pages — these may include types such as Article, FAQ, Product, LocalBusiness, BreadcrumbList, and more — and activate the ones relevant to your content following the on-screen controls. OTTO generates the structured data automatically based on the content of each page. You do not need to write or edit any JSON-LD manually. Step 3: Deploy Schema to Your Website Deployment without a plugin works through the verified site connection you set up in Step 1. When you activate schema in OTTO, the structured data is delivered to your pages through that connection. Ensure that any verification code you placed on your site remains in place, as it may also be used for ongoing schema delivery. If you encounter any issues connecting your site or deploying schema, gather the following before reaching out: your site URL, the verification method you attempted, and any error messages displayed during the process. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

📤 Export OTTO Suggestions and AI Content to Backend

🔍 Overview Once OTTO has analysed your site and generated SEO suggestions, you may want to export those recommendations — along with any AI-generated content — so your development or content team can implement them directly in your website's backend. This article explains what can be exported, where to find the export options, and how to get the content you need. ⚙️ What You Can Export from OTTO OTTO surfaces suggestions across multiple issue categories, including meta tags, headings, content improvements, and more. After reviewing and completing suggestions within a category, you can export the data for use outside the platform. The following types of output are available for export: - Completed OTTO suggestions — the recommended changes OTTO generated for your resolved issue categories - AI-generated content — text produced by OTTO or other AI tools within the platform, such as meta titles, meta descriptions, and on-page copy 🚀 How to Export OTTO Suggestions 1. In the left sidebar, click OTTO SEO → All Sites (SEO Automation) to open the OTTO dashboard. 2. Select the project you want to work with. 3. Navigate to the issue category you have completed (for example, Meta Titles or Meta Descriptions). 4. Look for the Export button — typically represented by a download icon — at the top right of the suggestions table for that category. 5. Click Export to download the suggestions as a CSV file. The file will include the page URL, the original value, and the OTTO-recommended replacement. 6. Repeat this process for each issue category you want to export. Tip: Export your suggestions after marking a category as complete. This ensures the file reflects only the finalised recommendations you intend to implement. 📊 How to Export AI-Generated Content If you have used the AI content tools within the platform — such as the Meta Generator or AI Content Templates — you can retrieve that output from the Content section. 1. In the left sidebar, click Content. 2. Navigate to the relevant sub-page: - Meta Generator (Left sidebar → Content Assistant v3 → Meta Generator) for bulk meta titles and descriptions - AI Content Templates (Left sidebar → Content Assistant v3 → AI Content Templates) for longer-form AI-generated copy - On-Page Audit (Left sidebar → Content Assistant v3 → On-Page Audit) for page-level content recommendations 3. Within each tool, use the available Export or Copy option to save the generated content. CSV and copy-to-clipboard options are available depending on the tool. 4. Paste or upload the exported content into your CMS or backend system as needed. 💡 Tips for Applying Exported Content to Your Backend - Match URLs carefully. Exported CSV files include the page URL in the first column. Use this to match each suggestion to the correct page in your CMS. - Prioritise completed categories. Only export categories where you have reviewed and approved all suggestions to avoid pushing unreviewed content live. - Use bulk import tools in your CMS. Most CMS platforms (WordPress, Shopify, etc.) support CSV imports for meta data, which makes applying OTTO's exported suggestions much faster. - Keep a backup. Before making bulk changes in your backend, export your current meta data as a backup so you can revert if needed. 🛠️ Troubleshooting Common Issues - Export button is greyed out or missing: Make sure the issue category has at least one suggestion marked as complete. The export option may only appear after suggestions have been reviewed. - CSV file is empty: This usually means no suggestions have been generated or completed for that category yet. Return to the OTTO dashboard and confirm the category shows completed items. - Content is not showing in AI Content Templates: Confirm you are viewing the correct project. Use the project selector at the top of the page to switch if needed. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔀 Why OTTO Plugin Creates Redirects Automatically

🔍 Overview Some Search Atlas customers notice that the OTTO WordPress plugin creates redirect rules on their website without an explicit manual instruction. This article explains what is happening and what to do if you experience this. ⚙️ What Is Happening OTTO is an AI-powered SEO automation tool. When it is active on a site, it is designed to apply on-page and technical SEO improvements automatically. However, we have received reports that the OTTO WordPress plugin is creating redirect rules that customers did not authorise or expect. If you are experiencing this issue, you are not alone — our team is aware of reports of this behaviour. 📋 What to Do Right Now Because this issue may require backend investigation, the most reliable next step is to contact our support team directly so we can look into your specific site. When you reach out, please have the following information ready: - Your Search Atlas project or site name — the name of the site where unexpected redirects are appearing. - Examples of the redirects created — the specific URLs being redirected, if you can locate them. Having this information ready will allow our team to investigate your case as quickly as possible and minimise disruption to your site. ⚠️ Important Note If you are concerned about further unauthorised changes to your site, you may consider temporarily deactivating the OTTO WordPress plugin from your WordPress admin dashboard while our team investigates. This will stop OTTO from applying any further automatic changes to your site. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

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

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

⚡ Bulk Keyword Removal and Knowledge Graph Rescan in OTTO SEO

Overview If you need to remove all keyword suggestions across your pages, roll back Missing Keywords Issues, or trigger a full Knowledge Graph rescan in OTTO SEO, this article explains what these actions involve and how to get assistance from our team. What These Actions Cover There are three common tasks users reach out about in this area: - Bulk keyword removal: Removing all suggested keywords across every page at once, rather than clearing them one page at a time. - Rolling back Missing Keywords Issues: Undoing changes that OTTO SEO applied through the Missing Keywords issue category. - Knowledge Graph rescan: Triggering OTTO SEO to rebuild its understanding of your site and generate fresh keyword recommendations. How to Get These Actions Performed Bulk keyword removal, rollback of Missing Keywords Issues, and Knowledge Graph rescans are actions that our support team can perform on your behalf. If you need any of these completed, please contact us directly so we can assist you as quickly as possible. What to Have Ready When You Reach Out To help our team act on your request without delay, please have the following information available: - Your project or site name as it appears in Search Atlas - Which action you need performed (bulk keyword removal, rollback of Missing Keywords Issues, Knowledge Graph rescan, or a combination of these) - Any relevant context, such as when the issue started or what behavior you are seeing in your OTTO SEO dashboard If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🐦 Understanding OTTO Twitter Cards and Manual Entry

What Are Twitter Cards in OTTO? The Twitter Cards section in OTTO lets you control how your pages appear when shared on Twitter (now X). When someone posts a link to your site on Twitter, Twitter reads special meta tags from your page to decide what title, description, and image to display in the preview card. OTTO surfaces these fields so you can set or update them directly from one place without having to edit your site's code or theme files manually. To locate this section, navigate to the OTTO area of your Search Atlas account and look for the Twitter Cards fields within your site's settings. Why Are There No AI Suggestions Here? Unlike other OTTO sections — such as meta titles, meta descriptions, or heading tags — the Twitter Cards section does not generate AI-powered suggestions. This is intentional, not a bug or missing feature. Twitter Card tags are used for social sharing previews, and OTTO's AI automation does not extend to these fields. You are expected to fill them in manually based on your own brand and content preferences. How to Fill In Twitter Cards Manually Because there are no AI suggestions for this section, you will need to enter your Twitter Card values by hand. Open your site's settings within OTTO and locate the Twitter Cards area, then fill in the available fields using your own content. If you are unsure which values to use, a good starting point is to reuse or lightly adapt the meta title, meta description, and featured image you have already set for the page, since Twitter Card fields are designed to mirror that kind of content. If you are having trouble finding the Twitter Cards section or the fields are not behaving as expected, please reach out to our support team with your site name and a description of what you are seeing so we can assist you directly. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚙️ OTTO Page Titles: Generation, Validation, and Bulk Workflows

🔍 Overview This article covers two common OTTO questions agencies encounter: why generated page titles are flagged in red, and how to manage optimizations across multiple clients without clicking each element one by one. Both topics are addressed below. 🚦 Why Page Titles Show as Red in OTTO Red highlighting on a page title means the title exceeds the recommended character limit. OTTO validates title length based on the version of the automation engine your workspace is using. - OTTO v2: Flags titles longer than 60 characters. - OTTO v3: Uses a stricter pixel-width threshold (approximately 580px), which translates to roughly 55–60 characters depending on the characters used. Wider characters such as uppercase letters or W/M can cause a title to fail even if the raw character count appears acceptable. To check which version your workspace is running, go to OTTO SEO → All Sites (SEO Automation). The version indicator appears at the top of the OTTO dashboard. If you are on v3 and titles are consistently flagging red, the pixel-width rule is likely the cause even when character counts look fine. 📋 When OTTO Generates New Titles vs. Copies Existing Ones A frequent source of confusion is that OTTO sometimes produces a suggested title that is identical to the page's current title rather than generating fresh content. This is expected behavior in specific situations, but it can also signal a configuration issue worth checking. OTTO generates a new title when: - The existing title is missing, too short, or does not contain the target keyword. - The page has been crawled recently and OTTO detects a clear optimization gap. - You manually trigger regeneration using the refresh icon on the suggestion card. OTTO copies or preserves the existing title when: - The current title already meets all validation rules (length, keyword inclusion, readability score). - The page was not recrawled before OTTO generated suggestions, so OTTO is working from a cached version that reflects the old title. - The target keyword field for the page is empty, giving OTTO no signal to optimize against. Troubleshooting steps if OTTO is not generating new content: 1. Go to OTTO SEO → All Sites (SEO Automation) and open the affected site in OTTO. 2. Locate the page in the task list and confirm a target keyword is assigned. If the keyword field is blank, add the primary keyword and save. 3. Click the recrawl icon for the page to force a fresh data pull before regenerating. 4. Select the title suggestion card and click the Regenerate (refresh) icon to produce a new suggestion based on updated data. 5. If the regenerated title still copies the existing one, check whether the existing title already satisfies all OTTO criteria. In that case, OTTO considers the title optimized and will not change it unless you manually edit the suggestion. 🏢 Agency Bulk Optimization Workflows Clicking through each optimization element one at a time is time-consuming when managing multiple clients. OTTO and the broader Search Atlas platform offer several ways to process optimizations in bulk. 1. Use OTTO's Deploy All feature Inside the OTTO dashboard (OTTO SEO → All Sites (SEO Automation)), each task category — including page titles, meta descriptions, and schema — has a Deploy All button at the top of the task list. Clicking Deploy All approves and pushes every pending suggestion in that category at once. Review the suggestions in the list view before deploying to catch any titles that are still flagged red. 2. Filter and action by status Use the status filters within each task category to isolate only the items marked Pending or Error. This lets you focus on items that need attention without scrolling past already-deployed optimizations. After filtering, you can select all visible items using the checkbox in the column header and deploy them together. 3. Batch across client sites using the Agency Dashboard If your workspace has multiple client sites connected, navigate to the top-level agency view. From here you can switch between client workspaces quickly without logging out. Plan a workflow where you move through each client site, run a filtered view for pending OTTO tasks, and use Deploy All per category before moving to the next client. 4. Generate meta tags in bulk with Meta Generator For clients who need titles and meta descriptions created before OTTO deployment, use Left sidebar → Content → Meta Generator. You can input multiple URLs or paste a list of page names and generate optimized meta content in one session. Copy the output into OTTO task cards or your CMS directly. 5. Schedule recrawls to keep suggestions fresh Stale crawl data causes OTTO to generate suggestions based on outdated page content. In the OTTO site settings, set a recurring crawl schedule aligned with your client reporting cadence — weekly for active sites, monthly for stable ones. Fresh crawl data means suggestions are relevant when you run bulk deployments and reduces the chance of copying titles that have already been updated. 6. Use On-Page Audit to prioritize which pages need titles first Go to Left sidebar → Content → On-Page Audit and filter by Missing Title or Title Too Long. Export the filtered list and use it as your working checklist inside OTTO, so you deploy high-impact fixes first rather than processing pages in arbitrary order. ✅ Quick Reference - Red title in OTTO v3: Exceeds pixel-width limit — shorten the title or reduce wide characters. - OTTO copying existing titles: Check keyword assignment, recrawl the page, then regenerate. - Bulk deployment: Use Deploy All per task category inside OTTO. - Multi-client efficiency: Filter by Pending status, use Meta Generator for batch creation, schedule recrawls. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔗 Auto-Link Topical Map Articles in OTTO

📋 Overview When you generate articles from a topical map in OTTO, you can have internal and external links added automatically — no manual linking required after the fact. The key is configuring the Links to Include settings in AI Settings before you run article generation. This article walks you through exactly how to do that. 🗺️ How Automatic Linking Works OTTO's AI Settings include a Links to Include section that controls two types of links inserted during content generation: - Global Internal Links — links to other pages on your own website, helping build a connected silo structure across your topical map articles. - Global External Links — links to third-party sources that add authority and context to the generated content. When these settings are configured before generation, OTTO applies them automatically to every article produced from the topical map. There is no separate "Internal Linking Engine" or "Auto-Link by Map" feature — the Links to Include configuration in AI Settings is the correct tool for this workflow. 🛠️ Step-by-Step: Configure Links Before Generating Articles 1. In the left sidebar, click OTTO SEO, then open SEO Automation. 2. Locate the project or site you want to configure, then open its AI Settings. 3. Scroll to the Links to Include section. 4. To add internal links, find the Global Internal Links field. Enter the URLs from your own site that you want OTTO to link to within the generated articles. These should be key pillar pages or other topical map articles you want to interconnect. 5. To add external links, find the Global External Links field. Enter any third-party URLs you want referenced across your generated content. 6. Save your AI Settings. 7. Navigate to Content → Topical Maps in the left sidebar. 8. Select your topical map and proceed to generate articles as normal. OTTO will now apply your configured links automatically during generation. ✅ Tips for Best Results - Add internal links before your first generation run. Links configured after articles are already generated will not be retroactively applied to existing content. - Prioritise pillar pages and cluster hubs in your Global Internal Links list. This strengthens the silo structure across your topical map. - Keep your link list focused. Adding too many URLs can dilute link placement. Aim for the most strategically important pages first. - Review generated articles after the first batch to confirm links are appearing as expected before scaling to larger topical maps. ❓ Frequently Asked Questions Can I add different internal links for different topical maps? AI Settings are configured at the project or site level. If you need different link sets for different topical maps within the same project, you may need to run separate generation batches after updating the settings each time. Will OTTO link to every URL I add on every article? OTTO places links contextually based on relevance within the generated content. Not every URL will appear in every article — the AI selects placements where the link fits naturally. What if I already generated articles without configuring Links to Include? You can manually add internal links to existing articles using the editing tools in Content → Topical Maps, or regenerate articles after configuring the settings. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 OTTO Schema Deployment: Visibility and Implementation Explained

🧩 Overview: Two Types of OTTO Deployments When OTTO applies schema markup or structural suggestions to your pages, it uses one of two deployment methods: code-only (invisible) deployments and visible content deployments. Understanding which method applies to each suggestion type will help you know exactly what changes on your page and what only exists in the source code. ❓ FAQ Schema: Why It's Invisible on Your Homepage When OTTO deploys FAQ schema markup, it injects structured data directly into your page's <head> or as a JSON-LD script block. This is a code-only deployment — it does not add any visible FAQ content to your page. Search engines like Google can read this structured data and may display rich results (expandable Q&A entries) in search listings, but your website visitors will see no change to the page itself. This is expected and correct behaviour. You do not need to add visible FAQs to your homepage for the schema to work. However, if you want FAQ content to be visible to visitors, you can add it manually as regular page content. 📋 Should You Add Visible FAQs Manually? Adding visible FAQ content to complement OTTO's schema deployment is optional, not required. If you choose to add visible FAQs, keep the following in mind: - No duplicate content penalty applies — having both visible FAQ content and FAQ schema on the same page is standard practice and is not treated as duplicate content by search engines. - The visible text and the schema questions/answers do not need to be word-for-word identical, but they should be consistent in meaning. - Adding visible FAQs can improve user experience and may increase dwell time, which is a positive SEO signal. In short, adding visible FAQs alongside OTTO's schema is safe and can strengthen your page's SEO — it will not harm your rankings. 📰 Why Is OTTO Suggesting Article Schema for Your Homepage? Article schema is a page-level schema type, meaning it describes the overall nature and content of the page to search engines rather than marking up a specific element like a product or FAQ. OTTO may suggest Article schema for your homepage when it identifies that the page contains editorial or informational content that would benefit from structured metadata — such as a publish date, author, or headline property. This suggestion does not mean your homepage should look like a blog post. Article schema operates entirely in the background as structured data. It tells search engines how to categorise your page's content, which can improve how your listing appears in search results. Accepting this suggestion will not change the visual layout or design of your homepage in any way. 🏷️ What Does "Page-Level Schema" Mean? Page-level schema refers to structured data that describes the page as a whole, rather than a single component within it. Common page-level schema types include: - Article — marks the page as informational or editorial content - WebPage — provides general metadata about any web page - FAQPage — signals that the page contains question-and-answer content All page-level schema is deployed as invisible structured data. It is read by search engine crawlers but produces no visible output on your page for visitors. 🔤 H2 Suggestions: Visible or Invisible? This is an important distinction. H2 heading suggestions from OTTO are visible content deployments — they are not injected as invisible elements or hidden code. When OTTO deploys an H2 suggestion, it adds or modifies an actual heading tag within your page's visible content structure. Here is what you need to know about H2 deployments: - Deployed H2 tags appear as visible headings on your published page. - They are part of your page's HTML structure and contribute to both readability and on-page SEO. - They are not schema markup — they are structural HTML elements, separate from JSON-LD structured data. - If OTTO suggests an H2 and you deploy it, the heading will be visible to all visitors browsing your page. If you see an H2 suggestion in OTTO but are unsure whether it has been deployed, navigate to OTTO SEO → All Sites (SEO Automation) and review the deployment status for that specific suggestion. A deployed H2 will reflect in your live page content. 📊 Quick Reference: Deployment Types at a Glance - FAQ Schema (FAQPage) — Code only. Invisible to visitors. Eligible for rich results in search. - Article Schema — Code only. Invisible to visitors. Improves search categorisation. - H2 Heading Suggestions — Visible content. Appears as a heading on your live page. - WebPage / Other Page-Level Schema — Code only. Invisible to visitors. 🛠️ How to Review and Manage OTTO Deployments 1. Go to OTTO SEO → All Sites (SEO Automation) (or navigate to /seo-automation-v3). 2. Select the page you want to review. 3. Browse the suggestion list and check the status column — look for Deployed, Pending, or Not Deployed labels. 4. For schema suggestions, you can preview the generated JSON-LD before accepting. 5. For H2 suggestions, the preview will show the heading text that will appear on your page. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

📊 Find OTTO Pixel Data Options in Search Atlas

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

🛠️ OTTO SEO: Exclude URLs, Boost GBP Rankings

🔍 Overview This article explains two things: how to exclude specific URLs from OTTO SEO scans, and how to improve your Google Business Profile (GBP) ranking and reach a perfect score of 100. Both actions help you get cleaner SEO automation and stronger local visibility. ⚙️ How to Exclude URLs from OTTO SEO Scans If there are pages you do not want OTTO to scan or apply optimisations to — such as thank-you pages, internal tools, or staging URLs — you can exclude them directly inside the OTTO SEO section. 1. In the left sidebar, click OTTO SEO and then open SEO Automation (All Sites view at /seo-automation-v3), and open your project. 2. At the top of the project overview, click the Autopilot / Smart Crawl card to open the OTTO SEO Settings modal. You can also reach it from the All Sites table by clicking the Smart Crawl status text on your site's card. 3. Scroll to URL Exclusion conditions and click + Add condition. 4. Set the condition to Exclude all URLs that Contains (or Start With) the text you want to skip — for example, Contains /thank-you/ matches every page with that path. 5. Click Update Settings. OTTO will skip those URLs in all future scans and will not apply automated fixes to them. Tip: Review your excluded URL list periodically. Pages that were once excluded may later need optimisation as your site evolves. 📊 How to Improve Your GBP Score to 100 Your Google Business Profile (GBP) score reflects how complete and optimised your local listing is. A score of 100 signals to Google that your profile is fully set up, which supports higher local rankings and greater visibility in map results. To access your GBP project and start improving your score, navigate to Left sidebar → Local → GBP Projects. From here you can work across all the sub-sections that contribute to your overall score. ✅ Key Areas That Improve Your GBP Score Focus on the following actions inside the Local section to push your score toward 100: - Overview: Go to Local → Overview to see your current score and a breakdown of what is complete and what still needs attention. Use this as your starting checklist. - Posts: Go to Local → Posts and publish regular Google posts — promotions, updates, events, or offers. Consistent posting signals an active, trustworthy business. - Reviews: Go to Local → Reviews to monitor and respond to customer reviews. Responding to reviews, both positive and negative, is a ranking factor and contributes to your profile score. - Media Library: Go to Local → Media Library to upload high-quality photos and videos. Profiles with rich media consistently outperform those without. - Local Citations: Go to Local → Local Citations to build and manage citations across directories. Consistent NAP (Name, Address, Phone) data across the web reinforces your local authority and improves map pack rankings. - My Tasks: Go to Local → My Tasks to see a prioritised list of recommended actions. Complete these tasks in order to make the fastest progress toward a score of 100. 🚀 Tips for Expanding Local Reach Beyond hitting a score of 100, the following practices will help you expand how many local searches your business appears in: - Target multiple service areas: If your business serves more than one location, make sure each area is reflected in your GBP settings and citation profiles. - Use location-specific keywords in posts: When writing posts inside Local → Posts, include city or neighbourhood names naturally in your content. - Build citations consistently: Use Local → Local Citations to submit your business to high-authority directories. The more consistent and widespread your citations, the broader your local footprint. - Keep your profile active: Google rewards profiles that are updated regularly. Aim to post at least once a week and respond to new reviews within 24 hours. 💡 Frequently Asked Questions Will excluding a URL remove it from my site's overall SEO? No. Excluding a URL only prevents OTTO from scanning and automating changes on that page. It does not affect how Google crawls or indexes the page. Why is my GBP score not reaching 100? Open Local → Overview to see exactly which items are incomplete. The most common gaps are missing photos, unanswered reviews, and no recent posts. How long does it take for GBP improvements to affect rankings? Changes to your profile can start showing results within a few days, but meaningful ranking improvements in competitive areas typically take two to four weeks of consistent activity. 🙋 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

📋 Track and Review AI-Generated Changes in Search Atlas

🧭 Overview Search Atlas supports bulk AI content generation, bulk editing of AI-generated title tags across multiple pages, and reviewing a log of changes made by AI within your account. This article explains what these capabilities cover and how to get help locating them in the platform. ✅ Bulk AI Content Generation Search Atlas allows you to generate AI content for multiple pages at once rather than working through them individually. This is useful when you need to produce or refresh content at scale. The exact steps and button labels for triggering bulk generation depend on your account configuration and the current version of the platform. To use this feature: 1. Log in to your Search Atlas account and navigate to the content management area of the platform. 2. Look for a bulk generation or multi-select option within the content or task list view. 3. Select the pages or tasks you want to include, then initiate the AI generation process. 4. Wait for each task to complete — generated content will appear once the process finishes. If you are unable to locate the bulk generation option in your current view, it may be available under a different section depending on your plan or workspace setup. ✏️ Bulk Editing AI-Generated Title Tags Once AI content has been generated, Search Atlas provides a way to edit title tags across multiple pages at the same time. To use this: 1. Navigate to the content or task list where your AI-generated pages are listed. 2. Select multiple pages using the checkboxes or multi-select controls available in that view. 3. Look for a bulk edit or batch action option that appears when multiple items are selected. 4. Apply your updated title tag value or transformation, then confirm the changes. Tip: Review AI-generated title tags before bulk editing to ensure the updates align with your target keywords and brand guidelines. 🕓 Accessing a Log of AI-Driven Changes Search Atlas includes change-tracking functionality so you can review what was updated by AI, when it happened, and what type of change was made. This audit history is accessible from within your account settings or a dedicated log area in the platform. To find the change log: 1. Log in to Search Atlas and open your account or settings menu. 2. Look for an activity log, audit log, or change history section within account settings. 3. Once located, you should be able to view a timestamped record of AI-driven and manual changes made in your account. 4. Sorting or filtering options may be available to help you narrow down entries by date or change type. If you cannot locate the change log or are unsure which section of the platform contains it, our support team can point you to the correct location for your account. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Deploy Custom JSON-LD via OTTO Custom HTML

🧭 Overview If the automated schema tab in OTTO Agent is locked — for example, because your plan does not include that feature or the tab is managed automatically — you can still deploy custom JSON-LD structured data using the Custom HTML option. This article explains the core requirement that determines whether your markup actually renders on live pages and how to approach the deployment. ⚠️ Critical Prerequisite: Your Project Must Be Active Before attempting any Custom HTML injection, confirm that your OTTO project is active. This is the single most common reason Custom HTML injections fail to appear on live pages. - If your project is inactive, OTTO will not inject any Custom HTML — including JSON-LD — onto your website, regardless of how correctly the markup is configured. - An inactive project means OTTO's script is either not deployed on your site or has been paused. No deployments of any kind will render until the project is reactivated. - If your project is active, Custom HTML injections will render normally and do not conflict with the locked automated schema tab. To check your project status, go to OTTO SEO → All Sites (OTTO SEO Projects) and locate your project. If it shows as inactive, reactivate it before proceeding with any Custom HTML work. 🔍 Does Custom JSON-LD Conflict with the Automated Schema Tab? No. When you deploy JSON-LD via Custom HTML, it operates independently from the automated schema tab. Even if the automated schema tab is locked or managed by OTTO automatically, your manually added JSON-LD will not duplicate or overwrite existing automated schema — provided you are not adding markup for the same schema type on the same page. As a best practice, review what schema types OTTO is already injecting automatically before adding your own to avoid unintended duplication. 📋 How to Deploy Custom JSON-LD via Custom HTML 1. Log in to Search Atlas and open OTTO Agent from the left navigation menu. 2. Select the project you want to work with and confirm its status is active. 3. Locate the Custom HTML option within your OTTO project. 4. Create a new Custom HTML entry and paste your complete JSON-LD markup, including the opening <script type="application/ld+json"> tag and the closing </script> tag. 5. Save your changes and allow a few minutes for the injection to propagate. 6. Verify the markup is live by visiting the target page and using a structured data testing tool (such as Google's Rich Results Test) to confirm the JSON-LD is present and valid. 📌 What to Have Ready If You Need Support If your Custom HTML injection is still not rendering after confirming your project is active, a support teammate can investigate further. To help resolve the issue as quickly as possible, please have the following ready: - Your OTTO project name - The URL(s) where the JSON-LD should appear - A copy of the JSON-LD markup you are trying to inject - Confirmation of your project status (active or inactive) at the time of the issue - Any error messages or unexpected behavior you observed, including approximate timestamps If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 OTTO New Page Detection and Analysis Timing

🧭 Overview OTTO continuously monitors your website to identify optimization opportunities. However, new pages you add to your site are not detected instantly. Understanding how OTTO's detection cycle works will help you set the right expectations and avoid confusion when newly published pages don't appear right away. ⏱️ How Often Does OTTO Analyze Your Site? OTTO runs automated analysis cycles on a scheduled basis rather than in real time. This means: - New pages added to your website are picked up during the next scheduled crawl cycle, not immediately after publishing. - The detection window can vary depending on your site size, server response times, and current crawl queue priority. - It is normal for newly published pages to take some time before they appear inside OTTO's page list and receive optimization suggestions. This is expected behavior and does not indicate a problem with your account or website setup. 🚫 Why Manual Recrawl Is Not Available A common question from customers is why there is no button to trigger a manual recrawl after adding new pages. OTTO's crawl process is managed automatically by the platform to ensure consistent, system-wide performance for all users. Exposing a manual recrawl option could overload crawl queues and negatively impact analysis quality across the platform. As a result, manual recrawl is not a supported feature at this time. The best approach is to allow the scheduled cycle to complete. Once OTTO detects your new pages, they will be automatically queued for analysis and optimization suggestions. 📋 What to Do After Adding New Pages 1. Publish your new pages and ensure they are live and accessible (not password-protected or blocked by robots.txt). 2. Wait for the next OTTO crawl cycle to complete. New pages will appear in your OTTO dashboard once they have been detected and processed. 3. Check your OTTO SEO dashboard by navigating to Left sidebar → OTTO SEO → SEO Automation to see if the new pages have been picked up and whether OTTO has generated recommendations for them. 4. If your pages include new content clusters or topics, consider reviewing your Topical Maps (Left sidebar → Content → Topical Maps) to align your new pages with your broader content strategy. ✅ Tips to Help OTTO Detect New Pages Faster - Submit an updated sitemap to Google Search Console. While this does not directly trigger an OTTO crawl, a well-maintained sitemap helps ensure your pages are structured and discoverable. - Internal linking: Link to your new pages from existing, already-indexed pages on your site. This improves crawlability across all tools, including OTTO. - Avoid noindex or robots.txt blocks on pages you want OTTO to analyze. Blocked pages will be skipped during crawl cycles. - Keep page URLs clean and consistent with your existing site structure to prevent detection delays caused by redirect chains. 🔄 After OTTO Detects Your New Pages Once the crawl cycle is complete and your new pages are detected, OTTO will automatically: - Add them to your tracked page list inside the OTTO SEO dashboard. - Generate on-page optimization recommendations and apply eligible automations based on your active OTTO settings. - Flag any issues that may impact those pages' search performance. You do not need to take any manual action to trigger this — it happens automatically as part of OTTO's ongoing analysis. 💬 Still Need Help? If your new pages have not appeared in OTTO after a reasonable amount of time, or if you have added more than 15 pages and are concerned something may not be working as expected, our team is here to help. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

📤 Export Deployed Page Title Changes from OTTO

🗺️ Overview When OTTO deploys page title changes, you can track progress and export a record of completed deployments from the Deployment Summary section. The exact steps differ depending on whether you are using OTTO v2 or OTTO v3. Use the sections below to find the right instructions for your version. 🔍 How to Check Which OTTO Version You Are Using To confirm your version, go to the left sidebar and select OTTO SEO, then open SEO Automation. The URL will update to /seo-automation-v3 if you are on OTTO v3. If you land on an older interface without that URL segment, you are on OTTO v2. 📋 OTTO v2 — Find and Export the Deployment Summary Follow these steps if you are on OTTO v2: 1. In the left sidebar, select OTTO SEO, then open SEO Automation to open your OTTO dashboard. 2. Locate the Deployment Summary panel. In v2, this section is visible directly on the main dashboard page without any additional clicks — scroll down if you do not see it immediately. 3. The panel displays a progress indicator, such as 71/133, showing how many page title changes have been deployed versus the total queued. 4. To export the completed changes, click the Export button displayed in the top-right corner of the Deployment Summary panel. The file downloads as a CSV containing all deployed page titles, their URLs, and deployment timestamps. 📋 OTTO v3 — Find and Export the Deployment Summary OTTO v3 uses a redesigned interface. The Deployment Summary and its export option are not visible by default on the main dashboard — they are located inside the Domain Report tab and require a hover interaction to reveal the export control. Follow these steps carefully: 1. In the left sidebar, select OTTO SEO, then open SEO Automation. Confirm you are on OTTO v3 by checking that the URL contains /seo-automation-v3. 2. At the top of the OTTO dashboard, locate the tab row and click the Domain Report tab. 3. Once inside the Domain Report tab, scroll to the Deployment Summary section. You will see a progress counter showing deployed versus total changes, for example 71 of 133 page titles deployed. 4. The export button in v3 is hidden until you interact with the row. Hover your cursor over the Deployment Summary section header. An Export icon will appear on the right side of the header bar. 5. Click the Export icon to download a CSV file. The file includes each deployed page title, its target URL, the original title, and the date it was deployed. Important: If you do not hover over the section header, the export icon will not be visible. This is expected behaviour in OTTO v3 and is not a bug. 📊 Understanding the Deployment Progress Counter The counter you see — for example, 71/133 — means: - 71 — page title changes that have been successfully deployed to your site. - 133 — the total number of page title changes OTTO has queued or approved for deployment. Only deployed changes (the first number) are included in the exported CSV. Changes that are still pending or awaiting approval are not included until they are deployed. ⚠️ Common Issues and Quick Fixes - I cannot see the Domain Report tab in v3. Make sure you have at least one domain connected to OTTO. If no domain is active, the tab may be hidden. Go to your OTTO settings and confirm your domain is connected and verified. - The export icon does not appear when I hover. Try refreshing the page and hovering again. If the icon still does not appear, clear your browser cache or try a different browser. If the problem persists, contact support using the method below. - My exported CSV is empty. The CSV only includes changes with a Deployed status. If all your changes are still pending, the file will have no data rows. Wait for deployment to complete or check your deployment queue for errors. - I see a Deployment Summary in v3 but the counter shows 0/133. This may mean OTTO has queued changes but deployment has not yet started. Confirm that auto-deployment is enabled or manually trigger deployment from the Domain Report tab. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

📋 Export OTTO Heading Recommendations for Client Approval

🔍 Overview OTTO generates heading optimization recommendations — including H1 length, missing H1 tags, and other heading structure improvements — as part of its on-page SEO analysis. You can export these recommendations as a summary report to share with clients or stakeholders for review and approval before deployment. 🧭 How to Access the OTTO Export 1. Log in to Search Atlas and click OTTO SEO in the left sidebar, then open SEO Automation (or navigate to /seo-automation-v3). 2. Select the project you want to export recommendations for. 3. Once inside OTTO, navigate to Site Audit → Overview (Website Overview) and locate the Export to Docs button. This is typically found near the top of the page, alongside other action controls. 4. Click Export to Docs to open the export options. 📄 Choosing the Right Export Type OTTO offers two export options from the Export to Docs menu: - OTTO Summary — exports a high-level overview of all recommendations OTTO has identified across all SEO categories, including headings. Use this when your client needs a broad snapshot of all suggested optimizations. - Work Summary — exports a detailed breakdown of completed and pending tasks. Use this when your client needs to see which recommendations have already been deployed and which are still pending approval. For sharing H1 length recommendations and other heading optimizations ahead of deployment, the OTTO Summary export is the recommended choice, as it lists all outstanding recommendations your client needs to review. ✅ What the Export Includes The exported file will contain heading-related recommendations such as: - H1 length recommendations (too short, too long, or missing) - Missing or duplicate H1 tags - H2 and subheading structure suggestions - Other on-page heading optimizations flagged by OTTO The export is formatted to be client-readable, making it straightforward to share directly without additional formatting work. 💡 Tips for Sharing with Clients - Use the OTTO Summary export early in the workflow so clients can approve heading changes before you deploy them inside OTTO. - If your client has already approved some changes and you need to show progress, use the Work Summary export instead to distinguish deployed vs. pending items. - Always download a fresh export immediately before sharing, so the data reflects the most current state of your project. ⚠️ Common Navigation Mistake to Avoid The export option is not located under a Project Dashboard or Deployment Summary section. If you cannot find an export button in those areas, you are in the wrong place. Always return to OTTO SEO in the left sidebar, open your project, navigate to Site Audit → Overview (Website Overview), and use the Export to Docs button directly from that page. 🆘 Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🤖 Control OTTO AI-Generated Title Lengths

🔍 Overview When OTTO SEO generates page titles through the task list, it follows built-in SEO best practices and targets a default character range designed to keep titles descriptive and keyword-rich while displaying correctly in Google search results. If your generated titles feel too long or do not match your brand's style, this article explains how to raise this with the support team so they can apply the appropriate constraint for your WordPress integration. ⚙️ What Controls Title Length OTTO's title generation behavior — including character length constraints — is configured at the project level. The exact settings available to you may vary depending on your plan and how your WordPress site is connected to Search Atlas. Because the specific controls for title length constraints are configured on the backend for your OTTO project, the most reliable path to adjusting them is to contact the support team directly with the details below. 📋 What to Have Ready When You Reach Out To help the team apply the correct title length constraint for your project as quickly as possible, please have the following information ready: - The name of your OTTO project or connected WordPress site - The title length or character range you would like OTTO to target (for example, "under 60 characters" or "between 50 and 65 characters") - Any example titles that were generated and feel too long, so the team can confirm the current behavior - Whether you need this change applied to all future titles or only to specific pages 💡 General Guidance on Title Length While the support team can assist with applying specific constraints to your project, keep the following in mind when deciding what range to request: - Google typically truncates titles that exceed around 60 characters in standard search results, so shorter targets are often preferable for display purposes. - Being specific in your request (for example, "titles under 60 characters") produces more predictable results than a vague preference like "short titles." - Style preferences — such as avoiding the brand name in titles or using sentence case — can also be communicated to the team at the same time. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🏥 Choosing the Right Schema for Services Pages

🔍 Overview Schema markup helps search engines understand what your page is about and can improve how your content appears in search results. When optimizing a services page in OTTO SEO, choosing the correct schema type is essential — especially for specialized businesses like veterinary clinics, emergency services, or healthcare providers. This article explains how to select the right schema and what to do if an expected option doesn't appear. 🗂️ Schema Types Available for Services Pages OTTO SEO offers several schema types that apply to services-related content. The best choice depends on the nature of your business and the specific page you are optimizing. Below are the most relevant options: - LocalBusiness — The broadest option. Suitable for any business serving a local area. Use this as a fallback when a more specific type is not available. - MedicalBusiness / VeterinaryCare — Recommended for veterinary clinics, animal hospitals, and emergency animal care pages. This schema signals to Google that your page represents a healthcare-related business for animals. - EmergencyService — Applicable to pages that provide urgent or around-the-clock services such as emergency veterinary care, urgent care clinics, or similar 24/7 providers. - Service — A general schema for describing a specific service offered by a business. Best used when no industry-specific type exists for your service. - ProfessionalService — Ideal for licensed or regulated service providers such as lawyers, accountants, or medical professionals. 🐾 Which Schema to Use for a Veterinary Emergency Services Page For a veterinary emergency services page, we recommend applying VeterinaryCare schema (a subtype of MedicalBusiness). This is the most semantically accurate option and the one Google's structured data guidelines recognize for animal healthcare providers. If your page specifically highlights 24/7 or emergency availability, you can also layer in EmergencyService schema or include emergency-related properties within your VeterinaryCare markup. Here is a quick decision guide: 1. Is the page for a veterinary clinic or animal hospital? → Select VeterinaryCare. 2. Does the page emphasize emergency or urgent care availability? → Add EmergencyService or include emergency hours in your markup properties. 3. Is neither option available in your OTTO SEO panel? → Select LocalBusiness and contact support to request the specific schema type for your account. ⚙️ How to Apply Schema Markup in OTTO SEO 1. Go to OTTO SEO → SEO Automation in the left sidebar (URL: /seo-automation-v3). 2. Find the page you want to optimize and open its OTTO SEO settings. 3. Scroll to the Schema Markup section. 4. Click the schema type dropdown and review the available options. 5. Select the most specific schema type that matches your page content (see recommendations above). 6. Fill in the required fields such as business name, address, phone number, and operating hours. 7. Save your changes and allow OTTO SEO to deploy the markup to your page. ❓ Why Isn't the Services Page Schema Option Appearing? If you cannot find a specific schema type in your OTTO SEO panel, there are a few likely reasons: - Account or plan limitations: Certain schema types are available only on specific plans. Check that your subscription includes advanced schema options. - Page type detection: OTTO SEO may pre-filter schema options based on the detected page type. If the page is classified differently than expected, some schema types may be hidden. - Schema not yet supported: Not every schema type in Google's vocabulary is currently available in OTTO SEO. The library is updated regularly, so a type you need may be added in a future release. In any of these cases, using LocalBusiness or Service schema as a temporary alternative ensures your page still benefits from structured data while you wait for the correct option to become available. ✅ Best Practices for Schema on Services Pages - Always choose the most specific schema type available — specificity helps search engines classify your business more accurately. - Fill in as many schema properties as possible, including hours, address, phone, and service descriptions. - Avoid applying multiple conflicting schema types to the same page element — this can confuse crawlers. - Validate your schema after deployment using Google's Rich Results Test to confirm there are no errors. - Review your schema choices whenever you update your services or add new pages. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚡ Bulk AI Content Generation and Change Tracking in OTTO SEO

Overview OTTO SEO supports bulk AI content generation, bulk editing of title tags, and change tracking so you can manage content updates efficiently across multiple pages. This article walks you through each of these workflows step by step. How to Bulk Select Pages for AI Content Generation To select multiple pages and queue them for AI content generation in OTTO SEO: 1. Open your project from OTTO SEO → All Sites (SEO Automation Projects) and navigate to Site Audit → Page Explorer. 2. Use the checkboxes next to each page to select the pages you want to include. You can also use a Select All option if available to choose all pages at once. 3. Once your pages are selected, look for the bulk actions menu or toolbar that appears when multiple pages are checked. 4. Choose the option to Generate AI Content from the bulk actions menu. 5. Confirm the action when prompted. OTTO will queue the selected pages and begin generating AI content for each one. How to Bulk Edit Title Tags After AI content has been generated, you can review and edit title tags in bulk: 1. In your OTTO SEO project, select the pages whose title tags you want to update using the checkboxes. 2. Open the bulk actions menu and select the option to edit title tags. 3. Review the AI-generated title tag suggestions for each selected page. 4. Make any edits you need directly in the bulk editing view, then save your changes. How to Review the Change Log OTTO SEO tracks every update applied to your site in a change log so you can audit what was changed and when: 1. Navigate to the change log or activity log section within your OTTO SEO project. 2. Review the list of recorded changes, which includes the type of update, the page affected, and the timestamp of when the change was applied. 3. Use any available filters to narrow down the log by date range, page, or action type. If You Run Into Issues If a bulk action does not appear to be working as expected, please have the following information ready so our team can assist you as quickly as possible: - The name of the project or site you are working with in OTTO SEO - A description of the specific action you attempted (e.g., bulk generating AI content, editing title tags, viewing the change log) - Any error messages you received, including the exact wording - The approximate date and time the issue occurred - Screenshots of what you are seeing, if possible If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔄 OTTO Recrawl vs Weekly Analysis Explained

🤔 What Is the Difference Between a Recrawl and a Weekly Analysis? OTTO runs two distinct processes to evaluate your site's SEO health: a manual recrawl that you trigger on demand, and an automated weekly analysis that runs in the background on a fixed schedule. Understanding what each one does helps you use OTTO more effectively after making changes to your site. 📅 How the Weekly Analysis Works OTTO automatically re-analyses your site once every seven days. This cycle is designed to keep your SEO recommendations fresh without requiring any action from you. During a weekly analysis, OTTO: - Re-evaluates all previously identified SEO issues across your site - Detects new issues that may have appeared since the last cycle - Updates recommendation statuses based on the latest state of your pages - Refreshes performance data and opportunity scores Because the weekly analysis runs on a set schedule, it is best suited for routine monitoring rather than verifying a specific fix you have just deployed. 🔍 What a Manual Recrawl Does A manual recrawl lets you immediately re-examine your site after you have made code or content changes. Instead of waiting up to seven days for the next scheduled cycle, you can trigger OTTO to crawl your site right away and confirm whether your fixes have resolved the flagged recommendations. During a manual recrawl, OTTO: - Re-crawls the pages associated with active recommendations - Checks whether previously flagged issues are now resolved - Updates the status of affected recommendations in real time - Reflects any structural or on-page changes you have implemented A manual recrawl is scoped to your existing recommendations — it validates fixes rather than performing a full discovery sweep of brand-new issues. For a comprehensive discovery of new issues, the weekly analysis cycle handles that automatically. 🛠️ How to Trigger a Manual Recrawl in OTTO 1. In the left sidebar, click OTTO SEO, then navigate to Site Audit → Overview (Website Overview). 2. Locate the site session you want to recrawl. 3. Click the Recrawl Site button associated with that session. The button is typically displayed near the top of the session overview or within the site's action menu. 4. OTTO will begin crawling immediately. Depending on your site's size, this may take a few minutes to complete. 5. Once the recrawl finishes, return to your recommendations list to review updated statuses and confirm that your fixes have been picked up. ✅ When Should You Use Each Option? - Use a manual recrawl when you have just pushed code changes, updated meta tags, fixed broken links, or resolved any specific recommendation and want immediate confirmation. - Rely on the weekly analysis for ongoing site health monitoring, discovering new SEO opportunities, and tracking overall progress over time without manual intervention. 💡 Tips for Getting Accurate Recrawl Results - Make sure your code changes are fully deployed and live before triggering a recrawl. OTTO crawls the live version of your site, so any changes still in staging will not be reflected. - Clear your CDN or server cache before recrawling to ensure OTTO reads the most up-to-date version of your pages. - Allow the recrawl to complete fully before reviewing results — checking mid-crawl may show incomplete data. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team. Additional Notes Immediate recrawl does NOT detect: deleted/redirected pages, codebase-level modifications, new pages added, site architecture/navigation changes, server-side rendering/framework-level changes. Results typically reflected within a few minutes to a couple of hours depending on site size.

🛠️ Disable Breadcrumbs and Schema in OTTO MetaSync

🔍 What Is OTTO MetaSync? OTTO MetaSync is the Search Atlas tool that automatically deploys on-page SEO changes — including breadcrumbs and schema markup — directly to your website. Both features are enabled by default to improve your site's search visibility, but you can disable either one at any time from within your OTTO MetaSync settings. 🍞 How to Disable Breadcrumbs Breadcrumbs add a navigational trail to your pages and inject breadcrumb schema automatically. To turn them off, locate the breadcrumbs setting within your OTTO MetaSync configuration for your connected site and disable it. The exact location of this setting may vary depending on your account setup. Note: Disabling breadcrumbs removes both the visual breadcrumb trail and the associated breadcrumb schema from your pages going forward. 📋 How to Disable Schema Markup Schema markup helps search engines understand your page content. If you prefer to manage schema independently or need to disable it for a specific reason, locate the schema markup setting within your OTTO MetaSync configuration for your connected site and disable it. Note: Schema and breadcrumbs are managed as separate settings. You can disable one without affecting the other. Review both settings individually to make sure each is set to your preference. ⚠️ Important Considerations Before Disabling - SEO impact: Breadcrumbs and schema markup contribute to your site's search performance and rich result eligibility. Disabling them may reduce your visibility in search results over time. - Re-enabling: You can turn either feature back on at any time by returning to your OTTO MetaSync settings and switching the setting back to enabled. 💡 Need Help Locating the Settings? If you are unable to find the breadcrumbs or schema markup settings within OTTO MetaSync, or if the options do not appear as expected for your connected site, our support team can guide you directly. When reaching out, please have the following ready: your connected domain name, the name of your OTTO project, and a brief description of what you see (or do not see) in your OTTO MetaSync settings. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team. Additional Notes Candidate covers per-page disabling of breadcrumbs and schema (open page in WordPress editor, find MetaSync settings panel, disable at individual page level) and distinguishes global vs per-page schema control — not present in keeper.

🔍 Connect GSC and Add Address in OTTO

🧭 Overview When setting up OTTO SEO for a WordPress site, two common configuration steps trip up new users: selecting the correct Google Search Console (GSC) property in the dropdown, and finding the field to enter a business address. This article walks you through both steps so your OTTO site is fully configured and ready to optimize. ⚙️ Step 1 — Access Your OTTO SEO Dashboard To begin, navigate to OTTO SEO in the left sidebar, then open SEO Automation (URL: /seo-automation-v3). Locate the WordPress site you want to configure and open its OTTO settings. If you have not yet activated OTTO for this site, you will need to complete activation before the GSC and address fields become available. 🔗 Step 2 — Connect Your Google Search Console Property If your GSC site is not appearing in the dropdown, this is almost always caused by one of the following reasons: - GSC is not connected to your Search Atlas account. You must first authorize Google Search Console under your account settings. Without this authorization, no GSC properties will populate in the dropdown. - The site is not verified in GSC. Only properties that are fully verified in Google Search Console will appear. Log in to search.google.com/search-console and confirm your WordPress site shows a verified status. - You are using the wrong property type. GSC supports two property types — Domain and URL-prefix. Make sure the property you added in GSC matches the exact URL format of your WordPress site (including or excluding www, and http vs https). - There is a mismatch between the site URL in OTTO and the GSC property URL. The domain entered when you created the OTTO site must match the GSC property exactly. Even a trailing slash difference can cause the property to be excluded from the list. Once the above points are confirmed, return to OTTO SEO in the left sidebar and open SEO Automation, refresh the page, and reopen the GSC dropdown. Your verified property should now appear. Select it and save your settings. 🏢 Step 3 — Add Your Business Address The business address field is not shown by default for all site types. It becomes available only when OTTO detects or is told that the site represents a local business. Follow these steps to make the field appear: 1. Open the OTTO site settings from the SEO Automation page (/seo-automation-v3). 2. Locate the Business Type or Site Category setting and ensure it is set to a local business category (for example: restaurant, law firm, medical practice, retail store). 3. Once a local business type is selected and saved, the Business Address field will appear in the configuration panel. 4. Enter your full address including street, city, state or region, postal code, and country. 5. Save your changes. OTTO will use this address to power local SEO recommendations and structured data. If you have already selected a local business type and the address field is still not visible, try clearing your browser cache and reloading the page, then revisit the OTTO settings. ✅ Confirming Your Configuration Is Complete After completing both steps, verify the following before activating OTTO optimizations: - The GSC property shown in OTTO matches your live WordPress site URL exactly. - GSC is returning data — allow up to 48 hours for Search Console data to sync after a new connection. - Your business address is saved and visible in the OTTO site details panel. - Your business type is correctly categorized so OTTO applies the right local SEO strategy. 💡 Tips to Avoid Common Mistakes - Always use the same Google account to connect GSC that owns the verified property. - If you manage multiple sites, double-check you are editing the correct OTTO site — it is easy to open the wrong one when several WordPress sites are listed. - Re-authorization of GSC may be required if you recently changed your Google account password or revoked app permissions. 🛠️ Still Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛒 Deploying OTTO Meta Descriptions to WooCommerce Pages

🔍 Why Meta Tags May Be Missing on Product Pages OTTO deploys meta titles and descriptions on a per-URL basis, not globally across your entire site. This means that even if your homepage and blog posts are already optimised, each WooCommerce product page must be individually selected and deployed to receive its meta tags. If meta descriptions appear on your homepage but not on product pages, the most likely cause is that those product URLs have not yet been targeted for deployment. 📋 Before You Begin - Make sure OTTO is activated for your connected domain. - Confirm your WooCommerce product pages have been crawled and are visible in your URL list inside OTTO SEO V3. - Check that you have not excluded product page URL patterns (such as /product/) from OTTO's scope. 🚀 How to Deploy Meta Tags to a WooCommerce Product Page 1. In the left sidebar, click OTTO SEO and then open SEO Automation to access the OTTO dashboard at /seo-automation-v3. 2. Locate the Meta Tags section within the OTTO task list. 3. Use the URL search or filter to find the specific product page URL you want to optimise — for example, yoursite.com/product/blue-widget. 4. Click the product URL to open its meta tag settings. 5. Review the AI-generated meta title and description. Edit either field if needed to better match your product's target keywords and value proposition. 6. Toggle the deployment switch to On to push the meta tags live to that page. 7. Repeat this process for each additional product page. ⚡ Deploying Meta Tags Across Multiple Product Pages If you have a large WooCommerce catalog, deploying pages one by one can be time-consuming. Use the following approach to work through your product catalog efficiently. - Filter by URL pattern: In the OTTO SEO V3 dashboard, filter or search for /product/ to surface all product page URLs at once. - Bulk selection: Use the bulk-select checkbox to highlight multiple product URLs simultaneously. - Bulk deploy: With multiple URLs selected, apply the deployment action to push meta tags to all selected pages in one step. - Prioritise top products first: Start with your highest-traffic or highest-converting product pages to capture SEO value quickly while you work through the rest of the catalog. ✅ Verifying Deployment Was Successful After deploying, confirm the meta tags are live on each product page. 1. Open the product page URL in your browser. 2. Right-click anywhere on the page and select View Page Source. 3. Use Ctrl + F (or Cmd + F on Mac) to search for meta name="description". 4. Confirm that the deployed description appears in the source code. You can also use a browser extension such as a meta tag inspector to quickly check the active title and description without viewing raw source code. ⚠️ Common Issues and Fixes - Product pages not appearing in the URL list: Run a fresh crawl of your site from the OTTO SEO V3 dashboard to ensure all product URLs are indexed by OTTO. - Meta tags deployed but not showing in source: Clear your site cache and any server-side caching plugin (such as WP Rocket or W3 Total Cache) after deployment. - Another SEO plugin is overriding OTTO: If you have Yoast SEO, Rank Math, or All in One SEO active on your WooCommerce product pages, their meta output may take precedence. Disable meta tag output in those plugins for product pages, or deactivate them entirely if OTTO is your primary SEO tool. - Deployment toggle is greyed out: Verify that OTTO is fully activated for your domain and that your current plan includes meta tag deployment for the number of URLs you are targeting. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔄 Remove and Replace Domains in OTTO Pixel

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

🔄 Deploy vs Sync to CMS in OTTO: Understanding the Distinction

🧭 Overview If OTTO shows your meta titles and descriptions as deployed but your WordPress Search Atlas → Settings page displays blank fields, you are not alone. This article explains the relationship between OTTO's Deploy action and the Sync to CMS function, clarifies when they produce identical results, and shows you exactly where to verify that your meta tags are live in WordPress (via Search Atlas → Settings in your WordPress admin). ⚙️ What Deploy and Sync to CMS Actually Do In OTTO SEO, these two terms describe steps in the same pipeline — not two separate features. Understanding where each step fits helps you diagnose what has or has not happened to your content. - Deploy — OTTO writes your generated meta titles and descriptions into its own internal database and marks them as active. This step happens entirely inside Search Atlas. - Sync to CMS — OTTO pushes those deployed values through the MetaSync plugin to your connected WordPress site, overwriting or populating the meta fields there. For most users and most workflows, pressing Deploy inside OTTO triggers both steps automatically and sequentially. This is why many customers reasonably experience them as a single action — in practice, they often are. 🔌 The Role of the MetaSync Plugin The MetaSync plugin is the bridge between Search Atlas and your WordPress database. Without it functioning correctly, OTTO can show a successful deploy while WordPress displays empty fields. The plugin must be installed, activated, and authenticated for the sync step to complete. Common reasons the sync step silently fails even after a successful deploy include: - The MetaSync plugin is deactivated or was recently updated and needs reauthorisation. - The API key connecting MetaSync to your Search Atlas account has expired or been regenerated. - A WordPress caching plugin is serving a stale version of the page metadata. - The specific URL was not included in the sync scope at the time of deployment. ✅ When Deploy and Sync to CMS Are Functionally Identical The two actions produce identical, immediate results when all of the following conditions are true: 1. The MetaSync plugin is installed, active, and authenticated on your WordPress site. 2. Your Search Atlas workspace is connected to the correct WordPress property. 3. The URL being optimised is within the synced scope defined in your OTTO project settings. 4. No WordPress security or caching layer is blocking outbound API requests from the plugin. If all four conditions are met, clicking Deploy in OTTO will simultaneously write the meta data internally and push it to WordPress. You will see populated fields in MetaSync and in WordPress almost immediately. 🔍 How to Verify Meta Tags Are Live in WordPress Because the Search Atlas → Settings page in WordPress can sometimes display blank fields due to a display refresh issue, use the following sequence to confirm the actual state of your meta tags. 1. Go to OTTO SEO → All Sites (SEO Automation) using the left sidebar and open your project. 2. Locate the URL in question and confirm its status shows Deployed in the OTTO interface. 3. Open your WordPress admin panel and navigate to the page or post for that URL. 4. Scroll to the SEO meta fields section — this will be labelled with the MetaSync plugin name or your active SEO plugin (such as Yoast or Rank Math if MetaSync writes to those fields). 5. Confirm the meta title and description fields contain the values OTTO generated. 6. As an independent check, visit the live URL in your browser, right-click, select View Page Source, and search for og:title or meta name="description" to see what is actually rendered. If the values appear in WordPress but the MetaSync tab in Search Atlas still looks blank, perform a hard refresh of the Search Atlas page (Ctrl + Shift + R on Windows or Cmd + Shift + R on Mac) and reopen the MetaSync tab. 🛠️ Troubleshooting Blank MetaSync Fields If your WordPress page source confirms the meta tags are missing, work through these steps in order: 1. Check the MetaSync plugin status — Log in to WordPress, go to Plugins, and confirm MetaSync is active. If it was recently updated, deactivate and reactivate it. 2. Reauthorise the connection — In your WordPress admin, go to Search Atlas → Settings, regenerate the MetaSync API key, then paste the new key into the MetaSync plugin settings inside WordPress and save. 3. Redeploy the affected URLs — Return to OTTO SEO, select the URLs showing blank meta fields, and trigger a fresh Deploy. Monitor the MetaSync tab after 60 seconds. 4. Clear WordPress cache — If you use WP Rocket, W3 Total Cache, or a hosting-level cache, clear it after redeploying so fresh meta data is served. 5. Verify sync scope — Inside your OTTO project settings, confirm the affected URLs fall within the defined sync scope and have not been excluded. 📋 Quick Reference: Deploy vs Sync to CMS - Deploy only (no sync) — Occurs if MetaSync is disconnected. OTTO records the meta data internally but WordPress is not updated. - Deploy + Sync (standard) — Occurs when MetaSync is connected. Both steps complete together; this is the expected behaviour for connected WordPress sites. - Sync to CMS manually triggered — Available as a standalone action if you need to re-push previously deployed values without regenerating them. Useful after reconnecting a broken MetaSync link. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🐦 Disable Twitter Card Suggestions in OTTO

🔍 Why OTTO Suggests Twitter Cards OTTO analyzes your site's metadata and identifies missing or incomplete social tags, including Twitter Card tags. If your pages lack these tags, OTTO automatically adds Twitter Card implementation to your task list as an SEO improvement opportunity. These tags control how your content appears when shared on Twitter (now X). However, if your business does not have a Twitter account, these suggestions are not relevant to you — and dismissing them will not negatively affect your SEO on other channels. This article explains how to permanently remove Twitter Card tasks so they no longer appear in your OTTO task list. 📋 What You Will Need - An active Search Atlas account with OTTO enabled - Access to the OTTO SEO V3 section of the platform 🗺️ Getting to OTTO 1. Log in to your Search Atlas account. 2. In the left sidebar, click OTTO SEO, then open SEO Automation. 3. Select the website you are managing from your list of connected properties. 4. Click the OTTO tab to open your task list. 🚫 How to Reject and Disable Twitter Card Suggestions Follow these steps to remove existing Twitter Card tasks and prevent new ones from appearing: 1. In your OTTO task list, use the search bar or scroll to locate any tasks labelled Twitter Card or Twitter Meta Tags, including tasks referencing twitter:card, twitter:site, or similar meta tags. 2. Click the task to expand it and view its details. 3. Click the Reject button on the task. This tells OTTO you do not want this suggestion applied. Alternatively, you can select one or more tasks using the checkbox next to each one and use the Dismiss or Ignore option that appears when tasks are selected, then confirm your choice. 4. When prompted to provide a reason, select or enter Not applicable — no Twitter account, or similar. This helps OTTO learn your preferences. 5. Repeat this step for every Twitter Card task currently in your list. Once all existing Twitter Card tasks are rejected, OTTO will treat this category as dismissed for your site and will not continue to resurface them during future analysis cycles. Dismissed tasks will also no longer count against your OTTO progress score. ✅ Confirming Twitter Cards Are Excluded After rejecting the tasks, verify they have been removed: - Refresh your OTTO task list and confirm no Twitter Card tasks remain in your active queue. - Run a new OTTO scan by clicking Scan in OTTO SEO → All Sites (SEO Automation) if available. Twitter Card suggestions should no longer appear in the results. - If any Twitter Card tasks reappear after a re-analysis, reject them again immediately. OTTO reinforces your preferences over successive rejections. 💡 Should You Ever Implement Twitter Card Tags? OTTO may still suggest Open Graph (OG) tags for Facebook, LinkedIn, and general social sharing. These are separate from Twitter Cards and are broadly recommended for SEO and link previews, even without a Twitter account. You can choose to accept or reject these tasks independently based on your needs. If your business decides to join Twitter or X in the future, you can revisit the Twitter Card recommendation at any time. Twitter Card tags are beneficial for brands that actively share content on the platform because they improve how page previews look in tweets. For now, if social sharing on Twitter is not part of your strategy, dismissing these tasks is completely fine. ⚠️ What Rejecting Does Not Do Rejecting a task in OTTO does not remove any existing Twitter Card tags that may already be present on your site from a previous implementation. If you want to remove those tags from your live pages, you will need to do so manually in your CMS or theme settings. Rejecting only prevents OTTO from adding new tags or prompting you about them in the future. ❓ Frequently Asked Questions - Will dismissing this task hurt my SEO score? No. Dismissed tasks are excluded from your overall OTTO score, so your progress will reflect only the tasks that are relevant to your site. - Can I restore a dismissed task later? Yes. Dismissed tasks can typically be reviewed in your OTTO settings or dismissed-tasks log. If you need help locating them, contact support via the chat widget. - Does OTTO suggest other social meta tags too? Yes. OTTO may also suggest Open Graph tags for Facebook and LinkedIn previews. Those are separate from Twitter Card tags and can be handled independently. 🆘 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

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

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

📈 Improve Your OTTO SEO Optimization Score

🔍 What Is the OTTO Optimization Score? The OTTO Optimization Score is a percentage that reflects how well your website has implemented OTTO's AI-driven SEO recommendations. A higher score means more recommendations have been applied, giving your site a stronger foundation for ranking in search results. The score updates automatically as OTTO detects changes on your site or generates new tasks. 📉 Why Did My Score Decrease? A drop in your Optimization Score — for example, from 68 to 63 — does not always mean something went wrong. Here are the most common reasons your score may decrease: - New recommendations added: OTTO continuously audits your site. When it identifies new SEO issues or opportunities, those are added to your task list. More open tasks mean a lower percentage of completed work, which reduces the score. - Previously applied changes were reversed: If a page was edited, a plugin updated a meta tag, or a CMS change overwrote OTTO's optimizations, those tasks may revert to an incomplete state. - Site content changes: Publishing new pages or posts introduces fresh content that OTTO needs to evaluate, adding new tasks to the queue. - Technical issues detected: OTTO may flag newly discovered technical problems such as broken links, missing schema, or slow-loading pages. A score decrease is a signal to act, not a cause for alarm. It simply means OTTO has found more ways to improve your site. 🛠️ How to Increase Your OTTO Score Follow these steps to review and complete your open recommendations inside Search Atlas. 1. Open OTTO SEO: In the left sidebar, click OTTO SEO → All Sites (SEO Automation). This takes you to the OTTO dashboard where all your active sites and scores are displayed. 2. Select your site: Click on the site whose score you want to improve. You will see a breakdown of pending tasks grouped by category — for example, On-Page, Technical, and Content. 3. Sort by impact: Prioritise tasks marked as High Impact first. Completing these moves the needle on your score the most and delivers the greatest SEO benefit. 4. Apply recommendations: Click Deploy or Apply next to each task. OTTO can push many changes directly to your site when the Search Atlas WordPress plugin is installed and connected. For tasks that require manual edits, follow the on-screen instructions. 5. Review content suggestions: Navigate to OTTO SEO → Site Audit → Page Explorer to find page-level recommendations. Update title tags, meta descriptions, headings, and body content as suggested. 6. Check technical tasks: Address any flagged technical issues such as missing canonical tags, broken internal links, or absent structured data. These often account for a significant portion of the score. 7. Re-scan your site: After applying changes, click Re-Analyze or wait for OTTO's next automatic crawl. Your score will update once the changes are confirmed. 💡 Tips to Maintain a High Score - Connect the Search Atlas WordPress plugin so OTTO can deploy on-page changes automatically without manual edits. - Check your OTTO dashboard weekly to catch new recommendations before they accumulate and lower your score. - Avoid overwriting OTTO changes in your CMS manually, as this can revert completed tasks back to open status. - Focus on completing all tasks in one category before moving to the next — this creates a clean, measurable lift in your score. - Use Site Metrics (left sidebar → Site Metrics) to track keyword rankings alongside your score, so you can correlate optimizations with ranking improvements over time. 📊 Understanding What a Good Score Looks Like There is no universal benchmark, but as a general guide: - Below 50%: Significant opportunities remain. Focus on high-impact tasks immediately. - 50–75%: Solid progress. Continue working through remaining recommendations systematically. - 76–90%: Strong optimization. Maintain the score by reviewing new tasks regularly. - 91–100%: Excellent. Your site is closely aligned with OTTO's best-practice recommendations. Monitor for new tasks as your content grows. Remember that OTTO's recommendations evolve with your site, so even a perfect score today may drop slightly tomorrow as new content or issues are detected. This is normal and expected behavior. 🆘 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🖼️ Exclude Decorative Images From OTTO Alt Text

🔍 Why This Matters Decorative images — icons, dividers, background flourishes, and purely aesthetic visuals — should have empty alt attributes (alt="") by accessibility and SEO best-practice standards. If OTTO applies descriptive alt text to these images, it can introduce unnecessary noise into your page's semantic structure and potentially flag accessibility issues. This guide shows you how to keep OTTO's alt text optimization focused only on meaningful, content-bearing images. ⚙️ How OTTO Handles Alt Text Optimization When OTTO processes a page, it scans all img elements and generates or improves alt text for images that are missing it or have weak descriptions. By default, OTTO does not distinguish between decorative and informational images automatically — it optimizes based on what it detects in the markup. Understanding this helps you set the right boundaries before OTTO runs. 🛠️ Step-by-Step: Excluding Decorative Images 1. Navigate to SEO Automation. In the left sidebar, click OTTO SEO, then open SEO Automation inside it, or go directly to /seo-automation-v3. 2. Open your active OTTO session for the site you want to configure. 3. Go to the Image Optimization settings. Inside the OTTO dashboard, locate the Alt Text or Image SEO section. This is where you control which images OTTO is permitted to modify. 4. Use the exclusion rules for individual images. OTTO provides an image-level exclusion option. Select any image flagged for optimization, then choose Exclude from optimization. This marks that specific image as off-limits for alt text changes without affecting any other images on the same page. 5. Apply a CSS class or attribute-based rule (recommended for scale). If your CMS or theme applies a consistent class to decorative images (for example, decorative, icon, or bg-image), you can add that class or attribute pattern to OTTO's global exclusion list. OTTO will skip any image carrying that identifier across your entire site, saving you from excluding images one by one. 6. Mark images with role="presentation" or aria-hidden="true" in your CMS. OTTO respects these standard accessibility attributes. Images that already carry role="presentation" or aria-hidden="true" are automatically skipped during alt text optimization — no additional configuration required. 7. Save and re-deploy. After setting your exclusion rules, click Save Changes and allow OTTO to re-process the affected pages. Verify the results in the Optimized Images log to confirm decorative images are no longer being modified. ✅ Best Practices for Decorative Image Management - Standardise your CMS classes early. Assign a dedicated CSS class (e.g., img-decorative) to all purely aesthetic images in your theme or page builder. Adding this class to OTTO's exclusion list once protects every decorative image site-wide. - Use empty alt attributes as your source of truth. Images already carrying alt="" in your HTML are treated by OTTO as intentionally empty. OTTO will not overwrite a deliberately empty alt attribute, so setting alt="" at the CMS level is a reliable safeguard. - Audit before activating alt text optimization on new pages. Before enabling OTTO on a page-type that contains many decorative elements (landing pages, icon grids, portfolio galleries), review the image list inside OTTO and apply exclusions proactively. - Do not exclude the entire page. Excluding a full page to avoid optimizing a handful of decorative images means missing out on alt text improvements for all the valuable content images on that page. Always prefer image-level or class-level exclusions. 🔎 Troubleshooting: OTTO Still Optimizing Excluded Images - Check that the exclusion was saved. Navigate back to the Image SEO settings and confirm the image or rule appears in your exclusion list. - Confirm the CSS class matches exactly. Exclusion rules are case-sensitive. Ensure the class or attribute value in OTTO matches what your CMS outputs in the rendered HTML. - Re-deploy the OTTO session. Exclusion rules apply on the next processing cycle. If you added an exclusion after a recent optimization run, trigger a manual re-deploy from the OTTO dashboard. - Verify the image URL hasn't changed. Dynamic image URLs (e.g., resized or CDN-transformed URLs) may create new entries in OTTO's image list. Apply class-based rules rather than URL-based rules for images that change frequently. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚡ OTTO On-Page Optimization: Title Tags, Meta Keywords, Deployment

Overview OTTO's on-page optimization features help you improve title tags, meta keywords, and overall page scores directly from the OTTO SEO dashboard. This article explains what OTTO's on-page optimization covers, how to work with its suggestions, and what to have ready if you need support. Where to Find OTTO On-Page Optimization Navigate to Left sidebar → OTTO SEO → All Sites (SEO Automation) to access OTTO. Once inside, select a connected domain and open the On-Page section to view all pages OTTO has crawled and queued for optimization. How Title Tag Suggestions Work OTTO generates title tag suggestions automatically as part of its on-page optimization workflow. After OTTO completes its crawl of your connected domain, it surfaces optimization recommendations — including title tag suggestions — for the pages it has analyzed. You can review these suggestions inside the On-Page section and choose to apply or modify them before deploying. If you are not seeing suggestions for a particular page, this may indicate that the page has not yet been crawled, that the domain connection needs to be refreshed, or that the page falls outside the current crawl scope. In these cases, contact our support team with the details described at the end of this article. Meta Keywords: How They Are Deployed OTTO can generate meta keyword recommendations as part of its on-page optimization pass. Meta keywords are considered a secondary on-page signal — OTTO prioritizes title tags and meta descriptions first. Once you are satisfied with the suggestions, you can deploy them through the On-Page section of the OTTO dashboard. If you are experiencing issues with meta keywords not deploying correctly, or if the deployment status is not updating as expected, please gather the details listed below before reaching out to support. Optimization Scoring Each page OTTO analyzes receives an optimization score reflecting how well the page's on-page elements align with SEO best practices. As you apply OTTO's recommendations — such as updating title tags, meta descriptions, or meta keywords — the score for that page updates to reflect the improvements made. If a page's score does not update after you have applied changes, or if you believe the score is incorrect, note the page URL, the changes you made, and the score you expected versus what is displayed, then contact support. Troubleshooting Common Issues - Suggestions not appearing: Confirm the domain is connected and that OTTO has completed its crawl. If the crawl appears complete but suggestions are missing, note the affected page URLs and contact support. - Deployment not completing: If you click deploy and the status does not change, try refreshing the page. If the issue persists, note the page URL, your CMS type, and the exact behavior you observed. - Score not updating: Note the page URL, the changes applied, and the current versus expected score before contacting support. What to Have Ready When Contacting Support - The domain name and connected project in Search Atlas - The specific page URL(s) affected - A description of the issue (e.g., suggestions missing, deployment not completing, score not updating) - Your CMS type (e.g., WordPress, Shopify, custom) - Any error messages or unexpected behaviors you observed, including timestamps if available If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 Fix AI Title Tags Exceeding 60 Characters

Overview Search Atlas uses AI to generate SEO title tags across several tools. By default, best-practice title tags should stay within 50–60 characters to avoid truncation in Google search results. If your AI-generated titles are consistently longer than this, this article explains how to address the length issue and how to request subscription changes if needed. How to Check and Fix Title Tag Length 1. Locate the title tag for the relevant page inside your Search Atlas project and review its character count. If it exceeds 60 characters, it needs to be revised. 2. Edit the title tag directly in the field provided and shorten it to 60 characters or fewer before saving. 3. If you want the AI to regenerate a title tag, open the relevant tool and include a clear instruction specifying your desired character limit in the prompt. Reviewing and manually editing the output before publishing is recommended to ensure the length meets your requirements. 4. After updating, verify the corrected title before publishing by pasting it into any free character-counter tool to confirm the length. Tips to Prevent Oversized Title Tags - Include a character limit in your prompt. Specify your maximum character count when generating title tags via any AI tool in the platform. - Review before publishing. Paste your title into any free character-counter tool to confirm length before going live. - Shorten long keywords. If your primary keyword is naturally long, consider a shortened variation that still captures search intent. Subscription Cancellation If you need to cancel your subscription or make changes to your billing, our support team can process the cancellation or any billing adjustments on your behalf. To get help quickly, use the chat widget in the bottom-right corner of the platform and type human teammate to connect with a team member. When reaching out, have the following ready to help the team act quickly: - Your account email address - The name of your Search Atlas project or workspace - The reason for cancellation (e.g., AI outputs not meeting expectations, credit usage concerns) - Any relevant dates or billing period details If you believe credits were used on AI outputs that did not meet your needs, mention this when you contact support so the team can review your account. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🧩 Schema Markup Layering: Deploy OTTO on Existing Markup

🔍 Overview OTTO can deploy schema markup automatically across your site, but if you already have custom, hand-crafted schema on specific pages, you need a clear strategy before activating OTTO's schema. This article explains how to layer OTTO schema safely, when to hold back, and how to protect the unique structured data you have already built. It also covers how to remediate broken image tags that can interfere with your structured data and page quality signals. 📋 Understanding the Two Types of Schema on Your Site Before making any changes, identify what schema you currently have and what OTTO is proposing to add: - Existing unique per-page schema: Custom structured data you or your developer wrote specifically for individual pages — for example, a detailed Product schema with specific offers, reviews, and SKUs, or a FAQPage schema tied to that page's exact content. - OTTO-generated schema: Structured data OTTO recommends and deploys based on page type, content signals, and SEO best practices. OTTO typically covers site-wide or category-level patterns such as Organization, BreadcrumbList, WebSite, and basic Article or WebPage types. ✅ When It Is Safe to Layer OTTO Schema on Top of Existing Markup Layering is safe and beneficial when the schema types do not overlap. If your existing markup covers a specific type — such as Product — and OTTO is adding a complementary type — such as BreadcrumbList or Organization — there is no conflict. Google reads multiple JSON-LD blocks on the same page without issue as long as they describe different entities or schema types. Deploy OTTO schema on top of your existing markup when: - OTTO is adding a different schema type than what is already present on the page. - Your existing schema covers highly specific data — pricing, inventory, custom review aggregations — that OTTO cannot replicate from its configuration. - You want site-wide consistency for secondary schema types without manually maintaining them on every page. ⚠️ When to Hold Back OTTO Schema Deployment Do not deploy OTTO schema on top of existing markup when the types overlap or conflict. Deploying two Product schemas or two FAQPage schemas on the same page can create contradictory signals that confuse search engine crawlers and may result in neither being used for rich results. Hold back or customise OTTO's schema deployment when: - OTTO is recommending the same schema type already present in your existing markup. - Your existing schema contains precise data — such as exact aggregateRating values or structured HowTo steps — that OTTO's version would overwrite or dilute with generic content. - Your developer has implemented schema tied to dynamic data pulled from a CMS or database that OTTO cannot access or replicate accurately. 🖼️ Broken Image Tag Remediation Broken image tags on your pages can affect both user experience and structured data quality. When schema markup references images — for example, an ImageObject within a Product or Article schema — a broken or missing image URL can cause validation errors in Google's Rich Results Test and reduce eligibility for rich results. To identify and remediate broken image tags: 1. Audit your pages for broken images. Use your site audit tool within Search Atlas to surface pages with broken image URLs (typically flagged as 4xx errors on image assets). 2. Check whether broken images are referenced in schema. If a broken image URL appears inside a JSON-LD block — for example, as the image property of a schema type — that schema block may fail validation. 3. Replace or remove the broken image reference. Update the image URL to a valid, publicly accessible asset, or remove the image property from the schema block temporarily until a valid image is available. 4. Re-validate your schema. After making corrections, use Google's Rich Results Test to confirm that the schema block is now valid and the image reference resolves correctly. 5. Redeploy or re-save the affected schema. If the schema is managed through OTTO, trigger a redeployment after fixing the underlying image so that the corrected reference is pushed live. Addressing broken image tags before or alongside schema deployment ensures that your structured data is both syntactically valid and pointing to accessible resources, which improves the likelihood of rich result eligibility. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚡ OG Descriptions and Schema Markup in OTTO SEO

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

✏️ Adjust AI-Generated Page Title Length in OTTO

🔍 Overview When OTTO generates page titles, the default output may not always match your preferred character length for SEO. If your titles are consistently too long or too short, you can guide OTTO's output by providing a plain-language instruction in the AI settings for your project. This article explains how to approach that configuration. 🗺️ How to Access OTTO's AI Settings To adjust how OTTO generates page titles, navigate to the OTTO SEO section of your Search Atlas account: 1. Log in to your Search Atlas account. 2. In the left sidebar, locate and click the OTTO SEO section. 3. Select the website or project you are working on. 4. Look for the settings area where you can provide custom or additional instructions for AI-generated content. The exact label for this field may vary depending on your account configuration — if you are unsure which field to use, contact support for guidance specific to your interface version. ✏️ How to Set a Title Length Constraint Once you have located the appropriate instructions field in your project's AI settings, type a plain-language instruction that specifies your desired title length. Here are examples you can use or adapt: - Shorter titles:"Generate page titles that are no longer than 60 characters, including spaces." - Tighter range:"Keep all page titles between 50 and 60 characters." - Strict maximum:"Page titles must not exceed 55 characters. Do not truncate words — rewrite the title to fit." Be as specific as possible. When instructions are saved, OTTO treats them as standing rules that apply to titles it generates for that project going forward. 💾 Save and Regenerate 1. After typing your instruction, save your changes using the save option in the interface. 2. Return to your project's task or page list. 3. Find the page title tasks you want to update and trigger regeneration so OTTO applies your new instructions to the output. 4. Titles that were already accepted or published will not update automatically — you only need to regenerate pending or draft title tasks. 🔗 WordPress Integration Notes If your site is connected via the OTTO WordPress plugin, updated titles generated after you save your instructions should sync to WordPress when you publish or push changes from your task list. If you experience any sync issues after updating your title instructions, contact support with your project name and a description of the behavior you are seeing so the team can investigate. 🆘 Need Help? If you are unsure which field to use for title length instructions, or if OTTO is not respecting your instructions after regenerating, please have the following ready when reaching out: your project or website name, the exact instruction text you entered, and an example of the title output you received. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚡ Bulk Generate Meta Titles in OTTO SEO

🧭 Overview OTTO SEO supports bulk meta title generation for large numbers of pages directly from the OTTO SEO dashboard. If you are having trouble locating bulk generation controls or are unsure where to start, this article explains how to get help completing this workflow. ✅ How to Bulk Generate Meta Titles in OTTO SEO Bulk meta title generation is managed from within the OTTO SEO dashboard for your project. To complete this task: 1. Log into your Search Atlas account and navigate to OTTO SEO from the left sidebar, then open SEO Automation inside it. 2. Select the project you want to work on to open its OTTO SEO dashboard. 3. Inside the dashboard, locate the section or task category related to meta titles or title tags for your pages. 4. Use the available selection controls to choose the pages you want to generate meta titles for — you can select individual pages or use any bulk-selection option shown in the interface. 5. Trigger meta title generation using the generation option available for your selected pages. 6. Wait for OTTO SEO to process the pages. The status of each page will update in the task list as generation completes. 7. Review the generated meta titles. You can edit individual titles if needed before applying them. 8. Use the available approval or deployment option shown in the interface to publish the generated meta titles to your site. Because the exact controls and labels in the OTTO SEO dashboard may vary depending on your account configuration and platform version, if you do not see the expected options, please reach out for direct assistance. 🔍 What to Have Ready If You Need Support If you encounter an error or a step does not match what you see on screen, please have the following ready when you reach out: - The name of the project you are working on in OTTO SEO - A description of what you see on screen and which step you are stuck on - Any error messages you have encountered - Approximately how many pages you need to generate meta titles for If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

📡 Find OTTO Pixel Data Options After Activation

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

⚙️ Configuring Sync to CMS by Content Type

📋 Overview The Sync to CMS setting in OTTO SEO lets you push optimizations directly into your connected CMS (such as WordPress) without leaving Search Atlas. You can configure this setting independently for different content types — including blog and article pages as well as service pages. This article explains how to locate and change the Sync to CMS setting for each content type. 🔗 What Is Sync to CMS? When Sync to CMS is enabled for a content type, any optimizations OTTO applies to matching pages are automatically pushed to your live CMS. When it is disabled, OTTO will still generate recommendations, but changes will not be sent to your CMS until you enable the sync for that content type. 🗂️ Understanding Content Types in OTTO SEO OTTO SEO categorises the pages on your site into distinct content types, most commonly: - Blog / Article pages — informational posts, news, or editorial content. - Service pages — commercial or product-focused pages describing your offerings. Each content type has its own independent Sync to CMS toggle, so you can push blog optimizations to your CMS while keeping service page changes in review mode, or vice versa. 🛠️ How to Change the Sync to CMS Setting for Blog or Article Content 1. Log in to Search Atlas and open the OTTO SEO dashboard for the relevant site. 2. Navigate to the section within OTTO SEO that lists the content types OTTO has detected on your site (such as Blog, Article, or Service). 3. Find the row corresponding to Blog or Article content (the label reflects how OTTO has classified your content). 4. Locate the Sync to CMS toggle on that row and click it to enable or disable syncing for blog and article pages. Once changed, OTTO will apply or withhold CMS pushes for blog and article content according to your new selection, without affecting the Sync to CMS state of your service pages or any other content type. 🔄 How to Change the Sync to CMS Setting for Service Pages 1. Return to the content types section in the OTTO SEO dashboard. 2. Find the row labelled Service or the content type that represents your service pages. 3. Click the Sync to CMS toggle on that row to enable or disable syncing for service pages independently. Because the exact UI labels and layout may vary depending on your site's content structure, if you are unsure which content type row to update or cannot locate the Sync to CMS toggle for a specific content type, please reach out to our team for guided assistance. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 How OTTO Deploys SEO Fixes to Your Site

🧠 Overview: Two Different Ways SEO Changes Can Appear When OTTO marks a fix as Deployed in Search Atlas, it does not mean your Shopify backend data has been updated. OTTO and Shopify operate through two separate mechanisms. Understanding the difference is essential for troubleshooting why a change appears live on your page but is not reflected inside your Shopify admin. ⚙️ How OTTO Actually Deploys Changes OTTO applies SEO fixes by injecting a header script directly onto your live page. This script runs when a visitor (or a search engine crawler) loads the page and dynamically renders the corrected SEO element — such as a title tag or meta description — in real time. - OTTO does not write changes to your Shopify database or theme files. - The fix exists as long as the OTTO script is present and active on the page. - Your Shopify admin will continue to show the original, unedited value because the backend data has not changed. This is by design. OTTO's script-based approach allows fixes to be applied and reversed quickly without permanently modifying your store's data. 🏪 Why "Deployed" in Search Atlas Doesn't Mean Shopify Is Updated The Deployed status in Search Atlas confirms that OTTO's fix has been successfully pushed to the header script and is rendering on the live page. It is not a confirmation that the underlying Shopify field has been edited. If you navigate to your Shopify admin after OTTO deploys a title tag fix, you will see the original title tag still stored there. Both values can coexist: the script-rendered value is what search engines and visitors see, while the backend retains the old value. Do not rely on the Shopify admin to verify whether an OTTO fix is active — always check the rendered source of the live page instead. ⚔️ What Happens When OTTO and Manual Shopify Edits Target the Same Field If you manually edit a field in Shopify — for example, updating a title tag directly in your Shopify admin — and OTTO has already deployed a fix for that same field, a conflict can occur: 1. The OTTO script continues to render its version of the fix on the live page. 2. Your manual Shopify edit is stored in the backend but may be overridden by the script at page load. 3. Search Atlas will not automatically detect your manual change until OTTO recrawls the page. To resolve a conflict and let your manual Shopify edit take effect cleanly, you should undeploy the OTTO fix for that field inside Search Atlas, then allow the page to be recrawled so Search Atlas reflects the updated backend value. 🔄 OTTO Recrawl Requirement After Manual Backend Changes Any time you make manual changes to SEO fields directly in Shopify, Search Atlas will not automatically know about those changes. OTTO bases its recommendations and deployed fixes on the data it last crawled. If you edit the backend without triggering a recrawl, the following can happen: - Search Atlas may still show the old value as the current page content. - OTTO may continue to deploy a fix for a problem that no longer exists in the backend. - Reporting and fix status may appear inconsistent. After making manual changes in Shopify, return to Search Atlas and trigger a fresh crawl of your site so OTTO can detect the updated values and adjust its recommendations accordingly. 🚨 What Happens When OTTO Disconnects or the Script Is Lost Because OTTO's fixes live in a header script and not in your Shopify backend, any event that removes or disables that script will cause all OTTO-deployed changes to stop rendering immediately. Common causes include: - Theme updates: Installing or switching to a new Shopify theme can remove the OTTO script, since the script is tied to the active theme's code. - OTTO disconnection: If the OTTO project is disconnected from your site inside Search Atlas, the script will no longer be served. - Manual theme file edits: Editing theme files directly and accidentally removing the script snippet. If your deployed fixes suddenly stop appearing on the live page, check whether your theme was recently updated or whether the OTTO project shows as disconnected in Search Atlas. You may need to reinstall the OTTO script by reconnecting the project. 🖼️ Why Theme Updates Remove OTTO's Header Script When you update your Shopify theme, Shopify replaces or resets the theme's code files. Because OTTO's script is embedded within those files, a theme update will overwrite it. After any theme update, verify that the OTTO script is still present by checking your live page source or reviewing the connection status inside Search Atlas. If the script has been removed, reconnect or reinstall it through your OTTO project settings. ✅ Quick Reference: Key Behaviors at a Glance - Deployed status = fix is active in the header script, not in Shopify's backend. - Shopify admin will show the original value even after OTTO deploys a fix. - Manual Shopify edits to the same field as an active OTTO fix can cause conflicts — undeploy the OTTO fix first. - Recrawl required after any manual backend change so Search Atlas reflects updated data. - Theme updates can remove the OTTO script — always verify script presence after a theme change. - OTTO disconnection removes all deployed fixes from the live page instantly. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔄 Locate and Use OTTO's Manual Reprocess Button

🧭 What Is the Manual Reprocess Button? The manual reprocess button is a dedicated control inside your OTTO project that lets you trigger a fresh analysis of your site's SEO data on demand. It is not the same as the Recrawl Site option in Site Auditor, and it is separate from OTTO's standard crawl feature. If a support tool or article pointed you toward either of those, this article will guide you to the correct button. 📍 Where to Find the Manual Reprocess Button 1. Log in to Search Atlas and click OTTO SEO in the left sidebar, then open All Sites (SEO Automation) inside it. This opens the OTTO dashboard at /seo-automation-v3. 2. Select the OTTO project you want to reprocess from your project list. 3. Once inside the project (OTTO Grader), scroll to the Recommendations section and look for the manual reprocess button. 4. Click the button to trigger reprocessing for that project. ⏱️ Cooldown Period — Important Timing Rule OTTO enforces a mandatory 1-hour cooldown between manual reprocess actions. If you click the button and nothing happens, or the button appears inactive, it means a reprocess was already triggered within the last 60 minutes. You must wait for the full hour to pass before the button becomes available again. - The cooldown applies per project, not per account. - Automated reprocessing that OTTO runs on its own also counts toward the cooldown timer. - There is no way to override or skip the cooldown period. 🔍 Manual Reprocess vs. Other Crawl Features It is easy to confuse similar-sounding features in Search Atlas. Here is a quick comparison to help you use the right tool: - Manual Reprocess (OTTO project) — Re-analyzes your site's SEO data within your active OTTO project. Use this when you want OTTO to reflect recent changes you have made to your site. - Recrawl Site (Site Auditor) — Initiates a new technical crawl of your website inside the Site Auditor tool. This updates audit data such as broken links, missing tags, and page errors, but does not trigger OTTO reprocessing. - OTTO Crawl — A background crawl that OTTO manages automatically as part of its ongoing optimization cycle. This runs on its own schedule and is separate from the on-demand manual reprocess. ✅ When to Use Manual Reprocessing Trigger a manual reprocess when: - You have recently published or updated pages and want OTTO to recognize those changes immediately. - You deployed new meta titles, descriptions, or structured data and want OTTO's recommendations to reflect the current state of your site. - OTTO's displayed data seems out of sync with your live site content. 🛠️ Troubleshooting - Button is greyed out or unclickable — The 1-hour cooldown is still active. Check when the last reprocess was triggered and wait until 60 minutes have passed. - Button is not visible — Confirm you are inside an OTTO project, not on the Site Auditor or another tool. Navigate to OTTO SEO in the left sidebar, open All Sites (SEO Automation), and re-enter your project. - Reprocessing completed but data looks unchanged — Allow a few minutes for the updated data to fully load. Refresh the page after 2–3 minutes to see the latest results. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔄 How to Sync OTTO SEO Changes to Shopify

This article explains the difference between a change being deployed within Search Atlas and that change being written to your live Shopify store — and walks you through the steps to confirm your optimizations have actually taken effect on your site. 🛠️ Step-by-Step 1. Understand what "Deployed" means: In Search Atlas, a status of Deployed means OTTO SEO has successfully pushed the change through the integration layer toward your Shopify store. It does not automatically guarantee the change is visible on your live storefront — the sync still depends on your Shopify connection being active and authorized. 2. Verify your Shopify integration is connected: Open your project settings and confirm that your Shopify store is listed as an active integration. If the connection is disconnected or the authorization token has expired, deployed changes will queue but will not write to Shopify. 3. Re-authorize the integration if needed: If the connection appears inactive or shows an error, disconnect and reconnect your Shopify store through your project settings. You will be prompted to re-approve access in your Shopify admin. 4. Manually trigger a re-sync (if available): After confirming the connection is active, return to the OTTO SEO deployment that shows a Deployed status and use the re-deploy or re-sync option for that change to push it again through the now-confirmed connection. 5. Check your Shopify admin directly: Log in to your Shopify admin panel and navigate to the specific page, product, or meta field that OTTO SEO was optimizing. Confirm the updated title tag, meta description, or other field now reflects the value Search Atlas deployed. ✅ How to Confirm It Worked A Deployed status in Search Atlas is the starting confirmation, but it is not the final one. To verify the change is truly live on Shopify, do the following: - In your Shopify admin, open the specific page or product and check the SEO section — the title and meta description should match exactly what OTTO SEO deployed. - Use a browser with cache cleared (or an incognito window) to visit the live URL and inspect the page source (Ctrl+U or Cmd+U). Search for the meta title or description tag and confirm the new value appears. - If the old value still appears in Shopify after re-syncing, check whether a conflicting Shopify app or theme is overriding the meta fields, as this can prevent Search Atlas changes from persisting. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Find and Track Your Deployed OTTO SEO Tasks

🧭 Overview After deploying OTTO SEO tasks, it can be unclear where to find them, which pages were affected, and why some changes do not appear on your live site right away. This article explains how to locate your deployed tasks, interpret their status, and what to do if changes are not yet visible. 📍 Where to Find Your Deployed OTTO Tasks All OTTO SEO activity is managed inside the OTTO SEO section of the platform. Follow these steps to locate your deployed tasks: 1. In the left sidebar, click OTTO SEO, then All Sites (SEO Automation). 2. Open your OTTO SEO project or select the relevant site. 3. Navigate to the Tasks or Deployed tab within the OTTO dashboard. Here you will see a list of every task that has been deployed, including the page it applies to, the task type, and its current status. 4. Use the filters at the top of the list to narrow results by status (for example, Deployed, Pending, or Failed) or by task category such as title tags, meta descriptions, or schema. Each row in the task list shows the target URL, the type of change made, the date it was deployed, and whether the deployment was successful. 📊 Understanding Task Status Labels OTTO uses several status labels to describe where a task is in the process: - Deployed: OTTO has successfully written the change to your site. The fix is live from Search Atlas's side. - Pending: The task has been queued but not yet applied. This can happen during high-volume deployments. - Failed: The change could not be applied. This is usually caused by a permissions issue, a plugin conflict, or a disconnected integration. - Crawled: A search engine bot has visited the page since the fix was deployed. This confirms the change is being discovered. ⏳ Why Changes May Not Appear on Your Site Yet A status of Deployed means Search Atlas has sent the change — but several factors can delay it from appearing on your live site or in search results: - Caching: Your website, hosting provider, or CDN may be serving a cached version of the page. Clear your site cache after a deployment to force the updated version to load. - Plugin or theme conflicts: Some WordPress plugins or themes override meta fields. If a deployed tag is not appearing, check whether another plugin is outputting the same field and taking priority. - Integration sync delay: If OTTO is connected via a plugin, confirm the plugin is active and that the connection status in the OTTO dashboard shows as Connected. - Search engine crawl delay: Even after your page is updated, Google and other search engines need to re-crawl and re-index the page before changes appear in search results. This can take anywhere from a few hours to several days depending on your site's crawl frequency. - Indexing not yet triggered: OTTO deploys the fix to your page, but requesting re-indexing from Google is a separate step. You can speed this up by submitting the updated URL manually through Google Search Console using the URL Inspection tool and clicking Request Indexing. 🛠️ Steps to Troubleshoot a Deployed Task Not Showing 1. Go to OTTO SEO → All Sites (SEO Automation) in the left sidebar and open your OTTO project. 2. Find the task in the deployed list and confirm its status is Deployed and not Failed. 3. Visit the affected page in your browser, open the page source (right-click → View Page Source), and search for the expected change — for example, the new title tag or meta description. 4. If the change is not in the page source, clear your site cache and reload. If it still does not appear, check your OTTO plugin connection status. 5. If the change is visible in the page source but not in search results, submit the URL for re-indexing via Google Search Console. 6. If the task shows a Failed status, review the error detail shown in the task row and check that OTTO has the necessary permissions to edit your site. 💡 Tips for Staying on Top of OTTO Deployments - Review the OTTO task list after every bulk deployment to confirm all tasks show a Deployed status before expecting changes on your site. - Clear your cache immediately after deploying a batch of tasks to avoid confusion caused by stale pages. - Use Google Search Console alongside OTTO to monitor crawl activity and confirm that search engines are picking up your updates. - Check back on deployed tasks after 48–72 hours — most changes will be crawled and reflected in search results within this window for regularly crawled sites. 💬 Still Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team. Additional Notes If you cannot find a specific task, verify that you are inside the correct OTTO project. Also confirm that the deployment step was fully completed — tasks that were only saved or queued may not yet appear as deployed.

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

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

🔄 Switch Domains on Your OTTO SEO Pixel

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

🏢 Managing OTTO SEO for Multi-Location Same-Domain Businesses

🗺️ Overview If your business operates multiple physical locations under a single website and domain, you can create a separate OTTO SEO project for each location. This allows you to target location-specific optimizations — including distinct Google Business Profiles — while sharing the same domain, Google Search Console (GSC) property, and social accounts. This guide walks you through the setup process and explains how OTTO handles shared resources across projects. 📋 Before You Begin Make sure you have the following ready for each location: - A verified Google Business Profile (GBP) for each location - Access to your Google Search Console property (shared across locations is fine) - Your shared domain URL - Location-specific details such as address, phone number, and service area 🚀 Step 1: Create the First OTTO SEO Project 1. In the left sidebar, navigate to OTTO SEO → All Sites (SEO Automation). 2. Click Create New Project (or open an existing project if you have already set one up for your first location). 3. Enter your domain URL in the website field. 4. Connect your Google Search Console property when prompted. 5. Under the Google Business Profile section, select or connect the GBP that corresponds to Location 1. 6. Complete the remaining setup steps and save the project. 🏗️ Step 2: Create a Second OTTO SEO Project for Location 2 1. From OTTO SEO → All Sites (SEO Automation), click Create New Project again. 2. Enter the same domain URL as your first project — this is expected and fully supported. 3. Connect the same Google Search Console property you used for Location 1. 4. Under the Google Business Profile section, select or connect the GBP that corresponds to Location 2. This must be a different GBP than the one used in your first project. 5. Complete the remaining setup steps and save the project. ⚙️ How Shared Resources Are Handled OTTO SEO is designed to support this multi-project setup. Here is how shared and unique elements work across projects: - Domain: The same domain can be used across multiple OTTO projects without conflict. - Google Search Console: The same GSC property can be connected to more than one project. GSC data will reflect the full domain, not individual locations. - Facebook Page: If both locations share a Facebook page, you can connect the same page to both projects. - Google Business Profile: Each project must connect to a unique GBP. This is the key differentiator that allows OTTO to deliver location-specific optimizations, such as GBP post scheduling, review management, and local SEO recommendations. 💡 Tips for Managing Multi-Location Projects - Name your projects clearly: Use descriptive project names that include the location (e.g., "Brand Name – New York" and "Brand Name – Los Angeles") so you can easily switch between them. - Review OTTO suggestions per project: Each project will generate optimization tasks tailored to its connected GBP and local context. Review and apply these separately for each location. - Track performance individually: Although GSC data is shared, OTTO will contextualize recommendations based on each location's GBP signals and local keywords. - Keep GBP listings up to date: OTTO relies on accurate GBP data to generate relevant local SEO tasks. Ensure each location's GBP has correct hours, address, and categories. ❓ Frequently Asked Questions Can I use the same domain for more than two locations? Yes. You can create as many OTTO projects as you have unique Google Business Profiles, all sharing the same domain. Will having multiple projects for the same domain cause duplicate optimizations? No. Each project operates independently based on its connected GBP. OTTO tailors its recommendations to that specific location's local signals. What if my locations share the same GBP? Each OTTO project requires a distinct GBP. If your locations share a single GBP listing, we recommend creating separate GBP listings for each physical location in Google Business before setting up additional OTTO projects. 🆘 Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 OTTO SEO: Meta Keywords and Alt Text Visibility

🧭 Overview When OTTO SEO deploys on-page optimizations to your website, two common questions arise: Where do meta keywords appear? and Where does image alt text appear? These are two distinct SEO elements that behave very differently after deployment. This article explains exactly what each element does, who can see it, and where to verify it. 📋 Meta Keywords: Source Code Only Meta keywords are placed inside the <head> section of your page's HTML as a <meta> tag. They are not visible to website visitors on the page itself. No text, label, or indicator appears anywhere on the front-end of your site. Meta keywords are only accessible in two places: - Your page's source code — right-click any page and select View Page Source to find the tag inside the <head> section. - Browser developer tools — open DevTools (F12), go to the Elements tab, and inspect the <head> block. This is standard browser behaviour and is not specific to OTTO SEO. Meta keywords have no visual presence on a webpage by design — they exist purely as metadata read by crawlers and tools, not by human visitors. 🖼️ Image Alt Text: Visible in Source Code and to Assistive Technology Image alt text behaves very differently from meta keywords. After OTTO SEO deploys alt text to your images, it becomes part of the rendered HTML of your page — meaning it is accessible to website visitors and external tools, not hidden inside a software layer. Specifically, deployed image alt text: - Appears in your page's source code — right-click the page, select View Page Source, and search for the alt="" attribute on your <img> tags. - Is read aloud by screen readers — visitors using assistive technology will hear the alt text description when they navigate to that image. - Displays as fallback text — if an image fails to load in a visitor's browser, the alt text appears in place of the broken image. - Is indexed by search engines — Googlebot and other crawlers read alt text directly from your page's HTML to understand image content. Alt text does not appear as a visible caption or label on the page for sighted visitors under normal circumstances — but it is fully present in the live HTML that anyone can inspect. ⚖️ Side-by-Side Comparison - Meta Keywords — Location: <head> section of HTML | Visible to site visitors: No | In page source code: Yes | Read by screen readers: No | Indexed by Google: No (largely ignored by modern search engines) - Image Alt Text — Location: <img> tag within page body | Visible to site visitors: No (unless image fails to load) | In page source code: Yes | Read by screen readers: Yes | Indexed by Google: Yes ✅ How to Verify Deployments in OTTO SEO 1. In the left sidebar, navigate to OTTO SEO → All Sites (SEO Automation) (URL: /seo-automation-v3). 2. Locate the page you optimized. 3. In your browser, open a new tab and go to the live URL of that page. 4. Right-click anywhere on the page and select View Page Source. 5. To check meta keywords: press Ctrl+F (or Cmd+F on Mac) and search for meta name="keywords". You will find it inside the <head> block. 6. To check image alt text: search for alt= in the source code. Each deployed alt text value will appear inside the corresponding <img> tag. If you do not see your changes reflected in the page source within a few minutes of deployment, try a hard refresh (Ctrl+Shift+R or Cmd+Shift+R) to bypass any cached version of the page. ❓ Frequently Asked Questions - Will visitors see my meta keywords on the page? No. Meta keywords are hidden metadata. No visitor — regardless of device or browser — will see them displayed on the page. - Does OTTO SEO only change how things look on the front end? No. Image alt text is written directly into your page's HTML source, making it a real structural change — not just a visual overlay. It will appear in your source code and be readable by search engines and assistive technology. - Why can't I see the alt text with my eyes on the page? Alt text is not a visible caption. It lives inside the HTML tag itself. You can confirm it is there by viewing the page source or using browser DevTools to inspect the image element. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ How to Manually Override Page-Level Schema Type

This article explains what to do when the AI-generated schema type assigned to a page in Search Atlas is incorrect and persists even after a recrawl. The specific steps to manually override a page-level schema type require assistance from our support team, who can apply the correct schema type directly on your behalf. What We Know - The issue involves a page-level schema type that the AI has misclassified. - Triggering a recrawl alone does not reliably fix a persistent schema type misclassification — a manual override is required. - This type of override currently requires the support team to step in and apply the correct schema type for the affected page. How to Get This Resolved Because manually changing a page-level schema type requires support intervention, please reach out to our team directly. To help us resolve this as quickly as possible, have the following ready before reaching out: - The project name where the affected page lives. - The exact URL of the page with the incorrect schema type. - The current (incorrect) schema type being assigned by the AI. - The correct schema type you want applied to that page. - Any steps you have already tried (e.g., triggering a recrawl, saving changes). If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🗂️ Accessing Your Project Overview in Search Atlas

🔍 Understanding the Issue When you click on a project from the Home dashboard, you may be taken directly to Site Audit rather than the project overview. This is a known navigation behaviour that can prevent you from quickly accessing content research tools, on-page editing features, and title tag management. This article explains how to reach the correct project overview so you can get back to your workflow. 🏠 How to Access Your Project Overview Follow these steps to navigate to your project overview where you can research content and edit on-page elements such as title tags: 1. In the left sidebar, click OTTO SEO. 2. Select Overview from the expanded sub-menu. This takes you to the OTTO SEO Overview page, which serves as the central hub for your project. 3. From the Overview page, locate your project and click on it to access project-level details, content tools, and on-page editing options. If you need to access features such as crawl data, page exploration, or content velocity, use the additional sub-pages listed under OTTO SEO in the left sidebar: - Crawl Monitoring — track crawl activity and coverage. - Page Explorer — browse and analyse individual pages. - Content Velocity — review content publishing trends. - All Audits — view all audit results across your projects. ⚠️ Why Does Clicking a Project Go to Site Audit? A bug was previously identified where clicking a project from the Home dashboard incorrectly redirected users to Site Audit instead of the project details page. This issue has been resolved in a recent update. If you are still experiencing this behaviour, try the following: - Refresh your browser and clear your cache, then attempt to open the project again from the Home dashboard. - Use the OTTO SEO → Overview path described above as a reliable alternative route to your project details. - Ensure you are using an up-to-date browser version for the best experience. 🛠️ Editing On-Page Elements Like Title Tags Once you are inside your project overview via OTTO SEO → Overview, you can access on-page editing tools including title tags, meta descriptions, and other content elements. Look for the on-page optimisation or content editing section within the project detail view to make changes directly. 💡 Quick Navigation Tips - Bookmark the OTTO SEO Overview page in your browser for faster access in future sessions. - Use the left sidebar as your primary navigation tool — it provides direct links to every major section without passing through the Home dashboard. - If a project appears stuck in a loading state, refresh the page or navigate away and return via the sidebar. 🙋 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

✍️ OTTO Page Optimization: Capabilities and Limitations Explained

🔍 What Is OTTO's Role in Page Optimization? OTTO is Search Atlas's OTTO SEO automation tool. It analyzes your connected pages and generates optimization recommendations — such as suggested rewrites for headings, meta descriptions, body content, and more. OTTO surfaces these suggestions directly inside the platform so you can review and act on them. OTTO does not directly edit, rewrite, or publish changes to your live website pages. It is a recommendation engine, not a content editor with CMS access. Any changes to your existing pages must be made manually inside your own CMS (for example, WordPress, Shopify, or Webflow). ⚙️ What OTTO Can Do - Audit your connected pages and identify on-page SEO gaps. - Generate rewrite suggestions for titles, meta descriptions, headings, and body copy. - Provide keyword and content structure recommendations tailored to your target terms. - Continuously monitor pages and update recommendations as search conditions change. - Surface actionable tasks in a prioritized list so you know what to address first. 🚫 What OTTO Cannot Do - Directly edit or overwrite content on your live website pages. - Publish or schedule content changes through your CMS automatically. - Create a new version of an existing page on your site without your manual input. - Push rewritten text live without you copying it into your CMS first. If you have noticed that following OTTO's workflow seems to produce a new page draft rather than updating an existing one, this is expected behavior in some workflows — OTTO creates a draft recommendation document inside Search Atlas, not a new page on your website. Your live site is never modified without your direct action. 📋 How to Apply OTTO's Recommendations to an Existing Page 1. Go to Left sidebar → OTTO SEO → SEO Automation to open the OTTO dashboard. 2. Locate the page you want to optimize in your connected pages list and open its recommendations. 3. Review the suggested rewrites for each content element (headings, body text, meta tags, etc.). 4. Copy the recommended text you want to use. 5. Log in to your CMS and navigate to the existing page you want to update. 6. Paste the optimized content into the appropriate fields and save or publish your changes. 7. Return to OTTO — it will re-crawl the page and confirm when the recommendations have been implemented. ✏️ Using the On-Page Audit for Deeper Content Guidance If you want a more detailed content rewrite experience before applying changes, the On-Page Audit tool gives you an in-depth analysis of a specific URL alongside content improvement suggestions. To access it, go to Left sidebar → Content → On-Page Audit. Enter your target URL and keyword, and the tool will produce a scored report with specific copy recommendations you can bring back to your CMS. 🛠️ Other Content Tools That Support Page Rewrites Search Atlas includes several additional tools that can help you rewrite and improve existing page content before you publish it in your CMS: - AI Content Templates — Left sidebar → Content → AI Content Templates. Use pre-built templates to generate optimized content blocks for common page types. - Meta Generator — Left sidebar → Content → Meta Generator. Quickly produce optimized title tags and meta descriptions for existing pages. - Scholar — Left sidebar → Content → Scholar. Research topics and gather supporting information to strengthen your rewrites. 💡 Key Takeaway OTTO is a powerful SEO advisor that tells you what to change and how to change it. The actual editing always happens inside your own CMS. Think of OTTO as a co-pilot: it handles the analysis and recommendations while you apply the changes where they count — on your live site. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

[UI Map] OTTO SEO

OTTO SEO Navigation path: Left sidebar → OTTO SEO URL pattern: /seo-automation-v3 Manages all OTTO SEO site projects, allowing users to deploy AI-driven SEO optimizations and technical fixes across multiple websites from a single dashboard. Primary actions: - Create - Scan - Freeze sites ( 0 ) - Clear selection - Explore Training Calls - Active 4 - Deep Frozen 5 - Add Domain - Active (14) - Inactive - All (238) - Previous page - Next page Key UI elements: - Site project cards list - Bulk freeze checkboxes - Installation status badge (Not Installed / Installed / Installed (WP) / Duplicate) - OTTO pixel engagement status - Healthy Pages count and progress bar - Grader score progress bar - Content / Authority / Technical / UX Signals score breakdown - Last analysis and Next analysis timestamps - Time saved with OTTO counter - Smart Crawl status indicator - Google Search Console integration icon - Google Business Profile integration icon - WordPress integration icon - Pagination controls - Lines per page dropdown (5 / 10 / 20 / 50 / 100) - Domains table - Status filter buttons (Active / Inactive / All) - Search domains text field - Add Domain button - Pagination controls (Previous / Next page, page number buttons) - Lines per page selector (10 / 20 / 50 / 100) - Platform icons per row (ChatGPT, Gemini, Perplexity, Copilot, Google AI Mode) - Sentiment score with tooltip (Positive / Neutral) - Row options button (kebab per domain) - Banner: Join Live Workshops & Training Sessions Sub-pages - All Sites — Navigation path: Left sidebar → OTTO SEO → All Sites (SEO Automation) — Lists all OTTO SEO site projects with their installation status, grader scores, healthy page counts, and engagement state for bulk management. — Actions: Create, Scan, Freeze sites ( 0 ), Clear selection, Active 4, Deep Frozen 5 - Overview — Navigation path: Left sidebar → OTTO SEO → Overview — Provides a high-level summary and overview dashboard for a selected OTTO SEO site project. - Crawl Monitoring — Navigation path: Left sidebar → OTTO SEO → Site Audit → Crawl Monitoring — Monitors crawl activity and status for the selected OTTO SEO site project. - Knowledge Base — Navigation path: Left sidebar → OTTO SEO → Knowledge Base — Links to the external Search Atlas help documentation and knowledge base for OTTO SEO. - Installation Guide — Navigation path: Left sidebar → OTTO SEO → Installation Guide — Provides step-by-step instructions for installing the OTTO SEO pixel or plugin on a site. - All Audits — Navigation path: Left sidebar → OTTO SEO → Site Audit → All Audits — Shows all site audits associated with OTTO SEO projects. - Page Explorer — Navigation path: Left sidebar → OTTO SEO → Site Audit → Page Explorer — Explores individual pages of the selected site audit project for SEO insights (requires a project to be created). - Content Velocity — Navigation path: Left sidebar → OTTO SEO → Site Audit → Content Velocity — Tracks and analyzes content publishing velocity for the selected site audit project (requires a project to be created). - Domain-level — Navigation path: Left sidebar → OTTO SEO → Domain-level — Displays domain-level SEO metrics and analysis for the selected site audit project (requires a project to be created). - Issues — Navigation path: Left sidebar → OTTO SEO → Issues — Lists SEO issues detected during site audits for the selected project (requires a project to be created). - Page Pruning — Navigation path: Left sidebar → OTTO SEO → Site Audit → Page Pruning — Identifies and manages underperforming pages recommended for pruning (requires a project to be created). - Site Lens — Navigation path: Left sidebar → OTTO SEO → Site Audit → Site Lens — Provides a visual lens view of site structure and SEO health for the selected project (requires a project to be created). - Email Alerts — Navigation path: Left sidebar → OTTO SEO → Email Alerts — Configures email alert notifications for site audit events for the selected project (requires a project to be created). - Live Monitoring — Navigation path: Left sidebar → OTTO SEO → Site Audit → Live Monitoring — Monitors the site in real-time for SEO changes and anomalies for the selected project (requires a project to be created). - All Projects — Navigation path: Left sidebar → AI Visibility → All Projects — The main projects list view showing all domains being tracked for AI visibility with status, visibility score, sentiment, platforms, schedule, and last scan information. — Actions: Add Domain, Active (14), Inactive, All (238), Previous page, Next page - Summary — Navigation path: Left sidebar → AI Visibility → Summary — Per-project summary of AI visibility data — requires a project to be opened first before content is accessible. - Visibility — Navigation path: Left sidebar → AI Visibility → Visibility — Per-project AI visibility trend and breakdown — requires a project to be opened first before content is accessible. - Sentiment — Navigation path: Left sidebar → AI Visibility → Sentiment — Per-project sentiment analysis of AI-generated brand mentions — requires a project to be opened first before content is accessible. - Topics & Queries — Navigation path: Left sidebar → AI Visibility → Topics & Queries — Per-project breakdown of topics and queries driving AI visibility — requires a project to be opened first before content is accessible. - Prompt Simulator — Navigation path: Left sidebar → AI Visibility → Prompt Simulator — Simulates AI prompts to see how the brand appears in AI-generated answers — requires a project to be opened first before content is accessible. - Site Detail — Navigation path: Left sidebar → OTTO SEO → Site Detail (URL: /seo-automation-v3/{project-id}) — Displays a detailed OTTO SEO project view for a specific site, showing SEO health grades, holistic SEO pillar scores, pending optimizations, and categorized recommendations that can be enabled or rolled back across onpage, link, indexing, miscellaneous, and content strategy categories. — Actions: Disengage OTTO, Scan, Open Brand Vault, Open Performance Report, View all, Filter by URL, Check now, Connect, Enable all in Category, Roll back all, Enable - DNS Setup RECOMMENDED — Navigation path: Left sidebar → OTTO SEO → Installation Guide → DNS Setup RECOMMENDED tab — Connects the site to OTTO via Cloudflare by generating and pasting a Cloudflare API Token to link domains automatically. — Actions: Validate & Connect, Step-by-step tutorial, Not sure which method to pick? Compare implementation benefits, Scan for pixel installation - CMS Integration — Navigation path: Top-right avatar → Settings → CMS Connectors — Connects the site to OTTO via a Content Management System (CMS) by providing a CMA Token, Space ID, and Environment ID. — Actions: Not sure which method to pick? Compare implementation benefits - Script Installation — Navigation path: Left sidebar → OTTO SEO → Installation Guide → Script Installation tab — Connects the site to OTTO by adding a custom SearchAtlas script via a tag manager (e.g., Google Tag Manager) using a Custom HTML tag. — Actions: Not sure which method to pick? Compare implementation benefits - WordPress Installation — Navigation path: Left sidebar → OTTO SEO → Installation Guide → WordPress Installation tab — Connects the site to OTTO by installing the Search Atlas WordPress plugin and connecting it to the account. — Actions: Not sure which method to pick? Compare implementation benefits - WordPress Installation RECOMMENDED — Navigation path: Left sidebar → OTTO SEO → Installation Guide → WordPress Installation RECOMMENDED tab — Step-by-step instructions for installing the Search Atlas WordPress plugin and connecting it to OTTO SEO. — Actions: WordPress, Email my developer, Not sure which method to pick? Compare implementation benefits, Go to OTTO SEO, Open, Scan, Disengage OTTO - DNS Setup — Navigation path: Left sidebar → OTTO SEO → Installation Guide → DNS Setup tab — Instructions for connecting the site to OTTO SEO via DNS-level setup. — Actions: Not sure which method to pick? Compare implementation benefits, Scan, Disengage OTTO Auto-generated by SA UI Mapper. Last updated: 2026-09-18.

⚡ Bulk Generate AI Fixes in OTTO SEO

🧭 Overview OTTO SEO's Bulk Actions feature lets you select up to 100 tasks at once and generate AI suggested fixes in a single click. If you are managing hundreds of tasks, this workflow will save you significant time compared to handling each row individually. You can also use the Atlas Agent chat for broader guidance, but the built-in Bulk Actions feature is the fastest way to generate fixes at scale. 🗂️ Step 1: Open OTTO SEO 1. Log in to your Search Atlas account. 2. In the left sidebar, click OTTO SEO → SEO Automation (All Sites). The URL will change to /seo-automation-v3. 3. Select the project you want to work on from the project switcher at the top of the page. 4. You will land on the OTTO SEO task list, which displays all outstanding SEO tasks organised by category. ✅ Step 2: Select Multiple Tasks 1. Locate the checkbox column on the far left of the task list table. 2. Click the checkbox next to each task you want to include. You can select up to 100 tasks per batch. 3. To select tasks faster, use the Select All checkbox in the column header. This selects all tasks visible on the current page (up to 100 rows). 4. If you need to filter first, use the category filters or status filters above the task list to narrow results before selecting. This helps you target a specific task type, such as missing meta descriptions or broken headings, in one batch. ⚙️ Step 3: Generate AI Suggested Fixes in Bulk 1. Once your tasks are selected, a Bulk Actions toolbar will appear at the top or bottom of the task list. 2. Click the Bulk Actions button or dropdown. 3. Select Generate AI Suggested Fix from the available options. 4. Confirm the action when prompted. OTTO SEO will begin generating AI suggested fixes for all selected tasks simultaneously. 5. Wait for the generation to complete. Depending on the number of tasks selected, this may take a few moments. The task list will update automatically when fixes are ready. 🔄 Step 4: Handle More Than 100 Tasks Because each batch is limited to 100 tasks, you will need to repeat the process if you have a larger volume, such as 500 tasks. Here is the most efficient approach: 1. Apply a filter to isolate a specific task category or status so your task list shows a manageable subset. 2. Select all tasks on the page using the header checkbox. 3. Run Generate AI Suggested Fix via Bulk Actions. 4. Once that batch is complete, clear the selection, move to the next page or adjust the filter, and repeat. 5. Continue until all task categories have been processed. Working category by category keeps batches organised and makes it easier to review fixes before approving them. 🤖 Alternative: Use Atlas Agent for Guided Assistance If you prefer a conversational approach or need help deciding which tasks to prioritise, Atlas Agent can assist you directly inside the platform. - Open the Atlas Agent chat panel within OTTO SEO. - Ask Atlas Agent to identify high-impact tasks or suggest a processing order for your specific site. - Atlas Agent can provide recommendations, but you will still use the Bulk Actions workflow described above to generate the actual fixes at scale. Atlas Agent is a useful companion for strategy, but Bulk Actions is the primary tool for generating fixes efficiently across large task volumes. ✍️ Step 5: Review and Apply Fixes 1. After generation, each task will display its AI suggested fix in the task detail panel. 2. Review the suggestions to confirm they match your content style and SEO goals. 3. Use Bulk Approve (if available for your plan) to apply multiple accepted fixes at once, or approve them individually as needed. 4. Tasks that have been approved and applied will move to a Completed or Resolved status, keeping your task list current. 💡 Tips for Working With Large Task Volumes - Filter before you select. Narrowing by category first ensures your 100-task batch is focused and easier to review. - Work highest-impact tasks first. Prioritise tasks flagged as critical or those affecting your most-visited pages. - Do not skip the review step. AI suggested fixes are a strong starting point, but a quick review ensures the output aligns with your brand voice and technical requirements. - Check task status after each batch. Refreshing the list confirms that fixes generated correctly before you move to the next batch. 🆘 Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔗 Exclude URL Patterns and Manage Subdomains in SearchAtlas

🗺️ Overview SearchAtlas gives you precise control over which URLs appear in your dashboards and reports. Using the URL Exclusion conditions feature inside your project's OTTO SEO Settings, you can filter out URLs that are not relevant to your SEO analysis — such as thank-you pages, admin paths, or staging URLs. Additionally, SearchAtlas treats subdomains as separate projects by default, which is important to understand when reviewing your data. ⚙️ Where to Find URL Exclusion Conditions 1. Log in to your SearchAtlas account. 2. In the left sidebar, click OTTO SEO and open SEO Automation (All Sites view at /seo-automation-v3), then open the project you want to configure. 3. At the top of the project overview, click the Autopilot / Smart Crawl card to open the OTTO SEO Settings modal. You can also reach it from the All Sites table by clicking the Smart Crawl status text on your site's card. 4. Scroll to the URL Exclusion conditions section. 5. Click + Add condition to begin entering your exclusion rules. ✍️ How to Write URL Exclusion Patterns URL exclusion conditions match URLs with two simple operators: Contains and Start With. When you add a condition, you choose Exclude, then pick the operator and type the text to match — for example /blog/ or ?ref=email. There is no wildcard or regular-expression syntax. Use the following operators when entering conditions: - Start With — matches the beginning of the URL path. Use /blog/ to exclude all URLs that begin with /blog/, such as /blog/post-1 and /blog/category/news. - Contains — matches that text anywhere in the URL. Use ?ref=email to exclude any URL containing that query string parameter, regardless of the path, or /admin/ to exclude any URL that contains /admin/ anywhere in the path. Conditions are matched against the full URL path and query string. To exclude several different groups of URLs, add one condition per group. 📋 Common Exclusion Pattern Examples - Start With /cart — Excludes the shopping cart page and anything under it. - Start With /checkout/ — Excludes all checkout step pages. - Contains ?sessionid= — Excludes URLs with dynamic session ID parameters. - Start With /wp-admin/ — Excludes all WordPress admin URLs. - Contains /print/ — Excludes print-version pages anywhere on the site. - Contains .jpg — Excludes direct links to image files. 💾 Saving and Applying Your Exclusions 1. Each condition is added with + Add condition — set it to Exclude, choose Contains or Start With, and type the text to match. 2. Repeat for each additional group of URLs you want to exclude. 3. When all conditions are entered, click Update Settings. 4. SearchAtlas will apply your exclusion rules to new data going forward. Historical data already processed may require a new crawl to reflect the updated exclusions. 🌐 How Subdomains Are Handled in SearchAtlas By default, SearchAtlas treats each subdomain as a separate, independent project. This means that blog.yourdomain.com, shop.yourdomain.com, and yourdomain.com are each tracked and reported on individually — they do not share data within the same dashboard unless explicitly configured together. Key points to understand about subdomain handling: - Subdomains are not automatically included in a root domain project. You must add each subdomain as its own project if you want to monitor it. - Google Search Console data is pulled per property. If your GSC property is set to the root domain (domain property), subdomain data may be included. If it is a URL-prefix property, only that specific subdomain or path is covered. - Backlink and keyword data is scoped to the project URL you define at setup. A project for yourdomain.com will not automatically surface data for shop.yourdomain.com. - URL exclusion conditions are project-specific. Patterns you configure for one project do not carry over to a subdomain project — you must configure exclusions independently for each. 🔄 Editing or Removing Existing Exclusion Rules 1. Open the relevant project and click the Autopilot / Smart Crawl card to open the OTTO SEO Settings modal. 2. Scroll to URL Exclusion conditions. 3. Find the condition you want to update or remove, and edit or delete it. 4. Click Update Settings to confirm your changes. 💡 Tips for Effective URL Exclusion - Start broad and refine. Check a condition against a small set of known URLs before adding it to avoid accidentally excluding important pages. - Exclude paginated URLs with a Contains ?page= condition if pagination creates duplicate content noise in your reports. - Review your exclusion list periodically as your site structure changes — outdated rules can hide content you now want to track. - Use exclusions on each project for the most precise control over what SearchAtlas indexes and reports on. 🆘 Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 OTTO Pixel Data, Deployment History & Webflow

🛰️ What Data Does the OTTO Pixel Collect? The OTTO pixel is a lightweight tracking script you place on your website. It collects anonymised, session-level behavioural data to help OTTO understand how visitors interact with your pages. Specifically, it captures: - Page views and URL paths — which pages are visited and in what order. - Scroll depth — how far down a page a visitor scrolls. - Click events — interactions with links, buttons, and navigation elements. - Session duration — time spent on individual pages and across the full session. - Device and browser type — general environment data (e.g. mobile vs desktop, browser family). - Referral source — the channel or URL that brought the visitor to your site. The OTTO pixel does not collect personally identifiable information (PII) such as names, email addresses, or payment details. No individual user profiles are created. All data is processed solely to inform OTTO's on-page SEO recommendations and to measure the impact of deployed changes on engagement signals. 📋 How to View Previously Deployed Changes in OTTO OTTO keeps a full log of every change it has applied to your site so you can audit, review, or roll back at any time. 1. In the left sidebar, navigate to OTTO SEO, then open All Sites (SEO Automation). 2. Open the OTTO project you want to review. 3. Click the Deployment History tab near the top of the project dashboard. 4. You will see a chronological list of all deployed actions, each showing the date and time, the page or element affected, the type of change (e.g. title tag update, meta description, schema injection), and the deployment status (Active, Rolled Back, or Pending). 5. Click any entry to expand the full details, including the before and after values for that change. 6. To revert a specific change, click Roll Back next to the relevant entry and confirm the action. Deployment history is retained indefinitely for your project so you always have a complete record of what OTTO has modified. 🌐 Will OTTO Changes Be Visible in Webflow Developer Mode? This depends on how OTTO deploys changes to your Webflow site. JavaScript-injected changes (default method): OTTO deploys most SEO updates — such as meta tags, structured data, and canonical tags — by injecting them via the OTTO pixel script at page load. These changes are applied to the rendered DOM and are not written back into the Webflow Designer or CMS. As a result, they will not be visible in Webflow's Designer, Editor, or developer mode panels. However, they are fully visible to search engine crawlers and in your browser's View Page Source or Inspect Element tools on the live site. Direct CMS integration (if enabled): If you have connected OTTO to your Webflow site via the native CMS integration, certain content-level changes may be written directly to Webflow CMS fields. In this case, those specific changes will appear inside Webflow's Editor and CMS collections. Check your OTTO project settings under Integrations to confirm which deployment method is active for your Webflow site. Key takeaway: Always verify OTTO changes by viewing your live page source rather than relying on Webflow's Designer view, unless you are using the direct CMS integration. ✅ Quick Reference Summary - OTTO pixel collects: anonymised behavioural data only — no PII. - Deployment history: found in OTTO SEO → All Sites (SEO Automation) → your OTTO project → Deployment History tab. - Webflow Designer visibility: changes are not visible in Designer by default; use View Page Source on the live site to confirm. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 View and Edit Deployed Titles and Meta Descriptions in OTTO

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

🤖 Managing OTTO Bulk Deletions, Subdirectory Scope, and External Platform Limits

🗂️ Overview This article covers three related OTTO workflows that are commonly misunderstood: bulk-deleting title tag suggestions, scoping an existing OTTO instance to include a new subdirectory, and understanding why Twitter/X (and other external platform) recommendations cannot be deployed directly through OTTO. 🗑️ How to Batch-Delete Title Tag Suggestions in OTTO OTTO does not currently support a single "select all and delete" button for title tag suggestions. However, you can remove multiple suggestions efficiently using the bulk-selection method below. 1. Navigate to OTTO SEO in the left sidebar, then open SEO Automation. 2. Open the relevant OTTO instance and go to the Title Tags section under On-Page recommendations. 3. Check the checkbox at the top of the suggestion list to select all visible items on the current page. 4. Click Reject or Delete from the bulk-action toolbar that appears. 5. Repeat for each additional page of suggestions until all unwanted items are removed. Important limitation: Bulk selection applies only to the suggestions visible on the current page. If you have hundreds of suggestions across multiple pages, you will need to repeat the selection and deletion step for each page. There is no platform-wide "delete all" option at this time. If you need to clear a very large volume of suggestions, contact support via the chat widget for guidance on the most efficient approach. 🌐 Managing a Subdirectory Under an Existing Domain with OTTO OTTO instances are scoped at the domain or subdomain level, not at the subdirectory level. This means one OTTO instance covers your entire root domain, including all subdirectories beneath it. If a client adds a new subdirectory (for example, example.com/new-section/) to a domain already connected to OTTO, you do not need to create a new OTTO instance. The existing instance will automatically discover and surface recommendations for pages within that new subdirectory once they are crawled. To ensure the new subdirectory is picked up promptly: 1. Go to OTTO SEO in the left sidebar, then open SEO Automation. 2. Open the existing OTTO instance for the domain. 3. Trigger a recrawl by navigating to OTTO SEO → Site Audit → Overview (Website Overview) and clicking the Recrawl Site button so OTTO indexes the new subdirectory pages. 4. Once the crawl completes, new recommendations for the subdirectory will appear alongside existing ones. Subdomains are different: A subdomain such as blog.example.com is treated as a separate property and requires its own dedicated OTTO instance. If you are unsure whether your client's new section is a subdirectory or a subdomain, check the URL structure — a subdirectory uses a forward slash after the root domain, while a subdomain uses a dot prefix before it. ⚠️ Twitter/X Recommendations Are Read-Only in OTTO OTTO can generate SEO and social recommendations for external platforms such as Twitter/X and LinkedIn, but it cannot deploy or publish these changes automatically. This is a known platform limitation caused by API restrictions on third-party write access to these external services. What this means in practice: - Twitter/X meta tag and profile recommendations appear inside OTTO for review purposes only. - The Deploy button is disabled or absent for these recommendation types. - Changes must be applied manually by logging into the respective external platform and updating the settings there. 📤 How to Export Twitter/X Recommendations and Apply Them Manually To action Twitter/X or other external platform recommendations without losing the OTTO-generated suggestions, follow this export workflow: 1. Navigate to OTTO SEO in the left sidebar, open SEO Automation, and then open the relevant OTTO instance. 2. Locate the Social / External Platform recommendations section. 3. Click the Export button (CSV or copy-to-clipboard, depending on your plan) to save the recommendations. 4. Open the exported file or your clipboard notes and review each suggestion. 5. Log in directly to your Twitter/X account (or LinkedIn, as applicable) and apply the changes manually — for example, updating your bio, profile description, or pinned post metadata. 6. Once applied, return to OTTO and mark the recommendations as Resolved or Dismissed to keep your task list clean. Tip: If you do not see an Export button, check that your account plan includes data export. Lower-tier plans may require an upgrade to access bulk export features. 📋 Quick Reference: OTTO Capability Summary - Title tag bulk deletion: Supported per-page via checkbox selection; no global delete-all option. - Subdirectory management: Covered automatically by the existing domain-level OTTO instance after a re-crawl. - Subdomain management: Requires a separate OTTO instance per subdomain. - Twitter/X recommendations: Read-only in OTTO — export and apply manually. - LinkedIn recommendations: Same read-only limitation as Twitter/X. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🗂️ How to Bulk Select All SEO Tasks at Once

This article explains how to select multiple SEO tasks in bulk so you can take action on them all at once — without clicking each task one by one. Up to 100 tasks can be selected at a time using the built-in bulk selection option. 🛠️ Step-by-Step 1. Navigate to the SEO task list within your project (for example, your OTTO SEO task queue). 2. Look for the checkbox at the top of the task list — this is the bulk select or "select all" checkbox located in the column header row, above the individual task checkboxes. 3. Click that header checkbox once to select all tasks currently visible on the page (up to 100 tasks at a time). 4. Once tasks are selected, the bulk action toolbar will appear — choose your desired action (such as enable, disable, or dismiss) and apply it to all selected tasks. 5. If you have more than 100 tasks, scroll to the next page and repeat the process to act on the next batch. ✅ How to Confirm It Worked After clicking the header checkbox, every task row on the current page should show a filled or checked checkbox next to it, and a bulk action bar or button group should become visible at the top or bottom of the list. This confirms all visible tasks are selected and ready for a bulk action. After applying an action, the task statuses should update accordingly — for example, tasks marked as enabled will show an active or enabled status in the list. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

📊 Improve UX Signals and OTTO's Role

🔍 What Are UX Signals? UX signals are measurable indicators of how real users experience your website. Search engines use these signals to evaluate page quality and determine rankings. Key UX signals include: - Core Web Vitals — page speed, visual stability, and interactivity (LCP, CLS, INP) - Bounce rate and dwell time — how long visitors stay and whether they return to search results - Mobile usability — how well your pages perform on smartphones and tablets - Page experience signals — HTTPS security, absence of intrusive interstitials, and safe browsing Strong UX signals tell search engines that your site delivers real value to visitors, which supports higher rankings and sustained organic traffic. ⚙️ What OTTO Currently Does With UX Signals OTTO evaluates your site across multiple pillars — including a UX Signal pillar — as part of its overall SEO health assessment. At this time, OTTO's UX Signal pillar provides a high-level score to help you understand where your site stands relative to page experience best practices. Important: The UX Signal pillar is actively being improved. Our engineering team is rebuilding it to replace placeholder metrics with genuine page experience signals such as Core Web Vitals data and real user interaction indicators. This means the scores and recommendations in this pillar will become significantly more detailed and actionable in an upcoming release. OTTO does not directly modify your site's server configuration, image compression, JavaScript execution, or other technical factors that affect Core Web Vitals. Improvements to those areas require action on your end or by your development team. 🛠️ How to Improve Your UX Signals Today While OTTO's UX pillar continues to evolve, you can take the following steps to improve your site's page experience right now: 1. Run a Core Web Vitals audit — Use Google Search Console (under the "Experience" section) or Google PageSpeed Insights to identify which pages fail LCP, CLS, or INP thresholds. 2. Optimize images — Compress images, use modern formats like WebP, and add explicit width and height attributes to reduce layout shift (CLS). 3. Reduce render-blocking resources — Defer non-critical JavaScript and CSS to improve Largest Contentful Paint (LCP). 4. Improve server response time — Use a reliable hosting provider and enable caching or a content delivery network (CDN). 5. Ensure mobile-friendliness — Test pages with Google's Mobile-Friendly Test tool and fix any viewport or tap-target issues. 6. Secure your site with HTTPS — All pages should be served over HTTPS. Mixed-content warnings negatively affect page experience scores. 7. Remove intrusive interstitials — Avoid pop-ups that cover the main content immediately on page load, especially on mobile. 8. Improve internal linking and content relevance — Keeping visitors engaged longer signals quality to search engines. Use OTTO's Content and Topical Authority recommendations alongside UX improvements. 💡 How OTTO's Other Pillars Support UX Indirectly Even while the UX Signal pillar is being rebuilt, other OTTO pillars contribute to a better user experience: - Content Quality — Well-structured, relevant content keeps users on your pages longer, reducing bounce rate. - Topical Architecture — Clear site structure and internal linking help visitors find related content easily, improving dwell time. - Authority Score — A strong, trustworthy domain profile reinforces credibility signals that align with user trust. - Technical SEO — Fixing crawlability and indexation issues ensures users land on properly functioning pages. Addressing OTTO's recommendations across all pillars creates a cumulative improvement in how both users and search engines perceive your site. 🚀 What's Coming Next for OTTO UX Signals The Search Atlas engineering team has several improvements in progress: - Replacing the current UX Signal score with real page experience data, including Core Web Vitals measurements - Expanding the pillar architecture so UX signals are tracked with greater granularity alongside content and authority metrics - Introducing clearer, task-level recommendations tied directly to page experience failures These updates will give you a much clearer picture of which specific pages need attention and why. Watch for release notes in the platform for announcements. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔄 Understanding OTTO's Weekly Analysis and Recommendation Refresh

🤔 Why Did My Optimizations Disappear? If you noticed that some of your AI-generated recommendations from last week are no longer visible — or that previously completed optimizations appear to need redoing — this is expected behavior. OTTO runs a weekly analysis cycle that refreshes its recommendations based on the latest data from your site, search engine signals, and competitive landscape. This refresh ensures that OTTO's suggestions always reflect current SEO conditions rather than outdated information. However, it also means that recommendations generated in one cycle may be replaced or updated in the next. ⚙️ How the Weekly Analysis Cycle Works Each week, OTTO automatically re-crawls your connected site and re-evaluates all SEO factors. Here is what happens during each cycle: 1. OTTO scans your site for new technical issues, content gaps, and on-page opportunities. 2. It compares your current performance against updated keyword data and competitor signals. 3. A fresh set of recommendations is generated to reflect these findings. 4. Recommendations that were resolved or no longer relevant may be removed; new ones may appear. Because the analysis starts fresh each week, recommendations that were generated but not yet applied may no longer appear in the new cycle if OTTO determines they are no longer the highest priority or if the underlying data has changed. ✅ The Difference Between Applied and Unapplied Changes This is the most important distinction to understand: - Applied changes — most optimizations are served through the OTTO pixel script at page load, so if the pixel is removed or the OTTO project is deleted, those pixel-served changes will stop showing on the site. Changes that were written directly into the site's CMS (for example through the WordPress plugin) can remain. - Unapplied recommendations — suggestions that were generated but not yet acted on may be refreshed, updated, or replaced during the next weekly cycle. If you saw optimizations disappear that you believed were already applied, it is worth verifying directly on your site or CMS that those changes were successfully saved and published. 🛠️ How to Access OTTO and Review Current Recommendations To review your latest OTTO recommendations and take action before the next weekly refresh: 1. In the left sidebar, click OTTO SEO, then open All Sites (SEO Automation). 2. Select the site you want to manage. 3. Review your current recommendations across all categories — Content, Authority, and Technical. 4. Apply any high-priority changes promptly to ensure they are deployed before the next analysis cycle runs. 💡 Best Practices to Avoid Losing Progress Follow these habits to stay on top of OTTO's weekly refresh without losing work: - Act on recommendations within the same week they are generated to ensure they are applied before the cycle resets. - Prioritize high-impact suggestions first. If you cannot action everything in one session, focus on the items flagged as critical or high priority. - Confirm each change is fully applied before closing your session. Look for confirmation indicators within the OTTO interface that a recommendation has been accepted and deployed. - Check in at least once per week to stay current with the latest analysis results and catch any new issues as they arise. 📊 Why Weekly Regeneration Is a Feature, Not a Bug SEO is not a one-time task — search engine algorithms, competitor strategies, and your own site content change constantly. OTTO's weekly regeneration cycle is designed to keep your optimization roadmap accurate, relevant, and prioritized at all times. Older, lower-impact suggestions are replaced with fresher, higher-value opportunities so that every recommendation you see is worth acting on. Think of each weekly cycle as receiving a new, up-to-date SEO audit rather than a static list that grows stale over time. 💬 Still Have Questions? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🚀 Understanding OTTO Deploy All Batch Deployment

🔍 Overview The Deploy All button in OTTO SEO is designed to apply multiple SEO optimizations across your site in a single action. However, customers sometimes expect it to resolve every detected issue in one click. This article explains how batch deployment works and why certain issues may remain after running it. ⚙️ How Deploy All Works When you click Deploy All, OTTO groups eligible optimizations and applies them to your site automatically. Not every detected issue will be resolved by a single Deploy All action — some issues are intentionally held back and require individual attention before they can be deployed. You can access OTTO by navigating to OTTO SEO → All Sites (SEO Automation) in the left sidebar of the platform. ⚠️ Why Some Issues Are Not Fixed by Deploy All Certain SEO issues cannot be batch-deployed and will remain in your issue list after running Deploy All. This is expected behavior. Those issues need to be reviewed and actioned individually within the OTTO dashboard before they can be applied to your site. 📋 What to Do When Issues Remain After Deploy All 1. After running Deploy All, check the OTTO dashboard for any issues that were not automatically deployed. 2. Review each remaining issue individually and follow the on-screen prompts to complete or approve the recommended fix. 3. Deploy each confirmed fix once you have reviewed it. 💡 Tips - Run Deploy All first to handle eligible optimizations in bulk, then focus on the smaller set of issues that require individual review. - If you are unsure why a specific issue was not deployed by Deploy All, our support team can review your account and clarify the behavior for that issue type. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔄 OTTO Weekly Analysis: Managing Recurring Recommendations

🤔 Why Did My Optimizations Disappear? If you applied AI-generated recommendations last week and noticed they were replaced or removed this week, OTTO's weekly analysis schedule is the cause. This is expected behaviour — not a bug or data loss. Each week, OTTO runs a fresh analysis of your site and regenerates its recommendations based on the latest crawl data, keyword performance, and ranking signals. This means the previous recommendation set is replaced with a new one. Any changes you applied from the old set remain live on your site, but they will no longer appear in OTTO's recommendation list because OTTO has moved on to its next analysis cycle. 📅 How the Weekly Analysis Schedule Works OTTO is designed to continuously monitor your site and surface the most relevant optimisations at any given time. Here is what happens during each weekly cycle: 1. OTTO crawls your connected site and collects fresh on-page, technical, and content data. 2. A new set of recommendations is generated based on the updated data. 3. The previous recommendation list is replaced with the new one. 4. Any optimisations you had already applied are retained on your site but are no longer shown as pending recommendations. This cycle ensures you are always working from the most current SEO intelligence rather than acting on outdated suggestions. ✅ What Happens to Changes You Already Applied It is important to understand that OTTO does not undo or remove changes you have already deployed to your site. When you accept and apply a recommendation, that change goes live and stays live. The disappearance you noticed is the recommendation card being removed from the OTTO interface — not the underlying SEO change being reversed. If you believe a live change was actually reverted on your site rather than simply removed from the recommendation list, check your CMS or page editor directly to confirm the content is still in place. If a change was genuinely undone, this would indicate a separate issue unrelated to the weekly schedule. 🔁 Why Recommendations Are Sometimes Regenerated for the Same Pages You may see OTTO suggest optimisations for pages it has recommended before. This can happen when: - A previously applied change was later edited or removed outside of OTTO. - New ranking data or competitor activity has shifted what is considered optimal for that page. - A technical issue such as a broken link or missing meta tag has reappeared after a site update. - OTTO has detected a new opportunity on the same page that was not present in the prior cycle. In these cases, acting on the new recommendation is the right course of action, even if the page looks familiar. ⚙️ Questions About the Analysis Schedule If the weekly regeneration cycle is causing confusion or you have questions about how OTTO's schedule applies to your specific project, our support team can look into the details of your account. When reaching out, please have the following ready: - The name of the project or site connected to OTTO. - The approximate date you last saw a recommendation set that has since been replaced. - A description of any specific recommendation or change you are trying to track down. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🚀 Deploy More Than 100 OTTO Improvements in Bulk

🔍 Overview When using OTTO SEO to deploy improvements across your site, you may notice that the platform applies a limit of 100 improvements per bulk deployment action. This is a deliberate safeguard designed to protect site stability, prevent server overload, and ensure each batch of changes is applied cleanly before the next set begins. This article explains why the limit exists, how to work within it effectively, and what to expect as the feature continues to evolve. ⚙️ Why the 100-Improvement Limit Exists Deploying large numbers of on-page changes simultaneously can put significant strain on both your website's server and Search Atlas's processing infrastructure. The 100-improvement cap helps to: - Prevent database and server overload — large uncapped batches can cause performance issues that affect your site and other users. - Ensure deployment accuracy — smaller batches allow the system to verify each change was applied correctly before continuing. - Maintain platform stability — our engineering team is actively working on scaling bulk operations safely (see the roadmap section below). 📋 How to Deploy More Than 100 Improvements Even with the current limit, you can still deploy hundreds or thousands of improvements — you just need to do it in sequential batches. Follow these steps: 1. Open OTTO SEO from your Search Atlas dashboard and navigate to the site you want to optimise. 2. Filter or sort your improvements by category, priority, or page to identify the first group you want to deploy. 3. Select up to 100 improvements from the list using the bulk-select checkboxes. 4. Click Deploy and wait for the confirmation that the batch has been successfully applied. 5. Repeat the process for the next group of improvements. There is no limit on how many batches you can run — only on the size of each individual batch. Tip: Start with your highest-priority improvements first — such as missing title tags, meta descriptions, or critical schema fixes — so your most impactful changes go live quickly while you work through the remaining batches. 💡 Best Practices for Large-Scale Deployments - Group improvements by type or page template — this makes it easier to review results and roll back a specific category if needed. - Allow time between batches — giving Search Atlas a few minutes to process and verify each batch before starting the next one helps ensure accuracy. - Monitor your site after each batch — check that pages are rendering correctly and that no unintended changes have occurred before continuing. - Use filters inside OTTO — filtering by improvement status (e.g. Suggested vs Deployed) helps you keep track of where you are across multiple sessions. 🛠️ What We're Building: Roadmap Update Our engineering team is actively working on improvements to bulk deployment capabilities. Planned work includes: - Expanded bulk deployment limits — we are developing the infrastructure to safely support larger batches without risking performance issues. - Bulk write-from-spreadsheet — an upcoming feature will allow you to upload improvements via spreadsheet with enforced validation, making large-scale deployments faster and more structured. - Enhanced OTTO Agent bulk actions — the OTTO Agent will gain the ability to suggest and deploy fixes in bulk with greater automation and control. These features are at various stages of development and will be announced in the platform when they become available. ❓ Frequently Asked Questions - Can I run multiple batches in the same session? Yes. You can deploy as many batches of up to 100 improvements as needed within a single session. There is no daily or session cap on the number of batches. - Will my progress be saved between sessions? Yes. Any improvements you have already deployed are marked as such in OTTO, so you can pick up where you left off in a future session. - Can I undo a batch after deploying it? OTTO SEO includes rollback functionality for deployed changes. Check the deployment history within your OTTO dashboard to revert specific batches if needed. - Is the 100-limit the same for all plan types? Currently, yes. As our bulk deployment infrastructure scales, higher limits may become available on certain plans. Watch for platform announcements. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

📝 Content Length and OG Descriptions Explained

📖 Overview When optimizing pages in Search Atlas, you will come across settings for content length and OG (Open Graph) descriptions. These settings help search engines and social platforms understand your page. This article explains what each one means and shows you how to add AI-generated descriptions in just a few clicks. 📏 What Content Length Means Content length refers to how much written text a page contains. Search Atlas groups pages into ranges so you can quickly spot pages that may need more detail. A page marked as short typically has a low word count, which often means it may not fully cover a topic or give search engines enough context to rank it well. - Short: A low word count. These pages may benefit from more detail, examples, or supporting information. - Medium: A moderate amount of content that covers the core topic. - Long: In-depth content that thoroughly explores a subject. There is no single correct length for every page. The right amount depends on the topic, the intent behind the search, and how much your competitors cover. Product or service pages such as those for Galserv should include enough content to clearly describe the offering, answer common customer questions, and support your target keywords. As a general guide, aim to move short pages toward a medium or long range when the topic has room for genuinely useful detail. Focus on quality and relevance rather than adding filler text simply to raise the word count. If the content length range shown in Search Atlas does not appear to match the actual word count on your page, refresh the page's data before acting on it. A previously reported discrepancy between the displayed word count and the content length category has been resolved. 🌐 What an OG Description Is An OG (Open Graph) description is a short summary of your page that appears when the page is shared on social platforms such as Facebook, LinkedIn, or messaging apps. It works alongside the OG title and OG image to create the preview card people see in their feed. While the OG description does not directly influence search rankings, a clear and compelling summary encourages more clicks when your content is shared. Keep it concise, accurate, and focused on the value the page offers. A good OG description is usually one to two sentences and reflects what the page is actually about. 🤖 How to Add AI-Generated Descriptions Search Atlas can generate descriptions for you, saving time and helping you maintain a consistent tone across your pages. Follow these steps: 1. Open the page you want to optimize within Search Atlas. 2. Locate the metadata section that contains the meta description or OG description field. 3. Click the AI generate option next to the field. 4. Review the suggested text. The AI uses your existing page content to create a relevant summary. 5. Edit the wording if needed so it matches your brand voice and includes your main keyword naturally. 6. Save your changes to apply the new description. You can regenerate a description as many times as you like until you are happy with the result. Always review AI suggestions before saving to make sure they accurately represent the page. If your site is built with a page builder such as Divi or Elementor, review the generated OG description especially carefully. An earlier issue where the OG description could auto-fill with raw page-builder shortcode has been fixed, but confirming the preview text is clean before you save avoids publishing unwanted markup. 💡 Best Practices - Match length to intent: Add more content only when it genuinely helps the reader understand the topic. - Keep descriptions unique: Give each page its own OG and meta description rather than reusing the same text. - Front-load key information: Place the most important details at the start of your descriptions. - Include relevant keywords: Work your target terms in naturally without overstuffing. - Review AI output: Treat generated text as a strong starting point, then refine it. Additional Notes Short ~300–600w for FAQs/local pages; Optimized (Medium) ~800–1,200w for blog/service pages; Long-Form ~1,500–2,500+w for pillar/competitive topics. For local keywords use Short/Optimized; for service explainers/comparisons consider longer form.

🤖 OTTO Deployment, Lucky Button & Dynamic Indexing

🤖 What Is OTTO and How Does Deployment Work? OTTO is Search Atlas's AI-powered SEO automation engine. It audits your site, identifies technical SEO opportunities, and generates fixes — including meta descriptions, title tags, heading structures, schema markup, and more — directly from the platform. OTTO follows a review-then-deploy workflow by default. This means every suggested fix is presented to you for review before it goes live on your site. You stay in control at every step. ✅ How to Review and Deploy OTTO Recommendations 1. Go to OTTO SEO in the left sidebar, then open SEO Automation (or navigate to /seo-automation-v3). 2. Connect your site to OTTO if you haven't already, and complete the initial site audit. 3. Browse the generated recommendations grouped by category (e.g., Meta Tags, Headings, Schema). 4. Review each suggestion — you can edit the AI-generated content before deploying. 5. Select individual fixes or use bulk selection to deploy multiple items at once. 6. Navigate to Local → My Tasks (My Tasks) and click Deploy all changes to push approved changes live to your site. Changes are only applied to your site after you explicitly approve and deploy them. OTTO will never publish updates without your confirmation unless you use the I'm Feeling Lucky feature described below. 🍀 How Does the "I'm Feeling Lucky" Button Work? The I'm Feeling Lucky button is an optional one-click deployment shortcut designed for users who want to move fast and trust OTTO's recommendations without reviewing each item individually. Here is exactly what it does: - Skips the manual review step — OTTO automatically selects and deploys all high-confidence recommendations in a single action. - Applies changes immediately — fixes go live on your site as soon as you confirm the prompt. - Covers all eligible fix types — meta descriptions, title tags, heading tags, and other supported elements are all included in the batch deployment. Important: Before using I'm Feeling Lucky, we recommend completing at least one manual review cycle so you are familiar with the types of changes OTTO makes on your site. You can always roll back individual deployed items from the OTTO dashboard if needed. 📋 Can OTTO Generate Technical SEO Elements Automatically? Yes. OTTO can automatically generate a wide range of on-page and technical SEO elements, including: - Meta descriptions — unique, keyword-aligned descriptions for every page. - Title tags — optimised titles based on your target keywords and page content. - Heading structures (H1–H6) — logical heading hierarchies to improve readability and crawlability. - Schema markup — structured data to enhance search result appearance. - Canonical tags, alt text, and more — depending on your connected site and plan. All generated elements are AI-drafted and editable. You have full control to modify any suggestion before it is deployed, whether you deploy items one at a time or in bulk. 🔍 Where Is Dynamic Indexing and Can I See It? Dynamic Indexing is a feature within OTTO that helps search engines discover and index your pages faster by managing crawl signals and sitemap updates automatically. Currently, Dynamic Indexing status and activity are visible under Authority → Indexer (URL Indexer) in the left sidebar. From this view you can: - See which pages have been submitted for indexing and when. - Monitor indexing request status (submitted, indexed, pending). - Identify pages that may need attention due to crawl or indexing issues. Note: If the Dynamic Indexing tab is not visible in your dashboard, make sure your OTTO project is fully set up along with any connected indexing services. 💡 Quick Reference: OTTO Deployment Modes - Manual review mode (default): You review each recommendation and click Deploy when ready. Full control, no surprises. - I'm Feeling Lucky (bulk auto-deploy): OTTO deploys all high-confidence fixes in one action. Best for experienced users who trust the AI output. - Dynamic Indexing: Runs automatically in the background once enabled; status is visible in your OTTO dashboard. 🛠️ Troubleshooting Common Issues - Recommendations not appearing: Make sure your site audit has completed. Large sites can take a few minutes to fully process. - Deploy button greyed out: Check that OTTO is fully connected to your site and that your plan includes deployment for the selected fix type. - Dynamic Indexing tab not visible: Make sure your OTTO project is fully set up along with any connected indexing services. - Changes not reflecting on site: Allow a few minutes after deployment. Some changes depend on your CMS cache clearing — try purging your site cache. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team. Additional Notes Generation vs. Deployment distinction: Generation analyzes pages and produces suggestions automatically once OTTO is connected — no live changes at this stage. Deployment is a separate step where you approve and push changes. Also explicitly lists: H1, H2/H3 headings, image alt text as generated elements.

🤖 What OTTO SEO Does (and Does Not) Do

🎯 What Is OTTO SEO? OTTO SEO is Search Atlas's AI writing assistant designed to help you organize research and draft content faster. You can access it from the left sidebar by clicking OTTO SEO → SEO Automation (URL: /seo-automation-v3). OTTO is built for content creation workflows — it is not a technical SEO auditor, a local SEO optimizer, or a platform integration hub. Understanding this distinction helps you use the right Search Atlas tool for the right job. ✅ What OTTO SEO Actually Does - Content research organization: Gathers and structures topic research so you can write with context. - AI-assisted drafting: Generates article drafts based on your target keywords and outline inputs. - On-page content suggestions: Recommends headings, subheadings, and keyword placement within the draft. - Content briefs: Produces structured briefs you can hand to writers or use yourself. 🚫 What OTTO SEO Does Not Do Several capabilities are not part of OTTO, even though they exist elsewhere in the Search Atlas platform: - No GEO-friendly content analysis: OTTO does not evaluate whether your content is optimized for a specific geographic location or local search intent. - No Google Business Profile (GBP) integration: OTTO does not connect to, read from, or push data to Google Business Profile. - No Google Search Console (GSC) integration within OTTO: GSC data is available in other Search Atlas tools, but OTTO itself does not surface or act on GSC signals. - No local SEO heatmaps: Rank tracking by geographic grid is a separate Search Atlas feature, not part of OTTO. - No citation building: Local citation management is handled by dedicated Search Atlas tools, not OTTO. - No affiliate link management: OTTO does not insert, track, or optimize affiliate links. 🗺️ Where Local and GEO SEO Features Live in Search Atlas Search Atlas does offer robust local SEO capabilities — they are just separate tools from OTTO. If geographic optimization is your goal, explore these platform areas: - Local SEO Heatmaps: Visualize your rankings across a geographic grid to see where you rank locally versus competitors. - Google Business Profile Tools: Manage and optimize your GBP listing directly inside Search Atlas. - Citation Builder: Build and audit local citations across directories to strengthen local authority. - Rank Tracker (Local): Track keyword rankings filtered by city, region, or ZIP code. These tools work together to support a local SEO strategy, but they operate independently of OTTO's content drafting workflow. 🔍 How OTTO Compares to Competitor Tools Customers sometimes ask how OTTO stacks up against Yoast, RankMath, SurferSEO, and affiliate link platforms. Here is an honest, side-by-side comparison: - Yoast SEO / RankMath: These are WordPress plugins that score on-page SEO in real time as you write, including readability and schema markup. OTTO focuses on pre-draft research and content generation rather than live in-editor scoring, though OTTO can also deploy JSON-LD schema markup (such as FAQPage, Article, Product, Recipe, Organization, and Person) on a per-page basis after the customer approves the recommendation, or automatically if OTTO auto-deploy is enabled. - SurferSEO: Surfer analyzes top-ranking pages and scores your content against them using NLP-based content guidelines. OTTO provides AI drafts and briefs but does not offer a real-time content score benchmarked against SERP competitors in the same way. - Affiliate link tools (e.g., Lasso, ThirstyAffiliates): These tools manage, cloak, and track affiliate links inside content. OTTO has no affiliate link functionality whatsoever. - GEO / local SEO tools (e.g., BrightLocal, Whitespark): These platforms specialize in citation audits, GBP management, and local rank tracking. OTTO does not replicate these features; Search Atlas's dedicated local SEO tools are the appropriate comparison point. OTTO's strength is speed and structure in content creation. It is not a direct replacement for real-time scoring plugins, local SEO platforms, or link management systems. ⚡ Quick Reference: OTTO vs. Search Atlas Platform - AI content drafting → OTTO ✅ - Content research briefs → OTTO ✅ - GEO-friendly content scoring → Not available in OTTO ❌ - Google Business Profile management → Search Atlas Local Tools ✅ | OTTO ❌ - Local rank heatmaps → Search Atlas Local Tools ✅ | OTTO ❌ - Citation building → Search Atlas Local Tools ✅ | OTTO ❌ - Affiliate link management → Not available in Search Atlas ❌ 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Bulk Schema Deployment With OTTO Dashboard

🗺️ Getting to the OTTO Dashboard All schema generation and deployment tools live inside the OTTO SEO workspace. To get there: 1. Log in to your Search Atlas account. 2. In the left sidebar, navigate to OTTO SEO → All Sites (SEO Automation). 3. You will land on the OTTO SEO dashboard. Make sure a website project is connected before proceeding. If no project is listed, use the project selector at the top of the dashboard to attach or create one. 📋 Understanding the Schema Section Inside the OTTO dashboard, schema management is handled through the schema section. This area displays pages on your connected website that OTTO has crawled, along with their current schema status. Use the available search and filter options to narrow pages by URL, page type, or status before running a bulk action. ⚡ Generating Page-Level Schemas in Bulk Follow these steps to generate schemas for multiple pages at once: 1. Open the schema section inside the OTTO dashboard. 2. Filter or browse the page list to find the pages you want to target. 3. Use the checkboxes to select all visible pages or specific individual pages. 4. Once pages are selected, look for the bulk actions options that become available. 5. Choose the option to generate schemas. OTTO will analyse each selected page and produce the most appropriate schema type — such as Article, Product, FAQ, or LocalBusiness — based on the page content. 6. Review the generated schemas for each page before proceeding to deployment. 🚀 Deploying Schemas in Bulk After generation, deploy the schemas so they go live on your website: 1. Select the pages whose schemas you want to deploy — you can reuse the same selection or filter to pages with schemas ready to deploy. 2. Use the bulk actions options to deploy the selected schemas. 3. OTTO will push the structured data to your site and update the status for each page once deployment is complete. Note: Deployment requires that the OTTO tracking script is properly installed on your website. If you encounter issues connecting your project or deploying schemas, please reach out to our support team for assistance. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚡ How to Access Your Dead Links List in OTTO SEO Overview

🧭 What Is the Dead Links List? The dead links list is a report generated inside your OTTO SEO Overview (OTTO SEO) project that identifies broken internal and external links across your site. If your project is showing a count like 157 dead links, this means OTTO has crawled your site and flagged that many URLs returning errors (such as 404s) or leading to unreachable destinations. Fixing these links is important for both user experience and search engine crawlability. 📍 Where to Find the Dead Links Report Follow these steps to locate your dead links list: 1. Log in to your Search Atlas dashboard. 2. Navigate to your OTTO SEO Overview project (OTTO SEO). 3. Select the specific project or domain you want to review. 4. Open the Page Insights section of your project. 5. Look for the Dead Links category or filter within Page Insights — this will display the list of broken internal and external links flagged during the crawl, along with their total count. 🔍 Viewing the Full URL List Once you are inside the Dead Links section of Page Insights, you will see each flagged URL listed individually. You can review which links across your site have been identified as broken and take action accordingly. Use any available URL filter to narrow down results by specific pages or link types if your count is large. 🛠️ What to Do After Reviewing the List Once you have access to the full dead links list, we recommend the following workflow: 1. Review internal links first, since these are typically the fastest to fix and most impactful for crawl efficiency. 2. Update or remove broken internal links pointing to deleted or moved pages. 3. For external dead links, either update the link to a live source or remove it if no longer relevant. 4. Re-crawl the project after making changes to confirm the dead links count has decreased. 💡 Tips for Managing Large Dead Link Counts If your count is high, such as 157 links, prioritize based on page authority and traffic. Fixing dead links on high-traffic or high-converting pages first will have the most immediate impact on both user experience and SEO performance. 📞 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with our support team.

🛠️ How to Roll Back OTTO H2 Heading Overrides

OTTO SEO can automatically deploy heading changes to help optimize your pages. Sometimes an updated H2 heading may not match what you want, such as an OTTO version replacing your intended text like Background Checks on a Services page. The good news is that every OTTO change is reversible. This article shows you how to locate the heading override and roll it back so your original heading is restored. ​🔍 How OTTO Heading Overrides Work ​When OTTO deploys optimizations, it applies changes through the OTTO Pixel installed on your site. These changes are not permanent edits to your source code. Instead, OTTO injects them on top of your existing content. This means you can always deactivate or revert a change without touching your website's underlying files. Heading overrides usually appear under OTTO's on-page optimization or content suggestions, where OTTO proposes and deploys an alternative H2 for a specific page. 🧭 Step 1: Open the Affected Page in OTTO​ 1. Log in to your Search Atlas dashboard and open the OTTO SEO project connected to your site. 2. Go to the Deployed or Action Items view. 3. Use the search or filter option to find the page you want to fix, such as your Services page.​ Filtering by page URL is the fastest way to isolate the exact heading change you need to review. ​ 📋 Step 2: Locate the Heading Change​ 1. Open the list of deployed items for that page. 2. Look for the category related to headings, H2, or on-page content. 3. Review the item to confirm it shows the override, for example OTTO's text in place of Background Checks.​ Each item displays the original value and the value OTTO deployed, so you can confirm you have the correct change before rolling it back. ​ ↩️ Step 3: Roll Back or Edit the Override​ You have two ways to fix the heading, depending on your goal: - Revert to the original: Toggle the deployed item off or select the revert option. OTTO will stop injecting its version, and your original H2 will display again. - Set your own text: If OTTO allows editing, replace the deployed heading with your preferred wording, such as Background Checks, then save and redeploy. Reverting removes OTTO's change entirely, while editing lets you keep an optimized heading that uses the exact text you want. ​ ✅ Step 4: Confirm the Change Is Live​ 1. Wait a few minutes for the update to propagate through the OTTO Pixel. 2. Open your Services page in a new browser tab or a private window to avoid cached content. 3. Confirm the H2 now shows your intended heading.​ If the old heading still appears, clear your browser cache or any site or CDN cache, then check again. Note: OTTO's deployment log may report a successful deployment before the change is visible on the live page. If the log shows success but the heading has not updated yet, perform a full cache purge and allow a few additional minutes for the OTTO Pixel to propagate the change. ​ 🚫 How to Prevent Unwanted Heading Overrides​ To reduce future surprises, consider these best practices: - Review before deploying: Use OTTO's review step to approve heading suggestions instead of auto-deploying them. - Protect key pages: Manually check high-priority pages, like Services or Contact, after each OTTO deployment. - Keep a record: Note any custom headings you have set so you can quickly spot unexpected changes.​ 💡 Important Notes​ - Rolling back an OTTO heading affects only the heading you select, not other optimizations on the page. - Changes made through OTTO do not alter your website's source code, so reverting is always safe. - If your site uses caching, allow a short time for updates to appear. - If your site routes traffic through Cloudflare DNS and you notice that an OTTO heading change reverts on its own shortly after being applied, this was a previously identified and resolved issue. If the behaviour recurs on your site, contact our support team so they can investigate further.

🏷️ OTTO Schema Markup: What Null Fields Mean and How to Fix Them

🤔 What does a null field in schema markup mean? When OTTO detects existing schema markup on your site (shown as FOUND), it reads the current values. If a field shows null, it means the field exists in your schema but has no value assigned to it. Null fields are normal and expected in FOUND schemas — they highlight areas where data is missing. A common source of null fields is markup imported from a CMS (such as WordPress), which can leave required fields empty or inject malformed values. OTTO now sanitizes FOUND content before storing it, so newly imported schemas are cleaned automatically. If you still see null fields left over from an earlier import, regenerating the schema (below) refreshes them. 🔧 How to fix null fields 1. In OTTO, find the page with the null field warning 2. Click Regenerate Schema for that page 3. OTTO will attempt to auto-populate the field based on your site content and Brand Vault data 4. Review the regenerated schema and deploy it 🚫 What if the field is not applicable to my business? If your business genuinely does not use a field, you have two options: - Regenerate — OTTO will omit fields it cannot populate from your content - Edit manually — click the field in the schema editor and remove it or set an appropriate value Schema markup that fails validation (for example, a missing required field) is not deployed unless validation was explicitly suppressed for it. You can also add custom fields in the schema editor — they are preserved through the edit, save, and deploy cycle and will not be stripped or trigger warnings. 📋 FOUND vs. GENERATED schemas - FOUND — schema OTTO detected already on your page. Null fields here reflect gaps in your existing markup. - GENERATED — schema OTTO created from scratch. These are fully populated before deployment. 👀 Seeing a FOUND schema or null fields you didn't expect? A few past issues could cause a schema to appear as FOUND when it shouldn't — all are now resolved: - Stale FOUND schemas — a page could still show "schema detected" after its markup was removed or never actually parsed. OTTO now clears these stale FOUND records on the next crawl sync, so they no longer report null fields for markup that isn't there. - OTTO-deployed FAQ schema shown as FOUND — FAQ schema that OTTO itself deployed was sometimes mislabeled as FOUND instead of SUGGESTED. This has been fixed, so OTTO-managed schema is now categorized correctly. - Internal fields in the preview — internal display fields once appeared in the JSON-LD preview panel for older FOUND schemas; these are now stripped from the preview. If a page still shows leftover null fields from before these fixes, click Regenerate Schema to refresh it.

📤 Bulk Export OTTO On-Page SEO Data

📋 Overview OTTO SEO includes a built-in Export Fixes feature that lets you bulk export all on-page SEO data in one click. The export is delivered as a Google Sheets file, giving you a clean, structured spreadsheet you can use to migrate data into Rank Math, share with your team, or keep as a backup. You do not need to copy and paste individual fields manually. 📦 What Gets Exported The Export Fixes feature covers every major on-page SEO field that OTTO manages, including: - Meta titles — optimised page titles for every URL - Meta descriptions — unique descriptions for every URL - Headings — H1 and other heading-level recommendations - Canonical tags — canonical URL values per page - Open Graph tags — OG title, OG description, and OG image data - Twitter/X Card tags — Twitter title and description fields - Alt text fixes — recommended alt attributes for images - Link fixes — internal link recommendations and anchor text Each row in the exported sheet corresponds to a single URL, so it is straightforward to match and import fields into Rank Math or any other SEO plugin. 🗺️ Where to Find the Export Fixes Button 1. In the left sidebar, click OTTO SEO → All Sites (SEO Automation) to open the OTTO SEO dashboard. 2. Make sure you are viewing the correct site. If you manage multiple sites, use the site selector at the top of the page to switch to the right domain. 3. Look for the Export Fixes button. It appears near the top-right area of the OTTO SEO dashboard, alongside other action controls. 4. Click Export Fixes. OTTO will compile all on-page fix data for your site. 5. A Google Sheets file will be generated and a link will be sent to your account email address. Open the link to access your full export. Tip: If you do not see the email within a few minutes, check your spam or promotions folder. The subject line will reference your site domain and the OTTO export. 📥 How to Use the Export with Rank Math Once you have the Google Sheets file, follow these steps to transfer the data into Rank Math: 1. Open the exported Google Sheet and review the column headers to identify the fields you need — for example, Meta Title and Meta Description. 2. In Rank Math, navigate to Rank Math → Status and Tools → Import and Export. 3. Use Rank Math's CSV import option or copy the values directly into the relevant fields for each post or page. Because the OTTO export is organised by URL, matching records is straightforward. 4. For large sites, consider using a spreadsheet formula to reformat the data into Rank Math's expected import column structure before uploading. Note: Search Atlas does not control the Rank Math import interface. If you encounter issues on the Rank Math side, refer to Rank Math's official documentation for CSV import guidance. ⚠️ Common Questions - Does the export include every page on my site? Yes. OTTO exports fixes for all URLs it has analysed within your connected site. Pages that have not yet been crawled may not appear. - Can I re-export after making changes? Yes. You can click Export Fixes at any time to generate a fresh export reflecting your latest OTTO recommendations and applied fixes. - Is the export a live Google Sheet or a snapshot? The export is a snapshot of your data at the moment of export. It does not update automatically if OTTO generates new recommendations later. - What if OTTO has not finished analysing my site? Wait for the OTTO scan to complete before exporting to ensure you receive the full dataset. You can monitor scan progress from the OTTO SEO dashboard. 💬 Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

✏️ Change or Remove a Deployed Page H1 Heading

⚠️ Important: The Section Is Now Called OTTO SEO The platform section previously referred to as AI SEO is now labelled OTTO SEO in the left sidebar. There is no separate Deployments tab. All deployed on-page fixes — including H1 heading changes — are managed directly inside OTTO SEO. Any instructions previously referencing AI SEO → Deployments are outdated; follow the steps below instead. 📍 Step 1 — Open Your Site 1. Click OTTO SEO in the left sidebar. 2. Click All Sites. Full path: Left sidebar → OTTO SEO → All Sites. 3. Find your domain in the list and click it to open the site dashboard. 🔍 Step 2 — Locate the Deployed Heading Fix Once inside the site dashboard you have two paths to find the deployed H1 fix: - Via Overview: Navigate to Left sidebar → OTTO SEO → Overview. Your site's active deployed fixes are listed here. Scroll through the on-page optimisations to find the heading fix associated with your target page (e.g. /aged-care/). - Via Page Explorer: Navigate to Left sidebar → OTTO SEO → Site Audit → Page Explorer. Search for or select the specific page URL. Open the page record and look inside the Headings section to find the deployed H1 fix. ✏️ Step 3 — Edit the H1 Heading Text To replace the deployed H1 with a different value: 1. Locate the heading fix for your target page using either path in Step 2. 2. Click the edit (pencil) icon next to the deployed heading value. 3. Type the new H1 text you want to appear on the page. 4. Save the change. The updated heading will push to your connected site automatically. 🗑️ Step 4 — Remove the H1 Heading Fix Entirely To revert the page to its original heading and remove the OTTO SEO-deployed H1: 1. Locate the heading fix using either path in Step 2. 2. Click the Undeploy or Remove option next to the fix. This may appear as a toggle, a trash icon, or a contextual menu depending on the view you are in. 3. Confirm the action. The page will revert to its original H1 heading. 📋 Alternative — Check the Tasks View If the heading change was submitted as an on-page recommendation rather than a direct deployment, it may appear as a pending task rather than a deployed fix. Navigate to Left sidebar → OTTO SEO → Tasks and filter by the relevant URL or fix type. You can edit or discard the heading recommendation directly from that list. 🔄 Changes Not Reflecting on Your Live Site? Allow a few minutes after saving for the change to propagate to your live page. If the H1 still shows the old value after 10–15 minutes, check the following: - Hard-refresh your browser or view the page in an incognito/private window to rule out a local cache issue. - Confirm the fix status shows Deployed (for an edited heading) or Undeployed (for a removed heading) in the OTTO SEO dashboard. - If your site uses Cloudflare, purge the Cloudflare cache for that specific URL. - For WordPress sites, confirm the OTTO SEO plugin is active and the site is connected correctly via Left sidebar → OTTO SEO → Installation Guide. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🚀 Activate OTTO Instant Indexing and Check Subscription Requirements

🎯 What Is OTTO Instant Indexing? OTTO instant indexing automatically submits your fixed pages to Google Search Console (GSC) the moment OTTO deploys improvements to your site. This speeds up Google's crawl and indexing of corrected content, helping your rankings recover faster. Instant indexing requires a service account connection to Google Search Console and is only available on specific Search Atlas subscription tiers. 📋 Subscription Tier Requirements OTTO instant indexing is available exclusively on: - Pro and Enterprise plans (including Agency/Enterprise) - Starter, Essential, and Growth plans do not include instant indexing access If you're on a Starter or Essential plan and need instant indexing, upgrade your subscription through your account settings. ⚙️ How to Activate Instant Indexing Step 1: Verify Your Subscription Tier Log in to Search Atlas and check your current plan in your account settings. If you're on Pro or Enterprise, proceed to step 2. If not, you'll need to upgrade. Step 2: Open your OTTO project Go to OTTO SEO → All Sites (SEO Automation) in the left sidebar, then select your OTTO project. Look for the Instant Indexing or Google Search Console Integration section. Step 3: Connect Your Google Service Account Click the Connect to GSC button. You'll be prompted to authorize Search Atlas to access your Google Search Console account using a service account. A service account email will be generated automatically during this process. This email grants Search Atlas permission to submit URLs to Google on your behalf. Step 4: Confirm Activation Once the service account is connected and active, the instant indexing feature will be enabled. You'll see confirmation that the integration is live. 🔧 Why Isn't My Service Account Email Generating? If you're not seeing a service account email appear during setup, check the following: - Verify subscription tier — the feature only works on Pro and Enterprise plans. Service account generation may be blocked if you're on a lower tier. - Check browser cache — refresh your browser or clear your cache, then try connecting again. - Confirm Google permissions — make sure your Google account has admin access to the Search Console property you're trying to connect. - Try a different browser — occasionally, browser extensions or cached data can interfere with the connection flow. - Wait a few moments — service account creation sometimes takes a few seconds to process. Refresh the page after waiting. ✅ How to Verify Instant Indexing Is Active After activation, you can confirm the feature is working: - The Instant Indexing button in your OTTO project dashboard will be active and clickable (not greyed out). - When OTTO deploys fixes to your site, URLs will automatically be submitted to Google Search Console. - You can manually submit pages by clicking the Submit to Google or Instant Indexing button in your OTTO dashboard. - Check your Google Search Console account to see submitted URLs listed under the URL Inspection tool. ❌ Instant Indexing Button Is Greyed Out If the instant indexing button appears inactive or disabled, one of the following is likely true: - You're on a Starter, Essential, or Growth plan — upgrade to Pro or Enterprise to unlock this feature. - Your GSC service account is not connected — return to the integration settings and complete the Google authorization process. - Your service account connection expired — disconnect and reconnect your Google Search Console account. - Your Google Search Console property is not verified — ensure the website property in GSC is fully verified before connecting. 🔐 Service Account Security and Permissions The service account generated for OTTO instant indexing: - Only has permission to submit URLs to Google Search Console — it cannot modify or delete your site content. - Is specific to your Search Atlas account and the connected GSC property. - Can be revoked at any time by disconnecting the integration in your OTTO settings. - Does not give Search Atlas access to other Google services or your Google Analytics accounts. ❓ Still Not Working? If you've completed all steps and instant indexing is still not activating, or if your service account email is not generating after waiting and refreshing, reach out to our team. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔄 Unlock OTTO V3 Schema Optimization to Boost Your Score

🤔 Why Is Your Optimization Score Stuck? If your optimization score has plateaued around 55/100 and OTTO shows no further suggestions, you are likely using an older version of OTTO that does not include schema optimization. Schema markup is one of the most impactful remaining improvement areas — but it is only available in OTTO V3. Switching to OTTO V3 unlocks a dedicated schema optimization layer that analyses your pages for missing or incomplete structured data and provides actionable fixes. This alone can push your score significantly higher. 🆚 What Is Different in OTTO V3? OTTO V3 is the current generation of Search Atlas's OTTO SEO engine. Compared to earlier versions, V3 introduces: - Schema optimization: Detects missing structured data types (Article, Product, FAQ, BreadcrumbList, LocalBusiness, and more) and generates schema markup ready to deploy. - Expanded on-page analysis: Deeper checks for heading hierarchy, internal linking gaps, and content depth. - Higher score ceiling: Earlier OTTO versions cap actionable suggestions at roughly 50–60 points. V3 surfaces additional improvement categories that raise the potential score toward 100. - Continuous re-scoring: V3 re-evaluates your score automatically as changes are applied, so progress is reflected in real time. 🗺️ How to Migrate to OTTO V3 1. In the left sidebar, click OTTO SEO, then open SEO Automation. This opens the OTTO dashboard at /seo-automation-v3. 2. If you see a banner or prompt indicating that a newer version is available, click Upgrade to OTTO V3 or Switch to V3. 3. If no banner appears, check the top of the OTTO dashboard for a version indicator. Click it and select V3 from the dropdown. 4. OTTO will re-analyse your connected site. This typically takes 1–3 minutes depending on site size. 5. Once the analysis is complete, your updated optimization score and the full list of V3 suggestions — including schema tasks — will appear on the dashboard. Note: Your previously applied optimizations are preserved. Migrating to V3 does not undo any existing changes. 📋 How to Use Schema Optimization in OTTO V3 1. Inside the OTTO V3 dashboard, locate the Schema section in the optimization task list. It may appear under a category labelled Structured Data or Technical SEO. 2. Click on any schema task to expand the details. OTTO will show you which page is affected, which schema type is missing or incomplete, and a preview of the recommended markup. 3. Review the suggested schema. If you are satisfied, click Apply to let OTTO deploy the markup automatically to the relevant page. 4. For pages where you prefer manual control, click Copy Code to copy the generated JSON-LD and paste it into your page's <head> section or your CMS's schema field. 5. After applying schema changes, return to the OTTO dashboard. Your optimization score will update within a few minutes to reflect the improvement. 📈 How Much Can Schema Optimization Improve Your Score? The exact gain depends on how many pages lack structured data and which schema types apply to your content. In typical cases, customers who migrate to V3 and complete schema optimization tasks see score increases of 15–30 points, moving from the 50–60 range into the 75–90+ range. Sites with e-commerce, local business, or FAQ-heavy content tend to see the largest gains because multiple schema types apply across many pages. ⚠️ Troubleshooting Common Issues - Schema section is not visible: Confirm you are viewing the V3 dashboard at /seo-automation-v3. If the URL shows a different path, navigate back by clicking OTTO SEO in the left sidebar and opening SEO Automation. - Score has not updated after applying schema: Allow up to 5 minutes for re-scoring. If the score remains unchanged after that, try refreshing the page. If it still does not update, the schema task may require manual deployment — use the Copy Code option instead. - Apply button is greyed out: OTTO needs site connection permissions to deploy changes automatically. Go to Settings → Site Connections and verify that write access is enabled for your site. - Suggestions list is empty after migrating: If V3 completes its analysis and shows no schema tasks, your site may already have valid structured data in place. In that case, review other V3 task categories such as Internal Linking or Content Depth for additional score improvement opportunities. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🗂️ OTTO Instant Indexing vs. URL Indexer Explained

🔍 Overview Search Atlas offers two separate indexing features: OTTO Instant Indexing and the Authority URL Indexer. These tools work differently and have different setup requirements. This article clarifies exactly what each feature does, what credentials it needs, and where to configure everything — so you never spend time on setup steps that do not apply to your chosen tool. ⚡ What Is OTTO Instant Indexing? OTTO Instant Indexing is the indexing capability built directly into OTTO, Search Atlas's OTTO SEO automation engine. It submits your URLs for indexing using one of two methods: - IndexNow — a protocol supported by Bing, Yandex, and other search engines. Setup requires only a plain-text verification file placed on your site. No Google Cloud Project (GCP) is needed. - Google Search Console (GSC) connection — links your GSC property to OTTO so pages can be submitted through Google's Indexing API via your existing GSC account. No JSON key upload is required inside OTTO. Important: OTTO Instant Indexing does not require you to create a Google Cloud Project, generate a service account, or upload a JSON key anywhere in OTTO. If you have been directed toward those steps for OTTO, that guidance was incorrect. 🌐 What Is the Authority URL Indexer? The URL Indexer is a separate tool in Search Atlas, accessed via the left sidebar → Authority → URL Indexer (URL Indexer). It is designed for bulk URL submission directly through Google's Indexing API using your own Google Cloud credentials. This tool does require a Google Cloud Project setup, including: 1. Creating a GCP project and enabling the Google Indexing API. 2. Generating a service account with the correct permissions. 3. Downloading the JSON key file from GCP. 4. Uploading that JSON key into the Authority URL Indexer tool inside Search Atlas. The JSON key upload field exists only inside the Authority URL Indexer — not inside OTTO. 📋 Side-by-Side Comparison - OTTO Instant Indexing — IndexNow: No GCP required. Add a plain-text file to your site to verify ownership, then activate in OTTO. - OTTO Instant Indexing — GSC connection: No GCP or JSON key required. Connect your Google Search Console account through the standard OAuth flow in OTTO settings. - Authority URL Indexer: GCP required. Create a service account, download a JSON key, and upload it inside the Authority URL Indexer tool. 🛠️ How to Enable OTTO Instant Indexing Follow these steps to activate indexing through OTTO using IndexNow or your GSC connection. 1. Go to OTTO SEO → All Sites (SEO Automation) in the left sidebar (URL: /seo-automation-v3). 2. Select or open the OTTO session for the site you want to configure. 3. Navigate to the Indexing section within your OTTO dashboard. 4. Choose your preferred method: IndexNow or Google Search Console. - For IndexNow: Download the provided verification text file and upload it to the root directory of your website. Once the file is live, return to OTTO and confirm verification. - For GSC: Go to Site Metrics (GSC page) and click Connect GSC Account, then complete the OAuth authorisation flow using the Google account that has access to your GSC property. 5. Once connected, OTTO will begin submitting URLs automatically based on your sitemap and automation settings. 🔑 How to Set Up the Authority URL Indexer (GCP Required) If you specifically want to use the Authority URL Indexer for bulk Google Indexing API submissions, follow these steps: 1. In your Google Cloud Console, create a new project and enable the Web Search Indexing API. 2. Create a service account and assign it the Owner role, then add the service account email as a verified owner in Google Search Console. 3. Generate and download the JSON key for the service account. 4. Inside Search Atlas, open the URL Indexer tool via the left sidebar → Authority → URL Indexer (URL Indexer). 5. Upload the JSON key file in the designated field and save your configuration. 6. Paste or import the URLs you want to submit and run the indexing job. 🗺️ How Sitemap Indexing Works in OTTO When OTTO Instant Indexing is active, OTTO reads your connected sitemap to identify URLs that should be indexed. You do not need to manually submit individual pages. OTTO monitors your sitemap and queues new or updated URLs for submission automatically through whichever method you have enabled — IndexNow or GSC. To ensure full coverage, confirm that your sitemap URL is correctly entered in your OTTO site settings and that it is publicly accessible. ✅ Quick Decision Guide - Want hands-off, automated indexing through OTTO? Use OTTO Instant Indexing with IndexNow or GSC. No GCP setup needed. - Want to manually submit large batches of URLs via Google's Indexing API with your own GCP account? Use the Authority URL Indexer and complete the GCP and JSON key setup. - Not sure which tool you are in? If you are inside an OTTO session (left sidebar → OTTO SEO → All Sites (SEO Automation)), you are using OTTO Instant Indexing. The Authority URL Indexer is a separate tool with its own navigation entry. 💬 Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Understanding OTTO Schema Deployment and Structure

🔍 What Is Schema Markup and How Does OTTO Deploy It? Schema markup is structured data added to your page's HTML code. It communicates information about your content directly to search engines — without displaying anything visible to your website visitors. When OTTO deploys schema, it injects this code into the background of your page, not into the visible text or layout. This means that after OTTO successfully deploys FAQ schema, Article schema, or any other schema type, you will not see any new text or elements appear on your page. That is expected and correct behaviour. ❓ Why Isn't FAQ Schema Visible on My Homepage? FAQ schema deployed by OTTO is intentionally invisible. It exists as structured data in your page's source code, which search engines like Google read to understand your content and potentially display rich results (such as expandable FAQ dropdowns in search listings). The schema tells search engines about your FAQ content — it does not create or display that content on the page itself. Think of it as a label on the back of a product: shoppers do not see it, but the warehouse system reads it perfectly. ✅ Should I Add Visible FAQs Manually to My Homepage? Whether you add visible FAQ content to your homepage is a separate editorial decision from schema deployment. Here is how to think about it: - If your homepage already has FAQ content: OTTO's FAQ schema references that existing content. No manual addition is needed. - If your homepage has no visible FAQ content: You may choose to add an FAQ section for user experience and SEO value. This is entirely optional and based on your content strategy. - Duplicate content concern: Adding visible FAQs to your homepage will not create duplicate content issues. Schema markup and visible page content serve different purposes and are read differently by search engines. They complement each other rather than conflict. 📄 Why Is OTTO Suggesting Article Schema for My Homepage? Article schema is a widely used schema type that helps search engines understand the primary topic, author, publication date, and editorial nature of a page. OTTO may suggest Article schema for your homepage when it detects that the page contains editorial or informational content that fits this structure. This suggestion does not mean your homepage must be a blog post. It means OTTO has identified that Article schema can help search engines better interpret and index the content already present on your homepage. Applying it provides context — particularly useful for brand authority and AI-driven search visibility. 🗂️ What Does "Page-Level Schema" Mean? Page-level schema refers to structured data that describes the page as a whole, rather than a specific element within it. Examples include: - Article schema — describes the overall editorial content of the page - WebPage schema — identifies the page type and its role on the site - FAQPage schema — signals that the page contains question-and-answer content When OTTO deploys page-level schema, it is adding a structured summary of your entire page for search engines to process. This is different from element-level suggestions, such as heading or image optimisations, which target specific parts of the page. 🏷️ Are H2 Suggestions Deployed as Invisible Elements? No. H2 heading suggestions are not deployed as invisible elements. H2 suggestions are structural recommendations that affect the visible headings on your page. When OTTO suggests or deploys an H2, it is modifying or adding a heading that will appear in your page content. Here is a quick reference for what is visible versus invisible after OTTO deployment: - Schema markup (FAQ, Article, WebPage, etc.): Invisible — exists in source code only - H2 heading suggestions: Visible — appear as on-page headings - Meta title and description updates: Invisible on the page — visible in search engine results - Image alt text: Invisible to visitors — read by screen readers and search engines 🚀 How to Check What OTTO Has Deployed To review the schema and structural changes OTTO has made to a specific page, follow these steps: 1. Go to OTTO SEO in the left sidebar, then open SEO Automation (or navigate to /seo-automation-v3). 2. Select the relevant project and locate the page you want to inspect. 3. Open the page's task list to see a full breakdown of deployed and pending optimisations, including all schema types that have been applied. 4. To verify schema in your page source, right-click your page in a browser, select View Page Source, and search for application/ld+json — this is where deployed schema will appear. You can also use Google's Rich Results Test (search.google.com/test/rich-results) to confirm that deployed schema is valid and being read correctly by Google. 💡 Key Takeaways - Schema deployed by OTTO is always invisible to page visitors — this is correct and intentional. - Adding visible FAQ content alongside FAQ schema will not cause duplicate content issues. - Article schema on a homepage is a valid and helpful signal for search engines, not a mismatch. - H2 suggestions are visible heading changes, not hidden code injections. - You can verify all deployed schema in your page source or through Google's Rich Results Test. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 OTTO Heading Optimization Hidden Injection Behavior

**🧩 What Is OTTO Heading Optimization?** OTTO Heading Optimization automatically injects a structured set of HTML heading elements (** ** through ****) into your page to strengthen its topical structure and on-page SEO signals. These headings are placed inside a dedicated module near the closing **** tag of your page's source code. ​ # **🙈 Why Are the Injected Headings Hidden with display:none?** The injected headings are deliberately wrapped in a container styled with **display:none**. This is the intended, hardcoded design of the feature — **not a deployment error**. The platform tooltip confirms this behavior. The approach serves two clear purposes: - **Structural signaling without visual disruption:** The headings provide semantic HTML structure that search engine crawlers can read without altering the visible layout or design of your live page. - **Theme-safe deployment:** Keeping the module visually hidden lets OTTO enrich the page's heading hierarchy independently of your theme or page builder, guaranteeing zero unintended visual impact on your site. If you see hidden heading markup near the closing **** tag after enabling this feature, your site deployment is working exactly as designed. ​ # **✅ Is This SEO-Safe Under Google Guidelines?** Yes. Google's guidelines prohibit hiding content from users **specifically to deceive search engines** — for example, cramming invisible keyword blocks into hidden divs to artificially inflate rankings. OTTO Heading Optimization does not fall into that category for three key reasons: - **Structural headings, not keyword stuffing:** The injected content is a clean, logical heading hierarchy that reflects the page's actual content structure — not hidden blocks of target keywords. - **Transparent and documented:** The behavior is disclosed directly in the platform tooltip and this documentation, satisfying Google's transparency expectations for automated site modifications. - **Full crawler parity:** Googlebot renders JavaScript and reads the complete DOM. The injected headings are accessible to the crawler as intended structural signals, with no attempt to show crawlers different content than users see. Search Atlas's implementation follows the same principle as structured data and schema markup — enriching machine-readable page signals without creating a deceptive user experience. ​ # **🗺️ How to Access OTTO Heading Optimization** You can review and manage Heading Optimization tasks from the OTTO SEO section of the platform: 1. In the left sidebar, click **OTTO SEO**. 2. Go to **OTTO SEO → Overview** or **OTTO SEO → Page Explorer** to locate the target page. 3. Open the page's OTTO task panel and find the **Heading Optimization** task. 4. Review the injected headings, their levels, and their current deployment status directly in the task panel. # **↩️ How to Roll Back or Add Headings Manually** If you want to remove the injected headings, adjust the heading structure, or add headings manually, follow these steps: 1. Navigate to **OTTO SEO → Page Explorer** and open the relevant page. 2. Locate the **Heading Optimization** task in the OTTO task panel. 3. To remove all injected headings, click the **Undo** or rollback option next to the task. The hidden module will be fully removed from the page source on the next sync. 4. To add or edit individual headings, use the task panel's heading editor to set the heading level, text content, and order before redeploying. 5. Click **Deploy** (or **Save & Deploy**) to push your updated heading configuration to the live page. Rolling back a Heading Optimization task does not affect any other OTTO tasks running on the same page. ​ # **💬 Need More Help?** If you need further assistance, open the chat widget in the bottom-right corner of the platform and type **human teammate** to be connected with a member of our team.

📊 How to Bulk Export On-Page SEO Data from OTTO to Google Sheets

📋 Overview If you manage on-page SEO at scale, you may want to pull all of OTTO's recommendations out of Search Atlas in one go. Exporting to a spreadsheet lets you review changes in bulk, share them with your team, or transfer them into another tool such as Rank Math, Yoast, or your CMS. This guide shows you how to bulk export your on-page SEO data from OTTO into Google Sheets and use it to update other platforms. 📦 What You Can Export OTTO's on-page module generates page-level recommendations that you can export, including: - Page URLs - Title tags (current and suggested) - Meta descriptions (current and suggested) - Header tags (H1, H2) - Image alt text suggestions - Schema and other structured data recommendations Note on schema: Schema and other structured data are currently handled on a per-page basis, so they export alongside each page's row rather than as a single, separate full-site schema file. A dedicated full-site schema download is a known limitation and is on our roadmap, so a one-click export of all schema across the entire site is not yet available. ✅ Before You Begin - Make sure OTTO is installed and active on the project you want to export. - Allow OTTO time to finish crawling and generating recommendations. A complete crawl produces a complete export. - Confirm you have access to a Google account so you can open the file in Google Sheets. 🪜 Step-by-Step: Export On-Page Data 1. Log in to your Search Atlas dashboard. 2. From the left-hand menu, open OTTO SEO and select the project you want to work with. 3. Go to the Onpage Audit tab to view the full list of page-level recommendations. 4. Use the filters at the top to narrow the data if needed (for example, by page type, status, or recommendation type). To export everything, leave filters cleared. 5. Click the Export button, usually found in the top-right corner of the table. 6. Choose CSV as your export format. CSV opens cleanly in Google Sheets and Excel. 7. The file downloads to your device. 💡 Tip: Exporting Large Sites For sites with thousands of pages, the export may take a moment to generate. If your plan or table view limits the number of rows shown, export in batches using filters (for example, by folder or page type) and combine the files later in your spreadsheet. 📑 Open the File in Google Sheets 1. Go to sheets.google.com and open a new blank spreadsheet. 2. Select File > Import. 3. Click Upload and choose the CSV file you downloaded. 4. Under import settings, set Separator type to Comma and click Import data. 5. Your on-page SEO data now appears in organized columns, ready to review or edit. 🔄 Transferring Data to Rank Math (or Other Tools) Once your data is in Google Sheets, you can use it to update title tags, meta descriptions, and other elements in another SEO tool. ✍️ Option 1: Manual Updates Best for smaller sites or selective changes: 1. Open the spreadsheet next to your CMS editor. 2. For each page, copy the suggested title and meta description from the sheet. 3. Paste them into Rank Math's title and description fields on the corresponding page or post. 4. Save and publish the page. ⚡ Option 2: Bulk Import with Rank Math Best for large sites. Rank Math supports CSV imports for bulk metadata edits: 1. In your spreadsheet, arrange columns to match Rank Math's bulk-edit format, typically including the page ID or URL, SEO title, and SEO description. 2. Download the sheet as a CSV (File > Download > CSV). 3. In WordPress, go to Rank Math > Status & Tools > Import & Export and use the CSV import option. 4. Map the columns, run the import, and review the results. Always test on a few pages first and keep a backup before running a full bulk import. 🟢 Keeping OTTO Active Exporting your data does not change how OTTO works on your live site. If OTTO is deploying optimizations dynamically, those remain in place. Use the export as a reference or as a way to migrate recommendations into a platform where you prefer to manage them manually. 🔧 Troubleshooting - Export button is missing: Confirm you are on the On-Page tab and that OTTO has finished generating recommendations. - File looks jumbled in Sheets: Re-import and confirm the separator is set to Comma. - Some pages are missing: Clear any active filters, or wait for the crawl to complete and export again. - Very large export: Split the export into batches using filters, then merge them in your spreadsheet. - You want all schema in one file: Schema exports on a per-page basis today; a single full-site schema download is not yet supported. Export your on-page data as described above, which includes the per-page schema recommendations. 🙋 Need More Help? If your export is incomplete or you do not see the data you expect, reach out to our support team through the in-app chat typing "Human Teammate". Include your project name and a screenshot of the On-Page tab so we can assist quickly.

⚡ OTTO SEO Keyword Optimization and Blog Automation Setup

How OTTO SEO Determines What to Optimize OTTO SEO is designed to automate keyword optimization and content configuration for your connected site. When setting up OTTO SEO, you can direct its optimization focus by providing your own target keywords and configuring automation preferences within the platform. If you have not yet configured custom keyword targets or automation settings, OTTO may not align with your specific business goals or campaign priorities. The steps below outline how to approach this configuration. Setting Up Custom Keyword Targets in OTTO SEO To define the keywords and optimization targets OTTO SEO should work toward, navigate to the OTTO SEO section of the platform using the left sidebar. From there, look for the settings or configuration area where keyword targets and business context can be entered. Enter the keywords you want OTTO to prioritize — including primary, secondary, and long-tail variants — and save your changes so OTTO can reference them during its next optimization cycle. If you are unable to locate the keyword configuration area, or if the controls you expect are not visible, this may depend on your account setup or the version of OTTO SEO available to you. In that case, please reach out to support with your project name and a description of what you are trying to configure so the team can guide you to the correct settings. Activating OTTO SEO Optimizations Once your keyword targets are saved, ensure that OTTO SEO is active for your site. Navigate to the OTTO SEO section in the left sidebar and confirm your site appears as active. If OTTO does not appear to be running or applying optimizations, double-check that automation has been enabled for your site and that the site has been scanned with current data. Review any available audit or recommendation panels to approve or adjust suggestions before they are applied. If you are unsure whether OTTO is active or optimizations are being applied, contact support with your project name, the site URL connected to OTTO, and a description of the behavior you are observing. Setting Up Automated Blog Posting OTTO SEO includes functionality to automate blog content generation and publishing. To configure this, navigate to the OTTO SEO section of the platform and look for blog or content automation settings. From there, you can typically define a publishing schedule and set content preferences to guide what OTTO generates. If you cannot locate the blog automation controls, or if the feature does not appear available in your account, contact support with your project name and account details so the team can confirm whether this feature is enabled for your plan and assist with setup. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔐 Brand Vault: OG Description, Content Length Settings, and AI Generation

🤔 What is an OG Description? An OG (Open Graph) description is a short text summary — typically 150-160 characters — that appears when your link is shared on social media platforms like Facebook, LinkedIn, or X (Twitter). It shows under the link preview title. ➕ How to add an OG Description in Brand Vault 1. Open your Brand Vault project 2. Navigate to the SEO / Metadata section 3. Find the OG Description field 4. Enter your description manually, or use the AI generation option to auto-generate one based on your content 📏 Content length settings — what "Short" means - Short — 1-2 sentences; ideal for taglines, social captions, and brief descriptions - Medium — 2-4 sentences; suitable for standard product or service descriptions - Long — full paragraphs; best for detailed service pages and landing pages For most Brand Vault use cases, Medium is recommended. 🤖 Using AI to generate content in Brand Vault Most Brand Vault text fields support AI generation. Click the Generate with AI button next to any field. The AI uses your business name, industry, and existing Brand Vault data to produce relevant content automatically. If you previously experienced an error when saving longer AI-generated content in the Business Info description field — for example when the generated text exceeded the older 3,000-character limit — this has been resolved. The maximum description length has been increased to 20,000 characters, so long AI-generated descriptions now save successfully.

🔄 What Are Golden Loops? An Overview of Search Atlas's Automated Marketing Cycles

🔄 What Is a Golden Loop? A Golden Loop is a repeatable cycle where one success naturally creates the conditions for the next success, making growth increasingly self-sustaining. Once you turn one on, Search Atlas keeps actively working on that part of your marketing for you — whether that's your Meta Ads account, Google Ads, your CRM, your SEO and AI-search visibility, and more. Rather than a one-time audit or a report you have to act on yourself, a Golden Loop keeps running on the surface you choose, continuously. 🔁 The 5-Stage Cycle Every Loop Runs Every Golden Loop, regardless of which part of your marketing it's working on, moves through the same five stages: - Signal — reads a named, trustworthy source: your ad account, your CRM, Google Analytics 4, Search Console, and similar connected data. - Recommend — turns that signal into a specific, bounded action, with a rollback path built in. - Approve — routes the recommendation to the right level of oversight. Most loops only ever report what they'd do; some ask for your confirmation first. - Ship — once approved, the change goes out through your own review path. - Measure — the outcome feeds back into the next signal, so the loop gets sharper over time, not just busier. This is what makes it a loop rather than a one-off recommendation: each cycle's result becomes the input for the next one. 🧭 Where to Learn More For the full list of surfaces you can activate a Golden Loop on and what each one delivers, see our companion article on Golden Loop surfaces. For how Search Atlas keeps every loop safe and under your control, see our article on the approval model and activation process. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🧊 Understanding OTTO Deploy All and Deep Freeze

🚀 What "Deploy All" Does in OTTO The Deploy All button in OTTO (OTTO SEO) pushes every approved optimization for your project live at once, instead of you approving and deploying each fix individually. This covers items such as meta titles and descriptions, schema markup, heading adjustments, internal links, image alt text, and other technical and on-page fixes. When you click Deploy All, OTTO applies those changes to your live website through the OTTO Pixel using dynamic client-side rendering. This means the optimizations are injected into the page as it loads in your visitors' browsers, rather than being hard-coded into your CMS or static HTML. 🔄 Are Deployed Changes Permanent or Temporary? Deployed changes are live but fully reversible — they are not permanently written into your website's source code. Because they are served through the OTTO Pixel, you remain in complete control of them at all times. - They stay live for as long as the OTTO Pixel is installed and your project is active. - They can be rolled back at any time from your dashboard, individually or in bulk. - They are removed automatically if you uninstall the OTTO Pixel, disable OTTO, or remove the optimization — unless you have protected them with Deep Freeze (explained below). In short: nothing is locked into your site permanently, which gives you the flexibility to review, adjust, or undo any optimization without touching your CMS. 🧊 What the Deep Freeze Feature Does The Deep Freeze feature is an SEO continuity tool. It "freezes" your deployed OTTO optimizations so they remain live even if you cancel your subscription or pause the project. When the main subscription is cancelled, 24 hours after the account becomes unsubscribed all OTTO projects are automatically put into Deep Freeze (autopilot off, read-only), and the OTTO Pixel keeps serving the fixes that were already deployed — OTTO just stops crawling and making new changes. Deployed changes stop being served only if the Pixel is removed, the project is disengaged, or the project is deleted. With Deep Freeze enabled, your SEO improvements continue to be served to visitors and search engines for as long as the OTTO Pixel remains installed on your site. This protects the SEO equity you have built so you don't lose rankings or on-page gains during a billing change or transition. 💰 Deep Freeze Costs and Slot Management Deep Freeze was originally a paid add-on that customers purchased per project (often referred to as slots). Based on customer feedback, Search Atlas has since made Deep Freeze free and included across all plans, removing the previous per-use charges. - Cost: Deep Freeze is now included at no extra charge on current plans, so you generally no longer need to buy individual slots to protect a project. - Slot management: If your account still reflects a slot-based setup, you can manage which projects are frozen from OTTO SEO → All Sites (OTTO SEO Projects), using the Active/Deep Frozen tabs and the Freeze sites control. In the OTTO All Sites view, you can also use the segmented filter to quickly see which projects are Deep Frozen. - Requirement: The OTTO Pixel must stay installed for frozen changes to keep being served — removing the Pixel removes the changes. Because plan details and availability can vary by account, confirm your specific Deep Freeze entitlement inside your dashboard. ↩️ Is Deep Freeze Reversible? Yes. Deep Freeze is reversible and keeps you in control: - You can turn Deep Freeze on or off for a project at any time. - While Deep Freeze is active, editing and rollback controls are blocked and a freeze message is shown; you'll need to unfreeze the project to roll back or edit changes. - If you remove the OTTO Pixel from your website, the frozen optimizations will no longer be served, which effectively reverses them. The key thing to remember is that Deep Freeze provides continuity — it preserves your work through subscription changes — while still leaving every change reversible whenever you need. ⚙️ Deploying on a Deep Frozen Project While a project is in Deep Freeze, editing and rollback controls are blocked and a freeze message is shown until the project is unfrozen. If you experience unexpected behavior on a frozen project, reach out to our team via live chat so we can help. ✅ Quick Summary - Deploy All pushes all approved OTTO optimizations live at once via the OTTO Pixel. - Deployed changes are live but reversible, not permanently coded into your site. - Deep Freeze keeps your deployed changes live even after cancellation, as long as the Pixel stays installed. - Deep Freeze is now included free on current plans, removing past per-slot charges. - Everything remains reversible — you can roll back changes or disable Deep Freeze at any time. 💬 Need More Help? If you need further assistance, click the chat icon in the bottom-right corner of the platform to start a live chat with a member of our team.

⚠️ OTTO Hidden Content Injection: Black Hat SEO or Safe Optimization?

OTTO may add keyword lists and FAQ sections to your WordPress pages in the background to improve SEO performance. This content follows Google's guidelines and is not black hat SEO — your site is not at risk of a penalty. 🔍 What OTTO Adds to Your Pages When OTTO optimizes a page, it may inject supporting content into the page's HTML — including keyword lists or FAQ sections. This content is tagged with data-otto-pixel="dynamic-seo" and is added without changing your site's visible design or layout for visitors. All content OTTO injects is directly relevant to the page's topic and existing keywords. It does not introduce unrelated terms or fabricated information. Note: Search Atlas engineering has an active review to assess this implementation and may refine how the content is added in a future product update. ⚠️ Is OTTO's Hidden Content Black Hat SEO? No. Google's guidelines flag hidden content as a violation only when it is deceptive or irrelevant — for example, stuffing unrelated keywords into invisible text to manipulate rankings. OTTO's injected content differs in three important ways: - It is relevant: All added content relates directly to the page's topic and target keywords. - It is not deceptive: The intent is to support legitimate on-page SEO signals, not to mislead Google's crawlers. - It is non-manipulative: OTTO does not generate false signals of authority or topical relevance. Your site does not face a risk of a manual action or algorithmic penalty from this behavior as currently implemented. 📋 How to Review OTTO's Optimizations You have full visibility into every change OTTO applies. To audit your optimizations: 1. Open the OTTO section in your Search Atlas dashboard. 2. Select the site you want to review. 3. Browse the list of applied optimizations to see exactly what content was added to each page. 4. Approve, reject, or roll back any individual item as needed. You stay in full control of every optimization OTTO applies across your client sites. 💡 How to Add Keywords to Visible Content Instead If you prefer keyword content to appear visibly on the page — inside headings, body copy, or FAQ blocks — rather than injected in the background, that option is available. Contact Search Atlas support to configure OTTO to insert keywords directly into visible page content for your workspace. 🎯 OTTO's background content additions are safe, guideline-compliant optimizations — review them anytime inside your Search Atlas dashboard, and contact support if you'd prefer to switch to visible content insertion instead.

🚀 Revolutionizing Browser-Based SEO: the Search Atlas Chrome Extension V3

While the Search Atlas dashboard is where strategy lives, most SEO work happens directly in the browser: analyzing SERPs, auditing pages, and exploring competitor sites. The Search Atlas Chrome Extension brings fast, accurate, actionable SEO data directly into Google Chrome, turning everyday browsing into a real-time SEO workflow. 🧭 Landing on a Page: Immediate Context As soon as you land on a webpage with the extension enabled, a small status indicator appears under the Search Atlas icon showing the page's crawlability: green means the page is indexable and followable, red means the page is marked no-index, and a split indicator means no-index but follow. This lets you instantly detect issues, such as production pages accidentally left on no-index, before you even open the extension. ⚡ Mini Toolbar If enabled, a mini toolbar appears at the top of the page, giving you immediate access to URL Rating and Domain Rating, backlinks and referring domains, organic traffic, and Domain Power, along with quick access to settings. You can disable the toolbar entirely or add specific sites to an exclusion list. 📊 Opening the Extension: Page Summary Clicking the Search Atlas icon opens the on-page summary, a fast technical health check. It shows your heading structure (including missing or duplicated H1s), title tag and meta description with character count guidance, canonical tag configuration, robots meta directives, word count, and detected page language. From here you can also download the page's robots.txt and sitemap in one click. 🧩 Deep Analysis via Tabs For deeper inspection, the extension offers specialized tabs: a Headings tab showing the complete H1 through H6 hierarchy, a Link Status tab with a full link-level audit (internal and external links, anchor text, follow status, and placement, exportable as a CSV), an Image Audit tab surfacing missing alt text and titles, a Schema Markup tab presenting schema in a clean, toggle-based layout, and a Social Metrics tab previewing Open Graph and X (Twitter) cards. 🔁 Transition to the Dashboard When you are ready to go deeper, click Go to Dashboard. The current URL or domain is sent to Site Explorer, a full report runs automatically, and you gain access to historical traffic trends, keyword rankings, backlink profiles, and the economic value of organic traffic. 🔍 SERP-Level Analysis The extension also works directly inside Google Search results, showing keyword difficulty, average monthly search volume, cost per click, and authority metrics for every ranking domain. ⚙️ Extension vs Dashboard Use the Chrome Extension when you want to quickly audit a live page, analyze competitors while browsing, validate indexability and on-page structure, or evaluate SERPs without leaving Google. Use the Search Atlas dashboard when you need to run full site audits, analyze historical trends, manage projects and campaigns, or deploy fixes at scale. The extension and the dashboard are designed to work together. If the Search Atlas dashboard is your strategic command center, the Chrome Extension is your real-time execution layer out in the field. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🤖 How to Pause OTTO, Review On-Page Changes, and Control What Gets Published

OTTO is built to automate on-page SEO improvements, but you always stay in control. If you want to review AI-generated changes before they are applied to your website, you can temporarily pause OTTO, inspect all recommendations, and selectively re-enable automation when you're ready. This guide explains exactly how to do that, step by step. ⏸️ When should you pause OTTO? Pausing (disengaging) OTTO is useful when: - 🧐 You want to review SEO changes before publishing - ✋ You need to approve or reject specific title, meta, or heading updates - 👥 You're validating changes with a client or internal team - ⚙️ You want to temporarily stop automation while making manual edits 💡 Note on terminology: Pausing OTTO is done by setting it to Disengaged — the terms Pause and Disengage mean the same thing throughout this guide and in the product. ⚠️ Important Disengaging OTTO does not revert, remove, or delete anything. It simply pauses automated publishing. If the OTTO status shows Engaged but no changes are being deployed after 10–15 minutes, or shows Disengaged but changes are still being pushed to your site, this indicates a stuck backend task on our side (the UI toggle changed state but the backend job did not complete). This is a known issue. Contact support and include the following so they can resolve it quickly: your project name, the domain, the toggle state shown in the UI, and the observed behavior (e.g., "toggle shows Engaged but no deployments after 20 minutes"). ⚠️ Website Studio compatibility: If your site is built with Search Atlas Website Studio, OTTO on-page changes (meta tags, title tags, etc.) will not deploy correctly through manual script installation. Adding the OTTO pixel script tag manually inside Website Studio is not sufficient — the platform requires either a CMS connector or a properly configured Cloudflare Worker for deployments to work. We strongly recommend contacting support before attempting any manual installation on a Website Studio site, so we can set up the correct deployment path for you. If changes appear deployed in OTTO but are not reflected on your live site, contact support. 🔄 Step 1: Disengage OTTO (Pause Automation) 1. Go to Left Sidebar → OTTO SEO → All Sites (SEO Automation) 2. Select the site you want to manage 3. At the top of the site overview, locate the OTTO Toggle 4. Toggle OTTO to Disengaged When OTTO is disengaged: - 🚫 No new on-page changes are published - 👀 All recommendations remain visible - ✍️ You can freely review and configure suggested updates This is a safe review state, not an error. 📍 Step 2: Navigate to On-Page Recommendations Continuing from Step 1 (you should already be on the site you selected under All Sites), follow this exact path within that site: 🧭 Path: OTTO SEO → All Sites (SEO Automation) → Select Your site → OTTO Grader (Onpage Optimizations) This section shows: - 📋 All detected on-page issues - 🤖 OTTO-recommended fixes - 🔍 Current live content vs suggested content - 🚦 Deployment status for each recommendation 🎛️ Step 3: Review and Control Individual Changes Inside Onpage Audit , you can approve or reject changes one-by-one — you do not have to re-engage OTTO wholesale. Use the per-item Enable/Disable controls described below to choose exactly which title, meta, or heading updates should be published when OTTO is re-engaged. 🔎 Filter by issue type (Title Tags, Meta Descriptions, Headings, etc.) 👁️ Compare Original content vs OTTO Suggested Fix ✅ Enable or ❌ disable recommendations at: Category level (for example, all Title Tag issues) Individual page level (such as your homepage) ℹ️ About supporting content suggestions: OTTO may suggest adding supporting content such as keyword lists or FAQ sections. This content is contextually relevant to the page, is visible to both users and search engines, and is designed to improve SEO without affecting the visual design of your page. It is not hidden using deceptive techniques (such as display:none keyword stuffing) and is not considered black-hat SEO, because it does not violate Google's guidelines on hidden text and links. If you prefer not to publish a specific supporting-content suggestion, simply disable it at the recommendation level before re-engaging OTTO. 🛠️ Tasks stuck in Pending: Some tasks may remain in Pending status when OTTO cannot generate a fix. The most common cause is image alt text recommendations where the image itself is missing from the site (not just missing alt text — the underlying image file cannot be found on the page). OTTO cannot generate alt text for an image that doesn't exist, so the task will stay in Pending. To resolve these, either add the missing image to the page and re-scan, or accept that those specific tasks will remain unresolvable until the image is present on the site. 🧠 What each state means: - Enabled → Will be applied when OTTO is active - Disabled → Will never be applied, even after re-engaging OTTO You can mix enabled and disabled items freely. Automation is granular, not all-or-nothing. ▶️ Step 4: Re-Engage OTTO When Ready After reviewing and configuring what should be published: 1. Return to the site overview 2. Toggle OTTO back to Engaged OTTO will now: - 🚀 Publish only the enabled recommendations - ⛔ Skip anything you disabled - 🔁 Respect your selections going forward You can disengage and re-engage OTTO as often as needed. 🧊 What happens if I leave OTTO disengaged? Nothing changes on your site. - ❌ No SEO updates are pushed - 🧾 No content is overwritten - 🗂️ All recommendations remain in a review state OTTO stays paused until you manually re-enable it. ❓ Common Questions Does disengaging OTTO delete recommendations? No. All recommendations remain available for review. Can I re-enable only some changes? Yes. You control recommendations at both category and page level. Will OTTO override my manual edits? No. Disabled recommendations are never applied. Is this reversible? Yes. OTTO can be paused or re-engaged at any time. OTTO is not a black box. You can: - ⏸️ Pause automation - 👀 Review every suggested change - 🎯 Decide exactly what gets published - ▶️ Re-engage only when you're confident This workflow is intentional and designed to give you editorial control with AI support, not forced automation.

🤖 Automating Title Tags with AI: Understanding Autopilot Settings

Some users believe they can't automate more than 100 title tag tasks. That's not entirely true. This guide clarifies how Autopilot works, how to configure quota allowances, and why users might only see 100 tasks at a time, even if the system can process more. Autopilot applies to title tags and meta descriptions as separate content types — the same logic described below applies to each content type independently. 🧠 The Misunderstanding Some users believe that they can only automate what they see on a single screen (100 tasks), but that's not the case. The UI only displays 100 tasks per page, but Autopilot works independently of this display. That's a UI constraint, not a system limitation. - Example: A site may have 220 title tags (and the same logic applies separately to meta descriptions). - You'll only see 100 at a time, and can only select and bulk-generate 100 manually via the UI. - But this doesn't affect Autopilot, which can operate across all eligible tasks—up to 1,000 every 14 days. ✅ You can auto‑generate and auto‑deploy up to 1,000 tasks—even if you can't see them all at once. ⚙️ How Autopilot Works 1. From the OTTO dashboard, open your project and go to Auto Settings (located in the OTTO project sidebar) 2. Click Edit 3. Locate the Autopilot Quota Allowance section There, you'll see: - Your total AI quota (e.g., 50,000) - Your Autopilot batch limit (e.g., 1,000 title tags every 14 days) 🗓️ Example: You can configure it to run every 14 days, automatically generating 1,000 title tags without manual action. ℹ️ What you can configure: You can toggle Autopilot on/off and choose which content types are enabled (title tags, meta descriptions, etc.). The 14-day interval and the 1,000-task batch limit are plan defaults and are not user-adjustable — they are fixed by your plan. ⚡ How Otto Automates Up to 1,000 Tasks (Step-by-Step) Once Autopilot is properly configured: 1. Otto runs automatically at the interval you define (e.g., every 14 days). 2. On each cycle, Otto will: - Check your quota allowance (e.g., 1,000 tasks allowed) - Identify eligible pages that lack strong title tags - Auto-generate suggestions for those pages using AI - Deploy or queue the generated content (auto-published if auto-deploy is on; otherwise queued for review) - Update the quota counter to reflect tasks consumed in this cycle 3. If auto-deploy is enabled, Otto will publish those title tags without manual review. 4. At cycle end, unused quota does not roll over — your batch allowance resets at the start of the next 14-day cycle. 🧠 Example: If your quota allows 1,000 and 1,000 valid pages are detected, Otto will generate and deploy 1,000 title tags in a single cycle. 🧠 If Otto finds only 100 valid pages, then only those 100 will be created and deployed. The rest of the quota remains unused until the next cycle. ⚠️ Important — quota exhaustion mid-run: If your AI generation quota runs out part-way through a batch, the entire batch may be dropped and no partial progress is saved. To avoid this, confirm your total AI quota is sufficient before each Autopilot cycle runs, and review task statuses after every cycle to confirm completion. 💡 Are quota units refunded for dropped batches? Historically, quota units consumed by a dropped batch were not automatically refunded. If you believe a batch failure caused quota loss, contact support to request a quota adjustment. ⚠️ About Auto‑Deploy and Customization If auto-deploy is enabled, the generated title tags are published immediately after Otto creates them. 🛑 This means you won't get a chance to review or customize the tags before they go live. If the system only detects 100 valid title tag tasks: - Those 100 will be auto-created and auto-published - You won't have a preview or editing step unless you disable auto-deploy Use caution when enabling auto-deploy, especially if you want to refine or validate content before it appears live. 📌 Tasks Otto can't complete: Some task types — for example, images with no detectable alt text source — may remain in 'pending' status even after an Autopilot cycle. These tasks still require manual review and input; Autopilot will not force-complete them. 🔍 But What If Only 100 Are Created? "If Otto only found 100 valid title tag tasks, then only those 100 would be created and deployed." This means: - Detection is dynamic, not forced. - You can't override the system to hit exactly 1,000 unless those 1,000 are detected as eligible. 🚦 If tasks went ungenerated, check your quota first: A quota-blocked outcome typically appears as tasks that remain ungenerated after a cycle. Quota-blocked tasks are now flagged with a distinct reason code in the OTTO interface, so you can tell them apart from LLM/generation pipeline failures. If you see tasks that did not process after a cycle, check your Autopilot Quota Allowance before assuming a generation error. 🔍 What Limits the Total? - If the platform only detects 100 valid title tag tasks, then only 100 will be generated—even if you have quota for 1,000. - You can't "force" more tasks unless more URLs are eligible and detected by the system. - AI generation quota vs. OTTO site quota: The AI generation quota controls how many tasks Autopilot can process. This is separate from the OTTO site quota, which controls how many sites you can add to OTTO. If you believe your OTTO site quota is incorrect or needs adjustment, contact support. 🛠️ Tips to Maximize Automation 1. Make sure your project includes as many valid URLs as possible. 2. Use filters to explore which pages are being excluded from AI generation. 3. Familiarize yourself with Autopilot Settings in your dashboard to monitor quota usage and upcoming runs. 4. Confirm your total AI quota is sufficient before each cycle to avoid mid-batch quota exhaustion. 5. After each cycle, review task statuses — including any tasks still marked pending or flagged as quota-blocked. ❌ Common Mistakes ❌ Misreading the UI: Seeing 100 tasks per page doesn't mean that's the platform limit. ❌ Assuming Autopilot is manual: It's an automated background process, not a bulk UI action. ❌ Expecting customization mid-run: Autopilot generates titles in batches—you can't manually select specific ones during that phase. ❌ Confusing the OTTO site quota with the AI generation quota — they are tracked separately. ❌ Assuming a missing task means a generation error — it may be a quota block (look for the distinct quota-blocked reason code). If your quota allows, Autopilot can process up to 1,000 title tags every 14 days. But the actual limit is how many tasks the system detects as valid. Use the available settings to manage, review, and optimize this powerful automation feature.

🔎 OTTO Preview Feature

The Preview Feature for Headings and Tags enables you to validate your SEO updates within Search Atlas before they go live. This gives you confidence in your optimizations and ensures your changes are accurate, consistent, and properly structured. Instead of guessing how a tag will appear to search engines or users, you can see it instantly in a side-by-side preview. 🧭 How To Use It 1. Log into your Search Atlas dashboard. 2. Navigate to OTTO SEO → All Sites (SEO Automation). 3. Select your site to open the OTTO Grader (Overview). 4. Go to On-Page Optimizations. 5. Click on Page Title (OTTO Grader). 6. Click the eye icon above OTTO's suggested fix. 7. Preview the fix before it gets launched. 8. Click Enable to deploy the fix, or Enable All Categories. 9. Or select the pencil icon in the right corner to edit the proposed title. 10. Adjust the title length or wording until it fits best. 11. Confirm when you're satisfied, knowing the published version will match the preview. Navigate to the Search Atlas dashboard 🔑 Key Details - Shows both the OTTO version (with the suggestion applied) and the original, live version - Hover over elements (like title tags) to view changes - Requirement: a suggested fix must exist (originals always exist) ⚡ Why It Matters Avoids publishing errors (like titles that are cut off or duplicate H1s), saves time by letting you validate content in real time, and creates cleaner, more SEO-friendly site structures. 💡 Pro Tip Use this feature during audits or bulk updates to catch small inconsistencies before they impact SEO performance. With the Preview Feature for Headings and Tags, you no longer need to second-guess your SEO updates. You can see exactly how your optimizations will look before going live — ensuring accuracy, boosting confidence, and saving valuable time. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

SEO Annotation Text

There are few SEO elements more complex than links. While most writers focus on internal linking, anchor text, and backlinks, many overlook annotation text — a costly mistake. Annotation text can significantly enhance how Google interprets links, making it a hidden key to stronger SEO performance. In short: anchor text is the clickable hyperlink text itself, while annotation text is the descriptive wording surrounding that link. 🧩 What is SEO Annotation Text? Annotation text is the text surrounding a link — distinct from anchor text, which is the clickable hyperlink text itself. Google's web crawlers can use this surrounding text to better understand the linked page. Research suggests that crawlers index not only the anchor text but also nearby words — even across entire paragraphs or sections. This behavior is most strongly documented in the context of outbound and external links; its application to internal links and inbound backlinks is less well documented, though many SEOs believe similar principles likely apply. Most importantly, Google's algorithm patent indicates that this surrounding text can be a ranking factor. 🧠 Diving into Google's Web Crawler System & Patent Based on the research of the late Bill Slawski — an independent SEO researcher who analyzed Google's publicly available patent filings — annotation text evolved from a system update that allows Google to index words found within a predetermined distance of a hyperlink. It is important to note that Google has never officially confirmed annotation text as a named ranking factor; the concept comes from third-party interpretation of patent documents, not from Google itself. Google has also not publicly disclosed the exact unit of that distance — whether it is measured in characters, words, sentences, or DOM elements — so use this as a general best-practice guide rather than a precise technical specification. Note: The term proximity-based semantic analysis used below is an informal industry phrase, not official Google language. It is offered only as a shorthand for the idea that Google's crawler appears to use nearby text to help interpret a link's meaning more accurately. This introduced what is informally called proximity-based semantic analysis, meaning that Google's crawler uses nearby text to interpret a link's meaning more accurately and to associate the linked page with the surrounding topical context. 📈 How Does Annotation Text Affect SEO? Google's NLP algorithms now analyze both anchor text and surrounding annotation text. - Anchor text = primary indicator of linked page relevance. - Annotation text = secondary indicator providing additional context. By indexing nearby phrases, Google refines its understanding of the link's destination, improving relevance and user experience. TL;DR: Annotation text gives your outbound, internal, and inbound links contextual meaning that helps Google interpret them more accurately. 🌐 Your Site's SEO & Text Around Links Optimizing annotation text strengthens your site's internal links and improves off-site backlinking efforts. Because most creators focus only on anchor text, optimizing the surrounding text gives you a competitive advantage. ⚖️ How Strongly Does Annotation Text Affect the Meaning of a Link? Although Google holds PageRank's exact signals secret, annotation text likely plays a role in ranking, especially given its alignment with Google's SMITH algorithm. However, Google has not officially confirmed this. 🔬 The Structure of Annotation Text Think of anchor text as the nucleus of an atom and annotation text as the electrons orbiting it. Both define the atom, but the anchor text is more precise. Google's system pulls data from a predetermined distance around the anchor tag — so ensure key terms appear close to your link, while maintaining natural, quality writing throughout the page. Quick example: - Weak annotation text: "For more info, click here." - Strong annotation text: "Learn how to run a complete technical SEO audit, including crawl analysis, indexation checks, and Core Web Vitals troubleshooting." The second version surrounds the link with topically relevant terms that help Google understand what the destination page is about. 🔗 What Is Anchor Text? Anchor text is the clickable text in a hyperlink that directs users to another page. It often describes the destination content (e.g., “an update of Google's algorithm patent”). Google uses anchor text to determine the topic of the linked page while crawling a site's sitemap. 🚫 Is Annotation Text the Same as an Annotation Link? No. Annotation links may refer to video or interactive hyperlinks that jump users to a section or multimedia element. This is not the same as annotation text, which refers to the contextual words around an anchor. 🛠️ Techniques for the Best SEO Annotation Text Step 1: Use Focus Terms Near Your Links Place topically relevant Focus Terms near both internal and external links. This helps Google better interpret the target page. Step 2: Identify Focus Terms to Include Use Search Atlas tools like Content Genius and the SEO Content Assistant to surface high-impact, topically relevant keywords you can place near your links. OTTO can also help by recommending on-page improvements that strengthen the context surrounding your anchors — for example, suggesting relevant phrases to weave into the sentences and paragraphs adjacent to important links. Any changes OTTO recommends or applies should be visible to both users and crawlers; annotation text that is hidden from users will not function as valid context. Avoid forcing unrelated terms, even if they are high-value. Step 3: Incorporate Focus Terms Naturally Avoid keyword stuffing. Focus on semantically related words and phrases that naturally support the meaning of your anchor text — for example, including related entities, synonyms, or descriptive context within the same sentence or paragraph as the link. Step 4: Develop the Surrounding Paragraph Ensure the paragraph containing your link is well-developed and relevant. Avoid: - Placing backlinks at the end of a section - Using backlinks in short or “thin” sections - Embedding high-value links in bullet lists, charts, or tables - Keyword stuffing or padding surrounding text with irrelevant terms - Using hidden text near links (e.g., display:none, off-screen text, or same-color-as-background text) — this is not valid annotation text, is not user-visible, and could be flagged by Google as a black-hat tactic - Surrounding links with boilerplate or thin filler content that adds no topical context 🚀 Annotation Text = Better SEO Annotation text gives Google and readers richer context about your links. Optimizing both anchor and annotation text — with the help of Search Atlas tools like Content Genius, the SEO Content Assistant, and OTTO — ensures Google better understands your content's relevance, improving user experience and increasing your chances of ranking in top SERP positions.

🧠 OTTO SEO Project Overview & Recommendations

Open the OTTO SEO module and navigate to All Sites (SEO Automation) in the left sidebar to land on the Project Overview: a decision-making dashboard showing your weighted site health score, prioritized issue categories, and a deployment readiness checklist. This article explains the full two-layer workflow, from reading your project health to deploying and rolling back SEO recommendations. The workflow is divided into two layers: - Project Overview — establishes context, system health, priorities, and readiness - Recommendations — where you review, customize, deploy, measure, and roll back SEO fixes, including Custom HTML Content The site health score is weighted, not a simple average. High-impact signals like page titles contribute more to your grade than low-impact signals like social meta tags — so fixing a small number of high-signal issues can produce a large improvement in your overall score. 🧭 How to Reach the Project Overview The Project Overview is the default landing screen for every OTTO SEO project — a decision layer, not an execution workspace. Navigate to it using this path: Left sidebar → OTTO SEO → All Sites (SEO Automation) The Overview loads automatically as soon as you select a project. Everything here answers one question: Is this project ready for action, and what should I focus on next? No fixes are deployed from this screen. The grade shown here is a weighted score: higher-impact signals such as page titles count more than lower-impact ones such as Twitter tags — which is why a small number of high-signal fixes can produce a sharp improvement in your overall grade. 🏷️ The Project Header: Identity, Context, and State The top of the screen anchors you to which project you are working on and confirms whether OTTO is technically ready to act — preventing a common mistake: working on the wrong site or acting before systems are properly connected. Project Identity (Top Left) The top-left corner displays: - The project name - The primary domain - A platform indicator (for example, a WordPress logo if detected) This confirms that all scans, all recommendations, and all deployments apply only to this specific site and environment. Always verify the project identity here before making changes in Recommendations. System Status Panels (Top Row) Below the project identity is a horizontal row of compact panels. These are system-level indicators, not performance metrics. They answer: - Is OTTO connected? - Is it informed? - Is it allowed to act? - Is it configured correctly? UUID Panel Location: Top row, left-center This panel shows whether OTTO's tracking identifier (UUID) is correctly connected to your site. How it looks: - A toggle switch showing whether OTTO is engaged or disengaged - A Scan ⚡ button alongside the toggle How to use it: - The toggle reflects the current engagement state - Click Scan ⚡ to force a validation check and confirm or re-establish the connection How to interpret it: If this panel shows an error or red state, OTTO may still analyze your site — but automation, deployment, and indexing may be limited or blocked. Resolve this panel before moving into Recommendations. Brand Vault Panel Location: Top row, center | Icon: ✏️ Pencil (Edit) This panel reflects the completeness and accuracy of your project's Brand Vault configuration — a quick visual indicator of how fully Brand Vault has been populated and whether your business intelligence layer is properly configured. The completion state shown here is directly tied to the structured data stored inside Brand Vault. 📋 Working with Recommendations The Recommendations layer is where SEO work is reviewed, customized, deployed, measured, and rolled back. Within Recommendations, you can also manage Custom HTML Content — create, edit, validate, preview, and deploy it directly through the OTTO Agent. Custom HTML Content is distinct from standard SEO fix types and requires HTML validation before deployment. To roll back a deployed fix: 1. Locate the specific fix type (for example, Heading Length ) in your OTTO SEO list 2. Open its deployment detail 3. Click Undeploy to remove it from the front end immediately Use Undeploy any time a deployed fix causes unintended front-end changes, such as unexpected heading text appearing on your site. ⚠️ Known Issues & Upcoming Changes Upcoming: Several issue types are moving to the main OTTO SEO Automation dashboard only In an upcoming release, the following issue types will only be accessible from the main OTTO SEO → All Sites (SEO Automation) dashboard — not the per-page detail view: - Topical Maps and Supplemental Content - Meta Description - Meta Keywords - Missing Keywords - Internal Link Suggestions If you currently manage any of these from the per-page detail view, switch to the main OTTO SEO → All Sites (SEO Automation) dashboard now. Cloudflare proxy: character encoding bug (OTTO-1357) If your site is proxied through Cloudflare, OTTO's script injection may corrupt special characters in headings that contain nested HTML. If you observe character encoding errors after engaging OTTO, contact Support and reference bug OTTO-1357. 🎯 You now understand how the OTTO SEO / OTTO SEO Project Overview and Recommendations layers work together — from reading your weighted health score and confirming system readiness to deploying fixes and rolling them back when needed. Confirm your UUID panel connection and populate Brand Vault before moving into Recommendations to deploy your first fixes.

🚀 How OTTO Deploys and Verifies SEO Changes

💡 Does OTTO Only Suggest Changes, or Does It Implement Them? OTTO does both. It first analyzes your pages and creates optimization suggestions. Once a suggestion is deployed, OTTO applies the change to your website for you, so you do not need to edit each page by hand. A suggestion by itself does not change your site. Changes go live only after deployment. Depending on your setup, deployment can happen in two ways: - Manual deployment: You review each suggestion and choose which ones to deploy. - Automatic deployment: If this is enabled for your project, OTTO deploys approved types of changes without waiting for you to click each one. Deployment also requires OTTO to be properly connected to your website. If the installation is incomplete, suggestions may appear in the platform but not show on your live pages. 🧭 Understanding the Stages of a Suggestion Each suggestion moves through simple stages. The exact labels may vary slightly in the platform, but the flow is generally the same: 1. Suggested: OTTO has found an opportunity and recommended a change. Nothing has changed on your site yet. 2. Deployed: The change has been sent to your website. 3. Live: The change is visible on the page for visitors and search engines. If a suggestion is still in the first stage, that is why you do not see any difference on your site. 📊 Where to See What OTTO Has Done So Far To review progress, open your OTTO project in the platform and look at the playbooks and their individual suggestions. Playbooks group related recommendations together, so you can see the work for each area in one place. Inside a playbook, you can: - Check the status of each suggestion to see whether it is waiting, deployed, or needs attention. - Open an individual suggestion to see the page it applies to and the change that was made. - Compare the current version of the page element with the optimized version. - Confirm which pages have already been updated and which are still pending. Use these views as your breakdown of completed work. If you manage many pages, work through one playbook at a time so it is easy to track what is finished. 🔍 How to Verify Changes on Your Live Website You can confirm that a change is live without any special tools. Follow these steps: 1. Open the page that the suggestion applies to in your browser. 2. Right-click anywhere on the page and choose View Page Source. 3. Use the search shortcut (Ctrl+F on Windows or Cmd+F on Mac) to look for the updated text, such as the new title or meta description. 4. Compare what you find with the optimized version shown in OTTO. Some changes are easy to see right on the page, such as updated headings or text. Others, such as title tags, meta descriptions, and schema markup, are only visible in the page source or in the browser tab title. 🛠️ Other Ways to Check Your Changes - Google Search Console: Use the URL Inspection tool to see how Google views the page, and request indexing if you want it recrawled sooner. - Rich Results Test: If OTTO added schema markup, paste your page URL into Google's Rich Results Test to confirm it is detected. - Private browser window: Open the page in an incognito or private window to avoid seeing an older saved version. ⏳ Why You May Not See a Change Right Away If you deployed a suggestion but cannot see the change, one of these is usually the reason: - Caching: Your browser, website plugin, or hosting service may be showing an older saved copy of the page. Clear your site cache and refresh the page. - Short delay: Changes can take a few minutes to appear after deployment. - Search results lag: Even after a change is live on your site, Google can take days or weeks to update how the page appears in search results. - Connection issue: If OTTO is not fully installed on your website, deployed changes may not reach your live pages. - Suggestion not deployed: The suggestion may still be waiting for approval. Check its status in the playbook. ✅ Quick Checklist 1. Confirm OTTO is installed and connected to your website. 2. Open the playbook and check that the suggestion status shows as deployed. 3. Clear your website and browser cache. 4. View the page source and look for the updated content. 5. Use Google Search Console to monitor how the page is crawled and indexed over time. 💬 Need More Help? If a deployed change still does not appear after you have worked through the checklist, or if a playbook does not show the breakdown you expect, our team can look at your project directly. Please have the page URL and the name of the suggestion or playbook ready. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🛠️ How to Manage Many OTTO Suggestions at Once

🔍 Overview If your project dashboard shows hundreds of OTTO suggestions, such as 300 or more link issues, going through them one by one is not practical. This article explains how to handle large volumes of suggestions, what to check when they look wrong, and how to get help with clearing them. ❓ Can I Bulk Delete OTTO Suggestions? Many customers ask this when a large batch of suggestions looks incorrect. Whether you can select and remove several suggestions at once depends on the view and suggestion type you are working in. If you do not see a select-all option or checkboxes next to the suggestions, bulk deletion is not available there, and the options below will save you the most time. Important: OTTO does not change anything on your website until you approve or deploy a suggestion. Unwanted suggestions are not live on your site, so you can take your time deciding what to do with them. 🧭 Step 1: Narrow Down the List Before deleting anything, work out which suggestions are actually the problem. A large count is often caused by one or two repeated issues. 1. Open your project from the dashboard. 2. Go to the section that lists the suggestions or issues, such as link issues. 3. Use any available filters or sorting to group suggestions by issue type, page, or status. 4. Look at a few examples from the group to see whether they are wrong or just unexpected. If most of the 300 suggestions share the same cause, fixing that one cause is faster than removing them individually. 🔗 Step 2: Check Why Link Suggestions May Look Incorrect Link suggestions can appear incorrect for a few common reasons. Check these first: - Redirected links: a link may point to a URL that redirects to another page. It can look broken but still work for visitors. - Recently changed pages: if you updated or moved pages recently, the suggestions may reflect an older version of your site. - Blocked or restricted pages: pages that require a login or block crawlers can be reported as problems when they are not. - Dynamic or script-loaded links: links added by scripts may not be read the same way as standard links. - Repeated site-wide elements: a single link in your menu, footer, or sidebar can create a suggestion for every page it appears on, which inflates the total. If a link in your menu or footer is the cause, fixing it once can clear a large share of the suggestions. ✅ Step 3: Manage Suggestions Without Deleting Them One by One If you are not ready to clear the list, you can still keep it under control: - Do not approve or deploy the suggestions you believe are incorrect. They will not affect your site. - Focus on a priority group. Handle the issue types most important to your goals first and leave the rest. - Use bulk selection where available. If checkboxes or a select-all option appear in your view, select the suggestions you want to remove and apply the action to all of them. - Re-check after fixing the cause. Once you correct the underlying problem, a fresh scan may update or remove outdated suggestions. 💡 Tips to Avoid This Next Time - Review suggestions soon after your first scan, before the list grows. - After a site redesign, migration, or URL change, check that your project settings still match your site. - Fix site-wide issues, such as menu or footer links, first, because they affect the most pages. - Keep notes on which suggestion types you consider incorrect so you can describe them clearly if you contact support. 🙋 Need Help Clearing a Large Batch? If you have hundreds of suggestions that you believe are incorrect and cannot find a faster way to remove them, our team can review your project and advise on the best next step. To help them move quickly, have the following ready: - The name or domain of your project - The type of suggestion affected, such as link issues - The approximate number of suggestions - A couple of example pages where the suggestion looks wrong If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team. 📌 Quick Summary - Unapproved suggestions do not change your website. - Check whether one repeated cause is creating most of the suggestions. - Use bulk selection if it is available in your view. - Fix underlying causes, then re-check your project. - For large batches, chat with a human teammate for help.

⚙️ How to Change Your OTTO Project Goal

🎯 What Is an OTTO Project Goal? When you set up an OTTO project, you choose a main goal. This tells OTTO what to focus on first. Common goals include Drive Traffic, Generate Leads or Sales, and Fix Technical SEO Issues. Your goal is not permanent. Many customers start with one goal, such as driving traffic, and later decide they want to clean up technical problems first. This article explains how to make that change and what to do if you can't find the option. ✅ Before You Change Your Goal A few quick checks will save you time: - Confirm the right project. If you manage several websites, make sure you have the correct project open. - Check your permissions. Only the account owner or users with project management access can edit project settings. - Note your current setup. Take a quick screenshot of your current settings so you can compare them later. 🛠️ How to Change Your Goal in an Existing Project The exact layout can vary slightly depending on your plan and platform version. In general, follow these steps: 1. Log in to your Search Atlas account. 2. Open OTTO SEO and select the project you want to update. 3. Open the project settings for that project. 4. Look for the section that shows your project goal or setup preferences. 5. Select Fix Technical SEO Issues (or the goal you want). 6. Save your changes and refresh the page to confirm the new goal appears. 🔎 What to Do If You Can't Find the Goal Option Some customers find that the goal is shown in their project but can't be selected again after the first setup. If this happens, try these steps in order: 1. Refresh the page. Log out and back in, or try a different browser window, to rule out a display issue. 2. Check the project overview and settings pages. The goal may be listed in a different area than you expect. 3. Ask our team to update it for you. If the goal is locked in your project, our support team can help change it. See the final section for how to reach them. 4. Consider a new project. If you want a completely fresh start with the new goal, you can set up a new project for the same website. Ask our team first, so you know how this affects your current data and plan limits. 🔄 What Happens After You Change Your Goal? - Your website data stays connected. Changing a goal does not remove your site from Search Atlas. - OTTO's priorities shift. Recommendations will focus more on the new goal. For Fix Technical SEO Issues, expect more attention on crawl errors, page speed, broken links, and site structure. - Updates may take time. New recommendations may not appear instantly. Give OTTO some time to re-scan your site. - Your earlier work is not lost. Changes already made to your site stay in place. 💡 Tips for Choosing the Right Goal - Choose Fix Technical SEO Issues if your site has errors, slow pages, or indexing problems that may be holding back your rankings. - Choose Drive Traffic if your site is technically healthy and you want to grow visitors. - Choose Generate Leads or Sales if you want to focus on pages that bring in customers. - It is common to start with technical fixes and then move on to traffic or leads once your site is in good shape. ❓ Frequently Asked Questions Can I change my goal more than once? You can request changes as your needs evolve. If you can't edit the goal yourself, our team can help. Will I lose my project data if I change the goal? No. Your connected site and existing data stay in place when the goal changes. Do I need to delete my project and start over? Usually not. Try the steps above first, and check with our team before deleting anything. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team. Let them know the name of your project and the goal you want to switch to, so they can help you quickly.

🔄 Do AI SEO Suggestions Refresh After Upload

💡 The Short Answer Yes, AI SEO suggestions can update after you upload new meta keywords or alt text for a client. They do not always change the instant you upload. Suggestions are based on the most recent information the platform has about the page, so they refresh once that new information has been processed. This article explains what to expect, what typically changes, and what to check if your list looks out of date. 🔍 How Suggestions Are Generated AI SEO suggestions are recommendations for improving a page, such as meta details, keyword usage, and image alt text. They are created by comparing what the platform sees on the page with SEO best practices and your target keywords. This means suggestions can change when: - You add or change the target keywords for a client - You add or update meta information or image alt text - The page content itself changes on the live site - The platform re-checks the page and finds new information 📋 What Updates After an Upload After your data has been processed, you can generally expect the following to change: - Suggestion list: Items you have already addressed may no longer appear, and new recommendations may be added based on the updated data. - Keyword-related recommendations: Suggestions that depend on target keywords may adjust to match the keywords you uploaded. - Alt text and meta recommendations: Suggestions about missing or weak alt text and meta details may update to reflect what you provided. Suggestions about things you did not change, such as page speed or site structure, will usually stay the same until the underlying issue is fixed. ⏱️ Why Suggestions May Not Change Right Away If you uploaded data and the list looks the same, one of these common reasons usually explains it: - Processing time: Larger uploads, such as many keywords or images at once, can take longer to process. - Your browser is showing an older view: The page may not have reloaded since your upload. - The live page has not changed: If suggestions are based on what is published on the client's site, uploading data to the platform may not change the live page until the updates are applied there. - Wrong client or project selected: The upload may have gone to a different project than the one you are viewing. - Upload issues: Formatting problems or skipped rows can mean some data was not imported. 🛠️ How to Refresh Your Suggestions Follow these steps in order: 1. Confirm that your upload finished without errors and that the data appears in the correct client project. 2. Wait a few minutes, especially after a large upload. 3. Reload the page in your browser to clear any outdated view. 4. Make sure the client project selected at the top of the platform matches the one you uploaded to. 5. Check that your meta details and alt text are live on the client's website, if the suggestions depend on the published page. 6. If the platform offers a rescan, refresh, or re-analyze option for that page or project, run it and check the list again. ✅ Tips for Cleaner Results - Upload in smaller batches so you can see which changes affect which suggestions. - Keep a record of what you uploaded and when, so you can compare before and after. - Double-check keyword and alt text entries for typos or empty fields before uploading. - Review the suggestions list after each major update instead of waiting until the end. ❓ Frequently Asked Questions Will old suggestions disappear on their own? Suggestions you have resolved should drop off the list once the platform has re-checked the page. If a resolved item stays, follow the refresh steps above. Do I need to re-upload to get new suggestions? Usually not. Re-uploading the same data will not change the results if the information has not changed. Can I see exactly what was updated? Compare your suggestions list before and after the upload. Keeping a note or screenshot of the earlier list makes this easier. 🙋 Still Seeing Outdated Suggestions? If you have followed the steps above and your suggestions still look out of date, our team can check your specific client project and confirm what is happening. Please have the client name and a short description of what you uploaded ready. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🚫 How to Exclude Pages from OTTO

🎯 What Excluding a Page Does OTTO can optimize many pages on your site automatically. Sometimes you want certain pages left exactly as they are, such as checkout pages, login pages, legal pages, or pages your developer manages by hand. The Excluded URLs list tells OTTO to skip those pages. It is important to know what this feature does and does not do: - It does: stop OTTO from applying optimizations to the pages you list. - It does not: remove Search Atlas or OTTO from your whole website. Your other pages stay optimized. - It does not: uninstall the OTTO setup on your site. If you want OTTO fully turned off, see the section below on disabling OTTO completely. ✅ Before You Start - Make sure you are signed in to the Search Atlas platform and have access to the project (website) you want to change. - Collect the full URLs of the pages you want to exclude, for example https://yourdomain.com/checkout. - Check that each URL belongs to the same website as your OTTO project. 🛠️ How to Add Pages to the Excluded URLs List Menu names and layout can change as we update the platform, so use the steps below as a guide and look for the closest match on your screen. 1. Open the Search Atlas platform and select the project for your website. 2. Open OTTO from the main navigation. 3. Look for the project's OTTO Settings area. The Excluded URLs option is found there if it is available on your account. 4. Find the Excluded URLs list. 5. Paste or type the full URL of the page you want to exclude, then add it to the list. 6. Repeat for each additional page. 7. Save your changes. 🔎 How to Confirm It Worked - Reopen the Excluded URLs list and check that your pages appear and the list saved correctly. - Open the excluded page in a private or incognito browser window to see the live version without cached content. - If the page still shows an old OTTO change, clear your website's cache (and your CDN cache if you use one). Then reload the page. Caching is the most common reason an update does not show right away. Allow some time for the update to take effect. It may not be instant on every site. 🧩 Tips for Choosing Which Pages to Exclude - Transactional pages: carts, checkout, and account pages usually do not need SEO changes. - Pages with custom work: if you or your developer carefully hand-tuned a page, exclude it so nothing is overwritten. - Temporary pages: landing pages for short campaigns or staging content can be excluded until they are final. - Keep the list short: exclude only what you need, so the rest of your site keeps benefiting from OTTO. ❓ I Don't See the Excluded URLs Setting If you cannot find the setting described above, the most common reasons are: - You are in the wrong place: the setting is tied to OTTO for a specific project. Make sure you have selected the correct project first. - Your account role: some settings are only visible to account owners or admins. - Your plan or setup: the option may not be available for every plan or every OTTO installation type. - The platform has changed: labels and locations get updated, and a setting may have been renamed or moved. Please do not worry if this applies to you. Our team can check your project and exclude the pages for you or point you to the right place. 🔌 Disabling OTTO Completely If your goal is to turn off OTTO for the whole site rather than a few pages, the Excluded URLs list is not the right tool. Our team can confirm the correct steps for your specific setup, since they depend on how OTTO was installed on your website. 🛟 Troubleshooting - The page is still being changed: check that the URL in the list matches the page exactly, including https, the domain, and any trailing slash. Then clear your cache. - The URL will not save: make sure it is a complete URL from your own site and does not contain extra spaces. - You need to exclude many pages at once: for example, an entire section of your site. Ask our team whether a faster option is available for your account. - You want to bring a page back: remove it from the Excluded URLs list and save. OTTO can then optimize it again. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team. To help us resolve your request quickly, include the website you are working on and the URLs you want excluded.

🤖 Exclude Pages from OTTO SEO

🧭 Overview OTTO, Search Atlas's OTTO SEO automation engine, crawls your site to discover and apply on-page optimizations. By default, OTTO will process all pages it can reach within your project. If you want to prevent OTTO from crawling or optimizing certain pages — such as Spanish-language pages, staging URLs, or low-priority sections — you do this through the URL Exclusion conditions in your project's OTTO SEO Settings inside Search Atlas, not through robots.txt or noindex tags. This article explains how to set up OTTO-specific exclusions, clarifies whether OTTO changes are permanently written to your site, and covers how OTTO's reporting and integration features work. ⚠️ OTTO Exclusions vs. robots.txt — Key Difference A common point of confusion is the difference between site-wide crawl rules and OTTO-specific exclusions. - robots.txt / noindex tags — These are server-level directives that instruct all crawlers (Google, Bing, OTTO, etc.) how to behave. Editing robots.txt does not exclusively affect OTTO and is not the correct method for managing what OTTO processes. - URL Exclusion conditions — These are exclusion rules configured entirely within Search Atlas. They tell OTTO which URLs to skip during its crawl and optimization passes, without touching your site's server configuration or affecting other crawlers. Always use URL Exclusion conditions when you want to control what OTTO specifically crawls or optimizes. 🚫 How to Exclude Pages from OTTO Crawl 1. In the left sidebar, click OTTO SEO and open SEO Automation (All Sites view at /seo-automation-v3), then open your project. 2. At the top of the project overview, click the Autopilot / Smart Crawl card to open the OTTO SEO Settings modal. You can also reach it from the All Sites table by clicking the Smart Crawl status text on your site's card. 3. Scroll to URL Exclusion conditions and click + Add condition. 4. Set the condition to Exclude all URLs that Contains (or Start With) the text you want to skip — for example, Contains /es/ excludes all Spanish-language pages under a language subdirectory. 5. Click Update Settings. When your exclusion rules are saved with Update Settings, OTTO will skip all matching URLs during its next crawl cycle. Any optimizations OTTO had already applied to those pages before the exclusion was added will remain in place unless you manually revert them. 🔄 Dynamic vs. Permanent Changes A frequent question is whether OTTO's optimizations are written permanently to your site. - Dynamic changes — Some OTTO optimizations are applied dynamically and are managed through Search Atlas. If you disconnect OTTO or remove a rule, those changes can be rolled back without a permanent edit to your CMS or server files. - Permanent changes — Other optimizations (such as those pushed directly to your CMS) are written to your site and persist independently of OTTO. These require manual intervention to revert. If you are unsure whether a specific OTTO action is dynamic or permanent, contact our support team before making changes. 📊 Reporting and Integrations OTTO provides reporting on the optimizations it has applied across your project. You can review which pages have been processed, which changes are active, and track the impact of OTTO's work over time. OTTO also integrates with your CMS, allowing certain optimizations to be pushed directly to your site from within Search Atlas. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 PRO Plan OTTO Activations Explained

🔍 Quick Answer The Search Atlas PRO Plan includes 4 OTTO activations. If you have seen or been told that the PRO Plan includes 10 activations, that information is incorrect. This article explains what an activation is, how to check yours, and what to do if you need more. 💡 What an OTTO Activation Is An OTTO activation connects OTTO SEO to one project in your Search Atlas account. Once activated, OTTO analyzes the connected website and begins implementing SEO improvements automatically. Key points to remember: - Each activation covers one project (one website). - Activations are tied to your plan tier, not to individual users on your team. - The PRO Plan includes 4 OTTO activations. - Higher-tier plans include more activations — you can compare options under Billing. 📊 How to Check Your Remaining Activations To see how many OTTO activations your plan includes and how many you have used: 1. Click your avatar in the top-right corner of the platform. 2. Select Billing from the Avatar Menu (👤). 3. Open the Plans & Top-ups tab. 4. Review your current plan details, including your OTTO activation total and remaining balance. To see which projects already have OTTO connected, go to Home in the left sidebar and review your selected projects list. 🚀 How to Get More Activations If you manage more than four websites and need additional OTTO activations, you can move to a higher-tier plan: 1. Click your avatar in the top-right corner and select Billing. 2. Open the Plans & Top-ups tab. 3. Click Change Plan or Manage Subscription. 4. Compare the available plans and select the one that matches the number of activations you need. All billing details are shown on screen before you confirm any plan change, so you can review costs and timing before committing. ⚠️ If You Were Told the Limit Is 10 Some earlier conversations and third-party materials incorrectly stated that the PRO Plan includes 10 OTTO activations. The accurate number is 4. If this discrepancy has affected your setup or purchase decision, we recommend the following: - Verify your current plan and activation count under Billing → Plans & Top-ups. - If you need more than 4 activations, follow the upgrade steps in the section above. - If you believe your account or purchase was made based on incorrect information, reach out through the chat widget so our team can review your situation. 💬 Contact Support If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🔗 Add Service Pages to OTTO Links

🔗 Overview OTTO SEO’s Internal Link Suggestions tool does not automatically import service or location pages from Brand Vault. To use these pages in link recommendations, add each one manually through Add Page. 📍 Open Internal Link Suggestions 1. In the Search Atlas left sidebar, select OTTO SEO. 2. Open the Internal Link Suggestions section. 3. Select Add Page to create a suggestion. ➕ Add a Service or Location Page 1. In the Destination page field, enter the service or location page you want to promote. 2. In the Source page field, enter the page where OTTO should place the internal link. 3. Review both URLs to confirm they are correct and use the preferred versions of the pages. 4. Save the suggestion. Repeat these steps for each service and location page. For example, you can set a service page as the destination and a related city or blog page as the source. ✅ Check Your Suggestions After saving the entries, review the Internal Link Suggestions list to confirm that each destination page has an appropriate source page. Use relevant page pairings so visitors and search engines can easily discover related content. 💡 Important Limitation Content Genius may not show your complete list of service and location pages because these pages are not automatically imported from Brand Vault into Internal Link Suggestions. This is expected behavior. Adding the pages manually is currently required. 🛠️ Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

⚙️ Make OTTO Changes Permanent in WordPress

🔍 How OTTO changes appear on your site OTTO can apply SEO changes in two ways. A change may be served by OTTO without being saved to your WordPress SEO plugin, or it may be written into supported plugin fields using Sync to CMS. To make supported changes persist in WordPress, enable Sync to CMS before deploying them. ⚙️ Enable Sync to CMS 1. In Search Atlas, open OTTO SEO from the left sidebar. 2. Find the Sync to CMS setting and turn it on. 3. Deploy the OTTO changes you want saved to WordPress. Sync to CMS applies only to supported fields. Changes that are not supported may still be served by OTTO without being saved to your WordPress SEO plugin. 🔄 If deployed changes are not showing - Confirm that Sync to CMS was enabled when you deployed the changes. Turning it on afterward may not save changes that were already deployed; redeploy them with the setting enabled. - Check the corresponding fields in your WordPress SEO plugin to see whether the values were written there. - Allow the site to refresh, then reload the page and check the result again. - If the values are saved in WordPress but the live page still shows old content, check whether your site or browser is showing a cached version. ⚠️ Before undeploying changes Undeploying OTTO changes may not restore the values that were in WordPress before OTTO updated them. Review and record existing values before deploying, and check the WordPress SEO plugin after undeploying. Do not assume undeploying will restore previous values automatically. 💬 Need help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

How to Understand Marquee Publisher Catalog Listings

This article explains why the Marquee publisher catalog may appear to list fewer sites than its description suggests, and how to correctly read and verify publisher domain authority (DA) data within the platform. 🔍 Common Causes of the Discrepancy - DA thresholds are minimums, not guarantees of volume: A catalog tier described as "DA 90+" means every listed site meets that floor — it does not promise a large number of results. There may genuinely be only one or a handful of publishers at that authority level at any given time. - Live inventory, not a static list: The publisher catalog reflects real-time availability. Publishers can enter or exit the marketplace, so the count you see today may differ from what the description was written against. - Catalog copy describes eligibility criteria, not quantity: The description sets the quality bar for inclusion, not a count of how many publishers currently qualify. - Active vs. paused publishers: Some publishers meeting the DA threshold may temporarily pause their listings, reducing the visible count without changing the catalog's stated criteria. 🛠️ Step-by-Step 1. Open the platform and navigate to the publisher marketplace area. Look for a publisher catalog or marketplace section within the main navigation — consult the platform's navigation menu to locate the correct area for your account type. 2. Locate the Marquee tier or catalog section and confirm you are viewing publisher listings, as different views may display different data sets. 3. Check any active filters applied to the catalog view (such as niche, language, or DA range). A narrower filter combination can reduce results even within a high-DA tier — try removing filters one by one, or reset all filters, to see a broader result set. 4. Note the DA value displayed for each publisher. Confirm whether the catalog description means strictly above 90 or 90 and above, as this affects which sites appear. 5. If you need to compare the catalog count over time, revisit the same view on different days to observe whether additional publishers are added as inventory updates. ✅ What to Check If Results Still Seem Low After removing all active filters and confirming you are viewing the correct catalog section, check the following: - Verify that no niche, language, or DA range filters remain applied — even a single active filter can significantly reduce visible results within a high-DA tier. - Consider that the total number of publishers at very high DA levels (e.g., DA 90+) is inherently limited across the web, so a small result set may accurately reflect real-world availability rather than a platform error. - If the count appears unexpectedly low even with no filters applied, note the exact tier name, any DA range shown, and the number of results visible, then escalate so the team can verify current inventory on the back end. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⬇️ Download OTTO Optimization Suggestions for Offline Viewing

Overview OTTO generates SEO optimization suggestions directly inside the Search Atlas platform. If you want to review these suggestions offline or share them with a colleague, you may be looking for a way to export or download them. This article explains what options are currently available. What Are OTTO Optimization Suggestions? When you create an OTTO project, OTTO analyzes your site and produces a prioritized list of SEO recommendations covering areas such as on-page content, technical fixes, schema markup, and more. Having a downloadable copy of these suggestions lets you review or share them outside the platform. Is There a Download or Export Option for OTTO Suggestions? Currently, there is no built-in one-click export or download button for OTTO optimization suggestions within the platform. The ability to download or export suggestions in formats such as CSV or PDF is not a standard self-serve feature available to all users at this time. If you need a record of your OTTO suggestions for offline review or sharing, here are the recommended approaches: 1. Use your browser's print or save function. Navigate to your OTTO project and open the suggestions list. Then use your browser's built-in print function (Ctrl+P on Windows or Cmd+P on Mac) and select Save as PDF as the destination. This lets you capture the current view of your suggestions as a PDF file. 2. Take screenshots of each suggestion category. Browse through the suggestion tabs (for example, on-page, technical, schema) and screenshot each section for offline reference. 3. Copy suggestion text manually. You can select and copy the text of individual suggestions from the platform and paste them into a document or spreadsheet for sharing with colleagues. Requesting Export Assistance from Support If none of the above workarounds meet your needs, or if you believe a download option should be available on your account or plan, our support team can review your specific setup and advise on any additional options. When you reach out, please have the following ready: - The name of your OTTO project - The type of suggestions you are trying to download (for example, on-page, technical, or schema) - Any error message or unexpected behavior you have encountered - A screenshot of the area in the platform where you expected to find a download or export option Frequently Asked Questions Can I download suggestions from multiple OTTO projects at once? There is no bulk export feature currently available. The browser print-to-PDF method works on a per-project, per-view basis. Is a native export feature planned? If you would like to see a dedicated download or export feature added to OTTO, let our support team know — customer feedback helps inform future product updates. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ On-Page Audit Content Optimization and Publishing Workflow

📋 Overview The On-Page Audit tool in Search Atlas analyzes your existing web pages and provides actionable SEO recommendations to improve their performance. A common question from customers is whether the tool updates existing pages or creates new content. This article explains how the optimization and publishing workflow operates so you can get the most out of your audit results. 🔍 What the On-Page Audit Tool Does The On-Page Audit tool scans pages on your website and evaluates them against a range of on-page SEO factors. It does not automatically create new blog posts or add new pages to your site. Instead, it focuses on improving the content and structure of your existing pages—including service pages, landing pages, and any other URLs you submit for analysis. The audit checks for issues and opportunities across areas such as: - Title tags and meta descriptions - Heading structure (H1, H2, H3) - Keyword usage and content relevance - Internal linking opportunities - Page speed and technical signals - Content length and readability ⚙️ How the Optimization Workflow Works To run an On-Page Audit and act on the recommendations, open your project in Search Atlas and navigate to the On-Page Audit section of the platform. 1. Submit the URL of the page you want to audit. This is typically an existing service page, homepage, or key landing page. 2. Review the audit results. The tool surfaces prioritized recommendations grouped by issue type and potential SEO impact. 3. Apply the suggested changes directly to your existing page in your CMS or website editor. The audit tells you what to change; you implement the edits on your live site. 4. Re-run the audit after publishing your changes to confirm the issues have been resolved and your score has improved. 📝 Does the Tool Create New Blog Posts? No. The On-Page Audit tool is designed to optimize existing content, not generate new pages or blog posts from scratch. If you need to create new content, Search Atlas offers separate content creation tools within the platform that are better suited for drafting new articles or blog posts. Think of the On-Page Audit as a quality-improvement layer for pages that already exist on your site—it helps you get more out of what you have already published. 🚀 Publishing Your Optimized Content Search Atlas provides the recommendations and optimized content suggestions, but you control when and how changes go live. The platform does not directly push edits to your website. Here is the typical publishing flow: 1. Review the recommendations inside the audit results for the submitted URL. 2. Make the corresponding edits in your own CMS or website editor. 3. Publish the changes through your CMS as you normally would. 4. Return to the On-Page Audit tool and re-run the audit to verify your improvements. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

SOP: Creating and Optimizing Landing Pages with Search Atlas OTTO

This guide walks you through creating an SEO-optimized landing page, importing competitor insights, structuring content, and deploying a functional page. What you need - Search Atlas - OTTO (AI-powered SEO and Landing Page builder) - Google Docs (for optional content review) - WordPress (if publishing via CMS) Watch the session replay here! How do I research and select a target website? - Identify a niche and location for your landing page. Example: Roofing services in Las Vegas. - Use Google Search to find a struggling website (preferably ranking on Page 2 or lower). - Open the competitor's website and analyze its content gaps. How do I set up a folder in Search Atlas? - Create a new project folder for the client or business in Search Atlas. - Enter the following details: - Website URL - Business Purpose (e.g., Attract homeowners in Las Vegas for roofing services) - Niche (Roofing) - Target Audience (Homeowners in Las Vegas) - Search Intent (Commercial, Navigational, Transactional) - Business Intent (Service-based) - Company Background (Extract details from the homepage, About Us, and Google Business Profile) - Preferred AI Model (Claude recommended for less AI artifacts) - Writing Parameters: - Tone: Professional, Third-person - Act as: A roofing contractor - Reading Level: 8th grade - Content Length: Short (Landing page focused) - Writing Style: Helpful, Informative, Persuasive - FAQs: Short - Tables & Lists: Enabled - Short Paragraphs: Enabled - Internal & External Linking Strategy: - Required Links: Homepage, Service Page, Contact Page - Optional Links: Additional service pages if relevant How do I research competitors and keywords? - Use Search Atlas Site Explorer to analyze a top-ranking competitor’s page. - Find top-ranking keywords for a similar service page. - Export competitor keyword data (high volume, high CPC, non-branded). - Select the primary keywords for the landing page (e.g., "roof repair Las Vegas"). - Import the page you are working on into Content Genius: - Input the client’s URL. - Skip this step if starting a new page from scratch! - Set the Location (Las Vegas, NV). - Add Primary and Related Keywords. - Create an Article Draft for optimization. - Analyze Content Score: - Review current content against competitors. - Compare word count, entity usage, and structure. - Use entity extraction to improve content quality. How do I create an AI-optimized landing page? Structure the landing page content - Select "Landing Page" mode in Search Atlas Content Genius. - Generate an outline (review headings, sections, and ordering). - Modify or add headings to match the desired page layout. - Ensure proper CTAs (Call-to-Actions) are placed strategically. - Include testimonials, social proof, awards, and FAQs for conversion optimization. - Embed internal links where relevant. Optimize for entities and SEO - Remove irrelevant entities (e.g., locations not related to the target area). - Include People Also Ask questions for additional FAQ content. - Generate AI images relevant to the business (e.g., "Roofer working on a Las Vegas home"). Generate content using AI - Use "Write with AI" (customized outline). - Ensure contextual references (company details, awards, etc.). - Proofread and refine the content for accuracy. How do I deploy and publish the landing page? Preview and edit the AI landing page in OTTO - Use the Landing Page Generator in OTTO. - Define Page Name, City, and Services Offered. - Select Color Palette (or let AI suggest one). - Set up Hero Section with an image and CTA. - Define Page Layout (Zigzag headers, Testimonials, FAQs, Google Maps embed, Contact Form). - Sample Prompt: “Hero section with a high quality image of a roofer. Include a click to call button in the hero section. Create 4 zig zag headers with CTAs under each. Include a customer testimonial section. Include a FAQ section. Include a Google Map Embed. Include a contact form at the bottom of the page.” - Generate the landing page layout. - Modify sections as needed (Edit HTML for fine-tuning). Export and implement the landing page - If using WordPress: - Use WordPress Sync to publish the page. - Select Publish as a new post or Sync to an existing page. - If using a custom CMS: - Export as HTML. - Open in a code editor or visualization tool. - If using a static site builder: - Copy and paste the AI-generated content into the site template. Final review and approval - Assign a team member to review and approve the content. - Ensure compliance with brand voice and SEO best practices. - Publish the page and monitor organic rankings and traffic. How do I monitor and iterate on the landing page? - Track performance metrics: - Content Score Improvements - Keyword Rankings - Click-Through Rate (CTR) - Conversion Rate - Update content periodically based on competitor movements and Google updates. - Use A/B Testing for variations in CTAs, headlines, and images. Additional notes - If the client lacks budget for custom design: - Use OTTO’s AI Landing Page Builder for a cost-effective solution. - Modify generated pages to align with brand guidelines. - For high-touch clients: - Develop custom templates in WordPress/Figma for better aesthetics. - For PPC landing pages: - Keep content concise and conversion-focused. - Apply No-Index tags to prevent organic ranking conflicts.

✨ Content Optimization with OTTO

OTTO's Content Optimization feature automatically enhances your web pages by adding NLP (Natural Language Processing) entities and relevant semantic terms. These additions help search engines better understand the context and depth of your content, leading to improvements in topical relevance, topical authority, and overall content quality. Here is what OTTO does when it optimizes your content: - Adds NLP entities: OTTO identifies and incorporates named entities — such as people, places, concepts, and organizations — that are semantically related to your page's topic. This signals to search engines that your content is comprehensive and contextually accurate. - Inserts relevant semantic terms: Beyond exact keywords, OTTO weaves in semantically related terms and phrases that naturally belong in a well-rounded discussion of your topic, helping your page cover the subject more thoroughly. - Improves topical relevance: By aligning your content more closely with the language and concepts search engines associate with your target topic, OTTO helps your pages rank for a broader and more meaningful set of queries. - Strengthens topical authority: Consistently optimized pages signal to search engines that your site is a credible, authoritative source on the topics you cover. - Raises content quality: The additions OTTO makes are designed to make your content more useful and complete for readers, not just for algorithms. Content Optimization runs as part of OTTO's automated workflow, so enhancements are applied directly to your web pages without requiring you to manually research or insert each term yourself. If you have questions about how Content Optimization is being applied to a specific page, or if you notice anything unexpected, feel free to chat with a human teammate using the live chat widget in the app.

🔍 How Search Atlas Swaps Page Elements and What Google Sees

When Search Atlas optimizes your pages through OTTO, it applies changes via JavaScript using the OTTO pixel script. This script is injected into the <head> tag of your site and makes updates directly in the browser at render time. Because of this approach, your underlying source code is never modified — meaning you will not see OTTO's changes if you right-click and view the raw page source. Despite this, Google can still read and index all changes OTTO applies. When Googlebot crawls your site, it executes JavaScript before reading the fully rendered HTML, just as a modern browser would. This means updates to the following elements are visible to Google during indexing: - Page titles and meta descriptions - Headings (H1, H2, etc.) - Internal and external links - Image alt text - Meta tags and canonical tags To verify what Google has actually indexed for your pages, check your pages in Google Search Console (GSC). Connecting GSC to Search Atlas is also recommended, as it provides deeper insights into how your optimizations are performing. If you want to confirm that OTTO's changes are being applied correctly before Google re-crawls your pages, open your browser's Developer Tools and navigate to the Elements panel. This panel shows the fully JavaScript-rendered version of your page, so any changes OTTO has applied will appear there. You can also install the Detailed SEO Extension, run it on your page, and confirm whether your updated titles, headings, meta tags, and other elements are live. One important benefit of OTTO's dynamic overlay approach is that your original backend code — for example, your WordPress templates and database — is never touched. Your source code remains completely unaffected regardless of your subscription status, which helps maintain the overall integrity and stability of your site. If you have additional questions about how OTTO applies changes to your specific site setup, feel free to chat with a human teammate directly through the in-app live chat widget.

🔄 Manual Reprocess in OTTO: What It Does, Where to Find It, and When to Use It

The Manual reprocess action in OTTO allows you to manually trigger a reprocessing of your OTTO project. This option is useful only when significant changes are made to your site and you want OTTO to reprocess the project before the next automatic cycle. This article explains: - Where to find Manual reprocess - What it does (and does not do) - Usage limits - When escalation is not required 📍 Navigation Path Search Atlas → OTTO SEO → OTTO SEO → All Sites → Select a website → Recommendations → Manual reprocess 🧭 Where to Find Manual Reprocess (UI Location) The Manual reprocess button appears: - Inside the OTTO SEO module - After selecting a specific site - Within the Recommendations section - At the top of the recommendations panel - Positioned next to the section title “Recommendations” 📝 Official Description Hovering over the button displays the following tooltip: “Click to manually reprocess your OTTO project. This action is useful when significant changes are made to your site. It can be triggered once every 24 hours.” ⚙️ What Manual Reprocess Does 1. Triggers a manual reprocessing of the selected OTTO project 2. Re-evaluates the project after significant site changes 3. Applies only to OTTO 4. Does not affect other Search Atlas tools ⏱️ Usage Limits and Cooldown 1. Manual reprocess can be triggered once every 24 hours 2. If the button was already used: - It cannot be triggered again until the 24-hour window has passed 3. This cooldown is expected behavior ❓ FAQs ❓ When should I use Manual Reprocess? When significant changes are made to your site, as stated in the tooltip. ❓ Why can’t I click Manual Reprocess again? The action is limited to once every 24 hours. ❓ Does Manual Reprocess mean something is broken? No. It is a manual control, not an error state. ❓ Do I need to contact support if it’s on cooldown? No. Cooldown behavior is expected and does not require support. Manual reprocess is a controlled, rate-limited action designed to reprocess an OTTO project after meaningful site changes. If it has already been triggered within the last 24 hours, waiting is the correct and expected next step.

🔍 OTTO Heading Optimization Hidden Injection Explained

🔍 What Is the Hidden Heading Injection? When OTTO Heading Optimization is active on your site, it injects a dedicated heading module near the closing </body> tag. This module renders your optimized heading content using display:none CSS. This is intentional, hardcoded behavior — not a deployment error. The tooltip inside the OTTO interface confirms this design. The injected module serves a specific structural role within OTTO's optimization architecture and is present on every correctly deployed site using this feature. ✅ Is display:none Content Safe Under Google Guidelines? Yes — when used for legitimate structural or technical purposes, hidden content is fully acceptable under Google's policies. Google's guidelines distinguish between hidden content designed to deceive users or manipulate rankings (which violates spam policy) and hidden content used for structural or technical scaffolding (which does not). OTTO's heading injection falls into the latter category for three key reasons: - No keyword stuffing: The injected headings mirror the same optimized heading structure applied to your visible page content. No extra or manipulative keywords are introduced. - Not deceptive: The hidden module does not present content to users that differs from what Googlebot indexes in context. The intent is structural, not manipulative. - Consistent with the rendered DOM: Google crawls the fully rendered page. The injected headings are consistent with OTTO's overall on-page heading strategy and do not create a conflict between visible and crawled content. Hidden content used as a technical scaffold — where there is no intent to hide keyword-stuffed text from users while showing it to search engines — is not treated as a violation of Google's spam policies. 📍 How to Confirm the Injection Is Working Correctly If you want to verify that the heading module was deployed successfully, inspect your page source directly: 1. Open your site in a browser and press Ctrl + U (Windows) or Cmd + Option + U (Mac) to view the raw page source. 2. Use Ctrl + F / Cmd + F to search for otto or your heading text near the bottom of the source. 3. Confirm that a heading module containing your target heading tags (H1, H2, H3, etc.) appears near the closing </body> tag with display:none styling applied. If the module is present and contains your configured headings, the deployment is correct and functioning exactly as designed. ⚙️ How to Edit, Add, or Roll Back Headings You can adjust or remove OTTO's heading optimizations at any time without contacting support: 1. In the left sidebar, navigate to OTTO SEO → Tasks. 2. Find the Heading Optimization task for the page you want to update. 3. To edit headings, open the task, update the heading values in the editor, and redeploy. 4. To add headings manually, use the task editor to include additional heading tags, then save and redeploy. 5. To roll back, open the task and select the revert or undo option. OTTO will remove the injected heading module from your page source on the next deployment cycle. You can monitor deployment progress and confirm changes have gone live under OTTO SEO → All Sites (SEO Automation). 💡 Quick Reference: Key Facts - The display:none heading module near </body> is hardcoded, intended behavior — not an error or failed deployment. - It is SEO-safe and consistent with Google's guidelines because it is structural, not deceptive. - The OTTO platform tooltip confirms this design explicitly. - Headings can be edited, supplemented, or fully reverted at any time from OTTO SEO → Tasks. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚙️ OTTO Deployment, Lucky Button, and Dynamic Indexing Explained

🔍 Overview OTTO is Search Atlas's OTTO SEO automation engine. It can generate technical SEO elements such as meta descriptions and headings, and it can deploy them to your site — but generation and deployment are two separate steps. This article explains the full workflow, the I'm feeling lucky button, credit costs, and how Dynamic Indexing appears to your users. 🛠️ How OTTO Generates SEO Elements OTTO can automatically generate the following on-page SEO elements for your site pages: - Meta titles - Meta descriptions - H1 headings - H2 and H3 subheadings - Image alt text - Schema markup suggestions To access OTTO, go to OTTO SEO → SEO Automation in the left sidebar (URL: /seo-automation-v3). From there, select your connected site and navigate to the relevant task category to view generated recommendations. OTTO generates suggestions based on your existing page content, target keywords, and SEO best practices. Each suggestion is queued for your review before anything is applied to your live site. ✅ Generation vs. Deployment: What Is the Difference? These are two distinct steps and it is important to understand both: 1. Generation: OTTO analyzes your pages and produces SEO element suggestions. This happens automatically once OTTO is connected and activated for your site. No changes are made to your live site at this stage. 2. Deployment: You review the generated suggestions and choose to approve and deploy them. Deployment pushes the changes to your site. By default, OTTO does not deploy changes without your approval. This two-step process ensures you maintain full control over what goes live. OTTO is designed to assist your workflow, not replace your editorial judgment. 🍀 How the 'I'm Feeling Lucky' Button Works The I'm feeling lucky button is a bulk-action shortcut available inside the OTTO dashboard. Here is exactly what it does: - It automatically approves and queues all currently generated suggestions across the selected task category for deployment in one click. - It does not skip the deployment mechanism — it simply removes the need to approve each suggestion individually. - It applies only to suggestions that have already been generated and are waiting in your review queue. It does not trigger new generation. Important limitations to know before using this button: - Once you click I'm feeling lucky, the batch approval cannot be undone in bulk. You would need to revert individual changes manually. - It is best suited for sites where you have already reviewed a sample of OTTO's output quality and are confident in its recommendations. - This button does not bypass credit consumption. Credits are still used per deployment action. 💳 Credit Costs for OTTO Actions OTTO actions consume credits from your Search Atlas plan. Here is how credits apply: - Generation: Generating suggestions consumes credits based on the number of pages analyzed and elements produced. - Deployment: Deploying approved suggestions also consumes credits. Using I'm feeling lucky to deploy in bulk will consume credits proportional to the number of changes deployed. - You can monitor your remaining credits inside your account settings at any time. If you are concerned about credit consumption before using bulk deployment, review a sample of OTTO's suggestions first and use selective approval for your most important pages. 🚫 Can OTTO Deploy Changes Without Manual Verification? Currently, OTTO does not fully auto-deploy without any human interaction. The workflow always produces a review queue that requires at least one explicit action from you — either approving suggestions individually or using the I'm feeling lucky button to approve all at once. There is no setting at this time that causes OTTO to detect, generate, and deploy SEO elements to your live site in a fully automated loop without any user input. This is an intentional safeguard to protect site quality and give you editorial control. 📡 Dynamic Indexing: What It Is and Who Can See It Dynamic Indexing is a Search Atlas feature that helps accelerate the discovery and indexing of your site's pages by search engines. It works by intelligently signaling updated and new content so that crawlers prioritize those pages. Is Dynamic Indexing visible to your end users (site visitors)? No. Dynamic Indexing operates entirely at the technical infrastructure level. It involves interactions between Search Atlas, your site's sitemap or API endpoints, and search engine crawlers. Your site visitors do not see any interface, badge, or indicator related to Dynamic Indexing. What you can see as a Search Atlas user: - Indexing status reports inside the OTTO dashboard showing which pages have been submitted and their crawl status. - Logs of indexing requests sent on your behalf. - Page-level visibility into which URLs are pending, indexed, or flagged for re-indexing. To review Dynamic Indexing activity, go to OTTO SEO → SEO Automation in the left sidebar and select your site, then navigate to the Indexing section within OTTO's task panel. 📋 Quick Reference Summary - OTTO generation: Automatic, produces a review queue, no live changes yet. - OTTO deployment: Requires your approval — individual or via I'm feeling lucky. - I'm feeling lucky: Bulk-approves all queued suggestions for deployment in one click; cannot be bulk-undone. - Auto-deploy without verification: Not currently available. - Credits: Consumed at both generation and deployment stages. - Dynamic Indexing: Invisible to site visitors; fully technical and backend-facing. 💬 Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Rescan Your Site and Run SEO Diagnostics

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

📌 Install the OTTO SEO Pixel on LearnWorlds

🔍 Overview You can install the OTTO SEO pixel on a LearnWorlds site that uses a custom domain. The pixel must be placed in the header section of your LearnWorlds site — not the body. This article walks you through finding your pixel code in Search Atlas and adding it correctly inside LearnWorlds. 🧭 Step 1: Copy Your OTTO SEO Pixel Code 1. Log in to your Search Atlas account. 2. In the left sidebar, click OTTO SEO, then open SEO Automation. 3. Locate your OTTO SEO pixel code. It is a short script snippet unique to your website. 4. Click to copy the pixel code. 🌐 Step 2: Confirm Your Custom Domain Is Active in LearnWorlds Before installing the pixel, make sure your custom domain is fully connected and active in LearnWorlds. If the domain is still propagating or not yet verified, the pixel will not fire correctly. 1. Log in to your LearnWorlds admin dashboard. 2. Go to Settings → Domain and confirm your custom domain shows a verified or active status. 📋 Step 3: Add the Pixel to the LearnWorlds Header The OTTO SEO pixel must go in the header of your LearnWorlds site. Placing it in the body will cause it to load incorrectly and tracking data will not be recorded. 1. In your LearnWorlds admin dashboard, navigate to Settings → Tracking Scripts (sometimes labelled Custom Scripts or Head Code depending on your LearnWorlds plan). 2. Locate the field labelled Header, Head Code, or Custom Head Scripts. 3. Paste your OTTO SEO pixel code into that field. 4. Save your changes. Important: Do not paste the pixel code into any field labelled Body, Footer, or Custom Body Scripts. The pixel will only work correctly when loaded from the header section. ✅ Step 4: Verify the Pixel Is Firing After saving, confirm the pixel is active: 1. Return to OTTO SEO in the left sidebar and open SEO Automation in Search Atlas. 2. Check the pixel status indicator for your site. It may take a few minutes to update after installation. 3. Visit your LearnWorlds site in a browser, then reload the Search Atlas pixel status. A green or active status confirms the pixel is receiving data. If the status does not update after 10–15 minutes, clear your browser cache, revisit your LearnWorlds site, and check again. ⚠️ Common Mistakes to Avoid - Placing the pixel in the body: The OTTO SEO pixel must be in the header. Body placement is incorrect and will prevent the pixel from working. - Adding the pixel before the custom domain is active: Always verify your custom domain is live in LearnWorlds before installing the pixel. - Pasting the pixel in a page-level editor: Use the site-wide header scripts field, not a single page's custom code block, unless you intentionally want tracking on one page only. - Duplicating the pixel code: Only paste the pixel once. Multiple instances can cause tracking conflicts. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔄 Sync Custom Post Types in OTTO Categories

🧭 Overview By default, OTTO's category dropdown shows a standard set of WordPress content types — typically Blog, Procedures, and Locations. If your WordPress site uses custom post types (such as Articles, Projects, or Services), they may not appear automatically. This article explains why this happens and how to get your custom post types recognised by OTTO. 🔍 Why Custom Post Types Don't Appear OTTO syncs with WordPress through the Search Atlas plugin. For a custom post type to appear in the OTTO category dropdown, it must meet two conditions: - It must be set to publicly queryable in WordPress. - It must be exposed via the WordPress REST API. Many custom post types are registered without these settings enabled, which prevents OTTO from detecting them during a sync. 🛠️ How to Enable Your Custom Post Type Follow the steps below to make your custom post type visible to OTTO. You will need access to your WordPress theme's functions.php file or the plugin that registers the custom post type. 1. Locate the registration code for your custom post type. This is usually found in your theme's functions.php file or in a dedicated custom plugin. 2. Find the register_post_type() call for the post type you want to sync (for example, articles). 3. Ensure the following arguments are set to true inside the arguments array: - public — makes the post type visible on the front end. - show_in_rest — exposes the post type to the WordPress REST API. - publicly_queryable — allows WordPress to serve queries for this post type. 4. Save your changes and update the file on your server. 5. Re-sync your WordPress site with Search Atlas. Navigate to OTTO SEO in the left sidebar, open All Sites (SEO Automation), select your individual project, and trigger a fresh sync. 6. Open the OTTO category dropdown — your custom post type should now appear as a selectable option for auto-sync. 💡 Example: Registering an "Articles" Post Type Correctly If you are registering a custom post type called articles, your register_post_type() call should include the following arguments at a minimum: - public → true - show_in_rest → true - publicly_queryable → true If you are using a plugin such as Custom Post Type UI (CPT UI) or Pods to create post types, you can update these settings directly in the plugin's interface without editing code. Look for options labelled Public, Show in REST API, and Publicly Queryable within the post type settings screen. ✅ Confirming the Sync Worked After completing the steps above, verify the setup was successful: 1. Go to OTTO SEO in the left sidebar of Search Atlas, then open All Sites (SEO Automation) and select your individual project. 2. Open your OTTO project and navigate to the category dropdown in the auto-sync settings. 3. Confirm your custom post type (e.g. Articles) now appears in the list. 4. Select it and save your auto-sync preferences. ⚠️ Common Issues - Post type still not showing after sync — Double-check that show_in_rest is explicitly set to true. Omitting this argument defaults to false in most WordPress setups. - Using a page builder or third-party plugin — Some plugins register post types late in the WordPress load order. Ensure there are no conflicts by deactivating other plugins temporarily to test. - Caching issues — Clear any server-side or plugin-based cache after making changes, then re-trigger the sync in Search Atlas. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚡ Bulk Deploy Meta Descriptions in OTTO SEO

Overview OTTO SEO allows you to generate, review, and deploy meta descriptions in bulk — so you don't have to update pages one by one. This article explains the general process for bulk deploying meta descriptions through OTTO SEO automation. Before You Start Make sure the following conditions are met before attempting a bulk deployment: - Your site is connected to OTTO SEO and OTTO is active. - Your WordPress integration is connected and syncing correctly (if applicable). - You have navigated to OTTO SEO → All Sites (SEO Automation) via the left sidebar in the platform. How to Bulk Deploy Meta Descriptions 1. Open OTTO SEO. In the left sidebar, click OTTO SEO → All Sites (SEO Automation) to open the automation dashboard. 2. Locate the Meta Descriptions section. Within OTTO SEO, navigate to the section where meta description suggestions are displayed for your pages. 3. Generate suggestions if needed. If suggestions have not been generated yet, use the available option to generate AI meta description suggestions. Wait for the process to complete before proceeding, as generation may take a few moments depending on the number of pages. 4. Review your suggestions. Browse through the list and make any adjustments to individual meta descriptions before deploying. 5. Select the meta descriptions you want to deploy. Use the selection controls available in the interface to choose the meta descriptions you wish to deploy in bulk. 6. Deploy in bulk. Once your desired items are selected, use the deploy option. OTTO will push the selected meta descriptions to your site. If Bulk Deployment Does Not Behave as Expected If you experience issues during bulk deployment — such as only some meta descriptions being deployed, changes not appearing on your live site, or errors during the process — please reach out to our support team for assistance. When escalating, have the following ready: - Your project name and the site URL connected to OTTO SEO. - A description of what happened (e.g., how many meta descriptions you attempted to deploy and how many were actually applied). - Any error messages you saw, along with the approximate time the issue occurred. - Screenshots of the current state in OTTO SEO, if possible. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚡ On-Page Audit Workflow and British English Setup

Overview The On-Page Audit tool in Search Atlas analyses your existing web pages and provides optimisation recommendations. Two questions come up often: whether the audit creates new content or updates what you already have, and how to configure the tool to produce content in British English. This article covers both topics at a high level. Because the exact steps and UI labels can vary by account and platform version, we recommend contacting our team directly for a guided walkthrough tailored to your setup. What Does On-Page Audit Do to Your Content? On-Page Audit does not create a new blog post and does not overwrite your existing service page. Here is what actually happens: - The tool crawls the URL you submit and analyses the page as it currently exists. - It generates a report with recommendations — covering areas such as topical coverage, questions to address, and structural improvements. - Any content changes are your decision to make. The audit surfaces insights; it does not push edits to your live site automatically. Think of On-Page Audit as a diagnostic report, not an editor. You review the findings and then decide how to act on them — whether that means updating your existing page manually or using Content Genius to rework the content. Running an On-Page Audit The On-Page Audit tool is accessible from the Content section of the left sidebar. From there you can select or create an audit for the page you want to analyse, run the audit, and review the recommendations that appear. Once you have reviewed and acted on the recommendations, you can mark your progress within the tool to keep your workflow organised. Because button labels and navigation paths may differ depending on your platform version, please reach out to our support team if you are unsure where to find a specific option. Configuring Content in British English Search Atlas defaults to American English. To generate audit-driven content in British English, you need to set your language preference before generating or reworking content. This option is available within the content creation workflow in Content Genius. Look for a language or writing language setting within the content configuration area and select the British English option before generating your content. The output should then use British English spelling and conventions — for example, optimise instead of optimize, colour instead of color. Because the exact label and location of this setting can vary, we recommend contacting our team if you cannot locate it or if the output is not reflecting the correct language variant. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔄 Roll Back FAQs and Configure Page Types

🗺️ Overview OTTO SEO can automatically deploy FAQ schema to your pages to improve search visibility. However, you may want to remove FAQ schema from specific pages — such as your homepage — or adjust how a page is classified. This article explains the self-serve steps available to you and what to have ready if you need further help. ↩️ Rolling Back FAQs from a Page If you need to remove FAQ schema that was deployed to a page, follow these steps inside OTTO SEO: 1. Open your OTTO SEO project and navigate to the page you want to update. 2. Locate the FAQ schema task associated with that page in your task list. 3. Change the task status to roll back or disable the deployed FAQ schema for that URL. 4. Save your changes and confirm the schema has been removed by rechecking the page. If you do not see a rollback or disable option for the relevant task, this may require support assistance. In that case, please have the following ready: - The name of your OTTO SEO project - The exact URL(s) of the page(s) you want to roll back FAQ schema from - Confirmation of which schema type was deployed (e.g. FAQ schema) - Any error messages or unexpected behaviour you have observed, including timestamps if available 📋 Changing the Page Type of a Page OTTO uses the page type to determine which optimisations are appropriate for each URL. To update the page type for a page, follow these steps inside OTTO SEO: 1. Open your OTTO SEO project and find the URL you want to reconfigure. 2. Locate the page type setting for that URL. 3. Select the correct page type from the available options (for example, changing a page from a blog post type to a homepage type). 4. Save your changes and review the updated task list to confirm the correct optimisations are now shown for that page. If the page type option is not available or does not save correctly, please have the following ready when contacting support: - The name of your OTTO SEO project - The exact URL of the page you want to reconfigure - The current page type shown for that URL - The page type you believe is correct and why (e.g. the page is a homepage, not a blog post) 💡 Tips and Best Practices - Review your task list after any configuration change to confirm the correct optimisations are active for each page. - Check each URL individually if you need to roll back schema or update page types across multiple pages. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔄 OTTO SEO Sync to CMS Safe Deployment Guide

What Is Sync to CMS? Sync to CMS is an OTTO SEO feature that automatically pushes approved SEO changes directly to your connected WordPress site. Instead of manually copying recommendations into your CMS, OTTO can deploy them for you — saving time and reducing human error. Important: Sync to CMS currently works exclusively with WordPress sites via the Search Atlas WordPress plugin. It is not available for other CMS platforms at this time. What Gets Synced to Your CMS? When Sync to CMS is enabled, OTTO can push SEO changes — such as meta titles, descriptions, and schema markup — directly to your WordPress site through your connected SEO plugin. Current limitations to be aware of: - Some recommendation types, such as heading structure changes and internal link suggestions, are surfaced by OTTO but may require manual implementation in your page editor rather than being automatically synced. How Disabling Sync to CMS Affects OTTO Disabling Sync to CMS does not stop OTTO from generating or displaying recommendations. OTTO continues to crawl your site, identify SEO opportunities, and surface actionable suggestions in the platform. The only difference is that approved changes will not be automatically pushed to your WordPress site. This means: - All recommendations remain visible inside OTTO SEO - You retain full control over which changes go live and when - Your live site remains unchanged until you manually apply updates in WordPress Disabling sync is a safe and reversible action — you can re-enable it at any time from within the OTTO SEO settings area of the platform. Best Practices for Managing SEO Changes Whether you use Sync to CMS or prefer manual deployment, follow these best practices to keep your SEO strategy organised and risk-free: 1. Review before approving. Always read OTTO's recommendations in full before approving them. Take time to understand the scope of each suggested change before it is pushed to your live site. 2. Review changes at the page level. Where possible, check recommendations on a per-URL basis before approving changes at scale, so you can catch any issues early. 3. Approve in batches, not all at once. Start with lower-risk changes like schema markup and meta descriptions. Review heading and internal link changes separately and apply them manually in your CMS editor. 4. Check your SEO plugin settings. Confirm your WordPress SEO plugin is properly connected and that OTTO has the permissions it needs before enabling sync. 5. Monitor your site after syncing. After approving and syncing a batch of changes, review your site to confirm everything looks and performs as expected. If you are unsure whether a particular recommendation is safe to sync, disable Sync to CMS temporarily and apply the change manually first. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Control OTTO Title and H1 Tag Behaviour

🔍 Overview OTTO can automatically optimise page titles, H1 tags, and meta fields on your WordPress site. While this saves time, some workflows require that client-approved blog titles and headings remain untouched. This article explains how to prevent unwanted overwrites and how to troubleshoot duplicate H1 or HTML rendering issues without deactivating OTTO entirely. ⚙️ How OTTO Controls Titles and H1 Tags When OTTO is connected to a WordPress site, it can deploy changes to on-page elements including SEO titles (meta titles) and H1 tags. Because the exact behaviour depends on your site's configuration, SEO plugin, and page builder setup, the specific controls available to you may vary. Contact our support team to confirm exactly which elements OTTO is managing on your site before making changes. 🚫 How to Prevent OTTO from Overwriting Approved Titles If a client has approved specific blog titles or H1 text and you want to protect them while keeping OTTO active for other optimisations, the right approach depends on your site's specific OTTO configuration. Because the available controls vary by account setup, we recommend reaching out to our support team so they can identify the correct settings for your site and guide you through protecting specific fields — such as the SEO title or H1 — without disabling OTTO globally. When you contact support, please have the following ready: - The name of the project or site in Search Atlas - The specific pages or post types whose titles or H1s you want to protect - The SEO plugin installed on the WordPress site (e.g. Yoast, Rank Math, AIOSEO) - Whether you are using a page builder such as Elementor - A description of any changes OTTO has already made that need to be reviewed 🔁 Fixing Duplicate H1 Tags A duplicate H1 occurs when both the theme or page builder and OTTO independently render an H1 element on the same page. This can cause frontend display issues and may flag as an SEO error. To begin troubleshooting a duplicate H1, check the following in WordPress: 1. Open the affected page in your WordPress editor or page builder and inspect the page structure to confirm how many H1 elements exist. 2. If you are using a page builder, check whether the post title widget is set to output an H1 tag — if so, look for any additional H1 that may have been injected in the content area and remove it. 3. After saving, use a browser inspector or an SEO crawler to verify that only one H1 is rendered on the page. If the duplicate H1 persists after checking your page structure, contact our support team with the project name, the URL of the affected page, and a description of the issue so they can investigate the OTTO configuration on your account. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚡ Manage Multiple Sites, UX Signals, and Authority with OTTO

Overview Search Atlas is built with agencies and multi-site managers in mind. Under a single account, you can manage multiple client websites, monitor UX and Authority signals, and let OTTO SEO handle repetitive optimization tasks automatically. This article walks you through each capability so you can get the most out of the platform with minimal manual effort. Managing Multiple Client Websites Under One Account You do not need separate accounts for each client. Search Atlas supports multi-site management directly from your dashboard, allowing you to add and switch between client domains without logging out and back in. To add and manage client domains: 1. Log in to your Search Atlas account and go to your main dashboard. 2. Add each client website as a separate project within your account. 3. Switch between client projects directly from the dashboard — no separate logins are required. Search Atlas also offers white-label options that allow you to present the platform under your own agency branding. To learn more about enabling white-label features for your account, contact the Search Atlas support team via the chat widget. What Are UX Signals? UX (User Experience) signals are data points that reflect how real users interact with a website. Search engines use these signals as quality indicators when ranking pages. Key UX signals include: - Page load speed — how quickly your pages become usable for visitors. - Mobile usability — whether the site renders and functions correctly on mobile devices. - Engagement metrics — indicators such as bounce rate and time on page that suggest content relevance. - Core Web Vitals — Google's standardized metrics covering loading, interactivity, and visual stability. How to Improve UX Signals Improving UX signals does not require rebuilding your site. Focus on high-impact, targeted fixes: - Compress images and enable lazy loading to reduce initial page load time. - Use a content delivery network (CDN) to serve assets faster to users in different regions. - Fix mobile layout issues — tap targets, font sizes, and viewport settings are common culprits. - Minimize render-blocking resources such as undeferred JavaScript and CSS that delay page display. - Improve internal linking to help users and search engines navigate your content more effectively. How to Improve Authority Authority reflects how trustworthy and credible your domain appears to search engines. Improving it is a long-term effort centered on earning high-quality backlinks and building topical relevance. Steps to improve your Authority score: - Build backlinks from relevant, authoritative sites — use Search Atlas's backlink research tools to identify link opportunities in your niche. - Create linkable assets such as original research, guides, or tools that naturally attract links. - Remove or disavow toxic backlinks that may be dragging down your domain's credibility. - Develop topical depth by publishing clusters of content that thoroughly cover your core subject areas. - Monitor your Authority score over time inside Search Atlas to track progress as new links are acquired. Automating SEO Tasks with OTTO OTTO SEO is Search Atlas's automation layer that handles repetitive on-site optimization tasks so you can focus on strategy. Once activated for a project, OTTO continuously scans for issues and applies or queues fixes based on your settings. Common tasks OTTO can help automate include: - Generating and deploying meta titles and descriptions at scale. - Identifying and flagging technical SEO issues such as broken links, missing tags, and duplicate content. - Applying schema markup to eligible pages. - Surfacing recommendations for content and UX improvements across your tracked sites. To get started with OTTO on a project: 1. Open the project you want to automate inside Search Atlas. 2. Activate OTTO for that project and review the initial audit results. 3. Work through OTTO's prioritized recommendations or configure automatic deployment where available. 4. Repeat across each client project — OTTO settings are managed per project under your single account. If you are unsure which OTTO features are available on your current plan, contact the support team for clarification before making changes. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

✏️ Manually Edit Blank OTTO SEO Suggestions

🔍 Overview A recent OTTO SEO update temporarily removed the ability to manually edit fields where the AI had not yet generated a suggestion (blank or 0-suggestion fields). This affected Meta Titles, Meta Descriptions, and Headings. This capability has been fully restored. You can now manually enter your own content for any field where OTTO has not produced an AI-generated suggestion. 🛠️ How to Manually Edit a Blank Suggestion Field 1. In the left sidebar, navigate to OTTO SEO → SEO Automation (or go directly to /seo-automation-v3). 2. Find the page or URL that contains a blank or empty suggestion for a Meta Title, Meta Description, or Heading. 3. Click on the empty suggestion field. An editable input box will appear. 4. Type or paste your desired content directly into the field. 5. Click Save (or press Enter, depending on the field type) to apply your changes. Important: If you paste a value that exactly matches the title or tag already live on the page, the save may appear to complete without any visible change. This is expected behaviour — the system recognises the content is already live and no update is needed. If you want to confirm the save was applied, try a slightly modified version of the text, or refresh the page to verify the current live value. 📋 Which Fields Support Manual Editing - Meta Titles — editable on any page where OTTO has not generated a suggestion. - Meta Descriptions — editable on any page with a blank suggestion slot. - Headings (H1, H2, etc.) — editable when no AI suggestion has been produced for that heading field. 💡 Tips for Getting the Best Results - Let OTTO generate first where possible. AI-generated suggestions are based on your page content and keyword data. If a suggestion is blank, give OTTO a moment — it may still be processing, especially on newly added URLs. - Use the empty-state nudge. When a field is blank, OTTO now displays a prompt to help guide you. You can choose to wait for AI generation or fill in the field manually straight away. - Keep content within recommended limits. Meta Titles should be 50–60 characters, Meta Descriptions 120–160 characters, to avoid truncation in search results. - Manually entered content is not overwritten by OTTO. Once you save a manual edit, OTTO will not replace it automatically with an AI-generated version unless you explicitly trigger a regeneration. ❓ Frequently Asked Questions Why was manual editing temporarily unavailable? A platform update adjusted how OTTO handles fields with no AI suggestion, which unintentionally disabled the manual edit option for those blank slots. The fix has been deployed and manual editing is available again. Can I still use AI-generated suggestions after saving a manual edit? Yes. You can click the regenerate or refresh option on any field to request a new AI suggestion. Keep in mind this will replace your manually entered content, so save a copy if needed. What if the field still appears uneditable? Try refreshing your browser and navigating back to OTTO SEO. If the issue persists after a refresh, contact our support team using the instructions below. Will my manually edited titles and descriptions appear in the Audit tool? Yes. Changes made in OTTO SEO sync with the Audit view so your reporting stays consistent. 🆘 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

📝 Bulk Update and Deploy Meta Descriptions in OTTO SEO

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

🛠️ Control Auto-Deployment of Supplemental Content

🔍 Overview Search Atlas includes a Content Strategy & Supplemental Content feature that can automatically publish content to your connected website. If you were not aware this feature was active, or if you would like to prevent content from being published without your approval, you can adjust the relevant settings directly within your Search Atlas account. This article explains what this feature does and how to disable auto-deployment. ⚙️ What Is Supplemental Content Auto-Deployment? Supplemental content refers to supporting pages, articles, or other assets that Search Atlas can generate and deploy to your website as part of an automated content strategy. When auto-deployment is enabled, this content may be published directly to your site without requiring you to approve each piece individually. 🗺️ How to Turn Off Auto-Deployment To stop supplemental content from being published to your site automatically, locate the auto-deployment or publishing settings within the Content Strategy area of your Search Atlas account. The exact location of this setting may vary depending on your account configuration. Once you find the auto-deployment controls, disable automatic publishing so that new content is held for your review before going live. If you are unsure where this setting is in your account, or if you cannot locate the relevant controls, please have the following ready so our team can guide you directly: - The name of the project or connected website where content is being auto-deployed - Any recent examples of pages or content published without your approval - A description of what you see in the Content Strategy section of your account If you have already had content published without your approval, you can review recently deployed pages from within the Content Strategy area of your account and manage or remove them as needed. 🚦 What to Expect After Making the Change Once auto-deployment is disabled, new supplemental content will not be published automatically. You will be able to review and approve each piece before it goes live on your site. If content continues to deploy after you have made the change, or if you cannot locate the auto-deployment setting at all, our support team can assist you directly. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Find Bulk Selection in the OTTO Dashboard

Overview After a recent update to the OTTO dashboard, some controls — including the bulk selection feature — were repositioned within the interface. This article explains how to locate the bulk selection control in the updated UI. Getting to the OTTO Dashboard 1. Log in to your Search Atlas account. 2. Navigate to the OTTO dashboard from the main menu. 3. Select the website project you want to work on if prompted. Locating Bulk Selection After the UI Update After the UI update, the bulk selection control was repositioned within the OTTO dashboard. To locate it, open the relevant task section in OTTO and look along the top of the task list area for a selection control that allows you to select multiple tasks at once. To use bulk selection: 1. Go to the OTTO dashboard and open the task section you want to work in. 2. Locate the task list that displays your pending or suggested items. 3. Find the bulk selection control at the top of the task list — clicking it will select all visible tasks at once. 4. Alternatively, select individual tasks one by one using the per-row selection controls. 5. Once tasks are selected, the available bulk action controls will appear — click the relevant action to apply it to all selected items. If you do not see the bulk selection option, make sure you are viewing a section of OTTO that supports bulk actions, and that you are not in a filtered view that has hidden selectable rows. Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚡ Using Bulk AI Generation in OTTO

Overview OTTO includes a bulk AI generation feature that can automatically generate AI-powered fixes for multiple recommendations at once. Some customers have had trouble locating this option. This article explains what we know about where to find it and how to get help if you cannot locate it in your account. Finding the Bulk AI Generation Feature The bulk AI generation feature is used for applying AI-powered fixes to recommendation items inside the OTTO section of the Search Atlas platform. If you are having trouble locating this option, the most common cause is navigating to recommendations from the wrong starting point within OTTO. To find the feature: 1. Open the Search Atlas platform and go to the OTTO section. 2. Make sure you are viewing the main OTTO dashboard for your connected property, not a sub-page or linked view. 3. Look for the bulk AI generation option within the relevant recommendation group. If you do not see it, try refreshing your browser and confirming your OTTO session is connected to the correct property. If You Cannot Find the Option Because the exact location of this feature can vary depending on your account configuration and the recommendation type you are working with, the best next step if you cannot locate it is to reach out directly so a team member can guide you to the right place in your specific dashboard. When you contact support, please have the following ready: - The name of the OTTO project or property you are working in - A description of where you are navigating when the option does not appear - Any error messages or unexpected behavior you have observed If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

📋 View and Track Deployed OTTO SEO Tasks

🔍 Overview After deploying OTTO SEO automation tasks, you may wonder where to find a record of what was deployed and how to confirm the changes are live. This article explains where to look for deployed tasks and what to expect regarding visibility on your website. 🗂️ Where Deployed Tasks Are Stored All deployed OTTO SEO tasks are tracked within your OTTO project in the Search Atlas platform. To locate your deployed tasks: 1. From the main left-hand navigation, go to OTTO SEO → All Sites (SEO Automation). 2. Select the specific OTTO project associated with the site where you deployed tasks. 3. Once inside the project, look for the area that lists your applied automation tasks. This is where completed deployments are recorded, showing what was deployed and when. 4. Review the listed tasks to confirm which changes have been applied to your site. If you cannot find a specific task, verify that you are inside the correct OTTO project. Also confirm that the deployment step was fully completed — tasks that were only saved or queued may not yet appear as deployed. 📋 What to Look for in Your Project Within your OTTO project, you will find a record of automation tasks that have been applied to your site. Use this to confirm what changes have been made and cross-reference with any site behavior you are monitoring. If you are still unable to locate a task, double-check that you completed the final deploy action (not just saved or staged the task), as only fully deployed tasks are recorded as deployed. ⏱️ When Will Changes Appear on Your Live Site? After a task is marked as deployed in the platform, it may take some time before the changes are visible on your live website. If changes do not appear immediately, allow some time to pass before checking again. 🙋 Still Can't Find Your Deployed Tasks? If you have checked your OTTO project and still cannot locate your deployed tasks, our team can help you identify where they are recorded. When reaching out, please have the following ready: your project name, the approximate date you deployed the tasks, and a description of the task type you are looking for. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔌 Generate and Install the OTTO Pixel Script

🧩 What Is the OTTO Pixel? The OTTO Pixel is a lightweight tracking script that connects your website to OTTO SEO automation inside Search Atlas. Once installed in your site's <head> tag, OTTO can read your pages, apply optimizations, and track performance in real time. 🚀 Step 1: Generate Your OTTO Pixel Script 1. Log in to Search Atlas and open your OTTO project (or create a new one). 2. Navigate to the pixel script section of your project to find your unique script snippet. 3. Copy the full script snippet shown on screen. It is a standard JavaScript tag unique to your project. Keep this script ready — you will paste it into your website in the next step. 🌐 Step 2: Install the Script on Your Website The OTTO Pixel must be placed inside the <head> tag of every page you want OTTO to manage. Locate your site's global header template file and paste the OTTO Pixel script before the closing </head> tag. Consult your platform's documentation if you are unsure where the header file is located. 🧪 Step 3: Test on Localhost Before Deploying to Production You can validate the OTTO Pixel on a local development environment before pushing changes live. Set up your local site using your preferred local server tool, then paste the OTTO Pixel script into the <head> tag of your local site's header file using the same method described in Step 2. Load a page of your local site in a browser and confirm the script is present and loading without errors before deploying to your production environment. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🚫 Exclude OTTO Schema Suggestions for Specific Pages

🔍 Overview OTTO can generate schema markup suggestions across your entire site, but there are situations where you want to suppress those suggestions for a specific page—without turning off schema recommendations everywhere else. This article explains what to do if you need to exclude schema suggestions on a per-page basis inside OTTO. 📋 When You Might Need Per-Page Schema Exclusion You may want to exclude schema suggestions for a specific page if: - You have already applied custom schema markup manually and do not want OTTO to interfere with it. - A page uses a third-party plugin or app that handles its own structured data. - A page type (such as a login or checkout page) does not benefit from schema suggestions. - You are troubleshooting a conflict on one page without affecting the rest of your site. ⚠️ Current Limitation At this time, the ability to exclude schema suggestions on a per-page basis within OTTO is not a self-serve option that can be confirmed through available documentation. The exact steps for suppressing schema suggestions for individual pages depend on your specific site configuration and OTTO setup. To ensure you receive accurate, up-to-date guidance for your account, we recommend reaching out to our support team directly. When you do, please have the following information ready: - The name of the project or site you are working on in OTTO. - The specific page URL(s) for which you want to suppress schema suggestions. - A description of why you need per-page exclusion (e.g., manual schema already applied, third-party plugin conflict). - Any error messages or unexpected behavior you have observed related to schema on those pages. A member of our team will be able to confirm the correct steps or make the necessary configuration change on your behalf. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Control Auto-Deployed Content Strategy Changes

🔍 Overview Search Atlas includes a Content Strategy feature that can automatically deploy content changes to your connected website. If you noticed updates published without manual approval, or you want to understand how to find and control these auto-deployments, follow the steps below to locate the relevant settings inside the platform. 📍 Where to Find the Auto-Deploy Setting The auto-deployment controls live inside your OTTO SEO project, under the Content Strategy section. To get there: 1. Open Search Atlas and navigate to your project dashboard. 2. Select the relevant OTTO SEO project connected to your website. 3. Click on the Content Strategy tab within that project. 4. Within the Content Strategy section, look for the deployment or publishing controls — this is where automatic publishing behavior is managed. ⚙️ How to Turn Off Auto-Deployment If you want content to require manual approval before going live, navigate to the Content Strategy settings inside your OTTO SEO project and look for the option that controls automatic publishing. Depending on your account configuration, you may be able to switch from automatic to manual deployment mode. Once you have changed the setting, save your changes so that future content updates do not publish without your review. ✅ Reviewing and Approving Pending Content Once automatic deployment is disabled, content changes should queue up for your review rather than publishing immediately. Return to the Content Strategy tab in your OTTO SEO project to find content that is waiting to be published. From there, you can review each item and choose whether to publish or discard it before it goes live on your connected website. 📋 What to Have Ready If You Still Need Help If you are unable to locate the deployment controls or content was published unexpectedly, have the following ready when you reach out: - Project name — the name of the OTTO SEO project connected to your website. - Website URL — the domain where content changes are being (or were) deployed. - Description of the issue — for example, content that published without your approval, content stuck in a pending state, or uncertainty about where the deployment setting is located. - Approximate date/time of any unintended deployment, if applicable. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Share OTTO Plugin Credentials With Your Developer

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

⚡ Disable Breadcrumbs and Schema Markup in OTTO MetaSync

Overview OTTO MetaSync gives you control over breadcrumbs and schema markup, both across your entire site and on individual pages. This article explains how to approach disabling each feature. Because the exact option labels and navigation paths can vary depending on your plugin version and site configuration, the steps below describe the general areas to look in — if you cannot locate a specific setting, our support team can walk you through it for your exact setup. Part 1: Disable Breadcrumbs in the OTTO MetaSync WordPress Plugin Breadcrumb settings are managed inside your WordPress dashboard through the MetaSync plugin. To turn off breadcrumbs globally, follow these general steps: 1. Log in to your WordPress admin dashboard. 2. In the left sidebar, locate and open the MetaSync plugin settings. 3. Look for a Breadcrumbs section within the plugin settings. 4. Locate the option to disable or turn off breadcrumbs site-wide and deactivate it. 5. Save your changes. Once saved, breadcrumbs should be removed from all pages on your site. If you only want to disable breadcrumbs on a specific page, open that page in the WordPress editor, look for the MetaSync settings panel associated with that page, and disable the breadcrumb option at the individual page level. Part 2: Disable Schema Markup in OTTO MetaSync Schema markup can typically be turned off at two levels: globally for your entire site or on a per-page basis. Choose the approach that fits your needs. Option A — Disable Schema Markup Globally 1. Log in to your WordPress admin dashboard, open the Search Atlas plugin, and navigate to Settings → Schema Markup tab. 2. Open the configuration or settings area for your site. 3. Look for a Schema or Structured Data settings section. 4. Locate the option to disable schema markup site-wide and turn it off. 5. Save your changes to confirm. Disabling schema globally will stop OTTO MetaSync from injecting structured data across your entire site. This is useful if you manage schema through a separate tool or prefer to handle it manually. Option B — Disable Schema Markup on a Specific Page 1. Open the page or post you want to edit inside your WordPress admin dashboard. 2. Locate the MetaSync settings panel associated with that page (typically found below or alongside the editor). 3. Find the Schema or Structured Data option within that panel. 4. Disable schema for that specific page using the available toggle or dropdown. 5. Save or publish the page to apply the change. If you are unsure where to find any of the settings described above, or if the options look different in your version of MetaSync, please reach out — our team can confirm the exact steps for your setup. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

[UI Map] OTTO SEO — Main Dashboard

OTTO SEO Navigation path: Left sidebar → OTTO SEO → All Sites (SEO Automation) URL pattern: /seo-automation-v3 The OTTO SEO All Sites dashboard lets users manage, monitor, and automate SEO across multiple websites using the OTTO AI agent, showing grader scores, pixel installation status, healthy page counts, and SEO pillar breakdowns per site. Primary actions: - Create - Scan - Clear selection - Freeze sites ( 0 ) - Active 22 - Deep Frozen 5 - Engage OTTO - Go Pick One - Add Domain - Active - Inactive - All (440) Key UI elements: - Sites list with per-site cards - OTTO pixel installation status badge (Installed / Not Installed / Wrong UUID / Installed (WP)) - OTTO engagement toggle switch - OTTO Grader score progress bar (out of 100) - Healthy Pages count - SEO pillar scores: Content, Authority, Technical, UX Signals - Last analysis date - Autopilot status indicator - Time saved with OTTO label - CMS integration icon (WordPress, Shopify, Webflow, Contentful, Custom CMS) - Google Search Console integration icon - Google Business Profile integration icon - Bulk freeze checkbox per site - Pagination controls - Active / Deep Frozen filter tabs - Domain list table - Search domains input - Status filter buttons (Active / Deep Frozen) - Project count label (10 of first 100 projects) - Add Domain button - Country flag icon per domain row - Row action button (kebab) per domain - Filtering notice banner - Introductory description paragraph Sub-pages - Overview (OTTO Grader) — Navigation path: Left sidebar → OTTO SEO → Overview (OTTO Grader) Displays a site-level overview including OTTO engagement status, Brand Vault, OTTO Grader score, Holistic SEO Pillars, Pending Optimizations, Onpage Optimizations, Performance Report, time saved, and ROI metrics. Actions: Engage OTTO, Scan, Brand Vault, Performance Report Click to view, Time saved with OTTO -, OTTO ROI $ 0 - Crawl Monitoring — Navigation path: Left sidebar → OTTO SEO → Site Audit → Crawl Monitoring Monitors crawl activity and status for the selected site within OTTO SEO. - Knowledge Base — Navigation path: Left sidebar → OTTO SEO → Knowledge Base Links to the external OTTO SEO help documentation and knowledge base on the Search Atlas help center. - Installation Guide — Navigation path: Left sidebar → OTTO SEO → Installation Guide Provides step-by-step instructions for installing the OTTO SEO pixel on the selected site. - All Audits — Navigation path: Left sidebar → OTTO SEO → Site Audit → All Audits Navigates to the Site Audit section listing all audits across sites. - Page Explorer — Navigation path: Left sidebar → OTTO SEO → Site Audit → Page Explorer Explores individual pages of the selected site for SEO analysis and optimization opportunities. - Content Velocity — Navigation path: Left sidebar → OTTO SEO → Site Audit → Content Velocity Tracks the rate and volume of content publishing activity for the selected site. - Domain-level — Navigation path: Left sidebar → OTTO SEO → Domain-level Shows domain-level SEO issues and optimizations for the selected site. - Issues — Navigation path: Left sidebar → OTTO SEO → Issues Lists all detected SEO issues for the selected site with severity and fix recommendations. - Page Pruning — Navigation path: Left sidebar → OTTO SEO → Site Audit → Page Pruning Identifies underperforming or low-value pages that may benefit from pruning or consolidation. - Site Lens — Navigation path: Left sidebar → OTTO SEO → Site Audit → Site Lens Provides a visual lens or structured view of the site's SEO health and architecture. - Email Alerts — Navigation path: Left sidebar → OTTO SEO → Email Alerts Configures email alert notifications for SEO events and changes detected on the site. - Live Monitoring — Navigation path: Left sidebar → OTTO SEO → Site Audit → Live Monitoring Provides real-time monitoring of site SEO changes and OTTO automation activity. - All Projects — Navigation path: Left sidebar → AI Visibility → All Projects Lists all domains being tracked for AI visibility with their active/inactive status and quick navigation to per-domain sub-sections. Actions: Active, Inactive, All (440), Add Domain - Summary — Navigation path: Left sidebar → AI Visibility → Summary Provides a summary view of AI visibility data across tracked domains. Actions: Active, Inactive, All (440), Add Domain - Visibility — Navigation path: Left sidebar → AI Visibility → Visibility Shows visibility metrics for how often tracked domains appear in AI-generated answers. Actions: Active, Inactive, All (440), Add Domain - Sentiment — Navigation path: Left sidebar → AI Visibility → Sentiment Displays sentiment analysis of how AI models represent and describe tracked domains. Actions: Active, Inactive, All (440), Add Domain - Topics & Queries — Navigation path: Left sidebar → AI Visibility → Topics & Queries Shows the topics and queries for which tracked domains appear in AI-generated answers. Actions: Active, Inactive, All (440), Add Domain - Prompt Simulator — Navigation path: Left sidebar → AI Visibility → Prompt Simulator Simulates AI prompts to test how tracked domains appear in AI-generated responses. Actions: Active, Inactive, All (440), Add Domain Auto-generated by SA UI Mapper. Last updated: 2026-08-14.

⚡ Optimizing High-Volume Content Editing Workflows

Overview As your content operation grows, two questions often arise: how does the Search Atlas infrastructure hold up under heavy usage, and how can power users make the article editing experience faster and more fluid? This article outlines what is currently known and how to get further help, since many of the specific behaviors around capacity limits and advanced editing workflows are subject to change and may vary by account. Platform Capacity and Processing Search Atlas is built to support growing content operations, but specific details about automatic scaling behavior, processing queues, and content volume caps depend on your subscription plan and account configuration. We are not able to confirm precise infrastructure limits or guarantees in this article, as these details are not universally documented for all plan types. If you are concerned about how the platform will perform under high-volume usage — for example, running large numbers of audits simultaneously, generating multiple AI drafts at once, or onboarding a large editorial team — connect with our support team so they can review your account and advise accordingly. Article Editing Workflow Optimization For power users producing high volumes of content, the following tools within Search Atlas are designed to support efficient, scalable editorial workflows: - Content Planner: Use the Content Planner to organize and schedule large batches of articles. Mapping out your content calendar in advance reduces context-switching and helps editorial teams stay aligned on priorities. - Topical Maps: Build Topical Maps to identify content clusters before writing begins. This allows writers to tackle groups of related articles in sequence, which is faster than approaching topics in isolation. - AI Content Templates: Set up AI Content Templates with your preferred tone, structure, and formatting guidelines. Reusing templates across similar article types significantly cuts per-article setup time. - On-Page Audit: Run the On-Page Audit on existing articles to quickly surface optimization gaps. Batch your audit reviews by content category or publication date to work through high volumes systematically. - SEO Content Assistant: Use the SEO Content Assistant while drafting to reduce the number of post-draft revision cycles. Addressing optimization signals during initial writing is more efficient than returning to articles after publishing. Submitting a Feature Request If you have identified a specific workflow improvement or capacity-related capability you would like to see added to the platform, our product team welcomes that feedback. When submitting a feature request, include the following to help the team evaluate and prioritize it: 1. A clear description of the workflow problem you are trying to solve 2. The volume of content or team size involved 3. Which existing Search Atlas tools you have already tried and how they fell short 4. Any specific behavior or feature you would like the platform to support Providing this detail gives the product team the context they need to assess feasibility and prioritization accurately. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔗 Internal Linking & Tagging Strategy for Shopify Brands

🎯 What This Article Covers If you sell multiple brands in your Shopify store, a clear tagging system and a structured internal linking strategy help search engines understand your catalog and help shoppers navigate it. This article explains how to create tags scoped to a single brand like Axis, and how to build a hub-and-spoke internal linking architecture across your brand's product pages. 🏷️ Creating Brand-Specific Tags in Shopify Shopify tags are store-wide by default, but you can make them brand-specific by using a consistent naming convention. This keeps your tags organised and filterable when you are working across dozens of products. Recommended tag format: - Use a brand prefix before every tag value, for example: axis_security-camera, axis_nvr, axis_access-control - Keep the prefix lowercase and consistent — axis_ not Axis- or AXIS_ - Separate the brand prefix from the descriptor with an underscore, and use hyphens within the descriptor for readability To apply tags to your 67 Axis products in bulk: 1. Go to Products in your Shopify admin. 2. Filter by vendor or use the search bar to surface all Axis products. 3. Select all matching products using the checkbox at the top of the list. 4. Click Actions and choose Add tags. 5. Enter your brand-prefixed tags, for example axis_network-camera, and confirm. Once your products are tagged, you can filter your product list by any axis_ tag at any time, making bulk edits, audits, and exports much faster. 🕸️ Understanding Hub-and-Spoke Internal Linking Hub-and-spoke is a linking architecture where one central page — the hub — links out to multiple related pages — the spokes — and each spoke links back to the hub. For a brand like Axis with 67 products, this structure passes authority efficiently and signals topical relevance to search engines. How it maps to your Axis catalog: - Hub page: Your Axis brand collection page, for example /collections/axis - Category hubs (secondary hubs): Sub-collection pages organised by product type, for example /collections/axis-cameras, /collections/axis-access-control - Spoke pages: Individual Axis product pages, for example /products/axis-p3245-v This creates a two-level hierarchy: the brand hub links to category hubs, and each category hub links to its product spokes. Every spoke links back up to its category hub and to the main brand hub. 🔨 Building the Linking Structure Step by Step 1. Create your Axis brand collection page. In Shopify, go to Collections and create a collection filtered by the vendor tag Axis or by your axis_ product tags. This becomes your hub. 2. Create category sub-collections. Group your 67 products into logical categories — for example cameras, NVRs, access control — and create a Shopify collection for each. These are your secondary hubs. 3. Add contextual links on the brand hub page. In the collection description, write a short paragraph about Axis and include anchor-text links to each category sub-collection. Use descriptive anchors like Axis security cameras, not generic text like click here. 4. Link from each category hub back to the brand hub. In every sub-collection description, include a sentence such as: "Browse the full Axis product range" with a link back to /collections/axis. 5. Link from product pages to their parent category hub. In each product description or via a breadcrumb, include a link back to the relevant sub-collection. Shopify themes often handle breadcrumbs automatically — confirm yours is enabled. 6. Cross-link related products within descriptions. On each product page, mention one or two complementary Axis products with contextual anchor text. For example, on an Axis camera page you might link to a compatible Axis NVR. ✅ Internal Linking Best Practices for Bulk Products - Use descriptive, keyword-rich anchor text — avoid learn more or see here - Do not link every product to every other product — keep links relevant and contextual - Aim for each spoke page to have at least one inbound internal link from a hub page - Review your linking structure whenever you add new Axis products so the hub pages stay current - Use Search Atlas Site Auditor to identify orphan pages — product pages with no inbound internal links 📋 Quick Reference: Axis Tag Naming Examples - axis_network-camera - axis_fixed-dome-camera - axis_nvr - axis_access-control - axis_video-encoder - axis_outdoor-camera Always review your tag list before adding new ones to avoid near-duplicates like axis_cameras and axis_camera coexisting in the same store. 💬 Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

💡 Optimize and Deploy FAQ Content with NLP

🔍 What Is the NLP FAQ Feature? The NLP FAQ feature uses natural language processing to analyze your existing FAQ content and suggest improved versions of your questions and answers. The goal is to make your FAQs more relevant to how real users search, which can improve your chances of appearing in featured snippets and People Also Ask results. When you use this feature, nothing on your live site changes automatically. You review every suggestion before deciding what to deploy. ⚙️ What Changes When You Optimize an FAQ? The NLP engine may adjust the following elements of your FAQ content: - Question phrasing — reworded to better match natural search queries - Answer structure — improved for clarity and conciseness - Keyword alignment — answers are refined to include semantically relevant terms - Schema readiness — content is structured to support FAQ schema markup You will always see a side-by-side comparison of the original and optimized versions before anything is applied. 🗂️ How to Open the NLP FAQ Section 1. In the left sidebar, click Local. 2. Select My Tasks from the submenu. 3. Open an existing audit or create a new one by entering your target URL and keyword. 4. Once the audit loads, scroll through the on-page recommendations until you reach the FAQ section. 5. Click on the FAQ section to expand it and view the NLP-powered suggestions. 📊 How to Compare Original vs. Optimized Versions Inside the FAQ section, each question-and-answer pair is displayed with two panels: - Original — the current content pulled directly from your page - Optimized — the NLP-suggested version with improvements highlighted Review each pair carefully. Look for changes in wording, length, and keyword usage. You are not required to accept every suggestion — treat this as a starting point for your own editorial judgment. If you want to make manual edits to the optimized version before deploying, click inside the optimized text field and type your changes directly. 🚀 How to Deploy Your FAQ Changes 1. Once you are satisfied with the optimized content, check the box next to each FAQ item you want to deploy. 2. Review your selections in the summary panel on the right side of the screen. 3. Click Deploy all changes to push the approved changes to your connected page. 4. A confirmation message will appear once the deployment is successful. Note: Deployment requires that your site is connected to Search Atlas via the OTTO SEO integration. If your site is not yet connected, you will need to set that up before deploying directly from the platform. ✅ How to Confirm Changes Were Applied After deploying, you can verify the updates in two ways: - Within the platform — return to the On-Page Audit for that URL and refresh the audit. The FAQ section should now reflect the deployed content as the new original version. - On your live page — visit the page in your browser and check that the FAQ text matches what you deployed. Allow a few minutes for changes to propagate if you do not see them immediately. 🛠️ Troubleshooting Common Issues - No FAQ section appears in the audit — this means no FAQ content was detected on the page. Add FAQ content to your page first, then re-run the audit. - Deploy all changes button is greyed out — your site may not be connected via OTTO SEO. Check your integrations in the platform settings. - Changes are not visible on the live page — wait a few minutes and do a hard refresh (Ctrl+Shift+R or Cmd+Shift+R). If the issue persists, contact support. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🚀 How OTTO Deploys SEO Changes to Your Site

🧠 Understanding How OTTO Deploys Changes OTTO does not modify your website's back-end code, database, or CMS files. Instead, it uses a front-end overlay method to inject SEO changes — including schema markup, meta titles, and meta descriptions — directly into your pages at the browser level. This means: - Your CMS (WordPress, Shopify, Webflow, etc.) will not show any changes in its editor or post settings. - The changes are not written into your HTML source files on the server. - Changes are applied in real time when a page is loaded in a browser, via the OTTO script installed on your site. This is expected behaviour, not a bug. The overlay approach allows OTTO to deploy and update SEO elements instantly, without requiring developer access or CMS edits. ✅ What You Need for Deployment to Work Before OTTO can deliver any changes to your site's visitors and to search engines, two conditions must be met: 1. The OTTO script must be installed on your website. Without this script, the overlay cannot load and no changes will appear. 2. OTTO must be activated for the relevant pages or site. Optimisations are only deployed to pages where OTTO has been switched on. To check or complete your script installation, navigate to the OTTO SEO section of the platform and follow the installation instructions provided for your platform. 🔍 How to Verify Your Changes Are Live Because OTTO's changes are not visible inside your CMS, you need to verify them directly in the browser. Use one of the following methods: Method 1: Browser Developer Tools (Recommended) 1. Open the published page on your website in a browser (Chrome or Firefox recommended). 2. Right-click anywhere on the page and select Inspect (or press F12). 3. Click the Elements tab. 4. Use Ctrl+F (or Cmd+F on Mac) to search for your meta title, meta description, or schema markup text. 5. If OTTO is active and the script is installed, your deployed values will appear inside the <head> section of the rendered page — even though they are absent from your CMS. Method 2: Google's Rich Results Test 1. Go to https://search.google.com/test/rich-results. 2. Enter the full URL of the page you want to check. 3. Run the test. Google's tool renders the page the same way a browser does and will detect OTTO-injected schema markup. Method 3: View Rendered Page Source 1. Open the page in Chrome. 2. In the address bar, type view-source: before the URL and press Enter. 3. Note: this shows the raw server HTML and will not include OTTO's overlay changes — use Method 1 or Method 2 to confirm live deployment instead. If your changes are not appearing after confirming the script is installed and OTTO is activated, please have the following ready when you reach out: your project name, the specific URLs affected, and a description of which elements (schema, meta title, meta description) are not showing as expected. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚡ Bulk Generation for On-Page SEO Suggestions Explained

Overview The On-Page Audit tool allows OTTO to automatically generate AI-powered suggestions for your on-page SEO tasks. However, not every task category supports the bulk generation feature. This article explains what bulk generation is and clarifies the current scope of this feature. What Is Bulk Generation? Bulk generation lets you trigger AI suggestions for multiple pages or tasks at once, rather than handling them one by one. This saves time when you are working across a large site with many flagged issues. Instead of requesting a suggestion for each item individually, supported categories allow you to generate recommendations across multiple items in a single action. Which Task Categories Support Bulk Generation? Based on the current scope of the feature, bulk generation is supported for select on-page task categories — for example, categories such as Meta Titles, Meta Descriptions, and Image Alt Text are among the types of tasks where AI-assisted bulk generation is available. For other task categories, bulk generation is not currently available. If you are unsure whether the specific category you are working with supports bulk generation, or if you are not seeing the bulk action option where you expect it, please reach out to our support team for confirmation specific to your account and platform version. Why Do Some Categories Not Have Bulk Generation? Bulk generation is not available for all task categories at this time. If a category you need does not currently support it, this may be a limitation of the feature's present scope. You can let our team know which category you need — customer feedback helps inform future development. What to Have Ready When Escalating If you are experiencing an issue with bulk generation — for example, a category that is not behaving as expected — please have the following information ready when you contact support: - The name of the specific task category where you are experiencing the issue. - A description of what you expected to happen versus what actually occurred. - The project or site name associated with the On-Page Audit. - Any error messages or unexpected behaviour you observed, along with the approximate time it occurred. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🚀 Bulk SEO Title Updates for GHL Blogs

🗺️ Overview Updating SEO titles one by one across dozens of GoHighLevel (GHL) blog posts is time-consuming. This article walks you through the fastest workflow for bulk SEO title updates using Search Atlas, so agencies can optimize 50+ blogs in a single session without manual, post-by-post edits. ⚙️ How GHL Blog SEO Titles Work in Search Atlas Search Atlas connects to your GHL site through the OTTO SEO integration. Once your site is active inside OTTO, Search Atlas can read your GHL blog pages, surface SEO issues (including missing or weak title tags), and push optimized titles back to your site automatically. Important: OTTO must be installed and set to Active status for your GHL site before bulk title changes can be applied. If OTTO is not yet connected, follow the steps in the Installation Guide inside the OTTO SEO section of the platform. 🔍 Step 1 — Locate Your GHL Site in OTTO SEO 1. In the left sidebar, click OTTO SEO. 2. You will land on the All Sites view. Find your GHL site in the list. The status badge should read Active. 3. Click the site name to open its Overview dashboard. 📊 Step 2 — Run or Refresh a Site Audit 1. Inside the site Overview, click Scan in the top-right area to trigger a fresh crawl of your GHL blog pages. This ensures OTTO has the latest data before you make changes. 2. When the scan completes, click All Audits in the left sidebar under OTTO SEO to review the full list of detected issues. 3. Filter or search for title tag issues to isolate the blog posts that need updates. OTTO groups issues by type, so all missing or duplicate title issues appear together. ✏️ Step 3 — Apply Bulk SEO Title Updates OTTO surfaces title tag recommendations for every affected page. To update titles in bulk across your GHL blogs: 1. In the All Audits view, select the title-tag issue category. You will see a list of all affected blog posts. 2. Review OTTO's suggested SEO title for each post. OTTO generates keyword-aligned titles based on each page's content and your connected Brand Vault settings. 3. Use the Clear selection control to deselect any posts you want to skip, then select all remaining posts you want to update at once. 4. Click the bulk-apply action to push the optimized titles to all selected GHL blog pages simultaneously. OTTO writes the changes directly to your GHL site — no manual copy-paste required. Tip for agencies: Before running a bulk apply on a large set, spot-check 3–5 suggested titles to confirm OTTO's output matches your client's tone and target keywords. You can edit any individual suggestion inline before applying. 💡 Quick Workflow for 50+ Blog Posts - Scan first: Always click Scan on the Overview page before a bulk session to get fresh crawl data. - Filter by issue type: In All Audits, filter by title-tag issues so you only see the pages that need attention — no scrolling through unrelated findings. - Use Brand Vault: Open the Brand Vault (available from the Overview page) and confirm your client's brand name, primary keywords, and tone settings are up to date. OTTO uses this data to personalize every generated title. - Select all, then deselect exceptions: It is faster to select all flagged posts and deselect the few you want to review manually than to select posts one by one. - Re-scan after applying: Run a second Scan once changes are pushed to confirm all title issues are resolved and no new issues were introduced. 🛠️ Troubleshooting Common Issues - OTTO shows the site as Deep Frozen: A Deep Frozen site will not push changes to GHL. Go to All Sites, select the site, and reactivate it before proceeding. - Bulk apply button is greyed out: This usually means no posts are selected, or the site scan is still in progress. Wait for the scan to finish, then try selecting posts again. - Title changes are not appearing on the live GHL site: Allow a few minutes for GHL to propagate the updates. If titles are still missing after 10 minutes, re-scan to verify the changes were written successfully. - OTTO is not detecting GHL blog pages: Confirm the OTTO installation snippet is correctly placed on your GHL site by following the Installation Guide under OTTO SEO in the left sidebar. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

📊 Export OTTO SEO Fixes

🔍 Find OTTO SEO tasks Open the Search Atlas platform and select OTTO SEO from the left sidebar. You can also go directly to AI SEO → OTTO SEO. Select All Sites, then open the site and audit or agent session containing the suggested fixes. 📥 Check for an export option Open the relevant task, audit, or agent session and check the available actions for Export or Download. If this option is available for that screen, select it and choose a spreadsheet format such as CSV. ⚠️ When export is unavailable OTTO SEO does not currently provide a universal spreadsheet export for every suggested fix, task, agent session, or date range. If you cannot find an Export or Download action, the fixes must be reviewed and managed inside OTTO SEO. 📝 Use a spreadsheet workaround To create a tracking sheet when native export is unavailable: 1. Open the relevant OTTO SEO audit or session. 2. Copy each suggested fix and its page URL. 3. Paste the information into a spreadsheet. 4. Add columns for priority, owner, status, and completion date. 5. Use OTTO SEO to review the fix and confirm its current status. 🛠️ Review related OTTO SEO areas Use Overview for a summary, All Audits for audit results, and Crawl Monitoring for crawl-related information. The Installation Guide and Knowledge Base provide additional OTTO SEO guidance. 💬 Get help finding a task If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Verify OTTO Title-Tag Changes

🔍 What OTTO change history includes OTTO does not store a detailed, customer-visible history of every title-tag fix. As a result, there may be no historical log available to confirm when a specific title tag was changed or what its previous value was. Do not assume that a missing history means OTTO made no change. It means the platform cannot provide a stored fix record for that comparison. 🧩 Confirm the project association Before reviewing a site, confirm that it is an OTTO project associated with your Search Atlas account. A domain may exist in another account, workspace, or project without being available to you. 1. Open the project currently selected in Search Atlas. 2. Check that the project domain matches the site you want to review. 3. Confirm that OTTO is enabled for that project. 4. If the project or domain is missing, do not use another project’s data to verify the change. For example, if neroac.com is not an OTTO project associated with your account, Search Atlas cannot confirm OTTO changes for that site from your account. 📄 Check the current title tag Open the associated OTTO project and review the page’s current title tag using the available page or SEO details shown in that project. Compare the current value with a trusted source, such as a previous crawl, your CMS, or a saved page snapshot. Search Atlas may show the current state without providing a historical record of the change. Avoid claiming that OTTO changed a title unless independent evidence supports that conclusion. ✅ How to explain a discrepancy - Current title differs: A change may have occurred, but OTTO’s unavailable fix history cannot identify when or confirm that OTTO made it. - Current title matches: There is no visible title-tag difference in the current data. - Project is unavailable: The site cannot be verified from the current account until the correct associated project is accessible. - External tools disagree: Check crawl dates, caching, redirects, and whether each tool inspected the same URL version. 🚫 What not to claim Do not say that OTTO stores detailed title-tag change history, provide an invented dashboard location for historical fixes, or confirm a change when the site is not associated with the customer’s OTTO project. 💬 Get help verifying access If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🤖 OTTO SEO Bulk Suggestion Generation — Supported Categories

🔍 Overview OTTO SEO includes a bulk suggestion generation feature that lets you generate AI-powered recommendations for multiple pages at once. However, this feature is only available for certain task categories — not all on-page tasks. This article explains which categories are supported, why others are excluded, and what you can do instead. ✅ Categories That Support Bulk Suggestion Generation Bulk suggestion generation works for task categories that follow a structured, template-based format. OTTO SEO can reliably produce consistent, page-specific output for these types because the required inputs are predictable and well-defined. Supported categories include: - Meta Descriptions — generated from page content and target keywords - Title Tags — generated using page topic, brand name, and keyword data - Basic Schema — structured data markup generated from recognised page patterns These categories share a common characteristic: each suggestion follows a defined structure, has a clear character or format constraint, and can be produced accurately at scale without requiring manual context from you. ❌ Categories That Do Not Support Bulk Generation Many on-page task categories are excluded from bulk generation because they require context, judgment, or content decisions that cannot be reliably automated across a large number of pages in a single action. Examples of unsupported categories include: - Header tags (H1, H2, H3) — depend on the specific structure and intent of each page's content - Image alt text — requires understanding of image context, which varies widely - Content body improvements — involve editorial decisions unique to each page - Internal linking suggestions — depend on your site architecture and existing link graph - Canonical tags — require manual review of duplicate content relationships Attempting to bulk-generate suggestions for these categories would produce unreliable or generic output that could harm rather than improve your pages. To maintain quality, OTTO SEO restricts bulk generation to categories where AI output is consistently accurate and actionable. 📍 How to Use Bulk Suggestion Generation 1. Go to Left sidebar → OTTO SEO → Overview. 2. Select a connected site to open its task dashboard. 3. Locate a supported task category such as Meta Descriptions, Title Tags, or Basic Schema. 4. Select the pages you want to generate suggestions for using the checkboxes. 5. Click Generate Suggestions (or the equivalent bulk action button for that category). 6. Review the generated suggestions before deploying them to your site. Always review bulk-generated suggestions before approving them. Even for supported categories, AI output should be checked for accuracy, tone, and relevance to your brand. 🛠️ What to Do for Unsupported Categories For task categories that do not support bulk generation, you have two options: - Generate suggestions individually — open each task within OTTO SEO and use the single-page suggestion feature to get an AI recommendation tailored to that specific page. - Use Content Genius for deeper content work — navigate to Left sidebar → Content → Content Genius for more advanced AI-assisted writing, including reworking existing content or creating new articles optimised for specific keywords. 💡 Summary Bulk suggestion generation in OTTO SEO is intentionally limited to structured categories like Meta Descriptions, Title Tags, and Basic Schema because these are the only task types where AI can produce reliable, page-specific output at scale. Other categories require a page-by-page review process to ensure quality and accuracy. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

✅ How to Bulk Select Page Title Tasks

This article explains how to select multiple page title tasks in bulk so you don't have to click each task one by one, and how to confirm your selection was applied correctly. 📍 Where to Find It Page title tasks live under Left sidebar → OTTO SEO → Site Audit. 🛠️ Step-by-Step 1. Go to Left sidebar → OTTO SEO → Site Audit. 2. Locate the list of page title tasks awaiting review or approval. 3. At the top of the task list, click the header checkbox (or "select all" control) to select all visible tasks on the page at once, rather than clicking each row individually. 4. Note that selections are capped at 100 tasks per batch. If you have more than 100 tasks, apply your action to the first batch, then repeat the select-all step for the next page of tasks. 5. With tasks selected, apply your intended bulk action (such as approve, reject, or publish) from the action menu that appears once items are checked. ✅ How to Confirm It Worked - After clicking select all, check that a counter or label appears near the task list showing the number of selected tasks (e.g., "98 selected"), confirming the selection registered. - Once you apply a bulk action, refresh the Site Audit page and verify the affected tasks no longer appear in the pending list, or that their status has updated accordingly. - If the counter does not update or tasks remain unchanged after refreshing, try selecting fewer tasks at once, staying under the 100-task limit. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

✅ How to Bulk Select All Page Titles

This article covers the bulk select all option for page titles. 1. Open the page title tasks. 2. Use the bulk selection option to select all page title tasks at once. 3. Review the selected tasks and apply your intended action. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

📊 Build Comparison Pages and a Compare Hub

🔍 Why Comparison Pages Matter Shoppers searching terms like "zellige vs ceramic" or "terrazzo vs marble" are close to making a purchase decision. If your site does not have a page targeting those queries, a competitor will capture that traffic instead. Comparison pages and a dedicated Compare hub in your main navigation help you rank for these high-intent keywords and guide visitors toward conversion. 🗂️ What Is a Compare Hub? A Compare hub is a single, centrally linked page — usually added to your main menu — that organises all of your comparison content in one place. It acts as an internal linking anchor, distributes page authority across your comparison pages, and gives visitors an easy entry point when they want to evaluate options side by side. - Hub page: An overview page listing all available comparisons with short descriptions and links. - Spoke pages: Individual comparison pages (e.g. "Zellige vs Ceramic Tile") that go deep on a single pairing. - Supporting tools: Optional resources like a tile and grout calculator that add utility and increase time on site. 📋 How to Plan Your Comparison Pages 1. Identify relevant pairings. Focus only on materials or products you actually sell. Use Search Atlas keyword data to find pairings with measurable search volume and buyer intent. 2. Audit competitor content. Check what comparison posts competitors have published. Look for gaps — pairings they cover that do not mention your products, or pairings they have missed entirely. 3. Prioritise by search volume and conversion potential. Start with the five to ten pairings that combine high monthly searches with strong purchase intent signals. 4. Map each page to a target keyword. Each comparison page should target one primary keyword (e.g. "zellige tile vs ceramic tile") and a small cluster of related terms. 5. Plan supporting content. Identify tools or guides — such as a calculator or a care guide — that complement your comparison pages and can be linked from the hub. 🛠️ How to Structure Each Comparison Page A well-structured comparison page answers the shopper's core question quickly and builds trust. Use the following structure as a starting point: - Introduction: Briefly explain both materials and who each suits best. - Side-by-side comparison table: Cover key attributes such as durability, cost, maintenance, and aesthetics. - Detailed sections: Expand on each attribute with practical guidance. - Use-case recommendations: Tell the reader which option is better for kitchens, bathrooms, outdoor areas, and so on. - Internal links: Link back to the Compare hub and to relevant product or category pages. - Call to action: Direct visitors to shop, request samples, or contact your team. 🧭 How to Set Up the Compare Hub in Your Main Menu 1. Create the hub page on your site and publish it with a clean URL such as /compare/ or /tile-comparisons/. 2. Add links to all published comparison spoke pages on the hub. 3. Add the hub page to your main navigation menu so it is accessible from every page of your site. 4. Submit the hub URL for indexing and include it in your XML sitemap. 5. Monitor performance in Search Atlas under Left sidebar → Site Metrics → Keywords to track ranking progress for each comparison keyword. 📊 Tracking Performance in Search Atlas Once your comparison pages and hub are live, use Search Atlas to measure results: - Go to Left sidebar → Site Metrics → Keywords to monitor ranking positions for your target comparison queries. - Go to Left sidebar → Site Metrics → Pages to review organic traffic and engagement for each comparison page individually. - Go to Left sidebar → Site Metrics → Overview for a high-level view of how the new content is affecting your overall site performance. ✅ Content Review Checklist Before Publishing - Each page targets one primary comparison keyword. - The comparison table is accurate and covers the attributes shoppers care about most. - Every spoke page links back to the Compare hub. - The hub is linked from the main navigation menu. - Supporting tools (e.g. calculators) are linked from relevant pages. - All internal links point to live, correctly indexed URLs. - Pages are submitted to your sitemap and GSC for indexing. 💬 Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Transferring Frozen OTTO Projects Between Accounts

Overview If you manage multiple Search Atlas accounts or work with an agency, you may need to transfer an OTTO project from one account to another. This article explains what to expect when a frozen OTTO project is involved in an account transfer. What Is a Frozen OTTO Project? An OTTO project becomes frozen when the account no longer meets the conditions required to keep it active — most commonly because the subscription has lapsed or the account no longer has access to OTTO SEO. While frozen, active automations and optimisations are paused. Can a Frozen OTTO Project Be Transferred? Transferring a frozen OTTO project between Search Atlas accounts is not a standard self-serve action. Because the project is in a frozen state, the transfer requires backend assistance from the Search Atlas support team. You cannot complete this through the platform interface on your own. What to Have Ready When You Contact Support To help the support team process your request as quickly as possible, have the following information ready before reaching out: - The name of the OTTO project you need transferred - The originating account (email or account name) - The receiving account (email or account name) - Any error messages or status indicators you have seen related to the frozen or transfer state - The date and time the issue was first noticed Before Requesting a Transfer 1. Confirm the receiving account has an active Search Atlas subscription that includes OTTO SEO access — a frozen project cannot be activated in an account that does not support OTTO SEO. 2. Ensure the receiving account owner has the appropriate permissions to manage the project once it is transferred. Frequently Asked Questions - Will previously deployed changes be lost during the transfer? The support team will assess the state of your specific project during the transfer process and advise you on the outcome for any previously deployed changes. - Can the original account still access the project after the transfer? Once a project is transferred, ownership moves to the receiving account. Contact support before initiating a transfer to understand the access implications for your specific setup. - What if the receiving account does not have an active subscription? The project cannot be unfrozen or activated in the receiving account until an eligible subscription is in place. The support team can advise on next steps. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Verify Your Pixel and Trigger OTTO Recrawls

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

🧊 Deleting Deep Freeze Projects in LSEO SEO Automation

🔍 What Is Deep Freeze Mode? Deep Freeze is a protective state that LSEO SEO Automation applies to a project when it detects active automation processes or safeguards that prevent accidental data loss. While a project is in Deep Freeze, certain actions — including immediate deletion — are restricted to protect your work and any connected automation workflows. ⚠️ Why You Cannot Delete a Deep Freeze Project Immediately When a website is placed into Deep Freeze mode, the platform locks the project to ensure no ongoing processes are interrupted mid-run. This is by design. Attempting to delete the project while it is in this state will either be blocked or require you to complete a few steps first. There is currently no option to force-delete a project that is actively in Deep Freeze without following the proper exit process. 🛠️ How to Delete a Website in Deep Freeze Mode Follow these steps to safely remove a Deep Freeze project from LSEO SEO Automation: 1. Navigate to OTTO SEO: In the left sidebar, click OTTO SEO → All Sites (SEO Automation). This opens the SEO Automation dashboard (URL: /seo-automation-v3). 2. Locate the project: Find the website you want to delete. Projects in Deep Frozen mode will display a visible Deep Frozen indicator on their project card. 3. Exit Deep Freeze mode: Open the project settings or the options menu (typically a three-dot icon) for that website. Look for the option to Disable Deep Freeze or Exit Deep Freeze and confirm the action. This lifts the protective lock on the project. 4. Wait for the status to update: After disabling Deep Freeze, allow a moment for the project status to refresh. The Deep Freeze indicator should disappear from the project card. 5. Delete the project: Once Deep Freeze is no longer active, return to the project options menu and select Delete Project. Confirm the deletion when prompted. 💡 Important Things to Know Before Deleting - Deletion is permanent. Once a project is deleted, all associated automation data, settings, and history for that website are removed and cannot be recovered. - There is no instant delete for Deep Freeze projects. The exit-then-delete process is required every time. This cannot be bypassed. - Disabling Deep Freeze does not delete your data. Simply turning off Deep Freeze mode only removes the lock — it does not delete anything until you explicitly confirm deletion in the next step. - Active automations may need to be paused first. If the project has automations currently running, you may need to pause or stop them before Deep Freeze can be disabled. 🚀 Quick Recap To delete a Deep Freeze project: go to OTTO SEO → All Sites (SEO Automation) in the left sidebar → find the project → disable Deep Freeze from the project options → confirm the status update → then delete the project. Following these steps in order ensures a smooth, error-free removal. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 Otto Schema Changes and Go High Level Publishing Explained

🧠 How Otto Publishes Schema Markup When Otto applies schema markup to your website, it does not modify your website's backend files, database, or CMS settings. Instead, Otto uses a script-based injection method where structured data is dynamically inserted into each page as it loads in the browser. This means the schema is live on the internet immediately after Otto applies it, even though no files inside your Go High Level dashboard have changed. Your visitors and search engine crawlers like Googlebot will read the schema correctly when they visit your pages. 🤔 Why Go High Level Dashboard Shows No Changes This is the most common point of confusion for customers using Otto with Go High Level (GHL). Because Otto's injection method works at the script level — outside of GHL's page editor — the following are all expected and normal: - Your GHL page editor will not show any new schema code blocks. - Your GHL funnel or website builder will look identical to before Otto ran. - No new pages, sections, or custom code entries will appear inside GHL. This is by design. Otto injects schema without touching your GHL content, which protects your existing page layouts and prevents accidental overrides of your site design. ✅ How to Confirm Otto's Schema Is Live Even though GHL shows no changes, you can verify the schema is active and correctly deployed using these methods: 1. Google's Rich Results Test: Go to search.google.com/test/rich-results, enter your page URL, and run the test. If Otto's schema is live, Google will detect and display the structured data types applied to that page. 2. Schema Markup Validator: Visit validator.schema.org, enter your page URL, and review the parsed schema output. 3. View Page Source: Open your live page in a browser, right-click, and select View Page Source. Search for application/ld+json — you will see the schema blocks Otto injected if the script is active. If none of these methods detect schema on your page, proceed to the troubleshooting section below. 🔍 Troubleshooting: Schema Not Detected on Live Pages If your schema is not showing up in validation tools, work through the following checks: - Confirm the Otto script is installed: The Otto tracking and injection script must be present in your GHL site's header. Check your Go High Level site or funnel settings to verify the Otto script tag is included in your header tracking code. If it is missing, return to Search Atlas and reconnect or reinstall the Otto script for your site. - Check that Otto has been run on the specific page: Schema can be applied either to a specific page or site-wide (domain level). Confirm inside Search Atlas that Otto has been activated for the page or domain you are testing. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

❄️ OTTO Deep Freeze: Cancellation, Permanence, and Multi-Site Strategy

🧊 What Is OTTO Deep Freeze? OTTO Deep Freeze is a feature that pauses OTTO's active SEO optimization on a connected website. When Deep Freeze is enabled, OTTO stops making new changes to that site, effectively placing it in a suspended state. This frees up your OTTO slot so you can assign it to another site without losing the work OTTO has already done — as long as your subscription remains active. ⚠️ What Happens to SEO Changes After Cancellation? When the main subscription is cancelled, 24 hours after the account becomes unsubscribed all of its OTTO projects are automatically placed into Deep Freeze (autopilot off, read-only). The projects are not deleted and stay engaged, so the OTTO pixel keeps serving the fixes that were already deployed; OTTO just stops crawling and making new changes. Deployed changes stop being served only if the pixel is removed, the project is disengaged, or the project is deleted. 🌐 How to Optimize 10 Sites with 2 OTTO Slots If your plan includes 2 OTTO slots but you need to optimize more sites, you can use a sequential rotation strategy with Deep Freeze. Here is how it works: 1. Connect your first two sites to your available OTTO slots and activate OTTO for both sites through the Search Atlas platform. 2. Allow OTTO to run on each site for a sufficient period to complete a meaningful optimization cycle and apply substantive changes. 3. Enable Deep Freeze on both sites once the optimization window is complete. This pauses further changes and holds the current optimized state. 4. Reassign your OTTO slots to the next two sites in your list and repeat the process. 5. Continue rotating through all 10 sites in pairs, using Deep Freeze to hold completed work while you move on. Important: Sites held in Deep Freeze retain their deployed changes as long as the pixel remains installed, the project stays engaged, and the project is not deleted. 📋 Recommended Best Practices - Prioritize sites by impact. Start with your highest-traffic or most revenue-critical sites so those receive optimization first. - Track each site's optimization status using the site monitoring tools available within Search Atlas to monitor keyword rankings and performance over time. - Keep your subscription active throughout the rotation cycle so OTTO can continue crawling and applying new changes. If you cancel, existing projects are moved into Deep Freeze automatically and previously deployed fixes keep serving via the OTTO pixel. - Plan your rotation pace based on each site's needs. Allow enough time on each site before enabling Deep Freeze and moving on. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

❄️ What Is OTTO Deep Freeze?

⚡ OTTO Account Pause, Deep Freeze, and Reactivation

What Is the Deep Freeze Workflow? The deep freeze option lets you fully pause an OTTO account without permanently deleting it or losing any optimizations already applied to the site. This is the recommended approach when a client needs to temporarily stop OTTO activity — for example, during a contract pause, a site rebuild, or a billing hold. Deep freezing is intended to be reversible. When you are ready to resume, you can reactivate the account and restore OTTO activity. Before You Begin Before pausing an OTTO account, make sure you have the necessary access level for the account inside Search Atlas. It is also good practice to confirm that any in-progress OTTO tasks have finished before initiating a pause, and to remove the OTTO pixel from the client's site as part of the workflow. General Workflow: Pausing an OTTO Account The following steps reflect the general process for pausing an OTTO account. Because specific menu labels and button names may vary depending on your account configuration or platform version, contact our support team if you cannot locate a particular option. 1. Remove the OTTO pixel from the client's site. Locate the pixel code that was originally installed and remove it from the site. Verify it is no longer active on the live site before continuing. 2. Navigate to the OTTO account you want to pause inside Search Atlas. 3. Locate the pause or deep freeze option within OTTO SEO → All Sites (SEO Automation) — Deep Frozen tab. 4. Confirm the action when prompted. The account should enter an inactive/paused state, and no further automated changes will be deployed to the client's site. General Workflow: Reactivating a Paused OTTO Account The following steps reflect the general process for reactivating a frozen OTTO account. Again, exact option names may differ — reach out to support if you are unsure which option to select. 1. Reinstall the OTTO pixel on the client's site. Retrieve the pixel code from the OTTO account and add it back to the site before reactivating. 2. Confirm the pixel is active on the live site before proceeding. 3. Navigate to the paused OTTO account inside Search Atlas. 4. Locate the reactivation option within the account's management or settings area and select it. 5. Confirm the action when prompted. OTTO activity should resume for the account. If you are unsure about any step in this process — including where to find the deep freeze or reactivation options, or how to remove and reinstall the OTTO pixel — our team can walk you through it directly. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⏱️ How Long Google Takes to Index OTTO Updates

🔍 What Happens After OTTO Deploys Your Changes When OTTO deploys updated meta titles or meta descriptions to your site, the changes are applied to your pages immediately. However, there are two separate timelines to be aware of: when the updates appear in Search Atlas Page Explorer and when they appear in Google Search results. 🗓️ How Long Does Google Indexing Take After your meta title or meta description is updated on your site, Google must crawl and re-index the affected pages before the new content appears in search results. This process is outside of Search Atlas's control and depends entirely on Google's crawl schedule. - Typical range: Most pages are re-crawled and updated in Google within 3 to 14 days. - High-authority or frequently updated sites may see changes reflected within a few days. - Lower-traffic or newer sites may take up to several weeks. - Google does not guarantee a specific crawl frequency for any page. This delay is normal and expected. It does not mean your changes failed to deploy. 📊 When Will Page Explorer Reflect the Updates Page Explorer in Search Atlas pulls live on-page data from your site. Once OTTO has successfully deployed a change, Page Explorer should reflect the updated meta title or description within 24 to 48 hours after the next scheduled data refresh for your project. If you want to verify the change was applied correctly right away, you can: 1. Visit the page directly in your browser and inspect the page source (Ctrl+U or Cmd+U). 2. Search for <meta name="description"> or the <title> tag to confirm the new content is live. 🚀 How to Speed Up Google Re-Indexing While you cannot force Google to crawl immediately, you can request re-indexing through Google Search Console to increase the chance of a faster crawl: 1. Go to Google Search Console and select your property. 2. Paste the updated page URL into the search bar at the top and press Enter. 3. Click Request Indexing in the URL Inspection panel. 4. Google will add the page to its priority crawl queue. Results typically appear within a few days. This method works best for a small number of high-priority pages. For large-scale deployments, allow the standard 3–14 day window. ✅ How to Confirm OTTO Deployed Successfully Before waiting on Google, first confirm that OTTO applied your changes correctly: - Navigate to OTTO SEO in the left sidebar of Search Atlas, then open SEO Automation. - Locate the relevant page and check the deployment status. A green deployed indicator confirms the update was pushed successfully. - If the status shows an error or is still pending, review the OTTO deployment log for that page and re-deploy if needed. 💡 Key Takeaways - OTTO applies meta changes to your site immediately upon deployment. - Page Explorer reflects updates within 24–48 hours of the next data refresh. - Google reflects updates in search results within 3–14 days on average. - Use Google Search Console URL Inspection to request faster re-indexing for priority pages. - A delay in Google does not mean the deployment failed — always verify in your page source first. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔄 OTTO Re-Scanning After Knowledge Graph Updates

🔍 Overview When you update your Knowledge Graph in Search Atlas, OTTO needs to re-evaluate your site to generate fresh recommendations based on the new information. This article explains exactly how that process works, what happens automatically, and when you need to take manual action. ⚙️ How OTTO Re-Scanning Works OTTO does not automatically re-scan your site on a daily schedule after a Knowledge Graph update. Instead, re-scanning is triggered manually by you whenever you are ready to apply updated recommendations. This gives you full control over when OTTO processes your latest Knowledge Graph data — so you are never caught off guard by unexpected changes to your recommendations. Here is what the process looks like from start to finish: 1. Update your Knowledge Graph — Add, edit, or remove entities, relationships, or attributes inside your Knowledge Graph. 2. Navigate to OTTO — In the left sidebar, go to OTTO SEO, then open All Sites (SEO Automation) (URL: /seo-automation-v3). 3. Trigger a manual re-scan — Initiate a new scan from within the OTTO dashboard. OTTO will pull in your latest Knowledge Graph data and regenerate recommendations accordingly. 4. Review updated recommendations — Once the scan completes, your recommendations will reflect all changes made to the Knowledge Graph. 💡 Why Manual Triggering Instead of Automatic? Manual triggering is intentional by design. Here is why this approach benefits you: - You stay in control. Knowledge Graph updates can be incremental — you may make several edits over a few days before you are ready to push them into your SEO recommendations. Manual triggering lets you batch those changes. - No unexpected recommendation shifts. Automatic daily re-scans could alter your active recommendations without warning. Manual control means changes only happen when you decide. - Predictable workflow. You can align re-scans with your content or publishing schedule rather than relying on a background process. 🛠️ Step-by-Step: Triggering a Re-Scan After a Knowledge Graph Update 1. Finish all edits to your Knowledge Graph before triggering a scan — this ensures OTTO processes your complete set of changes in one pass. 2. In the left sidebar, click OTTO SEO, then open All Sites (SEO Automation) (/seo-automation-v3). 3. Locate the site or project you want to re-scan. 4. Click the Scan (or Run diagnostics) button for that project. 5. Wait for the scan to complete — scan time varies depending on site size. 6. Review your new recommendations and deploy or approve any changes as needed. 📊 What Changes After a Re-Scan? After OTTO completes a re-scan using your updated Knowledge Graph, you can expect the following to refresh: - On-page recommendations — Titles, meta descriptions, headings, and body content suggestions updated to reflect new entities and relationships. - Schema markup suggestions — Structured data recommendations aligned with your revised Knowledge Graph. - Internal linking opportunities — New or adjusted link suggestions based on updated topic clusters. - Content gap insights — Any new gaps identified from additional Knowledge Graph entities. ✅ Best Practices - Make all Knowledge Graph edits before triggering a re-scan to avoid running multiple scans unnecessarily. - Re-scan after any significant Knowledge Graph update — adding new core entities, restructuring relationships, or changing your primary topic focus. - For minor edits (fixing a typo, small attribute update), you can batch several small changes together and re-scan once. - Keep a note of what you changed in the Knowledge Graph each time so you can verify the updated recommendations make sense. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔄 OTTO Domain Migration Cutover Sequence Guide

Overview If your website is moving to a new domain — for example, from one domain extension to another — your OTTO project may be able to follow the migration without losing your Knowledge Graph or settings. This article explains what is typically preserved, what requires attention, and the recommended approach during a domain cutover. Key Constraints to Understand First Before you begin, review these important limitations: - One domain per OTTO project: Each OTTO project is tied to a single root domain. You cannot run one project across two domains simultaneously. - Resolved optimizations are domain-scoped: OTTO tracks resolved items against specific URLs. When the domain changes, those URLs change, which means resolved statuses may not automatically transfer to the new domain's URL set. - Knowledge Graph is project-level: Your Knowledge Graph (entity data, business information, topical authority settings) lives at the project level and is preserved as long as you do not delete the project. - Domain cannot be changed in place: The website is set when an OTTO project is created and cannot be edited in the project settings. To move OTTO to a different domain (including www vs non-www), create a new OTTO project for the new domain and install its pixel. - A full re-crawl is required: After cutover, OTTO must crawl the new domain to surface its pages, errors, and opportunities before it can apply or verify optimizations. What Is Preserved vs. What Needs Attention - Preserved automatically: Knowledge Graph data, OTTO configuration settings, custom rules, and your connected integrations. - Requires re-verification: Previously resolved optimizations — OTTO will re-audit the new domain's URLs and previously resolved items may appear as open until OTTO confirms they are still applied on the new domain. - Requires a new project: The domain of an existing OTTO project cannot be changed. You must create a new OTTO project for the new domain and install its pixel before OTTO can crawl and index the new site. Recommended Approach Because the domain of an existing OTTO project cannot be changed in place, migrating to a new domain requires creating a new OTTO project for the new domain and installing its pixel. If you'd like guidance through this process, contact our support team before making any changes — a teammate can walk you through the correct steps for your account and help you avoid losing resolved optimization progress. When you reach out, please have the following ready: - The name of your OTTO project - Your current (old) domain and the new domain you are migrating to - The status of your DNS/server-side migration (whether 301 redirects are already in place) - Any relevant Google Search Console property changes you have made - A note of how many resolved optimizations you currently have, so progress can be cross-checked after migration If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🗑️ Cloud Stacks Campaigns: Deletion and Content Removal

🔑 Key Facts Before You Begin Cloud Stacks campaigns distribute your content to independent third-party web properties. Once content is submitted and published to those properties, it exists outside of Search Atlas and cannot be retracted, edited, or removed — by Search Atlas or by you. This is a hard platform limitation, not a process gap. Deleting a Cloud Stacks campaign inside Search Atlas does not remove or unpublish content that has already been sent to publishers. 📋 What Happens When You Delete a Campaign Deleting a campaign in Search Atlas removes it from your dashboard and stops any future submissions associated with that campaign. It does not: - Take down content that has already been published to web properties - Send removal or unpublish requests to any third-party platform - De-index pages from Google, Bing, or any other search engine - Give you or Search Atlas access to those third-party sites to modify content To delete a campaign, go to Left sidebar → Authority → Cloud Stacks, open the relevant campaign, and use the delete option. This action only affects your Search Atlas records. 🌐 Why Content Cannot Be Removed When a Cloud Stacks campaign is submitted, content is distributed to external web properties operated by independent publishers. Search Atlas does not own, control, or have editorial access to those sites. Because of this: - Search Atlas has no ability to log in to those properties and delete pages on your behalf - There is no contractual or technical mechanism to issue a takedown to these publishers after submission - Search Atlas support cannot contact individual cloud providers to request removal This is the same situation you would face with a guest post or press release published on an external site — once it is live, the publishing platform controls the content. 🔍 What About Indexed Pages in Search Engines? If pages from your Cloud Stacks campaign have already been crawled and indexed by search engines, Search Atlas cannot request de-indexing on your behalf because we do not have verified ownership of those third-party domains. Standard webmaster de-indexing tools (such as Google Search Console's URL removal tool) require verified site ownership. Since you do not own the cloud web properties, those tools are not available to you for this content. Over time, search engines may naturally drop low-authority or thin pages from their index, but this is not guaranteed and cannot be accelerated through Search Atlas. ⚠️ Important: Plan Before You Submit Because published Cloud Stacks content is permanent and irreversible, please review the following before launching any campaign: - Content accuracy: Confirm all URLs, brand names, anchor text, and facts are correct before submission. - Target URLs: Make sure the pages you are promoting are live, correctly optimised, and intended to be associated with the distributed content long-term. - Brand representation: All published content will be publicly visible and associated with the links and entities you include, indefinitely. Once you click submit, the campaign content moves to external publishers immediately and the process cannot be reversed. ✅ What You Can Still Do While you cannot remove already-published content, here are the actions that remain available to you: - Delete the campaign record in Search Atlas (Left sidebar → Authority → Cloud Stacks) to stop tracking it and prevent any unsent submissions from being processed. - Pause or stop future submissions if the campaign has scheduled or pending content that has not yet been sent. - Create a new campaign with corrected content to build additional signals if the original content contained errors. - Review campaign history via Left sidebar → Authority → Campaigns to see the status of all past submissions. 💬 Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🤖 OTTO Title Tag Suggestions and AI Credits Explained

🔍 Overview OTTO's title tag optimization feature uses AI to analyze your pages and generate improved title tag suggestions. Because this process uses a large language model to evaluate your content in real time, it draws on your account's AI credits. This article explains why credits are required, what OTTO's title tag diagnostics mean, and how to get the most accurate suggestions from the tool. 💡 Why AI Credits Are Required for Title Tag Suggestions Unlike rule-based checks (such as missing meta tags or broken links), generating a title tag suggestion is a creative, context-aware task. OTTO reads your page content, evaluates it against SEO best practices, and produces a customized recommendation — all powered by AI. This process consumes AI credits each time a suggestion is generated. - One credit per suggestion: Each page that receives a title tag suggestion uses one AI credit from your account balance. - Credits are not used for diagnostics alone: Viewing that a title tag has an issue does not consume credits. Credits are only spent when you actively request a suggestion. - Credit balance is visible in your account settings so you can monitor usage at any time. ⚠️ Understanding Title Tag Errors Without Full Explanations You may notice that OTTO flags a title tag issue on your dashboard without showing a detailed explanation of exactly what is wrong. This is a known limitation that the OTTO team has been actively improving. Here is what each common status typically means: - Title tag too short or too long: The tag falls outside the recommended 50–60 character range. Search engines may truncate or rewrite it. - Duplicate title tag: The same title is used on more than one page on your site, which can confuse search engines about which page to rank. - Missing primary keyword: OTTO's AI Grader has determined that the target keyword for the page is absent or poorly positioned in the title. - Low relevance score: The title does not closely reflect the page's main topic based on its content analysis. If the error label shown in your dashboard does not match one of the above, or if the flagged issue is unclear, generating an AI suggestion is the fastest way to see what OTTO recommends changing and why. 🤖 Why OTTO's Guidance May Not Match Your Dashboard A common point of confusion is when the in-platform chatbot or on-screen tips describe a different issue than what your dashboard is showing. This can happen for a few reasons: - AI Grader updates: OTTO's scoring model has been recently updated to expand the dimensions it evaluates. Pages graded before this update may show legacy labels that do not reflect current scoring logic. - Cached diagnostic data: Your dashboard may be displaying a previous scan result. Running a fresh scan on the affected page will pull the latest analysis. - Chatbot context limitations: The in-platform assistant provides general guidance and may not have real-time access to your specific page's diagnostic data. For the most accurate picture, always compare the suggestion OTTO generates against the live state of your page rather than relying solely on the error label. 🚀 How to Request a Title Tag Suggestion in OTTO 1. Go to Left sidebar → OTTO SEO → SEO Automation (All Sites) (URL: /seo-automation-v3). 2. Select the site you want to optimize from your active projects. 3. Navigate to OTTO SEO → Overview (OTTO Grader) → Page Title for that site. 4. Find the page flagged with a title tag issue. 5. Click Get Suggestion (or the AI wand icon next to the title field). OTTO will use one AI credit and generate a revised title tag. 6. Review the suggestion. You can accept it directly, edit it before applying, or dismiss it and keep your current title. Tip: If the generated suggestions appear identical or only minimally different from your existing title, try adding more content to the target page before requesting a new suggestion. OTTO's AI uses page content as its primary input, so richer content produces more differentiated recommendations. 📊 Managing Your AI Credit Balance - Check your remaining credits at any time in your account settings. - Credits are shared across all AI-powered features in Search Atlas, not just title tag suggestions. - If you run out of credits mid-optimization, you can purchase additional credits or wait for your next billing cycle refresh, depending on your plan. 🛠️ Troubleshooting Common Issues - Suggestion did not generate: Confirm you have sufficient AI credits and that the page URL is accessible (not password-protected or returning a non-200 status). - Suggestion is identical to current title: Re-scan the page to update OTTO's content index, then request a new suggestion. - Dashboard shows an error but the suggestion looks fine: Apply the suggestion, then trigger a re-scan. The diagnostic label should update to reflect the improvement. - Bot guidance conflicts with dashboard data: Trust the dashboard diagnostic and the AI-generated suggestion over the general chatbot response for page-specific decisions. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🧊 OTTO Sites Quota and Deep Freeze Explained

🔍 Overview If you purchased a plan that includes a set number of OTTO Sites but the count displayed in your dashboard looks lower than expected, Deep Freeze is the most likely cause. This article explains how OTTO Sites quota works, what Deep Freeze does to a slot, and what you can do right now. 📊 Understanding Your OTTO Sites Quota Your plan includes a fixed number of OTTO Sites slots. Each slot can be assigned to one active project. You can check your current usage by navigating to Left sidebar → OTTO SEO (or visiting /seo-automation-v3) and looking at the Active Sites count. You may notice two slightly different numbers in your account: - Plan quota — the total number of OTTO Sites slots included in your subscription (e.g., 4 on the PRO annual plan). - Active Sites — the number of slots currently available or in use, which may be lower if one or more slots are in a Deep Freeze state. 🧊 What Is Deep Freeze? When you disconnect or deactivate an OTTO Site, the slot does not become available again instantly. Instead, it enters a temporary Deep Freeze period. During this period: - The slot is held for a short cooldown window and is not available for a new project. - Your Active Sites count will appear lower than your total plan quota. - The frozen slot will be released automatically once the cooldown period ends. This is expected behaviour and is not a billing error or a system discrepancy. 💡 Example: PRO Plan with 5 OTTO Sites Here is a common scenario that explains the numbers customers see: 1. You purchase the PRO annual plan, which includes 5 OTTO Sites. 2. You previously disconnected one site, placing that slot into Deep Freeze. 3. Your dashboard shows 4 available slots in the OTTO Sites quota and only 3 Active Sites — because one slot is frozen and one is already assigned. 4. Once the Deep Freeze cooldown expires, the frozen slot is released and your available count returns to the expected number. 🛠️ What You Can Do Right Now While we are actively improving how frozen slots are displayed — including upcoming features that will show you exactly when each frozen slot will be released — here are the steps you can take today: 1. Go to Left sidebar → OTTO SEO and open your projects table. 2. Look for any projects that are marked as disconnected, inactive, or in a frozen state. 3. If a project is no longer needed, you can delete it entirely to free its slot sooner. Deleting a Deep Frozen project is now supported and will release the slot without waiting for the full cooldown. 4. If no projects appear frozen but your count is still lower than expected, the cooldown window may still be active — allow up to 14 days for the slot to be automatically released. 🚀 Improvements Coming Soon Our engineering team is working on several improvements to make this experience clearer: - A per-slot countdown timer will appear in the projects table, showing the exact date and time each frozen slot will be released. - A per-slot quota ledger will give you a transparent breakdown of all your slots and their current states. These updates will make it much easier to understand your quota at a glance and plan accordingly. ❓ Still Seeing an Unexpected Count? If you have waited 14 days, deleted any unused frozen projects, and your quota still does not match what your plan includes, there may be something else to investigate. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team. Additional Notes The 14-day hold period: Deep Freezing does not instantly release quota; the slot is held for 14 days before returning to available quota. This is hardcoded and cannot be overridden, waived, or expedited by support under any circumstance.

🔄 Changing Your OTTO Project Domain Correctly

🔍 Overview When you create an OTTO project in Search Atlas, the domain you enter is permanent. There is no option to change the domain after the project has been created. If you started with a temporary or development domain and are now ready to move to your live domain, you will need to delete the existing project and create a new one for the correct domain. This article explains the platform constraint and walks you through the general migration process for switching from a development domain to a live domain. ⚠️ Why You Cannot Edit the Domain After Creation OTTO ties its configuration directly to the domain entered at setup. Because of this, Search Atlas does not provide a domain-edit option inside an existing OTTO project. If you attempt to locate an option to change the domain field inside your project settings, you will not find one — this is expected behaviour, not a bug. 🗺️ How to Migrate from a Development Domain to a Live Domain Follow these general steps to move your OTTO setup to your live domain. 1. Delete the existing OTTO project. In the Search Atlas platform, delete the project associated with your development or temporary domain. 2. Create a new OTTO project for your live domain. Create a new project and enter your live production domain. Make sure the domain matches exactly what visitors use, including whether it uses www or not. 3. Complete any setup steps for the new project. Once the new project is created, follow any on-screen instructions within the platform to connect it to your live site. 4. Allow OTTO to begin working on the new project. After the new project is active, OTTO can start generating recommendations and applying SEO automation for your live site. 💡 Best Practice: Start with Your Live Domain To avoid repeating this process in future projects, always create your OTTO project using your final live domain from the start. Avoid using staging, development, or temporary domains when setting up a new OTTO project, as migrating later requires deleting and recreating the project from scratch. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🤖 AI Suggestions for Brand Vault Top Pages

🏦 What Is Brand Vault and What Are Top Pages? Brand Vault is your centralized hub for storing your brand's key information — business details, target keywords, top-performing pages, and press release content. Search Atlas uses this data to personalize AI-generated content and OTTO's technical SEO recommendations across your projects. Top Pages are the most strategically important URLs on your website. These are the pages you most want to rank in search results. Brand Vault stores them so every AI tool — from content generation to OTTO fixes — understands which pages matter most to your business. 📋 What Should I Add to Brand Vault for SEO and Press Releases? For the best results across SEO workflows and press release generation, add the following to Brand Vault: - Top Pages: Your homepage, core service or product pages, high-traffic blog posts, and any landing pages you are actively building authority for. - Target Keywords: Primary keywords and branded terms associated with each Top Page. Include both short-tail and long-tail variations. - Brand Details: Company name, industry, unique value proposition, and tone of voice. This shapes AI-written press releases and content briefs. - Press Release Topics: Product launches, company milestones, partnerships, or campaigns you want to promote. The more context you provide, the more accurate the AI output. A well-populated Brand Vault means AI-generated press releases and OTTO recommendations are immediately relevant to your business — requiring far less manual editing. 🤖 Can OTTO Auto-Suggest Top Pages and Keywords? Yes. OTTO's Domain Knowledge Network analyzes your connected domain and automatically detects candidate Top Pages and keyword associations. Here is exactly what OTTO does and what it does not do: What OTTO detects automatically: - High-traffic or high-impression pages pulled from your connected Google Search Console data. - Pages with strong internal linking signals or existing backlink equity. - Keyword clusters already associated with those pages based on search performance data. What requires your input: - OTTO surfaces suggestions — it does not add pages to Brand Vault without your confirmation. - Strategic priorities such as new product launches or pages with no historical data yet cannot be inferred automatically and must be added manually. - Keyword intent classification (informational, commercial, transactional) is reviewed and confirmed by you before saving. ✅ How to Review and Confirm OTTO's AI Suggestions 1. In the left sidebar, navigate to OTTO SEO → All Sites (SEO Automation) (URL: /seo-automation-v3). 2. Select your project and open the OTTO dashboard. 3. Click the apps-grid icon in the header, then go to More Features → Brand Vault. 4. Go to the Top Pages section. If OTTO has detected suggestions, you will see a highlighted AI Suggestions banner or a list of recommended URLs with a status badge. 5. Review each suggested page. Click View Details to see the associated keywords OTTO has detected for that URL. 6. For each suggestion, choose one of the following actions: - Confirm: Adds the page and its keywords to Brand Vault. - Edit then Confirm: Modify the URL or keyword list before saving. - Dismiss: Removes the suggestion without adding it. 7. To add a page OTTO did not suggest, click + Add Top Page, enter the URL manually, and assign target keywords. 8. Once your Top Pages are confirmed, click Save Brand Vault to apply your changes across all connected AI tools. OTTO refreshes its domain analysis periodically. If your site is newly connected or has limited Search Console history, suggestions may be sparse at first. Add pages manually in the meantime and OTTO will incorporate them into future analysis. 📰 How Much Do Press Release Credits Cost? Press release generation uses credits from your Search Atlas plan. Credit costs vary by plan tier. To check your current credit balance and per-release cost, click your Avatar (top-right) → Billing → Plans & Top-ups. If you need to purchase additional credits or upgrade your plan, the same section provides access to available top-up options. 🔗 Why Does My Wix Integration Fail With 'Domain Already Exists'? This error means the domain you are trying to connect is already registered under another Search Atlas project or account. To resolve it: 1. Check all your existing projects to see if the domain is already connected under a different project name. 2. If the domain is connected to a project you no longer use, open that project, go to Settings, and disconnect the domain before reconnecting it to your current project. 3. If the domain appears in a project you do not recognize or cannot access, contact support using the chat widget below — a teammate can audit and release the domain from the duplicate record. This error is specific to Wix because Wix sites use a verified domain handshake during integration. Unlike some other CMS platforms, Wix does not allow the same domain to be active in two Search Atlas projects simultaneously. 🔧 How Do I Use OTTO to Deploy Technical SEO Fixes? 1. Navigate to OTTO SEO in the left sidebar. 2. Open your project's OTTO dashboard. 3. Click the Technical SEO tab to view all detected issues grouped by category (crawlability, on-page, structured data, etc.). 4. Select the fixes you want to deploy. Each fix shows a description, affected URLs, and the expected SEO impact. 5. Click Deploy Selected Fixes. OTTO will implement the changes directly on your connected site if auto-deploy is enabled, or queue them for your review if you are using manual deploy mode. 6. After deployment, revisit the Site Audit → Issues tab to confirm fix statuses update to Resolved. Ensure your CMS integration is active and your domain is verified before deploying fixes. Disconnected integrations will prevent OTTO from pushing changes live. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔄 Delete OTTO Projects and Reassign Site Quota

🗺️ Overview Each Search Atlas plan includes a set number of OTTO site activations. If you want to move an OTTO project from one site to another — for example, when you stop working on a client site or want to audit a new domain — you need to deactivate OTTO on the existing site first. This frees up a quota slot that you can then assign to a new site. Important: Deactivating OTTO removes the automation from that site. Your Search Atlas project, OTTO settings, recommendations, and history are retained for later reactivation, but the OTTO pixel will stop serving OTTO's changes while the project is disengaged. ⚙️ Step 1 — Access Your OTTO Projects 1. Log in to Search Atlas. 2. In the left sidebar, click OTTO SEO, then open SEO Automation (URL: /seo-automation-v3). 3. You will see a list of all sites that currently have OTTO activated. 🔍 Step 2 — Identify the Site to Remove 1. Locate the site whose OTTO project you want to free up. 2. Confirm this is the correct site — deactivation cannot be undone without restarting the OTTO setup process. 3. Take note of any important settings, deployed fixes, or custom instructions you want to replicate on the new site. 🗑️ Step 3 — Deactivate OTTO on the Existing Site 1. Click on the site to open its OTTO dashboard. 2. Locate the Deactivate OTTO option (typically found in the site settings or via the three-dot menu next to the site name). 3. Confirm the deactivation when prompted. The quota slot is released immediately and becomes available for reassignment. Note: The underlying Search Atlas site project remains intact. Only the active OTTO session is removed. You can reactivate OTTO on the same site in the future and its saved settings, recommendations, and history will still be available. 🚀 Step 4 — Assign OTTO to a New Site 1. From the OTTO SEO → All Sites (SEO Automation) page (URL: /seo-automation-v3), click Activate OTTO or the equivalent button to start a new project. 2. Select the new site you want to connect, or create a new Search Atlas project for it. 3. Follow the on-screen setup steps: connect the site, choose your SEO goals, and configure OTTO settings for the new domain. 4. Once setup is complete, OTTO will begin auditing and automating improvements for the new site. 📊 Managing Your Quota - Your current OTTO quota usage is displayed on the OTTO SEO → All Sites (SEO Automation) page (URL: /seo-automation-v3) — check it any time to see how many slots are active versus available. - If you need more activations than your plan allows, you can upgrade your plan from the Top-right corner (avatar) → Billing → Plans & Top-ups tab of your account. - Deactivating a site frees its slot instantly — no waiting period applies. 💡 Tips and Best Practices - Document your settings first. Before deactivating, screenshot or note any custom OTTO configurations, ignored issues, or deployment preferences so you can replicate them on the new site. - Check active deployments. Changes served via the OTTO pixel will stop being served once OTTO is disengaged. However, any changes that were written directly into the site's CMS are not served by the pixel and will remain in place. - Plan quota usage proactively. If you manage multiple clients, consider which sites need active OTTO monitoring and rotate quota only when a project is truly complete. 🛠️ Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🌍 OTTO Geographic Targeting for Africa SEO

🗺️ Overview OTTO, Search Atlas's OTTO SEO automation engine, supports geographic targeting so you can focus your ecommerce growth on specific regions. This guide walks you through every step needed to target African markets — from initial setup through performance monitoring and solving common regional SEO challenges. ⚙️ Step 1: Set Your Geographic Parameters in OTTO Before OTTO can optimize for Africa, you need to define the target region in your project settings. 1. In the left sidebar, click OTTO SEO, then open SEO Automation to access the OTTO dashboard. 2. Select the project you want to target toward African markets. 3. Open Project Settings and navigate to the Geographic Targeting section. 4. In the Target Country / Region field, select the specific African country or countries you want to reach — for example, Nigeria, South Africa, Kenya, Ghana, or Egypt. You can select multiple countries if you are targeting a broader sub-regional audience. 5. Set your Target Language to match the primary language of your audience (English, French, Arabic, Swahili, Portuguese, or others depending on your market). 6. Save your settings. OTTO will now use these parameters to generate recommendations, keyword priorities, and automation actions tailored to your selected region. Tip: If you sell across multiple African sub-regions (for example, West Africa and East Africa), consider creating separate OTTO projects for each region so recommendations remain precise and actionable. 🔍 Step 2: Run a GEO-Specific Audit and Interpret Results With geographic parameters set, run a targeted audit to surface region-specific SEO issues. 1. From the OTTO dashboard, click Run Audit or Re-Scan if an audit already exists. 2. Once the audit completes, filter the results by priority. Look specifically for issues flagged under Content Relevance, Technical SEO, and Local Signals — these categories most directly affect African market visibility. 3. Review keyword gap recommendations. OTTO will surface high-opportunity keywords based on your selected country settings. Pay attention to search volume figures; African markets often show lower absolute volume but significantly less competition, meaning ranking is more achievable. 4. Check hreflang and language signal recommendations. If your site serves multiple African countries with different languages, OTTO may flag missing hreflang tags as a priority fix. Act on OTTO's highest-priority automated fixes first, then move to manual recommendations for content and localization. 🌐 Step 3: Apply Localization Strategies Ranking in African markets requires more than keyword changes. Localization signals tell search engines — and your customers — that your store genuinely serves their region. - Currency: Display prices in local currencies where possible (NGN, ZAR, KES, GHS, EGP). Use OTTO's content recommendations to update product descriptions and meta text that references pricing to match regional expectations. - Language: If your target country uses a language other than your site's primary language, create localized page variants. Use OTTO's content editor to generate or refine translated content and ensure meta titles and descriptions are written in the correct language. - Local Keywords: Apply the keyword suggestions OTTO generates after your geo parameters are saved. These reflect local search behavior — including colloquial product names, regional spelling variations, and locally popular search terms — rather than global search trends. - Local Trust Signals: Add region-specific content such as shipping information for African delivery zones, local return policies, and locally recognizable payment methods (M-Pesa, Flutterwave, Paystack references in content). OTTO's content recommendations may surface these as opportunities. - Structured Data: Ensure your schema markup includes region-relevant details. OTTO will flag missing or incomplete structured data as part of the audit. 📊 Step 4: Monitor Regional Performance After implementing OTTO's recommendations, track progress to confirm your African traffic is growing. 1. Connect or verify your Google Search Console integration inside Search Atlas. This allows OTTO to pull impression and click data filtered by country. 2. In the Search Atlas reporting dashboard, apply a Country filter for your target African nations to isolate regional organic performance. 3. Review metrics weekly: impressions, clicks, average position, and click-through rate for your targeted countries. 4. Return to OTTO's dashboard regularly to pick up new automation opportunities. As your rankings shift, OTTO generates fresh recommendations to maintain and extend your gains. Note: Organic growth in new geographic markets typically becomes measurable within 6 to 12 weeks of consistent optimization. Use impression growth as an early signal before clicks and rankings fully reflect your work. ⚠️ Step 5: Solve Common Africa-Specific SEO Challenges African markets present some unique technical and strategic considerations. Here is how to address the most common ones. - Slow page load speeds: Internet infrastructure varies significantly across African countries, and page speed is a strong ranking and conversion factor. Prioritize OTTO's Core Web Vitals and performance recommendations. Compress images, reduce render-blocking scripts, and enable caching. - Mobile-first audiences: The majority of African internet users browse on mobile devices. Ensure OTTO's mobile usability fixes are completed before other content tasks. - Limited local backlink opportunities: Building regional authority can be slower due to a smaller pool of African-based referring domains. Focus on content quality and use Search Atlas's link-building tools to identify relevant regional directories, news outlets, and industry sites. - Low search volume data: Keyword tools may show limited data for some African markets. Trust OTTO's geo-adjusted recommendations and supplement with manual research using Google Trends filtered to your target country. - Multiple official languages within one country: In markets like South Africa (11 official languages) or Cameroon (French and English), decide which language(s) to prioritize based on your audience segment, then configure OTTO's language settings accordingly. 💬 Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🤖 OTTO SEO Capabilities and Competitor Comparison

🧠 What Is OTTO SEO? OTTO is Search Atlas's AI-powered SEO automation engine. It analyzes your website, identifies on-page and technical SEO opportunities, and creates suggested fixes that you approve and deploy from the dashboard — without requiring manual edits to every page. If you prefer, you can enable OTTO's auto-deploy setting to have approved fixes pushed automatically. You can access OTTO by navigating to OTTO SEO in the left sidebar, then opening SEO Automation inside it (URL: /seo-automation-v3). OTTO goes beyond simple recommendations. It takes action on your behalf by generating optimizations for title tags, meta descriptions, heading structures, internal links, schema markup, and more — which you can review and deploy (or auto-deploy, if enabled) from a single dashboard. 🌍 Does OTTO Analyze GEO-Friendly Content? Yes. OTTO includes capabilities that support GEO (Generative Engine Optimization) — the practice of making your content more likely to appear in AI-generated answers, such as those from Google SGE, ChatGPT, Perplexity, and similar platforms. Specifically, OTTO helps with GEO-friendliness by: - Structured content optimization: Ensuring your content is clearly organized with proper headings, concise answers, and logical flow — the format AI engines prefer to cite. - Schema markup deployment: Adding structured data (FAQPage, Article, Product, Recipe, Organization, Person, and other supported types) per page after you approve the recommendation — or automatically if OTTO auto-deploy is enabled — so AI crawlers can better understand and surface your content. - Entity and topical authority signals: Strengthening the semantic relevance of your pages so AI systems recognize your site as an authoritative source on a topic. - Featured snippet targeting: Identifying and optimizing content that has strong potential to appear in position-zero results, which are also commonly pulled into AI-generated answers. While OTTO does not generate a single "GEO score" displayed as a standalone metric, its optimization actions are directly aligned with the signals that make content perform well in AI-driven search environments. ⚖️ How Does OTTO Compare to Competitors? Here is a straightforward comparison of OTTO against the tools customers most frequently ask about: 📝 OTTO vs. Yoast SEO - Yoast is a WordPress plugin that provides on-page SEO checklists and readability scores. It flags issues but does not fix them automatically. - OTTO operates at a site-wide level and deploys optimizations once you approve them (or automatically, if you enable auto-deploy). It also covers technical SEO, internal linking, and schema — areas Yoast does not address in depth. - Yoast has no GEO-specific features. OTTO's schema and entity optimization directly support GEO performance. 📝 OTTO vs. RankMath - RankMath is also a WordPress plugin with an expanded feature set compared to Yoast, including basic schema options and a content AI add-on. - OTTO is platform-agnostic (not limited to WordPress), streamlines implementation with one-click deployment (and optional auto-deploy) rather than just recommending changes, and integrates with the full Search Atlas suite including keyword research, content tools, and backlink data. - RankMath does not have a dedicated GEO optimization workflow. OTTO's structured data and topical authority features give it an advantage here. 📝 OTTO vs. SurferSEO - SurferSEO focuses on content scoring and NLP-based keyword density recommendations for individual pages. It is primarily a content editor tool. - OTTO handles both content-level and technical SEO across your entire site simultaneously. It also streamlines deployment through the dashboard (with optional auto-deploy) — whereas SurferSEO requires manual implementation of every suggestion. - SurferSEO has no built-in GEO or schema automation. OTTO's automated schema deployment and entity optimization provide a more complete GEO-readiness foundation. 🔗 OTTO and Affiliate Link Management OTTO is not designed as a dedicated affiliate link management tool. It does not automatically add, cloak, or track affiliate links in the way that plugins like ThirstyAffiliates or Pretty Links do. However, OTTO can assist with the SEO aspects of affiliate content by: - Optimizing the on-page structure of affiliate review and comparison pages. - Adding relevant schema (e.g., Product or Review schema) to affiliate content pages. - Improving internal linking to and from affiliate content to boost its authority. If you require full affiliate link management functionality, a dedicated affiliate plugin used alongside Search Atlas is the recommended approach. ✅ Summary: OTTO's Key Advantages - Automation over recommendation: OTTO generates fixes ready to deploy in one click, with an optional auto-deploy setting — it does not just advise. - Site-wide scope: Optimizes hundreds of pages simultaneously, not one at a time. - GEO-readiness: Schema, entity signals, and structured content formatting support AI search visibility. - Fully integrated: Works within the broader Search Atlas platform alongside keyword research, content creation, and backlink tools. - Platform-agnostic: Not limited to WordPress — works with any CMS. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🗑️ How to Delete a Deep-Frozen OTTO Project

❄️ What a Deep-Frozen OTTO Project Means An OTTO project becomes deep-frozen when it has been inactive or paused for an extended period, or when it sits outside your plan's active project quota. While a project is deep-frozen, OTTO stops processing and deploying changes for that website, but the project and its historical data remain stored in your account. Deep-freezing protects your account: it pauses work on projects you are no longer managing so your active clients continue running normally. A frozen project does not consume processing resources, but it may still count toward the total number of projects associated with your account depending on your plan. ​ 🔍 How Deleting Affects Your Other Clients Deleting a deep-frozen project only removes that single project. It does not touch, pause, or alter any of your other active clients. If you have 14 active clients and you delete one frozen project, all 14 active clients remain fully intact and continue running as normal. Each OTTO project is managed independently. There is no shared setting that links one project's deletion to another, so you can safely remove a frozen project without any impact on the rest of your portfolio. ​ 📊 Understanding Quota Limits​ Your subscription plan includes a set number of OTTO project slots. Both active and deep-frozen projects can count toward this quota, which is why a frozen project you no longer need may prevent you from adding a new one. - Active projects are projects OTTO is currently processing and deploying. - Deep-frozen projects are paused but still stored, and may occupy a quota slot. - Deleting a frozen project frees up a slot so you can add a new client in its place.​ If you are at your limit and want to onboard a new website, deleting an unneeded frozen project is the quickest way to make room. ​ 🛠️ How to Delete a Deep-Frozen OTTO Project Follow these steps to remove a frozen project from your account: 1. Log in to the platform and navigate to OTTO SEO → All Sites (SEO Automation). 2. Locate the project list and find the deep-frozen project you want to remove (for example, the frozen domain you no longer manage). 3. Click the options menu (the three dots or settings icon) next to that project. 4. Select Delete Project. 5. Read the confirmation message carefully to make sure you have selected the correct project. 6. Confirm the deletion. The project and its data will be permanently removed, and the quota slot will be freed.​ Once deletion is complete, your project count updates automatically and you can add a new client right away. ​ ⚠️ Important Things to Know Before You Delete​ - Deletion is permanent. Removing a project also removes its historical data and deployed changes. If you may need this project again, consider keeping it frozen instead. - Double-check the domain name. Confirm you are deleting the correct frozen project before confirming, since the action cannot be undone. - Your active clients are safe. Deleting one project never affects the others on your account. - Quota updates instantly. The freed slot becomes available as soon as the deletion finishes.​ 💡 Quick Recap​ Deleting a deep-frozen OTTO project is a safe way to clean up your account and free quota for new clients. The deletion is isolated to that single project, your active clients remain untouched, and the freed slot lets you onboard a new website immediately. If the project may be needed later, keep it frozen rather than deleting it. ​ 💬 Need More Help?​ If you need further assistance, click the chat icon in the bottom-right corner of the platform to start a live chat with a member of our team.

🛠️ OTTO Project Deletion, Restoration, and Domain Changes

🔍 Overview Accidentally deleting an OTTO project or needing to change the domain connected to a project are two of the most disruptive situations you can run into in Search Atlas. This article explains what happens in each scenario, what you can realistically expect, and how to get help quickly if you need a project restored. ⚠️ What Happens When You Delete an OTTO Project Deleting an OTTO project removes it from your workspace. This action is not reversible from within the platform on your own. However, project restoration is possible — it requires escalation to the Search Atlas engineering team and is handled on a case-by-case basis. Important things to know before requesting a restoration: - Restoration does not require you to upgrade your account. - Restoration does not affect your other existing OTTO projects or their edits. - The engineering team will need to investigate the project on their end — this may take time depending on review cycles. - Once confirmed, the project can be fully restored to its prior state. 📋 How to Request an OTTO Project Restoration Because restoration cannot be completed from within the platform, you will need to contact the support team directly. Follow these steps to make the process as fast as possible: 1. Open the chat widget in the bottom-right corner of the platform. 2. Type human teammate to be connected with a member of our support team. 3. Provide the following information in your message: - The domain name of the deleted OTTO project (for example, prescott.com). - Your account email or username. - A brief description of how the deletion occurred and when. - Confirmation that you have not made changes to your account since the deletion, if applicable. 4. The support agent will escalate your request to the engineering team for investigation and restoration. Once the engineering team confirms the project can be restored, they will complete the restoration and notify you through the support chat. 🌐 How Domain Changes Work for OTTO Projects A common reason customers accidentally delete a project is because they are trying to change the domain associated with it — for example, switching from a root domain to a www. version, or moving to a different domain entirely. Currently, the platform does not support modifying the domain on an existing OTTO project directly. If you need to use a different domain or subdomain (such as www.yourdomain.com instead of yourdomain.com), the correct workflow is: 1. Go to Left sidebar → OTTO SEO → All Sites (SEO Automation). 2. Create a new OTTO project using the correct domain from the start. 3. Do not delete the original project until you are confident the new one is set up correctly. This approach avoids accidental data loss and ensures your original project remains intact while the new one is configured. 💡 Tips to Avoid Accidental Deletion - Before deleting any project, confirm you are acting on the correct one — double-check the domain name displayed on the project card. - If your goal is to change or update a domain, create the new project first and verify it before removing anything. - If you are unsure whether deletion is the right action, reach out to support before proceeding. 🚀 What Is Coming in Future Updates The Search Atlas team is actively working on improvements in this area. Planned developments include the ability to support subdomain and staging domain deployments within existing OTTO projects. This will reduce the need to create entirely new projects when a domain variation is required. These features are not yet available, but they are in active development. 💬 Still Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 OTTO Page-Level Schema AI Credit Consumption Explained

🧩 What Is OTTO Page-Level Schema? OTTO's page-level schema feature uses AI to scan each page of your connected website, detect existing structured data, and generate schema markup recommendations tailored to each page type. To access this feature, navigate to Left sidebar → OTTO SEO → Overview (OTTO Grader) → Pending Optimizations and filter by the Page-Level Schema task type, or visit Left sidebar → OTTO SEO → Site Audit → Page Explorer to inspect schema findings on individual URLs.​ 💳 How AI OTT Credits Are Consumed AI OTT credits cover the cost of the AI analysis itself, not the deployment of schema to your site. Every time OTTO's AI engine processes a page-level schema — detecting an opportunity, generating a recommendation, or re-evaluating a previously flagged schema — it deducts approximately 5 AI OTT credits per schema action. Key points to understand: - Credits are debited at the moment the AI processes the schema, before any action is taken on your end. - A single page containing multiple schema types (e.g. Article + BreadcrumbList + FAQPage) will trigger a separate credit deduction for each schema instance. - Credits are consumed whether you approve, dismiss, or leave a recommendation untouched. - Re-crawling a site or refreshing schema analysis on already-scanned pages triggers fresh AI processing and additional credit deductions. 🔎 What 'Found' and 'Review' Statuses Mean When OTTO scans your pages, each schema item is assigned a status that reflects what the AI discovered and whether human input is required. Both statuses consume credits because both involve active AI processing: - Found: OTTO has detected an existing schema on the page and the AI has successfully analysed it. The AI may also generate improvement suggestions. Credits are consumed during this analysis phase. - Review: OTTO has flagged the schema as requiring your manual attention — for example because it is incomplete, contains conflicting markup, or cannot be automatically validated for deployment. The AI has still completed its full analysis to produce this flag, which means credits are consumed even though no schema is automatically applied to your site. You must then manually inspect the item, make corrections if needed, and confirm or dismiss the recommendation in Left sidebar → OTTO SEO → Overview (OTTO Grader) → Pending Optimizations. ⚠️ Why Credits Disappear Faster Than Expected Customers commonly expect credits to be spent only when a schema is successfully deployed. However, because credits pay for AI compute — not the end result — a 'Review' outcome costs the same as a successful deployment. Consider this example: if OTTO scans a site with 200 pages and every page triggers at least one schema finding flagged as 'Review', that alone consumes approximately 1,000 credits (200 schemas × 5 credits each), with no schema yet live on your site. On sites with multiple schema types per page, credit consumption scales proportionally — 200 pages with 3 schema types each could consume up to 3,000 credits in a single crawl cycle. ​ 📊 How to Monitor Your Credit Balance and Usage To understand where your credits have gone, use the following navigation paths: - Avatar (top-right) → Billing → Plans & Top-ups (Top Up / Add-on): View your overall OTTO credit balance and a summary of usage activity for your connected site. - Left sidebar → OTTO SEO → Tasks: See every schema task OTTO has processed. Filter by Page-Level Schema to isolate schema-related actions and review which pages consumed credits. Each task entry shows its current status (Found, Review, Deployed, Dismissed). - Left sidebar → OTTO SEO → Site Audit → Page Explorer: Inspect schema findings at the individual URL level to identify pages with multiple schema types that may have triggered higher credit deductions. ✅ Best Practices to Manage AI OTT Credits Follow these steps to avoid unexpected credit depletion when using OTTO's page-level schema features: 1. Start with a prioritised page set. Rather than crawling your entire site at once, begin with your highest-value pages (homepage, top landing pages, key product or service pages). Navigate to Left sidebar → OTTO SEO → Site Audit → Page Explorer to select specific URLs for schema analysis before running a full-site scan. 2. Resolve 'Review' items promptly. Each unresolved 'Review' item may be re-evaluated in subsequent crawl cycles, consuming additional credits. Navigate to Left sidebar → OTTO SEO → Overview (OTTO Grader) → Pending Optimizations, filter by Page-Level Schema, and address 'Review' flags in deliberate batches to prevent accumulation. 3. Avoid unnecessary re-crawls. Re-crawling a site or triggering a schema refresh re-runs the AI analysis on all pages in scope, deducting credits again even for pages previously processed. Only initiate re-crawls when you have made meaningful content or structure changes. 4. Monitor credit balance during large audits. Check Avatar (top-right) → Billing → Plans & Top-ups (Top Up / Add-on) regularly throughout a large-scale schema analysis to track real-time credit consumption and pause the crawl if needed. 5. Dismiss irrelevant suggestions. If OTTO surfaces a schema recommendation that is not applicable to a page, dismissing it prevents the AI from re-evaluating it in future crawl cycles and avoids repeated credit deductions for the same item. 💬 Need Further Assistance? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🚀 Control OTTO Deployments and Book Onboarding

🎯 Overview Search Atlas offers a guided onboarding experience to help you get the most out of the platform. At the same time, OTTO — our OTTO SEO automation engine — can deploy recommendations automatically, which may raise concerns if you already have high-quality technical SEO and custom schemas in place. This article explains how to book your onboarding call and how to take full control of what OTTO deploys on your site. 📅 How to Book Your Onboarding Call Every Search Atlas account is eligible for a personalised onboarding session with a member of our team. To schedule your call, follow these steps: 1. Log in to Search Atlas and navigate to Home in the left sidebar (URL: /home). 2. Look for the onboarding prompt or playbook on the Home dashboard. Click Browse all playbooks to view available getting-started guides. 3. If you do not see a scheduling link on the dashboard, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team who can book your session directly. During the onboarding call, you can share your existing SEO setup, discuss your goals, and configure OTTO to work alongside your current strategy rather than replacing it. ⚙️ Understanding OTTO Recommendation Deployment OTTO analyses your site and generates SEO recommendations across technical, on-page, and schema categories. By default, OTTO does not automatically publish fixes to your live site — it creates suggestions that you approve and deploy from the dashboard. Automatic deployment only occurs if you explicitly enable OTTO's auto-deploy setting. If your site already has carefully crafted technical SEO settings or custom schemas, it is important to review and control which recommendations OTTO is allowed to apply. Key things to know about how OTTO works: - Suggestions vs. deployments: OTTO first surfaces recommendations. Deployment only happens when a recommendation is approved or when auto-deploy is enabled for a specific category. - Todo List: OTTO maintains a structured to-do list of on-page recommendations so you can review each item before it goes live. - Bulk deploy: OTTO supports bulk deployment for efficiency, but you remain in control of which items are selected before confirming. - Site freeze: You can freeze a site entirely to prevent any OTTO changes from being applied. 🛠️ How to Review and Control OTTO Deployments To manage OTTO recommendations and prevent unwanted changes to your existing SEO or schemas, follow these steps: 1. In the left sidebar, click OTTO SEO → SEO Automation (URL: /seo-automation-v3). 2. You will see your active sites listed. Sites marked Active are eligible for OTTO recommendations and deployments. Sites marked Deep Frozen are fully protected — OTTO will not deploy anything to them. 3. To freeze a site and block all OTTO deployments, select the site using the checkbox and click Freeze sites at the top of the list. Confirm the action when prompted. 4. To review individual recommendations before anything is deployed, click into a specific site and open the Todo List. Here you can approve, skip, or dismiss each recommendation one by one. 5. If you want OTTO to suggest improvements without deploying them automatically, ensure auto-deploy is disabled for sensitive categories such as schema markup and technical SEO. Review each item manually before selecting Deploy. 6. For bulk actions, use Clear selection to deselect all queued items if you want to start a fresh review before deploying. 🔍 Protecting Existing Technical SEO and Schemas If you have invested time in building high-quality technical SEO configurations or structured data schemas, here is how to keep them safe: - Freeze the site immediately after connecting it to OTTO while you review all pending recommendations. This gives you time to audit suggestions without any risk of overrides. - Review schema recommendations individually. OTTO will flag schema opportunities, but you can dismiss any recommendation that conflicts with your existing structured data. - Use the Todo List to track what OTTO has queued. Nothing in the Todo List is deployed until you explicitly approve it (when auto-deploy is off). - Communicate your setup during onboarding. Let the onboarding specialist know which elements of your site are off-limits. They can help you configure OTTO's scope accordingly. 💡 Best Practices for New Accounts - Book your onboarding call before activating OTTO on a live, high-value site. - Start with one lower-priority site to get familiar with OTTO's recommendation style. - Freeze production sites until you have reviewed and approved the initial batch of recommendations. - Check the Todo List regularly to stay on top of new suggestions as OTTO continues to analyse your site. 🙋 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔄 Configuring Projects and OTTO After Domain Migration

🧭 Overview​ Migrating to a new domain raises an important question: should your main site and a subdomain (like a Shopify store) live in one project or two? This guide explains how to structure your projects and configure your OTTO pixels so you capture all of your traffic accurately after a migration. We'll use a common example: a customer who migrated airocidesystems.com to airocide.com and moved their Shopify store to shop.airocide.com. 🏗️ One Project or Two? The general rule is simple: create one project per OTTO pixel installation. Because each project generates a single OTTO pixel, and a pixel lives on one codebase, the answer depends on how your sites are built. - Your main site (airocide.com) and your Shopify store (shop.airocide.com) are almost always on separate platforms with separate codebases. This means each needs its own OTTO pixel, and therefore two projects. - If both addresses were served from the exact same platform and shared one template where a single pixel could fire site-wide, one project could be enough. With a separate Shopify subdomain, this is rarely the case. For the example above, the recommended setup is two projects: one for airocide.com and one for shop.airocide.com. ​ 📁 Setting Up Your Projects​ Follow these steps to create or update your projects after a migration: 1. Open your dashboard and create a new project using your new primary domain, airocide.com. 2. Create a second project for your store subdomain, shop.airocide.com. 3. If you had an existing project for the old domain (airocidesystems.com), keep it for historical reference — the domain of an existing OTTO project cannot be changed in place, so you'll need to create a new OTTO project for the new domain and install its pixel. 4. Confirm each project points to the correct, live URL so crawls and reports reflect your new structure.​ Because an existing OTTO project's domain cannot be edited, moving to a new domain (including www vs non-www) always requires creating a new OTTO project for the new domain and installing its pixel. If your historical OTTO SEO data needs to be moved to a new domain or account (for example, when a migration spans separate accounts), our team can migrate that data for you on request. 🚀 Installing OTTO Pixels Correctly​ Each project provides its own unique OTTO pixel. Install the matching pixel on the matching property: 1. Open the airocide.com project and copy its OTTO pixel script. 2. Add that script to the <head> section of your main site so it loads on every page. 3. Open the shop.airocide.com project and copy its separate OTTO pixel script. 4. Add that script to your Shopify theme so it loads across all store pages. 5. Activate OTTO in each project once the pixel is detected. Installing the correct pixel on each property is what allows OTTO to apply optimizations and capture traffic for both your main site and your store independently. ​ ✅ Verifying Traffic Is Captured​ After installation, confirm that both pixels are firing and traffic is flowing: - Check the pixel status indicator in each project; it should show as connected or active. - Visit a few live pages on each domain and confirm the pixel loads without errors. - Allow some time for data to populate, then review traffic and analytics in each project separately. - If a project shows the pixel or UUID as not detected even though the script is correctly installed, and your site is served through Cloudflare or another CDN, this can be related to how CDN-fronted pixels are detected. A known case of pixels not being detected behind Cloudflare has been resolved; if you still see a not-detected status, start a live chat so we can confirm your setup.​ Because the two properties are tracked in separate projects, you'll review their performance individually rather than as a single combined report. ​ 🔁 Handling Redirects and the Old Domain​ Domain migrations work best when traffic from old addresses is preserved: - Ensure 301 redirects are in place from airocidesystems.com pages to their matching airocide.com pages so link value and visitors transfer smoothly. - You do not need to keep a project or pixel running on the old domain once redirects are live, since visitors will land on your new domain where the new pixel fires. - Monitor your new projects over the following weeks to confirm traffic is consolidating onto the new domain. 💡 Best Practices - Use one project per pixel-bearing property to keep tracking clean and accurate. - To move OTTO to a different domain, create a new OTTO project for the new domain and install its pixel, since an existing OTTO project's domain cannot be changed in place. - Double-check that each pixel is installed on the correct property before activating OTTO. - Confirm redirects are working so no traffic is lost during the transition.​ 💬 Need More Help?​ If you need further assistance, click the chat icon in the bottom-right corner of the platform to start a live chat, then type "Human Teammate" and you'll be connected with a member of our team.

🛍️ OTTO Shopify Changes After Trial Cancellation

📌 Overview Many customers starting a 7-day Starter trial ask the same question: will OTTO's SEO changes stay on my Shopify store if I cancel? The answer depends on how the changes are delivered to your store. This article explains the two delivery methods, what to expect after cancellation, and how to protect your work. 🔍 How OTTO Delivers Changes to a Store OTTO can apply optimizations in two general ways: - Pixel-based deployment: A small JavaScript snippet (the OTTO pixel) is installed on your site. It applies optimizations as your pages load. The changes are delivered by the pixel and are not rewritten in your store's database. - Direct publishing through an integration: OTTO connects to your store and saves updates, such as titles, meta descriptions, or image alt text, in your store's own content fields. Which method applies to you depends on your plan, your store setup, and which OTTO features you use. Not every optimization type is necessarily available through every method. Check the deployment or integration settings for your project in the platform to see how your store is connected. 🧪 What Your Trial Includes The 7-day Starter trial lets you explore OTTO on your connected project. Available features and deployment options during a trial can differ from those on a paid plan. If you need to make permanent changes directly to your store, confirm this before you rely on it. You can do that by checking your project settings or asking our team in chat (see below). ❓ What Happens If You Cancel Here is what to expect, based on the delivery method: - Pixel-based changes: These depend on the pixel being active and your account being in good standing. If your subscription ends, the optimizations will usually stop appearing on your live pages. Your store goes back to how it looked before OTTO. - Changes saved directly in Shopify: Content written into your store's own fields is stored by Shopify. It generally stays in place after cancellation, unless you or someone else edits or reverts it. OTTO will stop making new updates. If you are not sure which method your store uses, review your changes in the Shopify admin. If you see updated titles, descriptions, or alt text in your Shopify product and page fields, those were saved directly in your store. If you only see the changes on the live site or in page source, they are probably pixel-delivered. 🛡️ How to Protect Your Work Before Cancelling 1. Open your OTTO project and review the changes that have been deployed. 2. Note the pages and fields that were updated, such as titles, meta descriptions, headings, and image alt text. 3. Check the same pages in your Shopify admin to see which changes are saved in the store. 4. Copy or export any optimized text you want to keep, so you can re-enter it manually if needed. 5. If you use the pixel, remember that removing or disabling it will also remove its changes from your live pages. 6. Cancel only after you have confirmed what will stay in place. ✅ Quick Answers - Can OTTO work without a JavaScript pixel on Shopify? This depends on your plan and how your store is connected. Check your project's deployment settings or ask our team to confirm for your account. - Will changes remain after I cancel? Changes saved directly in your Shopify store generally remain. Changes delivered by the pixel typically stop appearing once the subscription ends. - Can I undo changes? Yes. You can edit any field in your Shopify admin at any time. For pixel-based changes, removing the pixel reverts them. 💬 Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team. Tell us your store setup and which changes you want to keep, and we can confirm what will happen to your account.

🔍 Finding OTTO PPC and OTTO SEO After UI Update

🗺️ What Changed and Why Search Atlas recently updated its navigation and product naming to make the platform cleaner and more intuitive. As part of this update, the OTTO SEO and OTTO PPC modules were renamed and relocated within the left sidebar. If you previously bookmarked these sections or relied on their old names, they may appear to be missing — but they are still fully available. 📍 Where to Find OTTO SEO OTTO SEO is now accessible in the left sidebar under OTTO SEO, inside the SEO Automation page. To navigate to it: 1. Log in to your Search Atlas account. 2. Look at the left sidebar navigation menu. 3. Click on OTTO SEO in the left sidebar, then open SEO Automation inside it. 4. You will be taken directly to the OTTO SEO automation dashboard (URL: /seo-automation-v3). All of your existing OTTO SEO settings, activated sites, and configurations are preserved — only the label in the navigation has changed. 📍 Where to Find OTTO PPC OTTO PPC has also been integrated under the updated navigation structure. To find it, go to Ads → Google Ads → Campaign Hub (Campaign Hub) in the left sidebar. The module and all your campaign data remain intact. If the OTTO PPC option is not immediately visible after logging in, try the following: - Refresh your browser and check the sidebar again — some menu items load after authentication. - Ensure your subscription plan includes OTTO PPC access, as this feature is plan-dependent. - Clear your browser cache and reload the platform if you are seeing a stale version of the UI. 💡 Tips for Getting Around the Updated UI - Use the search bar (if available at the top of the sidebar) to quickly locate any module by keyword. - Update your bookmarks — old URLs may redirect, but saving the new direct URLs ensures faster access going forward. - Look for new labels — the core functionality remains the same even when a section has been renamed. 🛠️ Still Can't Find What You Need? If you have followed the steps above and still cannot locate OTTO PPC or OTTO SEO in your account, it is possible that your account permissions, plan tier, or a temporary display issue is causing the problem. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🗑️ Delete a Deep Freeze Website in LSEO SEO Automation

🧊 What Is Deep Freeze Mode? Deep Freeze is a paused state for a website project inside LSEO SEO Automation. When a site is frozen, OTTO stops actively optimising it, but the project remains in your account. You can still delete a Deep Freeze project at any time — no waiting period or unfreezing step is required. 🗑️ How to Delete a Deep Freeze Website Immediately 1. In the left sidebar, click OTTO SEO → All Sites (SEO Automation) to open the SEO Automation dashboard (/seo-automation-v3). 2. Locate the website project that shows the Deep Freeze status indicator. 3. Open the options menu for that project (look for the three-dot or kebab menu icon on the project card or row). 4. Select Delete from the dropdown options. 5. Confirm the deletion in the prompt that appears. The project is removed immediately. You do not need to unfreeze the site first, and there is no mandatory waiting period before deletion completes. ⚠️ What to Know Before You Delete - Deletion is permanent. All OTTO configurations, deployed optimisations, and automation history for that site will be erased and cannot be recovered. - Active deployments are not automatically reversed. Any on-page changes OTTO already published to your site remain live. If you want to roll those back, do so before deleting the project. - The website slot is released. Once deleted, the website no longer counts against your connected-site limit, and you can add a different site in its place. ❓ Frequently Asked Questions Do I need to unfreeze the site before deleting it? No. You can delete the project directly from Deep Freeze mode without going through any unfreezing process. How long does deletion take? Deletion is instant. As soon as you confirm the prompt, the project is removed from your dashboard. Can I recover a deleted Deep Freeze project? No. Deletion is irreversible. If you think you may want to use the project again in the future, consider leaving it in Deep Freeze rather than deleting it. Will deleting the project affect my live website? Deleting the project in Search Atlas does not automatically undo changes that OTTO already deployed. Review and reverse any live optimisations through your CMS or site editor if needed before you delete. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Viewing OTTO's Change History on Your Site

What This Article Covers If you need to know what changes OTTO made to a client's site — such as schema deployments or H1 tag updates — this article explains what records are currently available, how to access them, and what to do if you need a full detailed history. Is There a Self-Service Activity Log? At this time, there is no dedicated self-service activity log in the SearchAtlas dashboard that lists every OTTO action with timestamps in one place. The most reliable way to obtain a complete change history is to contact the support team directly, who can retrieve your account's OTTO activity from internal records. How to Request Your OTTO Activity Log 1. Gather any relevant details before reaching out: your site's domain, an approximate date range you want to review, and a description of any specific changes or issues you noticed (for example, a schema deployment, an H1 tag update, or an unexpected site change). 2. Contact the SearchAtlas support team through the chat widget in your dashboard. Provide the domain and date range so the team can look up the relevant records quickly. 3. The support team will pull the activity history from internal records and share the relevant entries with you, which can include details such as which OTTO actions were applied and on what dates. If You Suspect OTTO Changes Caused a Site Issue If you notice problems such as broken navigation menus, missing links, or unexpected layout changes after an OTTO deployment, follow these steps before concluding OTTO is the cause: - Check whether any third-party plugins — for example, multilingual or translation plugins — were recently updated or reconfigured, as these can independently affect site menus and URL structures. - Note the approximate date when the issue appeared and any specific pages affected, then share this information with the support team so they can cross-reference it against your OTTO change records. - Contact the SearchAtlas support team with these details so they can review the activity log and confirm whether any OTTO deployment corresponds to the issue. If you have questions about your OTTO change history that aren't covered here, please reach out to our support team — we're happy to help.

🛡️ OTTO Heading Injection SEO Ethics and Google Compliance

🔍 What Is Heading Injection and Why Does It Matter? OTTO SEO can automatically optimize your page headings (H1, H2, H3, etc.) by injecting or adjusting heading text to improve keyword relevance. When done correctly and visibly, this is a standard and accepted on-page SEO practice. However, if heading text is injected using display:none or similar CSS techniques that hide content from visitors while still exposing it to search engines, this crosses into territory that Google explicitly flags as a spam violation under its hidden text policies. We take this seriously. The sections below explain what was happening, what has changed, and what you can do right now. ⚠️ Does Hidden Text Injection Violate Google's Spam Policies? Yes — Google's spam policies state that hiding text from users while showing it to search engines is a manipulative tactic that can result in manual actions or ranking penalties. Specifically, using display:none, off-screen positioning, or zero-opacity CSS to inject keyword-rich headings that users cannot see violates these guidelines. Search Atlas does not endorse or recommend hidden text as an SEO strategy. If you observed hidden heading text being injected by OTTO in the past, this was not intended behavior and has been addressed. 🛠️ What Has Search Atlas Fixed? Our engineering team has shipped updates directly related to heading injection quality and visibility to ensure that injected headings are visible to users and comply with Google's spam policies. Hidden text injection is no longer the intended behavior of OTTO's heading optimization. 🚧 What Is Still in Development? Our team is currently working on improvements that will allow OTTO to more reliably prevent hidden keyword text and heading injection going forward. This work is actively in development, and further details will be shared when the feature is released. ✅ What You Should Do Right Now 1. Audit your injected headings: Review the headings on your site to confirm they are visible to users. If you find any headings hidden via CSS (such as display:none), note the affected pages and URLs. 2. Contact our team if you find issues: If OTTO has injected hidden headings on your site, reach out so our team can investigate and assist with remediation. Have your project name, affected page URLs, and any relevant details ready when you escalate. 3. Avoid manual workarounds: Do not attempt to patch hidden text injections by editing code directly without guidance, as this may interfere with other OTTO optimizations. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🧊 OTTO Site Slots and Deep Freeze Explained

🔍 What Is Deep Freeze in OTTO? When an OTTO-managed site is placed into Deep Freeze, it is paused and no longer actively managed by OTTO. However, a deep-frozen site continues to occupy one of your OTTO site slots until the freeze period has fully elapsed and the slot is released. 📊 Why Can't I Add a New Site After Freezing One? This is the most common source of confusion. Freezing a site does not immediately release its slot. A deep-frozen site must go through a release period before its slot becomes available again. Until that process completes, your slot count stays the same, and adding a new site may be blocked. Here is what happens step by step: 1. A site is placed into Deep Freeze. 2. The slot remains tied to the frozen site for the duration of the freeze period. 3. Once the freeze period ends, the slot is released and you can assign it to a new site. Until the freeze period ends, the slot remains locked — even if the site appears paused or frozen in the dashboard. ❄️ Does Freezing Multiple Sites Free More Slots? Not immediately. Each frozen site has its own release timeline. Freezing more than one site means multiple slots may eventually become available, but each slot only opens up when its individual freeze period has fully elapsed. Freezing more sites does not shorten the required period or bypass the limitation. 🗑️ Can I Remove a Frozen Site to Free the Slot? Because the exact options available depend on your account and plan, we recommend reaching out to our support team who can confirm the correct process for your specific setup and guide you through it safely. ⏱️ How Do I Check When a Slot Will Be Released? The OTTO SEO section of the platform displays information about your frozen sites and their current status. Check your OTTO dashboard for any available freeze or slot details. If you cannot locate the release information or the slot status is unclear, our support team can look this up for your account directly. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

➕ Add a New SEO Project Without Losing Data

Understanding Your Options If you want to track a new domain in Search Atlas, you may not need to replace or delete any existing project. Whether you can simply add a new project alongside your existing ones depends on how many project slots your current plan includes and how many you have already used. Before taking any action, check your plan's project limit and how many slots are currently occupied. That determines which path below applies to you. How to Check Your Project Slots Log in to Search Atlas and navigate to your account or subscription settings. Look for information about your SEO project limit and how many projects you currently have active. If the number of active projects is lower than your plan's limit, you have an open slot and can add a new domain without touching any existing project. If you are unsure where to find this information in your account, our support team can look this up for you. Option 1 — Add a New Project (Slot Available) If you have an open slot, you can create a new project for the additional domain without affecting any existing project or its data. Navigate to the SEO Projects area of the platform and look for the option to create or add a new project, then follow the on-screen prompts to enter your new domain and complete setup. Your existing projects remain fully intact with all their historical data, tracked keywords, backlinks, and reports. Option 2 — Replace a Project (No Slots Available) If every slot on your plan is occupied, you have two options: upgrade your plan to gain more slots, or remove an existing project to free up a slot for the new domain. Important: Deleting a project permanently removes all data associated with it, including keyword rankings, site audit history, and backlink records. This action cannot be undone. Before deleting any project, export any reports or data you want to keep using the export options available within the relevant tools. To replace a project, delete the project you no longer need through that project's settings or management options, then add the new domain as a fresh project in its place. Option 3 — Upgrade Your Plan If you need to keep all your current projects and still want to add a new domain, upgrading your plan is the cleanest solution. You keep every existing project and its data while gaining additional project slots. You can explore upgrade options by clicking your avatar in the top-right corner, selecting Billing, and opening the Plans & Top-ups tab (Billing). What to Have Ready If You Need Help If you are unsure about your current slot usage, cannot locate the project management area, or run into any issues adding a new project, our team can assist. Please have the following ready: your account email, the domain of the new project you want to add, and the names of any existing projects you are concerned about preserving. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🤖 OTTO SEO Slots, Clients, and Plan Limits

🔍 What Is an OTTO Project Slot? An OTTO project slot is one active OTTO SEO instance connected to a single website. Each slot allows OTTO to audit, optimize, and automate SEO tasks for that specific domain. The number of slots available to you depends on your current subscription plan. 📊 How Many OTTO Slots Does Each Plan Include? The number of OTTO slots varies by plan. On the Starter plan ($99/month), you receive 1 OTTO slot, meaning you can have OTTO actively running on one website at a time. Higher-tier plans include additional slots to support larger client rosters. Check your current plan details inside the platform to confirm your slot allocation. 👥 Can I Use My OTTO Slot Across Multiple Client Accounts? Each OTTO slot is tied to one active project at a time. On the Starter plan, you cannot run OTTO simultaneously on multiple client websites — only one site can be active under that single slot. If you manage several clients and need OTTO running on more than one domain at the same time, you will need to upgrade to a plan that includes additional slots. 🔄 Can I Switch an OTTO Project Between Clients? Yes, you can reassign or swap which website is connected to your OTTO slot. Here is how to do it: 1. Go to OTTO SEO → All Sites (SEO Automation) in the left sidebar (or navigate to /seo-automation-v3). 2. Locate your active OTTO project and deactivate it to free up the slot. 3. Create a new OTTO project and connect it to the new client's website. 4. OTTO will begin onboarding and auditing the new domain. Important: When you switch a slot to a new client, the previous client's OTTO session is paused. Any optimizations already deployed to the previous site remain in place, but OTTO will no longer actively monitor or automate that domain until the slot is reassigned back to it. 💡 Best Practices for Agencies Managing Multiple Clients - Audit your client roster first. Identify which clients need active, ongoing OTTO automation versus those in a maintenance phase. - Prioritize high-activity clients. Assign your available slots to clients with active campaigns or new site launches. - Upgrade for concurrent coverage. If multiple clients need simultaneous OTTO automation, upgrading your plan is the most efficient solution — switching slots frequently can slow down optimization momentum for each client. - Track projects in Reports. Use Reports (left sidebar → Reports, or /report-builder/projects-list) to monitor SEO progress across all client sites, even those not currently assigned an active OTTO slot. ⚙️ How to Upgrade Your Plan for More OTTO Slots 1. Click your avatar in the top-right corner of the platform. 2. Select Billing, then open the Plans & Top-ups tab (Billing). 3. Compare available plans and select one that matches the number of client sites you need to cover simultaneously. 4. Confirm your upgrade — your additional OTTO slots will be available immediately. 🛠️ Summary: Key Things to Remember - The Starter plan ($99/month) includes 1 OTTO slot — one active site at a time. - You can switch which client site uses your slot, but not run multiple sites simultaneously on a single slot. - Previously deployed OTTO optimizations remain on a site even after the slot is reassigned elsewhere. - Upgrading your plan is the best way to support multiple clients concurrently. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🏷️ Tagging and Internal Linking for Bulk Products

🗂️ Why Tagging and Internal Linking Matter for Product SEO When you manage dozens or hundreds of products, a clear tagging system and deliberate internal linking strategy help search engines understand your catalog structure — and help shoppers find what they need. For brand-specific collections like AXIS, these two tactics work together to boost topical relevance and distribute page authority efficiently. 🏷️ Creating Brand-Specific Tags in Shopify Shopify tags are flexible, free-form labels you can apply to products, orders, and customers. For a single brand like AXIS, follow this naming convention to keep tags consistent and filterable: - Use a brand prefix: Format every tag as brand-axis so all AXIS tags are grouped and searchable in your admin. - Add attribute tags: Combine the prefix with product attributes, for example brand-axis__type-jacket or brand-axis__collection-winter24. - Keep tags lowercase with hyphens: Shopify tag searches are case-sensitive, so a consistent format prevents duplicates like "Axis" and "axis" living side by side. - Avoid over-tagging: Limit each product to the tags that are genuinely useful for filtering or automation. Five to ten well-chosen tags per product is a healthy ceiling. To apply tags in bulk across your 67 AXIS products, go to Products in your Shopify admin, filter by vendor or existing tag to isolate the AXIS range, select all, then choose Add tags from the bulk actions menu. 🔗 Building an Internal Linking Strategy for 67 AXIS Products Internal links pass authority between pages and signal to Google which pages are most important. For a focused brand range, structure your links in three layers: 1. Hub page → All AXIS products: Create or designate one main AXIS collection page (e.g. /collections/axis) as the hub. Every AXIS product page should link back to this hub in the product description or breadcrumb. 2. Hub page → Sub-collections: If AXIS products span multiple categories (footwear, apparel, accessories), create sub-collection pages and link to them from the hub. This spreads authority downward and helps crawlers map your catalog. 3. Product page → Related products: On each individual product page, link to two to four complementary AXIS products. For example, an AXIS trail shoe page might link to AXIS trail socks and AXIS gaiters. Use descriptive anchor text like "AXIS waterproof trail socks" rather than generic text like "click here." ⚙️ Implementing Internal Links at Scale in Search Atlas Manually adding links across 67 pages is time-consuming. Use Search Atlas to streamline the process: - Bulk Content Editor: Open the Bulk Content Editor, filter by your AXIS tag, and add a consistent internal link block to all selected product descriptions in one action. - Internal Link Suggestions: Search Atlas surfaces internal linking opportunities based on keyword relevance. Review the suggestions filtered to your AXIS pages and approve the ones that fit. - OTTO SEO Automation: If you have OTTO enabled, it can automatically insert contextually relevant internal links as it optimises your product pages. Enable the internal linking task and set AXIS collection pages as high-priority targets. 📋 Quick-Reference Checklist - ✅ Apply brand-axis prefix to all AXIS product tags in Shopify. - ✅ Use sub-tags for attributes: category, season, or product type. - ✅ Bulk-apply tags using Shopify's admin bulk actions menu. - ✅ Designate one AXIS hub collection page as the internal linking anchor. - ✅ Link every product page back to the hub and to two to four related products. - ✅ Use keyword-rich, descriptive anchor text on every internal link. - ✅ Use the Search Atlas Bulk Content Editor or OTTO to scale link insertion. 💡 Common Mistakes to Avoid - Inconsistent tag naming: Mixing "AXIS," "axis," and "Axis" creates duplicate segments that break filters and automations. - Linking only to bestsellers: Spread internal links across the full AXIS range so newer or lower-traffic pages also receive authority. - Using the same anchor text everywhere: Vary anchor text naturally to avoid over-optimisation flags. - Forgetting to update the hub page: Each time you add a new AXIS product, add a link to it from the collection hub page. 🆘 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Control Auto-Deployed Content in Search Atlas

🔍 Overview Some Search Atlas features can publish or deploy content-related actions automatically, which may feel unexpected if you haven't configured your preferences. This article explains how to get help locating these settings and how to take full ownership of what gets deployed on your behalf. ⚙️ How to Locate and Control Auto-Deploy Settings Because auto-deployment controls can appear in different areas of the platform depending on which feature is active, the exact location of these settings varies. If you are unsure where to find the controls for a specific feature, the steps below will help you escalate quickly so our team can point you to the correct location. To prepare for that conversation, gather the following information before reaching out: - The name of the project or workspace where the content was deployed or is scheduled to be deployed - The name of the specific feature or tool you believe is triggering the auto-deployment (for example, a content planner, AI content template, or scheduled publishing tool) - The approximate date and time the content was published, if it has already gone live - A description of the content item or any relevant URLs - Screenshots of any settings area you have already checked ✅ Best Practices for Staying in Control - Audit your content queue regularly — check for any items that have moved to a scheduled or auto-deploy state unexpectedly. - Review generation and template settings after onboarding — default settings for content tools may have automatic publishing enabled. Confirm whether automatic publishing is on and disable it if you prefer a manual review step before content goes live. - Assign a team reviewer — if you work with a team, designate one person to approve content before it is published. - Verify integration connections — if your site is connected to Search Atlas via a CMS integration, confirm that the integration settings do not allow content to be pushed live without a manual confirmation step on your end. 🙋 Need Help Locating a Specific Setting? If content has already been published that you did not intend to go live, or if you cannot locate the auto-deploy controls for a specific feature, our support team can guide you to the exact setting. Have the information listed above ready so we can assist you as quickly as possible. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚡ OTTO Deployment: Live Site vs. Builder Updates

Overview OTTO applies SEO changes—including heading optimizations, meta updates, and structured data—directly to your live website via script injection. This is intentional: it lets changes go live instantly without waiting for a full rebuild. However, because OTTO writes changes to the live DOM rather than editing your website builder's source files, your builder interface (e.g., WordPress block editor, Webflow, Wix) will not reflect those changes automatically. This article explains the full workflow, how to sync manually, and what to expect from GSC integration and automated keyword research within OTTO. How OTTO Deploys Changes to Your Live Site When you deploy an optimization through OTTO, the change is pushed through the Search Atlas script installed on your site. This script modifies your page's rendered HTML in real time. As a result: - Changes appear on your live site immediately after deployment. - Search engines crawl and index the updated content. - Your website builder's editor still shows the original, pre-OTTO content because the builder reads from its own source database, not the rendered live page. Think of it as a layer sitting on top of your builder. OTTO's layer is what visitors and search engines see; the builder layer is your internal editing environment. The two do not sync automatically. How to Manually Sync Builder Changes After OTTO Deployment To keep your builder consistent with what OTTO has deployed—especially if you plan to edit or rebuild pages later—follow these general steps: 1. In Search Atlas, navigate to the OTTO section and locate the relevant project and page. 2. Review the optimizations that OTTO has deployed for that page, including any heading, title, or content changes. 3. Open your website builder and navigate to the same page. 4. Manually replicate each change—update headings (H1, H2, H3), meta titles, and descriptions to match what OTTO deployed. 5. Save and publish the page in your builder. 6. If you want the builder to serve the content natively going forward, undeploy the corresponding OTTO change to avoid conflicts. Important: Do not edit the same element in your builder without first undeploying OTTO's version. Conflicting edits can cause the builder's republish to overwrite OTTO's live changes. Connecting Google Search Console for OTTO Integration OTTO works alongside your connected Google Search Console (GSC) property to inform its SEO suggestions. To ensure OTTO has the data it needs, you should verify your GSC property is properly connected to your Search Atlas project. Without a verified GSC connection, OTTO may not be able to pull site performance data or fully populate entity and topical information for your project. To connect GSC: 1. Go to your project settings in Sear If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔌 Disconnect OTTO Automation from Google Business Profile

🔍 Overview If you want to stop OTTO from managing a Google Business Profile (GBP) and remove its automation entirely — without using the Deep Freeze option — this article walks you through the correct steps to fully disconnect OTTO from your GBP project. 📋 Before You Start - Deep Freeze vs. Disconnect: Deep Freeze pauses OTTO activity temporarily. The steps below permanently disconnect OTTO from the selected GBP project. - Disconnecting OTTO will stop all automated actions on that profile, including post scheduling, review responses, and any other active automations. - Your existing GBP data and content will not be deleted — only the OTTO automation link is removed. 🛠️ How to Disconnect OTTO from a Google Business Profile 1. In the left sidebar, click OTTO SEO, then open SEO Automation (URL: /seo-automation-v3) to open the OTTO SEO dashboard. 2. Locate the GBP project you want to disconnect — for example, Wafa Masonry — in your list of active OTTO projects. 3. Click on the project name to open its OTTO configuration panel. 4. Look for the Disconnect or Remove Connection option within the project settings. This is separate from the Deep Freeze toggle. 5. Confirm the disconnection when prompted. OTTO will immediately stop all automation for that Google Business Profile. ✅ Verify the Disconnection After completing the steps above, confirm that OTTO has been fully removed: - Navigate to Left sidebar → GBP Projects → Overview (URL: /gbp-galactic/gbp-projects). - Select the affected GBP project from your project list. - Check that no active OTTO automations are listed for the profile. The project should show as unmanaged by OTTO. - You can also review Left sidebar → GBP Projects → My Tasks to confirm no pending OTTO-generated tasks remain for that location. ⚠️ What Happens After Disconnection - Posts: Scheduled posts created by OTTO will be cancelled. Previously published posts remain live on your GBP. - Reviews: Automated review responses will stop. You can still manage reviews manually via Left sidebar → Local → Reviews. - Citations: Any citation work handled under Left sidebar → Local → Local Citations continues independently and is not affected by disconnecting OTTO. - Media: Uploaded media in Left sidebar → Local → Media Library is retained and unaffected. 🔄 Reconnecting OTTO in the Future If you decide to use OTTO automation again for this GBP project, you can reconnect at any time from the OTTO SEO V3 dashboard. Simply locate the project and follow the on-screen setup steps to re-enable automation. 💬 Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔗 Change Your Domain URL in OTTO

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

🤖 Noindex & Robots.txt Without Backend Access

🔍 Understanding the Problem When OTTO SEO is implemented through Google Tag Manager (GTM) rather than the WordPress plugin, you may not have direct access to the website's backend or server files. This means you cannot edit the robots.txt file or add meta tags directly to page templates. This article explains your available options for managing crawl directives in this scenario. ⚠️ Important Limitations to Know First Before choosing a method, understand these key constraints: - robots.txt requires server or hosting access. Without backend access, you cannot directly edit this file. - JavaScript-injected noindex tags (via GTM) are not reliable. Search engine crawlers may not execute JavaScript before deciding whether to index a page, so injecting a noindex meta tag through GTM is not a recommended or dependable method. - OTTO deployed via GTM does not control server-level directives such as X-Robots-Tag HTTP headers or robots.txt entries. - robots.txt Disallow ≠ noindex. Disallowing a URL in robots.txt prevents crawling but does not remove an already-indexed page from search results. A noindex meta tag or X-Robots-Tag header is required for de-indexing. ✅ Recommended Options When You Lack Backend Access Use one of the following approaches depending on what access you do have: 1. Request access from the client's developer or hosting provider. This is the most reliable path. Ask the client to grant you access to edit the robots.txt file via their hosting control panel (e.g., cPanel, Kinsta, WP Engine dashboard) or ask their developer to implement the directives on your behalf. 2. Use Google Search Console to manage indexing. If you have Google Search Console access for the property, you can use the URL Inspection tool to request removal of specific URLs. Note that this is a temporary fix (valid for approximately six months) and is not a substitute for a proper noindex directive. 3. Ask the client to add an X-Robots-Tag HTTP header. This is a server-level solution that functions identically to a noindex meta tag. The client's developer or hosting provider can configure this in the server settings (e.g., Apache .htaccess or Nginx config) without requiring changes to individual page templates. This is the preferred technical alternative when robots.txt and meta tags are both inaccessible. 4. Ask the client's developer to add a noindex meta tag to the page template. If GTM is already implemented, the developer clearly has some site access. Coordinate with them to add <meta name="robots" content="noindex"> directly inside the <head> of the relevant page templates. This is more reliable than injecting it through GTM. 🛠️ What OTTO Can and Cannot Do in GTM Mode It is important to set accurate expectations with your client about OTTO's capabilities when deployed via GTM: - OTTO via GTM can: Inject structured data, update meta titles and descriptions, and make on-page content optimisations that do not require server-level access. - OTTO via GTM cannot: Edit robots.txt, set X-Robots-Tag HTTP headers, or reliably control indexing through JavaScript-injected meta tags. - For full OTTO functionality — including robust robots directives management — the WordPress plugin installation is strongly recommended wherever possible. 📋 Steps to Coordinate With Your Client 1. Identify which pages or sections need to be blocked from indexing. 2. Determine what level of access is available: hosting panel, server config, CMS backend, or developer contact. 3. Share the appropriate directive with whoever has access — either the robots.txt rule, the X-Robots-Tag header configuration, or the noindex meta tag snippet. 4. After changes are implemented, verify them using the URL Inspection tool in Google Search Console or a third-party robots.txt tester. 5. Monitor Search Atlas to confirm OTTO is no longer flagging those pages as indexable. 💡 Pro Tips - Always confirm whether you are working on a subdomain — subdomains require their own separate robots.txt file. A robots.txt on the root domain does not automatically apply to subdomains. - If the site has both HTTP and HTTPS versions or www and non-www variants, ensure the correct canonical version is covered by your directives. Robots.txt rules apply per protocol and per subdomain. - After any robots.txt or noindex change, allow several days to weeks for Google to re-crawl and reflect the update in search results. 💬 Need Further Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team. Additional Notes To get the fastest resolution, have ready: project name and domain, OTTO implementation method, description of goal (noindex/robots.txt/removal), specific pages/URL patterns, current backend/CMS access level, and any error messages with timestamps.

⚙️ Update OTTO Schema and Descriptions

🔍 Overview OTTO can update your website’s cloud schema and meta descriptions. After changes are created or published, the live site may continue showing older data temporarily because deployment, page caching, or content delivery networks can delay the update. 🚀 Start an OTTO update 1. Open OTTO SEO from the left sidebar. 2. Select the relevant project and review its current status. 3. Use Create to generate or update recommendations for schema and meta descriptions. 4. Use Scan when you need OTTO to recheck the current site content before making changes. 5. Review the proposed updates and follow the available publishing or deployment prompts. 📊 Check deployment status After publishing, allow the deployment to finish before checking the live site. A completed action in OTTO does not always mean that every cached version of the page has refreshed. - Confirm that the correct project and domain are selected. - Check whether the update is still processing, queued, or complete. - Verify that the intended URL is included in the project and is accessible to search engines. - Wait for deployment and caching to complete before comparing the page again. 🧪 Verify schema and meta descriptions 1. Open the affected live URL in a private browser window. 2. View the page source or inspect the rendered HTML. 3. Search for the updated meta description and relevant JSON-LD properties, such as Product or hasProduct. 4. Compare the live output with the latest version shown in OTTO. Search results may not update immediately after the page source changes. Search engines can retain previously crawled descriptions until they recrawl the page. 🛠️ Troubleshoot stale live data - Deployment is incomplete: Wait until the update finishes, then verify the URL again. - Page or CDN cache is stale: Purge the relevant cache if your hosting or caching setup provides that option. - Multiple schema sources exist: Check whether your CMS, theme, plugins, or another SEO tool is adding older Product or hasProduct JSON-LD. - The wrong page was checked: Confirm the URL, canonical address, language version, and project domain. - Source and rendered HTML differ: Check the page after JavaScript loads, since some sites add metadata dynamically. - Search results still show old text: This can be normal until the page is crawled again; it does not necessarily mean the deployment failed. ✅ Best practices - Change one set of metadata at a time and record the affected URLs. - Keep only one trusted source for each schema property where possible. - Recheck both the page source and the rendered page after deployment. - Do not repeatedly republish while an earlier deployment is still processing. 💬 Get help If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🔄 Migrate OTTO SEO From WordPress to Wix

🗺️ Overview OTTO SEO is tied to a single website at a time. If you have moved your site from WordPress to Wix, you will need to disconnect OTTO from the old WordPress property and then activate it on your new Wix site. This article walks you through both steps in the correct order. ⚠️ Before You Begin - Complete your Wix site build first. Make sure your Wix site is live and fully set up before starting the migration. - Note your current OTTO settings. Take a screenshot or record any customisations (tone, focus keywords, activated features) you have applied on the WordPress site. You will need to re-apply these on Wix after migration. - OTTO actions are not transferred automatically. Any on-page changes OTTO deployed to your WordPress site stay on WordPress. They will not carry over to Wix. 🛠️ Step 1 — Deactivate OTTO on Your WordPress Site 1. In the left sidebar, click OTTO SEO → All Sites (SEO Automation) (URL: /seo-automation-v3). 2. At the top of the page, click the website selector dropdown and choose your WordPress site. 3. Locate the OTTO Status toggle or the Deactivate OTTO button on the dashboard. 4. Click Deactivate and confirm when prompted. OTTO will stop managing your WordPress site and your OTTO seat will be freed up. 5. If you added the OTTO tracking snippet manually to WordPress, log in to your WordPress admin, navigate to the plugin or theme where you inserted the code, and remove the snippet. 🌐 Step 2 — Add Your Wix Site to Search Atlas If your Wix site is not already listed as a property in Search Atlas, you need to add it before you can activate OTTO. 1. In the left sidebar, click Site Metrics (URL: /site-explorer/list). 2. Click Add New Site (or the + icon) and enter your Wix site URL. 3. Follow the on-screen verification steps to confirm ownership of the domain. 4. Wait for the initial site crawl to complete. This usually takes a few minutes. 🚀 Step 3 — Activate OTTO on Your Wix Site 1. In the left sidebar, click OTTO SEO → All Sites (SEO Automation). 2. Use the website selector dropdown at the top of the page to choose your Wix site. 3. Click Activate OTTO. Search Atlas will generate the OTTO tracking snippet for your Wix domain. 4. Copy the snippet provided and add it to your Wix site: - In your Wix dashboard, go to Settings → Custom Code. - Click + Add Custom Code, paste the snippet, and set it to load on All Pages in the <head> section. - Click Apply and then Publish your Wix site to make the code live. 5. Return to Search Atlas, click Verify Installation, and confirm the snippet is detected correctly. 6. Re-apply any OTTO settings — such as preferred tone, target keywords, and feature toggles — that you previously used on WordPress. ✅ Confirming the Migration Is Complete Once OTTO is active on Wix, you should see the OTTO Status indicator turn green on the OTTO SEO page for your Wix site. Your WordPress site should show OTTO as Inactive. If either status looks incorrect after a few minutes, try refreshing the page. ❓ Frequently Asked Questions - Will my OTTO subscription change? No. OTTO is included with your Search Atlas plan. Moving it between sites does not affect your billing. - Can I run OTTO on both sites at the same time? Only if your plan includes multiple OTTO seats. Check your plan limits in your account settings. - My Wix site is not showing in the site selector. Make sure you completed Step 2 and that the domain is fully verified before trying to activate OTTO. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🌐 Install Search Atlas on lovable.dev via Cloudflare

Overview Installing Search Atlas on a lovable.dev site with a custom Cloudflare domain connection is a known setup scenario that our team has assisted customers with directly. Because the specific steps depend on your project configuration and how your domain is routed through Cloudflare, the verified setup process requires guidance from our support team. What We Know About This Setup This type of installation involves connecting a custom domain managed through Cloudflare to a lovable.dev project, then ensuring the Search Atlas tracking script loads correctly. Common issues customers encounter include DNS misconfiguration, the tracking script failing to communicate with the site, and domain verification not completing as expected. What to Have Ready Before Contacting Support To get this resolved as quickly as possible, please gather the following information before reaching out: - Your lovable.dev project name or URL (for example, the default subdomain assigned to your project) - Your custom domain that you are connecting through Cloudflare - The exact error message you are seeing, if any (copy it in full) - The timestamp when you first encountered the issue - Whether you have already made any changes to your Cloudflare account for this domain (for example, added or edited any DNS records) - The name of your Search Atlas project associated with this site Having these details ready will allow our team to identify your configuration and walk you through the exact steps needed for your setup. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔌 Reconnecting Search Atlas After Website Migration

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

🔄 Migrate Your OTTO Tracking Script Between Websites

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

🛠️ Install OTTO SEO on GoHighLevel Without Duplicates

🔍 Overview When connecting OTTO SEO to a GoHighLevel (GHL) website, some customers encounter a duplicate pixel warning even though only one OTTO script appears visible in the page source. This article explains why this happens, how to install OTTO correctly on GHL, and how to ensure full coverage across your blog, category, and post pages. ⚙️ Why OTTO Detects a Duplicate on GoHighLevel GoHighLevel injects scripts in two separate locations during page rendering: - The GHL funnel/site builder header scripts — scripts you add manually inside the GHL platform settings. - The GHL blog engine header — a separate rendering layer that powers blog listing pages, category pages, and individual post pages. This layer loads its own script block independently. If you add the OTTO pixel to your site-wide header in GHL, the blog engine may also load it as part of its own template, resulting in two instances of the OTTO script firing on blog-related pages. The Search Atlas scanner detects both instances and flags the installation as a duplicate — even if you only see one script tag when inspecting the page manually. This is because browser dev tools often show the merged, rendered DOM rather than each injection source separately. ✅ The Supported Installation Method for GoHighLevel Follow these steps to install OTTO correctly on a GoHighLevel site and avoid duplicates: 1. In Search Atlas, go to OTTO SEO → All Sites (SEO Automation Projects) using the left sidebar (or navigate to /seo-automation-v3). 2. Select your GoHighLevel website and copy your unique OTTO pixel script. 3. Log in to your GoHighLevel account and open the Sites section. 4. Go to Settings → Custom Code (also called Header/Footer Scripts depending on your GHL version). 5. Paste the OTTO pixel script once in the Header field at the site level — do not add it again inside individual funnel steps, blog settings, or page-level script fields. 6. Save your changes and publish the site. Important: Do not add the OTTO pixel inside the GHL blog settings separately. The site-level header script will propagate to all pages including blog pages when configured correctly. Adding it in both locations is the primary cause of duplicate detection. 📄 Covering Blog, Category, and Post Pages A common concern is whether OTTO will activate on GoHighLevel blog listing pages, category pages, and individual post pages — not just the main site pages. Here is what you need to know: - Blog listing and category pages: These are covered by the site-level OTTO pixel as long as you follow the single-installation method above. No additional script is needed. - Individual blog post pages: GHL renders these through its blog engine. The site-level header script covers them provided the pixel is placed in the correct site-wide header field and not duplicated in blog-specific settings. - Funnels vs. websites: If your blog lives on a GHL website (not a funnel), use the website-level Custom Code field. If your blog is part of a funnel, use the funnel-level header script field instead — but again, only once per property. If your OTTO dashboard still shows blog pages as undetected after 24 hours, try clearing your GHL site cache and republishing. The Search Atlas crawler re-checks detection status periodically, and blog pages may take one additional crawl cycle to confirm activation. 🚫 Common Mistakes to Avoid - Adding the script in multiple places: Site header and blog settings, or site header and individual page headers — this always causes duplicates. - Using a third-party tag manager alongside a direct paste: If you are deploying OTTO through Google Tag Manager on GHL, do not also paste the pixel directly in GHL's Custom Code field. - Assuming the browser inspector shows all instances: The rendered DOM view can merge script sources. A duplicate flag from the Search Atlas scanner is reliable — trust it over a manual browser check. 🔄 After Installation — Verifying Detection 1. Return to OTTO SEO → All Sites (SEO Automation Projects) in Search Atlas (/seo-automation-v3). 2. Open your site and check the detection status. Allow up to 24 hours for the crawler to confirm the pixel is active and no duplicate is present. 3. If a duplicate warning persists after following the steps above, review every location in GHL where scripts can be injected (site header, blog settings, individual page headers, and any connected funnels) and remove any extra instances of the OTTO pixel. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🗑️ How to Remove Published and Indexed Cloud Stacks Content

📘 About Cloud Stacks Content Cloud Stacks lets you publish content to web properties (such as cloud storage entities and other hosted pages) to support your SEO strategy. Because this content is hosted externally and can be crawled by search engines, it may become indexed and appear in search results. This article explains what happens when you delete a Cloud Stacks campaign and how to remove content that has already been published or indexed. 🧩 What Happens When You Delete a Campaign Deleting a Cloud Stacks campaign removes the campaign and its management from your Search Atlas dashboard. However, deletion behaves differently depending on where the content lives: - Content managed by Search Atlas: Pages published and controlled through the platform are taken down when the campaign is deleted. - Content on external properties you own: Files pushed to your own connected accounts or storage may remain live until they are manually removed from those accounts. - Search engine index: Deleting a campaign does not instantly remove content from Google or other search engines. The index updates on its own schedule. In short, taking a page offline and removing it from search results are two separate steps. 🚀 How to Delete a Cloud Stacks Campaign 1. Log in to your Search Atlas account. 2. Open the Cloud Stacks tool from the main menu. 3. Locate the campaign you want to remove in your list of campaigns. 4. Select the campaign options menu and choose Delete. 5. Confirm the deletion when prompted. Once confirmed, the campaign is removed from your dashboard along with the content Search Atlas directly manages. 🌐 Removing Content From Web Properties If content was published to properties you own or connected, you may need to remove it at the source: - Sign in to the connected account or storage service where the content was published. - Locate the published files or pages created by the campaign. - Delete the files so the URLs return a 404 (Not Found) or 410 (Gone) status. Returning a 404 or 410 status is important, because it signals to search engines that the page no longer exists, which speeds up removal from the index. 🔍 Removing Already-Indexed Content From Search Results Even after a page is taken offline, it can linger in search results until search engines recrawl it. To speed this up: 1. Confirm the page is offline. Visit the URL and verify it returns a 404 or 410 error. 2. Use Google Search Console. If you own or can verify the property, submit a removal request through the Removals tool. This temporarily hides the URL while the index updates. 3. Wait for recrawling. Once search engines revisit a dead URL, they drop it from the index automatically. This can take days to a few weeks. 🔑 What to Do When You Have No Access to the Sites Customers often ask how to remove indexed content when they do not control the hosting property or its Search Console. If you cannot access the site directly, consider these options: - Request removal through Search Atlas. If the content was published through a Search Atlas-managed property, our team can help take it down. Start a live chat and share the campaign name and the affected URLs. - Use Google's public removal tools. For outdated or removed content on pages you do not own, Google offers a public Remove Outdated Content tool. This works once the page is already offline and returns an error. - Contact the property owner. If a third party controls the hosting, they may need to delete the files before the content can leave the index. ⏱️ How Long Removal Takes Timelines vary based on how often search engines crawl a page: - Search Console removal requests: Content is typically hidden within hours, then permanently dropped after recrawling. - Natural recrawling: Removal from the index usually takes a few days to several weeks. - High-authority or frequently crawled pages: These may be updated faster. ✅ Best Practices Before Deleting - Make a note of every URL published by the campaign before you delete it, so you can track and confirm removal later. - Take content offline first, then submit removal requests once the URLs return errors. - Keep a record of which properties you own versus those managed on your behalf. 💬 Need More Help? If you need further assistance, click the chat icon in the bottom-right corner of the platform to start a live chat with a member of our team. Please have your campaign name and the affected URLs ready so we can help you remove the content quickly.

🛑 Stop an OTTO SEO Background Deploy Job

🔍 Overview When you run OTTO SEO on a project, it can queue background jobs that automatically deploy fixes or publish content to your site. If you notice that a pending job contains incorrect information — such as wrong city or state data pulled into a Content Genius article — it is important to act quickly before the job completes and the content goes live. This article explains how to locate an active OTTO SEO deployment, freeze it to stop further changes, and verify the job has been halted. ⚠️ When Should You Stop a Background Job? - OTTO is about to publish or deploy content with incorrect location data (e.g., wrong cities or states). - A Content Genius article was generated with settings that do not match your actual business location. - You want to review all pending fixes before they go live. - You are making changes to your site and do not want OTTO deploying at the same time. 🧭 How to Locate Your Active OTTO Deployment 1. Log in to Search Atlas and go to Left sidebar → OTTO SEO → All Sites (SEO Automation Projects). 2. On the All Sites page, find the project that has the active background job (for example, your sprinklelaundry.com project). 3. Check the project card for a status indicator showing a pending or in-progress deployment. ❄️ How to Freeze (Stop) the Deployment 1. From Left sidebar → OTTO SEO → All Sites (SEO Automation Projects), locate the project with the active job. 2. Select the checkbox next to the project to highlight it. 3. Click Freeze sites in the toolbar at the top of the page. This immediately pauses all pending OTTO deploy actions for that project. 4. Confirm the project status changes to frozen. No further fixes or content will be deployed while the site is frozen. Important: Freezing a site stops new deployments from going out but does not automatically roll back any changes that have already been applied. See the next section for guidance on reviewing what has already been deployed. 🔎 How to Review What Has Already Been Deployed 1. Go to Left sidebar → OTTO SEO → Site Audit → All Audits to see a full list of fixes OTTO has applied to your site. 2. Go to Left sidebar → OTTO SEO → Site Audit → Page Explorer to review individual pages and the changes made to them. 3. If content has already been published with incorrect location data, you will need to manually edit or delete that content from your CMS or WordPress dashboard. ✏️ Preventing Wrong Location Data in Future Jobs - Before generating a Content Genius article, confirm that your project is set to the correct business location (city and state). - Double-check OTTO's location settings in your project configuration before initiating a scan or deployment. - Use the Freeze sites option any time you want to review pending fixes before they go live. - After making corrections to your project settings, unfreeze the site and re-run the scan to generate a fresh, accurate set of recommendations. 💬 Need Immediate Help Stopping a Job? If you have an urgent deployment in progress that you cannot stop using the steps above, our team can intervene on your behalf. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team. When you reach out, please share the project name, the domain, and a brief description of what the pending job is doing so our team can act as quickly as possible.

🖼️ Fix Inconsistent OTTO Alt Text Suggestions

🔍 Why Alt Text Quality Can Vary OTTO generates alt text by analysing the image file itself alongside the surrounding page context — including the page title, headings, and body copy. When any of these inputs are incomplete or ambiguous, the quality of the suggestion can drop. Understanding the root causes helps you get consistently strong results. Common reasons for inconsistent alt text include: - Generic or unclear image file names — files named IMG_4892.jpg or photo1.png give OTTO very little to work with. - Low page context — pages with thin content, missing headings, or no clear topic make it harder for OTTO to infer what an image represents. - Mixed image types on one page — decorative images, product shots, and infographics all require different alt text approaches, and a mixed batch can produce uneven outputs. - Images with embedded text — screenshots, banners, or graphics containing text are harder for OTTO to interpret accurately without additional context. - Very small or low-resolution images — OTTO has less visual data to analyse, which can lead to vague suggestions. 🛠️ How to Improve Alt Text Consistency Follow these steps to give OTTO the best possible inputs before generating or regenerating alt text. 1. Rename image files descriptively before uploading. Use short, keyword-relevant names such as red-running-shoes-side-view.jpg instead of generic strings. This single change has the biggest impact on output quality. 2. Ensure the page has sufficient content. Navigate to OTTO SEO → All Sites (SEO Automation) (URL: /seo-automation-v3) and check that the target page has a clear H1, at least one H2, and a descriptive body paragraph before running OTTO. 3. Separate image batches by type. If a page contains both decorative and informational images, process them in separate OTTO sessions. This helps the model apply the correct descriptive style to each group. 4. Add a manual hint in the image title or caption field. Where your CMS allows it, fill in the image title or caption before triggering OTTO. These fields are read as additional context. 5. Regenerate suggestions individually for outliers. After a bulk run, review each suggestion. For any that look off, select that image individually and regenerate. A single-image pass gives OTTO a more focused context window. ✅ How to Review and Edit Alt Text in OTTO Once OTTO has generated suggestions, you can review and refine them directly inside the platform. 1. Go to OTTO SEO → All Sites (SEO Automation) (URL: /seo-automation-v3). 2. Select the relevant site and open the page you want to review. 3. Locate the Images section within the OTTO recommendations panel. 4. Click on any alt text suggestion to open the inline editor. 5. Make your edits and click Save to apply the change before deploying. Always aim for alt text that is descriptive, under 125 characters, and relevant to both the image and the page topic. Avoid keyword stuffing — natural, readable descriptions perform better for both accessibility and SEO. 💡 Best Practices for Long-Term Consistency - Establish an image naming convention across your team before assets are uploaded to your CMS. - Run OTTO on pages that are content-complete — avoid generating alt text on draft or placeholder pages. - Review OTTO suggestions before deploying rather than auto-applying in bulk, especially for e-commerce product images where accuracy is critical. - Re-run OTTO after major page content updates — if the page topic changes, existing alt text may no longer be contextually accurate. 🆘 Still Seeing Inconsistent Results? If you have followed the steps above and OTTO is still producing low-quality alt text for specific images, it may indicate an issue with how those images are indexed or served on your site. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔄 Reset OTTO SEO After a Website Rebuild

🧭 Overview When you rebuild your website — for example, migrating to a new Shopify theme or launching a completely new site structure — your existing OTTO SEO project will still hold data from the previous build. This means OTTO may surface issues, recommendations, and audit results that no longer apply to your live site. To fix this, you need to trigger a fresh recrawl so OTTO can discover and analyse your new site from scratch. This article walks you through how to do that. ⚠️ Before You Start Make sure the following are true before triggering a recrawl: - Your new website is fully live. The recrawl will crawl whatever is currently published at your domain. If the new build is not yet live, wait until it is. - Your domain is the same. If your domain has changed, you will need to create a new OTTO SEO project rather than recrawling the existing one. - DNS and Cloudflare settings are propagated. If you made infrastructure changes alongside the rebuild, confirm those are fully propagated before crawling. 🛠️ How to Trigger a Recrawl in OTTO SEO 1. Navigate to OTTO SEO in the left sidebar. 2. Select the project associated with your rebuilt website (for example, trendygardenclub.com). 3. Once inside the project, locate the crawl option for your project and initiate a new crawl of your site. 4. Wait for the crawl to complete. Crawl times vary depending on the size of your site — most sites complete within a few minutes, though larger sites may take longer. 5. Once the crawl finishes, OTTO will update all audit results, issues, and recommendations to reflect your new website build. 📋 What Happens After the Recrawl After a successful recrawl, you can expect the following: - Old issues tied to pages or structures from your previous build will be removed. - New issues specific to your rebuilt site will appear in the audit results. - OTTO's recommendations will reset to reflect the current state of your live site. 🔁 If the Crawl Appears Stuck or Takes Too Long In some cases, a recrawl may appear to be still processing for an extended period. If the crawl status has not updated after an unusually long time, try the following: - Refresh the page and check whether the crawl status has updated. - Navigate away from the project and return to it to force a status refresh. - If the crawl still shows as processing after refreshing, attempt to initiate a new recrawl. If the issue persists, our team can investigate and manually trigger a backend recrawl for your project. When reaching out, please have your project name, domain URL, and a description of when the issue started ready to share. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚡ OTTO SEO Frozen Projects and Quota Management

Overview When you delete an OTTO SEO project, you may notice that your quota does not immediately free up. In most cases, this happens because a frozen project is still occupying a quota slot. Frozen projects are not the same as active or deleted projects — they exist in a suspended state that still counts against your plan limit until they are properly removed. What Is a Frozen OTTO SEO Project? A frozen project is an OTTO SEO project that has been suspended — either automatically by the system or manually — but has not been fully deleted. Frozen projects: - Continue to occupy a quota slot on your account. - Do not appear in your active project list by default. - Block you from creating new OTTO SEO projects if your quota is at its limit. - Remain in a frozen state until they are properly removed. This is the most common reason customers see a full quota even after deleting what appears to be their only project. How to Identify and Remove Frozen Projects To resolve a quota issue caused by a frozen project, you will need to locate any frozen projects in your account and remove them. Frozen projects may not appear in your default active project view, so look for a way to view all projects or filter by status within the OTTO SEO section of the platform (URL: /seo-automation-v3). Because the exact steps to unfreeze and delete a project may vary depending on your account and the current version of the platform, we recommend reaching out to our support team directly so they can guide you through the correct process for your account and confirm that the quota slot has been fully released. What to Have Ready When You Contact Support To help our team resolve your quota issue as quickly as possible, please have the following information ready: - Your account name or the email address associated with your Search Atlas account. - The name of the OTTO SEO project (or projects) you believe may be frozen. - The current quota count shown in your account (e.g., "3 of 3 slots used"). - Any steps you have already taken to try to delete or remove the project. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Service Page Type Suggested But No Schema to Deploy

🔍 Overview When OTTO SEO analyses your site, it assigns a page type to each URL and then recommends schema markup to deploy based on that classification. In some cases, OTTO may label a page as the Service page type but not present a corresponding Service schema option in the deployment area. This article explains what this means and how to get it resolved. 💡 Why Does This Mismatch Happen? The page-type classification and the schema deployment options are handled by two separate systems inside OTTO. A page type label (such as Service) is determined by AI analysis of your page's content and structure. The schema types available to deploy are filtered by a separate rules engine before surfacing any option. When these two systems produce results that do not align — for example, OTTO classifies a page as Service but no matching schema option appears — this is a backend mismatch that our engineering team needs to investigate. It is not something you can resolve by changing settings inside the platform. ⚙️ What You Should Do If you encounter this issue, please contact our support team so we can escalate it for investigation. To help us resolve it as quickly as possible, please have the following information ready before reaching out: - Your project name as it appears in Search Atlas. - The exact URL(s) where the Service page type is assigned but no schema deployment option appears. - A screenshot of the affected page showing the page type label and the empty schema deployment area, if possible. - Any error messages displayed on the screen, copied exactly as shown. With these details in hand, our team can identify whether the issue is a misclassification, a filtering rule, or a deeper bug, and work to get the correct schema options surfaced for your pages. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔄 OTTO Automatic Re-Scanning After Knowledge Graph Updates

🤖 How OTTO Handles Knowledge Graph Updates If you're unsure whether OTTO automatically re-scans your site after a Knowledge Graph update — or whether a manual trigger is needed — this behavior has not been fully confirmed through our support documentation. The specifics of how OTTO responds to Knowledge Graph changes (automatic vs. manual re-scan) may vary, and the Search Atlas team is best placed to clarify the current behavior for your account and project setup. 📋 What to Do If You've Updated Your Knowledge Graph If you've recently made changes to your Knowledge Graph (such as adding business details, updating entity relationships, or refining brand information) and you're not seeing updated recommendations in OTTO, gather the following information before reaching out so our team can investigate and assist you quickly: - Project name: The name of the website project in your Search Atlas account where OTTO is active. - Description of the Knowledge Graph change: What you updated (e.g., added a new entity, changed business information). - Approximate time of the change: When the Knowledge Graph update was made. - Current state of recommendations: What you currently see in OTTO's recommendations and what you expected to see instead. Having these details ready will allow our support team to identify what happened, confirm the expected behavior, and help you get OTTO reflecting your latest Knowledge Graph data as quickly as possible. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⏸️ Pause OTTO Changes While Preserving Completed Work

🔍 Overview OTTO continuously applies SEO changes to your connected sites. If you want to stop new changes from being made — without undoing anything already done — you can pause OTTO activity for a site inside the OTTO SEO section. This suspends future OTTO activity while keeping every completed change intact. ❄️ How to Pause OTTO Activity on a Site Pausing a site is the fastest way to stop OTTO without losing any work already applied. To do this, navigate to OTTO SEO → All Sites (SEO Automation) in the left sidebar, locate the site you want to pause, and use the available site management options to suspend OTTO activity for that site. Once paused, OTTO will stop all automated activity for that site — no new changes will be queued or deployed. Everything OTTO has already completed remains live on your site exactly as it was applied. ✅ What Happens to Completed Work Pausing a site does not roll back or remove any changes OTTO has already made. All optimisations OTTO completed before the pause remain in place, and your site continues to benefit from that work. Only future changes are suspended. ▶️ How to Resume OTTO When You Are Ready You can resume OTTO activity at any time. Navigate to OTTO SEO → All Sites (SEO Automation) in the left sidebar, find the paused site, and use the available site management options to reactivate it. OTTO will resume applying changes from where it left off. 🔄 Understanding the Rollback Option Pausing a site is different from rolling back changes. Keep these distinctions in mind: - Pause: Suspends all future OTTO activity. Completed work stays in place. This is the right choice when you want to stop new changes without undoing anything. - Rollback: Reverts specific changes that OTTO has already applied. Use this only if you want to undo a particular optimisation, not simply pause future activity. If you only want to stop further changes — not remove what is done — always use the pause option rather than a rollback. 💡 Tips for Managing OTTO Activity - You can pause multiple sites at once using the site management options in the OTTO SEO → All Sites (SEO Automation) section. - Pausing is fully reversible — resume OTTO at any time without losing your place in the workflow. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Squarespace /home Redirect with OTTO

🔍 Understanding the Squarespace /home Issue Squarespace automatically redirects your root domain (yourdomain.com) to yourdomain.com/home. This behaviour is built into Squarespace's platform and cannot be disabled from within Squarespace itself. When OTTO crawls and optimises your site, this forced redirect can cause it to treat / and /home as two separate pages, leading to duplicate content signals and index confusion. This is a known platform-level limitation with Squarespace, not a bug within OTTO. The sections below explain how OTTO currently handles this and what steps you can take to minimise its impact. ⚙️ How OTTO Handles the /home Redirect OTTO's infrastructure recognises the /home redirect pattern common to Squarespace sites. When OTTO detects this redirect during its crawl, it attempts to consolidate signals from both URLs and treat the root domain as the canonical home page. However, depending on your site's configuration, some duplication flags may still surface in your reports. This is expected behaviour while Squarespace enforces the redirect at the server level. 📊 What You May See in Your Reports - Duplicate page warnings — OTTO or your audit report flags both / and /home as separate URLs with identical content. - Index coverage issues — Google Search Console may show both variants being crawled or indexed. - Home page listed twice — Your site's internal link structure may reference both versions of the URL. These findings do not necessarily indicate a critical SEO problem, but resolving them will improve your site's clarity for search engines. 🚀 Steps to Reduce Duplication Impact 1. Set a canonical tag on your home page. In Squarespace, navigate to Pages → Home Page → SEO Settings and ensure the canonical URL points to your root domain (yourdomain.com/), not yourdomain.com/home. This tells search engines which version is authoritative. 2. Update your internal links. Check that all internal links pointing to your home page use the root domain format (yourdomain.com/) rather than the /home variant. Consistent internal linking reinforces the canonical signal. 3. Submit your preferred URL to Google Search Console. Use the URL Inspection tool in Google Search Console to request indexing of yourdomain.com/ and confirm it is the version Google recognises as canonical. 4. Re-run an OTTO crawl after making changes. In Search Atlas, go to OTTO SEO → All Sites (SEO Automation) in the left sidebar, then trigger a new crawl of your site. This allows OTTO to pick up your updated canonical signals and refresh its analysis. 5. Monitor your index coverage report. After a few days, revisit Google Search Console to confirm that only the preferred URL is being indexed and that duplicate warnings have been resolved. 💡 Squarespace Platform Limitations to Keep in Mind Because the /home redirect is enforced by Squarespace at the infrastructure level, neither OTTO nor any third-party SEO tool can fully prevent Squarespace from issuing this redirect. The steps above represent the most effective workarounds available within Squarespace's constraints. Squarespace has historically maintained this behaviour across plan types, so it is important to manage it proactively rather than waiting for a platform change. If Squarespace releases an update that allows users to disable or modify the /home redirect, OTTO's integration will continue to adapt accordingly. Search Atlas monitors these platform changes and updates OTTO's crawl logic as needed. 🛠️ Still Seeing Issues After Following These Steps? If you have completed all the steps above and are still experiencing duplication warnings or unexpected behaviour with your Squarespace home page in OTTO, our team is here to help investigate your specific site configuration. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 OTTO Deployment: H1/H2 Tag Changes Affecting Page Titles

🔍 What Happens to Page Titles After OTTO Deployment? After deploying OTTO on a Shopify site, you may notice that some page titles have changed unexpectedly. This is a known behavior caused by how OTTO applies on-page optimizations. OTTO can modify H1 and H2 tags as part of its on-page SEO optimizations. Depending on how your Shopify theme is structured, changes to these heading tags may affect the visible page title displayed on your storefront. This can be surprising if you were not expecting visual changes to your storefront content. If the new titles do not match your brand or content preferences, you can reverse them by undeploying the relevant OTTO optimizations from within the OTTO dashboard. 📋 Before You Begin - Make a note of the affected pages and their original titles before making any changes. - Ensure you have access to your Search Atlas account with OTTO configured for your Shopify site. - Navigate to the OTTO SEO section in your Search Atlas account to access the OTTO dashboard. 🔄 How to Undeploy H1/H2 Tag Changes in OTTO 1. Open the OTTO dashboard from the OTTO SEO section of your Search Atlas account. 2. Select the website profile that was affected by the unexpected title changes. 3. Locate the area of the dashboard where your deployed optimizations are listed. 4. Identify the H1 or H2 tag optimizations applied to the pages whose titles were affected. 5. For each affected page, use the available option to undeploy or reverse the H1/H2 tag optimization. 6. Repeat for all pages where the title was changed unexpectedly. If you are unsure which specific optimizations to undeploy, or if you cannot locate the relevant controls in your dashboard, please reach out to our support team for guidance — have your website profile name and a list of the affected page URLs ready so the team can assist you efficiently. ⏱️ How Long Does It Take for Changes to Sync? After undeploying an optimization, the reversal may not appear instantly on your Shopify storefront. Allow some time for the change to propagate before checking whether your original titles have been restored. Avoid re-deploying any H1/H2 optimizations on the same pages until you have confirmed the original titles have been restored. ✅ How to Verify the Titles Have Been Restored After allowing sufficient time for the changes to propagate, visit the affected pages on your Shopify storefront and confirm that the original page titles are displaying correctly. If the titles have not reverted as expected, contact our support team with the affected page URLs, your website profile name, and a description of the issue. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🌐 Scoping OTTO SEO on Multilingual Sites

🔍 Overview OTTO SEO is a site-wide automation tool. It is not possible to deploy OTTO exclusively to a single subdirectory, such as /pl/, /de/, or any other language path on a multilingual site. This is a platform-level constraint, not a configuration gap — no combination of settings will change this behaviour. This article explains why this limitation exists, clears up outdated guidance that may reference unavailable interface elements, and outlines the correct approach to safely test OTTO on one language version of your site. ⚠️ About Outdated Guidance Earlier guidance referred to these controls by several different names (URL Exclusions, Crawl Settings, Site Settings). In the current interface, the supported way to limit which URLs OTTO processes is the URL Exclusion conditions list in your project's OTTO SEO Settings (open the project and click the Autopilot / Smart Crawl card), or the URL exclusions list in the Site Audit Crawl Settings modal. These exclude specific URLs from a project's crawl scope — they do not allow activating OTTO on only one subdirectory of a domain. The steps in this article reflect the verified Search Atlas interface as of October 2026. 🚫 Why OTTO Cannot Be Scoped to a Subdirectory When you activate OTTO on a domain, it operates across the entire connected domain by design. This ensures that technical SEO fixes, schema deployments, and content recommendations are applied consistently and do not create conflicts between different sections of the same site. Restricting OTTO to a subdirectory path such as /pl/ is not supported because: - OTTO links to a root domain or subdomain, not a URL path. - Partial activation can produce conflicting signals across language versions. - Crawl and automation logic is tied to the domain-level project, not individual URL patterns. ✅ Correct Approach: Isolate Testing Using a Separate OTTO Project The only supported method to isolate OTTO activity to a single language version is to use that language version as a dedicated subdomain and connect it as its own OTTO project. If your site already uses subdomains per language (for example, pl.example.com), you can connect that subdomain directly. If your site uses subdirectories (for example, example.com/pl/), you will need to evaluate whether a subdomain structure is feasible before OTTO can be scoped to that language version. 1. Go to Left sidebar → OTTO SEO → All Sites (SEO Automation) (URL: /seo-automation-v3). 2. Click Create in the top toolbar to start a new OTTO project. 3. When prompted for the domain, enter the subdomain for the language you want to test — for example, pl.example.com. 4. Complete the project setup. This new project will operate entirely independently from any OTTO project connected to your root domain or other language subdomains. 5. Activate OTTO on this project only. Your root domain and other language versions remain unaffected. This approach gives you a clean, isolated environment to evaluate OTTO's impact on one language version before rolling out to additional domains or subdomains. 🌍 If Your Site Uses Subdirectories, Not Subdomains If your multilingual site is structured with subdirectories (example.com/pl/, example.com/de/) rather than subdomains, OTTO cannot be isolated to any one of those paths. In this situation, your options are: - Test on a staging environment: Set up a staging subdomain that mirrors your target language version and connect OTTO to that staging subdomain for evaluation. - Full-site activation: Activate OTTO on the root domain understanding that it will operate across all language subdirectories. Review OTTO's recommended actions carefully before approving any bulk changes. - Migrate to a subdomain structure: If long-term per-language control is a priority, consider restructuring the multilingual architecture to use subdomains. This is a broader technical decision that falls outside the scope of OTTO configuration. 📋 Current OTTO SEO Navigation Reference Use the following confirmed navigation paths when working with OTTO projects in the current interface: - OTTO SEO dashboard: Left sidebar → OTTO SEO → All Sites (SEO Automation) | URL: /seo-automation-v3 - Create a new OTTO project: OTTO SEO dashboard → click Create - View active projects: OTTO SEO → All Sites (SEO Automation) → Active 4 filter - Freeze or manage sites: OTTO SEO dashboard → select a site → click Freeze sites If you do not see the OTTO SEO option in your left sidebar, your account plan may not include OTTO access. Contact support via the method below to confirm your plan entitlements. 💬 Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🖼️ OTTO Alt-Text Suggestions for Missing Images Explained

🔍 Why OTTO Suggests Alt-Text for Images You Can't See If OTTO is recommending alt-text for an image that doesn't appear to be on your page, this may be caused by images that are present in the page's HTML source but are not visually prominent in the normal rendered view. This can include tracking pixels, placeholder assets, hidden section backgrounds, or template components injected by your CMS or funnel-builder platform. OTTO scans the raw HTML of your page, not the rendered visual layout. This means it detects every <img> tag in the source, including images that may not be immediately visible to you when browsing the page. This behaviour is intentional — OTTO flags all missing alt-text to ensure full accessibility and SEO compliance. ✅ How to Handle These Suggestions You have two straightforward options when OTTO surfaces an alt-text suggestion for an image you cannot locate visually: 1. Accept the suggestion. If the image exists in your source code, adding descriptive alt-text is still the correct SEO and accessibility practice. Review the suggested text and apply it if it is accurate. 2. Dismiss the suggestion. If you have confirmed the image is a tracking pixel, a decorative placeholder, or an artifact with no meaningful content, you can dismiss the task within OTTO. To inspect whether the image actually exists in your page source, right-click your page in a browser and select View Page Source, then search for the image file name or URL associated with the suggestion. This confirms the image is present even if invisible in the rendered view. 🗺️ Navigating to OTTO in the Platform OTTO is accessible within the Search Atlas platform. Once there, you can view all active OTTO tasks, including alt-text suggestions, grouped by site and category. If you manage multiple sites, navigate between your projects within the platform to view their respective task queues. 📋 Understanding OTTO Deployments When OTTO is deployed on a site, it audits the page source for accessibility and SEO issues — including missing alt-text on any image element it finds in the HTML. This includes images that may not be immediately visible in a standard browser view. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 OTTO Pixel Removal and SEO Work Preservation

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

🔍 Why OTTO Detects H2 Headings From Wrong Sections

🧭 Overview OTTO analyzes your page's HTML structure to identify headings and generate SEO suggestions. Occasionally, customers notice that OTTO is pulling H2 headings from sections like FAQs, sidebars, or footers rather than the main content area. This article explains why that happens and what you can do about it. 🤔 Why Does This Happen? OTTO crawls the raw HTML of your page exactly as a search engine would. It reads all H2 tags present in the page's source code, regardless of where they visually appear on the page. This means if your FAQ section, sidebar, or any other page component uses H2 tags, OTTO will include them in its analysis. Common reasons OTTO picks up H2 headings from unexpected locations include: - FAQ sections using H2 tags: Many FAQ plugins and themes mark each question with an H2 tag, which places them at the same heading level as your main content headings. - Widgets and sidebars: Some themes apply H2 tags to widget titles or sidebar section headers. - Page builders: Drag-and-drop builders sometimes assign H2 tags to decorative or secondary elements by default. - Third-party embeds: Scripts or embedded components can inject their own heading tags into your page HTML. ⚙️ Is This an OTTO Issue or a Website Code Issue? In most cases, this is a website code or theme structure issue, not a bug in OTTO. OTTO is correctly reading the heading hierarchy that exists in your HTML. When non-primary content like FAQs uses H2 tags, it signals to both OTTO and search engines that those elements share equal importance with your core content headings — which may not reflect your intent. That said, OTTO uses the heading data it finds to generate crawl suggestions. If the heading structure it reads is inconsistent with your page's actual content hierarchy, the suggestions it produces may feel off-target. 🛠️ How to Fix Heading Structure on Your Page To help OTTO — and search engines — correctly interpret your page structure, review and update your HTML heading tags as follows: 1. Audit your page HTML: Right-click your page in a browser and select View Page Source or use browser developer tools to search for all H2 tags. Note which sections they belong to. 2. Reclassify FAQ and secondary headings: Change FAQ question headings, sidebar titles, and widget headers from H2 to H3 or H4 tags. Reserve H2 tags for your primary content sections only. 3. Check your theme or page builder settings: Many themes and builders let you change the heading level for specific components without editing code directly. Look for a "Heading Tag" or "HTML Tag" dropdown in your FAQ plugin or widget settings. 4. Re-run OTTO after making changes: Once you have updated your heading structure, navigate to OTTO SEO in the left sidebar, open SEO Automation, and allow OTTO to re-crawl the page. OTTO will then reflect the corrected heading hierarchy in its suggestions. ✅ Best Practices for Heading Structure Maintaining a clean heading hierarchy benefits both OTTO's analysis and your overall SEO performance. Follow these guidelines: - Use one H1 tag per page for the primary page title. - Use H2 tags only for main content sections that directly support the page's primary topic. - Use H3 and H4 tags for subsections, FAQs, sidebars, and supporting content. - Avoid skipping heading levels (e.g., jumping from H1 to H4), as this can confuse crawlers. - Treat your heading structure as an outline — it should reflect the logical flow and priority of your content. 💬 Still Seeing Unexpected Heading Suggestions? If you have corrected your heading structure and OTTO is still pulling headings from the wrong locations, or if you are unsure how to update your site's HTML, our team is here to help. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⏳ OTTO Pixel Verification After Site Audit

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

🔗 Fix Unwanted URL Parameters in Canonical Links

🧭 Overview When you run a Screaming Frog crawl on a site managed with Search Atlas, you may notice canonical links containing an extra URL parameter: is_otto_page_fetch=1. This parameter is appended by Otto, the Search Atlas automation engine, during page fetches for analysis. It is an internal crawl signal and should never appear in your canonical tags on the live site. If it does, search engines may index the wrong canonical URL, which can negatively affect your SEO. This article explains why this happens, how to verify the issue, and the exact steps to resolve it inside Search Atlas and Screaming Frog. 🔍 Why This Parameter Appears Otto adds is_otto_page_fetch=1 to page requests so it can identify its own crawl traffic internally. Under normal circumstances this parameter exists only in the HTTP request and is never written to the page's HTML. However, if your site or CMS dynamically generates canonical tags based on the current request URL, the parameter can be captured and rendered inside the <link rel="canonical"> tag. This is a site-side configuration issue that Search Atlas tooling can help you detect and fix. ✅ Step 1 — Confirm the Issue in Screaming Frog 1. Open Screaming Frog and crawl your site. 2. Click the Canonicals tab in the lower panel. 3. In the filter dropdown, select Contains a Canonical URL. 4. Export the list and search for any canonical value containing is_otto_page_fetch=1. 5. Note the affected URLs. If only a handful appear, the issue is likely isolated to pages with dynamic canonical logic. If the parameter is widespread, your CMS is globally reflecting request parameters into canonical tags. ⚙️ Step 2 — Configure Parameter Filtering in Search Atlas Search Atlas lets you define URL parameters that should be stripped before canonical evaluation. Follow these steps: 1. Log in to Search Atlas and navigate to your project. 2. Open Settings and select Crawl Configuration. 3. Scroll to the URL Parameter Exclusions section. 4. Click Add Parameter and enter is_otto_page_fetch (without the value). 5. Save your settings. Otto will now strip this parameter from all URLs before they are evaluated, reported, or compared against canonical values. After saving, re-run your site audit from within Search Atlas. The parameter should no longer appear in canonical link reports generated by the platform. 🛠️ Step 3 — Fix the Canonical Tag on Your Site Even after adjusting Search Atlas settings, you must prevent your site from writing the parameter into the canonical tag in the first place. The correct fix depends on your CMS or framework: - WordPress (Yoast / Rank Math / All in One SEO): These plugins build canonical URLs from get_permalink() rather than the raw request URL, so they are usually not affected. If you are using a custom canonical filter or a theme function that reads $_SERVER['REQUEST_URI'], update it to use get_permalink() or home_url(add_query_arg(array(), false)) with query args explicitly stripped. - Custom CMS / server-side rendering: Locate where the canonical meta tag is built and ensure the URL is constructed from the canonical page path, not the live request URL. Strip all query parameters before inserting the value into the tag, or maintain an explicit allowlist of parameters that are permitted in canonicals. - Cloudflare / CDN or edge workers: If a worker or transform rule is injecting or reflecting parameters, add a rule to strip is_otto_page_fetch before the canonical tag is generated or cached. 📋 Step 4 — Re-Crawl and Verify in Screaming Frog 1. After updating your site, clear any full-page cache (WordPress cache plugins, Varnish, Cloudflare cache, etc.). 2. Return to Screaming Frog and run a fresh crawl. 3. Go back to the Canonicals tab and re-export the list. 4. Confirm that no canonical URLs contain is_otto_page_fetch=1. 5. If affected pages had previously been indexed with the incorrect canonical, submit them via Google Search Console under URL Inspection > Request Indexing to prompt Google to re-evaluate the correct canonical. 🚫 Common Mistakes to Avoid - Only fixing it in Screaming Frog settings: Configuring Screaming Frog to ignore the parameter hides it from reports but does not fix it on your live pages. Always fix the source. - Caching old pages: If your CDN or server cache is serving stale HTML, the bad canonical will persist even after a code fix. Always purge caches after making changes. - Blocking Otto entirely: Blocking the Otto crawler user agent in robots.txt will prevent Search Atlas from auditing your site. Instead, use the parameter exclusion settings described in Step 2. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 OTTO and High Level H1 Tags Explained

🔍 What Is This Article About? If you've activated OTTO on your High Level website and your H1 tags don't seem to be changing in your CMS backend, you're not alone. This article explains exactly how OTTO applies SEO changes, why High Level sites behave differently, and how to confirm OTTO is actually working correctly. ⚙️ How OTTO Actually Makes Changes OTTO does not edit your CMS backend. This is the most important thing to understand. OTTO works exclusively through front-end DOM injection, which means it rewrites page elements in the browser at the moment a page loads — it does not write changes directly into your High Level page builder, database, or any backend system. Here is what that means in practice: - Your H1 tag in the High Level editor will look unchanged — this is expected and correct. - When a real visitor (or a search engine crawler) loads your page, OTTO's pixel intercepts the page and injects the updated H1 before the content is rendered. - The change is real and visible to search engines, but it lives on the front end, not inside High Level's backend. OTTO is not hallucinating or malfunctioning when your CMS shows the original tag. That is how the technology is designed to work. 🌐 Why High Level Sites Work This Way High Level is a closed CMS platform. OTTO cannot directly edit the source files or database records of a High Level site. Instead, OTTO's pixel — a small JavaScript snippet installed on your site — runs on every page load and applies your approved SEO optimisations in real time at the browser level. This approach works across any website platform without requiring backend access. ✅ How to Confirm OTTO Is Working on Your Site Follow these steps to verify that OTTO's H1 changes are being applied correctly on the front end: 1. Open your website in a browser and navigate to the page where the H1 change was approved. 2. Right-click anywhere on the page and select Inspect (or press F12) to open your browser's developer tools. 3. Click the Elements tab and look for the <h1> tag in the HTML. 4. If OTTO is working, you will see the updated H1 text that OTTO injected — even though your High Level editor still shows the original text. 5. You can also right-click the visible H1 on the page and choose Inspect Element to jump directly to that tag. If the injected H1 appears in the browser's developer tools, OTTO is functioning correctly. 🚀 How to Access and Manage OTTO Settings To review and manage your OTTO optimisations, log in to your Search Atlas account and navigate to the OTTO section of the platform. From there you can review approved optimisations, check the status of your pixel installation, and confirm which changes have been applied to your site. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔄 Fix Missing OTTO Data After V2 to V3 Migration

🧭 Overview After Search Atlas migrated from V2 to V3, some projects may display missing or zeroed-out data in the OTTO dashboard — including Content, Authority, Technical, and UX Signals sections. This is a known side effect of incomplete data migration and is not necessarily caused by a missing or broken OTTO Pixel installation. If your project shows empty metrics right after the platform upgrade, this is likely a backend migration data issue that our support team will need to investigate and resolve on your behalf. ⚠️ How to Recognise a Migration Data Issue You are likely experiencing a migration-related data gap — not a pixel or tracking error — if you notice any of the following: - Content, Authority, Technical, or UX signal panels show zero values or blank states - The issue appeared shortly after your account was upgraded to V3 - Some projects display data correctly while others do not - OTTO Pixel is confirmed as installed on your site, yet data is still missing - Re-checking the pixel or re-connecting Google Search Console has no effect 🛠️ What to Do Because this is a backend migration issue, there are no self-serve steps guaranteed to restore your data. Attempting workarounds on your own may not be effective. Instead, please contact our support team directly so they can investigate your specific projects and restore the missing data on the backend. When you reach out, please have the following ready so we can resolve your issue as quickly as possible: - The name(s) of the affected project(s) and the associated domain(s) - Confirmation of which signal sections are missing (Content, Authority, Technical, UX, or a combination) - Approximately when the data disappeared or when you first noticed it (date and time if possible) - A screenshot of the empty dashboard panel(s), if available If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ OTTO Heading Deployments on Wix Sites Explained

🔍 Overview When OTTO deploys heading optimizations to a Wix site, customers sometimes notice that the changes seem to disappear or revert immediately after deployment. This behavior is expected and is caused by how OTTO interacts with Wix's rendering environment. This article explains exactly what is happening and what you should expect to see. ⚙️ How OTTO Deploys Headings on Wix OTTO applies heading changes — such as rewriting H1, H2, or H3 tags for better SEO — by injecting optimized content through Wix's supported integration layer. Unlike platforms such as WordPress, Wix does not allow third-party tools to directly and permanently overwrite page content in the site editor. Instead, OTTO's changes are applied at the rendering level, meaning they are delivered to search engine crawlers and browsers when the page loads, rather than being stored visibly inside the Wix editor itself. 👁️ Are the Changes Visible in the Wix Editor? No — and this is the key point that causes confusion. When you open the Wix editor after OTTO has deployed heading changes, you will not see the updated headings reflected there. The Wix editor will continue to display your original content. This does not mean the deployment failed. The optimized headings are still being served correctly to visitors and search engine bots when the live page is rendered. ✅ How to Confirm the Changes Are Live To verify that OTTO's heading optimizations are active on your published Wix pages, use one of the following methods: 1. View the live page source: Open your published Wix page in a browser, right-click anywhere on the page, and select View Page Source. Search for your heading tags (H1, H2, etc.) and confirm the OTTO-optimized text is present in the source code. 2. Use a crawl tool: Run the URL through a site auditing tool such as Search Atlas's own Site Auditor to verify the headings being read by crawlers match your OTTO deployments. 3. Check OTTO deployment status: In the Search Atlas platform, navigate to OTTO SEO in the left sidebar and open All Sites (SEO Automation) inside it, then review the deployment log for your Wix site. A green status indicator confirms the changes were successfully pushed. 🔄 Why Do the Changes Look Like They Are Reverting? The appearance of reverting happens because: - Wix stores its own version of your page content independently of OTTO's injected optimizations. - When you view the Wix editor, you are seeing Wix's stored version — not the rendered, OTTO-optimized version that visitors and crawlers see. - If you manually edit and republish a page inside Wix after an OTTO deployment without re-deploying from OTTO, the Wix-stored content will take precedence and the OTTO heading changes will need to be redeployed. ⚠️ Important: Avoid Overwriting OTTO Changes To keep your OTTO heading optimizations intact on your Wix site, follow these best practices: - Do not manually edit headings in the Wix editor after OTTO has deployed changes to those same elements, unless you plan to redeploy from OTTO afterward. - Redeploy from OTTO any time you publish significant page updates in Wix. Navigate to OTTO SEO in the left sidebar and open All Sites (SEO Automation) inside it, then trigger a new deployment for the affected pages. - Use page source or a crawl tool — not the Wix editor — as your source of truth for what headings are actually live on your site. 💡 Summary OTTO heading changes on Wix are working as designed. The optimizations are applied at the rendering layer and are visible in the live page source and to search engine crawlers — but they will not appear inside the Wix editor. Changes may appear to revert if you edit and republish pages in Wix without redeploying from OTTO. Always check the live page source or OTTO's deployment log to confirm your changes are active. 🙋 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Understanding OTTO Title Tag Errors and AI Credits

What This Article Covers If you have noticed that the Title Tags section in OTTO shows flagged issues without a clear explanation of what is wrong, you are not alone. This article explains how OTTO surfaces title tag errors, when AI credits are used, and how you can make informed decisions before generating suggestions. How OTTO Flags Title Tag Issues OTTO automatically audits your pages and flags title tags that do not meet SEO best practices. A flag means OTTO has detected a potential problem with one or more title tag conditions, such as a missing, duplicate, or otherwise problematic title. The flag indicator will appear in the Title Tags section within OTTO. The flag may appear before the specific reason is fully visible. We understand this creates uncertainty about whether taking action is worth the cost of AI credits. When Are AI Credits Used? AI credits are consumed when you ask OTTO to generate a suggested title tag for a flagged page. Simply viewing the flagged list or reviewing a page does not spend credits. Credits are only deducted at the moment OTTO produces a new AI-written title suggestion for that URL. Here is a clear breakdown of what does and does not use credits: - Does NOT use credits: Viewing the list of flagged pages, seeing the flag indicator, reading the current title tag text - DOES use credits: Asking OTTO to generate an AI title suggestion for a specific page How to Evaluate a Flagged Title Before Using Credits Before asking OTTO to generate an AI suggestion, it is worth reviewing the existing title tag yourself to see if the issue is something you can address directly. Common title tag problems include a title that is blank, too short, too long, duplicated across multiple pages, or one that does not clearly describe the page content. If you can identify the problem yourself, you may be able to resolve it without consuming any AI credits. Only request an AI-generated suggestion when you want OTTO to produce an alternative title — that is the point at which credits are deducted. Taking a moment to assess the flagged title before requesting AI assistance helps you preserve credits for cases where you genuinely need them. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🗑️ Delete Non-Applicable Alt Text Issues in OTTO

🔍 Overview When OTTO's On Page Optimizer scans your page for image alt text issues, it may flag items that are not applicable to your site — such as SVG files, icon fonts, or other unsupported image types that do not require alt text. These line items cannot be fixed automatically, but you can manually delete them so your audit reflects only actionable tasks. This article walks you through how to identify and remove those non-applicable alt text issues in the new OTTO format. 🤔 Why Are SVG and Unsupported Items Flagged? OTTO scans all image elements on a page and flags any that are missing alt text attributes. Some of these may include: - SVG files — inline or embedded SVGs that are decorative or icon-based - Icon fonts rendered as images — elements that visually appear as images but are not standard img tags - Unsupported image formats — file types that OTTO cannot automatically apply alt text to These items are flagged because the scanner detects a missing alt attribute, but in many cases no alt text is needed or the format is not supported for automated fixes. Deleting these line items tells OTTO they are not applicable to your workflow. 🧭 How to Navigate to the On Page Optimizer 1. Log in to your Search Atlas account. 2. In the left sidebar, go to OTTO SEO → All Sites (SEO Automation) and select your site. 3. Open OTTO Grader (the OTTO Grader is also accessible from OTTO SEO → Overview). 4. Scroll to the Image Alt Text task group to see all flagged alt text issues. 🗑️ How to Delete a Non-Applicable Alt Text Line Item 1. Locate the alt text issue you want to remove. Review the file name or image path to confirm it is an SVG, icon, or unsupported item that does not need alt text. 2. Find the delete option for that line item within the row. 3. Click the delete option to remove the line item from your On Page Optimizer task list. 4. Repeat these steps for any additional non-applicable items in the alt text group. Note: Deleting a line item does not make any changes to your live page. It only removes the task from OTTO's audit list, indicating that it is not applicable to your optimization workflow. ✅ Tips for Managing Alt Text Issues Efficiently - Review before deleting — Check each flagged item carefully. Some SVGs used as content images (such as infographics) may still benefit from a descriptive alt attribute. - Decorative images — Purely decorative images that add no informational value are safe candidates for removal from the audit list. - Keep a record — If you are managing multiple pages, note which item types you are removing so you can apply consistent decisions across your site. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🤖 Fix OTTO SEO Showing Zero Deploys

🔍 Why OTTO SEO Shows 0 Deploys OTTO SEO uses a two-step workflow: first you generate suggestions, then you deploy them. If you see 0 deploys, it almost always means suggestions have not yet been generated, or they are waiting to be reviewed and deployed. Engaging OTTO SEO does not automatically push changes to your site — you need to complete both steps manually. 🗺️ Step 1 — Open OTTO SEO 1. Log in to Search Atlas. 2. In the left sidebar, click OTTO SEO, then open SEO Automation. The URL will change to /seo-automation-v3. 3. Select the website you want to work on from the property selector at the top of the page. 4. Confirm that OTTO SEO is shown as Engaged for that property. ✨ Step 2 — Generate Suggestions 1. Inside the OTTO SEO dashboard, locate the Generate Suggestions button or the relevant task category (for example, Title Tags, Meta Descriptions, or Schema). 2. Click Generate for each category you want OTTO to analyse. OTTO will crawl your pages and produce a list of recommended changes. 3. Wait for generation to complete — a progress indicator will show when OTTO is working. This can take a few minutes depending on the size of your site. 4. Once complete, the suggestions panel will populate with individual recommendations for each page. Important: OTTO SEO must finish generating suggestions before the Deploy option becomes available. If you skip this step, the deploy counter will remain at 0. 🚀 Step 3 — Deploy Generated Suggestions 1. Review the suggestions listed in the OTTO SEO dashboard. You can approve all suggestions at once or select specific ones to deploy. 2. Click Deploy next to individual suggestions, or use the Deploy All option to push all approved recommendations live. 3. OTTO SEO will apply the changes directly to your connected site. The deploy counter will increment for each successful change. 4. Refresh the dashboard after a moment to confirm the updated deploy count. ⚠️ Common Reasons for 0 Deploys - Suggestions not yet generated: You engaged OTTO but never clicked Generate. Return to the dashboard and run generation for each task category. - Suggestions pending review: Suggestions were generated but not yet deployed. Open each category, review the recommendations, and click Deploy. - No pages crawled: OTTO could not access your site. Check that your website URL is correct and that OTTO has been granted the necessary site access or plugin permissions. - Website not connected: If the site integration (WordPress plugin or DNS verification) is incomplete, OTTO can generate suggestions but cannot deploy them. Verify your site connection in the account settings. - Suggestions filtered out: Active filters on the dashboard may be hiding suggestions. Clear any status or page filters to see all available items. ✅ Troubleshooting Checklist - OTTO SEO status shows Engaged for the correct property. - You have clicked Generate inside at least one task category. - Generation has fully completed — no spinner or progress bar is visible. - You have clicked Deploy on one or more suggestions. - Your site connection (plugin or DNS) is active and verified. - No dashboard filters are hiding pending suggestions. - You have refreshed the page after deploying to see the updated counter. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⏱️ OTTO Deployment vs. Google Indexing Timeline

🔍 What This Article Covers When you deploy meta title and description changes through OTTO in Search Atlas, two separate events happen at different times. This article explains both stages so you know exactly what to expect and how to speed up the process. ⚡ Stage 1: Instant Deployment to Your Live Website As soon as you deploy a meta title or meta description update in OTTO, the change is applied to your live website immediately via JavaScript. This means: - The updated tag is active on the page right away. - Any visitor who loads the page will see the new meta data in the page source. - No manual code changes or developer involvement is required. Deployment itself is not the delay — the wait comes in the next stage. 🕐 Stage 2: Google Must Re-Crawl and Re-Index Your Page Even though your changes are live on the website instantly, Google does not know about them yet. Google maintains its own schedule for crawling and re-indexing pages. Until Google revisits your page, the old meta title and description will continue to appear in search results and in the Page Explorer inside Search Atlas. Here is what the typical timeline looks like: - Minimum: 2–3 days for frequently crawled, high-authority pages. - Typical: 5–10 days for most pages. - Maximum: Up to 14 days or longer for low-traffic or rarely crawled pages. This delay is controlled entirely by Google and is not something Search Atlas can override. It applies to all websites, regardless of the tool used to deploy changes. 📊 Why Page Explorer May Still Show the Old Values The Page Explorer in Search Atlas reflects the meta data that Google has most recently indexed for your page. If Google has not yet re-crawled the page since your OTTO deployment, Page Explorer will still display the previous title and description. Once Google indexes the updated page, Page Explorer will automatically reflect the new values on its next data refresh. 🚀 How to Speed Up Google Re-Indexing You cannot force Google to crawl your page immediately, but you can submit a re-indexing request to move the page higher in Google's crawl queue. Follow these steps: 1. Go to Google Search Console (search.google.com/search-console) and sign in with the account linked to your website. 2. Paste the exact URL of the updated page into the search bar at the top. 3. Click Request Indexing. 4. Google will typically process high-priority pages within 1–3 days after a manual request. This is the fastest available method and is strongly recommended after any significant meta data deployment. 🔗 Using the Search Atlas Index Integration Search Atlas also offers a native Index integration that can help streamline the indexing process for your pages. To access it: - Navigate to OTTO SEO in the left sidebar, then open SEO Automation (or go to /seo-automation-v3). - Look for the Index integration options within the OTTO dashboard. This integration works alongside Google Search Console to help signal updated pages for re-crawling and can reduce the time between deployment and Google reflecting your changes. 📋 Quick Reference Summary - OTTO deployment: Instant — changes are live on your website immediately via JavaScript. - Google search results: 2–14 days — Google must re-crawl the page on its own schedule. - Page Explorer update: Reflects Google's most recent indexed data — updates after Google re-indexes the page. - To speed things up: Submit a re-indexing request in Google Search Console or use the Search Atlas Index integration. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 OTTO Script Installation and Logo Positioning Guide

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

🔌 Activate GSC Properties for OTTO Integration

🔍 Overview If you can see a GSC property listed under Top-right avatar → Settings → Integrations but it does not appear as an option when setting up OTTO, the property has not yet been activated through Site Metrics. This activation step is required before OTTO can recognise and use the property. ⚙️ Why This Happens Connecting a GSC property in your integrations settings only links your Google account to Search Atlas. OTTO requires an additional activation step — the property must first be activated inside Site Metrics before it becomes available to select in OTTO. Skipping this step is the most common reason a property appears in integrations but not in OTTO. ✅ How to Activate Your GSC Property for OTTO 1. From the left sidebar, navigate to Site Metrics. 2. Locate the GSC property you want to use. If it is not already listed, add it by selecting it from the available options. Only properties connected under Top-right avatar → Settings → Integrations will appear here. 3. Once the property is listed in Site Metrics, open it to activate the property within Search Atlas. 4. After activation, return to OTTO SEO → All Sites (SEO Automation) using the left sidebar. 5. Open OTTO and attempt to add your property again. The GSC property should now appear in the available options list. 🛠️ Quick Troubleshooting Checklist - Property visible in integrations but not OTTO: Complete the Site Metrics activation steps above. - Property not visible in Site Metrics: Confirm the GSC account connected under Top-right avatar → Settings → Integrations has verified ownership of the property in Google Search Console. - Property activated but still missing in OTTO: Try refreshing your browser and re-entering the OTTO setup flow. Allow up to one minute for the change to propagate. - Multiple GSC accounts connected: Make sure the property you want belongs to the GSC account that is actively linked in your Search Atlas integrations. Properties from a different Google account will not appear. 📋 Key Things to Remember - Integrations settings and OTTO are not automatically in sync — the Site Metrics activation step is always required. - You only need to activate a property once. After the first activation it will remain available in OTTO for future use. - Any team member with the correct permissions can complete the activation on behalf of your organisation. 💬 Still Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Understanding OTTO Meta Description Flagging Discrepancies

🧭 Overview If you've noticed that OTTO flagged a different number of pages for missing meta descriptions compared to missing title tags — for example, 136 pages versus 220 — this is expected behaviour. It does not mean OTTO missed pages or that your audit is incomplete. This article explains why these numbers can differ. ⚙️ Why the Counts Differ OTTO audits title tags and meta descriptions as separate issues, and the number of pages flagged for each can vary. This is a known and expected behaviour within OTTO's audit logic. The two checks do not always evaluate the exact same set of pages, which is why you may see different flagged counts for each issue type. If you are seeing a discrepancy between the number of pages flagged for missing meta descriptions and the number flagged for missing title tags, this does not indicate a bug or an incomplete audit — it reflects how OTTO handles these as independent checks. ✅ What to Do If You're Concerned About Coverage If you believe pages with missing meta descriptions are not being surfaced correctly, here is what to do when contacting support: 1. Note the exact numbers you are seeing for each issue type (e.g. 136 flagged for meta descriptions, 220 for title tags). 2. Note the name of the project or domain where you are seeing the discrepancy. 3. Take a screenshot of the flagged pages list for each issue type if possible. 4. Have this information ready so a support teammate can investigate the specific audit scope applied to your site. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 Fix OTTO Auto-Generated Incorrect Schema Markup

Why Is OTTO Adding the Wrong Schema? OTTO generates schema markup automatically based on its built-in AI defaults. When no custom prompt exists for a project, OTTO has no context about your business type, industry, or goals — so it falls back on generic or statistically common schema types. In some cases, this results in incorrect schema suggestions being applied to businesses that have nothing to do with the suggested schema type. This is not a bug. It is expected default behavior when OTTO lacks the business-specific context it needs to make accurate recommendations. The fix is to configure a custom OTTO prompt that tells OTTO exactly what your business does. Important: OTTO Prompts vs. Content Genius Custom OTTO prompt settings apply only to the OTTO dashboard and the automations OTTO runs within it. These settings do not affect Content Genius or any other tool in Search Atlas. If you use Content Genius, you will need to manage context and instructions separately within that tool. Step 1 — Configure a Custom OTTO Prompt Adding a custom prompt gives OTTO the business context it needs to generate accurate schema, meta tags, and other SEO recommendations. To configure your custom prompt for an affected project, navigate to the OTTO dashboard and look for the project settings or prompt configuration area. Once you locate the custom prompt field, enter a clear, specific description of the business. Include details such as: - Business type and industry (for example, "This is a licensed plumbing company serving residential customers") - Primary services or products - Target audience - Any schema types that are not relevant to the business Save your prompt, then repeat this process for every project that is showing incorrect schema suggestions. Tip: The more specific your custom prompt, the more accurate OTTO's recommendations will be. Two to four sentences covering business type, services, location, and exclusions will produce the best results. Step 2 — Delete Incorrect Auto-Generated Schema After saving your custom prompt, remove any incorrect schema that OTTO has already deployed. In the OTTO dashboard, look for the schema management area where auto-generated schema markup is listed. From there, select the incorrect schema entries and delete them so they are no longer applied to your pages. If you are unable to locate the custom prompt configuration or schema management area within the OTTO dashboard, please reach out to our support team for guided assistance. When doing so, have the following ready: your project name, the incorrect schema type(s) being generated, and any relevant page URLs where the incorrect schema appears. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🗂️ Remove or Freeze an OTTO SEO Project

🔍 Overview When an OTTO SEO project is no longer active, you have two main options: Deep Freeze the project to pause it temporarily, or permanently delete it. This article explains the practical difference between those options and answers common questions about the OTTO code or plugin. ❄️ What Is Deep Freeze? Deep Freeze pauses an OTTO SEO project without removing it from your account. The project record, settings, and history are preserved so you can reactivate it later. When to use Deep Freeze: - The site is temporarily inactive but you may return to it in the future. - You want to stop OTTO activity without losing your project data and configuration. - You need to free up an active project slot on your plan without permanently removing the project. How Deep Freeze affects your quota: Freezing a project is intended to release its active slot so that slot becomes available for another project on your plan. The frozen project remains visible in your account and can be reactivated when you need it again. For confirmation of how slot release works on your specific plan, please reach out to our team. 🗑️ When Should You Delete a Project Instead? Permanent deletion removes the project and all its data from your account. This action cannot be undone — project history, settings, and optimizations are not recoverable after deletion. When to use deletion: - The site no longer exists or will never be used again. - You want to fully remove the project and permanently free up the slot. - You have no need to retain any historical data or settings for that site. If there is any chance you will return to the site, use Deep Freeze instead — it frees up the active slot while keeping your data intact. 📋 Archiving and Plan Limits Your plan includes a limit on the number of active OTTO SEO projects at one time. Deep Freezing a project counts it as inactive, releasing the active slot for use by another project. Deleted projects are removed entirely and permanently free the slot. Frozen projects still appear in your account list but do not consume an active slot. 🔌 Do You Need to Remove the OTTO Code or Plugin? In most cases, you do not need to remove the OTTO tracking code or plugin from your site when you Deep Freeze or delete a project. However, if you are fully decommissioning the site or handing it off to another party, removing the code or plugin is good practice to keep the site clean. If you are unsure whether the code or plugin should be removed for your specific situation, our support team can advise you. 📋 How to Deep Freeze or Delete a Project The exact steps to Deep Freeze or permanently delete an OTTO SEO project depend on your account setup. Because the workflow may vary, we recommend contacting our support team to walk you through the correct steps for your account and plan. When reaching out, please have the following ready: - The name of the OTTO SEO project you want to freeze or delete. - Your account email or workspace name. - Whether you want to Deep Freeze (pause) or permanently delete the project. - Any specific questions about quota or slot release on your plan. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔄 Backend Cache Flush and CMS Detection Refresh After Migration

Overview When you migrate a website between platforms — for example, from Wix to another CMS — Search Atlas may continue reading data from your previous environment. This can cause issues with on-page optimization deployment and GSC sitemap sync that appear unrelated to the migration itself. This article walks you through the steps to verify your OTTO pixel installation and restore accurate on-page optimization data after a platform migration. Why On-Page Optimization May Not Reflect Your New Platform After a CMS migration, Search Atlas may not immediately recognize your new platform environment. Until a fresh detection is triggered, on-page optimization scores and GSC sitemap sync may not reflect your current setup. This is a common occurrence after migrating platforms such as Wix. Step 1 — Verify Your OTTO Pixel Is Correctly Installed on the New Platform Before anything else, confirm that the OTTO pixel is present and correctly installed on your new platform. A missing or duplicated pixel is a frequent cause of detection failures after migration. 1. Open your website in a browser and use your browser's developer tools to search for the OTTO pixel script tag in your page source. 2. Confirm the pixel appears exactly once. If you migrated from a previous platform and the old pixel script was not fully removed, you may see two instances — remove any legacy pixel from the old platform before proceeding. 3. After confirming the pixel is installed correctly on the new platform, navigate to your OTTO setup within Search Atlas and check whether on-page optimization deployment is now registering accurately. Step 2 — Resubmit Your Sitemap in Google Search Console After a migration, your GSC sitemap sync may be pointing to an outdated sitemap or may not reflect your new platform's URL structure. To resolve GSC sitemap sync issues post-migration: 1. Log in to Google Search Console and navigate to Sitemaps under the relevant property. 2. Remove any outdated sitemap entries associated with your previous platform. 3. Submit your new sitemap URL generated by your current platform. 4. Return to Search Atlas and trigger a re-crawl or refresh of your project so that GSC data is pulled in from the updated sitemap. Step 3 — Escalate if Issues Persist After Pixel and Sitemap Verification If you have confirmed the OTTO pixel is correctly installed and your sitemap has been resubmitted but on-page optimization or GSC sync still appear incorrect, a backend reset may be required. When escalating, have the following ready: - Your website project URL - The platforms involved in your migration (for example, migrated from Wix on [date]) - A description of the specific issue — for example, on-page optimization not deploying, or GSC sitemap sync not updating - Any error messages or incorrect readings you are seeing in Search Atlas If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🖼️ OTTO Alt Text Appearing as Google Meta Descriptions

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

🔄 Why SEO Tasks Stay Empty After Recrawls

🧭 Overview After deploying WordPress updates and triggering a recrawl in Search Atlas, you may notice that your SEO task lists appear empty or unchanged. This is expected behavior — and understanding why will save you from unnecessary troubleshooting. The key distinction is this: recrawling detects your site's current state, but task generation depends on OTTO's separate algorithmic analysis cycle. These are two different processes that run on different timelines. 🔍 Recrawls vs. OTTO Analysis Cycles Many users assume that triggering a recrawl will immediately produce new or updated SEO tasks. Here is what actually happens: - Recrawl: Scans your website to detect its current technical state — page structure, metadata, content, and any changes you have made. It updates OTTO's awareness of your site. - OTTO Analysis Cycle: A separate algorithmic process that evaluates your site's SEO performance, compares it against best practices and ranking signals, and generates actionable tasks. This cycle does not run automatically every time you recrawl. A recrawl feeds new data into OTTO, but task generation only happens when OTTO's next analysis cycle runs. Triggering a recrawl does not trigger a new task generation cycle. 📅 How Often Does OTTO Generate New Tasks? OTTO's task refresh schedule is tied to SEO meta and best-practice changes and Google indexing periods, not to a fixed weekly schedule or your recrawl frequency. In practice, this means task updates occur approximately monthly or once per indexing period. This cycle exists because meaningful SEO improvements require time to be indexed and evaluated by Google. Generating new tasks before your previous fixes have been indexed would produce inaccurate or redundant recommendations. - Task updates reflect actual changes in your site's indexed state — not just changes to your site files. - Running recrawls more frequently will not accelerate the task generation cycle. - OTTO will not surface new tasks simply because you deployed updates, even significant ones. ✅ OTTO Fixes Persist Until Marked Outdated When OTTO applies or marks a fix as resolved, that fix remains in its completed state until the algorithm determines it has become outdated. This means: - Completed tasks will not reappear after a recrawl unless OTTO's next analysis cycle identifies a regression or new issue. - You do not need to re-apply fixes after every WordPress update. - Fixes are durable across recrawls unless your site changes cause OTTO to flag them again in a future cycle. 🟦 Why WordPress Sites Often Show Blank Task Sections If you are managing a WordPress site and certain task sections appear completely empty, this is normal and expected. WordPress sites commonly have configurations — such as page builders, caching plugins, or crawl restrictions — that can act as site blockers during OTTO's scan. Blank task sections on WordPress sites typically indicate one of the following: - OTTO has not yet completed its next analysis cycle since your updates were deployed. - The relevant pages have not yet been re-indexed by Google since your fixes were applied. - A site blocker or plugin is limiting what OTTO can evaluate in that section. An empty task section does not mean something is broken. It means OTTO has no new recommendations to surface at this time for that category. 📋 Expected Workflow After Deploying WordPress Updates Follow this sequence to work effectively with OTTO's task cycle rather than against it: 1. Deploy your WordPress fixes or updates as normal through your CMS or hosting environment. 2. Trigger a recrawl inside Search Atlas by navigating to Left sidebar → OTTO SEO → All Sites (SEO Automation), selecting your active site, then going to Site Audit → Overview (Website Overview) and clicking the Recrawl Site button. This ensures OTTO has the latest snapshot of your site. 3. Allow time for Google to re-index your changes. This typically takes several days to a few weeks depending on your site's crawl budget and the scope of changes. 4. Wait for OTTO's next algorithmic analysis cycle — approximately monthly or aligned with the current indexing period. New tasks will appear in your dashboard once this cycle runs and detects actionable opportunities. 5. Review updated tasks in the OTTO SEO section after the cycle completes. You will see refreshed recommendations based on your site's newly indexed state. Do not interpret an empty task list immediately after a recrawl as an error. If tasks were present before your updates and are now resolved, their absence confirms OTTO registered your fixes successfully. ⚠️ When to Investigate Further While empty tasks after a recrawl are normal, there are situations where you should take a closer look: - Tasks that were active before your updates have disappeared but you did not apply any fixes — this may indicate a crawl issue. - Your site has been re-indexed by Google but no new OTTO cycle has run after several weeks. - Task sections remain blank across multiple OTTO cycles with no explanation from your site's configuration. In these cases, verify that your WordPress site does not have crawl restrictions (such as disallow rules in robots.txt or password-protected staging environments) that could prevent OTTO from analyzing your pages. 💬 Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔄 Re-Add Your Site to OTTO SEO Correctly

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

📄 Pagination Variants vs. Duplicate URLs in Search Atlas

Overview If Search Atlas is showing multiple versions of your blog post URLs — for example, example.com/blog/post/, example.com/blog/post/?page=2, and example.com/blog/post/?page=3 — these are pagination variants, not duplicate pages created by Search Atlas. They are separate, search-engine-visible URLs that exist on your site and are being surfaced so you can manage them correctly. This article explains what pagination variants are, why they appear in your audit, and how to resolve any canonicalization issues. What Are Pagination Variants? Pagination variants are numbered URL versions of a single page. They are generated by your CMS or website platform when long-form content — such as a blog post, product listing, or article — is split across multiple pages. Common formats include: - example.com/blog/post/?page=2 - example.com/blog/post/2/ - example.com/blog/post/?p=2 Search engines crawl and index each of these URLs independently. Without correct canonical tags, search engines may treat them as competing versions of the same content, which can dilute your page authority and hurt rankings. Search Atlas does not create these URLs. It detects them during your site crawl and flags them so you can take action. How to Find Pagination Variant Issues in Your Audit Once your site crawl is complete, navigate to your audit project in Search Atlas and look for any issues related to duplicate or paginated URLs. The audit will surface grouped URL sets — showing the parent URL alongside its numbered variants — so you can review which pages are affected. If you are unsure where to locate these results within your specific audit view, our support team can guide you to the correct section of the interface. How to Fix Pagination Variants The correct fix depends on how your content is structured. The following approaches are commonly used to resolve pagination canonicalization issues. Option 1 — Add a canonical tag to each paginated URL Point the canonical tag on each paginated variant back to the main (first) page of the post. For example, example.com/blog/post/?page=2 should include a canonical tag referencing example.com/blog/post/. Add this inside the <head> section of each paginated page: - <link rel="canonical" href="https://example.com/blog/post/" /> Many CMS platforms allow you to set canonical URLs through SEO settings or plugins without editing code directly. Refer to your CMS documentation for the specific steps that apply to your platform. Option 2 — Disable pagination if it is not needed If your blog posts do not require pagination, consider disabling it in your CMS settings. This will prevent the additional paginated URLs from being generated and crawled. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Fix OTTO Duplicate URL Suggestions Explained

🧭 Overview OTTO sometimes displays SEO suggestions — such as H1 length fixes or missing alt text — for URLs that are non-canonical variants of a page you have already optimised. A common example is receiving suggestions for /blog when your canonical URL is /blog/ (with a trailing slash). This article explains why this happens and how to resolve it. 🤔 Why Does OTTO Show Suggestions for Non-Canonical URLs? OTTO crawls your site and evaluates every URL it discovers, including redirected or non-canonical variants. When OTTO encounters a URL like /blog that resolves to the same content as /blog/, it may still flag SEO issues on the non-canonical version for one or more of the following reasons: - Crawl discovery: OTTO's crawler follows all internal links and sitemaps. If any page on your site links to the non-canonical version, OTTO will crawl and analyse it independently. - Redirect chain evaluation: OTTO evaluates pages before following the redirect, so it can surface issues that exist at the source URL — even if a canonical tag or 301 redirect is present. - Canonical tag not yet processed: If a canonical tag was recently added or the site was just connected, OTTO may not have completed a full re-crawl incorporating the canonical signal. - Sitemap inconsistencies: If your XML sitemap includes both /blog and /blog/, OTTO treats them as separate URLs to audit. This behaviour is by design — OTTO surfaces issues at every discovered URL so you have full visibility. However, you can exclude non-canonical variants to keep your suggestion list clean and focused. ✅ How to Exclude Non-Canonical URLs from OTTO Suggestions Follow these steps to exclude duplicate or non-canonical URLs so OTTO stops generating suggestions for them. 1. In the left sidebar, navigate to OTTO SEO → All Sites (SEO Automation) and open your project. 2. Click the Autopilot / Smart Crawl card at the top of the overview to open the OTTO SEO Settings modal. 3. Scroll to URL Exclusion conditions and click + Add condition. 4. Set it to Exclude all URLs that Contains or Start With a pattern that matches only the non-canonical variant — for example, a query-string or parameter variant of /blog. 5. Click Update Settings and trigger a recrawl. OTTO will stop generating new suggestions for URLs that match the condition. Repeat with additional conditions for any other non-canonical variants you want to suppress. Conditions can be reviewed, edited, or removed at any time in the same URL Exclusion conditions list. If the variant cannot be distinguished from the canonical URL by pattern (for example /blog vs /blog/), use the suggestion row's Delete action to hide that suggestion, or implement a 301 redirect. 🛠️ How to Prevent Duplicate URLs from Appearing in Future Crawls Excluding URLs in OTTO is a quick fix, but addressing the root cause ensures duplicate suggestions do not reappear after the next crawl. Take the following actions on your site: - Standardise internal links: Audit your site's internal linking and ensure all links point consistently to the canonical version (e.g., always use /blog/ with a trailing slash). - Implement a 301 redirect: Redirect the non-canonical variant (/blog) permanently to the canonical URL (/blog/) at the server or CMS level. - Update your XML sitemap: Remove non-canonical URLs from your sitemap so they are not submitted to crawlers as standalone pages. - Verify canonical tags: Confirm that each canonical page includes a self-referencing <link rel="canonical"> tag pointing to the preferred URL version. Once these changes are in place, trigger a fresh crawl in OTTO to reflect the updated site structure. 📊 How to Trigger a Fresh Crawl in OTTO 1. In the left sidebar, navigate to OTTO SEO → All Sites (SEO Automation) and click your target site, then open Site Audit → Overview (Website Overview). 2. Click Recrawl Site. 3. Wait for the crawl to complete — you will see a progress indicator in the interface. After the crawl finishes, your suggestions list will reflect the current state of your site, and previously excluded or resolved URLs should no longer appear. 💡 Quick Reference: Common Duplicate URL Scenarios - /blog vs /blog/ — Trailing slash variant. Standardise and 301 redirect. - http:// vs https:// — Protocol variant. Ensure full HTTPS migration with redirects. - www vs non-www — Subdomain variant. Choose a preferred version and redirect the other. - ?utm_source= parameters — Tracking parameter variant. Use canonical tags or configure parameter handling in Search Atlas. 🆘 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚙️ Deep Freeze Rollback and Reactivation Workflow

Overview If a client pauses their engagement or goes inactive, you can roll back their site to its pre-OTTO state and place it in Deep Freeze. This preserves all of OTTO's work so that when the client returns, you can reactivate everything without starting from scratch. This article walks you through the full workflow from rollback to reactivation. What Is Deep Freeze? Deep Freeze is an OTTO SEO status that suspends all active optimizations on a site. When a site is in Deep Freeze: - OTTO stops applying new changes to the site. - All previously saved OTTO configurations and recommendations are retained in the platform. - In Deep Freeze, OTTO does not crawl, analyze, or fix anything new, but already-deployed fixes stay live. This is ideal for clients who are temporarily pausing services but are expected to return. Step 1 — Roll Back the Site to Its Pre-OTTO State To roll back a site to its pre-OTTO state, open the site inside OTTO SEO and use the rollback option available for that site. This reverts all OTTO-applied changes on the live site, restoring the original pre-OTTO content and metadata. Wait for the platform to confirm the rollback is complete before proceeding. If you are unsure where to find the rollback option for your account, please reach out to our team for guidance. Step 2 — Apply Deep Freeze to the Site Once the rollback is confirmed, apply the Deep Freeze status to the site within OTTO SEO. After Deep Freeze is active, OTTO will not push any changes to the site. All configurations, approved tasks, and recommendations remain saved inside the platform and are ready to be redeployed when needed. Step 3 — Reactivate OTTO When the Client Returns When your client is ready to resume, reactivating their OTTO setup is straightforward because all prior work has been preserved. 1. Return to OTTO SEO and open the frozen site. 2. Change the site's OTTO status from Deep Freeze back to an active state. 3. Review the saved tasks and recommendations to confirm nothing needs updating since the freeze was applied. 4. Redeploy the previously approved OTTO optimizations back to the live site. 5. Verify the deployment completed successfully by checking the site's current status in the platform. Your client's site will now reflect all of the OTTO improvements that were in place before the freeze, with no need to recreate any work. Best Practices - Always confirm the rollback is complete before applying Deep Freeze. - Make a note of when the freeze was applied so you can review whether any recommendations need refreshing before redeployment. - Deep Freeze is intended for temporary pauses — if a client is permanently discontinuing service, consult your account workflow for the appropriate offboarding steps. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚡ OTTO Meta Edits: View Source vs. Browser Inspect

Overview When OTTO applies meta title or meta description edits to your website, you may notice that the changes do not appear when you use your browser's View Page Source option. This is expected behaviour — not a bug. Understanding the difference between View Source and Browser Inspect will help you confirm your edits are live and visible to Google. How OTTO Delivers Meta Edits OTTO applies meta tag changes at the rendering stage, which means the edits may not be reflected in the raw static HTML returned by your server. There are two ways a browser can show you a page's code: - View Page Source: Displays the raw, static HTML that the server sends before rendering. OTTO's changes may not appear here. - Browser Inspect / DevTools: Displays the fully rendered version of the page after the browser has processed it. OTTO's meta edits will appear here. How to Verify Your OTTO Meta Edits Are Live To confirm your OTTO meta edits are rendering correctly, use your browser's Inspect or DevTools feature (typically accessed by right-clicking the page and selecting Inspect). In the Elements panel, search for the meta title or meta description tag and confirm it displays the updated text that OTTO generated. If the updated value appears there, your edit is rendering correctly in the browser. How Google Crawls OTTO-Generated Edits Google's crawler reads the rendered version of a page, similar to what you see in Browser Inspect rather than View Source. This means Google can index meta tags that are applied dynamically by OTTO. After OTTO applies edits, allow some time for Google to recrawl and re-render the page before expecting the changes to be reflected in search results. How to Confirm Google Has Indexed Your Updated Meta Title To check whether Google has picked up your updated meta title, open Google Search Console and use the URL Inspection tool for the page you edited. This will show you the version of the page Google last crawled and whether it reflects OTTO's changes. If it does not yet reflect the update, you can request a recrawl directly from that tool. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Fix Yoast Meta Description Detection Discrepancy

🧩 Why the Discrepancy Happens If Page Issues flags your page as missing a meta description while On-Page Audit shows one is present, the most common cause is a conflict with the Yoast SEO plugin. Yoast can output meta description tags differently depending on how it is configured, which may cause one tool to detect the tag while the other does not. Specifically, Yoast sometimes conditionally renders the meta description based on page type, template settings, or its own snippet preview logic. This inconsistency in how the tag is delivered in the page's HTML can confuse detection tools that crawl or parse the page at different times or in different contexts. 🛠️ How Each Tool Detects Meta Descriptions Understanding how each tool works helps clarify why they can produce different results: - Page Issues crawls your live URL and parses the raw HTML response to check for a <meta name="description"> tag in the <head> section. - On-Page Audit (found at Left sidebar → Content → On-Page Audit) performs a deeper content analysis that may render JavaScript or interpret the page differently, catching tags that a basic crawl might miss. Because these tools use different detection methods, a meta description that is injected dynamically or rendered conditionally by Yoast may appear in one tool but not the other. ✅ Steps to Resolve the Conflict 1. Verify the meta description in your page source. Open your live page in a browser, right-click, and select View Page Source. Use Ctrl+F (or Cmd+F on Mac) to search for meta name="description". Confirm the tag exists in the raw HTML and contains the correct content. 2. Check your Yoast settings for that page. In your WordPress dashboard, open the page editor and scroll to the Yoast SEO meta box. Ensure the Meta description field is filled in and that the snippet preview shows the expected text. If the field is blank, Yoast will not output a tag. 3. Disable Yoast's advanced snippet settings if applicable. Some Yoast configurations suppress meta descriptions on archive pages, paginated pages, or pages set to noindex. Confirm the page is set to index and that no Yoast template is overriding the description output. 4. Clear your site cache. After making any changes in Yoast, clear your WordPress cache plugin (e.g. WP Rocket, W3 Total Cache) and your CDN cache if applicable. Stale cached pages can cause detection tools to read outdated HTML. 5. Re-run the On-Page Audit. Navigate to Left sidebar → Content → On-Page Audit, enter your page URL, and run a fresh audit. This gives Search Atlas updated data after your Yoast changes. 6. Re-check Page Issues. After the cache is cleared and the audit is re-run, allow Page Issues to recrawl your site or manually trigger a recheck. The two tools should now agree on the meta description status. ⚠️ When to Use On-Page Audit as the Source of Truth If your page source confirms the meta description is present and correctly formatted, treat the On-Page Audit result as the more reliable indicator. Page Issues uses a lightweight crawl that may not always account for how Yoast conditionally renders tags. The On-Page Audit performs a more thorough analysis and is better suited for diagnosing actual on-page SEO issues. 💡 Best Practices to Prevent Future Conflicts - Always write a unique meta description directly in the Yoast snippet editor for every important page rather than relying on auto-generated descriptions. - Avoid using multiple SEO plugins simultaneously (e.g. Yoast and All in One SEO). Duplicate meta tags or conflicting outputs are a common source of detection discrepancies. - After updating Yoast settings or upgrading the plugin, clear all caches and re-run your audits in Search Atlas to ensure data stays current. - Use Left sidebar → Content → Meta Generator to create optimised meta descriptions for your pages and paste them directly into Yoast for consistent, high-quality output. 💬 Still Seeing a Discrepancy? If you have followed all the steps above and the two tools still disagree, there may be a plugin-specific configuration or theme conflict that requires a closer look. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Disable Search Atlas Schema Injection on Your Site

🔍 What Is Schema Injection? When Search Atlas manages your on-page SEO through OTTO SEO, it can automatically inject schema markup (structured data) into your site's pages. This helps search engines better understand your content. However, there may be situations where you want to disable this feature — for example, if you are managing schema manually, using a third-party plugin, or troubleshooting conflicts. ⚙️ How to Disable Schema Injection Follow these steps to turn off schema injection for your site: 1. Log in to your Search Atlas account. 2. In the left sidebar, click OTTO SEO → All Sites (SEO Automation). 3. Select the site you want to manage from the site list. 4. Navigate to the OTTO SEO dashboard for that site. 5. Locate the Schema section within the OTTO SEO settings. 6. Toggle off the schema injection option to disable it. 7. Confirm your changes when prompted. Once disabled, Search Atlas will stop injecting schema markup into your site's pages. Any schema that was previously injected may need to be manually removed depending on how it was implemented. 💡 Things to Consider Before Disabling Before turning off schema injection, keep the following in mind: - Impact on rich results: Schema markup helps your pages qualify for rich results in Google Search (such as star ratings, FAQs, and breadcrumbs). Disabling injection may reduce your eligibility for these features. - Existing schema conflicts: If you already have schema added through another plugin or tool, running two sources simultaneously can cause duplicate or conflicting structured data. Disabling Search Atlas injection in this case is recommended. - Re-enabling is easy: You can turn schema injection back on at any time by returning to the same OTTO SEO settings and toggling the option back on. 🚀 Verifying Schema Has Been Removed After disabling schema injection, it is good practice to confirm that the structured data has been removed from your pages: 1. Visit any page on your site that was previously receiving injected schema. 2. Open Google's Rich Results Test (search for it at Google) and enter the page URL. 3. Review the results to confirm no Search Atlas-generated schema is detected. 4. You can also right-click the page and select View Page Source, then search for schema or application/ld+json to check for remaining structured data. 🙋 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🗑️ Remove Stale Organization JSON-LD from OTTO Custom HTML

What This Issue Is Some users have reported finding outdated Organization JSON-LD markup — such as an old phone number or a previous business name — still appearing on their site after updating their details in Search Atlas. The stale schema is located in the Custom HTML area of a page (most commonly the homepage), which is a separate location from the standard Domain-Level and Page-Level Schema controls managed by OTTO. Because this Custom HTML area sits outside OTTO's standard schema management workflow, the outdated block is not automatically cleared when OTTO is reconfigured or when business details are updated. It therefore continues to render on the page alongside — or instead of — the correct schema, which can cause structured data conflicts. Why It Can Be Hard to Spot Inspecting Domain-Level Schema or Page-Level Schemas through the normal OTTO controls will not reveal a block stored in Custom HTML. The stale code only becomes visible when you look directly at the Custom HTML or header injection field for the specific page. This is why a Rich Results Test or a crawl tool may surface schema details that do not match what you see in OTTO's schema settings. What to Do Because the exact location of the Custom HTML field depends on your connected CMS or platform, and because the specific steps needed to identify and remove the stale JSON-LD block may vary by site setup, this issue requires hands-on investigation by our support team. When you contact support, please have the following information ready so the team can assist you as quickly as possible: - The project or website name as it appears in your Search Atlas account - The URL of the page showing the incorrect or duplicate Organization schema (usually the homepage) - The exact outdated details you are seeing — for example, the wrong telephone number or business name — so the team can confirm which JSON-LD block needs to be removed - Any screenshot or source-code snippet of the stale <script type="application/ld+json"> block if you are able to locate it in your page source After the Issue Is Resolved Once the stale Custom HTML block is removed, your Organization schema will reflect only the authoritative data managed through your Search Atlas account. If you notice the problem recurring after future OTTO deployments, contact support promptly with the details listed above so the team can investigate the deployment behaviour for your specific setup. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔄 Refresh OTTO Analysis After Site Migration

🗺️ Overview When you migrate your site to a new build — even if the URLs remain the same — OTTO needs to re-analyse the updated pages before it can deliver accurate recommendations. This article explains how to trigger a fresh OTTO analysis and how OTTO handles 301 redirects after a migration. 🧭 How to Trigger a Fresh OTTO Analysis After completing your site migration and confirming that your 301 redirects are live, navigate to OTTO SEO → All Sites (SEO Automation) in your Search Atlas account and trigger a new analysis for the relevant site. OTTO will begin crawling your site and refreshing all audit data based on the current state of your pages. Depending on your site size, this process may take some time, and the dashboard will update when it is complete. Once the analysis is complete, OTTO's task list and recommendations will reflect your migrated site's current content and structure. ⏱️ How Long Does It Take for OTTO to Recognise 301 Redirects? OTTO does not automatically detect 301 redirects in real time. Recognition happens when a new crawl is triggered manually. Here is what to expect: - Immediate effect: Triggering a new analysis right after migration starts a fresh crawl that takes your current 301 redirects into account. - Previous suggestions: OTTO may retain audit items tied to old page states until the new analysis completes. Once the run finishes, outdated suggestions are replaced with findings based on the redirected and migrated pages. ✅ Best Practices Before Running the Analysis To get the most accurate results from OTTO after a migration, confirm the following before triggering a new analysis: - All redirects are correctly implemented and live. - The migrated site is fully accessible — not behind a staging password or maintenance mode. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔄 OTTO New Page Detection and Analysis Schedule

🧭 Overview If you have recently added new pages to your website and OTTO has not detected them yet, this is expected behaviour. OTTO operates on a fixed 7-day analysis cycle that runs independently of manual recrawls. Understanding the difference between a crawl and an OTTO analysis will help you set the right expectations and plan your SEO workflow accordingly. 🔍 The Difference Between Crawling and OTTO Analysis These are two separate processes, and it is important not to confuse them: - Crawling collects raw data from your website — page URLs, HTML content, metadata, and technical signals. A manual recrawl updates this dataset. - OTTO Analysis processes that crawl data to generate SEO recommendations, detect new pages, identify issues, and surface optimisation opportunities. This step runs on a scheduled cycle — not on demand. Running a manual recrawl refreshes the underlying data but does not trigger OTTO to re-analyse your site. OTTO will only process the latest crawl data when its next scheduled analysis runs. 📅 How the 7-Day OTTO Analysis Cycle Works OTTO analysis runs automatically on a 7-day schedule from the date your site was first connected. Here is what that means in practice: 1. Your site is connected to OTTO and an initial analysis runs. 2. OTTO sets a recurring 7-day cycle from that date. 3. Any new pages added to your site — regardless of when you added them or whether you ran a manual recrawl — will only be detected and analysed at the next scheduled cycle. 4. Once the cycle runs, new pages appear in OTTO and are eligible for recommendations and task generation. There is currently no way to force an immediate OTTO analysis outside of this schedule. This design ensures consistent, reliable processing across all connected sites. ⚙️ What Manual Recrawl Does and Does Not Do You can trigger a manual recrawl from the OTTO SEO section in the left sidebar, then open SEO Automation inside it. Here is a clear breakdown of its scope: - Does: Update the raw crawl data for your site with the latest page URLs, content, and technical signals. - Does: Ensure that when the next OTTO analysis cycle runs, it works from the most up-to-date crawl snapshot. - Does not: Trigger OTTO to immediately analyse new pages. - Does not: Accelerate or reset the 7-day analysis schedule. - Does not: Surface new pages in OTTO recommendations before the next cycle completes. Running a manual recrawl after adding new pages is still a good practice — it means the fresh pages are ready and waiting in the crawl data so OTTO can process them as soon as the next analysis cycle begins. ✅ Recommended Steps After Adding New Pages 1. Go to OTTO SEO in the left sidebar and open SEO Automation inside it (or navigate to /seo-automation-v3). 2. Trigger a manual recrawl to capture your new pages in the crawl dataset. 3. Note the date of your last OTTO analysis — this is shown in the OTTO dashboard. Your new pages will appear after the next 7-day cycle completes from that date. 4. Once the analysis cycle runs, return to the OTTO dashboard to review recommendations for your new pages. ⏱️ How Long Should I Expect to Wait? The maximum wait time is 7 days from your last OTTO analysis. If your last analysis ran 4 days ago, new pages should appear within the next 3 days. If you just had an analysis run today, you may wait a full 7 days before new pages are detected. You do not need to take any additional action during this window. OTTO will automatically pick up pages that are present in the crawl data when the cycle runs. ❓ Frequently Asked Questions - Can I request an immediate OTTO analysis? No — OTTO analysis runs on a fixed 7-day schedule and cannot be triggered manually or on demand at this time. - Will a manual recrawl hurt anything? No. Running a manual recrawl is safe and ensures your crawl data is current before the next analysis cycle. - What if my pages still do not appear after 7 days? First confirm the pages are publicly accessible and not blocked by your robots.txt file. Then run a manual recrawl and wait for the next cycle. If the issue persists, contact our support team using the chat widget. - Does this apply to all site changes, not just new pages? Yes. Any site change — updated content, removed pages, new metadata — is reflected in OTTO only after the next 7-day analysis cycle processes the updated crawl data. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 Running Multiple SEO Tools Alongside OTTO Without Conflicts

Overview If you use Search Atlas OTTO alongside another SEO plugin such as Rank Math, both tools can write metadata, schema, and canonical tags to the same pages. When two tools output the same fields simultaneously, search engines may see conflicting or duplicate signals — which can hurt rather than help your rankings. This article explains how to safely roll back OTTO changes, configure Rank Math and OTTO so they do not conflict, validate that no duplicate tags are live, and understand how Search Atlas delivers value for local service businesses. How to Roll Back OTTO SEO Changes OTTO logs every change it makes, so you can reverse deployments without manually editing your CMS. To roll back OTTO changes, navigate to the OTTO session for the site you want to revert within your Search Atlas account and look for options to undo or revert previously deployed changes. If you are unable to locate the rollback option within your session, or the specific controls do not appear as expected, please reach out to the support team — a teammate can perform or confirm the rollback on your behalf and walk you through the exact steps for your account's current interface. After reverting any changes, clear your site cache and any CDN cache layer so that search engines and browsers fetch the restored version immediately. Why Duplicate Metadata Is a Problem Duplicate metadata occurs when two tools both inject values into the same HTML fields — for example, two <title> tags, two meta description tags, or two sets of schema markup for the same entity. The specific risks include: - Unpredictable rendering: Browsers and crawlers use the first tag they encounter, so the version you carefully optimised may be ignored entirely. - Schema validation errors: Duplicate or conflicting JSON-LD blocks cause Google's Rich Results Test to flag errors, removing your eligibility for rich snippets. - Wasted crawl budget: Conflicting canonical tags can signal contradictory preferred URLs, confusing crawlers about which version of a page to index. - Ranking instability: Search engines may distrust inconsistent signals and deprioritise affected pages in their index. Configuring Rank Math and OTTO to Coexist The safest approach is a clear division of responsibility: one tool owns on-page metadata and the other owns a separate, non-overlapping scope. The key principle is to ensure that only one tool is actively writing to any given metadata field at a time — for example, title tags, meta descriptions, canonical tags, and schema markup. Review the settings in both OTTO and Rank Math to identify any overlapping output areas and disable the relevant features in whichever tool you designate as secondary for that field type. If you are unsure which settings to adjust or how to confirm that conflicts have been resolved, our support team can review your specific setup and provide tailored guidance. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔌 Disable OTTO Dynamic SEO in WordPress Plugin

🧭 Overview OTTO's Dynamic SEO feature injects SEO signals — including canonical tags — directly into your page output via the Search Atlas WordPress plugin. If you need to stop this behaviour, you can disable Dynamic SEO from within the plugin settings. This article walks you through the exact steps using the verified plugin interface. ⚠️ Before You Begin Make sure you have: - The Search Atlas WordPress plugin installed and activated on your site. - Administrator access to your WordPress dashboard. - Your Search Atlas account connected to the plugin (you can verify this under the plugin's connection settings). 🛑 What Dynamic SEO Does When Dynamic SEO is enabled, OTTO pushes SEO changes — such as canonical tags, meta directives, and structured data — directly to your pages without modifying your WordPress database. Disabling this feature stops all active pixel injections immediately, including any canonical tag overrides applied by OTTO. 📋 How to Disable Dynamic SEO 1. Log in to your WordPress admin dashboard and locate Search Atlas in the left-hand menu. 2. Open the Search Atlas plugin panel by clicking the Search Atlas menu item. This loads the plugin's main settings interface inside WordPress. 3. Go to the OTTO Settings tab within the plugin panel. This tab is labelled OTTO or OTTO SEO depending on your plugin version. 4. Locate the Dynamic SEO toggle. It is listed as Enable Dynamic SEO and is displayed as an on/off switch. 5. Click the toggle to turn it off. The switch will move to the off position and the label will reflect the disabled state. 6. Save your changes if prompted. Some plugin versions save automatically on toggle; others display a Save Settings button — click it to confirm. Once disabled, OTTO will stop injecting canonical tags and other Dynamic SEO signals into your page output. Changes take effect immediately without requiring a cache clear or page reload. ✅ How to Confirm Dynamic SEO Is Off After disabling the feature, verify the change was applied correctly: - Reload any page on your site and inspect the page source (Ctrl+U or Cmd+U). Canonical tags previously injected by OTTO should no longer appear in the <head> if they were not originally set by your theme or another plugin. - Return to the OTTO Settings tab in the plugin and confirm the Enable Dynamic SEO toggle is still in the off position. - If you use a caching plugin (such as WP Rocket, W3 Total Cache, or WP Super Cache), clear your site cache after disabling Dynamic SEO to ensure visitors receive updated page output. 🔁 Re-enabling Dynamic SEO If you want to turn Dynamic SEO back on at any point, follow the same steps and toggle Enable Dynamic SEO back to the on position. OTTO will resume injecting SEO signals based on your active automation rules in Search Atlas. 🔗 Related Search Atlas Platform Settings OTTO's automation rules are managed from within your Search Atlas account, not the WordPress plugin. To review or adjust which SEO rules OTTO is applying to your site, navigate to your Search Atlas account and go to OTTO SEO in the left sidebar, then open SEO Automation inside it (URL: /seo-automation-v3). From there you can audit active OTTO tasks, including any canonical tag rules that were in effect before you disabled Dynamic SEO. ❓ Troubleshooting - I don't see an OTTO tab in the plugin. Ensure you are running the latest version of the Search Atlas WordPress plugin. Update the plugin via WordPress Dashboard → Plugins → Updates and check again. - The toggle is greyed out. Your WordPress user account may not have sufficient permissions, or the plugin may have lost its connection to your Search Atlas account. Reconnect the plugin using your Search Atlas API key and try again. - Canonical tags are still appearing after disabling. Another plugin or your theme may be generating its own canonical tags independently of OTTO. Use a tool such as Google's URL Inspection or a browser source view to identify the origin of the tag. - I see an "Enable OTTO Server-Side Rendering" toggle but no Dynamic SEO toggle. These are different features. Server-Side Rendering controls how OTTO renders pages for crawlers and is separate from Dynamic SEO. Do not disable Server-Side Rendering to address canonical tag injection — use only the Enable Dynamic SEO toggle as described above. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Why Site Explorer Shows No Data

🧭 Overview If you open Site Explorer for a domain and see no data — no traffic estimates, no keywords, no backlinks — this is not always a technical error. In many cases, empty results reflect the site's actual organic search footprint. This article explains why this happens and what you can do next. 📋 What Site Explorer Data Is Based On Site Explorer pulls data from Search Atlas's organic search index. This index is built from crawled web data, third-party clickstream signals, and tracked keyword rankings. For a domain to appear with populated data, it must meet certain thresholds: - Recent organic traffic: The domain must have generated measurable organic search traffic within a recent crawl window. - Indexed keywords: At least some of the domain's pages must rank for keywords that Search Atlas tracks. - Crawl coverage: The domain or its pages must have been discovered and processed by the index. If a domain does not meet these thresholds, Site Explorer will return empty or near-empty results. This is expected behavior, not a system error. 🏪 Low-Traffic and Niche Domains Domains with very low organic traffic — such as regional storefronts, subdomain shops, or sites that rely primarily on paid or direct traffic — frequently show no data in Site Explorer. This is because: - Their pages may not rank for any keywords in the Search Atlas tracking database. - Clickstream and crawl signals may be too sparse to meet the minimum data threshold. - A subdomain (e.g., shop.example.com) is indexed separately from the root domain and may have little to no independent organic presence. In these situations, clearing a backend cache will not change the results. There is no cached data to refresh — the index simply has no qualifying data for that domain at this time. 🔎 How to Confirm This Is Expected Behavior Before concluding there is a technical problem, try the following checks: 1. Search the root domain: Enter the root domain (e.g., valvolineglobal.com instead of shop.valvolineglobal.com) in Site Explorer. Subdomains are tracked independently, and the root domain may have significantly more data. 2. Check a high-traffic domain for comparison: Enter a well-known domain to confirm Site Explorer is loading and returning data normally. If data loads for other domains, the issue is specific to the domain you searched — not a platform outage. 3. Review the domain's known traffic profile: If the site primarily uses paid ads, direct traffic, or social channels rather than SEO, it is expected that organic data will be minimal or absent. 4. Try related tools: Navigate to Left sidebar → Keywords → Keyword Magic or Left sidebar → Keywords → Rank Tracker (Keyword Rank Tracker) to see if there is any keyword data associated with the domain through other entry points. 📅 When Data Becomes Available Data availability in Site Explorer is not static. A domain that shows no data today may appear with data in the future if: - It begins ranking for tracked keywords as its SEO efforts grow. - It generates enough organic traffic signals to cross the minimum index threshold. - Search Atlas expands its crawl coverage to include previously unindexed pages. There is no manual override or cache-clearing process that can populate data for a domain that has not yet generated qualifying organic search signals. ⚠️ When to Suspect a Real Technical Issue Empty data is expected for low-traffic domains, but there are situations where a technical problem may be the cause. Contact support if: - A domain that previously showed rich data in Site Explorer has suddenly gone blank with no change in the site's SEO profile. - High-traffic, well-established domains return no data when searched. - Site Explorer fails to load entirely or shows an error message rather than an empty state. 💬 Still Have Questions? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Why OTTO Flags Fewer Meta Description Pages

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

🔍 Why OTTO Title Tags Exceed 60 Characters

🧠 Understanding the 60-Character Guideline The 60-character limit for title tags is a widely cited SEO best practice, not a hard technical rule. Search engines such as Google use pixel width — not character count — to decide where to truncate a title in search results. The 60-character figure is an approximation based on average character widths, which means a title of 62–65 characters using narrow letters (i, l, t, f) may display fully, while a 58-character title using wide letters (W, M) may still get cut off. Because pixel width varies by character, OTTO AI is designed to optimize for readability and keyword completeness within a practical range rather than cutting titles at an arbitrary character count. ⚙️ How OTTO Generates Title Tags OTTO uses contextual signals — your target keyword, brand name, page content, and competitive data — to craft title tags that balance click-through potential with keyword relevance. This approach can produce titles in the 60–88 character range depending on the page and keyword combination. A dedicated AI Grader is built into OTTO to score title tags across multiple quality dimensions, including length. Titles that score poorly are flagged for review. Additionally, a unified post-generation guardrail layer is actively in development to enforce field-level quality constraints — including length limits — across all AI-generated fields automatically. ✅ How to Review and Shorten a Generated Title Tag If you receive a title tag that is longer than you prefer, you can edit it directly inside the platform. Follow these steps: 1. Go to Left sidebar → OTTO SEO → All Sites (SEO Automation) to open your OTTO dashboard. 2. Locate the page whose title tag you want to adjust and open its recommendations. 3. Find the generated title tag and click the edit icon next to it. 4. Shorten the title to your preferred length — aim for under 60 characters while keeping the primary keyword near the front. 5. Save your changes. OTTO will apply the updated title tag to the page. 💡 Tips for Writing Effective Short Title Tags - Lead with the primary keyword. Place the most important term in the first 30–40 characters so it displays even if truncation occurs. - Skip filler words. Remove articles (a, an, the) and conjunctions where the meaning stays clear. - Use a separator before the brand name. Format as Primary Keyword – Brand Name so the brand can be dropped without losing the main message. - Use a pixel-width checker. Tools such as Portent's SERP Preview Tool or Google Search Console's rich results preview show how your title renders at actual pixel width rather than character count. - Test variations. OTTO's AI Grader scores generated titles — use it to compare edited versions before publishing. 🛠️ What Search Atlas Is Doing to Improve This Our engineering team has already shipped an AI Grader for title tags that evaluates length alongside other quality signals. Work is underway on a post-generation guardrail layer that will automatically enforce character and quality thresholds for every AI-generated field in OTTO, reducing the need for manual edits. These improvements will roll out progressively — no action is needed on your end to receive them. ❓ Still Seeing Unexpected Title Lengths? If OTTO is consistently generating titles well above 70 characters for a specific site or page type, this may indicate a configuration issue worth investigating. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

📊 Fix Site Audit Score Drops and OTTO Authority

🔍 Why Your Site Audit Score May Drop After Fixing Issues It can be frustrating to complete all suggested tasks and still see your Site Audit score fall. This is a common experience and usually has a straightforward explanation. Here is what is likely happening: - New issues are being detected. Search Atlas continuously crawls your site. As new pages are published or existing pages change, the crawler discovers fresh technical issues that did not exist during the previous audit. Even if you resolved every prior issue, new ones can push the score down. - The score reflects a percentage of healthy pages. Your audit score is calculated against the total number of pages crawled. If your site grows — more pages indexed, more URLs discovered — the denominator increases. A handful of new errors on new pages can reduce your overall percentage even though your previous fixes are still in place. - Fixes have not yet been re-crawled. Search Atlas needs to re-audit your site to register resolved issues. If you fixed something but have not triggered a fresh crawl, the score will not update until the next scheduled or manual audit run. - Previously hidden pages are now crawlable. Changes to your robots.txt, sitemap, or internal linking structure can expose pages that were previously excluded. These newly discovered pages may carry their own issues. The key takeaway: a dropping score does not always mean your work was wasted. It often means the audit is surfacing deeper layers of your site that were not visible before. ✅ How to Stabilise and Improve Your Site Audit Score 1. Re-run the audit after each round of fixes. Navigate to OTTO SEO in the left sidebar, then open SEO Automation (or go to /seo-automation-v3) and trigger a new crawl so your resolved issues are reflected in the latest score. 2. Prioritise issues by severity. Focus on critical and high-severity errors first. Resolving a large number of warnings will have less impact than fixing a smaller number of critical errors. 3. Review newly discovered pages. After each crawl, filter for issues on URLs that are new to the report. This helps you catch problems introduced by recent site changes before they compound. 4. Check your crawl scope settings. Make sure the audit is scoped correctly so it is not repeatedly discovering large sections of your site that contain known, acceptable issues (such as paginated archive pages). 🚀 Understanding the OTTO Authority Score of 0 If OTTO shows an Authority score of 0, it does not mean something is broken. It means OTTO has not yet deployed any Authority-building actions for your site. OTTO's Authority module is separate from on-page optimisation and requires you to activate specific campaigns and tasks. Authority in Search Atlas is built through deliberate off-page signals. A score of 0 simply indicates that the automated authority workflows have not been started yet. 🛠️ How to Start Building Authority with OTTO Follow these steps to activate OTTO's Authority-building features: 1. In the left sidebar, click Authority. 2. Start with Cloud Stacks — navigate to Authority → Cloud Stacks. Cloud Stacks create a network of high-authority web properties that link back to your site, signalling trust and relevance to search engines. 3. Use the URL Indexer at Authority → URL Indexer to ensure your important pages and newly built authority assets are indexed quickly by search engines. 4. Explore QUEST LLM Visibility at Authority → QUEST LLM Visibility to optimise your brand's presence in AI-generated search results and large language model outputs. 5. Set up outreach and link-building workflows under Authority → Campaigns. Campaigns allow OTTO to automate press release distribution and other authority signals at scale. 6. Monitor responses and opportunities in Authority → Inbox and review what has been sent via Authority → Sent. Once OTTO begins executing Authority tasks, your Authority score will start to increase as actions are completed and signals are registered. 💡 Tips for Getting the Most from Authority Building - Allow time for results. Authority signals — especially backlinks and indexation — take days or weeks to be recognised by search engines. Check your score weekly rather than daily. - Run Cloud Stacks before Campaigns. Building foundational authority assets first gives your outreach campaigns stronger linking destinations, improving their effectiveness. - Keep your Site Audit score healthy in parallel. A technically sound site converts authority signals more effectively. Strong off-page authority combined with a clean technical foundation produces the best ranking outcomes. - Use QUEST LLM Visibility proactively. As AI-driven search results become more prominent, ensuring your brand appears in LLM outputs is an increasingly important part of a complete authority strategy. 📞 Still Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Access Project Overview Instead of Site Audit

Overview When you click on a project in Search Atlas, you may be taken directly to the Site Audit screen instead of the Project Overview. This article explains the difference between these two areas and how to reach the one you need. Project Overview vs. Site Audit These two sections are related but serve different purposes within a project: - Project Overview: The project-level hub where you can manage settings, pages, and tasks such as editing title tags for your site. - Site Audit: A dedicated section for reviewing technical SEO audit reports and audit history for a site. If you land on Site Audit when you expected the Project Overview, you will need to navigate to the correct section within your Search Atlas account. How to Navigate Between Project Overview and Site Audit If you are inside a project and find yourself on the Site Audit screen, look for the navigation options available within your Search Atlas project to switch to the Project Overview. The two sections are separate areas of the same project, and switching between them is done through the in-app navigation. If you are unsure where to find the Project Overview option in your specific account setup, our support team can walk you through the exact steps for your workflow. Need More Help? If you are having trouble locating the Project Overview or continue to land on Site Audit unexpectedly, please reach out to our support team via the chat icon in your Search Atlas account and we will be happy to assist you.

⚙️ Disable OTTO Automated Changes Without Losing Progress

🔍 Overview OTTO is Search Atlas's AI-powered SEO automation engine. It applies on-page optimizations to your site automatically once activated. If you want to stop OTTO from making further changes — without undoing the work it has already completed — this article explains what to expect and how to proceed safely. 💡 What Happens When You Disable OTTO? Before making any changes, it's important to understand the difference between pausing OTTO and rolling back changes: - Disabling or deactivating OTTO stops the OTTO pixel from serving OTTO's changes to your site. Changes written directly into your site's CMS are not served by the pixel, but your project's settings, recommendations, and history are preserved for later reactivation. - Rolling back changes is a separate action that reverses specific optimizations. This article does NOT cover rollbacks — only how to stop future automation. In short: turning off OTTO preserves your project's settings, recommendations, and history for later reactivation, though the OTTO pixel will stop serving OTTO's changes while disengaged. 🛠️ How to Disable OTTO Automated Changes 1. Log in to your Search Atlas account. 2. Navigate to the OTTO SEO section of the platform. 3. Locate the OTTO session connected to the site you want to manage. 4. Click into the OTTO session to open its settings. 5. Find the option to disable or deactivate automation for that session. 6. Turn off automation for the session. 7. Confirm the action if a confirmation prompt appears. Once automation is turned off, OTTO will stop processing new changes, and the OTTO pixel will stop serving OTTO's changes to your site. Changes written directly into your site's CMS are not served by the pixel. ✅ Confirming OTTO Is No Longer Active After disabling automation, verify the status by checking the session settings to confirm that automation has been turned off. If you still see new changes being applied after disabling automation, wait a few minutes for any in-progress tasks to complete, then refresh the page to confirm the updated status. 🔄 Re-Enabling OTTO in the Future You can turn OTTO back on at any time by returning to your OTTO session and switching automation back on. OTTO will resume analyzing and deploying optimizations, and the pixel will resume serving OTTO's changes. Your project's settings, recommendations, and history are preserved during the pause period. ⚠️ Important Considerations - Deactivating does not remove your OTTO project. Settings, recommendations, and history remain visible and accessible for later reactivation. - The OTTO pixel stops serving OTTO's changes while the project is disengaged. Changes written directly into your site's CMS are not served by the pixel. - You remain in full control. You can re-enable automation whenever you are ready to continue. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Stop OTTO Flagging Non-Canonical URL Duplicates

🤔 What Is Happening? When OTTO crawls your site, it may detect two versions of the same page as separate URLs — for example, /blog and /blog/ (with and without a trailing slash). Even if one version has a canonical tag pointing to the other, OTTO treats both URLs as crawlable pages and generates on-page suggestions — such as H1 length warnings or missing alt text — for each one independently. This is not a canonical tag error. OTTO is working as designed: it crawls every URL it discovers and audits the content it finds at that address. The duplicate suggestions appear because both URL versions are being crawled and evaluated, not because your canonical tags are broken. 🕷️ Why OTTO Crawls Both URL Versions OTTO's crawler follows links found in your sitemap, internal links, and server responses. If your server returns a valid page at both /blog and /blog/ — even with a canonical tag on one — the crawler logs both as live URLs and audits both for content issues. The canonical tag tells search engines which version to index, but it does not prevent OTTO from reaching and auditing the non-canonical version. Common reasons both versions are reachable include: - Your server does not redirect one version to the other (for example, /blog does not 301-redirect to /blog/). - Both versions appear in your XML sitemap. - Internal links on your site point to both variants. - A CDN or caching layer serves content at both paths without enforcing a redirect. ✅ The Recommended Fix: Enforce a Server-Side Redirect The most reliable way to stop OTTO — and search engines — from treating both versions as separate pages is to redirect one version permanently to the other at the server level. 1. Decide on your preferred URL format: trailing slash (/blog/) or no trailing slash (/blog). Be consistent across your entire site. 2. Configure a 301 redirect on your server or CDN so the non-preferred version automatically redirects to the preferred one. For example, redirect /blog → /blog/. 3. Remove the non-preferred version from your XML sitemap. 4. Update any internal links that point to the non-preferred version. 5. Re-run the OTTO crawl after changes are saved. Once the redirect is in place, OTTO will follow it and only audit the canonical version. After the redirect is live, the duplicate suggestions for the non-canonical URL will no longer appear in future crawls. 🚫 Cannot Implement a Redirect Right Now? If a server-side redirect is not immediately possible, you can tell OTTO to skip the non-canonical URL pattern during its crawl with a URL Exclusion condition: 1. Go to OTTO SEO → All Sites (SEO Automation) at /seo-automation-v3 and open your project. 2. Click the Autopilot / Smart Crawl card at the top of the overview to open the OTTO SEO Settings modal. 3. Scroll to URL Exclusion conditions and click + Add condition. 4. Set it to Exclude all URLs that Contains or Start With a pattern that matches only the variant — for example Contains /blog? for a query-string variant. If the variant cannot be distinguished from the canonical URL by pattern (for example /blog vs /blog/), a server-side redirect remains the reliable fix. 5. Click Update Settings and trigger a recrawl. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Verify OTTO SEO Deployment on Netlify Sites

🧭 Overview OTTO SEO automates on-page optimizations by injecting changes through a pixel script installed on your site. If you publish recommendations in the OTTO SEO → All Sites (SEO Automation) section but do not see title tags or other changes appearing on your Netlify site, the issue is almost always one of four things: the OTTO pixel is missing or mismatched, the OTTO project is paused, the UUID is incorrect, or there is a misunderstanding of how OTTO renders changes. This article walks you through each diagnostic step. ⚠️ Important: OTTO Is Not WordPress-Only OTTO SEO works on any website platform, including Netlify. The deployment method is the same regardless of your platform — a JavaScript pixel script is added to your site's <head>. You do not need a WordPress plugin. If you were previously given WordPress-specific instructions, please follow the Netlify-specific steps below instead. 🔎 Step 1: Verify Your OTTO Pixel Is Installed on Netlify The OTTO pixel must be present in the HTML of every page you want OTTO to manage. To confirm it is installed: 1. Open your Netlify site in a browser and navigate to any page where you expect OTTO changes. 2. Right-click anywhere on the page and select Inspect (or press F12). 3. Click the Elements tab and expand the <head> section. 4. Use Ctrl+F (or Cmd+F on Mac) to search for otto or searchatlas. 5. You should see a <script> tag that references the OTTO pixel. If no script tag appears, the pixel has not been installed. To install the pixel on Netlify, log in to your Netlify dashboard and locate the setting that allows you to inject custom code into the <head> of your site. Paste your OTTO pixel snippet there, then save and redeploy your site. The exact location of this setting may vary depending on your Netlify plan and site configuration — refer to Netlify's own documentation if you are unsure where to find it. 🆔 Step 2: Confirm the UUID Matches Your OTTO Project Each OTTO project has a unique identifier called a UUID. If the UUID in your pixel script does not match the project you are configuring in Search Atlas, OTTO cannot apply changes to your site. 1. In Search Atlas, open the OTTO project connected to your Netlify site. 2. Locate the pixel snippet provided for your project. Copy the UUID — it is the long alphanumeric string inside the script URL, for example: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx. 3. Return to your browser inspect panel on your Netlify site and find the installed pixel script in the <head>. 4. Compare the UUID in the installed script against the UUID shown in your Search Atlas OTTO project. They must be identical. If the UUIDs do not match, replace the pixel script on your Netlify site with the correct snippet from your Search Atlas OTTO project, then save and redeploy. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Verify OTTO Plugin Meta Edits Are Indexing

🧠 How the OTTO Plugin Applies Meta Edits The OTTO plugin delivers meta title and description changes dynamically at the browser level, not by rewriting your website's backend files or database records. This is expected behaviour — OTTO injects the optimised meta tags into the HTML that is served to visitors and search engine crawlers, without touching your CMS theme files, plugin settings, or source templates. Because of this, you will not see the OTTO-generated meta titles reflected inside your WordPress dashboard, Yoast SEO fields, or any other backend editor. That does not mean the edits are missing — it means they are being applied at the output layer, which is exactly where Google reads them. 🔎 How to Verify OTTO Edits in the Rendered Page Source There is an important distinction between View Page Source and Inspect Element in your browser. Use the steps below to check the correct one. 1. Open the page you want to verify in your browser. 2. Right-click anywhere on the page and select Inspect (or press F12) to open DevTools. 3. Click the Elements tab inside DevTools. 4. Use Ctrl+F (Windows) or Cmd+F (Mac) to search for meta name="title" or title. 5. Confirm the OTTO-generated text appears in the rendered DOM. Why not View Page Source? Pressing Ctrl+U shows the raw HTML before JavaScript runs. Because OTTO injects tags after page load, the raw source may still show your old CMS meta values. The DevTools Elements panel shows the final rendered output — this is what Google's crawler processes. 📊 How to Confirm Google Is Indexing the OTTO Meta Tags Once you have confirmed the tags appear in the rendered DOM, use the following methods to verify Google has picked them up. - Google Search Console — URL Inspection Tool: Paste the page URL into the URL Inspection Tool and click Test Live URL. Scroll to the HTML section and check the meta title Google fetched. This renders JavaScript, so it reflects what OTTO injects. - Google Search Results (site: search): Search site:yourdomain.com/your-page-slug in Google. Once Google has re-crawled the page, the OTTO meta title and description will appear in the snippet. - Search Atlas OTTO SEO V3 Dashboard: Navigate to Left sidebar → OTTO SEO → All Sites (SEO Automation) to review which OTTO optimisations are active and deployed on each URL. ⏱️ How Long Does It Take Google to Reflect the Changes? After OTTO applies meta edits, Google needs to re-crawl the page before the new tags appear in search results. Typical timelines are: - High-traffic pages: A few days to one week. - Lower-traffic or less-linked pages: One to four weeks. You can speed this up by submitting the URL for re-indexing inside Google Search Console → URL Inspection → Request Indexing. ⚠️ Common Reasons OTTO Edits May Not Appear - OTTO is not connected or activated for that specific URL. Verify the connection status in Left sidebar → OTTO SEO → All Sites (SEO Automation). - A conflicting plugin is overriding the output. Caching plugins (e.g. WP Rocket, W3 Total Cache) can serve a cached version that bypasses OTTO's injection. Clear your site cache after activating OTTO edits. - The page is blocked from crawling in your robots.txt file or has a noindex directive set elsewhere in your CMS. - You are checking View Page Source instead of DevTools. Always use the Elements panel in DevTools to see the rendered output. ✅ Quick Verification Checklist 1. Open DevTools (F12) → Elements tab → search for the meta title tag. 2. Confirm the OTTO-generated title is present in the rendered DOM. 3. Clear your site cache if you recently activated OTTO. 4. Use Google Search Console URL Inspection → Test Live URL to see what Google fetches. 5. Request re-indexing for priority pages via Search Console. 6. Check OTTO activation status in Left sidebar → OTTO SEO → All Sites (SEO Automation). 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔗 Fix Duplicate OTTO Anchor Texts at Scale

🧭 Overview OTTO's Internal Linking Opportunities feature can, in some cases, apply the same anchor text across a large number of pages, creating widespread duplication. There is currently no bulk regeneration option within the platform. This article explains what to expect and how to get help resolving the issue as efficiently as possible. ⚠️ Understanding the Limitation When OTTO generates anchor text suggestions for Internal Linking Opportunities, it may produce identical anchor text across many URLs — for example, when a batch of pages shares a dominant keyword theme. Once those suggestions are accepted and deployed, the platform does not provide a one-click option to regenerate or replace them in bulk. This is a known product limitation. 🔍 Step 1: Identify the Full Scope of Duplication 1. Navigate to OTTO SEO → All Sites (SEO Automation) using the left sidebar. 2. Open the Internal Linking Opportunities section. 3. Review your deployed suggestions and note which anchor texts appear to be repeated and across how many URLs. 4. Determine whether the duplicates are concentrated on a single target page or spread across multiple targets — this affects which remediation path is most practical. 🚨 Step 2: Escalate to Our Team for Assisted Remediation Because bulk regeneration is not currently available in the platform, and because per-suggestion editing of already-deployed anchor texts is not a confirmed self-serve option at this time, the recommended path for any volume of duplicate anchor text is to contact our team directly. Our team can assess options for assisted remediation based on your specific situation. When you reach out, please have the following information ready to help us assist you faster: - Your project name and the affected domain - The specific anchor text or texts that are duplicated - An estimate of how many URLs or pages are affected - Whether the duplicate suggestions have already been deployed or are still pending - Any relevant timestamps or recent changes to your OTTO settings If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Rolling Back OTTO Heading Overrides

What This Article Covers OTTO (our AI-powered optimization tool) sometimes modifies page headings to improve SEO performance. If OTTO has changed an H2 heading on your page and you want to restore the original version, our support team can process the rollback for you directly. Why Headings Get Overridden OTTO analyzes your pages and may suggest or deploy heading changes to better match search intent and improve ranking potential. While these changes are typically beneficial, you may want to revert them if they conflict with your brand voice, user experience, or page structure. How to Request an H2 Heading Rollback Rolling back an OTTO H2 heading deployment override requires assistance from our support team. To get this resolved as quickly as possible, please reach out with the following information ready: - The URL of the page with the heading you want to revert - The original heading text you want restored - The heading that OTTO deployed (if known) Once our team receives these details, they can process the rollback and restore your original H2 heading. Best Practices for Managing Heading Changes Review Before Deploying: If you have auto-deployment disabled, always review OTTO's suggested heading changes before approving them. This prevents unwanted overrides. Monitor Your Deployments Regularly: Periodically check which changes OTTO has deployed across your site to stay informed about heading modifications. Document Your Rollbacks: If you frequently need to revert certain types of changes, note which pages or heading styles conflict with your brand to inform future OTTO settings. Test Impact: After rolling back a heading, monitor your page rankings for 1–2 weeks to ensure the original heading isn't negatively affecting performance. Troubleshooting Common Issues Not Sure if the Heading Was Deployed? Our support team can confirm whether a heading change has been deployed to your page and whether it is eligible for rollback. Rollback Not Available? Some deployments may not be reversible if they have been superseded by a newer update or are part of an active configuration. Contact our support team to discuss your options and we will be happy to help. If you have any questions or need assistance, please don't hesitate to reach out to our support team via the chat icon in your Search Atlas account.

⏸️ How to Stop OTTO From Changing Your Site

🔍 Overview OTTO SEO can automatically apply on-page optimisations to your website. If you want to stop OTTO from making further changes — without losing the work already done — this article explains what to have ready when you contact our team for hands-on help. 📋 What to Have Ready Before Contacting Support Stopping OTTO from making further changes to your site requires assistance from our support team, who can identify the correct setting or action for your specific project configuration. To help them resolve this as quickly as possible, please have the following ready when you reach out: - Your OTTO SEO project name or the domain it is connected to - A description of the changes OTTO is making that you want to stop - Any steps you have already tried - The date and time you first noticed the unwanted changes 💡 What Happens to Existing Work? Pausing or disabling OTTO activity does not remove optimisations that have already been applied or saved. Your existing project data and optimisations are preserved regardless of how OTTO activity is stopped. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Verify OTTO Pixel After Website Rebuild

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

🔧 OTTO Heading Deployment Behavior on Wix Explained

🧭 Overview When OTTO deploys heading fixes on a Wix site, the changes may look like they have reverted or disappeared. This is expected behavior, not a bug. OTTO uses two distinct fix types for headings, and each one behaves differently depending on whether a heading is missing or simply too long. This article explains both fix types, how they appear on your site, and why your changes are working even when they seem invisible. 📋 The Two Types of Heading Fixes OTTO Deploys OTTO identifies heading issues in two categories, and each category is resolved in a different way. - Missing Heading Fix: When a required heading (for example, an H1) is completely absent from the page, OTTO injects the heading into the page with a display:none style. This means the heading exists in the page's HTML and is fully readable by search engine crawlers, but it is intentionally invisible to human visitors so it does not disrupt your Wix site's visual design. - Length Fix (Too Long or Too Short): When a heading already exists on the page but exceeds or falls below the recommended character length, OTTO replaces the heading text with an optimized version. This replacement is visually live — the updated heading text is visible to both visitors and search engines. 👁️ Why Missing Heading Fixes Look Like They Reverted After OTTO deploys a missing heading fix, you will not see any new text appear on your Wix page. Because the injected heading is set to display:none, it is hidden from view by design. This is the most common reason customers believe their changes have reverted — the fix was successfully deployed, but it is not meant to be seen. To confirm the fix is active, you can inspect the page source or use your browser's developer tools. The heading element will be present in the HTML with an inline display:none style. Search engines read this element and use it for indexing purposes, which is the intended outcome. 🔄 Why Length Fixes May Also Appear to Revert If a length fix appears to have reverted, the most likely explanation is one of the following: - Wix rendering delay: Wix sites can take a short time to reflect script-injected changes after a new page load. Try refreshing the page or clearing your browser cache and checking again. - OTTO re-evaluated the heading: If the heading was subsequently edited in your Wix editor and the text was changed again, OTTO may re-queue it for a new fix on the next optimization cycle. - Deployment is still in progress: Large batches of fixes may take several minutes to propagate. Wait a few minutes before concluding a fix has not applied. 🗂️ Summary of Expected Visibility by Fix Type - Missing heading injected by OTTO → Hidden on page (display:none), visible to search engines, invisible to visitors. This is correct and intentional. - Length-optimized heading replaced by OTTO → Visible on page, updated text shown to both visitors and search engines. 🚀 How to Check OTTO Heading Deployment Status 1. Log in to Search Atlas and navigate to OTTO SEO → All Sites (SEO Automation) using the left sidebar. 2. Select your Wix site and open the OTTO dashboard. 3. Review the Headings section to see which fixes have been marked as deployed. 4. A fix marked as deployed is confirmed active regardless of whether it is visible on the page. 5. To verify a hidden heading in your browser, right-click the page and select View Page Source or open Inspect Element and search for your injected heading text. ⚠️ What Is Not Covered by This Behavior This article covers the standard behavior for Wix sites connected to OTTO. If you are seeing fixes marked as not deployed in the OTTO dashboard, or if a deployed fix disappears from the page source entirely after more than 24 hours, that may indicate a separate connectivity or script issue that requires investigation. 💬 Still Have Questions? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Bulk Deleting Pending OTTO Schema Suggestions

Overview If you have a large number of pending schema suggestions in an OTTO project that you want to remove all at once — for example, because they are outdated or no longer relevant — you can use the bulk action bar in the schema suggestions table to delete multiple selected suggestions at once. This article explains how to do that and what to expect. Bulk Delete for Schema Suggestions OTTO's schema suggestions table includes a bulk action bar that lets you delete multiple selected schema suggestions at once directly from the UI. If you run into any issues, the support team can also assist. How to Request Bulk Removal of Pending Schema Suggestions To get your pending schema suggestions removed, follow these steps before contacting support so your request can be processed without unnecessary back-and-forth: 1. Do not manually delete suggestions one by one if you have a large volume. This is time-consuming and unnecessary — the support team can handle bulk removal on your behalf. 2. Identify the OTTO project where the pending schema suggestions need to be removed. Note the exact project name or the website domain it is associated with (for example, example.com). 3. Confirm the scope of removal. Decide whether you want all pending schema suggestions removed, or only suggestions of a specific schema type (for example, only FAQ or Product schema suggestions). Having this clear before you write in speeds up the process. 4. Contact the support team using the chat widget below and include: - The exact name of the OTTO project (domain or project label as it appears in your dashboard) - Whether you want all pending schema suggestions removed, or a specific subset - A brief reason the suggestions are outdated or no longer needed (optional but helpful for the support agent) 5. Wait for confirmation from the support team. Once the backend action is completed, the agent will confirm that the pending schemas have been cleared from your project. This typically happens within the same support session. Tips for Managing Schema Suggestions Going Forward - Review schema suggestions regularly so they do not accumulate to a point where bulk removal is needed. - When evaluating individual schema suggestions, review the guidance available within the platform to understand whether a suggestion is appropriate for your site before accepting or dismissing it. - If you have questions about which schema types are most beneficial for your site, reach out to the support team for guidance. If you need help with bulk removal of pending schema suggestions, our support team is available via the chat widget below and will be happy to assist you.

🛠️ OTTO SEO Deployments and Manual Backend Conflicts

🔍 Overview OTTO SEO automates on-page optimisations — including title tags, meta descriptions, and structured data — by deploying changes through a connected integration layer. If you are also making manual edits inside your Shopify (or other CMS) backend at the same time, those two sources can conflict, causing changes to appear missing, overwritten, or duplicated. This article explains how OTTO deployments work, what to expect after deploying, and the safest way to manage edits alongside OTTO. ⚙️ How OTTO SEO Deploys Changes When you approve and deploy a fix inside OTTO SEO, the platform pushes that change through its integration with your connected store or site. The deployment does not always edit your theme files or database records directly in the way a manual Shopify edit would. Instead, OTTO injects or overrides values through its connector layer. - Shopify connector: OTTO writes changes via the Shopify API. The update is visible in Search Atlas as "Deployed," but it may take a short crawl or cache-refresh cycle before it appears in your live storefront or in Google Search Console. - Cloudflare integration: For sites using Cloudflare, OTTO can serve optimised tags at the edge, meaning the change is live faster but may not be reflected inside your Shopify admin panel — this is expected behaviour. - Propagation delay: After deployment, allow up to 24–48 hours for search engines to recrawl and reflect the updated tags in search results. ⚠️ Why Title Tags Show as Deployed but Are Not Visible in Shopify This is the most common source of confusion. There are two typical causes: 1. OTTO uses API-level injection, not theme-file edits. When OTTO deploys a title tag via the Shopify API, it updates the SEO fields on the product, collection, or page object — not the Liquid template in your theme. Some Shopify themes prioritise the Liquid template value over the API value, which can make it appear as though nothing changed inside the Shopify editor even though the live HTML <title> tag is correct. 2. A conflicting manual edit was saved after deployment. If you (or a team member) manually edited the same title tag inside Shopify after OTTO deployed its version, your manual save will overwrite OTTO's value. OTTO will still show the status as "Deployed" because the deployment itself succeeded — it does not continuously monitor for subsequent manual changes. 🚫 Avoid Applying Both Manual Edits and OTTO Deployments to the Same Field Editing the same SEO field in both OTTO and your Shopify backend creates a conflict loop and can lead to: - Overwritten changes: whichever edit was saved last will win, and the other will be lost. - Apparent duplication: in rare cases, certain theme configurations can render both values, resulting in duplicate title tags or meta descriptions visible to crawlers. - Confusing status reporting: OTTO will continue to show "Deployed" even if a later manual save has overridden its output. The safest approach is to choose one source of truth for each SEO field and stick to it consistently. ✅ Recommended Workflow Follow these steps to keep OTTO deployments and your Shopify backend in sync: 1. Let OTTO own SEO fields. Once you connect OTTO SEO and begin deploying optimisations, stop editing title tags, meta descriptions, and other OTTO-managed fields directly inside Shopify. Manage all changes through OTTO SEO at Left sidebar → OTTO SEO. 2. Verify the live HTML, not the Shopify admin panel. After a deployment, right-click your live page in a browser and select View Page Source. Search for <title> to confirm the deployed value is present. The Shopify admin editor may not reflect API-level changes. 3. Clear your Shopify and browser cache. If the live source still shows an old value, clear your storefront cache (if applicable) and perform a hard refresh in your browser before assuming the deployment failed. 4. Check for theme overrides. Ask your developer to confirm that your Shopify theme's title tag in the Liquid template reads from the page_title variable rather than a hard-coded string. Hard-coded values will always override API updates. 5. Re-deploy if a manual edit overrode OTTO. If a team member saved a manual change that overwrote OTTO's deployment, simply return to OTTO SEO, find the affected page, and redeploy the fix. 📊 Checking Deployment Status in OTTO SEO To review what OTTO has deployed and its current status: 1. Go to Left sidebar → OTTO SEO (URL: /seo-automation-v3). 2. Find the site or project and open the relevant fix category (for example, Title Tags). 3. Review the status column. A Deployed status confirms the API call succeeded at the time of deployment — it does not guarantee the value has not been overridden since. 4. If you suspect a conflict, redeploy the fix and immediately verify the live page source before making any further manual edits. 💡 Key Takeaways - OTTO deploys SEO changes via API or edge injection — these may not appear inside the Shopify admin editor, which is expected. - "Deployed" in OTTO means the push succeeded, not that the value is immune to later manual overrides. - Editing the same field in both OTTO and Shopify causes conflicts, overwrites, and potential duplication. - Always verify changes by viewing the live page source, not the CMS editor panel. - Choose one system to own each SEO field and do not switch between them without a clear handoff. 🙋 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🤖 Fix AI Disallow Entries in Your Robots.txt

🔍 Understanding the Problem Your live robots.txt file may contain Disallow entries targeting AI crawlers (such as GPTBot, Claude-Web, or similar bots) that do not appear in the Search Atlas robots.txt preview. This mismatch can cause confusion about which version search engines and AI systems are actually reading. The most common reason for this discrepancy is that the rules were added directly to your server or CMS — outside of Search Atlas — and the platform preview only reflects what has been configured and saved within Search Atlas itself. ⚙️ Why the Two Versions Don't Match Search Atlas displays a preview of the robots.txt it manages. If your robots.txt has been edited through any of the following, those changes will appear live but will not be visible inside Search Atlas: - Your CMS settings (e.g. WordPress plugins such as Yoast SEO or Rank Math) - Hosting control panel file managers (cPanel, Plesk, etc.) - Manual FTP or SSH edits to the root directory file - A CDN or reverse proxy injecting headers or rewrite rules Because your live robots.txt is the file that crawlers actually read, any rules added outside Search Atlas take effect immediately — even though they are invisible in the platform preview. 🛠️ How to Identify the Source of the AI Disallow Entries 1. Open your live robots.txt by navigating to https://yourdomain.com/robots.txt in a browser. 2. Copy the AI-related Disallow entries you see there. 3. Log in to your CMS and check any SEO plugin settings that manage robots.txt output. 4. Check your hosting control panel for a robots.txt file in the root (public_html or www) directory. 5. If you use a CDN (Cloudflare, Fastly, etc.), review any page rules or transform rules that could modify the file. Identifying the source is the critical first step — without it, any edits you make in Search Atlas may be overridden by the external source. ✅ How to Fix the Mismatch Once you have identified where the AI disallow entries are coming from, choose the appropriate resolution below. Option 1 — Remove the rules from the external source (recommended) 1. Delete or disable the AI disallow entries in your CMS plugin, hosting file manager, or CDN configuration. 2. Verify your live robots.txt no longer contains those entries. 3. Add any rules you want to keep into Search Atlas so they are managed in one place. Option 2 — Let Search Atlas manage robots.txt exclusively 1. Disable robots.txt output in your CMS SEO plugin (look for a setting such as "Let your CMS manage robots.txt" and turn it off). 2. Remove any manually created robots.txt file from your server root. 3. In Search Atlas, configure all the rules you need — including any intentional AI bot restrictions — and publish them. Option 3 — Keep external management and mirror the rules in Search Atlas If you prefer to manage robots.txt outside Search Atlas, manually replicate any AI disallow entries inside the platform so the preview stays accurate and your team has a single reference point. 💡 Should You Block AI Crawlers? Whether to allow or block AI content crawlers is a business decision. Keep these points in mind: - Blocking AI bots (e.g. GPTBot, Claude-Web, PerplexityBot) prevents those systems from using your content for training or answers, but it does not affect traditional search engine rankings. - Allowing AI crawlers may increase your content's visibility inside AI-powered search experiences and answer engines. - Always test your live robots.txt after making changes using Google Search Console's robots.txt tester or a third-party validator. 🔄 Verifying Your Changes 1. Wait 2–5 minutes after saving any edits for server caches to clear. 2. Reload https://yourdomain.com/robots.txt in an incognito window to see the live version without browser cache. 3. Compare the live file with the Search Atlas preview to confirm they now match. 4. Use Google Search Console (Settings → robots.txt) to check how Google currently reads the file. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

↩️ Roll Back OTTO H2 Heading Deployment Overrides

🔍 Overview When OTTO deploys on-page SEO optimizations, it can automatically update H2 headings across your site to improve keyword targeting. In some cases, this may replace custom or business-critical headings — for example, changing a heading like Background Checks on your Services page to an SEO-optimized variant you did not intend to keep. This article explains how to identify those overrides, roll them back, and prevent OTTO from redeploying them. 🗺️ Step 1: Locate the Affected Page in Page Explorer Navigate to Left sidebar → OTTO SEO → Site Audit → Page Explorer and use the search bar to find the specific page where the H2 heading was changed (for example, your Services page). Click the page URL to open its detail view. Here you will see a full list of on-page elements OTTO has analysed or modified, including all heading tags. 📋 Step 2: Review Deployed H2 Changes in Tasks Go to Left sidebar → OTTO SEO → All Sites (SEO Automation) → Select your project → Tasks. Filter the task list by Status: Deployed and by Type: H2 (or use the search field to look for the page URL). This will surface every H2 heading task that OTTO has already pushed live. Locate the task that corresponds to the heading you want to revert. ↩️ Step 3: Revert the Deployed Heading Once you have found the deployed H2 task, follow these steps: 1. Click the task row to expand its detail panel. 2. Review the Original Value (your previous heading text) and the Deployed Value (what OTTO changed it to). 3. Click Revert (or Undo Deployment) to restore the original heading. OTTO will push the original value back to your site. 4. Confirm the action in the dialogue that appears. The task status will update to Reverted. After reverting, return to Left sidebar → OTTO SEO → Site Audit → Page Explorer and reload the page record to confirm the H2 heading now displays your intended text. 🚫 Step 4: Prevent OTTO from Redeploying the Override Reverting alone does not stop OTTO from suggesting or re-deploying the same change in a future optimization run. To lock the heading: 1. In the task detail panel (accessible from Left sidebar → OTTO SEO → All Sites (SEO Automation) → Select your project → Tasks), locate the reverted H2 task. 2. Select Dismiss or Ignore on the task. This signals to OTTO that this specific recommendation should not be reapplied. 3. If your project supports page-level exclusions, go to Left sidebar → OTTO SEO → All Sites, open your project card, and check the settings for page or element exclusions. Adding the page URL to an exclusion list will prevent OTTO from modifying any headings on that page automatically. ✅ Step 5: Verify the Fix Is Live To confirm everything is working as expected: - Visit the live page in your browser and hard-refresh (Ctrl + Shift + R on Windows or Cmd + Shift + R on Mac) to bypass cache. - Check Left sidebar → OTTO SEO → Site Audit → Crawl Monitoring to trigger a fresh crawl of the affected URL and verify the corrected H2 heading is detected. - Return to Left sidebar → OTTO SEO → Site Audit → Page Explorer and confirm the heading value shown matches your intended text. 💡 Tips to Avoid Unintended Heading Overrides - Review tasks before deploying in bulk. In Left sidebar → OTTO SEO → All Sites (SEO Automation) → Select your project → Tasks, always preview H2 recommendations for key pages — such as service, product, or brand pages — before approving a batch deployment. - Use selective deployment. Rather than deploying all recommendations at once, filter by page or task type and deploy in smaller batches so changes are easier to audit and reverse. - **Check the Overview regularly.**Left sidebar → OTTO SEO → Overview gives a high-level summary of recent OTTO activity, helping you spot unexpected changes early. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Understanding OTTO Title Tag Issues and Suggestions

🧭 Overview When OTTO detects a Title Tag issue on your site, it flags the page and displays the current title value. You may notice that OTTO does not immediately explain why the title needs updating, and that generating a suggested replacement requires AI credits. This article explains how the Title Tag issue type works, what triggers a flag, and how to get actionable suggestions. ⚠️ Why OTTO Flags a Title Tag OTTO evaluates every page title against a set of on-page SEO best practices. A title is flagged when one or more of the following conditions are detected: - Too short or too long: Titles should fall within the recommended range of 30–100 characters. Titles outside this range may be truncated or under-descriptive in search results. - Missing target keyword: The primary keyword for the page is absent from the title, reducing its relevance signal to search engines. - Duplicate title: The same title appears on multiple pages, which can cause indexing confusion and keyword cannibalisation. - Generic or non-descriptive text: Titles such as "Home" or "Page 1" provide no meaningful context to users or crawlers. Currently, OTTO displays the flagged title value so you can review it directly, but a detailed written explanation of the specific rule that triggered the flag is not yet shown inline. This diagnostic improvement is on our product roadmap and is actively being developed. 💡 Why AI Credits Are Required for Suggestions Generating a replacement title is not a simple rule lookup — OTTO uses AI to analyse your page content, target keyword, and character constraints before producing a contextually relevant suggestion. This generation process consumes AI credits because it calls a large language model to craft a title that is both SEO-optimised and aligned with your content. Think of the AI credit as the cost of having a specialist writer review your page and propose an improved title, rather than applying a generic template. 🛠️ How to Review and Fix Title Tag Issues in OTTO 1. Open OTTO from your Search Atlas dashboard and navigate to the Title Tags issue category. 2. Review the current title shown for each flagged page. Cross-reference the common flag reasons listed above to identify the likely problem (e.g., check character count, look for your target keyword). 3. When you are ready to generate a suggestion, click the Generate button next to the flagged title. OTTO will use AI credits to produce an optimised replacement. 4. Review the suggested title. If it meets your needs, apply it directly. If you prefer to write your own fix, you can manually edit the title field without spending any credits. 5. Once a title is updated, mark the issue as resolved so OTTO tracks your progress accurately. 📊 Managing Your AI Credits To avoid running out of credits unexpectedly, consider these tips: - Prioritise generating suggestions for pages with the highest traffic or strategic importance first. - For straightforward fixes — such as a title that is simply too long — edit the title manually to save credits for more complex cases. - You can check your remaining AI credit balance in your account settings at any time. 🚧 Known Issues and Upcoming Improvements Our engineering team is actively working on several improvements related to Title Tag diagnostics: - A "How it works" tooltip update is in development that will clarify the 30–100 character range guideline directly within the OTTO interface, so the flagging criteria are immediately visible without leaving the page. - Work is ongoing to ensure title tag suggestions are consistently unique and meaningfully differentiated from the original title. - A bug affecting title tag display on page load is also being resolved to improve the stability of the OTTO interface. These updates will roll out progressively. No action is required on your end — improvements will appear automatically once deployed. ❓ Frequently Asked Questions - Can I fix a title tag without using AI credits? Yes. You can type your own replacement title directly into the editable field. AI credits are only consumed when you click Generate to request an AI-written suggestion. - Why does the suggestion look very similar to my original title? In some cases, the original title may already be close to optimal, and the AI makes minor refinements. If you receive a suggestion that feels too similar, try editing the title manually for a more distinct result. Our team has also addressed cases of near-identical suggestions in a recent update. - Will OTTO explain the reason for each flag in the future? Yes. Inline diagnostic explanations are planned as part of ongoing OTTO improvements. The tooltip update currently in development is a first step toward this goal. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🗺️ Remove or Disable Duplicate Sitemaps in Otto

🔍 What Are Duplicate Sitemaps? Duplicate sitemaps occur when Otto detects more than one sitemap pointing to the same content but under different URLs. The most common example is a www vs non-www conflict, such as: - www.bleudentist.com/sitemap.xml - bleudentist.com/sitemap.xml Both URLs resolve to the same sitemap file, but search engines may treat them as separate sitemaps. This can dilute crawl signals, cause indexing confusion, and trigger technical SEO warnings inside Otto. Resolving this keeps your site's crawl data clean and ensures Otto is only tracking one authoritative sitemap. ⚠️ Why This Happens Otto automatically discovers all sitemaps associated with your connected domain. If your site responds to both the www and non-www versions of its URL without a proper redirect in place, Otto will register both sitemap variants as active. This is not an Otto error — it reflects the actual configuration of your website and needs to be resolved either at the sitemap level inside Otto or at the server level on your site. 🛠️ How to Disable a Duplicate Sitemap in Otto Follow these steps to remove or disable the duplicate sitemap entry inside Otto: 1. Log in to your Search Atlas account and navigate to OTTO SEO using the left sidebar, then open SEO Automation inside it. 2. Select the project for the affected domain (for example, bleudentist.com). 3. Inside the project dashboard, locate the Otto panel and open it. 4. Look for the Sitemaps section. Otto will display all discovered sitemaps for your domain. 5. Identify the duplicate entry — this is typically the sitemap using the non-canonical version of your URL. For example, if your canonical domain is www.bleudentist.com, the duplicate would be bleudentist.com/sitemap.xml (without www), or vice versa. 6. Select the duplicate sitemap entry and choose the option to disable or remove it from Otto's tracking. 7. Confirm the change. Otto will stop processing the disabled sitemap in future crawls. After completing these steps, only your preferred canonical sitemap will remain active in Otto. ✅ How to Identify the Correct Sitemap to Keep Always keep the sitemap that matches your site's canonical domain — the preferred URL version you use consistently across your site and in Google Search Console. To verify which version is canonical: - Check your Google Search Console account. The domain listed under your verified property is your canonical version. - Test both URLs in a browser. The version that does not redirect to the other is typically the canonical one. - Check your website's robots.txt file (e.g., yourdomain.com/robots.txt). The sitemap URL declared there should match the version you keep active in Otto. 🌐 Fix the Root Cause: Set Up a Redirect on Your Server Disabling the duplicate inside Otto resolves the issue at the SEO automation level, but the underlying cause — your site responding to both www and non-www URLs without redirecting — should also be fixed to prevent the duplication from reappearing and to protect your overall SEO. To permanently resolve this, configure a 301 redirect on your server so that all traffic to the non-canonical version automatically redirects to the canonical version. For example: - If your canonical domain is www.bleudentist.com, set up a 301 redirect from bleudentist.com to www.bleudentist.com for all pages. - If your canonical domain is bleudentist.com (non-www), redirect www.bleudentist.com to bleudentist.com. This redirect is typically configured in your .htaccess file (Apache), nginx.conf (NGINX), or through your hosting provider's domain settings. Once the redirect is live, rerun a crawl in Otto so it can verify the duplicate no longer exists. 🔄 Re-sync Sitemaps After Making Changes After disabling the duplicate in Otto and optionally fixing the server redirect, trigger a fresh sitemap discovery to confirm everything is resolved: 1. Return to the Sitemaps section inside the Otto panel. 2. Select Re-sync or Refresh Sitemaps to prompt Otto to re-discover your site's sitemaps. 3. Confirm that only one sitemap entry now appears for your domain. If the duplicate reappears after re-syncing, it means the www vs non-www redirect has not yet been applied at the server level. Address the redirect first, then re-sync again. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 OTTO SEO Compatibility With GoDaddy Website Marketing

🧩 What Is OTTO SEO and How Does It Work? OTTO SEO is Search Atlas's AI-powered SEO automation tool. It applies on-page optimisations, manages deployments, and integrates with your site's infrastructure to improve rankings automatically. To do this, OTTO SEO requires a technical connection to your website — either through a CMS connector (such as WordPress) or a Cloudflare Worker that can intercept and modify your site's content at the edge. ⚠️ Why OTTO SEO Does Not Support GoDaddy Website Marketing GoDaddy Website Marketing is a closed, proprietary website builder. It does not allow third-party tools to install plugins, configure workers, or access the site's underlying code in the way OTTO SEO requires. Specifically, GoDaddy Website Marketing does not support: - CMS connectors — OTTO SEO cannot integrate with GoDaddy's builder as it would with WordPress or other open platforms. - Cloudflare Workers — GoDaddy Website Marketing does not give users access to Cloudflare or equivalent edge-layer configuration, which OTTO SEO uses to deploy optimisations. Because neither integration method is available, OTTO SEO cannot activate, deploy changes, or deliver any SEO improvements on a GoDaddy Website Marketing site. Connecting OTTO SEO to this type of site will not produce results, and activation will fail. ✅ Compatible Platforms for OTTO SEO OTTO SEO works with platforms that support at least one of the required connection methods. Compatible options include: - WordPress — via the Search Atlas WordPress plugin (recommended for full feature access). - Sites hosted on Cloudflare — via Cloudflare Worker deployment, regardless of the CMS used. - Search Atlas Website Studio — built-in compatibility; no additional configuration required. Access it from the left sidebar under Website Studio. If you are considering migrating away from GoDaddy Website Marketing, moving to one of these platforms will allow you to take full advantage of OTTO SEO's automation capabilities. ❌ How to Cancel Your Search Atlas Subscription If OTTO SEO does not meet your needs because your site runs on GoDaddy Website Marketing and you do not plan to migrate, you may cancel your subscription. Follow these steps: 1. Log in to your Search Atlas account. 2. Click your avatar in the top-right corner of the platform. 3. Navigate to Billing → Plans & Top-ups. 4. Use Manage Subscription and follow the on-screen prompts to confirm. Your access will remain active until the end of your current billing period. No charges will occur after cancellation takes effect. If you experience any issues completing the cancellation steps, or if the option is not visible in your account, please reach out for immediate assistance. 💡 Consider These Alternatives Before Cancelling Before cancelling, it is worth knowing that Search Atlas offers a range of SEO tools beyond OTTO SEO that do not require a site connection, including: - Keyword research and content planning tools. - Rank tracking for any domain, regardless of platform. - Backlink analysis and competitor research. - Content Editor for writing optimised content manually. These tools can still add value even if OTTO SEO's automated deployment is not available for your site. You can explore them at any time from the left sidebar in your Search Atlas account. 🆘 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

📊 Understanding and Improving Your OTTO Optimization Score

🔍 What Is the OTTO Optimization Score? The OTTO Optimization Score is a 0–100 rating that reflects how well your site's SEO health aligns with best practices detected during each crawl. A higher score means fewer issues and stronger overall optimization. Scores are recalculated every time OTTO runs a fresh audit, so it is normal to see the number shift — up or down — between sessions. 📉 Why Did My Score Decrease? A drop in your score does not always mean your site got worse. Several factors can cause a decrease even when you have been actively working on your SEO: - Crawl freshness: Each new audit scans your live site in real time. Pages added, modified, or broken since the last crawl are included in the updated score calculation. - Algorithm updates: OTTO's scoring model is updated regularly to reflect current SEO best practices. A rule that previously had low weight may now carry more impact. - New issues detected: As your site grows, new content can introduce new issues — missing meta tags, thin content, broken internal links — that were not present in the previous audit. - Regression on previously fixed items: CMS updates, plugin changes, or template edits can reintroduce issues that were already resolved. A drop from 68 to 63, for example, typically signals that five or more medium-impact issues were detected in the latest crawl that were not flagged before, or that existing issues increased in severity. 🗂️ The Five Impact Categories Explained OTTO groups every detected issue into one of five impact categories. Understanding each one helps you prioritise your fixes effectively. 1. Critical Issues: These carry the highest score penalty. Examples include pages returning 4xx/5xx errors, missing canonical tags on duplicate content, and blocked resources in your robots.txt that prevent indexing. Each unresolved critical issue can subtract multiple points from your score. 2. On-Page SEO: Covers title tags, meta descriptions, heading structure (H1–H6), and keyword usage. For instance, a page missing a unique H1 or containing a duplicate title tag across multiple URLs will be flagged here. 3. Content Quality: Flags thin pages (low word count), duplicate content blocks, and pages with poor keyword relevance. A blog post under 300 words with no target keyword in the body is a typical example. 4. Technical SEO: Includes site speed signals, structured data errors, mobile usability issues, and broken internal links. A page with invalid schema markup or a Core Web Vitals failure falls into this category. 5. Link Health: Covers broken outbound links, orphaned pages with no internal links pointing to them, and internal link equity distribution. A page buried more than four clicks from the homepage with no backlinks is a common example. 🛠️ Step-by-Step Fix Procedures Follow these steps inside Search Atlas to address each category and recover your score. Step 1 — Open your OTTO audit. In the left sidebar, click OTTO SEO, then open SEO Automation. Your current Optimization Score and all flagged issues are displayed on the main dashboard. Step 2 — Sort issues by impact. Use the issue filter to sort by Critical first. Resolving one critical issue recovers more points than resolving several low-impact ones. Step 3 — Fix Critical Issues. Click any critical issue to expand its detail panel. OTTO displays the affected URLs, the specific problem, and a recommended fix. Apply the fix directly in your CMS or hosting environment, then click Mark as Resolved inside OTTO to queue that URL for re-evaluation. Step 4 — Fix On-Page SEO issues. Select the On-Page SEO category. Use the inline suggestions to rewrite title tags and meta descriptions directly in your CMS. For bulk issues (e.g., 20+ pages missing meta descriptions), export the list using the Export button and update in bulk, then re-import or apply changes through your CMS. Step 5 — Improve Content Quality. Navigate to Left sidebar → Keywords → Keyword Magic to identify relevant keywords with sufficient search volume. Use these keywords to enrich thin pages flagged by OTTO. Aim for at least 600 words of original, topically relevant content per flagged page. Step 6 — Resolve Technical SEO issues. Review structured data errors and fix invalid schema in your CMS or theme settings. For Core Web Vitals issues, work with your developer to optimise image sizes, reduce render-blocking scripts, and enable caching. After deploying fixes, return to OTTO SEO → Site Audit and mark those items resolved. Step 7 — Fix Link Health issues. Broken outbound links should be updated or removed. For orphaned pages, add contextual internal links from related, higher-authority pages on your site. Use Left sidebar → Keywords → Rank Tracker to identify your best-performing pages as strong internal linking candidates. Step 8 — Trigger a new audit. Once you have resolved a meaningful batch of issues, click Recrawl Site inside OTTO SEO → Site Audit. OTTO will crawl your site and recalculate your score based on the current state. ⏱️ How Long Does Score Recovery Take? Recovery timelines depend on the number and type of issues resolved: - Immediate (within the next audit): Fixing critical errors like 404 pages, missing canonical tags, or broken redirects typically reflects in the very next re-audit, which can be triggered manually at any time. - 1–3 days: On-page fixes such as updated title tags and meta descriptions are picked up quickly after you trigger a fresh crawl. - 1–2 weeks: Content quality improvements take slightly longer as OTTO evaluates topical depth and keyword relevance over a more thorough crawl cycle. - 2–4 weeks: Technical SEO improvements, especially Core Web Vitals changes, may require multiple crawls and real-world performance validation before they are fully reflected in your score. As a general benchmark, resolving all critical and high-impact issues in one session typically restores 5–15 points within the first two re-audits. Consistent weekly maintenance keeps your score trending upward over time. 💡 Best Practices to Maintain a High Score - Schedule a weekly re-audit inside OTTO SEO → Site Audit to catch regressions early. - After any major site update (theme change, CMS migration, new content batch), trigger a manual re-audit immediately. - Use Left sidebar → Keywords → Keyword Gap to discover content opportunities that improve both rankings and content quality scores simultaneously. - Prioritise Critical and On-Page issues before tackling Link Health — the point recovery is faster and the SEO impact is greater. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 OTTO Schema Markup & Redirect Link Warnings Explained

📋 Why Page-Level Schema Suggestions Cannot Be Completed or Dismissed OTTO and Brian generate page-level schema suggestions based on crawl data and content analysis. These suggestions are automated recommendations, not mandatory tasks. The platform currently does not provide a Dismiss or Mark Complete button for page-level schema items because they are informational only. They exist to guide your schema implementation strategy. If you have already implemented the recommended schema on the page, you can safely ignore the suggestion. No action is required in the platform to clear it. ⭐ Why Review and Aggregate Rating Fields Show Errors Without Review Data Schema markup for Review and AggregateRating requires actual review content on the page — such as user ratings, testimonials, or structured review blocks. If OTTO detects schema markup for these types but finds no corresponding review data in the page content or structured data, it flags an error. This is a validation check to prevent invalid schema that could trigger Google warnings. To resolve: either add genuine review content to the page or remove the Review/AggregateRating schema markup from the page's code. 🔗 Why Redirected Old URLs Still Generate Internal Link Issues Internal link warnings are based on the href attribute found in your site's HTML, not the final destination after redirects. If your pages still contain links pointing to old URLs (even if those URLs 301 redirect), OTTO flags them as internal link issues because: search engines crawl the raw link, redirect chains waste crawl budget, and users may experience slower navigation. Fix by updating all internal links to point directly to the current canonical URL. Use the Page Explorer (Left sidebar → OTTO SEO → Site Audit → Page Explorer) to identify pages linking to old URLs, then update the links in your CMS or site code. ✅ Recommended Actions - Treat page-level schema suggestions as advisory — implement if relevant, ignore if already done. - Only include Review/AggregateRating schema when real review data exists on the page. - Audit and update internal links to point directly to final URLs; avoid relying on redirects. - Re-crawl after fixes: Left sidebar → OTTO SEO → Site Audit → Crawl Monitoring → Start New Crawl. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🗺️ GSC Schema Warnings from OTTO Local SEO Updates

🔍 Overview If you received a Google Search Console (GSC) email flagging a schema-related warning tied to a meta description after an OTTO Local SEO update, you are not alone. This is a known, non-critical notification that occurs when OTTO deploys Local SEO schema to your site. No action is required on your part. This article explains what triggered the warning, what it means, and why it is safe to ignore. ⚙️ What Triggered the Warning When OTTO applies a Local SEO update to your site, it injects structured data (schema markup) to help search engines better understand your business information — such as your name, address, phone number, and hours of operation. As part of this deployment, GSC may detect a mismatch between certain schema fields and page-level meta elements, including the meta description. This mismatch triggers a schema warning in GSC and, in some cases, an automated notification email from Google. This is a side effect of how Google validates structured data. It does not indicate a problem with your site, your rankings, or the quality of the schema OTTO deployed. 🟡 Warning vs. Error — What Is the Difference GSC distinguishes between two types of structured data issues: - Errors: Critical problems that prevent Google from processing your schema. These require immediate attention. - Warnings: Non-critical notices that flag a potential inconsistency. Google can still read and use your schema. Warnings do not cause your pages to lose rich result eligibility. The meta description schema warning generated by an OTTO Local SEO update is a warning, not an error. Your schema is valid, functional, and being processed by Google correctly. ✅ Should You Be Concerned No. Schema warnings related to meta descriptions after an OTTO Local SEO deployment are expected behaviour and are completely safe to ignore. Here is why: - The warning does not affect your search rankings. - The warning does not remove or invalidate the Local SEO schema OTTO applied. - The warning does not trigger any manual action or penalty from Google. - Google continues to index and understand your structured data normally. You do not need to modify your meta descriptions, remove the schema, or make any changes to your site in response to this warning. 📋 How to Confirm the Warning Is OTTO-Related If you want to verify that the GSC warning is connected to your OTTO Local SEO update, follow these steps: 1. Log in to Google Search Console and navigate to the structured data or schema-related section of your property. 2. Locate the warning associated with your Local Business schema or the affected URLs. 3. Check the warning timestamp and compare it to the date OTTO deployed the Local SEO update on your site. 4. If the dat

🔌 Remove OTTO SEO From Your Website Completely

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

🔍 Why OTTO Schema Isn't Detected by Static Validators

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

🔍 Find Broken Links in Your OTTO SEO Audit

🗺️ Overview When Search Atlas runs an OTTO SEO audit on your site, it scans every crawlable URL and flags links that return error responses. If your audit has flagged dead links — for example, 157 broken URLs — this article walks you through exactly where to find them and how to review the full list. 🧭 How to Access the OTTO SEO Audit 1. Log in to your Search Atlas account. 2. In the left sidebar, click OTTO SEO, then All Sites (SEO Automation). 3. Your most recent audit results load automatically on the OTTO SEO Overview page (/seo-automation-v3). 🔗 How to Find the Broken Links List 1. On the OTTO SEO Overview page, scroll down past the summary score cards until you reach the audit pillars (Technical, On-Page, Content, etc.). 2. Locate the Technical pillar section. 3. Inside the Technical pillar, look for the Issues with Links section. This is where all broken link findings are grouped. 4. Click on the Issues with Links heading or its expand arrow to open the full list of flagged URLs. 5. You will see each broken link listed with its source page (the page containing the bad link), the broken URL itself, and the HTTP error code returned. 📋 Understanding the Broken Links Results Each entry in the broken links list tells you: - Source page: The page on your site where the broken link appears. - Broken URL: The destination URL that is returning an error. - Error type: The HTTP status code detected (such as 404 Not Found, 410 Gone, 403 Forbidden, or 5xx server errors). The audit checks for a range of error responses — not just 404s — so you may see several different error types in your list. ✅ How to Fix Broken Links Once you have your full list, here are the recommended steps to resolve broken links: 1. Remove the link if the destination page no longer exists and has no replacement. 2. Update the link to point to the correct, live URL if the page has moved. 3. Set up a redirect (301) on your server if the old URL should forward visitors to a new page. 4. After making fixes, return to OTTO SEO and re-run the audit to confirm the broken links have been resolved. ⚠️ Things to Keep in Mind - The number shown on the overview card (for example, 157 dead links) reflects all broken links detected across your entire site at the time the audit was last run. - AI-suggested replacement URLs in the Issues with Links section are generated to guide you — always review suggestions before applying them to confirm they point to the most relevant page on your own domain. - If the Issues with Links section appears blank or the page does not load correctly when a large number of broken links is present, try refreshing the page. This is a known display issue that is actively being resolved. - To get the most up-to-date broken link data, trigger a fresh audit after you have completed fixes. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

📊 Understanding OTTO's Optimization Score and Weekly Refresh

🔍 Why Does My Optimization Score Drop After Fixing Issues? If your OTTO optimization score has fallen after you fixed issues — or previously resolved items are showing up again weeks later — this is expected behavior, not a bug. OTTO is designed to continuously monitor your website and rescan it on a weekly basis. Each rescan reflects the current state of your site, not a historical record of past fixes. This means that if new SEO problems have appeared, existing issues have recurred, or page content has changed in a way that reintroduces a problem, OTTO will flag those items again — even if you marked them as fixed months ago. 🔄 How the Weekly Refresh Cycle Works OTTO automatically rescans your connected website every week. During each rescan, it does the following: - Crawls your site's pages fresh, as they exist right now - Re-evaluates every SEO signal it tracks — titles, meta descriptions, headings, internal links, schema, page speed, and more - Updates your optimization score to reflect the current findings - Flags any issues it detects, regardless of whether they were previously marked as fixed Your optimization score is a live health indicator, not a progress tracker. A score that drops after a rescan means OTTO found new or recurring problems on your site at that point in time. ⚠️ Common Reasons Previously Fixed Issues Reappear There are several reasons an issue you resolved can come back after a rescan: - Content updates introduced a new problem. Editing a page — changing a title, removing a heading, or updating body copy — can unintentionally break an SEO element that was previously correct. - CMS or plugin changes overwrote your fixes. Theme updates, plugin conflicts, or automated CMS changes sometimes reset metadata, schema, or other on-page elements. - The fix was not saved or deployed correctly. If a change was made in a staging environment or not published, the live page OTTO scans will still show the original issue. - The underlying SEO problem was not fully resolved. For example, if a page had a missing meta description and a new description was added but left empty after a template change, OTTO will flag it again. - New pages were added that have the same issue. OTTO scans your whole site. New pages with unfixed SEO problems contribute to your overall score. ✅ How to Keep Your Optimization Score Stable To prevent your score from reverting after each rescan, follow these best practices: 1. Verify fixes on the live site. After making a change, visit the published page directly and confirm the update is visible before marking the issue as resolved in OTTO. 2. Check your CMS settings. Make sure plugins or theme updates are not overwriting your SEO metadata automatically. 3. Review OTTO after each weekly refresh. Make it a routine to log in and check for newly flagged items. Early fixes keep your score high. 4. Use OTTO's issue details before dismissing. Each flagged item includes context about what OTTO found. Review this carefully to make sure your fix directly addresses the root cause. 🗂️ How to Access OTTO and Review Your Current Score To check your optimization score and see which issues OTTO has flagged in the latest rescan: 1. Log in to Search Atlas. 2. In the left sidebar, click OTTO SEO, then open All Sites (SEO Automation). 3. Select your project to open the OTTO dashboard. 4. Review the optimization score at the top of the page and the list of active issues below it. 5. Click any issue to see OTTO's details and recommended fix. 💡 Key Takeaways - OTTO rescans your site every week and recalculates your score based on what it finds at that moment. - A dropping score means new or recurring SEO issues were detected — it does not mean your previous work was undone inside OTTO. - Issues marked as fixed in the past will be flagged again if the same problem reappears on your live site. - Consistent site maintenance is the most reliable way to keep your optimization score high over time. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚠️ OTTO and Site Auditor Shared Quota Explained

🔍 Overview If you encounter a quota limit error when trying to add a new OTTO site — even though your OTTO slots appear available — the most likely cause is that your Site Auditor Projects are already using slots from the same shared quota pool. This article explains how the quota system works and how to free up space so you can activate new OTTO sites. ​ 📦 How the Shared Quota Pool Works Site Auditor Projects and OTTO Sites do not have separate quotas. They draw from the same pool of slots included in your subscription plan. This means: - Every active Site Auditor Project occupies one slot in your quota. - Every active OTTO Site also occupies one slot in the same quota. - The total number of slots available is determined by your current plan, regardless of whether those slots are used by Site Auditor Projects, OTTO Sites, or a combination of both. For example, if your plan includes 10 slots and you have 8 active Site Auditor Projects, only 2 slots remain available for OTTO Sites — even if you have never activated a single OTTO site before. ​ 🚨 Why the Error Appears The quota limit error appears when the combined total of your active Site Auditor Projects and OTTO Sites equals or exceeds your plan's slot limit. The platform checks the full shared pool before allowing a new site to be added, so an apparent availability of OTTO-specific slots can be misleading if Site Auditor Projects have already consumed that space. ​ ✅ How to Resolve the Conflict To free up quota slots and successfully add your OTTO site, you will need to reduce the number of active sites currently consuming slots from your shared pool. Here is how to approach this: 1. Review your currently active Site Auditor Projects and OTTO Sites to identify any that are no longer needed or are lower priority. 2. Remove or deactivate any projects or sites that are inactive so that their slots are returned to your shared pool. 3. Once you have freed up at least one slot, attempt to add your new OTTO site again. 💡 Tips for Managing Your Quota - Audit regularly: Periodically review your active Site Auditor Projects and OTTO Sites to ensure you are only using slots for domains that are actively being worked on. - Remove unused projects: If a domain is no longer in active use, removing it from your Site Auditor Projects or OTTO Sites will return that slot to your shared quota pool. - Plan ahead when onboarding new clients: Before adding a new OTTO site, check your current slot usage across both Site Auditor Projects and OTTO Sites to confirm a slot is available. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Schema Markup Deployment and Image Tag Fixes

🔍 Overview When OTTO SEO audits your site, it may recommend adding schema markup and flag empty image tags in your HTML. Two common questions arise: should OTTO schema overwrite or stack on top of your existing per-page schema? And where is the right place to remove empty image tags — in your HTML or inside OTTO? This article answers both questions clearly so you can deploy with confidence. 📋 How OTTO Schema Works With Existing Schema Markup OTTO adds schema markup at the site or template level, but it is designed to complement, not replace, any unique per-page schema you have already built. Here is what you need to know: - OTTO injects additional schema blocks — it does not overwrite or delete schema that already exists in your page source code. - Multiple schema blocks on the same page are valid — Google and other search engines can read and process more than one JSON-LD block per page without conflict. - Your custom per-page schema takes priority for unique data — if you have hand-crafted schema for specific products, events, or articles, that information is preserved exactly as you wrote it. - Avoid duplicating the same schema type — for example, if you already have a fully populated Article schema on a blog post, do not activate OTTO's Article schema for that same page, as duplicate type blocks can create redundancy and may confuse validators. The safest deployment strategy is to review which schema types OTTO plans to add before activating, and disable any type that already has a complete, custom implementation on that page. For all other pages or schema types you have not yet covered, let OTTO deploy freely. 🖼️ Understanding Empty Image Tags Flagged by OTTO OTTO flags empty <img> tags — HTML image elements that have a blank or missing src attribute — because they can cause accessibility issues, slow page rendering, and trigger validation errors. These tags look something like this in your source code: <img src="" alt=""> or simply <img>. Customers often ask whether they should remove these tags from the HTML directly or dismiss them inside OTTO. The answer depends on where the tag lives and whether you still need it. ✅ When to Remove the Tag From Your HTML In most cases, removing the empty image tag from your HTML source is the correct fix. You should edit your HTML (or your CMS template, page builder, or theme file) when: 1. The image tag is a leftover placeholder that serves no current purpose — for example, a slot that was never populated with an actual image. 2. The tag appears inside a page builder or theme template that you can edit directly. 3. The tag is generated by a plugin or widget you control and can update to stop outputting empty elements. Removing the tag at the source means the issue is permanently resolved and will not reappear in future OTTO scans. This is the recommended approach for a clean, lasting fix. ⚙️ When to Dismiss the Flag Inside OTTO There are situations where dismissing or ignoring the flag inside OTTO is the appropriate action rather than editing your HTML: - The empty image tag is intentional and functional — for example, a placeholder element used by a JavaScript framework that populates it dynamically after page load. - The tag is inside a third-party script or widget you cannot modify, and removing it would break functionality. - Your development team has confirmed the tag is required for a specific layout or animation and its empty state is expected. In these cases, mark the flag as ignored or acknowledged inside OTTO so it does not continue to appear as an open issue. This keeps your OTTO dashboard clean without making changes that could break your site. 🚀 Recommended Deployment Checklist 1. Audit your existing schema — before activating OTTO schema, list which schema types are already present on your key page templates (homepage, product pages, blog posts, etc.). 2. Disable duplicate schema types in OTTO — for any page that already has a fully populated schema type, turn off that specific type in OTTO's schema settings for those pages. 3. Activate OTTO schema for uncovered pages and types — let OTTO handle all pages and schema types that you have not yet implemented manually. 4. Validate after deployment — use Google's Rich Results Test or Schema.org Validator to confirm there are no conflicts or errors after OTTO deploys. 5. Review empty image tag flags — for each flagged tag, check whether it is a genuine leftover placeholder (remove from HTML) or a required dynamic element (dismiss in OTTO). 6. Re-scan after fixes — trigger a fresh OTTO scan to confirm resolved issues no longer appear in your audit report. 💡 Quick Reference Summary - OTTO schema stacks on top of existing schema — it does not overwrite your custom markup. - Avoid enabling the same schema type twice on pages where you already have a complete custom version. - Remove empty image tags from your HTML whenever they are genuine placeholders with no active purpose. - Dismiss the flag inside OTTO only when the empty tag is intentional and required for functionality. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🤖 OTTO Tracking Pages Despite Noindex Tags

🔍 Why OTTO Tracks Pages Even With Noindex Tags Noindex tags and robots.txt directives tell search engines not to index or crawl a page — they do not automatically remove those URLs from OTTO's internal tracking list. When OTTO first crawls your site, it discovers and logs every reachable URL, including paginated URLs such as /page/2, /page/3, and query-string variants like ?paged=2. Those URLs remain in OTTO's database until they are explicitly excluded or removed, regardless of any noindex or robots.txt changes made after the initial crawl. The key distinction: noindex controls what Google indexes. OTTO's tracked page count reflects every URL that has been discovered and queued for monitoring — these are two separate systems that do not automatically sync. ⚙️ How Crawl Limits and Robots.txt Interact With OTTO Lowering the crawl limit in your project settings affects how many new pages OTTO discovers on future crawls — it does not retroactively remove URLs already added to your tracked list. Likewise, adding a robots.txt block prevents OTTO from re-crawling those paths on future runs, but does not instantly delete them from your current page count. This is why you may see a high tracked page count (for example, 922 pages) even after applying all three changes — noindex tags, robots.txt blocks, and a lower crawl limit. The count only decreases once already-tracked URLs are actively excluded from OTTO's page list. 📋 How to Exclude Paginated URLs From OTTO Follow these steps to remove paginated and noindexed URLs from OTTO's tracking and bring your page count down to your target. 1. Go to Left sidebar → OTTO SEO → All Sites and click on your project card to open the project. 2. Navigate to Left sidebar → OTTO SEO → Site Audit → Page Explorer. This screen lists every URL currently tracked by OTTO for your project. 3. Use the search bar or URL filter to isolate paginated URLs — for example, filter by patterns containing /page/, ?paged=, or whichever pagination format your site uses. 4. Select all paginated URLs you want to remove. Use the bulk-select checkbox at the top of the list to select all filtered results at once. 5. Click Exclude or Remove from tracking to dequeue those URLs. OTTO will stop monitoring them, and they will no longer count toward your tracked page total. 6. Confirm the action when prompted. Your tracked page count will update to reflect the removed URLs. 🔄 Preventing Paginated URLs From Being Re-Added After removing the unwanted URLs, take these additional steps to stop them from reappearing in the next crawl cycle. - Keep your robots.txt block in place — this signals OTTO not to re-crawl those URL patterns in future runs. - Verify noindex tags are server-side rendered — go to Left sidebar → OTTO SEO → Site Audit → Crawl Monitoring to review which pages OTTO detected as noindexed. Tags rendered only via client-side JavaScript may not be read correctly during crawl; ensure they appear in the raw HTML response. - Add a URL Exclusion condition — in Left sidebar → OTTO SEO → All Sites (SEO Automation), open your project and click the Autopilot / Smart Crawl card to open the OTTO SEO Settings modal. Under URL Exclusion conditions, click + Add condition and set it to Exclude all URLs that Contains /page/ or ?paged= to permanently block paginated paths. This prevents newly discovered paginated URLs from being added to your list in the future. - Confirm your crawl limit is still set correctly — your lowered crawl limit reinforces the exclusion rules by capping how many pages OTTO queues per crawl cycle. ✅ Verifying Your Updated Page Count After completing the steps above, go to Left sidebar → OTTO SEO → Overview to view your refreshed tracked page total. Allow up to one full crawl cycle for the count to update completely. If the count is still higher than expected, return to Left sidebar → OTTO SEO → Site Audit → Page Explorer and check for any remaining paginated or noindexed URLs that were not captured in your initial filter — for example, URLs with different pagination patterns or query strings. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 What Happens When You Remove the OTTO Pixel

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

🦆 Remove Hidden OTTO Keyword Injection From Your Homepage

🔍 What This Article Covers Sometimes OTTO can inject text that does not match your business, such as unrelated keywords or entities (for example, duck, mallard, or call duck) into your homepage HTML. This usually happens because the OTTO Natural Language Processing (NLP) and entity modules learned from incorrect data about your site. This guide shows you how to remove and regenerate only that faulty output, while keeping OTTO active everywhere else. 💡 Why This Happens OTTO analyzes your site to understand its topic, then server-side renders SEO enhancements like keyword references, entities, and structured data into your pages. If OTTO's understanding of your homepage was built from inaccurate crawl data, cached content, or an incorrect Knowledge Graph, it can generate keyword and entity content that has nothing to do with your business. This appears in your live HTML because OTTO serves these enhancements through the Cloudflare worker or JavaScript snippet you installed. Unexpected or irrelevant text being injected into the page source is a recognized behavior that our engineering team has investigated and resolved, so following the steps below to remove the faulty output and correct the source data will clear it up. ⚙️ Before You Begin Have the following ready so the fix is quick and accurate: - Access to your OTTO project inside the platform. - The exact incorrect keywords or entities you are seeing (for example, the duck-related terms). - Confirmation that OTTO is installed and deployed on the affected domain. 🛠️ Step 1: Locate the Incorrect Output First, confirm where the bad content is coming from. 1. Go to OTTO SEO → All Sites → [your project] (OTTO Grader) → Pending Optimizations. 2. Filter to your homepage URL. 3. Review the deployed suggestions and look for NLP keyword, entity, or content-injection items that reference the incorrect terms. 4. Note each incorrect suggestion so you can target it precisely. 🧹 Step 2: Remove the Faulty Suggestions You can delete individual pieces of incorrect output without turning OTTO off. 1. Select the specific homepage suggestion containing the wrong keywords or entities. 2. Choose Delete or toggle it off to stop it from deploying. 3. Repeat for every incorrect NLP or entity item on the homepage. 4. Redeploy your changes so the corrected output is pushed live. OTTO also includes an AI-powered option to remove irrelevant terms, which you can use to help clear out entities and keywords that do not match your business. This keeps every other page and every correct optimization fully intact. 📊 Step 3: Correct the Source Data To stop the wrong keywords from returning, fix what OTTO learned about your site. 1. Open the Knowledge Graph for your project and confirm your business name, industry, entities, and topics are accurate. 2. Remove any incorrect entities (such as the duck-related terms) and save your changes. 3. Update your homepage description or target keywords if they were set incorrectly. Accurate source data ensures newly generated suggestions reflect your real business. 🔄 Step 4: Regenerate Only the Homepage Output Now rebuild the corrected suggestions for that single page. 1. Trigger a recrawl of your homepage so OTTO reads the current, accurate content. 2. Use the regenerate option on the homepage to create fresh NLP and entity suggestions. 3. Review the new output before it deploys to confirm the incorrect terms are gone. 4. Deploy the approved suggestions. Because you are targeting only the homepage, the rest of your OTTO deployment continues running normally. ✅ Step 5: Verify the Fix Is Live 1. Wait a few minutes for the deployment and any caching to refresh. 2. Open your homepage and view the page source, or use your browser's inspect tool. 3. Search the HTML for the incorrect keywords to confirm they no longer appear. 4. If your site uses a CDN or cache plugin, clear that cache and check again. 🚀 Keeping OTTO Running Everywhere Else Every step above is scoped to individual suggestions and to your homepage. You never need to pause or uninstall OTTO to fix incorrect output. This means your working optimizations, schema, and indexing features keep delivering results while you clean up the isolated issue.

🧊 Understanding Deepfrozen OTTO Sites and Quota Counts

🔍 Overview If you are on the annual PRO plan and expect to see 4 OTTO Sites but your dashboard shows fewer — or your Active Sites count under OTTO SEO does not match your total quota — a deepfrozen OTTO Site is almost always the reason. This article explains how deepfreeze affects your quota display and how to confirm everything is working as expected. 🧊 What Is a Deepfrozen OTTO Site? Deepfreeze is a state you can apply to an OTTO Site to pause all OTTO SEO activity on that site without permanently removing it from your account. A deepfrozen site is not actively optimised, but it still occupies one slot in your OTTO Sites quota. This is by design — the site remains attached to your account and can be reactivated at any time. 📊 How Deepfreeze Affects Your Quota Display Your OTTO Sites quota and your Active Sites count are two different numbers, and deepfrozen sites cause them to diverge. Here is what each figure represents: - OTTO Sites quota (e.g. 5 of 5 used): The total number of OTTO Site slots consumed across all states — active, paused, and deepfrozen. A deepfrozen site counts toward this total. - Active Sites under OTTO SEO: Only sites that are currently active and receiving OTTO SEO optimisation. Deepfrozen sites are excluded from this count. This means if you have 5 OTTO Sites and 1 is deepfrozen, you will see 4 Active Sites in OTTO SEO and your quota will show 5 of 5 used — which can look like a discrepancy but is correct behaviour. 🗺️ Where to Check Your OTTO Sites and Their States 1. In the left sidebar, click OTTO SEO → All Sites (SEO Automation) (URL: /seo-automation-v3). 2. Review the list of OTTO Sites displayed on the page. 3. Look for any site marked with a deepfrozen status indicator. Deepfrozen sites appear in the list but are not counted in the Active Sites total. 4. Add up all sites across every status — active, paused, and deepfrozen — to confirm the total matches your plan quota. ✅ How to Reconcile a Quota Discrepancy Before concluding there is a billing or entitlement issue, follow these steps: 1. Navigate to OTTO SEO → All Sites (SEO Automation) in the left sidebar. 2. Count every OTTO Site listed, regardless of its current state. 3. Check whether any site shows a deepfrozen status. If one or more sites are deepfrozen, that explains why your Active Sites count is lower than your quota total. 4. If the combined count of all sites — active, paused, and deepfrozen — equals your plan quota (e.g. 4), your account is correctly provisioned and no correction is needed. 5. If the total across all states is still lower than your entitled quota, there may be a genuine provisioning issue worth investigating further. 🔄 How to Unfreeze a Deepfrozen OTTO Site If you deepfroze a site unintentionally or want to reactivate it, you can restore it to active status directly from the OTTO SEO page: 1. Go to OTTO SEO → All Sites (SEO Automation) in the left sidebar. 2. Locate the deepfrozen site in your site list. 3. Select the site and choose the option to unfreeze or reactivate it. 4. Once reactivated, the site will reappear in your Active Sites count and OTTO SEO optimisation will resume. Note that reactivating a deepfrozen site does not consume an additional slot — it simply transitions the existing slot back to an active state. 💡 Quick Reference: Quota Count Summary - Active site: Counts toward quota ✔ | Appears in Active Sites count ✔ - Paused site: Counts toward quota ✔ | Appears in Active Sites count ✗ - Deepfrozen site: Counts toward quota ✔ | Appears in Active Sites count ✗ 🙋 Still Have Questions? If you have checked for deepfrozen sites and your total OTTO Site count across all states is still less than your plan entitlement, there may be a provisioning issue on our end. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Understanding OTTO Audit False-Positive Flags

🧭 Overview When reviewing your OTTO audit results, you may notice flags for Multiple Meta Descriptions or Too Many External Links — even when your page source clearly shows only one meta description and no manually added external links. These are known false-positive scenarios caused by how OTTO's crawler reads your page at the time of the audit. This article explains why they occur and what to expect. 🤔 Why Does This Happen? OTTO's audit engine crawls your live page and parses all rendered HTML, including content injected by third-party scripts, tag managers, or plugins. This means that even if you have only one meta description in your source code, another one may be temporarily inserted by: - Google Tag Manager (GTM) or other tag management systems firing meta tags dynamically - SEO plugins (e.g. Yoast, Rank Math) that output duplicate tags during certain page states - A/B testing tools or personalisation scripts that inject additional head elements - Caching layers serving a stale or partial version of your page at crawl time Similarly, Too Many External Links flags can be triggered by dynamically loaded widgets, social embeds, ad scripts, or footer/header includes that add outbound links to the rendered DOM — none of which you added manually to your page content. 🔎 How to Investigate the Flag 1. Go to Left sidebar → OTTO SEO → Site Audit → Page Explorer and search for the flagged URL. 2. Open the page details and review the meta tags and links sections to see exactly what OTTO detected at crawl time. 3. Compare this against your raw HTML source (right-click the live page → View Page Source) to identify any discrepancies. 4. Check for active GTM tags, SEO plugins, or third-party scripts that may be injecting extra meta tags or links into the rendered page. 5. If you identify a script or plugin as the cause, disable or reconfigure it, then trigger a fresh crawl (see next section). 🔄 Will These Flags Clear After the Next Crawl? Yes — in most cases, once the underlying cause is resolved, the flags will clear automatically after OTTO re-crawls the affected page. To trigger a fresh crawl and re-evaluate the flags: 1. Navigate to Left sidebar → OTTO SEO → All Sites and select your project card. 2. Open the Left sidebar → OTTO SEO → Site Audit → Crawl Monitoring section for your site. 3. Initiate a new crawl for the affected URL or run a full site re-crawl. 4. Once the crawl completes, return to Left sidebar → OTTO SEO → Overview or Left sidebar → OTTO SEO → All Sites (SEO Automation) → Select your project → Tasks to confirm the flags have been resolved. If the root cause (e.g. a misconfigured plugin or tag) has not been removed, the flags will reappear after each crawl. Make sure to address the source of the duplicate tags or injected links before re-crawling. ✅ Quick Checklist to Resolve False Positives - Audit active GTM container tags for any that write to the <head> section - Check your CMS SEO plugin settings for duplicate meta description outputs - Review third-party widgets and social embeds that may add external links to the rendered DOM - Clear your site's cache before triggering a new OTTO crawl - Use your browser's Inspect Element (not View Source) to check the fully rendered DOM for duplicate tags - After fixes are applied, re-crawl via Left sidebar → OTTO SEO → Site Audit → Crawl Monitoring and verify results in Left sidebar → OTTO SEO → All Sites (SEO Automation) → Select your project → Tasks 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team. Additional Notes Flags clear automatically on the next scheduled weekly analysis. Triggering a manual recrawl does NOT refresh Site Audit flags — it updates other data points but does not re-run the full audit analysis. Only the weekly analysis cycle clears these flags.

⚠️ OTTO and Paginated Archive Pages Limitation

🔍 Overview When you deploy OTTO across your WordPress site, you may notice that canonical tags are not applied to paginated archive pages such as /blog/2/, /blog/3/, or similar numbered URL paths. This is intentional behavior, not a deployment failure. This article explains why OTTO skips these pages and what your options are. 📄 What Are Paginated Archive Pages? Paginated archive pages are automatically generated by WordPress when your blog or post archive spans multiple pages. They follow a pattern like: - /blog/ — the root archive page (page 1) - /blog/2/ — page 2 of the archive - /blog/3/ — page 3 of the archive These pages are distinct from individual posts, category pages, or static pages, and they are handled differently by OTTO during deployment. ⚙️ Why OTTO Skips These Pages OTTO intentionally excludes paginated archive pages from canonical tag deployment to prevent a known conflict with Divi's pagination JavaScript. Here is what happens when OTTO attempts to inject canonical tags on these pages: 1. OTTO inserts its canonical tag module into the page's module sequence in the WordPress head. 2. This insertion shifts the numbering of existing modules on the page. 3. Divi's pagination JavaScript relies on fixed module numbers to function correctly. 4. The numbering shift causes Divi's pagination to break, resulting in non-functional page navigation for site visitors. To protect your site's user experience and prevent pagination from breaking, OTTO skips canonical tag injection on all paginated archive pages. This limitation is tracked internally as WP-315. ✅ What OTTO Does Cover OTTO successfully deploys canonical tags on all other supported page types, including: - Individual blog posts and pages - The root archive page (/blog/ or equivalent) - Category and tag archive pages (non-paginated) - Product pages and other custom post types - Homepage and static landing pages 🛠️ How to Manage Canonicals on Paginated Archive Pages Because OTTO does not write canonical tags to paginated archive pages, you have two recommended options for handling these URLs: - Use your SEO plugin directly: If you are running Yoast SEO, Rank Math, or another SEO plugin, you can configure canonical tag behavior for paginated archives from within that plugin's settings. Most plugins handle paginated archive canonicals automatically by default. - Leave the default browser canonical: WordPress and most themes output a default canonical tag for paginated archive pages that points back to the correct URL. If you have not customized these pages, the default behavior is typically acceptable for SEO purposes. You do not need to take any action to fix a deployment error. OTTO has not failed on these pages — it has skipped them on purpose. 🔎 How to Confirm This Is the Expected Behavior To verify that OTTO's skipping behavior is the cause and not an unrelated issue, follow these steps: 1. Go to OTTO SEO in the left sidebar of your Search Atlas dashboard. 2. Open your connected site and navigate to the OTTO deployment report for your site. 3. Search for the paginated archive URL (for example, /blog/2/). 4. If the URL appears with a skipped or not applicable status rather than a failure status, OTTO has correctly identified and excluded it per this limitation. If the URL shows an unexpected error status unrelated to skipping, that may indicate a separate issue worth investigating. ❓ Frequently Asked Questions Will this limitation affect my SEO? In most cases, no. Paginated archive pages carry relatively low individual SEO value. Search engines generally handle paginated archives well when standard WordPress or plugin-generated canonical tags are in place. Does this apply to all themes, or only Divi? The confirmed conflict is specific to Divi and its pagination JavaScript. However, OTTO applies this skip rule to all paginated archive pages as a precautionary measure to avoid similar conflicts with other themes that use module-dependent JavaScript. Will OTTO ever support paginated archive pages? This is a known limitation tracked under WP-315. Our engineering team is aware of it and is evaluating solutions. We will update this article when support is added. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Reduce OTTO's Tracked Page Count Effectively

🔍 Why OTTO Still Tracks Pages After Noindex or Robots.txt Changes A common misconception is that adding noindex tags or robots.txt blocks will reduce the number of pages OTTO tracks. These directives tell search engines to ignore or skip certain pages — but they do not stop OTTO from counting a URL it has already successfully crawled. OTTO tracks every URL it can reach during a crawl, regardless of whether those pages are marked noindex or blocked for search engines. The tracked-page count reflects OTTO's crawl scope, not your site's indexability in Google or Bing. This means you can have a site with 922 tracked pages where hundreds of those pages carry noindex tags — OTTO will still count all 922 because it crawled them successfully. 📋 What Counts as a Tracked Page OTTO adds a URL to its tracked-page count when all of the following are true: - The URL was discovered during a crawl (via internal links, sitemaps, or pagination). - The server returned a successful response (typically a 200 status code). - The URL was not excluded through OTTO's own exclusion settings before the crawl ran. Noindex meta tags, X-Robots-Tag headers, and robots.txt disallow rules are not evaluated by OTTO when deciding whether to count a page. They are signals for search engine crawlers only. ⚙️ How to Reduce Your Tracked Page Count To bring your tracked-page count down, you need to reduce the number of URLs OTTO discovers and counts during its crawl. The key approaches are lowering the crawl limit and excluding specific URL patterns from OTTO's crawl scope — for example, paginated URLs, tag archives, or filtered product pages that do not need to be tracked. These exclusions are the URL Exclusion conditions in your project's OTTO SEO Settings (open the project at /seo-automation-v3 and click the Autopilot / Smart Crawl card), and they should be configured before the crawl runs. Applying noindex or robots.txt changes after pages have already been crawled will not retroactively remove them from the tracked count — noindex tags never exclude a page from OTTO, and robots.txt is only honored if Crawl Criteria is set to Respect robots.txt in the same settings modal. 🔄 When to Contact Support If your tracked-page count does not decrease after configuring URL Exclusion conditions and re-running the crawl, please reach out to our support team via the chat icon in your dashboard. We can review your specific configuration and guide you through the correct steps to reach your target page count.

↩️ Undo OTTO H1 and H2 Header Changes

🔍 Overview OTTO SEO can automatically deploy optimised H1 and H2 headings to your pages. If you want to revert those changes — or if your account displays a no connect to CMS warning even though your integration appears connected — this article explains what to expect and how to get help. ⚠️ Understanding the 'No Connect to CMS' Warning This status message may appear after OTTO deploys or modifies headings on your pages. If you see it, wait two to three minutes and refresh the page — in many cases it will clear on its own. If the warning persists after refreshing, please contact our support team for assistance, as resolving a persistent CMS connection error may require agent intervention. ↩️ Reverting OTTO H1 and H2 Heading Changes Reverting H1 or H2 headings deployed by OTTO SEO requires locating the specific heading change within your OTTO project and using the undo or revert control associated with it. Because the exact location of these controls can vary depending on your account version, the steps below describe the general approach — if what you see does not match, our support team can guide you through the exact flow for your account. To attempt to revert a heading change: 1. Open your OTTO project for the relevant site in your Search Atlas account. 2. Locate the page whose heading you want to revert within the project. 3. Find the heading change associated with that page and look for an option to undo or revert it. 4. Confirm the action if prompted, then allow a few minutes for OTTO to re-sync with your CMS. A temporary no connect to CMS status during this period is expected and should clear on its own. If you are unable to locate the undo option, or if the change is not listed in your project view, please contact our support team directly — this is a known gap where agent assistance is required to complete the revert on your behalf. 📋 What to Have Ready When Contacting Support If you need agent assistance to revert heading changes or resolve a persistent CMS connection error, please have the following information ready to share: - The name of your OTTO project or connected site - The exact URL(s) of the page(s) whose headings you want to revert - Whether the change affected the H1, H2, or both - The exact error message or status displayed in your account (e.g. the full text of the 'no connect to CMS' warning) - A screenshot of the current state of the page or heading change in your account If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 How to Exclude Pages from OTTO Crawls and Manage SEO Health Score Volatility

🧭 Overview When OTTO crawls your website, it scans every accessible page by default — including template pages, thank-you pages, tag archives, and other low-value URLs that you may not want audited. This can lead to two common frustrations: unexpected credit consumption and SEO Health Score volatility caused by issues surfacing on pages you never intended to optimize. This article explains how page exclusions work, how to configure them correctly, and what to expect from your SEO Health Score after making fixes. 🤔 Why Does My SEO Health Score Show More Issues After Fixing Them? Your SEO Health Score is recalculated every time OTTO runs a new crawl. If your score drops or new issues appear after a fix, there are a few common reasons: - New pages were discovered: Each crawl may find additional URLs — such as paginated pages, filtered product pages, or auto-generated tag archives — that were not part of the previous scan. These newly discovered pages contribute new issues to your score. - Template-level issues propagate widely: A single issue on a template (for example, a missing meta description on a category page template) can generate hundreds of individual issue instances, one per page that uses that template. Fixing one instance does not resolve the others. - Recrawl after deployment: If you published fixes and triggered a new scan before the changes fully propagated (such as a caching delay), OTTO may still detect the old state on some pages. - Dynamic content changes: Pages with dynamic titles, descriptions, or structured data can shift between crawls if the underlying content or database values changed. The most effective way to stabilize your SEO Health Score is to exclude pages that are not part of your core SEO strategy before running audits, so the score only reflects URLs you actively want to optimize. 📋 What Types of Pages Should Be Excluded? Not every page on your website deserves to be audited. Consider excluding the following page types to keep your audits focused and your credit usage efficient: - Template and archive pages: Tag archives, category index pages, author pages, and date-based archive URLs that are not individually optimized. - Utility and system pages: Thank-you pages, order confirmation pages, login and logout pages, cart and checkout pages. - Paginated URLs: Pages like /blog/page/2/ or /?page=3 that duplicate content from the primary page. - Parameter-based URLs: Filtered or sorted views such as /products?color=blue&sort=asc that are dynamically generated and not independently meaningful. - Staging or development paths: Any URL patterns that belong to test environments or internal tools not intended for public search visibility. ⚙️ How to Configure Page Exclusions in OTTO Follow these steps to exclude specific pages or URL patterns from OTTO's crawl and audits: 1. Log in to your Search Atlas account and navigate to OTTO SEO in the left-hand sidebar, then open SEO Automation. 2. Select the project (website) you want to configure. 3. At the top of the project overview, click the Autopilot / Smart Crawl card to open the OTTO SEO Settings modal. You can also reach it from the All Sites table by clicking the Smart Crawl status text on your site's card. 4. Scroll to URL Exclusion conditions and click + Add condition. 5. Set the condition to Exclude all URLs that Contains or Start With the text you want to skip: - Contains /thank-you/ to exclude every page with that path. - Start With /tag/ to exclude all URLs that begin with that string, such as all tag archive pages. - Contains ?page= to exclude paginated or filtered URLs that share a common parameter. 6. Click Update Settings. 7. Trigger a new crawl so OTTO re-audits the site with the exclusions applied. Your SEO Health Score will be recalculated based only on the pages that remain in scope. Once exclusions are saved, OTTO will skip the matching URLs in all subsequent crawls, which reduces credit consumption and prevents low-value pages from affecting your SEO Health Score. 💡 Tips for Maintaining a Stable SEO Health Score - Set exclusions before your first full crawl on a new project whenever possible, so your baseline score is clean from the start. - Review newly discovered URLs after each crawl by checking the full URL list in your audit results. If unexpected page types appear, add their patterns to your exclusion list. - Fix template-level issues at the source — correcting a meta description or title tag in your CMS template will resolve the issue across all pages using that template in a single fix, rather than page by page. - Allow caching to clear before triggering a re-crawl after deploying fixes, so OTTO picks up the updated page state accurately. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team. Additional Notes Rule updates — Search Atlas periodically refines its SEO audit rules, which can surface issues that were previously uncategorized. Also notes: fixing one high-impact template issue can resolve hundreds of individual instances at once.

🧹 Remove OTTO-Injected Hidden NLP Modules Per Page

🔍 What Are OTTO's Hidden NLP Modules? When OTTO processes a page, it can inject client-side output modules into your front-end HTML. These modules are rendered as display:none containers or JSON-LD script blocks, meaning they are invisible to visitors but present in the page source. They are used by OTTO to deliver SEO enhancements such as internal linking suggestions and heading optimizations. The three modules most commonly found on homepages are: - otto-inlinks-module — Powers OTTO's Internal Linking feature. Injects anchor and link data as a hidden container in the page HTML. - otto-missing-headings-module — Powers OTTO's Heading Optimizations feature. Injects suggested heading structures as a hidden container. - Homepage Missing Keywords module — Injects NLP-derived keyword targets and related terms (including semantically associated terms) as a JSON-LD block to support on-page optimization signals. If you are seeing unexpected keyword content — such as unrelated terms like duck, mallard, or call duck — in your homepage source code, this is almost always coming from the Homepage Missing Keywords module. OTTO's NLP model may have associated these terms with your target keywords through semantic clustering. The content is hidden from users but is present in the raw HTML. ⚠️ This Is Not a Deployment Bug These modules are not SEO fixes deployed through OTTO's Deployments queue. They are generated client-side by OTTO's automation layer on a per-page basis. You cannot remove them by undeploying a fix from the Deployments list. Attempting to do so will have no effect on the injected module content. The correct approach is to have the specific module deactivated for the affected page. If you need these modules removed from your homepage, please reach out to our support team via the chat icon in your dashboard so they can remove the hidden OTTO-injected NLP keyword modules on your homepage directly. 🗺️ How to Get This Resolved Because the controls for deactivating individual per-page modules may vary depending on your OTTO configuration, the fastest path to resolution is to contact our support team. When reaching out, please include: - The URL of the affected page (e.g. your homepage) - The specific module or content you want removed (e.g. unexpected keywords in JSON-LD, hidden heading containers) - A copy or screenshot of the unexpected source code if possible Our team can remove the hidden OTTO-injected NLP keyword modules on your homepage without affecting OTTO's activity on your other pages or disabling OTTO globally. If you need help with this, please use the chat icon in your Search Atlas dashboard to contact our support team and we will take care of it for you.

📊 Diagnosing Stalled Holistic SEO Pillar Scores

🔍 Why Your Pillar Scores May Not Be Moving Deploying OTTO recommendations is the right first step, but pillar scores won't improve unless the right types of issues are resolved on the right pages. Each of the four Holistic SEO Pillars — Content, Authority, Technical, and UX Signals — is fed by a distinct set of OTTO issue categories. Fixing issues that do not map to the lagging pillar, or fixing low-impact pages, will have little visible effect on your scores. 🗂️ Understanding Pillar Scores and OTTO Issue Categories Each of the four Holistic SEO Pillars is influenced by different types of issues surfaced in OTTO. In general terms: - Content Score — is affected by on-page content issues such as missing or duplicate metadata, heading structure problems, thin content, and internal linking gaps. - Authority Score — is affected by issues related to your site's backlink profile and external link quality. - Technical Score — is affected by crawlability and indexation issues, broken links, redirect chains, sitemap errors, canonical conflicts, and structured data problems. - UX Signals Score — is affected by page experience issues such as Core Web Vitals failures, mobile usability errors, and image optimization problems that impact load performance. Because the exact issue subcategories and their pillar assignments can vary based on your site's configuration and the version of OTTO you are using, the most reliable way to identify which open issues are suppressing a specific pillar score is to contact our support team directly. A teammate can review your account, confirm which issue types map to the stalled pillar, and advise on prioritization. 📋 What to Have Ready When You Escalate To help our team diagnose your stalled pillar score as quickly as possible, please have the following information ready: - The name of the project affected and the domain it is connected to. - Which specific pillar score is stalled (Content, Authority, Technical, or UX Signals) and approximately how long it has been unchanged. - Whether you have recently deployed OTTO recommendations and, if so, which issue categories those recommendations belonged to. - Any error messages or warnings visible in your OTTO dashboard related to the affected pillar. - The timestamp of your most recent deployment, so the team can check whether a score recalculation has been triggered. Providing this detail upfront will allow the team to identify the root cause without needing to ask follow-up questions, and get you to a resolution faster. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔁 Fix Duplicate Meta Descriptions on Your Site

🧩 Why Duplicate Meta Descriptions Happen Duplicate meta descriptions occur when more than one tool or source writes a meta description to the same page at the same time. Search Atlas gives you several ways to set meta descriptions, and if more than one is active simultaneously, your site may display multiple conflicting tags. The three most common sources of conflict are: - OTTO SEO — Search Atlas's AI automation engine can deploy meta descriptions directly to your site. - Search Atlas sidebar (manual entry) — Meta descriptions entered manually through the on-page tools inside Search Atlas. - Third-party SEO plugins — Plugins installed on your site such as SmartCrawl, Yoast SEO, Rank Math, or All in One SEO may also be writing meta descriptions independently. When two or more of these sources are active for the same page, search engines and SEO audit tools will detect multiple meta description tags in the page's HTML — which is exactly what you are seeing. 🔍 How to Identify Which Sources Are Conflicting Before making any changes, confirm which tools are currently writing meta descriptions to the affected pages: 1. Open your browser and navigate to the affected page on your live site. 2. Right-click anywhere on the page and select View Page Source. 3. Press Ctrl + F (or Cmd + F on Mac) and search for meta name="description". 4. Count how many instances appear. If you see more than one, note the content of each tag so you can trace which tool produced it. 5. Log in to your WordPress dashboard (or your CMS) and check which SEO plugins are installed and active. 🛠️ How to Fix Duplicate Meta Descriptions The fix is straightforward: make sure only one source is responsible for writing meta descriptions. Follow the steps below based on your setup. ⚙️ Step 1 — Choose Your Preferred Meta Description Source Decide which single tool will manage your meta descriptions going forward. Search Atlas recommends using OTTO SEO for automated, AI-optimised descriptions, or entering them manually through Search Atlas if you prefer full manual control. Only one approach should be active at a time. 🤖 Step 2 — Check and Manage OTTO Deployments 1. In the left sidebar, navigate to OTTO SEO → All Sites (SEO Automation). 2. Select the site that is showing duplicate meta descriptions. 3. Review the list of deployed actions and look for any meta description tasks that have been applied to the affected pages. 4. If you do not want OTTO to manage meta descriptions for specific pages, disable or roll back those individual deployments from within the OTTO task list. 5. If you do want OTTO to manage meta descriptions, leave these deployments active and proceed to disable all other sources in the steps below. ✏️ Step 3 — Remove Manual Entries in Search Atlas 1. In the left sidebar, go to Content, then select On-Page Audit. 2. Open the audit for the affected page. 3. Check whether a meta description has been entered manually in the sidebar panel. 4. If OTTO is handling meta descriptions for this page, clear the manual field so it is blank. This prevents Search Atlas from writing a second, separate tag. 🔌 Step 4 — Disable Meta Descriptions in Third-Party Plugins If you have a third-party SEO plugin installed (such as SmartCrawl, Yoast SEO, Rank Math, or All in One SEO), you must turn off its meta description output for the affected pages — or disable it site-wide if Search Atlas is your primary SEO tool. - SmartCrawl: Go to SmartCrawl → Sitemap & Meta in your WordPress dashboard, then navigate to the Meta Tags section and disable meta description output. - Yoast SEO: Open the page in the WordPress editor, scroll to the Yoast SEO meta box, and clear the meta description field. To disable it globally, go to Yoast SEO → Search Appearance and remove template tags from the meta description field. - Rank Math: Open the page editor, expand the Rank Math panel, and clear the meta description field. - All in One SEO: Open the page editor, scroll to the AIOSEO settings, and clear the meta description field. If you are unsure which plugin is generating the conflicting tag, deactivate plugins one at a time and check the page source after each deactivation until the duplicate disappears. ✅ Step 5 — Verify the Fix 1. After making your changes, revisit your live page and view the page source again. 2. Search for meta name="description" and confirm only one instance appears. 3. You can also use the Content → On-Page Audit tool in Search Atlas to re-scan the page and confirm the duplicate issue is resolved. 💡 Best Practices to Prevent Duplicates in Future - Use only one tool to manage meta descriptions across your site — either OTTO, the Search Atlas manual workflow, or a third-party plugin, never a combination. - When activating OTTO on a site that already has a third-party SEO plugin, always disable the plugin's meta description output first. - After any major plugin installation or update, re-audit your key pages to check for newly introduced duplicates. - Use the Content → Meta Generator tool in Search Atlas to create optimised meta descriptions, then deploy them through a single consistent channel. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Removing Hardcoded Schemas from Shopify in OTTO

📌 What This Message Means If OTTO reports that it cannot remove a number of hardcoded schemas (for example, 537), it is letting you know that those schemas live directly inside your Shopify theme or app code, not inside OTTO. Because OTTO did not create them, it cannot delete them for you. This article explains what that means in plain language and shows you how to clean them up. 🧩 What a Hardcoded Schema Is A schema is structured data that helps search engines understand your page (for example, product details, reviews, or breadcrumbs). OTTO can add and manage schema for you automatically. A hardcoded schema is schema that was added directly into your Shopify store's theme files, a theme app, or a third-party plugin before OTTO was installed. It is fixed in place inside the code, which is why it is called "hardcoded." ❓ Why OTTO Cannot Remove Them OTTO only controls the schema it generates and injects through your OTTO Pixel. It does not have permission to edit your Shopify theme files or other apps. When OTTO finds hardcoded schemas, it flags them so you are aware of them, but it leaves the removal to you. This protects your store from unexpected changes to code OTTO does not own. ⚠️ Why Duplicate Schemas Matter When hardcoded schemas and OTTO schemas both exist on the same page, search engines can see duplicate or conflicting data. This can: - Confuse search engines about which information is correct - Trigger schema validation warnings - Reduce the chance of earning rich results Removing the old hardcoded schemas lets OTTO manage your structured data cleanly from one place. 🔍 How to Find the Hardcoded Schemas Use the count OTTO gives you as your guide, then locate the source: 1. Open a sample page from your store in a browser. 2. Right-click and choose View Page Source. 3. Search the code for application/ld+json or the word schema. 4. Note where the schema appears so you can identify its source (theme file, theme section, or an installed app). 🛠️ How to Remove Them in Shopify Most hardcoded schemas come from one of three places. Work through these in order: 1. Theme files: In Shopify, go to Online Store > Themes, click Edit code, and search your template and section files (often theme.liquid or product templates) for the schema markup. Remove or comment out the hardcoded blocks. 2. SEO or schema apps: If a third-party app is injecting schema, open that app's settings and disable its structured data feature, or uninstall the app if it is no longer needed. 3. Page or product content: Check for schema pasted directly into product descriptions or custom HTML blocks, and remove it there. Always create a backup of your theme before editing code. In Shopify, duplicate your theme first so you can restore it if needed. ✅ How to Confirm It Worked 1. After editing, reload an affected page and check the source code again to confirm the hardcoded schema is gone. 2. Run the page through a structured data testing tool to confirm only your intended schema remains. 3. Return to OTTO and re-scan your site. The hardcoded schema count should drop. 💡 Helpful Tips - Work on one schema type at a time so changes are easy to track. - Keep your duplicated theme until you have confirmed everything looks correct. - If a developer built your theme, share the schema locations with them so they can remove the markup safely. - Allow time for search engines to re-crawl your pages after the cleanup. 💬 Need More Help Cleaning up hardcoded schemas can take a few steps, but it keeps your structured data accurate and lets OTTO manage it for you going forward. If you need further assistance, click the chat icon in the bottom-right corner of the platform and type "Human Teammate" to start a live chat with a member of our team. Additional Notes Common sources include: Your Shopify theme (ships with built-in schema for products, collections, articles), Third-party apps (SEO, review, rich-snippet apps), Custom development (code added manually by a developer/agency). Also: Check theme files via Online Store > Themes > Edit code; schema usually found in template/section files.

📊 Why Your Content Score Isn't Improving in OTTO

Your content score measures the on-page optimization of your existing pages, not how much new content you publish. To raise it, approve and deploy the pending OTTO recommendations in your dashboard. 📊 What the Content Score Measures The content score reflects how many of OTTO's content recommendations you have approved and deployed across your site. It tracks on-page optimization fixes, such as headings, meta titles, meta descriptions, canonical links, and meta keywords on your current pages. Because the score is tied to these recommendations, it stays flat until you act on them. A score that holds at the same number means those fixes are still waiting in your dashboard. 🆕 Why Publishing New Articles Doesn't Move the Content Score Publishing new content builds topical coverage, which is how broadly your site covers the subjects your audience searches for. New articles do not change the content score. The content score measures optimization of your existing pages. New posts add coverage, but they do not approve or deploy the on-page fixes the score is built from, so the number stays the same no matter how many you publish. ✅ How to Increase Your Content Score To move the score, work through the pending OTTO recommendations in your dashboard and deploy them. Follow these steps: 1. Open your OTTO dashboard. 2. Locate the pending content recommendations, grouped by type. 3. Review and approve the heading optimizations. 4. Approve the meta titles and meta descriptions. 5. Approve the canonical link fixes. 6. Approve the meta keywords. 7. Deploy the approved recommendations to your site. As each batch deploys, your content score rises to reflect the newly optimized pages. 📋 Example: Pending Recommendations That Hold a Score Down A score can stay flat when large volumes of recommendations remain pending. For example, an account holding at a score of 33 had the following waiting in the dashboard: - 530 of 553 heading optimizations pending. - 199 meta titles and descriptions pending. - 39 canonical links pending. - 199 meta keywords pending. Clearing these pending items is exactly what raises the score. 🛠️ If Your Content Score Still Won't Move If the score stays the same after you deploy recommendations, check the following: - Confirm the recommendations show a deployed status, not just approved. - Make sure you are reviewing the pages tied to OTTO, since the score measures existing optimized pages. - Allow time for deployed changes to register in the dashboard. Once your deployed recommendations register, the content score reflects the improved on-page optimization. 🔍 Why Your Content Score Might Stay Stuck Even With Recommendations Sometimes the score stalls for reasons beyond pending recommendations. If you have deployed your fixes and the number still won't budge, check for these issues: - OTTO is still processing. If your OTTO dashboard shows 0 total pages or no recommendations appear, your project may still be processing. Wait a few minutes and refresh, or contact support if the issue persists. - Inactive OTTO pixel. Confirm the OTTO pixel is installed and active on your site, since deploying recommendations relies on it. - Quota or crawl budget exhaustion. If you have used up your quota or crawl budget, new pages and recommendations cannot be processed until it refreshes. - Slow site performance. If you don't see any pending recommendations, your site may be loading too slowly for our crawler to scan it properly. Check site performance and contact your hosting provider if needed. 🎯 You now know that your content score tracks deployed on-page fixes, not new articles. Open your OTTO dashboard, approve and deploy the pending heading, meta, and canonical recommendations, and watch your content score climb.

🚩 OTTO False Positives: Why Fixed Issues Still Appear as Flags

🔄 Why OTTO still shows issues you've already fixed OTTO analyzes your site on a weekly crawl cycle. The flags and recommendations you see are based on the data from the most recent crawl. If you fixed an issue today, it will not disappear from OTTO until the next weekly analysis runs. ⚠️ Common false positive scenarios - "Multiple Meta Descriptions" flagged on pages you've already corrected - "Too Many External Links" on pages you've edited - Missing H1 or title tag errors on pages that now have them - Schema markup warnings on pages where you've deployed correct schema - Missing alt tag or "image not in NextGen/modern format" warnings on images that are actually correct — this can happen when the crawler reaches an authenticated, cached, or origin-layer version of the page instead of the public view (see Known issues below) - Redirect-related false positives, such as a page flagged as redirecting only because of trailing-slash differences (for example example.com/ vs example.com) In all these cases, the flag reflects stale crawl data, not your current site state. ✅ What to do 1. Wait for the next weekly analysis — if you've fixed the issue, it will automatically disappear after OTTO's next crawl 2. Trigger a manual recrawl — if your plan supports it, you can request a fresh crawl from OTTO SEO → Site Audit → Overview (Website Overview) using the 'Recrawl Site' button 3. Don't re-fix what you've already fixed — making additional changes based on stale flags can create new problems 🔍 How to verify your fix is live before the next crawl Use Google Search Console's URL Inspection Tool to fetch and render your page as Google sees it. You can also open the affected page in an incognito/unauthenticated browser window. OTTO audits the public, anonymous version of your page, so the incognito view is the closest match to what the crawler should see. If the page looks correct in incognito but OTTO still flags it, the flag is most likely a false positive rather than a real issue. 🛠️ Known issues we're tracking - Alt tag and modern-image-format false positives: We have identified a bug where the audit can incorrectly flag images as missing alt tags or as not being in NextGen/modern format (such as WebP/AVIF) even when they are correctly implemented on the public page. This occurs when the crawler accesses a non-public variant of the page; the incognito view shows the correct state. A fix is currently awaiting release. - Redirect false positives: Several redirect-handling false positives — including pages flagged as redirecting due to trailing-slash normalization and lowercase-URL checks incorrectly flagging the domain or scheme — have been fixed and released.

📶 UX Signals: What OTTO Can and Cannot Do

📌 What Are UX Signals? UX signals are behavioral metrics that indicate how visitors experience your website. Search engines use these signals as quality indicators when ranking pages. Common UX signals include: - Page load speed — how quickly your pages render for users - Core Web Vitals — Google's set of performance metrics (LCP, INP, CLS) - Mobile usability — how well your site functions on mobile devices - Bounce rate and dwell time — whether visitors stay and engage with your content - Interactivity — how smoothly users can click, scroll, and navigate 🤖 What OTTO Does and Does Not Optimize OTTO is Search Atlas's OTTO SEO automation engine. It is designed to handle on-page and technical SEO tasks that can be managed through content and metadata — not through changes to your website's underlying code, server configuration, or design. OTTO can optimize: - Title tags, meta descriptions, and heading structure - Internal linking and anchor text - Schema markup and structured data - Content gaps and keyword targeting - Image alt text - Canonical tags and robots directives OTTO cannot optimize: - Page load speed or server response times - Core Web Vitals (LCP, INP, CLS scores) - JavaScript rendering performance - Mobile layout and responsive design - Font loading, image compression pipelines, or CSS efficiency - Hosting infrastructure or CDN configuration UX signal improvements require changes at the website level — in your code, design, hosting, or development stack. These fall outside OTTO's automation scope and must be addressed directly on your site or with the help of a developer. 🔍 How to Find Your Current UX Signal Scores To review your site's UX signals inside Search Atlas: 1. In the left sidebar, navigate to OTTO SEO → All Sites (SEO Automation). 2. Select your project and open the site audit or performance overview. 3. Look for Core Web Vitals, page speed scores, and mobile usability flags in the audit results. 4. Each flagged issue will include a description of what is underperforming. You can also use Google's free tools — PageSpeed Insights and Google Search Console — to get a detailed breakdown of your Core Web Vitals and mobile usability issues alongside field data from real users. 🛠️ How to Improve Your UX Signals The following changes are the most impactful for improving UX signals and must be implemented at the website or hosting level: Improve page load speed: - Compress and serve images in next-gen formats (WebP, AVIF) - Enable browser caching and GZIP or Brotli compression on your server - Minify CSS, JavaScript, and HTML files - Use a content delivery network (CDN) to reduce latency for global visitors Improve Core Web Vitals: - LCP (Largest Contentful Paint): Optimize your largest above-the-fold element — usually a hero image or heading. Preload critical resources and eliminate render-blocking scripts. - INP (Interaction to Next Paint): Reduce JavaScript execution time and break up long tasks that block the main thread. - CLS (Cumulative Layout Shift): Set explicit width and height attributes on images and embeds so the browser reserves space before they load. Improve mobile usability: - Use a responsive design framework and test all pages on multiple screen sizes - Ensure tap targets (buttons, links) are large enough and spaced apart - Avoid intrusive pop-ups or interstitials on mobile Improve engagement signals: - Make sure your page content matches the intent of the search query driving traffic - Improve readability with clear headings, short paragraphs, and relevant visuals - Reduce time-to-first-meaningful-content so visitors see value immediately ✅ Recommended Workflow 1. Run a full site audit in Search Atlas (OTTO SEO → All Sites (SEO Automation)) to identify specific UX signal issues. 2. Cross-reference findings with PageSpeed Insights for lab and field data. 3. Prioritize fixes by impact — Core Web Vitals failures tend to have the largest ranking effect. 4. Work with your developer or hosting provider to implement the required changes. 5. Re-run the audit after changes go live to confirm improvements. 6. Let OTTO handle all on-page SEO tasks in parallel so both tracks progress simultaneously. 💬 Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛡️ OTTO Hidden Modules: SEO Safety and Best Practices

🔍 What Are the NLP Keywords and Missing Keywords Modules? When OTTO is active on a page, it may inject two hidden on-page modules to strengthen your content's semantic relevance: - NLP Keywords Module (Meta Keywords Issues fix): Inserts a hidden block of semantically relevant terms that help search engines understand your page's topical context. This addresses gaps identified in OTTO's Meta Keywords Issues audit check. - Missing Keywords Module (Missing Keywords Issues fix): Injects additional keyword phrases that were detected as absent from your page content. This addresses OTTO's Missing Keywords Issues audit check. Both modules are rendered in a visually hidden format — they are not visible to human visitors but are readable by search engine crawlers. Their purpose is to reinforce topical signals without requiring manual edits to your CMS content. ⚠️ Do Hidden Keyword Modules Cause SEO Harm? This is a common concern, and it deserves a direct answer. OTTO's hidden modules are designed to be crawler-safe. They use standard HTML that search engines can read, and the keywords injected are directly derived from your page's existing topic and target terms — not unrelated or excessive phrases. However, there are situations where you should review or disable these modules: - Your page already has strong keyword coverage and adding more terms could create an unnaturally high keyword density. - Your site operates in a niche where any form of hidden content could attract manual review scrutiny. - You have manually audited your page and confirmed the injected terms are redundant or mismatched. Keyword stuffing risk: OTTO limits injected terms to those identified in its audit, so accidental over-optimisation is uncommon. That said, if your page content already covers the flagged keywords naturally, disabling the module is a safe and recommended choice rather than duplicating signals. ✏️ How to Manage an OTTO-Injected Module If you want to review or disable an active NLP Keywords or Missing Keywords module, navigate to the OTTO section of your Search Atlas dashboard. From there, locate the affected site and the specific page where the fix is applied. You should be able to see the active fixes associated with that page — look for entries corresponding to Meta Keywords Issues or Missing Keywords Issues. You can turn off an individual fix from within that page's fix list if you determine the injected content is no longer needed or is causing unwanted keyword density. If you are unsure where to find these controls in your current dashboard view, or if the option to disable a specific fix is not visible to you, please reach out to our support team for guided assistance — they can walk you through the exact steps for your account. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Add a Domain to OTTO SEO via Agent Chat

Most websites can be added to OTTO SEO in just a few clicks. Occasionally, though, a domain returns a persistent Invalid URL error that does not clear after the usual fixes. When this happens, our agent chat workaround lets our team add the domain manually so you can keep moving. This guide walks you through the standard setup, quick troubleshooting, and how to request the workaround. ​ 🚀 Standard Way to Add a Domain​ Before using the workaround, try the normal flow first, as it resolves the majority of cases. 1. Open OTTO SEO → All Sites (SEO Automation) from the left-hand menu. 2. Click Add Project or Add Domain. 3. Enter your full website URL. 4. Select your platform (for example, WordPress) and follow the prompts. 5. Click Create Project to create the project.​ ⚠️ Why the Invalid URL Error Appears​ The Invalid URL error usually means the address you entered does not match the format OTTO SEO expects, or the domain cannot be verified during setup. Common causes include: - Extra characters, spaces, or trailing slashes in the URL. - Including a path or parameters instead of just the domain. - Mixing up http and https, or adding (or omitting) www incorrectly. - A redirect chain that confuses verification. - Temporary connectivity or DNS issues on the site.​ 🔍 Quick Troubleshooting Steps​ Work through these steps in order. Most Invalid URL errors clear after one of them. 1. Enter the cleanest version of your address, such as https://yourdomain.com, with no trailing slash and no extra path. 2. Try the alternate format if the first fails, for example switch between www and the non-www version. 3. Confirm your site loads normally in a browser and is not down for maintenance. 4. Check that your site does not force an unexpected redirect to another domain. 5. Refresh the page, clear your browser cache, or try a different browser, then attempt the setup again.​ 💬 Using the Agent Chat Workaround​ If the error continues after all the steps above, our team can add the domain for you manually through live chat. This is the recommended workaround for stubborn Invalid URL errors, such as the one some WordPress sites experience even after every standard troubleshooting step has been tried. 1. Click the chat icon in the bottom-right corner of the platform to start a live chat with a member of our team. 2. Let the agent know you are seeing a persistent Invalid URL error when adding a domain to OTTO SEO. 3. Provide the exact domain you want to add, written out in full. 4. Confirm the platform your site runs on, such as WordPress. 5. Share the troubleshooting steps you have already tried so the agent can skip them.​ The agent will add the domain to your OTTO SEO account on your behalf. Once it has been added, you will see the new project appear in your OTTO SEO dashboard. ✅ After Your Domain Is Added​ Once the domain is in place, you can continue your setup as normal: - Install or confirm the OTTO SEO connection on your site. - Enable the dynamic optimizations you want to run. - Review your recommendations and deploy changes from the dashboard.​ The manual workaround only affects how the domain is added. After that, every OTTO SEO feature works exactly the same as a domain added through the standard flow. In rare cases, a project added this way may at first appear incomplete or not begin processing right away — a known issue that has since been resolved. If your new project does not start processing, refresh your dashboard, and if it still does not begin, reach out via live chat so our team can confirm it is set up correctly. 📌 Helpful Tips to Avoid Future Errors​ - Always enter the root domain unless instructed otherwise. - Keep your URL free of spaces, quotes, and trailing characters. - Make sure your site is live and reachable before adding it. - If you manage multiple sites, add them one at a time to confirm each is verified.​

How to Remove OTTO-Injected Body Text from Your Website Footer

🛠️ How to Remove OTTO-Injected Body Text from Your Website Footer If unexpected text is appearing below your website footer on every page, it is likely being pushed by content entered in the Miscellaneous → Body Text field inside your OTTO project. Follow the three steps below to stop the injection and permanently remove the text. ⚠️ Version note: These steps apply to OTTO V3, the current default version. If your account shows a legacy OTTO V2 interface, contact Search Atlas support for assisted migration before proceeding. 🔴 Step 1: Disengage OTTO Go to Search Atlas → OTTO SEO and open your site's OTTO project. If you cannot locate it by name, navigate directly to the OTTO Tasks Dashboard. ▶️ Click Disengage OTTO to pause all active content injections. 🔍 If your project does not appear by site name, use the OTTO Tasks Dashboard and filter or scroll to locate the correct project. 👥 If you manage multiple sites, ensure you are looking under the correct workspace. ⚠️ Important warning: Disengaging OTTO pauses all OTTO-managed optimisations across your site — including title tags, meta descriptions, schema markup, and more — not just the body text injection. Proceed only if you are ready to temporarily remove all active OTTO deployments, or if you plan to re-engage OTTO after completing Step 3. ✅ Once disengaged, OTTO stops delivering content to your pages. New visitors will stop seeing the injected text as soon as your cache is cleared in Step 2. 🗑️ Step 2: Clear Your Site Cache Clearing your cache ensures the change takes effect immediately for all visitors. Use the method that matches your setup: 🔌 WordPress caching plugin (WP Rocket, LiteSpeed Cache, W3 Total Cache): Open the plugin settings and click Clear Cache. ☁️ Cloudflare: Go to Caching → Configuration and select Purge Everything. 🖥️ Hosting-level cache: Contact your hosting provider or use their control panel to flush the server cache. ✅ After clearing the cache, reload a page on your site and scroll to the bottom to confirm whether the injected text has disappeared. If it is gone, proceed to Step 3 to ensure it cannot return. ✏️ Step 3: Delete the Body Text from the Miscellaneous Tab Return to your OTTO project inside Search Atlas. Click the Miscellaneous tab in the left-hand navigation panel. 🔎 Locate the Body Text field and delete all content entered there. 💾 Save your changes. 🔄 You may now safely re-engage OTTO if desired. All other optimisations — title tags, meta descriptions, schema, and more — will continue to apply. Only the deleted body text will be gone, preventing the injection from reappearing if OTTO is re-engaged in the future. ✅ Verifying the Fix Visit several pages on your site and scroll to the bottom of each page. The injected text should no longer appear below the footer. 🚨 If the content is still visible after clearing your cache, contact Search Atlas support. A specialist can confirm whether the deployment rollback has been applied on the server side and push an additional correction if needed. 🌀 Website Studio users: If your site was built in Search Atlas Website Studio and the text persists even after following all three steps, a known issue (LPS-984) may require engineering intervention. Contact support directly for assistance.

⚡ Search Atlas Resolution Playbook (Action Layer)

This guide tells you exactly: - What to do - How to fix it - How to prevent it This is your execution layer. ⚡ QUICK FIX MATRIX 🧠 If AI is not working 🔴 Likely Cause Gemini quota exceeded (429) ✅ Action - Retry later - Use fallback model - Reduce request volume 📊 If data is missing 🔴 Likely Cause External service failure (SEMRush, ClickHouse) ✅ Action - Refresh data - Wait for recovery - Check service health 🔄 If tasks are stuck 🔴 Likely Cause Celery / queue issue ✅ Action - Re-trigger process - Re-run crawl - Restart workflow 🕷️ If crawl is stuck 🔴 Likely Cause Timeout on large site ✅ Action - Reset crawl - Re-run - Break into smaller batches ⚠️ If dashboard not loading 🔴 Likely Cause Database or Redis issue ✅ Action - Refresh - Retry after 30–60 seconds - Check system status 🖥️ If UI is broken 🔴 Likely Cause Frontend rendering issue ✅ Action - Hard refresh - Clear cache - Reload session 🧩 ADVANCED RESOLUTION PATTERNS 🔧 Pattern 1 — Retry with Backoff Used when: - API calls fail - External services unstable 👉 Always retry before escalating 🔄 Pattern 2 — Fallback Systems Used when: - AI model unavailable - Data provider fails 👉 Switch provider instead of blocking 🧠 Pattern 3 — Graceful Degradation Used when: - Partial data available 👉 Show partial results instead of failing ⚙️ Pattern 4 — Queue Recovery Used when: - Jobs stuck 👉 Re-trigger instead of waiting 💣 Pattern 5 — Scale Adjustment Used when: - Memory / limits hit 👉 Reduce load or increase capacity 🛡️ PREVENTION LAYER 🚨 Add Monitoring For: - DB connections > 80% - Queue depth spikes - API rate limits - AI quota usage 🔄 Always Implement: - Retry logic - Circuit breakers - Async processing - Idempotent actions 🧠 Design Principle 👉 Systems should fail gracefully, not completely 🎯 FINAL TAKEAWAY There are only 3 real failure modes: 1. System overloaded 2. Dependency unavailable 3. Process stuck 💡 Operational Insight If you fix: - Retries - Queues - Fallbacks 👉 You eliminate 80% of production issues

Fix Duplicate Meta Descriptions in OTTO SEO

When OTTO SEO and another SEO plugin are both configured to write meta descriptions on your WordPress site, your pages may render two tags simultaneously. Search engines like Google read only the first tag they encounter, making your intended description unpredictable in search results. 📋 Why This Happens OTTO SEO deploys meta descriptions through its JavaScript pixel (injected into your site's ) or the Search Atlas WordPress plugin. If a plugin such as Yoast SEO, Rank Math, or All in One SEO is also set to output a meta description, both tags appear in the rendered HTML. Because OTTO's pixel writes to the DOM after page load, the other plugin's server-rendered tag is already present in the raw HTML source — creating a true duplicate every time. 🔧 How to Fix It Choose which tool should own your meta descriptions, then follow the matching steps below. Option A: Let OTTO control meta descriptions 1. Open OTTO SEO and navigate to your project. 2. Go to On-Page fixes and confirm the meta description fix is deployed. 3. In your conflicting plugin, disable meta description output: - Yoast SEO: Go to SEO > Search Appearance and turn off meta descriptions. - Rank Math: Go to General Settings and disable the meta description field. - All in One SEO: Locate the meta description setting under General Settings and disable it. Option B: Let your existing SEO plugin control meta descriptions 1. Open OTTO SEO and navigate to your project. 2. Go to On-Page fixes and locate the meta description fix. 3. Toggle off or undeploy that specific fix so OTTO no longer writes the tag. ⚠️ Important Notes - OTTO does not automatically detect or suppress output from conflicting plugins — the duplicate must be resolved manually. - There is no built-in conflict resolution toggle inside OTTO; the fix requires disabling the duplicate source in one tool or the other. - Rank Math silent override: A known issue exists where Rank Math can silently override OTTO's meta description deployment. If the OTTO dashboard shows a status of Deployed but the wrong description still appears in your page source, Rank Math may be actively overriding OTTO's output despite the deployment indicator. In this case, you must disable the meta description field in Rank Math's General Settings (Option A, step 3) to resolve the conflict. - After making changes, use View Page Source in your browser (not the DevTools inspector) to confirm only one tag appears in the raw HTML. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🗑️ How to Clear Your Site Cache After Making Changes in Search Atlas OTTO

🗑️ How to Clear Your Site Cache After Making Changes in Search Atlas OTTO When OTTO deploys or removes content on your website, those changes do not always appear immediately for visitors. Your site's cache stores older versions of your pages and serves them to users until the cache is refreshed. Clearing your cache is a required step any time you disengage OTTO, update injected content, or troubleshoot unexpected content appearing on your site. 🤔 Why Cache Clearing Matters After OTTO Changes OTTO pushes content changes at the server and application level. However, caching layers — whether at the WordPress plugin level, the CDN level, or the hosting level — capture snapshots of your pages and continue serving those snapshots even after the underlying content has changed. ⚠️ If you skip this step, visitors (and you) may continue to see old injected content even after OTTO has been disengaged and the body text field has been cleared. Always clear cache immediately after making changes in OTTO to confirm the fix is live. 🛠️ How to Clear Your Cache by Platform ⚡ WordPress Caching Plugins ✅ WP Rocket: Log in to your WordPress dashboard, go to Settings → WP Rocket, and click the Clear Cache button at the top of the screen. You can also clear cache directly from the WordPress admin toolbar by clicking the WP Rocket icon. ✅ LiteSpeed Cache: In your WordPress dashboard, navigate to LiteSpeed Cache → Toolbox → Clean All. This purges all cached files stored by LiteSpeed on your server. ✅ W3 Total Cache: Go to Performance → Dashboard and click Empty All Caches. If you use a CDN integration within W3 Total Cache, also purge the CDN cache from the same dashboard. ✅ WP Super Cache: Navigate to Settings → WP Super Cache and click Delete Cache under the Easy tab. 🌐 Cloudflare CDN ✅ Log in to your Cloudflare account and select the domain you are working with. ✅ In the left-hand sidebar, go to Caching → Configuration. ✅ Under the Custom Purge or Purge Cache section, click Purge Everything to clear all cached assets across Cloudflare's global network. ⚠️ Important: Purging everything in Cloudflare clears all cached assets site-wide. This is the safest option when troubleshooting OTTO content injection issues, as partial purges may miss the affected pages. 🖥️ Hosting-Level Cache Many managed WordPress hosts — including WP Engine, Kinsta, Flywheel, SiteGround, and Cloudways — maintain their own server-side caching layers that operate independently of any WordPress plugin. ✅ WP Engine: In your WP Engine User Portal, go to your environment and click Purge All Caches. ✅ Kinsta: In the MyKinsta dashboard, navigate to your site, go to Tools, and click Clear Cache. ✅ SiteGround: In the SiteGround Site Tools, go to Speed → Caching and click the flush icon next to Dynamic Cache. ✅ Cloudways: In your Cloudways console, open your application and go to Application Management → Varnish. Click Purge Varnish Cache. ✅ Other hosts: If your host is not listed above, log in to your hosting control panel or contact your host's support team and ask them to flush the server-side or full-page cache for your domain. ✅ How to Confirm the Cache Has Been Cleared ✅ After purging your cache, open a new private or incognito browser window. This prevents your own browser cache from serving a stale version of the page. ✅ Navigate to several pages on your site — including the homepage, a category page, and an inner page — and scroll to the bottom of each. ✅ If the previously injected content no longer appears below the footer, the cache has been cleared successfully and the OTTO change is live. ⚠️ If the content is still visible after clearing all cache layers, contact Search Atlas support. A specialist can confirm whether the OTTO deployment rollback has been applied on the server side and push an additional correction if needed. 🔁 When Else Should You Clear Cache with OTTO? 🔄 Any time you engage or disengage OTTO on a site, clear your cache afterwards to ensure the changes propagate immediately to all visitors. 🔄 After editing content in any OTTO tab — including title tags, meta descriptions, schema markup, or the Miscellaneous body text field — clear your cache so updated deployments are reflected live. 🔄 After completing a troubleshooting session with Search Atlas support involving OTTO deployments, always perform a full cache purge as the final step before confirming the issue is resolved.

🖼️ OTTO Pending Tasks Caused by Missing Image Alt Text

When OTTO cannot access an image on your site, it cannot generate alt text — so that task stays permanently in pending status. You can resolve it manually, approve an AI-generated fix, or use Atlas Brain AI to write the alt text yourself. 🔍 Why OTTO Image Alt Text Tasks Stay in Pending Status OTTO scans your site and attempts to generate alt text automatically for every image it finds. If an image is missing — broken link, deleted file, or a URL OTTO cannot reach — there is no content to analyze. The task has nothing to act on, so it stays stuck in Pending indefinitely. This affects both the OTTO task queue and any manual deployment attempts for those specific tasks. Before writing alt text, check whether the image itself can be restored. If the file was deleted or the URL is broken, adding alt text will move the task out of pending, but your page will still be missing the image. Whenever feasible, fix the source first — re-upload the file or update the image URL — and then let OTTO re-scan. Writing alt text for a permanently missing image is a fallback, not a true fix for the page. ✅ How to Resolve Pending Image Alt Text Tasks You have three options. Choose the one that fits your workflow. Option 1: Enter alt text manually 1. Go to OTTO SEO → Overview (OTTO Grader) and open the Pending Optimizations panel. 2. Click the image alt text task you want to fix. 3. Type the alt text directly into the field provided. 4. Click Deploy to apply the change. The task moves out of pending as soon as the fix is deployed. Once deployed, the task is resolved and will not be re-flagged on the next crawl for that same image URL — unless OTTO detects a new change to the image or the alt text is removed. If the underlying image is still missing, OTTO may surface a related issue on a future scan, which is another reason to fix the image source when possible. Option 2: Approve an AI-generated fix 1. In the pending task, click the AI Fix button in the top-right corner of the task detail panel to have OTTO suggest alt text. 2. Review the generated suggestion carefully. 3. Click Approve to deploy it. OTTO will not deploy any AI-generated fix without your explicit approval — always review the suggestion before you approve. ⚠️ Check your approval settings and task history. Before approving fixes in bulk, open your OTTO settings to confirm that AI-generated changes require manual approval, and review your recent task history to make sure no AI alt text was deployed without your review. This is especially important if multiple teammates have access to the dashboard or if you are processing a large batch of pending tasks at once. Option 3: Prompt Atlas Brain AI 1. Open Atlas Brain AI from within the task panel by clicking the Atlas Brain icon. 2. Describe the image — subject, context, and any keywords you want included — and ask Atlas Brain AI to suggest alt text. 3. Copy the suggested alt text from the Atlas Brain response. 4. Paste it into the task's alt text field and click Deploy to apply the change. Atlas Brain AI is especially useful when you want more descriptive or SEO-optimized alt text than the auto-generated option provides. 🛠️ If Manual Deployment Is Not Working If clicking Deploy on a pending alt text task does nothing, check the following: - Confirm the image file is live and accessible at its URL before you attempt to deploy. - Refresh the OTTO SEO → All Sites (OTTO SEO Projects) page and try deploying the task again. - If the problem continues, contact Search Atlas support and include a screen recording of the failed deploy — this helps the team pinpoint the issue quickly. 📞 Still Stuck? Contact Support If none of the three resolution options work — for example, manual entry deploys but the task returns to pending, or Deploy consistently does nothing — this may indicate a deeper deployment issue that requires engineering review. Contact Search Atlas support with the following: - The specific task ID or URL of the affected image. - A screen recording or screenshots showing the steps you took and the failure. - A note that manual deployment is also not working, so support can escalate directly rather than asking you to retry the standard fixes. 🎯 You now know why OTTO image alt text tasks stay in pending status and have three ways to resolve them: manual entry, AI-generated fixes with approval, or Atlas Brain AI. If manual deployment is still failing after these steps, reach out to Search Atlas support with a screen recording for a faster diagnosis.

🔄 Manage, Find, and Rollback OTTO SEO Deployments

🗺️ Overview When OTTO SEO deploys changes to your WordPress site, you may need to do three things: resolve schema conflicts with plugins like Yoast or Schema Pro, find exactly which fixes were deployed, or reverse changes you no longer want. This article walks you through all three steps. ⚠️ Resolving Schema Conflicts with Yoast or Schema Pro OTTO SEO generates and injects schema markup directly into your site. If Yoast SEO or Schema Pro is also active, duplicate or conflicting schema can appear in your page source, which may confuse search engines. To resolve schema conflicts: 1. Log in to your WordPress admin panel. 2. Go to your installed plugins list and locate Yoast SEO or Schema Pro. 3. Disable the schema output from whichever plugin you want to defer. In Yoast SEO, go to Yoast SEO → Settings → Site features and toggle off Schema. In Schema Pro, go to Schema Pro → Settings and disable or delete conflicting schema types. 4. If you prefer to keep a third-party plugin active for other features, disable only its schema output rather than deactivating the full plugin. 5. After making changes, use a schema validation tool such as Google's Rich Results Test to confirm only one clean schema source is rendering per page. Best practice: Let OTTO SEO own schema output and disable schema generation in other plugins. This gives OTTO full control and avoids duplication. 🔍 Finding Your Deployed OTTO SEO Fixes After OTTO deploys changes, you can review exactly what was applied directly inside the Search Atlas platform. To find deployed fixes: 1. Log in to Search Atlas and open the OTTO SEO dashboard for your connected site. 2. Look for the Deployed Fixes or Activity section within the OTTO dashboard. This panel lists every change OTTO has pushed to your site, grouped by fix type (e.g., title tags, meta descriptions, schema, internal links). 3. Click on any fix category to expand the list and see the individual pages or elements that were updated. 4. Each fix entry shows the page URL, the type of change, and a timestamp so you can confirm when it was deployed. 5. Use the search or filter options at the top of the fix list to narrow results by fix type, page, or date range if you are looking for a specific change. If a fix does not appear in the deployed list, it may still be in a pending or suggested state. Pending fixes are visible in the recommendations panel and have not yet been deployed to your site. ↩️ Undeploying or Rolling Back OTTO SEO Changes If a deployed fix causes an issue or you simply want to revert a change, OTTO SEO allows you to undeploy individual fixes or groups of fixes without affecting other deployed changes. To undeploy a fix: 1. In the OTTO SEO dashboard, navigate to the Deployed Fixes section as described above. 2. Locate the specific fix or fix category you want to reverse. 3. Select the fix by checking its checkbox, or open the fix detail view by clicking on it. 4. Click the Undeploy button (sometimes labelled Revert or shown as a rollback icon). OTTO will remove the change from your site and restore the previous value. 5. Confirm the action when prompted. The fix will move back to a suggested or undeployed state in your dashboard. 6. Verify the rollback by visiting the affected page and checking the source or using a site audit tool to confirm the original content has been restored. Important notes on rollbacks: - Rolling back a fix only reverts that specific change. Other deployed fixes remain active and are not affected. - If you rolled back schema changes, return to your WordPress plugins and re-enable any schema output you previously disabled in Yoast or Schema Pro so there is no gap in structured data coverage. - Undeployed fixes can be re-deployed at any time from the OTTO recommendations panel. ✅ Quick Reference: Three-Step Workflow - Schema conflict? Disable schema output in Yoast or Schema Pro, and let OTTO own schema generation. - Need to see what was deployed? Open OTTO SEO → Deployed Fixes and filter by type, page, or date. - Need to reverse a change? Select the fix in the Deployed Fixes panel and click Undeploy or Revert. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔌 Find and Install Your OTTO Pixel Script

🧩 What Is the OTTO Pixel? The OTTO pixel is a small JavaScript snippet that must be installed on your website so Search Atlas can verify site ownership and enable OTTO's AI-powered SEO automation. If the dashboard shows the pixel as not installed, it means either the script has not been added to your site yet or it cannot be detected. 📋 How to Retrieve Your OTTO Pixel Script 1. Log in to your Search Atlas account. 2. In the left sidebar, click OTTO SEO. This opens the OTTO dashboard at /seo-automation-v3. 3. Select the OTTO project for the website you are working on. 4. Locate the pixel or site verification section within the project. Your unique pixel script will be displayed there. 5. Click Copy to copy the full script to your clipboard. Your OTTO pixel script will look similar to this structure: <script> (function(o,t,t,o){ ... })(your-unique-project-id); </script> Every pixel script is unique to your OTTO project. Do not share it or use a script from a different project on this site. 🛠️ How to Install the OTTO Pixel on Your Website Paste the copied script into your website so that it loads on every page. The recommended placement is just before the closing </head> tag in your site's HTML. Here are common installation methods: - WordPress: Use a plugin such as Insert Headers and Footers, or paste the script directly into your theme's header.php file before </head>. - Shopify: Go to Online Store → Themes → Edit Code → theme.liquid and paste before </head>. - Wix / Squarespace / Webflow: Use the custom code or header injection section in your site settings. - Google Tag Manager: Create a new Custom HTML tag, paste the script, and set the trigger to All Pages. Publish the container after saving. ✅ How to Confirm the Pixel Is Detected 1. After installing the script, return to the OTTO project in Search Atlas at OTTO SEO in the left sidebar. 2. Look for a Verify or Check Installation button and click it. 3. If detection is successful, the pixel status will update to Active or Installed. 4. If the status still shows Not Installed, work through the troubleshooting steps below. 🔍 Troubleshooting: Pixel Still Showing as Not Installed - Check the script is on every page: The pixel must appear in the HTML source of your live pages. Right-click any page on your site, select View Page Source, and search for your unique project ID to confirm it is present. - Clear caching: If your site uses a caching plugin or CDN (such as Cloudflare, WP Rocket, or LiteSpeed), purge the cache after installing the script so the updated code is served to visitors and to Search Atlas. - Confirm no script blockers: Browser extensions or firewall rules can prevent the pixel from firing. Test in a private/incognito window with extensions disabled, or on a different network. - Check for duplicate installations: Installing the script more than once can occasionally cause conflicts. Ensure the pixel appears exactly once in your page source. - Allow a few minutes: After a successful installation, the Search Atlas dashboard may take a few minutes to register the pixel as active. Refresh the page before retrying verification. - Correct project script: Confirm the script you installed matches the one shown in the OTTO project for this specific site. Scripts are project-specific and are not interchangeable. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team. Additional Notes You can validate the OTTO Pixel on a local development environment before pushing changes live. Set up your local site using your preferred local server tool, paste the script into the tag, load a page in a browser and confirm the script is present and loading without errors before deploying to your production environment.

🌐 How to Resolve Duplicate URLs with or without Trailing Slashes in Search Atlas (Sitemaps & OTTO Brand Vault)

🌐 How to Resolve Duplicate URLs with or without Trailing Slashes in Search Atlas (Sitemaps & OTTO Knowledge Graph) Duplicate URLs resulting from trailing slashes can cause mismatches between your live site, Google Search Console (GSC), and tools like OTTO Knowledge Graph. This guide walks you through resolving these discrepancies and maintaining a clean, consistent URL structure in Search Atlas. 🧭 Step-by-Step Instructions 1. Understand the Issue URLs with and without trailing slashes (e.g., /about vs. /about/) are treated as separate pages by search engines. If both appear in your sitemap, it creates duplication, confusing Google's crawlers and causing inconsistencies in GSC data. 💡 A uniform URL format ensures accurate tracking and indexing of your pages. 2. OTTO Knowledge Graph: Trailing Slash Handling Previously, OTTO Knowledge Graph stripped trailing slashes from manually added URLs, which could create duplicate URL versions and conflicting SEO recommendations in your OTTO account. ✅ This issue has been resolved. The Search Atlas engineering team has shipped a fix (internal ticket SPE-574) and it is fully merged and live in production. Manually added URLs now retain their original trailing slash format as entered. If you still observe this behavior after the fix, please contact support and include a screen recording (for example, via Jam) so the team can investigate further. 3. Set Up Redirections To eliminate duplicate entries and establish a consistent URL structure: - Redirect URLs without trailing slashes to their versions with trailing slashes. - Implement this via your access file or server configuration. Example command: RewriteRule ^(.*[^/])$ /$1/ [R=301,L] - Ensure GSC recognizes your preferred structure. - Test that redirections are working correctly. - Keep internal links consistent — they should always reference URLs with the trailing slash. - Update your sitemap to reflect the chosen format (e.g., all URLs ending with a slash). ⚙️ Implementation may vary depending on your hosting environment — consult a developer if needed. 4. Resolve GSC and Live Sitemap Mismatches Search Atlas pulls sitemap data from GSC, not directly from your uploaded sitemap file. If GSC detects both URL versions, indexing data can appear inconsistent. Use redirections and sitemap updates to communicate a single, canonical URL structure to GSC. ✅ Consistency between your live site and GSC data ensures smoother reporting in Search Atlas. 5. Test and Verify Your Changes After making updates: - Use Google's URL Inspection Tool in GSC to confirm that the correct version is indexed. - Test your sitemap with browser-based validators to ensure every listed URL follows the same trailing-slash format. - Conduct regular audits of your sitemap and GSC coverage reports to detect any future inconsistencies. - In OTTO Knowledge Graph, verify that newly added URLs retain their trailing slash as entered. 🔍 Routine validation helps maintain healthy SEO performance and data accuracy in Search Atlas. 6. Involve a Developer if Needed Changes to access or other server configuration files require technical precision. If you're unsure, consult a web developer to avoid unintended redirects or broken links. 🧑‍💻 Proper implementation ensures your fixes enhance, not hinder, your site's SEO performance. ❓ FAQs ❓ Why are trailing slashes causing duplicate URLs in Search Atlas? 💡 Because GSC views URLs with and without trailing slashes as distinct, Search Atlas may display both if your sitemap or redirects are inconsistent. ❓ Does OTTO Knowledge Graph still strip trailing slashes from manually added URLs? 💡 No. This was a known issue that has been resolved by our engineering team (ticket SPE-574). The fix is live in production, and manually added URLs now preserve their trailing slash format as entered. If you still see this behavior, please contact support with a screen recording (e.g., via Jam) so we can investigate. ❓ Can I fix this issue without editing my access file? ⚡ You can standardize links manually in your sitemap and internal URLs, but redirects remain the most reliable long-term solution. ❓ Does changing sitemap URLs affect my SEO? 💡 Correctly implemented redirects (301s) preserve link equity and improve crawl consistency, enhancing overall SEO performance.

🔍 Verify OTTO Is Not Connected to Your Domain

If you want to be sure OTTO is not making live changes to your website, you can check this yourself in a few minutes. This article explains how OTTO connects to a site, how to check whether your domain is connected, and what to do if you want to stop any changes. 💡 How OTTO Makes Changes to a Website OTTO can only change a live website if that site has been deliberately connected to it. A connection normally requires one of the following: - A domain added as an OTTO project inside a Search Atlas account. - An OTTO script (code snippet) installed on the website, or added through a tag manager or a similar tool. - A plugin or integration set up on your website platform, such as WordPress. If none of these are in place, OTTO has no way to publish changes to your site. Simply having a domain name mentioned somewhere in Search Atlas, such as in a report or a competitor list, does not mean OTTO is editing it. 📋 Step 1: Check Your Search Atlas Account First, confirm whether the domain has been added as an OTTO project. 1. Log in to your Search Atlas account. 2. Open the OTTO section of the platform. 3. Look through your list of projects or domains and check whether your domain appears. 4. If you manage more than one workspace or account, repeat the check in each one. If your domain is not listed in any account you have access to, it has not been set up as an OTTO project from your side. 🔎 Step 2: Check Your Website for the OTTO Script Next, confirm that nothing on the website itself connects it to OTTO. 1. Open your website in a browser. 2. Right-click the page and choose View Page Source. 3. Press Ctrl+F (Cmd+F on Mac) and search for OTTO or searchatlas. 4. If no results appear, no OTTO script is loading on that page. Check a few different pages, such as the homepage and an inner page, to be thorough. 🛠️ Step 3: Check Your Website Platform and Tools Some connections are made through tools outside the page code. Ask whoever manages your website to check these places: - Plugins: Look through your installed plugins for any related to Search Atlas or OTTO. - Tag managers: Check tools like Google Tag Manager for any tag that loads a Search Atlas script. - Theme or header settings: Look for custom code added to your site header or footer. - CDN or hosting tools: If your site uses a service such as Cloudflare, check for any rules or apps linked to Search Atlas. ✅ What Your Results Mean - Not listed in the account, and no script or plugin found: OTTO is not connected to your domain and is not making changes. - Listed in the account, but no script or plugin found: The domain has been added as a project, but nothing is installed on the site, so changes are not being published. - Script or plugin found: OTTO may be able to publish changes. Follow the steps below to disconnect it. 🚫 How to Disconnect OTTO From a Domain If you find a connection that you do not want, take these steps: 1. Remove or deactivate the OTTO script, plugin, or tag from your website. 2. Clear your website cache, and your CDN cache if you use one. 3. In Search Atlas, pause or remove the domain from your OTTO projects if it is listed. 4. Reload your website and search the page source again to confirm the OTTO reference is gone. Once the script or plugin is removed, OTTO can no longer apply changes to your pages. Pages return to the content stored on your own website. ⚠️ If the Domain Is Not Yours or You Are Unsure If you do not recognize a connection, or you manage a site on behalf of someone else, check with your team or website developer first. They may have set up OTTO without your knowledge. Do not delete code you are not sure about without confirming what it does. 💬 Need Help Confirming? If you would like us to confirm whether a specific domain is connected to OTTO, our team can check for you. Have the exact domain name ready, for example yourdomain.com, and tell us what you have already checked. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🔍 Why OTTO Schema Suggestions Reappear After Crawl

You generated schema for every page, then ran a new crawl and OTTO is suggesting schema for many pages again. This is a common question, and in most cases you are not repeating work. This article explains why it happens, how to confirm nothing is duplicated, and how to build a before-and-after comparison of your crawls. 🤔 Why Schema Suggestions Can Reappear Each crawl is a fresh scan of your site. OTTO compares what it finds on your live pages against its recommendations. Suggestions can come back for several reasons: - Schema was generated but not deployed. Generating schema creates the markup, but it only counts once it is live on the page. If it was not published or deployed, the crawl will not find it. - The crawl did not detect the deployed markup. Caching, a CDN, or a page builder plugin can delay updated code from reaching the crawler. - New or changed URLs. New pages, redirected pages, or URLs with different parameters or trailing slashes may be treated as new pages that need schema. - Different schema types. OTTO may suggest an additional type, such as FAQ, Breadcrumb, or Product, on a page that already has a basic type like Article or Organization. - Page content changed. If a page changed significantly, the earlier schema may no longer match its content, so a new suggestion appears. - Site-wide changes. A theme update, migration, or plugin change can remove or override schema that was previously live. ✅ How to Confirm You Are Not Duplicating Work Spot-check a few pages from the new suggestion list before generating anything again. 1. Pick 3 to 5 pages that OTTO is suggesting schema for again. 2. Open each page in your browser, right-click, and choose View Page Source. Search for application/ld+json. If you see your schema, it is live. 3. Paste the page URL into Google's Rich Results Test or the Schema Markup Validator. This shows exactly which schema types the page currently exposes. 4. Compare the result with OTTO's suggestion. If the same schema type is already live, the suggestion may be out of date and you can wait for the next crawl to refresh. 5. If the schema is missing, it was likely not deployed, or something on your site removed it. Re-deploy it rather than generating a new version. Tip: Avoid adding a second copy of the same schema type to a page. Duplicate markup can cause validation warnings. 📊 Building a Before and After Crawl Inventory A simple inventory shows what changed between crawls and confirms which suggestions are new. If you can export your OTTO schema or page lists from the platform, use that. If not, a manual snapshot works well. Before your next crawl: 1. Record the date of your last crawl. 2. Make a list of all pages where you generated and deployed schema. Include the URL, schema type, and deployment date. 3. Note the total number of pages with schema suggestions at that time. After the crawl finishes: 1. Make a second list of pages OTTO now flags for schema, with the URL and suggested type. 2. Put both lists in a spreadsheet and use a filter or lookup to find URLs that appear in both. 3. Sort the results into three groups: Already handled (same URL, same type, already live), Needs re-deployment (schema not found on the live page), and Genuinely new (new URLs or new schema types). Only the second and third groups need action. This usually shrinks a long suggestion list to a short to-do list. 🛠️ Steps to Take When Suggestions Look Wrong - Wait for caching to clear. If you deployed recently, allow time for your site cache or CDN to refresh, then run another crawl. - Clear your cache. Purge your site, plugin, and CDN caches so the crawler sees your latest code. - Check your URLs. Make sure the URLs OTTO crawls match the ones you deployed to, including the www or non-www version, HTTP or HTTPS, and trailing slashes. - Look for conflicts. Some SEO plugins or themes add their own schema. Check that nothing overrides or removes the markup. - Re-deploy if needed. If schema is missing from the live page, deploy it again, then re-crawl to confirm. 💡 Best Practices to Prevent Confusion - Keep a simple log of when schema was generated and deployed for each page. - Verify a few pages with a validator after each deployment. - Run a new crawl after major site changes, not before them. - Review suggestions by page group, such as blog posts, product pages, and service pages, instead of all at once. - Take a snapshot of your suggestion counts before each crawl so you can compare. 💬 Need More Help? If suggestions still look wrong after these checks, such as schema that is confirmed live but still flagged, send us a few example URLs so we can look into it. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🔍 Publication Media DA Scores and Meta Tag Verification

📌 Overview Many customers notice that the Domain Authority (DA) shown in the Publication Media dashboard is much lower than what other SEO tools report. For example, the dashboard may show a DA of 5, 7, or 10 with zero organic traffic, while another tool shows 20-45. Some customers also see meta tag verification fail when they try to confirm ownership of a site. This article explains why both happen and how to resolve them. 📊 Why DA Scores Differ Between Tools Domain Authority is not a single universal number. Each SEO tool calculates its own authority score using its own data and method, so the same website can get very different results. Common reasons for the gap include: - Different metrics: Tools use different scores, such as Domain Authority, Domain Rating, Authority Score, or Trust Flow. These are not directly comparable, even when they look similar. - Different link databases: Each tool crawls the web on its own schedule and finds a different set of backlinks. - Different update schedules: A score may be refreshed monthly or less often. A recently improved site can show an older, lower number for a while. - New or recently changed domains: Newer sites, or sites with few links pointing to them, often get lower scores until more data is collected. - Scale differences: Scores are usually on a 1-100 scale that is logarithmic, so small differences at the low end can look big. Because of this, a DA of 7 in one tool and 35 in another does not necessarily mean either one is wrong. Always compare scores from the same source over time instead of across tools. 📉 Why Organic Traffic May Show Zero Organic traffic figures are estimates based on the keywords a site is known to rank for. A zero can appear when: - The site is new, or only recently started ranking. - The site ranks for very few keywords, or only for low-volume keywords. - The site's keyword data has not yet been collected or refreshed. - The site is a niche or local publication whose traffic comes mostly from direct visits, social media, or newsletters rather than search. A zero in the dashboard does not mean your site has no visitors. It means little or no search-driven traffic has been detected yet. Your own analytics tool is the best source for your real visitor numbers. ✅ How to Review Your Site's Numbers 1. Note which metric the other tool is showing (DA, DR, Authority Score, and so on). 2. Check the date of the last update in each tool, if available. 3. Compare the trend over several weeks rather than a single snapshot. 4. Confirm that you entered the exact domain you want evaluated, including the correct version (with or without www). 5. Check your own analytics for actual traffic, and compare it with the dashboard's estimate. 🏷️ Why Meta Tag Verification Fails Meta tag verification works by checking your site's homepage for a specific tag that proves you own or control the site. If the platform cannot find that exact tag, verification fails. The most common causes are: - Tag placed in the wrong location: The tag must be inside the section of the homepage, not in the body of the page. - Incomplete or altered copy: Missing characters, extra spaces, or curly quotes added by a text editor can break the tag. Copy and paste it exactly as provided. - Cached pages: Caching plugins or a CDN may serve an older version of your homepage without the new tag. - Plugins or themes stripping the tag: Some optimization or security plugins remove or rewrite unknown tags. - Domain version mismatch: The tag may be on www.example.com while you submitted example.com (or the other way around), especially if the two do not redirect to each other. - Access restrictions: Password protection, maintenance mode, firewalls, or bot-blocking rules can stop the verification check from reaching your page. - Tag added to the wrong page: The tag must be on the homepage, not on an inner page or a draft. 🛠️ How to Fix Meta Tag Verification 1. Copy the verification tag again from the platform without changing it. 2. Paste it into the section of your homepage. In most website builders and CMS tools, look for a header code or custom code area. 3. Save and publish the change. 4. Clear any caching, including plugin cache, server cache, and CDN cache. 5. Open your homepage in a private browser window, view the page source, and search for the tag to confirm it appears. 6. Make sure the domain you submitted matches the version of the site where you added the tag. 7. Turn off maintenance mode or any password protection temporarily, and make sure no firewall rule is blocking automated checks. 8. Return to the platform and run verification again. Allow a few minutes after clearing the cache before retrying. 💡 Tips to Avoid Future Issues - Use the same domain format (with or without www) everywhere in the platform and on your site. - Keep the verification tag in place after verifying, since removing it may cause ownership to be rechecked. - Use DA as a rough guide only, and judge progress by your own trend over time. - Rely on your analytics data to measure real traffic. 💬 Need More Help? If you have followed the steps above and your scores or verification still look wrong, please have the domain you submitted and a description of what you see ready. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🛠️ How to Remove OTTO From Webflow

🔍 Overview If your Search Atlas account has been deactivated, you may want to remove OTTO from your Webflow website. You may also see a message asking you to sign up again when you try to log in. This is expected for a deactivated account. You do not need to log in to Search Atlas to remove the OTTO script. This guide shows you how to do it directly in Webflow. ❓ Why You Need to Remove It Yourself The OTTO script is stored in your Webflow project settings, which you control. Because it lives inside your own site, the removal has to be done from your Webflow account. Removing it is quick and does not affect the rest of your site content. - You do not need an active Search Atlas subscription to remove the script. - You only need access to your Webflow project with permission to edit site settings. - Removing the script will stop OTTO from running on your site. 📋 Before You Start - Make sure you are logged in to Webflow with an account that has Site Settings access (usually the site owner or an admin). - Have a few minutes available to publish your site after making the change. - Optional: copy your current custom code into a text file as a backup, in case you need to restore other scripts by accident. 🛠️ Step-by-Step: Remove the OTTO Script in Webflow 1. Log in to Webflow and open your Dashboard. 2. Find the website where OTTO was installed and open its Site Settings. 3. Select the Custom Code tab. 4. Look in the Head Code section first. Find the script snippet that references OTTO or Search Atlas. 5. Delete only that script snippet. Leave any other code, such as Google Analytics or other tools, exactly as it is. 6. Check the Footer Code section as well, in case the script was added there. 7. Click Save Changes. 8. Click Publish and publish to all of your domains. The change does not go live until you publish. 📄 Check Page-Level Custom Code If you or a teammate added the script to a specific page, it will not appear in Site Settings. To check: 1. Open the Designer for your site. 2. Open the Pages panel and hover over a page. 3. Click the gear icon to open Page Settings. 4. Scroll to Custom Code and look for the OTTO or Search Atlas script. 5. Remove it if you find it, then save and publish again. ✅ How to Confirm the Script Is Gone 1. Open your live website in a browser. 2. Right-click the page and choose View Page Source. 3. Press Ctrl+F (or Cmd+F on Mac) and search for otto and searchatlas. 4. If nothing related to OTTO appears, the script has been removed. If you still see the script, clear your browser cache or try a private browsing window. Then confirm that you published your site after saving. 💡 Common Questions - Can Search Atlas remove the script for me? The script is installed in your Webflow project, so the removal needs to be done from your Webflow account. The steps above take only a few minutes. - Why does the login page ask me to sign up? This usually means the account is deactivated. It does not prevent you from removing the script from your site. - Will removing the script break my website? No. Deleting only the OTTO snippet does not affect your pages, design, or other integrations. Your site will simply no longer load OTTO. - I can't find the script. What should I do? Check both Head Code and Footer Code, then check page-level code. If a developer or agency set up your site, they may have added it in a different place. - I don't have access to Webflow settings. Ask the site owner or a Webflow admin to grant you access, or ask them to follow the steps in this article. 🚀 Next Steps - Remove the script from Head Code, Footer Code, and any page-level code. - Save and publish your site. - Verify the removal using View Page Source. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🛠️ Checking Status of Escalated OTTO Deployment Tickets

📌 Overview When OTTO changes are not deploying on a client website, our team may escalate your ticket for a deeper technical review. Escalated tickets often involve the client's site setup, so they can take longer than standard requests. This article explains what escalation means, how to ask for a status update, and what you can check yourself while you wait. 🔎 What Does an Escalated Ticket Mean? An escalated ticket has been passed from first-line support to a team with deeper technical expertise. This usually happens when a problem cannot be solved with standard troubleshooting. For OTTO deployments, common reasons include: - Changes show as deployed in the platform but do not appear on the live website - The OTTO installation cannot be detected on the client site - Deployments fail or stay pending for a long time - The issue affects a specific site and needs a closer look at its setup Escalation does not mean your request has been forgotten. It means the issue needs extra investigation. 💬 How to Get a Status Update on Your Ticket The fastest way to check on an escalated ticket is through the live chat widget in the platform. Follow these steps: 1. Log in to your Search Atlas account. 2. Open the chat widget in the bottom-right corner of the platform. 3. Type human teammate to be connected with a member of our team. 4. Share the details listed in the next section so we can find your ticket quickly. 5. Ask for the current status and any next steps needed from you. 📋 What to Include When You Ask for an Update Having the right details ready helps our team locate your case without back-and-forth. Please include: - The client or project name the ticket relates to - The website domain affected (for example, whether it uses www or non-www) - The approximate date you submitted the ticket - A short description of the problem, such as OTTO changes not appearing on the live site - Any updates since you submitted the ticket, such as site migrations, plugin changes, or new hosting settings If you manage several clients, mention which one your question is about, since each site may have a separate case. 🧰 What You Can Check While You Wait These checks are safe to run and can help our team move faster. Some of them may even resolve the issue. 1. Confirm the project domain. Make sure the domain in your Search Atlas project exactly matches the live website address, including www or non-www and http or https. 2. Check the OTTO installation. Open the OTTO setup area for the project and confirm the installation is still detected. If it is not, reinstall following the setup instructions for your site platform. 3. Clear caches. Clear any caching plugin, server cache, or CDN cache on the client site, then reload the page. Cached pages can hide recent changes. 4. Review deployment status. Look at the specific changes in OTTO and note whether they show as deployed, pending, or failed. 5. Test in a private window. Open the page in a private or incognito browser window to rule out your own browser cache. 6. Look for recent site changes. A new theme, plugin, security setting, or hosting change can affect how OTTO works. Note any changes made around the time the problem started. ⏱️ What to Expect After Escalation Escalated issues are reviewed in order of complexity and impact. Resolution time depends on what the investigation finds. In some cases we may need more information from you, such as access details or confirmation of recent site changes. Replying promptly to any request from our team helps keep your case moving. You do not need to submit a new ticket to follow up. Opening duplicate tickets can slow things down because they may need to be merged. Ask for an update on your existing ticket through the chat widget instead. ✅ Tips to Prevent Deployment Issues - Keep the OTTO installation in place when updating or migrating a client website. - Tell your team before changing hosting, CDN, or caching settings. - Double-check the domain format when adding a new project. - Test a few deployed changes on the live site soon after setup. - Record the date and details of any problem so you can reference them in a follow-up. 🙋 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🔓 How to Unfreeze OTTO Sites and Reconnect WordPress

🔍 Overview If you froze OTTO sites months ago and have just signed back up, those sites may not appear as active in your dashboard. This guide explains why that happens, how to bring the sites back, and how to reconnect the WordPress plugin so OTTO can resume optimizing your pages. Menu names can vary slightly as the platform is updated, so use the steps below as a guide. ❄️ What Does a Frozen Site Mean? When you freeze a site, OTTO stops applying optimizations to it and the site stops counting toward your active plan. A site that has been frozen for a long time, often called deep-frozen, may also have lost its connection to your website. That is why you may need to reconnect it after you resubscribe. - Frozen: OTTO is paused for the site, but the project is still saved in your account. - Deep-frozen: The site has been frozen for an extended period, and its connection to your website may no longer be valid. - Disconnected plugin: The WordPress plugin is no longer linked to the project, so changes cannot be applied to your site. ✅ Before You Begin Check these items first. They prevent most problems. - Your subscription is active and your plan includes enough site slots for the sites you want to unfreeze. - You are signed in with the same account you used when you first set up the sites. - You have admin access to each WordPress site. - The domains are still live and reachable in a browser. 🔓 Step 1: Unfreeze Your Sites 1. Sign in to your Search Atlas account. 2. Open OTTO SEO from the main menu. 3. Find the site in your project list. Frozen sites are usually labeled with a frozen or paused status. 4. Open the site's settings or the options menu next to the project name. 5. Select the option to unfreeze or reactivate the site. 6. Confirm the action and wait a few minutes for the status to update to active. If you do not see your old sites in the list, check whether a filter or archive view is hiding them. Also confirm that you are signed in to the correct account. If a site has no unfreeze option, or the status does not change after a few minutes, it may be deep-frozen and need help from our team. See the last section of this article. 🔌 Step 2: Reconnect the WordPress Plugin Once the site is active, make sure the plugin on your website is linked to the project again. 1. Log in to your WordPress admin area. 2. Go to Plugins and look for the Search Atlas or OTTO plugin. 3. If it is installed, update it to the latest version and make sure it is activated. If it is missing, reinstall it from the setup instructions in your OTTO project. 4. Return to your OTTO project in Search Atlas and follow the connection steps shown for WordPress. 5. Enter the connection details, such as the API key or authorization shown in your project, in the plugin settings. 6. Save your changes and return to the dashboard to check the connection status. If the plugin was deactivated or removed while the site was frozen, reinstalling it and reconnecting is normal and does not affect your content. 🧪 Step 3: Confirm Everything Works - The site shows an active status in your OTTO project list. - The plugin shows as connected in WordPress and in the dashboard. - Your pages are visible in the project and OTTO can detect them. - Clear any caching plugin or CDN cache on your site so new optimizations appear when pages load. Optimizations may take a little time to show on your live pages after reconnecting, especially on large sites. 🛠️ Common Issues and Fixes - The site does not appear in my dashboard: Confirm you are using the original account, check any filters, and make sure your plan has available site slots. - The unfreeze option is unavailable: Your plan may have reached its site limit. Upgrade your plan or free up a slot by freezing another site. - The plugin will not connect: Update the plugin, confirm that the connection details were copied without extra spaces, and make sure no security plugin or firewall is blocking the connection. - The site shows as connected but nothing changes: Clear your site cache and your CDN cache, then reload the page. - I changed my domain or website setup since freezing: The old connection may no longer match. Reconnect the site using the current domain or set it up as a new project. 💡 Tips to Avoid Problems in the Future - Keep the WordPress plugin installed while a site is frozen, so you only need to reactivate it later. - Note which sites you froze and why, so you can reactivate them quickly when you return. - Check your plan's site limit before unfreezing several sites at once. - Keep your plugin and WordPress version up to date. 💬 Still Need Help? Deep-frozen sites sometimes need to be restored by our team, especially if a site has been inactive for many months or the connection cannot be re-established from your dashboard. When you reach out, mention the domain names of the sites you want restored so we can help faster. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🛠️ Fix an Inactive Publisher Site and Resubmit

🔍 Overview If your publisher site suddenly shows as Inactive in your publication account, it means the site is no longer eligible to receive or publish content through the platform. This usually happens for one of two reasons: the site failed a quality re-check (such as a Domain Authority, or DA, review), or the site's ownership verification stopped working. This article explains both causes, why your DA may look different in different tools, and how to verify and resubmit your site. ❓ Why Did My Site Become Inactive? Publisher sites are checked from time to time to make sure they still meet the platform's requirements. A site can move to Inactive when: - The DA reading changed or was lower at the time of the check. If the platform records a DA below the accepted level, the site may be deactivated automatically. - The verification meta tag was removed. Theme changes, plugin updates, site migrations, or caching tools can delete or overwrite the tag in your site's header. - The site could not be reached. Downtime, a password-protected page, or a firewall that blocks our checker can cause a failed verification. - The domain or its settings changed. Switching between www and non-www, moving to HTTPS, or changing the domain can break the link between your site and your account. 📊 Why Is My DA Different in My Account Than in Moz? It is common to see two different DA numbers for the same website. For example, you may see 41 in Moz but a much lower number in your publication account. Here are the most common reasons: - Different data sources. DA is a third-party estimate. Tools that read DA from different sources or at different times can show different numbers. - Different update timing. DA is recalculated periodically. The value saved in your account may be older or newer than the one you see in Moz today. - Different versions of the address. The score can differ between the root domain, a subdomain, and a specific URL. Make sure the address in your account exactly matches the one you checked in Moz. - Redirects or recent changes. If your site recently moved, changed its address, or was redirected, the platform may have read the score of a different version of your domain. - Temporary lookup errors. A failed or partial lookup can occasionally return a very low value until the next refresh. A large gap, such as 41 versus 9, is worth reviewing. Please see the section below on what to send us so our team can investigate. ✅ Step 1: Check Your Site Status 1. Log in to the platform and open your publication account. 2. Find your website in the list of publisher sites. 3. Note the status, the DA shown, and any message next to the site, such as a verification warning. 4. Open your site in a browser and confirm it loads normally without a login or password screen. 🏷️ Step 2: Re-Add the Verification Meta Tag The meta tag proves you own the site. If it is missing, the site cannot stay active. 1. In your publication account, open the site and choose the option to verify or resubmit it. 2. Copy the meta tag shown. It looks like a short line of code that begins with <meta name=. 3. Open your website's settings. In WordPress, use your theme's header settings or an SEO or header-and-footer plugin. 4. Paste the tag inside the section of your homepage, before the closing line. 5. Save your changes. 6. Clear your site cache and any CDN cache (such as your caching plugin or Cloudflare) so the new tag is visible to our checker. 🔎 Step 3: Confirm the Tag Is Live 1. Open your homepage in a browser. 2. Right-click the page and select View Page Source. 3. Press Ctrl+F (or Cmd+F on Mac) and search for meta name. 4. Check that the verification tag appears near the top, inside the head section, and that it matches the one in your account exactly. If you do not see the tag, it is likely being blocked by caching or by a theme setting. Clear the cache again or check that you saved the change on the correct homepage template. 🚀 Step 4: Verify and Resubmit Your Site 1. Return to your publication account. 2. Click Verify on the site. 3. Once verification succeeds, click Resubmit so the site can be reviewed again. 4. Wait for the review to complete. Status updates are not always instant, so check back after a short time. If the site is reviewed again and the DA shown is still below the required level, resubmitting will not change the result until the DA value is refreshed. In that case, our team can review it with you. 💡 Tips to Prevent Your Site From Going Inactive - Keep the verification meta tag in place permanently. Do not remove it after the first verification. - Re-check the tag after theme updates, plugin updates, or site migrations. - Keep your site online, publicly accessible, and free of password protection. - Use the same exact domain version (with or without www, HTTP or HTTPS) in your account as on your live site. - Avoid adding the same site more than once under different address versions. - Check your site's authority regularly and keep publishing quality content that earns links over time. 📋 What to Send Us If the DA Looks Wrong If your DA in the platform is far from what you see elsewhere, having the right details helps us resolve it faster. Please prepare: - The exact website address as it appears in your publication account. - A screenshot of the DA shown in your publication account. - A screenshot of the DA shown in Moz, including the date and the address you searched. - The date your site became inactive. - Confirmation that the verification meta tag is live (from the page source check above). 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

❓ Why OTTO Doesn't Suggest FAQ Schema

📖 Overview You may notice that OTTO suggests FAQ schema for some of your pages but not others. This is expected. FAQ schema is only useful when a page actually contains questions and answers, so OTTO does not recommend it for every URL. This article explains the most common reasons a suggestion does not appear and how to get one. 🧩 What Is FAQ Schema? FAQ schema is a type of structured data (code added to your page) that tells search engines your page contains a list of questions and their answers. It helps search engines understand your content more clearly. For the markup to be accurate, the questions and answers must also be visible to visitors on the page. 🔍 Common Reasons You Don't See a Suggestion - The page has no question-and-answer content. Pages such as a homepage, a contact page, or a product page with no Q&A section usually have nothing to mark up. Adding FAQ schema to a page without FAQs would be inaccurate and could cause problems with search engines. - The questions are not clearly formatted. If your questions are buried in long paragraphs, it is harder to recognize them as a distinct FAQ. Clear question headings with answers directly below work best. - The page already has FAQ schema. If valid FAQ markup is already on the page, whether from your theme, a plugin, or a previous deployment, there is nothing new to suggest. - The page type is not a good fit. Some page types, such as category pages, login pages, and thank-you pages, are generally not good candidates for FAQ markup. - The page has not been scanned recently. If you just added or changed content, the page may not have been picked up yet, so suggestions may not reflect your latest version. - The page is not accessible. Pages that are blocked from crawling, behind a login, or returning errors cannot be analyzed properly. - Search engines limit where FAQ results appear. Google now shows FAQ rich results only for a small set of sites, mainly well-known government and health websites. Because of this, FAQ schema may be a lower priority than other schema types for many pages. It can still help search engines understand your content. 🛠️ How to Get an FAQ Schema Suggestion 1. Open the page in your browser and check whether it contains real questions and answers. 2. If it does not, add a short FAQ section. Write each question as a clear heading or bold line, with the answer directly beneath it. 3. Make sure the questions are ones your visitors actually ask, and that the answers are written for people rather than just for search engines. 4. Publish the updated page and confirm it is live and accessible to the public. 5. Wait for OTTO to rescan the page, then check again for a new suggestion. ✅ How to Check for Existing FAQ Schema 1. Open the page you want to check. 2. Use a structured data testing tool, such as Google's Rich Results Test, and enter the page URL. 3. Look for an FAQ item in the results. If it is already listed, the page has FAQ markup and OTTO has no need to suggest it again. 4. If you see duplicate or conflicting markup, remove the extra version so only one remains. 💡 Best Practices for FAQ Content - Add FAQs only where they help the visitor. Do not add them to every page. - Keep answers short, accurate, and easy to read. - Do not mark up content that is not visible on the page. - Avoid using FAQs for advertising or promotional messages. - Review your FAQs regularly so they stay current. 🙋 Still Not Seeing a Suggestion? If the page has clear Q&A content, is live, and has no existing FAQ schema but you still do not see a suggestion, our team can take a closer look. Please have the page URL ready so we can check it quickly. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🛠️ Removing OTTO Hidden Keywords and Indexing Links

🔍 What This Article Covers Some customers notice a block of keywords or a group of links near the footer of their page HTML and worry that it looks like keyword stuffing. This article explains where that content comes from, how to find it, and how to have it removed. 💡 Why You See These Elements OTTO applies optimizations to your pages at the page level instead of editing the files in your CMS or theme. Two of those optimizations can add content near the bottom of the HTML: - Hidden NLP keywords: a block of related terms and phrases meant to help search engines understand the topic of a page. - Dynamic indexing links: a set of links meant to help search engines discover and re-crawl pages on your site. Because OTTO adds this content when the page loads, you will not find it in your theme editor, page editor, or footer template. This is why many customers cannot locate it in their website files. 🔎 How to Find the Content on Your Page 1. Open the page you want to check in your browser. 2. Right-click the page and choose View Page Source. You can also use your browser's Inspect tool. 3. Press Ctrl+F (Cmd+F on Mac) and search for a keyword you suspect was added, or scroll to the bottom of the HTML near the footer. 4. Look for a hidden paragraph of comma-separated terms with class otto-nlp-module (NLP Terms) or otto-missing-keywords-module (Missing Keywords), or for empty hidden anchors with class otto-dynamic-indexing-module. All carry data-otto-pixel="dynamic-seo" and style="display:none", so nothing shows on the rendered page. Tip: Either View Page Source or Inspect will show this content. It is inserted into the HTML response by the OTTO pixel, so it is not limited to the live DOM. The terms sit in a display:none paragraph and the indexing links are empty anchors, so you will not see them rendered on the page itself. ⚙️ How to Remove or Turn Off These Elements Follow these steps in your Search Atlas account: 1. Log in and open your OTTO SEO project for the affected website. 2. In the OTTO project, open the issue list. The keyword block comes from Content Optimizations → Semantic Analysis and Knowledge Graph Optimization (NLP Terms) and, if present, Missing Keywords. The links come from Dynamic Indexing, a sitewide issue that requires Google Search Console. There is no separate settings page for these, and the labels do not change by plan. 3. Open the NLP Terms row for the affected page and click Undeploy all, or undeploy the individual terms. Do the same for Missing Keywords if that block is present. For the links, open Dynamic Indexing and undeploy or delete the listed URLs. Undeploying removes the injected markup; there is no per-page control for Dynamic Indexing because its links are added only to the homepage footer. 4. The change is applied as soon as you undeploy. No save button is needed. 5. Reload the page, check it again using the steps above, and confirm the block is gone. If you still see it, clear your site cache and any CDN cache. To remove NLP Terms from every page at once, use Deploy All / Undeploy for the Semantic Analysis and Knowledge Graph Optimization category in the OTTO task list. Dynamic Indexing is a single sitewide list, so undeploying or deleting its entries removes the links from the homepage in one step. Contact support only if the block remains after undeploying and clearing cache. 🚀 After the Content Is Removed - Clear your caches. Purge your caching plugin, server cache, and CDN so visitors and crawlers see the updated page. - Request a re-crawl. In Google Search Console, use URL Inspection and click Request Indexing for your most important pages. - Monitor your rankings. Search engines can take days or weeks to process changes, so check your performance over a few weeks instead of expecting an immediate shift. 📊 About Keyword Stuffing Concerns Third-party SEO audit tools sometimes flag a long list of repeated or unrelated terms as keyword stuffing. If you are concerned, it is reasonable to remove the block. Removal also helps you rule it out as a factor if you are investigating a ranking drop. Rankings depend on many factors, so a ranking change should be checked against other causes too, such as content updates, technical issues, and algorithm updates. ✅ Quick Checklist - Check the page using Inspect to confirm the content is there. - Disable the NLP keyword and indexing link optimizations in your OTTO project. - Clear your site and CDN caches. - Request re-indexing in Google Search Console. - Re-run your SEO audit to confirm the warning is gone. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team. To help us act faster, include your website address and a few example page URLs where you see the content.

🛠️ Reverting OTTO Changes on a Live Page

🔍 Overview OTTO can deploy on-page SEO changes to the version of your site that visitors see, such as updated title tags, meta descriptions, headings, image alt text, and meta keywords. It does not rewrite the body copy stored in your CMS. Sometimes a deployed change is not what you wanted, for example a name or brand term that reads differently in the live title or heading than in your editor. This article explains why that happens and how to undeploy the change. ❓ Why Does the Live Page Show Different Wording? In most setups, OTTO applies its changes to the version of the page that visitors see. It does not rewrite the original content stored in your website's backend or CMS. This is why you may see one name or phrase in your editor and a different one on the live page. A few things can cause wording to change in a way you didn't expect: - AI suggestions: OTTO can generate a new title tag, meta description, or heading for a page, and it can add missing keywords or related terms. Those suggestions change the live title, description, or heading. They do not rewrite the body copy in your CMS. - Name inside a rewritten field: A person’s name or brand term can change when it is part of a title, heading, or meta description that OTTO rewrites. OTTO does not run a separate name-replacement pass, and its title suggestions are instructed to keep brand and product names. - Bulk deployment: If several changes were deployed together, a small edit may have been included without a close review. 🛠️ How to Revert a Deployed Change Follow these steps to take one deployed fix off the live page. The button stays labeled Deployed while the fix is live. Click it once to undeploy that fix. Labels can differ slightly if your account uses a white-label name. 1. Log in to Search Atlas and open OTTO for the website in question. 2. Find the page that shows the wrong wording. You can search by page URL or browse the list of optimized pages. 3. In the left sidebar, open Onpage Optimizations and then the category that holds the wording, such as Title Tags, Meta Description, Heading Optimizations, H1 Length, or H2 Length. 4. Locate the specific change that affects the wording, such as the content or text change that includes the name. 5. On that row, click the green Deployed pill. It switches back to Deploy and removes only that fix from the live page. Do not use Roll back all unless you want every deployed fix in that category removed. If the page has several items, such as keywords or links, use Undeploy all on that page to remove only that page’s items. 6. You do not need to redeploy or save. Clicking Deployed is the undeploy. A confirmation dialog appears only for bulk actions such as Roll back all. ✅ Confirm the Revert Worked After reverting, check the page to make sure the original text is back. 1. Wait a few minutes for the update to take effect. 2. Open the live page in a private or incognito browser window. 3. Do a hard refresh to bypass your browser's saved copy. On Windows, press Ctrl + F5. On Mac, press Cmd + Shift + R. 4. If the old wording still appears, clear the cache in your website's caching plugin, hosting platform, or CDN, then check again. ⚠️ Special Case: Names and Brand Terms People's names, job titles, brand names, product names, and legal wording should usually stay exactly as written. If OTTO changes one of these: - Revert the change using the steps above. - Check that the correct spelling is used in your backend as well, since it is the source OTTO works from. - Review any future suggestions for that page before you deploy them. 💡 Tips to Prevent Unwanted Changes - Review before you deploy: Read each suggested text change, especially on About, Team, and Contact pages. - Deploy in small batches: Smaller deployments make it easier to spot and undo a single problem. - Check key pages after deployment: Look at your most important pages on the live site within a day of deploying. - Keep a record: Note the page URL and the exact wording you want, so a fix is quick if something changes. 🧰 Troubleshooting - The change is still visible after reverting: This is usually caching. Clear your site and browser cache and check again. - The change keeps coming back: A new OTTO suggestion may have been deployed for the same page. Check the page's deployed changes list for a newer entry and revert it too. - You can't find the change: Compare the live page with your backend text to identify exactly what differs, then look for the matching item in the page's change list. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team. To help us resolve it faster, include the page URL, the wording that appears on the live page, and the wording you expect to see.

🔄 Switch Your SEO Focus to a New Industry

🧭 Overview If your Search Atlas account was previously optimised for one industry — such as solar energy — and you now need to rank for a different niche, such as windows and doors installation or replacement, you must update two key areas: your Brand Vault and your OTTO SEO configuration. Skipping either step will cause OTTO to continue generating content, meta descriptions, and keyword targets based on your old business focus. This guide walks you through the full reset process so that every optimisation OTTO produces reflects your new target market, services, and location. 🏦 Step 1 — Update Your Brand Vault The Brand Vault is the source of truth OTTO uses to understand your business. If it still describes a solar company, OTTO will keep optimising for solar — even after you change other settings. Update it first. 1. Go to Brand Vault: top-right More Features menu (grid icon, next to your Avatar Menu (👤)) → Brand Vault, or OTTO SEO → All Sites (SEO Automation) in the left sidebar → open your project → Brand Vault. 2. Open the Business Information section and rewrite your business name, description, and value proposition to reflect your windows and doors services. 3. Update your Products & Services list. Remove all solar-related entries and add your new offerings, for example: window installation, door replacement, energy-efficient windows, sliding doors, and any other services you provide. 4. Update your Target Location to reflect the geographic area you serve — for example, Las Vegas, NV — if this has not already been set correctly. 5. Review your Target Audience description and rewrite it to reflect homeowners or contractors searching for window and door services in your area. 6. Save all changes before moving to the next step. Why this matters: OTTO reads your Brand Vault every time it generates or updates content. An accurate Brand Vault prevents domain drift — where OTTO produces descriptions or titles that do not match your actual business. 🔑 Step 2 — Revise Your Target Keywords Before reprocessing OTTO, make sure your keyword targets are aligned with your new niche. This ensures OTTO prioritises the right terms from the moment it reprocesses your site. 1. Navigate to OTTO SEO → SEO Automation in the left sidebar (or go to /seo-automation-v3). 2. Open the Keyword Targeting or Focus Terms section. 3. Remove any solar-related keywords that are currently set as primary or secondary targets. 4. Add high-intent, location-specific keywords relevant to your new niche, such as: window replacement Las Vegas, door installation Las Vegas, energy-efficient windows Las Vegas, and similar variations. 5. Prioritise non-branded, service-intent keywords — these drive the most valuable organic traffic for local home-services businesses. Tip: Use the Keyword Research tool in Search Atlas to find additional high-opportunity terms in the windows and doors category before finalising your list. ⚙️ Step 3 — Reprocess Your Site With OTTO SEO Once your Brand Vault and keyword targets are updated, trigger a full reprocess in OTTO SEO. This tells OTTO to regenerate all on-page optimisations — titles, meta descriptions, headings, and content suggestions — using your new business profile. 1. Go to OTTO SEO → All Sites (SEO Automation) in the left sidebar. 2. Select the website you want to reprocess. 3. Click Reprocess (or the equivalent refresh/re-run option shown on your dashboard). 4. Confirm the action when prompted. OTTO will begin analysing your pages against your updated Brand Vault and keyword targets. 5. Once processing is complete, review the generated recommendations under OTTO SEO → Overview (OTTO Grader) across the Holistic SEO Pillars — Content, Authority, Technical, and UX Signals — to confirm they reflect windows and doors topics rather than solar content. 6. Deploy the approved changes to your site. Important: Reprocessing may take a few minutes depending on the size of your site. Do not navigate away from the page while it is running. ✅ Step 4 — Verify the Results After OTTO finishes reprocessing, perform a quick audit to confirm the old industry focus has been fully replaced. - Check that page titles and meta descriptions on your key service pages reference windows and doors — not solar panels or energy systems. - Confirm that your target keywords appear in OTTO's recommendations and are mapped to the correct pages. - Review at least your homepage, top service pages, and any location pages to ensure consistent messaging throughout. - If you spot any remaining solar references, manually edit those fields within OTTO SEO and re-deploy. 💡 Additional Tips - Create dedicated service pages for each major offering — for example, a separate page for window installation and another for door replacement — so OTTO can target specific keywords at the page level rather than competing terms on a single page. - Add a location page targeting Las Vegas specifically if you do not already have one. Local landing pages improve OTTO's ability to generate geo-targeted meta data and schema. - Check your schema markup after reprocessing. OTTO may generate LocalBusiness or Service schema — confirm the service type and area served fields reflect your new niche. - Allow two to four weeks for search engines to re-crawl your updated pages and begin reflecting the new focus in rankings. 🆘 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔄 Reset Playbook Rerun Restrictions

🔍 Why reruns become restricted Playbook rerun restrictions help prevent duplicate changes and repeated work. After a redirect is created or updated, the affected URL may remain restricted until Search Atlas refreshes its crawl and confirms the current page state. 🔗 How redirects affect Playbooks A redirect can change the URL that a Playbook should evaluate. The original URL may no longer be eligible for another run, while the destination URL may need to be crawled before recommendations or fixes can continue. 🛠️ Reset the restriction 1. Confirm that the redirect points to the intended destination and does not create a redirect loop. 2. Run a fresh crawl for the affected site or URL so Search Atlas can update its page status. 3. Open the relevant Playbook and review the affected task after the crawl finishes. 4. If the rerun option is available, rerun the Playbook on the current destination URL. 5. Review the result and confirm that the Otto error is resolved before applying additional changes. 🚦 Can a crawl or restriction be overridden? Customers cannot directly override crawl processing or Playbook rerun safeguards from the platform. These protections prevent conflicting changes and inaccurate results. A fresh crawl and review of the destination URL are the recommended way to reset the workflow after a redirect. ✅ If the restriction remains - Check that the destination URL returns the expected status code. - Verify that the redirect is not chained, looping, or pointing to an unavailable page. - Make sure the destination is included in the site configuration and is not blocked from crawling. - Wait for the crawl to complete, then reopen the Playbook and check its latest status. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🛡️ Whitelist OTTO on Cloudflare for Shopify

🔍 Why This Is Needed OTTO is Search Atlas's AI SEO automation bot. It crawls your website to scan pages, identify optimisation opportunities, and apply changes on your behalf. If your Shopify store is proxied behind Cloudflare, Cloudflare's security rules may block or challenge OTTO's requests — preventing it from working correctly. Whitelisting OTTO in Cloudflare ensures the bot can access your site without interference. ⚠️ Important: Shopify vs WordPress Differences The whitelisting process for Shopify differs from the WordPress guide published on the Search Atlas blog. Shopify does not give you access to server configuration files (such as .htaccess), so all traffic rules must be managed entirely within your Cloudflare dashboard. Follow the Shopify-specific steps below. 📋 What You Will Need - Access to your Cloudflare account (the account managing your Shopify store's domain) - Your Shopify store's domain confirmed as an active zone in Cloudflare - OTTO's IP addresses and user agent string (listed in the section below) 🤖 OTTO Bot Details Use the following identifiers when creating your Cloudflare rules: - **User Agent:**OTTOBot (the user agent string sent by OTTO during crawls) - IP Addresses: Contact the Search Atlas team via the chat widget to obtain the current list of OTTO IP addresses, as these may be updated periodically. 🛠️ Step-by-Step: Whitelist OTTO in Cloudflare 1. Log in to Cloudflare and select the domain associated with your Shopify store from your account dashboard. 2. Go to Security → WAF using the left-hand navigation in Cloudflare. 3. Click the Custom Rules tab, then click Create rule. 4. Name your rule something descriptive, such as Allow OTTO SEO Bot. 5. Under If incoming requests match…, set the following conditions using OR logic between them: - Field: User Agent | Operator: contains | Value: OTTOBot - Field: IP Source Address | Operator: is in | Value: (paste each OTTO IP address) 6. Under Then take action…, select Skip from the dropdown, then enable Skip all remaining custom rules. This ensures OTTO bypasses WAF blocks without disabling your protection for other visitors. 7. Set the rule order so it appears above any existing block or challenge rules that could affect bot traffic. 8. Click Deploy to save and activate the rule. 🔒 Also Check: Bot Fight Mode and Security Level Two additional Cloudflare settings can interfere with OTTO even after you create a custom rule: - Bot Fight Mode: Go to Security → Bots. If Bot Fight Mode or Super Bot Fight Mode is enabled, it may challenge or block OTTO independently of your WAF rules. You may need to disable this feature or, if you are on a Business or Enterprise plan, configure bot exceptions to allow the OTTOBot user agent. - Security Level: Go to Security → Settings. If the security level is set to I'm Under Attack, all visitors including bots will face a JavaScript challenge. Lower this to High or Medium while OTTO performs its scans, then raise it again afterwards if needed. ✅ How to Verify OTTO Can Access Your Site 1. In Search Atlas, go to Left sidebar → OTTO SEO (URL: /seo-automation-v3). 2. Select your Shopify project and trigger a new Scan. 3. If the scan completes without errors and OTTO begins returning page-level recommendations, the whitelist is working correctly. 4. In Cloudflare, you can also go to Security → Events and filter by the OTTOBot user agent to confirm requests are being allowed rather than challenged or blocked. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🗺️ Update OTTO Topical Map Seeds

🧭 How seed keywords work When you create an OTTO topical map, its seed keywords are set for that map. Updating seed keywords in Brand Vault does not change the seeds in a map that already exists. Refreshing the existing map will not apply the updated Brand Vault seeds. 🔄 Create a replacement map 1. Update the seed keywords in Brand Vault. 2. In the left sidebar, select OTTO SEO. 3. Open the topical maps area and start creating a new topical map for the page or site you want to target. 4. Use the updated seed keywords when setting up the new map, then create it. A new map is needed to use the revised seeds. The existing map remains unchanged; refreshing it does not replace its seed keywords. ✅ Check the new map Open the newly created map and confirm that it uses the intended seed keywords. If it does not, check the seeds selected during map creation. 💬 Need help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🔍 Investigating Spam Links in OTTO Generated Blogs

🔍 Understanding Spam Links in OTTO Blogs Spam links can appear in blogs created by OTTO SEO when content generation pulls from unverified external sources or when link filters are not applied. This issue affects multiple sites if project settings allow broad content scraping without quality checks. 🛠️ Steps to Investigate the Problem Start by reviewing recent blog posts in your OTTO SEO projects. Check for any links pointing to low-quality or unrelated domains. Use the AI Visibility section under OTTO SEO to scan active projects and identify patterns in generated content. 1. Navigate to Left sidebar then OTTO SEO. 2. Select the affected project from the Active list. 3. Review blog output for embedded links and note any spam patterns. 4. Compare across multiple sites to see if the issue is widespread. 🚀 How to Prevent Spam Links Configure your OTTO SEO settings to restrict link sources and enable content validation before publishing. Apply these changes to all projects to avoid recurrence. - Set strict domain filters in project creation to block known spam sites. - Enable quality scoring for all generated content in the AI Visibility tools. - Review and approve links manually for new blogs until filters are tuned. - Run regular scans on all active projects to catch issues early. 📊 Monitoring and Ongoing Checks Schedule periodic audits using the Visibility and Topics sections to maintain clean content across sites. Update filters as new spam sources emerge to protect your entire account. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

⚙️ OTTO Title Tag Deployment and Rollback

🔍 How OTTO title tags work OTTO can recommend and deploy optimized title tags for eligible pages. When deployment is enabled, OTTO adds the configured title to the page through its supported integration. The title shown to visitors and search engines may also be affected by your CMS, SEO plugin, caching, or other site code. 📊 Check the title on your site 1. Identify the affected page and compare its expected title with the title currently shown in the browser tab. 2. View the page source and check the <title> element to see which title is present in the page HTML. 3. Repeat these checks for each affected page, since title behavior can differ between pages. ↩️ Understanding deployment and rollback The available information does not establish a particular control or procedure for disabling OTTO title deployment or rolling it back. Do not assume a specific setting will restore a previous title. The title rendered on a page can depend on the website’s CMS, SEO plugin, theme, custom code, or caching. Check these sources to understand which system is supplying the current title. 🛠️ Troubleshoot the displayed title 1. Check the browser tab title and the page source for the affected page. 2. Review the CMS title field, SEO plugin settings, theme templates, and custom code that may control the title. 3. Clear relevant website, CDN, and browser caches, then check the page again in a private browser window. ✅ Verify the final title Do not rely only on the browser tab. Check both the rendered page and the page source. If the title remains unexpected, review which site systems may be supplying or overriding it. Search engines can display a different title from the one in the page source, so allow time for them to recrawl the page. ⚠️ When the title still looks incorrect A title may remain unchanged temporarily because of browser, website, or CDN caching. Confirm the live HTML first, then allow time for search engines to recrawl the page. Some OTTO recommendations may match the title already on the page or may be treated as no-op recommendations. In that situation, there may be no visible change even though the recommendation is present. Manual title edits and other SEO plugin rules can also override the expected result. 💬 Get help If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚙️ OTTO SEO and Webflow: Current Limitations Explained

🔍 Overview OTTO SEO connects to your website through a JavaScript pixel that is installed on your pages. On some platforms, OTTO can write changes directly to your page content at the source level — meaning edits land inside the actual CMS and persist as real content updates. On Webflow, this deeper integration is not yet available. This article explains what that means for your site, why the limitation exists, and what the current situation looks like. ⚙️ How the OTTO Pixel Works on Webflow When you install OTTO on a Webflow site, the pixel is injected as a client-side JavaScript snippet. This means OTTO can: - Read and analyse your page content - Surface SEO recommendations and audit findings - Apply certain on-page changes via the browser at render time However, because the pixel operates client-side, it cannot write changes back into Webflow's CMS or Designer. Any modifications OTTO applies are rendered in the browser layer — they are not stored as permanent edits inside your Webflow project. 🚧 Why a Source-Level Fix Is Not Yet Available Webflow uses a closed Designer environment and a separate CMS API that requires a different integration approach — one that goes beyond what a client-side pixel can do on its own. Bridging OTTO's automation engine with Webflow's CMS API at a source level is a significant technical undertaking, and this capability is not currently available. 📊 What This Means for Your Webflow Site Right Now If you are running OTTO on a Webflow site, here is what you can expect: - SEO audits and recommendations work fully — OTTO will scan your site and surface issues through the standard audit workflow. - Client-side optimisations applied by the pixel are active while the pixel is loaded, but are not written into Webflow's source content. - Manual implementation is currently required — to make OTTO's recommendations permanent, you or your team will need to apply the suggested changes directly inside the Webflow Designer or CMS editor. 🛠️ Interim Workaround: Applying OTTO Recommendations Manually in Webflow While native CMS-write is unavailable, you can still action every OTTO recommendation by following these steps: 1. Run an OTTO audit on your Webflow site. Navigate to OTTO SEO → Site Audit in the left sidebar, select your project, and open the Audit or Recommendations panel to see a prioritised list of issues. 2. Export or note the specific recommendations — for example, missing meta titles, meta descriptions, heading structure issues, or alt-text gaps. OTTO surfaces the exact field and suggested value for each finding. 3. Log in to your Webflow project and open the page or CMS Collection that contains the flagged content. 4. For static pages: Open the page in the Webflow Designer, click the relevant element or use the SEO settings panel (Page Settings → SEO tab) to update meta title, meta description, Open Graph fields, or on-page content as recommended by OTTO. 5. For CMS Collection items: Go to your Webflow CMS editor, open the relevant Collection, and edit the individual item fields (e.g., SEO Title, Meta Description, or custom fields) to match OTTO's suggested values. 6. Publish your Webflow site after making changes so that updates go live and are reflected when OTTO re-scans the page. 7. Re-run the OTTO audit to confirm the issues are resolved and track your progress over time. Repeating this workflow for each audit cycle allows you to systematically implement OTTO's recommendations even without automated CMS-write support. 🗺️ Roadmap Status A native, source-level Webflow integration — one that writes changes directly into your Webflow CMS — is not available at this time. There is no confirmed delivery date for this capability. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Finding and Accessing Missing SEO Analysis Features

Overview Some customers notice that features such as meta keywords analysis, missing keywords, semantic analysis, knowledge graph optimization, and knowledge-based trust are not immediately visible in their account. This article explains what to check and what information to have ready if you need support to resolve the issue. Why Features May Appear Missing Because the original source for this topic did not include a documented agent resolution, the exact root cause can vary. Common factors that have been reported include plan-level access restrictions, features that only appear after a site analysis has been run, or features located in a different section of the platform than expected. The actual cause in your case may differ and may require a backend review by our team. What to Check Before Escalating Work through the following checks to rule out common display or access issues: 1. Confirm a site analysis has been run. Navigate to your project and verify that a crawl or on-page analysis has been completed. Some features only populate with data after this step. 2. Check all relevant sections of the platform. Expand any collapsed submenus and switch between tabs to make sure you are not overlooking a nested section. 3. Select a specific page or URL. Some analysis features only appear when an individual URL is selected rather than the project-level overview. 4. Review your subscription plan. Go to your Avatar (top-right) → Billing (Plans & Top-ups) and confirm which features are included in your current plan, as plan-level restrictions may limit visibility. 5. Clear your browser cache or try a different browser. Client-side rendering issues can occasionally prevent features from loading correctly. If the Feature Is Still Not Visible If none of the above steps resolve the issue, our team will need to investigate on the backend. Please have the following ready when you reach out: - The exact name of the feature you cannot locate (e.g., Missing Keywords, Knowledge Graph, Semantic Analysis) - Your project name and the specific URL or page where you expected to find the feature - A screenshot or screen recording showing what you see in place of the expected feature - The date and time you first noticed the feature was missing - Your current subscription plan name If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛡️ Allowlist OTTO SEO in Cloudflare WAF and CSP

🔍 Overview OTTO SEO needs to crawl your site and load its scripts without being blocked by your server's firewall or Content Security Policy (CSP). This article explains the areas to review when troubleshooting access problems in Cloudflare or another security layer. ⚠️ Review Your WAF Configuration Check your Cloudflare WAF and any other firewall, security plugin, or server-level protection that could block OTTO SEO's crawler. Review the security events and blocked requests associated with your site, then create an exception for the crawler according to the identifier and guidance provided for your account. If you use a third-party WAF or firewall plugin, review its allowlisting documentation and apply the equivalent exception there as well. 🌐 Review Your Content Security Policy If your site sends a Content-Security-Policy HTTP header, review the directives that control scripts, connections, and other resources required by OTTO SEO. Confirm that your policy permits the Search Atlas resources used by your site, based on the domains shown in your account or provided by Search Atlas support. - script-src — review whether required OTTO SEO scripts are permitted. - connect-src — review whether required connections are permitted. - img-src — review whether required image resources are permitted. ✅ Test After Updating Your Rules After updating your WAF or CSP, retry the affected OTTO SEO action and check your browser console, server logs, and security events for blocked requests. If requests are still blocked, record the exact error, affected domain, and timestamp before escalating the issue. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🛡️ WAF Blocking Script Tags in OTTO Custom HTML

🔍 Overview When you paste code containing <script> tags into the Custom HTML Content field inside OTTO SEO, the platform's Web Application Firewall (WAF) may strip or block that content before it is saved or deployed. This article explains why this happens, how to deliver JSON-LD structured data safely, and what to do if you need to inject other types of scripts. ⚙️ Why the WAF Blocks Script Tags Search Atlas runs a WAF in front of all user-submitted content fields to protect the platform and your site from cross-site scripting (XSS) and code-injection attacks. The WAF applies a blanket rule that flags any raw <script> tag submitted through form inputs — including the Custom HTML Content field in OTTO SEO. This behavior is intentional and by design; it is not a bug specific to your account. The WAF rule affects: - Inline <script> blocks (e.g. JSON-LD wrapped in <script type="application/ld+json">) - External script references (e.g. <script src="...">) - Any HTML attribute that contains JavaScript event handlers ✅ Supported Way to Deliver JSON-LD Structured Data JSON-LD is the recommended format for structured data, and there is a dedicated, WAF-safe path to deploy it through OTTO SEO without using the Custom HTML Content field. 1. Open OTTO SEO → All Sites (SEO Automation) from the left sidebar (or navigate to /seo-automation-v3). 2. Select the page or template you want to add structured data to. 3. Look for the Schema / Structured Data section within the OTTO SEO page settings. 4. Enter your JSON-LD object directly into the structured data editor — without the wrapping <script> tags. OTTO automatically wraps your payload in the correct <script type="application/ld+json"> tag and injects it into the page head at deploy time, bypassing the WAF rule entirely. 5. Save and deploy your changes as normal. This is the only fully supported method for delivering JSON-LD through OTTO SEO. It ensures your structured data passes WAF validation and is rendered correctly by search engine crawlers. 📋 What About Tracking Pixels and Other Scripts? Tracking pixels and third-party scripts (e.g. Google Tag Manager, Meta Pixel, TikTok Pixel) should not be added through the Custom HTML Content field. The recommended approach is: - Google Tag Manager (GTM): Install the GTM container snippet through your site's theme or CMS header/footer injection settings, then manage all pixels and scripts inside GTM. OTTO SEO can detect an existing GTM installation and will not duplicate it. - Native pixel fields: Some integrations within Search Atlas have dedicated pixel ID fields — use those instead of pasting raw script tags. - CMS-level injection: For scripts that must be on every page, add them at the theme or template level in your CMS (e.g. WordPress header.php, Shopify theme settings) rather than through OTTO's content fields. 🚫 What Is Not Supported - Raw <script> tags pasted into the Custom HTML Content field — these will be blocked by the WAF and will not appear on your site. - Account-level WAF exceptions for individual customers — the WAF rules are platform-wide and cannot be disabled for specific accounts. - Encoding workarounds (e.g. Base64-encoded scripts or HTML entity encoding) — the WAF is designed to detect obfuscated script patterns and will still block them. 💡 Quick Troubleshooting Checklist - JSON-LD not appearing on your page? Confirm you are using the dedicated Schema / Structured Data section in OTTO SEO, not the Custom HTML Content field. - Structured data editor not visible? Make sure your OTTO SEO plan includes schema automation. Check your subscription or contact support. - Pixel not firing? Verify the pixel is installed at the CMS or GTM level, not through a Custom HTML field. - Custom HTML content disappearing after save? This is the WAF removing blocked tags. Remove any <script> tags from your content before saving. 🆘 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🖼️ OTTO Alt Text Generation: Image Exclusions and Rollback Timing

🔍 What This Article Covers This article explains the current capabilities and limitations of OTTO's alt text generation feature, specifically around excluding individual images from processing. It also covers how rollbacks work and how changes may appear on your WordPress site. ⚠️ Image Exclusion Is Not Currently Supported OTTO does not provide a way to exclude specific images from alt text generation. When you deploy the alt text feature, OTTO processes all eligible images across the connected site. There is no per-image toggle, exclusion list, or filter available in the platform at this time. We understand this may not match every workflow, so the sections below describe practical workarounds you can use right now. ✅ Workarounds for Managing Specific Images Although you cannot exclude individual images before generation, you have options to control which alt text changes are ultimately applied to your site. - Review before deploying: After OTTO generates alt text, review the suggested values inside the platform before pushing them live. Inspect the alt text recommendations and only deploy when you are satisfied with the output. - Do not deploy specific changes: OTTO gives you control at the deployment stage. If a generated alt text value is not suitable for a particular image, do not confirm that deployment. Leave those images undeployed and manage their alt text manually in WordPress instead. - Use WordPress as your source of truth for sensitive images: For images that require custom, brand-specific, or legally sensitive alt text, set those values directly in your WordPress media library. Where possible, manage alt text for those images manually rather than deploying OTTO's suggestions for them. ⏱️ How Long Do Alt Text Rollbacks Take? If you have already deployed alt text changes through OTTO and need to reverse them, you can initiate a rollback from within the OTTO SEO section of the platform. Rollback timing and behavior — including how quickly changes reflect on your WordPress site and whether caching may delay visibility — can vary depending on your site configuration and plugin setup. Because rollback timing specifics depend on your individual WordPress environment, we recommend reaching out to our team for guidance tailored to your setup. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚡ Manage WordPress Sync, OTTO CSS, and GSC Issues

Overview This article covers three common questions Search Atlas customers ask about OTTO SEO and WordPress integration: how to un-sync a specific page from WordPress, how OTTO handles CSS when updating headings, and how to resolve Google Search Console (GSC) connection issues. How to Un-Sync a Page from WordPress The Sync-to-CMS feature is available exclusively through the Search Atlas WordPress plugin. If you need to stop a specific page from being synced to WordPress, our support team can assist. When contacting us, please have the following ready: - The URL of the page you want to un-sync - Your Search Atlas project name or domain - A description of any changes you want to stop being published Note: Our team will need to investigate your account configuration to assist with un-syncing specific pages. How OTTO Handles CSS When Changing H1 Text If you notice unexpected visual changes on your site after an OTTO sync — such as missing styles, a removed hero image, or broken page layouts — this may be related to how your page template or theme interacts with OTTO's updates. These issues require backend investigation by our support team. If you are seeing unstyled or visually broken pages after an OTTO sync, please contact our support team so it can be investigated. Because these issues may require backend investigation, it is helpful to have the following ready when you reach out: - The affected page URL(s) - A description of the visual change (e.g. missing styles, removed image) - The approximate date and time the sync occurred - Any error messages or screenshots you can share Google Search Console (GSC) Connection Issues If you are experiencing problems connecting your Google Search Console account within Search Atlas, this typically requires investigation by our support team, as GSC connection issues can involve backend authentication or account configuration factors. When reaching out for help, please have the following ready: - Your Search Atlas project name or domain - The exact error message you see when attempting to connect GSC - The Google account email associated with your GSC property - The timestamp or date when the issue first occurred If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔄 Refresh OTTO SEO Audit After Fixing H1 Errors

Overview After you fix H1 heading errors on your website — such as duplicate H1 tags caused by a page builder, lightbox plugin, or theme setting — OTTO SEO does not automatically update the audit results. You need to manually trigger a new scan so the platform can re-evaluate your pages and clear any resolved issues. This article explains what to do and what to have ready if you need support. Why Duplicate H1 Errors Appear A duplicate H1 error means OTTO detected more than one H1 tag on a single page. Common causes include: - Lightbox overlays — some lightbox implementations inject a hidden H1 into the page HTML, creating a second H1 alongside your main heading. - Page builder blocks or templates — certain blocks or templates add heading tags outside the main content area. - Theme header templates — certain themes render the site name or tagline as an H1 in addition to the post title. Once you have identified and removed the duplicate H1 — for example, by editing the lightbox template or adjusting your theme settings — you are ready to refresh the audit. How to Re-Run Your OTTO SEO Audit Because the exact button labels and navigation paths in the OTTO SEO interface may vary by account or platform version, the general process is: 1. Log in to your Search Atlas account and open the OTTO SEO section of the platform. 2. Locate the site you fixed. 3. Look for an option to trigger a new crawl or re-scan — this is typically a button or action available from your site's audit or dashboard view. 4. Initiate the scan and wait for it to complete. Scan time varies based on site size. 5. Once the scan finishes, open the updated audit report for that site and review the Headings section to confirm the duplicate H1 errors are no longer flagged. If you are unsure which button or option starts the rescan in your account, our support team can walk you through the exact steps for your current interface. Confirming the Fix Worked After the scan completes, open the audit report for the relevant site and look for the Headings category. If the fix was applied correctly, the duplicate H1 issue will no longer appear for the affected pages. If the error still shows, double-check the following: - The page builder or plugin change was saved and published — not just previewed. - Your site cache has been cleared so OTTO crawls the live version of the page. - No other theme, plugin, or widget is injecting an additional H1 on the same page. Tips for Avoiding H1 Errors in the Future - Audit after every major design change. Any time you add a new page builder block, lightbox, or template, run a fresh OTTO scan to catch new heading conflicts early. - Keep one H1 per page. Every page should have exactly one H1 tag. Use H2 and lower-level headings for subheadings and section titles. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔄 Trigger a Fresh OTTO SEO Recrawl

🚀 How to Trigger a Fresh Recrawl If you need to run a new crawl of your connected site in OTTO SEO, navigate to OTTO SEO in the left sidebar and look for the crawl or scan option within the dashboard. Trigger a new scan and allow it time to complete — crawl duration will vary depending on your site's size. 🔍 Checking Crawl Status After triggering a scan, monitor the OTTO SEO dashboard for updates to your crawl results. If results do not appear to have refreshed, allow additional time for the scan to finish before triggering another one. ⚠️ Why Does a 'Page Modifications Need Attention' Warning Persist? If a warning continues to appear after running a new scan, consider the following: - The fix may not yet be live on your site. OTTO SEO evaluates the current live state of your pages. If a recommended change has not been published, the warning may remain after subsequent scans. - A previous scan may still be in progress. Avoid triggering multiple scans simultaneously, as this can cause results to appear stale. 🛠️ What to Have Ready If You Need to Escalate If the warning continues after running a fresh scan and confirming your changes are live, please have the following information ready before reaching out: - The name of the affected project or connected site - The specific warning message you are seeing - The URL of the affected page - The timestamp of your most recent scan If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 SEO Score vs Content Score: Location, Differences, and Troubleshooting

Overview Search Atlas uses two distinct scoring systems to help you evaluate and improve your content: the Content Score and the SEO Score. Although they sound similar, they measure different things and appear in different parts of the platform. Not all users can see both scores by default. If you can see one but not the other, this article explains why and what to do next. What Is the Content Score? The Content Score measures how well your article is written from a content-quality perspective. - Where it appears: Inside the Content Editor (also called the Article Editor). Open or create a document in the Content Editor and the Content Score will be displayed within that editor view. - Who can see it: The Content Score is available to all users who have access to the Content Editor, regardless of subscription tier. What Is the SEO Score? The SEO Score is a broader, site-level metric that reflects the overall SEO health of a page or website based on audit and scan data. - Where it appears: The SEO Score is associated with the OTTO SEO feature. It becomes visible once you have an active OTTO SEO project with completed scan data. - Who can see it: The SEO Score is only visible if your subscription plan includes OTTO SEO and you have an active, connected project with scan data available. Why You Can See Content Score but Not SEO Score Because the two scores live in completely separate parts of the platform and depend on different features, it is entirely normal to see one without the other. The most likely reasons you cannot see the SEO Score are listed below. - Your plan does not include OTTO SEO. The Content Editor and Content Score are available on lower-tier plans, while OTTO SEO and its SEO Score require a plan that includes the OTTO SEO module. Check your current plan and consider upgrading if you need access to the SEO Score. - You have not created an OTTO SEO project yet. Even if your plan includes OTTO SEO, the SEO Score will not appear until you create a project and connect it to your site. - No scan has been completed. The SEO Score is generated from crawl and audit data. If a scan has not finished, no score will be displayed. Ensure a scan has been run and completed for your project. - Feature rollout status. The SEO Score feature is part of an ongoing rollout. Some workspaces may not yet have access even if their plan includes OTTO SEO. In this case, you will need to contact support to confirm your workspace's access status. Steps to Take If Your SEO Score Is Missing 1. Confirm that your current subscription plan includes the OTTO SEO module. You can review your plan details in your account settings. 2. If OTTO SEO is included in your plan, navigate to the OTTO SEO section and ensure you have created a project connected to your site. 3. Check whether a crawl or audit scan has been completed for your project. If not, initiate a scan and wait for it to finish before expecting the SEO Score to appear. 4. If your plan includes OTTO SEO, your project is set up, and a scan has completed but the SEO Score is still not visible, your workspace may not yet have access due to the ongoing feature rollout. Contact support with your project name and workspace details to confirm your access status. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Purge Ghost Routes and Rebuild

🧭 What this process removes A backend purge removes unwanted ghost, orphaned, staging, and corrupted routes from the website data and cache layers. This can include duplicate URL variants, encoded characters, outdated imported pages, and routes that no longer belong to the current site. A clean rebuild then recreates the website using the approved pages and settings. This helps prevent removed routes from returning after publishing or cache refreshes. 🔎 Prepare the route list 1. Collect every unwanted URL and variant in one list. 2. Include differences in capitalization, trailing slashes, query parameters, encoded characters, and alternate paths. 3. Mark each route as ghost, orphaned, staging, corrupted, or otherwise invalid. 4. Confirm which pages and assets must remain live. Include the complete URL, not only the visible page name. Encoding garbage and duplicate variants can otherwise be missed during cleanup. 🧹 Request a backend purge Backend purge requests are handled by the Search Atlas team because they can affect stored site data, cache layers, and published content. Provide the complete route list and clearly request both actions: purge the invalid routes and start a clean rebuild. Do not repeatedly republish while the purge is being processed. New publishing activity can recreate routes or make verification harder. 🏗️ Start the clean rebuild After the purge is confirmed, open Website Studio from the left sidebar. Review the remaining pages and site settings, then use the appropriate site workflow, such as Import Site or Generate PPC Site. Submit the rebuilt site only after confirming that unwanted routes are excluded. Publishing and cache cleanup are separate steps. A page may appear unchanged temporarily if a browser, edge, or website cache still contains an older version. ✅ Verify the result 1. Check the previously invalid URLs and all listed variants. 2. Confirm that valid pages still load and that removed routes no longer resolve to published content. 3. Refresh the relevant report data from Reports in the left sidebar, then review the updated results. 4. Test again after cache propagation is complete, using a private browser window when possible. If a removed route returns, capture the exact URL, when it returned, and the action that preceded it. This information helps identify whether the route was recreated by an import, republish, redirect, or external cache. 💡 Prevent routes from returning - Use one approved source of truth for pages and imports. - Remove obsolete pages from the source before rebuilding. - Keep staging and production content separate. - Review redirects, internal links, sitemaps, and integrations for references to deleted routes. - Allow each purge or rebuild to finish before starting another publish action. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛡️ Disconnect OTTO Projects Without Losing Rankings

🧭 Overview When you no longer need an active OTTO SEO project, it is natural to want to remove it from your workspace. However, simply deleting a project can strip away optimizations that are actively supporting your rankings. This article explains why deletion can be risky and walks you through the recommended safe disconnection process for an OTTO project. ⚠️ Why Deletion Can Damage Your Rankings Deleting an OTTO project does more than tidy up your dashboard — it can reverse the SEO work OTTO has deployed on your site. Here is what you risk when you delete rather than pause or freeze a project: - Reversal of applied optimizations: On-page changes, schema markup, and other deployments may be rolled back. - Loss of project data: All historical data, audit results, and configurations are permanently removed and cannot be recovered. - Ranking drops: Pages that were benefiting from OTTO's active optimizations may lose their positions in search results. To avoid these outcomes, the recommended approach is to pause or freeze the project rather than deleting it. ❄️ What Does Pausing or Freezing a Project Do? Pausing or freezing an OTTO project stops active automation without removing any of the optimizations already applied to your site. This means: - Your existing rankings and deployed changes are preserved. - All project data, history, and settings remain intact. - No new changes are pushed to your site. - You can reactivate the project at any time without losing progress. This is the safest way to disconnect from OTTO when you are unsure about the future of a project or want to stop activity without risking ranking loss. 🔢 How to Safely Disconnect an OTTO Project 1. In the left sidebar, click OTTO SEO → All Sites (SEO Automation) to open the main OTTO SEO dashboard. 2. Locate the project you want to disconnect from the list of active projects. 3. Look for the option to pause or freeze the project within that project's settings or management controls. 4. Select the pause or freeze option and confirm the action when prompted. The project will move to an inactive state, pausing all active automation. 5. Verify that the project now appears in the Deep Frozen tab of the All Sites (SEO Automation) page. Your site's optimizations remain live and your rankings are protected. The project is now safely disconnected from active automation. 🔄 How to Reactivate a Paused Project If you decide to resume OTTO automation in the future, reactivating a paused project is straightforward: 1. Go to OTTO SEO → All Sites (SEO Automation) in the left sidebar. 2. Find your paused project in the Deep Frozen tab of the All Sites (SEO Automation) page. 3. Select the option to reactivate or unfreeze the project and confirm when prompted. 4. OTTO will resume automation from where it left off, with all previous data and settings intact. If you are unsure which option to choose, or if you do not see a pause or freeze option for your project, reach out to our support team before deleting — a team member can confirm the safest path forward for your specific setup. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛡️ Recover Your Site After a Spam Attack

🚨 What Is a Content Injection Attack? A content injection attack happens when a malicious actor gains access to your website and inserts unwanted content — such as gambling keywords, adult links, or spammy pages — directly into your site files, database, or CMS. These injections are designed to manipulate search rankings and redirect your visitors. Acting quickly is essential to protect your SEO authority and user trust. 🔍 Step 1: Identify the Scope of the Damage Before cleaning anything, understand exactly what was affected. - Search site:yourdomain.com casino OR gambling OR poker in Google to surface injected pages indexed by search engines. - Check your Google Search Console account under Security & Manual Actions for any manual penalties or security notices. - Review your server access logs for unusual file modifications or unfamiliar IP addresses during the suspected attack window. - Use Search Atlas's On-Page Audit (Left sidebar → Content → On-Page Audit) to scan your key pages for unexpected keyword signals or content anomalies. 🔒 Step 2: Secure the Entry Point Immediately Cleaning injected content without closing the vulnerability means attackers can re-inject. Complete these security steps first. 1. Change all admin, FTP, database, and hosting passwords immediately. 2. Revoke any unfamiliar user accounts or API keys from your CMS and hosting panel. 3. Update your CMS core, all plugins, and themes to their latest versions — outdated software is the most common entry point. 4. Install or reconfigure a Web Application Firewall (WAF) such as Cloudflare or Wordfence to block further intrusions. 5. Contact your hosting provider and ask them to confirm whether server-level files were modified. 🧹 Step 3: Remove Injected Content With the entry point secured, begin the cleanup process. 1. Restore from a clean backup if you have one dated before the attack. This is the fastest and safest option. 2. If no clean backup exists, manually audit your CMS pages, posts, templates, and widget areas for injected text, hidden links, or base64-encoded scripts. 3. Check your database for injected rows — look specifically in post content, meta fields, and options tables for gambling-related strings. 4. Scan your server file system for recently modified PHP or JavaScript files that were not part of a legitimate update. 5. Remove or replace every infected file and database entry. Do not simply edit over injected code — verify the entire block is clean. 📊 Step 4: Audit and Restore Your SEO Content Once the site is clean, use Search Atlas to assess SEO damage and rebuild content health. - Run an On-Page Audit (Left sidebar → Content → On-Page Audit) on your highest-traffic pages to confirm that injected keywords no longer appear in titles, meta descriptions, or body content. - Use the Meta Generator (Left sidebar → Content → Meta Generator) to rewrite any titles or descriptions that were corrupted or replaced by the attack. - Check your Topical Maps (Left sidebar → Content → Topical Maps) to identify whether the attack created topical dilution — content that now ranks your site for irrelevant gambling topics instead of your core subject matter. - Use the Content Planner (Left sidebar → Content → Content Planner) to prioritise rebuilding or strengthening the pages most harmed by the injection. 🚀 Step 5: Request Google Reconsideration (If Penalised) If Google issued a manual action against your site, you must formally request a review after cleanup is complete. 1. Log in to Google Search Console and navigate to Security & Manual Actions → Manual Actions. 2. Verify that all injected content has been removed and your site is fully secured. 3. Click Request Review and provide a clear summary of: what happened, what you removed, and what security measures you put in place. 4. Google typically responds within a few days to a few weeks. Monitor Search Console for the status update. 💡 Step 6: Prevent Future Attacks Strong ongoing hygiene reduces your risk of repeat incidents. - Schedule automated daily or weekly backups stored off-server so you always have a clean restore point. - Enable two-factor authentication (2FA) on all CMS, hosting, and domain registrar accounts. - Conduct regular security scans using a trusted malware scanner. - Audit user account permissions every quarter and remove anyone who no longer needs access. - Use Search Atlas's On-Page Audit monthly to spot unexpected content changes early, before they cause SEO damage. 🛠️ Need Additional Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 Fix OTTO Auto-Changing Root Domain to Subdomain

🔍 Overview When setting up an OTTO SEO project, the platform may automatically detect and pre-fill a subdomain (for example, services.yourdomain.com) instead of your root domain (yourdomain.com). This is a known bug that has been reported during OTTO project setup. This article explains what to expect and what information to have ready so our team can resolve this for you quickly. ⚙️ What Is Happening During OTTO project creation, the platform may automatically select a subdomain rather than the root domain you intended to use. This is not the expected behavior and requires a backend correction by our support team. There are no self-serve steps that reliably resolve this issue on your own. ⚠️ What to Do Because this issue requires action on the backend, please contact our support team as soon as you notice the domain has been set incorrectly. To help us resolve this as quickly as possible, please have the following information ready when you reach out: - Your OTTO project name as it appears in the platform. - The subdomain that was auto-detected (for example, services.yourdomain.com). - The correct root domain you want the project to use (for example, yourdomain.com). - The approximate date and time the project was created or when you first noticed the incorrect domain. Do not continue configuring the OTTO project with the incorrect domain in place, as this may affect the accuracy of your SEO data and recommendations. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Bulk Editing FAQ Issues in OTTO SEO

Overview If your site has many FAQ-related issues flagged across multiple pages, working through them one by one can feel slow. This article explains what bulk editing capabilities currently exist in OTTO SEO, what does not exist, how plan limitations may affect your options, and practical tips to move faster within the current interface. What Does Not Exist — Setting the Record Straight To avoid confusion, the following features are not available in OTTO SEO at this time: - A bulk deploy workflow that pushes all FAQ answers at once - A single-click button that auto-populates and deploys every FAQ issue simultaneously - A dedicated FAQ table review screen that loads all issues before the editing modal opens If you were previously told any of these options exist, we apologise for the confusion. The information was incorrect. What You Can Actually Do Today Within the current OTTO SEO interface, you can work through FAQ-type issues by opening each flagged item individually, reviewing any suggested answer, editing if needed, and deploying one item at a time. You may also be able to filter issues by category to help isolate a specific type of FAQ issue and work through a more focused batch. Contact our team for guidance on the exact steps available in your account. Plan Limitations and FAQ Editing The scope of FAQ issue detection and the volume of issues surfaced in OTTO SEO may vary depending on your current plan. If you find that certain audit categories are unavailable, that issue counts appear capped, or that specific editing features are not accessible in your account, this may be related to your plan tier. To understand exactly which features and issue types are included in your plan, review your account settings or reach out to our team for a plan comparison. Practical Tips to Work Faster While true bulk editing is not available, these habits can help reduce the time you spend per issue: 1. Prioritise by page impact first. Focus on pages with the highest number of flagged issues before moving to lower-priority pages. 2. Accept suggestions when they are accurate. If a suggested answer looks correct, accepting it without editing is the fastest path through the queue. 3. Keep your business information current. The more complete and up-to-date your account's business details are, the better any generated suggestions tend to be, reducing the need to manually rewrite answers. 4. Work in focused sessions by issue type. Isolate one issue type at a time to avoid context-switching and move through a batch more efficiently. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 OTTO SEO Project Showing No Issues Found

🧭 Overview After creating a new OTTO SEO project, you may notice that all on-page optimization categories display "No issues found" with zero recommendations. This is a known processing issue that can affect newly created projects and does not mean your site is fully optimized. This article explains why it happens and what to have ready when contacting support. ⚠️ Why This Happens There are a few possible reasons your OTTO SEO project may return no issues or recommendations: - Analysis did not complete correctly: In some cases, OTTO begins processing a project but fails to return analysis results, even when your site has been detected in Site Audit and is correctly whitelisted. - Project is still initializing: Newly created projects sometimes need additional time to fully process before recommendations appear. - Data did not load in the background: OTTO may display a success message for certain categories while no actual project data is loaded in the background. 🛠️ Steps to Try Before Escalating 1. Wait and refresh: If your project was created recently, give it some additional time to process and then refresh the page to check if recommendations have populated. 2. Verify your Site Audit is active: OTTO relies on Site Audit data to generate recommendations. Confirm that a Site Audit has been run for the same domain and that crawl results are available. 3. Check that your domain is whitelisted: Inside OTTO SEO → Site Audit → All Audits (Site Audit) via the 'How to Whitelist our Crawler?' link, confirm the correct domain is connected and whitelisted. A misconfigured domain can prevent analysis from running. 4. Clear your browser cache: Occasionally, a cached page state can display outdated results. Clear your cache and reload the OTTO SEO dashboard. ✅ What a Healthy OTTO Project Looks Like Once OTTO has successfully analyzed your site, you should see: - A non-zero page count listed in your project overview - Categorized on-page recommendations such as title tag issues, meta descriptions, heading structure, and more - An accurate count of issues per category with actionable suggestions 📋 What to Have Ready When Escalating If your project still shows zero pages and no recommendations across every category after following the steps above, the issue will need to be investigated by our backend team. Please have the following ready: - The exact name of the affected OTTO SEO project - The domain associated with the project - Any error messages or status messages displayed in the project dashboard - The approximate date and time the project was created or last processed If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Resolve Unusable Publication Sites

🔍 Why publication stops A Zia Tile article can remain unassigned when its selected site is no longer usable. Common reasons include no active publication, a non-US publication, a farm-listed domain, or a failed validation rule. The assigner does not automatically replace a site selected in Publication Notes. This prevents Search Atlas from changing your publishing decision without approval. The article is therefore skipped during each hourly assignment run until a replacement is chosen. 📋 What the replacement options mean Suggested sites come from the same assignment engine used for normal placement. Each option meets the applicable requirements, including: - The minimum ordered DA - DR and organic traffic requirements - The 2.5x price limit compared with the ordered DA - QP quality requirements - Your account’s rejection history Options may have a DA above the ordered range. This is expected: the price limit is the effective ceiling, and additional authority can be beneficial. Sites are listed from least used to most used where possible. Topic evidence shown beside a site is a preference signal, not a requirement. It is based on reviewing the site’s existing article titles. ✅ How to resolve the articles 1. Review each article with an unusable current pin. 2. Compare the suggested domains, DA, price, prior usage, and topic evidence. 3. Choose one option for every article, or suggest another suitable site. 4. Provide the article ID and your choice, such as 200586 → 2. 5. Wait for the approved reassignment and updated Publication Note before the next assignment run. For multiple orders, include the order number and article ID to avoid confusion. You can choose different sites for different articles, even when they share the same order. 🔁 What happens after approval After your choices are confirmed, the articles are reassigned and their Publication Notes are updated. This prevents the hourly cron or cascade process from moving them again. Articles should then become eligible for normal placement, provided the replacement site remains active and passes validation. 💡 Prevent future delays - Review Publication Notes before submitting or pinning an article. - Avoid selecting sites without an active publication. - Confirm that the publication is US-based when that rule applies. - Recheck saved sites if an article remains unassigned across multiple runs. - Respond with one clear replacement choice per article. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Fix a Quest LLM Digital PR Campaign Stuck on Paused

🧭 Overview If your Quest LLM Digital PR campaign has been sitting on Paused even after you've confirmed your credits are available, a common cause is that no contacts have been selected for the campaign. Without at least one contact assigned, the platform has no recipients to send outreach to, which can prevent the campaign from activating. This article explains why this happens and what you need to do to get your campaign running. 🔎 Why Does This Happen? A Quest LLM Digital PR campaign requires contacts to be selected before it can move out of a Paused state. Credits and configuration may be set up correctly, but if no contacts have been added as recipients, the campaign may not be able to proceed. This step is easy to overlook if the campaign was saved before contacts were added. ✅ How to Resolve It To get your campaign out of the paused state, you need to ensure at least one contact is selected for the campaign. Here is what to do: 1. Open your Quest LLM Digital PR campaign in the platform. 2. Check whether any contacts have been added as recipients. If none are present, this may be the cause of the paused status. 3. Add the contacts you want to include in this outreach campaign. 4. Once contacts have been selected, the campaign should be able to proceed out of the paused state. If you have added contacts and your campaign remains stuck on Paused, or if you are unsure how to locate the contact selection area in your account, please use the chat widget at the bottom of this page to reach our support team and we will be happy to walk you through it.

🔍 Where Are Otto SEO Changes Deployed?

When Otto SEO applies fixes to your website, those changes are not written directly into your site's source code files. Instead, the fixes are deployed through the Otto pixel, a JavaScript snippet that is installed on your site. Otto injects the changes dynamically via HTML using client-side rendering, meaning the fixes are applied in the browser when the page loads. This approach allows Otto to deploy optimizations quickly without requiring direct access to your CMS or codebase. How to verify that Otto's changes are live on your page: - Step 1: Copy the fix that Otto has suggested for a specific item. - Step 2: Open the URL listed on that same line in your browser. - Step 3: Right-click anywhere on the page to open the context menu. - Step 4: Select Inspect to open your browser's developer tools. - Step 5: Use Ctrl + F (Windows) or Command + F (Mac) within the inspector panel, then paste the fix you copied in Step 1 to search for it in the rendered HTML. If the fix appears in the inspected HTML, Otto is working correctly and the change has been successfully injected on that page. Keep in mind that because Otto uses client-side rendering, the fix may not appear if you simply view the raw page source (using "View Page Source"), since that only shows the original HTML before JavaScript runs. If you are unable to locate a deployed fix or have questions about your Otto pixel installation, please use the in-app live chat widget to chat with a human teammate.

🔌 Stop OTTO From Changing Canonical Tags in WordPress

🧭 Overview If OTTO has changed the canonical tag on one of your WordPress pages and you want to stop it, this article explains how canonical changes work in the Search Atlas WordPress plugin and the ways to stop them. Important: There is no "Dynamic SEO" toggle and no plugin setting that turns off OTTO's canonical changes for the whole site. Canonical changes are controlled per page, as described below. 🔍 How OTTO Changes Canonical Tags OTTO only changes a canonical tag when it has a canonical recommendation deployed for that page. When it does, OTTO updates the address in the page's existing canonical tag to the recommended one. Pages without a deployed canonical recommendation are not changed. 🛑 How to Stop OTTO Changing a Canonical Tag Use whichever option fits your situation: 1. Undeploy the canonical recommendation in Search Atlas. Open your OTTO project in Search Atlas, find the canonical recommendation for the affected page, and undeploy or remove it. This is the supported way to stop OTTO's canonical change for that page. 2. Set a manual canonical for the page. A valid canonical you set manually for a page takes priority over OTTO's recommendation, so OTTO will leave it unchanged. 3. Turn OTTO off for a single page. While logged in to WordPress, open the page on your live site and use the OTTO frontend toolbar to disable OTTO for that page. ✅ How to Confirm It Worked - In WordPress, go to Search Atlas → Settings and use Clear Page Cache (or Clear all cache). If you also use a caching plugin such as WP Rocket, clear its cache too. - Reload the page and view its source (Ctrl+U or Cmd+U). The canonical tag in the <head> should now show the address you expect. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ How BrandVault Changes Affect AB

🔍 Understanding BrandVault and AB Not every change in BrandVault can break or affect AB. BrandVault stores brand information that some Search Atlas features may use, while AB only responds when a changed field is part of its workflow. ✅ Changes that usually do not affect AB - Updating unrelated brand details that AB does not use. - Changing the order of information without changing its meaning. - Editing internal organization, labels, or project settings. - Adding knowledge that is not selected or referenced by the AB process. ⚠️ Changes that may affect AB AB may produce different results when a BrandVault update changes information it uses as an input. Examples can include changes to core brand instructions, business descriptions, target audiences, writing preferences, approved messaging, links, or visual brand data used by the workflow. The impact depends on the AB feature, the specific BrandVault field, and whether the updated information is included when AB runs. A BrandVault update alone does not automatically mean AB is broken. 🧭 How to check whether AB was affected 1. Note the exact BrandVault field or content that changed. 2. Identify the AB project, task, or output where the difference appeared. 3. Compare a result created before the BrandVault update with one created afterward. 4. Check whether the changed information is expected to guide that AB workflow. 5. Run the task again after confirming the intended BrandVault content and compare the results. 🛠️ Recommended troubleshooting - Restore the intended BrandVault value if the change was accidental. - Make brand instructions clear, specific, and consistent. - Check links and source information for accuracy and relevance. - Allow for normal variation between generated results; a different result does not necessarily indicate a failure. - Record the BrandVault change, AB project, task time, and affected output if the issue continues. 📌 Key takeaway BrandVault changes should be reviewed based on whether AB uses the changed information. Avoid treating every BrandVault update as an AB-breaking change. Focus on the connection between the specific field, the AB workflow, and the observed result. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Locate and Remove Duplicate OTTO JavaScript

🧩 Why This Message Appears When you install the OTTO WordPress plugin, it automatically adds the OTTO JavaScript snippet to your site. If you previously added the snippet manually — for example, by pasting it into your theme files or a header/footer plugin — both versions run at the same time. Search Atlas detects this conflict and warns you to remove the duplicate so OTTO can work correctly. ✅ Before You Start Confirm which method you want to use going forward. The OTTO WordPress plugin is the recommended approach because it manages the script automatically. You only need to remove any manually added copies of the script. Do not uninstall the plugin itself. 🔎 Step 1: Check Your Theme's Header and Footer Files The most common place a manual script is added is directly inside a theme file. 1. Log in to your WordPress admin dashboard. 2. Go to Appearance → Theme File Editor (or Theme Editor). 3. In the file list on the right, open header.php. 4. Use your browser's find function (Ctrl + F or Cmd + F) and search for otto or searchatlas. 5. If you find a script tag containing the OTTO snippet, delete the entire script tag. 6. Click Update File to save. 7. Repeat this check for footer.php. 🔎 Step 2: Check Header/Footer Plugins If you use a plugin to inject code site-wide, the duplicate script may be stored there. 1. In your WordPress dashboard, go to Plugins → Installed Plugins. 2. Look for plugins such as Insert Headers and Footers, WPCode, Header Footer Code Manager, or any similar tool. 3. Open the plugin's settings and search each code snippet for the OTTO script tag. 4. Delete any snippet that contains the OTTO JavaScript and save your changes. 🔎 Step 3: Check Your Page Builder or Theme Options Many themes and page builders include a custom code or scripts section. 1. Go to Appearance → Customize and look for a section called Additional CSS, Custom Code, or Scripts. 2. Search for any OTTO script tag and remove it, then publish your changes. 3. If you use a page builder such as Elementor, Divi, or Beaver Builder, open the builder's global settings or site settings and check for a header or footer scripts field. Remove the OTTO snippet if present and save. 🔎 Step 4: Check Individual Pages and Posts The script may have been added to a specific page rather than site-wide. 1. In WordPress, go to Pages or Posts. 2. Open pages one at a time and switch to the Code Editor view (click the three-dot menu in the block editor, then select Code Editor). 3. Search the source for the OTTO script tag and delete it if found, then update the page. 4. Focus first on high-traffic pages and your homepage. ✔️ Step 5: Verify the Duplicate Has Been Removed After removing the script from all locations above, confirm the conflict is resolved inside Search Atlas. 1. In the left sidebar, go to OTTO SEO → All Sites (SEO Automation). 2. Open the OTTO dashboard for your site. 3. Check whether the duplicate JavaScript warning has cleared. It may take a few minutes to update. 4. If the warning is still showing, right-click your website in a browser, select View Page Source, and search for otto. Count how many times the script tag appears. There should be exactly one instance, loaded by the plugin. If you still see two instances, return to the steps above and check any location you may have missed. ⚠️ Common Reasons the Script Is Hard to Find - Child theme files: If you use a child theme, check both the child theme and the parent theme files. - Caching plugins: A caching plugin may serve an old version of your page. Clear your site cache after making any changes. - Multiple snippet plugins: You may have more than one code injection plugin installed. Check all of them. - Deactivated plugins still storing code: Some plugins retain saved snippets even when deactivated. Reactivate them briefly to check and delete any stored OTTO code, then deactivate again. 💬 Still Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔄 Re-Engage OTTO SEO After Disengagement

What Does "Disengaged" Mean? When OTTO SEO is disengaged, the AI pauses all automation and you lose the ability to approve, apply, or interact with any recommended changes. This is a manual state — nothing is broken. You simply need to re-engage OTTO to restore full functionality. How to Re-Engage OTTO SEO To re-engage OTTO SEO, navigate to OTTO SEO → All Sites (SEO Automation) and look for the option to engage or activate OTTO for your project. Once you trigger the re-engagement action, OTTO SEO should return to an active state and your controls for approving and applying changes will become available again. If you are unsure where to find the re-engagement option, or if the option does not appear to be available in your account, please reach out to our support team directly — they can guide you through the exact steps for your account configuration. What to Have Ready When Escalating If re-engagement does not work or the option is not visible, please have the following information ready before contacting support: - The name of the OTTO project that is showing as disengaged - Your account or workspace name - A description of what you see on screen (e.g., whether any engage/activate button is visible) - Any error messages displayed - The approximate time you first noticed the disengaged status If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Remove OTTO-Inserted Links From Your Website

🔍 What Are OTTO-Inserted Links? When the OTTO pixel is active on your website, OTTO SEO automatically implements on-page optimizations — including inserting internal or external links to improve your site's SEO performance. These links are added based on OTTO's recommendations and are designed to strengthen your content's relevance and authority. Occasionally, a link may no longer be relevant, may point to a broken URL, or may have been inserted on a page where you did not expect it. This article explains how to locate and remove those links quickly. ⚙️ How OTTO Inserts Links OTTO applies SEO changes — including link insertions — through the pixel installed on your site. All changes made by OTTO are logged and manageable from within the OTTO SEO V3 dashboard. You do not need to edit your site's code manually to undo them. 🚀 Step-by-Step: Remove an OTTO-Inserted Link 1. In the left sidebar, click OTTO SEO, then open SEO Automation (or navigate to /seo-automation-v3). 2. Select the website project where the unwanted link appears. 3. Open the Deployed Changes or Activity Log section to see a full list of optimizations OTTO has applied. 4. Use the search or filter options to find the specific page or link type you want to review. 5. Locate the link insertion entry for the affected page. 6. Click Revert or Undo next to that specific change to remove the link from your page immediately. 7. Verify the change by visiting the live page and confirming the link is no longer present. 💡 Tips for Managing OTTO Link Insertions - Review before deploying: OTTO presents recommendations before applying them. Review the suggested links in the Recommendations tab and approve or reject each one individually before deployment. - Use selective deployment: You can deploy changes page-by-page rather than applying all recommendations at once, giving you full control over what goes live. - Check for broken links regularly: If OTTO inserted a link to a URL that has since changed or been removed, revert the change and let OTTO generate an updated recommendation. - Pause OTTO on specific pages: If there are pages where you do not want OTTO to make any changes, you can exclude them from automation in your project settings. 🛠️ What If the Link Is Not Showing in the Activity Log? If you cannot find the inserted link in your OTTO activity log, it is possible the change was applied through a manual edit in Website Studio. In that case: 1. In the left sidebar, click Website Studio (or navigate to /website-studio). 2. Open the page where the unwanted link appears. 3. Use the page editor to locate and delete the link directly. 4. Save and republish the page. 📊 Keeping Your Site Clean Going Forward To maintain full visibility over OTTO's activity and avoid unexpected changes: - Enable notification alerts in your project settings so you are informed each time OTTO deploys a change. - Schedule a regular review of your Deployed Changes log — weekly or after each major OTTO session. - Only deploy OTTO recommendations in bulk when you have reviewed them in the recommendations panel first. 💬 Still Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⏱️ OTTO Deployment Timing and UI Update Delays

🔍 Overview When you deploy optimizations through OTTO SEO, changes are processed in stages — from Search Atlas sending instructions to your site, through to your CMS applying them and the OTTO UI reflecting the results. Understanding this pipeline helps set the right expectations and avoid unnecessary concern when updates don't appear instantly. ⏳ How Long Do Deployments Take? Deployment times vary depending on several factors, but here are the general benchmarks to keep in mind: - Initial deployment trigger: OTTO sends instructions to your site within seconds of you clicking Deploy. - CMS processing time: Your CMS (e.g. WordPress) typically applies changes within 1 to 5 minutes, depending on server speed, plugin load, and site size. - OTTO UI refresh: After your site processes the changes, the OTTO dashboard may take an additional 5 to 15 minutes to reflect the updated deployment status. - Full propagation: In some cases — particularly for larger sites or sites with caching layers — the complete cycle can take up to 30 minutes. If it has been fewer than 30 minutes since you deployed, the process may still be running normally in the background. 🔄 Why Hasn't My Deployment Updated After 10 Minutes? Seeing no change after 10 minutes is common and usually not a sign that something has gone wrong. Here are the most frequent reasons for a delay at this stage: - Caching plugins: Tools like WP Rocket, W3 Total Cache, or server-level caches can prevent freshly deployed changes from appearing immediately. OTTO may have applied the update, but the cached version of your page is still being served. - CDN propagation: If your site uses a CDN such as Cloudflare, updated content may take extra time to propagate across all edge nodes. - Server response delays: Slow or overloaded hosting environments can stall the handshake between Search Atlas and your CMS. - UI polling interval: The OTTO dashboard does not update in real time. It checks for status changes on a scheduled interval, so there is always a short lag between when your site updates and when OTTO reflects it. ✅ What to Check Before Escalating Before reaching out to support, run through these quick checks: 1. Wait the full 30 minutes from the time you clicked Deploy. 2. Go to Left sidebar → OTTO SEO → SEO Automation (URL: /seo-automation-v3) and hard-refresh the page (Ctrl + Shift + R on Windows, Cmd + Shift + R on Mac) to force the UI to reload the latest status. 3. If you use a caching plugin, purge your site cache and check whether the deployed changes now appear on the live page. 4. If your site uses Cloudflare or another CDN, purge the CDN cache for the affected URLs. 5. Check that your OTTO connection is still active by reviewing the site settings in the OTTO SEO section. A disconnected site will not receive deployments. ⚠️ When Something May Actually Be Wrong If more than 30 minutes have passed and none of the checks above resolved the issue, there may be a genuine problem worth investigating. Signs that a deployment has failed include: - The deployment status shows a persistent error or failed badge in the OTTO UI. - Changes are not visible on the live page even after clearing all caches. - The OTTO connection status shows as disconnected or inactive. In these cases, document the affected URL(s) and the approximate time you triggered the deployment before contacting support — this will help the team investigate faster. 💬 Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⏱️ OTTO Optimization: Understanding Metric Recovery After Bulk Changes

🔍 Overview After applying bulk optimizations through OTTO SEO, it is completely normal to observe a temporary decrease in keyword positions, impressions, and organic traffic. This does not mean something went wrong. Search engines need time to recrawl, reindex, and reassess your pages following significant on-page changes. Understanding this process will help you set realistic expectations and avoid making unnecessary rollback decisions that could disrupt long-term gains. 📉 Why Metrics Drop After Bulk OTTO Changes When OTTO applies bulk changes — such as updating title tags, meta descriptions, heading structures, internal links, or content optimizations across many pages at once — search engines treat these as new signals that require fresh evaluation. Several factors contribute to the temporary dip you may be seeing: - Recrawl delay: Googlebot and other crawlers do not revisit all changed pages instantly. Depending on your site's crawl budget and authority, it can take days to weeks for all updated pages to be recrawled. - Reindexing lag: Once a page is crawled, it must be processed and reindexed before updated rankings are reflected in search results or tracking tools. - Ranking volatility: Search engines temporarily fluctuate rankings while they assess whether the new signals improve or maintain relevance for target queries. - Data reporting delay: Tools like Google Search Console often reflect data with a 2–3 day lag, meaning drops you see today may actually represent activity from several days ago. ⏳ Typical Recovery Timeline Recovery timelines vary depending on the scale of changes, your site's crawl frequency, and your domain authority. The following is a general guide: 1. Days 1–7: Initial volatility is most pronounced. Keyword positions may fluctuate significantly and impressions may dip as search engines begin recrawling changed pages. This is expected and does not indicate a problem. 2. Days 7–21: The majority of changed pages will have been recrawled and reindexed for most sites with regular crawl schedules. You should begin to see stabilization during this window. 3. Days 21–45: Full recovery and improvement are typically visible within this range. Pages that received high-quality optimizations often surpass their pre-change performance by the end of this period. 4. Beyond 45 days: If significant recovery has not occurred, this may indicate a more specific issue worth investigating, such as crawl budget constraints, indexing errors, or conflicting directives on certain pages. Note: Sites with lower domain authority or infrequent crawl schedules may experience longer timelines, while high-authority sites with frequent crawl cycles often recover more quickly. 📊 How to Monitor Recovery in Search Atlas You can actively track your site's recovery progress using the Site Explorer section of Search Atlas. Here is how to navigate to the most relevant data: - Keyword position trends: Go to Left sidebar → Keywords → Rank Tracker. Use the search and filter tools to isolate the keywords most affected by your OTTO changes and monitor their position trajectory over time. - Organic traffic and impressions: Go to Left sidebar → Site Metrics → Overview (Site Explorer) and review the Organic Research data. This gives you a high-level view of traffic and impression trends across the site. - Page-level performance: Go to Left sidebar → Site Metrics → Pages to identify which specific pages are recovering, which are stable, and which may need additional attention. - AI Visibility score: Go to Left sidebar → Authority → QUEST AI Visibility (check current sidebar labeling) to monitor how your site's presence in AI-generated search results is trending alongside traditional metrics. It is recommended to check these metrics on a weekly basis rather than daily during the recovery window to avoid reacting to normal short-term fluctuations. ✅ Best Practices to Support Faster Recovery While the recovery process is largely driven by search engine behavior, there are steps you can take to support it: - Submit updated URLs to Google Search Console: Manually requesting indexing for your most important changed pages can accelerate the recrawl process for those URLs. - Avoid making additional bulk changes during recovery: Stacking multiple rounds of bulk changes can reset the evaluation window and extend the time it takes for rankings to stabilize. - Review your OTTO deployment in SEO Automation: Go to Left sidebar → OTTO SEO → All Sites (SEO Automation) to confirm all changes were deployed correctly and that no pages are showing errors or incomplete optimizations. - Do not roll back changes prematurely: Rolling back optimizations during the volatility window is one of the most common reasons sites fail to recover. Give the changes adequate time unless a confirmed technical error is identified. - Ensure your sitemap is up to date: An accurate XML sitemap helps search engines discover and prioritize recrawling of your recently updated pages. 🚩 When to Be Concerned Most metric drops following OTTO bulk changes are temporary and self-resolving. However, you should investigate further if you observe any of the following: - Rankings have not shown any recovery trend after 45 or more days - Specific pages have been completely dropped from the index (not just lower-ranked) - Google Search Console is reporting a sharp increase in crawl errors or coverage issues coinciding with the changes - Traffic has continued to decline steadily week over week beyond the 21-day mark with no stabilization In these cases, it is worth conducting a deeper technical audit using Left sidebar → Site Metrics → Pages and reviewing individual page statuses to identify any indexing or crawlability issues introduced during the optimization process. 💬 Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ OTTO Pixel on Webflow: Limitations & Cloudflare Workaround

🔍 Overview OTTO SEO applies on-page optimisations in two ways: source-level injection (changes written directly into the page's HTML source, as with WordPress and Shopify) and client-side injection (changes applied in the browser after the page loads, via the OTTO pixel JavaScript tag). Webflow currently supports only the client-side method, which comes with a set of limitations described below. ⚙️ How OTTO Works on Webflow When you install the OTTO pixel on a Webflow site, the pixel loads in the visitor's browser and applies SEO changes — such as meta titles, descriptions, and structured data — at render time. The raw HTML delivered by Webflow's servers is not modified. This is different from the WordPress and Shopify integrations, where OTTO injects changes directly into the page source before it is served to the browser or to search engine crawlers. ⚠️ Client-Side Limitations on Webflow - Crawler visibility: Some search engine crawlers and SEO audit tools that do not execute JavaScript may not see the changes OTTO applies. - Render dependency: Optimisations only appear after the pixel script has fully loaded and executed, which can introduce a brief delay. - No source-level changes: The underlying Webflow page source remains unchanged, so tools that inspect raw HTML will not reflect OTTO's updates. - Limited CMS field control: Dynamic content managed through Webflow CMS cannot be rewritten at the source level the way it can in WordPress or Shopify. 🗺️ Is a Source-Level Fix for Webflow on the Roadmap? The Search Atlas team is actively exploring deeper platform integrations, including rendering coverage improvements and migration paths for sites on hosted CMS platforms like Webflow. While a native source-level Webflow integration is not available today, it is part of ongoing product investigation. In the meantime, the Cloudflare Worker approach described below is the recommended solution for teams that need changes to land in the actual page content. 🚀 Cloudflare Worker: The Recommended Alternative If your Webflow site is proxied through Cloudflare, you can use a Cloudflare Worker to intercept HTTP responses and rewrite the HTML before it reaches the visitor's browser or a crawler. This effectively bridges the gap between client-side injection and source-level changes. At a high level, the Worker sits between Cloudflare's edge network and the visitor, fetching the original Webflow response and modifying the HTML — injecting OTTO's recommended tags and content — before delivering it. Prerequisites - Your domain is active on a Cloudflare account (Free plan or higher). - Webflow DNS is pointed to Cloudflare (orange-cloud / proxied mode enabled). - You have access to the Cloudflare Workers dashboard. High-Level Setup Steps 1. Log in to your Cloudflare dashboard and navigate to Workers & Pages. 2. Create a new Worker and paste in a transformation script that fetches your Webflow page, parses the HTML response, and injects the meta tags, structured data, or content changes recommended by OTTO. 3. Use the HTMLRewriter API built into Cloudflare Workers to target specific HTML elements (for example, <head> for meta tags) and apply your changes without loading a full DOM parser. 4. Add a Worker Route (for example, yourdomain.com/*) so the Worker intercepts all page requests. 5. Test the Worker using Cloudflare's preview tool and verify the output with a raw HTML inspection tool or a crawler simulator to confirm changes appear in the source. 6. Deploy the Worker and monitor for any performance impact using Cloudflare Analytics. Note: The OTTO pixel should remain installed on your Webflow site alongside the Cloudflare Worker. The Worker handles source-level changes; the pixel continues to manage any dynamic or JavaScript-dependent optimisations. 📊 Comparing Your Options - OTTO pixel only (default): Easy to set up; changes are browser-rendered. Best for sites where crawler JavaScript rendering is not a concern. - Cloudflare Worker + OTTO pixel: Changes land in the HTML source served at the edge. Best for teams that need full crawler visibility and parity with WordPress/Shopify behaviour. - Source-level CMS integration (WordPress, Shopify): Deepest level of control; changes are written directly into the page before delivery. Not yet available for Webflow. 💡 Tips & Best Practices - Always test your Cloudflare Worker in a staging environment or on a single URL route before rolling it out site-wide. - Keep Worker scripts lean — heavy transformations can add latency. Use HTMLRewriter rather than full HTML string replacements wherever possible. - Review OTTO's recommended changes in the OTTO SEO → Site Audit → All Audits section of Search Atlas so you know exactly which elements the Worker needs to inject. - Periodically re-check your Worker output after Webflow publishes site updates, as template changes may affect element selectors. 🆘 Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ OTTO Schema Deploy All Button and Pending Items

🔍 Overview The Deploy All button in OTTO SEO lets you push multiple schema tasks to your site at once. However, customers sometimes notice that after clicking Deploy All, certain schema tasks remain in a pending state or the task counter does not update as expected. This is a known issue that requires investigation by our support team. ⚙️ How the Deploy All Button Works The Deploy All button is designed to deploy all schema tasks that are currently eligible for deployment. The pending counter reflects the number of schema tasks that still need action and should update as tasks are processed. ⚠️ Known Issue: Tasks Remaining Pending After Deploy All Some customers have reported that after clicking Deploy All, one or more schema tasks remain in a pending state or the counter does not reflect the expected change. This behavior has been identified as a bug and is handled on a case-by-case basis by our engineering team. This is not something that can be resolved through standard troubleshooting steps on your end. Our team will need to investigate your specific project to determine the cause. 📋 What to Have Ready When You Escalate To help our team resolve this as quickly as possible, please have the following information ready before reaching out: - Project name or the site URL affected - Exact number of tasks showing as pending after clicking Deploy All - Screenshot of the pending task counter and schema task list - Timestamp of when you clicked Deploy All and first noticed the issue - Any recent changes made to the site (plugin updates, theme changes, etc.) around the time the issue began If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚡ OTTO Recrawl Scheduling and Audit Issue Navigation

Overview OTTO performs automatic site audits on a recurring schedule so you always have fresh SEO data without manual intervention. This article explains what to expect from OTTO's recrawl process and how to locate specific audit issues — such as Page not in sitemap — inside your audit results. How Automatic Recrawl Scheduling Works OTTO is designed to run site audits automatically for your project. You generally do not need to trigger recrawls manually under normal circumstances. Here is what to expect from the automatic recrawl process: - OTTO initiates audit crawls on a recurring schedule managed by the platform. - When a crawl completes, OTTO processes the results and updates your audit data automatically. - Refreshed issue counts, affected page totals, and recommendations will appear once the crawl finishes — no action is required on your part. - If your audit data appears stale or not yet updated, allow some time after the scheduled crawl window before concluding data has not refreshed, as processing can take time depending on your site's size. How to Find Specific Audit Issues Issues such as Page not in sitemap are grouped and listed within your OTTO audit results. To locate a specific issue: 1. In the left sidebar, go to OTTO SEO → Site Audit. 2. Select your project to open its Site Audit results. 3. Browse or search the list of flagged issues to find the one you are looking for, such as Page not in sitemap. 4. Select the issue to view the full list of affected pages and any available guidance on addressing it. If an issue you expect to see does not appear, the crawl may still be processing. Wait for the audit to complete and then refresh your view. What to Do If You Need Help If your audit data is not updating, a specific issue is missing from your results, or you are unsure how to interpret your audit findings, please reach out to our support team with the following information ready: - Your project name or URL - A description of the issue you are seeing (e.g., missing audit results, unexpected issue counts) - Any relevant timestamps or screenshots If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Website Studio Multi-Page Editing and AI Content Issues

🔍 Overview When working on a multi-page project in Website Studio, two questions come up frequently: does uploading an HTML file to one page affect the rest of the project? And why does the AI agent rewrite or invent content instead of using the exact wording you provided? This article explains both behaviours and shows you how to get the results you expect. 📄 How HTML File Uploads Work in Multi-Page Projects HTML file uploads in Website Studio are scoped to the page you are editing. If you experience unexpected changes appearing on pages you did not intend to modify, this is a known issue that requires investigation by our team. If you notice unexpected changes appearing on pages you did not intend to edit, please reach out to our support team with your project name, the page(s) affected, and the approximate time the issue occurred. 🤖 Why the AI Agent Rewrites Your Content Instead of Using Your Exact Wording The AI agent in Website Studio may rewrite or adapt content you provide rather than preserving your exact wording. This is a known behaviour, particularly when providing legal, compliance, or brand-specific content that must remain exact. If the AI continues to rewrite content despite your instructions, please contact support with your project name, the prompt you used, and an example of the content that was changed so our team can investigate further. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🌐 OTTO Project Scoping for Multilingual Subdirectories

🗺️ Overview If your website serves multiple languages through subdirectories — for example, /pl/ for Polish, /fr/ for French, or /en/ for English — you may want to deploy OTTO to just one language version at a time. This article explains how OTTO handles multilingual sites, what to expect, and the recommended approach for isolating OTTO to a specific subdirectory. ⚙️ How OTTO Scopes a Project When you create an OTTO project, it is tied to the root domain you enter during setup. OTTO crawls and applies optimisations across the entire domain by default — it does not automatically restrict itself to a single subdirectory such as /pl/. Because of this, deploying OTTO to a multilingual site without any configuration adjustments means OTTO will discover and potentially act on pages across all language versions of your site, not just one. 🚫 Known Limitation: Subdirectory-Only Scoping At this time, OTTO does not support a built-in subdirectory scope selector that restricts crawling and automation exclusively to a path like /pl/. A dedicated subdirectory scope UI is planned for a future release. Until that feature is available, the approaches below are the recommended ways to isolate OTTO to a single language version. ✅ Recommended Approaches Choose the method that best fits your technical setup and testing goals: 1. Create a separate OTTO project for the target subdirectory domain: If your multilingual setup uses a subdomain structure (e.g., pl.example.com), create a dedicated OTTO project using that subdomain as the root domain. This gives you clean, isolated coverage for that language. 2. Use URL filtering during onboarding: When setting up your OTTO project, enter the full subdirectory URL as the starting point (e.g., https://www.example.com/pl/). This signals to the crawler where to begin, which can limit the initial scope of discovered pages — though full root-level isolation is not guaranteed. 3. Apply OTTO recommendations selectively: After OTTO generates suggestions, review them page by page and apply changes only to pages that belong to your target language subdirectory. Avoid bulk-deploying suggestions if you have not yet verified the language scope of each page. 4. Monitor language attribution carefully: A known issue exists where AI suggestions may be generated in the wrong language on multilingual sites — for example, English-language suggestions appearing on French or Polish pages. Always review suggestion language before deploying, especially on mixed-language domains. 🛠️ Setting Up Your OTTO Project Follow these steps to create a new OTTO project: 1. In the left sidebar, click OTTO SEO → All Sites (SEO Automation). 2. Click Create to start a new project. 3. Enter the domain or subdirectory URL you want OTTO to focus on. 4. Complete the setup wizard, paying close attention to any crawl settings that allow you to narrow the starting URL path. 5. Once the project is active, review the discovered pages and confirm they match the language version you intend to optimise. 💡 Best Practices for Multilingual Sites - Audit before deploying: Always run a full page review after OTTO crawls your site to confirm which language pages were discovered. - Check suggestion language: Read each AI-generated suggestion to verify it matches the target language of the page before applying it. - One project per language: Where your site architecture allows, consider maintaining one OTTO project per language region. This makes performance tracking cleaner and reduces the risk of cross-language errors. - Use hreflang correctly: Ensure your site's hreflang tags are properly implemented. Well-structured hreflang helps OTTO and other tools correctly identify language and regional intent for each page. 🔮 What's Coming The Search Atlas team is actively working on expanded subdirectory scope controls for OTTO, which will allow you to restrict crawling and automation to a specific path such as /pl/ or /fr/ directly within the project settings. This feature is on the product roadmap and will be announced in release notes when available. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔄 Why OTTO Optimizations Persist After Plugin Changes

🤔 What Is Happening? You edited or deleted content in WordPress, deactivated the Search Atlas plugin, yet your live webpage still shows the old content OTTO deployed — for example, a "24/7" phrase or other optimized text you no longer want. This is expected behaviour, not a bug. Understanding why it happens will help you fix it quickly. ⚙️ How OTTO Deployments Work OTTO SEO applies optimizations directly to your live page at the server or rendering layer, independently of what is stored inside your WordPress editor. This means: - OTTO-deployed content is not stored inside your WordPress posts or pages — it lives in the Search Atlas platform and is injected on top of your existing page content. - Editing or deleting text in the WordPress block editor or classic editor does not remove an OTTO optimization that has already been deployed. - Deactivating or uninstalling the Search Atlas WordPress plugin removes the plugin's local connection but does not automatically roll back active OTTO deployments on your site. Think of OTTO optimizations as a separate layer sitting above your WordPress content. To remove them, you must manage them inside the Search Atlas dashboard — not inside WordPress. 🛠️ How to Remove a Persisting OTTO Optimization 1. Log in to your Search Atlas account. 2. In the left sidebar, click OTTO SEO → SEO Automation (URL: /seo-automation-v3). 3. Select the website or property where the outdated content is appearing. 4. Locate the specific optimization that contains the content you want to remove — for example, the deployment that inserted the "24/7" text. 5. Click the optimization to open its details. 6. Use the Undeploy or Revert option to roll back that specific change. The optimization will be removed from your live page. 7. Reload your live webpage to confirm the outdated content is gone. If you want to remove all active OTTO optimizations for a property, look for the option to undeploy all changes within the same OTTO SEO section before disconnecting the site. 🔌 Deactivating the Plugin Safely If your goal is to fully disconnect Search Atlas from your WordPress site, follow this order to avoid leaving orphaned content on your pages: 1. First, go to OTTO SEO → SEO Automation in the Search Atlas dashboard and undeploy all active optimizations for that property. 2. Confirm your live pages look correct and no OTTO-managed content remains. 3. Then deactivate and uninstall the Search Atlas plugin from your WordPress admin panel. Following this sequence ensures your site is clean before the plugin is removed. ❓ Why Can't I Just Edit It in WordPress? Because OTTO writes to your live page independently, any text you type into the WordPress editor for that section will be overwritten or ignored as long as an OTTO deployment for that element is still active. Always undeploy first in Search Atlas, then make your WordPress edits if needed. 🚀 Quick Reference - Content still showing after WordPress edit? → Undeploy the optimization in OTTO SEO → SEO Automation dashboard. - Content still showing after plugin deactivation? → Reactivate the plugin temporarily, undeploy all optimizations in OTTO SEO → SEO Automation, then deactivate again. - Not sure which optimization is responsible? → Review the deployment list in OTTO SEO → SEO Automation and match it to the URL where the content appears. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

📈 OTTO Bulk Optimization Recovery Timeline Explained

🔍 Why Metrics Temporarily Decline After OTTO Changes When OTTO applies bulk optimizations — such as updating page titles, meta descriptions, schema markup, or on-page content — Google must recrawl and reindex every affected page before it can reflect the improvements in search rankings. During this reindexing window, it is completely normal to see a temporary dip in keyword positions, impressions, and organic traffic. This happens because Google re-evaluates modified pages before restoring or improving their rankings. The larger the number of pages changed, the more pronounced this temporary fluctuation can appear. Common OTTO changes that trigger reindexing include: - Title tag and meta description updates — directly affect how Google reads and ranks your pages - Schema markup additions or changes — require Google to reprocess structured data signals - On-page content optimizations — alter the relevance signals Google uses to match queries - Header tag restructuring — changes the content hierarchy Google uses during crawling 📅 Expected Recovery Timelines Recovery from bulk OTTO optimizations typically follows a gradual pattern. In the initial days after changes are applied, metrics may fluctuate as Google begins recrawling affected pages. Over the following weeks, rankings generally begin to stabilize and return toward their pre-change levels or better. Full recovery and measurable improvement can take several weeks to a couple of months, depending on the size and nature of the changes. Because Google's crawl and reindex schedule varies by site and change type, there is no single fixed timeline that applies to every project. Treat any initial metric drop as a normal part of the process rather than a sign that something has gone wrong. ⚙️ Factors That Affect Recovery Speed Not every site recovers at the same pace. Several factors influence how quickly Google reindexes your pages and restores rankings: - Crawl frequency: Sites that receive more frequent bot visits tend to be recrawled and reindexed faster than newer or lower-authority sites. - Number of pages changed: Optimizing a large number of pages at once takes longer for Google to fully process compared to changes made to a small set of URLs. - Schema complexity: More advanced structured data changes may require additional processing time before Google reflects them in search results. - Site health: Technical issues such as slow page speed, crawl errors, or poor internal linking can slow down Google's ability to reprocess updated pages. ✅ What You Should Do During the Recovery Window While waiting for rankings to stabilize, focus on monitoring rather than making additional large-scale changes. Frequent re-optimization during this window can reset the reindexing cycle and delay recovery. Use Search Atlas to track keyword positions and impressions over time so you can identify when recovery is progressing as expected. If you are concerned that a drop is larger or longer-lasting than expected, gather the following information before reaching out for support: your project name, the approximate date OTTO changes were applied, the number of pages affected, and any specific URLs showing unusual behavior. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 How to Confirm Brand Vault Is Complete

This article explains what to do if your Brand Vault completion status appears unclear or incomplete in Search Atlas. When Brand Vault Completion Status Is Unclear If you have been working on your Brand Vault but the status does not appear to reflect your progress — for example, sections look empty or you are unsure whether your information has been saved — this is a known point of confusion that our team can help clarify. Because the exact fields required for completion and how saving works may not be immediately obvious, we recommend reaching out to our team rather than attempting further edits that could overwrite your existing entries. What to Have Ready Before Reaching Out To help our team resolve this as quickly as possible, please have the following information ready when you contact us: - The name of the project or workspace where the Brand Vault is set up. - A description of what the unclear or incomplete status looks like — for example, a specific section that appears empty or a prompt asking you to add information you have already entered. - Any steps you have already tried, such as re-entering information or refreshing the page. - A screenshot of the current Brand Vault state, if possible — this helps the team identify the issue faster. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🧩 Understanding and Removing Hardcoded Schemas on Shopify

📖 What Are Hardcoded Schemas? Schema markup is structured data added to your pages that helps search engines understand your content, such as product details, reviews, and prices. When this markup is hardcoded, it means the code is written directly into your Shopify theme files or app-generated code, rather than being managed dynamically by a tool like OTTO. In short, a hardcoded schema is structured data that lives inside your website's template files. Because it is baked into the theme, it stays on your pages regardless of what OTTO adds or changes. 🔍 Where Do Hardcoded Schemas Come From? If OTTO reports that it cannot remove a number of hardcoded schemas (for example, ~537), it means those schemas already existed on your site before OTTO was connected. Common sources include: - Your Shopify theme: Most themes ship with built-in schema markup for products, collections, and articles. - Third-party apps: SEO, review, and rich-snippet apps often inject their own schema into your pages. - Custom development: Code added manually by a developer or agency in the past. Because these schemas are part of your theme or app code, OTTO can detect them but cannot automatically delete them. OTTO only controls the schema it generates itself. ⚠️ Why This Matters Having both hardcoded schemas and OTTO-generated schemas on the same page can create duplicate structured data. Search engines may see conflicting information, which can reduce the effectiveness of your rich results. Cleaning up duplicate schema helps ensure search engines read a single, accurate source of structured data. 🛠️ How to Remove Hardcoded Schemas Because hardcoded schemas live in your Shopify theme or apps, they must be removed at the source. Follow these steps: 1. Identify the source. Review a page's structured data to see whether the markup comes from your theme or from an installed app. 2. Check your theme files. In Shopify, go to Online Store > Themes > Edit code. Schema is usually found in template and section files (often labelled with terms like JSON-LD or schema). 3. Review your apps. If a review or SEO app is generating schema, adjust that app's settings or remove it if it is no longer needed. 4. Back up before editing. Always duplicate your theme before changing any code, so you can restore it if needed. 5. Remove or disable the duplicate markup. Delete the hardcoded schema blocks you no longer want, then save your changes. If you are not comfortable editing theme code, we recommend working with a Shopify developer to make these changes safely. ✅ After Removing Hardcoded Schemas Once the hardcoded schemas are removed at the source, OTTO will manage your structured data going forward. Keep these points in mind: - OTTO's schema stays active and continues to update automatically. - It can take time for search engines to re-crawl your pages and reflect the changes. - You can validate your pages using a structured data testing tool to confirm duplicates are gone. 💬 Need More Help? Removing theme-level code can feel technical, and that is completely normal. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🤖 Managing Noindex and Robots.txt Without Backend Access

Understanding the Constraint When a client implements OTTO through Google Tag Manager (GTM) rather than the WordPress plugin, you typically do not have direct access to the server's robots.txt file or the site's CMS backend. This means standard approaches — editing robots.txt directly or adding meta tags through a CMS admin panel — may not be available to you. This is a known configuration gap. Because the specific steps for resolving this depend on your site setup and what access your client can grant, the most reliable path is to work directly with our support team, who can guide you through the appropriate approach for your situation. What to Have Ready Before Escalating To get the fastest resolution, please have the following information available when you contact us: - Your project name and the domain where OTTO is deployed - Confirmation of how OTTO is implemented (e.g., via GTM, WordPress plugin, or another method) - A description of what you are trying to achieve — for example, applying noindex to specific pages, blocking certain paths in robots.txt, or removing URLs from Google's index - The specific pages or URL patterns you need to control - What backend or CMS access you currently have (e.g., GTM container access, Google Search Console access, FTP/hosting access) - Any error messages or unexpected crawl/index behavior you have observed, including timestamps if available General Guidance Depending on your level of access, common approaches for this type of issue include collaborating with your client to apply changes at the server or CMS level, using any GTM or Search Console access you do have, or requesting that your client implement specific directives on your behalf. Our support team can help you identify which option fits your situation and walk you through the correct steps. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔄 OTTO Recrawl vs Weekly Analysis Cycle Explained

🎯 Overview OTTO offers two distinct ways to evaluate your site after changes: an immediate recrawl you can trigger manually, and a weekly analysis cycle that runs automatically in the background. Knowing which one to use — and what each one detects — ensures you get accurate feedback after making code or structural updates. ⚡ Immediate Recrawl: What It Does and When to Use It The immediate recrawl button lets you re-check your site on demand without waiting for the scheduled cycle. Use this option after making surface-level fixes such as updating meta tags, adjusting title tags, fixing on-page copy, or resolving schema markup issues that do not involve changes to your site's architecture or codebase. What the immediate recrawl detects: - Updated meta titles and descriptions - Fixed heading tags (H1, H2, etc.) - Corrected image alt text - Resolved internal linking issues on existing pages - Schema and structured data updates on live pages - Changes to on-page content and keyword usage What the immediate recrawl does NOT detect: - Deleted or redirected pages - Codebase-level modifications - New pages added to the site - Changes to site architecture or navigation structure - Server-side rendering updates or framework-level changes Timeline: Results from an immediate recrawl are typically reflected in OTTO within a few minutes to a couple of hours, depending on your site's size. 🗓️ Weekly Analysis Cycle: What It Does The weekly analysis is an automated, deep-scan cycle that OTTO runs on a recurring schedule. This cycle is designed to catch structural and architectural changes that a surface-level crawl cannot detect. If you have made significant updates to your codebase, deleted pages, added new sections, or restructured your site navigation, you will need to wait for — or be aware of — the weekly cycle to see those changes reflected in OTTO's recommendations. What the weekly analysis detects: - Deleted or newly added pages across the site - Codebase and framework-level modifications - Changes to site architecture and internal linking patterns - New or removed URL structures and redirects - Shifts in crawl depth and page indexability - Broad technical SEO changes across the full site Timeline: The weekly analysis runs automatically every seven days. There is no manual trigger for the full weekly cycle — it operates on a fixed schedule set by OTTO. After the cycle completes, OTTO updates its recommendations to reflect all structural changes detected. 🖱️ How to Trigger an Immediate Recrawl 1. In the left sidebar, click OTTO SEO → All Sites (SEO Automation) to open the OTTO dashboard. 2. Select the site project you want to recrawl. 3. Navigate to Site Audit → Overview (Website Overview) and locate the Recrawl Site button. 4. Click Recrawl Site to start the immediate crawl process. 5. Wait for the crawl to complete — a progress indicator will confirm when it is finished. 6. Once complete, review the updated recommendations to confirm your fixes have been recognised. ✅ Choosing the Right Option After Making Changes Use the table below as a quick reference to decide which process applies to your situation: - Fixed a meta tag, title, or on-page content? → Use the immediate recrawl button. Results will appear within hours. - Updated schema or structured data on an existing page? → Use the immediate recrawl button. - Deleted pages, added new pages, or restructured your site architecture? → Wait for the next weekly analysis cycle for accurate results. - Made changes to your codebase or server-side rendering? → Wait for the weekly analysis cycle, as these changes require a deep structural scan. - Not sure which category your change falls into? → Run the immediate recrawl first. If OTTO's recommendations do not update as expected, the change likely requires the weekly analysis cycle to be fully detected. ⏳ Timeline Summary - Immediate recrawl: Triggered manually; results typically within a few minutes to a few hours. - Weekly analysis: Runs automatically every 7 days; no manual trigger available; covers all structural and codebase-level changes. 💬 Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🇫🇷 Fix French Titles and Pages

📄 Create French content Search Atlas supports French content generation for pages, headings, titles, and meta descriptions. To create a new French article, go to Content → Content Genius and choose Generate, Write with AI in Bulk, or Write it yourself. 1. Choose the content workflow you need. 2. Set the target page language or specify French in your instructions. 3. Review the generated H1, title tag, meta description, and body content before publishing. 4. Confirm that names, accents, keywords, and search intent match the French audience. 🔍 Review French page suggestions For existing pages, open Content → Onpage Audit and select the relevant page tab. Use Run Audit to review recommendations. Check that suggested titles, headings, keywords, and descriptions are written in French rather than English. ✏️ Correct English titles or metadata If a French page receives English suggestions, update the page language or add a clear instruction such as: Write all titles, headings, meta descriptions, and recommendations in French. Then regenerate the content or suggestion and compare the result with the original page. - Use French keywords and search terms. - Keep the intended meaning and tone of the original page. - Check accents and French punctuation. - Make sure the title and meta description accurately describe the page. ✅ Validate before publishing Before applying changes, confirm that the page URL, H1, title tag, meta description, and body content are all aligned with the French topic. If the page is multilingual, review each language version separately to prevent English text from appearing on the French version. 🛠️ When French localization still fails Some older workflows or previously generated recommendations may retain English labels or suggestions. Regenerate the content after confirming the language instructions, then review the output manually. Do not publish titles or metadata until the language and meaning are correct. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔀 Fix 404 Errors and Create Redirects in Website Studio

🔍 Overview If your Site Audit has flagged hundreds of broken URLs, you can export that list, create 301 redirects to send visitors and search engines to the correct pages, and design a custom 404 error page — all within Search Atlas. This article walks you through each step. 📋 Step 1: Export Your 404 URLs from Site Audit Before creating redirects, you need a clean list of all broken URLs on your site. 1. Go to OTTO SEO → Site Audit in the left sidebar. 2. Open your project and wait for the crawl to finish. 3. Navigate to OTTO SEO → Site Audit → Overview (Website Overview) and filter by 404 status code. 4. Click the Export to Docs button to download a CSV file containing all 404 URLs. 5. Open the CSV in a spreadsheet tool. You will see columns for the broken URL and the page that links to it. Use this to determine where each broken URL should redirect. Tip: If you have a large list (such as 915 URLs), sort the broken URLs by folder or pattern. Many URLs may share the same fix, which lets you create fewer redirect rules. 🔀 Step 2: Create 301 Redirects in Website Studio Once you have your list of broken URLs and their intended destinations, set up 301 redirects inside Website Studio. 1. Open Website Studio from the left-hand navigation. 2. Select the project that matches the site you audited. 3. Go to Settings inside your project, then find the Redirects section. 4. Click Add Redirect. 5. In the Source field, enter the broken URL path (for example, /old-page-name). 6. In the Destination field, enter the new URL path where you want visitors to land (for example, /new-page-name). 7. Set the redirect type to 301 (Permanent). 8. Click Save. 9. Repeat for each URL in your export list, or use bulk import if that option is available in your plan. Note: A 301 redirect tells search engines that the page has permanently moved. This passes link equity to the new URL and removes the broken URL from search results over time. 🎨 Step 3: Create a Custom 404 Error Page in Website Studio Even after setting up redirects, some visitors may still reach a dead end. A well-designed custom 404 page improves the user experience and keeps visitors on your site. 1. Inside your Website Studio project, click Add Page. 2. Name the page 404 or Page Not Found. 3. Use the drag-and-drop editor to design the page. Best practices include: - A clear, friendly message explaining the page does not exist. - A search bar or navigation links to help visitors find what they need. - A prominent button linking back to your homepage. 4. Once the page is designed, go to Settings for the page and assign it as your site's 404 error page. 5. Save and publish your changes. Tip: Keep the message short and helpful. Avoid technical language — a simple line like "Sorry, we can't find that page. Let's get you back on track." works well. ✅ Step 4: Verify Your Redirects Are Working After setting up your redirects and custom 404 page, confirm everything is functioning correctly. - Paste a formerly broken URL into your browser and confirm it lands on the correct destination page. - Re-run a Site Audit crawl after a few days to verify the 404 errors are no longer flagged. - Check that your custom 404 page appears when you visit a URL that genuinely does not exist on your site. ❓ Frequently Asked Questions Can I bulk-import redirects instead of adding them one by one? Bulk import availability depends on your plan. Check the Redirects section in Website Studio settings for an import option. If you do not see one, adding redirects individually or grouping similar URL patterns into wildcard rules can save time. Should I use a 301 or 302 redirect? Use a 301 (Permanent) redirect when a page has moved for good. Use a 302 (Temporary) redirect only when the move is short-term, such as during a promotion or A/B test. For fixing 404 errors, 301 is almost always the right choice. Why are 404 errors bad for SEO? Broken pages waste crawl budget, lose any backlink value pointing to them, and create a poor experience for visitors. Fixing them with 301 redirects transfers authority to your live pages and improves overall site health. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⏳ OTTO SEO Revert Changes: Timeline and Cache Expectations

🔍 Why Reverted Changes May Still Appear When you revert a change in OTTO SEO — such as an H1 length update — the revert is processed on the Search Atlas side, but the updated content must travel through several layers before it becomes visible everywhere. Even after clearing your browser cache and checking in incognito mode, you may still see the old content. This is expected behavior and does not mean the revert failed. There are four distinct stages between a revert action and full visibility: OTTO processing, your browser cache, your CDN or hosting cache, and Google's search index. Each stage has its own timeline. ⚙️ Stage 1: OTTO Revert Processing Time Once you trigger a revert inside OTTO SEO, Search Atlas processes and deploys the change to your connected site. Propagation time can vary — if you have recently triggered a revert and the change does not yet appear on your live site, allow some time to pass before troubleshooting further. If the change still does not appear after a reasonable wait, please contact support so the team can confirm the revert was applied successfully on the backend. 🖥️ Stage 2: Clear Your Local Browser Cache Your browser stores copies of web pages to load them faster. Even after a revert is live, your browser may serve the old cached version. Incognito mode alone does not always bypass a cached DNS or service worker. Follow these steps to fully clear your local cache: 1. Open your browser settings and navigate to Clear Browsing Data. 2. Select Cached images and files and Cookies and other site data. 3. Set the time range to All time. 4. Click Clear data. 5. Close and reopen your browser, then revisit your site. Alternatively, perform a hard refresh by pressing Ctrl + Shift + R (Windows/Linux) or Cmd + Shift + R (Mac) on the page in question. ☁️ Stage 3: Clear Your CDN and Hosting Cache If your site uses a CDN (such as Cloudflare, Fastly, or a hosting provider's built-in cache), those services cache your pages independently of your browser. The reverted content will not appear until that cache is purged. Steps vary by provider, but the general process is: - Cloudflare: Log in to your Cloudflare dashboard → select your domain → go to Caching → click Purge Everything or purge specific URLs. - WP Engine / SiteGround / other managed hosts: Log in to your hosting control panel and use the built-in cache purge or flush tool. - WordPress caching plugins (WP Rocket, W3 Total Cache, etc.): Go to your plugin settings and click Clear All Cache. After purging, revisit your page in a new browser tab to confirm the updated content is now showing correctly. 🌐 Stage 4: Google's Search Index Even after your live site reflects the reverted change, Google's search index may still display the old version in search results. Google needs to recrawl and reindex your page before the updated content appears in search. You can speed this up by submitting a reindex request through Google Search Console: 1. Log in to Google Search Console and select your property. 2. Paste the affected URL into the search bar at the top and press Enter. 3. Click Request Indexing in the URL inspection panel. Google typically processes priority reindex requests within a few days, though it can take longer depending on your site's crawl budget and overall traffic. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🗺️ Fix Empty Video and News Sitemaps

🔍 Overview If your video-sitemap.xml or news-sitemap.xml is returning an empty URL set despite having published video pages or recent news articles on your site, the most common cause is that the relevant custom post types have not been enabled in your sitemap settings. This article walks you through how to identify and fix the issue. ❓ Why Are My Sitemaps Empty? Search Atlas generates video and news sitemaps based on the post types you explicitly select in the sitemap configuration. By default, only standard post types (such as Posts and Pages) may be active. If your video content or news articles live inside a custom post type, those URLs will be excluded from the sitemap until you enable them manually. Common scenarios where this happens include: - Video content is stored in a custom post type such as Videos, Media Posts, or a plugin-generated type. - News articles are published under a custom post type rather than the default Posts type. - A recent site migration or plugin change created new post types that were never added to the sitemap settings. 🛠️ How to Enable Custom Post Types in Your Sitemap Settings 1. Log in to your WordPress admin panel for your connected site. 2. Navigate to Search Atlas → Settings to open the sitemap settings area. 3. Locate the section for the sitemap type that is empty — either the video sitemap or the news sitemap. 4. Find the option to select or enable post types for that sitemap. You should see a list of post types registered on your site. 5. Enable each custom post type that contains your video or news content. 6. Save your settings using the available save option in the interface. 7. If a sitemap regeneration option is available, trigger it; otherwise, wait for the next scheduled refresh. 8. Once regenerated, visit your video-sitemap.xml or news-sitemap.xml URL directly in your browser to confirm URLs are now appearing. ✅ How to Verify the Fix Worked After saving and regenerating, confirm the following: - Open yourdomain.com/video-sitemap.xml or yourdomain.com/news-sitemap.xml in your browser. You should now see a list of URLs matching your published content. - The number of URLs listed should reflect your published posts in those custom post types. - If you use Google Search Console, resubmit your sitemap after the fix to prompt Google to recrawl. 💡 Tips to Prevent This Issue - Whenever you install a new plugin that registers additional post types, review your sitemap settings to ensure those types are included if needed. - After any site migration, audit your sitemap configuration to confirm all relevant post types are still enabled. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚡ Share OTTO Plugin Credentials Without Outlook

Overview When you add the OTTO pixel plugin to your website, Search Atlas provides an Email my developer button to quickly share installation credentials. However, this button opens Microsoft Outlook by default. If your team uses Gmail, Slack, or any other communication tool, the button may not work as expected. This article shows you how to manually retrieve your UUID and API Key, and share them with your developer through any channel you choose. Where to Find Your OTTO Plugin Credentials 1. Log in to Search Atlas and navigate to the OTTO section of your dashboard. 2. Locate your OTTO workspace and find the area where your plugin credentials are displayed. 3. You will see two key credentials: - UUID — your unique site identifier - API Key — the authentication key required by the plugin 4. Copy each value by highlighting the text and pressing Ctrl + C (Windows) or Cmd + C (Mac). Why the 'Email My Developer' Button May Not Work The Email my developer button uses a mailto: link, which automatically opens your operating system's default email client. If Outlook is not installed or configured on your device, the button may not function as expected. This is a browser and OS limitation — not a Search Atlas error. The solution is to share the credentials manually, as described below. How to Manually Share Credentials With Your Developer Once you have copied your UUID and API Key, you can share them through any method your team uses. Follow these steps to put together everything your developer needs: 1. Copy your UUID from your OTTO dashboard credentials area. 2. Copy your API Key from the same area. 3. Open your preferred communication tool — for example, Gmail, Slack, Microsoft Teams, or a project management app. 4. Compose a message or task for your developer and include the following information: - UUID: [paste your UUID here] - API Key: [paste your API Key here] - Plugin name: OTTO SEO (available in the WordPress plugin directory) 5. Ask your developer to install the OTTO SEO plugin on your WordPress site and enter the UUID and API Key when prompted during setup. If You Need Help If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔗 OTTO Pixel: Removing Unwanted Inserted Links

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

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

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

🗑️ Delete Duplicate OTTO Site Explorer Projects by Region

🔍 Why Duplicate Regional Projects Appear When setting up a website in OTTO Site Explorer, it is possible to create multiple projects for the same domain. If you only need one version, the duplicate can be safely deleted without affecting your remaining project. 📋 Before You Delete Take a moment to confirm the following before removing a project: - Identify the correct project to keep. Review your existing projects in OTTO Site Explorer and confirm which one you want to retain before proceeding. - Check for linked OTTO automations. Note which project is linked to any active OTTO SEO session before proceeding, so you delete the correct one. - Save any data you need. Download any reports you want to keep before deleting, as deleted project data may not be recoverable. 🗑️ How to Delete the Unwanted Project To remove a duplicate project, follow these steps: 1. Log in to Search Atlas and navigate to Site Metrics > Site Explorer. 2. Locate the duplicate project in your project list. 3. Open the project's settings or options menu (typically accessible via a three-dot or gear icon next to the project name). 4. Select the Delete or Remove option. 5. Confirm the deletion when prompted. If you do not see a delete option, or if the option is unavailable for a particular project, please contact our support team for assistance. When you reach out, please have the following ready: - The domain name associated with the duplicate projects - Which project you want to delete - Which project you want to keep - Whether either project is linked to an active OTTO SEO session ✅ After Deleting Once the unwanted project is deleted: - Confirm that only your preferred project remains in your OTTO Site Explorer project list. - If you use OTTO SEO, verify that your active session is still correctly linked to the project you kept. 💡 Tips to Avoid Duplicate Projects - Before creating a new project, always check your existing OTTO Site Explorer project list to see if a project for that domain already exists. - When setting up a project, double-check all settings before saving to avoid creating unintended duplicates. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⏳ OTTO Negative Keyword Suggestions — Timing and Traffic Requirements

🔍 Overview OTTO's AI-powered negative keyword suggestions help you eliminate wasted ad spend by identifying search terms that are unlikely to convert. However, these suggestions do not appear immediately after activation. OTTO needs to collect and analyse a minimum amount of campaign traffic data before it can generate reliable recommendations. This article explains what to expect and what to do if suggestions are not showing up. ⚙️ How OTTO Negative Keyword Suggestions Work Once you activate the negative keyword recommendation feature, OTTO begins monitoring your connected Smart Ads campaigns. It analyses incoming search term data, evaluates click and conversion patterns, and uses that information to surface terms worth excluding. Because the AI relies on real performance data — not estimates — it cannot generate meaningful suggestions until enough traffic has flowed through your campaigns. 🗓️ Activation Timeline — What to Expect After you activate the feature, there is a data-collection period before suggestions begin to appear. During this initial phase, no suggestions will show — this is normal and expected behaviour. Suggestions will start to surface once OTTO has gathered sufficient campaign data. If you have recently activated the feature and are not yet seeing suggestions, your account is most likely still within the normal warm-up window and no immediate action is required. 📊 Minimum Traffic Requirements OTTO requires a baseline level of campaign activity before suggestions are generated. If your campaigns are new, paused, or running with very limited budgets, the necessary traffic volume may not yet have been reached. Key factors that affect whether suggestions appear include: - Active campaigns: One or more campaigns must be in an active, running state — not paused or ended. - Sufficient impressions and clicks: Your campaigns need to accumulate enough traffic data for OTTO's AI to identify patterns. Low-volume campaigns may experience a longer wait before suggestions appear. - Search term data: Your campaigns must be receiving search term reports. Broad match or phrase match keywords tend to generate the most usable data for OTTO's analysis. If your campaigns are seeing very low traffic, increasing your daily budget, broadening match types, or expanding your keyword set can help accumulate the data OTTO needs more quickly. ✅ What to Do If Suggestions Are Not Appearing 1. Confirm that the negative keyword recommendation feature is activated within your OTTO settings. 2. Check that at least one of your Smart Ads campaigns is currently active and running. 3. Review your campaign traffic levels — low impressions or clicks will delay suggestions from appearing. 4. If everything appears correctly configured and your campaigns have been active for some time with reasonable traffic, allow additional time for OTTO to accumulate enough data. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Configure OTTO Pixel and Knowledge Graph Settings

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

🛠️ Google Reviews Horizontal Scrolling Display Issue

🔍 What Was the Issue? Some users noticed that Google Review drafts in the Reviews section appeared on a single line, requiring horizontal scrolling to read the full text. This made reviewing and editing drafts noticeably harder and raised questions about whether the behaviour was intentional or a bug. 📋 What Caused It? This was caused by a recent platform update that unintentionally affected how review draft text was displayed. Text that should have wrapped across multiple lines was instead rendering on one continuous line, forcing users to scroll sideways to read it. This was confirmed as a UI issue — not intentional design — and was logged with the engineering team for a fix. ✅ Current Status: Resolved This issue has been resolved. A UI improvement update was applied to the Google Business Profile Reviews section, and text wrapping now works as expected. You should no longer need to scroll horizontally to read review drafts. 🧭 How to Check Your Reviews To access your Google Reviews and confirm the display is working correctly, follow these steps: 1. Open the platform and navigate to Local → Reviews (Google Business Profile Reviews) in the left sidebar. 2. Browse your review drafts and confirm that text wraps naturally across multiple lines without requiring horizontal scrolling. 💡 What to Do If You Still See Horizontal Scrolling If you open the Reviews section and the horizontal scrolling issue is still present for you, try the following before contacting support: - Hard-refresh your browser by pressing Ctrl + Shift + R (Windows/Linux) or Cmd + Shift + R (Mac). This clears cached page data and loads the latest version of the platform. - Try a different browser to rule out a local browser rendering issue. - Check your browser zoom level — a zoom level above 100% can sometimes cause layout shifts that introduce unexpected scrollbars. If none of the above steps resolve the problem, the issue may have reappeared or may be specific to your account or browser environment. In that case, it is important to report it promptly so the team can investigate. 📞 Still Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Understanding the OTTO SEO Pending Optimizations Counter

🧭 Overview The Pending Optimizations counter in OTTO SEO is one of the most frequently misunderstood metrics on the platform. If you notice that tasks you have already deployed — such as title tag updates — still appear in the counter, or that the number does not match what you expect, this article explains why and what (if anything) you need to do. 📊 What Does the Pending Optimizations Counter Actually Measure? The counter displays the total number of SEO tasks that OTTO has identified across your site and considers unresolved at the time the snapshot was last taken. Specifically, it reflects: - Undeployed tasks — optimizations OTTO has recommended but that have not yet been applied to your site. - Recently deployed tasks that are still in the cache — tasks you have deployed, but whose status has not yet refreshed in OTTO's internal snapshot. This is the most common reason deployed tasks continue to appear in the counter. - Tasks pending validation — tasks OTTO has applied but is still confirming are live on your site via crawl data. In short, the counter is a point-in-time snapshot, not a real-time live feed. A short delay between deployment and counter update is expected and normal. ⚙️ Why Do Deployed Title Tag Tasks Still Appear? After you deploy a task — for example, a title tag change — OTTO does not immediately remove it from the Pending Optimizations counter. The platform uses an internal snapshot to verify that a deployed change is live on your site. Until that snapshot refreshes, the task may remain flagged as pending in the counter, even though the optimization has been successfully applied. Once the system confirms the change is live, the task is automatically moved out of the pending count. This is a known platform behaviour. You do not need to redeploy tasks that are already deployed — doing so will not speed up the counter update and may cause unintended duplicate changes. 🌐 Should I Redeploy Tasks for a Specific URL (e.g. /en/faq)? If you are unsure whether a task for a specific page — such as /en/faq — requires redeployment, check the task's current status within the OTTO SEO interface before taking any action. If the task already shows as deployed or applied, no further action is needed and the counter will update once the platform's internal snapshot refreshes. Only redeploy a task if it clearly has not been applied and the recommendation is still relevant to your current page content. If the counter continues to show unexpected numbers after allowing sufficient time for the snapshot to refresh, or if you are unsure how to interpret a specific task's status, please reach out to our support team with your project name, the affected URL, and a description of what the counter is currently showing. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔄 OTTO Overlay vs WordPress Plugin Schema Explained

🧭 Overview Search Atlas offers two separate ways to deploy schema markup on your site: the OTTO SEO overlay and the Search Atlas WordPress plugin. These are independent systems with different deployment methods. The Search Atlas WordPress plugin supports receiving and saving schema markup deployed from OTTO. ⚙️ How OTTO Deploys Schema OTTO is a front-end overlay system. When you deploy schema through OTTO (found in the left sidebar under OTTO SEO at /seo-automation-v3), it injects structured data directly into your page's rendered HTML at the front-end level. This means: - Schema is added to what search engines and browsers receive when they load the page. - No changes are written to your WordPress database, theme files, or plugin settings. - The Search Atlas dashboard correctly shows the schema as deployed because OTTO has successfully applied it to the live page output. - When the Search Atlas WordPress plugin is installed, it can receive and save schema markup deployed from OTTO. This front-end injection approach lets OTTO work across many site types without requiring back-end access or plugin installation. 🔌 How the WordPress Plugin Deploys Schema The Search Atlas WordPress plugin operates entirely within your WordPress backend. When you configure schema through the plugin, it writes structured data directly to your WordPress database and outputs it through your theme. This means: - Schema settings are stored in WordPress and managed from within the WP admin interface. - Changes made in the plugin are visible in the plugin fields at all times. - The plugin is best suited for teams who prefer managing SEO settings directly inside WordPress. 🔍 Why Your Dashboard and Plugin Fields Look Out of Sync If your Search Atlas dashboard shows schema as deployed, the Search Atlas WordPress plugin can receive and save that schema markup deployed from OTTO. Additionally, schema type mismatches (for example, the dashboard showing Service Page schema while the plugin shows Article) occur because each system maintains its own schema configuration independently. OTTO and the plugin can be set to different schema types without either being wrong — they simply reflect the settings applied within each respective system. ✅ Choosing the Right Method for Your Setup Use the guidance below to decide which deployment method fits your needs: - Use OTTO if you want Search Atlas to manage schema automatically without touching your WordPress backend. OTTO handles deployment through its overlay and keeps your WordPress installation unchanged. - Use the WordPress plugin if you prefer schema to be stored and managed within WordPress itself, giving your development team direct back-end control. - Do not use both simultaneously for the same schema type on the same page. Running OTTO and the plugin with overlapping schema configurations on the same page can result in duplicate structured data, which may cause issues with how search engines process your markup. 🛠️ How to Verify Which System Is Serving Your Schema 1. Open the page in your browser and view the page source (Ctrl+U or Cmd+U). 2. Search for application/ld+json to locate any schema blocks on the page. 3. If schema is present in the rendered source but absent from the WordPress plugin fields, OTTO is the active deployment method. 4. Use Google's Rich Results Test or the Schema Markup Validator to confirm what structured data search engines are reading from the live page. You can also review your OTTO deployment status at any time by navigating to OTTO SEO in the left sidebar of Search Atlas (/seo-automation-v3) and checking the schema settings for the relevant URL. 📋 Quick Reference Summary - OTTO schema deployed? Dashboard shows active. The Search Atlas WordPress plugin can receive and save the schema markup deployed from OTTO. - WordPress plugin schema deployed? Plugin fields are populated. OTTO dashboard does not reflect this. This is correct. - Schema type mismatch between systems? Each system has its own independent schema type setting. Update each one separately if alignment is needed. - Schema not appearing at all? Verify which system is active using the page source method above, then check configuration within that system. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Recovering a Deep-Frozen Site in OTTO SEO

🧊 What Is a Deep Freeze in OTTO SEO? A deep freeze pauses all active SEO automations for a site and removes it from your active site list in OTTO SEO. Unlike a standard freeze, a deep freeze is designed for long-term suspension, which is why the site no longer appears in your normal view after it is applied. This is expected behaviour — the site has not been deleted, but it does require a specific recovery pathway to bring it back. ⚠️ Why You Can't See the Site Anymore When a site is manually deep frozen, OTTO SEO moves it out of the default site list to prevent accidental edits. If you are looking for the site in your main list and it is not there, this is the most likely reason. The site still exists in your account and can be recovered by our support team. 🔄 How to Recover a Deep-Frozen Site Because the recovery process requires backend access to restore deep-frozen sites, this action needs to be completed by our support team. You can find your deep-frozen sites under the Deep Frozen tab in OTTO SEO → All Sites. To get your site unfrozen as quickly as possible, please have the following details ready before reaching out: - The exact domain of the deep-frozen site (for example, bestfitdigital.co). - The approximate date the deep freeze was applied, if known. - The name of the Search Atlas account or workspace the site belongs to. Do not attempt to re-add the site manually — doing so may create a duplicate entry and could affect your historical data and automation history. ✅ After Unfreezing — What to Check - Confirm the site now appears in your OTTO SEO → All Sites (SEO Automation) list with an Active status. - Review your automation settings to make sure they are configured as expected. A deep freeze preserves your settings, but it is good practice to verify them after restoring. - Check that any scheduled tasks or pending optimisations are queued correctly and running. 💬 Need Further Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

📋 Understanding OTTO Recommendation Persistence After Deployment

🔍 Overview When you manually implement an OTTO recommendation, you might expect it to disappear from your list automatically after the next analysis runs. However, OTTO is designed to keep recommendations visible indefinitely until you explicitly remove them. This article explains how recommendation persistence works and how to manage your list effectively. ⚙️ How OTTO Recommendation Persistence Works OTTO surfaces SEO recommendations based on analysis of your site. Once a recommendation appears in your list, it will remain there regardless of whether you have already deployed it. There are two important points to understand: - Deploying a recommendation does not remove it automatically. After you manually implement a fix, the recommendation stays in your list until you take action to dismiss it. - Running a new analysis does not clear deployed recommendations. Re-analysis updates the findings on your site but does not trigger automatic removal of existing recommendations from the list. This behavior is intentional. OTTO retains deployed recommendations so you always have a clear record of what changes were suggested and when you acted on them. 🗑️ How to Remove a Recommendation Manually Once you have implemented a recommendation, you can remove it from your list at any time. Follow these steps: 1. In the left sidebar, navigate to OTTO SEO and open SEO Automation (URL: /seo-automation-v3). 2. Locate the recommendation you have already deployed. 3. Select the recommendation to open its detail view. 4. Use the Dismiss or Mark as Done option to remove it from your active list. Removing a recommendation from the list does not undo any changes you have made to your site. It simply clears the item from your OTTO recommendation queue. 📌 Why Recommendations Persist by Design OTTO keeps suggestions visible after deployment for several practical reasons: - Audit trail. You can review everything OTTO suggested and confirm which items your team has addressed. - Avoiding duplicate work. If a recommendation is still visible, team members know it exists and can verify the implementation status before acting. - Manual control. You decide when a recommendation is truly resolved and ready to be cleared, rather than relying on automated removal that could dismiss items prematurely. ❓ Common Misconceptions Does crawl frequency affect when recommendations are removed? No. Crawl schedule and re-analysis do not control recommendation removal. New crawls update your site data and may surface new recommendations, but they will not remove existing ones from your list. Will a recommendation reappear if the issue returns after I dismiss it? No. Once a recommendation is dismissed or ignored, OTTO skips it in later crawls and does not suggest it again. ✅ Best Practices for Managing Your Recommendation List - After implementing a fix, immediately dismiss the corresponding recommendation to keep your list accurate and actionable. - Use the recommendation list as a running checklist — review it regularly with your team to track outstanding versus completed items. - Do not rely on re-analysis to clean up your list. Make manual dismissal part of your standard deployment workflow. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Verify OTTO Deployments on WordPress

🔍 What deployment verification confirms Verifying an OTTO deployment helps confirm that changes made in Search Atlas have reached your WordPress website. Depending on your setup, changes may be applied through the OTTO WordPress plugin, a connected CMS sync, or a headless implementation. ⚙️ Check your OTTO installation 1. In Search Atlas, open OTTO SEO from the left sidebar. 2. Select Installation Guide. 3. Review the installation status and confirm that your WordPress site is connected to the correct project. 4. Confirm the OTTO WordPress plugin is installed and active in your WordPress admin area when your setup requires the plugin. Some headless WordPress setups may not show a visible plugin marker in the page source. In those cases, use the live page and deployment checks below instead of relying only on a page marker. 🚀 Confirm the change is published 1. Make or identify a small, specific change in OTTO SEO. 2. Save or publish the change according to the instructions shown in Search Atlas. 3. Wait several minutes, then open the affected page in a private browser window. 4. Compare the live page with the expected result. Check the page title, meta description, canonical URL, headings, or other element changed by OTTO. Use the exact published URL, including the correct protocol and subdomain. Testing a staging, redirected, or different version of the URL can make a successful deployment appear missing. 🛠️ Verify the live HTML To check whether an on-page change is live, open the affected page, view its page source, and search for the expected title, meta description, canonical URL, or other updated content. The browser inspector may show changes created after page load, while page source helps confirm what the server returned. For structured data or other code changes, use a suitable search engine testing tool or inspect the rendered page. Confirm that the result appears on the live URL, not only inside the Search Atlas preview. 🧹 Clear caching before retesting Caching is a common reason a deployment appears not to sync. After publishing, clear or bypass caches at each applicable level: - WordPress caching or optimization plugins - Hosting or server cache - Content delivery network cache - Browser cache Retest in a private browser window after caches are cleared. If the change appears in Search Atlas but not on the live page, compare the page again after cache expiration or request a cache purge from your hosting or CDN settings. 📊 If the change still is not visible 1. Confirm you edited the correct Search Atlas project and target URL. 2. Check that the URL is indexable and is not redirected to another page. 3. Verify that WordPress and the OTTO plugin are connected to the same site. 4. Check whether another plugin, theme, server rule, or CDN is replacing the title, canonical, or other element. 5. Review the page source and record what appears instead of the expected change. Do not repeatedly publish the same change before checking the live HTML and cache layers. These checks help identify whether the issue is installation, deployment, caching, or another WordPress setting. 💬 Get help with a deployment If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Clear a Stale MetaSync Deployment

🔍 When to clear a deployment Use this process when a URL still shows deleted OTTO or MetaSync content, such as an outdated keyword, after you removed the recommendation and cleared your site caches. MetaSync may retain a URL-specific deployment separately from your browser, CDN, or WordPress cache. Clearing those caches alone may not remove the stale deployment. ✅ Check the URL first 1. Open the affected URL in an incognito browser window. 2. Confirm that the response is fresh and not served from a CDN, page cache, or browser cache. 3. View the page source and check whether the outdated HTML is still present. 4. In Search Atlas, confirm that the related recommendation or optimization is deleted or un-deployed. 🧹 Request a targeted cleanup If the deleted content remains in a fresh, uncached response, the MetaSync deployment needs a targeted cleanup for that URL. Open the chat widget in the bottom-right corner of the platform and type human teammate. Share the complete URL and explain that you need the stale OTTO/MetaSync deployment cleared for that URL only. A targeted cleanup removes the stale MetaSync deployment without removing other deployed optimizations on your site. Include the deleted recommendation, the text that is still appearing, and the cache checks you completed. 🔄 Verify after cleanup 1. Wait for the team to confirm that the URL-specific deployment was cleared. 2. Request a new uncached response or use an incognito browser window. 3. Check the page source and rendered page for the deleted content. 4. Confirm that other OTTO or MetaSync optimizations remain active. ⚠️ Important considerations - Do not remove the MetaSync plugin or reset all deployments to resolve a single stale URL. - Purging WordPress, CDN, and browser caches does not necessarily clear MetaSync's own deployment. - If the URL was cloned, redirected, or recently changed, provide the original and current URLs so the deployment can be checked accurately. - For headless WordPress, WPGraphQL, or Next.js setups, mention the architecture when contacting the team because deployment behavior may differ. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Stop OTTO From Overriding Yoast SEO Metadata

🔍 Why This Happens OTTO SEO can sync metadata — including title tags and meta descriptions — directly to your WordPress site through the Search Atlas plugin. This feature, sometimes called Persistence Mode or Sync to CMS, can continue writing to your Yoast SEO fields even after you disengage OTTO in the dashboard. Disengaging OTTO stops new deployments from being scheduled, but it does not automatically roll back metadata that has already been pushed to your CMS. In short: disengaging OTTO pauses future automation, but any metadata OTTO has already synced to Yoast remains in place until it is manually corrected or rolled back. ⚙️ Step 1 — Disengage OTTO in the Dashboard If you have not already disengaged OTTO for your site, do this first: 1. In the left sidebar, click OTTO SEO, then select All Sites. 2. Locate the site you want to manage. 3. Click the toggle or action menu for that site and select Disengage. 4. Confirm the action when prompted. This stops OTTO from scheduling or pushing any new metadata changes to your site. 🔌 Step 2 — Disable Metadata Sync in the WordPress Plugin Disengaging OTTO in the dashboard is only part of the process. You must also turn off the metadata sync inside the Search Atlas WordPress plugin to prevent any residual writes to Yoast fields: 1. Log in to your WordPress admin panel. 2. Navigate to Plugins → Search Atlas (or the OTTO SEO plugin settings). 3. Locate the Sync to CMS or Persistence Mode setting. 4. Toggle this setting Off and save your changes. Once this is disabled, OTTO will no longer have the ability to write to your Yoast title tags, meta descriptions, or any other on-page metadata fields — even if a sync is somehow triggered. ✅ Step 3 — Restore Your Yoast Metadata Manually Any titles or meta descriptions that OTTO has already overwritten will need to be corrected directly inside Yoast SEO. OTTO does not automatically revert metadata it has previously synced. 1. In WordPress, go to the page or post whose metadata was overridden. 2. Open the Yoast SEO meta box at the bottom of the editor. 3. Update the SEO title and Meta description fields with your preferred content. 4. Publish or update the page to save your changes. Repeat this for each page or post that was affected. If a large number of pages were overwritten, contact our team for guidance on bulk-restoration options (see below). 🚧 Keeping Your Redirects Safe A common concern when disengaging OTTO is whether existing redirects will be removed. The good news: disengaging OTTO does not delete redirects that have already been deployed to your site. Redirects pushed by OTTO remain active and intact. You can continue to manage them inside your WordPress redirect plugin or through OTTO's redirect tools without risk of losing them during disengagement. 💡 Best Practices Going Forward - Decide on a single source of truth. Choose either OTTO or Yoast SEO to control your metadata. Running both simultaneously with sync enabled will cause conflicts. - Review the plugin sync setting after any OTTO re-engagement. If you re-engage OTTO in the future, the Sync to CMS setting may be re-enabled. Check the plugin settings each time. - Use OTTO's override check. OTTO now checks for active third-party SEO plugins before pushing title changes. Make sure your Search Atlas WordPress plugin is updated to the latest version to benefit from this behaviour. - Monitor the plugin logs. If you notice unexpected metadata changes, check the Search Atlas plugin logs in WordPress for entries labelled as OTTO deployments. 🆘 Need Further Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Fixing Pixel Scan and Sitemap URL Issues

🔎 How the Deployment Scan Works When you activate OTTO, Search Atlas checks whether the OTTO pixel is installed on your site. The scan loads and renders your pages the same way a real browser does, then looks for the pixel in that rendered output. A deployment is marked as live only when the pixel is confirmed during the scan. Scans run in the background on a schedule, so a recently started scan may be queued, deferred, or still in progress before any verdict appears. 🤔 Why a Visible Pixel May Not Be Detected It is common for a developer to see the OTTO pixel in the live page source while the scan still shows no deployment. This does not always mean the pixel is missing. Common causes include: - The scan has not finished yet. Deployment scans are queued and can take time to complete. While a scan is pending or in progress, no deployment verdict appears, even if the pixel is already live on your site. - The pixel is deployed through Google Tag Manager (GTM) or another tag manager. Tag managers inject scripts after the initial page load. Because the scan evaluates the rendered page, a tag-manager deployment may not be recognized reliably. We recommend installing the OTTO pixel directly in the head section of your site instead. - Delayed script loading. If the pixel loads late in the page lifecycle, it may fall outside the scan window and go undetected. - Scan cooldowns. After a scan completes, there is a waiting period before a new scan can run, so recent changes to your site may not be reflected immediately. 🛠️ Steps to Resolve a Detection Issue 1. Confirm the OTTO pixel snippet is placed directly in the head section of your site, not only inside GTM or another tag manager. 2. Publish your changes and clear any server, plugin, or CDN caches so the scan sees the latest version of your pages. 3. Allow time for the next scheduled scan to run and complete. If a scan appears stuck in progress for more than 24 hours, contact us so we can investigate your project. 4. Check your URL scheme. Make sure your site, sitemap, and Search Atlas project all use the same protocol (https). A mismatch between http and https can produce false results in audit and sitemap checks. 🗺️ Where GSC Sitemap URLs Come From When you connect Google Search Console, Search Atlas imports the URLs listed in your sitemap. These URLs power site audit and sitemap coverage checks. Because they are synced from Google Search Console, they cannot be edited or deleted directly inside Search Atlas. They always reflect whatever your sitemap contains at the time of the sync. ✏️ How to Edit or Remove a Sitemap URL 1. Update the sitemap at the source, meaning in your CMS or wherever the sitemap file is generated, to add, change, or remove the URL slug. 2. If you changed a slug permanently, set up a redirect from the old URL to the new one so you do not lose traffic or backlinks. 3. Submit the updated sitemap in Google Search Console so Google registers the change. 4. Return to Search Atlas and re-sync your Google Search Console connection, or wait for the next automatic sync, so your URL list reflects the updated sitemap. After the sync completes, the outdated slug will stop appearing in your sitemap-based checks. If a page is still flagged as Not in XML Sitemap, verify that the sitemap entry and the live page use the exact same protocol and domain spelling, for example https with and without www are treated as different addresses. 💡 Tips to Avoid Future Discrepancies - Install the OTTO pixel directly in your site template rather than through a tag manager. - Keep your sitemap current whenever you publish, rename, or remove pages. - Use one consistent URL format (https, with or without www) across your site, sitemap, and Search Atlas project. - Allow one full scan cycle to pass before troubleshooting a fresh installation. 💬 Still Need Help? If the scan continues to report no deployment after you have confirmed direct pixel installation and a full scan cycle, or if a Google Search Console URL will not update after a re-sync, our team can look into your project directly. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Removing Incorrect OTTO Recommendations and Compensation

🔍 Understanding OTTO Recommendations OTTO SEO generates suggestions to improve your website rankings. Occasionally these may not match your specific needs such as title tag changes that conflict with your branding. You can review and manage these directly in the platform. 🗑️ Removing Specific Recommendations To eliminate unwanted suggestions follow these steps. Go to the left sidebar and select OTTO SEO. Then choose Site Audit to view active recommendations. Locate the specific items such as title tags for your domain. Use the available options to exclude or dismiss them from future suggestions. This prevents them from appearing again. 💰 Requesting Compensation If OTTO recommendations caused unwanted changes to your content you may request compensation. Open the chat widget in the bottom-right corner of the platform and type human teammate to connect with our team. Provide details about the affected site and the specific issues. Our team will review your case and guide you through the next steps. 📋 Preventing Future Issues Regularly check your OTTO SEO dashboard after site updates. Exclude URLs or page types that should not receive automated changes. This keeps recommendations aligned with your goals and reduces the chance of incorrect suggestions. 📞 Getting Further Help If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🧩 OTTO and Yoast Schema Output Conflicts

🔍 Overview OTTO and Yoast can both generate Schema.org JSON-LD on the same WordPress page. When both systems publish overlapping schema, search engines may receive competing or invalid schema blocks. This can cause the Yoast schema graph to appear false, prevent the author Person entity from being included, or create duplicate BlogPosting data. MetaSync OTTO or an external Search Atlas sync does not intentionally remove a valid Yoast author entity. However, an OTTO deployment can interact with the SEO plugin output when both systems attempt to control schema on an OTTO-covered page. ⚙️ Why the conflict happens - Yoast generates a connected schema graph, commonly including WebPage, Article or BlogPosting, Organization, and Person entities. - OTTO may deploy page-level schema or schema-related recommendations through its WordPress integration. - When both outputs target the same page, WordPress can render competing JSON-LD blocks instead of one deduplicated graph. - Conflict handling may override, suppress, or incorrectly modify part of the Yoast graph, including the author Person entity. - Older conflict-handler behavior could produce an invalid value such as "@graph":false. ✅ Recommended workaround 1. Identify whether the affected URL is covered by an active OTTO deployment in Search Atlas. 2. Temporarily use one system as the schema owner for that URL. If Yoast is responsible for your author and article entities, do not deploy overlapping BlogPosting schema through OTTO. 3. Keep Yoast schema enabled and confirm that the post has a valid author assigned in WordPress. 4. Clear WordPress, plugin, server, and CDN caches, then request a fresh crawl of the page. 5. View the rendered page source and search for application/ld+json. Check whether multiple BlogPosting blocks or an invalid @graph value are present. 6. Validate the final output using Google’s Rich Results Test or Schema Markup Validator. Test the live URL after caches have cleared. 🧪 Troubleshooting checklist - Confirm the author profile is published and linked to the post in WordPress. - Check whether the author profile has a name and URL that Yoast can use for the Person entity. - Compare a page covered by OTTO with a similar page that is not covered. - Review the page source rather than only the WordPress editor or rendered visual page. - Look for duplicate Article, BlogPosting, WebPage, Organization, or Person entities. - Check Search Atlas plugin logs for unrecognized OTTO deployments or Yoast overrides. - After changing schema ownership, clear caches and retest the live page. 📌 Global BlogPosting schema support Global BlogPosting deployment should not be used as a workaround when Yoast already generates BlogPosting and author schema. Publishing both globally can increase duplication and may cause conflicting properties or missing connections in the Yoast graph. For reliable output, use Yoast as the source of truth for Yoast-managed article and author schema, or use OTTO for pages where OTTO is explicitly configured to own the complete schema output. Avoid deploying two independent global BlogPosting templates on the same URLs. 🛠️ When to request an investigation Contact support through the platform if the conflict continues after assigning one schema owner, clearing caches, and retesting the live source. Include the affected URL, whether OTTO is active for the page, the rendered JSON-LD output, and the relevant plugin log entries. This helps the team determine whether the issue involves duplicate schema, an invalid graph value, a deployment recognition problem, or an author configuration issue. 💬 Need help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛍️ Stop Shopify Product Title Overwrites

🔎 Identify the source of the overwrite If a Shopify product title changes after the page loads, the cause may be an active Atlas Brain deployment rather than a CMS Connector setting. Atlas Brain can apply changes to the live page after Shopify initially renders it. 1. Open the affected product in Shopify and note the original title. 2. Reload the product page and confirm whether the title changes after loading. 3. In Search Atlas, review the product’s Atlas Brain deployments or recommendations. 4. Check whether a deployment is active for the affected page, product, collection, or Shopify connection. 🛑 Undeploy Atlas Brain changes To stop the title overwrite, remove the active deployment that is applying the title change. 1. Open the Atlas Brain area in Search Atlas. 2. Locate the deployment affecting the Shopify product or connected site. 3. Open the deployment actions menu. 4. Select Undeploy, Remove deployment, or the equivalent rollback option shown in your account. 5. Confirm the action and wait for the deployment status to show that it is no longer active. Undeploying stops Atlas Brain from continuing to apply the deployed title change. It does not necessarily restore the previous Shopify title automatically. ✏️ Restore the correct Shopify title 1. In Shopify, open the affected product. 2. Enter the title you want customers to see. 3. Save the product. 4. Clear any applicable cache, then open the product page in a private browser window. 5. Reload the page and confirm the title remains unchanged after page load. 🔗 Check CMS Connector activity If the title still changes after Atlas Brain is undeployed, review recent CMS Connector activity for the product. Look for a sync or update that writes product titles to Shopify. Confirm that the connected Search Atlas content contains the intended title and that no active workflow is publishing the old value. Do not rely on unsupported settings such as “Sync Lock” or a CMS source-of-truth mode unless they are available and documented in your Search Atlas account. The first corrective action for this failure is to undeploy the active Atlas Brain deployment. ✅ Verify the fix - The affected Atlas Brain deployment is no longer active. - The Shopify product has the correct title. - The title remains correct after a full page reload. - No new CMS Connector activity is changing the title. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Delete OTTO Recommendations and Fix Article Titles

🗑️ How to Delete OTTO Recommendations If OTTO has generated title tag recommendations that are incorrect or that you do not want, you can remove them directly from the OTTO SEO dashboard. Deleted recommendations are removed from your task queue and will never be deployed to your site. 1. In the left sidebar, click OTTO SEO. 2. Scroll to the recommendations list and locate the title tag recommendation you want to remove. Use the filters to narrow the list by page URL or recommendation type. 3. Click the three-dot menu next to the recommendation. 4. Select Delete and confirm when prompted. To remove several recommendations at once, tick the checkbox beside each item, choose the bulk Delete action, and confirm. Deleting a recommendation never changes anything on your live site — it only clears the suggestion from OTTO. 💡 Why OTTO Suggests Title Changes You Already Made Sometimes OTTO recommends a new title tag even though you already updated the title yourself. These are called no-op recommendations — suggestions that would not actually change your page, because your current title already matches, or closely resembles, what OTTO is proposing. This typically happens when OTTO based its analysis on an earlier crawl of your site, before your manual edit went live. We are actively shipping an update so OTTO can tell the difference between a manual title edit and a genuine optimization opportunity. Until that update reaches your account, use this workaround: - Delete the no-op recommendation using the steps above. - Trigger a fresh crawl by going to OTTO SEO → Site Audit → Crawl Monitoring so OTTO picks up your current titles. - After the crawl completes, review any remaining recommendations and delete the ones that duplicate your manual edits. ✏️ Keeping Your Article Titles Exactly as You Set Them If you specified a title and Search Atlas appears to have invented a different one, the cause is almost always one of the following: - The SEO title field overrides the headline. The title tag used in search results comes from the SEO title field, not the article headline. If that field is left blank, the platform may auto-generate a title. - An OTTO title recommendation was deployed before your manual edit, overwriting your intended title. - The sync missed your latest save. See the next section for how to fix this. To lock in your preferred title: 1. In the left sidebar, click Content and open your article. 2. Open the article SEO settings and type your exact title into the SEO title field. Never leave this field blank. 3. Delete any pending OTTO title recommendation for that URL so it cannot overwrite your title when deployed. 4. Save the article, then re-sync it with your site. 🔄 Fixing Titles That Look Outdated After Syncing On WordPress sites, titles and meta descriptions are copied into Search Atlas by an asynchronous sync. Occasionally a sync misses a recent save, so the platform keeps displaying the old title even though the correct one is live on your site. 1. Open the article in Content, click Save again, and trigger a manual re-sync. 2. Run a fresh crawl under OTTO SEO → Site Audit → Crawl Monitoring. 3. Check the page in OTTO SEO → Site Audit → Page Explorer to confirm the fetched title now matches your live page. 4. If OTTO still shows the old version, delete the stale recommendation and reach out to support so we can force a refresh on our side. 🚫 Preventing Unwanted Title Recommendations - Always fill in the SEO title field for every article so OTTO has nothing to auto-generate. - Finish your title edits before running a crawl, so OTTO analyzes your final version. - Delete recommendations you disagree with — OTTO will not re-suggest a deleted recommendation for the same page unless the page changes significantly. - Re-crawl after bulk title updates so recommendation data stays current. 💬 Still Need Help? Our team can delete recommendation sets in bulk for you and investigate any title that refuses to sync. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Verify OTTO Pixel Installation & Compare Plans

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

Fix OTTO Site Quota and Reuse Your Pixel

Overview Every Search Atlas plan includes a set number of OTTO sites — these are quota slots that control how many websites you can activate OTTO on at one time. A common point of confusion is that deleting an OTTO project or removing the pixel from your website does not automatically free up that quota slot. This article explains how the quota system works and how to get help reusing your allotted pixel on a new URL. How OTTO Sites Quota Works Your plan comes with a fixed number of OTTO site slots. Here is what you need to know about how those slots are counted and managed: - A slot is occupied the moment a site is activated — connecting a domain and installing the OTTO pixel claims one quota slot. - Deleting the pixel from your website does not free the slot — removing the pixel code from your site is a front-end action only. The slot remains reserved inside Search Atlas until it is explicitly released from within the platform. - Deleting an OTTO project does not always free the slot — depending on your plan and account state, the system may retain an occupied slot even after a project is removed. Why You May Still See a Site in Use If you deleted your OTTO project and pixel but the dashboard still shows a site slot in use, the quota slot was not released during deletion. This is the most common reason customers are blocked from installing the pixel on a new URL. How to Get Your Quota Slot Released and Reassign Your Pixel Because the steps to release an occupied quota slot and reassign a pixel to a new URL depend on your specific account configuration, we recommend reaching out to the Search Atlas support team directly. A support agent can review your account, release the retained slot, and help you set up your pixel on your new URL. To get assistance, use the chat button on this page to contact our support team. Please have your account email and the new URL you want to assign your pixel to ready when you reach out.

🖼️ OTTO Alt Text Contradictory States and Credit Usage

🔍 Overview Some OTTO users notice that images appear to show contradictory alt text statuses — for example, an image flagged as Missing alt text while elsewhere in the interface it indicates that no new action is needed. This inconsistency can cause confusion and lead customers to manually trigger regeneration, consuming credits unnecessarily. This article explains why this happens, what the current behaviour means, and the best steps to take while a permanent fix is being worked on. ⚠️ What the Contradictory State Looks Like You may see one or more of the following in your OTTO project's image alt text section: - An image is listed as needing alt text attention in the dashboard. - The same image appears to require no further action when you inspect it directly. - Attempting to re-apply a fix does not resolve the flagged status, yet credits are still consumed. - Some images receive alt text suggestions that do not seem appropriate for their type. 🛠️ Why This Happens This behaviour is related to a known issue where OTTO's displayed status for an image can fall out of sync with its actual state. As a result, images may appear to need attention even when no change is required. This can lead to unnecessary credit consumption when customers attempt to force a resolution. The issue has been identified and a fix is in progress. Once deployed, images will be correctly classified and the dashboard will accurately reflect their real status. ✅ What You Should Do Right Now Until the fix is fully released, follow these steps to minimise unnecessary credit usage: 1. Do not mass-regenerate flagged images. If an image appears to already have a valid alt attribute when you inspect it, forcing regeneration will consume a credit without improving the result. 2. Review the actual alt text value first. Before taking any action on a flagged image, inspect the current alt text value shown in the interface. If a meaningful description is already present, no further action is needed. 3. Skip images that appear correctly described. Focus credit usage on images that are genuinely missing or have clearly inadequate alt text. 📞 Need Help? If you are experiencing this issue and are concerned about credits that may have been consumed due to the contradictory state, please reach out to our support team. Have the following ready to speed up the process: - Your OTTO project name - The specific images or pages affected - An approximate timestamp of when the issue was observed If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 OTTO Pixel Shopify Verification and Plan Comparison

🧩 Overview After installing the OTTO pixel in Shopify, it is common to check whether the code is live by viewing the page source. If you saved the code correctly but cannot find it in the source, this does not necessarily mean the installation failed. This article explains why the pixel may not appear immediately and how to verify it is working. 🤔 Why the Pixel May Not Appear in Page Source There are two common reasons the OTTO pixel code may not be visible when you view the raw page source in your browser. - Crawl phase delay: After saving the pixel in Shopify, OTTO begins processing your site. During this phase the pixel may not yet be injected into every page. This process can take a short time to complete depending on your site size. - Dynamic script injection: Shopify themes and third-party apps can load scripts dynamically after the initial HTML is delivered. The view-source method shows only the raw HTML returned by the server. Scripts that load asynchronously or are injected by JavaScript after the page renders will not appear in this view even when they are fully active. ✅ How to Confirm the Pixel Is Working Use the steps below to verify the pixel is live without relying on view-source. 1. Open your website in Google Chrome. 2. Right-click anywhere on the page and select Inspect to open Developer Tools. 3. Go to the Network tab and reload the page. 4. In the filter search bar type otto or the pixel script name to look for a matching network request. 5. You can also log in to the Search Atlas platform and check your OTTO site status to confirm the pixel is communicating with the platform. If your OTTO site status shows as connected and the pixel request appears in the Network tab, the installation is successful even if view-source does not display it. 🛠️ Reinstalling the Pixel in Shopify If the Network tab shows no pixel activity and your OTTO status remains inactive after some time, follow these steps to reinstall. 1. Log in to Search Atlas and navigate to your OTTO site settings to copy the pixel code. 2. In your Shopify admin, locate the theme editor and paste the pixel code in the appropriate location, then save. 3. Reload your live site and repeat the Network tab check described above. 📋 Subscription Plan Questions If you have questions about which sites or features are included in your current subscription plan, the best approach is to contact our support team directly. A team member can review your account, clarify exactly which sites and features are covered under your plan, and walk you through any upgrade or adjustment options that may be available to you. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔄 Restoring Recurring Platinum Account Benefits

💡 What This Article Covers If your recurring Platinum account benefits are no longer available, this guide explains what information to provide when reporting the issue. 🛠️ How to Report Missing Benefits Contact our support team so they can investigate why your recurring Platinum benefits are no longer available. Provide your account details, the benefits that are missing, and when you first noticed the issue. Support can review the reported issue and advise on the next steps. ✅ What to Include in Your Request - Your account or workspace name. - The Platinum benefits that are missing, including any OTTO SEO or AI Visibility benefits. - When the benefits stopped appearing or reset. - Any relevant error message or recent account change. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🔧 Fix Low OTTO Crawl Volume and Schedule

Overview If OTTO is indexing significantly fewer pages than your site contains—for example, 16,000 of 65,000 pages—this is a crawl volume issue, not a plugin installation problem. This article explains the most common root causes of low crawl coverage and how to diagnose them. Why Is OTTO Only Reaching a Subset of Pages? There are five primary reasons OTTO may index fewer pages than expected. Work through each one before assuming a technical fault. 1. Crawl budget limits: Large sites have a finite crawl budget—the number of URLs a crawler will fetch in a given period. If your site has 65,000 pages, OTTO prioritises the most discoverable and link-connected pages first. Pages buried deep in your architecture or receiving few internal links are reached in later crawl cycles. To expand coverage, improve internal linking to surface orphaned or deep pages. 2. Noindex tags on large page groups: Template-level noindex meta tags or HTTP headers can silently exclude entire categories, tags, paginated archives, or product filter URLs. Audit your page templates—especially e-commerce faceted navigation, paginated series, and auto-generated tag pages—to confirm intended pages are not marked noindex. 3. Robots.txt restrictions: A Disallow rule in your robots.txt file can block OTTO from crawling entire URL path segments. Review your robots.txt (accessible at yourdomain.com/robots.txt) and confirm that no rules accidentally block large sections of the site such as /products/, /blog/, or /category/. 4. Sitemap gaps: If your XML sitemap does not include all expected pages—or if it contains broken URLs, incorrect priorities, or is not submitted—OTTO has no reliable map to follow. Verify your sitemap is complete, up to date, and submitted within the platform. 5. Site structure and internal linking depth: Pages more than three to four clicks from the homepage are harder for any crawler to reach within a standard crawl budget window. Flatten your site architecture where possible and ensure key pages are reachable through prominent internal links. What to Have Ready When Escalating If you have reviewed all five areas above and crawl coverage remains unexpectedly low, please gather the following before contacting support: - Your project name and the domain being crawled - The total number of pages on your site and the number OTTO has indexed - A copy of your robots.txt file contents - Your XML sitemap URL - Any specific URL patterns or sections of the site that appear to be missing from the crawl If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ OTTO Schema Changes & Go High Level Integration

🔍 Why Schema Changes Don't Appear in Go High Level When OTTO applies schema markup to your Go High Level (GHL) website, the changes are injected directly into your live website — they do not pass through the Go High Level dashboard or editor. This means you will not see any new code blocks, widgets, or edits inside your GHL account, and that is completely expected behavior. OTTO works at the DNS/CDN layer, pushing structured data directly to the publicly accessible version of your site. Your GHL dashboard simply reflects the template and content you have manually built there — it is not a mirror of what is live on the internet. ✅ How to Confirm Schema Changes Are Live Because the changes bypass the GHL editor, you need to verify them on the live site directly. Use any of these methods: - Google's Rich Results Test: Go to search.google.com/test/rich-results, enter your page URL, and run the test. OTTO-injected schema will appear here if it is active. - Schema Markup Validator: Visit validator.schema.org and paste your URL to see all structured data detected on the page. - View Page Source: Open your live page in a browser, right-click, and select View Page Source. Search for application/ld+json — this is where OTTO injects schema markup. If schema appears in any of these tools, the changes are successfully published to the internet, even though nothing has changed inside your GHL dashboard. ⚙️ How OTTO Injects Schema on Go High Level Sites OTTO uses a live environment injection method, which means: 1. OTTO connects to your website through the Search Atlas platform. 2. Schema markup is written as a JSON-LD script tag and delivered directly to your live pages. 3. Visitors and search engine crawlers see the structured data immediately — no manual publishing step is required on your end. 4. Your Go High Level account remains unchanged because the injection happens outside the GHL content management layer. This approach keeps your GHL workflow intact while still giving search engines the rich structured data they need to understand your content. 📊 Understanding Google Search Console Schema Errors Even after OTTO successfully injects schema, you may still see errors or warnings in Google Search Console (GSC). Here is what you need to know: - Indexing delays are normal. Google does not re-crawl pages instantly. It can take anywhere from a few days to several weeks for GSC to reflect the latest state of your schema markup. - Errors may already be resolved. If GSC is showing an error but your Rich Results Test passes cleanly, the error is likely from a previous crawl. Use the Validate Fix button inside GSC to request a re-crawl of the affected pages. - Property mismatch warnings. Some GSC warnings are informational (e.g., recommended but not required fields). These will not prevent your pages from appearing in search results. - Critical errors need attention. If the Rich Results Test also flags an error on the same page, open the OTTO SEO V3 section in Search Atlas (left sidebar → OTTO SEO → SEO Automation) and review OTTO's active deployments to ensure the correct schema type is applied. 🚀 Steps to Resolve Remaining Search Console Errors 1. Confirm schema is live using the Rich Results Test or Schema Markup Validator as described above. 2. Log in to Google Search Console and navigate to Enhancements in the left menu. 3. Select the schema type flagged (e.g., FAQ, Local Business, Article) and open the error details. 4. Click Validate Fix to ask Google to re-crawl the affected URLs. 5. Allow 7–14 days for Google to process the re-crawl and update the status. 6. If errors persist after re-validation, check the specific error message — it may point to a missing required field that OTTO needs to be updated to include. 💡 Key Things to Remember - OTTO schema changes are live immediately on the internet even though your GHL dashboard shows no changes. - Always verify schema using external tools like the Rich Results Test, not the GHL editor. - Google Search Console errors often lag behind actual fixes — use Validate Fix to speed up the review process. - Persistent or recurring GSC errors after re-validation may require a review of your OTTO configuration inside Search Atlas. 🙋 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔌 Fix OTTO Pixel Installation on GoHighLevel

🧭 Overview If you have added the SearchAtlas OTTO tracking pixel to your GoHighLevel (GHL) site but the Search Atlas dashboard still shows the pixel as undetected — or you are seeing a JSON parsing error — the issue is almost always caused by how GHL handles custom code blocks. This article walks you through the correct installation method and the most common failure points. 📋 Before You Begin Confirm the following before troubleshooting: - You have access to your GoHighLevel funnel or website builder as an admin. - You have your OTTO pixel snippet ready. To find it, go to OTTO SEO in the left sidebar, open SEO Automation (URL: /seo-automation-v3), open your OTTO workspace, and copy the pixel script from the tracking setup panel. - The site is published and publicly accessible — the dashboard cannot detect the pixel on unpublished pages. ⚠️ Why GHL Installations Commonly Fail GoHighLevel uses a block-based editor that processes custom code differently from standard HTML page builders. Three failure points account for almost all detection problems: - Wrong placement location: Pasting the script into a content block body instead of the dedicated Header Tracking Code field causes the script to be wrapped in additional markup, which breaks JSON parsing. - JSON parsing error: GHL sometimes auto-encodes quotation marks inside custom code blocks. When the pixel script contains JSON-formatted configuration data, these encoded characters corrupt the payload and produce a JSON parsing error in the browser console. - Script added to a single page only: Adding the script to one page's settings instead of the site-wide header means the pixel fires inconsistently, causing intermittent or zero detection in the dashboard. ✅ Correct Installation Method Follow these steps exactly to install the OTTO pixel site-wide in GoHighLevel: 1. Log in to GoHighLevel and open the Sites section from the left menu. 2. Select the website or funnel where you want to install the pixel. 3. Click Settings (the gear icon) for that site — do not open an individual page editor. 4. Scroll down to the Header Tracking Code field. This is the only field that injects code cleanly into the <head> tag without encoding characters. 5. Paste your OTTO pixel snippet directly into the Header Tracking Code field. Do not wrap it in any additional tags. 6. Click Save and then Republish the site. 7. Wait 2–3 minutes, then return to OTTO SEO in the left sidebar in Search Atlas, open SEO Automation, and refresh the OTTO workspace to check detection status. 🚫 What to Avoid - Do not paste the pixel script into a custom HTML or code content block inside the page editor. GHL re-encodes quotes in these blocks and will break the script. - Do not use the Footer Tracking Code field for the OTTO pixel. Some GHL themes render the footer after the main content loads, which can cause the pixel to fire too late or not at all on fast-loading pages. - Do not add the script only to individual page settings. Always use the site-level Header Tracking Code field for consistent, site-wide detection. 🔍 Verifying the Pixel Is Firing Correctly After republishing, verify the installation using your browser before checking the Search Atlas dashboard: 1. Open your published GHL site in Google Chrome. 2. Right-click anywhere on the page and select Inspect, then open the Network tab. 3. Reload the page and filter requests by typing otto or your pixel domain in the search bar. 4. Confirm a network request is being made and that the response status is 200. 5. Open the Console tab and check that there are no JSON parsing errors. If a JSON error still appears, the script was most likely pasted into a content block rather than the Header Tracking Code field — repeat the installation steps above. 🛠️ Still Seeing a JSON Parsing Error? If you followed the steps above and the JSON parsing error persists, check these additional causes: - Conflicting scripts: A third-party script on the same page may be interfering. Temporarily disable other custom scripts in the Header Tracking Code field to isolate the conflict. - Caching: GoHighLevel caches published pages aggressively. Clear the site cache from the GHL Settings panel and hard-reload the page in your browser (Ctrl + Shift + R on Windows, Cmd + Shift + R on Mac). - Pixel snippet modified: Ensure the pixel snippet is copied exactly as provided in the Search Atlas dashboard. Any manual edits — including added line breaks or extra spaces — can invalidate the JSON structure. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔄 Reconnect OTTO After Migration

🔄 When to follow these steps Use this guide after moving your site to a new server, changing hosting providers, updating DNS, switching from Cloudflare, or reinstalling OTTO on WordPress. A connected plugin alone does not complete the migration process. After the move, you must recrawl the site and manually reprocess OTTO so it can use the current site configuration. ✅ Confirm the new site is ready 1. Confirm the domain resolves to the new server. 2. Open the live website and verify that key pages load correctly. 3. Confirm WordPress is installed and the OTTO plugin is active on the new site. 4. Check that the site uses the correct HTTPS version and preferred domain. 5. Review the OTTO installation instructions in OTTO SEO → Installation Guide if the plugin was reinstalled or its installation method changed. 🔌 Check the OTTO connection Open OTTO SEO → All Sites and select the affected site. Review its current connection status and confirm that the site is associated with the correct WordPress installation. If the connection was removed during the migration, follow the available installation or connection instructions for the site. Do not treat a successful connection check as the final migration step. 🕷️ Recrawl the site 1. Go to OTTO SEO → Overview. 2. Select the affected site. 3. Choose Scan to start a new crawl. 4. Wait for the crawl to finish before continuing. You can review crawl activity in OTTO SEO → Crawl Monitoring. A new crawl helps OTTO read the current version of the site after the server or hosting change. ⚙️ Manually reprocess OTTO After the recrawl is complete, manually reprocess OTTO for the affected site using the available site actions in OTTO SEO → All Sites or OTTO SEO → Overview. This step is required after the migration. It refreshes OTTO's processing for the newly crawled site and should be completed even when the plugin connection appears active. 🔍 Verify the result - Confirm the site is listed under the correct OTTO site entry. - Check that the latest crawl reflects the new server and current pages. - Review Crawl Monitoring for errors or incomplete activity. - Verify that OTTO recommendations or changes are associated with the current installation. - Run another scan or reprocess only if the first operation did not complete. 🛠️ If the site still does not work Review the domain, HTTPS settings, WordPress installation, and OTTO installation method again. If the site was duplicated, make sure you are working with the correct OTTO site record and not an older entry. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

❄️ Deep Freeze OTTO: Billing, Changes & Quota Reuse

🧭 Overview When you no longer need an active OTTO project, you may want to Deep Freeze it, cancel an associated billing slot, or understand how your quota can be reused. This article explains the key concepts involved so you know what to expect and what to prepare when reaching out to our team. ❄️ What Is Deep Freeze? Deep Freeze is an OTTO project state that suspends active optimization while keeping all previously deployed changes live on your site. Think of it as pausing OTTO without rolling back the work it has already done. - Deployed changes stay live: SEO improvements OTTO has already pushed to your site are intended to remain active after freezing. Deep Freeze does not revert or remove them. - Active monitoring stops: OTTO will no longer crawl, detect new issues, or deploy additional changes while frozen. - The project is preserved: Your OTTO project history, settings, and configuration are saved so you can unfreeze later if needed. 💳 Billing Slots and Deep Freeze Questions about how Deep Freeze affects your active OTTO slot count, how to cancel an extra slot after freezing a project, and the timeline for quota reuse depend on your specific subscription and account configuration. Because these details vary, our support team will need to review your account directly to confirm the correct steps and timing for your situation. When you contact us, please have the following ready: - The name of the OTTO project you want to freeze or have already frozen - The domain it is connected to - Your current subscription plan - A description of what you are trying to accomplish (e.g., cancel a slot, reuse quota on a new site, confirm a change is still live) ✅ Will My Deployed Changes Stay Live? Deep Freezing a project is designed so that changes OTTO has already deployed to your site remain intact. The only thing that stops is new automated activity from OTTO. However, if you have any concerns about whether specific changes are still active after freezing or cancelling a slot, our team can verify this for your account. 🔄 Reusing Quota on Another Site If you want to use your OTTO quota or a freed slot on a different site after freezing an existing project, the available options and timeline depend on your account setup. Please reach out to our team with your project and domain details so we can guide you through the correct process. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

💡 Wix OTTO SEO Title Tags and Credit Refunds

🔍 What This Article Covers If you used Search Atlas credits to generate OTTO SEO title tag suggestions for your Wix site and expected them to publish automatically, this article explains how the Wix integration works, why auto-sync is not currently supported, and what steps to take if you believe credits were spent in error. ⚙️ How the Wix Integration Works Search Atlas connects to Wix through an authorised credential link. Once connected, the platform can analyse your Wix pages and generate AI-powered SEO suggestions — including title tags — directly inside the Search Atlas dashboard. However, there is an important limitation to be aware of: - OTTO SEO title tag suggestions do not auto-publish to your Wix site. They are generated as recommendations only. - To apply a suggested title tag, you must manually copy it and update the field inside your Wix site editor or Wix SEO settings panel. - Credits are consumed at the point of generation, not at the point of publishing. This behaviour applies to all Wix-connected sites regardless of your subscription plan. 📋 Why Credits Are Used at Generation When you request OTTO SEO title tag suggestions, the platform immediately uses computing resources to analyse your page content, evaluate keyword relevance, and produce optimised recommendations. This process consumes credits whether or not you choose to apply the suggestions to your site. This is consistent with how AI-generated content works across other areas of the platform — credits reflect the cost of generation, not the outcome. 🛠️ How to Apply Title Tag Suggestions to Your Wix Site 1. Open your Search Atlas dashboard and navigate to the page where your AI title tag suggestions were generated. 2. Copy the recommended title tag text. 3. Log in to your Wix account and open the Wix Editor or go to Marketing & SEO > SEO Tools > SEO Basics. 4. Locate the relevant page and paste the title tag into the Title Tag field. 5. Save and publish your changes in Wix. Completing these steps ensures your AI-generated title tag is live on your site. 💬 Requesting a Credit Review If you believe credits were spent due to unclear guidance about how the Wix integration works, you may be eligible for a credit review. Search Atlas does not offer automatic refunds for generated suggestions, but our team can assess your case individually. To request a review, please have the following information ready: - The date and approximate time the credits were used - The number of credits you believe were spent in error - A brief description of what you expected to happen versus what occurred Credit reviews are assessed on a case-by-case basis and are not guaranteed. Submitting a request does not automatically result in a credit restoration. 🚀 Preventing This Issue in the Future To avoid unexpected credit usage going forward: - Before generating AI suggestions, confirm that your Wix credentials are connected and in an active state inside the Search Atlas dashboard. - Review the suggestion preview before confirming generation if a preview option is available for your plan. - Treat all AI-generated content as a starting point that requires manual review and manual publishing on your Wix site. If your Wix credentials appear disconnected or you are prompted to reconnect your site, resolve the connection first before generating new suggestions to ensure credits are used effectively. 🙋 Need Further Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

💳 Understanding OTTO SEO Site Slots and Charges

🔍 What Are OTTO SEO Site Slots? OTTO SEO is Search Atlas's AI-powered on-page SEO automation tool. Every Search Atlas plan includes a set number of OTTO SEO site slots — these are the websites you can actively run OTTO SEO on at the same time. Your plan includes a default number of OTTO SEO site slots. If you want to activate OTTO SEO on more websites than your plan allows, you will need to purchase additional slots, called top-ups. 📊 Why You May See Extra Charges If you activated OTTO SEO on more sites than your plan includes, Search Atlas automatically prompts you to purchase top-up slots. Each top-up adds one additional site slot and is billed separately from your base subscription. Common reasons customers see unexpected charges include: - Activating OTTO SEO on a new domain without realising the base plan limit had already been reached - Purchasing multiple top-ups in a single session (for example, three top-ups purchased on the same day) - Confusion between the number of sites added to the platform and the number of sites with OTTO SEO actively enabled Only sites with OTTO SEO switched on count against your slot limit. Adding a site to your Search Atlas account does not automatically consume a slot. 🛠️ How to Check Your Current OTTO SEO Usage 1. Log in to Search Atlas and navigate to the OTTO SEO section of your account. 2. Review the list of sites shown. Any site displaying an active OTTO SEO status is using one of your slots. 3. Compare the number of active sites against the slots included in your plan plus any top-ups you have purchased. If you see more active sites than you intended to enable, you can deactivate OTTO SEO on any site to free up a slot for future use. 💡 Understanding Top-Up Billing Top-up slots are purchased on demand and charged at the point of activation. Each top-up purchase adds one site slot, and multiple top-ups purchased on the same day will each appear as a separate line item on your invoice. For specific details about how top-up slots apply to your plan and billing cycle, please contact the support team. 🔄 Can You Get a Refund for Top-Up Charges? Refund eligibility for top-up purchases is reviewed on a case-by-case basis by the Search Atlas billing team, and refunds are not guaranteed. When the team reviews a request, they will typically consider: - Whether the top-up slots were used (i.e., whether OTTO SEO was actively run on the additional sites) - How recently the charges were made - Whether the purchase appeared to be unintentional Please be aware that based on the nature of OTTO SEO top-up purchases, refund requests may be denied even if the charge was unexpected. 📋 How to Request a Billing Review If you believe you were charged incorrectly for OTTO SEO top-up slots, please reach out to the support team directly with your account details and the specific charges in question. The billing team will review your case and respond as soon as possible. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Delete Frozen OTTO Projects Blocked by Quota

🔍 Understanding the Problem When you downgrade your Search Atlas plan, OTTO projects that exceed your new quota become frozen. Because frozen projects cannot be unfreeezed without a higher-tier plan, and because the platform previously blocked deletion of frozen projects, many users found themselves stuck — unable to remove old projects or add new ones. Good news: this has been resolved. Search Atlas engineering has shipped updates that allow frozen and deep-frozen OTTO projects to be deleted, freeing up your quota slot so you can add a new project within your current plan limits. ⚙️ What You Can Do Now If you are on a plan that limits you to a set number of active OTTO projects, you can now delete frozen projects directly to reclaim those slots. Follow the steps below. 1. Open the platform and go to Left sidebar → OTTO SEO → All Sites (SEO Automation). 2. Review the list of your existing OTTO sites. Frozen projects will be visually indicated as inactive or locked. 3. Select the frozen project or projects you want to remove. 4. Delete the selected projects. The slot should be freed immediately, allowing you to create or activate a new OTTO project within your quota. If the deletion option does not appear for a specific frozen project, or if deleting a project does not free your slot as expected, do not attempt to work around the issue — contact support directly using the instructions at the bottom of this article. 📊 A Note on Quota and Slot Timing In some cases there was a known delay of up to 24 hours before a deleted OTTO project fully released its quota slot. This issue has been addressed by the engineering team. If you delete a project and your slot does not appear to be freed after a reasonable wait, reach out to support so the team can verify your account on the backend. ⚠️ When You Need the Support Team There are situations where self-service deletion may not be possible — for example, if a project appears frozen but cannot be selected or deleted through the interface, or if the project no longer exists on your end but is still counting against your quota. In these cases, the support team can manually remove the affected domains from the backend to restore your available slots. When contacting support, have the following ready: - The full domain name (or names) you want removed - Confirmation that these projects are frozen and you no longer need them - Your current plan and how many OTTO slots it allows 💡 Tips to Avoid This Issue in the Future - Before downgrading your plan, review how many active OTTO projects you have and delete any you no longer need. - If you anticipate a plan change, proactively reduce your active OTTO sites to match the quota of your target plan. - Regularly audit your OTTO projects under Left sidebar → OTTO SEO → All Sites (SEO Automation) to keep your list clean and within limits. 🆘 Get Further Help If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🤖 OTTO Quota Release Timeline and Project Freeze

🧭 Overview Each Search Atlas account includes a fixed number of OTTO activation slots. When you activate OTTO on a project, it occupies one of those slots. If you want to move OTTO to a different project but your slots are full, you must first freeze the existing project. However, the slot is not released immediately — there is a mandatory 14-day waiting period before that quota becomes available again. ⏳ The 14-Day Quota Release Window When you freeze an OTTO-activated project, Search Atlas begins a 14-day release period. During this time: - Your slot count will continue to show as fully used (for example, 5/5). - You will not be able to activate OTTO on a new project until the release period ends. - Refreshing your dashboard, clearing your browser cache, or logging out and back in will not speed up or bypass this process. After the 14-day period is complete, the slot is automatically returned to your available quota, and you can activate OTTO on a new project. 🔄 How to Free Up an OTTO Slot Step by Step 1. Go to OTTO SEO in the left sidebar and open SEO Automation (URL: /seo-automation-v3). 2. Open the project that currently has OTTO activated and that you no longer need it on. 3. Locate the OTTO activation toggle or settings panel for that project. 4. Select the option to Freeze the project. Freezing pauses all OTTO activity and begins the quota release countdown. 5. Wait 14 days from the freeze date. You will receive no in-app notification when the slot is released, so make a note of the date. 6. After 14 days, return to OTTO SEO in the left sidebar and open SEO Automation, then open the project where you want to activate OTTO. 7. Activate OTTO on your new project as normal. ❗ Important Distinctions: Freeze vs. Delete Deleting a project and freezing a project are not the same action when it comes to quota release: - Freezing a project is the correct method to begin the 14-day quota release process. OTTO recognises this action and starts the countdown. - Deleting a project removes the project from your dashboard and releases your OTTO slot right away (the counter may take a short time to refresh because of caching). The 14-day hold only applies to projects put into Deep Freeze, not to deleted projects. If you delete a project, its slot is freed immediately, though the displayed counter may take a short time to refresh. 📋 Common Questions My dashboard shows 5/5 slots used even though I deleted the project. Is this a bug? Deleting a project releases its slot right away, but the counter may take a short time to refresh because of caching. The 14-day hold applies only to projects put into Deep Freeze, not to deleted projects. Can Search Atlas support manually release my slot early? Slot releases follow a fixed system timeline and cannot be manually overridden or expedited by the support team. How do I know when my slot has been released? Navigate to OTTO SEO in the left sidebar and open SEO Automation to check your OTTO slot counter. Once the 14-day period has passed, the counter will update automatically and you will be able to activate OTTO on a new project. Does freezing a project affect my SEO data or rankings? Freezing pauses all OTTO automation on that project. Your historical data and settings are preserved, but OTTO will stop making active changes until the project is reactivated or the slot is reassigned. ✅ Quick Reference Summary - Freeze the project to begin the slot release process. - Wait 14 days for the quota to be returned to your account. - Deleting a project releases its slot right away (the counter may take a short time to refresh); the 14-day hold applies only to Deep Freeze. - Cache clearing and dashboard refreshes have no effect on quota release timing. - After 14 days, activate OTTO on your new project from the SEO Automation page inside OTTO SEO. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

📰 Fix Press Release Hyperdrive Credit Errors

🔍 Overview When you attempt to publish a press release using Hyperdrive, Search Atlas checks your available credit balance in real time. If the system detects that your balance is insufficient — even if you believe you have enough credits — a publication error will appear and the press release will not be submitted. This article walks you through how to verify your balance and resolve the issue. 📊 Step 1: Check Your Hyperdrive Credit Balance Before troubleshooting the error, confirm your actual available balance: 1. Log in to your Search Atlas account. 2. Navigate to the top-right Avatar Menu (👤) → Billing (Billing) page. 3. Locate the Hyperdrive Credits panel and note your current balance. 4. Compare the displayed balance against the credit cost shown on the press release publication screen. If your balance is lower than the required amount, you will need to purchase additional Hyperdrive credits before publishing. ⚙️ Step 2: Refresh Your Session Occasionally, a cached session may display an outdated credit balance, causing a mismatch between what you see and what the system reads. To rule this out: 1. Save any draft content you are working on. 2. Fully log out of Search Atlas. 3. Clear your browser cache and cookies, or open Search Atlas in a private/incognito window. 4. Log back in and navigate back to your press release. 5. Check the credit balance again and attempt to publish. 🛠️ Step 3: Verify Credit Type and Plan Eligibility Not all credits are interchangeable inside Search Atlas. Keep the following in mind: - Hyperdrive Credits are specifically required for press release distribution. General platform credits or other credit types cannot substitute for them. - Confirm that your current subscription plan includes access to Hyperdrive press release publishing. - If your credits were recently purchased or added by a team administrator, allow a few minutes for the balance to sync, then refresh your session as described in Step 2. 💡 Step 4: Review Recent Credit Usage It is possible that recent activity consumed credits you were not aware of. To check: 1. Go to your Billing or Usage History section. 2. Review recent Hyperdrive transactions to see if credits were used for other press releases or services. 3. If you notice any unrecognised charges or unexpected deductions, make a note of the dates and amounts before contacting support. 🚀 Step 5: Attempt Publication Again Once you have confirmed your balance is sufficient and your session is refreshed, retry publishing your press release: 1. Open the press release you want to publish. 2. Review all required fields to ensure the submission is complete — incomplete submissions can sometimes trigger misleading error messages. 3. Click Publish and monitor the confirmation screen. If the error persists after completing all steps above, do not restart repeatedly, as this will not resolve an underlying balance or account issue. ⚠️ Common Reasons the Error Appears - Your Hyperdrive credit balance is genuinely below the required amount for the selected distribution tier. - A recent purchase has not yet been reflected due to a brief sync delay. - Your session is displaying a stale balance from before a credit deduction. - Your subscription plan does not include Hyperdrive press release access. - A temporary platform issue is affecting credit reads — in this case, waiting a few minutes and retrying often resolves it. 🙋 Still Seeing the Error? If you have followed all the steps above and the publication error continues, our support team can investigate your account balance, recent transactions, and any platform-side issues directly. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔗 DKN Generation and OTTO Quota Dependency Explained

🧠 Overview: Why Are DKN and OTTO Quota Connected? This is a common and understandable question — and the short answer is: this is intentional by design, not a bug. When you generate content using the Done-for-You Knowledge Network (DKN), Search Atlas automatically creates and activates an OTTO site as part of the process. Because each DKN generation spins up a new OTTO-managed site, it consumes one slot from your OTTO Sites quota. The two features are architecturally linked — DKN cannot function without an underlying OTTO site to manage the deployment. This means that even if you are not actively thinking about OTTO when you work with DKN, your available OTTO Sites slots directly control how many DKN generations you can create. 📊 How the Quota Dependency Works Here is a simple breakdown of the relationship: - Each DKN generation = 1 OTTO Site consumed. When you initiate a DKN generation, the platform reserves one OTTO Sites slot for that project. - Your OTTO Sites limit is set by your plan. Your current plan determines how many OTTO Sites — and therefore how many DKN generations — you can have active at one time. - Reaching your Sites limit blocks new DKN generations. If all your OTTO Sites slots are in use, the platform will prompt you to increase your quota before you can create a new DKN project. This prompt is expected behaviour, not an error. 🔍 Why You Might See the Quota Warning You will see a message asking you to increase your OTTO quota when either of the following is true: - You have used all available OTTO Sites slots on your current plan. - You have existing OTTO sites (created manually or via previous DKN generations) that are still active and occupying slots. The platform does not distinguish between manually created OTTO sites and DKN-generated ones when counting against your limit — all active sites share the same pool. ✅ What You Can Do to Create More DKN Projects You have two options to free up capacity for new DKN generations: 1. Delete sites you no longer need. If you have active OTTO sites — whether created manually or through previous DKN generations — that you no longer use, removing them will free up slots and allow new DKN generations without upgrading your plan. 2. Upgrade your OTTO Sites quota. If you need more active DKN projects simultaneously, you can increase your Sites limit by upgrading your plan or purchasing an OTTO Sites add-on. This is the right path if you want to keep all existing sites active and still create new DKN projects. 🚫 Is This a Bug? No — the quota dependency between DKN and OTTO Sites is intentional design. DKN generation is built on top of the OTTO infrastructure, so every DKN project requires an OTTO site to exist. The quota prompt you see is the platform correctly enforcing your plan's site limit, not a malfunction. If you believe your site count shown in the platform does not accurately reflect the sites you actually have active, or if you are seeing the quota warning even though you appear to have available slots, that would indicate an unexpected issue worth investigating. In that case, please reach out to our team using the instructions below. 💬 Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔄 Free an OTTO Slot After Deep Freeze

🧊 What Happens When You Deep Freeze an OTTO Site When you Deep Freeze an OTTO site — for example, after offboarding a client — the quota slot that site occupied is not released immediately. There is a 14-day holding period before the slot becomes available again. During this window, your total OTTO site count remains unchanged, which can prevent you from activating a new site. 💡 If You Cannot Wait — Request a Temporary OTTO Site If the 14-day freeze window conflicts with your billing cycle or a live project deadline, our specialized team can grant a free temporary OTTO site to cover the gap. This is the same resolution our support agents have applied for customers in this situation. Because this requires manual review by a higher-tier team, it cannot be self-served at this time. To request it as quickly as possible: 1. Open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team. 2. Explain that you have a Deep Frozen site holding a slot and that the 14-day wait conflicts with your billing cycle or active work. 3. Have your project name and the approximate date the Deep Freeze was applied ready to share, so the team can review your case efficiently. 4. The team will escalate your case and, where eligible, provision a temporary OTTO site for the duration of the freeze window. 🚫 How to Avoid This Issue in the Future - Plan freezes around your billing date. If you know a client project is ending, try to Deep Freeze it shortly after your billing cycle renews so the 14-day window expires before your next cycle begins. - Track your frozen sites. Keep a note of when each site was Deep Frozen so you can anticipate when slots will become available again. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🗂️ Delete Deep-Frozen OTTO Projects and Free Quota

🔍 Overview A deep-frozen OTTO project is one that has been inactive long enough for the platform to suspend it automatically. Deep-frozen projects still count against your OTTO site quota even though they are not actively running. If you have reached your site limit and cannot add a new site, a deep-frozen project may be the cause. This article explains the general process for removing a deep-frozen project and what to expect regarding quota after deletion. ❄️ What Is a Deep-Frozen Project? When an OTTO project remains inactive for an extended period, Search Atlas automatically deep-freezes it to preserve system resources. Deep-frozen projects: - Remain visible in your OTTO dashboard - Continue to occupy one slot of your OTTO site quota - Cannot be edited or optimised in their frozen state - May require an unfreeze action before deletion options become accessible 🔓 Step 1 — Unfreeze the Project 1. Navigate to your OTTO dashboard. 2. Locate the deep-frozen project in your project list. It will be visually marked as frozen. 3. Open the project and look for an option to unfreeze or reactivate it. The platform will reactivate the project so that management options become available. 🗑️ Step 2 — Delete the Project 1. Return to the main OTTO dashboard. 2. Find the project you just unfroze. 3. Look for the action menu associated with that project row. 4. Select the Delete option from the available actions. 5. Confirm the deletion in the prompt that appears. Important: If you do not see a delete option, confirm that the unfreeze step completed successfully before proceeding. ⏳ Step 3 — Quota After Deletion Deleting a deep-frozen OTTO project may not immediately restore your quota. Depending on the project's state at the time of deletion, there may be a processing period before the quota slot is released back to your account. You do not typically need to take any manual action — the quota update should happen automatically once that period ends. If you have deleted a deep-frozen project and your quota does not appear to have updated as expected, our support team can investigate and confirm the status of your quota release. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚡ Instant Indexing Requires a Pro or Agency Plan

🔍 What This Error Means If you attempt to activate Instant Indexing on a project and receive an HTTP 400 'Unable to activate indexing' response with is_transient: false, your current subscription does not include access to this feature. This is a plan-level restriction, not a configuration problem. Importantly, this error will appear even when every other prerequisite is correctly in place — including the tracking pixel installed on your site, Google Search Console (GSC) connected, and your sitemap registered. A non-transient 400 error means no amount of reconfiguration will resolve it; a plan upgrade is required. ​ ✅ Which Plans Include Instant Indexing Instant Indexing is available exclusively on the following Search Atlas subscription plans: - Pro - Agency Starter plans and free trials do not include access to Instant Indexing. If your account is on a lower-tier plan, every activation attempt will return a non-transient 400 error, regardless of your project's setup. ​ 🔧 How to Upgrade Your Plan 1. Log in to Search Atlas and click your account avatar in the top-right corner of the platform. 2. Select Billing from the dropdown menu. 3. Go to the Plans & Top-ups tab (Billing). 4. Select the Pro or Agency plan and complete the checkout steps. 5. Once your upgrade is confirmed, navigate to Left sidebar → OTTO SEO → All Sites → [your project card] → Instant Indexing and activate the feature for your project. 📋 Already on Pro or Agency? Check These First If you are already on a qualifying plan and still see the HTTP 400 error, confirm the following before contacting support: - Pixel installed: Verify the Search Atlas tracking pixel is present in the <head> of your site and loading without errors. - GSC connected: Go to Avatar → Settings → Integrations and confirm Google Search Console shows a green connected status. - Sitemap registered: Ensure your sitemap is submitted and verified directly inside your Google Search Console account, not only within Search Atlas. - Correct project selected: Confirm you are activating Instant Indexing on the intended project under Left sidebar → OTTO SEO → All Sites. ❓ Frequently Asked Questions Does a plan upgrade take effect immediately? Yes. Upgrades are applied instantly. You can activate Instant Indexing as soon as your payment is confirmed — no waiting period. Will I lose my project data when I upgrade? No. All existing projects, configurations, connected integrations, and historical data are fully preserved when you change plans. Can I activate Instant Indexing for multiple projects? Yes. Once on a Pro or Agency plan, you can activate Instant Indexing across all projects in your account from Left sidebar → OTTO SEO → All Sites. What does is_transient: false mean in the API response? A is_transient: false flag means the error is permanent under the current account conditions — it will not resolve by retrying or waiting. The root cause must be addressed first, which in this case means upgrading to a Pro or Agency plan. If you need further assistance, open the chat widget in the bottom-right corner of the platform any type human teammate to be connected with a member of our team.

💡 How to Understand Seller Pricing Control in Search Atlas

This article addresses a common concern: the belief that Search Atlas has lowered your pricing or pressured you to reduce your rates. To be clear, Search Atlas does not set, adjust, or influence your seller pricing in any way. Your rates are always under your full control. This guide explains how pricing works and how to confirm your current rates are exactly what you set. 🔍 Common Causes of This Concern - Informational displays vs. requirements: Some areas of the platform may display data or reference values. These are informational only — they are never applied to your account automatically. - Misread rate fields: A value in a pricing field can look like a change, but it only takes effect if you explicitly save it. - External platform policies: If you operate across multiple platforms or channels, pricing policies outside of Search Atlas are separate and are not controlled here. 🛠️ Step-by-Step: Verify and Correct Your Pricing 1. Log in to your Search Atlas account and click the apps-grid icon in the header, then go to More Features → Help → Pricing to open the Pricing page. 2. Review each rate value displayed and compare it against your own records of what you intended to charge. 3. If any value differs from what you set, update the field manually by typing in your correct rate. 4. Review any other visible pricing fields on the same screen to make sure all values reflect your intentions. 5. Save your changes using the save or confirm button on that settings page. ✅ How to Confirm It Worked - After saving, refresh the page and reopen your pricing settings. Verify that every rate field displays the exact value you entered. - If your service is visible to clients, open the client-facing view or preview and confirm the displayed price matches your saved rate. - Check any active quotes, proposals, or reports that reference your pricing to ensure they reflect your updated figures. - If a rate still appears incorrect after saving and refreshing, note the exact field name and the incorrect value shown — you will need this information when contacting support. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚙️ How to Manage Your Own Pricing in Search Atlas

This article is for sellers or agency users who are concerned that their pricing has been changed without their knowledge. To be clear: Search Atlas does not adjust, override, or recommend changes to your rates. All pricing is set and controlled entirely by you. This guide explains where that control lives and how to confirm your current rates are exactly as you set them. 🔍 Common Causes of Pricing Confusion - A team member updated the rate — if multiple users have access to your account, another user may have edited the pricing settings. - A default or placeholder value was applied — some fields may display a default figure until you explicitly save your preferred rate. - Platform communications were misread as directives — suggestions or benchmarks shown in reporting screens are informational only and do not alter your actual pricing. 🛠️ Step-by-Step 1. Log in to your Search Atlas account and navigate to the top-right avatar → Billing → Services — this is where service pricing is configured. 2. Locate the pricing or rate field for the relevant service. Review the current value displayed. 3. If the value does not match what you intended, type your correct rate directly into the field. 4. Save your changes using the save or confirm button on that screen. 5. If you manage a white-label setup, also review any pricing-related fields within your white-label or agency configuration area to ensure your rates are reflected there as well. ✅ How to Confirm It Worked - After saving, refresh the page and reopen the pricing field — confirm the value shown matches exactly what you entered. - If your pricing appears in any client-facing reports or proposals generated through the platform, open one of those outputs and verify the rate displayed is correct. - Check your activity or change log (if available in your account settings) to see whether any recent edits were made and by which user. - If the value reverts or still looks incorrect after saving, take a screenshot of the field showing the incorrect value, note the service or section where it appears, and contact support so a team member can investigate directly. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔗 Wix Integration Limits and OTTO SEO Credits Explained

🌐 How Search Atlas Connects with Wix Search Atlas integrates with Wix through OTTO SEO, our AI-powered optimization engine. However, Wix is a closed website platform, which means it places strict limits on what third-party tools can automatically change on your site. These platform-level restrictions are set by Wix — not Search Atlas — and they affect how OTTO SEO suggestions are delivered and applied. ⚠️ Why Suggestions Don't Auto-Install on Wix Unlike open platforms such as WordPress, Wix does not allow external tools to automatically write changes directly to your site's pages, metadata, or content. As a result, OTTO SEO operates in manual implementation mode for Wix sites. This means: - OTTO SEO suggestions are generated and displayed inside your Search Atlas dashboard. - You must log in to your Wix editor and apply each recommendation yourself. - OTTO cannot push changes, inject code, or modify your site's structure automatically. This is a known limitation of the Wix platform and applies to all third-party SEO tools that integrate with it. 🔑 Wix API Key Requirements For the integration to function correctly — including blog-related recommendations — your Wix API key must have the correct permissions enabled. A common issue that prevents OTTO from retrieving data is a missing or misconfigured permission. Make sure your Wix API key has the 'Manage Blog' permission enabled. If this permission is absent or the key has expired, category and content data will not load, and some recommendations may not generate as expected. To check or update your API key permissions: 1. Log in to your Wix account and go to Settings → Advanced → API Keys. 2. Locate the key connected to Search Atlas. 3. Confirm that Manage Blog is toggled on. 4. If the key is expired, generate a new one and update it inside your Search Atlas dashboard under your Wix integration settings. 💡 How OTTO SEO Credits Are Used OTTO SEO credits are consumed at the point when suggestions are generated — not when they are applied to your site. This is important to understand for Wix users because the credit usage happens during the analysis and recommendation creation process, regardless of whether your platform supports automatic implementation. Here is how the credit process works: - Credit deducted: When OTTO analyzes your page and produces an OTTO SEO suggestion. - No additional credit: Viewing, copying, or manually applying a suggestion does not use extra credits. - Credit not refunded: If a suggestion was successfully generated and delivered to your dashboard, the credit has been used — even if you expected automatic installation. 🔄 Can I Get Credits Refunded? Credits are consumed during the generation process and are generally non-refundable once a suggestion has been successfully produced. However, if you believe credits were deducted due to a technical error — for example, if OTTO failed to generate any recommendations despite the process appearing to complete — this may qualify for review. Situations that do not qualify for a credit refund include: - Suggestions were generated but you did not apply them manually. - You expected automatic installation but the Wix platform limitation prevented it. - You changed your mind about optimizing a particular page. Situations that may qualify for review include: - OTTO showed an error during generation and no suggestion was delivered. - A confirmed platform or system error caused the process to fail on our end. ✅ Best Practices for Wix Users To get the most value from your OTTO SEO credits on a Wix site, follow these recommendations: - Before generating suggestions, ensure your Wix API key is valid and has all required permissions. - Review your existing suggestions in the dashboard before generating new ones to avoid duplicate credit usage. - Use the Search Atlas dashboard as your central reference and manually implement each recommendation in your Wix editor. - Prioritize high-impact pages — such as your homepage and top-traffic landing pages — when applying manual changes. 🛠️ Troubleshooting Common Wix Issues - Recommendations not generating: Check that your Wix API key is active and has 'Manage Blog' permission. Re-connect the integration if needed. - Blog categories not loading: This is usually caused by an expired or incorrect API key. Update the key and reconnect. - OTTO pixel not tracking: Wix requires manual pixel installation. Follow the in-platform instructions to add the OTTO pixel code to your Wix site header. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🏷️ How to Understand and Control Your Pricing in Search Atlas

This article addresses a common concern: the belief that Search Atlas has lowered or altered your service pricing. Search Atlas does not set, adjust, or recommend changes to the rates you charge your clients. All pricing decisions remain entirely yours. If you have seen a price change, this guide will help you identify where that change originated and how to ensure your rates are set exactly as you intend. 🔍 Common Causes of Unexpected Pricing Changes - Manual edits made inside a project or proposal: A team member with account access may have updated a rate directly inside a project, report, or client-facing document. - Template or default values: If you use pricing templates or default rate fields, these may have been updated and applied to new or existing projects automatically. - Whitelabel or reseller settings: If you operate under an agency or whitelabel setup, pricing fields within client-facing materials may reflect settings configured in your agency profile rather than a per-project override. - Third-party integrations: If Search Atlas is connected to an external billing or CRM tool, price changes in that system can appear to originate inside Search Atlas. 🛠️ Step-by-Step 1. Identify the specific price in question. Note the exact figure you see and where it appears — for example, inside a report, a proposal, a GBP project, or a client dashboard. 2. Check your project or report settings. Open the relevant project and review any rate or pricing fields that appear. Confirm whether the value shown matches what you originally entered. 3. Review your whitelabel or agency settings. If you use agency features, navigate to More Features → Agency Hub and review the White Label Setup and Settings sections. Confirm that no default pricing values are being pulled into client-facing outputs from this area. 4. Audit recent account activity. If other team members have access to your account, ask them whether any edits were made to pricing fields. Search Atlas does not log a price reduction on your behalf — any change will have originated from a user action. 5. Correct the pricing field directly. Once you locate the field containing the incorrect value, update it to your intended rate and save your changes. ✅ How to Confirm It Worked After updating your pricing, verify the fix by doing the following: reopen the project, report, or client-facing view where the incorrect price appeared and confirm the new value is now displayed. If the pricing appears inside a generated report or exported document, regenerate or re-export that output to ensure it reflects your updated rate. If the value reverts after saving, this may indicate a connected template or external integration is overwriting your entry — note where the reversion occurs so you can describe it precisely when contacting support. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🧩 Understanding OTTO Page-Level Schema Credit Usage

📌 Overview When you run OTTO on your site, certain tasks — including page-level schema — consume AI credits from your plan balance. A common source of confusion is the Review button: clicking it deducts credits even if no schema is ultimately deployed. This article explains exactly how credits are consumed, what triggers a deduction, and how to avoid unexpected credit loss. 🔍 How Page-Level Schema Credits Work Page-level schema is one of OTTO's most credit-intensive task types. Here is what you need to know: - Each click of the Review button costs 5 AI credits, regardless of whether you accept, reject, or take no further action on the generated schema. - Credits are consumed at the moment OTTO generates the schema suggestion — the AI model runs during the review step, not after you approve. - If OTTO surfaces dozens of pages with schema opportunities and you click Review on each one, the credits add up quickly. For example, 200 Review clicks = 1,000 credits consumed. - This means a 1,000-credit balance can be exhausted after approximately 200 page-level schema reviews — which matches the experience customers most commonly report. 📂 Where to Monitor Your Credit Usage You can track how your credits are being spent directly inside the platform: 1. Go to Left sidebar → OTTO SEO → All Sites and open your project card. 2. Navigate to Left sidebar → OTTO SEO → Tasks to see a breakdown of active and completed OTTO tasks, including schema-related actions. 3. Check your remaining credit balance in your account settings or billing dashboard — look for the AI credits counter at the top of the platform. Reviewing this breakdown regularly helps you identify which task types are consuming the most credits before your balance runs low. ⚙️ Why Credits Deduct on Review, Not on Approval The credit deduction happens when OTTO generates the schema recommendation — this is the computationally intensive step powered by AI. Clicking Review triggers that generation. Because the AI work is done at that point, the credit cost applies whether you: - Approve and deploy the schema - Dismiss or reject the suggestion - Navigate away without taking action Think of it like a consultation fee: you are charged when the expert produces the recommendation, not when you decide to act on it. 💡 Tips to Use Credits More Efficiently - Prioritise high-value pages first. Before clicking Review on every page, go to Left sidebar → OTTO SEO → Site Audit → Page Explorer and filter by traffic, impressions, or priority score. Focus your schema reviews on the pages most likely to benefit. - Batch your reviews intentionally. Avoid clicking Review across hundreds of pages in a single session unless you have sufficient credits to cover the volume. - Review your task queue before approving large schema runs. Visit Left sidebar → OTTO SEO → Tasks to see how many schema tasks are queued or pending and estimate the credit cost before proceeding. - Check your credit balance before starting a large session. Running out of credits mid-session may leave tasks incomplete. ❓ Frequently Asked Questions - Will I get credits back if I reject a schema suggestion? No. Credits are consumed when the AI generates the recommendation, not based on your decision afterward. - Why did 100–200 clicks use my entire 1,000-credit balance? Page-level schema costs 5 credits per Review click. 200 clicks × 5 credits = 1,000 credits. This is expected behaviour. - Can I see a log of exactly where each credit was spent? Navigate to Left sidebar → OTTO SEO → Tasks for a record of completed OTTO actions, which can help you correlate activity with credit consumption. - Are there task types that cost fewer credits? Yes — different OTTO task types carry different credit costs. Page-level schema is among the higher-cost tasks due to the complexity of the AI generation involved. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔄 Managing OTTO Quota and Migrating Your Pixel to a New URL

📋 Overview OTTO uses a quota system to track how many active websites (projects) you can manage under your plan. If you've deleted an OTTO project and pixel and noticed your quota still shows as "used," or you're planning to set up OTTO on a different URL, this article explains what's happening and how to avoid any duplicate charges. ⚙️ How OTTO Quota Works Each OTTO subscription includes a set number of project slots. A slot is occupied when you create an OTTO project and install its pixel on a website. Your quota reflects how many of these slots are currently in use. - One project = one quota slot. Every active OTTO URL consumes one slot. - Quota is tied to your subscription, not to a specific URL. Freeing a slot makes it available for a new website. - Your plan limit stays the same whether you add, remove, or move projects. ❓ Why Quota Still Shows as Used After Deleting a Project This is the most common question we receive. If you deleted an OTTO pixel and project but your dashboard still shows the slot as used, one of the following is usually the cause: 1. The change hasn't synced yet. Quota counts can take a short time to update. Refreshing the page or logging out and back in often resolves it. 2. The project was archived, not deleted. Archived projects can still hold a slot. Make sure the project was fully removed. 3. The pixel was removed from the site, but the project still exists in your OTTO dashboard. Deleting the pixel from your website does not automatically delete the OTTO project. 🗑️ How to Fully Free a Quota Slot 1. Open your OTTO dashboard. 2. Locate the project for the URL you no longer need. 3. Select the project's settings or options menu. 4. Choose Delete Project (not Deep Freeze). 5. Confirm the deletion when prompted. 6. Refresh your dashboard and check that your quota count has decreased. Once the project is fully deleted, the slot returns to your available quota and can be reused for another URL at no extra cost. 💳 Will I Be Double-Charged for a New URL? No. As long as you stay within your plan's quota, creating a new OTTO project on a different URL does not create a second charge. You are billed for your subscription and the number of slots it includes — not for each individual URL you set up over time. Here's what that means in practice: - Deleting a project and creating a new one on a different URL simply reuses an existing slot. - You are only charged more if you intentionally add slots or upgrade your plan to manage more websites than your current quota allows. - Switching a single OTTO project from one domain to another keeps you on the same plan with no additional billing. 🚚 Recommended Steps to Migrate OTTO to a New URL Follow this order to move OTTO from an old website to a new one cleanly and without affecting your quota or billing: 1. Remove the pixel from the old site. Delete the OTTO script from your old website's code or disconnect it from your CMS integration. 2. Delete the old project in OTTO. This frees the quota slot (see the steps above). 3. Confirm your quota is available. Your dashboard should now show one more open slot. 4. Create a new OTTO project for the new URL. 5. Install the new pixel on the new website and verify it is active. 💡 Things to Keep in Mind - Project data does not transfer. Deleting a project removes its historical OTTO data. If you want to keep records, export or note any important information before deleting. - Verify the pixel after migration. Confirm the new pixel is firing correctly so OTTO can begin optimizing the new site. - Check your plan limit first if you want to run both the old and new URLs at the same time — that would require two slots. 🙋 Frequently Asked Questions I deleted my project but quota didn't change. What now? Wait a few minutes and refresh your dashboard. If the slot is still showing as used after that, confirm the project was deleted rather than deep frozen. If it still hasn't updated, contact support with your account details and the URL involved. Can I reuse a freed slot immediately? Yes. Once a slot is free, you can create a new project on any URL right away with no waiting period and no extra charge. Does removing only the pixel free up my quota? No. Removing the pixel from your website does not delete the OTTO project. You must delete the project itself to release the quota slot. 🤝 Need More Help? If your quota does not update after fully deleting a project, or you have a billing question about your OTTO plan, reach out to our support team via messenger chat and type "Human Teammate". Please include your account email, the URL you removed, and the new URL you want to set up so we can assist you quickly.

💳 Why You're Asked to Pay for an Extra OTTO Site (OTTO Slot Limits Explained)

Search Atlas plans include a set number of OTTO AI project slots. After reading this, you'll know how many slots your plan includes, why you may hit a limit when connecting Google Search Console or creating a new OTTO project, and how to add more slots through a billing top-up. 🧠 Projects vs. OTTO Project Slots An OTTO project slot is a project that has OTTO AI actively enabled. It is different from a regular project. - You can create unlimited projects in Search Atlas. - Only a limited number of those projects can have OTTO AI active at the same time. - Your OTTO quota is a concurrent limit, not a monthly reset. Example: if your plan includes 5 OTTO slots, only 5 projects at a time can have OTTO enabled. To enable OTTO on a sixth project, free a slot or buy a top-up. 📊 OTTO Slot Allocations by Plan Each Search Atlas plan includes a default number of OTTO project slots: - Growth plan: 2 OTTO project slots. Once both are in use, you can't create another OTTO project or connect Google Search Console to a new one until you free a slot or buy a top-up. - Higher tiers / custom plans: allocation varies — confirm with billing or your account contract. - Promotional accounts: may include additional OTTO slots beyond the standard default (see the Promos section below). If the OTTO slot count shown in your account does not match your plan's allocation, see the troubleshooting section below. 🔍 How to See Which Projects Are Using OTTO To check how many OTTO slots you're using: 1. Open Search Atlas. 2. In the left sidebar, select OTTO SEO. 3. Go to All Sites → OTTO SEO Automation. This page lists every project that currently has OTTO AI active. Each project listed counts toward your OTTO quota. 🛠️ Error: "Failed to connect otto_v2 to project. No service ID was returned" If you see the error Failed to connect otto_v2 to project. No service ID was returned, or you can't link Google Search Console to a project or create a new OTTO project, you've reached your plan's OTTO slot limit. This is expected behavior, not a bug. On the Growth plan, for example, both OTTO slots are already in use, so new OTTO projects and new Google Search Console connections are blocked. When you reach the limit, the Create OTTO Project button is disabled and new Google Search Console connections fail. To fix it, choose one option: - Free a slot: disable OTTO on a project you no longer need to automate — this frees the slot instantly. - Add slots: purchase a top-up in the billing section (see the next section). After a slot opens up, you'll be able to connect Google Search Console and create the OTTO project without the error. If the Create OTTO Project action fails even when you have an available slot, refresh the page and retry — this may be a temporary backend issue. 💳 Why You May See a Charge, and How to Add Slots You may be charged for an additional OTTO site if: - You tried to enable OTTO on more projects than your plan includes. - An extra OTTO slot was added to avoid blocking your workflow. - Your plan includes fewer OTTO slots than expected. Additional OTTO slots are billed per slot, based on your total OTTO quota rather than individual project activity. To intentionally add more OTTO project slots: 1. Open the billing section of your account. 2. Purchase an OTTO slot top-up. The new slots become available immediately, so you can enable OTTO on more projects and connect more Google Search Console accounts. If your OTTO quota doesn't reflect your paid add-ons after 24 hours, this may indicate a sync delay. Contact the support team if quotas remain unsynced. ⚠️ Troubleshooting: OTTO Quota Doesn't Match Your Plan Occasionally an account shows fewer OTTO slots than the plan entitles. For example, a Growth plan account may display only 1 OTTO slot when the plan supports 2. If this happens: 1. Verify your plan's standard OTTO allocation (see the plan list above). 2. Confirm the number of OTTO-enabled projects under OTTO SEO → All Sites (SEO Automation). 3. Refresh your browser or app, then recheck the slot count. 4. Allow up to 24 hours for billing changes to sync, especially after a plan change or add-on purchase. Recent system updates may affect quota provisioning. 5. If there's still a mismatch, escalate to the billing team. Billing can correct the assigned quota on the backend, typically within 24 hours and often sooner. After billing confirms the fix, refresh your account and verify the corrected OTTO slot count. Note: the billing team resolves quota correction errors of this type without requiring additional payment when the entitlement is part of your plan. 🎟️ Promos and Special Offers Some accounts include promotional OTTO limits (for example, event, summit, or cohort promos). Because promos vary, confirm your promotional allocation with the billing team or your account contract if your slot count looks higher or lower than the standard plan default. Promotional OTTO slots are added to your account automatically — check your active plan in the billing section to see your total OTTO slot allocation. 🎯 You now know that OTTO slots are a concurrent, plan-based limit: the Growth plan includes 2, the "No service ID was returned" error means you've hit that limit, and you can add more slots anytime with a billing top-up. If your slot count looks wrong for your plan, escalate to billing for a backend correction.

🛠️ Offboarding a Client with OTTO Deep Freeze

🔍 Overview When a client cancels their SEO services, you usually want two things: to free up a project slot in your Search Atlas plan, and to make sure the client doesn't lose the optimizations you've already built. OTTO Deep Freeze is designed for this situation. This article explains how to plan an offboarding, what to check first, and what to expect afterward. ❄️ What Deep Freeze Does Deep Freeze preserves the OTTO optimizations already deployed on a client's website, so the work stays in place after the project is no longer actively managed. Think of it as taking a snapshot of the current state and keeping it live. - Preserved: the optimizations already deployed to the site. - Not active: new OTTO recommendations, ongoing updates and fresh optimizations for that site. - Quota-based: frozen sites count against a separate Deep Freeze quota, not your regular active project limit. That's why freezing a site can free up a regular project slot. Your Deep Freeze quota depends on your plan. If you're unsure how many frozen sites your plan includes, check your plan details or ask our team in chat (see the last section). ✅ Before You Offboard A little preparation prevents most problems. Go through this checklist first: - Confirm the cancellation. Make sure the client has agreed to end the engagement and understands that active optimization will stop. - Check your Deep Freeze quota. Make sure you have at least one open Deep Freeze spot on your plan. - Finish pending work. Deploy or approve any OTTO recommendations you want to keep. Anything not deployed before the freeze is generally not included. - Export your reports. Download rankings, audit and performance reports for your records or to hand over to the client. - Tell the client what to expect. Let them know the existing work will stay in place but will no longer be updated. 🚀 How to Offboard a Client Step by Step 1. Open your Search Atlas dashboard and select the client's project or site. 2. Go to the OTTO section for that site and review the deployed optimizations to confirm everything you want to keep is live. 3. Find the Deep Freeze option for the site. It is usually in the OTTO settings or project management options for that site. 4. Choose to freeze the site and confirm. The site will use one spot from your Deep Freeze quota. 5. Check that the site now shows a frozen status and that your active project count has gone down. 6. Add a new client or project in the freed-up slot whenever you're ready. Important: freeze the site before you remove or delete the project. Removing a project without freezing it first may mean the optimizations are no longer served on the client's website. 🔄 What Happens After the Freeze - The existing optimizations should continue to appear on the client's site. - OTTO will not create or deploy new optimizations for that site while it is frozen. - Changes the client makes to their own website, such as a redesign, a migration or a change of platform, may affect how the preserved optimizations work. - If the client returns, you can ask about reactivating the site so OTTO can resume active optimization. This uses one of your regular project slots again. 💡 Tips for a Smooth Handover - Send the client a short summary of the work completed, such as pages optimized, issues fixed and results achieved. - Let them know the optimizations are managed through your Search Atlas account, and that moving the site elsewhere may require a separate plan. - If the client plans to redesign or migrate their website soon, tell them in advance so the preserved work isn't unexpectedly lost. - Keep a note of which clients are frozen so you can track your Deep Freeze quota usage. ❓ Common Questions Will the client lose their optimizations if I freeze the site? No. The purpose of Deep Freeze is to keep the deployed work in place. Will freezing a site free up a slot in my plan? Yes. A frozen site uses a Deep Freeze spot instead of an active project slot, so you can use the freed slot for another client. What if I've used all my Deep Freeze spots? You will need to free up a spot or look at your plan options before freezing another site. Our team can walk you through the options. Can I undo a freeze later? In most cases a frozen site can be reactivated, provided you have an open project slot on your plan. 💬 Need Help? If you can't find the Deep Freeze option, you're unsure about your quota, or you want a second opinion before offboarding a client, we're happy to help. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

💡 Fixing Counteroffers Rejected by Pricing Caps

🔍 Overview If you are a publisher and the platform rejects a price change, you may have hit the maximum price allowed for that site. The same rejection also applies when you respond to a platform price offer. This article explains what that limit is, why the change is rejected, and what you can do about it. 📌 What Is a Pricing Cap? The pricing cap is the highest price the platform allows for a specific site. It is calculated as 2.5 times that site's Domain Authority, using Moz Domain Authority when available and SEMrush authority otherwise. It is not shown next to the price field. If you enter a higher price, the platform rejects it immediately with the message "The price you set for publication {id} is too high for this site. Please lower it and try again." This is not an error on your account. The platform is working as designed. The cap applies whenever you try to raise a site's price, whether you edit the listing or respond to an offer. A raise can also be blocked by a 30-day price lock, an open payout, or articles still assigned to the site. ❓ Why Was My Counteroffer Rejected? The most common reasons are: - The price is above the cap. Any requested price higher than 2.5 times the site's Domain Authority is rejected automatically. The rejection tells you the price is too high, but it does not tell you the maximum. - The cap does not match your expectations. The limit may be lower than what you charge elsewhere, so a rate that is normal for you can still fall outside the allowed range. - Your site details being out of date does not cause this rejection. The cap uses the site's Domain Authority, which the platform measures. Updating your description, categories, or other listing details does not change the maximum price. - The amount must be a number greater than zero. Symbols and text are not accepted by the price field. Using the wrong currency or another field does not produce the pricing-cap rejection. 🛠️ How to Submit a Counteroffer That Is Accepted 1. Sign in to the publisher portal. To change an existing site's price, open the site and use its Counter Offer field. To answer a price offer from the platform, open the Counter Offer section, where the offer shows a Request price and an Offered Price. 2. For an existing site, enter the new amount in the Counter Offer field and save. For a platform offer, choose Decline, which opens a window titled "Make offer," or use Bulk Counter Offer when several offers are selected. 3. The price field does not show a maximum or a price range. Keep the amount at or below 2.5 times the site's Domain Authority. If you do not know that number, submit a price and use the rejection message to tell you it is too high. 4. Enter your price using numbers only, with no symbols or text. 5. Check the amount, then save the listing or click "Make offer" for a single offer, or "Submit Offers" for a bulk counteroffer. 6. If the rejection appears again, the amount is still above the cap. Lower it before trying again. Do not keep submitting small reductions: once a lower increase is accepted, the price is locked for 30 days and cannot be raised again until the lock ends. 💡 What to Do If You Want a Higher Price Because the cap is set by the platform, you cannot raise it from the counteroffer form. Here are some steps you can take: - Choose an amount at or below the cap. Any accepted increase locks that price for 30 days, so you cannot raise it again during that period. You can still lower it at any time. - Updating your description, categories, or metrics does not raise the pricing cap. The cap is based only on Domain Authority measured by the platform. If the authority figure looks wrong, contact support and ask them to review it. - This price change only sets what you are paid for a placement on your site. It does not include a content type, link placement, or other offer terms to review. If you are responding to a platform offer, compare your amount with the Request price and Offered Price shown on the offer. - You cannot raise the cap yourself. If you believe the Domain Authority used for your site is wrong, contact support and ask them to review the metric. They can explain how the limit was calculated. Support cannot raise the cap for an individual site from the counteroffer form, and premium pricing above the cap is limited to marquee sites negotiated by the platform. 📝 What to Include When You Ask for a Review Sharing these details helps our team respond faster: - The URL of your site - The price you tried to enter - The exact wording of the rejection message - The price you would like to charge - Why you feel this rate is justified, such as traffic, niche, or audience ⚠️ Good to Know - A rejected counteroffer is not sent to the advertiser, so no negotiation has started yet. - Your original offer stays available until it expires, so you can still accept it or submit a new counteroffer within the allowed range. - Pricing limits are designed to apply to all publishers, so a review does not guarantee that a limit will change. 🙋 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🧾 View Purchase History and Manage SEO Services

📋 Overview This article explains how to review your purchase history and service spend within Search Atlas, check your OTTO SEO implementer activity, and manage site audit recrawls. Whether you need to confirm what was purchased in a specific month or review how credits have been used, this guide walks you through each step. 💳 How to View Your Purchase History To review the services you have purchased and the amounts spent in a given month, follow these steps: 1. Log in to your Search Atlas account. 2. Click on your Avatar Menu (👤) or account name in the top-right corner of the platform. 3. Select Billing or Subscription from the dropdown menu. 4. Navigate to the Purchase History or Invoices section. 5. Use the date filter to select the month you want to review (for example, September). 6. You will see a list of all services purchased, including the date, service name, and amount charged. Each line item in your purchase history corresponds to a specific service or credit package. If you purchased additional OTTO activations, site audit credits, or other add-ons, these will appear as individual entries. 🤖 Understanding OTTO SEO Implementer Activity OTTO SEO is Search Atlas's AI-powered SEO automation tool. It implements on-page and technical SEO recommendations directly on your connected sites. To review your OTTO SEO activity: 1. In the left sidebar, click OTTO SEO. 2. You will see a list of all sites that have OTTO activated. 3. Click on a specific site to view the tasks OTTO has implemented, including the date each action was taken. 4. The implementer log shows which recommendations were applied, such as meta tag updates, schema additions, or internal linking changes. If you want to check how many OTTO activations you have used versus how many remain in your plan, this information is available on the same Billing page under your subscription details. 🔄 How to Trigger a Site Audit Recrawl A site audit recrawl allows Search Atlas to re-scan your website and update its technical health data with the latest findings. This is useful after you have made changes to your site and want to verify that issues have been resolved. To run a site audit recrawl: 1. In the left sidebar, click Site Metrics. 2. Select the site you want to recrawl from the list. 3. Go to the Overview tab for that site. 4. Look for the Recrawl or Run Audit button, typically located near the top of the page. 5. Click the button to start the recrawl. The time to complete depends on the size of your site. 6. Once the crawl is finished, your site audit data will refresh automatically. Note: Recrawls may consume crawl credits depending on your plan. Check your credit balance before initiating a large crawl. 📊 Tracking Spend on Specific Services If you need a breakdown of how much was spent on a particular service type in a given month, keep the following in mind: - OTTO activations are charged per site activated. Each new site you connect and activate OTTO on counts as one activation. - Site audit credits are consumed each time a crawl is run. Larger sites use more credits. - Additional purchases such as content generation, backlink credits, or plan upgrades will also appear in your billing history with clear labels. All charges are listed with timestamps, so filtering by month gives you a complete picture of your spend for that period. 💡 Tips for Managing Your Account Spend - Review your billing page at the start of each month to stay on top of usage. - Deactivate OTTO on sites you are no longer actively optimising to avoid unnecessary charges. - Schedule recrawls strategically — run them after completing a batch of site changes rather than frequently throughout the month. - Check your plan limits regularly to avoid unexpected overage charges. 🆘 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

💳 Fix a Stuck Plan Change and OTTO Setup

💳 Fix a stuck plan change If the Change Plan page shows messages such as “please wait” or “payment processed” before you select a plan, this is a checkout issue—not a completed plan change. Don’t repeat the plan-selection steps or submit another payment while the page is stuck. 1. Take a screenshot of the full error page, including any messages and the browser address bar. Don’t include payment card details. 2. Refresh the page once. If the same message returns, stop and avoid retrying the checkout. 3. Open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team. Explain that the checkout showed “please wait” or “payment processed” before you selected a plan, and attach the screenshot. Our team can review the billing state and help you continue safely. A screenshot is useful evidence; you don’t need to send it again or provide more details unless the team asks. 🛍️ Check OTTO’s Shopify pixel If OTTO says the pixel is not installed after you added the script to your Shopify theme, confirm the script is in the correct theme and that your changes were saved and published. Then check the storefront in a fresh browser tab. Theme changes may take a short time to appear. 1. In Search Atlas, open OTTO SEO from the left sidebar, or go to /seo-automation-v3. 2. Confirm the site shown in OTTO matches the Shopify storefront where you added the script. 3. In Shopify, verify that the script is in the theme’s head section, then save and publish the theme if needed. 4. Reload the storefront and check OTTO again. If it still reports that the pixel is not installed, contact the team through the platform chat and share the site URL and a screenshot of the OTTO status. Do not share store passwords or secret keys. 👁️ Invite a single-site viewer To give someone view-only access to one site, open the site’s access or user invitation settings in Search Atlas, invite the person using their account email, and select the view-only role and only the site they should access. Review the selected site and permissions before sending the invitation. If you don’t see these options, use the platform chat for help locating the correct settings. 📎 What to do if guidance repeats If you already followed the suggested steps or attached a screenshot, say what you tried and what the page shows now. You don’t need to repeat completed steps. For a billing error or a repeated response that doesn’t address the issue, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

⚡ Managing OTTO Credits and Client Installation Validation

Overview When working with clients, it is important to understand exactly when OTTO credits are used and what happens if a client never installs the OTTO code. This article explains what our support team has confirmed about credit consumption timing and the recommended workflow to protect your credits before committing them to a new project. When Are OTTO Credits Consumed? Based on confirmed support guidance, OTTO credits are deducted when a new OTTO project is created, not when OTTO is activated or deployed on the site. This means: - Creating a project for a client uses one credit right away. - If the client never installs the OTTO code, the credit is still consumed. - Simply leaving a project inactive does not protect or return your credit. Understanding this timing is critical before you create any new project on behalf of a client. Recovering Credits If you need to recover an OTTO credit, options may be available depending on your situation — such as removing the website from the project or deleting the project entirely. The availability, timing, and conditions of credit recovery (including any waiting periods or data loss implications) can vary. To understand exactly what recovery options apply to your account and project, please contact our support team directly for guidance before taking any action. Recommended Workflow: Validate Installation Before Creating a Project To avoid losing credits when a client is undecided or has not yet installed the OTTO code, follow this workflow before creating the project in Search Atlas: 1. Share the OTTO installation instructions with your client first. Send them the installation documentation and ask them to add the OTTO script to their website before you proceed. 2. Ask the client to confirm installation in writing. Get a clear confirmation via email, message, or your preferred communication channel before taking any action in the platform. 3. Only create the OTTO project once installation is confirmed. This ensures that when you use a credit, the client is ready to proceed and the project will be actively used. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔒 Otto Deployments After Plan Cancellation Explained

🤔 What Happens to Otto's Changes If You Cancel? When your Search Atlas plan expires or is cancelled, Otto's deployed SEO changes do not automatically revert. 24 hours after your account becomes unsubscribed, all of your OTTO projects are automatically put into Deep Freeze (autopilot off, read-only). The projects are not deleted and stay engaged, so the OTTO pixel keeps serving the fixes that were already deployed. Deployed changes stop being served only if the pixel is removed, the project is disengaged, or the project is deleted. ❄️ What Is Deepfreeze? Deepfreeze is an Otto feature designed to retain your current SEO deployments on your website after your plan ends. When activated, it preserves your deployed changes so they remain in place regardless of your subscription status. Think of it as locking in Otto's changes so they no longer depend on an active Search Atlas plan to stay on your site. ✅ Before Activating Deepfreeze Make sure Deepfreeze is enabled while your plan is still active. Once your subscription ends, you will lose access to Otto settings, including Deepfreeze. If you are unsure whether Deepfreeze is available on your account or how to enable it for your specific setup, reach out to our team for guidance before cancelling. ⚠️ Important Considerations - Activate Deepfreeze before cancelling. You must enable it while your plan is still active. You will lose access to Otto settings — including Deepfreeze — once your subscription ends. - Only currently deployed changes are affected. Any Otto suggestions that have not yet been deployed will not be retained after cancellation. - Future updates require an active plan. Deepfreeze preserves your existing deployments, but making new Otto changes or updates will require reactivating a subscription. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🧊 OTTO Deployments & Deep Freeze After Cancellation

🔍 Overview When you use OTTO to deploy on-page SEO changes, one of the most common questions is: will those changes disappear if I cancel my subscription? The short answer is no — your deployed changes are not automatically reverted. This article explains what happens to your OTTO deployments after cancellation and how the Deep Freeze feature plays a role in protecting your site. ⚙️ What OTTO Does When It Deploys Changes OTTO (found in the left sidebar under OTTO SEO → All Sites (SEO Automation)) pushes optimisations directly to your website — things like title tags, meta descriptions, heading structures, schema markup, and more. Once OTTO deploys a change, it is live on your site just like any manual edit you would make yourself. - Changes are written directly to your website's content or code. - OTTO does not act as a proxy or intermediary layer sitting between your site and visitors. - Deployments are persistent by default — they do not rely on an active subscription to remain live. 🚫 What Happens If You Cancel Your Plan If you cancel your Search Atlas subscription, your OTTO-deployed changes remain on your website. There is no automatic rollback or reversion of the SEO improvements OTTO has made. Your site keeps all the optimisations that were successfully deployed before cancellation. However, there are important limitations to be aware of once your plan is cancelled: - No new deployments: OTTO will no longer push new changes or optimisations to your site. - No monitoring: OTTO will stop monitoring your site for new issues or opportunities. - Platform access is restricted: You will lose access to the OTTO dashboard and reporting features inside Search Atlas. - Deep Freeze mode activates: Your project enters a read-only "Deep Freeze" state (see below). 🧊 What Is Deep Freeze? Deep Freeze is a special project state that you can turn on (and Unfreeze) yourself from the OTTO project's menu, and it also activates when a Search Atlas account is cancelled or a plan lapses. It is designed to preserve the record of everything OTTO has done on your behalf, without allowing new actions to be taken. Here is what Deep Freeze means in practice: - Your deployment history is preserved: A record of all changes OTTO made is retained, so nothing is lost from a data perspective. - No new changes can be made: OTTO cannot deploy, edit, or roll back anything while a project is in Deep Freeze. - Your live site is unaffected: Changes already deployed remain live on your website — Deep Freeze does not touch your site. - Reactivation restores full access: If you resubscribe, your project exits Deep Freeze and you regain full OTTO functionality, including your history and previous configurations. ✅ Key Things to Remember 1. OTTO changes are not reverted when you cancel — they stay live on your site. 2. Deep Freeze is a data-preservation mode, not a rollback mechanism. 3. Your deployment history is safe and retrievable if you reactivate your plan. 4. To make new SEO deployments or access OTTO reporting, an active subscription is required. 🔄 How to Reactivate and Exit Deep Freeze If you want to resume using OTTO after a cancellation, simply reactivate your Search Atlas subscription. Once your plan is active again: - Your project automatically exits Deep Freeze. - All previous deployment history and project settings are restored. - OTTO can begin monitoring and deploying new optimisations immediately. To reactivate, log in to your Search Atlas account and navigate to your billing or plan settings. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team. Additional Notes When the main subscription is cancelled, 24 hours after the account becomes unsubscribed all of its OTTO projects are automatically put into Deep Freeze (autopilot off, read-only). Projects are not deleted and stay engaged, so the OTTO pixel keeps serving the fixes that were already deployed. Deployed changes stop being served only if the pixel is removed, the project is disengaged, or the project is deleted. Only currently deployed changes are retained; undeployed suggestions are not preserved.

🤖 OTTO AI Title Length and Billing After Cancellation

Overview This article covers two common questions from Search Atlas users: how to control the length of page titles and SEO titles generated by OTTO AI, and why you may receive billing notifications or see a charge after canceling your subscription. How to Generate Shorter Page Titles with OTTO AI OTTO AI generates page titles and SEO titles based on the instructions and context you provide. If the output is too long, you can guide OTTO to produce shorter results by adjusting your inputs before generating content. To shorten page title output in OTTO: 1. Navigate to the OTTO AI section of the platform and open the page or task where titles are being generated. 2. Before running or regenerating the title, include a specific character-limit instruction in your prompt. For example: "Keep the page title under 60 characters" or "Write an SEO title no longer than 55 characters." 3. Regenerate the title with the updated instruction in place. 4. Review the output. If it is still too long, tighten the instruction further — for example: "Maximum 50 characters, no exceptions." Best practices for concise OTTO titles: - Always specify a character limit in your prompt instructions. - Ask OTTO to prioritize the primary keyword at the beginning of the title to stay within limits naturally. - Avoid open-ended prompts — the more specific your instruction, the more predictable the output length. At this time, length control for OTTO-generated titles is managed through your prompt instructions. If you are unsure where to enter instructions for your specific workflow, see the final section of this article for how to connect with our team. Why You Received a Notification or Charge After Canceling Receiving a billing notification or seeing a charge after canceling your Search Atlas subscription is understandably confusing. Because billing behavior can vary depending on your specific account setup and timing, the best step is to connect with our team directly so we can review your account and clarify exactly what the notification or charge relates to. When reaching out, please have the following ready: - The date you canceled your subscription - The date of the charge or notification you received - The amount shown, if applicable - Any invoice or email reference numbers Having these details on hand will allow our team to look into your account quickly and provide a clear explanation. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 OTTO Subdirectory Scoping and Trial Cancellation Guide

🗺️ Can OTTO Be Scoped to a Subdirectory? OTTO SEO is designed to operate at the root domain level. This means when you connect a site to OTTO, it analyses and deploys optimisations across the entire domain — it cannot be restricted to a single subdirectory such as /pl/ on a multilingual site. If your site uses subdirectories to separate languages or regions (for example, example.com/pl/ for Polish content), OTTO will still process the full domain. There is currently no option to limit OTTO's scope to one specific path segment. 💡 Workarounds for Multilingual or Subdirectory Sites If you only want to optimise a specific language version of your site, consider the following approaches: - Review OTTO's suggestions selectively: After OTTO generates recommendations, you can choose to deploy only those changes that apply to your target subdirectory's pages. Not every suggestion needs to be approved. - Use a subdomain instead: If your site architecture is flexible, hosting your regional content on a subdomain (e.g., pl.example.com) allows you to create a separate OTTO project scoped exclusively to that subdomain. - Reach out before committing: If you are evaluating OTTO for a multilingual site, we recommend speaking with our team before your trial ends to find the best setup for your use case. ❌ How to Cancel Your OTTO Trial If OTTO does not meet your current needs, you can cancel your trial at any time before it converts to a paid subscription. Follow these steps: 1. Log in to your Search Atlas account. 2. In the left sidebar, click OTTO SEO → All Sites (SEO Automation) (URL: /seo-automation-v3). 3. Locate the trial subscription you want to cancel and open its settings or billing details. 4. Select the cancellation option and follow the on-screen prompts to confirm. 5. You should receive an on-screen confirmation message that your trial has been cancelled. Important: After cancelling, refresh the page to verify the cancellation is reflected in your account status. In rare cases, the cancellation may appear active before a page refresh completes the update. If the trial still shows as active after refreshing, this is a known display issue — contact our team immediately via the chat widget to confirm your account status. 💳 Will I Be Charged After Cancelling My Trial? No charges will occur if you cancel your trial before the trial period ends. Here is what you need to know: - Cancelling your trial stops any future billing for the OTTO subscription. - You will not be charged for the trial period itself — trial access is free. - If you have any active OTTO top-up add-ons, these should also be reviewed and cancelled separately, as add-ons are billed independently from the base subscription. - Once cancelled, your OTTO projects will move to an inactive or frozen state and will no longer consume credits. We recommend taking a screenshot of your cancellation confirmation screen for your own records. If you do not receive a confirmation on-screen or via email, treat this as a signal to verify with our support team before your trial period expires. ⚠️ Known Issues to Be Aware Of Our team has resolved several issues related to OTTO trial and subscription management. Here are things to watch for: - Cancellation confirmation not persisting: On rare occasions, the cancellation screen may show a success message, but the subscription appears active again after a page refresh. This has been addressed, but if you experience it, contact support right away. - OTTO weekly emails after cancellation: Some users previously continued receiving OTTO-related emails after cancelling. If this happens to you, it is safe to ignore those emails — your cancellation is still valid. Notify our team so we can remove you from those sends. - Trial start confirmation emails: If you did not receive a trial confirmation email when you signed up, this does not affect your trial status. Your account dashboard is the authoritative source for your subscription state. 🙋 Still Have Questions? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

❄️ Freezing OTTO Projects and Subscription Cancellation

🔍 Overview This article explains the relationship between freezing an OTTO SEO project and cancelling your Search Atlas subscription. Understanding this distinction helps you manage your projects and subscription with confidence. ❄️ What Does Freezing an OTTO Project Mean? Freezing a project is a project-level action that pauses OTTO's active SEO automation for a specific site. When a project is frozen: - OTTO stops making automated changes and recommendations for that site. - Your project data and settings are preserved. - The project remains visible in your dashboard in a frozen state. - You can unfreeze the project at any time while your subscription is active. To freeze a project, go to Left sidebar → OTTO SEO and use the Freeze sites option on the main OTTO SEO page. 💳 Does Freezing a Project Cancel My Subscription? No. Freezing a project does not cancel your subscription. These are two completely separate actions: - Freezing a project pauses automation for one specific site — your subscription remains active and you continue to be billed. - Cancelling your subscription ends your billing relationship with Search Atlas and affects all projects across your account. If you want to stop being charged, you must cancel your subscription directly through your account settings. Freezing a project alone will not achieve this. ⚙️ What Happens to Frozen Projects if I Cancel My Subscription? When your subscription is cancelled, all active OTTO projects are automatically moved into a deep-frozen state. Here is what that means for your data: - All OTTO project data is retained but becomes inaccessible while your account is inactive. - No further SEO automation runs on any of your sites. - You will not be able to access or edit frozen projects until you resubscribe. 🔄 What Happens When I Resubscribe? When you resubscribe to Search Atlas, your previously frozen projects are automatically unfrozen and restored to their prior state. You can then resume OTTO SEO automation without losing your previous configuration or data. ⚠️ A Note on Automated Freeze Emails Some customers have reported receiving freeze or cancellation warning emails while their subscription was still active. If you receive such an email and believe it was sent in error, please do not be alarmed — check your subscription status directly in your account settings to confirm whether your account is active. If your subscription is active but you received a freeze warning, this may be a notification error. 📋 Quick Reference: Freeze vs. Cancel - Freeze a project: Pauses automation for one site. Subscription stays active. Data is preserved. Reversible at any time. - Cancel subscription: Ends billing. All projects deep-freeze. Data retained but inaccessible until resubscription. - Resubscribe: All projects automatically unfreeze and restore to their previous state. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

❄️ Cancel Your OTTO Sites Top-Up: Deep Freeze vs. Remove

🧭 Overview If your current plan already includes enough OTTO sites for your needs, you can cancel an OTTO Sites top-up add-on to stop the additional monthly charge. Before you do, it's important to understand the difference between deep freeze and remove — choosing the wrong option could affect your live site. 📋 What's Included in Your Plan An OTTO Sites top-up adds extra site slots beyond your plan's base allowance. If your plan already covers the sites you need OTTO activated on, you do not need the top-up add-on and can cancel it. ❄️ Deep Freeze vs. 🗑️ Remove: Key Differences Before canceling the top-up, you must decide what to do with any OTTO projects currently assigned to the extra slots. You have two options: - Deep Freeze: Stops the project — automation is turned off, the project becomes read-only, and it stops running scans and using automation quota. Changes already deployed stay live on the site. The project's OTTO site slot is released automatically after a 14-day hold period. Note that deep freezing does not cancel the top-up add-on; billing continues on its normal cycle until the add-on is cancelled separately. - Remove: Permanently detaches OTTO from the project. All OTTO settings and automation history for that site are deleted and cannot be recovered. Use this option only if you are certain you will never reactivate OTTO on that domain. In most cases, deep freeze is the safer choice — it keeps your data intact while freeing up the slot. 🔢 Step 1 — Deep Freeze or Remove the Extra OTTO Project Deep freezing does not cancel the top-up — it only stops the project and releases the site slot after a 14-day hold. The top-up will keep billing on its normal cycle until it is cancelled separately. Follow these steps to free up the slot: 1. Navigate to OTTO SEO → All Sites (SEO Automation). 2. Locate the OTTO project assigned to the site you want to remove from the top-up slot — this should be a domain other than the one you intend to keep active. 3. Open that project's settings or actions menu. 4. Select Deep Freeze to pause the project and preserve all data, or select Remove to permanently delete OTTO from that site. 5. Confirm your selection when prompted. Once confirmed, the site slot is released and is no longer consuming your top-up allocation. 💳 Step 2 — Cancel the Top-Up Add-On After freeing up the slot, cancel the OTTO Sites top-up add-on from your dashboard: click your Avatar Menu (👤) → Billing → Services, then open the ⋮ menu on the top-up and select Cancel. If you need assistance completing the cancellation, please reach out to our support team via the chat icon in the bottom-right corner of the app.

How to Cancel OTTO Add-ons and Understand Pending Cancellation Status

📋 Understanding OTTO Add-ons Search Atlas offers several OTTO add-ons that extend your platform capabilities, including OTTO Pixels, OTTO Sites, and OTTO Quotas. Each add-on is a separate subscription that you can manage independently from your base Search Atlas plan. ❌ How to Cancel OTTO Add-ons To cancel an OTTO add-on subscription, follow these steps: 1. Log into your Search Atlas account. 2. Navigate to your Billing or Subscription settings from your Avatar Menu (👤). 3. Locate the OTTO add-on you wish to cancel (for example, OTTO Pixels, OTTO Sites, or OTTO Quotas). 4. Select the option to cancel that specific add-on and confirm when prompted. After you initiate cancellation, the add-on will enter Pending Cancellation status. This does not mean your cancellation failed — it is a normal part of the process. Your add-on will remain active during the pending period and will be fully removed at the end of your current billing cycle. If you are unable to locate the cancellation option for your specific add-on, or if you encounter any issues while canceling, our support team can process the cancellation on your behalf. Please reach out using the contact options at the bottom of this article. ⏳ What Does Pending Cancellation Mean? Pending Cancellation is an intermediate status that appears after you request a cancellation. It indicates that your cancellation request has been received and will take effect at the end of your current billing cycle. Your add-on will continue to function normally while in this status. If your add-on remains in Pending Cancellation longer than your billing cycle, or if you have questions about when your cancellation will take full effect, our support team can look into the status of your request directly. 🔄 Need Further Help? If you have questions about canceling an OTTO add-on, understanding your cancellation status, or anything related to your OTTO subscription, our support team is happy to help. If you cannot resolve the issue using the steps above, please contact us and we will assist you directly. Additional Notes How Many OTTO Add-ons Are You Paying For: navigate to billing page to see all active add-ons with costs; if you see charges you do not recognize, review your active add-ons immediately to identify any you no longer use.

🧊 Deep Freeze and OTTO Top-Ups: How to Stop the Charge

📋 Overview​ If you added an OTTO Sites top-up to cover an extra website, you may later realize you no longer need it. A common example: you bought a top-up to run OTTO on a second site, but you only actually need OTTO on a single domain that is already included in your Growth plan. In this case, cancel the top-up in Billing to stop the recurring charge. Deep freezing the extra project only stops its automation and does not stop the charge. This article explains what a top-up is, why deep freezing does not cancel it, and the exact steps to cancel the charge. 💡 What Is an OTTO Sites Top-Up?​ Your subscription plan includes a set number of OTTO-enabled sites. A top-up is an additional recurring charge (for example, $239/month) that lets you run OTTO on a site beyond what your plan covers. As long as the top-up is active, you will be billed for it each month. If the extra site is no longer needed, removing the top-up stops that charge. ​ 🧊 How Deep Freeze Relates to a Top-Up​ OTTO top-ups are linked to a specific project. When you deep freeze that project, automation is turned off, the project becomes read-only, and it stops running scans and using automation quota (changes already deployed stay live on the site). The project's OTTO site slot is released automatically after a 14-day hold period. Important: deep freezing does not cancel the recurring top-up charge. The top-up keeps billing on its normal cycle until you cancel it separately (see steps below). Your main project—such as the domain already covered by your Growth plan—stays active and continues running OTTO normally. ​ 🛠️ Steps to Cancel the Top-Up​ To stop the recurring top-up charge, cancel the top-up directly from your billing settings: 1. Log in to your Search Atlas account. 2. Click your Avatar Menu (👤) and go to Billing. 3. Open the Services section. 4. Find the OTTO top-up you want to cancel and click the ⋮ menu on it. 5. Select Cancel and confirm. If you'd prefer, you can also ask support to cancel the top-up for you. Optionally, you can deep freeze the related project to stop automation and release its OTTO site slot after the 14-day hold, but freezing on its own will not stop the top-up billing. ​ ✅ What to Check Before You Freeze​ Before deep freezing, confirm the following so you keep the coverage you need: - Correct project: Make sure you are freezing the extra site tied to the top-up, not the domain included in your plan. - Plan coverage: Verify that the site you want to keep using OTTO on is the one covered by your current plan. - Active work: Deep freezing pauses OTTO activity for that project, so confirm you no longer need optimizations running on it.​ 💳 When Will Billing Stop?​ Cancelling the top-up from Billing → Services stops it from renewing on your next billing cycle. The charge already paid for the current cycle is not prorated. Deep freezing the project alone will not stop billing — the top-up must be cancelled separately. You can review your billing details from the top-right avatar → Billing page (Invoices/Activity Log). 🧯 Troubleshooting​ If something doesn't behave as expected after deep freezing, these previously reported issues have been resolved. If you still encounter any of them, contact support so the team can correct it on your account: - Top-up still being charged: Remember that deep freezing a project does not cancel the top-up on its own — you must cancel it in Billing → Services (or via support). If you've already cancelled the top-up and still see charges, reach out to support to have it removed. - Cancellation looks confirmed but the project still shows active: In some cases the cancellation/freeze confirmation appeared, but the project still showed as active after refreshing the page. Perform a hard refresh and re-check the project status. Contact support if it does not update. - Deep Freeze option appears unavailable: The Deep Freeze option could be incorrectly disabled in a same-day edge case (when the last paid date matched the trial end date). If you cannot select Deep Freeze for a project, contact support. - Unexpected freeze or cancellation warning emails: Some active subscribers previously received cancellation/freeze warning emails in error. If you receive a warning you don't expect, you can disregard it or confirm your status with support.​ 🔄 Reactivating Later​ If you need OTTO on that site again in the future, you can unfreeze the project. Reactivating a frozen project that exceeds your plan's included sites may require adding the top-up again. This lets you scale your usage up or down as your needs change. Note: access to deep-frozen projects on accounts that have been canceled is a known limitation the team is still working on. If your account is canceled and you need to access a deep-frozen project, contact support. 💬 Need More Help?​ If you need further assistance, click the chat icon in the bottom-right corner of the platform and type "Human Teammate" to start a live chat with a member of our team. Additional Notes When you deep freeze an OTTO project, automation pauses immediately and the project's OTTO site slot is released automatically after a 14-day hold period, at which point it becomes available to assign elsewhere. Note that this does not cancel any associated top-up — the top-up must be cancelled separately in Billing → Services or through support. Remove: Permanently detaches OTTO from the project. All OTTO settings and automation history for that site are deleted and cannot be recovered. Use this option only if you are certain you will never reactivate OTTO on that domain.

🧊 Cancel an OTTO Top-Up via Deep Freeze

🚀 Strategic Search Atlas Implementation for SEO Growth

🎯 Why a Strategic Approach Matters Search Atlas offers a powerful suite of SEO tools, and it can feel overwhelming to know where to begin. Rather than exploring features at random, following a structured implementation plan helps you build a strong SEO foundation, identify quick wins, and create a repeatable system for growing organic traffic and leads over time. 🔍 Step 1: Audit Your Site's Current Performance Before making any changes, understand where your site stands today. Start by reviewing your baseline metrics inside Left sidebar → Site Metrics (Site Explorer). This dashboard gives you a snapshot of your domain's authority, traffic trends, and keyword visibility. - Check your top-ranking keywords and their current positions. - Identify pages already receiving organic traffic — these are your quick-win opportunities. - Note any significant drops in ranking or traffic that may require urgent attention. 🔑 Step 2: Build a Targeted Keyword Strategy With your baseline established, move on to keyword research. Navigate to Left sidebar → Keywords → Keyword Magic to discover high-value keyword opportunities relevant to your niche. - Search for broad topics related to your products or services. - Filter by search volume, keyword difficulty, and intent to prioritise terms your site can realistically rank for. - Group keywords by topic cluster — this helps you plan content that covers subjects in depth rather than targeting isolated terms. Next, use Left sidebar → Keywords → Keyword Gap to compare your keyword coverage against competitors. This reveals high-traffic terms your competitors rank for that you are currently missing, giving you a clear content roadmap. 📊 Step 3: Track Rankings Consistently Keyword research only becomes actionable when you monitor progress over time. Set up your tracking inside Left sidebar → Keywords → Rank Tracker. Add the keywords you are targeting from your Keyword Magic and Keyword Gap research. - Organise tracked keywords by campaign, page, or topic cluster for easy reporting. - Review rankings weekly to spot upward trends and pages that need optimisation. - Use ranking movement as a signal to update existing content or build additional backlinks to stalled pages. ✍️ Step 4: Create and Optimise Content Systematically Content is the engine of organic lead generation. Use the insights from your keyword strategy to build a content calendar. For each target keyword cluster, plan one or more pieces of content — whether blog posts, landing pages, or service pages — that directly address user search intent. - Prioritise pages with commercial or transactional intent first, as these are most likely to convert visitors into leads. - Optimise existing pages before creating new ones — improving a page already on page two is often faster than building from scratch. - Interlink related pages to help search engines understand your site structure and distribute authority across your content. 📍 Step 5: Strengthen Your Local SEO Presence If your business serves a local market, local SEO is one of the highest-ROI activities you can invest in. Navigate to Left sidebar → GBP Projects → Overview to see a summary of your local visibility and Google Business Profile (GBP) performance. - Use Left sidebar → Local → Posts to publish regular updates to your GBP, keeping your listing active and relevant. - Manage and respond to customer feedback via Left sidebar → Local → Reviews (GBP Reviews) — consistent review responses improve trust signals for both users and search engines. - Build your local authority with Left sidebar → Local → Local Citations, ensuring your business name, address, and phone number are consistent across directories. - Use the Left sidebar → GBP Projects → Media Library to organise and publish optimised images to your GBP listing. 🔄 Step 6: Review, Iterate, and Scale SEO is not a one-time task — it is an ongoing process. Set a monthly review cadence to assess performance across all the areas above. 1. Check Rank Tracker for keyword movement and identify pages needing attention. 2. Run a fresh Keyword Gap analysis to uncover new competitor opportunities. 3. Review your Local Overview to ensure your GBP health remains strong. 4. Add new content based on keyword clusters you have not yet covered. 5. Repeat the cycle — consistent iteration compounds into significant organic growth over three to six months. 💡 Quick-Start Checklist - Week 1: Audit Site Explorer, set up Rank Tracker for current rankings. - Week 2: Complete Keyword Magic research, run Keyword Gap against top competitors. - Week 3: Prioritise and begin optimising top content opportunities. - Week 4: Set up Local tools if applicable; publish first GBP post and audit citations. - Ongoing: Weekly rank checks, monthly strategy review, continuous content production. 🛠️ Need Help Getting Started? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

📈 Frequently Asked Questions — SEO Fundamentals & Best Practices

This article answers foundational SEO questions that come up frequently when using Search Atlas tools. Understanding these concepts will help you get more value from the platform. What is an OTTO Score and is 100% the goal? The OTTO Score reflects how many of OTTO's identified recommendations have been deployed on your site. A higher score means more optimizations are active. However, 100% is not always the goal — some recommendations may not apply to your site's specific context. 💡 Focus on deploying recommendations in OTTO's highest-priority categories first: On-Page, Schema, and Technical fixes typically have the most direct impact. What is the difference between on-page SEO and technical SEO? On-page SEO refers to optimizations on the content of specific pages — title tags, meta descriptions, heading structure, keyword usage, content depth, and internal links. Technical SEO refers to the infrastructure of the site — crawlability, page speed, mobile-friendliness, structured data (schema), canonical tags, indexation settings, and Core Web Vitals. OTTO handles both categories, grouped separately in its recommendation list. What is schema markup and why does OTTO generate it? Schema markup (JSON-LD structured data) is code added to a page's HTML that tells search engines precisely what the content is — a business, an article, a product, a recipe, etc. Google uses this data for rich results (star ratings, knowledge panels, FAQ accordions). ✅ OTTO generates schema automatically based on your business profile, GBP data, and page content, and deploys it via the pixel or Cloudflare Worker. What is topical authority and how does Content Genius help build it? Topical authority means your site comprehensively covers a subject area, signaling expertise to search engines. Sites with topical authority rank more consistently and broadly. Content Genius builds topical authority through the DKN (mapping all topics your domain should cover) and Topical Maps (generating article clusters around specific themes), ensuring your content fills gaps rather than duplicating existing content. What is a backlink and why does Link Lab matter? A backlink is a link from another website to yours. Google treats backlinks as votes of confidence — links from high-authority, relevant sites improve your Domain Authority and rankings. 💡 Link Lab provides access to a marketplace of real editorial placements on established publisher sites, which is a safer and more scalable approach than manual outreach. What is Domain Authority and how is it calculated? Domain Authority (DA) is a third-party metric (from Moz) scoring your site's overall link equity on a 1–100 scale. Higher is better, but the number itself is only meaningful relative to your competitors — a DA of 40 is strong in some niches, weak in others. Search Atlas's Site Explorer shows DA alongside Domain Rating (DR from Ahrefs) and other backlink metrics. What is the Google 3-Pack and why is it important for local businesses? The 3-Pack (also called the Local Pack) is the box at the top of Google search results showing three nearby businesses on a map. It's prime real estate for local intent searches ("plumber near me," "coffee shop Austin"). Search Atlas's Local Heatmaps show where your business ranks in the 3-Pack across your geographic area, and GBP Galactic provides the tools to improve that ranking. What are Core Web Vitals? Core Web Vitals are Google's page experience metrics: Largest Contentful Paint (LCP — loading speed), Interaction to Next Paint (INP — interactivity), and Cumulative Layout Shift (CLS — visual stability). OTTO's technical audit reports on these and flags pages that need improvement. ⚠️ Pages with poor Core Web Vitals are eligible for a ranking penalty from Google's Page Experience signal. What is E-E-A-T and how should I think about it? E-E-A-T stands for Experience, Expertise, Authoritativeness, and Trustworthiness. Google's search quality guidelines use E-E-A-T to evaluate content quality, particularly for health, finance, legal, and other "Your Money or Your Life" topics. Practically: publish well-researched content, cite credible sources, display clear authorship, and build legitimate backlinks. 💡 Content Genius articles can be tuned for E-E-A-T signals through the Brand Vault tone settings and the on-page audit. What is the difference between a canonical tag and a redirect? A canonical tag tells Google which version of a URL is the "official" one — it doesn't redirect users, it just signals to crawlers. Useful when the same content is accessible at multiple URLs (with/without www, with/without trailing slash, etc.). A redirect (301 or 302) actually sends users and crawlers to a new URL. ⚠️ Use a redirect when content has permanently moved; use a canonical tag when content intentionally exists at multiple URLs but you want one version to rank. What is sitemap.xml and does Search Atlas create one automatically? A sitemap is an XML file listing all pages on your site that you want Google to index. OTTO can configure and manage your sitemap submission to Google Search Console. ✅ Website Studio sites generate a sitemap automatically on publish. For WordPress sites, the MetaSync plugin works alongside your existing sitemap plugin (Rank Math, Yoast, etc.). What does "not indexed" mean and how do I fix it? "Not indexed" means Google knows the page exists but has chosen not to include it in its search results — or hasn't crawled it yet. OTTO's Instant Indexing feature can request immediate indexing of specific URLs via Google's Indexing API. ⚠️ Common causes of non-indexation: noindex tag, thin content, duplicate content, blocked by robots.txt, or the page is simply too new. OTTO's technical audit identifies which cause applies to each page.

🚀 Mastering the Science of Search: OTTO SEO Mastery Course Overview

🚀 Mastering the Science of Search: OTTO SEO Mastery Course Overview The OTTO SEO Mastery Course is a comprehensive educational ecosystem designed for professionals who want to move beyond surface-level SEO tactics and into a deeper, scientific understanding of how modern search engines actually work. Instead of relying on fragmented hacks or outdated opinions, this course teaches a holistic methodology grounded in primary research, controlled experimentation, and over 10 years of real-world campaign data. With more than 400 pages of synthesized research, the program focuses on the physics, systems, and engineering principles behind ranking, relevance, and visibility in both traditional search and AI-driven interfaces. 🧠 What's Inside the Curriculum The curriculum is built around foundational pillars that bridge classic ranking theory with modern AI-first search environments. 📜 Patent & Data Analysis This pillar focuses on understanding search engines from the inside out through deep analysis of primary sources. Topics include: - Google patents such as Knowledge-Based Trust, Embeddings, and vector-based systems - Analysis of the Content Warehouse API leak, offering insight into how Google stores and processes data internally The goal is to move from assumptions to mechanical understanding of search engine behavior. 🧪 Experimental "Petri Dish" SEO Rather than relying on anecdotal case studies, the course provides access to controlled, single-variant SEO experiments. These experiments isolate individual factors to determine true causal impact. A key example is the "Snackusetts" study, where variables were tested independently to identify what genuinely moves rankings. 🧩 Content Engineering & Semantics This section dives into how search engines interpret meaning at scale. Covered concepts include: - Micro and macro semantics - Algorithmic authorship - Topical relevance algorithms - How content structure and semantic alignment influence ranking systems Applying the Domain Knowledge Network (DKN) The DKN tool operationalizes the semantics pillar inside Search Atlas. Recommended workflow: - Look at the map gaps — those gaps represent your next articles. - Prioritize clusters where you already have some existing but incomplete content — completing partial clusters compounds authority faster than starting new ones. - Follow the clusters, not random topics — topical coherence beats keyword scatter. - Prioritize by authority potential when choosing which cluster to complete next. - Pair DKN with the Search Atlas Content Planner to turn cluster gaps into a publishable roadmap. 🤖 Generative Engine Optimization (GEO) A dedicated pillar focused on winning visibility inside AI-driven search interfaces, including ChatGPT and Google's AI mode. Key concepts include: - The Guided Inquiry Framework - Techniques for influencing AI retrieval and synthesis - Visibility strategies specific to generative search results Internal testing showed a 56% improvement in AI search visibility within 30 days using these frameworks. 📍 Local SEO Mastery This module applies the same scientific rigor to local search. You'll learn how to use the Local Ranking Factor Matrix to: - Analyze Google Business Profiles (GBP) - Measure the impact of profile completenessForecast projected gains based on review authority and optimization depth 🎯 Who This Course Is For The OTTO SEO Mastery Course is designed for SEO professionals, content strategists, and product leaders who want a defensible, evidence-based approach to ranking in both classical and AI-driven search. 🛠️ Tooling & Troubleshooting Companion The methodology above is delivered through Search Atlas tooling. The following operational notes address the most common issues encountered while completing the course exercises. 🔗 Indexing Integrations (GSC & Bing) - GSC Instant Indexing: Confirm the integration shows as connected under Avatar → Settings → Integrations. If submissions appear to fail, re-verify the connection before contacting support. - Bing Indexing: Bing's indexing API requires root domain access. If you only have access to a subdomain or subdirectory, Bing Indexing cannot be configured from your account and the integration will not function until root-level verification is provided. 💳 AI Premium Credits & Quotas - Recurring quota (your monthly AI Premium allotment) can be restored by support if it was consumed in error. Reload the tab after restoration to see the updated balance. - Non-recurring credits (one-time top-ups) that have already been consumed cannot be restored. Plan high-volume generation runs accordingly. ⚠️ Content AI Editor Errors If you encounter an error when editing an article (e.g., updating the About The Author section), this is typically an intermittent content AI processing issue. Check current platform status at https://status.searchatlas.com/ before retrying or escalating. 📚 Further Learning Refer to the in-app documentation and scheduled training sessions for live walkthroughs of DKN, the Content Planner, and the indexing integrations referenced above.

🚀 Search Atlas Features, Training, and Competitive Edge

🎯 What This Article Covers This article answers the most common questions about Search Atlas platform capabilities, available training resources, and how our tools compare to other SEO platforms — including keyword research and competitor analysis features. 📚 Live Training and Learning Resources Search Atlas offers several ways to get up to speed quickly and continue learning as the platform evolves: - Live weekly walkthroughs: Search Atlas hosts regular live training sessions where the team walks through platform features, new updates, and real-world SEO workflows. Check your email and the in-platform notifications for upcoming session dates and registration links. - On-demand video library: A growing library of recorded tutorials covers everything from initial setup to advanced strategies. These are available inside the platform and through the official Search Atlas YouTube channel. - Help Center articles: Step-by-step KB articles (like this one) cover every major feature with clear navigation instructions and best-practice guidance. - Onboarding support: New customers receive onboarding guidance to help them configure their workspace and launch their first campaigns quickly. These resources are designed to reduce the learning curve and help you get measurable results as fast as possible. 🔍 Keyword Research: How It Compares Search Atlas includes a powerful keyword research suite built to match — and in several areas exceed — what you would find in tools like SEMrush or Ahrefs. Here is what you have access to: - Keyword Magic (Left sidebar → Keywords → Keyword Magic): Generate thousands of keyword ideas from a seed term. Filter by search volume, keyword difficulty, intent, and more. This is comparable to SEMrush's Keyword Magic Tool and is designed for both broad discovery and deep niche research. - Rank Tracker (Left sidebar → Keywords → Rank Tracker): Monitor your keyword rankings over time across multiple locations and devices. Track progress against your target keywords and spot drops early. - Keyword Gap (Left sidebar → Keywords → Keyword Gap): Compare your keyword profile against up to several competitors at once to instantly identify opportunities your site is missing. This is one of the most direct equivalents to SEMrush's Keyword Gap tool. The Search Atlas keyword database is continuously updated, and the tools are integrated with the rest of the platform — meaning insights flow directly into content creation, OTTO SEO, and campaign workflows without switching tabs. 🕵️ Reverse-Engineering Competitor Strategy One of Search Atlas's core strengths is competitive intelligence. You can uncover exactly what is driving a competitor's organic traffic and replicate or outperform their strategy. Here is how: 1. Site Explorer (Left sidebar → Site Metrics (Site Explorer)): Enter any competitor domain to see their estimated traffic, top-ranking keywords, backlink profile, and domain authority. This gives you a complete picture of their SEO footprint. 2. Keyword Gap (Left sidebar → Keywords → Keyword Gap): Input your domain alongside one or more competitor domains. The tool surfaces keywords your competitors rank for that you do not — ranked by opportunity size. Focus on high-volume, lower-difficulty gaps to close ground quickly. 3. Backlink analysis: Within Site Explorer, review a competitor's referring domains to identify link-building opportunities, spot patterns in their anchor text strategy, and find publications you should be targeting. 4. Content benchmarking: Use the data from competitor keyword rankings to brief content that is more thorough and better optimised than what currently ranks on page one. Together, these tools let you move from guesswork to a data-driven strategy based on what is already working in your niche. ⚖️ How Search Atlas Positions Against SEMrush and Similar Tools Search Atlas is built as an all-in-one SEO platform — combining keyword research, rank tracking, backlink analysis, content optimisation, local SEO, and AI-powered automation (OTTO SEO) in a single workspace. Key differentiators include: - OTTO SEO automation: Unlike SEMrush, Search Atlas includes an AI agent that can implement on-page and technical SEO fixes directly on your site — reducing the gap between insight and action. - Local SEO suite (Left sidebar → Local → GBP Projects): A dedicated module covering Google Business Profile management, local citations, reviews, posts, and media — features that require separate tools or add-ons in most competing platforms. - Unified workflow: Research, content creation, optimisation, and reporting all live in one platform, reducing the need for multiple subscriptions. - Pricing: Search Atlas is designed to deliver enterprise-level capabilities at a more accessible price point than comparable all-in-one platforms. 💡 Tips for Getting the Most from Search Atlas - Attend at least one live weekly walkthrough to see features demonstrated in real time and ask questions directly. - Start with the Keyword Gap tool to identify your quickest competitive wins before building out a broader content plan. - Use Site Explorer to audit a competitor before entering a new niche or launching a campaign. - Bookmark the Help Center and check it before escalating — most workflows are covered in step-by-step articles. 🙋 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Finding Product Updates and Notifications in Search Atlas 🗺️

🗺️ Overview The Search Atlas dashboard layout has been updated, and the location of product updates and notifications may not be immediately obvious. If you are looking for the latest platform updates, new feature announcements, or in-app notifications, this article explains how to find them in the current UI. 📍 Finding What's New and Notifications To find product updates and notifications in the current Search Atlas dashboard, follow these steps: 1. Log in to your Search Atlas account. You will land on the Home page (/home). 2. Look at the top navigation bar. Click the apps-grid icon (More Features) in the header, then go to Help → What's New to access product updates and notifications. 3. Click the What's New entry or notifications indicator to open a panel showing the latest feature announcements and platform updates. 4. If you do not see these elements in the top navigation, navigate directly to the Home page (/home) and look for update-related cards or announcement banners displayed on the main dashboard area. 🏠 What Is on the Home Dashboard The Home page is designed as a quick-access overview of your account activity and key SEO metrics. Product update communications and the What's New entry point are accessible from the header apps-grid icon (More Features) → Help → What's New. If you recently noticed the location changed, this is because the dashboard layout was updated — the feature is still available via the header apps-grid icon (More Features) → Help → What's New. 💬 Still Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 Install OTTO Pixel on Your Squarespace Site

🧩 What Is the OTTO Pixel? The OTTO Pixel is a small tracking script that connects your Squarespace website to Search Atlas. Once installed, it allows OTTO SEO to collect on-site data, monitor performance, and apply automated SEO optimizations directly to your site. 🔍 Step 1: Find Your OTTO Pixel UUID in Search Atlas 1. Log in to your Search Atlas account. 2. In the left sidebar, click OTTO SEO, then open SEO Automation (URL: /seo-automation-v3). 3. Select the project associated with your Squarespace website. 4. Navigate to the OTTO Settings or Pixel section within your project dashboard. 5. Locate your unique OTTO Pixel UUID script. It will look similar to a short JavaScript snippet containing a unique identifier string. 6. Copy the full script to your clipboard. 🌐 Step 2: Add the OTTO Pixel to Squarespace Squarespace allows you to inject custom code through its built-in Code Injection feature. Follow these steps: 1. Log in to your Squarespace account and open your website dashboard. 2. In the left sidebar, click Settings. 3. Scroll down and click Advanced, then select Code Injection. 4. In the Header field, paste your OTTO Pixel UUID script. 5. Click Save in the top-left corner. Important: Code Injection is available on Squarespace Business plans and above. If you do not see this option, check your current Squarespace subscription plan. ✅ Step 3: Verify the Pixel Is Installed Correctly 1. Return to Search Atlas, click OTTO SEO in the left sidebar, then open SEO Automation. 2. Open your project and navigate to the OTTO Settings or Pixel section. 3. Check for a confirmation indicator showing the pixel has been detected on your site. 4. If the status shows Installed, the installation was successful. Otherwise, it will show Not Installed. It may take a few minutes after saving in Squarespace for Search Atlas to detect the pixel. If it has not been detected after 10–15 minutes, clear your browser cache and reload both platforms. ⚠️ Common Issues and Tips - Pixel not detected: Double-check that the full script was pasted without any characters missing. Even a small copy error will prevent detection. - Code Injection not available: This feature requires a Squarespace Business plan or higher. Upgrade your plan if needed. - Script pasted in the wrong field: Always paste the OTTO Pixel script in the Header field, not the Footer or Page Header fields. - Multiple websites: Each Squarespace site needs its own unique OTTO Pixel UUID. Do not reuse a pixel script from a different project. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team. Additional Notes Do not share your UUID publicly or use another site's UUID. Script format example:

🔌 Install OTTO Pixel in Webflow Custom Code

🧭 Overview The OTTO Pixel is a tracking script that allows OTTO to audit and automate SEO changes on your website. When using Webflow, the script must be added through Webflow's built-in custom code feature. If the pixel is not being recognized after installation, our support team can walk you through the exact steps required for your account setup. ✅ Before You Begin - Confirm you have the necessary access level in Webflow to add custom code to your project. - Make sure your Webflow site is published before expecting the pixel to be detectable — unpublished changes are not visible to external scanners. - Have your OTTO Pixel script ready to copy from within Search Atlas. 📋 General Installation Process The general process for installing the OTTO Pixel in Webflow involves the following steps. Because the exact UI labels and navigation paths in both Search Atlas and Webflow may vary depending on your account type and platform version, contact our support team if you are unsure where to find a specific setting. 1. Log in to Search Atlas and locate your unique OTTO Pixel script. Copy it to your clipboard. 2. Log in to your Webflow project and navigate to the area where custom code can be added to your site. 3. Paste the OTTO Pixel script into the appropriate custom code area for site-wide scripts. 4. Save your changes and republish your Webflow site so the script appears on your live pages. 5. Return to Search Atlas and initiate a pixel detection or site scan for your website. 🛠️ If the Pixel Is Still Not Recognized If the pixel is not detected after following the steps above, common things to check include: - Site not republished: Changes in Webflow only go live after you explicitly publish the site. Verify the site was republished after pasting the script. - Script placement: Ensure the script was added to a site-wide location rather than a single page, unless OTTO only needs to track a specific page. - Correct script copied: Confirm the script you pasted matches the one shown in Search Atlas for the correct website/project. If you have worked through these checks and the pixel is still not recognized, please have the following ready when you contact support: your Search Atlas project or website name, the Webflow site URL, and any error or status message shown in Search Atlas. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Install OTTO on a Wix Website

🔍 Overview OTTO is Search Atlas's AI-powered SEO automation engine. To let OTTO analyse and optimise your website, it needs to verify ownership by detecting a small tracking pixel on your pages. Wix uses a closed, proprietary builder, so the installation steps differ slightly from WordPress or custom-coded sites. This article walks you through the full setup and explains what to do if you see the red 'OTTO not found' warning. ⚙️ Before You Begin - You must be logged in to both Search Atlas and your Wix account. - You need Editor or Admin access to the Wix site you want to connect. - OTTO works at the domain level — confirm you are installing the pixel on the correct domain. 🚀 Step 1: Find Your OTTO Pixel Code 1. In Search Atlas, navigate to the OTTO or OTTO SEO section of the platform. 2. Add a new site or select an existing site from your list. 3. Follow the on-screen prompts until you reach the pixel installation step. 4. Copy the pixel snippet — it is a short JavaScript tag unique to your site. 🌐 Step 2: Add the Pixel to Your Wix Site Wix does not allow direct file editing, so you must use Wix's built-in custom code functionality to inject the pixel into every page. The exact menu path may vary depending on your Wix plan and dashboard version, but the general process is: 1. Log in to your Wix account and open the dashboard for your site. 2. Locate the settings or advanced section of your Wix dashboard. 3. Find the custom code or tracking tools option. 4. Add a new custom code entry and paste your OTTO pixel snippet into the code box. 5. Give it a recognisable name, for example OTTO SEO Pixel. 6. Set the code to apply to All Pages and place it in the Head section. 7. Save your changes. 8. Publish your site — Wix custom code only goes live after you publish. Use the publish option in your Wix Editor or Dashboard to make the changes live. ✅ Step 3: Verify the Pixel Is Detected 1. Return to Search Atlas and go back to the OTTO or OTTO SEO section. 2. Select your site and look for the pixel verification status. 3. Allow some time for Search Atlas to crawl your homepage and detect the pixel. 4. When the pixel is detected, the status will update to confirm that OTTO is ready to activate. 🔴 What Does 'OTTO Not Found' Mean? The red OTTO not found message means Search Atlas crawled your website but could not detect the pixel code. This is almost always caused by one of the following reasons: - Site not published after adding the code. In Wix, custom code changes do not go live until you publish the site. Make sure you have clicked the publish option after saving your custom code. - Pixel placed on selected pages only. Ensure the custom code is set to load on all pages, not just specific ones. - Pixel placed in the wrong section. The pixel should be placed in the Head section, not the body or footer. - Caching or propagation delay. After publishing, allow a short period for the changes to propagate before re-checking the status in Search Atlas. - Wrong domain connected. Confirm that the domain you connected in Search Atlas matches the domain your Wix site is published on. If you have worked through these steps and the pixel still cannot be detected, it may help to remove the custom code entry in Wix, re-copy the pixel snippet from Search Atlas, and repeat the installation process from the beginning. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Install OTTO AI Pixel on PrestaShop

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

🔌 Connect OTTO Pixel and CMS to Namecheap

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

🔧 Install OTTO Script on Non-WordPress Sites

🧭 What This Article Covers OTTO, the Search Atlas OTTO SEO assistant, requires a small JavaScript snippet to be installed on your website so it can detect your site and begin making optimizations. If your site does not run on WordPress, you will need to add this snippet manually or through a tag manager. This article walks you through finding the script, installing it, and resolving the OTTO not found error. 🗂️ How to Find Your OTTO Script Snippet 1. Log in to your Search Atlas account. 2. In the left sidebar, click OTTO SEO → All Sites (SEO Automation) to open the OTTO dashboard. 3. If you have not yet connected a site, add your domain. If your site is already listed, select it from the dashboard. 4. Once inside the site dashboard, locate the script installation area within the OTTO setup flow. 5. Copy the JavaScript code snippet unique to your website. 📋 Installation Method 1 — Add Script Directly to Your Site This method works for any website where you have access to edit the HTML source code, including custom-built sites, Webflow, Shopify, Squarespace, and others. 1. Open your website's theme editor, template files, or CMS layout settings. 2. Navigate to the file or section that controls the global <head> tag across all pages. 3. Paste the OTTO script snippet either directly after the opening <head> tag or just before the closing </head> tag. 4. Save and publish your changes. 5. Return to the OTTO setup area in Search Atlas to confirm that OTTO detects your site successfully. 🏷️ Installation Method 2 — Use Google Tag Manager Google Tag Manager (GTM) is supported but not required. If GTM is already set up on your site, it offers a convenient way to deploy the OTTO script without editing code directly. 1. Log in to your Google Tag Manager account and open the container for your website. 2. Click New Tag and select Custom HTML as the tag type. 3. Paste the OTTO script snippet into the HTML field. 4. Under Triggering, select All Pages so the script fires on every page load. 5. Click Save, then click Submit and Publish to push the tag live. 6. Return to Search Atlas and check the OTTO setup area to confirm detection. ⚠️ Resolving the "OTTO Not Found" Error If you see an OTTO not found error after installing the script, try the following steps: - Confirm the snippet was pasted into a location that loads on every page of your site, not just a single page template. - If you used Google Tag Manager, verify that the tag has been published (not just saved) and that the All Pages trigger is applied. - Clear your site's cache and any CDN cache, then reload the page and re-check detection in Search Atlas. - Ensure no security plugin, firewall, or Content Security Policy is blocking external JavaScript from loading. - View your page source in a browser and search for the OTTO snippet to confirm it is present in the rendered HTML. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🤖 Install OTTO on HubSpot via Custom JavaScript

🧭 Overview If your website runs on HubSpot, you cannot use the Cloudflare integration to install OTTO. Instead, you will add the OTTO script directly to your HubSpot site's custom header HTML. This article walks you through every step, from copying your script to confirming OTTO is active. ⚙️ Before You Begin - You must have Admin or Super Admin access in your HubSpot account. - Your Search Atlas account must have an active OTTO seat assigned to the property you want to manage. - Make sure your website domain in Search Atlas matches the domain you are managing in HubSpot. 📋 Step 1: Copy Your OTTO Script from Search Atlas 1. Log in to Search Atlas and go to OTTO SEO → Installation Guide in the left sidebar. 2. Locate the property for machmanufacturing.io in your property list. 3. Click Activate OTTO or open the OTTO settings for that property. 4. On the Installation Guide page, click Copy Script. The script is a short <script> tag unique to your property. 🛠️ Step 2: Add the Script to HubSpot Site Header 1. Log in to your HubSpot account. 2. In the top navigation, click the Settings gear icon. 3. In the left sidebar, go to Website → Pages. 4. Select the tab for the site you want to update (for example, machmanufacturing.io). 5. Scroll down to the Site Header HTML section. 6. Paste your copied OTTO script into the text area. Place it just before the closing </head> tag if you see existing code, or simply paste it into the empty field. 7. Click Save at the bottom of the page. Important: The Site Header HTML field in HubSpot applies the script globally across all pages on your site. You do not need to add it page by page. 🔍 Step 3: Verify the Installation After saving, use the following methods to confirm OTTO is installed correctly. - Check in Search Atlas: Return to OTTO SEO → Installation Guide in Search Atlas for machmanufacturing.io. Look for a green Connected or Active status indicator. It can take up to 15 minutes for the status to update after you save the script in HubSpot. - Inspect your live site: Open your website in a browser, right-click anywhere on the page, and select View Page Source. Use Ctrl + F (or Cmd + F on Mac) to search for otto or the script tag you pasted. If it appears in the source, the script is live. - Use browser developer tools: Open your browser's developer tools with F12, go to the Network tab, reload the page, and filter requests by otto or your script's domain. A successful request with a 200 status confirms the script is loading. ⚠️ Common Issues and Fixes - Status still shows "Not Connected" after 15 minutes: Double-check that you saved the settings in HubSpot and that the script appears in your live page source. If the script is missing from the source, repeat Step 2. - Script is in the source but OTTO is not activating: Confirm the script you copied belongs to the correct property (machmanufacturing.io) and has not been modified after copying. - HubSpot Site Header HTML field is greyed out: You may not have the correct permissions. Ask your HubSpot Super Admin to make the change or to grant you the necessary access level. - Changes not appearing on the live site: HubSpot may be serving a cached version. Try a hard refresh with Ctrl + Shift + R (or Cmd + Shift + R on Mac), or check back after a few minutes. ❓ Frequently Asked Questions - Do I need Cloudflare to use OTTO? No. Cloudflare is one installation method, but it is not required. The custom JavaScript method described in this article works independently of Cloudflare. - Will this affect my HubSpot site performance? The OTTO script is lightweight and asynchronous. It loads without blocking your page content. - Can I add the script to only specific pages? OTTO requires site-wide installation to function correctly. Adding it only to selected pages will prevent it from working as intended. 💬 Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

☁️ Install OTTO SEO via Cloudflare Worker

☁️ What Is the Cloudflare Worker Installation? Search Atlas can be deployed directly on your website using a Cloudflare Worker — a lightweight script that runs on Cloudflare's edge network. This method is ideal if you prefer not to modify your site's source code directly. To complete the setup, you will need a Cloudflare account with access to your domain's DNS settings and a valid Cloudflare API token. 🛠️ Before You Begin Make sure you have the following ready before starting the installation: - An active Cloudflare account with your website's domain added and proxied through Cloudflare. - Access to the Search Atlas platform with OTTO SEO enabled for your site. - Permission to create API tokens in your Cloudflare account (account owner or admin role). 🔑 Step 1: Create a Cloudflare API Token A Cloudflare API token allows Search Atlas to deploy and manage the Worker on your behalf. Follow these steps to generate one: 1. Log in to your Cloudflare dashboard at dash.cloudflare.com. 2. Click your Avatar Menu (👤) in the top-right corner and select My Profile. 3. Navigate to the API Tokens tab and click Create Token. 4. Configure the token with the permissions required for Workers deployment, including access to Workers Scripts and Workers Routes for the relevant zone (domain). 5. Under Zone Resources, select the specific zone (domain) you are installing Search Atlas on. 6. Review the permissions, then confirm and create the token. 7. Copy the token immediately — Cloudflare will only display it once. ⚙️ Step 2: Enter Your API Token in Search Atlas Once your token is created, return to the Search Atlas platform to begin the Worker installation: 1. Open the Search Atlas platform and navigate to OTTO SEO. 2. Locate the Cloudflare Worker installation option within your site's setup or connection settings. 3. Paste your Cloudflare API token into the designated field and confirm. 4. Search Atlas will verify that the token is active and has the correct permissions before proceeding. If token validation fails, double-check that the token was copied in full, that it has not expired, and that it includes the necessary permissions for Workers deployment on the correct zone. You may need to generate a new token in Cloudflare and re-enter it. 🚀 Step 3: Deploy the Cloudflare Worker After your token is verified, complete the deployment by selecting the Cloudflare zone (domain) you want to deploy the Worker to and confirming the Worker route that will be created for your site. ⚠️ When to Contact Support If you are unable to complete the installation, please have the following ready when you reach out: - Your project or site name in Search Atlas. - The exact error message displayed, if any. - The timestamp of when the issue occurred. - Confirmation of whether the Cloudflare API token was successfully generated and copied. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Install OTTO Tracking Code on a Second WordPress Site

🔍 Overview If you have already connected one WordPress site to OTTO and are now adding a second, the tracking code will not automatically carry over. Each site requires its own unique tracking code, and that code must be installed in the correct location for OTTO to detect it. This article walks you through the general steps to get your second WordPress site verified successfully. ⚙️ Why OTTO Isn't Detecting Your Second Site The most common reasons OTTO fails to detect the tracking code on a second WordPress site are: - Using the wrong tracking code — Every site connected to OTTO gets a unique code. Copying the code from your first site and pasting it into your second site will not work. - Installing into the wrong location — The code must be placed in the <head> section of the page, not the body or footer. - Caching preventing detection — WordPress caching plugins may serve an old version of your page, hiding the newly added code from OTTO's verification check. - Code stripped by a theme or plugin — Some WordPress themes and security plugins filter or remove custom scripts added to the header. 🚀 Step-by-Step: Install the Tracking Code on Your Second Site 1. In the Search Atlas platform, locate the section where your OTTO tracking code is displayed for the second site. 2. Select your second website from the site selector. Make sure you are not viewing your first site. 3. Find the OTTO tracking code for your second site and copy it in full — it is unique to this site and different from the code used on your first site. 4. Log in to the WordPress admin dashboard of your second site. 5. Navigate to Appearance → Theme File Editor (or use a dedicated header plugin if available). 6. Open your theme's header.php file and paste the tracking code immediately before the closing </head> tag. If you are using a header plugin, paste it into the header scripts field. 7. Save your changes. 8. Return to Search Atlas and check whether OTTO can now detect the code for your second site. 💡 Recommended: Use a Header Plugin Editing header.php directly risks losing the code if you update your theme. Using a dedicated header plugin is safer and easier to manage, as it provides a dedicated field for header scripts that survives theme updates. 🧹 Clear Your Cache After Installation After saving the tracking code, clear your WordPress cache using your caching plugin if you have one installed. Serving a cached version of your page may prevent OTTO from detecting the newly added code. Once the cache is cleared, return to Search Atlas to confirm detection. 📋 If You Still Need Help If OTTO is still not detecting your tracking code after following these steps, please have the following ready before reaching out: your site URL, the WordPress plugins currently active on the site, and a description of where you placed the tracking code. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ WordPress Plugin & Cloudflare Setup Order

🔍 Why Timing Matters Search Atlas offers two ways to implement tracking and site optimizations: the WordPress plugin and a Cloudflare CDN integration. Both methods are powerful on their own, but running them simultaneously can cause dashboard errors, duplicate data, or conflicting configurations. Following the correct sequence ensures a smooth transition with no data gaps or broken settings. ⚠️ What Happens If You Use Both at Once Activating Cloudflare while the WordPress plugin is still running may cause: - Dashboard errors or missing metrics in Search Atlas - Duplicate script injections on your site - Conflicting cache rules between the plugin and Cloudflare's CDN layer - Inaccurate reporting due to overlapping data sources To avoid these issues, always follow the step-by-step order below. ✅ The Correct Setup Sequence 1. Log in to your WordPress admin panel. Navigate to Plugins → Installed Plugins and locate the Search Atlas plugin. 2. Deactivate the WordPress plugin. Click Deactivate and wait for the page to confirm the plugin is no longer active. Do not delete it yet — you may want to keep it available in case you need to roll back. 3. Clear your WordPress cache. If you use a caching plugin (e.g., WP Rocket, W3 Total Cache), purge all cached files before proceeding. 4. Log in to your Search Atlas dashboard. Navigate to the Cloudflare integration settings inside the platform. 5. Connect your Cloudflare account. Follow the on-screen prompts to authorise the connection and select the correct domain. 6. Verify the Cloudflare integration is active. Confirm that your domain shows a Connected status in the Search Atlas dashboard before making any further changes. 7. Test your site. Visit your website and check that pages load correctly and no console errors appear in your browser's developer tools. 💡 Tips for a Smooth Transition - Do not reactivate the WordPress plugin after connecting Cloudflare. The two methods serve the same function and do not need to run together. - If you manage multiple WordPress sites, repeat this process for each domain individually — do not connect all sites at once. - Allow up to 24 hours for Cloudflare's DNS propagation to complete fully after connecting. Some metrics in your dashboard may appear delayed during this window. - Keep a note of your plugin settings before deactivating, in case you need to reference any custom configurations later. 🔄 Rolling Back to the WordPress Plugin If you need to switch back to the WordPress plugin for any reason, reverse the process: disconnect the Cloudflare integration in your Search Atlas dashboard first, then reactivate the plugin in WordPress. Never enable both at the same time. 🙋 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔑 OTTO Pixel WordPress Plugin API Key Setup

🧩 Overview If the OTTO pixel shows Not Installed even after reinstalling the plugin and clearing your cache, the most common root cause is a missing or incorrectly entered API key in your WordPress plugin settings. This article walks you through the complete setup so your OTTO pixel verifies successfully. 🔍 Step 1: Locate Your OTTO API Key in Search Atlas 1. Log in to your Search Atlas account. 2. In the left sidebar, click OTTO SEO, then open SEO Automation. The URL will change to /seo-automation-v3. 3. Open the OTTO dashboard for the website you are connecting. 4. Click Settings or the pixel/installation section within OTTO. 5. Copy the unique API key displayed for your site. Keep this tab open — you will paste the key into WordPress in the next steps. ⚙️ Step 2: Enter the API Key in Your WordPress Plugin Settings 1. Log in to your WordPress admin panel (yoursite.com/wp-admin). 2. In the left menu, go to Search Atlas → Settings. 3. Locate the API Key field. This field is required and must not be left blank. 4. Paste the Search Atlas API key you copied into this field. 5. Paste the OTTO Pixel UUID. 6. Click Save Changes. Important: The API key is unique to each website. If you manage multiple sites, make sure you are using the correct key for the domain you are configuring. 🗑️ Step 3: Clear All Caches After Saving Caching layers can prevent the pixel from being detected even when the plugin is configured correctly. After saving your API key, clear caches in this order: 1. WordPress caching plugins — Go to your caching plugin (such as WP Rocket, W3 Total Cache, or LiteSpeed Cache) and purge all caches. 2. Hosting-level cache — Log in to your hosting control panel and clear any server-side or CDN cache. Refer to your host's documentation if needed. 3. Browser cache — In your browser, press Ctrl + Shift + Delete (Windows) or Cmd + Shift + Delete (Mac), select cached images and files, and clear them. 🔄 Step 4: Trigger a Sync and Verify the Pixel 1. Return to the OTTO dashboard in Search Atlas (click OTTO SEO in the left sidebar, then open SEO Automation). 2. Click Verify Installation or Check Pixel Status for your site. 3. Wait up to 2 minutes for the verification to complete. The status should change from Not Installed to Installed. 4. If the status does not update after 2 minutes, click Re-check or refresh the page. ⚠️ Common Reasons the Pixel Still Shows Not Installed After Setup - Wrong API key used — Double-check that the key in WordPress matches exactly what is shown in the OTTO dashboard for that specific domain. - Plugin not activated — Confirm the MetaSync (SearchAtlas) plugin status shows Active in WordPress, not Inactive or Deactivated. - Conflicting plugins — Security or firewall plugins (such as Wordfence) can block pixel scripts. Temporarily disable them to test, then whitelist the OTTO script if needed. - Cache not fully cleared — If you use a CDN such as Cloudflare, purge the CDN cache in addition to your WordPress and hosting caches. - API key field saved with extra spaces — When pasting your API key, ensure there are no leading or trailing spaces in the field before saving. ✅ Quick Checklist Before Contacting Support - API key copied from the correct OTTO site dashboard and pasted into WordPress plugin settings - Changes saved in WordPress - WordPress caching plugin cache cleared - Hosting and CDN cache cleared - Browser cache cleared - Pixel verification re-run in Search Atlas - Plugin shows as Active in WordPress If you have completed every step above and the pixel still shows Not Installed, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🚀 Switch From GHL to Vercel and Install OTTO

🔍 Overview If you moved your website from GoHighLevel (GHL) to Vercel, your Search Atlas project needs to be updated. The old GHL integration should be disconnected, and your site should be reconnected through Vercel so OTTO can be installed on the new hosting setup. This article walks you through the full process: disconnecting GHL, connecting Vercel, installing OTTO, and checking that everything works. 📋 Before You Begin Make sure you have the following ready: - Your website is live on Vercel and loads correctly on your domain. - You can log in to your Vercel account with permission to manage the project. - You can log in to Search Atlas as the project owner or an admin. - Your domain no longer points to GHL (your DNS or domain settings now point to Vercel). Tip: Menu names in the platform may change slightly as we update the product. If a label looks a little different from what is described here, look for the closest match. 🔌 Step 1: Disconnect the GHL Integration Disconnecting GHL first helps avoid conflicts between the old and new setups. 1. Log in to Search Atlas and open the project for your website. 2. Go to the integrations or OTTO installation settings for that project. 3. Find the GoHighLevel (GHL) connection. 4. Select the option to disconnect or remove the integration, and confirm when prompted. 5. If you previously added an OTTO script or snippet inside your GHL account, log in to GHL and remove it there too. This keeps old code from lingering on a site you no longer host there. Disconnecting does not delete your Search Atlas project, your keywords, or your reporting history. It only removes the link between OTTO and your old GHL site. 🔗 Step 2: Connect Your Vercel Site 1. In the same project, open the OTTO installation or integrations area. 2. Choose Vercel as your platform or deployment method. 3. Follow the on-screen prompts to authorize access. You may be asked to sign in to Vercel and select the project that hosts your website. 4. Confirm that the domain shown in Search Atlas matches the domain of your live Vercel site. 5. Save or complete the connection. If you are asked to add a setting, key, or code snippet to your Vercel project, copy it exactly as shown in Search Atlas. Then redeploy your Vercel project so the change goes live. ⚙️ Step 3: Install OTTO 1. After the Vercel connection is saved, return to the OTTO installation screen. 2. Follow the remaining installation steps shown for Vercel. 3. If a change was made to your Vercel project, trigger a new deployment from your Vercel dashboard. 4. Wait for the deployment to finish, then return to Search Atlas and run the installation check, if available. Once OTTO detects the installation, the status in your project should change to connected or active. ✅ Step 4: Verify That Everything Works - Check the status: Your project should show OTTO as installed and Vercel as the connected platform. - Visit your site: Open your website in a private or incognito browser window to avoid cached content. - Confirm the GHL link is gone: GHL should no longer appear as an active integration in your project. - Allow some time: Some changes may take a little while to appear, especially if your site uses caching. 🛠️ Troubleshooting Common Issues - OTTO is not detected after installation: Make sure your Vercel project was redeployed after the changes. Then clear your browser cache and run the installation check again. - The wrong domain is connected: Confirm that the domain in Search Atlas matches the live domain on Vercel, including whether it uses www or not. - You cannot find your Vercel project: Check that you are signed in to the correct Vercel account or team and that you have permission to access the project. - GHL still appears as connected: Refresh the page and try disconnecting again. Also confirm that the domain no longer points to GHL. - Old changes still show on your site: Clear any site or CDN cache, then reload the page in a private window. 💡 Best Practices - Complete the domain move to Vercel before reconnecting in Search Atlas. - Disconnect GHL before connecting Vercel to keep your setup clean. - Redeploy your Vercel project after any installation change. - Test your site in a private window after each update. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🛠️ How to Install OTTO Pixel on GoHighLevel

🔍 What Is the OTTO Pixel? The OTTO pixel is a small snippet of code that connects your website to Search Atlas OTTO. Once it is on your site, OTTO can apply SEO improvements automatically, without you editing each page by hand. GoHighLevel (GHL) sites, including sites built with GoHighLevel's AI Studio, let you add custom code to the header of your site. That is where the OTTO pixel goes. ✅ Before You Start Have the following ready so the setup goes smoothly: - Access to your Search Atlas account with your website added as an OTTO project - Admin access to the GoHighLevel sub-account that contains your website - Your site's live domain connected in GoHighLevel, if you want to test on the live site 📋 Step 1: Copy Your OTTO Pixel Code 1. Log in to Search Atlas. 2. Open OTTO and select the project for your website. 3. Find the installation or pixel section and choose the option for adding the pixel manually. 4. Copy the full code snippet. Make sure you copy all of it, from the opening tag to the closing tag. Each project has its own unique pixel. Do not reuse a pixel from another website. ⚙️ Step 2: Add the Pixel in GoHighLevel The exact menu names in GoHighLevel can change over time, but the process is usually the same: 1. Log in to GoHighLevel and open the sub-account that holds your website. 2. Go to Sites and open Websites (or Funnels, depending on how your site was created). 3. Click your website to open it. 4. Open the site's Settings tab. 5. Find the Head Tracking Code or Custom Code (Header) field. 6. Paste the OTTO pixel code into the field. 7. Click Save. Adding the code at the site level is best, because it loads the pixel on every page. If you only see page-level code options, add the pixel to each page you want OTTO to optimize. 🤖 Sites Built With GoHighLevel AI Studio If your site was generated with AI Studio, it is still a GoHighLevel website, so the pixel is installed the same way. Open the site in the website builder, then look for the site Settings or Custom Code area and paste the pixel into the header section. Keep these tips in mind: - If you regenerate or rebuild the site with AI Studio, check that the pixel is still in the header settings afterward. - If you cannot find a header code field, check for a custom code option at the page level instead. - Paste the code as plain text. Copying from a formatted document can add extra characters that break the snippet. 🚀 Step 3: Publish Your Changes Saving the settings may not be enough. Publish or re-publish your website in GoHighLevel so the updated code goes live. If you use a custom domain, make sure it points to the published site. 🔎 Step 4: Verify the Installation 1. Return to your project in Search Atlas OTTO. 2. Use the option to check or verify the pixel installation. 3. If it does not show as connected right away, wait a few minutes and try again. You can also open your live website in a private or incognito browser window, so you are not seeing a cached version, and then check again in OTTO. 🛠️ Troubleshooting Common Issues - Pixel not detected: Confirm you published the site after saving the code, and that you are testing the live domain rather than a preview link. - Code pasted in the wrong place: The pixel belongs in the header (head) section, not in the footer or in a page text block. - Incomplete snippet: Copy the pixel again from OTTO and make sure the whole snippet was pasted. - Wrong project: Check that the pixel came from the OTTO project that matches this website. - Changes not showing: Clear your browser cache, or check the site in a private window. - Multiple sites in GoHighLevel: Each site needs its own pixel installed in its own settings. 💡 Helpful Tips - Install the pixel once at the site level rather than adding it page by page. - Save a copy of your pixel code in a safe place in case you need to reinstall it later. - After any major site rebuild, re-verify the pixel in OTTO. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

⏳ OTTO Cloudflare Token: What to Expect After Setup

🔍 Overview After you connect your Cloudflare API token to OTTO, the platform begins a background audit of your website. This audit is required before OTTO can be detected and activated. It is completely normal for OTTO to show as 'not found' for up to 24 hours after your token is connected. No action is needed during this time. 🗺️ How to Access OTTO To reach the OTTO dashboard, navigate to OTTO SEO in the left sidebar of the platform and open SEO Automation inside it. Your OTTO status and connected sites are managed from this section. ⚙️ What Happens After You Connect Your Cloudflare Token Connecting your Cloudflare token triggers a multi-step process that runs automatically in the background: 1. Token validation — Search Atlas verifies that your Cloudflare API token has the correct permissions. 2. DNS record discovery — The platform scans your Cloudflare account to locate all domains associated with the token. 3. Site audit initiation — OTTO begins a full technical audit of each discovered domain. This is the most time-intensive step. 4. OTTO activation — Once the audit completes, OTTO becomes visible and ready to deploy optimisations on your site. The entire process typically completes within 24 hours, though most sites are ready sooner. The exact duration depends on site size, the number of pages crawled, and current platform load. 📋 Cloudflare Token Permission Requirements Before waiting out the audit period, confirm your token was created with the correct permissions. An incorrectly scoped token will cause the audit to fail silently. Your Cloudflare API token must include: - Zone — DNS — Edit - Zone — Zone — Read - Workers Scripts — Edit - Workers Routes — Edit - Workers KV Storage — Edit If you are unsure whether your token has these permissions, you can generate a new token in your Cloudflare dashboard under My Profile → API Tokens → Create Token and reconnect it inside the OTTO setup flow. ✅ How to Check Your OTTO Status You can monitor the audit progress at any time: 1. Go to OTTO SEO in the left sidebar and open SEO Automation inside it. 2. Locate your connected site in the OTTO dashboard. 3. Check the status indicator next to your domain. Statuses you may see include: - Auditing — The background audit is in progress. No action required. - Not Found — The audit has not yet started or is still queued. This is expected within the first 24 hours. - Active — The audit is complete and OTTO is ready to use. 🚫 What Not to Do While the Audit Is Running To avoid interrupting the audit process, please avoid the following during the 24-hour window: - Disconnecting and reconnecting the Cloudflare token - Revoking or modifying the API token permissions in Cloudflare - Changing your domain's nameservers away from Cloudflare Repeating the token connection resets the audit timer and extends your wait time. ⚠️ When to Take Action In most cases, waiting 24 hours resolves the 'not found' status automatically. However, you should take action if: - More than 24 hours have passed and OTTO still shows Not Found or no status at all - You received an error message during the token connection step - Your domain does not appear in the OTTO site list at all after 24 hours In these situations, first confirm your Cloudflare token permissions are correct (see above), then proceed to contact support using the instructions below. 💬 Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 IndexNow Setup and Brand Vault Image Uploads

🌐 What Is IndexNow and Why It Matters IndexNow is a protocol that lets you instantly notify search engines — including Bing — whenever your content is created, updated, or deleted. Connecting it inside Search Atlas means your pages get crawled and indexed faster, without waiting for a search engine to discover changes on its own. ⚙️ How to Set Up IndexNow for Bing Setting up IndexNow for Bing involves connecting Search Atlas to your Bing Webmaster Tools account. Follow these steps: 1. Log in to Search Atlas and navigate to Settings in the left-hand sidebar. 2. Select Integrations (or Site Settings) and locate the IndexNow section. 3. Click Connect next to the Bing IndexNow option. 4. You will be prompted to enter your Bing Webmaster Tools API key. To find this, log in to Bing Webmaster Tools, go to Settings → API Access, and copy your API key. 5. Paste the API key into Search Atlas and select the site property you want to connect. 6. Click Save to confirm the connection. Search Atlas will now automatically submit URLs to Bing via IndexNow whenever content is published or updated. If you see an error during connection, double-check that the API key matches the correct Bing Webmaster Tools property and that the domain in Search Atlas matches the verified domain in Bing Webmaster Tools. 🏛️ What Is Brand Vault? Brand Vault is your centralised library of brand assets inside Search Atlas. It stores logos, product images, team photos, and other visual resources so they can be referenced across your SEO campaigns, content, and reporting. Keeping Brand Vault complete and up to date helps Search Atlas better represent your brand identity in AI-powered features and content generation. 🖼️ How to Upload Images to Brand Vault You can upload image assets to Brand Vault directly within Search Atlas. Follow these steps: 1. Log in to Search Atlas and navigate to Brand Vault via the header apps-grid icon → More Features → Brand Vault. 2. Click the Upload button (or the + icon) within the Brand Vault section. 3. Select the image file(s) you want to upload from your device. Supported formats typically include JPG, PNG, GIF, or WebP. 4. Once selected, the file will begin uploading. You can add a name or label to each asset for easy reference. 5. Click Save or Confirm to finalise the upload. Your images will now appear in your Brand Vault library and be available for use across Search Atlas features. If an upload fails, check the following: - Ensure the file format is supported (JPG, PNG, GIF, or WebP). - Check that the file size is within the allowed limit (up to 10 MB per image). - Try refreshing the page and uploading again. - If the error persists, note the exact error message and the file's format and size so our team can assist you efficiently. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛍️ Migrating Your Website to Shopify

🔎 Overview Moving your website to Shopify (or any new hosting platform) does not mean starting over in Search Atlas. Your account, project history, and keyword tracking can continue as normal. What matters is whether your domain name stays the same and whether your page URLs stay the same. This article walks you through what to do before, during, and after the move so you keep your rankings and data. 🧭 Step 1: Decide Which Migration Type You Have Your next steps depend on which of these applies to you: - Same domain, new platform: You keep your domain (for example, yourbrand.com) and only change where the site is built and hosted. Your existing Search Atlas project can usually stay in place. - New domain: Your website address changes. In this case, set up a new project in Search Atlas for the new domain and keep the old one for reference until your redirects have taken effect. 📋 Step 2: Before You Migrate Capture a baseline so you can compare results after the move. 1. Run a fresh Site Audit on your current site and save or export the results. 2. Export your current keyword rankings from your tracking project so you have a before-and-after comparison. 3. Make a list of your most important pages, such as your top traffic pages, service or product pages, and any pages that currently rank well. 4. Write down the page titles, meta descriptions, and headings on those key pages. 5. If you use OTTO SEO, note which optimizations you have deployed so you can confirm them after the move. 🔗 Step 3: Protect Your URLs During the Move Changing URLs is the most common cause of ranking drops after a migration. Shopify uses its own URL structure (for example, /products/ and /collections/), so some of your old URLs may change. - Keep your old URLs wherever possible. - For every URL that changes, create a 301 redirect from the old address to the new one. In Shopify, you can do this under Online Store, Navigation, then URL Redirects. - Redirect each old page to the most closely related new page, not just your home page. - Carry over your page titles, meta descriptions, image alt text, and on-page content. - Make sure your new store is not password-protected and is not blocking search engines when you go live. ⚙️ Step 4: Reconnect OTTO SEO and Other Tools OTTO SEO works by connecting to your website. When the website platform changes, that connection needs to be set up again on the new site. - Open your project in Search Atlas and follow the OTTO installation instructions for your new platform. - After reconnecting, confirm that your OTTO optimizations are showing on the live pages. Re-deploy any that are missing. - If you use other connected tools, such as Google Search Console, Google Analytics, or Google Business Profile, check that each connection is still active. Reconnect any that show an error. 🚀 Step 5: After Your Site Goes Live 1. Visit your most important pages and confirm they load correctly and old URLs redirect properly. 2. Run a new Site Audit in Search Atlas and look for broken links, missing titles or descriptions, redirect problems, and pages blocked from indexing. 3. Submit your new Shopify sitemap (usually yourdomain.com/sitemap.xml) in Google Search Console. 4. If your domain changed, use the Change of Address tool in Google Search Console. 5. Check your keyword rankings daily for the first two weeks, then weekly. Small movements are normal while search engines re-crawl your site. 6. Compare your new audit and rankings with the baseline you saved in Step 2. ⚠️ Common Mistakes to Avoid - Skipping redirects: Old URLs that lead to error pages lose their ranking value. - Leaving the site in test mode: A password page or search-engine block will keep your pages out of search results. - Forgetting to reconnect OTTO: Optimizations will not appear on the new site until the connection is re-established. - Creating a duplicate project unnecessarily: If your domain is unchanged, keep your existing project so you do not lose history. - Changing too much at once: Avoid redesigning your content and changing platforms at the same time if you can, so you can tell what caused any ranking change. ❓ Quick Answers - Will I lose my Search Atlas data if I migrate? No. Your account and historical data stay in Search Atlas. Only the connection to your website needs to be updated. - Do I need a new project? Only if your domain name changes. - How long until rankings recover? With correct redirects, many sites stabilize within a few weeks, though timing varies. 💬 Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🚀 Migrate WordPress to Lovable with Search Atlas

🔍 Overview Moving your website from WordPress to Lovable is a multi-step process. The good news is that you can fully configure Search Atlas on your new Lovable site before you point your domain to it. This means zero downtime for your SEO tracking and no scrambling to set things up after the switch. This article walks you through exactly how to do that. 📋 What You Will Need Before You Start - An active Search Atlas account - Your existing WordPress site currently live and tracked in Search Atlas - A published Lovable project (the site must be published to generate a UUID) - Access to your domain registrar or DNS settings 🛠️ Step 1: Publish Your Lovable Site and Get the UUID Search Atlas identifies your Lovable site using a UUID — a unique identifier that Lovable assigns to each published project. You cannot retrieve the UUID from an unpublished project, so make sure your Lovable site is published first. 1. Log in to your Lovable account and open your project. 2. Click Publish if you have not already done so. Lovable will generate a preview URL in the format your-project-name.lovable.app. 3. To find the UUID, look at the Lovable project URL in your browser while inside the editor. The UUID is the alphanumeric string in the URL, for example: lovable.dev/projects/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx. Copy this value. If you are unsure where to find the UUID, open your Lovable project settings — it is typically displayed under project details or in the share/publish panel. ⚙️ Step 2: Add Your Lovable Site to Search Atlas With your UUID ready, you can now add the Lovable site to Search Atlas using its preview URL. This lets you start configuring everything before your real domain is pointed over. 1. In Search Atlas, go to Left sidebar → Site Metrics (Site Explorer). 2. Click Add New Site (or the + icon at the top of your site list). 3. Enter your Lovable preview URL (e.g., your-project-name.lovable.app) as the site URL. 4. Complete the site setup and save. Once the site is added, Search Atlas will begin pulling data for that URL. You can set up rank tracking, run keyword research, and configure all settings against the preview URL right away. 📊 Step 3: Configure Search Atlas Settings on the Lovable Site Before switching your domain, get your Search Atlas setup fully in place: - Rank Tracker: Go to Left sidebar → Keywords → Rank Tracker and add the keywords you want to monitor for the new site. - Keyword Magic: Use Left sidebar → Keywords → Keyword Magic to research and map keywords to the new Lovable pages. - Keyword Gap: Run a competitor gap analysis via Left sidebar → Keywords → Keyword Gap to identify opportunities ahead of launch. 🔄 Step 4: Point Your Domain to Lovable When your Lovable site is ready to go live, update your DNS settings at your domain registrar to point your custom domain to Lovable. Refer to Lovable's official documentation for the exact DNS records required, as these may vary. After DNS propagation is complete (usually 24–48 hours), update the site URL in Search Atlas to reflect your custom domain: 1. Go to Left sidebar → Site Metrics (Site Explorer) and select the Lovable site you added. 2. Navigate to the site settings and update the URL from the .lovable.app preview URL to your custom domain (e.g., www.yourdomain.com). 3. Save your changes. Search Atlas will now track rankings and metrics against your live domain. ⚠️ Important Notes - Rank tracking history is tied to the URL you entered. Updating the URL to your custom domain starts fresh tracking on that domain — plan accordingly if historical data matters to you. - If you were previously tracking your WordPress site in Search Atlas under the same domain, you do not need to delete that property until you are confident the Lovable migration is complete and stable. - Make sure your Lovable site has a connected custom domain before updating the URL in Search Atlas, otherwise tracking will not work correctly. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.