WordPress Plugin

⚙️ Configuring Sync to CMS by Content Type

🛠️ Stop OTTO From Overriding Yoast SEO Metadata

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

🔌 Add Meta Tags to WordPress Without Third-Party Plugins

🧭 Overview Search Atlas lets you generate and apply meta titles and meta descriptions directly to your WordPress posts and pages — no need for a third-party SEO plugin like Yoast or Rank Math. This guide walks you through the full process from generating your meta tags to pushing them live on your site. ✅ Before You Start Make sure the following are in place before you begin: - Your WordPress site is connected to Search Atlas. (If not, navigate to your integrations settings and follow the WordPress connection steps.) - You have at least Editor-level access to the WordPress site you want to update. - You have a published or draft post or page ready to optimise. 📝 Step 1: Generate Your Meta Tags Search Atlas includes a built-in Meta Generator tool that creates SEO-optimised meta titles and descriptions for your content. 1. In the left sidebar, click Content, then select Meta Generator. 2. Enter the target URL or paste the content you want to optimise. 3. Add your primary keyword in the keyword field. 4. Click Generate. Search Atlas will produce one or more meta title and description suggestions. 5. Review the suggestions. A strong meta title is typically 50–60 characters, and a meta description should be 120–158 characters. 6. Click Copy next to the version you want to use, or edit it inline before proceeding. 🔗 Step 2: Apply Meta Tags to Your WordPress Post Once you have your meta title and description ready, you can push them directly to your WordPress post through the On-Page Audit tool. 1. In the left sidebar, click Content, then select On-Page Audit. 2. Enter the URL of the WordPress post or page you want to update and run the audit. 3. In the audit results, locate the Meta Title and Meta Description fields. 4. Paste or type your optimised meta title and description into the respective fields. 5. Click Push to WordPress (or the equivalent save/apply button shown for your connected site). 6. Search Atlas will write the meta tags directly to that post via the Search Atlas WordPress plugin, which must be installed and connected to your site. 🔍 Step 3: Verify the Tags Are Live After pushing your meta tags, confirm they are applied correctly: - Visit the post URL in a new browser tab and inspect the page source (Ctrl+U on Windows, Cmd+U on Mac). Search for <title> and <meta name="description" to confirm the values match what you entered. - Alternatively, re-run the On-Page Audit on the same URL. The audit will reflect the updated meta tags if they have been applied successfully. - You can also use Google's Rich Results Test or any meta tag checker tool to validate the output. 💡 Tips for Better Meta Tags - Include your primary keyword near the beginning of both the meta title and description. - Make descriptions action-oriented — tell users what they will find or gain by clicking. - Avoid duplicate meta tags across your site. Each post should have a unique title and description. - Use the Content Planner (Left sidebar → Content → Content Planner) to plan and batch-optimise meta tags across multiple pages at once. ⚠️ Troubleshooting Common Issues If your meta tags are not saving or appearing incorrectly, check the following: - WordPress connection is active: Go to your integrations settings and confirm your WordPress site shows a connected status. Re-authenticate if needed. - Conflicting plugin: If you have Yoast, Rank Math, or another SEO plugin installed, its meta fields may override the tags set by Search Atlas. Disable or uncheck meta tag management in that plugin to avoid conflicts. - Caching: Your hosting cache or a caching plugin may serve an older version of the page. Clear your site cache after pushing changes and then re-verify. - User permissions: Confirm your connected WordPress account has sufficient permissions to edit post meta fields. 🆘 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.

🗺️ Include Custom Post Types in Video and News Sitemaps

🔍 Overview If your video-sitemap.xml or news-sitemap.xml is returning an empty URL set despite having published pages, the most common cause is that your custom post types are not enabled in your sitemap configuration. This is a configuration step — not a missing feature or a plugin limitation. ✅ Before You Begin Confirm the following before adjusting your sitemap settings: - You have published pages or posts using a custom post type (for example, a Videos or News post type). - You have admin-level access to your WordPress dashboard. - MetaSync is installed and active on your site. 🛠️ How to Enable Custom Post Types in Your Sitemaps Follow these steps to include your custom post types in the video or news sitemap: 1. Log in to your WordPress dashboard and navigate to Search Atlas in the left-hand menu. 2. Go to Settings (Sitemap Settings page). 3. Open the Post Types tab (sometimes labeled Content Types). 4. Locate your custom post type (e.g. Videos or News) in the list and toggle it on to include it in the sitemap. 5. Save your changes. 6. Return to Sitemap Settings and click Regenerate Sitemap (or the equivalent regeneration button in your version) to force MetaSync to rebuild the sitemap index. 7. Visit your sitemap URL (e.g. yoursite.com/video-sitemap.xml or yoursite.com/news-sitemap.xml) and confirm that URLs are now appearing. ⚠️ Troubleshooting Empty Sitemaps If the sitemap is still empty after enabling the post type and regenerating, check the following: - Post type visibility: The custom post type may not be registered as public in your theme or plugin code. Ask your developer to confirm the post type is registered with public: true. - Post status: Only posts with a Published status are included in sitemaps. Confirm your pages are fully published and not saved as drafts. - Caching: Some caching plugins may serve an older version of your sitemap. Try clearing your site cache and reloading the sitemap URL. If you need further assistance, open 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 Meta Tags to WordPress Posts via Search Atlas

