Troubleshooting: Publishing & CMS Sync

🔧 Fix WordPress Sync Failures and Gutenberg Errors

🔍 Overview If Search Atlas is reporting a successful WordPress publish but your live site still shows old content, or if your Content Genius articles contain Gutenberg block errors that prevent proper sync, this article explains why these issues occur and what to have ready when escalating to our team. This article also covers duplicate location page generation, which can accompany WordPress sync problems. ⚠️ Common Symptoms - Search Atlas shows a WordPress Post ID and a success status, but the live post still contains outdated or incorrect content. - Content Genius articles display formatting errors, large whitespace gaps, or duplicated bullet points on the published page. - The sync process completes without an error message, yet changes are not reflected in your WordPress editor or front end. - Gutenberg block validation warnings appear inside the WordPress editor after publishing from Search Atlas. - Duplicate location pages are generated unexpectedly during or after a sync operation. 🧩 Why This Happens These issues have a few common root causes: - Stale Post ID mapping: Search Atlas may reference an outdated Post ID from an earlier draft or failed publish attempt, causing WordPress to update a record that does not correspond to the intended live page. - Gutenberg serialization errors: Content Genius generates structured HTML for your article. If that HTML contains unsupported tags or extra line breaks between block boundaries, WordPress's block parser may reject or corrupt the block, causing whitespace gaps, duplicated list items, or a fallback to Classic Block mode. - Duplicate location page generation: Under certain sync conditions, the integration may trigger creation of duplicate location pages rather than updating the existing ones. ✅ What to Do Because these issues require investigation and correction on the backend, please do not attempt repeated re-publishes, as this may compound duplicate page problems. Instead, gather the following information and contact our support team: - Your project name and the specific article or page affected. - The Post ID shown in Search Atlas and the Post ID visible in your WordPress dashboard for the affected post — note whether they match. - The exact error message or block validation warning displayed in your WordPress editor, copied verbatim. - The timestamp of the failed or incorrect sync attempt. - Screenshots of any Gutenberg block errors, whitespace issues, or duplicate pages you are seeing on the live site. - Whether duplicate location pages were created, and if so, how many duplicates exist and their URLs. Our team will investigate the Post ID mapping, Gutenberg serialization, and any duplicate page records on the backend and apply the appropriate 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.

🔍 Blog Post Showing a Fatal Cache Error

This article explains what to do if your blog post is displaying a fatal cache error on your website. This type of error requires direct investigation by our support team to identify the root cause and guide you to the right resolution, as the fix will depend on your specific setup. What Is This Error? A fatal cache error on a blog post typically means something went wrong during the publishing or rendering process, and your site is unable to serve the post correctly. The exact cause can vary depending on your hosting environment, active plugins, and how the post was built. What to Have Ready Before Contacting Support Our support team will need to investigate your case directly. To help us resolve this as quickly as possible, please have the following information ready when you reach out: - The exact URL of the blog post showing the fatal cache error - The exact error message displayed on the page (copy and paste it if possible, or take a screenshot) - The date and time you first noticed the error - The name of your hosting provider - Any recent changes made to the post, your site's plugins, or your theme before the error appeared 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 d15 Validation Loop and Stuck Blog Post Refiner

🔍 What Is Happening? Two related issues can occur inside the Content Genius editor that disrupt your writing workflow: - d15 validation check loop: The system repeatedly flags missing article metadata — such as title, meta description, or keywords — even though all fields appear correctly filled in. - Blog Post Refiner stuck state: After clicking a Refiner action, the interface shows "Working on it" for 10 or more minutes without completing or returning a result. Both issues are linked to an Atlas Agent behavior where recommendation checks can loop endlessly. Engineering is actively working on a fix. ⚙️ Why Does the d15 Validation Loop Happen? The d15 check is part of the Atlas Agent's automated recommendation system inside Content Genius. Under certain conditions, the agent re-evaluates metadata requirements in a continuous loop instead of recognising that the fields have already been set. ⚙️ Why Does the Blog Post Refiner Get Stuck? The Blog Post Refiner relies on the same Atlas Agent pipeline. When the agent enters a loop, Refiner actions can remain in a "Working on it" state indefinitely until the underlying issue is resolved on the engineering side. 🚀 What to Do Right Now These issues are caused by a backend bug that our engineering team is actively investigating. There are no confirmed self-serve steps that fully resolve either issue at this time. To get unblocked as quickly as possible, please reach out to our support team and have the following information ready: - The name of the affected project or article - The exact behavior you are seeing (d15 validation loop, stuck Refiner, or both) - Approximately when the issue started, including the date and time - Any error messages or status text displayed on screen (e.g., "Working on it") Our team will escalate your report to engineering so your case can be linked to the active investigation and prioritized accordingly. 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 Table Display Issues From Content Genius

🔍 Overview When you publish or sync content from Content Genius to WordPress, tables in your article may display incorrectly. Common symptoms include: - Tables appearing as raw HTML code on the published page instead of formatted tables - Tables disappearing entirely after switching between the WordPress Block editor (Gutenberg) and Classic editor - Surrounding text and headings updating correctly while only the table is affected This is a known rendering issue related to how WordPress processes HTML table markup during content sync. The steps below will help you resolve it. ⚙️ Why This Happens Content Genius generates tables using standard HTML (<table> tags). When WordPress receives this markup, it may not convert it into a native Gutenberg block automatically. If you then switch editors — for example, from the Classic editor to the Block editor — WordPress can strip or misinterpret the raw HTML, causing the table to disappear or display as plain code on the front end. ✅ Steps to Resolve 1. Open your WordPress admin panel and navigate to the post that was synced from Content Genius. 2. Do not switch editors. If the post opened in the Classic editor, stay in the Classic editor. If it opened in the Block editor, stay there. Switching between editors mid-edit is the most common cause of tables disappearing. 3. Locate the table in the editor. If it is showing as raw HTML, switch to the Text / HTML view (not the Visual view) in the Classic editor, or use a Custom HTML block in the Block editor, and confirm the full table code is present and intact. 4. In the Classic editor: Make sure you are viewing the post in Text mode (not Visual mode) before saving, so WordPress does not reformat the HTML. Switch back to Visual only after confirming the table code is correct in Text mode. 5. Save or update the post and then preview it on the front end to confirm the table renders correctly. 6. If the table is missing entirely after a previous editor switch, return to Content Genius in Search Atlas and re-sync the article to WordPress. This will restore the original HTML output. 🚀 Re-Syncing From Content Genius If the table content is lost and cannot be recovered from WordPress, re-syncing from Content Genius is the fastest way to restore it. Open your article in Content Genius within Search Atlas and use the WordPress sync option to push the content again. Once re-synced, open the post in WordPress and follow the steps above to ensure the table is not affected by an editor switch before saving. 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 Table and Thumbnail Sync Issues

