🛠️ Troubleshooting

📅 Content Planner Troubleshooting

This article covers: - Content Planner scheduling - Calendar visibility - Content brief generation - Publishing workflows - CSV imports - Team collaboration Content Planner helps teams: - Organize publishing schedules - Generate SEO content briefs - Coordinate workflows - Manage topic planning across projects and campaigns Content Planner integrates with: - Keyword Research - Supported CMS connections (e.g., WordPress) - AI Brief Generation - Project-level permissions Many issues are caused by: - Project mismatches - Missing metadata - Formatting errors - Synchronization delays ⚠️ Known Limitation: Direct publishing from Content Genius/Content Planner to Website Studio sites is not currently available. This integration is in development with no confirmed release date. In the meantime, you can publish through a connected WordPress CMS or manually copy content into your Website Studio site. ⚠️ Error 1: Scheduled content items are not appearing on the calendar What's happening Content Planner displays content items based on: - the currently selected project - visibility filters - and active calendar views. Items created under different projects remain hidden unless the correct project is selected. The Content Planner shows the content of the one project/plan currently selected, not all projects at once. Steps to try 1. Confirm the correct project is selected in the Project dropdown. 2. Refresh the calendar page. 3. Check whether date filters are hiding the content item. 4. Verify the item was saved successfully. 5. Confirm the content item has a valid publish date assigned. Items without an assigned publish date will not appear in monthly or weekly calendar views. Switch to List view to locate undated items and assign a date. 6. Switch between monthly, weekly, and list views — some items may only appear in list view if they lack a publish date or if the calendar view is filtering by a date range that excludes them. 7. Check whether the item was accidentally archived or deleted. 8. Confirm the item belongs to the current workspace/team. 9. Contact support if calendar items disappear across all projects. Important Notes - Project filtering is the most common cause of missing calendar items. When the wrong project is selected, items created in other projects will remain hidden until you switch projects. The Content Planner shows only the currently selected project. - Items are isolated by project structure intentionally to keep workspaces organized and prevent cross-project clutter. ⚠️ Error 2: Content brief generated from the planner is missing or empty What's happening Content briefs rely on: - associated target keywords - keyword data availability - and successful AI brief generation. Items without target keywords cannot generate meaningful briefs. Steps to try 1. Open the calendar item settings. 2. Confirm a Target Keyword is assigned. 3. Use a keyword with measurable search data. 4. Click Generate Brief again after saving the keyword. 5. Wait 30–60 seconds for generation to complete. 6. Refresh the item after generation finishes. 7. Avoid extremely broad or unsupported keywords. 8. Test the keyword in Keyword Research first. 9. Regenerate the brief using a more specific keyword phrase. 10. Contact support if briefs remain empty despite valid keywords. Important Notes - Brief generation depends heavily on keyword quality. - Missing keyword data produces incomplete or blank briefs. ⚠️ Error 3: Published content is not being automatically marked as complete What's happening Content Planner does not always detect publishing automatically unless: - CMS Integration is connected - synchronization is enabled - and the publish event is recognized correctly. Manual publishing outside integrated workflows may not sync automatically. Steps to try 1. Manually update the item status: Status → Mark as Published. 2. Check whether CMS Integration is enabled. 3. Go to: CMS Integration → Settings → Sync to Content Planner. 4. Confirm the connected CMS matches the project domain. 5. Refresh the Content Planner after publishing. 6. Verify the published URL matches the planned content URL. 7. Reconnect the CMS integration if sync appears broken. 8. Wait a few minutes for synchronization delays. 9. Avoid duplicate calendar entries for the same URL. 10. Contact support if automatic sync never updates published items. Important Notes - Manual publishing workflows require manual status updates unless sync is enabled. - CMS synchronization can take several minutes. ⚠️ Error 4: Content Planner shows a duplicate topic conflict warning What's happening The planner compares: - target keywords - semantic similarity - and planned topics to prevent content cannibalization. Similar keywords trigger warnings automatically. Steps to try 1. Click View Conflicting Item to inspect the overlap. 2. Compare the keyword intent between both items. 3. Determine whether the topics truly compete. 4. Merge duplicate content plans if appropriate. 5. Differentiate the angle or search intent if keeping both. 6. Use more specific target keywords. 7. Add modifiers to distinguish the content: - guide - comparison - local - pricing - tutorial - etc. 8. Review whether one item is outdated or unnecessary. 9. Ignore the warning only if the content serves different intents. 10. Re-run keyword validation after adjusting the topic. Important Notes - Duplicate warnings are preventive, not blocking errors. - Similar keywords do not always equal cannibalization. ⚠️ Error 5: Team member cannot see the Content Planner items created What's happening Content Planner visibility depends on: - project permissions - workspace access - and team role settings. Users without access to the specific project or workspace will not see items created within it, even if they belong to the same organization. Steps to try 1. Confirm the team member has been added to the correct project. 2. Verify their assigned role grants Content Planner access. 3. Ask the team member to switch to the correct project in the Project dropdown. 4. Refresh the calendar after permission changes are applied. 5. Re-invite the team member if their account was recently added. 6. Confirm the items were not accidentally created in a personal or private workspace. 7. Contact support if access issues persist after role adjustments. Important Notes - Project and workspace permissions are the primary driver of visibility issues for team members. - Role changes may take a few minutes to propagate. ⚠️ Error 6: WordPress shows as connected but publishing fails with a "website not connected" error What's happening The WordPress integration can appear connected in the interface while the underlying credentials or authentication tokens have expired or become invalid. This causes publish attempts to fail with a "website not connected" error even though the connection status looks healthy. Steps to try 1. Disconnect the WordPress integration from Avatar Menu (👤) → Settings → CMS Connectors. 2. Reconnect the WordPress site and re-authenticate. 3. Verify CMS credentials (username, application password, or API token) are still valid in WordPress. 4. Confirm the WordPress site URL matches the project domain. 5. Check that the WordPress user account has publishing permissions. 6. Retry the publish action after reconnecting. 7. Contact support if the issue persists after reconnecting the integration. Important Notes - A visually connected WordPress integration does not always mean the credentials are still valid. - Disconnecting and reconnecting forces a fresh authentication and resolves most "website not connected" errors. ⚠️ Error 7: Publish action hangs or takes longer than expected What's happening Publish actions can take several minutes depending on: - CMS response times - platform-level processing delays - and synchronization queues. If publishing to a Website Studio site appears to hang or takes longer than expected, this may be a platform-level delay. Wait several minutes and check the published URL before retrying, as duplicate publish attempts can compound delays. Steps to try 1. Wait several minutes before retrying — the publish may still be processing. 2. Check the published URL directly to confirm whether the content actually went live. 3. Avoid clicking Publish multiple times, which can create duplicate publish attempts. 4. Refresh the Content Planner to see if status has updated. 5. Verify the CMS connection is healthy in CMS Integration settings. 6. If the publish still appears stuck after 10+ minutes, mark the item manually using Status → Mark as Published once you confirm the URL is live. 7. Contact support with the item ID if the publish never completes. Important Notes - Publish delays are most often platform-level and resolve without intervention. - Always verify the live URL before retrying to avoid creating duplicate posts. ❓ FAQ: Can I publish Content Planner or Content Genius articles directly to Website Studio? Not yet. Direct publishing from Content Planner or Content Genius to Website Studio sites is not currently available. This integration is in development with no confirmed release date. Available alternatives: - Publish through a connected WordPress CMS if your project uses WordPress. - Manually copy the finalized content from Content Genius/Content Planner into the Website Studio editor. - Track publishing status manually in Content Planner by setting Status → Mark as Published once the article is live on your Website Studio site. If direct Website Studio publishing is critical to your workflow, contact support to be notified when the integration becomes available.

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

✍️ Content Rewriting & Press Release Troubleshooting

✍️ Content Rewriting & Press Release Troubleshooting This article covers: AI rewriting generation, rewrite queue delays, semantic drift, plagiarism similarity, brand voice alignment, keyword preservation, language configuration, rewrite processing failures, and Press Release publication issues (including typos, retractions, and credit refunds). Content Rewriting is designed to: paraphrase content, improve readability, create alternate versions, reduce duplication, and adapt tone or structure while preserving the original meaning as closely as possible. Because rewriting uses large language models: outputs vary between generations, semantic interpretation can shift, and rewrite quality depends heavily on: source clarity, rewrite intensity, formatting, and content complexity. ⚠️ Error 1: Rewrite button is not responding after clicking What's happening Rewrite requests are processed through a background AI queue. During peak traffic periods: requests may remain queued temporarily, processing workers may delay execution, and the UI may appear unresponsive while the task initializes. Steps to try - Wait at least 10–15 seconds after clicking Rewrite. - Avoid clicking the button repeatedly during queue processing. - Refresh the page if nothing happens after 30 seconds. - Rewrite smaller sections instead of entire articles. - Keep rewrites under 500–800 words for fastest processing. - Close unnecessary browser tabs to reduce memory load. - Try Chrome if another browser is producing UI delays. - Disable browser extensions that interfere with scripts. - Retry during off-peak hours if queues remain slow. - Contact support if rewrite tasks never start across multiple projects. Important Notes - Queue delay does not necessarily indicate failure. - Large rewrites process significantly slower than small sections. ⚠️ Error 2: Rewritten content has a completely different meaning from the original What's happening Semantic drift occurs when: source content is ambiguous, technical language lacks context, or rewrite intensity is too aggressive. The AI may reinterpret the meaning instead of paraphrasing it closely. Steps to try - Set Rewriting Intensity to: Light or Moderate. - Rewrite one section at a time instead of the full article. - Simplify unclear or highly technical sentences before rewriting. - Use shorter paragraphs for more stable rewrites. - Compare outputs using Compare View after generation. - Restore important terminology manually if needed. - Avoid stacking multiple rewrites on the same text. - Add context before rewriting technical sections. - Use Heavy Rewrite only for major structural changes. - Manually QA all rewritten factual statements before publishing. Important Notes - Smaller rewrite chunks preserve meaning more accurately. - Aggressive paraphrasing increases semantic drift risk. ⚠️ Error 3: Rewritten content does not match my brand voice What's happening Without Brand Vault integration: rewriting defaults to generic language patterns, neutral tone, and generalized phrasing. Brand voice guidance only applies when: a Brand Vault is selected and the rewrite session starts with that vault enabled. Steps to try - Select the correct Brand Vault before starting the rewrite session. - Verify the Brand Vault contains tone, style, and terminology guidelines. - Re-run the rewrite after enabling the vault if it was missed initially. - Manually adjust phrasing post-rewrite if brand alignment is critical. ⚠️ Error 4: Press Release contains a typo or incorrect information (e.g., wrong location, name, or detail) What's happening Press Releases distributed through Search Atlas follow a one-way publication workflow. Once a PR moves out of draft and is submitted to the distribution network: - Drafts can be freely edited before submission. - PRs in Publishing status are mid-distribution and cannot be edited by the customer directly, but support can retract them internally if distribution has not yet completed. - Published PRs cannot be edited, recalled, or modified post-publication, because syndication partners and news outlets have already received the content. Common example: a customer publishes a PR listing a location as "Redmond, OR" instead of "Redmond, WA" and needs to correct it. Steps to try - Before submission: proofread the PR carefully in draft mode. Verify location, names, dates, URLs, and contact details. - If the PR is stuck in 'Publishing' status: contact support immediately. Support can retract PRs internally before distribution finalizes so you can correct and republish. - If the PR is already 'Published': publication cannot be reversed. You will need to issue a corrected/updated PR as a new submission. The original cannot be retracted from syndication partners. - Provide support with the PR ID(s) and a clear description of the typo or required correction. Credit (HDC) refund policy - When support retracts PRs stuck in 'Publishing' due to a customer-side typo, a credit gift may be issued to allow republishing. Standard gift in these cases is 150 HDCs (sufficient to republish corrected PRs). - Credit refunds are discretionary and reviewed case-by-case. Refunds are not guaranteed for PRs that have already fully published. - Customers should request the credit refund in the same support ticket where the retraction is requested. Important Notes - Always treat PR submission as final — review carefully before submitting. - Retraction is only possible while a PR is in 'Publishing' status, not after full publication. - Credit gifts (e.g., 150 HDCs) are intended to cover the cost of republishing the corrected version, not as compensation beyond that.

✍️ Search Atlas — Content Assistant & AI Writing Issues

This article covers AI content generation, NLP optimization, the AI brief, the content editor, and related publishing timelines. ⚠️ Error 1: AI generation spinner runs forever — no content appears What's happening: The AI generation service is under high demand or your request timed out. Steps to try: - Wait up to 3 minutes — long-form content (2,000+ words) takes time. - Refresh and try generating a shorter piece first (outline only) to test if the service is working. - Simplify your prompt — contradictory or very complex instructions increase failure rate. - Check your AI credit usage: Top-right corner (avatar) → Billing (Plans & Top-ups / Activity Log). - Try again during off-peak hours if it consistently fails. ⚠️ Error 2: Generated content has broken formatting, placeholders, or truncated text What's happening: The AI returned a malformed response, usually a one-off issue. Steps to try: - Click Regenerate — this resolves the issue in most cases. - Reduce the target word count slightly — very high targets (4,000+ words) are more prone to truncation. - If you see #{{variable}} placeholders, go to More Features → Brand Vault and fill in all required fields. - Avoid pasting prompts with special characters — ", &, / can disrupt templates. - Report persistent template issues to support with a screenshot. 📊 Error 3: NLP optimization scores never load What's happening: NLP analysis requires a stable connection and a minimum content length to run. Steps to try: - Wait 90 seconds — NLP analysis is computed on demand and takes longer for large documents. - Make sure your article has at least 200 words before expecting a score. - Enter a target keyword — NLP scoring requires a primary keyword to score against. - Save your content, then reopen the article to trigger a fresh analysis. - Hard-refresh the page and reload the article. 🔄 Error 4: "Enrich with keywords" loads indefinitely What's happening: The keyword enrichment service is temporarily slow or unavailable. Steps to try: - Wait 60 seconds — enrichment pulls from live keyword databases. - Test if Keyword Research is working independently: Left Sidebar → Keyword Research. - If Keyword Research also fails, wait 10 minutes and try again. - Check monthly enrichment credits: Top-right corner (avatar) → Billing (Plans & Top-ups / Activity Log). - Contact support if enrichment has failed for more than 2 hours. 🖼️ Error 5: Image upload fails What's happening: The file is too large, the format isn't supported, or storage is full. Steps to try: - Confirm the file is under 10 MB. - Use a supported format: JPEG, PNG, WebP, or GIF. - Disable browser extensions (especially privacy tools) and try again. 🤖 Error 6: AI alt text suggestions don't generate What's happening: Previously a known bug where the AI alt text suggestion engine returned no recommendations after clicking the suggest/auto-generate button. This was tracked internally under ticket SPE-613. Status: ✅ Resolved — the fix has been fully merged and is live in production. If you still encounter the issue: - Hard-refresh the editor (Ctrl+Shift+R / Cmd+Shift+R) to load the latest build. - Confirm the image is fully uploaded and visible before requesting alt text. - Try a different image to rule out a corrupted file. - Contact support and reference ticket SPE-613 if the problem persists. 🧩 Error 7: Saved content is missing or shows an old version What's happening: Auto-save may have missed recent edits due to a dropped connection. Steps to try: - Check Version History in the article editor toolbar — earlier drafts are saved there. - Search by article title: Left Sidebar → Content → Content Genius → Search. - Check your trash or archive folder — articles can be accidentally archived. 🌐 Error 8: Page import fails — "URL could not be fetched" or URL returns a 500 error What's happening: Some websites block our crawler with firewall rules or return 500 errors for automated requests. This error also appears during topical map and competitor analysis tasks if the Domain Knowledge Network (DKN) is unable to retrieve the target URL. Steps to try: - Confirm the URL is publicly accessible — open it in a private or incognito browser window to rule out login or session issues. - If the page is behind a login or paywall, copy and paste the content manually into the editor instead of importing via URL. - For Cloudflare-protected URLs, wait a few minutes and try again — challenge pages can temporarily block automated fetches. - If you are seeing a "failed to create" error in the topical map or competitor analysis tools, this is related to the DKN task failing to fetch the domain — retry after a few minutes as the system will attempt the request again. - Contact support via the chat widget if the import continues to fail after retrying, and include the URL so a human teammate can investigate further. 📰 Press Release Publishing Timeline Press releases submitted through Search Atlas typically take 3–4 working weeks to be fully published across the distribution network. Please plan your campaigns and announcements with this lead time in mind. If a press release has been in submission status for longer than 4 working weeks, contact support with the press release title and submission date for a status check.

🛠️ Auto Upload to WordPress via Brand Vault in Content Genius

The Brand Vault Auto Upload to WordPress toggle automatically publishes Content Genius articles to your connected WordPress site when generation finishes. A known issue currently prevents this for single-article generations — the sections below cover how the feature works, the manual workaround, and how to get support. 📋 How the Auto Upload to WordPress toggle works The Auto Upload to WordPress toggle lives inside each Brand Vault (accessed via Header apps-grid icon → More Features → Brand Vault). When enabled, it links your Brand Vault to a connected WordPress site so newly generated articles publish without a manual upload step. The intended flow: 1. Enable Auto Upload to WordPress in your Brand Vault settings. 2. Generate an article in Content Genius using that Brand Vault. 3. The article finishes generation and moves to review status. 4. Content Genius sends the article to your connected WordPress site automatically. When working as intended, the article appears in your WordPress dashboard with no extra clicks. ⚙️ How to enable Auto Upload to WordPress in your Brand Vault To turn on the toggle for an existing Brand Vault: 1. In Search Atlas, click the apps-grid icon in the header, then go to More Features → Brand Vault. 2. Select the vault you want to update. 3. Locate the Auto Upload to WordPress toggle. 4. Confirm your WordPress site is connected to the Brand Vault. 5. Switch the toggle on. Your Brand Vault is now set to auto-publish every new article generated with it. ⚠️ Known issue: articles not auto-publishing after generation A known issue in Content Genius causes single-article generations to skip the auto-publish step, even when the Auto Upload to WordPress toggle is enabled in the Brand Vault. What you will see - The article completes generation in Content Genius. - The article transitions to a Needs Review status. - The article stays unpublished on your WordPress site. - The Auto Upload to WordPress toggle remains enabled, but no upload is triggered. Current status This issue is logged with our engineering team and a fix is in development. Tracking reference: CG-1731. 🚀 Manual workaround: publish your article to WordPress While the fix is in development, publish any affected article to WordPress in a few clicks: 1. Open the article in Content Genius. 2. Confirm the article is in Needs Review status. 3. Click Upload to WordPress at the top of the article. 4. Select the correct WordPress site if prompted. 5. Confirm the upload. Your article publishes to WordPress the same way it would through the automatic flow. 🔑 Before you troubleshoot: check these requirements If the manual upload also fails, confirm the following first: - Your WordPress site is connected to Search Atlas under Integrations. - The connected WordPress account has permission to publish posts. - The correct WordPress site is linked to the Brand Vault you used to generate the article. - The article was generated using the Brand Vault with the toggle enabled, not a different vault. Once each item is confirmed, the Upload to WordPress button will successfully push your article live. 💡 What to do if the manual upload still fails If you have confirmed all requirements and the manual Upload to WordPress still fails, contact Search Atlas support with the following details: - The Content Genius article name or URL. - The Brand Vault name. - The connected WordPress site URL. - A screenshot of the article status and the toggle setting. Our support team will link your report to the active engineering ticket and update you when the auto-publish fix ships. 🎯 You now know how the Brand Vault Auto Upload to WordPress toggle is meant to work, the known auto-publish issue in Content Genius, and the manual upload workaround to keep publishing while the fix is in development. For more on connecting your site, see the Search Atlas WordPress integration article.

🔄 Content Genius WordPress Synchronization Status Resolution

Complete your WordPress article synchronization to resolve conflicting connection statuses. This article shows you how to sync your author and category details so your statuses align across Content Genius and Brand Vault. 🔗 Why Content Genius and Brand Vault Show Different Statuses WordPress integration in Content Genius runs two separate status checks: the CMS connection and the article synchronization. When synchronization is not yet complete, you see two different results: - Connected in the general integration settings (the CMS connection is live). - Not Connected in Brand Vault (the article metadata is still missing). Brand Vault waits for article metadata — author names and categories — to be synced before it marks the full integration as connected. Until you sync that metadata, the two statuses stay out of step. 🔄 How to Complete the WordPress Synchronization Follow these steps to sync your WordPress article details and resolve the status conflict: 1. Open an article in WordPress. 2. On the article editing screen, find the Synchronization status section at the top of the article page. It sits above the article content in the main editing area, not in a separate sidebar or modal. 3. Click the gray bar labeled Not synced to open the synchronization form. 4. Enter the author name in the field provided. 5. Select the category for the article. 6. Save the synchronization details. Once you finish these steps, both the CMS connection and synchronization statuses align to Connected across Content Genius and Brand Vault. ✅ How to Verify the Connection Status in Brand Vault After you sync, confirm the change in two places: - Open Brand Vault and go to your WordPress integration settings. The WordPress connection should now display Connected instead of Not Connected. - Open the article in Content Genius to confirm the author and category details are populated and saved. A fully connected state means both the CMS connection and the article synchronization show Connected, with no conflicting indicators between the general integration settings and Brand Vault. If the status still shows Not Connected after syncing, refresh the page, re-open the article, and confirm that both the author name and category were saved correctly before checking Brand Vault again. ❓ Why Content Genius Requires This Sync Step Content Genius synchronizes more than the CMS connection — it aligns article metadata (author, category, and related attributes) between your WordPress site and Brand Vault. This step keeps your content properly discoverable and attributed within the platform. The Connected status in Brand Vault confirms that this metadata alignment is complete. 🛠️ Troubleshooting WordPress Sync Issues If your synchronization does not reflect as expected, review these common questions: - How long should the sync take? The status typically updates in Brand Vault within a few minutes. Allow up to 5–10 minutes for the change to fully propagate. - What if the status does not update after 5–10 minutes? Refresh both Content Genius and Brand Vault, confirm the author and category were saved on the article, then re-check the status. If it still has not updated, re-save the synchronization details and reach out to Support if the conflict persists. - What errors might I see when entering author or category details? The most common issues are leaving the author field blank or not selecting a category, which can prevent the synchronization from saving. Complete both fields before you save. - Is category selection mandatory? Yes. Both the author name and category must be provided for synchronization to complete and for Brand Vault to display Connected. 🌀 You now know how to complete the WordPress synchronization process and resolve conflicting connection statuses. Repeat these steps for each article, or reach out to Support if you run into any issues.

🛠️ Content Genius Article Stuck on "Not Started" After Write with AI