Overview Search Atlas can integrate directly with your WordPress site to help you manage meta titles and meta descriptions for your posts. This article explains the general workflow for using this integration and what to have ready if you need additional help. Before You Start Make sure the following are in place before following the steps below: - Your WordPress site is connected to Search Atlas. If it is not connected yet, click the top-right avatar → Settings → Integrations / CMS Connectors and use the WordPress integration option to connect your site. - You have at least Editor-level access to the WordPress site in question. - The post you want to update already exists in WordPress, or you are ready to create a new one. How to Add Meta Tags to WordPress Posts Once your WordPress site is connected to Search Atlas, you can manage meta titles and meta descriptions for your posts directly from within the platform. The general workflow is as follows: 1. Open the relevant tool in Search Atlas where you manage your content — such as the On-Page Audit or SEO Content Assistant — and locate the post you want to update. 2. Find the meta title and meta description fields for that post. These fields allow you to enter or edit the SEO metadata that will be applied to your WordPress post. 3. Enter your desired meta title and meta description values in the provided fields. 4. Use the available option to push or save those meta tag values to your connected WordPress site. This will update the meta title and meta description on the WordPress post without requiring a separate plugin. After pushing the changes, visit your WordPress post and verify that the meta title and meta description have been updated as expected. If the fields do not appear or the push does not work, confirm that your WordPress connection is active under the top-right avatar → Settings → Integrations / CMS Connectors. What to Have Ready When You Contact Support If the steps above do not resolve your issue, please have the following information on hand when reaching out: - The URL of your WordPress site or the specific post you want to update. - Whether your WordPress site is currently showing as connected inside Search Atlas. - A description of what you are trying to do — for example, setting a meta title, setting a meta description, or both. - Any error messages you have seen, with the exact text of the message and the time it occurred. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚡ OTTO CMS Integration and Content Deployment Guide

What Is OTTO CMS Integration? OTTO SEO can connect directly to your website's CMS (Content Management System), allowing it to read your existing pages and push SEO changes — such as updated page titles, meta descriptions, and on-page content — without requiring you to manually copy and paste anything. This makes implementing SEO recommendations faster and significantly reduces room for human error. Supported CMS Platforms OTTO supports direct integration with a range of CMS platforms, enabling it to read your pages and apply SEO recommendations automatically. The specific platforms supported may vary depending on your account configuration and the current state of OTTO's integrations. If you are unsure whether your CMS is supported, or if you cannot locate the integration option within your project settings, please reach out to our support team who can confirm compatibility for your setup. Connecting Your CMS to OTTO To connect your CMS, navigate to Account Menu → Settings → CMS Connectors within Search Atlas. From there, you can select your CMS platform and follow the authentication steps to grant OTTO the access it needs. Once connected, OTTO will be able to surface recommendations tied directly to your live pages. If you do not see your CMS listed or encounter any issues during the connection process, our support team can assist you directly. Deploying SEO Changes Once your CMS is connected, you can review and approve OTTO's recommendations from within Search Atlas and push them directly to your site without leaving the platform. Always review changes before deploying — while OTTO's suggestions are data-driven, you remain in full control of what gets published. Applying SEO Changes Manually (Unsupported CMS) If your CMS is not yet supported for direct integration, you can still use OTTO's on-page recommendations and apply them manually within your CMS. View the recommendations generated for your site inside Search Atlas, then implement each suggested change (such as updated page titles or meta descriptions) directly in your CMS's editing interface. If you are unsure how to locate a specific recommendation or how to apply it in your CMS, our support team can walk you through the process. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔐 Mandatory WordPress Support Flow: Secure Token-Based Access

To improve security, accountability, and compliance, Search Atlas no longer supports accessing customer WordPress environments via shared usernames or passwords. All WordPress support access must be granted via temporary Support Access Tokens, generated directly by the customer inside their WordPress admin. This flow is mandatory and replaces all previous credential-sharing practices. ✅ What’s Changing (High Level) 1. No more WordPress usernames or passwords shared, stored, or requested 2. Temporary, revocable access via secure token links 3. Admin-only access, controlled by the customer 4. Time-limited access with automatic expiration 5. Full visibility and accountability of who accessed what, and when 🧩 Prerequisites (Required) Before support access can be granted, all of the following must be true: 1. Plugin version must be 2.5.16 or higher. Any version below 2.5.16 is not supported and cannot use token-based access. 2. The customer must be logged in as a WordPress ADMIN. Only Admin users can generate support tokens. 🛠️ The Mandatory Support Flow (Step by Step) 1. Customer updates to the latest plugin version. Minimum supported version: v2.5.16. Without this version, support access cannot be granted. 2. Customer generates a Support Access Token. Path inside WordPress: WordPress Admin → Settings → Support Access. From here, the customer can choose an expiration time (for example, 4 hours), add a short description (bug, issue, investigation context), and generate a secure, temporary access link. 3. Customer shares the secure link. The generated link is shared with Customer Support, Product Specialists, and the WordPress Team if needed. No usernames or passwords should ever be sent. 4. Search Atlas team accesses WordPress via the link. Using the link, team members are automatically logged in as ADMIN, and access uses the same User ID that generated the token. Full admin-level debugging and investigation is allowed. 5. Access is revoked after work is completed. Once the issue is fixed, tested, or fully investigated, the Search Atlas team must revoke the support token and inform the customer that access has been terminated. This is a required step, not optional. 6. If the token expires before work is finished. Tokens may expire based on the timeframe chosen by the customer. If this happens, politely request a new Support Access Link, clearly explain why additional access is needed, and never attempt to reuse or bypass expired tokens. 🚫 Critical Rules (Non-Negotiable) Do not ask for, store, or accept WordPress usernames or passwords. 👑 Admin Role Required Only WordPress Admins can generate tokens and grant support access. 📁 Exception: FTP Access This flow applies only to WordPress admin access. If FTP access is required, the existing FTP request process remains unchanged, coordinate via CS/PS as usual. 🧠 Why This Matters This flow protects customer security, reduces liability, improves trust, and creates a clear, auditable support process. Following this process is mandatory for all WP-related support cases. 📌 Summary 1. Token-based access is now the only approved method 2. Credentials are no longer allowed 3. Access is temporary, revocable, and customer-controlled 4. Expired access means requesting a new token 5. Security first, always This WordPress Support Access flow marks a fundamental shift in how we provide secure, reliable, and compliant support to our customers. By fully eliminating credential sharing and moving to a controlled, token-based access model, we protect both our customers’ environments and our own teams while maintaining the level of support quality they expect from Search Atlas. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🧩 Elementor Modules, Page Structure, and SEO