🔍 Overview When you publish or sync content from Content Genius to WordPress, you may occasionally encounter two display issues: tables appearing as raw HTML code instead of formatted tables, and an article thumbnail showing the wrong image even after you have manually updated it. These are known bugs that our team investigates on a case-by-case basis. This article explains what to expect and how to escalate effectively. 📋 Issue 1 — Tables Rendering as Raw HTML in WordPress Tables created inside Content Genius use standard HTML markup. After syncing to WordPress, the table code may display as plain text rather than a formatted table, depending on how your WordPress environment handles the synced content. This is a known issue that may be related to how the Search Atlas plugin transfers content into WordPress blocks. Because the root cause can vary by environment, our support team will need to investigate your specific case. To help us resolve this quickly, please have the following ready when you contact support: - The exact name or URL of the affected WordPress post or page. - A screenshot showing the raw HTML as it appears on the front end or in the WordPress editor. - The version of the Search Atlas WordPress plugin you currently have installed. - The name of your active WordPress theme and any page builder or caching plugins you are using. 🖼️ Issue 2 — Incorrect Thumbnail Image After Sync After syncing an article from Content Genius, the featured image (thumbnail) in WordPress may show the wrong image. This can persist even after you manually set the correct featured image and save the post. This is a known bug that our team investigates per report. Because the behavior depends on your specific sync configuration, self-serve steps cannot be guaranteed to resolve it. To help us resolve this quickly, please have the following ready when you contact support: - The exact name or URL of the affected WordPress post or page. - A description of what image is appearing versus what image you expect to see. - Whether the incorrect image returns after each sync or only appeared once. - The version of the Search Atlas WordPress plugin you currently have installed. 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 Avatar 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 Avatar 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.

🛠️ Fix Wix Content Genius Publish-Sync Issues

🔍 Overview Some Wix-connected sites experience recurring publish-sync defects when pushing content from Content Genius to their CMS. Known symptoms include stale blog card images, delayed title and alt-text updates, and unexpected H1 page-jump behaviour after content is published. This article explains what causes these issues, how to document them, and how to escalate for engineering investigation. ⚠️ Known Defects and Symptoms The following issues have been identified for Wix integrations and are tracked by our engineering team: - Stale og:image / blog-card image: The featured image shown on blog listing pages or in social previews does not update after a new article is published from Content Genius. - Delayed title and alt-text mutations: The page title or image alt-text set inside Content Genius does not immediately reflect on the live Wix page, sometimes reverting to a previous value. - H1 page-jump after publish: After syncing, the H1 element on the Wix page shifts position or duplicates, affecting both visual layout and on-page SEO signals. These defects are a recurrence of a previously reported integration issue and are actively tracked in our engineering backlog. ✅ Steps to Confirm You Are Affected 1. Open the Content Genius article you recently published to Wix. 2. Confirm the title, H1, and featured image are correctly set inside Content Genius before checking your live site. 3. Open your live Wix blog page and compare the displayed title, H1 text, blog-card image, and og:image (use a social preview tool or inspect the page source) against what was set in Content Genius. 4. Note any discrepancies — specifically whether the image is stale, the title has reverted, or the H1 appears in an unexpected position. 5. Record the URL of the affected page, the article title, and the date and time you published from Content Genius. 📋 Information to Collect Before Escalating Our support and engineering teams can investigate using existing evidence — you do not need to create new screen recordings. However, gathering the following details will speed up resolution: - The full URL of the affected Wix blog post or page. - The Search Atlas project name and the Content Genius article title. - A description of which specific defect you are seeing (stale image, title revert, H1 jump, or a combination). - The approximate date and time the content was published from Content Genius. - Any browser console errors or screenshots you already have — these are helpful but not required. 🔄 What Our Team Does During Investigation Once escalated, our support team coordinates directly with engineering to: - Link your case to the active engineering ticket tracking Wix/Content Genius publish-sync defects. - Reproduce the issue using your project and page details. - Push any available fixes or patches and verify the affected page updates correctly. 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 Genius 500 Error on Hostinger

Overview Some users hosting WordPress sites on Hostinger have encountered a 500 Internal Server Error when attempting to sync articles from Content Genius to their WordPress site using the Search Atlas plugin. This error is typically related to a backend conflict between the Search Atlas plugin and the Hostinger hosting environment. Steps to Resolve the 500 Error Try the following steps in order to resolve the issue on your own before contacting support: 1. Update the Search Atlas plugin. Make sure you are running the latest version of the Search Atlas WordPress plugin. Go to your WordPress admin dashboard, navigate to Plugins > Installed Plugins, and update Search Atlas if an update is available. 2. Deactivate and reactivate the plugin. In Plugins > Installed Plugins, deactivate the Search Atlas plugin, then reactivate it. This can clear authentication or connection state issues that cause 500 errors. 3. Re-enter your API credentials. After reactivating, go to the Search Atlas plugin settings and re-save your API key or authentication credentials to re-establish the connection between Content Genius and your WordPress site. 4. Check for plugin conflicts. Temporarily deactivate all other plugins, then attempt the sync again. If the sync succeeds, reactivate your other plugins one at a time to identify the conflicting plugin. 5. Increase PHP memory limit. Hostinger environments sometimes have low PHP memory limits that can trigger 500 errors. In your Hostinger control panel or via your wp-config.php file, try increasing the PHP memory limit (for example, add define('WP_MEMORY_LIMIT', '256M'); to wp-config.php). 6. Retry the sync. Once you have completed the steps above, return to Content Genius and attempt to sync the article again. If the Error Persists If you have tried all of the steps above and the 500 error continues, please contact our support team with the following information so we can investigate further: - Your WordPress site URL - The article you were attempting to sync - Any error messages or screenshots you can share You can reach our support team through the live chat widget in the bottom-right corner of the platform — type human teammate to reach a member of the team, and we will be happy to assist.

