Schema & Structured Data

🔍 Access and Interpret Schema Markup Suggestions

🗺️ What Is the Schema Markup Feature? Schema markup is structured data that helps search engines understand your page content. Search Atlas scans your site and surfaces schema-related suggestions so you can improve how your pages appear in search results. The suggestion count you see reflects the total number of schema opportunities identified across your site. 📍 How to Navigate to Schema Markup 1. Log in to your Search Atlas account. 2. In the header, click the apps grid (More Features). 3. Select Schema Creator to open the Schema Markup section. 4. Click the schema count or the associated link to open the full schema view. 🔢 Understanding the Suggestion Count The number displayed next to Schema Markup means Search Atlas has identified that many individual schema markup opportunities across your site. Each suggestion corresponds to a specific URL or page element where schema could be added, improved, or corrected. - High counts are common on large sites and simply reflect the number of pages or elements flagged — not the severity of any single issue. - The number does not reset automatically — it updates after a new site crawl is completed. - You can page through suggestions using the navigation controls to review each one individually. 👁️ Viewing Detailed Schema Information After clicking into a schema suggestion, you can explore the available details for each flagged URL. The information shown will depend on what Search Atlas detected during the crawl for that page. If the detail view appears limited, the steps below may help: 1. Click directly on the URL or page name listed in the schema suggestion row to open the full per-page view. 2. Review any schema-related data displayed for that page, including what structured data types have been detected and what may be missing or incomplete. 3. If a page shows no detected schema, this means no structured data has been implemented on that page — the suggestion itself is the prompt to add schema. ⚠️ Why Schema Details May Appear Limited There are a few reasons the detail view might seem sparse when you first click into a suggestion: - The page has no existing schema: If a page has not implemented any structured data, the detected schema section will be empty. The suggestion itself is the prompt to add schema — not a reflection of existing code. - The crawl is still processing: If you recently added your site or triggered a new crawl, full schema data may not be populated yet. Wait for the crawl to complete and refresh the page. - Filters are applied: Check whether any active filters are narrowing your view and clear them if needed to see all suggestions. 🛠️ What to Do If You Cannot Find Schema Suggestions If you are having trouble locating or interpreting your schema markup suggestions, try the following steps: 1. Confirm your site has completed at least one full crawl in Search Atlas. 2. Navigate back to the Schema Markup section via the header apps grid (More Features) → Schema Creator, and verify no filters are limiting the results. 3. Refresh the page after a crawl completes to ensure the latest data is displayed. If you need further assistance, open 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.

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

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

⚡ Semantic HTML for SEO: Elements, Accessibility & Structured Data

What Is Semantic HTML? Semantic HTML uses elements that describe the meaning of their content, not just its visual appearance. Instead of relying on generic containers like div and span, semantic markup uses tags whose names communicate their role on the page. This helps browsers, assistive technologies, and search engine crawlers understand how content is structured and what each piece means. HTML5 introduced a set of semantic elements that define common page regions and content types. Key examples include: - header — groups introductory or navigational content at the top of a page or section - nav — identifies primary navigation links - main — wraps the primary content of a page - article — marks up independent, self-contained content (e.g., a blog post or news item) - section — organizes related themes within a page - aside — represents content tangentially related to the main content - footer — groups closing content for a page or section - figure and figcaption — pair media (images, charts) with descriptive captions How Semantic HTML Differs from Non-Semantic HTML Non-semantic HTML forces crawlers and assistive technologies to infer meaning from class names or visual layout — signals that are unreliable and inconsistent. Semantic HTML encodes meaning directly in the markup itself. A non-semantic blog post layout might wrap everything in generic div elements labeled with class names like page, top, or content. A semantic version uses main, article, header, and section so that every region is self-describing. The difference matters because crawlers use the document outline — the hierarchy of semantic elements and headings — to identify the main topic, prioritize content, and reduce indexing ambiguity. SEO Benefits of Semantic HTML Semantic markup can improve SEO in several concrete ways: - Crawl efficiency — Labeled landmarks help crawlers navigate a page faster and focus on the content that matters most, rather than parsing undifferentiated nested containers. - Content segmentation — Tags like article and section signal topical boundaries, making it easier for search engines to identify the main subject and how supporting sections relate to it. - Snippet selection — Placing a blog title inside a clearly structured heading hierarchy sends a clearer signal about which heading is the primary title of the main topical unit. - Accessibility alignment — Semantic elements provide built-in landmark roles that assistive technologies rely on, and accessibility signals increasingly factor into search quality assessments. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🚀 The Revolution of Data Markup: Page-Specific Schema and the End of “Schema Decay”