If your Content Genius article stays on Not begun after you click Generate (under Content → Content Genius — What are we writing today?), the generation job was never queued. Follow the steps below to resolve the stall and get your article generating without waiting for support. ⚙️ What the "Not begun" Status Means After Submission Not begun is the default status assigned to a Content Genius article before generation begins. If the status has not advanced to In progress within approximately 30–60 seconds of clicking Generate, the job likely did not enter the generation queue. Occasional high server load can delay status updates, so a brief wait beyond this window is sometimes normal. This is a distinct failure mode from a slow-running article (status In progress) or a generation error (status Failed). A stuck Not begun status typically means the process was never triggered — not that it stalled midway. Common causes include a stale browser session, missing required article fields, or an exhausted generation quota. Note: If you experienced an unexpected page refresh immediately after clicking Generate, your session may have been interrupted by a known editor issue. Re-submit using the steps below and stay on the page to monitor the status change. 🛠️ How to Fix a Content Genius Article Stuck on "Not begun" 1. Hard-refresh the page. Press Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac) to reload without cache, then check whether the status has updated. 2. Re-submit generation. Open the stuck article, click Generate again, confirm the submission, wait 30–60 seconds, then refresh the article list. 3. Verify all required fields are complete. At minimum, the article must have a target keyword and an assigned project. If your workflow uses a Brand Vault, confirm one is selected — missing configuration can prevent queue entry in some setups. 4. Clear your browser cache and cookies. A stale or corrupted session can prevent the submission from reaching the server. After clearing, log back in to Search Atlas and re-submit via Generate. 5. Try a different browser or an incognito window. Browser extensions or outdated session credentials can interfere with the API call that queues generation. 6. Check your Content Genius generation quota. Go to Avatar (top-right) → Billing (Billing) (or your account's quota/usage page) and confirm you have remaining Content Genius generation credits. Exhausted quotas can silently block new submissions — upgrade your plan or contact support to request a quota review if needed. 7. Contact Search Atlas support. If none of the steps above resolve the issue, contact support and include your article name, project name, and a screenshot of the Not begun status. Quota issues and account-level blocks may require manual review by the support team. After each step, wait 30–60 seconds and refresh the article list. A status of In progress or Completed confirms the issue is resolved. ⚠️ When to Contact Search Atlas Support If the article still shows Not begun after completing every step above, contact the Search Atlas support team. Have the following ready to speed up resolution: - The article title and the Content Genius project it belongs to - The date and approximate time of the original Generate submission - Your browser name and version - Any error messages or unexpected behavior you observed during submission - A screenshot of the Not begun status, if available The support team can inspect the generation queue directly, review quota status, and manually trigger the article if the job was dropped at submission. 🎯 You now know how to diagnose and resolve a Content Genius article stuck on Not begun — confirm your required fields are set, check your generation quota, clear your browser cache, and re-submit via Generate (under Content → Content Genius) to get generation back on track.

🔧 Fixing WordPress Sync Failures and Google Business Profile Display Issues

📋 Overview This article helps you resolve two common connection problems in Search Atlas: the WordPress Content Genius plugin not syncing posts, and a connected Google Business Profile (GBP) account not appearing in your dashboard. Most issues are caused by expired permissions, plugin version mismatches, or account access settings. Follow the steps below to get both integrations working again. 🔌 Part 1: WordPress Content Genius Plugin Not Connecting or Syncing If your posts are not publishing to WordPress or the plugin shows a connection error, work through these checks in order. ✅ Step 1: Confirm Plugin Installation and Version 1. Log in to your WordPress admin dashboard. 2. Go to Plugins > Installed Plugins. 3. Confirm the Search Atlas / Content Genius plugin is installed and Active. 4. Check that you are running the latest version. If an update is available, click Update Now, then deactivate and reactivate the plugin. 🔑 Step 2: Re-verify the API Connection 1. In WordPress, open the Content Genius plugin settings. 2. Copy the API key shown in your Search Atlas dashboard under Settings > Integrations > WordPress. 3. Paste the key into the plugin field and click Save or Connect. 4. A green confirmation message indicates a successful connection. If the key is rejected, generate a new key in Search Atlas and paste the updated value. 👤 Step 3: Check User Permissions The WordPress account used for the connection must have Administrator or Editor rights. Accounts with limited roles cannot publish synced content. Update the user role under Users in WordPress if needed. 🛡️ Step 4: Rule Out Conflicts - Security plugins and firewalls: Tools like Wordfence or server-level firewalls can block incoming sync requests. Temporarily disable them to test, then add Search Atlas to the allowlist. - Caching plugins: Clear your cache after connecting so new settings take effect. - REST API: Content Genius relies on the WordPress REST API. If a plugin or security rule disables it, sync will fail. Re-enable the REST API to restore syncing. 🔄 Step 5: Test a Manual Sync 1. Return to your Search Atlas dashboard. 2. Select a draft and choose Publish to WordPress. 3. Confirm the post appears in your WordPress drafts or published list. 📍 Part 2: Connected Google Business Profile Not Showing in the Dashboard If you linked a Google Business Profile but it does not appear in Search Atlas, the cause is usually a permissions or refresh issue. 🔐 Step 1: Confirm Account Ownership and Access The Google account you connected must have Owner or Manager access to the business profile. Profiles where you only have limited or pending access will not display. Verify your access level at business.google.com. 🔁 Step 2: Reconnect the Google Account 1. In Search Atlas, go to Local → GBP Projects and click Connect GBP Account. 2. Disconnect the existing account. 3. Click Connect GBP Account and sign in. 4. On the Google permissions screen, make sure every requested permission box is checked. Unchecked boxes are the most common reason profiles fail to load. 5. Complete the authorization. 🗂️ Step 3: Select the Correct Location If your Google account manages multiple locations, you may need to choose which profile to display. Open the GBP integration panel and select the correct business location from the dropdown. ⏳ Step 4: Allow Time to Sync Newly connected profiles can take up to 15 minutes to populate. Refresh the dashboard or log out and back in if the profile has not appeared after this window. ⚠️ Step 5: Check for Suspended or Unverified Profiles Google will not share data for profiles that are unverified, suspended, or pending review. Confirm the profile is verified and in good standing in your Google Business Profile account before reconnecting. 🐞 Known Issue: Connecting GBP During Onboarding Also Connects Google Search Console If you connected your Google Business Profile through the onboarding flow, you may notice that Google Search Console is also connected automatically, even if you did not explicitly select it. This is a known issue our engineering team is working to fix; the two integrations are meant to be connected independently. If you only intended to connect GBP, you can safely disconnect Google Search Console afterward under Settings > Integrations. 🐞 Known Issue: Citation Scan Fails With a 400 Error (Missing "State" Field) If your profile connects but the Citation Scan on the GBP Overview page does not complete — returning the error "Citation scan requires a complete business profile. Please add the following: state." — the profile is missing its required state field, usually because of an incomplete profile sync from Google. Our engineering team is tracking this issue and a fix is planned. In the meantime, open your profile at business.google.com, confirm the full business address (including the state/region) is complete, then reconnect or refresh the profile in Search Atlas. 🆘 Still Need Help? If both integrations are correctly configured and the problem continues, contact our support team with the following details to speed up resolution: - Your Search Atlas account email. - The WordPress site URL and plugin version. - A screenshot of any error message. - The Google account email and business profile name you are trying to connect. Our team can review the connection logs on our end and help restore full sync functionality. WordPress publishing now records every sync attempt (including the error code and payload) in an append-only log, and our team is automatically alerted when a publish keeps failing for about 15 minutes — so persistent sync failures are often flagged on our side even before you reach out.

🔄 Resolving WordPress Sync Status in Content Genius

📌 Overview Content Genius connects to your WordPress site so you can publish and update content directly from Search Atlas. Sometimes the platform shows conflicting connection statuses for the same site. For example, WordPress may appear as Connected inside Content Genius but show as Not Connected in CMS Connectors (Integrations), found via Avatar → Settings → CMS Connectors. This article explains why that happens and walks you through resolving it. 🧩 Why Statuses Can Conflict Content Genius and Brand Vault each verify your WordPress connection in slightly different ways. A status mismatch almost always points to a connection that is partially set up rather than fully broken. The most common causes are: - Separate connection records: A site connected directly inside Content Genius may not yet be linked in CMS Connectors (Integrations) under Avatar → Settings, where your central integrations are stored. - Expired or revoked credentials: An application password or API token may have expired, been regenerated, or been removed in WordPress. - Plugin status changed: The Search Atlas WordPress plugin may have been deactivated, updated, or reinstalled. After a plugin update, synced media such as images can occasionally be affected, so it is worth confirming content still renders correctly. - Cached status: One area of the platform may be displaying an older, cached result that has not refreshed. - URL mismatch: The site was added with a slightly different address (for example, with or without www, or using http instead of https). ✅ Confirm the Source of Truth CMS Connectors (Integrations), accessed via Avatar → Settings → CMS Connectors, is the central location where your WordPress connection is stored and shared across tools. If CMS Connectors shows Not Connected, treat that as the status to fix first, even if Content Genius still appears connected. Resolving the connection there updates the status everywhere it is used. 🛠️ Step-by-Step Resolution Follow these steps in order. Most mismatches are resolved within the first few steps. 1. Refresh the platform. Reload the page or sign out and back in. This clears any cached status and often syncs the two areas automatically. 2. Open CMS Connectors. Navigate to Avatar → Settings → CMS Connectors (Integrations), locate your WordPress site in the list, and check the current connection status. 3. Verify the site URL. Confirm the address matches your live site exactly, including https and the correct www format. A small difference creates a separate, unverified record. 4. Reconnect the site. If CMS Connectors (Integrations) shows Not Connected, select the option to reconnect or edit the connection, then re-enter your WordPress credentials or application password. 5. Check the WordPress plugin. In your WordPress admin area, confirm the Search Atlas plugin is installed, activated, and updated to the latest version. If you recently updated the plugin, verify that synced content (especially images) still appears correctly. 6. Regenerate credentials if needed. If reconnecting fails, create a new application password in WordPress and paste it into CMS Connectors (Integrations) via Avatar → Settings → CMS Connectors. Remove any old or unused credentials. 7. Return to Content Genius. Once CMS Connectors (Integrations) shows Connected, reopen Content Genius and confirm the status now matches. 🔍 Verify the Connection Works After both areas show Connected, run a quick test to confirm everything is working: - Open a piece of content in Content Genius. - Use the publish or push-to-WordPress option to send a draft. - Check your WordPress drafts to confirm the content arrived. - Confirm that images and other media in the draft rendered correctly, not just that the post itself arrived. Content Genius performs an automatic post-publishing verification of articles pushed to WordPress, so a failed push is flagged rather than silently lost. If the draft appears in WordPress, your sync is fully restored and the statuses will remain aligned going forward. 💡 Tips to Prevent Future Mismatches - Manage connections in CMS Connectors (Integrations). Adding and updating WordPress sites from Avatar → Settings → CMS Connectors keeps a single, consistent record across all tools. - Keep the plugin updated. Enable automatic updates for the Search Atlas plugin so credentials and endpoints stay current, and run a quick test publish after each update to confirm content and images still sync correctly. - Avoid duplicate site entries. Use one consistent URL format whenever you add or reconnect a site. - Review credentials periodically. Replace application passwords before they expire to avoid sudden disconnections. 🆘 Still Seeing a Mismatch? If the statuses still conflict after completing these steps, the connection may need a closer review. Before reaching out, note the site URL, the status shown in each area, and any error messages you see. This helps us resolve the issue faster. If you need further assistance, click the chat icon in the bottom-right corner of the platform and type "Human Teammate" to start a live chat with a member of our team.

⚠️ Content Audit Failed Importing Error in Content Genius Onpage Audit

If you see the toast "This Content Audit failed importing!" when running an Onpage Audit in Content Genius, a resolved bug was blocking the audit from completing. Hard-refresh your browser and follow the steps below to run a successful audit. ⚠️ What the "Content Audit Failed Importing" Error Means This toast notification appears in the Onpage Audit tool when the system cannot finish importing and processing your URL and keywords. The audit does not return any results — it fails immediately after you click Run Audit. The error was caused by a bug in the GHL (GoHighLevel) integration with Content Genius. It affected all Onpage Audits consistently, regardless of which URL or keywords you entered. 🔍 Steps That Trigger the Error The error appears when you complete this sequence: - Open Content Genius → Onpage Audit. - Enter one or more target keywords and a page URL. - Click Run Audit. The audit fails immediately and the toast "This Content Audit failed importing!" appears on screen. No partial results are returned. ✅ How to Resolve the Error This bug has been patched. To load the latest version of Content Genius and confirm the fix is active on your account: 1. Hard-refresh your browser: press Ctrl + Shift + R on Windows or Cmd + Shift + R on Mac. 2. Go to Content Genius → Onpage Audit. 3. Enter your target keywords and page URL. 4. Click Run Audit. If the audit processes and returns results without the error toast, the fix is confirmed on your account. 🛠️ If the Error Persists After a Hard-Refresh If you still see the error, try these additional steps: - Clear your browser cache and cookies completely, then log back in to Search Atlas. - Switch to a different browser — Chrome or Edge are recommended. - Confirm your GHL account is still connected under Settings → Integrations. If none of these steps resolve the error, contact Search Atlas support with the URL you were auditing and a screenshot of the error toast so the team can investigate your specific account. 🎯 You now know what triggers the "Content Audit failed importing" error in Content Genius and how to clear it. If you continue to see unexpected audit failures after trying these steps, reach out to Search Atlas support for direct account-level assistance.

⚠️ Content Genius: Incorrect Year References in Generated Articles

Content Genius was inserting incorrect year references — such as "in 2023" or "as of 2023" — into AI-generated article headings and body content. The fix has been deployed; articles generated now include correct date context. Note: This article covers only the incorrect year reference issue. Several related but separate known issues are tracked independently: - Incorrect Brand Vault assignments across projects (CG-141, resolved) — Regenerate affected articles to pick up the fix. - Brand Vault sync mapping errors causing missing logos, images, or incorrect social profile assignments (CG-1761, resolved) — Regenerate affected articles to pick up the fix. - Articles missing target keywords, Topical Terms, or competitor analysis (CG-1792, under investigation) — Contact support and reference your account for investigation. - Excluded Brand Vault terms still appearing in generated content (CG-1576, resolved) — Regenerate affected articles to pick up the fix. - Brand Vault social media links not saving to the database across accounts (SPE-732, active) — Do not re-enter the data repeatedly; contact support and reference SPE-732. - Brand Vault logos or images visible in the backend but not rendering on the frontend — This is a separate rendering issue from CG-1761; contact support so the team can investigate. - Unable to create a new Brand Vault due to a false "domain already exists" error (CG-1886, awaiting release) — Contact support in the meantime so they can flag your account. 🔍 What's Happening Date context was missing from the prompts used during heading outline and content generation. Without this signal, the AI model defaulted to stale year references, making generated content appear factually outdated even when the article topic had no connection to that year. - Symptom: Generated articles contain phrases like "in 2023" or "as of 2023" regardless of your chosen topic. - Who is affected: Articles generated before the fix was deployed. Contact support via the in-app chat or by submitting a ticket at support.searchatlas.com with your account ID and generation timestamps so the team can confirm whether your articles fall within the affected window. The team typically responds within one business day. - Where it appears: Both article headings and body paragraphs — including introductions, section headings, and inline references throughout the generated content. Articles generated after the fix was deployed will no longer include stale year references. 🛠️ Workaround Steps If you have existing articles that contain incorrect year references, choose either option below. Option 1 — Edit the article manually 1. Open the affected article in the Content Genius editor. 2. Search for incorrect year references (e.g., "2023"). 3. Replace each instance with the correct year. 4. Save your changes. Option 2 — Delete and regenerate 1. Delete the affected article. 2. Regenerate it — the fix is live, so the new version will include correct date context automatically. Tip: To reduce year ambiguity in future articles, include the target year explicitly in your topic or brief — for example, add "2026 guide" to your topic input to anchor the AI to the correct time context. If you generated a high volume of articles during the affected window, use your workspace's article search to locate generations containing "2023" or "2024" so you can review them in batches rather than one by one. 📡 Engineering Status This issue has been identified and resolved. The fix is deployed to production — date context is now correctly passed into both the heading outline and content generation prompts. By "correct date context," we mean the AI now references the current calendar year by default (e.g., 2026) unless you specify a different year in your topic or brief. Articles you generate going forward will no longer contain incorrect year references. 📞 When to Contact Support Reach out to the support team if any of the following apply: - You regenerate an article and still see incorrect year references. - You cannot access the Content Genius editor to make manual corrections. - You need help identifying all affected articles in your account, or confirming whether a generation falls inside the affected window. - Your Brand Vault social media links are not saving across accounts (SPE-732, active) — reference SPE-732 when you reach out, and avoid re-entering the data repeatedly while the fix is in progress. - Your Brand Vault logos or images are visible in the backend but not rendering on the frontend — this is a separate rendering issue from CG-1761 and requires support investigation. - You are unable to create a new Brand Vault due to a false "domain already exists" error (CG-1886, awaiting release) — contact support so they can flag your account until the fix ships. - You suspect a different issue — such as incorrect Brand Vault assignment across projects (CG-141, resolved — regenerate affected articles to confirm the fix), Brand Vault sync mapping errors causing missing logos, images, or incorrect social profile assignments (CG-1761, resolved — regenerate affected articles to confirm the fix), or articles missing target keywords, Topical Terms, or competitor analysis (CG-1792, under investigation). When you contact support, include the article title and the specific incorrect year references you are seeing. Reach the team through the in-app chat or by submitting a ticket at support.searchatlas.com — expect a response within one business day. 🌀 This issue is resolved — articles you generate now reflect the correct date context. A quick edit or regeneration will bring any existing affected articles fully up to date, and the team is here if you need further assistance.

🔓 Fixing the "Execution Already in Progress" Error When Optimizing Content with AI

❓ What this error means When you optimize an article with our AI content tools in Content Genius, Search Atlas places a temporary lock on that article so two edits cannot run at the same time. This lock protects your content from being overwritten or duplicated mid-edit. If an AI optimization job is interrupted, the lock can occasionally fail to release. The next time you try to edit, you see a message like: - "Execution already in progress" This means the system still thinks an earlier edit is running, even though it has actually stopped. Until the lock clears, new AI edits on that specific article are blocked. 🔍 Common causes - An AI optimization job was closed or refreshed before it finished. - Your internet connection dropped during an edit. - Two edits were started on the same article within a few seconds of each other. - A temporary server-side interruption left the job in a "running" state. A previously reported issue in Content Genius, where AI article writing could become stuck at the progress-completion stage and leave the job in a "running" state, has been resolved. If you encountered this on an older article and still see the error, the lock may simply need to be cleared using the steps below. 🛠️ How to clear the lock yourself Most stuck locks release automatically within a short period. Try these steps in order before contacting support. ⏳ Step 1: Wait and refresh 1. Close the article editor completely. 2. Wait about 15 minutes so any background job can time out. 3. Reopen the article and try the AI optimization again. 🧹 Step 2: Clear your browser session 1. Log out of Search Atlas. 2. Clear your browser cache, or open the app in a private/incognito window. 3. Log back in and reopen the article. 4. Run the AI optimization once and wait for it to fully complete before clicking anything else. 🗂️ Step 3: Confirm no other tab is open 1. Check that the same article is not open in another browser tab or on another device. 2. Close any duplicates, then retry the edit. 🆘 If the lock is still stuck Some locks—especially those that have persisted for several days—must be cleared on our end. This is a server-side action you cannot perform from your dashboard. If the error continues after the steps above, contact support and we will release the lock manually. 📋 What to include in your request To resolve your case quickly, please send: - The article name or URL affected. - The project or workspace the article belongs to. - The date the error first appeared. - A screenshot of the error message. With these details, our team can locate the stuck job and clear it, usually within one business day. 💳 About credits used on failed attempts We understand that repeated failed attempts can consume credits. Search Atlas does not charge credits for optimizations that do not produce a result. If you believe credits were deducted for edits blocked by this error, let support know in the same message. 🔁 How to request a credit review 1. Note the approximate dates and number of failed attempts. 2. Include your account email and project name. 3. Send these to support along with the lock details above. Our team will review your usage history and restore any credits that were charged for blocked or failed edits. 🛡️ How to prevent this in the future - Let each AI optimization finish completely before navigating away or refreshing. - Avoid running edits on the same article from multiple tabs or devices at once. - Use a stable internet connection when running AI content tasks. - If a job appears frozen, wait for it to time out instead of starting a new one immediately. 💬 Need more help? If you are unsure whether a lock is active or you cannot edit an article at all, reach out to our support team. Include the details listed above and we will clear the lock and review any affected credits for you.

🛠️ Content Genius to Link Lab: Troubleshooting Article Submission Failures

When a Content Genius article submission to a Link Lab publisher fails, the cause is almost always one of a handful of fixable issues. Follow the steps below to identify and resolve the error without losing your article. Created your order through the AI Agent chat instead of directly inside Content Genius? AI Agent-generated Link Lab orders follow a separate flow with their own known issues (such as the article not appearing on the order page). See the AI Agent Link Lab troubleshooting article instead of this guide. ⚠️ Known issue (May 2026) — Wix, HubSpot, and Webflow connections: Customers submitting articles through Wix, HubSpot, or Webflow UCMS integrations may currently see validation errors such as content_type is required, member_id is required, meta.collection_id is required, or Unsupported content_type None. This is a platform-side regression (ticket CG-1722) and cannot be resolved by changing your article. Contact Search Atlas support rather than attempting to self-fix. This notice will be removed once the fix ships to production. 🔍 How the Content Genius → Link Lab Submission Works The Content Genius to Link Lab workflow lets you send a finalized article directly to a publisher placement you have secured in Link Lab. When you click Submit to Link Lab inside Content Genius, the platform runs three checks in sequence: 1. Validates that the article includes all required fields (title, body, target URL, anchor text). 2. Authenticates your account's Link Lab access and publisher permissions. 3. Packages the article and delivers it to the selected publisher queue in Link Lab. A failure at any of these three steps produces a submission error. The sections below map each failure point to its fix. ⚠️ Common Causes of Submission Failures Match your on-screen error text to one of these known causes before working through the full troubleshooting steps: - Missing required fields — The article is missing a title, body text, target URL, or anchor text. The submission validator blocks incomplete articles. Typical error: Missing required field: anchor text or Missing required field: target URL. - Article status not set to Complete — Content Genius requires the article status to be Complete before the Submit to Link Lab button activates. Open your article in Content Genius, click the Status dropdown in the top-right panel (options: Draft, In Progress, Needs Review, and Complete), select Complete, and save. The Submit to Link Lab button activates after you save. Typical error: Article must be marked Complete before submission. - No publisher selected or publisher connection lost — If the Link Lab publisher was removed, paused, or never linked, the submission has no destination. Typical error: Publisher not found or No active publisher selected for this article. - Insufficient account permissions — Your user role may not include Link Lab submission rights. Only an account admin can grant this access. Typical error: You do not have permission to submit articles. - Session timeout — A long editing session can expire your authentication token. Refreshing the page re-authenticates you without losing saved content. Typical error: Session expired. Please refresh and try again or 401 Unauthorized. - Duplicate submission — Link Lab blocks articles already submitted to the same publisher placement to prevent accidental double-publishing. Typical error: Duplicate submission detected for this publisher placement. 🛠️ Step-by-Step: Fix a Failed Submission Work through these steps in order. Most submission failures resolve by step 4. 1. Confirm all required fields are filled in Content Genius. Open the article and verify all four fields are present: article title, body content (minimum word count met), target URL, and anchor text. Save the article after filling in any missing field. 2. Set the article status to Complete. In the Content Genius editor, open the Status dropdown in the top-right panel and select Complete. The Submit to Link Lab button activates only when status is set to Complete. 3. Verify the publisher is active in Link Lab. Go to Link Lab → Publishers and confirm the target publisher shows a status of Active. If the publisher shows Paused or Disconnected, re-activate it before retrying the submission. 4. Refresh your session and resubmit. Save the article, hard-refresh the page (Ctrl+Shift+R on Windows / Cmd+Shift+R on Mac), reopen the article, and click Submit to Link Lab again. A session refresh resolves most transient authentication errors. 5. Check for a duplicate submission. In Link Lab, go to Submissions → All Submissions and search for the article title. If a prior submission already exists for this publisher placement, Link Lab blocks the new one. Confirm receipt of the earlier submission with your publisher before creating a replacement. If none of these steps resolve the error, check your account permissions in the next section. 🔑 Check Account Permissions for Link Lab Submission Link Lab submission access is controlled at the user-role level. If you see "You do not have permission to submit articles", or the Submit to Link Lab button remains grayed out after the article is marked Complete, your role is missing the required permission. To check and update permissions: 1. Ask your account admin to go to Settings → Team → Roles. 2. Select your role and locate the Link Lab – Submit Articles permission toggle. 3. Enable the toggle and click Save. 4. Log out, then log back in for the permission change to take effect. After logging back in, retry the submission. A green Submission Successful confirmation banner appears at the top of the Content Genius editor when the article delivers correctly. 📋 What to Include When Contacting Support If you have completed all steps above and the submission still fails, contact Search Atlas support. Include the following to speed up resolution: - Your account email address - The article name as it appears in Content Genius - The publisher name or publisher ID in Link Lab - The exact error message displayed (a screenshot is ideal) - The date and time of the failed submission attempt - A screen recording or JAM video of the failure, if available - The CMS integration in use, if any (Wix, HubSpot, Webflow) — relevant for the CG-1722 known issue The Search Atlas support team will review the Content Genius–Link Lab bridge logs tied to your account and escalate to engineering if a platform-side issue is identified. 🎯 You now know how to diagnose and resolve Content Genius to Link Lab submission failures — from missing required fields and session timeouts to permissions gaps and duplicate submissions. To learn more about setting up and managing your publisher placements, see the Link Lab Publishers guide.

💡 AI Premium vs AI Generation Quota in Content Genius

🔍 Overview Content Genius uses a separate quota from the general AI Generation quota you may see elsewhere in Search Atlas. If your article generation fails inside Content Genius — even when your AI Generation balance shows hundreds of thousands of credits remaining — this article explains why and what to do. 📊 The Two Quotas Explained Search Atlas tracks two distinct AI credit pools across the platform: - AI Generation Quota — A general-purpose credit pool used by various tools across the platform (such as meta generation, templates, and other lightweight AI features). This is the large number (e.g. ~997,000 credits) you may see in your account usage dashboard. - AI Premium Quota — A separate, higher-value credit pool reserved specifically for advanced AI generation tasks, including full article creation inside Content Genius. This pool is smaller and is billed differently because it powers more resource-intensive outputs. These two pools are independent of each other. Having a large AI Generation balance does not grant access to AI Premium features. Content Genius article creation will fail if your AI Premium Quota is empty, regardless of how many general AI credits remain. ✍️ Why Content Genius Requires AI Premium Quota Content Genius generates full, SEO-optimised long-form articles. This process is significantly more resource-intensive than shorter AI outputs, so it draws from the AI Premium Quota pool — not the general AI Generation pool. This separation ensures fair usage and consistent performance for all customers using advanced content generation. 📍 How to Check Your AI Premium Quota 1. Log in to your Search Atlas account. 2. Click on your avatar (top-right corner). 3. Navigate to Billing → Plans & Top-ups (Billing). 4. In the Content section, look specifically for the AI Premium quota line item — this is the balance that Content Genius draws from. 5. If this value is 0 or very low, article generation will fail even if your general AI Generation quota appears healthy. 🚀 How to Get More AI Premium Quota AI Premium Quota can be added to your account in the following ways: - Plan upgrade — Higher-tier plans include a larger monthly AI Premium Quota allocation. Review your current plan to see if upgrading increases this limit. - One-time top-up — Search Atlas supports purchasing additional AI Premium Quota as a one-time add-on. If this option is available on your plan, you will see it in the Billing section of your account. If you are unsure which option applies to your account, the support team can confirm your current entitlements and guide you to the right solution. 🛠️ Troubleshooting Failed Article Generation If Content Genius fails to generate an article, follow these steps before contacting support: 1. Go to Left sidebar → Content → Content Planner to access Content Genius. 2. Attempt to start a new article and note the exact error message displayed. 3. Check your AI Premium Quota balance in your account settings (see steps above). 4. If the AI Premium Quota is 0, add more credits via a plan upgrade or one-time top-up. 5. If the AI Premium Quota shows a positive balance but generation still fails, this may be a technical issue — please contact support using the method below. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🖼️ Fixing 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.

🛠️ Blog Pages Created by Vibe Coding Skip the Blog Section and SEO Pipeline

If you add a blog page with the vibe coding agent in the Website Builder, it may publish as a standard top-level page without blog routing or SEO settings. Add blog posts through Content Genius (CG) ingestion instead, which places them in the blog section with full SEO configuration applied. 🔍 What's Happening With Vibe Coding Blog Pages When you ask the vibe coding agent to add a blog page, the agent creates it as a generic top-level website page instead of routing it into your blog section. - Expected: the page is created under your blog path, for example /blog/compound-movements. - Actual: the page is created at the top level, for example /compound-movements. Because the page does not follow the blog page format, it does not pass through the SEO pipeline. The result is a page that lacks proper blog routing and SEO configuration. Who Is Affected This affects Website Builder customers who use the vibe coding agent to add blog pages. Pages added through Content Genius ingestion are not affected. 🛠️ Workaround: Add Blog Posts Through Content Genius Ingestion Use Content Genius (CG) ingestion to add blog posts. CG ingestion correctly places pages inside the blog section and applies full SEO configuration. If You Have Not Created the Page Yet 1. Add the blog post through Content Genius (CG) ingestion rather than the vibe coding agent. 2. Confirm the page routes under your blog path (for example /blog/your-post). Your blog post will appear in the blog section with SEO settings applied. If a Page Was Already Created at the Top Level 1. Recreate the page through Content Genius (CG) ingestion. 2. Verify the new page routes under /blog/ with SEO configuration applied. The recreated page will sit in your blog section with the correct blog format and SEO settings. 📡 Engineering Status for This Issue Our team is aware of this behavior and is actively working on a fix so that vibe coding detects an existing blog section, or creates one, when adding blog pages. Until the fix ships, the Content Genius ingestion workaround above is the recommended way to add blog posts. 📞 When to Contact Support Reach out to our support team if: - The Content Genius ingestion workaround does not place your page under /blog/. - Your blog page is missing SEO settings after CG ingestion. - You need help recreating a page that was published at the top level. Share the page URL and the blog path you expected so the team can assist quickly. 🌀 Our team is on it and working toward a permanent fix. In the meantime, adding blog posts through Content Genius ingestion keeps them in your blog section with full SEO configuration. Thank you for your patience.

🛠️ Fixing Square (1:1) Content Genius Images by Setting an Aspect Ratio

Content Genius lets you control the aspect ratio of generated article images by setting a project-wide default in the Brand Vault content tab. 🔍 What's Happening Content Genius was generating article images at a 1:1 (square) aspect ratio instead of the intended 16:9 (widescreen) default. The fix is live in production, and you have a UI control to set the ratio yourself. 🛠️ How to Set Your Default Aspect Ratio in Brand Vault Setting the aspect ratio in the Brand Vault content tab applies it as the global default for every article in that project. 1. Open your project and go to More Features (apps-grid icon) → Brand Vault. 2. Select the Content tab. 3. Find the aspect ratio field and select your preferred ratio (for example, 16:9). 4. Save your changes. New images generated across the project now use this ratio as the default. 📌 Note on Per-Article Overrides There is no longer a per-article aspect ratio override in the editor — the More Features (apps-grid icon) → Brand Vault content tab setting is the only place to configure this, and it applies to every article in that project. 📞 When to Contact Support If your images still generate at the wrong ratio after setting the Brand Vault field and generating a new image, reach out via the live chat widget inside the platform with your project name and the ratio you selected.

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

⚠️ Content Rewriting — Step 1 and Step 2 Panels Go Blank After Clearing Original Content

A display bug in the Content Rewriting feature of Content Genius caused both panels to appear blank after clearing the original content in Step 1. No content is ever lost — the fix is now live, and a hard refresh is all you need to resume your workflow. 🔍 What's Happening After a successful rewrite, deleting or clearing the original content in Step 1 and then clicking into Step 2 causes both panels to go blank, making the rewritten result appear to disappear. Clicking back to Step 1 may also cause the rewritten content to reappear in Step 2 unexpectedly. This is a display and rendering issue only — no content is deleted or permanently lost at any point during this interaction. 🛠️ Workaround Steps 1. Copy or save your rewritten content from Step 2 before clearing Step 1. Do not delete the original content until you have saved the rewritten result. 2. If both panels are already blank, click back to Step 1 — your rewritten content should reappear in Step 2. 3. Perform a hard refresh of your browser to pick up the live fix and permanently resolve the issue: - Windows / Linux: Ctrl+Shift+R - Mac: Cmd+Shift+R After a hard refresh, the blank-panel behavior will no longer occur and Content Rewriting will work as expected. 📡 Engineering Status This bug has been identified, investigated, and resolved. The fix is live in the current version of Search Atlas — no further action is required beyond performing a hard refresh of your browser to load the updated version. 📞 When to Contact Support If blank panels persist after performing a hard refresh, reach out to the Search Atlas support team. Include a brief description of the steps you took and, if possible, a screenshot of what you are seeing so the team can investigate promptly. 🌀 This display issue is fully resolved — a hard refresh restores your Content Rewriting workflow immediately. If blank panels continue after refreshing, our support team is ready to help.

🛠️ Publishing Content Genius Articles to Website Studio: Workaround and Correct Steps

Content Genius articles can be published to a Website Studio site (as well as to WordPress and through Universal CMS connectors such as Shopify and HubSpot). If you prefer a chat-based workflow, you can also copy an article's content into the Website Studio chat, upload images to the Media Library first, and include every detail explicitly in your prompt. ⚠️ Why the Website Studio Publish button is missing A direct Content Genius to Website Studio integration does not exist at this time. Earlier Knowledge Base instructions described a Publish button and an automatic hand-off that the product does not currently support, which is why you could not find the button and kept receiving errors. We are correcting that article. If you still have the outdated version open, close it and follow this guide instead—this article replaces the older instructions that referenced a Publish button. In the meantime, use the chat-based workaround below to move your content into Website Studio successfully. 🛠️ How to publish a Content Genius article in Website Studio Follow these steps in order to move your finished article into Website Studio without errors. Step 1: Copy the article content into the Website Studio chat - Open your finished article in Content Genius and copy the full text. - Paste the text directly into the Website Studio chat. - Do not paste a Google Doc link. The AI cannot open external links, so any content behind a link is ignored and can trigger errors. Step 2: Upload images to the Media Library first - Upload each image to the site's Media Library before you reference it. - Note the exact filename of each uploaded image. - Reference each image by its Media Library filename in your prompt so Website Studio can place it correctly. - Website Studio inserts each image at the location you describe in the prompt. If the placement is not exactly where you want it, move or adjust the image manually in the Website Studio editor after the page is generated. Step 3: Include every detail explicitly in the prompt - Type out all specifics the article needs, such as company phone numbers, calls to action (CTAs), and links. - Spell out the structure, tone, target audience, headline, sections, bullet points, formatting preferences, and any SEO keywords—anything you expect on the finished page should be written into the prompt. - Write every important detail directly into the prompt, since the AI cannot retrieve it from an external source. - Example: "Convert this Content Genius article [topic] into a Website Studio post. Include the headline, all sections, and bullet points, and style it for [audience]. Place [Image Name 1] after the introduction and [Image Name 2] in the conclusion." When these steps are complete, Website Studio generates your page from the pasted content and referenced images without the repeated error messages. Once the page appears in the Website Studio editor with your text, images, and details in place, review the page, adjust any image placement if needed, and save or publish it from the editor. 📋 Structured prompt template to copy into Website Studio Use this format to keep your content, images, and details organized in a single prompt: Create a new page using the article below. ARTICLE CONTENT: [paste full article text here] IMAGES: Use [image-filename-1.jpg] after the intro and [image-filename-2.jpg] in the section about [topic]. Both are already uploaded to the Media Library. BUSINESS DETAILS: Phone: [your phone number]. CTA: [your call to action]. Links: [your URLs]. Replace each bracketed placeholder with your own content, then send the prompt in the Website Studio chat. 🛟 Website Studio error messages and credit reset The repeated errors you saw over the past 24 hours came from referencing content the AI could not access, such as Google Doc links or external image sources. Pasting content directly and referencing Media Library filenames resolves these errors. Because the previous instructions were misleading, we have reset your Website Studio credits so the failed attempts do not count against your balance. 🎯 You now know that Content Genius articles can be published to Website Studio, and you can also move articles over by pasting content into chat, uploading images to the Media Library, and including every detail in your prompt. Try the structured prompt template above on your next article, and reach out to support if any error returns.

🛠️ Fix Content Genius Create Button Stuck Loading

🔍 Overview When trying to create or publish an article from Content Genius to WordPress, some customers find the Create button enters an endless loading state and resets without completing the action. This article walks you through the most common causes and the steps to resolve them. ⚙️ Before You Begin Confirm the following before troubleshooting: - You are on the Content Genius page: navigate to Left sidebar → Content, then open your article. - Your WordPress site is connected as a connector inside Search Atlas. - You have a stable internet connection. ✅ Step 1 — Verify Your WordPress Connector Is Set Up Correctly A missing or broken WordPress connection is the most common reason the button gets stuck. Follow these steps to check it: 1. Navigate to Left sidebar → Coworker → Connectors. 2. Look for your WordPress site in the list of connected platforms. 3. If WordPress is not listed, click Add Connector and select WordPress from the available options. Complete the authorisation steps shown on screen. 4. If WordPress is already listed, remove the connector and re-add it to refresh the authentication. Once the connector is confirmed active, return to Content Genius and try the Create button again. 🔄 Step 2 — Refresh and Retry Temporary session issues can cause the button to loop without completing. Try the following: 1. Save any edits to your article using the save option in the editor. 2. Do a hard refresh of the page (Ctrl + Shift + R on Windows or Cmd + Shift + R on Mac). 3. Click the Create button once and wait up to 60 seconds without clicking again. Clicking repeatedly can reset the request. 🌐 Step 3 — Check for Browser Issues Browser extensions and cached data can interfere with the publishing action: - Clear your browser cache and cookies, then reload Search Atlas and try again. - Disable browser extensions — particularly ad blockers or script blockers — and retry. - Try a different browser (Google Chrome is recommended) or open Search Atlas in a private/incognito window. 📋 Step 4 — Check the Article Status in the Content Table Sometimes the article creation process runs in the background even if the button appears stuck: 1. Navigate to Left sidebar → Content to open the Content Genius listing table. 2. Look for the article in question and check its status column. 3. If the status shows Generating or a similar in-progress state, wait a few minutes and refresh the table. The process may already be running. 4. If the status shows Not Begun after several minutes, the request did not go through — proceed to Step 5. 💡 Step 5 — Re-attempt Article Creation If the article status is stuck on Not Begun or the button continues to reset after completing the steps above: 1. Open the article in the Content Genius editor. 2. Confirm the target WordPress site is selected in the publishing destination field. 3. Click Create once and do not navigate away from the page until the confirmation message appears. ⚠️ Important Note on Edited Content If you have made edits to your article inside Content Genius, be aware that in some cases the system may export the original AI draft rather than your latest saved version. Before clicking Create, scroll through the editor to confirm your most recent edits are visible and saved. This behaviour is being addressed in an upcoming platform update. 🆘 Still Stuck? If the Create button is still loading or resetting after following all the steps above, our team can investigate your specific account and connector configuration. 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.

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

🛠️ Fix Content Genius Stuck Articles and Folder Errors

🔍 Overview Two separate issues can disrupt your Content Genius workflow: articles that remain stuck on AI is still generating long after a request was made, and errors that prevent you from moving articles into folders. This article walks you through resolving both problems step by step. ⏳ Part 1 — Articles Stuck on 'AI Is Still Generating' If an article has shown the AI is still generating status for more than 10–15 minutes, the generation job has likely stalled. Follow these steps to resolve it. 1. Hard-refresh the page. Press Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac) to clear the cached status and reload the latest state from the server. 2. Check your project list. Go to Left sidebar → Content and open Content Genius. Confirm you are viewing the correct workspace or project where the article was created. Stalled articles occasionally appear in a different project if multiple workspaces are active. 3. Wait two minutes, then refresh again. Server-side generation queues can experience brief delays during peak hours. A second refresh after a short pause often resolves a false stuck state. 4. Delete the stalled article and regenerate. If the article still shows the same status after refreshing twice, delete it using the three-dot menu next to the article title, then submit a new generation request with the same inputs. Stalled jobs do not resume — a fresh request is the fastest fix. 5. Check your subscription usage. Generation failures can occur silently if your monthly AI word or article quota has been reached. Review your usage from your account settings before submitting a new request. If multiple articles from the same session are all stuck, this may indicate a temporary platform issue. Check the Search Atlas status page or ask the support team (see the bottom of this article) whether a known incident is affecting generation. 📁 Part 2 — Folder Organization Errors If you receive an error when trying to move articles into folders, or if folders are not responding as expected, the steps below cover the most common causes. 1. Confirm the article has fully loaded. You cannot move an article that is still in a generating or processing state. Wait until the article status shows as complete before attempting to assign it to a folder. 2. Refresh the Content Genius page. Stale UI states can block drag-and-drop or folder-assignment actions. Press Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac) and try the folder action again. 3. Use the three-dot menu instead of drag and drop. If dragging the article into a folder produces an error, click the three-dot menu (⋯) next to the article title and select Move to folder. This method is more reliable when the UI is in an inconsistent state. 4. Check folder permissions. If you are part of a team account, folders created by another user may be restricted. Ask the folder owner or your account admin to share the folder with your user role, or create a new folder under your own account. 5. Create a new folder and retry. If a specific folder consistently causes errors, create a new folder by clicking New Folder inside Content Genius, then move the article into the new folder. If this works, the original folder may be corrupted — contact support to have it reviewed. 6. Try a different browser. Browser extensions (particularly ad blockers and script blockers) can interfere with drag-and-drop and modal interactions. Test in a private/incognito window or a different browser to rule this out. ✅ Quick Reference — Which Fix to Use - Article stuck for under 15 minutes: Hard-refresh and wait. - Article stuck for over 15 minutes: Delete and regenerate. - Folder error on a generating article: Wait for generation to complete, then move. - Folder error on a completed article: Use the three-dot menu → Move to folder. - Folder error for all folders: Refresh browser, disable extensions, retry. - Folder error for one specific folder: Create a new folder and contact support. 🚫 What Does Not Help - Repeatedly clicking Generate on a stalled article — this creates duplicate jobs without fixing the original. - Logging out and back in — this does not clear a server-side generation queue. - Refreshing without waiting — give the server at least two minutes between refreshes for accurate status. 💬 Still Need Help? If you have followed all the steps above and the issue persists — for example, articles continue to stall immediately after regeneration, or folder errors appear across every folder — there may be an account-level or platform-level issue that requires investigation. 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 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 Content Genius Articles Stuck at AI In Progress