🛠️ Fix WordPress Publishing Stuck in Content Genius

🔍 Overview Some customers find that when they try to publish an article from Content Genius directly to WordPress, the Create button keeps spinning and resets without publishing anything. This guide explains the most common causes and the steps you can take to resolve the issue. ⚙️ Common Causes - Stale generation loop: Content Genius can occasionally get stuck in a background status-polling loop, preventing new publish actions from completing. - Article stuck at Step 1: If article generation did not fully complete, the article may be in an incomplete state that blocks export. - Incorrect WordPress connection: The platform may be referencing an outdated or misconfigured WordPress CMS connector, causing publish requests to fail silently. - Syncing the original draft instead of your edits: A known issue can cause the export to send the original AI-generated draft rather than your latest saved version, which may also interrupt the publish flow. ✅ Step-by-Step Fixes 1. Refresh and check article status. Go to Left sidebar → Content and open the Content Genius listing table. If the article shows a loading or generating status, wait two to three minutes and refresh the page. If it remains stuck, continue to the next step. 2. Save your edits before exporting. Open the article in the editor. Make sure all your changes are saved — look for a confirmation that the latest version is stored. Do not attempt to publish immediately after making edits without saving first. 3. Re-open the article and retry the Create button. Close the article, return to the Content Genius listing table, reopen the article, and click Create again. A fresh session often clears the loop. 4. Verify your WordPress CMS connector. Navigate to Avatar Menu (👤) (avatar) → Settings → CMS Connectors and confirm that your WordPress site is connected correctly. If you see more than one connection for the same site, remove the duplicate and keep only the active one. Do not add a new connection if one already exists — the platform should detect and use the existing connector automatically. 5. Check your WordPress site permissions. In your WordPress admin panel, confirm that the user account connected to Search Atlas has the Administrator role. Author or Editor accounts cannot connect the plugin, and insufficient permissions can silently block publishing. 6. Try publishing a different article. If the issue affects only one article, it may be in a corrupted state. Try creating a new article and publishing that one to confirm your connection is working. Then retry the original article. 7. Clear browser cache or switch browsers. Occasionally a cached session causes button states to freeze. Clear your cache or open Search Atlas in a different browser and attempt the publish again. 🚫 What to Avoid - Do not click the Create button repeatedly. Multiple rapid clicks can create duplicate publish requests and worsen the loop. - Do not disconnect and reconnect your WordPress site unnecessarily. If a valid CMS connector already exists, adding a new one can cause conflicts. - Do not navigate away mid-generation. If an article is still generating (Step 1 progress visible), leaving the page can interrupt the process and leave the article in a stuck state. 💡 Tips to Prevent This Issue - Always wait for article generation to fully complete before opening the editor or attempting to publish. - Save your edits explicitly before clicking Create to ensure the latest version is exported to WordPress. - Keep only one active CMS connector per WordPress site under Avatar Menu (👤) (avatar) → Settings → CMS Connectors. - Use a supported modern browser such as Chrome or Firefox, kept up to date. 🆘 Still Need Help? If you have followed all the steps above and the Create button is still stuck, our team can investigate your specific account and article state. 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 Broken Images and Formatting When Syncing Content Genius to WordPress

📋 Overview When you sync content from Content Genius to WordPress, images sometimes fail to appear and text formatting can look different from what you saw in the editor. This usually happens because of how WordPress imports media and how your theme or page builder handles incoming HTML. The good news: almost every case can be fixed with a few settings checks. This guide walks you through the most common causes and how to resolve them. 🤔 Why This Happens Two separate issues are often grouped together. Understanding which one you are seeing helps you fix it faster. - Missing images: Images may not transfer because the WordPress connection lacks permission to upload media, the image files are hosted externally and blocked, or your media library upload limits are too low. An outdated Search Atlas WordPress plugin can also cause images to break (see the plugin update step below). - Broken formatting: Headings, bold text, lists, or spacing can shift when your WordPress theme, block editor, or a page builder (such as Elementor or Divi) re-renders the incoming HTML. ✅ Before You Start Confirm the basics first. These checks resolve a large share of sync problems. 1. Make sure your WordPress integration is connected in Search Atlas under your project settings, and that the connection status shows as active. 2. Confirm the WordPress user account linked to Search Atlas has an Administrator role, which is required to connect the plugin. 3. Make sure the Search Atlas WordPress plugin is updated to the latest version. An outdated plugin is a known cause of both broken images and incorrect header styling (for example, Elementor styles not applying so all headings render with identical styling). 🖼️ Fixing Missing Images 1. Check media upload permissions WordPress only accepts images when the connected user has upload rights. If your linked account is set to Author or Editor, reconnect using an Administrator account, which is required to connect the Search Atlas WordPress plugin. 2. Confirm images are embedded, not just linked Open the article in Content Genius and make sure each image is added directly into the content rather than referenced by an external URL. Embedded images are uploaded into your WordPress media library during sync, while external links can break if the source becomes unavailable. 3. Review your upload size limits If large images fail silently, your hosting may be blocking them. Ask your host or check your WordPress settings for the maximum upload file size. Increase it if your images exceed the limit, or resize images before syncing. 4. Update the WordPress plugin if images appear broken or show 404 placeholders A bug that caused inline images to be dropped from the post body during sync — leaving broken or 404 image placeholders on the published post even when permissions and file sizes were correct — was resolved in a 2026 update to the Search Atlas WordPress plugin. If your synced images render as broken placeholders, update the plugin to the latest version and re-sync the article before doing further troubleshooting. 5. Re-sync after changes After adjusting permissions, limits, or the plugin version, trigger the sync again from Content Genius. Existing posts update in place, so you will not create duplicates. 🎨 Fixing Broken Formatting 1. Identify what changed Compare the published WordPress post with the Content Genius preview. Note whether the problem is with headings, spacing, lists, or fonts. This tells you whether the issue comes from the theme or the editor. 2. Check your editor type WordPress handles content differently depending on the editor: - Block (Gutenberg) editor: Incoming HTML is converted into blocks. Most formatting transfers cleanly. If text looks unstyled, switch the post to the block editor rather than the Classic editor. - Classic editor: Generally preserves raw HTML well, but may strip certain styling defined by Content Genius. - Page builders (Elementor, Divi, WPBakery): These often override imported formatting with their own templates. This is the most common cause of formatting differences. 3. Adjust page builder behavior If you use a page builder, set new posts to use the default WordPress editor for synced content, or create a clean template that does not override headings and paragraph spacing. Page builders apply their own styles last, which can hide the formatting that synced correctly. 4. Review theme styling Some themes apply custom spacing, fonts, or heading sizes that differ from the Content Genius preview. The content is correct; the theme is simply displaying it with its own design. This is expected behavior and does not require a fix unless the layout is broken. 5. Check for a duplicated title (duplicate H1) If the article title appears twice on the published post, this is a known sync issue. It happened because the title was added both to WordPress's native title field and to the top of the post body. Since most themes render the title field as an H1 in the page header, a matching H1 at the start of the body produced a second one. This was fixed in a 2026 update to the Search Atlas WordPress plugin — update the plugin and re-sync if you still see a duplicated title. 6. Note for synced pages Pages (as opposed to posts) published from Content Genius may currently render with a plain article layout instead of your site's intended page template. This is a known issue our team is actively working on. As a workaround, after syncing a page you can open it in WordPress and assign the correct page template manually. ⚡ Quick Troubleshooting Checklist 1. Confirm the WordPress integration is connected and active. 2. Verify the linked user is an Administrator. 3. Make sure the Search Atlas WordPress plugin is on the latest version. 4. Make sure images are embedded in the content, not externally linked. 5. Check that image file sizes are within your upload limits. 6. Confirm whether a page builder is overriding formatting. 7. Check for a duplicated title (duplicate H1) on the published post. 8. Re-sync the content and review the published post. 🆘 Still Seeing Issues? If images or formatting remain broken after these steps, gather the following details and contact Search Atlas support: - The URL of the affected WordPress post. - The name of your active theme and any page builder you use. - The version of the Search Atlas WordPress plugin installed on your site. - A screenshot comparing the Content Genius preview and the published result. This information helps our team pinpoint whether the problem is with the sync, your WordPress configuration, or your theme, so we can resolve it quickly.

