Deployment & Rendering

🛠️ Service Page Type Suggested But No Schema to Deploy

💡 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.

⚡ Bulk Schema Generation and Deployment Workflow

Overview Search Atlas lets you generate schema markup for multiple pages at once using the bulk schema workflow. If your generated schemas seem to disappear after selection, or you cannot find the deploy option, this article explains what is happening and how to complete the process. How Bulk Schema Generation Works The bulk schema workflow is designed to let you generate structured data for several pages in a single session. The general flow involves selecting pages, generating schema markup for each, and then deploying the generated schemas to make them live on your site. Generated schemas are held in a staging state after generation — they are not live until you explicitly deploy them. The most common point of confusion is this staging state: generated schemas do not disappear, but they move to a different view within the schema tool once processed, requiring a separate deploy step. Why Generated Schemas Appear to Disappear After bulk generation, schemas may no longer appear in the same view as unprocessed pages. This can make it look like the output has been lost. Common reasons this happens include: - Filter mismatch: The page list defaults to showing only pages without schema. Once schema is generated for a page, it moves out of that filtered view automatically. - Status view not switched: Generated schemas appear under a separate status — you need to change the status filter in the schema tool to see pages that already have schema generated. - Selection cleared: Navigating away from the page or refreshing the browser before deploying can clear your selection and may require you to regenerate. How to Locate Your Generated Schemas and Deploy Them Follow these steps to find your staged schemas and complete deployment: 1. Open the Schema Creator tool by clicking the apps-grid icon in the header, then selecting More Features → Schema Creator, and select your project. 2. Look for a status filter or tab selector near the top of the page list — common options include labels such as No Schema, Generated, and Deployed. 3. Switch the filter or tab to Generated (or the equivalent status for schemas that have been created but not yet deployed). Your previously generated schemas will appear here. 4. Select all the pages whose schemas you want to deploy by checking the checkboxes next to each page, or use the Select All option if available. 5. With pages selected, look for a Deploy button or a bulk action dropdown at the top of the list. Click it to push the generated schemas live to your site. 6. After deploying, switch the filter to Deployed to confirm the pages now show their schema as active. If you do not see a Generated status tab or the Deploy option does not appear after selecting pages, try clearing any active filters first, then repeat the selection. If the option is still missing, it is possible the generation step did not complete — return to the No Schema view, reselect the affected pages, and run bulk generation again before attempting to deploy. What to Do If You Are Still Stuck If you have followed the steps above and still cannot locate your generated schemas or complete deployment, our support team can walk you through the correct steps for your specific account and project setup. When reaching out, please have the following ready: - Your project name - The pages you attempted to generate schema for - The status tab or filter you currently see in the schema tool - A description of where in the workflow you got stuck (e.g., after generation, before deployment) - 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.

🧠 Understanding Atlas Brain Schema Found vs Deployed

🔍 What Does Found vs Suggested Mean? When Atlas Brain processes your website for schema deployment, it works in two distinct stages: - Suggested (Found): The total number of schema opportunities Atlas Brain has identified across your pages. - Deployed: The number of schemas that have been confirmed as live on your site. A difference between the Found and Deployed counts is a known distinction in how Atlas Brain reports schema status. The exact reasons the two numbers may differ in your specific case can depend on your site setup and configuration. ⚙️ Why the Numbers May Not Match The Found vs Deployed distinction is a recognized behavior in Atlas Brain. Because the underlying causes can vary depending on your site, our support team can review your specific project and confirm what is contributing to the gap you are seeing. 🛠️ What to Do If You See a Gap If your Deployed count is lower than your Found count and you are unsure why, the best next step is to reach out to our support team directly. To help us investigate quickly, please have the following ready: - Your project or site name - The current Found and Deployed counts you are seeing - Any status messages or error messages displayed in Atlas Brain If you need further assistance, open 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 Deploy Button Grayed Out After AI Generation

🧩 Overview After running AI schema generation in Search Atlas, you may notice the Deploy button remains grayed out and unclickable. This can be confusing because the AI generation appears to have completed successfully. This article walks you through self-serve steps to resolve the issue before escalating. 🔍 Why the Deploy Button May Be Grayed Out The Deploy button can remain inactive after AI schema generation for a variety of reasons. The following self-serve steps resolve the issue in most cases. ✅ Steps to Try First 1. Refresh the page. A full browser refresh (Ctrl+F5 or Cmd+Shift+R) can clear a stale UI state that is preventing the button from activating. 2. Re-run AI schema generation. Navigate back to the schema generation step and run the AI generation again. Once it completes, check whether the Deploy button becomes active. 3. Check for unsaved or incomplete changes. Make sure all required fields or schema selections have been completed. An incomplete schema state can keep the Deploy button disabled. 4. Try a different browser or clear your cache. Browser extensions or cached data can sometimes interfere with button states. Test in a private/incognito window or a different browser. 5. Log out and log back in. Re-authenticating can reset session state that may be causing the issue. ⚠️ What to Have Ready If You Still Need Help If the steps above do not resolve the issue, reach out to our support team with the following information ready: - Project or page URL where the Deploy button is grayed out. - Screenshot of the grayed-out Deploy button. - Any error messages visible on the screen. - Steps you have already tried from the list above. If you need further assistance, open 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 Generation, Deployment, and CMS Sync