🔍 What This Issue Looks Like You start a Content Genius workflow — whether generating a single article, writing in bulk, or using the Content Planner — and the article never finishes. Instead, it stays frozen with an AI generating or in-progress status and does not complete, even after waiting several minutes. This issue is caused by a failure in the Content Genius article generation process. When the background generation chain fails mid-way, the article can be left in a stuck state with no automatic recovery. Before troubleshooting, keep in mind that generation can take longer than expected depending on article length and server load. Wait at least 15–30 minutes before assuming an article is stuck. If a generation job has not progressed for more than one hour, it is unlikely to complete on its own and you should proceed with the steps below. ✅ Steps to Resolve a Stuck Article 1. Do not delete the stuck article. Preserving the stuck article helps the support team investigate and resolve the underlying job failure. Leave it in place while troubleshooting. 2. Refresh the page. Navigate to Content Genius in your platform and perform a full browser refresh. You can use the hard refresh shortcut — Ctrl+Shift+R on Windows or Cmd+Shift+R on Mac — to bypass cached page data. Wait up to two minutes after refreshing to allow any pending background process to complete. 3. Clear your browser cache and cookies. Cached data can sometimes cause the interface to display a stale loading state. Clear your cache and cookies, then reload your Search Atlas account and navigate back to Content Genius. 4. Try a new browser session. Open an incognito or private window, log back into the platform, and navigate to Content Genius. Check whether the article status has updated or whether starting a new generation attempt succeeds. 5. Retry the generation. If the stuck article cannot be resumed, start the generation again from scratch using the appropriate option for your workflow (single article or bulk generation). Allow the generation to complete fully before navigating away from the page. When resubmitting bulk jobs, start with a smaller batch — for example, five to ten articles at a time — to confirm the workflow completes successfully before scaling back up to full volume. Also avoid navigating away from the page while a bulk job is actively queuing, as this may interrupt the submission process. 6. Check for partial output. In some cases, a stuck article may have captured partial content before failing. Review the article to see if any sections were generated and decide whether to continue from there manually or regenerate fully. ⚠️ If Articles Are Still Getting Stuck If you are still encountering stuck articles after following the steps above, this may indicate an issue that needs further investigation by our support team. - Note the exact workflow you were using when the article got stuck (single article, bulk generation, or Content Planner). - Note the article title or keyword and approximately when the issue started. - If possible, note whether the issue happens consistently or only on specific articles. - If credits were deducted for a failed generation, the support team can issue a refund — include this detail when you reach out so it can be addressed alongside the technical issue. Providing this information when you contact support will help the team investigate quickly. 💬 Contact Support 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 Stability & Bug Fixes

We've shipped 40 updates to Content Genius, focused on stability, faster content generation, and more reliable Brand Vault and CMS integrations. ✨ What's New This release strengthens the reliability of AI content generation, image creation, Brand Vault, and CMS connectors. Highlights include timeout and rate-limiting protection to prevent interruptions, fixes for content and image generation crashes, and cleaner formatting in your published posts. 🛠️ Key Fixes and Improvements - Added timeout protection for asynchronous operations and extended timeouts for AI image generation to prevent interruptions. - Added rate limiting protection against plugin request flooding and for Brand Vault initialization, and increased rate limits for large agency accounts to prevent false quota errors. - Fixed AI image generation crashes on malformed responses, image history loading issues, and secondary crashes during image generation retries. - Fixed multiple Brand Vault issues including save errors, hostname filtering, sync targeting the wrong projects, address field validation, false detection errors in Project Overview, and infinite loops in statistics updates. - Fixed CMS connector authentication issues, sync errors with specific parameters, incorrect publish dates for imported blog posts, and improved CMS connection error messages. - Fixed Domain Knowledge Network creation failures, generation timeouts, and empty generation results. - Fixed content generation crashes with missing page references, task retry crashes, incomplete content brief generation, and excessive token usage. - Fixed HTML heading styles, extra spacing between bullet points, and table formatting loss when copying or exporting content. - Improved content indexation with better fallback and status handling, Brand Vault performance with smart cache invalidation, and updated the document export system for improved reliability. 📋 What to Expect These changes apply automatically with no action needed on your part. You should experience fewer interruptions during content and image generation, more accurate Brand Vault behavior, more reliable CMS syncing, and cleaner formatting in your published and exported content. 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 AI Article Generation and Language Issues

This article helps you resolve two common issues in Content Genius: AI article generation that fails to start or complete, and output that appears in the wrong language despite your settings. Follow the steps below to identify and fix the root cause of each problem. 📍 Where to Find It All Content Genius tools are accessed via Left sidebar → Content. Depending on which tool you are using, navigate to the relevant sub-page: AI Content Templates for template-based generation, Content Planner for planned content briefs, or Scholar for research-assisted articles. 🛠️ Step-by-Step 1. Confirm your project and workspace are active. Before generating, make sure you are working inside a project that is fully set up. An incomplete or misconfigured project can prevent AI generation from running. 2. Check and re-apply your language setting. Go to Left sidebar → Content → AI Content Templates (or the tool you are using). Locate the language selector — typically visible in the article setup or brief configuration panel — and confirm the correct language is selected. If it already shows the right language, deselect it and reselect it, then save or re-apply before generating. 3. Clear and re-enter your keyword or topic input. Empty the keyword or topic field completely, retype your target keyword, and confirm any required fields (such as title, tone, or word count) are filled in. Missing required inputs are a common cause of silent generation failures. 4. Retry generation. Click the generate button again. If the process stalls for more than 60 seconds without progress, refresh the page, navigate back to the tool, and attempt generation once more. 5. Try a different Content tool to isolate the issue. If generation fails in AI Content Templates, try Left sidebar → Content → Content Planner or Left sidebar → Content → Scholar. If generation succeeds there, the issue is specific to your template configuration, not your account or connection. 6. Check your browser and connection. Use a supported, up-to-date browser (Chrome or Edge recommended). Disable browser extensions that may block network requests, and ensure you have a stable internet connection before retrying. ✅ How to Confirm It Worked Generation is working correctly when the AI output panel populates with a full draft within approximately 30–60 seconds of clicking generate, with no error messages or empty results. To confirm the language fix took effect, check the first paragraph of the generated article — the body text, headings, and any meta content should all appear in the language you selected. If any section still appears in a different language, repeat step 2 and ensure the language setting is saved before clicking generate again. 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.

⚠️ Press Release Preview Appears Empty After AI Generation

If the Edit & Review panel (Step 3) in the press release creation flow appears blank immediately after using 'Generate with AI,' your content has been successfully generated and saved. This is a display issue only — a full page reload restores the preview instantly. 🔍 What's Happening After clicking 'Generate with AI' on Step 2 and advancing to Step 3 (Edit & Review), the preview panel may render as completely blank. AI generation completed successfully and your content is stored — only the visual rendering of the preview is affected. This issue can occur on any browser or operating system. 🛠️ Workaround Steps Follow these steps to restore your AI-generated content without losing any work: 1. After reaching Step 3 and seeing the empty preview, keep your browser tab open — do not close it. 2. Perform a full page reload: press F5 on Windows or Linux, or press Cmd+R on Mac. 3. Navigate back to the press release you were editing. 4. Your AI-generated content will now appear correctly in the preview panel. Your content was saved during generation — the blank preview is a rendering issue only, and the reload resolves it. 📡 Engineering Status Our engineering team has identified the root cause of this display issue. A fix has been released and is being rolled out to all users. Your data is safe and no generated content has been lost. If you are still experiencing the blank preview after reloading, your account may not yet have the fix deployed. 📞 When to Contact Support If the workaround does not restore your content after a full page reload, or if you cannot locate your press release after reloading, please contact Search Atlas Support. Include your press release ID and details such as when you generated the content and which browser you're using so our team can investigate quickly. Avoid closing your browser tab during troubleshooting, as this may affect our ability to assist you. 🎯 A permanent fix for this preview rendering issue has been released and is being rolled out. Your AI-generated content is always saved. If you are still seeing a blank preview after reload, your product may not yet have the fix deployed — contact Support with your press release ID and we'll investigate.

✍️ Content Genius Blog Slug Auto-Inclusion Explained

🔍 What Is Happening? When you generate a blog post in Content Genius, you may notice that the slug (the URL-friendly version of your title, such as my-blog-post-title) is automatically inserted into the generated content. This is expected behavior tied to the Dynamic Keyword Nesting (DKN) system, which uses your slug as a structural reference during content generation. While this helps Content Genius align the output with your target URL and keyword structure, it can produce unwanted text in the final draft if you do not need the slug displayed in the content body. ⚙️ Why Does This Happen? Content Genius uses the slug you provide as a content signal. During generation, the DKN system may surface that slug directly inside the output — typically near the top of the article or within the first heading block. This is not a bug; it is an automatic behavior designed to reinforce topical relevance. However, it is fully avoidable using either of the two methods below. ✅ Method 1: Prevent the Slug via Your Prompt The quickest way to stop the slug from appearing in your content is to explicitly instruct Content Genius to exclude it in your generation prompt. Follow these steps: 1. Go to Left sidebar → Content and open Content Genius. 2. Set up your blog topic, target keyword, and any other inputs as usual. 3. In the Additional Instructions or prompt customization field, add a clear instruction such as: Do not include the slug or URL string in the body of the content. 4. Run the generation. Content Genius will follow your instruction and omit the slug from the output. This method works best for one-off blog posts or when you want full control over each generation without changing your default workflow. 🗂️ Method 2: Create the Blog from the Content Genius Tab If you consistently experience slug auto-inclusion, the way you initiate blog creation may be contributing to the behavior. Using the dedicated Content Genius tab workflow gives you more control over what signals are passed into the generator. 1. Navigate to Left sidebar → Content and select Content Genius. 2. Instead of importing or linking an existing URL or slug, start a new blog document directly from within the Content Genius interface (What are we writing today?) by clicking Write an article. 3. Enter your blog title and target keywords manually without pasting a pre-formed slug into the slug field, or leave the slug field blank until after generation is complete. 4. Complete the remaining inputs and generate your blog post. 5. Once the content is generated and finalized, add or edit the slug field separately before publishing. By decoupling the slug input from the generation step, you prevent the DKN system from referencing it during content creation, which eliminates the auto-inclusion behavior. ✏️ What If the Slug Already Appeared in My Content? If you have already generated a blog post and the slug is present in the output, you can resolve this quickly: - Open the generated document inside Content Genius. - Use the in-editor search (typically Ctrl+F or Cmd+F) to locate the slug text. - Delete or replace the slug with your intended heading or introductory text. - Re-run the generation for that section only if needed, using the Additional Instructions field to exclude the slug. 💡 Quick Comparison of Both Methods - Prompt-based prevention — Best for individual posts; add one line to your prompt to exclude the slug each time. - Content Genius tab creation — Best for an ongoing workflow; leave the slug field blank during generation and add it afterward to avoid auto-inclusion entirely. 🆘 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 AI Content Missing After Deployment — Fix It

🔍 What This Article Covers If OTTO AI-generated content on your deployed pages — including dental practice pages — is suddenly showing a Missing status, this is not a rendering error, a caching issue, or a tracking script problem. The root cause is tied to how OTTO AI manages quota consumption and how content is stored after generation. This article explains what happened, why quota was consumed, and what steps to take next. ⚙️ How OTTO AI Content Generation Works Understanding the generation lifecycle helps clarify why content can go missing: - Each time OTTO AI generates content for a page, it draws from your account's content generation quota. This quota is consumed at the moment of generation, not at the moment of deployment. - Generated content is stored temporarily in your OTTO AI workspace. If that content is deleted — either manually, through a workspace reset, or as a result of a plan change — the deployed pages lose their reference to the stored content and display a Missing status. - Re-generating content for the same pages counts as a new quota draw. The original quota used for the first generation is not refunded, even if the content no longer exists. - Deploying content to a page does not create an independent backup of that content outside of the OTTO AI workspace. The deployed page remains linked to the stored generation record. 🚨 Common Reasons Content Shows as Missing - Content was manually deleted from the OTTO AI workspace after deployment. - A workspace or project was reset, clearing all previously generated records. - A subscription plan change or downgrade caused stored generations beyond the new plan's retention limit to be removed. - Bulk actions were applied in the OTTO SEO V3 section that removed previously generated page content. - Session or account changes caused a mismatch between the deployed page's content reference and the stored record. 🧭 How to Confirm the Root Cause 1. Go to Left sidebar → OTTO SEO and open SEO Automation (URL: /seo-automation-v3). 2. Locate the affected pages in your OTTO AI project. Filter by Missing status if the option is available. 3. Check whether a generation record exists for each affected page. If the record is absent, the content has been deleted from the workspace — this confirms data loss, not a display or script error. 4. Review your account's quota usage history within the OTTO SEO V3 section to confirm that generation quota was consumed during the original run. 5. Check if any workspace resets, bulk deletions, or plan changes occurred around the time the Missing status appeared. 📋 What to Do When Content Is Missing Once you confirm the content records are gone, follow these steps: 1. Navigate to Left sidebar → OTTO SEO and open SEO Automation, then open the affected OTTO AI project. 2. Select the pages showing Missing status. 3. Use the Regenerate option to create new content for those pages. Be aware that this will consume additional quota from your current balance. 4. Before regenerating, verify your available quota is sufficient to cover all affected pages. Prioritise your highest-traffic or highest-value pages first if quota is limited. 5. After regeneration, redeploy the content to the affected pages and confirm the status updates from Missing to Deployed. 💡 How to Prevent This in the Future - Do not delete generation records for pages that are actively deployed. Deleting a record removes the content reference from the live page. - Before performing a workspace reset or bulk deletion, export or document any content you want to preserve. - If you are considering a plan change, review how it may affect stored generation retention limits before confirming the change. - Treat generated content records as live dependencies for your deployed pages — not as draft files that can be safely discarded after publishing. ❓ Quota and Refund Questions Quota consumed for a successful generation is generally not automatically refunded just because the content was later deleted, since the generation itself completed successfully at the time. That said, quota-related billing questions — including cases where you believe quota was consumed due to a platform error, such as a generation that failed or produced no output — are reviewed on a case-by-case basis. Contact the support team with the details of your case so it can be investigated. 🙋 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.

⚠️ Content Genius Warning Messages Explained

🔎 Overview When working inside Content Genius, you may occasionally see a warning message appear on screen. These messages can look alarming, but most of them are recommendations, not errors. This article explains the difference, what each type of message means, and when — if ever — you need to update your settings. ⚠️ Warnings vs. Errors: What's the Difference? Content Genius uses two distinct types of messages to communicate with you: - Warning messages — Informational notices that flag something worth your attention. They do not stop you from using the tool and do not require you to change any settings. Think of them as helpful suggestions. - Error messages — Notices that indicate something has gone wrong and may be blocking an action. These typically require a specific step to resolve, such as re-entering a value or adjusting a configuration. If the message you see does not prevent you from continuing your work, it is almost certainly a warning, not an error. 📁 The Folder Settings Warning Message One of the most common warning messages customers ask about is related to folder settings. This message typically appears when Content Genius detects that no default folder has been assigned for saving your content. Here is what you need to know about this message: - It is a recommendation. Content Genius is suggesting that you assign a default folder so your documents are organised automatically. - It does not mean your content is lost, broken, or unsaved. - It does not prevent you from creating, editing, or publishing content. - You can dismiss the message and continue working without making any changes. You will only need to act on this message if you want your content automatically saved to a specific folder by default. If you are happy managing folders manually, no action is required. 🗂️ How to Set a Default Folder (Optional) If you decide you would like to assign a default folder and clear the warning message, follow these steps: 1. In the left sidebar, click Content to expand the section. 2. Select the Content Genius document where the warning appeared. 3. Locate the folder selector, usually found in the document settings panel or the top toolbar of the editor. 4. Choose an existing folder from the dropdown, or create a new one by selecting New Folder. 5. Save your selection. The warning message will no longer appear once a default folder is assigned. This step is entirely optional. Your content is safe and fully functional whether or not a default folder is set. 🧩 Other Common Warning Messages in Content Genius Below are additional warning messages you may encounter and what they mean: - "Target keyword not set" — A reminder that you have not entered a primary keyword for this document. Content Genius uses this keyword to power its SEO recommendations. You can add it at any time without losing your work. - "Word count below recommended threshold" — A suggestion that your content may benefit from additional depth. This is a guideline based on competitive benchmarks, not a hard limit. - "No content brief linked" — Indicates the document is not connected to a Content Planner brief. You can link one via Left sidebar → Content → Content Planner, but this is optional if you are working without a brief. - "AI suggestions unavailable" — This message typically appears when an AI generation request cannot be completed. If it persists, refreshing the page or starting a new session usually resolves it. If it continues, contact support using the instructions below. ✅ Quick Reference: Do I Need to Act? - Message appears but I can still work normally — This is a warning. No action required unless you want to follow the recommendation. - Message blocks me from completing an action — This is likely an error. Follow any on-screen instructions, or contact support. - I am unsure which type of message I have — Check whether you can still click, type, or save. If yes, it is a warning. 💬 Still Have Questions? 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.

🛠️ Topical Maps Article Generation Failures and Empty Content

🔍 Overview Some users have encountered an issue where articles generated through Topical Maps either fail outright, produce empty content, or remain stuck in a generating state for an extended period with no visible progress. This article explains what caused the issue, what was done to fix it, and what steps you can take right now. ⚙️ What Caused This Issue This problem was traced to a backend race condition in the bulk article creation process used by Topical Maps. Specifically, when multiple articles were dispatched for generation at the same time, the system occasionally could not locate the correct processing session, causing generation to fail silently or stall indefinitely. The engineering team identified and resolved this in production. The following confirmed bugs have all been marked Done in our engineering backlog: - Bulk article creation in Topical Maps and Supplemental Content returning a Failed to create articles error - Bulk Topical Map generation intermittently failing due to an internal session lookup error during processing - Topical Map article creation failing consistently when using the bulk creation workflow ✅ What to Do Right Now Because the fix has been deployed to production, most users will no longer experience this issue. Follow these steps to retry article generation: 1. Go to Left sidebar → Content → Content Genius. 2. Open your Topical Map and review the articles that failed or show empty content. 3. Retry generation for the affected articles. Use the bulk generation option if you need to regenerate multiple articles at once. 4. Allow a few minutes for processing to complete. If articles begin generating successfully, the fix is working as expected for your account. 🚩 If Articles Are Still Stuck or Failing If you retry generation and articles remain stuck, return empty content, or immediately show a failure message, there are a few things worth checking before contacting support: - Refresh the page before retrying. A stale session in your browser can sometimes cause generation to appear stuck when it has actually already failed in the background. - Try generating a smaller batch. If you were generating many articles at once, try generating a few at a time to isolate whether the issue is batch-size related. - Check your account's content generation quota. If your plan's content generation limit has been reached, new articles will not generate successfully. - Wait and retry. If there is an active platform incident, retrying after 15–30 minutes often resolves temporary failures. 📋 What to Share With Support If none of the steps above resolve the issue, gathering the following information before contacting support will speed up the investigation: - The name of the affected Topical Map - The approximate time the failure first occurred - Whether all articles failed or only some - Whether any articles show empty content versus an explicit error message - How long affected articles have been stuck in a generating state 💬 Contact Support 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 Mismatches and Understand LLM Visibility