🔧 Fix WordPress Content Genius Sync & Duplicate Pages

Overview When publishing content from Content Genius to a WordPress site, you may encounter issues such as Search Atlas reporting a successful publish but the page content not appearing correctly in WordPress, or duplicate service-area and location pages appearing on your site. These are known areas where WordPress sync, Gutenberg block handling, and duplicate location page creation can go wrong. What to Have Ready Before Escalating Because these issues require investigation on the backend, please gather the following information before reaching out to our team: - The name of the affected project in Content Genius - The URL(s) of the WordPress page(s) affected (including any duplicate pages) - The exact error message or behavior you observed (e.g., a success notification followed by no visible change, a block recovery prompt in WordPress, or multiple pages created for the same location) - The approximate date and time when the publish action was triggered - Whether the issue occurred during a single publish or a bulk publish job - Any WordPress plugins that may interact with the REST API or the Gutenberg editor (e.g., caching plugins, redirect plugins, or custom post type plugins) What to Expect Our team will review the sync logs for your project, identify whether the issue relates to WordPress REST API communication, Gutenberg content serialization, or duplicate post creation from retried publish jobs, and work with you to resolve it. You do not need to manually edit WordPress block markup or delete duplicate pages before speaking with us, as doing so may make it harder to diagnose the root cause. 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 Elementor Formatting Issues After Content Genius Sync