This article explores how AI has transformed structured data implementation from static templates to deep contextual understanding. For years, structured data has been one of the most misunderstood, and most poorly maintained, parts of SEO. While schema markup was designed to help search engines understand content, the way it has traditionally been implemented has created a long-term problem: schema decay. Search Atlas introduces a fundamentally different approach: AI-driven, page-specific schema, built from real contextual analysis instead of static templates. 🧩 Why “Schema Decay” Happens Historically, schema implementation has been treated as a one-time setup task. Developers hard-code markup into templates or individual pages, deploy it, and then move on. The problem is that websites are not static. Over time: - Prices change - Services evolve - Reviews accumulate - Content gets updated But the schema often stays exactly the same. As a result, the structured data no longer reflects the reality of the page. This mismatch between visible content and structured data is what we refer to as schema decay. It creates ambiguity for search engines and undermines the very purpose of schema in the first place. Manual maintenance doesn’t scale, and most teams simply don’t have the time, or the visibility, to keep schema perfectly synchronized across thousands of pages. 🤖 How Search Atlas Solves Schema Decay with AI Search Atlas approaches schema as a dynamic representation of page understanding, not a static block of code. Instead of relying on templates, the platform uses AI to analyze each individual page and extract its full context, including: - Entities - Page intent - Content structure - Business attributes - Relationships between data points This analysis is performed at the page level, which allows Search Atlas to generate schema that is specific, accurate, and aligned with what actually exists on that URL. The system supports over 1,000 schema types, including more than 200 niche local business subtypes, spanning industries from healthcare and legal services to aviation and specialized professional services. This level of granularity makes it possible to represent businesses and content far more accurately than generic schema templates ever could. 🧠 From Static Markup to Pre-Computed Understanding Schema, in this model, is not just markup, it’s a pre-computed understanding of the page. Search Atlas builds this understanding by analyzing the page content, mapping it to the correct schema types, filling required and recommended fields using contextual signals, and validating the structure before deployment. Inside the platform, users can review the generated schema, audit it, and make adjustments when needed. This creates transparency and control without reintroducing the maintenance burden that causes schema decay in the first place. ⏱️ Why Manual Schema Management Doesn’t Scale The operational cost of manual schema becomes clear at scale. On a site with approximately 5,000 pages, deploying 8 to 10 unique schema types per page would require an estimated 2,000 to 4,000 hours of work, the equivalent of one to two full-time employees for an entire year. And that effort doesn’t even account for ongoing updates as content changes. Search Atlas automates this entire process. What would normally take months of manual work can be analyzed, generated, and deployed in seconds, with consistency across the entire site. 📊 Real-World Impact: What the Data Shows Search Atlas conducted an impact analysis across 22,000 connected sites to measure the effect of AI-driven, page-specific schema fixes. The results showed a strong correlation between proper schema implementation and significant organic visibility gains, including an average 110% increase in total ranking keywords, noticeable improvements in impressions, and increased click activity across indexed pages. While schema alone is not a ranking factor, these results highlight its role as a visibility amplifier when search engines can accurately interpret page content. 🔍 Supporting Infrastructure: Real-Time Crawl Logs To support this system, Search Atlas also provides real-time crawl logs, allowing users to see how search engines are interacting with their pages as crawls happen. This visibility helps teams identify crawl issues immediately, confirm that schema-enhanced pages are being accessed correctly, and validate status codes and crawl behavior at scale. Together, page-specific schema and crawl visibility form a closed feedback loop between understanding, execution, and verification. 🚀 Bulk Deployment Without the Risk Even with this level of precision, Search Atlas is built for scale. Users can review schema suggestions in bulk, select multiple pages at once, and deploy schema across hundreds of URLs with a single action. When schema suggestions are generated using AI, the system clearly indicates AI credit usage, keeping execution transparent and predictable. 🏁 The End of Schema Decay Schema decay is not a tooling problem, it’s a methodology problem. By replacing static templates with AI-driven, page-level analysis, Search Atlas transforms structured data into a living system that evolves alongside your site. The result is schema that stays accurate, relevant, and aligned with real content, without the operational overhead that has historically made schema such a fragile part of SEO. This is what schema was always meant to be: a faithful representation of meaning, not a forgotten block of 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.

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

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

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

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

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

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

🔍 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, OTTO does support URL exclusion configuration so it can be instructed to skip specific URL patterns during a crawl. Because the exact steps for configuring crawl exclusions depend on your account setup and the version of OTTO you are using, we recommend reaching out to our team directly so they can walk you through the correct settings for your project. When you contact us, please have the following ready: - Your project name and the site domain being crawled. - The specific URL pattern causing duplicate suggestions (for example, /blog vs /blog/). - Whether you have already attempted a server-side redirect and what result 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.

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

🔄 Sync Google Local Business Info to Schema Markup

Overview When you enter Google Local Business information in Search Atlas, the platform is designed to push that data into your site's Local Business schema markup automatically. If the sync is not working, the issue typically involves a missing setup step, an inactive OTTO SEO connection, or incomplete business information. This article explains what the sync is intended to do and how to get help resolving it when it is not working as expected. What This Feature Is Meant to Do Search Atlas is designed to read your business details — such as business name, address, phone number, hours, and categories — from your connected Google Business Profile (GBP) and use that data to populate Local Business schema markup on your site via OTTO SEO. When the sync is working correctly, no manual copy-paste into your site's backend is required. What to Check Before Escalating If your Local Business data is not appearing in your schema markup, review the following before contacting support: - Your GBP account is connected in Search Atlas: Confirm your Google Business Profile account is linked within the platform. If it is not connected, the sync cannot run. - A GBP project exists for the correct location: Each business location typically needs its own project. Open the project and verify that business details — name, address, phone, hours, and category — are fully populated and accurate. - OTTO SEO is active on your site: OTTO must be enabled for schema deployment to occur. Confirm OTTO is active for the site in question. - A page is assigned to receive the Local Business schema: OTTO needs a target page (such as your homepage or a location page) designated for Local Business schema. If no page is assigned, the schema will not deploy. - All required business fields are completed: Missing fields such as phone number, address, or business category can prevent schema from being generated or deployed correctly. What to Have Ready When You Contact Support Because Local Business schema sync issues often require a Support team member to investigate your specific project configuration, please have the following information ready when you reach out: - The name of the GBP project or business location affected - The URL of the page where Local Business schema should appear - A description of what you see versus what you expect (for example, schema missing entirely, or schema present but showing incorrect data) - Any error messages or unexpected behaviors you have noticed in the platform If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Why OTTO Schema Isn't Showing in External Validators