🔍 Overview If you build pages with Elementor, three common questions come up around SEO: does the Icon List module hurt rankings because it skips standard HTML list tags, do WordPress parent/child page relationships matter for SEO, and should content inside Tab modules be indexed? This article answers all three clearly so you can make informed decisions inside Search Atlas. 📋 Elementor Icon List Module and Semantic HTML Elementor's Icon List widget does not output a traditional <ul> or <ol> element. Instead, it renders a series of <div> containers styled to look like a list. Here is what that means for SEO: - Googlebot can still read the content. Google's crawler processes rendered HTML, so the text and links inside an Icon List are fully visible and indexable regardless of the wrapper element used. - Semantic signals are weaker. Native <ul> and <ol> tags communicate list structure to search engines, which can help with featured snippets and content understanding. Div-based lists do not carry the same semantic weight. - When it matters most. For pages targeting featured snippet formats — such as step-by-step guides, comparison lists, or ingredient-style content — prefer Elementor's standard Text Editor widget or a custom HTML widget that outputs real <ul> or <ol> markup. - When it is acceptable. For decorative icon lists used in hero sections, feature grids, or sidebar callouts where snippet eligibility is not a priority, the Icon List widget is fine to use. Inside Search Atlas, audit your on-page HTML structure using the Content Editor or Site Auditor. Flag pages where list-format content is a ranking priority and swap the widget accordingly. 🗂️ WordPress Parent/Child Page Structure and SEO WordPress allows you to assign a parent page to any page, creating a hierarchical URL structure such as /services/ as the parent and /services/seo-audit/ as the child. This structure has real SEO implications. - URL hierarchy signals topic relevance. A nested URL tells search engines that the child page belongs to a broader topic cluster. This can reinforce topical authority when your site architecture matches your content strategy. - Parent pages inherit linking equity. Internal links pointing to a parent page pass some authority to child pages through the site's crawl path, but this is not automatic — you still need explicit internal links between related pages. - Hierarchy alone does not replace internal linking. Do not rely solely on the parent/child relationship to connect pages. Add contextual internal links within your body copy. Search Atlas's Internal Link Suggestions tool surfaces opportunities to link parent and child pages together more effectively. - Flat vs. deep structures. A flat architecture — where most pages are within one or two clicks from the homepage — generally performs better for crawlability. Avoid nesting pages more than three levels deep unless your site scale genuinely requires it. - Breadcrumbs amplify the hierarchy signal. Enable breadcrumb schema (via Yoast, Rank Math, or a custom plugin) on parent/child page sets. Search Atlas's Schema Markup audit will flag pages missing breadcrumb structured data. Use Search Atlas's Site Audit tool (accessible from Left sidebar → Site Audit) to review your crawl depth report and confirm that child pages are being discovered and indexed correctly. If child pages are orphaned — meaning no internal links point to them beyond the parent relationship — add contextual links from the parent page body. 🗃️ Elementor Tab Modules, Content Indexing, and Noindex Strategy Elementor's Tabs widget hides inactive tab panels using CSS (display: none or similar). Google has confirmed it can index content inside hidden CSS tabs, but there are nuances you should understand before deciding on a noindex strategy. - Google does index tab content. Since Google renders JavaScript and CSS, content inside inactive tabs is generally crawled and indexed. You do not need to noindex tab panels by default. - Hidden content may receive less weight. Some SEO professionals report that content not visible on page load is treated as lower priority. If a tab contains your primary keyword content, consider whether it should be the default active tab or moved into the main page body instead. - Do not noindex individual tab panels. You cannot reliably noindex a tab panel without noindexing the entire page. Applying a noindex directive to a page removes all of its content from the index, including the visible content — this is rarely the right move. - Use tabs for supplementary content. Tabs work well for FAQs, technical specifications, or secondary information that supports the main topic but does not need to rank independently. Avoid placing your core optimised content exclusively inside a tab. - Structured data still applies. If your tab content contains FAQ pairs or how-to steps, you can still apply FAQ or HowTo schema to that content. Search Atlas's Schema Markup tool will help you validate the output even if the content renders inside a tab. To audit how Googlebot sees your tabbed pages, use the URL Inspection feature in Google Search Console alongside Search Atlas's On-Page SEO Checker. Compare the rendered HTML against your target keywords to confirm the tab content is being picked up correctly. ✅ Quick Reference Summary - Icon List widget: Use for decorative lists; switch to native HTML lists for snippet-targeted content. - Parent/child pages: Hierarchy reinforces topical clusters, but always add explicit internal links — do not rely on URL structure alone. - Tab modules: Content is indexed but may carry less weight; keep primary optimised content visible on page load and avoid noindexing pages just because they use tabs. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

💡 Justify Search Atlas ROI vs Traditional SEO Plugins