Four fixes resolve the Elementor formatting and image issues that occur when Content Genius syncs raw HTML into WordPress. In most cases the conflict occurs inside WordPress after the content arrives. If none of the fixes below resolve the issue, contact support and mention you have followed this guide so our team can review your specific Elementor and Content Genius configuration. 🔍 Why Formatting Breaks After Content Genius Sync Content Genius sends content to WordPress as raw HTML. When that HTML lands inside an Elementor-managed Page or a custom theme, the page builder's own CSS rules and layout wrappers can override the imported styling, strip spacing, or block images from rendering. This is typically a WordPress/Elementor compatibility issue rather than a problem with the sync itself. Important caveat: These formatting and image issues are not always limited to Elementor — they can persist across multiple themes and may be compounded by Atlas Brain or plugin-level connection issues. Before applying the fixes below, check your CMS connection status as a preliminary step (Avatar Menu (👤) (avatar) → Settings → CMS Connectors) to rule out a disconnected or partially functional connector. 🩺 Known Symptoms This article applies if you are seeing any of the following after a Content Genius sync, so you can self-identify whether these fixes match your situation: - Missing or broken images — images do not render, show as placeholders, or are stripped from the synced content. - Skewed or misaligned layout — spacing, columns, or paragraph margins look broken compared to the source content. - All headers rendering with identical styling — H1, H2, and H3 headings all share the same visual treatment, indicating an Elementor global typography override. ✅ Before You Start: Confirm Elementor Is Active Customers sometimes misidentify their active theme or page builder (for example, reporting "Builder Theme" when Elementor is actually active). Before applying the fixes below, verify Elementor is actually in use on the specific page in question: 1. In WordPress, go to Plugins → Installed Plugins and confirm Elementor is installed and activated. 2. Go to Pages in the WordPress admin and look for the "Built with Elementor" label next to each page to confirm which pages are managed by Elementor. 3. Open the affected page in the WordPress editor and look for the Edit with Elementor launch button at the top of the page, or check the editor URL for action=elementor. This confirms Elementor is the active editor for that specific page, not just installed site-wide. 4. Verify that no OTTO tasks are actively modifying the page content. OTTO-injected changes can mimic Elementor formatting issues and may be incorrectly attributed to the Content Genius sync. Review the OTTO tasks dashboard in Search Atlas to confirm no active tasks are altering the affected page. 🛠️ Fix 1: Use Posts Instead of Pages WordPress Posts use the native content area, which handles raw HTML far more reliably than Elementor-managed Pages. This is the fastest fix for most accounts and the recommended first step. 1. In WordPress, go to Posts → Add New instead of creating a Page. 2. Re-run the Content Genius sync targeting that Post. 3. Preview the Post — formatting and images should render correctly. 🖼️ Fix 2: Switch to a Simpler Elementor Template Elementor's default template applies layout wrappers that conflict with imported HTML. Switching to a minimal template removes those wrappers. 1. Open the Page in the WordPress editor. If using the WordPress block editor (Gutenberg), look for Page Attributes in the right-hand Settings panel under the Page tab. If using the Classic editor, Page Attributes appears in a box in the right-hand sidebar. 2. In the right-hand panel, locate Page Attributes → Template. 3. Select one of these templates, testing in this order: - Default Template — uses the theme's standard layout - Elementor Full Width — removes the sidebar, keeps header and footer - Elementor Canvas — strips all wrappers; useful for isolated testing 4. Click Update and reload the page to check rendering. If content renders correctly on Elementor Canvas, a template wrapper or sidebar widget is the source of the conflict. ⚠️ Note on Elementor global typography: Elementor's global CSS settings can override imported HTML heading hierarchy — for example, causing all headings (H1, H2, H3) to share the same styling. If your synced content's headings all look identical, audit Elementor's global typography settings under Elementor → Site Settings → Typography and adjust the per-heading styles so each level renders distinctly. ⚙️ Fix 3: Disable Optimization and Caching Plugins Temporarily Caching, minification, and image lazy-load plugins can rewrite or defer the HTML and images that Content Genius imports, causing them to appear broken or missing. 1. In WordPress, go to Plugins → Installed Plugins. 2. Temporarily deactivate any of the following if installed: - LiteSpeed Cache - WP Rocket - Autoptimize - Any plugin with "lazy load" or "image optimization" in its name 3. Clear your browser cache and reload the synced page. 4. If formatting is restored, re-enable plugins one at a time to identify the conflict, then configure that plugin to exclude your synced content. 💻 Fix 4: Check for Theme CSS Conflicts Some themes inject global CSS that overrides font sizes, image widths, or paragraph margins inside the WordPress content area. Ask your developer to inspect the synced page in browser DevTools and identify CSS rules that override the imported HTML styles. Scoping or removing those conflicting rules resolves the issue without changing your Content Genius workflow. 🖼️ If Images Are Missing After Sync If images are missing after sync, verify that source images in Content Genius are in a supported format (JPEG or PNG). Unsupported formats (WEBP, AVIF, HEIC, BMP, TIFF, ICO) — as well as corrupt files — will be flagged in Step 3 of the Content Genius workflow with inline errors and will prevent publishing (the Publish button will be disabled until the unsupported images are replaced). If image formats are supported but images still do not render after sync, try the following in order: 1. Regenerate thumbnails — use a plugin such as Regenerate Thumbnails to rebuild WordPress image sizes for the synced media. 2. Re-upload via the WordPress Media Library — manually upload the affected images directly into WordPress, then re-insert them into the synced content to confirm whether the issue is sync-related or media-library-related. 3. Check Elementor version compatibility — confirm your installed Elementor version supports the image block markup being imported. Older Elementor versions may not render newer image block attributes correctly; updating Elementor to the latest stable release often resolves this. 4. Confirm the CMS connector is healthy — a partially disconnected Atlas Brain connector can deliver HTML without successfully transferring image assets, so verify the connector status before retrying. 🔌 If Atlas Brain Reports the CMS Connector as Disconnected If Atlas Brain shows your WordPress connection as disconnected despite the plugin being active, verify the status via Avatar Menu (👤) (avatar) → Settings → CMS Connectors and contact support — this may be a display error and the underlying connection may still be functional. ⏱️ Why the One-Click Sync Button Appears to Fail If the sync button seems unresponsive or times out, the sync may have already completed in the background. This happens when the server response is slow or delayed. 1. Confirm your API key and OTTO UUID are entered correctly in the WordPress plugin settings. 2. After clicking the sync button, wait 30–60 seconds. 3. Refresh the page — if the sync completed, the content will be present even if no confirmation message appeared. If content does not appear after a refresh and your credentials are correct, contact Search Atlas Support. 🆘 Still Stuck? Contact Support If none of these fixes resolve the issue, contact Search Atlas support with your WordPress admin credentials (temporary access) and the URL of the affected page so an agent can investigate the specific theme/plugin conflict. When you reach out, mention you have followed this guide — our team can then review your specific Elementor and Content Genius configuration without retracing the same steps. 🎯 Formatting issues after a Content Genius sync most often originate inside WordPress, not on the Search Atlas side. Start with Posts over Pages, test Elementor templates, and disable optimization plugins one at a time until the conflict is isolated.

🛠️ Fix Wix Content Genius Publish and Sync Defects

🔍 Overview When you publish content from Content Genius to a Wix-connected site, you may notice rendering issues that affect how your page appears in search results and on the live site. This article explains what is known about these defects and what to expect while our team works on a resolution. ⚠️ Known Issues Affecting Wix Integrations Our engineering team has confirmed defects related to how Content Genius syncs post content to Wix, specifically affecting how titles, headings, and image metadata are rendered after publishing. The affected areas include post-render title output and image metadata such as the featured image and associated metadata fields. These issues are actively tracked in our development backlog and are being worked on in priority order. ✅ What You Can Do Right Now Because these defects occur at the platform integration level, there is no self-serve fix that fully resolves the underlying sync behavior. However, you can take the following steps to mitigate the impact while a fix is in progress: - After syncing from Content Genius, manually review the affected post directly in your Wix site editor and check that headings, titles, and image metadata appear as expected. - If you notice incorrect values, manually update those fields within Wix to reflect your intended content until the sync defect is resolved at the platform level. - Note the specific post URL, the exact fields affected, and any error messages or unexpected output you observe, so you can share these details if escalation is needed. 📋 When Contacting Support To help our team investigate and prioritize your case, please have the following ready: - Your project or site name in Search Atlas - The URL of the affected Wix page or post - A description of which fields are incorrect (e.g. title, heading structure, featured image, metadata) - Any screenshots showing the issue on the live page 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 Content Genius Formatting and WordPress Sync Issues