🎯 Overview A common question we hear is: my OTTO plugin shows as connected and the schema shows as deployed, so why isn't it appearing in Google Rich Results Test, schema validators, or search results? This article walks through the most frequent causes and how to resolve them so your structured data is served and recognized correctly. ⏱️ Give It Time to Crawl and Cache OTTO deploying schema is not the same as Google indexing it. Even when a validator can read the markup instantly, search results and rich results require Google to re-crawl the page. Keep these timelines in mind: - Validators (Rich Results Test, Schema.org validator): Should reflect changes within minutes to a few hours after deployment. - Google Search rich results: Can take days to weeks after Google re-crawls the page. - CDN or caching plugins: May serve a cached version of the page without the injected schema until the cache clears. If a validator does not show your schema after a few hours, continue with the checks below. ✅ Confirm the Page Is Crawlable OTTO schema will not be recognized if the target URL cannot be crawled by search engines. We previously fixed an issue where schema was being deployed on pages that were not crawled. Verify the following for the exact URL you are testing: - The page returns a 200 status (not a redirect, 404, or 500). - The URL is not blocked in robots.txt. - The page does not carry a noindex meta tag or header. - You are validating the exact same URL that OTTO deployed to — including trailing slashes, http vs https, and www vs non-www variations. 🔗 Test the Correct URL Variation Schema is deployed on a specific URL. If your site redirects between www and non-www, or between http and https, validators may test a version of the page that OTTO did not inject into. Always run the validator against the canonical, final URL that resolves in your browser after any redirects. ⚠️ Check for Validation Errors and Warnings OTTO validates schema before deployment. In some cases schema may deploy with warnings, and certain errors can prevent Google from recognizing it as valid structured data. Watch for these known issues: - @context must use HTTPS: If the schema context reads http:// instead of https://, validators may reject it. Ensure your context is set to the secure schema.org URL. Note that this error can also appear in nested schema properties and may not always be caught before deployment — if validators flag an @context HTTPS error even after re-deploying, inspect all nested schema objects for http:// references. - Bypassed validation warnings: OTTO allows you to bypass validation and deploy anyway with a warning. If you used this option, the deployed schema may contain errors that external validators flag. If you bypassed a validation warning during deployment, re-review the schema and correct the underlying issue before re-deploying. 🧹 Rule Out Duplicate or Stale Schema If schema continues to appear even after you remove an OTTO deployment — or the wrong schema shows up — another source may be serving structured data on the same page. Common sources include: - A separate SEO or schema plugin injecting its own markup. - Your WordPress theme adding built-in schema. - A previously cached version of the page still being served. Conflicting or duplicate schema can cause validators to display unexpected results. Disable other schema sources temporarily to isolate what OTTO is serving. Note for WordPress users: A known issue exists where schemas continue to be served on a page even after the OTTO schema deployment has been removed. If you are seeing schema in validators that you have already deleted in OTTO, check whether another plugin or theme is the source, and also clear all caches before concluding OTTO is still injecting it. This issue has been addressed in a recent release (WP-541). 🔄 Re-Deploy and Clear Caches Once you have confirmed the page is crawlable and free of validation errors, refresh your deployment: 1. Confirm the OTTO plugin still shows as connected. 2. Re-deploy the schema to the target URL. 3. Clear your WordPress cache and any CDN cache. 4. Load the live page and view the source to confirm the JSON-LD markup is present. 5. Run the URL through the Rich Results Test and a schema validator again. If the markup is present in the page source but a validator still does not detect it, the issue is almost always a caching layer or a URL mismatch — recheck those first. 💬 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.

🧩 Schema Markup

