Troubleshooting: Sync & Publishing Failures

🔗 GHL Child Accounts and Missing Billing Section

🔍 Why the Billing Section Is Hidden If your Search Atlas account was set up through a GoHighLevel (GHL) integration, you are on a child account linked to a parent agency or reseller. By design, child accounts do not have access to the Billing section — even if you hold an Admin role inside that account. This is intentional behaviour. In the GHL integration model, billing and subscription management are controlled exclusively at the parent account level to prevent conflicting changes and ensure the agency retains full control over plan administration. 🧩 Understanding GHL Parent and Child Accounts When an agency or reseller uses GoHighLevel to provide Search Atlas access to their clients, each client is provisioned as a child account under the agency's master account. This structure means: - Your subscription, plan tier, and payment details are owned and managed by the parent agency. - The Billing menu item is intentionally hidden from child accounts to reflect this separation of responsibility. - Admin permissions inside a child account grant control over users, settings, and tools — but not over billing. - Some agencies are themselves child accounts under a larger parent organisation. If your account was provisioned by such an agency, you may be on a child-under-child account. The same billing restriction applies at every level of this hierarchy — billing is always managed at the top-level parent account. 🚀 How to Upgrade or Change Your Plan Because billing sits at the parent level, you cannot make plan changes directly from your account. To upgrade, downgrade, or update payment details, you need to reach out to the agency or reseller who provisioned your Search Atlas account. They can: 1. Review your current plan and usage. 2. Upgrade or downgrade your subscription on your behalf. 3. Update billing and payment information as needed. If you are unsure who your parent agency is, check any onboarding emails you received when your account was first created — the agency's contact details are typically included there. ⚙️ How to Confirm You Are on a GHL Child Account Follow these steps to verify your account type: 1. Click your avatar in the top-right corner of the platform. 2. Select Settings from the dropdown menu (or navigate to /settings). 3. Review the top-right corner Avatar Menu (👤) for a Billing option. 4. If no Billing section appears, your account is a GHL child account and plan management must go through your parent agency. ❓ Frequently Asked Questions - I'm an Admin — why can't I see Billing? Admin roles in GHL child accounts control team members and platform settings, but billing permissions are reserved for the parent agency account only. - Can Search Atlas re-enable Billing for my child account? This is not possible by default. The restriction is part of the GHL integration architecture. Your parent agency is the correct point of contact for any plan changes. - My agency is itself a GHL child account — does the same restriction apply to me? Yes. Search Atlas supports multi-level GHL hierarchies, including child-under-child accounts. Billing is always managed at the top-level parent account, so the Billing section will be hidden at every nested level below it. - What if I want to manage my own billing independently? You would need to ask your agency to set you up as a standalone Search Atlas account instead of a GHL child account. Your agency can advise on whether this is an option for your situation. 💬 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.

🔧 Fix Slack Integration Errors in Search Atlas

🔍 Overview Some Search Atlas users encounter errors when setting up or using the Slack integration, including a message stating 'Gemini 3.5 Flash is no longer available.' This article explains why these errors occur and how to resolve them quickly. ⚠️ Common Slack Integration Errors The most frequently reported issues with the Slack integration include: - 'Gemini 3.5 Flash is no longer available' — the AI model previously used for this feature has been deprecated and replaced. - Silent failures after approvals — the integration appears to complete setup but does not return a successful result or confirmation. - Channels not appearing — connected Slack channels may not display as expected within the platform. ✅ Step-by-Step Resolution 1. Refresh the integration: In the left sidebar, go to Coworker → Connectors, and locate Slack. Disconnect the existing connection if one is shown. 2. Reconnect your Slack workspace: Click Connect Slack and follow the on-screen authorisation steps. Make sure you are logged into the correct Slack workspace before proceeding. 3. Verify channel access: After reconnecting, confirm that your Search Atlas agent has been added to the relevant Slack channels inside Slack itself. The agent must be a member of a channel to send or receive messages there. 4. Test the integration: Send a test message or trigger an action through the platform to confirm the connection is working. A successful result will be confirmed on screen. 5. Clear your browser cache: If the integration still does not respond as expected, clear your browser cache and cookies, then reload the platform and repeat the steps above. 💡 Why Did the Gemini Error Happen? The 'Gemini 3.5 Flash is no longer available' error appeared because an earlier version of the AI model powering certain Search Atlas features was deprecated. Our engineering team has resolved this by updating the platform to use a supported model version. No action is required on your part to fix the model itself — the update has already been applied. If you still see this error message, it is likely a cached page. Clearing your browser cache and reloading the platform should resolve it. 🏢 Note for GoHighLevel (GHL) Account Users If you are using Search Atlas through a GoHighLevel (GHL) account and cannot see the Slack integration option in your Settings page, this is expected behaviour. The Slack integration is currently not available for GHL-connected accounts. This is a platform-level restriction and is not related to your subscription tier or permissions. 🛠️ Troubleshooting Checklist - Ensure you have admin permissions in your Slack workspace — without these, the authorisation step may fail silently. - Check that your browser is not blocking third-party pop-ups, as the Slack authorisation flow opens in a new window. - If using a company Slack workspace, confirm that your organisation's Slack admin has approved third-party app connections. - Make sure your Search Atlas account has an active plan that includes AI agent and integration features. 💬 Still Need Help? If you have followed the steps above and are still experiencing issues with the Slack integration, our support team is ready to help. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔗 GoHighLevel Integration: Page Optimization Limit Errors