🤔 Why This Comparison Matters Many SEO professionals have invested in traditional plugins like RankMath, Yoast, or All-in-One SEO, only to find that rankings stagnate and the promised results never fully materialise. If you're evaluating Search Atlas, it's completely reasonable to ask: what makes this different, and how do I know it will be worth the investment? This article explains the core differences between AI-powered SEO platforms and traditional plugin tools, and outlines how to approach measuring your return on investment so you can make a confident, informed decision. 🔌 What Traditional SEO Plugins Actually Do Tools like RankMath and Yoast are on-page formatting assistants. They help you structure content according to a checklist of basic SEO rules — things like adding a meta description, including your keyword in the title, or ensuring your content reaches a minimum word count. While these checks are useful, they come with significant limitations: - They evaluate content in isolation, with no awareness of what competitors are doing. - They rely on static rules that do not adapt to algorithm changes. - They offer no keyword research, backlink analysis, or content strategy guidance. - They cannot identify why pages are underperforming or what action to take next. - They generate no original content and cannot optimise at scale. In short, traditional plugins tell you whether you followed a formatting checklist. They do not tell you whether your content will actually rank. 🤖 What an AI-Powered SEO Platform Does Differently Search Atlas is built around a fundamentally different model. Instead of checking boxes, it analyses real data — your site, your competitors, and the search landscape — and recommends actions with the highest probability of improving rankings. Key capabilities that traditional plugins do not offer include: - Topical authority mapping: Identifies content gaps and cluster opportunities so your site builds genuine authority in your niche. - Competitor intelligence: Analyses what is actually ranking and helps inform the strategy behind your content decisions. - AI content creation: Generates optimised drafts aligned to search intent, not just keyword density. - Technical SEO tooling: Surfaces technical issues across your site so your team can prioritise and resolve them efficiently. - Unified reporting: Connects keyword rankings, traffic, and content performance in one dashboard so you can see what is working. 📊 How to Approach ROI Measurement The clearest way to justify any SEO investment is to track the right metrics from the start. A practical framework to follow: 1. Baseline your current rankings: Before making changes, record your existing keyword positions, organic traffic levels, and conversion rates. This gives you a clear before-and-after comparison point. 2. Set specific, time-bound goals: Define what success looks like — for example, a target increase in ranking positions for priority keywords, or a percentage uplift in organic sessions within 90 days. 3. Track content output and impact: Log every piece of content created or optimised using Search Atlas, and monitor how those pages perform in rankings and traffic over time. 4. Calculate cost per outcome: Compare the time and cost of achieving results with Search Atlas against what the same outcomes would require using manual methods or traditional tools. 5. Review and iterate monthly: SEO compounds over time. Review your metrics monthly, identify what is working, and adjust your strategy based on actual data rather than assumptions. If you are unsure how to set up tracking or interpret your results, the Search Atlas support team can walk you through the reporting features available in your plan. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔄 How to Sync OTTO SEO Changes to Shopify

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

🗺️ Disable URL Types in Search Atlas Sitemaps After Yoast Migration

🔍 Overview When you migrate from Yoast to Search Atlas, your previous sitemap exclusion settings are not automatically carried over. If you had author pages, video pages, category pages, or tag pages disabled in Yoast, you will need to re-apply those exclusions directly in Search Atlas. This article explains what to do and what to have ready when contacting support. ⚠️ Why This Matters Pages that return errors — such as 404s or thin-content pages — should not appear in your sitemap. Including them can signal quality issues to search engines and negatively affect your site's crawl budget. Disabling these URL types in your Search Atlas sitemap keeps it clean and aligned with your SEO strategy. 🧭 How to Access Your Sitemap Settings 1. Log in to your Search Atlas account. 2. Navigate to the project associated with the domain you migrated from Yoast. 3. Look for a sitemap or sitemap configuration area within your project settings. The exact location may vary depending on your account setup — if you cannot locate it, see the escalation steps below. 🚫 Disabling Specific URL Types Within your sitemap settings, you should be able to control which URL types are included in your sitemap. Common URL types that users disable after a Yoast migration include: - Author pages — archive pages grouped by post author - Video pages — pages associated with video content - Category pages — taxonomy archive pages for post categories - Tag pages — taxonomy archive pages for post tags If your sitemap settings include controls for these URL types, disable the ones you want to exclude and save your changes. After saving, regenerate or refresh your sitemap so the exclusions take effect. If you do not see controls for specific URL types in your sitemap settings, this configuration may need to be applied by the Search Atlas support team on your behalf. Please see the escalation steps below. ✅ Verifying Your Changes After saving and refreshing, confirm the excluded URL types no longer appear in your sitemap: - Open your live sitemap URL (typically yourdomain.com/sitemap.xml) and check that author, video, category, or tag URLs are absent. - If your sitemap is split into sub-sitemaps (e.g., a dedicated category sitemap), verify those sub-sitemaps are also removed or empty. 📋 Before You Escalate — What to Have Ready If you cannot locate the URL type controls in your sitemap settings, or if the exclusions are not taking effect after saving, please reach out to the support team with the following information: - Your project name and the domain you migrated from Yoast - The specific URL types you need to disable (e.g., author, video, category, tag) - A description of what you see in your current sitemap settings, or a note that you cannot locate the sitemap configuration area - Any error messages or unexpected behavior you have observed If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔄 CMS SYNC & Publishing Platform Strategy Guide