Overview This article covers two common questions: why Content Genius sometimes generates articles that don't match your intended topic, and how Search Atlas calculates LLM Visibility metrics. Both issues are closely related — strong topic alignment in your content directly influences your visibility scores across AI-powered search engines. Why Content Genius Generates Off-Topic Articles Content Genius uses your inputs — such as your keyword, topic brief, audience, and intent — to generate article drafts. When the output doesn't match your expected topic, it is typically caused by one of the following: - Vague or broad seed keyword: Using a keyword that is too general gives the AI too much room to interpret direction. Use specific, intent-driven phrases that clearly reflect the exact topic you want to cover. - Missing or thin brief: If the topic brief is left empty or contains only a few words, Content Genius may drift from your intended topic. - Conflicting inputs: A mismatch between your keyword and your brief can cause the AI to blend both signals, producing an unfocused draft. - Incorrect content type selection: Choosing the wrong format for your topic can skew the article structure and narrative direction. How to Fix a Topic Mismatch in Content Genius 1. Open Content → Content Genius (What are we writing today?) in Search Atlas. 2. Start a new article rather than re-running the same settings that produced the mismatch. 3. Enter a specific, long-tail keyword that clearly reflects the exact topic you want to cover. 4. Write a clear topic brief — 2–4 sentences describing the article's goal, target audience, and the main question it should answer. The more precise your brief, the more accurate the output. 5. Select the content type and search intent options that best match your goal. 6. Generate the draft and review it. If a section still drifts off-topic, try rewriting that section's input with a more specific instruction. How Search Atlas Calculates LLM Visibility Metrics LLM Visibility metrics measure how prominently your brand or content appears across AI-powered search engines and large language models. To understand and improve your LLM Visibility score, you can take the following self-serve steps: - Check your LLM Visibility dashboard: Navigate to the LLM Visibility section in your Search Atlas project to see your current score and any available breakdown of contributing factors. - Review your tracked brand mentions and citations: The dashboard surfaces how often your brand or content is referenced in AI-generated responses. Look for gaps in coverage across the AI engines being tracked. - Strengthen topical authority: Publishing comprehensive, well-structured content on topics relevant to your niche helps AI models recognize your site as an authoritative source. Use the Content Planner and Topical Maps tools in Search Atlas to identify and close content gaps. - Run an on-page audit: Use the On-Page Audit tool to ensure your existing pages meet quality and relevance standards that support AI citation signals. - Allow time for score updates: LLM Visibility scores reflect data gathered from AI engines over time. If you have recently published or updated content, allow some time before expecting the score to update. If your score does not reflect recent changes after sufficient time has passed, or if you need clarification on a specific metric in your account, escalate to support with your project name and the specific score or metric you have questions about. 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 GHL Blog Integration with Content Genius

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

🛠️ Content Genius 400 Errors and Research Phase Freezes

🔍 Overview Some users experienced two related issues in Content Genius: a 400 error appearing when opening or posting to an article, and the tool becoming stuck in the research phase during article generation. Both issues were caused by a broken SQL join in the platform's backend (linked to an internal database inconsistency) and have since been fully resolved with a fix deployed to production. If you encountered these errors before the fix was released, this article explains what happened, confirms the resolution, and tells you what to do if you are still seeing any issues. ⚠️ What the Errors Looked Like - Opening a Content Genius article returned a 400 error (sometimes displayed via Cloudflare). - The article generation process appeared to freeze or hang indefinitely in the research phase without progressing. - Attempts to interact with the Content Genius agent returned a "Request failed: 400" message. - Editing sessions timed out while generating article content. 🧩 Root Cause Our engineering team identified a broken SQL join on a non-existent database reference within Content Genius. This caused the platform to fail when trying to load or process certain articles, resulting in 400 errors across multiple parts of the tool — including article opening, agent interactions, and the content generation workflow. ✅ Current Status: Resolved The engineering team developed, reviewed, tested, and deployed a fix to production. Both the article 400 error and the research phase timeout are now resolved. You should be able to: - Open existing Content Genius articles without errors. - Generate new articles through Left sidebar → Content → Content Genius without the research phase freezing. - Interact with the Content Genius agent without receiving 400 error messages. 🚀 Steps to Verify the Fix on Your Account 1. Log out of Search Atlas and log back in to ensure you have a fresh session. 2. Navigate to Left sidebar → Content → Content Genius. 3. Open an existing article or start a new one using the available generation options. 4. Allow the research phase to run. It should now progress normally without freezing or returning an error. 5. If you were previously posting content to your site and received a 400 error, try the action again to confirm it completes successfully. 💡 If You Are Still Seeing Errors The fix has been deployed and confirmed in production. However, if you are still experiencing 400 errors or a frozen research phase after following the steps above, here is what to try: - Clear your browser cache and reload the page, or try an incognito/private browsing window. - Try a different browser to rule out a local caching issue. - Check that you are working with a newly started session rather than a tab left open from before the fix was deployed. If none of the above resolves the issue, it is possible there is a separate edge case affecting your specific account or article. Please reach out so our team can investigate directly. 📋 Notes on Trial Extensions If your trial period was impacted by these errors and you were unable to use Content Genius as expected, our team can review your account and apply an extension where appropriate. Raise this when you contact support and include the dates during which you were affected. 💬 Still 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.

🛠️ 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 AI Credits and Article Generation

📋 Overview Content Genius uses AI credits to generate articles. If your account does not have sufficient AI credits, article generation will fail — even if other users on the same account (such as admins) can generate content without issue. This article explains how AI credits work, why you may see an error, and how to fix it. ⚠️ Understanding the 'Article Generation Could Not Be Started' Error If you see the message "Article generation could not be started" when trying to generate an article in Content Genius, this typically means one of the following: - Your user account does not have enough AI credits assigned to it. - The workspace or sub-account you are working in has run out of AI credits. - Your user role has a credit limit that differs from the admin's limit. Admins often have access to the full pool of AI credits and may not encounter this error, while other users — such as editors or contributors — may have a separate, lower credit allocation. This is why admins can generate articles without issue while other users cannot. 🔍 How to Check Your AI Credit Balance Before attempting to generate an article, confirm that your account has available AI credits: 1. Log in to Search Atlas. 2. Click your avatar (usually in the top-right corner) and go to Billing → Plans & Top-ups. 3. Look for the Your Plan and Credits section to see your current balance. 4. If your balance is at zero or below the required threshold, you will need to top up or have an admin allocate credits to your user profile. ✍️ How to Generate an Article in Content Genius Once you have confirmed you have sufficient AI credits, follow these steps to generate an article: 1. In the left sidebar, go to Content → Content Genius. 2. Click Generate or Write with AI in Bulk depending on your needs. 3. Enter your target keyword or topic, configure your settings, and click Generate. 4. The platform will consume AI credits and begin producing your article. If you prefer to write without AI assistance, select Write it yourself — this option does not consume AI credits. 🛠️ How to Resolve the Error If you are still seeing the error after checking your credit balance, try the following: - Contact your workspace admin: Ask them to review AI credit allocations for your user role. Admins can adjust how credits are distributed across team members. - Upgrade your plan: If the entire workspace is out of AI credits, the account owner may need to purchase additional credits or upgrade the subscription plan. - Check your user role permissions: Some roles may have restrictions on AI feature usage. An admin can update your permissions if needed. - Refresh and retry: Occasionally a temporary system issue can trigger this error. Wait a moment, refresh the page, and try again. 💡 Tips for Managing AI Credits Efficiently - Use Write with AI in Bulk only when you need to generate multiple articles at once, as this consumes more credits per session. - For shorter or less complex content, consider using Write it yourself and supplementing with targeted AI suggestions to save credits. - Admins should regularly review credit usage under account settings to avoid unexpected shortfalls for team members. 🙋 Need More Help? If you have followed the steps above and are still experiencing the error, or if you are unsure how to adjust credit allocations for your team, we are here to help. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Content Genius Article Generation Errors Explained

🔍 Overview Some customers encounter the error "Article generation is temporarily unavailable" or notice their article is stuck at Step 1 with no progress when using Content Genius. This article explains why this happens, what you can do right now, and how to track resolution. ⚠️ What Causes This Error? This error typically appears when there is a temporary disruption in the Content Genius article generation pipeline. Known triggers include: - A backend service outage affecting article or image generation - High traffic causing generation jobs to queue or stall - A specific article request getting stuck in the pipeline with no progress - Image generation stopping mid-process during article creation These issues are usually detected and resolved by the Search Atlas engineering team quickly. In most cases, no action is required on your end beyond the steps below. ✅ Steps to Try First 1. Refresh the page. Go to Left sidebar → Content → Content Genius and reload your browser. A temporary glitch may resolve on its own. 2. Wait a few minutes and retry. If the pipeline is under high load, waiting 5–10 minutes before attempting a new generation often resolves the issue. 3. Try a different article type. On the Content Genius page, test whether Write it yourself or Rework existing article options are available and functioning. This helps confirm whether the issue is specific to AI generation or broader. 4. Clear your browser cache. A stale session can occasionally cause display or submission errors. Clear your cache and try again in a fresh tab. 5. Try a different browser or device. This rules out a local browser issue as the cause. 📊 How to Know If It Is a Platform-Wide Outage If the error persists after following the steps above, it is likely a temporary platform-side outage. Here is how to stay informed: - Check the in-platform notification bar. Search Atlas displays system status messages at the top of the platform when a known issue is active. - Contact support via live chat. A support teammate can confirm whether an active incident is being investigated and provide an estimated resolution time. Outages affecting Content Genius are escalated directly to the engineering team and are typically resolved within a short timeframe. Your article requests are not lost — once service is restored, you can re-submit your generation request from Left sidebar → Content → Content Genius. 💡 Tips to Avoid Disruption - Use Write with AI in Bulk during off-peak hours if you need to generate multiple articles to reduce the chance of hitting a congested pipeline. - Save your keyword and topic inputs before submitting, so you can quickly re-enter them if a generation attempt fails. - If an article appears stuck at Step 1 for more than 10 minutes with no movement, do not repeatedly resubmit — contact support so the stuck job can be cleared from the pipeline. 🙋 Still Seeing the Error? If you have followed all the steps above and article generation is still unavailable, our team needs to investigate your specific account and pipeline status. 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. Additional Notes Avoid repeatedly retrying generation, as this is unlikely to resolve a platform-side outage. Also useful escalation checklist: exact error message, date/time with timezone, project/workspace name, browser/device, and whether issue affects all users on account or only your login.

🖊️ Content Genius: Article Pages vs Non-Article Pages

🎯 What Content Genius Is Designed For Content Genius is Search Atlas's AI-powered writing assistant built specifically for creating long-form, article-style content. This includes blog posts, how-to guides, listicles, news articles, and other text-heavy pages that follow a standard editorial structure. ❌ What Content Genius Cannot Do Content Genius is not designed for building or generating non-article pages. It will not produce the layouts, sections, or structured components typically needed for pages such as: - Homepage designs - Service or product landing pages - Contact pages - About pages - Pricing pages - Portfolio or gallery pages Attempting to use Content Genius for these page types will result in plain article-style output that lacks the visual structure and conversion-focused layout these pages require. 🏗️ What to Do Instead for Non-Article Pages Content Genius is the right tool for article-style content, but it is not the appropriate tool for non-article page types. If you need to create a homepage, landing page, service page, or similar structured page, we recommend reaching out to our support team, who can point you to the correct Search Atlas tool or workflow for your specific use case. When contacting support, please have the following ready so we can assist you quickly: - The type of page you are trying to create (e.g., homepage, landing page, contact page) - A description of the content or layout you are aiming for - Any error messages or unexpected outputs you received when attempting to use Content Genius for this purpose 💡 Tips for Getting the Best Results from Content Genius If you are building a content-heavy section of a non-article page — for example, an FAQ block or a detailed product description — you can use Content Genius to draft that specific section's copy. This lets you take advantage of Content Genius's article-writing strengths for the text portions of your page. If you are unsure whether Content Genius is the right tool for your use case, our support team can help you evaluate your options and identify the best approach for your specific page goals. 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.

💡 Get Help Inside Content Genius Fast

🧭 What Is Content Genius? Content Genius is Search Atlas's AI-powered content suite. It brings together several tools designed to help you plan, create, and optimise content — all from one place. You can access every tool by navigating to Left sidebar → Content inside the platform. The suite includes the following tools: - SEO Content Assistant — Write and optimise content with real-time SEO guidance. - On-Page Audit — Identify on-page issues and get actionable fix recommendations. - Topical Maps — Build content clusters around core topics to strengthen topical authority. - Content Planner — Plan and schedule your content pipeline in one organised view. - Scholar — Research topics and find supporting data to enrich your content. - Meta Generator — Generate optimised title tags and meta descriptions at scale. - AI Content Templates — Use pre-built prompts to produce common content types quickly. 🚀 How to Get Started With Content Genius 1. Log in to Search Atlas and locate Content in the left sidebar. 2. Click Content to expand the section and see all available tools. 3. Select the tool that matches your current task — for example, choose SEO Content Assistant to start writing optimised content. 4. Follow the on-screen prompts inside each tool. Each tool includes inline guidance to walk you through the workflow. 🛠️ Common Issues and Quick Fixes Before escalating to a support agent, try the steps below. Most issues are resolved without extra help. - Tool not loading or appearing blank: Refresh the page. If the issue persists, clear your browser cache and try again in a different browser. - AI output not generating: Check your internet connection, then click the generate button again. Avoid clicking multiple times rapidly, as this can interrupt the request. - Content score not updating: Scroll down to confirm the full content analysis has loaded. If it still does not update, refresh the page and re-open your document. - Can't find a specific tool: Make sure you are navigating to Left sidebar → Content and clicking to expand the section. All tools are listed there as sub-pages. - Unexpected results or low-quality output: Review your input. More specific keywords, target URLs, and detailed briefs consistently produce better AI output. 📊 Tips for Better Results in Content Genius - Enter a clear target keyword before generating any content — this anchors the AI's output to your SEO goal. - Use Topical Maps before writing to identify which subtopics and supporting pages to create, so your content strategy is well-structured from the start. - Run an On-Page Audit after publishing to catch any remaining optimisation gaps. - Use AI Content Templates for recurring content types to save time and maintain consistency across your output. 📋 When You Need to Escalate to Support If you have tried the quick fixes above and the issue persists, a human agent can investigate further. To help us resolve your case as quickly as possible, please have the following ready before reaching out: - The name of the specific Content Genius tool you were using (e.g. SEO Content Assistant, On-Page Audit, Meta Generator). - A description of the exact issue — what you expected to happen and what happened instead. - The exact error message displayed, if any (copy and paste the full text). - The date and time when the issue occurred, including your time zone. - Your project name or URL if the issue is tied to a specific document or audit. - The browser and device you were using when the problem 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.

🛠️ 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 Content Genius Keyword Generation Timeout Issues

🔍 Overview When writing content in Content Genius, the keyword generation feature may time out or fail to return results entirely. This is most commonly caused by browser compatibility issues rather than a problem with your account, quota, or internet connection. This article explains the root cause and walks you through the steps to resolve it. ⚠️ What You Might See - Keyword suggestions fail to load after clicking generate - A timeout or loading spinner that never completes - The page becomes unresponsive during keyword generation - No error message is shown, but results do not appear These symptoms are consistent with a browser-level compatibility issue affecting how Content Genius processes and returns keyword data. Switching to a supported browser resolves the issue in most cases. ✅ Supported Browsers Content Genius keyword generation is fully tested and supported on the following browsers: - Google Chrome (latest stable version) — recommended - Microsoft Edge (Chromium-based, latest stable version) If you are using Safari, Firefox, or any other browser, keyword generation may time out or behave inconsistently. This is a known compatibility limitation and the most frequent cause of this issue. 🛠️ Step-by-Step Fix 1. Switch to Google Chrome or Microsoft Edge. If you are not already using one of these browsers, download and install the latest stable version before continuing. 2. Open Search Atlas in your supported browser and navigate to Left sidebar → Content → Content Genius (page title: "What are we writing today?") at /content/seo-content-assistant. 3. Clear your browser cache. In Chrome or Edge, press Ctrl + Shift + Delete (Windows) or Cmd + Shift + Delete (Mac), select Cached images and files and Cookies and other site data, then click Clear data. 4. Disable browser extensions. Some ad blockers or privacy extensions can interfere with API requests. Open an Incognito / InPrivate window to test keyword generation without extensions active. 5. Reload the Content Genius editor and attempt keyword generation again. Results should now load without timing out. 🔄 If the Issue Persists After Switching Browsers If you are already using Chrome or Edge and still experience timeouts, try the following additional checks: - Check your network connection. A slow or unstable connection can cause requests to time out. Try switching to a wired connection or a different network. - Confirm you have an active Content Genius session. If your session has expired, log out and log back in before retrying. - Test with a shorter content brief. Very long documents or briefs with a high volume of content may take longer to process. Try generating keywords on a shorter draft to isolate whether document length is a factor. - Avoid running multiple Content Genius tabs simultaneously. Opening several editor sessions at once can cause request conflicts that lead to timeouts. 📋 Quick Reference: Common Causes and Fixes - Unsupported browser (Safari, Firefox, etc.) → Switch to Chrome or Edge - Browser extensions blocking requests → Test in Incognito / InPrivate mode - Stale cache or cookies → Clear browser data and reload - Unstable network connection → Switch networks or use a wired connection - Expired session → Log out and log back in - Multiple editor tabs open → Close extra tabs and retry in a single session 💬 Still 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 Content Genius AI Credits Depleted Error

🔍 Overview When generating articles in Content Genius, Search Atlas uses AI credits to power each piece of content. If your credits are depleted, article generation will stop working. This article explains what to do if you encounter this issue. ❓ Why Article Generation May Stop Working If you are unable to generate articles in Content Genius, the most likely cause is that your account's AI credits have been depleted for the current billing period. 🚀 What to Do If Your AI Credits Are Depleted If your AI credits are depleted and you are unable to generate articles, please contact our support team directly. A team member can review your account, confirm your current credit status, and advise you on the available options to restore access to article generation. 📋 What to Have Ready When Contacting Support To help the support team resolve your issue as quickly as possible, please have the following information available: - Your Search Atlas account email address - The approximate date when article generation stopped working - The name of the blog or project where you encountered the issue - Any error message displayed when attempting to generate an article 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 Twitter Cards Write Button Not Generating AI

🔍 What Is This Issue? When you open a Twitter Card in the OTTO SEO V3 section and click the Write button, you expect Search Atlas to automatically generate AI-powered fix suggestions. Instead, a blank manual input box appears and no AI content is produced. This happens because the Twitter profile URL stored in your Knowledge Base is outdated or not properly saved. Search Atlas uses this URL to pull context for AI generation — if it is missing or stale, the AI cannot proceed and falls back to a manual input prompt. 🗺️ Where This Happens This issue occurs inside the OTTO SEO V3 tool. To get there, go to the left sidebar and click OTTO SEO V3. From your site's overview, navigate to the Twitter Cards section and locate any card flagged for a fix. Click Write on any flagged card to reproduce the issue. 🛠️ How to Fix It The solution is to re-enter and save your Twitter profile URL in the Knowledge Base. Follow these steps carefully: 1. In the left sidebar, click OTTO SEO V3 to open the OTTO SEO V3 dashboard. 2. Locate the Knowledge Base section within the OTTO SEO V3 settings. This is typically found in the site configuration or settings panel for your connected property. 3. Find the field labelled Twitter Profile URL (it may currently be blank, contain an old handle, or show a broken link). 4. Clear the existing value completely, then type or paste your correct, full Twitter profile URL. Use the format https://twitter.com/yourhandle or https://x.com/yourhandle — both are accepted. 5. Click Save or Update to confirm the change. 6. Return to OTTO SEO V3 in the left sidebar, navigate back to the Twitter Cards section, and click the Write button on a flagged card again. The AI content generator should now activate automatically and produce suggested fixes instead of opening a manual input box. ✅ How to Confirm the Fix Worked After completing the steps above, the Write button should immediately trigger AI-generated copy suggestions for your Twitter Card fields — such as the title, description, and image alt text — without showing a blank manual input prompt. If AI content appears, your Knowledge Base URL has been successfully refreshed. ❓ Frequently Asked Questions Why does the URL go stale? If your Twitter handle was recently changed, your account was migrated from Twitter to X, or the Knowledge Base was set up without a URL initially, the stored value may be missing or no longer valid. Search Atlas cannot auto-detect handle changes, so a manual update is required. Will this fix affect other AI features? Yes — keeping your Twitter profile URL current in the Knowledge Base also improves AI suggestions in other social metadata fields that reference your brand's social presence. What if I do not have a Twitter or X profile? If your site does not use Twitter Cards or you do not have a profile, leave the field blank and consider disabling Twitter Card audits in your OTTO SEO V3 settings to avoid false flags. Do I need to re-crawl my site after updating? No re-crawl is needed. The Knowledge Base update takes effect immediately for AI generation tasks. 💬 Still 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.

🎓 Course Video Access and Content Format in SCHOLAR

📚 Overview The AI Search and SEO Mastery course lives inside the SCHOLAR module. Modules across this course use a mix of content formats — some include embedded video lessons, while others are structured as text-based reading material. If videos are not playing in certain modules, the cause may be the module's content format, a browser issue, or a platform loading error. This article explains what to expect and how to resolve selective playback problems. 🗺️ How to Access the SCHOLAR Module 1. Log in to your Search Atlas account. 2. In the left sidebar, go to Content → Scholar to open the SCHOLAR module. 3. Select the AI Search and SEO Mastery course from the course library. 4. Use the course outline to navigate between modules. 🎬 Content Format by Module Not every module in the AI Search and SEO Mastery course contains a video. Some modules are intentionally designed as text-based reading lessons with no embedded video player, while others include an embedded video lesson. If a module does not display a video player at all, that may be expected behaviour for text-only modules — a missing video player is not necessarily a playback error, as the lesson content may be delivered entirely through written material. If you are unsure whether a specific module should contain a video, please reach out to our support team (see below) with the module name or number so we can confirm its intended format. 🔧 Troubleshooting Selective Video Playback Failures If you see a video player in a module but it will not load or play, follow these steps before escalating: 1. Confirm the module contains a video. Check the module outline or lesson header. Text-only modules will not have a player. If no player appears, the module may be intentionally text-based. 2. Hard-refresh the page. Press Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac) to clear the cached version of the page and reload fresh assets. 3. Try a different browser. Open the course in a second browser such as Chrome, Firefox, or Edge to rule out a browser-specific rendering issue. 4. Disable browser extensions. Ad blockers, privacy extensions, and script blockers can prevent embedded video players from loading. Temporarily disable all extensions and reload the module. 5. Check your internet connection. Video content requires a stable connection. Run a quick speed test and reconnect if your signal is weak or intermittent. 6. Clear cookies and site data. In your browser settings, clear cookies and cached data for the Search Atlas platform, then reload the module. 📩 When to Contact Support If none of the troubleshooting steps above resolve the issue, or if you need confirmation on whether a specific module is supposed to contain a video, please escalate to our team. When you do, have the following ready: - The exact name or number of the module where the issue occurs - A description of what you see (e.g. no player visible, player visible but not loading, error message shown) - The browser and device you are using - Any error messages displayed on screen 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 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.

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

🛠️ Content Genius Job Failures and Credit Restoration

🔍 Overview Some customers have encountered failed Content Genius jobs. This is a known platform issue that has been identified and addressed by the engineering team. If your article jobs failed, your content credits will be restored once the fix is fully deployed to your account. ⚠️ What Causes This Error The failure is caused by a platform-level bug in the Content Genius workflow — it is not related to your settings, keywords, or content brief. You do not need to change anything in your setup. ✅ What You Should Do Right Now 1. Check your Content Genius job history and identify all articles showing a failed status. Make note of the exact number of failed jobs — this count will be used to verify the correct number of credits is returned to your account. 2. Re-run the failed jobs. Once the engineering fix is deployed to your account, navigate to Content Genius, locate the failed articles, and resubmit them for generation. The underlying bug will have been resolved and the jobs should complete successfully. 3. Verify your credit balance. After the fix is deployed, confirm that credits for all failed jobs have been restored. The restoration is handled on the backend by the Search Atlas team — you do not need to submit a manual refund request. 4. Contact the Search Atlas support team if your credits have not been restored or if jobs continue to fail after the fix has been deployed. Reach out through the support contact options available in your account so a team member can investigate and manually restore your credits if needed. 💳 How Credit Restoration Works Once the engineering fix is confirmed as deployed, the Search Atlas team will restore your full credits for the failed jobs. This restoration is handled on the backend — you do not need to submit a manual refund request. You will receive confirmation from the team once the credits have been returned to your account. 🚀 After Credits Are Restored 1. Verify that the correct number of credits has been returned by confirming your credit balance within your account. 2. Resume article generation in Content Genius as normal. 3. If you experience further failures after the fix has been deployed, contact the Search Atlas support team immediately. 📋 Summary - Content Genius job failures are caused by a known platform bug, not a user error. - Note the number of failed jobs, then re-run them once the fix is deployed to your account. - Credits are restored on the backend by the Search Atlas team — no manual refund request is needed. - Confirm your credit balance after the fix is deployed, and contact support if credits are missing or failures continue. 💬 Need Help? If your credits have not been restored or if you continue to experience failures, please contact the Search Atlas support team through the chat or email options available in your account. A team member will investigate and manually restore your credits if needed.

⚕️ Content Genius Accuracy for Healthcare Clients

🎯 What This Article Covers Content Genius is an AI writing tool built for SEO-focused content at scale. If you manage content for a healthcare client — such as an addiction treatment centre — this article explains what Content Genius does well, where human oversight is essential, and how to build a reliable workflow that meets both search and compliance goals. ✅ What Content Genius Does Well Content Genius is designed to help you produce structured, SEO-focused articles quickly. For healthcare clients, it can help with: - Topic generation and keyword targeting: It surfaces relevant topics based on your target keywords, helping you build a content calendar efficiently. - Content structure and readability: Articles follow logical heading hierarchies, making them easier for readers and search engines to navigate. - Calls-to-action (CTAs): You can include CTA instructions in your brief or prompt, and Content Genius will incorporate them into the article. - Bulk production: Content Genius supports queuing multiple articles at once, making higher-volume monthly output more manageable. ⚠️ Important Limitations for Healthcare Content AI-generated content — from any platform — carries specific risks in regulated industries like healthcare and addiction treatment. You must be aware of the following before publishing at scale: - Statistics and citations are not automatically verified. Content Genius may reference statistics or studies, but it does not browse live sources or guarantee factual accuracy. Every statistic should be manually checked against authoritative sources before publication. - Medical claims require expert review. AI can produce plausible-sounding health content that contains inaccuracies. For addiction treatment specifically, false or misleading claims can carry serious compliance implications. A qualified clinical reviewer should approve all medical assertions. - Compliance standards vary by state and channel. Regulations and platform-specific rules impose strict content requirements that Content Genius does not apply automatically. - Content Genius does not replace a medical or legal review process. It is an SEO writing assistant, not a compliance tool. 🛠️ Recommended Workflow for Healthcare Content at Scale Use this process to produce content responsibly at volume: 1. Build your brief carefully. In your Content Genius prompt, specify the target audience, required disclaimers, preferred sources, CTA language, and any topics to avoid. The more specific your brief, the more usable the output. 2. Review all statistics before publishing. Cross-reference any figures or study references against authoritative sources such as SAMHSA, NIH, or CDC. 3. Have a qualified clinical reviewer approve medical claims. Do not publish assertions about treatment outcomes, drug interactions, or recovery statistics without expert sign-off. 4. Apply your compliance checklist. Run each article through your internal review process for applicable regulations and platform policies before it goes live. 5. Treat Content Genius as a first draft, not a final product. The tool accelerates production; your team is responsible for accuracy and compliance. 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 Data Access Issues Fast

🧭 Overview Content Genius is Search Atlas's AI-powered writing and optimization suite found under the Content section of the platform. If you're seeing missing data, blank results, or errors when trying to access Content Genius features, this guide explains what to check and how to escalate if the issue persists. ⚠️ Common Reasons Data May Be Unavailable Before escalating, it helps to understand why Content Genius data may not be loading correctly. The most frequent causes include: - No project or domain connected — Content Genius needs an active project to pull data against. - Data not yet imported — If you recently set up your account, your site data may not have been imported yet. - Integrations not connected — Third-party integrations such as Google Search Console or Google Analytics may be missing, limiting the data available. - Temporary loading delay — Large sites or freshly connected domains can take some time to process. - Browser or session issue — Cached data or an expired session can occasionally prevent content from loading. 🛠️ What to Try First 1. Confirm a project and domain are active. Check that you have a project set up and a domain associated with it. If no project exists, you will need to create one before Content Genius tools can surface data. 2. Check that your integrations are connected. From the top-right avatar, go to Settings → Integrations, and verify that any relevant third-party integrations are linked. Missing integrations can reduce the data Content Genius is able to show. 3. Allow time for data to process. After connecting a new integration or setting up a project, wait a little while before returning to the Content section, as data may still be processing. 4. Refresh your browser. Try a hard refresh or clear your browser cache, then reload the page. 5. Try a different browser or incognito window. This rules out session or extension-related issues. 📋 When to Contact Support If none of the above steps resolve the issue, a support agent will need to investigate your account directly. To help us resolve this as quickly as possible, please have the following ready when you reach out: - Your project name and the domain you are working with - The specific Content Genius feature or section where data is missing - A description of any error message you are seeing (or a screenshot if possible) - The approximate time you first noticed the issue 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.