🧭 Overview If you recently connected your Search Atlas account through GoHighLevel (GHL) and immediately see a 'You've reached the limit to optimize this page' error, your account is most likely still being provisioned. This is a temporary condition that resolves on its own in most cases — no subscription upgrade is required. This article explains why the error appears, what to expect during setup, and the steps you can take right now to resolve it. ⚠️ Why This Error Appears on New GHL Accounts When you create a Search Atlas account through a GoHighLevel integration, your account goes through an automated provisioning process. During this window, your plan limits and feature entitlements are still being configured in the background. Until provisioning is fully complete, the platform may temporarily read your page optimization quota as zero — even on a paid plan — which triggers the limit error. This is a known behaviour specific to GHL-integrated accounts and is not a billing issue or a sign that your plan is incorrect. ⏱️ Typical Provisioning Timeline In the majority of cases, provisioning completes automatically within the following timeframes: - 5–15 minutes: Most accounts are fully provisioned and the error clears on its own. - 15–30 minutes: Accounts created during high-traffic periods may take slightly longer. - Over 30 minutes: If the error persists beyond 30 minutes, manual intervention may be needed (see the section below). We recommend waiting at least 30 minutes after account creation before taking further troubleshooting steps. 🛠️ Troubleshooting Steps 1. Wait and refresh. Allow 15–30 minutes after your account was created, then do a hard refresh of your browser (Ctrl + Shift + R on Windows or Cmd + Shift + R on Mac). 2. Log out and log back in. Sign out of Search Atlas completely, then sign back in. This forces the platform to re-read your current plan entitlements. 3. Clear your browser cache. Cached session data can sometimes cause outdated limit values to persist. Clear your cache, then log in again. 4. Try a different browser or incognito window. This rules out any local browser extension or cache conflicts. 5. Verify your plan in account settings. Confirm that your paid plan is showing correctly under your account profile. If the plan appears as free or inactive, your GHL provisioning may not have completed successfully. 6. Attempt the optimization again. Navigate to Left sidebar → Content → On-Page Audit, select your target page, and try running the optimization. If your account is now fully provisioned, the error will no longer appear. 📋 When to Contact GoHighLevel Support vs. Waiting Use the guidance below to decide whether to wait or escalate: - Wait it out if your account was created less than 30 minutes ago and you have not yet tried logging out and back in. - Contact GoHighLevel support if your account was created more than 30 minutes ago, you have completed all troubleshooting steps above, and your plan still appears inactive or incorrectly provisioned inside GHL's dashboard. GHL support can verify that the agency-level seat or sub-account was activated correctly on their end. - Contact Search Atlas support (via the chat widget below) if your GHL plan appears active and correct inside GoHighLevel but the limit error continues inside Search Atlas after 30 minutes and after completing all troubleshooting steps. ✅ Confirming the Issue Is Resolved Once provisioning is complete, you should be able to: - Run page optimizations from Left sidebar → Content → On-Page Audit without seeing the limit error. - See your correct plan quota reflected in your account settings. - Access all other content tools — including Content Planner, Meta Generator, AI Content Templates, and Topical Maps — in line with your paid 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.