🔍 Overview Schema markup helps search engines better understand your pages and can improve how your content appears in search results. Search Atlas supports schema markup generation, a deployment workflow to push that markup to your site, and — for Webflow users — CMS sync capabilities to keep your content in sync with the platform. This article explains what is available so you know what to expect and how to get help if something is not working. 📋 Schema Markup Generation Search Atlas includes tools for generating schema markup for your pages, including support for bulk generation across multiple pages at once. If you are not sure where to access the schema generation feature or which schema types are supported for your content, our support team can point you to the right place within your account. When reaching out about schema generation, please have the following ready: - The name of the project you are working in - The URL or URLs you are trying to generate schema for - The schema type you need (e.g. Article, Product, FAQ, LocalBusiness) if known - A description of what you are seeing — including any error messages and the exact time the issue occurred 🔎 Schema Deployment Workflow Once schema markup has been generated, Search Atlas provides a workflow for deploying it to your connected site. If you are experiencing issues with the deployment process — such as schema not appearing to deploy correctly or the workflow behaving unexpectedly — please contact support so the team can review your specific setup. When reaching out about deployment, please have the following ready: - The project name and the page URL(s) affected - A description of the behavior you are seeing and when it started - Any error messages shown, with timestamps if possible 🔗 Webflow CMS Sync For users on Webflow, Search Atlas offers CMS sync capabilities that connect your Webflow CMS with the platform. If you need help setting up or troubleshooting the Webflow CMS sync integration, our support team can walk you through the process based on your account configuration. When reaching out about Webflow CMS sync, please have the following ready: - Your Webflow site URL and the project name in Search Atlas - A description of what is not working as expected - Any error messages and the time they 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.

🧩 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.

🔄 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.

🔍 Find and Deploy Your OTTO Grader Undeployed Fixes

🤔 Why Does This Happen? You may notice a mismatch in your OTTO Grader dashboard: the summary shows a number of undeployed fixes, but when you look at each category individually, every category displays zero remaining fixes. This is a known display behaviour, not a data error. 🔎 Steps to Locate and Deploy Your Pending Fixes Follow these steps to find and act on your undeployed fixes in the Grader dashboard: 1. Open your OTTO Grader dashboard and note the total undeployed fix count shown in the summary section. 2. Check all available category sections — review every category listed in your dashboard rather than relying only on the default view, as fixes may not appear prominently in the initial summary. 3. Try a full page refresh — occasionally the summary count and category counts fall out of sync due to a display lag. Refreshing the page can resync the totals. 4. If fixes become visible, select and deploy them from within the relevant category. 📋 What to Have Ready If You Need to Escalate If the steps above do not surface the missing fixes, our support team can investigate the discrepancy at the account level. Before reaching out, please have the following ready: - Your project name — the specific project where the mismatch is appearing. - The undeployed fix count shown in your summary. - A screenshot or description of what your Grader dashboard currently displays, including which categories show zero. - Any actions you have already taken — for example, if you recently deployed a batch of fixes or made 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.

🛠️ 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.

🛠️ 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.

🛠️ Understanding OTTO Grader Undeployed Fixes Count