🧭 Overview Search Atlas offers a native CMS SYNC integration with WordPress, which changes how you should think about where to publish your articles. This guide walks you through the differences between Shopify and WordPress for content publishing, how CMS SYNC fits into your workflow, and how to make the right platform choice for your SEO strategy. 🐦 Fixing Twitter Card Metadata Before choosing a publishing platform, ensure your Twitter Card metadata is correctly configured. Twitter Cards require the following meta tags in your page <head>: - twitter:card — set to summary, summary_large_image, or another supported type. - twitter:title — matches your article's primary title. - twitter:description — a concise summary under 200 characters. - twitter:image — a publicly accessible image URL, minimum 144×144 px. On WordPress, an SEO plugin such as Yoast or Rank Math handles these tags automatically under the Social settings for each post. On Shopify, Twitter Card tags are included in most themes by default, but you may need to edit your theme.liquid file or install a third-party SEO app if tags are missing or incorrect. Always validate your tags using the Twitter Card Validator after making changes. ⚖️ Shopify Blog vs. WordPress: Key Differences Both platforms can host blog content, but they serve different primary purposes and have distinct SEO capabilities. - Shopify Blog is built for e-commerce first. Its blogging feature is functional but limited — you get basic post creation, tags, and author fields. Customising URL structures, schema, or metadata requires theme edits or paid apps. - WordPress is purpose-built for content management. It offers granular control over SEO metadata, URL slugs, schema markup, internal linking structures, categories, and taxonomies — all essential for a strong content strategy. If your primary goal is publishing articles at scale to drive organic traffic, WordPress consistently provides more flexibility and SEO control than Shopify's blog module. 🔗 What Is CMS SYNC and How Does It Work? CMS SYNC is a Search Atlas feature that pushes content you create or optimise inside the platform directly to your connected WordPress site — no copy-pasting required. Here is how the workflow operates: 1. Connect your WordPress site to Search Atlas via the Account Menu (avatar) → Settings → CMS Connectors. 2. Write or optimise your article inside Search Atlas using the Content Editor or AI writer. 3. When your content is ready, select Publish via CMS SYNC. 4. Search Atlas pushes the article to your WordPress site as a draft or live post, depending on your settings. 5. All formatting, headings, and metadata configured inside Search Atlas are preserved on publish. CMS SYNC significantly reduces the time between content creation and live publishing, and keeps your Search Atlas content data linked to live performance metrics. ⚠️ CMS SYNC Limitations to Know - CMS SYNC is currently supported for WordPress only. There is no native sync to Shopify, Webflow, Wix, or other CMS platforms at this time. - Images must be hosted or accessible via URL before syncing — very large media files may require manual upload to your WordPress media library. - Custom post types or heavily modified WordPress themes may require minor adjustments after the first sync to ensure correct display. - Republishing an already-synced article will overwrite the existing WordPress post — always review before re-syncing. 📊 SEO Implications by Platform Platform choice has a direct impact on your SEO outcomes. Consider the following: - WordPress + CMS SYNC gives you full control over title tags, meta descriptions, Open Graph tags, Twitter Cards, canonical URLs, structured data, and XML sitemaps. This level of control is critical for competitive content strategies. - Shopify Blog is well-suited for product-adjacent content — how-to guides tied to your catalogue, buying guides, or brand storytelling — where the primary conversion goal is the product page rather than organic traffic growth. - WordPress sites consistently allow faster iteration on on-page SEO because changes are made in a single interface without theme dependencies. ✅ Which Platform Should You Use? Recommended Use Cases - Use WordPress with CMS SYNC if: your strategy centres on scaling organic traffic through blog content, you want to manage your entire content lifecycle inside Search Atlas, or you need precise metadata and schema control. - Use Shopify Blog if: you operate a Shopify store and want simple, on-brand content that supports your product pages, and your content volume is low enough that manual publishing is not a bottleneck. - Use both if: you run a Shopify store but also maintain a WordPress subdomain or separate domain for your content hub. In this case, publish all editorial content to WordPress via CMS SYNC, and keep Shopify blog posts limited to store-specific announcements or product updates. 🚀 Getting Started with CMS SYNC 1. In Search Atlas, go to Settings → CMS Connectors. 2. Enter your WordPress site URL and generate an API connection using the Search Atlas WordPress plugin. 3. Test the connection with a draft post before syncing live content. 4. Return to any article in your Content Editor and use the Publish button to sync directly to WordPress. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔌 Configure OTTO Pixel UUID and WordPress Plugin Authentication

🧭 Overview The Search Atlas WordPress plugin connects your site to OTTO SEO by verifying your API Key and a tracking pixel tied to your site's unique OTTO Pixel UUID. Authentication failures typically happen when credentials are mismatched, the site URL does not align with what Search Atlas has on record, or the UUID has not been entered manually. This article walks you through the general process to resolve these issues. 🔑 Step 1: Locate Your API Key Your API Key is found inside the Search Atlas platform. Follow these steps: 1. Log in to your Search Atlas account. 2. Navigate to Account Menu → Settings → API Keys. 3. Find the section related to API access or integrations. 4. Copy the API Key displayed. Keep this value ready — you will paste it into the WordPress plugin in a later step. Important: Do not share your API Key publicly. If you suspect it has been compromised, regenerate it from the same settings area and update it in the WordPress plugin immediately. 🪄 Step 2: Locate Your OTTO Pixel UUID Each website you manage in Search Atlas has a unique OTTO Pixel UUID. This identifier links the WordPress plugin to the correct OTTO SEO project. To find it: 1. Log in to your Search Atlas account. 2. Navigate to the OTTO SEO or OTTO SEO section of the platform. 3. Select the website project you are trying to connect. 4. Look for the pixel or UUID information within that project's settings or setup area. 5. Copy the UUID string displayed. Note: Each website has its own UUID. If you manage multiple sites, confirm you are copying the UUID for the specific domain you are configuring in WordPress. 🔌 Step 3: Enter Credentials Manually in the WordPress Plugin Once you have both your API Key and OTTO Pixel UUID, enter them directly into the plugin: 1. Log in to your WordPress admin dashboard. 2. Navigate to the Search Atlas plugin settings within WordPress. 3. Locate the field for your API Key and paste the value you copied in Step 1. 4. Locate the field for your OTTO Pixel UUID and paste the value you copied in Step 2. 5. Save the settings to apply the credentials. 6. Check whether the connection is confirmed. If an error appears, proceed to the troubleshooting steps below. 🌐 Step 4: Verify Your Site URL Matches A mismatch between the URL registered in Search Atlas and the URL your WordPress site reports is one of the most common causes of authentication failures. To address this: 1. Check the domain associated with your project inside the Search Atlas platform. 2. Compare it to the URL your WordPress site is using (including whether it uses www or non-www, and whether it uses http or https). 3. If there is a discrepancy, update the URL in Search Atlas or adjust your WordPress site URL so the two values match exactly. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