🛠️ Fix ws_bulk_send_message HTTP 403 WebSocket Errors

🔍 Overview When using the Search Atlas AI agent via the Model Context Protocol (MCP), you may encounter a situation where the ws_bulk_send_message tool returns an HTTP 403 Forbidden error on the Website Studio WebSocket channel — even though all other MCP calls complete successfully and your project container appears healthy. This article explains what this error indicates and what information to have ready when escalating to the support team. ⚠️ What the Error Looks Like You may see error output similar to the following when the MCP agent attempts to send messages through the Website Studio WebSocket channel: - Error: ws_bulk_send_message failed — HTTP 403 - Context: WebSocket connection to the SearchAtlas agent channel is rejected - Scope: Only affects ws_bulk_send_message; other MCP tools (such as create_project or read operations) may appear to work normally - Container status: The project container reports as healthy 💡 Why This Happens An HTTP 403 on the ws_bulk_send_message WebSocket channel indicates an authentication or authorization failure during the WebSocket handshake in the Website Studio MCP integration. Because this error occurs at the infrastructure level, it cannot be resolved through client-side configuration changes alone and requires investigation by the support team. ✅ Steps to Take If you are experiencing this error, take the following steps: 1. Refresh your session: Log out of Search Atlas and log back in to clear any stale authentication state that may be cached in your browser or MCP client, then retry the operation. 2. Note your project name: Record the exact name of the Website Studio project you were working in when the error occurred. 3. Capture the exact error message: Copy the full error output returned by ws_bulk_send_message, including any error codes or stack trace details visible in your MCP client. 4. Record the timestamp: Note the date and time (including timezone) when the 403 error occurred so the support team can correlate it with server-side logs. 5. Escalate to support: If the error persists after refreshing your session, contact the support team with your project name, the exact error message, and the timestamp of the failure. This information is required for the team to investigate the WebSocket authentication failure on the backend. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Open Graph Image & Meta Output Issues

🔍 Overview Open Graph (OG) output issues have been reported in the Search Atlas WordPress plugin. This article covers common symptoms users have encountered, and walks you through steps to confirm whether the issue is resolved on your site after updating. ⚠️ Known Issue Users have reported problems with Open Graph image output in the Search Atlas WordPress plugin. Symptoms may include incorrect or missing OG tags, unexpected page layout changes, or featured images not appearing as expected when content is shared. If you are experiencing any of these symptoms, follow the troubleshooting steps below. ✅ Steps to Troubleshoot 1. Update the Search Atlas WordPress plugin to the latest available version. Go to your WordPress dashboard, navigate to Plugins > Installed Plugins, and check for updates next to the Search Atlas plugin. 2. Clear all caches after updating — this includes your WordPress cache plugin, server-side cache, CDN cache, and any Elementor CSS cache. 3. Inspect your Open Graph tags using a tool such as the Facebook Sharing Debugger or the OpenGraph.xyz preview tool. Paste in the URL of a post, an archive page, and your homepage separately. 4. Check archive pages specifically. Visit your blog archive (e.g. /blog/) and confirm that the og:url and canonical tag point to the archive URL — not the URL of an individual post. 5. Verify OG image output. In your page source or a meta tag inspector, confirm that your Open Graph image tag is present and populated correctly. 6. Check your page layout. If you use a page builder such as Elementor, review affected pages to confirm that images and layout elements are rendering at the expected dimensions. 📋 When Escalating If you are still experiencing issues after following the steps above, please have the following ready when you contact support: - The URL(s) of the affected page(s) - A description of the specific symptom (e.g. missing OG image, broken layout, incorrect canonical URL) - Any third-party plugins that may interact with OG output (e.g. page builders, media storage plugins) - Your current Search Atlas plugin version - Any error messages or screenshots you can share If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Stale 'Ask' Results After Deleting BrandVault Images, Videos, or BrandVaults