🔍 Overview You may notice that your OTTO Grader displays a total count of undeployed fixes — for example, 344 fixes not deployed — while every individual category shows 0 issues remaining. This can be confusing, but it is a known display behaviour that has a straightforward explanation. 💡 Why This Happens The total undeployed fix count shown on the OTTO Grader summary reflects a cumulative historical snapshot of all fixes that were identified across your site at the time OTTO last ran a full audit. This number does not always update in real time when you resolve issues category by category. There are two common reasons for the mismatch: - Fixes were resolved outside OTTO: Some issues may have been corrected manually in your CMS or by another tool. OTTO tracks that a fix was recommended but cannot automatically confirm it was applied externally, so the count persists until a new full scan is completed. - Pending scan refresh: OTTO updates category-level counts more frequently than the top-level summary. If you recently deployed fixes, the summary total may lag behind the individual category totals until the next full grader sync. 📊 How to View the 344 Undeployed Fixes To investigate which specific fixes make up the undeployed count, follow these steps: 1. In the left sidebar, click OTTO SEO, then open SEO Automation to go to the OTTO dashboard (/seo-automation-v3). 2. Open the OTTO Grader for the relevant site. 3. Review each fix category listed in the grader. Even if a category shows 0 deployable fixes, expand it to check for items marked as Ignored, Skipped, or Not Applicable — these still count toward the undeployed total. 4. Look for a Filters or Status dropdown within each category and set it to show All statuses, not just active ones. This reveals fixes that were dismissed or excluded rather than deployed. 5. Check the Ignored Fixes section if available. Any fix you or a team member previously ignored is excluded from the deployable queue but still included in the undeployed summary count. ⚙️ How to Reconcile the Count Once you have identified where the undeployed fixes are sitting, you have two options to bring the summary count to zero: - Deploy the fixes: If any ignored or skipped fixes are still valid improvements, update their status to active and deploy them through OTTO. - Mark fixes as Ignored or Not Applicable: If certain fixes do not apply to your site (for example, recommendations for page types you do not use), explicitly mark them so OTTO can exclude them cleanly from the count. After taking either action, trigger a manual rescan by navigating to OTTO SEO → Overview (OTTO Grader) to recalculate the summary total against the current state of all categories. 🚀 Best Practices to Keep Your Count Accurate - Run a full OTTO Grader rescan after making bulk changes to your site, whether through OTTO or manually in your CMS. - Regularly review the Ignored fixes list to ensure nothing important has been accidentally dismissed. - Address fixes category by category and rescan between sessions so the summary total stays in sync. - Avoid making large structural site changes (URL changes, template updates) without triggering a rescan immediately after, as stale fix recommendations can inflate the undeployed count. 🙋 Still Need Help? If you have followed the steps above and your undeployed fix count still does not reflect the correct number, or you cannot locate where the 344 fixes are categorised, our team is happy to 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.

🛠️ 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.

↩️ 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.

🔍 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.

🛠️ 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.

🔄 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.

Choosing Your Website Platform for OTTO SEO Deployment

Overview Search Atlas integrates with three website platforms: GoHighLevel (GHL), WordPress, and Search Atlas Website Studio. Each works differently with OTTO SEO, and the right choice depends on your priorities around vendor independence, management simplicity, and how SEO improvements are applied. This article explains the key differences so you can make an informed decision. How OTTO SEO Deploys Changes OTTO SEO can apply optimizations in different ways depending on the platform you use. The method of deployment affects how changes are stored and what happens if your Search Atlas connection or subscription changes. Understanding this distinction is an important factor when evaluating which platform fits your needs. WordPress: Plugin-Based OTTO Deployment WordPress with the Search Atlas WordPress plugin is a strong choice if you want a direct integration between OTTO SEO and your website's content management system. How it works: After installing the Search Atlas plugin on your WordPress site and connecting it to your Search Atlas account, OTTO can push SEO optimizations — such as meta titles and descriptions, schema markup, canonical tags, and image alt text — through the plugin to your WordPress site. Key benefits: - WordPress is open-source and self-hostable, giving you significant control over your hosting environment. - The plugin provides a direct connection between Search Atlas and your site's CMS. - You retain ownership and portability of your website and its content. Management considerations: WordPress requires you to manage hosting, plugin updates, and site security independently. This adds some operational overhead compared to fully hosted options, but gives you flexibility and control. Website Studio: All-in-One Simplicity Search Atlas Website Studio is a fully hosted website builder built directly into the Search Atlas platform, offering a streamlined experience for users who want everything managed in one place. How it works: Because Website Studio is part of the Search Atlas ecosystem, OTTO SEO and your website are managed within the same platform. This eliminates the need to configure a separate CMS or install additional plugins. Key benefits: - Everything — your website, SEO management, and OTTO deployment — is handled within a single platform. - No separate hosting setup or plugin management is required. - Ideal for users who want a simplified, unified workflow. Management considerations: Because Website Studio is hosted within Search Atlas, your site is tied to your Search Atlas subscription. This is a trade-off to consider if vendor independence is a priority for you. GoHighLevel (GHL): Integration via Search Atlas GoHighLevel can be connected to Search Atlas, allowing OTTO SEO to work alongside your GHL-hosted websites. How it works: Search Atlas connects to your GoHighLevel account to enable SEO management through the Search Atlas platform. This allows you to use OTTO SEO features for sites hosted in GHL. Key benefits: - Suitable for agencies or users already using GoHighLevel as their primary platform. - Allows you to manage SEO through Search Atlas without migrating your existing GHL sites. Management considerations: Because GHL is a third-party platform, the behavior of the integration depends on how Search Atlas and GHL communicate. Contact the Search Atlas team for the most current details on what is supported for your specific GHL setup. Choosing the Right Platform When deciding which platform to use with OTTO SEO, consider the following: - If you want a self-hosted, open-source environment: WordPress with the Search Atlas plugin offers the most independence. - If you want a single, all-in-one platform: Website Studio keeps everything within Search Atlas. - If you are already using GoHighLevel: The Search Atlas integration allows you to use OTTO SEO without moving to a new CMS. If you need further assistance, open 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.