📘 Using Search Atlas with 10Web AI Website Builder (WordPress)

Using Search Atlas with a WordPress site built on the 10Web AI Website Builder is a supported and effective setup for SEO. While 10Web provides strong performance and infrastructure, Search Atlas adds an automated SEO execution layer that handles content, metadata, schema, and ongoing optimization. This article explains how the two platforms work together and how to configure them for optimal SEO results. 🧠 How 10Web and Search Atlas Work Together 🏗️ 10Web (Infrastructure Layer) 10Web provides: - High-performance hosting - Strong PageSpeed scores (often 90+) - Built-in performance and caching tools This creates a solid technical foundation for SEO. 🤖 Search Atlas (Execution Layer) Search Atlas adds: - Automated SEO execution - Content publishing and optimization - Technical SEO fixes and schema deployment The Search Atlas WordPress plugin (v3) acts as the bridge between Search Atlas and your 10Web-built site. ✅ Key Advantages of Using Search Atlas on 10Web When combined, the platforms cover different but complementary SEO needs: - One-Click Publishing Generate long-form content in Search Atlas and publish directly to WordPress with SEO tags preserved. - Automated Technical Fixes Automatically identifies and resolves issues such as: - 404 errors - Broken links - Metadata gaps - Advanced Schema Deployment Deploys advanced schema (FAQ, Article, etc.) that may not be handled natively by 10Web. - Google Search Console Visibility View GSC data for specific URLs directly inside the WordPress dashboard. ⚙️ Recommended Setup for Best SEO Results Follow this configuration path for optimal performance: Step 1 — Install and Sync the Plugin Install the Search Atlas WordPress plugin and connect it using your API key. Step 2 — Migrate Existing SEO Data If the site previously used plugins like Yoast or RankMath, use the plugin’s one-click import to migrate existing SEO data into the Search Atlas system. Step 3 — Set Up OTTO SEO Enter your OTTO Pixel UUID in the plugin settings (Search Atlas → Settings, under the OTTO Server-Side Rendering section) to enable real-time SEO optimizations. Step 4 — Build Topical Authority Use the Topical Map Creator to plan service-area or niche content, then generate drafts using Search Atlas AI tools. 🔧 Compatibility Notes - Search Atlas is cache-aware - Fully compatible with modern builders like Elementor (used by 10Web) - Does not overwrite existing Yoast configurations - Designed to run alongside 10Web performance tools without slowing down the site ⚠️ To avoid conflicts: - Avoid overlapping SEO plugin features - Assign one primary tool per SEO function (meta tags, schema, etc.) - Check the site’s <head> for duplicate meta or schema injections ❓ FAQs ❓ Does Search Atlas work with 10Web AI sites? Yes. It works well with WordPress sites built on 10Web. ❓ Will it conflict with 10Web or Elementor? No. Search Atlas is designed to be compatible with modern builders and caching systems. ❓ Does Search Atlas overwrite existing SEO plugins? No. It complements existing setups and does not overwrite Yoast configurations. ❓ Is this recommended for optimal SEO? Yes. The combination provides both performance (10Web) and automated SEO execution (Search Atlas). Using Search Atlas with a 10Web-built WordPress site is a recommended setup for scalable, automated SEO. 10Web handles infrastructure and speed, while Search Atlas handles ongoing SEO execution and optimization.

🔗 Key Points of CMS Integrations

OTTO applies all optimizations to your site's front end only — your CMS settings and database are never modified. Understanding how JavaScript injection, visual visibility, and user targeting work lets you deploy OTTO with confidence. 🔒 No Permanent Changes to Your CMS OTTO does not alter your CMS configuration. All optimizations are applied to the front-end display only — your underlying settings and database remain untouched. 👁️ Visibility of Changes on the Page Not every OTTO change appears visually on the page: - Meta titles and descriptions — injected into the page HTML and visible when inspecting the source, but not displayed on the page itself. - Headings (H1, H2) — visible directly on the live page. ⚙️ JavaScript Dependency OTTO injects all changes through JavaScript. If the script is disabled or removed from your site, all optimizations disappear immediately. Keep the script active to maintain your changes for site visitors. There is one conditional exception: if the Disable OTTO for Logged in Users setting is enabled, logged-in users will not see OTTO's front-end changes even while the script remains fully active. See the section below for details. 🔑 Excluding Logged-In Users from Front-End Changes When Disable OTTO for Logged in Users is enabled, authenticated users — editors, admins, and any other logged-in visitors — see the original CMS output instead of OTTO's front-end changes. The script remains active and continues injecting changes for all non-authenticated visitors. When to use this setting: - You need editors or admins to preview the unmodified page without OTTO changes applied. - You want to separate the logged-in and logged-out viewing experience. How to confirm it is working: 1. Enable the setting, then reload the page while logged in — you should see the original CMS output with no OTTO-injected changes. 2. Log out and reload to confirm that non-authenticated visitors still see the optimized version. 🎯 OTTO keeps your CMS untouched by applying all changes through JavaScript at the front-end layer — meta tags appear in the source only, headings appear on the live page, and logged-in users can be excluded entirely via the Disable OTTO for Logged in Users setting. For next steps, see the OTTO Deployment guide to start applying optimizations.