💡 Understanding Content Genius Web Access Limits

🔍 Overview Content Genius is Search Atlas's AI-powered writing assistant, designed to help you create optimized, high-ranking content. Some customers notice that Content Genius does not browse the live web in real time — this article explains why, and how the tool still delivers content recommendations. 🤔 Why Content Genius Doesn't Access the Live Web Content Genius is built on an AI model combined with Search Atlas's SEO data infrastructure. Rather than crawling the web live during each session, it draws on Search Atlas's internal datasets to generate content recommendations. This means outputs are based on indexed and processed data rather than real-time web browsing. 🖼️ Image Generation and Editing Content Genius is focused on text-based content creation — writing, optimizing, and structuring articles for SEO. Image generation and image editing are not part of Content Genius's current feature set. If your workflow requires custom images, we recommend using a dedicated image generation tool alongside Content Genius for your written content. 📊 Competitor Research Limitations Because Content Genius does not browse the live web, it cannot perform real-time competitor research or pull live data from competitor websites. Content generated by the tool is based on Search Atlas's internal datasets rather than on-the-fly web crawling. If your workflow requires up-to-the-minute competitor data, consider using dedicated SEO research tools alongside Content Genius. 💬 Submitting a Feature Request If live web access or image generation are important to your workflow, we encourage you to submit a feature request so our product team can consider these capabilities for future updates. To submit a feature request, contact our support team via the chat widget in the bottom-right corner of the platform and let the team know the specific capability you need (e.g., real-time web browsing, image generation inside Content Genius). Our product team reviews all submissions and uses them to inform the roadmap. ⚠️ Common Questions - Will Content Genius ever support live web access? This is not a confirmed planned feature at this time, but feature requests are reviewed by the product team. - Can I use another Search Atlas tool for live competitor data? Other Search Atlas tools such as site audits and keyword research modules pull regularly refreshed data that can complement your Content Genius workflow. 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.

🖼️ Brand Vault Images in Content Genius

🔍 What This Article Covers If you are using Content Genius, eligible images from your Brand Vault library can be matched to image placeholders in the article during content generation. This article explains how this works. ⚠️ The Current Limitation Content Genius does not currently have the ability to pull or reference images stored in your Brand Vault. When generating or editing content, the tool will not automatically retrieve logos, product photos, or other brand assets you have uploaded to the Brand Vault. This means that even if your Brand Vault is fully populated for a domain, Content Genius operates independently and will not surface those images during the writing process. This is by design and applies to all accounts and domains. It is not specific to any individual workspace or website. 💡 Why This Happens Brand Vault and Content Genius are separate features within Search Atlas. The Brand Vault is designed to store and organize your brand assets for reference and brand consistency. Content Genius, on the other hand, focuses on generating SEO-driven written content based on your keywords, topics, and instructions. Because these tools were built to serve distinct purposes, image data from the Brand Vault is not wired into the Content Genius generation pipeline. This keeps each tool lightweight and focused on its core function. 🛠️ Workarounds You Can Use Today While Content Genius cannot access Brand Vault images directly, there are several easy ways to incorporate your brand visuals into the content you produce: - Copy image links manually: If your Brand Vault images are hosted on a publicly accessible URL, you can copy the direct image link and paste it into your content after generation. - Upload images after generation: Generate your content in Content Genius first, then manually insert your Brand Vault images into the final document before publishing. - Use your CMS media library: If you are pushing content to a CMS like WordPress, add your Brand Vault images through the CMS media uploader after the Content Genius draft is published or exported. - Reference image filenames in your prompt: Include the names or descriptions of the images you want to use within your Content Genius instructions. While the tool will not insert the actual image, the generated content can include placement notes such as [Insert product photo here] to streamline your editing workflow. 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 Article Generation Errors in Topical Maps

🔍 Overview When you attempt to generate articles from Topical Maps and see the error "Article generation could not be started for the selected titles", this is almost always caused by AI premium quota exhaustion — not a technical platform issue. This article explains what that means and how to resolve it. ⚠️ What This Error Actually Means The error message appears when your account's AI premium credits have been fully used up. Content Genius features — including article generation from Topical Maps — consume AI premium credits each time they run. Once your quota reaches zero, new generation requests cannot be started and this error is displayed. This is not a temporary queue issue or a backend timeout. The platform is correctly blocking the request because there are no credits available to fulfil it. Refreshing the page or retrying will not resolve it. 📊 How to Check Your AI Premium Quota Before purchasing credits, confirm that quota exhaustion is the cause by checking your current AI premium credit balance in your account settings. If your balance is depleted, quota exhaustion is confirmed as the cause of your error. 💳 How to Purchase Additional AI Credits Once you have confirmed your quota is exhausted, navigate to your account settings and locate the option to add more AI premium credits. Select a credit package and complete the purchase. After payment is confirmed, your new credits will be applied to your account and you will be able to resume article generation. ✅ How to Resume Article Generation After Adding Credits With credits restored, return to Topical Maps and retry your generation: 1. Navigate to Content → Topical Maps in the left sidebar. 2. Select the titles you want to generate articles for. 3. Trigger article generation as you normally would. 4. The error should no longer appear and generation will start as expected. 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 Image Upload Validation Errors

This article explains what to do if you encounter upload or generation errors in Content Genius, including errors that prevent your image from being validated or processed. These errors can appear during image uploads or content generation workflows. 📍 Where to Find It Open Content → Content Genius (What are we writing today?) in your Search Atlas account. The error will appear in the editor when an image fails to process during generation or upload. 🛠️ Step-by-Step 1. Note the exact error message you are seeing. Error messages vary and the specific wording will help our team identify the cause quickly. Copy or screenshot the full error text before attempting any other steps. 2. Try re-uploading the image. Close the editor, return to Content Genius, and attempt the upload again. Transient errors sometimes resolve on a second attempt. 3. Try a different browser. If the error persists, test in a second browser (e.g., Chrome or Firefox) to rule out a browser-specific conflict. 4. Clear your browser cache and retry. A stale browser session can occasionally cause upload or generation failures. Clear your cache, refresh the page, and attempt the upload once more. 5. If you are uploading via a URL, verify the image is publicly accessible. Paste the URL into a private/incognito browser window to confirm the image loads without requiring a login. If it does not load, download the image to your device and upload the file directly instead. ✅ Before Contacting Support If the error continues after following the steps above, please have the following information ready so our team can investigate as quickly as possible: - The exact error message text or a screenshot - The image file name or URL you were attempting to upload - The name of the Content Genius project or document where the error occurred - The approximate date and time 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 Images Not Displaying in Content Genius

Images Not Displaying in Content Genius Some users have reported that images do not display correctly in articles generated by Content Genius. If you are experiencing this issue, there are several steps you can try yourself before reaching out to support. Steps to Try First 1. Refresh the page: A simple browser refresh can resolve temporary rendering issues. Press F5 or Ctrl+R (Cmd+R on Mac) and check whether the images load. 2. Clear your browser cache: Cached data can sometimes prevent images from displaying correctly. Clear your browser cache and cookies, then reload the Content Genius article. 3. Re-insert the image: In the Content Genius editor, remove the image block that is not displaying and re-add the image by uploading it again or re-inserting it from your image source. 4. Check the image source URL: If the image is referenced from an external URL, confirm that the URL is still valid and publicly accessible. Broken or expired links will prevent images from rendering. 5. Try a different browser: Test the article in a different browser to rule out a browser-specific issue. 6. Check the published article: If images appear correctly in the editor but not in the published version (or vice versa), note which environment is affected, as this helps narrow down the cause. If Images Still Do Not Display If the steps above do not resolve the issue, our support team can investigate further. Before reaching out, please have the following ready: - Project or article name: The exact name of the Content Genius article where images are not displaying. - Description of what you see: What you observe where the image should appear. - Which steps you already tried: The troubleshooting steps above that you have already attempted. - When the issue started: The date and approximate time you first noticed images were missing. - Screenshots: A capture of what the affected image area looks like in your editor or published article. 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.

🛠️ Content Genius Blank Pages: What to Know

🔍 What Is This Issue? Some users creating articles in Content Genius — including content generated from topical maps — have encountered blank pages instead of the expected generated content. Rather than producing a draft, the tool returns an empty document with no text. This was caused by an underlying bug (tracked internally as CG-2657) that triggered an empty content error during article generation. The engineering team identified the root cause, completed a fix, and has shipped the resolution. 📊 Current Status The fix for this issue has been completed, passed internal code review and QA, and has been released. If you were affected by this bug, the issue should no longer occur when generating articles in Content Genius. ✅ What You Should Do Now 1. Go to Left sidebar → Content → Content Genius. 2. Try generating an article again using your preferred method — for example, writing a new article or generating from a topical map. 3. If a blank page appears again, note the exact steps you followed before the blank result occurred, including any topical map or keyword used. This detail will help the support team investigate quickly. 💡 Tips to Reduce Generation Errors - Avoid leaving the page during generation. Navigating away while an article is being created can interrupt the process and result in an empty draft. - Try one article at a time first. If you plan to use bulk generation, test with a single article first to confirm generation is working before scaling up. - Refresh and retry. If you see a blank result, refresh the page and attempt generation again — transient errors sometimes resolve on a second attempt. - Check your document title. If a document is created with the default title and no content, this is a sign the generation did not complete. Delete the empty draft and try again. 🚀 If the Problem Persists If you are still seeing blank pages after the fix has been applied, this may indicate a separate or environment-specific issue that needs investigation. 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.

💡 Understanding the Content Genius Folder Settings Warning

📋 Overview If you have seen a warning message in Content Genius related to folder settings, you are not alone. This message can appear unexpectedly and cause confusion about whether something is broken or requires urgent action. This article explains what the warning means, why it appears, and what steps to take. 🔍 What Does the Warning Message Mean? The folder settings warning in Content Genius is an informational prompt, not an error that blocks your work. It appears to let you know that your current folder configuration may not be fully optimised for organising and saving your content projects. Nothing has gone wrong with your account — the platform is simply guiding you to review your setup. Common reasons the warning appears include: - You have not yet created or assigned a folder for your Content Genius projects. - A previously assigned folder has been deleted or renamed. - Your workspace has been updated and folder associations need to be refreshed. 🛠️ How to Resolve the Warning Follow these steps to review and update your folder settings so the warning no longer appears: 1. In the left sidebar, navigate to Content to open the Content section. 2. Open Content Genius (also accessible at /content/seo-content-assistant). 3. Locate the warning message banner at the top of the page and click the settings link or button within it. 4. In the folder settings panel, review the currently assigned folder. If no folder is assigned, create a new one or select an existing folder from the dropdown. 5. Confirm your selection by clicking Save or Apply. 6. Refresh the page. The warning should no longer appear once a valid folder is assigned. ❓ Do I Need to Update My Folder Settings Immediately? The warning does not prevent you from creating or editing content in Content Genius. You can continue working normally while the warning is present. However, resolving it is recommended because: - Assigning a folder keeps your projects organised and easy to find later. - It ensures that any content you generate is saved to the correct location in your workspace. - It prevents the warning from reappearing on future visits. ⚙️ Related Content Tools You May Be Using While you are in the Content section, you may also find these tools useful for your workflow: - On-Page Audit — Analyse and improve individual pages for on-page SEO signals. - Topical Maps — Plan content clusters around core topics. - Content Planner — Schedule and manage your content pipeline. - Meta Generator — Quickly generate optimised meta titles and descriptions. - AI Content Templates — Use pre-built templates to speed up content creation. 💬 Still Seeing the Warning? If you have followed the steps above and the folder settings warning continues to appear, or if you cannot locate the settings option within the banner, our support team is ready to help. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

✍️ Content Genius Fixes and Responsiveness Update

Content Genius received four bug fixes and a responsiveness improvement on July 2, 2026, making the platform more stable and easier to use across all screen sizes. ✨ What's New This release ships one improvement and four targeted bug fixes across the Content Planner and meta tags generator: - Responsive meta tags generator: The meta tags generator drawer now adapts correctly to small screens, ensuring all controls and output remain accessible regardless of window size. - Clickable Page Issues URLs: URLs inside the Page Issues modal are now clickable and open in a new browser tab, making it faster to act on flagged issues. - Content Planner scrollbar flicker fixed: The scrollbar in the cluster modal no longer flickers, resulting in a smoother browsing experience. - Pagination reset on starring fixed: Starring a row in the Content Planner no longer resets your current pagination position, keeping you on the right page. - Star toggle filter preservation: Toggling the star on a row no longer overwrites or collapses the active filtered AI template list. 🛠️ How to Use It 1. In the left sidebar, go to Content → Content Planner (Content Planner | searchatlas.com). 2. In the Content Planner, verify that starring rows preserves your current page and active filters. 3. Click any URL inside the Page Issues modal to confirm it opens in a new tab. 4. Open the Meta Generator on a smaller browser window or device to see the responsive layout in action. 📋 What to Expect - All four fixes apply automatically — no configuration changes are required. - The meta tags generator drawer responsiveness improvement affects viewports narrower than standard desktop widths; behavior on full-size screens remains unchanged. - Existing starred items and saved filters in the Content Planner are unaffected by this update. 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 a Stuck Execution in Progress Article Lock

🔍 What Is This Issue? Sometimes a Content Genius article can get stuck in an "Execution already in progress" state (also shown as a 409 error). When this happens, the article appears locked and every attempt to run an AI edit is blocked or automatically restarted. This is caused by a server-side process that failed mid-flight and did not release its lock on the article. This is a known platform issue that our engineering team has identified and fixed at the system level. However, individual articles can still become stranded if they were in progress at the time of the failure. The good news: once the backend lock is cleared, your article becomes fully editable again and any AI credits consumed by the failed operation can be restored. ⚙️ What Causes This? - The AI generation pipeline fails partway through a task (for example, during the research step) and does not clean up its progress state. - The article remains flagged as AI_IN_PROGRESS on the server even though no active process is running. - Any new AI edit request detects the existing flag and refuses to start, creating a loop. ✅ Steps to Resolve 1. Stop retrying the edit. Repeatedly attempting to start a new AI edit while the lock is active will not help and may complicate the resolution. 2. Note your article details. Before contacting support, write down the affected article name or page ID — this allows the support agent to locate and clear the lock as quickly as possible. 3. Contact the Search Atlas support team via the in-app chat. This lock can only be cleared on the backend by our team. Open the chat widget inside Search Atlas, describe the stuck lock, and share the article name or page ID. A support agent will manually remove the stuck AI_IN_PROGRESS flag from the affected article on the server side and confirm once it is done. If you need help reaching the chat, type human teammate in the chat widget in the bottom-right corner of the platform to be connected with a member of our team. 4. While you wait, confirm the article is truly stuck. Check whether the article status still shows the lock after waiting at least 5 minutes without any retries. If the lock clears on its own, proceed directly to step 5. 5. Return to the article in Content Genius. After you receive confirmation that the lock has been cleared (or if it cleared on its own), navigate back to Content → Content Genius (What are we writing today?) and open the previously locked article. 6. Retry your AI edit. Attempt the AI edit again. It should now proceed without errors. If the 409 error appears again, reply in the same support chat thread immediately — do not start a new conversation — so the agent can investigate further without losing context. 7. Request a credit review in the same conversation. If the failed execution consumed AI premium quota, tell the support agent during the same conversation. Provide the article name and the approximate date and time the failure occurred. Our team can review your account and restore any credits lost due to the stuck process. 💡 Tips to Avoid This in the Future - If an AI edit appears to be running for an unusually long time without completing, do not refresh the page repeatedly or navigate away and back in quick succession — allow it to finish or time out naturally first. - If you must navigate away, wait at least 2–3 minutes before returning and retrying, so any in-flight server process has time to resolve or fail cleanly. - If you see the 409 error immediately on your first attempt (not after a timeout), contact support right away rather than retrying multiple times. If you are still experiencing this issue after following these steps, please reach out to our support team via the in-app chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 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!

🔧 Fix Content Genius to Link Lab Bridge Failures

Overview After running a Guest Post Backlink campaign, some users are unable to push articles from Content Genius to Link Lab for publication. When this happens, the platform may report that the bridge between the two tools is blocked or unavailable. This is a known platform-level integration failure. Is This Happening to You? - You ran a Guest Post Backlink campaign in Link Lab. - You tried to push a completed article from Content Genius to Link Lab. - The platform returned an error indicating the bridge is blocked or unavailable. If this matches your situation, follow the self-service steps below before contacting support. What You Should Do 1. Refresh your session. Log out of Search Atlas completely, clear your browser cache, and log back in. Then navigate back to Content Genius and attempt the article push again. 2. Check the status of your Guest Post Backlink campaign in Link Lab. Open Link Lab, locate the campaign that was active when the error occurred, and confirm its status. If the campaign shows a pending, paused, or error state, wait for it to reach an active or completed state before retrying the push from Content Genius. 3. Retry the article push from Content Genius. Once your campaign status is confirmed as active or completed, return to Content Genius, open the article, and attempt to push it to Link Lab again. In many cases this resolves the bridge failure without further intervention. 4. Try pushing to a different or newly created Guest Post Backlink campaign. If the error persists on the original campaign, create a new Guest Post Backlink campaign in Link Lab and attempt to push the article to that campaign instead. 5. If none of the above steps resolve the issue, contact our support team. Take a screenshot of the exact error message and note the name of the campaign that was active when the error occurred. Share both with our team so they can investigate the integration failure at the account level and get your article submitted successfully. Background: What Causes This Issue A failure in the integration layer between Content Genius and Link Lab can prevent article submissions from going through when a Guest Post Backlink campaign is active. Campaign status conflicts or session-level issues are common triggers that can often be resolved by refreshing your session or targeting a different campaign. If the issue persists, it requires our support team to investigate on a per-account basis. Tips to Avoid Delays - Always record or screenshot any error message you see — exact error text helps our team pinpoint the cause faster. - Note the name of the Guest Post Backlink campaign that was active when the error appeared, as this helps our team identify the source of the conflict. Still Need Help? If you have followed the steps above and are still experiencing this issue, please reach out to our support team via the live chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team so we can investigate the bridge failure for your account and help you complete your article submission.

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

🛠️ Fix Content Genius Workflow Failed Errors

🔍 What This Article Covers Some users encountered a persistent Workflow failed error when trying to generate articles in Content Genius. Even after clearing the browser cache, performing a hard refresh, or switching to an incognito window, the error continued to appear — and in some cases, the article page became permanently stuck in a loading or in-progress state. This article explains what caused the issue, confirms it has been resolved, and tells you what to do if you are still experiencing it. ⚙️ What Caused the Issue The root cause was a bug in the Content Genius article generation pipeline. When the background generation process failed partway through, the system did not correctly clean up the job. As a result, the article page remained stuck in an AI in progress state indefinitely, and new generation attempts continued to fail. This was an internal platform-side issue — not caused by anything in your browser, account settings, or content inputs. Browser troubleshooting steps such as clearing cache or using incognito mode did not resolve it because the problem existed in the generation pipeline itself. ✅ The Fix Is Now Live Search Atlas engineering identified and resolved this bug. The fix was reviewed, tested through quality assurance, and deployed to the platform. Articles that were stuck in a failed or in-progress state should now be recoverable, and new article generation attempts should complete successfully. 🚀 Steps to Try After the Fix 1. Navigate to Content → Content Genius (What are we writing today?) in your Search Atlas account. 2. Locate the article that was stuck or that previously returned a Workflow failed error. 3. Attempt to generate or re-generate the article as you normally would. 4. If the article is still showing an in-progress or failed state, try starting a new article to confirm whether generation is working on your account. 5. If the new article generates successfully but the original stuck article does not recover, you may need to recreate that article from scratch. 6. Try a different browser. If the error only appears in one browser, it is likely a local browser issue rather than a platform bug. 💡 When to Contact Support If you are still seeing Workflow failed errors or articles stuck in a permanent loading state after following the steps above, the issue may need to be investigated by our team directly. Before reaching out, capture a recording or screenshot of the error — this will speed up escalation to our engineering team. 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.

💡 Get Help Inside Content Genius Tool

🧭 What Is Content Genius? Content Genius is Search Atlas's AI-powered content suite. It brings together several tools designed to help you plan, write, and optimise content from a single workspace. The suite includes tools such as the SEO Content Assistant, On-Page Audit, Topical Maps, Content Planner, Scholar, Meta Generator, and AI Content Templates. 🔍 Troubleshooting Common Issues If you are experiencing a problem with a Content Genius tool, try the following steps before escalating to support: 1. Refresh the page — Many display or loading issues resolve with a simple browser refresh. 2. Clear your browser cache and cookies — Cached data can cause tools to behave unexpectedly. Clear your cache, then log back in and try again. 3. Try a different browser or incognito window — This helps rule out browser extensions or local settings as the cause. 4. Check that your project or domain is correctly set up — Navigate to your project settings and confirm the domain is saved and verified. Some tools require a connected project to function. 5. Re-run the tool — If a report or audit appears incomplete or stuck, try closing the tab and re-opening the tool to initiate a fresh run. 6. Check your subscription plan — Certain Content Genius tools or usage limits are tier-dependent. Visit Avatar (top-right) → Billing → Plans & Top-ups to confirm your plan includes the feature you are trying to use. 📋 When to Escalate to Support If the steps above do not resolve your issue, please have the following ready when you reach out so our team can investigate as quickly as possible: - The name of the specific Content Genius tool you are using - The exact error message or behaviour you are seeing (screenshots are helpful) - The name of the project or domain you are working with - 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 'Agent Temporarily Unavailable' in Content Genius

🔍 What This Error Means If Content Genius displays the message "The agent is temporarily unavailable" and does not respond after one or more hours, this is a platform-side service disruption — not an issue with your account, browser, or internet connection. The error occurs when the underlying AI agent service encounters a server-level fault that cannot be self-corrected automatically. This type of disruption is typically resolved by the Search Atlas engineering team once it is identified and escalated. ✅ Steps to Take When You See This Error 1. Wait briefly and retry. Occasional, short-lived blips can clear within a few minutes. Refresh the page and attempt to use Content Genius again after 5–10 minutes. 2. Check that you are in the right location. Navigate to Left sidebar → Content → Content Genius to confirm you are on the correct page and not on a sub-section that may behave differently. 3. Try a different action. If you were using one feature (for example, writing an article), try selecting another available action to rule out a feature-specific issue rather than a full service outage. 4. Clear your browser cache and reload. A hard refresh can sometimes clear a stale connection state. After clearing the cache, navigate back to Left sidebar → Content → Content Genius and try again. 5. Try a different browser or an incognito window. This helps rule out any browser extension or local storage conflict interfering with the agent connection. 6. If the error persists beyond one hour, contact support immediately. This error has previously required engineering intervention to deploy a fix. The sooner our team is made aware, the faster a resolution can be deployed. ⚠️ Why Waiting Too Long Is Not Recommended Based on past incidents, this error does not resolve on its own without an engineering fix. If you have already waited one to two hours and Content Genius is still showing the unavailability message, the issue is unlikely to clear without intervention from our team. Reporting it promptly allows us to escalate to the right engineering team as quickly as possible. 💡 What Happens After You Report It When this error is reported through our support team, the following process takes place: - Your report is reviewed and escalated to our specialized engineering team. - The engineering team investigates the root cause at the server level. - Once a fix is identified, it is deployed to restore the Content Genius agent service. - Our support team will confirm with you once the issue has been resolved so you can verify everything is working correctly. In the confirmed past resolution of this exact issue, the fix was successfully deployed and the customer was able to resume using Content Genius normally after confirmation from our team. 📋 Information to Have Ready When Contacting Support To help our team escalate your report quickly, have the following details on hand before reaching out: - The exact error message you are seeing. - How long the error has been occurring. - The action you were trying to perform in Content Genius when the error appeared. - Your browser type and version. - Whether you have already tried the self-help steps above. 🙋 Need Further Help? If the steps above did not resolve the issue, or if Content Genius remains unavailable after refreshing and retrying, please reach out to our team right away. 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.

🛠️ Content Genius Keywords Not Recognized Fix

🔍 Overview Some users have experienced Content Genius displaying a 'No keywords configured' message even after keywords were added at the top of an article, or generating generic content that ignores approved keyword inputs. These issues were confirmed as platform bugs by the Search Atlas engineering team and have since been resolved. This article explains what caused the problem, what was fixed, and what steps you can take if you are still experiencing unexpected behavior. ⚙️ What Was Causing the Issue Two separate bugs were identified and confirmed as valid by the engineering team after triage and video evidence review: - Keywords not splitting correctly: When keywords were pasted into Content Genius as a comma-separated list, the platform was saving the entire string as a single keyword instead of recognizing each individual keyword. This caused the tool to behave as if no valid keywords were configured. - Content ignoring keywords and formatting instructions: Even when keywords appeared to be saved, Content Genius was generating content that did not apply the approved keywords, style instructions, or formatting requirements provided. Both bugs were developed, reviewed, and moved to a resolved status by the engineering team. The fixes have been released and validated. ✅ What the Fix Covers - Comma-separated keywords pasted into Content Genius are now correctly split and saved as individual keywords rather than a single combined string. - Content generation now properly applies configured keywords, formatting preferences, and style instructions when producing output. Note: If your account uses a default domain keyword setting (such as a broad geographic or brand-level default), this behavior may be expected by design and is not a bug. If you are unsure whether your situation falls into this category, the support team can clarify. 🚀 Steps to Take Right Now 1. Open Content Genius in your Search Atlas account. 2. If you previously saved keywords as a single comma-separated string, remove the existing keyword entry and re-enter your keywords one at a time, or paste them again now that the splitting fix is live — they should now be recognized as individual keywords. 3. Confirm that your keywords appear as separate, distinct entries before generating content. 4. Run a new content generation to verify that the output reflects your configured keywords and any style or formatting instructions you have set. 5. If the content still appears generic or the 'No keywords configured' message persists, clear your browser cache, reload the page, and try again in a fresh session. 💡 Tips to Avoid This Issue Going Forward - After entering or pasting keywords, always verify that they appear as individual items rather than a sing

🛠️ 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 Content Genius Topical Terms Keyword Display

🔍 Overview When working inside Content Genius, the Topical Terms panel is designed to display multiple recommended keywords to help you optimise your content. In some cases, you may notice that only a single keyword appears instead of the full list. This article explains what to do if you experience this display limitation. ⚙️ Why Only One Keyword May Appear A display limitation in the Topical Terms panel can result in fewer keywords appearing than expected. This is a known issue that our team can investigate and resolve on your account. 🛠️ What to Do If You See This Issue Because resolving a Topical Terms keyword display limitation typically requires a backend review of your account or document, please take note of the following before reaching out: - The name of the Content Genius document affected - The target keyword you used when creating the document - The exact number of keywords currently visible in your Topical Terms panel - The date and time you first noticed the issue Having this information ready will allow our team to investigate your specific case quickly. ✅ What to Expect Once our team reviews your account, they will be able to determine whether the Topical Terms panel data needs to be refreshed or regenerated on the backend. You do not need to take any additional steps in the platform in the meantime. 🆘 Still 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 Blog Page Redirects and WordPress Sync Issues

🔍 Overview This article covers an issue that can affect your publishing workflow in Search Atlas: articles created in Content Genius failing to sync to your WordPress site. This is a known issue that our engineering team has been made aware of. ⚠️ Blog Page Access Opening a Website Studio blog page URL directly loads that page; there is no redirect. 🔗 Known Issue: Content Genius to WordPress Sync Failures If articles you create in Content Genius are not syncing to your WordPress site, this is a known issue affecting some accounts. Because the root cause requires a backend investigation, there are no self-serve steps that are confirmed to resolve it. When escalating, please have the following ready: - The name of your Search Atlas project or workspace affected. - The exact error message or behaviour you see when attempting to sync (e.g. sync appears to succeed but content does not appear in WordPress, or an error is displayed). - The URL of your WordPress site. - The approximate date and time when the issue first occurred. Our team will investigate the connection between your Content Genius account and your WordPress destination on the backend. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