Overview Two common issues affect Content Genius users: generated content appearing in blog post style even when a landing page type is selected, and edits made inside Content Genius not reflecting on the live WordPress site after publishing or scheduling. If you are experiencing either of these problems, our support team can investigate your specific project and configuration to identify the cause and guide you to a resolution. Why Does Content Genius Generate Blog-Style Content for Landing Pages? If your Content Genius output looks like a blog post rather than a conversion-focused landing page, the exact cause depends on your account configuration and the current version of Content Genius. Please reach out to our team so we can review your setup and confirm the correct steps for your situation. When contacting support, please have the following ready: - The project name or URL of the affected Content Genius document - The content type you selected (e.g. landing page, service page, or other) - The topic or brief text you entered - A description of how the output differs from what you expected - Any template or playbook name you used, if applicable Why Don't My Edits Sync Back to WordPress After Publishing or Scheduling? When content published or scheduled inside Content Genius does not appear updated on your live WordPress site, the cause may relate to your WordPress integration settings, page builder compatibility, or how the sync is triggered. These issues can vary depending on your specific WordPress setup and integration configuration. To help our team investigate, please have the following information ready when you reach out: - The name of the Content Genius project and the URL of the WordPress page or post affected - Whether you used Publish or Schedule, and approximately when the action was taken - Any error messages or unexpected behavior you observed - Whether you use a page builder (such as Elementor or another tool) on the affected page - The timestamp of the last sync attempt 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 Content Genius WordPress Publishing Sync Errors

🔍 Understanding the Sync Error When Content Genius displays 'We're unable to sync with your WordPress site', it means the platform cannot establish a connection with one or more of your WordPress domains at the time of publishing. This can affect a single site or multiple connected domains simultaneously. What to Have Ready When You Contact Support This type of sync error requires investigation by our technical team. To help us resolve your issue as quickly as possible, please have the following information ready before reaching out: - The exact error message you are seeing (a screenshot is helpful) - The WordPress site URL(s) affected - The date and time the error first occurred - Whether the issue affects one site or multiple connected domains - Any recent changes made to your WordPress site, hosting environment, or Search Atlas connection 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 Content Genius Publishing Failures with Elementor

🔍 Overview Content Genius in Search Atlas lets you publish articles directly to your WordPress site. When Elementor is your page builder, a few specific conditions must be met before publishing works correctly. This article walks you through the required setup, common failure points, and a step-by-step diagnostic flow so you can publish without errors. ✅ Prerequisites Before You Publish Before attempting to publish from Content Genius, confirm all of the following are in place: - Search Atlas WordPress plugin is installed and activated on your site. Content Genius communicates with your site through this plugin — without it, no publishing connection exists. - The plugin is authenticated with your Search Atlas account. Go to your WordPress dashboard, open the Search Atlas plugin settings, and verify your API key is saved and the connection status shows as active. - Your WordPress user role has publishing permissions. The connected account must have at minimum an Editor or Administrator role. - Elementor is active on the target page template you intend to use. If Elementor is installed but not set as the editor for that post type, the integration will not trigger correctly. - Your site URL in Search Atlas matches your live domain exactly, including the correct HTTP or HTTPS prefix and no trailing slash mismatches. 📋 Step-by-Step: Publishing an Article from Content Genius 1. Open Content Genius and finish writing or importing your article. 2. Click the Publish button in the top-right area of the Content Genius editor. 3. In the publish panel, select your connected WordPress site from the dropdown. If no site appears, your plugin connection is not active — see the section below. 4. Choose your target post status: Draft, Pending Review, or Publish. 5. Select the post category, featured image, and any custom fields required by your theme. 6. Click Send to WordPress. A success confirmation will appear when the article transfers correctly. 7. Go to your WordPress dashboard and open the post. If Elementor is your editor, click Edit with Elementor to apply your template or layout after the content has been received. Important: Content Genius sends article content as a standard WordPress post. Elementor styling and layout are applied inside WordPress after the content arrives — they are not set inside Content Genius itself. Expecting the full Elementor layout to render inside Content Genius is a common misunderstanding. ⚠️ Common Errors and How to Fix Them - "No sites connected" in the publish dropdown — The Search Atlas WordPress plugin is not installed, not activated, or the API key has not been saved. Reinstall the plugin and re-enter your API key from your Search Atlas account settings. - Publish button appears to complete but the post never appears in WordPress — Your domain URL in Search Atlas does not match the actual WordPress site address. Check both your WordPress general settings and your Search Atlas site settings for an exact URL match. - Content arrives in WordPress but Elementor shows a blank or broken layout — This is an Elementor-side issue, not a Content Genius issue. The content was delivered successfully. Open the post in Elementor and apply or reassign your page template. Elementor's Flexbox or Grid Container settings are irrelevant to the Content Genius publishing step. - Authentication error when publishing — Your API key may have been regenerated. Go to your Search Atlas account, copy the current API key, and re-paste it into the Search Atlas plugin settings in WordPress, then save. - Post publishes as wrong post type — Confirm the post type setting in the Content Genius publish panel. Some Elementor themes use custom post types; select the correct one from the dropdown before sending. 🔎 Quick Diagnostic Flow 1. Can you see your site in the Content Genius publish dropdown? No → Fix your plugin installation and API key first. 2. Does the publish action return a success message? No → Check your domain URL match and WordPress user permissions. 3. Does the post appear in WordPress? No → Check your WordPress REST API is not blocked by a security plugin or firewall. 4. Post is in WordPress but layout looks broken? → This is an Elementor template issue inside WordPress, not a Content Genius error. Reassign your Elementor template to the post. 🔗 Backlink Purchase Frequency Best Practices If you are also managing link-building alongside your content publishing, Search Atlas provides dedicated tools under Left sidebar → Authority (Press Releases) for Cloud Stacks and press releases. Here are the recommended frequency guidelines: - Cloud Stacks: Cloud Stacks are best built once per domain or campaign target as a foundational authority layer. You do not need to repeat them frequently. Navigate to Left sidebar → Authority (Press Releases) → Cloud Stacks to set up or review existing stacks. - Press Releases: A cadence of one to two press releases per month is generally safe and effective for most sites. Avoid large sudden spikes in press release volume. Access this at Left sidebar → Authority (Press Releases) (the main Authority page at /outreach/press-release). - Link Lab (Backlinks): For purchased or outreach backlinks, a gradual ramp is always recommended — start with a small number of links per month and increase over three to six months. Sudden large link acquisition can trigger search engine scrutiny. Review your existing backlink profile before purchasing new links by going to More Features → Backlinks → Backlink Research and identify gaps with More Features → Backlinks → Link Gap Analysis. - General rule: Diversify link types across press releases, cloud stacks, and editorial links. Do not concentrate all link-building into one channel in the same period. 💬 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.