Some webmasters feel intimidated when working on the backend of their websites. However, the metadata you include on a page, and how it’s formatted, can have a meaningful impact on SEO performance. One of the most powerful types of SEO-friendly metadata is schema.org markup. Schema markup is a form of structured data that helps search engines better understand your web pages. It also improves how your pages appear in search results, increasing both visibility and click-through rates. The good news is that anyone can add schema markup, you don’t need to be a developer to get started. This guide explains what schema markup is, why it matters for SEO, and how to create and manage it effectively. 🔍 What Is Schema Markup? In simple terms, schema markup is a semantic vocabulary added to your website’s code to help search engines generate more informative and relevant search results. - On the backend, schema.org markup is implemented as structured data within your HTML. - On the frontend, that markup can generate rich results in Google, enhanced search listings that show more context than a standard snippet. A standard search result usually includes: - Page title - URL - Meta description A rich result, enabled by schema markup, can additionally show: - Business hours - Star ratings - Event details - Product or recipe information Schema markup is what allows search engines to surface this additional data. To standardize how structured data is interpreted, major search engines, including Google, Yahoo!, Bing, and Yandex, collaborated to create schema.org, a shared vocabulary for describing businesses, products, reviews, jobs, and more. 📈 SEO Benefits of Schema.org Markup Despite its advantages, schema markup is still underused. Implementing it can give your site a competitive edge without changing your on-page content. 🧠 Clearer Meaning for Search Engines Schema acts as a translator, helping search engines understand what your data represents, not just the words on the page. ✨ Enhanced Search Results Rich results stand out visually and provide users with information aligned to search intent—helping them decide faster. 🖱️ Higher Click-Through Rates (CTR) More informative listings lead to better engagement. Schema helps each page communicate its purpose clearly in the SERPs. 📍 Stronger Local SEO (Especially on Mobile) On mobile devices, rich results and carousels take up more screen space. For local businesses, this can significantly increase visibility and brand presence. 🔐 A Competitive Advantage Only a minority of websites actively use schema markup, making it one of the easiest ways to stand out in crowded search results. 🧠 Common Schema Formats 🎨 Creative Works Used for media such as books, movies, games, and music, highlighting attributes like ratings, genres, and availability. 🧬 RDFa A framework embedded directly into HTML attributes to describe relationships and metadata. 🧩 Microdata Uses attributes such as itemscope, itemtype, and itemprop to define structured data elements. ⚙️ JSON-LD (Recommended) The most widely recommended format. JSON-LD is easy to implement, flexible, and can be added to the <head> or body of a page. 🧭 How to Choose the Right Schema Markup Selecting the right schema starts with understanding the purpose of each page and how it supports your broader SEO goals. A practical approach includes: 1. Identifying your core business information 2. Mapping pages to the appropriate schema.org vocabularies 3. Determining whether content is recurring or one-off 4. Connecting structured data into a coherent knowledge graph When search engines clearly understand your site’s context, relevance and visibility typically improve. 🛠️ How to Use a Schema Markup Generator Schema generators simplify implementation by producing ready-to-use JSON-LD code—no manual coding required. 📍 Where to Find the Schema Creator in Search Atlas To access the Schema Markup Generator, follow this exact path inside the platform: ➡️ Header apps-grid icon (More Features) ➡️ Schema Creator 💡 The apps-grid icon in the header opens the More Features menu. 🧩 Typical Schema Creation Workflow Once inside the Schema Creator, the process is straightforward: 1. Select the appropriate schema type (e.g., Article, Local Business, FAQ Page, Product, Organization) 2. Fill out the structured fields (headline, URL, images, author, publisher, dates, etc.) 3. Review the auto-generated JSON-LD preview on the right panel 4. Click Copy Markup 5. Paste the JSON-LD code into the <head> section of your webpage ✅ Validate Your Schema Markup After publishing, validate your structured data using: - Google Rich Results Test - SEMrush Site Audit - Google Content Markup Guide - Schema.org official documentation ✨ Why This Matters Using the Schema Creator ensures: - Clean, error-free JSON-LD - Faster implementation without developers - Better eligibility for rich results - Consistent structured data aligned with Google standards This tool removes friction from technical SEO and makes structured data accessible to every team. 🚀 Schema Management & Suggestions in Search Atlas Search Atlas includes built-in tools to help users review, update, and improve schema markup without working directly in code. To access schema recommendations and management inside Search Atlas, follow this path: From the Left Sidebar: ➡️ OTTO SEO ➡️ All Sites ➡️ Select your project ➡️ Overview ➡️ Onpage Optimizations (OTTO Grader) ➡️ Click Schema Markup This opens the Schema Markup recommendations view, where you can review existing schema, see suggestions, fix missing values, and regenerate schema when needed. 👁️ Organization-Level Schema Preview & Editing At the top of the Schema Markup section, you’ll see the Organization-level schema for your project. From this area, you can: - Click Preview to see how the Organization schema will appear - Edit schema fields directly inline - Update values without navigating to the Knowledge Graph - Save changes when ready 💡 Note: The Knowledge Graph is still available for advanced edits, but previewing and updating Organization-level schema no longer requires leaving this view. 🧠 Schema Suggestions for Individual Pages Below the Organization schema, you’ll find a list of pages with schema recommendations. For each page: - The page URL is listed - A schema suggestion is available when applicable To review a suggestion: 1. Click Reveal Schema 2. Review the suggested structured data 3. Choose one of the following actions: - Edit the fields manually - Click Regenerate Schema to generate a fresh version based on the latest page content This is especially useful after updating page copy or metadata. ⚠️ Fix Indicators for Missing Required Fields For Auto Projects: - Schema recommendations appear automatically - Users can click Generate or Regenerate to apply schema - No manual setup is required This keeps schema aligned with content updates over time. 🚫 Current Limitation At this time: - Users cannot manually create brand-new schema types - Schema management is limited to: - Organization-level schema - System-generated schema recommendations - Editing, fixing, or regenerating existing schema Manual schema creation will be added in a future update. 📦 Auto Projects & One-Click Generation For auto-generated projects: - Schema suggestions appear automatically - Values can be generated with a single click - No manual setup is required This makes schema optimization easier to maintain over time. Schema markup remains one of the most underutilized yet impactful SEO tools available. With previews, suggestions, and validation built directly into Search Atlas, structured data no longer requires technical expertise to manage. By applying schema consistently, you can improve search visibility, click-through rates, and long-term SEO performance—making structured data a foundational part of your optimization strategy.

🖼️ Schema Markup for AI-Generated Images in Search Atlas