If you deleted or edited a BrandVault image, video, or an entire BrandVault and still see it referenced in your 'Ask' (bv_ask) AI search results, this is a known issue with a fix already in our release pipeline. This article explains what is happening and how to get your account flagged for follow-up. 🔍 What's Happening in BrandVault 'Ask' Search BrandVault's 'Ask' feature (bv_ask) uses stored content chunks to generate AI answers. When you delete or modify certain assets, some of those chunks can be left behind, so the 'Ask' results still reference content that no longer exists or has changed. You may notice one or more of the following: - Deleted content still appears: images, YouTube videos, or whole BrandVaults you removed are still cited in 'Ask' answers. - Outdated or broken references: 'Ask' results point to assets you already modified, showing stale details. - Duplicate references after alt text changes: regenerating an image's alt text can surface two results that point to the same asset. Who Is Affected This affects customers who use the BrandVault 'Ask' (bv_ask) AI search feature and who have recently deleted or edited BrandVault images, videos, or BrandVaults, or regenerated image alt text. 🛠️ Workaround for Stale BrandVault 'Ask' References There is no self-serve workaround available at this time. Deleting or re-editing the asset again will not clear the orphaned reference, because the leftover chunk needs to be removed on our side. The upcoming fix will clear these orphaned references automatically once it ships, so no manual cleanup will be required from you. 📡 Engineering Status for the BrandVault 'Ask' Cleanup Fix Our team is aware of this issue and a resolution is already in the release pipeline. The fix will automatically clean up the orphaned content chunks left behind after BrandVault image, video, or BrandVault deletions and alt text regeneration. After the fix ships, deleted and modified content will stop appearing in your 'Ask' results, and duplicate references from alt text changes will be removed. 📞 When to Contact Search Atlas Support Reach out to our support team if the stale 'Ask' results are actively affecting your work and you would like priority follow-up. We can flag your account so it is reviewed once the fix is released. When you contact us, please include: - The BrandVault name where you see the stale results. - Whether the affected content is an image, a video, or a full BrandVault. - An example 'Ask' query that returns the outdated or duplicate reference. You'll receive confirmation that your account has been flagged for follow-up. 🎯 Your team isn't alone on this — we're actively on it. The fix to clear these orphaned BrandVault 'Ask' references is on the way, and reaching out to support ensures your account is reviewed as soon as it ships.

🖼️ Why Your Search Preview Logo Still Shows the Old Image

🤔 The Common Mix-Up A frequent question we hear is: "I updated my logo in Search Atlas Brand Vault, but search previews still show the old logo. I've cleared every cache layer and it won't update." If this sounds familiar, the good news is that nothing is broken. The issue is simply that two different features are being confused. Brand Vault and Open Graph serve completely different purposes, and only one of them affects what appears in search and social previews. 🎨 What Brand Vault Actually Does Brand Vault is an internal Search Atlas feature. It stores your brand assets so they appear consistently inside the platform and in the reports and documents you generate. - White-label reports that display your logo instead of ours. - Exported PDFs and dashboards shared with clients. - Consistent branding across the tools you use day to day. Behind the scenes, Brand Vault also feeds Search Atlas's internal Knowledge Graph, which supplies your brand information to AI-powered tools such as OTTO and Content Genius. Note that this internal Knowledge Graph is not Google's Knowledge Graph or Knowledge Panel — despite the similar name, the Search Atlas version lives entirely inside the platform. Brand Vault never edits your live website's code. Because of this, it has no influence over how your site appears in Google search results, link previews, or social media cards. 🌐 What Controls Search and Social Previews The logo or image shown when your page appears in search results or is shared on social platforms is controlled by Open Graph tags and related metadata in your website's HTML. The key tags include: - og:image — the image used for social and link previews. - og:title and og:description — the text shown alongside the image. - Structured data (schema) logo — the logo Google may use in certain search features, such as the Knowledge Panel. - Favicon — the small icon shown next to some search listings. These tags live on your actual website, not inside Search Atlas. Updating Brand Vault will not change them. To update your search preview logo, you must update the metadata on your live site. 🛠️ How to Update Your Search Preview Logo Follow these steps to correct an outdated preview image: 1. Locate the Open Graph tags on your website. These are usually in the page header, managed through your CMS, theme settings, or an SEO plugin. 2. Update the og:image URL to point to your new logo. Make sure the image meets recommended dimensions (at least 1200 x 630 pixels works well for most platforms). 3. Update your structured data logo if your site uses organization schema, so Google references the correct image. 4. Replace your favicon if the small search icon also needs updating. 5. Publish the changes and confirm the new image loads when you view your page's source code. ♻️ Why Clearing Cache Isn't Enough Clearing your website and browser cache is a good habit, but it does not solve this issue on its own. Search engines and social platforms keep their own separate cache of your page metadata. Even after your site is updated, the old image can linger until those external systems refresh. To speed this up: - Use the platform's sharing debugger or validation tools (offered by major search and social networks) to force a re-fetch of your updated metadata. - Request re-indexing of the affected page through your search engine's webmaster tools. - Allow time for search engines to recrawl, which can take anywhere from a few days to a few weeks. ✅ Quick Reference - Logo wrong in Search Atlas reports? Update Brand Vault. - Logo wrong in search or social previews? Update the Open Graph tags and metadata on your website, then trigger a re-fetch. - Still seeing the old image? Give external caches time to refresh and confirm the new image URL loads correctly.