💡 Content Genius Web Browsing and Image Limitations Explained

🔍 What Is Content Genius? Content Genius is Search Atlas's AI-powered writing assistant, designed to help you create, optimize, and rework SEO content at scale. You can access it from within the Search Atlas platform. While Content Genius is a powerful tool, it has specific boundaries around web access, competitor research, and image generation. Understanding these limits will help you get the best results and avoid frustration. 🌐 Does Content Genius Have Access to the Web? Content Genius does not browse the live internet in real time. It cannot visit URLs, scrape competitor pages, or pull up-to-the-minute data from external websites during content generation. This means the following tasks are not supported directly inside Content Genius: - Visiting and analyzing live competitor URLs on demand - Pulling current pricing, statistics, or news from external sites - Verifying or inserting live hyperlinks into your content automatically - Accessing paywalled or login-protected pages The AI works from its training data combined with the context and inputs you provide inside the editor. The more specific your brief, the better your output. 🖼️ Why Can't Content Genius Generate Images? Image generation is not a feature of Content Genius. The tool is focused exclusively on text-based SEO content — articles, outlines, meta descriptions, and on-page copy. It does not include an image creation engine or integration with image generation services. If your workflow requires images, you will need to source or create them using a dedicated design or AI image tool and upload them separately into your content. 📊 How Do I Conduct Competitor Research With Search Atlas? Although Content Genius cannot browse competitor sites live, you can still bring competitive insights into your content by gathering research externally and providing it as structured context in your Content Genius brief. Here are some practical approaches: - Manually review competitor pages in your browser, note the topics, headings, and questions they cover, and paste those key findings directly into your Content Genius brief. - Use Search Atlas's keyword and backlink research tools available in the platform to gather competitive intelligence, then bring those insights into Content Genius as structured prompts or brief context. - Include specific statistics, talking points, or target keywords in your brief so the AI can incorporate them without needing to visit live URLs itself. This workflow keeps your research grounded in real data while letting Content Genius handle the writing at scale. ✍️ How to Get the Best Results From Content Genius Because Content Genius relies on the context you provide, a well-structured brief makes a significant difference in output quality. Be as specific as possible about your target audience, key points to cover, tone of voice, and any competitor insights you have gathered manually. 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 MCP Auto-Publishing to Wrong Site

What Is This Issue? When generating Content Genius articles through the MCP (Model Context Protocol) integration, some customers have reported that articles are automatically published live to an incorrect or unintended WordPress site — even when auto-publish settings are expected to prevent this. This behaviour appears to be specific to the MCP integration. Manual publishing and article generation through other methods do not reproduce the same problem. Is This Affecting You? You are likely experiencing this issue if: - You generated a Content Genius article using MCP. - The article published automatically to a WordPress site you did not intend. - Your auto-publish settings are configured to prevent automatic publishing. Immediate Steps to Take This is a known bug affecting Content Genius article generation via MCP. While the root cause is within the MCP integration itself, you can take the following steps to limit impact and help resolve the issue: 1. Pause MCP-based article generation for any projects connected to WordPress sites until the issue is resolved. This is the most effective way to prevent additional unintended publishing while the bug is being investigated. 2. Unpublish or delete the incorrectly published article directly from your WordPress site's admin dashboard (Pages or Posts > find the article > set to Draft or Trash) to remove it from public view immediately. 3. Review your connected WordPress sites in your Search Atlas account settings to confirm which site is set as the default publish destination for your MCP workflow, and correct it if it is pointing to the wrong site. 4. Check your auto-publish settings in Content Genius and ensure that auto-publish is explicitly disabled for any sites you do not want articles pushed to automatically. 5. Document the incident — note the WordPress site the article was published to, the site it should have been published to, the approximate date and time, your auto-publish settings, and any MCP workflow or prompt details you used. This will be needed if the steps above do not prevent recurrence. If unintended publishing continues after taking the steps above, our support team can investigate your account configuration directly. Please contact us and include the details you documented in step 5 so we can assist you as quickly as possible. How to Contact Support Reach out to our support team and include the following details to speed up the investigation: - The WordPress site the article was published to, and the site it should have been published to. - The approximate date and time the unintended publishing occurred. - Your current auto-publish settings. - Any MCP workflow or prompt details you used when the incorrect publishing occurred. Our team is actively investigating this issue. If you are experiencing unexpected publishing behaviour through the MCP integration that persists after following the steps above, please contact our support team so we can assist you directly.

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

🛠️ Fix Content Genius Article Generation Errors

🔍 What This Issue Looks Like When you attempt to create a new article in Content Genius, you may see a message stating that article generation is temporarily unavailable. The article fails to load or produce content even after entering your details. This is a known intermittent issue that can affect any article project and is typically caused by a platform-level or service disruption — not something on your end. 📊 What to Expect Because this issue is caused by a backend or platform-level outage, it cannot be resolved by browser-side actions alone. Our team needs to investigate and apply a fix on the platform side. The best course of action is to escalate promptly so we can look into it for your account. 🚀 How to Escalate Efficiently Before reaching out, please gather the following details so our team can investigate as quickly as possible: - The exact article title you were trying to generate when the error occurred. - The time and date the error occurred. - The exact error message text displayed on screen. - The browser and operating system you are using. Having these details ready will help our team identify whether this is an account-specific issue or a wider service disruption and resolve it 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.

🛠️ Fix Content Genius Article Generation Issues

🔍 Overview Some customers encounter two related issues inside Content Genius: the Add Links feature appears greyed out or unavailable, and the Atlas Agent article generation tool fails repeatedly without completing. These issues are typically caused by a temporary platform-side outage or backend disruption — not by a configuration error on your end. 🚨 What Is Happening When a platform-level outage affects Content Genius, article generation may fail to complete and the Add Links feature may become inaccessible as a result. Because Add Links depends on a fully generated article, any interruption to the generation process will keep that feature unavailable until the underlying issue is resolved. In these situations, there are no customer-side steps that will reliably restore functionality. The fix must be applied on the backend by the Search Atlas team. 📋 What to Have Ready When You Contact Support To help our team investigate and resolve the issue as quickly as possible, please have the following information ready before reaching out: - The name of the project or document where the issue is occurring - The exact error message you are seeing, if any - The approximate date and time when the issue started - A description of what happened — for example, whether generation started and then stopped, or never began at all - Whether the Add Links feature is also affected 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 Topical Maps Blank Screen and Failed Generations

🔍 Overview When working with Topical Maps in Search Atlas, you may encounter two related issues: clicking to view generated content opens a blank screen, or articles triggered from Topical Maps fail to generate at all. Both issues are linked to how Topical Maps hands off article jobs to Content Genius. This article explains what is known about these problems and what to have ready so our team can resolve it for you quickly. ⚠️ What Causes These Issues? These issues are related to how Topical Maps initiates and tracks article generation in Content Genius. When a generation job fails or the handoff between the two tools does not complete correctly, the result can be a blank screen where content should appear, or a silent failure with no article created. The exact cause can vary, which is why our team investigates these on a case-by-case basis. 🛠️ What to Do If You See a Blank Screen or Failure If your articles failed to generate or are not appearing, this is a bug that requires backend investigation by our team. Before escalating, please collect the following so we can resolve it as quickly as possible: - Your project name (the workspace or project where the Topical Map is located) - The exact error message displayed, if any (e.g., any failure notice shown on screen) - The titles or topics you attempted to generate articles for - The approximate date and time when the issue occurred - Steps to reproduce — what you clicked and in what order before the blank screen or failure 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.

✍️ Content Genius WordPress Sync Scroll Fix

A scrolling issue that affected the Content Genius sync-to-WordPress workflow has been resolved as part of the Content Genius release on 2026-07-21 (bugfix CG-2738), ensuring a smoother editing and publishing experience. ✨ What's New Mouse wheel scroll was not functioning correctly when syncing content from Content Genius to WordPress. This bug (CG-2738) has been patched in the 2026-07-21 release. No action is required on your end — the fix is deployed automatically to the platform. 🛠️ What To Do If You're Still Experiencing This Issue Because the source details of this fix are limited, the steps below are general browser-side remediation steps that may help if you are still seeing scroll issues after the fix was deployed: 1. Open Content Genius and navigate to the content you want to publish. 2. Proceed with the WordPress sync workflow. 3. If scroll is still not responding, hard-refresh your browser (Ctrl+Shift+R on Windows, Cmd+Shift+R on Mac) to ensure the latest version of the platform is loaded. 4. If the issue persists, clear your browser cache and reload the page, then attempt the sync again. 5. If scrolling still does not work, try using a different supported browser to determine whether the issue is browser-specific. 📋 What to Expect Mouse wheel scroll should behave normally during the WordPress sync workflow following the 2026-07-21 release. If the problem continues after following the steps above, please have the following ready when contacting support: your browser name and version, the name of the content piece you were syncing, and any error messages or unexpected behavior you observed. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

💡 Fix 'Article Generation Could Not Be Started' Error

🔍 Overview If you encounter an error when trying to add or generate blog articles in Content Genius, the most common cause is that your account has run out of AI article generation credits. This article explains why it happens and what you can do to get back up and running. ⚠️ What Causes This Error? Content Genius uses AI credits each time you generate a full article. Your plan includes a set number of these credits per billing cycle. The error appears when your AI article generation credits for the current billing period have been fully used. ✅ How to Resolve the Issue If your AI article generation credits have been exhausted, you will need to wait until your billing cycle renews or contact our support team to discuss your options for continuing to generate articles. When reaching out, please have your account email, a description of the error you are seeing, and the date the issue began ready so we can assist you 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.

🛠️ Troubleshooting AI Content Generation and Language Issues

This article covers two common Content Genius problems: AI-generated articles failing to produce output, and content being written in the wrong language despite your settings. At this time, there is no fully documented self-serve resolution for these issues — but this article will help you prepare the right information so our team can resolve it quickly. 📍 Where to Find It Content Genius is accessed via Left sidebar → Content. Depending on the workflow you are using, the relevant tools are located at: - AI Content Templates — Left sidebar → Content → AI Content Templates - Content Planner — Left sidebar → Content → Content Planner 🛠️ What to Do If you are experiencing either of these issues, please gather the following details before contacting support so our team can investigate promptly: - Which workflow is affected — AI Content Templates, Content Planner, or both. - The exact behavior you are seeing — for example, whether generation produces no output at all, produces an error message, or produces content in the wrong language. Include the exact error message text if one appears. - The language setting you selected and the language the output was actually generated in (if applicable). - The target keyword you entered when the problem occurred. - Approximate date and time the issue occurred, including your timezone. - Your project name or workspace name as it appears in the platform. ✅ What to Expect Once our team receives the above details, they will be able to investigate the root cause — whether it relates to a generation failure, a language setting not being applied, or another underlying issue — and provide a confirmed fix or next steps specific to your account. 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 Meta Generator Wrong Language Output

🔍 Overview Some customers using Content Genius with a German-language project have noticed that the Meta Generator produces output in Dutch instead of German. This is a known bug that our engineering team is actively investigating. Because this issue requires backend investigation, there are no self-serve steps that will reliably resolve it. Please follow the guidance below to help our team identify and fix the problem for your account as quickly as possible. ⚙️ What to Have Ready When You Escalate To help our support team investigate your case efficiently, please have the following information available before reaching out: - Project name — the exact name of the project where Dutch output is appearing. - Expected language — confirm that the project is intended to generate content in German. - Where the wrong output occurs — for example, whether it happens on first generation, on regeneration, or in a specific part of the Meta Generator workflow. - A screenshot or copy of the incorrect output — showing the Dutch text that was generated instead of German. - Approximate date and time of when you first noticed the issue, including your timezone. 💡 What to Do in the Meantime - If you need meta content urgently, you can manually edit any Dutch output directly in the editor to correct the language while the bug is being resolved. - Avoid running repeated regenerations in the hope of triggering correct output, as this is unlikely to resolve the underlying issue and may consume generation credits. 🔄 Next Steps If you are experiencing this bug, please contact our support team directly so we can investigate your specific project and escalate to engineering if needed. 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.

📄 Publishing Content Genius Articles to Non-WordPress Sites

🔍 Overview Content Genius is Search Atlas's AI-powered article creation tool. Its one-click publishing feature is built exclusively for WordPress websites. If your site is hosted on a platform such as Replit, Webflow, Wix, Squarespace, or any other non-WordPress environment, the direct publish option will not be available for your site. This article explains why that limitation exists, what you can do right now to publish your content, and what to expect in the future. ⚙️ Why Publishing Only Works with WordPress Content Genius connects to your website through the Search Atlas WordPress plugin. This plugin creates a secure API link between the platform and your WordPress installation, allowing articles to be pushed directly to your CMS with a single click. Replit is a cloud-based coding and hosting environment — it does not run WordPress or expose the same plugin architecture. Because there is no compatible plugin layer, Content Genius has no way to authenticate with your Replit site or send content to it automatically. ✅ How to Publish Your Article Manually Even though one-click publishing is unavailable for non-WordPress sites, you can still create high-quality articles in Content Genius and transfer them to your Replit site manually. Follow these steps: 1. Go to Left sidebar → Content and open your article inside Content Genius. 2. Once your article is complete, click Copy or select all the text in the editor to copy the content. 3. Open your Replit project and navigate to the file or page where you want to add the article. 4. Paste the content into your site's HTML, Markdown, or template file — depending on how your Replit site is built. 5. Save and redeploy your Replit project so the changes go live. If your article contains images, download each image from the Content Genius editor first, then upload them to your Replit project's assets folder and update the image paths in your pasted content. 💡 Tips for a Smooth Manual Transfer - Use the HTML view if your Replit site is built with raw HTML — this preserves headings, bold text, and links without extra cleanup. - Use the plain-text or Markdown view if your Replit project uses a static site generator such as Jekyll or Hugo. - Check heading levels after pasting to make sure H1, H2, and H3 tags align with your site's existing structure. - Review meta titles and descriptions — copy these from the Content Genius SEO settings panel and add them manually to your page's <head> or your site's SEO configuration. 🚀 Connecting a WordPress Site for Future Use If you plan to scale your content production, consider running a WordPress instance alongside or instead of your Replit site. WordPress can be hosted on many affordable providers and unlocks the full Content Genius publishing workflow, including scheduled publishing and automatic image syncing. To connect a WordPress site to Search Atlas: 1. Install the Search Atlas WordPress plugin on your WordPress site. 2. Follow the setup steps at Left sidebar → OTTO SEO → Site Audit → Installation Guide. 3. Once connected, your WordPress site will appear as a publish destination inside Content Genius. ❓ Frequently Asked Questions - Can Search Atlas add Replit support in the future? Our engineering team evaluates new integrations on an ongoing basis. Replit support is not on the current roadmap, but customer feedback helps prioritise future development. - Will my article be saved in Content Genius even if I cannot publish it? Yes. All articles are saved to your Search Atlas account regardless of whether you publish them. You can return to edit or copy them at any time. - Can I schedule a post on a non-WordPress site? No. The schedule feature is also tied to the WordPress plugin integration and is unavailable for other platforms at this time. 🛠️ 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.

🌐 Fix Content Genius Metadata Generating Wrong Language

🔍 Overview If Content Genius generates your meta title or meta description in the wrong language — for example, Dutch instead of German — the cause is almost always one or both of two language settings being mismatched. This article walks you through exactly where to find and correct both settings so your metadata generates in the right language every time. ⚙️ Why This Happens Content Genius uses two separate language inputs when generating metadata: - The document language — set inside the Content Genius editor for each individual piece of content. - The project or workspace language — a default that applies when no document-level language is explicitly set. If either of these is pointing to the wrong language, Content Genius may generate metadata in an unexpected language, even if the rest of your settings look correct. Both settings must match the language you want your output in. 🛠️ Step-by-Step Fix 1. Open Content Genius. In the left sidebar, go to Content → Content Genius. Open the article or content document that is producing metadata in the wrong language. 2. Check the document-level language setting. Inside the editor, look for the language selector — this is typically displayed near the top of the document settings panel or in the generation options before you click Generate. Confirm it is set to your target language (for example, German, not Dutch). 3. Update the document language if needed. Use the dropdown to select the correct language. If you are starting a new document, set this before generating any content or metadata. 4. Check the workspace or project default language. Navigate to your account or project settings — accessible via your Avatar Menu (👤) or the settings menu — and locate the default content language. Confirm this also matches your intended language. 5. Update the default language if needed. Change it to your target language and save. This ensures all future documents default to the correct language from the start. 6. Regenerate the metadata. Return to Content → Content Genius, open your document, and use the Generate action to regenerate your meta title and meta description. The output should now appear in the correct language. ✅ How to Confirm It Is Working After regenerating, review both the meta title and meta description fields to confirm the language is correct. If you are generating content in bulk using Write with AI in Bulk, verify the language setting before starting the batch, as each document in the queue will inherit the settings active at the time of generation. 🚫 Common Mistakes to Avoid - Only changing one setting. Both the document-level language and the workspace default must be correct. Changing only one may not resolve the issue. - Assuming the language auto-detects from your keyword. Content Genius does not automatically detect your intended output language from the keyword or topic. You must set it explicitly. - Regenerating without checking settings first. If you regenerate before fixing the language settings, you will receive the same incorrect output again. 💡 Tips for Consistent Results - Set your workspace default language once to avoid having to update it document by document. - If you produce content in multiple languages, double-check the language selector each time you start a new document before generating. - When using Write with AI in Bulk, confirm the language setting before submitting the batch to avoid regenerating multiple documents. 🆘 Still Seeing the Wrong Language? If you have updated both language settings and metadata is still generating in the wrong language, there may be a configuration issue specific to your account. 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 Article Generation Quotas by Plan

📋 Overview Content Genius lets you generate AI-written articles directly inside Search Atlas. However, the number of articles you can generate each billing period depends on your subscription plan. If you recently renewed or signed up and are seeing a quota exhaustion message, this article will help you understand your options. ⚠️ Why You May Be Seeing a Quota Exhaustion Message A quota exhaustion message typically appears for one of two reasons: 1. Your current plan does not include AI content generation. Some plans do not include an AI article generation quota. Renewing a plan that does not include this feature will not add article credits. 2. You have used your full quota for the current billing period. If your plan includes AI content generation, your quota resets each billing cycle. If you are unsure of your exact quota allowance or reset date, please contact our support team to confirm the details for your specific plan. 🔍 How to Check Your Current Plan and Quota To confirm which plan you are on and review your remaining quota, log in to your Search Atlas account and navigate to your account or billing settings. If you are uncertain which section shows your AI content generation quota, our support team can point you to the correct location for your account. ✍️ How to Resolve a Quota Exhaustion Issue Depending on the cause of your quota exhaustion message: - If your plan does not include AI content generation: You will need to upgrade to a plan that includes this feature. Review the available plan options inside your Search Atlas account settings to find one that includes an AI content generation quota. - If you have used up your quota for the current billing cycle: Your credits will reset at the start of your next billing period. If you need additional credits sooner, contact our support team to discuss your options, including whether a plan upgrade may be appropriate. 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 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.

🌍 On-Page Audit Ignores Selected Location

🔍 What You Are Seeing You run an on-page audit in Content Genius with a specific location selected, such as Easton, MD. The audit finishes normally, but when you open the completed report, the location shown is Worldwide instead of the one you picked. Rankings, search results, and competitor data in the report reflect global results rather than local ones. 💡 Why This Happens This is a known issue. When an on-page audit runs, Content Genius currently does not carry your configured target location into the audit job, so the audit falls back to the default: Worldwide. Our engineering team is aware of the behavior and is triaging it for a permanent fix. - The location selector appears to save correctly when you set up the audit. - The setting is simply not applied when the audit actually runs. - The audit itself is not broken. Content analysis, keyword coverage, and optimization suggestions are still generated; only geographic targeting is affected. 📊 How This Affects Your Report - Ranking positions and search engine results page (SERP) data reflect worldwide results, not your local market. - Competitor pages pulled into the report may differ from the local competitors you see when searching from your area. - Content scoring remains useful for your target keyword overall, but local search intent may carry less weight than expected. If you access Search Atlas through a white-label partner such as GoHighLevel, some location options in the on-page audit may appear restricted. That behavior is separate from and unrelated to this issue. 🛠️ Workarounds Until the Fix Ships 1. Add your location to the keyword. Instead of auditing a keyword like "plumber," use "plumber Easton MD." The audit reads geographic signals directly from the keyword, so results, competitors, and suggestions lean local even when the location field defaults to Worldwide. 2. Review local results manually. Run a search in your browser with your location applied, then compare the top results against the pages in your report. This helps you spot local competitors and landmarks worth mentioning in your content. 3. Re-run the audit after the fix. Once the issue is resolved, run a fresh on-page audit with your location selected so the report reflects true local data. 📋 How to Confirm Which Location Was Used 1. Open the completed on-page audit in Content Genius. 2. Check the report header or summary area, where the target location appears alongside your keyword and URL. 3. If it reads Worldwide, the audit ran with the default location, regardless of the location you selected during setup. 📣 Staying Updated and Getting Help You do not need to report the issue to be included in the fix. Watch for product update notes inside the platform announcing the resolution. 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 Quota Types Explained and Diagnosed

Overview Content Genius uses two independent quota counters to govern how much content you can create. Both counters must have available capacity for you to generate a new article. If either counter is exhausted, you will see a Quota Limit Reached error — even if the other counter still shows plenty of room. This means you can have unused article slots and still be completely blocked from creating new content if your Target Keywords quota is fully used up. The Two Quota Types - Article Quota — the total number of articles you can generate within your billing cycle. Even if many article slots remain, this alone does not guarantee you can create new content. - Target Keywords Quota — the total number of target keywords you can assign across all articles within your billing cycle. If this quota is fully used, no new article can be created, regardless of how many article slots are open. Each new article requires at least one Target Keyword to be assigned before generation can proceed. If your Target Keywords quota is at zero, the system cannot start a new article regardless of how many article slots are open. Diagnose Which Quota Is Blocking You Follow these steps to identify the exact constraint causing your error. 1. Open Content → Content Genius (What are we writing today?) in your Search Atlas account. 2. Locate your quota information within the dashboard. 3. Check your Article Quota: note how many articles have been used versus your plan limit. 4. Check your Target Keywords Quota: note how many keywords have been used versus your plan limit. 5. If your Target Keywords counter shows that used equals your limit, your keywords quota is exhausted — this is the root cause of your error. 6. If both counters show available capacity and you are still seeing the error, contact support using the instructions at the bottom of this article. How to Resolve an Exhausted Target Keywords Quota Once you have confirmed that Target Keywords are the limiting factor, you have three options. - Free up existing keywords — Review articles you have already created. If any articles contain target keywords that are no longer relevant or duplicated, edit those articles and remove unnecessary keywords. Each keyword you remove returns capacity to your quota. - Upgrade your plan — If you consistently need more keyword capacity, upgrading to a higher-tier plan increases both quota limits. Visit your account billing settings to review available plan options. - Wait for your quota to reset — Both quota counters reset at the start of your next billing cycle. If you are close to your reset date, planning your next articles around that date may be the simplest short-term solution. 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.

📘 Why AI-Generated Pages Can Stay in “AI Generating” Status

If your AI-generated pages remain in an “AI Generating” state longer than expected, this is usually related to system processing time rather than an error. This article explains why generation delays can happen and what to expect while your content is being created. ⚙️ When This Happens This situation may occur when you generate pages using Content Genius or related AI content tools, the page status shows “AI Generating” for an extended period, the pages do not load immediately after starting generation, or you are not generating content in bulk but delays still occur. 🤖 Why AI Generation Can Take Longer AI content generation runs through a shared processing queue. Delays can happen due to high server demand when multiple users generate content at the same time, pages being processed sequentially in the generation queue, or recently started generations that are still within the normal processing window. Even if you are not generating content in bulk, queue delays can still affect individual pages. ⏱️ What to Expect During Generation When pages show “AI Generating,” the content is still being processed by the system, progress may not update immediately in the interface, pages can take longer than usual during peak usage, and some pages may complete sooner than others. In many cases, pages finish generating shortly after showing progress. ✅ Confirmed Steps to Follow Follow these steps if your AI-generated pages remain in “AI Generating” status: 1. Confirm the pages are still progressing. Support can verify that pages are actively moving through the AI generation queue. 2. Check if some pages are near completion. It is normal for individual pages to finish at different times. 3. Verify there are no setup errors. Support can confirm whether any errors were detected in the content configuration or generation setup. 4. Allow additional time for completion. When pages are actively progressing, the recommended action is to wait and allow the system to finish processing. ❓ FAQs Is it normal for AI-generated pages to take over an hour? Yes. During high server activity, AI generation can take longer than usual. Does generating content in bulk cause delays? Bulk generation can increase queue time, but delays can also happen with individual pages. Should I restart generation if it takes too long? If progress is visible, it’s best to allow more time before retrying. If your AI-generated pages remain in “AI Generating” status, this usually means they are still being processed. Allow additional time for completion. 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.

🌐 Fix Content Genius Metadata Language Settings

🔍 Overview If Content Genius generates your meta title or meta description in the wrong language — for example, producing Dutch output when German is expected — the most common cause is an incorrect or missing language setting in your Brand Vault. Content Genius reads the target language directly from Brand Vault when generating and regenerating metadata. If that setting is wrong or absent, the output language will not match your expectations. This article walks you through how to identify the problem, correct your Brand Vault language setting, and regenerate your metadata in the right language. ⚙️ Step 1: Check Your Brand Vault Language Setting 1. In the left sidebar, navigate to your Brand Vault settings. 2. Locate the Language field in your brand profile. 3. Confirm the correct target language is selected (for example, German). 4. If the language is incorrect or blank, update it to the desired language and save your changes. Important: Content Genius uses this Brand Vault language directive every time it generates or regenerates metadata. An incorrect language here is the primary reason metadata appears in the wrong language. ✍️ Step 2: Regenerate Your Metadata in Content Genius After correcting the Brand Vault language setting, you need to regenerate your metadata so Content Genius picks up the updated directive. 1. In the left sidebar, go to Content → Content Genius. 2. Open the article or content piece that has the incorrect metadata. 3. Locate the meta title and meta description fields in the editor. 4. Trigger a regeneration of the metadata fields. Content Genius will now reference the corrected Brand Vault language setting and produce output in the correct language. 5. Review the regenerated metadata to confirm it appears in the expected language before publishing. 💡 Why This Happens Content Genius V5 uses an editing agent to regenerate metadata when you make changes inside the editor. In earlier versions, this agent did not always inherit the language setting from Brand Vault, which caused metadata to fall back to a previously cached or default language. This issue has been resolved in the current version — as long as your Brand Vault language is set correctly, regenerated metadata will reflect the right language. Common scenarios where this problem occurs: - The Brand Vault language was set up incorrectly during initial account configuration. - The language field was left blank, causing Content Genius to fall back to a default. - Metadata was generated before a Brand Vault language correction was saved. - An article was duplicated or reworked from content originally created under a different language setting. ✅ Best Practices to Avoid Language Mismatches - Always verify your Brand Vault language setting before starting a new content project, especially when working in multiple languages. - Regenerate metadata after any Brand Vault update — existing content does not update automatically when Brand Vault settings change. - Review metadata before publishing to catch any language inconsistencies early. - If you manage content for multiple languages or markets, confirm you are working under the correct brand profile before generating content. 🛠️ Still Seeing the Wrong Language? If your metadata continues to generate in the wrong language after updating Brand Vault and regenerating, try the following: - Refresh your browser and reopen the article in Content Genius before regenerating again. - Confirm the save was successful in Brand Vault — look for a confirmation message after updating the language field. - Check whether the article was created using a different brand profile that may still have an outdated language setting. 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 Bug Fixes and UI Improvements

