Troubleshooting: Publishing & CMS Sync

🔧 Fix WordPress Sync Failures and Gutenberg Errors

🔍 Blog Post Showing a Fatal Cache Error

🛠️ Fix d15 Validation Loop and Stuck Blog Post Refiner

🛠️ Fix WordPress Table Display Issues From Content Genius

🛠️ Fix WordPress Table and Thumbnail Sync Issues

🛠️ Troubleshooting Blog Image Validation

This error means the platform could not retrieve or read the image file during validation. Replacing the file with a clean, locally saved copy usually resolves the issue. 🛠️ Step-by-Step 1. Save the image to your device and open it to confirm that it loads correctly. 2. Create a fresh copy in a standard image format such as JPG or PNG. Follow any format or size limits shown by the upload control. 3. Rename the copy using simple letters and numbers, then upload that new file instead of the original. 4. Wait for the upload to finish completely before continuing or saving the blog. 5. If the error returns, try a smaller version of the image or upload a different known-good image to determine whether the issue is limited to the original file. ✅ How to Confirm It Worked The image should display a preview or thumbnail after uploading, and the validation message should disappear. Confirm that the image remains visible in the blog draft after saving or reopening it. 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.

🔄 Troubleshooting WordPress Content Genius Sync Failures

🧭 Overview If your WordPress site was previously syncing blogs through Content Genius but has suddenly stopped, the most common cause is an outdated or misconfigured Search Atlas WordPress plugin. This article walks you through the correct troubleshooting order — starting with the plugin version check — and also covers what to do if you notice invalid backlink data in your account. ⚠️ Before You Start If you have more than one issue to report (for example, a sync failure and unexpected backlink data), please work through each section of this article separately. Both topics are covered below so you do not need to contact support twice. 🔌 Step 1 — Check Your Search Atlas Plugin Version An outdated plugin is the leading cause of WordPress sync failures, even when no backend errors appear in Search Atlas. Complete these steps before anything else: 1. Log in to your WordPress admin dashboard. 2. Go to Plugins → Installed Plugins. 3. Locate the Search Atlas plugin in the list. 4. If an update is available, you will see an Update Now link beneath the plugin name. Click it and wait for the update to complete. 5. If no update prompt is visible, note the current version number and compare it with the latest release provided by Search Atlas. If they differ, deactivate and delete the plugin, then reinstall the latest version by uploading the plugin .zip provided by Search Atlas via Plugins → Add New → Upload Plugin. After updating, return to Search Atlas and attempt the sync again before moving on to the next steps. 🔑 Step 2 — Re-authenticate the WordPress Connection A plugin update sometimes resets the API connection between WordPress and Search Atlas. Re-authenticate to restore it: 1. Inside Search Atlas, navigate to Settings → Integrations → WordPress. 2. Disconnect your site by clicking Remove Site. 3. Click Connect WordPress Site and follow the on-screen prompts to paste your site URL and generate a fresh API key. 4. Save the settings, then trigger a manual sync from Content Genius to confirm the connection is working. 🛠️ Step 3 — Verify Plugin Permissions and Conflicts If the sync still fails after updating and re-authenticating, check for permission or conflict issues in WordPress: - User role: The WordPress account used during integration must have Administrator privileges. Editor or lower roles cannot complete the handshake. - Security plugins: Tools such as Wordfence or iThemes Security can block external API calls. Temporarily disable them and retry the sync to isolate the cause. - Caching plugins: Clear your site cache (W3 Total Cache, WP Super Cache, or your host's built-in cache) after every plugin change before testing again. - PHP version: Search Atlas requires PHP 7.4 or higher. Check your host's control panel and upgrade if needed. 🌐 Step 4 — Confirm Site URL Format A mismatch in URL format is a common but easy-to-miss cause of sync failures: - Make sure the URL saved in Search Atlas matches your site exactly, including whether it uses http or https. The connection only requires a valid domain URL (for example, https://example.com). - If your site recently migrated from HTTP to HTTPS, update the stored URL in Settings → Integrations → WordPress. 🔗 Separate Issue — Invalid Wildfire Backlinks for Your Domain If you have noticed backlinks appearing in your Wildfire backlink data that do not seem accurate or valid for your domain (for example, links shown for onpointservicecompany.com or any other domain that appear incorrect), this is a separate issue from your WordPress sync and requires its own investigation. To report invalid backlink data effectively, please gather the following before contacting support: - The specific domain or URL where the invalid backlinks are displayed. - Screenshots of the backlinks in question inside the Search Atlas dashboard. - The date you first noticed the discrepancy. Our team will cross-reference the data with the index and correct any inaccuracies. Do not disavow or take action on these links until the data has been reviewed and confirmed. ✅ Quick-Reference Checklist Use this checklist to move through the sync troubleshooting steps efficiently: - Search Atlas WordPress plugin is up to date - WordPress connection has been re-authenticated with a fresh API key - WordPress user account used for integration has Administrator role - Security and caching plugins have been tested for conflicts - Site URL format (HTTP/HTTPS) is a valid domain URL in Search Atlas settings - Invalid backlink data documented and reported separately to support 💬 Still Need Help? If you have followed every step above and your WordPress sync is still failing, or if you need your invalid backlink data reviewed, 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. When you start the chat, please include your WordPress site URL, the version of the Search Atlas plugin currently installed, and screenshots of any error messages — this helps our team resolve your issue as quickly as possible.

🔄 Fix WordPress Articles Not Syncing Automatically

🧭 Overview When Search Atlas generates an article, it does not automatically publish it to your WordPress website. Syncing is a separate step you must trigger — either one article at a time or in bulk. This article explains why articles stay in a generated state, how to push them to your site, and what to check if the sync fails. ❓ Why Doesn't the Article Appear on My Website? Search Atlas separates the content creation process from publishing. A status of Generated means the article exists inside the platform but has not yet been sent to your connected WordPress site. This design gives you control over what gets published and when. To make the article live, you need to sync it manually or enable the bulk sync feature. 🖱️ How to Manually Sync a Single Article 1. In the left sidebar, click Content to expand the section. 2. Navigate to the tool where your article was created (for example, Content Planner or AI Content Templates). 3. Locate the generated article in your list. 4. Click the Synchronization option for that article. 5. Select the website page you want to associate with the article. 6. Change the article status to Posted. 7. Confirm the action. The article will be pushed to your connected WordPress site. After a few moments, visit your WordPress dashboard to confirm the post has appeared. It may be saved as a draft or published depending on your sync settings. ⚡ How to Use Bulk Sync for Automatic Synchronization If you manage a large volume of content and want articles to sync without repeating the manual steps each time, the Bulk Sync feature is available. 1. Go to Content → Content Genius in the left sidebar. 2. Select multiple articles using the checkboxes next to each item (these appear for Restore Deleted Articles). 3. Look for the Restore Articles bulk action in the toolbar that appears. 4. Choose your target website and preferred publish status. 5. Confirm the bulk sync. All selected articles will be queued and pushed to WordPress. Bulk sync is especially useful when you have generated a batch of articles through Content Planner and want to push them to your site in one action rather than syncing individually. 🔍 Common Causes of Sync Failures If an article fails to sync or does not appear on WordPress after you trigger the sync, check the following: - WordPress connection is disconnected: Your site may have become unlinked from Search Atlas. Reconnect it by verifying your WordPress integration settings inside the platform. - Incorrect website selected: During the sync step, confirm you selected the correct website from the dropdown. If you manage multiple sites, it is easy to push to the wrong one. - Plugin not installed or deactivated: The Search Atlas WordPress plugin must be installed and active on your site. Log in to your WordPress admin panel and check that the plugin is enabled. - User permissions: The WordPress account connected to Search Atlas must have Administrator role to connect the plugin. - Article status not set to Posted: If you skipped the step of changing the status to Posted, the article remains in a pending state and will not be pushed. - Network or timeout error: Occasionally a sync request may time out. Wait a few minutes and try the sync again. ✅ Quick Checklist Before Contacting Support - WordPress plugin is installed and active on your site. - Your WordPress site is connected in the platform integration settings. - You clicked Synchronization and selected the correct website page. - You changed the article status to Posted and confirmed. - The WordPress user role is Administrator. - You have checked your WordPress dashboard under both Published and Drafts. 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 Blog Post Upload Errors in the Search Atlas WordPress Plugin

📋 Overview If you see an error when publishing or uploading a blog post through the Search Atlas WordPress plugin, the cause is almost always a connection or authentication issue between Search Atlas and your WordPress site. The most common reason is a missing or incorrect Search Atlas API key or a failed one-click authentication. This guide walks you through fixing the error and restoring the plugin connection. ❓ Why This Error Happens The WordPress plugin connects to your site using a Search Atlas API key or one-click authentication rather than a WordPress username and password. If the API key was never generated, was entered incorrectly, or your hosting environment blocks the connection, uploads will fail. Common error messages reported by users include "Could not publish to WP page" and a rest_forbidden error, both of which usually point to the same underlying connection or permission problem. Common triggers include: - No Search Atlas API key has been generated or one-click authentication has not completed. - A security plugin or firewall is blocking the WordPress REST API. - Your WordPress user role does not have permission to publish posts. 🔑 Step 1: Create a WordPress Application Password Application Passwords are built into WordPress 5.6 and later. To create one: 1. Log in to your WordPress admin dashboard. 2. Go to Users > Profile (or Users > All Users and select your account). 3. Scroll down to the Application Passwords section. 4. Enter a name you will recognize, such as Search Atlas, and click Add New Application Password. 5. Copy the generated password exactly as shown, including the spaces. WordPress only displays it once. Paste this password into the Search Atlas plugin connection settings along with your WordPress username and site URL. 🔍 Step 2: If You Cannot Find the Application Password Option If the Application Passwords section does not appear on your profile page, work through the checks below. 🔒 Confirm your site uses HTTPS WordPress hides the Application Passwords feature on sites that are not served over a secure (HTTPS) connection. Make sure your site loads with https:// and has a valid SSL certificate. Once HTTPS is active, refresh your profile page and the section should appear. 🔄 Check your WordPress version Application Passwords require WordPress 5.6 or higher. Go to Dashboard > Updates to confirm your version and update if needed. 🛡️ Look for a security plugin disabling the feature Security plugins such as Wordfence, iThemes Security, or Solid Security can disable Application Passwords or block the REST API. Temporarily review these settings: - Find any option labeled "Disable Application Passwords" and turn it off. - Make sure the WordPress REST API is not blocked or restricted to logged-in users only. 👤 Confirm your user role You must be logged in as an Administrator (or a user with publishing rights) to see and use Application Passwords. Editor and lower roles may not have access. A rest_forbidden error when publishing is a strong sign that the connected user lacks the required permissions or that the REST API is being blocked. 🔌 Step 3: Reconnect the Plugin After creating a valid Application Password, reconnect your site: 1. Open the Search Atlas WordPress integration settings. 2. Re-enter your WordPress site URL, username, and the new Application Password. 3. Save and run a test connection. 4. Try uploading your blog post again. ⚠️ Still Getting an Error? If uploads still fail after completing the steps above, check the following: - Site URL format: Enter the full URL including https:// and no trailing slash. - Hosting firewall: Some managed hosts block external API requests. Ask your host to allow REST API access for trusted services. - Caching: Clear your WordPress and server cache, then try again. - Permalinks: Go to Settings > Permalinks and click Save once to refresh REST API routes. - Existing posts: When updating or re-syncing a post that already exists in WordPress, make sure the article has an assigned author and a selected website, as these are required before an existing post can publish. - Plugin version: Update the Search Atlas WordPress plugin to the latest version. Recent updates improved WordPress REST API error handling and fixed publish failures that occurred when WordPress returned an empty response. 🙋 Need More Help? If the error continues, contact the Search Atlas support team. Please include the exact error message, your WordPress version, the name of any active security plugins, and a screenshot of your plugin connection settings. This information helps us resolve your issue faster.

🛠️ Content Genius Edits Not Saving to WordPress

🔍 What Is Happening Some users have reported that manual edits made inside Content Genius are not carrying over when an article is published or synced to WordPress. Instead of the latest edited version, the original AI-generated draft is exported. Images may also appear slow to load within the editor. This is a known platform bug that has been identified, investigated, and resolved by the Search Atlas engineering team. The fix has been deployed to production. 📋 Who Is Affected - Users who write or edit articles in Content Genius and then publish or sync them to a connected WordPress site. - Users who notice that their saved changes are not reflected in the published WordPress post. - Users experiencing slow image loading within Content Genius articles. ✅ What Was Fixed The engineering team confirmed and resolved two related issues: - Edited content not syncing: When an article was edited after the initial AI draft was generated, the sync and export process was incorrectly shipping the original unedited draft to WordPress instead of the most recent saved version. - Bulk upload not updating published posts: Published WordPress posts could not be updated correctly through the bulk upload workflow. This has also been resolved. - WordPress plugin authentication and content sync: Underlying issues affecting the connection between Search Atlas and WordPress were addressed as part of the same release. 🚀 Steps to Try Now 1. Open your article in Content Genius. 2. Make your edits and confirm they appear as expected in the editor. 3. Save your changes before attempting to publish or sync. 4. Attempt to publish or sync the article to WordPress again. 5. Check your WordPress site to confirm the correct, edited version of the content has been published. Because the fix has been deployed to production, most users should see the correct behaviour immediately. If you previously experienced this issue and your WordPress content still shows the old draft, try re-syncing or re-publishing the article from Content Genius. ⚠️ If the Problem Persists If you complete the steps above and your edits are still not appearing in WordPress, please gather the following before reaching out so our team can investigate quickly: - The title or URL of the affected article. - A brief description of the edits that were not saved or published correctly. - If possible, a screen recording or screenshots showing the discrepancy between the editor and the published WordPress post. 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 support team.

🔌 Content Genius V3 CMS Connector Options Explained

🚨 Important Notice: Universal CMS Connector Unavailable The Universal CMS Connector that previously appeared in Content Genius has been temporarily removed from the platform. This change was made due to API key stability issues that caused unreliable publishing behaviour. Any documentation or guidance referencing this feature is outdated and should be disregarded. If you were directed here by an in-platform assistant that described steps for configuring the Universal CMS Connector, those instructions no longer apply. We apologise for any confusion this may have caused. ✅ Currently Supported CMS Integrations Content Genius V3 currently supports direct, native integrations with the following platforms: - WordPress — connect via your site URL and application password to push posts directly from the Content Genius editor. - Shopify — link your Shopify store to publish blog content without leaving Search Atlas. - Webflow — connect using your Webflow API token to publish to Collections. - Wix — available through the Wix API integration panel inside Content Genius settings. These are the only officially supported integrations at this time. Support for additional platforms is actively being evaluated by the product team. ❓ What If My CMS Is Not Listed? If you use a platform such as Payload CMS, Emdash, Ghost, Contentful, or any other headless or custom CMS, a direct native connector is not currently available inside Content Genius V3. In the meantime, you have two practical options: 1. Copy content manually. Use the Content Genius editor to write and optimise your article, then copy the finished content into your CMS. The editor supports plain text and HTML export to make this straightforward. 2. Submit a platform request. Let our team know which CMS you need. Customer requests directly influence the roadmap priority for new integrations. Use the chat widget described at the end of this article to submit your platform name. 🔧 How to Connect a Supported CMS Follow these steps to connect one of the natively supported platforms: 1. Navigate to Content → Content Genius (What are we writing today?) in Search Atlas. 2. Open or create a document, then click the Publish button in the top-right corner of the editor. 3. Select your CMS from the list of available integrations. 4. Enter the required credentials for your platform. Each integration displays inline instructions for where to find your API token or application password. 5. Click Connect and wait for the confirmation message before publishing. Once a CMS is connected, it is saved to your workspace and available for all future documents without re-entering credentials. 🗺️ What Is Coming Next 💬 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.

🔄 How to Fix Wrong Article Syncing to WordPress

This article explains what to do when syncing from Search Atlas creates a WordPress draft with the wrong article — a different piece of content than the one you were editing. This can happen when the wrong article is active or selected at the moment you trigger the sync. What to Do Because the exact steps to sync an article to WordPress may vary depending on your current Search Atlas interface, the most reliable approach is to: 1. Before initiating any sync, confirm that the article you intend to send to WordPress is the one currently open and active in your Content Genius editor. Visually verify the article title and body content match what you want to publish. 2. Avoid switching between articles or browser tabs between opening the article and triggering the sync action. 3. If the wrong article still appears as a WordPress draft after syncing, close any other Content Genius articles that may be open in additional browser tabs, return to a single tab with the correct article open, and attempt the sync again. 4. If the problem persists after retrying, note the exact article name you intended to sync and the title of the incorrect draft that was created, as this information will help our team investigate. Before Contacting Support To help our team resolve this quickly, please have the following ready: - The name or title of the article you intended to sync to WordPress - The title or content of the incorrect draft that was created in WordPress - The approximate date and time the incorrect sync 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.

🔧 Fix WordPress Content Sync Unexpected Error

🔍 Identify the Issue If you see an unexpected_error popup or the message We're unable to sync with your WordPress site when publishing content, and synced posts show no permalink URLs, the sync process may be failing even though posts are actually publishing. 🛠️ Use the Plugin's Manual Sync Option 1. Log in to the Search Atlas dashboard. 2. Navigate to Left sidebar → Content → Content Genius (What are we writing today?). Use the CMS SYNC column to trigger a manual content sync. 3. Check your WordPress posts list — the content should now appear published with valid permalinks. This manual sync often bypasses the UI issue that incorrectly flags successfully published posts as unsynced. ✅ Verify the Fix After running the manual sync, open a few synced posts in WordPress and confirm they have live permalink URLs. If posts are publishing correctly but the Search Atlas dashboard still shows an error, the issue is likely a display bug that has been resolved in a recent platform update. 📞 Contact Support If Needed If the manual sync does not resolve the issue or errors persist across multiple sites, 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. Provide the affected site URLs and any error screenshots to help us investigate further.

🔧 Fixing the "unexpected_error" When Syncing Content to WordPress

📋 Overview When you push or repost content from Search Atlas to your WordPress site, you may occasionally see an "unexpected_error" message during the sync. When this happens, your changes are not saved to the live page, even though the edit looks complete on your end. This error almost always points to a connection or permissions issue between Search Atlas and WordPress. The good news: it is usually quick to fix. This guide walks you through the most common causes and how to resolve each one. 🔍 Common Causes - The WordPress connection (integration) has expired or been disconnected. - The connected user account no longer has permission to edit or publish the page. - A WordPress security plugin or firewall is blocking the request. - The page or post was deleted, moved to a draft, or had its URL changed in WordPress. - A temporary server timeout caused by very large content or slow hosting. ⚡ Quick Fixes to Try First 1. Wait one to two minutes and retry the sync. Many "unexpected_error" messages are temporary timeouts. 2. If you just triggered a sync from the Search Atlas dashboard (Left sidebar → Content → Content Genius (What are we writing today?) — using the CMS SYNC column), you may instead see a "Request Throttled — Please make another request after 5 minute(s)" notice. This is a normal cooldown — wait the full five minutes before trying again. 3. Confirm the page still exists in WordPress and is published (not in Draft or Trash). 4. Make a small edit again in Search Atlas and resync to confirm the issue repeats. If the error continues, work through the steps below. 🔌 Step 1: Reconnect Your WordPress Integration An expired connection is the most frequent cause of this error. 1. In Search Atlas, go to Settings > Integrations (or the WordPress connection panel for your project). 2. Locate your WordPress site and select Disconnect. 3. Select Connect and sign in to WordPress again, approving the requested permissions. 4. Return to your content and retry the sync. 🔑 Step 2: Check User Permissions in WordPress The WordPress account used for the connection must be allowed to edit and publish content. 1. Log in to your WordPress admin dashboard. 2. Go to Users and open the account connected to Search Atlas. 3. Confirm the role is Administrator or Editor. Author and Contributor roles often cannot update published pages. 4. If the role was recently changed, update it, then reconnect the integration (see Step 1). 🛡️ Step 3: Review Security Plugins and Firewalls Security tools can block automated updates from outside services. 1. Check whether you use plugins such as Wordfence, Sucuri, iThemes Security, or a Cloudflare firewall. 2. Temporarily disable the plugin, or add Search Atlas to its allowlist. 3. Retry the sync. If it succeeds, ask your developer to permanently allowlist Search Atlas so you can re-enable full protection. 🔗 REST API Access Search Atlas updates content through the WordPress REST API. If a plugin or hosting setting disables the REST API, syncs will fail. Confirm the REST API is enabled, or ask your host to enable it. 📄 Step 4: Confirm the Page Still Matches If the page was renamed, moved, or its URL (slug) changed in WordPress after you first connected it, the sync can no longer find it. 1. Open the page in WordPress and copy its current URL. 2. Compare it to the URL shown in Search Atlas. 3. If they differ, reconnect or re-import the page in Search Atlas so it points to the correct destination. 🐢 Step 5: Handle Large or Slow Pages Very large pages, or sites on slower hosting, can time out mid-sync. - Try syncing during off-peak hours. - Split unusually large updates into smaller edits where possible. - Ask your host whether PHP timeout or memory limits can be increased. 💬 Related Sync Messages Not every failed sync returns "unexpected_error." If you see one of the messages below, use the matching guidance. "Article is still being generated. Please wait until generation is complete before publishing" Normally this means the article is not finished generating yet — reopen it and wait until the status shows complete, then sync again. If the message keeps appearing on an article that has already finished generating, this is a known issue our engineering team is actively working on. Contact support with the affected article link so we can publish it for you while the fix is rolled out. Bulk Sync Fails but Individual Sync Works If syncing several articles at once with Bulk Sync to WordPress fails while syncing a single article succeeds, sync the affected articles one at a time as a workaround, and let support know the bulk action failed. 🆘 Still Seeing the Error? If you have completed the steps above and the sync still fails, contact our support team and include the details below so we can investigate quickly: - The URL of the page you are trying to update. - The exact date and time of your most recent failed attempt. - A screenshot of the "unexpected_error" message. - The name of any security plugin or firewall on your site. - The WordPress user role connected to Search Atlas. With this information, our team can pinpoint the cause and get your content syncing again.

📝 Schedule Blog Post Button Disabled in WordPress Synchronize

📝 Overview If you scheduled a blog post for the wrong website inside Content Genius → Content Planner, and when trying to change it the "Schedule Blog Post" button appears disabled (greyed out), this is not a sync error. This happens when required WordPress publishing fields are incomplete. 🧭 Navigation Path Search Atlas → Left Sidebar → Content → Content Planner → open the scheduled post → WordPress Synchronize. 🐾 Step-by-Step Fix 1. Open the scheduled post: go to Content → Content Planner, locate the scheduled post, and open it. 2. Go to WordPress Synchronize: inside the post editor, click WordPress Synchronize. 3. Change Publish Status to Draft: under Publish Status, select Draft. Resetting the status allows the system to reprocess the scheduling configuration. 4. Complete required fields: scroll down and make sure Author, Categories, and Parent (if applicable) are filled in. If any required field is empty, the Schedule button will remain disabled. 5. Click "Schedule Blog Post": once all required fields are filled, the button becomes active. Click it to re-sync and schedule the post correctly. 6. Refresh the page: after scheduling, refresh the page to confirm the updated publishing status reflects correctly in the interface. 🔴 Why This Happens The Schedule button remains disabled when required WordPress fields are empty, or when the publish status wasn't reset before attempting to re-sync. This is expected system behavior and does not indicate a WordPress connection issue. ❓ FAQs - Is this a WordPress sync error? No, it's a required field validation issue. - Do I need support to fix this? No, completing the required fields and refreshing the page resolves the issue. - Will changing to Draft delete the post? No, it simply allows you to reconfigure the publishing settings. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Blog Posts Not Opening or Appearing

🔍 Overview If blog posts on your Website Studio site are not opening when clicked, or newly published posts are not appearing on the blog listing page, this is a known issue that requires investigation by our support team. This article explains what to expect and how to escalate effectively. ⚠️ What Is Happening Some users experience blog posts that fail to open when clicked or do not appear on the blog listing page after publishing. This behavior is not caused by a configuration error on your end — it indicates an underlying bug that our team needs to investigate directly. 📋 How to Escalate Because this is a bug-category issue, our support team will need to look into your account on the backend. To help us resolve this as quickly as possible, please have the following information ready when you reach out: - The name of your Website Studio project or site - The URL of the affected blog listing page - The title or titles of the specific blog posts that are not opening or not appearing - The exact behavior you are seeing (e.g., clicking a post does nothing, posts are missing from the listing page entirely) - When the issue started or was first noticed (date and approximate time, including your timezone) - Any error messages you see, if applicable If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 How to Fix Meta Keywords Blocking CMS Sync

This article explains how to resolve a specific blocker where meta keywords fields prevent you from turning on CMS sync in Content Genius. If your sync toggle is unresponsive or throws an error tied to meta keywords, the steps below will help you identify and clear the conflict so sync can activate successfully. 🛠️ Step-by-Step 1. Open Content Genius: In the left sidebar, go to Content → Content Genius. Make sure you are viewing the article or content piece that has the CMS sync issue. 2. Locate the meta keywords field: Inside the article editor or its settings panel, look for a field labeled Meta Keywords. This field is often found in the SEO metadata or document settings section of the editor. 3. Check for unsupported characters or formatting: Meta keywords fields that contain special characters (such as quotation marks, brackets, or line breaks), excessively long strings, or values copied from an external source with hidden formatting can block sync validation. Clear the field contents entirely and retype clean, comma-separated keywords if you need to keep them. 4. Leave the field blank if not required: If your CMS does not require meta keywords, delete all content from the meta keywords field. Most modern CMS platforms do not use this field, and leaving it empty removes the conflict. 5. Save your changes: Save the article or document after clearing or correcting the meta keywords field before attempting to activate sync again. 6. Attempt to activate CMS sync: Return to the CMS sync toggle or connection option for the article and try enabling it again. The toggle should now respond without the previous error. ✅ How to Confirm It Worked After enabling the sync toggle, look for a confirmation indicator — typically a green status badge, a "Connected" label, or a success notification — within the Content Genius editor confirming the CMS sync is now active. If you open the article again, the sync toggle should remain in the enabled state rather than reverting or showing an error message. You can also verify by checking whether your CMS receives the published or updated content as expected after your next save or publish action. 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.

🔧 Troubleshooting Meta Keywords Blocking CMS Sync

This article explains what to do if the CMS sync toggle appears stuck or unresponsive in relation to your meta keywords settings. 🔍 What Is Happening In some cases, settings related to meta keywords can prevent the CMS sync toggle from turning on. Because no self-serve resolution steps have been documented for this specific issue yet, our support team will need to investigate your account directly to identify and resolve the underlying cause. 🛠️ How to Get This Resolved To help our team resolve this as quickly as possible, please have the following information ready before reaching out: - The exact name of the content item where the CMS sync toggle is not responding. - The meta keywords you have entered (or attempted to enter) in that content item. - A description of what happens when you try to enable the toggle — for example, whether it stays off, flips back, or shows any message. - Any error messages you see, including the exact wording and where they appear. - The approximate date and time when you first noticed the issue. Having these details ready will allow our team to investigate your specific configuration and provide a targeted fix. 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.

🛠️ Content Genius Articles Stuck on WordPress Integration

🔍 Overview Some users experienced an issue where articles created in Content Genius became stuck during generation — showing no progress and never appearing in the dashboard or WordPress — or where the publish action appeared to complete but nothing was actually sent to WordPress. This was a confirmed platform bug (internal ticket CG-2657) that has been investigated, fixed, and deployed to production. ⚠️ Symptoms to Watch For - Article generation gets stuck at the first step and shows no progress. - The article never appears in your Content Genius dashboard after generation. - Clicking the button to publish or push content to WordPress appears to load, then resets without any content being sent. - The issue persists across multiple attempts over an extended period. ✅ Current Status: Fixed The engineering team identified this as a reproducible bug in Content Genius, developed a fix, and deployed it to production. The ticket has been marked Done. If you were affected by this issue, the fix is now live and article creation and WordPress publishing should work as expected. 🚀 Steps to Try Now 1. Navigate to Left sidebar → Content → Content Genius in your Search Atlas platform. 2. Attempt to create a new article using the generation options available on that page. 3. If you are publishing to WordPress, go through the sync or publish flow as normal and allow it time to fully complete. 4. Check your Content Genius dashboard to confirm the article appears after generation. 5. If the article was previously stuck, try regenerating or re-initiating the article — the underlying issue preventing completion has been resolved. 💡 Additional Notes While the core generation and publishing bug has been fixed, the engineering team is continuing to work on related improvements to the WordPress integration. A separate issue where edited Content Genius articles sync the original AI draft instead of the most recently edited version is currently in progress. If you notice your WordPress content does not reflect your latest edits after syncing, this may be related to that ongoing work. To help avoid confusion when syncing content, always confirm that your final edits are saved within Content Genius before initiating a sync or publish to WordPress. 🛠️ If the Problem Persists If you are still experiencing articles getting stuck or failing to publish to WordPress after the fix has been deployed, gather as much detail as possible about what you see on screen — including the step where the process stops and any error messages — before reaching out. This will help the team investigate quickly. 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 the 400 Error When Editing Blog Entries

🔍 What Is This Issue? When editing a blog entry in Search Atlas, you may encounter a 400 error accompanied by a spinning star icon that continues indefinitely without loading the page. This prevents you from accessing or saving your blog content. This article explains what this error means and what to do if you experience it. ⚙️ Why Does This Happen? A 400 error in the Blog Builder indicates that the platform was unable to process a request. Based on known occurrences, this issue has been caused by a platform-side problem affecting blog entry loading — not a setting or configuration on your end. Customers experiencing this error at the same time are typically impacted by the same underlying backend issue. 🚀 What You Should Do Because this is an outage-type issue resolved on the backend, there are no customer-side steps that will reliably fix it. If you encounter this error, please do the following: 1. Note the exact error message — record any error code or text displayed on screen (e.g., "400 Bad Request"). 2. Note the timestamp — record the date and time (including your timezone) when you first encountered the issue. 3. Note the affected blog entry — record the name or URL of the blog entry you were trying to edit. 4. Contact our support team — share the above details so our team can investigate and apply a fix on the backend. ✅ What to Expect Once our engineering team identifies and resolves the underlying platform issue, the Blog Builder will load your entry normally and the spinning star icon will no longer appear. No changes to your blog content or account settings are required on your part. 🛡️ If the Issue Recurs If you see this error again in the future, follow the same steps above and contact support right away with your project name, the exact error message, and the timestamp. Early reports help our team detect and resolve platform issues faster. 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.

📅 Content Genius WordPress Scheduled Posts Not Appearing

🔍 Overview When you deploy content from Content Genius to a WordPress site and receive a Deployed confirmation, you may notice the post or page does not immediately appear in your WordPress admin. This is usually caused by one of three things: the content was scheduled rather than published instantly, a plugin conflict after a recent WordPress update, or a connection issue between Search Atlas and your site. This article walks you through each scenario so you can confirm and resolve the issue quickly. ⚙️ Why This Happens - Scheduled publication: Content Genius allows you to set a future publication date. If a date and time were selected during deployment, the post exists in WordPress as Scheduled, not Published, and will not be visible on your site until that time arrives. - WordPress plugin update conflict: Updates to the Search Atlas WordPress plugin can occasionally disrupt the content sync, causing images or post data to not transfer correctly. - Publish error silently blocked: In some cases, a validation or connection error can prevent publication even when all required fields appear complete. The deployment confirmation is sent, but the post is not created in WordPress. - WordPress REST API or permissions issue: If the WordPress user credentials connected to Search Atlas have changed, or REST API access has been restricted, deployments will fail silently. 🛠️ Step 1 — Check Scheduled Posts in WordPress 1. Log in to your WordPress admin panel. 2. Navigate to Posts (or Pages, depending on what you deployed). 3. In the status filter at the top of the list, click Scheduled. 4. Look for the content you deployed from Content Genius. If it appears here, it is queued and will publish automatically at the set time. 5. If you want it to publish immediately, open the post, go to the Publish panel, change the date to the current date and time, and click Update. 🔎 Step 2 — Confirm the Deployment Details in Content Genius 1. Open Content Genius in Search Atlas. 2. Locate the content piece you deployed and open its details. 3. Check the Publication Date field. If a future date was set, this confirms the scheduled behaviour described above. 4. Verify the correct WordPress site was selected as the destination — it is easy to accidentally select a different connected site. 5. Review the deployment log for any error messages. An error here means the content did not reach WordPress and you will need to redeploy after resolving the issue. 🔌 Step 3 — Check Your WordPress Plugin and Connection 1. In your WordPress admin, go to Plugins and confirm the Search Atlas plugin is active and up to date. 2. If you recently updated the plugin and content stopped syncing, deactivate and reactivate the plugin to reset the connection. 3. Go to the Search Atlas platform, open Settings, and navigate to CMS Connectors. Confirm the site is listed as Connected. 4. If the connection shows an error or is disconnected, re-enter your WordPress credentials to restore it. 5. Once reconnected, return to Content Genius and redeploy the affected content. 🚀 Step 4 — Redeploy If Content Is Missing Entirely If the content does not appear under Scheduled, Draft, or Published in WordPress, the deployment did not complete successfully. Follow these steps to redeploy: 1. Open the content piece in Content Genius. 2. Review and confirm all mandatory fields are filled in — title, content body, target site, and post type. 3. Select Publish Now (unless you intentionally want to schedule it) and click Deploy. 4. Wait for the confirmation message, then immediately check your WordPress admin to verify the post appears. ✅ Best Practices to Avoid This Issue - Always double-check the Publication Date field before deploying — leave it blank or set it to the current date if you want immediate publication. - Keep the Search Atlas WordPress plugin updated and reconnect after any major plugin updates. - After every deployment, do a quick check in WordPress admin under All Posts or All Pages to confirm the content arrived. - If you manage multiple WordPress sites, confirm the correct site is selected in the destination dropdown before deploying. 💬 Still Need Help? If you have followed all the steps above and content is still not appearing in 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.

⚡ How to Fix a WordPress Cache Error on Your Blog Post

This article covers a cache-related display error that can appear after publishing a blog post in WordPress. Because the original support ticket for this issue contained only a topic label — with no documented agent resolution or confirmed root cause — we are not able to provide verified self-serve steps for this specific error at this time. What We Know The reported symptom is: a blog post displaying a WordPress cache error after publishing. The underlying cause and the exact fix applied by our support team have not been documented, so any specific troubleshooting steps would be speculative and could lead you in the wrong direction. What to Do Next To get accurate help with this issue, please contact our support team directly. When you reach out, having the following information ready will help us resolve your issue as quickly as possible: - Your project or site name as it appears in Search Atlas - The exact error message you are seeing (a screenshot is ideal) - The URL of the affected blog post - The date and time the error first appeared - Any recent changes you made to the post or your WordPress setup before the error 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.

🛠️ Fix Canonical URL Errors and Global Blog Styling

🎨 Setting Up a Consistent Look and Feel Across All Blogs Search Atlas does not currently have a single built-in "global blog template" feature that automatically applies one design to every blog. However, you can achieve a consistent look and feel across all your blogs using the workarounds below. 📋 Option 1: Use Brand Vault as Your Style Reference Brand Vault stores your brand assets — logos, color palettes, and font choices — so you can apply them consistently when building or editing each blog. 1. Access Brand Vault: top-right More Features menu (grid icon, next to your account menu) → Brand Vault, or Header More Features menu (apps-grid icon, top-right) → Brand Vault. 2. Confirm your brand colors, fonts, and logo are saved. 3. When creating or editing a blog in Website Studio, open the Brand Vault panel and apply your saved brand assets to match your desired style. 4. Repeat this process for each blog to keep styling consistent. Limitation: Brand Vault does not push styles automatically. You must apply your brand assets manually to each individual blog. 🖌️ Option 2: Apply Custom CSS to Each Blog If you need more precise control over the visual appearance, you can add custom CSS directly to each blog. 1. Open the blog you want to style in Website Studio. 2. Go to Settings within the blog editor. 3. Locate the Custom CSS field. 4. Paste your CSS rules. Use the same CSS code for every blog to keep the look consistent. 5. Save and preview to confirm the styles are applied correctly. Tip: Keep a copy of your CSS snippet in a text file so you can paste it quickly into each blog without re-writing it. 📄 Option 3: Duplicate an Existing Blog as a Starting Point 1. Build and style one blog to your exact specifications. 2. Use the Duplicate option on that blog to create a copy. 3. Rename the duplicate and update its content. 4. Repeat for each additional blog you need. This is the fastest way to maintain a uniform design when creating multiple new blogs from scratch. 🔍 Understanding the "11 Pages Have Multiple Canonical URLs" Error A canonical URL tells search engines which version of a page is the primary one. When Search Atlas detects that 11 pages each have more than one canonical URL defined, it flags this as an error because conflicting canonical signals can confuse search engines and hurt your rankings. ⚠️ Common Causes of Multiple Canonical URL Errors - Duplicate canonical tags in the page source: A canonical tag exists in both the <head> section and an HTTP response header, creating two competing signals. - Pagination misconfiguration: Paginated content (page 2, page 3, etc.) is accidentally self-canonicalizing each paginated URL instead of pointing back to the root page. - Sitemap conflicts: Pages listed in the sitemap have a canonical tag pointing to a different URL, creating a mismatch. - Blog post syndication or duplication: The same content exists at multiple URLs with inconsistent or missing canonical tags. - Plugin or theme conflicts (external sites): If your site is connected to Search Atlas via integration, an external plugin may be injecting additional canonical tags. 🛠️ Step-by-Step: Diagnosing the Error 1. Go to OTTO SEO → Site Audit in the left sidebar of Search Atlas. 2. Open the latest crawl report and filter for Canonical issues. 3. Click into the Multiple Canonical URLs error to see the full list of affected pages. 4. For each affected page, note the conflicting canonical URLs shown in the report. 5. Open your browser and view the page source (Ctrl+U or Cmd+U) to find all <link rel="canonical"> tags in the <head> section. 6. Also check the HTTP headers of the page using a tool such as a browser extension or developer tools to detect header-level canonical tags. ✅ Step-by-Step: Fixing the Error 1. Remove duplicate canonical tags: Ensure only one canonical tag exists per page, placed in the HTML <head>. Delete any additional or conflicting tags. 2. Fix pagination settings: Paginated pages should either self-canonicalize correctly or use rel="next" and rel="prev" markup. Do not have page 2 canonicalize to page 1 unless that is intentional. 3. Align your sitemap: Make sure every URL in your sitemap matches the canonical URL defined on that page. Remove any URLs from the sitemap that are not the canonical version. 4. Check for HTTP header conflicts: If your server or a caching plugin is adding a Link: <URL>; rel="canonical" header, disable that setting to avoid conflicting with your HTML canonical tag. 5. Re-crawl your site: After making changes, return to OTTO SEO → Site Audit and trigger a new crawl to confirm the errors are resolved. 🔄 Verifying the Fix Once the re-crawl is complete, return to the Canonical issues section of the Site Audit report (OTTO SEO → Site Audit). The 11 affected pages should no longer appear under Multiple Canonical URLs. If any pages remain flagged, repeat the diagnostic steps for those specific URLs. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ OTTO Pixel on Webflow: Limitations & Cloudflare Workaround

🔍 Overview OTTO SEO applies on-page optimisations in two ways: source-level injection (changes written directly into the page's HTML source, as with WordPress and Shopify) and client-side injection (changes applied in the browser after the page loads, via the OTTO pixel JavaScript tag). Webflow currently supports only the client-side method, which comes with a set of limitations described below. ⚙️ How OTTO Works on Webflow When you install the OTTO pixel on a Webflow site, the pixel loads in the visitor's browser and applies SEO changes — such as meta titles, descriptions, and structured data — at render time. The raw HTML delivered by Webflow's servers is not modified. This is different from the WordPress and Shopify integrations, where OTTO injects changes directly into the page source before it is served to the browser or to search engine crawlers. ⚠️ Client-Side Limitations on Webflow - Crawler visibility: Some search engine crawlers and SEO audit tools that do not execute JavaScript may not see the changes OTTO applies. - Render dependency: Optimisations only appear after the pixel script has fully loaded and executed, which can introduce a brief delay. - No source-level changes: The underlying Webflow page source remains unchanged, so tools that inspect raw HTML will not reflect OTTO's updates. - Limited CMS field control: Dynamic content managed through Webflow CMS cannot be rewritten at the source level the way it can in WordPress or Shopify. 🗺️ Is a Source-Level Fix for Webflow on the Roadmap? The Search Atlas team is actively exploring deeper platform integrations, including rendering coverage improvements and migration paths for sites on hosted CMS platforms like Webflow. While a native source-level Webflow integration is not available today, it is part of ongoing product investigation. In the meantime, the Cloudflare Worker approach described below is the recommended solution for teams that need changes to land in the actual page content. 🚀 Cloudflare Worker: The Recommended Alternative If your Webflow site is proxied through Cloudflare, you can use a Cloudflare Worker to intercept HTTP responses and rewrite the HTML before it reaches the visitor's browser or a crawler. This effectively bridges the gap between client-side injection and source-level changes. At a high level, the Worker sits between Cloudflare's edge network and the visitor, fetching the original Webflow response and modifying the HTML — injecting OTTO's recommended tags and content — before delivering it. Prerequisites - Your domain is active on a Cloudflare account (Free plan or higher). - Webflow DNS is pointed to Cloudflare (orange-cloud / proxied mode enabled). - You have access to the Cloudflare Workers dashboard. High-Level Setup Steps 1. Log in to your Cloudflare dashboard and navigate to Workers & Pages. 2. Create a new Worker and paste in a transformation script that fetches your Webflow page, parses the HTML response, and injects the meta tags, structured data, or content changes recommended by OTTO. 3. Use the HTMLRewriter API built into Cloudflare Workers to target specific HTML elements (for example, <head> for meta tags) and apply your changes without loading a full DOM parser. 4. Add a Worker Route (for example, yourdomain.com/*) so the Worker intercepts all page requests. 5. Test the Worker using Cloudflare's preview tool and verify the output with a raw HTML inspection tool or a crawler simulator to confirm changes appear in the source. 6. Deploy the Worker and monitor for any performance impact using Cloudflare Analytics. Note: The OTTO pixel should remain installed on your Webflow site alongside the Cloudflare Worker. The Worker handles source-level changes; the pixel continues to manage any dynamic or JavaScript-dependent optimisations. 📊 Comparing Your Options - OTTO pixel only (default): Easy to set up; changes are browser-rendered. Best for sites where crawler JavaScript rendering is not a concern. - Cloudflare Worker + OTTO pixel: Changes land in the HTML source served at the edge. Best for teams that need full crawler visibility and parity with WordPress/Shopify behaviour. - Source-level CMS integration (WordPress, Shopify): Deepest level of control; changes are written directly into the page before delivery. Not yet available for Webflow. 💡 Tips & Best Practices - Always test your Cloudflare Worker in a staging environment or on a single URL route before rolling it out site-wide. - Keep Worker scripts lean — heavy transformations can add latency. Use HTMLRewriter rather than full HTML string replacements wherever possible. - Review OTTO's recommended changes in the OTTO SEO → Site Audit → All Audits section of Search Atlas so you know exactly which elements the Worker needs to inject. - Periodically re-check your Worker output after Webflow publishes site updates, as template changes may affect element selectors. 🆘 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.

🔧 Fix WordPress Sync Errors in Content Genius

What This Error Means When Content Genius displays "We're unable to sync with your WordPress site", it means the connection between Search Atlas and your WordPress installation has been interrupted. This can affect a single site or multiple domains at once. What to Expect WordPress sync errors of this type require investigation and action by the Search Atlas support team on the backend. There are no self-serve steps that reliably resolve this class of error, and attempting to reconnect or change settings without guidance may make diagnosis harder. Our team will look into the connection issue on their end and work to restore publishing functionality for the affected WordPress domain or domains. How to Escalate To help our team resolve this as quickly as possible, please have the following ready when you reach out: - The name of the Search Atlas project where the error is occurring. - The WordPress domain or domains affected (list all if multiple sites are impacted). - The exact error message displayed in Content Genius (copy it verbatim if possible). - The date and approximate time you first noticed the sync error. - Any recent changes made to your WordPress site or credentials around the time the error began. 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.

🛠️ Blog Article Deletion and Repositioning Bug Fix

🔍 Overview A bug was identified and fixed affecting blog articles in Website Studio. Some customers experienced blog articles being unexpectedly removed from their blog page or repositioned within the article list. This article explains what is known about this issue, confirms the current fix status, and tells you what to do if you are still experiencing problems. This was a platform-level bug. No action was required on your part to trigger it, and the fix has been deployed by the Search Atlas team. ✅ Current Fix Status The blog article deletion and repositioning bug in Website Studio has been resolved at the platform level. If you published blog articles and noticed they were missing or out of order, this has been addressed. You do not need to take any technical action on the backend. 📋 What to Do If Your Articles Are Still Affected If your blog articles are still appearing out of order or missing after the fix was deployed, please escalate so the team can investigate your specific account. Before reaching out, have the following ready to speed up resolution: - The name of your project or workspace in Search Atlas - The titles of the affected blog articles - A description of the problem you are seeing (e.g., articles missing entirely, articles appearing at the wrong position in the list) - Any approximate date and time when you first noticed the issue - Screenshots of the current state of your blog page in Website Studio, if possible The support team will be able to review your account directly and take any necessary backend action to restore your article order or recover missing entries. 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 Duplicate H1 Titles When Syncing to WordPress

🔍 What This Article Covers When publishing content from Content Genius to WordPress, some users experienced a duplicate H1 title appearing in their posts — meaning the article title showed up twice on the page. Additional formatting errors were sometimes present alongside this issue. This article explains what to do if you are still seeing it. ⚙️ What Was Causing the Problem This was a confirmed platform bug specific to posts published or synced through Content Genius — manual posts created directly in WordPress were not affected. The duplicate H1 title appeared as a result of the Content Genius sync process. ✅ Current Status This bug has been resolved on the platform side. New posts published or synced from Content Genius to WordPress should no longer produce duplicate H1 titles. If you are still seeing a duplicate H1 on a newly published post, try the following steps before contacting support: 1. Disconnect and reconnect your WordPress integration inside Search Atlas under Account Menu > Settings > CMS Connectors. 2. Re-publish or re-sync the affected post from Content Genius. 3. Clear your WordPress and browser cache, then reload the post to confirm the duplicate is gone. 🧹 What To Do With Already-Affected Posts Posts that were published before the fix may still contain a duplicate H1. You will need to manually remove the extra title from those posts: 1. Open the affected post in your WordPress editor. 2. Locate the duplicate H1 title — it will typically appear at the top of the body content, immediately below the post title field. 3. Delete the duplicate heading so only one H1 remains. 4. Save or update the post. 💡 Still Seeing Duplicate H1 Titles? If the steps above do not resolve the issue, please contact our support team via the chat bubble in your Search Atlas dashboard. Share the affected post URL and a brief description of your publishing workflow so our team can investigate and assist you directly.

🔧 Fix wp_client_error When Syncing Content Genius to WordPress

What This Article Covers When syncing an article from Content Genius to WordPress, you may encounter a wp_client_error and find that the sync fails. The WordPress plugin may appear to be working correctly on the WordPress side, yet the sync still does not complete. What Causes This Error? This error occurs when there is a problem with the WordPress connector connection between your site and the Search Atlas platform. Because the specific cause can vary between accounts and connector configurations, our support team will need to investigate your setup directly to identify and apply the correct fix. What to Have Ready When You Contact Support To help our team resolve this as quickly as possible, please have the following information ready before reaching out: - Your project name and the specific article(s) you were attempting to sync when the error occurred. - The exact error message displayed (e.g., wp_client_error) and where it appeared in the platform. - The date and time of the failed sync attempt. - Whether the WordPress plugin appears connected or shows any errors on the WordPress side of your dashboard. - Any recent changes made to your WordPress site, hosting environment, or connector settings prior to the error. Still Experiencing Issues? If you are seeing the wp_client_error, please reach out to our support team via the chat icon in the Search Atlas platform so we can investigate your specific connector configuration and apply the correct fix. We're happy to help!

🖼️ Fixing AI Image Creator Not Populating Blog Images

🔍 Overview The AI Image Creator inside the Content Assistant lets you generate and insert images directly into your blog posts. In rare cases, generated images may not appear in the post body. This usually happens because of a browser issue, a temporary connection problem, a version/sync conflict, or a large or unsaved document. The good news is that this is almost always fixable in a few steps. ⚙️ Common Causes If your AI-generated images are not populating in a blog post, one of the following is usually responsible: - Browser cache or extensions interfering with image loading. - Unstable or slow internet connection interrupting the image request. - Unsaved content preventing the image from attaching to the post. - Very large documents that slow down rendering. - A temporary service delay while the image is being generated. - A version/sync conflict — such as a "Page updated elsewhere" or "version mismatch" message — when the editor is being edited in more than one place at once. 🛠️ Step-by-Step Fixes Work through these steps in order. Most issues resolve after the first few. 1. Save your document first. Before generating images, make sure your blog post is saved. Unsaved posts can prevent new images from attaching. 2. Refresh the page. Reload the Content Assistant and try generating the image again. This clears temporary display glitches. 3. Clear your browser cache. Old cached data is a frequent cause of images failing to load. Clear the cache, then reopen the platform. 4. Disable browser extensions. Ad blockers, privacy tools, and script blockers can stop images from rendering. Temporarily disable them and try again. 5. Try an incognito or private window. This opens the platform without extensions or cached data, helping you confirm whether the issue is browser-related. 6. Check your internet connection. A weak or interrupted connection can stop the image request from completing. Switch networks if possible and retry. 7. Avoid editing the post in multiple tabs or windows. Working on the same post in more than one place can trigger a version conflict that stops an image from being added. Close extra tabs, refresh, and generate again. 8. Wait and regenerate. If the service is temporarily busy, wait a minute and generate the image again. 💡 Why Multiple Browsers Show the Same Problem Some customers notice the issue persists across Chrome, Brave, and Safari. When the same problem appears in every browser, it usually points to something other than the browser itself — most often an unsaved document, a network issue, a version conflict, or a very large post that is slow to render. In these cases, saving the post and reducing its size often resolves the problem faster than switching browsers. 📝 Tips for Long or Complex Posts Very detailed guides — for example, a complete SEO guide with many sections — can be large enough to slow down image insertion. If you are working on a long post, try these adjustments: - Save the document frequently as you build it. - Generate and insert images one at a time rather than in bulk. - Give each image a moment to fully load before generating the next. - Avoid making other edits while an image is being created. ✅ Confirming the Fix After completing the steps above, generate a new image and confirm that it appears in the post body. If it displays correctly, save your document again to make sure the image is stored with your content. Additional Notes Try a different supported browser (e.g., if using Brave or Safari, switch to Chrome). If images appear in the alternate browser, re-enable extensions one at a time to identify the conflict.