🔗 Fix GHL Blog Integration with Content Genius

🗺️ Overview This article covers two related issues that often occur together during a Search Atlas whitelabel setup: the WordPress plugin connecting to the wrong dashboard URL after a DNS change, and blog content not rendering tables correctly when synced to a GoHighLevel (GHL) site. Follow the sections below in order to resolve both. ⚠️ Before You Start Confirm the following before troubleshooting: - You have completed the DNS record addition in Cloudflare for your whitelabel domain. - You have access to your GoHighLevel site builder and blog settings. - You have the Search Atlas WordPress plugin installed and active on your site. - Your Content Genius workspace is connected to your Search Atlas account. 🌐 Fix 1 — Correct the WordPress Plugin Dashboard URL When you add a whitelabel DNS record in Cloudflare, the Search Atlas WordPress plugin may still point to the original app.searchatlas.com dashboard URL instead of your custom domain. This causes authentication failures and connection errors inside the plugin. 1. Log in to your WordPress admin panel and go to Search Atlas → Settings. 2. Locate the Dashboard URL or API Endpoint field. 3. Replace any existing URL with your whitelabel domain (for example, seo.youragency.com). Do not include a trailing slash. 4. Save the settings and click Test Connection to verify the plugin authenticates successfully. 5. If the connection still fails, clear your Cloudflare cache: log in to Cloudflare, select your domain, go to Caching → Configuration, and click Purge Everything. 6. Wait up to 15 minutes for DNS propagation to complete, then test the connection again. If you see an SSL or certificate error after updating the URL, ensure your Cloudflare SSL/TLS mode is set to Full (Strict) under SSL/TLS → Overview in your Cloudflare dashboard. 📝 Fix 2 — Resolve Tables Not Showing on GHL Blog Content published from Content Genius to a GoHighLevel blog may display missing or broken tables. This happens because GHL's blog editor strips certain HTML table elements that Content Genius exports by default. 1. Open Content Genius in Search Atlas and navigate to the article that contains the table. 2. Switch the editor to HTML / Source view using the toolbar toggle. 3. Check that your table markup uses standard HTML tags: <table>, <thead>, <tbody>, <tr>, <th>, and <td>. Remove any inline style attributes that reference external fonts or CSS variables, as GHL does not inherit these. 4. Copy the full cleaned HTML of the article. 5. In GoHighLevel, open your Sites → Blog section and locate the post. 6. Click Edit Post and switch the GHL editor to HTML/Code view. 7. Paste the cleaned HTML directly. Do not use the visual paste option, as it may reformat the table structure. 8. Save and preview the post to confirm the table renders correctly. If the table still does not appear, check your GHL site's active Theme CSS. Some GHL themes hide table elements by default. Add the following override to your theme's custom CSS section: - Navigate in GHL to Sites → Themes → Custom CSS. - Add: table { display: table !important; width: 100%; border-collapse: collapse; } - Save and republish the page. 🔄 Fix 3 — Re-Sync Content After Making Changes After correcting either the plugin URL or the GHL HTML, re-sync the content to ensure everything is consistent. 1. In Content Genius, open the article and click Publish / Sync. 2. Select GoHighLevel as the destination when prompted. 3. Choose whether to update existing post or create a new draft. 4. Click Confirm Sync and wait for the success notification. 5. Open the live GHL blog post in a new browser tab and confirm both the content and tables display as expected. ✅ Quick Reference — Common Causes and Fixes - Plugin shows wrong URL: Update the Dashboard URL field in WordPress plugin settings to your whitelabel domain. - DNS not resolving: Purge Cloudflare cache and wait up to 15 minutes for propagation. - SSL error on whitelabel domain: Set Cloudflare SSL/TLS mode to Full (Strict). - Tables missing in GHL: Paste clean HTML directly into GHL code view; remove inline styles. - Tables hidden by theme: Add a CSS override in GHL Sites → Themes → Custom CSS. 💬 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.