🛠️ Recovering Blog Articles Deleted After Image Fix

🔍 What Happened A recent update to Website Studio resolved an issue where blog post image previews were not rendering correctly. In some cases, this fix unintentionally removed published blog articles from customers' blog pages. If you noticed that one or more blog posts disappeared after this update, you are not alone — this was a known platform-side issue that has since been resolved. 📋 What You Should Do First Before contacting support, take a few minutes to gather the following information. This will help our team restore your articles as quickly as possible: - The titles or URLs of the blog articles that went missing - The approximate date when you last saw the articles published on your blog page - Your Website Studio domain or project name so our team can locate your workspace - Any screenshots of the missing articles if you have them (for example, from a previous browser session or a cached version) ⚠️ Why This Happened The root cause was a bug in Website Studio where certain publishing actions — including image preview rendering fixes — could overwrite or remove previously published blog posts. Specifically, the platform was not always preserving all existing blog entries when changes were applied to the site. This has been patched, and new publishing actions should no longer affect previously published content. ✅ Steps to Check Before Escalating 1. Log in to Website Studio and navigate to your blog page to confirm which articles are missing. 2. Check Content Genius — if the articles were originally drafted there, the content may still exist as saved drafts even if they are no longer visible on your live blog page. 3. Review your published content list inside Website Studio to see if the articles appear as unpublished rather than deleted. 4. Try re-publishing any drafts that still exist in Content Genius directly to Website Studio to see if they restore correctly. 💬 How to Get Your Articles Restored If your articles are not recoverable through the steps above, our team can investigate and restore your content on the back end. To get help fast, 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. Please share the article titles, your project name, and any other details you gathered in the checklist above so we can resolve this as efficiently as possible. 🚀 What We Have Fixed Our engineering team has resolved several related blog stability issues in Website Studio, including: - Blog pages that were only keeping one article visible at a time after publishing from Content Genius - Published blog posts rendering as raw XML instead of styled web pages - Blog posts becoming unclickable or disappearing when unrelated site changes were saved - Published blog posts vanishing after a new prompt was submitted in the Content Genius chat These fixes are now live in production. If you experience any of these issues going forward, please report them immediately through the chat widget so our team can investigate. 🛡️ How to Protect Your Blog Content Going Forward - Keep drafts saved in Content Genius so you always have a recoverable copy of your blog content. - Take note of your published article URLs after publishing so you can quickly identify if anything goes missing. - Avoid making multiple simultaneous publishing changes until you confirm each one has saved correctly. - Check your live blog page after any major update or site change to confirm all articles are still visible. 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 'Select Approved Site' Error in Publication Media

🔍 What Is This Error? When creating a Publication Media account in Search Atlas, you may see the following message: "Select at least one approved site to continue." This error means that no approved sites are currently linked to your Publication Media account, so the system cannot proceed with the creation step. 💡 Why Does This Happen? This error occurs for one or more of the following reasons: - You have not yet added any sites to your Publication Media account. - The sites you added are still pending review and have not been approved yet. - A previously submitted site was rejected, leaving no approved sites available to select. - Your account is new and the approval process has not been completed. 🚀 How to Resolve the Error 1. Check your site approval status. Navigate to your Publication Media dashboard and review the status of any sites you have submitted. Sites must show a status of Approved before they can be selected during account creation. 2. Add a site if none exist. If you have not submitted any sites yet, use the Add Site option within the Publication Media section to submit your first domain for review. 3. Wait for approval. After submitting a site, the review process may take some time. You cannot proceed with account creation until at least one site is approved. Check back after receiving a confirmation notification. 4. Resubmit a rejected site. If your site was rejected, review any feedback provided, make the necessary changes, and resubmit the site for approval. 5. Refresh and retry. Once at least one site shows an Approved status, return to the account creation flow, select the approved site, and continue. ⚙️ Tips to Avoid This Error - Always confirm that a site's status is Approved before starting the Publication Media account creation process. - Submit your sites for review well in advance of when you plan to create your account, to allow time for the approval workflow to complete. - If you manage multiple domains, ensure at least one is approved and active before proceeding. 📊 Still Seeing the Error? If you have one or more approved sites but the error still appears, try the following: - Hard-refresh your browser (Ctrl + Shift + R on Windows or Cmd + Shift + R on Mac) to clear any cached data. - Log out of Search Atlas, log back in, and attempt the account creation again. - Try using a different supported browser such as Google Chrome or Microsoft Edge. If the problem persists after following these steps, 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 URL Rewrite and Social Share Thumbnail Mismatch

Overview When sharing a Website Studio project URL on social media, the preview thumbnail may display an incorrect domain (for example, juicynote.com instead of thejuicynote.com). In some cases, this misconfiguration may also be associated with duplicate form submissions. Both issues are related to URL rewrite and domain configuration in your Website Studio project. What Causes This Issue A URL rewrite or custom domain mapping that is not applied consistently across your project can result in a mismatch between the domain visitors see in a social media thumbnail and the domain your project actually lives on. Social platforms read Open Graph (OG) metadata to generate thumbnails, and if that metadata still references an old or alternate domain, the wrong domain may appear in previews. Duplicate form submissions may also occur when more than one domain variant is active for the same project, though the exact mechanism can vary depending on your specific setup. What to Do Because the specific settings and steps needed to resolve URL rewrite and social share thumbnail issues depend on how your Website Studio project is configured, our support team will need to review your setup directly to identify the correct fix. When contacting support, please have the following ready: - The name of the affected Website Studio project - The domain or domains involved (e.g., the incorrect domain appearing in thumbnails and the correct intended domain) - Any error messages or unexpected behavior you have observed, including whether you are seeing duplicate form submissions - The URL you are sharing on social media and the platform(s) where the incorrect thumbnail appears - The approximate date and time the issue started 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 Custom JavaScript Not Showing on Live Site

