Troubleshooting: Other Issues

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

⚠️ "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.

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

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.

🔗 GoHighLevel (GHL) Child Accounts: Why You Can't See Billing or Change Your Plan

🤔 What is a GHL child account? If your Search Atlas account was created through a GoHighLevel (GHL) agency integration, your account is a child account (also referred to as a sub-account in GoHighLevel) linked to a parent agency account. This is automatically set up by the GHL integration. 🚫 Why you cannot see the Billing section Child accounts do not have direct access to Billing in Account Settings. Billing is managed entirely by the parent agency account. This is by design. ⬆️ How to upgrade your plan or add credits You cannot upgrade from inside your own dashboard. You must: 1. Contact the agency that set up your account (the GHL parent account) 2. Ask them to make the plan change or credit addition through their agency portal If you are not sure who your parent agency is, contact Search Atlas support with your account email and ask them to identify the parent account. 🔍 How to tell if your account is a GHL child account - No Billing tab visible in Account Settings - Account was set up through a GoHighLevel agency or white-label partner ⚠️ My new GHL account shows zero credits or quota If a newly provisioned GHL sub-account shows zero quota or credits even though your plan is active, this can be caused by a resync not triggering during account provisioning. This was a known issue that has since been resolved. If you still see zero quota on a newly created account, contact Search Atlas support (or your parent agency) with your account email so the account can be resynced. 🔄 Can I move to a direct Search Atlas account? Yes, but it requires coordination with support. Contact Search Atlas support to discuss migrating your account to a direct subscription independent of the GHL parent.