🔧 Fixing the GoHighLevel CMS Connector When It Won't Sync Your Latest Article Version

📋 Overview If you've updated an article in Search Atlas but your GoHighLevel CMS Connector keeps publishing an older version, even after repeated manual syncs, this guide will help you fix it. In most cases, the problem comes from cached content, an unsaved draft, or a connection that needs to be refreshed. The steps below walk you through the most common causes and how to resolve them. 🤔 Why This Happens The CMS Connector syncs the version of your article that it last recognized as "final." When the latest version isn't pulling through, it's usually because of one of these reasons: - The newest changes were not saved or published inside Search Atlas before syncing. - Cached content on the GoHighLevel side is still serving the previous version. - The connector's authorization token has expired or the connection has drifted. - The article is mapped to the wrong page or post in GoHighLevel. - The sync completed, but the GoHighLevel page cache hasn't refreshed yet. ✅ Before You Start Confirm the following so your sync has the correct content to pull: - You are editing the same article that is mapped to the connector. - Your most recent edits are saved and published in Search Atlas, not left in draft. - You have admin access to both your Search Atlas account and your GoHighLevel sub-account. 🛠️ Step-by-Step Fix 1️⃣ Step 1: Confirm the latest version is published in Search Atlas 1. Open the article in Search Atlas. 2. Check the version history or last-edited timestamp to confirm your changes are present. 3. Click Save and then Publish. A draft that is saved but not published will not sync. 2️⃣ Step 2: Verify the connector mapping 1. Go to Avatar → Settings → CMS Connectors and open your GoHighLevel CMS Connector. 2. Confirm the article is mapped to the correct GoHighLevel page or blog post. 3. If the mapping points to a different or duplicate page, update it to the correct destination. 3️⃣ Step 3: Run a fresh manual sync 1. From the connector screen, select the article. 2. Click Sync and wait for the status to change to Completed. 3. Do not start a new sync until the current one finishes, as overlapping syncs can re-queue the older version. 4️⃣ Step 4: Clear the GoHighLevel cache Even after a successful sync, GoHighLevel may continue serving a cached page. 1. Open the page in GoHighLevel and republish it. 2. View the live page in a private or incognito browser window to bypass your local cache. 3. If you use a CDN or third-party cache, clear it as well. 5️⃣ Step 5: Reconnect the integration If the latest version still isn't appearing, the connection may need to be refreshed. 1. In Avatar → Settings → CMS Connectors, disconnect the GoHighLevel CMS Connector. 2. Reconnect and re-authorize access to your GoHighLevel sub-account. 3. Re-map the article and run the sync again. 🚨 Still Seeing the Old Version? If you've completed all the steps and the connector is still pulling an outdated article, contact our support team and include the details below to speed up resolution: - The article name and its URL in Search Atlas. - The GoHighLevel page or post URL where the old version appears. - The date and time of your most recent edit and your most recent sync attempt. - A screenshot of the connector's sync status. 💡 Quick Tips to Prevent Sync Issues - Always publish your changes in Search Atlas before syncing. - Wait for each sync to finish before starting another. - Refresh the live page in a private browser window to confirm the update. - Re-authorize the connector periodically if you change GoHighLevel passwords or permissions.

Fix Cloudflare Blocking Search Atlas Content Pushes