🔍 Overview Custom JavaScript added through your site's custom code settings should appear in your live site's page source after publishing. If your code is not showing up, a few common causes are usually responsible. This article walks you through general troubleshooting steps to try before escalating to the support team. ✅ Step 1: Confirm the Code Was Saved and Published The most frequent cause of missing custom code is an incomplete save or publish action. 1. Navigate to the custom code or custom scripts section of your platform dashboard. 2. Verify your JavaScript code is present in the correct field. 3. Save any unsaved changes. 4. Publish or apply the changes to push them to your live site. 5. Wait 1–2 minutes, then hard-refresh your live site (Ctrl + Shift + R on Windows or Cmd + Shift + R on Mac) and check the page source again. 🗄️ Step 2: Clear Your Cache Caching at multiple levels — browser, server, or CDN — can prevent updated code from appearing immediately in your live site source. - Browser cache: Perform a hard refresh as described above, or open your site in a private/incognito window. - Server or CDN cache: If your site uses a CDN (such as Cloudflare) or a server-level caching plugin, purge the cache from that service's dashboard and check again. - Platform cache: If your Search Atlas-connected site has a caching layer, clear it and re-check the live source. 📋 Step 3: Check That Your Code Is Valid JavaScript Invalid or malformed JavaScript can cause the code block to be stripped or silently ignored during publishing. - Make sure your code does not contain unclosed tags, mismatched brackets, or syntax errors. - If you are embedding a third-party script, ensure you are pasting the full snippet exactly as provided, including any required opening and closing <script> tags. - Test your snippet in a JavaScript validator or your browser's developer console before adding it to the platform. 🔒 Step 4: Check for Security or Content Policy Restrictions Some hosting environments and security configurations block the injection of inline scripts or scripts from external domains. This is enforced by the server or CDN — not by Search Atlas — and can silently prevent custom code from rendering. - Review your site's Content Security Policy (CSP) headers to confirm external script sources are allowed. - If you are using a security plugin or firewall (such as Wordfence or Sucuri), check whether it is filtering custom script injections. - Contact your hosting provider if you suspect server-level policies are blocking the code. 📩 Still Not Showing? Escalate to Support If you have worked through the steps above and your custom JavaScript is still not appearing in your live site source, the issue may require investigation by the Search Atlas team. To help us resolve it quickly, please have the following ready before reaching out: - The exact JavaScript snippet you are trying to add. - The URL of the live page where the code should appear. - A description of which step you completed and what result you observed. - Any error messages shown in your browser's developer console (right-click the page → Inspect → Console tab). - The timestamp of when you last saved and published your changes. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix WordPress Content Deployment Sync Failures via AI Agent

🔍 Overview When deploying content to WordPress sites through the Search Atlas AI Agent, you may receive a "deployed" confirmation but find that no new pages or posts appear in your WordPress admin dashboard. This article explains why this happens and walks you through the steps to verify your deployment and get your content live. ⚠️ Why This Happens Several known issues can cause the AI Agent to report a successful deployment when content has not actually been published to WordPress: - The AI Agent may confirm deployment without verifying whether the content is live on your site. - An incorrect or duplicate WordPress connection link may be used, bypassing your existing CMS connector. - WordPress cache is not purged after deployment, making it appear as though no content was published even when it was. - Metadata fields such as category and author may be silently ignored during publishing, causing the post to fail validation or save in an unexpected state. - HTML heading styles may not be applied correctly, which can affect how content is saved or rendered in certain page builders such as Elementor. ✅ Step-by-Step: Verify and Resolve Your Deployment 1. Check your WordPress admin dashboard directly. Log in to each affected WordPress site and navigate to Posts or Pages. Filter by All statuses, including Draft and Pending, to confirm whether the content exists in any state. 2. Check your CMS connector in Search Atlas. Go to your Avatar Menu (👤) → Settings → CMS Connectors and confirm that the correct WordPress site is connected. If a duplicate or incorrect connection exists, remove it and reconnect using the official connector. 3. Purge your WordPress cache manually. If your site uses a caching plugin (such as WP Rocket, W3 Total Cache, or LiteSpeed Cache), navigate to the plugin settings and clear the cache. Then reload your WordPress admin to check for new content. 4. Re-deploy the content through the AI Agent. After confirming your CMS connector is correct and your cache is cleared, return to the AI Agent and redeploy the affected pages or posts. Watch for any error messages during the process. 5. Verify category and author assignment. After deployment, open each newly created post in WordPress and confirm that the correct author and category have been assigned. If these fields are blank, update them manually or adjust your deployment settings before re-publishing. 6. Review heading styles if using Elementor. If your site uses Elementor, open the deployed content in the Elementor editor and check that headings (H1, H2, H3) are rendering correctly. Re-apply heading styles if needed before publishing through Elementor. 🔗 Reconnect Your WordPress CMS Connector If the steps above do not resolve the issue, your WordPress connection may need to be reset entirely. Follow these steps: 1. In Search Atlas, navigate to Settings and open the CMS Connectors section. 2. Locate the affected WordPress site and select Disconnect. 3. Re-add the site using the correct WordPress URL and authentication credentials. 4. Test the connection by deploying a single piece of content before attempting a bulk deployment. 💡 Best Practices to Prevent Future Sync Failures - Always verify content in your WordPress admin after deployment, especially for bulk publish operations. - Limit bulk deployments to small batches (three to five posts at a time) until you have confirmed the connection is stable. - Clear your WordPress cache after every deployment session. - Ensure that category IDs and author IDs exist in WordPress before deploying content that references them. - If you use a page builder such as Elementor, test a single post deployment first to confirm compatibility before publishing at scale. 🆘 Still Seeing the Issue? If you have followed all the steps above and your content still does not appear in WordPress after deployment, our team can investigate your specific connector configuration and deployment logs. 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.