⚠️ Received a Copyright Infringement (DMCA) Email About the Search Atlas SEO / Metasync Plugin?

Some users have received an email presented as a formal copyright infringement notice related to the Search Atlas SEO WordPress plugin (also referred to as "Metasync"). This article confirms the status of these emails and outlines the recommended steps. 🔍 How to Recognize This Email The email typically has these characteristics: - It is presented as a formal DMCA / Federal Copyright Infringement notice and cites copyright law. - It claims the Metasync ("Search Atlas SEO") WordPress plugin contains the sender's copyrighted code, distributed without authorization. - It references legal statutes and a pending court case, and threatens a large monetary damages claim. - It demands that you remove or disable the plugin from your website. - It asks you to identify the company or person who provided or sold you the plugin. - It includes the sender's personal contact details (email, phone, address, and website). ⚠️ Is It Legitimate? No. Search Atlas has confirmed that this notice is not legitimate. It is a known scam targeting websites that use the Search Atlas SEO / Metasync WordPress plugin. Our legal team is already involved and is actively handling this at the company level. ✅ What to Do No action is required on your end. Specifically: - Do not respond to the sender. - Do not remove the plugin. - Do not make any changes to your website. - Block the sender and disregard the notice entirely. 🔗 Reporting Follow-Up Messages If you receive any follow-up communications related to this notice, forward them to our Intercom chat (click the messenger icon — type Human Teammate when Voodoo responds to reach a human agent), and we will make sure they are routed to our legal team. 🤝 In Short This notice is a known scam, not a genuine legal claim, and your website and plugin are fine to keep running exactly as they are. There's nothing you need to fix or remove — just block the sender, ignore the message, and forward any further contact to us so our legal team can handle it. We've got you covered.

🔄 Push OTTO Optimizations Directly Into Your CMS

🤔 What Is Sync to CMS? Sync to CMS allows OTTO to automatically push approved SEO optimizations from your dashboard directly into your website's CMS. When enabled, each approved optimization is written to your CMS's native fields as well as the SEO plugin you are using, keeping your live website and CMS records in sync at all times. ✅ Who Can Use Sync to CMS? Sync to CMS is available only for websites connected through the SearchAtlas WordPress plugin (MetaSync). If your website uses the Cloudflare or Pixel installation method, the Sync to CMS option will not appear in your dashboard. You must be on a WordPress plugin project to access this feature. ⚙️ How to Turn On Sync to CMS 1. Open your OTTO project. 2. Select a syncable optimization type (for example, Page Title or Meta Description). 3. Locate the Sync to CMS toggle. 4. Turn it on and confirm. Once enabled, every approved optimization for that type will automatically sync to your CMS. You can turn the feature off at any time. Doing so prevents future optimizations from syncing, but any changes that have already been synced will remain in your CMS. 📋 What Gets Synced Each supported optimization is saved to the SearchAtlas plugin's native fields and synchronized with your active SEO plugin (Yoast SEO, Rank Math, or AIOSEO). The following optimization types are synced: - Meta title — synced - Meta description — synced - Focus keyword / keyphrase — synced - Open Graph title and description — synced - Twitter title and description — synced - Schema / structured data — synced - Canonical URL — synced - Image alt text — synced (updates the WordPress Media Library) 🚫 What Does Not Sync Heading changes and Link corrections (Issues with Links) are not synced. These optimizations modify the page body content, which is native to the SearchAtlas plugin. Because SEO plugins such as Yoast SEO, Rank Math, and AIOSEO do not provide equivalent fields for page body content, there is nothing to synchronize. Additionally, heading and link changes are supported only on posts and pages using the Gutenberg or Classic Editor. They are intentionally skipped on the following page builders because those builders store content outside the standard WordPress post body: - Elementor - Divi - WPBakery - Beaver Builder - Oxygen - Brizy All other supported optimization types sync regardless of which editor or page builder is used. ❓ Frequently Asked Questions Is syncing reversible? Turning off Sync to CMS prevents future optimizations from syncing. It does not remove or roll back changes that have already been written to your CMS. I am using Cloudflare or Pixel. How can I use Sync to CMS? To use Sync to CMS, you must connect your website through the SearchAtlas WordPress plugin (MetaSync). The feature is not available for Cloudflare or Pixel installation methods. 💬 Need More Help? If you have additional questions about Sync to CMS, open the chat widget in the bottom-right corner of the platform and type human teammate to connect with our support team.

⚙️ How 'Disable OTTO for Logged-in Users' Works in the WordPress Plugin