Content Genius has been updated with targeted bug fixes and interface improvements, delivering a more accurate and reliable experience in the SEO Metatags Generator and Brand Vault. ✨ What's New This release ships two bug fixes and a visual interface refresh across Content Genius: - GHL SEO Metatags Generator — URL validation corrected: Valid page URLs in GoHighLevel integrations were incorrectly flagged as invalid inside the SEO Metatags Generator. All properly formatted URLs are now recognized and accepted without error. - Brand Vault — Address mismatch warning clears on confirmation: An address mismatch warning was persisting in Brand Vault even after the discrepancy had been confirmed or resolved. The alert now dismisses correctly as soon as the mismatch is addressed. - Interface modernization: UI components have been migrated to a more modern component library, producing a cleaner and more consistent look and feel across Content Genius. 🛠️ How to Use It 1. Open Content Genius from the main navigation menu. 2. To confirm the SEO Metatags fix, go to your GHL integration, open the SEO Metatags Generator, and enter a valid page URL — it will now be accepted without triggering a false invalid-URL error. 3. To confirm the Brand Vault fix, navigate to Brand Vault, review your business address details, and acknowledge any mismatch warning — the alert will clear immediately after confirmation. 📋 What to Expect - All existing Content Genius settings, templates, and saved content are unaffected by this update. - Some interface elements may appear visually refreshed due to the component library update; all functionality remains identical. - GHL users will no longer encounter false URL validation errors in the SEO Metatags Generator. - Brand Vault users will find that address mismatch warnings dismiss correctly once confirmed, with no stale alerts lingering on screen. 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 AI Article Generation Folder Permissions Error

🔍 What This Error Means When you attempt to generate an AI article and see the message "Folder you are looking for has been deleted or doesn't exist", the platform cannot locate the destination folder assigned to your content. This is a folder or permissions issue — not a quota or credit problem. Your AI article generation credits are unaffected. This error typically appears in the AI Content Templates tool, but can also surface in other content generation workflows that write output to a saved folder. ⚠️ Common Root Causes - Deleted workspace folder: The target folder was removed by you or another team member after it was originally assigned. - Permission revocation: Your user role was changed and you no longer have write access to the folder where generated articles are saved. - Corrupted folder path: The folder reference stored in your template or project settings points to a path that no longer exists, often after a workspace reorganisation. - Shared workspace conflict: A collaborator deleted or renamed a shared folder that your account still references. 🛠️ Step-by-Step Troubleshooting 1. Navigate to AI Content Templates. Go to Left sidebar → Content → AI Content Templates. Locate the template or generation task that triggered the error. 2. Check the assigned output folder. Open the template settings or the generation task configuration. Look for a Save to Folder or Destination field. If it shows a folder name that no longer exists, this is the direct cause. 3. Reassign a valid folder. Click the folder field and select an existing folder from the dropdown. If no folders appear, you will need to create a new one first (see Step 4). 4. Create a new folder if needed. Inside AI Content Templates, use the folder management options to create a new destination folder. Give it a clear name so it is easy to identify going forward. 5. Re-run the article generation. With the valid folder now assigned, trigger the article generation again. The error should no longer appear and your article will save to the new location. 6. Check your role permissions (if the error persists). Ask your workspace admin to confirm that your user role includes write access to the selected folder. In shared or agency workspaces, folder permissions are role-dependent. The admin can adjust permissions under workspace settings. 7. Audit other templates for the same issue. If you use multiple AI Content Templates, review each one to ensure no other templates still reference a deleted or inaccessible folder. Updating them now prevents repeat errors. ✅ How to Prevent This Error in Future - Before deleting any folder in your workspace, check whether it is referenced in an active AI Content Template or content generation task. - When reorganising folders, update all template destination settings to point to the new folder paths. - If your team shares a workspace, communicate folder changes to all collaborators before making them. - Periodically review your AI Content Templates settings to confirm all folder references are still valid. ❓ This Is Not a Quota Issue A common misconception is that this error indicates you have run out of AI article generation credits. That is not the case. Quota exhaustion produces a different, clearly labelled message. If you see the folder error described in this article, your credits are intact and the fix is purely a folder or permissions correction as outlined above. 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.

📄 Publishing Content Genius Articles on Non-WordPress Sites

🔍 Overview Content Genius is Search Atlas's AI-powered article creation tool. Its one-click publishing feature is built exclusively for WordPress websites. If your site is hosted on a platform like Replit, Webflow, Squarespace, Wix, or any other non-WordPress environment, the direct publish option will not be available to you. This article explains why that limitation exists and walks you through how to get your finished articles live on your site manually. ⚙️ Why Direct Publishing Requires WordPress Content Genius publishes articles by connecting to your site through the WordPress REST API and the Search Atlas WordPress plugin. This integration allows the platform to send your content directly to your WordPress dashboard with a single click. Platforms like Replit do not expose a compatible API endpoint, so there is no technical pathway for Content Genius to push content to them automatically. This is a platform-level limitation, not a bug or account issue. ✍️ How to Manually Publish Your Content Genius Article Even without direct publishing, you can still use Content Genius to create high-quality, SEO-optimised articles and then copy them into your Replit site. Follow the steps below. 1. Go to Left sidebar → Content and open your article inside Content Genius. 2. Once your article is complete and approved, click into the editor to select all of the content. 3. Copy the full article text, including headings, body paragraphs, and any meta information you want to use. 4. Open your Replit project and navigate to the page or file where you want the article to appear. 5. Paste the content into your site's HTML, Markdown, or CMS editor, depending on how your Replit site is structured. 6. Format the content as needed to match your site's styling and structure. 7. Save and deploy your Replit project to make the article live. 💡 Tips for a Smooth Manual Workflow - Use the HTML view inside the Content Genius editor if your Replit site accepts raw HTML. This preserves heading structure and formatting automatically. - Copy meta tags separately. If Content Genius generated a meta title and meta description for your article, note these down and add them to your page's <head> section or your site's SEO settings. - Check image URLs. Images embedded in your Content Genius article may link to Search Atlas storage. Re-upload images directly to your Replit project or a hosting service to ensure they remain accessible long term. - Preserve heading hierarchy. Make sure H1, H2, and H3 tags carry over correctly when pasting into your site's editor, as these are important for on-page SEO. 🚀 Considering a Move to WordPress? If you plan to publish content frequently and want to take full advantage of Content Genius's scheduling, auto-publishing, and content sync features, migrating your site to WordPress is worth considering. WordPress is the only platform currently supported for direct Content Genius integration. Once your WordPress site is connected to Search Atlas, you can publish and schedule articles in one click, with your brand settings applied automatically. 🛠️ What to Expect in the Future The Search Atlas team is actively developing Content Genius and its publishing capabilities. While there is no confirmed timeline for non-WordPress integrations, the roadmap includes improvements to the native CMS publishing experience. Keep an eye on in-platform announcements for updates. 🙋 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.

⚡ Fix Content Genius 'Not Enough Data' Error

What This Error Means When you try to generate an article in Content Genius and see a "not enough data" error, it means the platform could not retrieve sufficient search data to build the article brief. This can happen even when the topic was pulled directly from your Topical Map. The error indicates that the keyword or topic has too little available search volume, SERP data, or competitive content for the AI to generate a well-optimised article. Where This Happens This error appears in Content Genius when you attempt to generate an article — whether you entered a topic manually or imported one from your Topical Map. Common Causes - Low search volume keyword: The topic has very few monthly searches, leaving insufficient SERP data for the AI to analyse. - Highly localised or niche topic: Hyper-local or very niche subjects may not have enough indexed content for the system to reference. - Newly trending term: If the keyword has only recently emerged, search engines may not yet have enough indexed results. - Spelling or formatting issue: A typo, extra character, or unusual punctuation in the topic field can cause a data lookup failure. - Unsupported language or region: The selected language or target country may have limited data availability for that specific topic. What to Do When You See This Error Follow these steps in order to resolve the error yourself before reaching out to support: 1. Check for typos or formatting issues: Review the topic or keyword you entered for any spelling mistakes, extra spaces, special characters, or unusual punctuation, then correct and retry generation. 2. Try a broader keyword: If your topic is very specific or niche, rephrase it using a wider, more general term that is likely to have higher search volume. For example, instead of a hyper-local phrase, try a broader regional or industry-level keyword. 3. Switch to a different target country or language: Navigate to your Content Genius settings and change the target country or language to one with a larger English-language or general search index (such as the United States or United Kingdom), then retry. If the topic only makes sense in a specific region, this error may be unavoidable for that keyword. 4. Use a related keyword with sufficient data: Open your Topical Map or a keyword research tool and identify a closely related keyword on the same subject that may have more monthly search data, then use that as your article topic instead. 5. Wait and retry for newly trending terms: If the keyword has only recently emerged, search engines may not yet have indexed enough content. Try generating the article again after a few weeks. If you have tried all of the steps above and the error persists, our support team can review the keyword data available for your specific topic and help you find an alternative path to generating the article successfully. When you reach out, please have the following ready so our team can assist as quickly as possible: - The exact topic or keyword you entered when the error appeared - Whether the topic was typed manually or imported from your Topical Map - The target country and language selected at the time of the error - Which self-serve steps above you already attempted - Any screenshot or screen recording of the error message 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 Internal Links Not Added by Content Playbook

🔍 Overview When you run the Content-Build Internal Links playbook, you may receive a completion report but find that no internal links were actually inserted into your target pages. This article explains the most common causes and the steps you can take to fix the issue. ⚠️ Why This Happens The internal links playbook relies on data stored in your BrandVault to identify which URLs to link to. If that data is missing, incomplete, or not yet populated, the agent has nothing to work with and will silently skip the insertion step — even though the task is marked as complete. The most common root causes are: - Empty internal links fields in BrandVault — The agent requires populated URL and anchor-text data. If these fields are blank, no links are inserted. - No valid page paths detected — The playbook needs resolvable page paths. URLs that are missing, malformed, or return errors are ignored. - Article Refinement conflict — If you requested internal links through an Article Refinement step rather than a dedicated internal-links step, the links may not be inserted correctly. - Stale or cached project data — Occasionally, outdated project data causes the playbook to act on old information. 🛠️ How to Fix It 1. Check your BrandVault internal links fields. Navigate to your BrandVault settings and confirm that the internal links section contains valid URLs and corresponding anchor text. Every URL must be a complete, working path. 2. Refresh your project data. Go to Left sidebar → Home → [project] (Executive Summary) and click Refresh Summary. Wait for the refresh to complete before re-running the playbook. 3. Re-run the internal links playbook. After confirming BrandVault data is populated and your project data is fresh, open your playbook and run the Content-Build Internal Links step again. Check the target pages once the completion report appears. 4. Avoid using Article Refinement as a substitute. If you need internal links inserted, use the dedicated internal-links playbook step rather than requesting them through an Article Refinement prompt. These are separate processes and produce different results. 5. Verify page paths are valid. Review the URLs listed in your BrandVault and confirm each one resolves correctly. Remove or correct any broken, redirected, or incomplete paths. ✅ How to Confirm Links Were Added After re-running the playbook, open each target page in the Content Builder and review the body content for inserted anchor links. Do not rely solely on the completion report — always inspect the page content directly to verify the links are present. 🚫 Known Limitations - The agent does not insert links if all internal link fields in BrandVault are empty. There is no partial insertion — it is all or nothing based on available data. - Links requested through Article Refinement follow a different insertion path and may not be added even if BrandVault data is complete. Use the dedicated playbook step instead. - Newly added BrandVault URLs may take a moment to be recognised. Always refresh project data before running the playbook after making BrandVault changes. 💬 Still Need Help? If you have followed all the steps above and internal links are still not being inserted, 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.

📝 AI Content Templates Availability

🔎 What happened to AI Content Templates? As of September 22, 2026, AI Content Templates is no longer available as a menu option in Search Atlas. The section has not been renamed or moved to another location. It has been deprecated and removed from the current platform navigation. 🧭 Where can I find current tools? For current AI-powered SEO workflows, open AI SEO from the left sidebar, then select OTTO SEO. Available areas include: - All Sites for managing sites - Overview for account and performance information - Knowledge Base for SEO guidance and stored information - Installation Guide for setup instructions - All Audits and Crawl Monitoring for site analysis AI Content Templates is not currently listed under OTTO SEO, Content, Authority, or another Search Atlas menu. 💳 Plan eligibility Because the feature has been deprecated, it is not available on any current Search Atlas plan. Changing plans, clearing your cache, or refreshing the browser will not restore the menu option. 🔄 Migration guidance If you used an older AI Content Template workflow, move the work into your current SEO process: 1. Open AI SEO → OTTO SEO. 2. Select the site you want to work on from All Sites. 3. Review the Knowledge Base, Installation Guide, and available audit tools. 4. Use your existing template prompts, briefs, and brand requirements as guidance when creating new content through your current workflow. Saved templates from the retired section may not appear in the current interface. Keep copies of any reusable prompts, outlines, or brand instructions you still need. 🛠️ When to contact support 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.

📄 Topical Terms in Content Genius Explained

📌 Overview When you create an article in Content Genius, the platform automatically generates a set of topical terms — keywords and related phrases that guide your content's SEO structure. Understanding how this process works will help you get the best results and avoid confusion when the terms don't match your expectations. 🔍 How Topical Terms Are Generated Topical terms are created automatically when you create a new article in Content Genius. The platform analyses your target keyword and generates a relevant set of topical terms based on that initial input. Key things to know about this process: - Topical terms are tied to the specific article created at that time. - If only one keyword appears in your topical terms panel, this reflects what was generated at the time of article creation — it is not a display error or a data sync issue. ⚠️ Why You May See Only One Keyword If your topical terms section is showing fewer keywords than expected — for example, only a single keyword — this is most likely because: - The target keyword entered at article creation was very narrow or highly specific, resulting in limited topical term suggestions. - The keyword had low data availability at the time of generation. - The article was created before additional keyword data was available in the platform. ✅ How to Get Different or Additional Topical Terms If you are seeing fewer topical terms than expected, the recommended approach is to create a new article with a different or broader keyword. To do this: 1. Open Content Genius in your Search Atlas workspace. 2. Create a new article. 3. Enter your target keyword carefully — consider using a broader or more descriptive keyword phrase to increase the number of topical terms generated. 4. Complete the article setup. The platform will generate a fresh set of topical terms based on your new input. 5. Review the topical terms before writing. If they look comprehensive, proceed with your content. Your original article will remain intact in your workspace. You can keep it as a reference or delete it if it is no longer needed. 💡 Tips for Better Topical Term Results To maximise the number and relevance of topical terms when creating a new article: - Use a clear, specific primary keyword that has sufficient search volume and broad enough scope to support multiple related terms. - Avoid overly niche or long-tail phrases at the article creation stage if you want a richer set of topical terms. - Review the topical terms immediately after creation so you can decide early whether to proceed or start a new article with an adjusted keyword. 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 AI Editing Timeouts

🔍 What Is Happening? If your Content Genius workspace shows jobs stuck at a specific progress percentage and AI editing actions consistently time out, this is typically caused by a temporary outage or degraded performance from our upstream AI provider. During these periods, jobs that are mid-process can stall in the queue and will not automatically recover without intervention. ⚠️ How to Recognise This Issue - One or more jobs in your Content Genius workspace are frozen at the same progress percentage for an extended period. - AI editing actions fail or time out every time you attempt them. - The issue affects multiple jobs simultaneously rather than a single document. - The problem began around a specific date or time, suggesting an external trigger rather than a user error. 🚀 Steps to Resolve Stalled Jobs 1. Confirm the jobs are genuinely stalled. Open your Content Genius workspace and check whether the affected jobs have shown any progress recently. If the percentage has not changed after an extended wait, the jobs are stalled. 2. Do not create duplicate jobs. Avoid re-submitting the same content for the same AI actions while the original jobs are still queued. Duplicate jobs can compound queue congestion once the provider recovers. 3. Wait for automatic provider recovery. In most cases, once our AI provider resolves the outage, the queue processes automatically. Allow some time after a confirmed recovery before taking further action. 4. Attempt a manual retry. If jobs remain stuck after provider recovery, open the affected document in Content Genius and re-trigger the timed-out action. The stalled job will be superseded by the new request. 5. Contact support if needed. If you have a large number of stalled jobs and manual retries are not practical, contact our team directly so we can clear the stalled queue entries on the back end and restart processing for you. When reaching out, please have the following ready: your workspace/project name, the names or URLs of the affected documents, and the approximate time the issue started. 💡 Tips to Prevent Future Timeouts - Run AI editing actions in smaller batches. Submitting fewer jobs at a time reduces the impact of any single provider disruption. - Check platform status before bulk submissions. If you plan to process a large volume of documents, verify that Content Genius is responding normally by running a quick test on one document first. - Allow jobs to complete before chaining actions. Start a second AI action only after the first action has reached 100% and confirmed completion. 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 Score Stuck Same Value

🔍 What Is Happening? If Content Genius is returning the same score for two or more different articles, this is caused by a temporary outage or degraded performance from the underlying AI provider that powers the content scoring engine. When the AI provider cannot process new requests, scoring may get stuck at the same value rather than calculating a fresh result for each article. This is a platform-side issue, not a problem with your content or account settings. No data is lost, and scoring will return to normal once the AI provider recovers. ⚠️ How to Confirm This Is the Cause - Two or more articles receive the exact same numerical score despite having clearly different content. - The score does not change after editing the article and re-running the scorer. - The issue affects multiple projects or articles around the same time. 🚀 What to Do Because this issue is caused by an AI provider outage on the platform side, there is no self-serve fix that will force scoring to recover. The recommended approach is to wait and retry: 1. Wait and retry. AI provider outages are typically short-lived. After some time has passed, return to the affected article in Content Genius and attempt to score it again. 2. Try a different article. Open a second article and score it. If it returns a different, plausible score, the service has recovered and you can re-score the original article. 3. Check again later. If the issue persists, the provider may be experiencing a longer incident. No action on your end is required for the fix to take effect — scoring will recover automatically once the provider is back online. 💡 What You Should Know - Your content is safe. A stuck score does not affect your saved drafts, article history, or any published content. - Scores are recalculated fresh each time. Once the AI provider is back online, every new scoring request will produce an accurate, individualised result for your article. - This is not a billing or account issue. The problem is entirely tied to AI provider availability and resolves automatically. - Avoid making major edits based on a stuck score. If you suspect scoring is affected, wait for the service to recover before using the score to guide optimisation decisions. 🛠️ Still Seeing the Same Score? If the score remains identical across multiple articles after waiting, please reach out to our team. To help us investigate quickly, have the following ready: the name of the affected project, the article(s) showing the stuck score, and the approximate time you first noticed the issue. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

📊 Add Competitors to Content Velocity Correctly

🔍 Overview Content Velocity lets you track how often your site and your competitors publish new content. If you are having trouble adding competitors directly inside Content Velocity, the correct approach is to add them through Site Auditor first — they will then become available within Content Velocity. ⚙️ Why Can't I Add Competitors Directly in Content Velocity? Content Velocity draws its competitor list from your Site Auditor project. Competitors need to be configured at the Site Auditor level before they will appear as options inside Content Velocity. This ensures a consistent competitor set is shared across the tools linked to your project. 🛠️ How to Add Competitors via Site Auditor To make competitors available in Content Velocity, add them through Site Auditor: 1. In the left sidebar, navigate to Site Auditor. 2. Open the relevant project (or create a new one if needed). 3. Locate the competitors or project settings area within your Site Auditor project. 4. Add the competitor domain there and save your changes. 5. Return to Content Velocity within your project — your added competitor should now be available. If you are unsure exactly where to find the competitor settings inside your Site Auditor project, or if the competitor still does not appear in Content Velocity after adding it, please reach out to our support team for guidance specific to your account setup. ❓ Frequently Asked Questions Can I add competitors directly inside Content Velocity? Competitors need to be added at the Site Auditor project level first. Once added there, they will be available to use within Content Velocity. My competitor was added in Site Auditor but is not showing in Content Velocity — what should I do? Allow a short time for the data to sync. If the competitor still does not appear, contact our support team and have your project name and the competitor domain ready so we can investigate. 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. Additional Notes Using a different project in Content Velocity: Make sure the project you select in Content Velocity matches the one where you added competitors in Site Auditor, otherwise competitors may not appear. Also: select the same domain project you updated in Site Auditor, then choose competitors from the available list.

⏸️ Can I Turn Off Content Genius for One Project?

⏸️ Is There an On/Off Switch per Project? No. Content Genius doesn't have a setting to turn it off for a single project, and it doesn't need one: it only creates content when you generate an article yourself. It doesn't run on a schedule or in the background. 🔌 Stop Articles From Uploading to WordPress Automatically If articles are appearing in WordPress without you publishing them, check the WordPress auto-upload setting. It's set in your Brand Vault, in the content settings for WordPress, not in the Content Genius project. 1. Open the Brand Vault connected to your site. 2. Open its content settings and find the WordPress section. 3. Turn off automatic upload to WordPress, then save. After that, finished articles stay in Content Genius until you publish them. ⚙️ What the Project Settings Control Content Genius project settings control how articles are written, such as tone of voice, language and point of view. They don't pause or disable Content Genius. 🤖 Looking for OTTO Autopilot? Automatic, ongoing optimization is part of OTTO SEO, not Content Genius. If changes are appearing on your site on their own, check the OTTO project for that site. 🙋 Need More Help? Open the chat widget and type human teammate.

🛠️ Resolving WordPress Publishing and Vault Errors

🔍 Understanding the Error If you are seeing a REST API sync failure or a "Brand Vault not connected" error while using Content Genius, these are known issues that our engineering team is actively investigating. These errors can prevent content from being published to WordPress and may affect access to your saved brand guidelines. ⚙️ What to Gather Before Reaching Out To help our team diagnose and resolve these errors efficiently, please have the following information ready: - The exact error message you are seeing, including any error codes. - The URL of your WordPress site. - A screenshot of the error or the affected screen. - The date and approximate time the error occurred. - Whether the issue happens every time or only intermittently. 💡 Known Impact These issues may affect your ability to publish articles directly from Content Genius to WordPress, or may prevent Content Genius from accessing your Brand Vault settings. Our team is working to identify the root cause and deploy a fix as quickly as possible. 💬 Need Additional Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Slack Coworker Off-Brand Content

🔍 Why Coworker Content Goes Off-Brand The Slack Coworker AI generates daily article ideas and can draft full articles on request. However, if it lacks clear brand guidelines, target keywords, and topic context, it may produce content that misses the mark — wrong tone, incorrect keywords, or entirely unrelated subject matter. This usually happens for one of three reasons: - No brand voice configured: The AI has no reference for your tone, style, or audience. - Missing keyword targeting: The AI guesses at keywords instead of using the ones you intend. - Lost context mid-conversation: Long Slack threads can cause the AI to drift from the original topic. The good news is that each of these issues is preventable with a few setup steps. ⚙️ Set Up Brand Voice in Content Genius Before asking the Slack Coworker to write articles, make sure your brand voice and content settings are configured in the platform. This gives the AI a consistent reference point for tone, audience, and style. 1. Navigate to Content → Content Genius from the left sidebar. 2. Open a new or existing project under Generate or Write an article. 3. Fill in the brand voice fields: describe your target audience, preferred tone (professional, casual, authoritative, etc.), and any style notes the AI should follow. 4. Specify your primary and secondary keywords so the AI knows what to optimize for. 5. Save your settings before requesting articles through Slack. Once these settings are saved, the Slack Coworker pulls from them when generating content, which dramatically reduces off-brand output. 💡 Provide Clear Context in Slack When you reply to a daily idea message and ask the Coworker to write an article, the more context you provide, the better the result. Follow these guidelines: - Reference the specific idea: Instead of saying "write it," say "write the article about [exact topic from the idea]." - Restate your target keyword: Include the keyword you want the article to target so there is no ambiguity. - Keep conversations short: Start a fresh Slack thread for each article request to prevent context drift. - Specify article type: Tell the Coworker if you want a listicle, how-to guide, thought leadership piece, or news commentary. For example, instead of "Write this one", try: "Write a 1,200-word how-to article about off-road caravan maintenance targeting the keyword 'off-road caravan tips' for a South African audience." 📊 Review and Rework Generated Articles Even with proper setup, always review AI-generated content before publishing. If an article comes back off-brand or with the wrong keywords, you can refine it directly in the platform: 1. Navigate to Content → Content Genius. 2. Select Rework existing article. 3. Paste the generated content and provide specific instructions on what needs to change (tone, keywords, structure, etc.). 4. Click generate to receive a revised version. This gives you a second pass with more explicit guidance, which typically resolves quality issues. ✅ Recently Fixed Known Issues Our team has resolved several bugs that contributed to off-brand and inaccurate Slack Coworker output. If you experienced any of the following, they should no longer occur: - Context loss: The Coworker would lose the original topic mid-thread and generate completely unrelated content (for example, writing about skincare instead of off-road caravans). This has been fixed. - Hallucinated responses: When asked to write news jacking articles, the AI would sometimes share unrelated account details or meeting schedules. This has been resolved. - Slack formatting errors: Emoji shortcodes rendered as literal text and bold formatting appeared incorrectly. Formatting now renders properly in Slack. If you still encounter any of these issues after the fixes, let us know so we can investigate further. 🚀 Best Practices for Consistent Results - Update brand voice settings quarterly or whenever your messaging strategy changes. - Use Content Genius for complex articles that require detailed keyword targeting — it offers more controls than the Slack quick-write flow. - Avoid stacking multiple requests in a single Slack thread. One topic per thread keeps the AI focused. - Always verify keywords in the generated output against your intended targets before publishing. 💬 Still Getting Off-Brand Content? If you have followed the steps above and the Slack Coworker is still producing inaccurate or off-brand content, there may be an account-specific configuration issue we can help resolve. 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.

🛠️ Content Genius Article Generation Outage Explained

🔍 What This Error Means If you encounter an error inside Content Genius indicating that article generation is unavailable, it typically means the article generation service is experiencing a temporary disruption. This is a platform-side issue and is generally not related to your account, subscription, or browser settings. ✅ Steps to Take Right Now 1. Wait a few minutes and retry. Most service disruptions are short-lived. Wait 5–10 minutes, then refresh your browser and attempt to generate an article again. 2. Try a different browser or device. This helps confirm whether the issue is platform-wide or limited to your current setup. 3. Note the exact error message you are seeing. If you need to escalate, having the precise wording of the error will help our team investigate faster. ⏳ What to Do While You Wait If the disruption is ongoing and you need to keep your content workflow moving, consider pausing article generation tasks and focusing on other planning or research work until the service is restored. Avoid repeatedly retrying generation, as this is unlikely to resolve a platform-side outage. 🔄 When Service Is Restored Once the outage is resolved, article generation will resume. You do not need to reinstall anything or make changes to your account. Simply return to Content Genius and proceed with your generation as normal. 📋 When to Escalate — and What to Have Ready If the error persists beyond 15–20 minutes or you need an urgent status update, please reach out to our support team. To help us investigate as quickly as possible, have the following ready before you contact us: - The exact error message displayed in Content Genius - The date and time (including your timezone) when you first noticed the issue - Your project or workspace name - The browser and device you are using - Whether the issue affects all users on your account or only your login 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 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.

📊 Why Content Genius Scores Change

🔍 Why the score changes Content Genius recalculates the score whenever you add or remove words. The score reflects how closely your content matches the current recommendations for the topic, including coverage, relevance, and content length. Because the score is calculated from the complete draft, even a small edit can change the result. Adding a relevant term may improve coverage, while removing a word or section may reduce it. In some cases, removing unnecessary text can also improve the score by making the content more focused. 📈 What the score means The score is a guidance indicator, not a permanent rating or a guarantee of search performance. It is designed to help you identify opportunities while writing and should be considered alongside accuracy, clarity, search intent, and the quality of the reader’s experience. ✍️ How to improve your content 1. Open Content → Content Genius from the left sidebar. 2. Choose an existing workflow or select Write it yourself to edit your draft. 3. Review the recommendations and add information only when it is useful and relevant. 4. Remove repetition, filler, or content that does not support the topic. 5. Recheck the score after meaningful edits, then review the article as a reader before publishing. ✅ Best practices - Do not add words solely to increase the score. - Prioritize helpful, accurate, naturally written content. - Use recommendations as suggestions rather than strict requirements. - Expect the score to move as your draft changes; this is normal behavior. - Compare changes after editing a complete section instead of reacting to every small score movement. 🛠️ When to contact support If the score does not update after a completed edit, behaves inconsistently, or appears unrelated to the content, note the project, article, and changes you made. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🔌 Connect a WordPress Subdomain to Content Genius