🧭 Overview This article covers two topics that customers have asked about: adding schema markup to AI-generated images, and configuring or reconnecting a Google Business Profile (GBP) for a local project in Search Atlas. Because the exact steps depend on your specific project setup, this article explains what to prepare so our team can assist you quickly. 🤖 Schema Markup for AI-Generated Images Search Atlas supports structured data implementation as part of its on-page and technical SEO toolset. Customers have asked about adding ImageObject schema to AI-generated images — for example, how to attribute the image correctly using fields such as creditText, copyrightNotice, and creator. Because the exact workflow for adding or editing schema markup within Search Atlas varies by project type and feature access, our support team can walk you through the correct steps for your account. When you reach out, please have the following ready: - The name of the project and the specific page(s) you want to add ImageObject schema to. - Whether you are working with a manually created schema block or an existing structured data tool inside the platform. - Any error message or validation result you have received (for example, from Google's Rich Results Test). 🔗 GBP Configuration for a Local Project Customers have also asked about connecting or reconfiguring a Google Business Profile within a local project in Search Atlas. Common scenarios include a GBP that is not loading, a disconnected profile, or questions about how to associate the correct business listing with a project. Because GBP connection steps depend on your account permissions and project configuration, our support team can guide you through the correct process. When you reach out, please have the following ready: - The name of the local project in Search Atlas. - The Google account email associated with the GBP listing. - A description of what you are seeing — for example, whether the profile appears disconnected, shows an error, or is simply not displaying data. - Your current access level on the GBP listing in Google Business Profile Manager (Owner or Manager). If you need further assistance, open 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 Review Stars Schema With Schema Creator

⭐ What Are Review Stars in Schema Markup? Review stars (also called star ratings) appear directly in Google search results beneath your page title. They are powered by structured data markup — specifically, Review or AggregateRating schema — that tells search engines about ratings associated with your content, product, or business. Adding this markup correctly can improve your click-through rate by making your listing stand out on the results page. 🗺️ Where to Find Schema Creator Schema Creator is a tool available within Search Atlas that allows you to build structured data for your pages without writing code manually. To locate Schema Creator, log in to your Search Atlas account and explore the available tools in your dashboard. If you are unsure where to find it, our support team can point you to the exact location for your account. 🛠️ How to Add Review Stars Schema Once you have located Schema Creator, you can use it to create a structured data block for review stars. The two main schema types relevant to star ratings are: - AggregateRating — used for an overall rating based on multiple reviews. This is the most common type for displaying star ratings in search results. - Review — used for a single individual review. To add review stars schema, open Schema Creator and select the appropriate schema type for your page. Fill in the relevant rating details as prompted by the tool, then copy the generated JSON-LD code and add it to the <head> section of your page's HTML, or via your CMS's schema or header script field. If you are not sure which schema type to choose or how to complete a particular field, contact our support team for guidance specific to your use case. ✅ Tips for Valid Review Stars Schema - Nest AggregateRating inside a parent schema — Google requires the rating to be attached to an entity such as Product, LocalBusiness, or Recipe. - Use real, accurate rating data — Google may penalise pages that display inflated or fabricated ratings. - Test your markup — after adding the schema to your page, use Google's Rich Results Test (search.google.com/test/rich-results) to confirm the structured data is valid and eligible for rich result display. - Keep ratings current — if your review count or score changes, update your schema accordingly to maintain 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.

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

🗂️ Manage Top Pages in Your Knowledge Graph

Overview The Knowledge Graph in Search Atlas includes a Top Pages section that displays the most prominent pages associated with your website. You may want to manage which pages appear in this section to keep your Knowledge Graph relevant and clutter-free. This article explains what to do if you want a page removed from the Top Pages section. How to Request Removal of a Page from the Top Pages Section At this time, there is no confirmed self-serve button or in-product option to hide or delete individual pages directly from the Top Pages section of the Knowledge Graph. If you want a specific page removed from this view, the recommended path is to contact our support team so they can assist without requiring you to delete anything from your live website. Important: Do not delete a page from your CMS solely to remove it from the Knowledge Graph Top Pages view. Deleting a live page affects your website and its SEO, and it may not be necessary to achieve the Knowledge Graph result you want. What to Have Ready When You Contact Us To help our team resolve this as quickly as possible, please have the following information ready before reaching out: - The exact URL of the page you want removed from the Top Pages section. - Your project or domain name in Search Atlas. - Whether you want the page hidden from the Knowledge Graph view only, or whether you also want it excluded from future crawls. - Any steps you have already tried and the result you observed. Common Confusion: Knowledge Graph vs. Crawler Exclusions Managing pages in the Top Pages section of the Knowledge Graph is not the same as excluding URLs from your site crawl. - Knowledge Graph Top Pages management — controls which pages are displayed inside the Knowledge Graph feature. This is a content curation action. - Crawler exclusions — controls which URLs Search Atlas crawls when scanning your domain. Excluding a URL from the crawl prevents it from being indexed by Search Atlas, but it is a separate setting from the Knowledge Graph Top Pages view. If you are trying to prevent a URL from being crawled entirely, look for crawler or exclusion settings within Search Atlas rather than managing it through the Knowledge Graph interface. If you need further assistance, open 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 Page-Specific Schema Markup in Authority

🔍 What Is Page-Specific Schema Markup? Schema markup is structured data that helps search engines understand what your page is about. Instead of applying one generic schema to your entire site, page-specific schema lets you assign the right schema type to each individual page — for example, Service schema on a locksmith service page, FAQPage schema on a frequently asked questions page, or LocalBusiness schema on a location page. Adding the correct schema to each page improves how your content appears in search results and strengthens your site's relevance signals. 🗂️ Supported Schema Types Search Atlas supports a wide range of schema types for page-specific markup, including: - Service — ideal for individual service pages (e.g., locksmith, plumbing, legal services) - FAQPage — for pages that list questions and answers - LocalBusiness — for location or contact pages targeting a specific area - Organization — for about or homepage-level business identity - Article / BlogPosting — for blog and editorial content - Product — for e-commerce or service product pages - BreadcrumbList — for navigation hierarchy signals 🛠️ How to Add Schema Markup to a Specific Page Follow these steps to assign schema markup to an individual page using OTTO SEO inside Search Atlas: 1. Log in to your Search Atlas account and navigate to your site's OTTO SEO dashboard. 2. In the OTTO interface, locate the Schema section or the list of pages OTTO has processed for your site. 3. Find the specific page you want to update — for example, your locksmith service page, FAQ page, or a location page. Use the search or filter options to narrow down the list quickly. 4. Click on the page to open its individual settings panel. 5. Look for the Page Type or Schema Type selector. Use this dropdown to choose the schema type that best matches the page's content (e.g., Service, FAQPage, LocalBusiness). 6. Fill in any required fields that appear for the selected schema type. For example, Service schema may ask for a service name and description; LocalBusiness may require an address and phone number. 7. Once all fields are complete, click Save or Apply to confirm your changes. 8. OTTO will process and deploy the updated schema markup to the selected page automatically. 💡 Best Practices for Schema Assignment Keep these tips in mind to get the most out of page-specific schema markup: - Match schema to page intent. Only use schema types that accurately reflect the page's primary content. Mismatched schema can confuse search engines rather than help them. - Use FAQPage schema only when the page has real Q&A content. Each question and answer pair should be visible to users on the page, not hidden in the code alone. - Apply LocalBusiness schema to every location page if you serve multiple areas. Each page should have unique address and geo-coordinate data for that specific location. - Avoid stacking incompatible schema types on a single page unless they are logically nested (e.g., a LocalBusiness that also contains a Service). - Validate your schema after deployment using Google's Rich Results Test (search.google.com/test/rich-results) to confirm there are no errors or missing fields. ❓ Frequently Asked Questions Can I add schema to pages that OTTO has not yet processed? Yes. You can manually select a page within OTTO and assign a schema type even if OTTO has not automatically processed it yet. OTTO will include your manual selection when it next processes that page. What if the schema type I need is not in the dropdown? Search Atlas regularly expands its supported schema library. If you do not see the schema type you need, the live chat team can advise on the best available alternative or log a feature request on your behalf. Will adding schema markup affect my page's existing content or design? No. Schema markup is added as structured data in the background and does not change how your page looks or reads to visitors. How long does it take for schema changes to be reflected in search results? After OTTO deploys the schema, Google typically processes and reflects changes within a few days to a few weeks, 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.

⚠️ The Dangers of SEO Split Testing: Cloaking & Canonical Tag Risks

What Is SEO Split Testing? SEO split testing, sometimes called SEO A/B testing, is the process of serving different versions of page elements to segmented groups of users or URLs in order to isolate the impact of those changes on rankings, traffic, and conversions. Unlike conversion rate optimization (CRO) testing — which typically uses client-side JavaScript that modifies the page after it loads — SEO split testing requires that search engines actually crawl and index the test variants. This distinction is what makes SEO testing uniquely risky if implemented incorrectly. Why Responsible SEO Testing Matters Stakeholders increasingly demand measurable proof that SEO changes produce results. Split testing offers that proof by isolating variables and measuring their effect. However, improper implementation can result in penalties from search engines, lost rankings, and long-term organic traffic declines. The line between legitimate experimentation and a guideline violation is narrower than most practitioners realize, and the consequences of crossing it can be severe. The Core Risks of SEO Split Testing Understanding the specific risks involved is the first step toward avoiding them. The most common dangers include: - Cloaking violations: Serving different content to search engine crawlers than to regular users - Canonical tag conflicts: Creating duplicate content signals that confuse crawlers and dilute ranking signals - Redirect misconfigurations: Implementing 301 or 302 redirects that create chains or loops - Indexation problems: Accidentally blocking test variants from being crawled, or allowing unintended variants to be indexed Cloaking Risks in SEO Testing Cloaking occurs when a website shows different content or URLs to search engines than it shows to users. Major search engines prohibit this practice because it undermines the integrity of search results. SEO tests can inadvertently become cloaking violations when: - Test logic detects a crawler's user agent and serves it a different page variant than human visitors receive - Server-side rendering (SSR) delivers different HTML to crawlers versus client-side rendered content for users - CDN or edge-side caching layers serve cached test variants inconsistently depending on whether the requestor is a bot or a human The safest approach is to ensure that any page variant shown to a search engine crawler is also accessible to human users, and that your test is genuinely intended to improve user experience rather than manipulate rankings. Canonical Tag Dangers in Split Testing Canonical tags are HTML elements that tell search engines which version of a page is the "preferred" version for indexing. During split tests, canonical tag mistakes are a frequent source of ranking problems. Common issues include: - Self-referencing canonicals on test variants: If a test variant has its own canonical tag pointing to itself rather than the original URL, search engines may index the variant as a separate page, creating duplicate content. - Missing canonicals on test pages: Test variant URLs without any canonical tag may be crawled and indexed independently, splitting ranking signals across multiple URLs. - Conflicting canonicals: When the canonical on a variant points to the original but other signals (such as internal links or sitemaps) point to the variant, crawlers receive contradictory guidance. Best practice is to ensure all test variant URLs carry a canonical tag pointing back to the original, control URL. This signals to search engines that the original page is the authoritative version and prevents ranking signal dilution. Redirect Risks During SEO Tests Redirects are sometimes used in split tests to route users to different variant URLs. However, careless redirect implementation introduces its own risks: - Using permanent (301) redirects for temporary tests can cause search engines to transfer ranking signals away from the original URL, making it difficult to restore rankings after the test ends. - Temporary (302) redirects are more appropriate for test scenarios, as they signal to search engines that the change is not permanent. - Redirect chains — where one redirect points to another — slow crawling and can cause search engines to stop following the chain entirely. Indexation Control Best Practices Keeping test variants out of the search index (unless intentional) is critical to a clean test. Recommended approaches include: - Use the noindex meta tag on test variant pages if you do not want them to appear in search results independently. - Monitor your coverage reports in Google Search Console during active tests to catch unexpected indexation of variant URLs. - Remove or consolidate test variant URLs promptly once the test concludes to avoid orphaned pages accumulating over time. Running SEO Tests Safely: Key Takeaways To conduct SEO split tests without risking penalties or ranking losses, keep these principles in mind: 1. Never serve meaningfully different content to crawlers than to users — this is the core definition of cloaking. 2. Always use canonical tags on test variant URLs pointing back to the original, control URL. 3. Use temporary (302) redirects rather than permanent (301) redirects for test routing. 4. Monitor indexation coverage throughout the test period and clean up variant URLs after the test ends. 5. Keep test durations as short as necessary to collect statistically meaningful data, and end tests cleanly. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Rank Math and OTTO SEO Schema Compatibility

🧩 Can Rank Math and Search Atlas Work Together? Yes — Rank Math and Search Atlas are compatible and can run on the same WordPress site at the same time. Search Atlas does not require you to uninstall Rank Math. However, when OTTO SEO deploys schema markup on your site, it can conflict with schema that Rank Math is also generating for the same pages. Running duplicate schema can confuse search engines and reduce the effectiveness of your structured data. The good news is that this conflict is easy to resolve by disabling Rank Math's schema output while keeping all other Rank Math features active. ⚙️ How to Prevent Schema Conflicts with OTTO SEO To avoid duplicate schema output, disable Rank Math's built-in schema module while keeping everything else active. This lets OTTO SEO take full ownership of structured data while Rank Math continues to handle meta tags, sitemaps, and other SEO features. 1. Log in to your WordPress dashboard. 2. Open the Rank Math plugin settings from the WordPress admin menu. 3. Locate the schema or structured data feature within Rank Math's module settings. 4. Disable that schema module. 5. Save your changes. Once the Rank Math schema module is disabled, OTTO SEO will be the sole source of structured data on your site. All other Rank Math features — including meta descriptions, Open Graph tags, and the sitemap — will continue to work normally. ✅ Quick Checklist: Rank Math + OTTO SEO Setup - Rank Math installed: No need to remove it — keep it active. - Rank Math schema module: Disable this to prevent duplicate structured data. - OTTO SEO schema: Enable and deploy through the 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.

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

🔄 Why OTTO Schema Doesn't Appear in Your WordPress Plugin

📐 Two Separate Systems When you deploy schema through OTTO SEO (Left sidebar → OTTO SEO → All Sites → [your project card]), the changes are delivered via a JavaScript overlay — a script that injects schema markup directly onto your live page at render time. This allows changes to go live immediately without touching your WordPress database or plugin settings. Because of this architecture, your WordPress plugin fields will never reflect changes made through OTTO. The two systems operate independently and do not communicate with each other. ⚠️ Why the Plugin Fields Look Empty - OTTO overlay: Schema is injected via JavaScript when your page loads. It is live and visible to search engine crawlers. - WordPress plugin: Stores schema in your WordPress database. It has no visibility into what OTTO's overlay is serving. ✅ How to Confirm Your Schema Is Live 1. Run your page through Google's Rich Results Test — OTTO-injected schema will appear there. 2. Use View Page Source on the live page to see the schema rendered by the overlay. 3. Check Left sidebar → OTTO SEO → All Sites → [your project card] — a green "Deployed" badge confirms the overlay is active. 📌 Avoid Schema Conflicts If your WordPress plugin is also configured to output schema for the same page types, you may end up with duplicate or conflicting markup. Disable schema output in your WordPress plugin for any page type OTTO is already managing. 💬 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.

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

🗺️ 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

🏠 OTTO Domain Schema Reverting to Old Address

Overview Some users find that after manually updating their domain-level schema in OTTO — particularly the business address — the schema reverts to an older, incorrect address after a few days. This incorrect address can even appear in the live website source code, which affects your local SEO signals. This article explains what to do if you experience this. Why This Happens This is a known platform issue where OTTO may reapply an outdated address to your domain-level schema. Because the root cause exists at the account level rather than in a setting you can directly edit, resolving it requires assistance from the support or engineering team. What You Should Do Now 1. Confirm the correct address. Before reaching out, make a note of the exact address, city, province/state, and postal/ZIP code you want to appear in your schema. Having this ready speeds up the resolution significantly. 2. Check your domain-level schema settings in OTTO. Navigate to your domain schema configuration and verify whether the address shown there matches your intended address. If it appears correct in the settings but still reverts in the deployed schema or site source code, this confirms the issue is occurring at the account level and requires escalation. 3. Attempt a manual re-save. In some cases, opening the domain schema record, re-entering the correct address fields, and explicitly saving the record again can temporarily stabilise the output. Check the site source code after 24 hours to see whether the correct address is now present. 4. Contact support if the issue persists. If the schema continues to revert after a manual re-save, reach out to the support team and provide your correct address details along with the information listed below. The team will review the address stored against your account, confirm the correct entry with you, and work with engineering as needed to ensure the right address is applied going forward. Information to Have Ready When you contact support, please have the following ready so the team can act quickly: - Your correct business address in full (street, city, province/state, postal/ZIP code, country) - The incorrect address currently appearing in your schema or site source code - The domain the schema is deployed on - Roughly when you first noticed the reversion - Whether a manual re-save was attempted and what the result was What Happens After You Report It The support team will review the address stored against your account, confirm the correct entry with you, and work with engineering as needed to ensure the right address is applied. Once resolved, OTTO will use the correct address in your domain-level schema. If you need help at any point, please reach out to our support team and we will be happy to assist.

Understanding Optional Schema Warnings in Google Rich Results Tool

When validating structured data, you may encounter warnings about missing or invalid schema fields in Google Rich Results Tool. However, not all warnings indicate problems that require action. In some cases, Google Rich Results Tool may flag optional schema properties. These warnings are informational recommendations rather than validation errors and do not necessarily indicate issues with your schema implementation. Because Google Rich Results Tool and schema.org validator serve different purposes, it is possible for a page to pass schema.org validation while still displaying optional-field warnings in Google's tools. 🔍 Why Do Different Validation Tools Show Different Results? Google Rich Results Tool and schema.org validator serve different purposes and therefore may report different results. 🧩 schema.org Validator The schema.org validator checks your structured data against the official schema.org specification. If your markup complies with schema.org requirements, the validator will consider it valid—even if certain optional properties are not present. 🔎 Google Rich Results Tool Google Rich Results Tool focuses on Google's interpretation of structured data and may highlight additional fields that Google recommends but does not require. These recommendations often appear as warnings rather than errors. As a result, it is possible for structured data to: - Pass validation in schema.org validator - Display warnings in Google Rich Results Tool - Remain fully valid and functional 🏷️ A Common Example - mainEntityOfPage The presence of these kind of warnings does not automatically indicate a problem with your schema implementation. 🔑 Key Facts - ✅ schema.org validator is the authoritative reference for schema.org compliance - ✅ Optional fields are not required for valid schema implementation - ⚠️ Google Rich Results Tool may display recommendations for optional fields - ℹ️ Not every warning represents a technical issue that needs correction - 📈 Optional-field warnings are not ranking factors by themselves - ✅ Passing schema.org validation generally indicates your structured data is implemented correctly 🛠️ What Should You Do? When validating structured data: ✅ Recommended Approach 1. Use the schema.org validator as your primary validation source: - https://validator.schema.org/ 2. Review Google Rich Results Tool warnings and recommendations. 3. Prioritize fixing: - Missing required properties - Invalid values - Syntax errors - Structured data validation errors 4. Evaluate optional-field warnings individually rather than treating them as critical issues. 🎯 Important Reminder Warnings related to optional schema properties are generally informational and should not be treated the same way as validation errors. ✅ Conclusion OTTO and Search Atlas use schema.org as the primary source of truth for structured data validation. Google Rich Results Tool may display warnings for optional schema properties that are not required by schema.org. This behavior is expected and does not necessarily indicate a problem with your schema implementation. If your structured data passes schema.org validation and contains all required properties, optional-field warnings can generally be treated as recommendations rather than errors requiring action.

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

🧭 Canonical Tags Guide (2024): Prevent Duplicate Content and Improve SEO

Canonical tags are a vital SEO tool that helps manage duplicate content and ensure search engines index and rank the correct version of a page. Without proper canonicalization, your site risks duplicate content issues, diluted link equity, and crawl inefficiencies. This guide breaks down what canonical tags are, how to implement them correctly, common pitfalls, and advanced techniques to strengthen your site’s SEO foundation. 🔍 What Are Canonical Tags? A canonical tag (<link rel="canonical" href="https://example.com/page" />) is an HTML element placed in the <head> section of a page to specify the preferred version of a URL. When multiple URLs contain identical or similar content — such as filtered product pages or UTM-tagged URLs — the canonical tag signals which page should be treated as the “official” version by search engines. ⚙️ Why Canonical Tags Matter for SEO Canonical tags help you: - Prevent duplicate content penalties: Direct crawlers to the correct version of a page. - Consolidate link equity: Merge ranking signals and backlinks into a single URL. - Improve crawl efficiency: Ensure Google’s crawl budget focuses on essential pages. 🔁 Common Duplicate Content Scenarios Solved by Canonical Tags - Session IDs & URL parameters (e.g., tracking codes, filters). - Product sorting/filtering pages on e-commerce sites. - Print-friendly versions of articles. - HTTP vs HTTPS / www vs non-www duplicates. 🧩 How to Implement Canonical Tags 1. In HTML Add this tag to the <head> of your page: <link rel="canonical" href="https://example.com/canonical-page" /> 2. In CMS Platforms - WordPress: Yoast SEO automatically adds canonical tags; customize via the page editor. - Shopify: Adds self-referencing canonicals by default (edit templates for custom tags). - Squarespace: Canonicals are built in but can be manually adjusted via code. 3. In HTTP Headers For non-HTML assets (like PDFs): Link: <https://example.com/canonical-file>; rel="canonical" 4. In XML Sitemaps Only include canonical URLs in your sitemap to guide crawlers efficiently. 5. Via 301 Redirects If alternate URLs are no longer needed, use a 301 redirect to the canonical page. 🌟 Best Practices for Canonical Tags ✅ Use absolute URLs (not relative). ✅ Include only one canonical tag per page. ✅ Add self-referencing canonicals to every page. ✅ Maintain consistent protocols and trailing slash formats. ⚠️ Common Canonical Tag Mistakes to Avoid 1. Multiple canonical tags on one page. 2. Pointing to redirected URLs. 3. Using canonicals for non-duplicate content. 4. Forgetting to update canonicals during migrations (HTTP → HTTPS). 5. Using relative URLs instead of absolute ones. 6. Omitting self-referencing tags. 7. Inconsistent trailing slash formats. 8. Not auditing canonicals regularly. Use tools like Google Search Console, Ahrefs, or Semrush to monitor and validate your canonical implementation. 🔧 Advanced Canonicalization Techniques Cross-Domain Canonicals When syndicating content, the republished version should reference the original with: <link rel="canonical" href="https://originaldomain.com/article" /> Pagination Handling Each paginated page (Page 1, Page 2, etc.) should include a self-referencing canonical tag. Optionally, use rel="prev" and rel="next" tags to help crawlers understand pagination relationships. International SEO (hreflang + Canonical) For multilingual or regional sites, use canonical tags alongside hreflang attributes to indicate language versions and preferred URLs. 🧠 FAQ: Canonical Tags Simplified Q: What happens if I don’t use canonical tags? A: Google might index multiple versions of the same page, diluting your rankings. Q: Should I use a canonical tag or a 301 redirect? A: Use 301 redirects for permanent moves; use canonical tags when duplicate pages still need to exist. Q: Do all pages need canonical tags? A: Yes — even self-referencing ones prevent confusion and ensure consistent indexing. 🏁 Conclusion Canonical tags are a cornerstone of a clean, optimized SEO strategy. When implemented correctly, they: - Consolidate ranking signals - Prevent duplicate content issues - Improve crawl efficiency - Strengthen your site’s authority Regular audits and consistency across your website are key to keeping canonical tags effective.