Overview When your website uses Cloudflare and its Web Application Firewall (WAF) is active, it may block automated content pushes from Search Atlas tools such as OTTO SEO. This happens because Cloudflare does not recognise Search Atlas servers by default and may treat the requests as potential threats. This article explains how to whitelist Search Atlas IP addresses inside your Cloudflare account so content automation works without interruption. Step 1 — Access Your Cloudflare Security Settings Log in to your Cloudflare account at cloudflare.com and select the domain that is blocking your content pushes. From your domain's dashboard, navigate to the security or firewall section where IP-based rules can be managed. If you access Cloudflare through a hosting control panel (such as cPanel), look for a Cloudflare or security option within that panel and open the firewall or IP rules area from there. Step 2 — Add an IP Allowlist Rule for Search Atlas Once you are in the firewall or IP rules area of your Cloudflare settings, create an allow rule for the following Search Atlas IP addresses: - 52.41.36.82 - 52.43.154.161 - 54.69.73.23 For each IP address, set the action to Allow and apply it to your domain. Save your changes once all addresses have been added. Step 3 — Retry Your Content Push After saving the allowlist rules, return to Search Atlas and retry the content push that was previously blocked. In most cases this resolves the firewall block immediately. If the content push still fails after adding all IP addresses, check that the rules have been saved correctly and that no other firewall or security layer (such as a separate hosting-level firewall) is also active on your domain. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚠️ "Clear All Settings" Does Not Reset Media Optimization or Code Minification Settings

A known issue in the Search Atlas WordPress plugin causes Media Optimization and Code Minification settings to remain active after you run "Clear All Settings." Use the steps below to complete the reset manually while a fix is queued for the next plugin update. 🔍 What's Happening When you click Clear All Settings in Advanced Settings → Reset Plugin Settings, the following settings are not cleared and remain in their previous state: - Image Conversion (Media Optimization) - Lazy Loading (Media Optimization) - Dimension Injection (Media Optimization) - All Code Minification settings (Note: the plugin settings do not contain a Code Minification section — available sections are Settings, LLMs.txt, SEO Controls, OTTO cache, Branding, Schema Markup, Search engine verification, Code snippets, and Local SEO.) Both metasync_code_minification and metasync_media_optimization option keys are fully uncleared — not partially — so every sub-setting under each section, not just the master toggle, retains its previous state. Media optimization cache and batch data also remain, leaving the plugin in an inconsistent partial-reset state. Affected versions: all current plugin versions prior to the upcoming fix release. Once the fix is released, the version number will be noted here. 🛠️ Workaround Steps After running Clear All Settings, follow these steps to achieve a complete reset: 1. Click Clear All Settings in Advanced Settings → Reset Plugin Settings to reset all other plugin settings. 2. Navigate to the Media Optimization section in the plugin settings. 3. Disable the Image Conversion, Lazy Loading, and Dimension Injection master toggles. 4. Click Save in the Media Optimization section before navigating away. 5. Navigate to the Code Minification section. 6. Disable or reset every setting in that section. Confirm each toggle and option — including Minify CSS, Minify JS, Minify HTML, and any related sub-toggles — is in its default-off state. 7. Click Save in the Code Minification section. 8. Clear the Media Optimization cache and any pending batch data using the Clear Cache or Reset Batch controls in the Media Optimization section. If no such control is visible in your plugin version, contact Search Atlas Support to clear the cache and batch data on the backend. After saving, your plugin is in the same fully reset state that Clear All Settings is intended to produce. 📡 Engineering Status Our team is aware of this issue and a fix is actively in development. The correction is complete and awaiting release in the next plugin update. This article will be retired once the fix is confirmed live. The tracked fix (WP-357) addresses the uncleared metasync_media_optimization and metasync_code_minification option keys. Cleanup of leftover media optimization cache and batch data is tracked separately — continue to use the cache/batch step in the workaround above until that follow-up is confirmed shipped. 📞 When to Contact Support Contact Search Atlas Support if: - The workaround steps do not fully clear your settings. - You experience unexpected behavior after completing the manual reset. - You need help confirming your plugin is in a clean state before proceeding. 🌀 Our team is actively working on a fix shipping in the next plugin release — the workaround above fully resolves the issue in the meantime, and Search Atlas Support is available anytime if you need hands-on help.

🔌 Using Search Atlas with SiteGround Speed Optimizer