🧭 Overview Content Genius lets you publish AI-generated content directly to your WordPress site using a CMS connector. When your WordPress installation lives on a subdomain (for example, cms.yourdomain.com.au), additional configuration may be required to ensure the connection works correctly. This article explains what to prepare and what information to have ready if you need assistance. ✅ Before You Begin - You must have Administrator access to your WordPress site. - Your subdomain must be publicly accessible. 📋 Setting Up Your Subdomain CMS Connector Setting up a WordPress CMS connector for a subdomain in Content Genius requires your WordPress subdomain URL, your WordPress username, and your WordPress credentials. If you encounter issues completing this setup, our team can assist you directly. Please have the following ready before reaching out: - Your full subdomain URL (e.g. https://cms.yourdomain.com.au) - The exact error message you are seeing - Confirmation of the credentials you are using to authenticate - Any relevant details about your WordPress configuration 🔑 About WordPress Application Passwords WordPress Application Passwords are a built-in WordPress feature that allows external services to connect to your site. If you are unsure whether you have generated one or need guidance on doing so, please reach out and our team will walk you through the process. ⚠️ Common Issues If you are experiencing errors connecting your WordPress subdomain to Content Genius, our team can investigate these issues on your behalf. When reaching out, please provide your subdomain URL and the exact error message displayed so our team can assist you efficiently. 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.

💳 PR Distribution Hyperdrive Credits Insufficient Balance Error

🔍 What This Error Actually Means When you try to submit a press release and see the message 'payment information needs to be updated', your first instinct may be to check your credit card or billing details. However, in most cases your payment method is perfectly fine. This error message is misleading. It is almost always triggered by an insufficient Hyperdrive credit balance — not a billing or payment issue. Your subscription can be fully active and your card completely valid, yet the error will still appear if you do not have enough Hyperdrive credits to cover the cost of your selected distribution. 📦 What Are Hyperdrive Credits? Hyperdrive credits are the in-platform currency used to submit press releases through the PR Distribution tool in Search Atlas. Each submission requires a minimum number of credits depending on the distribution tier and the number of outlets selected. - Credits are separate from your subscription billing. - You must have enough credits before you submit — the system does not automatically charge your card to top up your balance. - The minimum credit requirement varies by distribution package. For example, a standard submission may require 23 or more credits. ⚠️ Why the Error Message Is Confusing The platform surfaces a generic payment-related error when a submission cannot be processed due to insufficient credits. This is a known display issue. The underlying cause is a low or empty Hyperdrive credit balance, not a problem with your saved payment method. Steps like clearing your browser cache, re-entering your credit card, or contacting your bank will not resolve this error. The only fix is to ensure your Hyperdrive credit balance meets or exceeds the minimum required for your submission. ✅ How to Check Your Hyperdrive Credit Balance 1. Log in to your Search Atlas account. 2. Navigate to the PR Distribution tool from the left-hand menu. 3. Look for your Hyperdrive Credits balance, displayed in the top section of the PR Distribution dashboard. 4. Note your current balance and compare it to the credit requirement shown for your selected distribution package. 🛒 How to Add More Hyperdrive Credits 1. Click your Avatar → Billing → Plans & Top-ups (Billing), then click the Top Up button next to HyperDrive Credits. 2. Select the credit package that meets or exceeds the amount required for your press release submission. 3. Complete the purchase using your saved payment method. 4. Once the credits are added to your account, return to your press release draft and resubmit. Your credit balance updates immediately after a successful purchase, so you can resubmit your press release right away. 📋 Quick Troubleshooting Reference - Error appears even though card is valid: Check your Hyperdrive credit balance first — this is the most common cause. - Submission fails partway through: Your credit balance may have dropped below the minimum mid-session. Refresh the page and recheck your balance. - Not sure how many credits your submission requires: The credit cost is displayed on the submission review screen before you confirm. You can also check the pricing breakdown in the PR Distribution settings. - Credits were deducted but submission did not go through: Do not resubmit before contacting support, as you may be charged twice. Use the chat widget described below. 💡 Tips to Avoid This Error in the Future - Check your Hyperdrive credit balance before drafting a new press release, especially if you have submitted recently. - Keep a buffer of credits in your account if you submit press releases regularly. - Review the credit cost for each distribution tier before selecting your package so you are never caught short at the submission stage. 🙋 Still Need Help? If you have confirmed your credit balance is sufficient but the error persists, or if credits were deducted without a successful submission, please reach out. 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.

⚡ Recover Deleted AI Projects and Fix Geo-Tagging

Overview This article covers two issues that may occur in Content Genius: accidentally deleting an active AI project and being unable to click the geo-tagging feature. It explains what to expect in each case and how to escalate effectively to our support team. Understanding AI Project Deletion Content Genius does not currently offer a confirmed self-serve restore option for deleted AI projects. Once a project is deleted, its generated content, settings, and associated artifacts may no longer be accessible from your workspace. What to Do After an Accidental Deletion Deleted project recovery requires investigation by our support team. To give our team the best chance of looking into recovery options, please connect with us as soon as possible and have the following information ready: - The exact name of the deleted project - The approximate date and time of the deletion - Your account email address - Any exported or saved copies of the project content you may already have The sooner you report the deletion, the sooner our team can investigate your specific case. Content Genius Geo-Tagging Bug Some customers report that the geo-tagging option inside Content Genius is unresponsive — clicking it produces no action or does not open the expected selector. If you are experiencing this, please connect with our support team and have the following ready: - The name of the project where the geo-tagging option is unresponsive - The exact behavior you are seeing (for example, no response on click, or a selector that opens but cannot be interacted with) - The date and time you first noticed the issue - Your browser name and version 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.

🧰 Brand Vault Shows Incomplete Even After Completion

This guide covers what to do when your Brand Vault keeps showing as incomplete even after you have already entered and saved your brand's information. This is typically a saving or display persistence issue rather than missing data, so verifying and re-saving the affected sections is the fastest way to resolve it. 🛠️ Step-by-Step 1. Refresh the page and reopen Brand Vault. In some cases the incomplete status is only a display issue and clears once the page reloads. 2. Open each section that shows as incomplete and check whether the values you previously entered are still present. Make a note of which sections lost your entries and which kept them but still show as incomplete. 3. For sections that lost your entries, re-enter the information and save the section again. 4. For sections that kept your entries but still show incomplete, confirm each field still holds the correct value and save the section again so the most recent version is recorded. 5. Refresh the page one more time and recheck every section to see whether the incomplete status has cleared. 6. If any sections still show as incomplete, repeat the re-enter and re-save steps for those specific sections, then refresh and check again. ✅ How to Confirm It Worked After refreshing, each section of your Brand Vault should retain the information you entered and no longer be flagged as incomplete. If the status still does not update after re-saving, our team will need to review it — to speed things up, have the following details ready: the names of the affected sections, the exact information you entered, the date and time you saved it, and the browser you were using. 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 Keywords Stuck Loading

🧩 What This Article Covers Some users have reported that the All Suggested Keywords report inside Content Genius fails to load — the page either spins indefinitely or shows zero data for every search. This is a known platform-side issue that our support and engineering teams have investigated. This article explains what to do if you encounter it. ⚠️ What You Might See - Keyword data stays stuck on 0 results. - Every search you run in the All Suggested Keywords report produces no data. - The loading indicator never completes, regardless of the keyword or topic you enter. 🛠️ What to Do This issue has been identified as a platform-level loading error affecting the All Suggested Keywords report in Content Genius. Because the root cause is on the platform side rather than in your browser or account settings, the resolution requires action from our support and engineering team. There is no self-serve workaround confirmed to resolve this issue. If you are experiencing it, please contact our support team directly so they can investigate and apply the appropriate fix for your account. 📋 How to Report This Issue To help our team resolve this as quickly as possible, please have the following ready when you reach out: - Confirmation that the All Suggested Keywords report is stuck loading or returning zero results for all searches. - The keyword or topic you were searching when the issue first occurred. - Your account email address so our team can look into the platform-side status for your account. If you need help, please reach out via the chat icon in the bottom-right corner of the platform and type human teammate to be connected with a member of our team. Our team will investigate and follow up with a resolution.

📝 Content Genius Not Begun Articles Explained

📄 Why Articles Appear as Not Begun When you create articles from scratch in Content Genius, they start with a Not Begun status. This means the system has created the article structure but has not generated any content yet. You need to manually trigger content generation for these articles. 🤖 Generate Content with AI or DKN To populate Not Begun articles, run the content generation process again using either the AI writing option or the DKN (Domain Knowledge Network) method. Both approaches will create complete articles with full content. The DKN method uses your domain expertise and existing content patterns, while the AI method generates fresh content based on your keywords and topic. 🔄 Re-run Generation for Existing Articles If you have multiple articles stuck in Not Begun status, you can process them again through the content generation workflow. Select the articles you want to write and choose your preferred generation method. The system will then create complete content for each selected article. 📊 Compare Competitor Pages To add a competitor page for comparison, use the competitor analysis feature within the content creation workflow. Enter the competitor URL when setting up your article or topical map. The system will analyze their content structure and topics to help guide your own content strategy. ✅ Expected Behavior Articles created via AI or DKN generation are complete by default. Only articles created manually from scratch start as Not Begun. This is normal platform behavior — simply trigger generation when you are ready to produce content. 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 Generation Deadline Exceeded Error

🔍 What This Error Means If you see a "generation deadline exceeded" error while trying to generate an article in Content Genius, it means the system did not complete the article within the expected time window. This error is caused by a platform-side outage or infrastructure issue — not by anything you did wrong. When an outage affects the Content Genius service, article generation requests time out before they can finish. Because this is a backend infrastructure event, there are no self-serve steps that will resolve it. The fix requires action from the Search Atlas engineering team. ⚠️ What to Expect During an Outage While a Content Genius outage is active, article generation attempts will continue to fail with this error regardless of how many times you retry. Once the engineering team has resolved the underlying issue, generation will resume normally. You do not need to change any settings or inputs — the error is not related to your content or configuration. 📋 What to Have Ready When You Escalate If you are seeing this error, please contact our support team. To help the team investigate and resolve the outage as quickly as possible, have the following information ready: - The keyword or topic you were trying to generate content for. - The exact time and date of each failed attempt (including your timezone). - Whether the error appears immediately or after a long loading period. - Any Content Genius settings you had configured at the time (word count, tone, language, etc.). 🚀 Getting Further Help If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

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

🛠️ Troubleshooting AI Article Generation and Language Settings in Content Genius

This article covers two related issues in Content Genius: AI failing to generate articles at all, and AI producing content in the wrong language despite your settings. Because these issues require investigation of your specific account configuration, our support team will need to look into this directly for you. What to Expect AI article generation failures and incorrect language output in Content Genius can stem from account-level configuration, project settings, or platform-side issues. These are not always resolvable through self-serve steps alone — a support teammate can review your account and identify the exact cause. How to Get Help When contacting support, please have the following ready so your teammate can investigate quickly: - Your project or workspace name — the name of the Content Genius project or workspace where the issue occurred. - The language you intended to generate content in — and the language that was actually produced, if the output was incorrect. - A description of the generation failure — for example, whether generation did not start, stalled partway through, or completed but produced unexpected output. - Any error messages displayed — copy the exact text of any error message shown on screen, including the timestamp if visible. - Whether the issue affects single article generation, bulk generation, or both — this helps narrow down where the problem originates. 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.

🛠️ Missing AI Content Templates Menu

🔍 Why the menu is missing The AI Content Templates menu was decommissioned and removed from Search Atlas. This change also applies to the Meta Tag Generator and Content Rewriter interfaces. The removed menu previously included tools such as tweet generation, YouTube scripts, email subject lines, meta descriptions, and other content templates. Its absence is expected and does not indicate a problem with your account or browser. 📋 What changed - The AI Content Templates navigation item is no longer available under the Content section. - Direct links to the retired template pages may no longer work. - Labels and page headings related to the former templates were updated or removed to keep the platform navigation consistent. 🚀 What to do next Use the currently available Search Atlas features shown in your platform navigation for your SEO and content workflows. Menu options can vary by account, permissions, and ongoing product updates, so rely on the tools currently displayed in your workspace rather than older instructions or saved links. If you are following an older guide that references AI Content Templates, Meta Generator, or Content Rewriter, that guide may no longer reflect the current Search Atlas experience. 💬 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.

🛠️ Troubleshooting AI Article Language

This guide helps when Content Genius cannot generate an article or produces content in the wrong language. 📍 Where to Find It Open Content from the left sidebar, then select Content Genius. 🛠️ Step-by-Step 1. In Content Genius, choose Write an article for a single article, or choose Write with AI in Bulk for multiple articles. 2. Complete the required article details, including the topic, instructions, and target audience. 3. In the generation settings, select the exact language you want. Do not leave the language set to automatic if a specific language is required. 4. Include the language in your instructions as well, such as “Write the entire article in Spanish,” then start generation. 5. If generation fails, copy your completed brief, reopen Content Genius, and retry the article individually instead of processing it in bulk. 6. Before accepting the result, check that the title, headings, body, and call to action all use the selected language. ✅ How to Confirm It Worked Generation is successful when the article output appears completely, contains no error message, and every section is written in the selected language. Check the title, headings, and several body paragraphs for mixed-language text before publishing. 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.

⏱️ Content Genius Timeout and Billing Disputes

🔍 Overview If Content Genius appears to be spinning or stuck without producing content, the session may have timed out or encountered a generation error. This article explains what to do when this occurs and how to address any unexpected billing charges. ⚠️ Why Article Generation Gets Stuck Article generation in Content Genius can sometimes stall or fail to complete. When this happens, the article may remain in a processing state without producing output. 🛠️ What to Do When Generation Is Stuck If you experience a stuck or timed-out generation, please note the following details so our support team can investigate: - Your project or workspace name - The approximate date and time the generation attempt occurred - A description of what happened (e.g. how long it was stuck, any error messages displayed) 💳 Understanding Charges for Failed or Timed-Out Articles If a failed or timed-out generation has resulted in an unexpected charge or credit deduction on your account, our support team can investigate and help resolve the dispute. Please have the details above ready when you reach out so the team can look into the issue and take any necessary action on your account. 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 and On-Page Audit Issues

🔍 Overview Two tools that customers occasionally report issues with are Content Genius (the Atlas AI writing agent) and the On-Page Audit tool. This article explains what these issues typically indicate and what to do if you encounter them. ⚙️ Why Is the Atlas Agent Stuck on 'Working on it...'? The Atlas agent inside Content Genius may appear frozen on the 'Working on it...' status when processing requests such as content trimming, rewriting, or optimisation. This is a known issue that has required backend investigation and platform-level intervention to resolve. It is not always something that can be fixed through browser-side actions alone. 🚀 What to Do If the Atlas Agent Appears Stuck Because this issue may be caused by a platform-level disruption, the most important step is to escalate promptly rather than repeatedly retrying. Before escalating, please have the following information ready: - The name of the content project or document affected - The exact status message displayed (e.g. 'Working on it...') - The type of request you submitted (e.g. trim, rewrite, optimisation) - The approximate time and date the issue began - Any error messages shown on screen You may try a page refresh or opening the content piece again to see if the task completed in the background, but if the issue persists, escalate to the support team immediately — do not continue resubmitting the same request. 📊 Why Is the On-Page Audit Tool Not Working? The On-Page Audit tool may fail to load results, return an error, or appear unresponsive. Like the Content Genius issue, malfunctions with this tool have required backend investigation to resolve and may not be fixable through customer-side actions. 🚀 What to Do If the On-Page Audit Tool Is Malfunctioning If the On-Page Audit tool is not returning results or is unresponsive, please gather the following before escalating: - The URL of the page you were attempting to audit - The exact error message or behaviour observed (e.g. spinning loader, blank results, error code) - The approximate time and date the issue began - Whether the issue affects all pages or only specific URLs These details allow the support team to investigate the backend cause quickly and accurately. ⚠️ Important: These Issues May Indicate a Platform Outage Both of these issues — a stuck Atlas agent and On-Page Audit malfunctions — may be symptoms of a broader platform or backend outage rather than an isolated user-side problem. If you are experiencing either issue, do not assume it is caused by your browser or network settings. Escalate to the support team with the details listed above so the issue can be investigated at the platform level. 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.

🖼️ Troubleshooting Image Generator Button

This article explains how to look for the image generator button in the content editor. 📍 Where to Find It Open the relevant content item in the Content editor and review the available editor controls and content actions. 🛠️ Step-by-Step 1. Open the relevant content item in the Content editor. 2. Review the editor controls and available content actions for the image generator button. 3. If the button is available, select it to confirm it can be accessed from the editor. 4. If the button is unavailable, note the content item and the controls shown so the issue can be investigated. ✅ How to Confirm It Worked The check is complete when you have reviewed the Content editor and confirmed whether the image generator button is available. If it is not available, keep the content item details and the visible editor controls ready when requesting 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.

🛠️ Troubleshooting AI Image Generator

This article explains how to check for the AI image generator in the content editor and distinguish its absence from a product bug. 🛠️ Step-by-Step 1. Open the content editor for the project or article you are working on. 2. Open the editor’s image or media insertion controls. 3. Review the available image options. If no AI image generation option appears, the feature is not currently available in the content editor. 4. Use the available upload or image-selection options instead. Updating or reopening the editor will not restore a feature that has been removed. ✅ How to Confirm It Worked Confirm that the image controls load normally and that you can insert an image using the options shown. If those controls work but no AI generator appears, this confirms a current product limitation rather than a loading or configuration issue. 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 AI Image Creator Images Not Populating

🔍 Overview If images are not appearing in your blog post after using the AI Image Creator inside the Content Assistant, our support team can investigate your specific account and session to identify the cause. This article outlines the steps to take before contacting support so we can resolve the issue as quickly as possible. ✅ Before You Begin Confirm the following before troubleshooting: - You are working inside Left sidebar → Content → Content Genius (What are we writing today?). - Your blog post is already open and saved. - You have attempted image generation at least once and images did not appear in the editor. 🌐 Fix 1: Rule Out Browser-Specific Issues Browser extensions or cache issues can sometimes interfere with content loading in the editor. Try the following steps: 1. Clear your browser cache and cookies, then reload the page. 2. Disable any browser extensions (particularly ad blockers or script blockers) and try generating images again. 3. Try a different supported browser (for example, if you are using Brave or Safari, switch to Chrome) and repeat the image generation step. 4. If images appear in the alternate browser, the issue is browser-specific. Re-enable extensions one at a time to identify the conflict. 🔄 Fix 2: Refresh and Retry If browser switching does not resolve the issue, try the following: 1. Save your blog post content. 2. Fully close the tab and reopen your blog post in the Content Assistant. 3. Attempt image generation again from the beginning. 4. If images still do not appear, note exactly what steps you took and what you observed on screen. 📩 Contact Support If images are still not populating after trying the steps above, please reach out to our support team via the in-app chat. Include the following details so we can investigate promptly: - Your account email and workspace name. - The URL of the blog post where images are not appearing. - The browser and operating system you are using. - A brief description of the steps you took and what happened (or did not happen) after attempting image generation. Our team will review your account and session details to identify the root cause and get your images populating correctly.

🛠️ 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 Incomplete Content Generation

🔍 What causes these issues? Generated articles may occasionally contain extra spaces, unusual paragraph breaks, or stop before the content is complete. This is a known issue (GitLab issue 576) that has been reported when generating articles or blog posts in Content Genius. Our team is aware of it and it is being investigated. ✍️ What to do while this is being investigated If you encounter spacing problems or incomplete content in a generated article, the following general steps may help while a fix is in progress: 1. Try generating the article again with a more focused or specific topic request. 2. Review the output immediately after generation to identify any missing sections or formatting problems. 3. If the article ends abruptly, consider generating it in smaller sections rather than all at once, then combine the reviewed sections manually into a final draft. 4. Manually clean up any extra spaces, empty paragraphs, or duplicate line breaks directly in the editor before publishing. ✅ Check before publishing - Confirm the introduction and conclusion are present. - Make sure every heading has supporting content. - Remove placeholder text and unfinished sentences. - Review facts, links, keywords, and formatting manually. 📋 When escalating to support If the issue persists, please have the following ready so our team can investigate quickly: - The exact topic or prompt you entered when generating the article. - A description of what went wrong (e.g., where the content cut off, what spacing looked like). - The date and approximate time the generation was attempted. - A screenshot or copy of the incomplete or incorrectly formatted output. 💬 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 instantly connected with a member of our team.

🐛 Fix Atlas Agent 400 Errors in Content Genius

Overview When using Atlas Agent inside Content Genius, you may encounter a "Request failed: 400" error. This can occur during various content workflows. Because the root cause of this error requires investigation on the backend, our support team will need to look into your specific case to identify and resolve it. What Is Happening A 400 error from Atlas Agent indicates that a request was rejected or could not be processed. The underlying reason can vary and is not always visible from the platform interface. This is a known error type that our team investigates on a case-by-case basis. What to Try While You Wait - Refresh the page. Reload Content Genius and attempt your action again — a fresh page load can sometimes clear transient errors. - Try a different browser or incognito window. Open the platform in a private/incognito window or a different browser to rule out browser-specific issues. - Clear your browser cache. Outdated cached data can occasionally interfere with platform requests. Clear your cache, then reload and try again. What to Have Ready When You Contact Support To help our team investigate as quickly as possible, please have the following information ready before reaching out: - The exact error message you see (e.g. "Request failed: 400") - The name of the article or project you were working on in Content Genius - The specific action you were performing when the error appeared - The approximate date and time the error occurred (including your timezone) - Any steps you already tried to resolve it If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🚫 Fix the Billing Not Active Content Error

🔍 What Is This Error? The billing_not_active — Refresh Page error appears when Search Atlas cannot confirm your billing status at the moment of generating content. This can happen even if your account shows an available credit balance and you have recently purchased credits or a subscription. The error is a billing-state verification issue, not a credit shortage. ⚙️ Why Does This Happen? This error is typically caused by a billing status sync issue. After a purchase or plan change, your billing state may not have updated across all platform services yet, causing the platform to temporarily block content generation even though your account is in good standing. 🛠️ What to Do When You See This Error Because this error reflects a backend billing sync issue rather than a problem you can resolve directly, the recommended step is to escalate to the support team. When reaching out, please have the following ready so an agent can investigate quickly: - Your workspace or project name - The exact error message displayed - The approximate time and date the error first appeared - Any recent billing changes (new purchase, plan upgrade, etc.) 📊 Verify Your Account Status Before Escalating To confirm your account is in good standing before escalating: - Check that your credit balance is visible and greater than zero in your account settings. - Confirm your subscription status has not lapsed by reviewing your billing details in your account 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.

🛠️ How to Fix AI Article Output

This guide helps when Content Genius cannot generate an article or produces content in the wrong language. 📍 Where to Find It Open Content in the left sidebar, then select Content Genius. 🛠️ Step-by-Step 1. Choose Generate to create one article, or select Write with AI in Bulk for multiple articles. 2. Complete the required article details, including the topic, keyword, and any audience or content instructions. 3. Set the language in the generation form. If no language setting is available, state the required language clearly in the instructions, such as “Write the entire article in Spanish.” 4. If generation fails, shorten the brief, remove unusual symbols or formatting, confirm that required fields are complete, and select Generate again. 5. If the output uses the wrong language, revise the language instruction, remove conflicting multilingual instructions, and generate the article again. ✅ How to Confirm It Worked Confirm that a complete article draft appears after generation. Check the title, headings, and body text to ensure they are consistently written in the selected language. If the draft is incomplete or still uses another language, update the instructions and retry with a shorter brief. 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 Auto-Linker Empty Inventory Error

If the Content Genius auto-linker returns zero links and shows the message page_inventory_empty, even though you added your location pages to the Brand Vault, this article explains why it happens and how to fix it. 🔍 What the Error Means The auto-linker builds internal links from a list of pages it can use, called the page inventory. The message page_inventory_empty means that when the auto-linker ran, it found no usable pages in that list. It had nothing to link to, so it returned zero links. This does not usually mean something is wrong with your article. It means the pages you added are not reaching the auto-linker in a usable form. 🧩 Common Causes - URLs were not saved. Pages entered in the Brand Vault only count once they are saved or confirmed. - Wrong brand or project. The pages were added to one brand, but the Content Genius document is connected to a different one. - Domain mismatch. The auto-linker is designed for internal links, so URLs should be on the same website as the content you are writing. - URL formatting issues. Missing https://, extra spaces, duplicate entries, or several URLs pasted on one line can cause pages to be skipped. - Pages that cannot be used. URLs that redirect, return a not-found or error page, require a login, or are blocked from crawling may be left out. - Pages still processing. Newly added pages may need a few minutes before they are available. - Stale document session. A document opened before you updated the Brand Vault may not pick up the changes. 🛠️ Step-by-Step Fix 1. Check that your pages were saved. Open the Brand Vault and confirm that your location page URLs appear in the list after you refresh the page. 2. Confirm the right brand. Make sure the brand or project that holds your location pages is the one selected for the Content Genius document you are working in. 3. Check the URL format. Each URL should be complete, such as https://www.yourdomain.com/locations/city-name, with one URL per entry and no extra spaces. Remove any duplicates. 4. Open each URL in a browser. Each page should load directly and show your content. If it redirects elsewhere, shows an error, or asks for a login, replace it with the final, working URL. 5. Check the domain. Make sure the pages belong to the same website as the brand connected to your document, including the same www or non-www version. 6. Wait a few minutes. If you just added the pages, give the platform a short time to process them. 7. Refresh and run the auto-linker again. Reload Content Genius, reopen your document, and run the auto-linker once more. 8. Try a new document. If the error remains, create a new Content Genius document under the same brand and run the auto-linker there. This helps show whether the problem is in the document or in the Brand Vault. 📍 Tips for Location Pages - Add only the live, public location pages you want linked, not draft or staging pages. - Use the final version of each URL, not a version that redirects. - Make sure location pages are not set to noindex or blocked from crawlers, since this can make them unavailable. - Keep your content relevant. The auto-linker works best when the article topic relates to the pages in your inventory, so a post about one city is more likely to find links than an unrelated topic. ✅ How to Check That It Worked - The auto-linker returns one or more suggested links instead of zero. - The page_inventory_empty message no longer appears. - The suggested links point to the location pages you added. 🛡️ How to Prevent It Coming Back - After adding or editing pages in the Brand Vault, always save and refresh before opening Content Genius. - Keep your page list current. Remove pages that are deleted, moved, or redirected. - Check that each new document is connected to the correct brand before running the auto-linker. - When you add many pages at once, wait a few minutes before running the auto-linker. 💬 Still Seeing the Error? If the error persists after these steps, it helps to have a few details ready: the brand name, the document you are working in, and two or three of the location URLs you added. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🔌 Using Content Genius With Your CMS

📌 What the Universal CMS Connector means The Universal CMS Connector is intended for CMS platforms that are not covered by a dedicated Search Atlas plugin. However, it is not guaranteed to work with every CMS. Compatibility depends on the platform’s publishing access, authentication method, API capabilities, and content structure. References to a “universal” connector describe its intended use case, not a promise of compatibility with all CMS platforms. Some platforms, including certain hosted or closed CMS solutions, may not support the connection or automated publishing workflow. ✅ Before you connect your CMS - Confirm that your CMS allows third-party integrations or API-based publishing. - Check whether your account has permission to create or update articles. - Verify that your CMS supports the authentication method requested during setup. - Confirm that your website can accept the required article fields, such as title, body, slug, and metadata. - Test the connection on a draft or staging site before publishing live content. 📝 Create content in Content Genius 1. Open Content in the left sidebar. 2. Select Content Genius. 3. Choose Generate, Write it yourself, or Write with AI in Bulk. 4. Review and edit the generated content before sending it to your CMS. 🔗 Connect and publish If your CMS has a dedicated Search Atlas integration, use that integration instead of the Universal CMS Connector. For other CMS platforms, follow the connector setup instructions and complete a test connection. If the connection succeeds, publish a draft first and verify the result in your CMS. If setup fails, do not assume the CMS is supported. The failure may indicate that the platform does not expose the required permissions, API access, or publishing features. You can still use Content Genius to create and export content, then add it to your CMS manually. 🛠️ Troubleshoot connection problems - Recheck the CMS URL and login or API credentials. - Make sure the connected user has content publishing permissions. - Disable restrictions that block third-party requests, if your CMS provides those settings. - Check whether security tools, redirects, or staging protections prevent the connection. - Try a draft workflow rather than publishing directly. - Use manual copy and paste or export when the CMS cannot support the connector. 📋 Important note for Duda users Duda may not support the Universal CMS Connector workflow described in general setup guidance. A successful connection and publishing process is not guaranteed for Duda sites. If the connector does not work, use Content Genius to create the article and add it to Duda through your normal content workflow. 💬 Need help confirming compatibility? When contacting support, include your CMS name, site type, the setup step that failed, and any error message. This helps the team determine whether the issue is configuration-related or a platform compatibility limitation. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🗑️ Deleting Cloud Stacks Campaigns and Removing Indexed Content