🛠️ 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.

🛠️ 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 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.

✏️ 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.

🔍 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 Unwanted Schema Markup Deploying on Your Site

🔍 Why Schema Markup May Still Appear After Undeploying OTTO If you have undeployed all OTTO schema recommendations but schema markup is still being served on your website, the markup is likely coming from a source outside of OTTO's controls. Common sources include your WordPress theme or plugins and Custom HTML tags inside a Google Tag Manager (GTM) container. Both sources operate independently of OTTO's deploy/undeploy controls, so undeploying OTTO alone will not remove them. 📋 Source 1 — WordPress Theme or Plugin Injecting Schema Many WordPress themes and SEO plugins (such as Yoast SEO, Rank Math, or All in One SEO) output schema markup automatically. This markup will continue to appear on your site regardless of what you do inside Search Atlas. 1. View the source code of an affected page in your browser and search for <script type="application/ld+json"> to locate schema blocks. 2. Identify which plugin or theme is responsible — the surrounding code comments or script attributes often indicate the source. 3. Log in to your WordPress admin dashboard. 4. If a plugin is the source, navigate to that plugin's settings and look for a schema or structured data section where output can be disabled. 5. If your theme is the source, check your theme's settings or consult your theme documentation for how to disable built-in schema output. 6. Save your changes, then re-check the page source to confirm the schema blocks have been removed. In some cases schema output is hardcoded into a theme's template files. If no settings toggle is available, you may need to edit the theme files directly or use a child theme to override the output — or contact your theme developer for guidance. ⚙️ Source 2 — Google Tag Manager Container Injecting Schema A GTM container can inject schema markup site-wide through Custom HTML tags, entirely outside of Search Atlas. If your site uses GTM, your container may contain one or more Custom HTML tags that output schema JSON-LD or other structured data. 1. Log in to your Google Tag Manager account at tagmanager.google.com. 2. Open the container associated with your website. 3. Navigate to Tags and filter or scan for any tags of the type Custom HTML. 4. Open each Custom HTML tag and review its contents for schema markup (look for <script type="application/ld+json"> blocks). 5. For each tag containing unwanted schema, either pause or delete the tag depending on whether you may need it later. 6. Publish a new version of your GTM container to push the changes live. After publishing, allow a few minutes for the changes to propagate, then re-check your pages using a structured data testing tool to confirm the schema is no longer being served. ✅ How to Confirm the Schema Has Been Removed After completing the steps above, verify that no unwanted schema remains on your pages by using a structured data testing tool such as Google's Rich Results Test or Schema Markup Validator. If schema markup continues to appear and you cannot identify the source, please reach out to our support team via the chat icon in your Search Atlas dashboard and we will help you track it down.

🏷️ OTTO Page-Level Schema Bulk Deployment via GTM

Overview Some users encounter issues when deploying page-level schemas through OTTO using Google Tag Manager (GTM). Because the specific resolution for this issue requires investigation of your account and GTM configuration, the Search Atlas support team will need to assist you directly. Common Symptoms - Only a fraction of your selected schemas (for example, 5 out of 800 pages) show as deployed after a bulk deploy action. - Checkboxes for individual schema selection or bulk-deploy options are not visible on the page. - The main-entity fields display as blank or show a null value and you are unsure what to enter. What to Have Ready Before Contacting Support To help the support team investigate and resolve your issue as quickly as possible, please gather the following information before reaching out: - Your project name in Search Atlas. - The exact number of pages you attempted to deploy schemas to and how many actually show as deployed. - A description of the symptom you are experiencing (for example, missing checkboxes, blank main-entity fields, or incomplete bulk deployment). - Your GTM container ID and whether your GTM container has been published after OTTO pushed the schema tags. - Screenshots or screen recordings showing the issue, including any error messages displayed in the UI. - The timestamp of when you attempted the bulk deploy action. - The browser and browser version you are using. Next Steps If you are experiencing issues with OTTO page-level schema bulk deployment via GTM, please contact us via the chat icon in the bottom-right corner of Search Atlas and we will be happy to investigate and resolve the issue on your behalf.