🧩 Compatibility Overview The Search Atlas WordPress plugin is fully compatible with SiteGround Speed Optimizer. You can safely disable LiteSpeed Cache and switch to SiteGround Speed Optimizer without affecting how Search Atlas functions on your site. The two plugins do not conflict, and no special configuration is required to make them work together. 🔄 How to Switch from LiteSpeed Cache to SiteGround Speed Optimizer Follow these steps to migrate cleanly and avoid any temporary performance gaps on your site. 1. Log in to your WordPress admin dashboard. 2. Go to Plugins → Installed Plugins. 3. Locate LiteSpeed Cache and click Deactivate. 4. Once deactivated, click Delete to remove LiteSpeed Cache entirely. This prevents any settings conflicts. 5. If SiteGround Speed Optimizer is not yet installed, go to Plugins → Add New, search for SiteGround Speed Optimizer, then click Install Now and Activate. 6. Open SiteGround Speed Optimizer settings and configure caching, minification, and image optimization according to your preferences. 7. Confirm the Search Atlas plugin is still active under Plugins → Installed Plugins. No reconfiguration is needed. ✅ What Continues to Work Normally After switching caching plugins, all Search Atlas features continue to operate without interruption. This includes: - On-page SEO analysis and audits - Content scoring and recommendations - Keyword tracking and reporting - Any data syncing between your site and the Search Atlas platform SiteGround Speed Optimizer handles front-end performance independently from Search Atlas, so there is no functional overlap between the two plugins. ⚠️ Things to Keep in Mind - Clear your cache after completing the switch. Residual LiteSpeed Cache data can occasionally cause pages to load outdated assets. In SiteGround Speed Optimizer, go to Supercacher → Flush Cache to clear everything. - Test your site after the migration. Load a few key pages and confirm they render correctly and that no console errors appear. - Avoid running two caching plugins simultaneously. Having both LiteSpeed Cache and SiteGround Speed Optimizer active at the same time can cause caching conflicts, slow load times, or broken page layouts. Always deactivate one before activating the other. - If your hosting plan is on SiteGround, SiteGround Speed Optimizer is the recommended caching solution and is optimised for that hosting environment. 🛠️ Troubleshooting After the Switch If you notice any unexpected behaviour after switching plugins, try the following: 1. Clear the SiteGround Speed Optimizer cache and reload your site. 2. Temporarily deactivate SiteGround Speed Optimizer and check whether the issue persists. This helps isolate the cause. 3. Re-check that Search Atlas is still active and that your API connection to the platform is intact by logging in to Search Atlas and confirming data is still populating as expected. 4. If pages look broken, check for minification conflicts. In SiteGround Speed Optimizer, try disabling CSS Minification or JavaScript Minification one at a time to identify the source. 💬 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.

🛡️ Whitelist Search Atlas IPs in cPanel Firewall

🔍 Overview If your website shows a not connected error in Search Atlas, your cPanel firewall may be blocking our servers from accessing your site's data. The most common fix is adding the Search Atlas IP addresses (provided by our support team) to the Remote MySQL whitelist inside cPanel. This guide walks you through the general steps. ⚠️ Before You Begin - You need cPanel access for your hosting account. Log in through your hosting provider's client area or directly via yourdomain.com/cpanel. - You will need the Search Atlas IP addresses ready. Contact our support team to obtain the current list of IP addresses that need to be whitelisted. - If your host uses a custom firewall plugin such as CSF (ConfigServer Security & Firewall), the steps may differ slightly — contact your host's support if you are unsure. 🛠️ Step-by-Step: Remote MySQL Whitelist in cPanel The Remote MySQL tool in cPanel controls which external IP addresses are allowed to connect to your databases. Adding Search Atlas IPs here resolves the most common firewall-related connection errors. 1. Log in to your cPanel account. 2. In the top search bar, type Remote MySQL and click the result, or scroll to the Databases section and click Remote MySQL. 3. In the Add Access Host field, enter each Search Atlas IP address provided by our support team. 4. Click Add Host for each IP. The IPs will appear in the list of allowed hosts below. 5. Once all IPs are added, return to Search Atlas and reconnect your website. The not connected error should be resolved. ✅ Verify the Connection in Search Atlas After whitelisting the IPs, return to Search Atlas and check whether the connection status for your website has updated. If the not connected error is gone and your site shows as connected, the whitelist is working correctly. 🔒 Optional: Whitelist IPs in CSF Firewall (Advanced) If your hosting provider uses CSF (ConfigServer Security & Firewall) in addition to or instead of the cPanel Remote MySQL tool, you may also need to whitelist the IPs at the firewall level. - In cPanel, go to CSF Firewall (found under the Security section if installed). - Enter each Search Atlas IP address provided by our support team and save your changes. - If you are unsure how to do this, contact your hosting provider's support for guidance. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.