The Disable OTTO for Logged-in Users setting in the Search Atlas WordPress plugin is designed to hide OTTO-deployed titles from authenticated WordPress users. If you've enabled it and logged-in users are still seeing OTTO titles on your frontend, a confirmed bug is the cause. ⚙️ What 'Disable OTTO for Logged-in Users' Controls When OTTO deploys optimized titles to your site, it replaces the original page and meta titles on your frontend for all visitors. The Disable OTTO for Logged-in Users setting creates an exception for authenticated WordPress users. - Setting enabled: Logged-in WordPress users see the original, pre-OTTO page and meta titles on the frontend. - Setting disabled (default): All visitors — logged in or not — see OTTO-deployed titles. This is most useful for site administrators and editors who want to QA original content or compare it against OTTO's deployed version without logging out of WordPress. 🔧 How to Enable 'Disable OTTO for Logged-in Users' 1. Log in to your WordPress admin dashboard. 2. Navigate to the Search Atlas plugin settings. 3. Find the Disable OTTO for Logged-in Users toggle. 4. Turn the toggle on. 5. Click Save Changes. The setting saves immediately. Once the known issue below is resolved, logged-in WordPress users will see original titles when browsing your site's frontend. ⚠️ Known Issue: The Setting Has No Effect in the Current Plugin Version A confirmed bug (WP-313) means that enabling Disable OTTO for Logged-in Users currently has no observable effect. OTTO-deployed titles continue to appear on the frontend for logged-in users — the setting does not suppress them as intended, and deployed titles override original defaults regardless of login state. If you've enabled this setting and logged-in users are still seeing OTTO-deployed titles, WP-313 is the cause. A fix is in progress and will be included in an upcoming plugin release. 🛠️ Workarounds While WP-313 Is Being Fixed Until the fix ships, use one of these approaches to view or verify your original (pre-OTTO) titles: - Log out and open a private browsing window — this shows exactly what visitors see, including all OTTO-deployed titles, with no login state affecting the output. - Review titles in the Search Atlas dashboard — the OTTO interface displays both the original and the deployed title for each page, so you can compare them side-by-side without leaving your admin account. - Use a staging site — deploy OTTO titles on a staging copy of your site and review while logged out to QA changes safely before they affect production. 🎯 You now understand what the Disable OTTO for Logged-in Users setting is designed to do and why logged-in users may still see OTTO-deployed titles in the current plugin version. The WP-313 fix is actively in progress — reach out to Search Atlas support if you need a status update on the release timeline.

🚀 Export OTTO On-Page SEO Data to Rank Math

📋 What This Article Covers Many WordPress users manage their meta titles, descriptions, and other on-page elements with the Rank Math plugin. If you use OTTO in Search Atlas to generate on-page SEO recommendations, you can export that data in bulk and apply it inside Rank Math instead of editing each page manually. This guide explains how to export your OTTO on-page data and how to make sure the meta fields you need are included. If you have the Search Atlas WordPress (OTTO) plugin connected, OTTO can also sync your on-page optimizations directly into your active SEO plugin's data store when changes are saved, which can remove the need for a manual CSV import. Rank Math is a supported active SEO plugin, so with the plugin connected OTTO writes the optimized meta titles and descriptions straight into Rank Math's data store on every save. The CSV workflow described here is useful when you prefer to review and apply changes yourself, or when you are not using the plugin connection. ✅ Before You Begin Make sure you have the following ready: - An active Search Atlas account with OTTO enabled for your project. - OTTO has finished crawling your site and generated on-page recommendations. - Administrator access to the WordPress site that runs Rank Math. - The Rank Math plugin installed and activated. 📤 Step 1: Export Your OTTO On-Page Data Follow these steps inside Search Atlas to create your export file: 1. Open your project and go to the Left sidebar → Content → Onpage Audit to view all generated recommendations. 2. Review the list and confirm the pages you want to export are marked as deployed or ready. 3. Click the Export button at the top of the on-page table. 4. Choose CSV as the file format and confirm the download. The CSV file will download to your computer and contain one row per URL with the on-page fields OTTO has generated. 🔍 Why Meta Fields May Be Missing The most common reason an exported file appears to have no meta fields is that the affected pages did not have recommendations generated or deployed before the export. OTTO only includes fields it has actually produced values for. Check the following: - Recommendations not generated: If OTTO has not finished processing a page, its meta title and description columns will be empty. Wait for the crawl to complete and try again. - Suggestions generated for only top pages: A known issue with the Fix Critical On-Page SEO Issues AI playbook causes it to generate AI suggestions for only the top ~10% of pages rather than every page. Pages outside that set will export with empty meta title and description fields. A fix for this is currently awaiting release, and once it ships the playbook will generate suggestions for all pages rather than only the top set; in the meantime, confirm recommendations have been generated and deployed for the remaining pages before exporting. - Filtered view: If you applied a filter to the on-page table, the export may only reflect the visible rows. Clear all filters before exporting to capture every field. - Pending or undeployed changes: Pages with changes that are still pending may export blank values. Deploy or approve the recommendations first. - Column mismatch: When opening the CSV, confirm you are viewing the correct columns. Spreadsheet programs sometimes hide or misalign columns if the file is not imported with the right delimiter. 📥 Step 2: Map Your Columns for Rank Math Rank Math imports on-page data through its CSV Import & Export feature, which expects specific column names. Before importing, align your Search Atlas export to match the fields Rank Math recognizes: - id or url — used to match each row to the correct post or page. - rank_math_title — the SEO meta title. - rank_math_description — the meta description. - rank_math_focus_keyword — the target keyword, if available. Open your exported CSV in a spreadsheet program, rename the relevant Search Atlas columns to match the Rank Math field names above, and remove any columns Rank Math does not use. Save the file as CSV when finished. ⚙️ Step 3: Import the File into Rank Math 1. Log in to your WordPress dashboard. 2. Go to Rank Math SEO, then Status & Tools. 3. Select the Import & Export tab. 4. Scroll to the CSV Import section and upload your prepared file. 5. Match each column to the correct Rank Math field if prompted, then start the import. Rank Math will update the meta fields for each matched post. Review a few pages afterward to confirm the titles and descriptions appear correctly. 💡 Tips for a Clean Export - Always clear filters in the OTTO on-page table before exporting to ensure every field is included. - Confirm OTTO has finished crawling and generating recommendations before downloading. - Keep a backup copy of your original CSV before editing column names. - Import in smaller batches if you manage a large site, so you can spot any mapping issues early. - This export covers on-page meta fields. A full-site schema export/download (rather than page-by-page) is not yet available and is being tracked as an open feature request, so plan any schema work separately from this on-page export. 💬 Need More Help? If you need further assistance, click the chat icon in the bottom-right corner of the platform and type "Human Teammate" to start a live chat with a member of our team.