Troubleshooting: Content Generation Errors

💡 Content Genius Web Browsing and Image Limitations Explained

🔍 Fix Missing Target Article Validation

🔍 What the error means The “Missing Target Anchor Text” error means Search Atlas could not confirm the required anchor text and destination link on the published target article during validation. The link may appear correct in your editor or browser while the automated check receives different content, an older page version, or a modified HTML structure. ✅ Check the live article 1. Open the target URL in a private or incognito browser window. 2. Confirm that the page loads successfully without requiring a login, special access, or a temporary preview link. 3. Search the rendered page for the exact required anchor text, including spelling, spacing, punctuation, and capitalization. 4. Confirm that the anchor text is linked directly to the required target URL. 5. Check that the link is a normal DoFollow link and does not include a nofollow, sponsored, or ugc attribute. 6. Verify that the link is in the article content, not only in navigation, a footer, a sidebar, a related-content block, or a hidden element. 🛠️ Check the link destination Compare the destination URL exactly with the required URL. Differences such as http versus https, www versus non-www, trailing slashes, URL parameters, fragments, redirects, or a canonical destination can prevent validation. If the required URL redirects, update the article so the link points directly to the final destination whenever possible. 🔄 Republish and validate again Validation can use the publicly available version of a page rather than an unsaved editor version. After making changes, publish the article and wait for the updated page to load consistently. Then return to the relevant article in Content and run the validation again. If your site uses caching, a content delivery network, or a publishing workflow, clear or complete those processes first. 🧩 Check for content and keyword mismatches Some article-generation or editing workflows may create content without the expected target keyword or may associate a keyword with the wrong article. Confirm that the article is assigned to the intended target URL and keyword, and that the required anchor text was not changed during editing. If the article was generated from a planner or AI workflow, compare its assigned target details with the current validation requirements. 📄 Check the page source when needed If the link is visible but the error remains, inspect the page source or browser developer tools and confirm that the anchor exists in the HTML delivered to visitors. JavaScript-rendered links, links inside blocked content, duplicate anchor text, or a page that serves different content to automated requests may not be detected reliably. 🚨 When to request an investigation Request a review if all of the following are true: - The live URL is publicly accessible. - The exact anchor text appears in the published article. - The link points directly to the required destination. - The link is DoFollow and appears in the main article content. - You republished the page and ran validation again. When contacting the team, include the article URL, target URL, exact anchor text, a screenshot of the live link, and the approximate time of your latest validation attempt. This helps the team compare the live page with the validation result and identify caching, rendering, assignment, or dashboard issues. 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.

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

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

🖼️ Fix Article Image Alt Text

🖼️ Understand the issue In some Content Genius V5 articles, image alt text may describe the surrounding section or heading instead of explaining what appears in the image. This can make the text less useful for accessibility and search engines. 🔍 What effective alt text includes Good alt text briefly describes the image’s meaningful content and purpose. It should help someone understand the image without seeing it. - Describe the main subject, action, or result shown. - Use specific, natural language related to the image. - Keep it concise and avoid unnecessary phrases such as “image of.” - Do not repeat the article heading or nearby paragraph unless the image directly shows that information. - For decorative images, use empty alt text when your publishing system supports it. 🛠️ Review an article in Content Genius 1. Open Content in the left sidebar. 2. Select Content Genius. 3. Open an existing article or choose an action such as Generate, Write with AI in Bulk, Write it yourself, Write an article, or Rework existing article. 4. Review every inserted image and compare its alt text with the actual visual content. 5. Replace alt text that repeats the section heading, paragraph, or unrelated topic. 6. Save or publish the article only after confirming that each image has accurate, concise alt text. ✏️ Improve inaccurate alt text Write a replacement that identifies what the reader can see and why it matters in context. For example, change “Benefits of remote work” to “Employee working from a home office with a laptop and video call.” Avoid adding keywords that are not visibly supported by the image. ✅ Validate before publishing - Check that each meaningful image has a relevant description. - Confirm that alt text does not copy the section heading or body text. - Remove descriptions of details that are not visible. - Make sure the wording is useful when read by a screen reader. - Review the published page to confirm the final alt text was retained. 🚧 If the article is blocked If Content Genius flags image alt text as duplicate prose or prevents the article from being completed, review the affected image and rewrite the alt text to describe the image itself. If the image is defective or does not match the article, replace it with a suitable image before continuing. 💬 Get 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 Duplicate FAQ Sections

🧭 What content1Summary and content8Summary mean These labels identify content summary fields used during article generation. They are not intended to create two separate FAQ sections on the same page. If both fields contain similar questions and answers, the generated article may display duplicate or misplaced FAQ content. This can happen when source instructions, templates, or generated content include overlapping FAQ material. 🔎 How to identify the issue 1. Open Content from the left sidebar. 2. Select Content Genius. 3. Open the relevant generated article or project. 4. Review the article outline and search for repeated FAQ headings, questions, or answers. 5. Compare the content associated with content1Summary and content8Summary. Duplicate content may appear as two FAQ headings, repeated accordion items, or the same questions placed in the middle of the article and again at the end. 🛠️ How to fix duplicate FAQs 1. Keep only one FAQ section in the article. 2. Remove repeated questions and answers from the summary or generation instructions. 3. Make sure each FAQ question is unique and directly related to the article topic. 4. Regenerate the article or edit it manually after removing the duplicate content. 5. Preview the final article and confirm that each question appears only once and that answers display as normal text. ✍️ Prevent the issue in new articles - Use one clearly defined FAQ section in your content brief. - Avoid copying the same FAQ list into multiple summary fields. - Review generated content before publishing, especially after bulk generation. - Check that FAQ formatting uses the available FAQ controls rather than pasted markup or unsupported HTML. - When reworking an existing article, confirm that the original FAQ section is not being retained alongside a newly generated one. ✅ Final publishing checklist - There is only one FAQ heading unless multiple sections are intentionally required. - No question or answer is repeated. - FAQ items appear in the intended location. - Accordion controls, if used, have one arrow per item and readable text. - No raw tags such as appear in the published 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.

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

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 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 Images That Disappeared After Adding Map Code

🔍 What Happened to My Images? If your website images disappeared shortly after you added a map embed code (such as a Google Maps iframe), the two events are almost certainly connected. Map embed code that contains unclosed HTML tags, extra quotation marks, or misplaced characters can corrupt the surrounding HTML structure, causing images — and sometimes entire sections — to stop rendering. The good news is that your images have not been deleted. They are still stored in your media library. The issue is a broken HTML structure that prevents the browser from displaying them correctly. 🛠️ How to Fix the Problem 1. Open Website Studio. In the left sidebar, navigate to Website Studio (URL: /website-studio) and open the affected page in the editor. 2. Locate the map code block. Scroll to the section where you pasted the map embed code. Click on that block to select it. 3. Switch to the HTML/Code view. Inside the block editor, switch from the visual view to the HTML or code view so you can inspect the raw markup. 4. Remove the map code entirely. Delete all of the map embed code you pasted. Save the page and preview it to confirm whether your images reappear. If they do, the embed code was the cause. 5. Clean the embed code before re-adding it. Copy your map embed code into a plain-text editor (such as Notepad or TextEdit in plain-text mode) to strip any hidden characters. Check that every tag is properly closed — for example, an <iframe> must end with </iframe> — and that there are no stray quotation marks or extra brackets. 6. Re-paste the cleaned code. Return to the HTML view of the map block and paste the cleaned code. Save and preview the page again to verify that both the map and your images display correctly. ⚠️ Common Mistakes That Break Page Layouts - Unclosed tags: An <iframe> or <div> that is never closed will cause everything below it to be interpreted as part of that element, hiding images and other content. - Copied code from a web page instead of the embed tool: Copying map code directly from a rendered web page often picks up extra HTML that conflicts with your site's structure. Always use the official Share → Embed option from Google Maps or your map provider. - Pasting into the visual editor: Pasting raw HTML code into the visual (WYSIWYG) editor rather than the HTML/code view can introduce duplicate or malformed tags. Always paste embed code in the code view. - Extra line breaks or whitespace in the code: Some editors insert <br> or <p> tags inside your embed code when you paste, which can break it. ✅ Best Practices for Adding Map Embeds - Always use the HTML/code view of a block when pasting any embed code. - Validate your embed code at a free HTML validator (such as validator.w3.org) before adding it to your page. - After saving any code change, immediately preview the page on both desktop and mobile to catch layout issues early. - Keep a backup of your page content before making code edits — use the page duplication or version history feature in Website Studio if available. 💬 Still Need Help? If your images are still missing after following these steps, or if you are unsure which part of the code is causing the issue, our team is ready to assist. 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 and Disable AI Alt Text Errors

🔍 Overview When using the AI alt text feature inside Search Atlas, you may occasionally see an error message during generation, or you may simply prefer to write alt text manually. This article explains what to do when you encounter an AI alt text error and how to request that AI generation be turned off for alt text. ⚠️ What to Do When You See an AI Alt Text Error If an error message appears when the platform attempts to generate alt text for your images, try the following general troubleshooting steps before escalating: 1. Note the exact wording of the error message you are seeing — this will be important if you need to contact support. 2. Refresh your browser and navigate back to the AI alt text feature. 3. Confirm you are connected to the internet and that your session has not timed out. 4. Clear your browser cache, then reload the platform. 5. Try a different browser (Chrome or Edge recommended) to rule out a browser-specific conflict. 6. If the error persists across multiple images or multiple attempts, wait a few minutes and try again, as the issue may be temporary. If the error continues after completing these steps, please contact our support team with the exact error message text, the name of the project or page affected, and a description of what you were doing when the error appeared. 🚫 How to Disable AI Generation for Alt Text If you prefer to write alt text manually and want to stop the platform from triggering AI generation automatically, our support team can help you with this. When reaching out, let the team know which project or workspace you would like this changed for, and whether you want AI generation disabled for all images or for a specific page. 📋 What to Have Ready When You Contact Support To help our team resolve your issue as quickly as possible, please have the following information available: - The exact error message text as it appears on screen - The name of the project, page, or URL where the error occurred - The approximate date and time the error first appeared - A description of any steps you have already tried 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 Signal Genesys API Key Validation Errors

🔍 What Is This Error? When publishing a press release through Signal Genesys, you may encounter a 401 'API Token is invalid' error. This means the API key connected to your Signal Genesys account could not be authenticated. The press release will not publish until this is resolved. This error is generally caused by an issue with the API key configured for your Signal Genesys integration — for example, the key may have been entered incorrectly, regenerated in Signal Genesys without being updated in Search Atlas, or it may lack the necessary permissions. ⚙️ What to Check - Verify the API key in Signal Genesys: Log in to your Signal Genesys account and locate your API key in your account settings. If you are unsure where to find it, consult Signal Genesys's own documentation or support. - Update the key in Search Atlas: Once you have a valid API key from Signal Genesys, navigate to the Signal Genesys integration area within Search Atlas and replace the existing key with the new one. Save your changes. - Retry publishing: After updating the key, attempt to publish your press release again to confirm the error is resolved. - Check for typos or extra spaces: Always copy and paste your API key directly — never type it manually. Even a single extra space will cause a validation failure. - Confirm API permissions: Ensure the key you are using has the permissions required to publish press releases. If you are unsure, check your Signal Genesys account plan or contact Signal Genesys support to verify the key's scope. 🛠️ If the Error Persists If you have updated your API key and the 401 error continues, please reach out to our support team. To help us investigate quickly, have the following ready: - Your Search Atlas project name or workspace URL - The exact error message you are seeing (a screenshot is helpful) - The timestamp of the failed publish attempt - Confirmation of whether the API key was recently regenerated or changed in Signal Genesys 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.

🛠️ 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 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 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 Duplicate Content After Rollback Recovery

What Happened and Why When a rollback is used to recover lost or missing pages in Website Studio, the recovery process can occasionally reintroduce content blocks that were already present on your live pages. The result is duplicated sections — most commonly appearing below the footer — that show up across pages of your project. This is a known side effect of the rollback recovery process and requires our technical team to resolve it on the backend. What to Expect Because this issue originates from the rollback process itself, it cannot be reliably resolved through manual editing in the Website Studio interface. Our team will need to access your project on the backend to safely remove the duplicated content without affecting the rest of your site. Once reported, our team will investigate and apply the fix directly. How to Escalate To help our team resolve this as quickly as possible, please have the following information ready when you reach out: - Project name — the exact name of the Website Studio project affected. - Affected pages — a list of specific pages (or confirmation that the duplicate appears site-wide). - Rollback date and time — when the rollback was performed, as accurately as possible. - Description of the duplicated content — what the duplicated section contains or looks like (e.g., a banner, a footer block, a text section). - Any screenshots — if you are able to capture the duplicated sections, these will help our team identify the issue 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 Topical Map and Crawl Settings Errors

🔍 Overview When creating a topical map in Search Atlas, you may run into two common issues: a URL validation error that greys out the input field, or OTTO only returning results for one page even though your site has many more. Both issues are usually caused by incorrect URL formatting or misconfigured crawl settings. This article walks you through how to fix each problem. ⚠️ Issue 1: URL Field Shows a Validation Error and Is Greyed Out This error appears when the URL entered does not match the expected format. The field becomes uneditable until the issue is resolved. Common causes: - Missing or incorrect protocol (e.g., typing www.example.com instead of https://www.example.com) - A trailing space before or after the URL - Special characters or unsupported symbols in the URL - Entering a URL path instead of the root domain (e.g., https://example.com/blog instead of https://example.com) How to fix it: 1. Go to Left sidebar → Content → Topical Maps. 2. Click to create a new topical map. 3. Clear the URL field completely. 4. Re-enter your URL in the correct format: https://www.yourdomain.com — include the protocol and avoid any trailing slashes or spaces. 5. Wait for the validation indicator to confirm the URL is accepted before proceeding. 📄 Issue 2: OTTO Only Shows Results for One Page If OTTO is crawling your site but only returning data for a single page, your crawl depth or crawl scope settings are likely limiting the number of pages analysed. Common causes: - Crawl depth is set to 1, meaning only the root URL is crawled - Crawl scope is restricted to a single page or subdirectory - The sitemap has not been submitted or is not accessible - The website blocks crawlers via robots.txt rules How to fix it: 1. Navigate to Left sidebar → OTTO SEO → SEO Automation (URL: /seo-automation-v3). 2. Locate your project and open its crawl settings. 3. Increase the crawl depth to cover the number of page levels your site contains. For most sites, a depth of 3 to 5 is recommended. 4. Ensure the crawl scope is set to your full root domain, not a specific subfolder or page. 5. If you have a sitemap, confirm the URL is entered correctly in the sitemap field (e.g., https://www.yourdomain.com/sitemap.xml). 6. Save your settings and re-run the crawl. Once the crawl completes, return to Left sidebar → Content → Topical Maps and generate or refresh your topical map. You should now see data across all crawled pages. ✅ Best Practices for Topical Map Setup - Always use the full root domain with https:// when entering your URL. - Set crawl depth to at least 3 for small sites and 5+ for larger sites. - Submit an XML sitemap to help OTTO discover all pages faster. - Check your robots.txt file to make sure it does not block Search Atlas crawlers. - Re-run the crawl after any major site changes before generating a new topical map. 💬 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 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.

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

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

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

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

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

⚕️ 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 Topical Map Generation and Edit Issues

🔍 Overview Two known issues can affect Topical Maps in Search Atlas: articles failing to start generating, and content layout appearing broken after editing headings or meta tags. Both are bugs that our team is actively investigating. This guide explains what to expect and how to escalate effectively if you encounter either issue. ⚠️ Issue 1: Article Generation Fails to Start Some customers find that after clicking to generate articles from a Topical Map, nothing happens — no progress indicator, no status update, and no content is produced. This is a known issue. The root cause has not yet been confirmed, and there is no guaranteed self-serve workaround at this time. 📋 How to Escalate a Generation Failure To help our team investigate as quickly as possible, please have the following ready before reaching out: - Your project or Topical Map name — the exact name as it appears in your account. - The exact time you attempted generation — including your timezone. - The number of articles you selected — how many topics or subtopics you attempted to generate at once. - A description of what you saw — for example, whether any button state changed, whether any error message appeared, or whether the page was completely unresponsive. - Your browser and operating system — for example, Chrome on Windows 11. ⚠️ Issue 2: Layout Corruption After Editing Headings or Meta Tags Some customers report that after editing article headings or meta tags inside Topical Maps, the layout of their content appears broken. This is a known issue currently under investigation. The confirmed root cause has not been identified, and no self-serve fix has been documented. 📋 How to Escalate a Layout Corruption Issue Please gather the following details before contacting support so our team can investigate efficiently: - Your project or Topical Map name — the exact name as it appears in your account. - Which fields you edited — for example, which heading level or which meta tag was changed. - When the issue first appeared — the date, time, and your timezone. - What the broken layout looks like — a screenshot or screen recording showing the problem is extremely helpful. - Where the corruption appears — for example, inside the Search Atlas editor, in an exported file, or on a published page. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Fix Content Genius 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.

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

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

🔌 Troubleshooting 'Failed to Fetch' AI Agent Errors

This article addresses the 'failed to fetch' error that appears when working with the AI agent inside Content Genius — specifically when the agent fails to respond or load results regardless of what you type. This error is a connection-level failure, not a problem with your input, and it has specific causes and fixes you can work through step by step. 🔍 Common Causes - Browser or network interruption: The AI agent loses its connection mid-session, often due to a timeout, unstable Wi-Fi, or a VPN interfering with requests. - Stale session or cached data: An expired session token or corrupted cache can block the agent from making successful API calls. - Browser extension conflict: Ad blockers, privacy extensions, or script blockers frequently intercept AI agent fetch requests. - Temporary platform instability: A brief backend outage or degraded service can produce this error across all users intermittently. 📍 Where to Find It The AI agent is accessed via Left sidebar → Home (Hi, CSM. What will we get done today?). Once there, click Launch Atlas Agent as a per-project action to open the agent interface where the error appears. 🛠️ Step-by-Step 1. Reload the page: Press Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac) to do a hard refresh, bypassing the cache. Then relaunch the agent via Left sidebar → Home (Hi, CSM. What will we get done today?) → Launch Atlas Agent (per-project action). 2. Check your internet connection: Open another tab and load a different website to confirm your connection is stable. If you are on Wi-Fi, try switching to a wired connection or a mobile hotspot to rule out network instability. 3. Disable browser extensions: Open an Incognito or Private window (which disables most extensions by default) and navigate back to Left sidebar → Home (Hi, CSM. What will we get done today?) to test whether the error persists. If the agent works in Incognito, a browser extension is the cause — disable them one by one to identify the culprit. 4. Clear browser cache and cookies: In your browser settings, clear cached images, files, and cookies for the Search Atlas domain, then log back in and retry the agent. 5. Try a different browser: If the error continues, open Search Atlas in a different browser (e.g., switch from Chrome to Firefox or Edge) and relaunch the agent to isolate whether the issue is browser-specific. 6. Disable your VPN (if applicable): If you are using a VPN, temporarily disconnect it and retry. VPNs can route traffic in ways that block AI agent fetch requests. 7. Wait and retry: If none of the above steps resolve the issue, wait 5–10 minutes and try again, as this error can also be caused by a temporary platform-side issue that resolves on its own. ✅ How to Confirm It Worked After applying any of the steps above, confirm the fix by doing the following: - Navigate to Left sidebar → Home (Hi, CSM. What will we get done today?) and click Launch Atlas Agent (per-project action). - Type any prompt into the agent input field and submit it. - A successful connection will show the agent actively processing your request — you will see a loading indicator followed by a response, not the 'failed to fetch' error message. - If the agent responds — even partially — the connection has been restored. If the error reappears immediately, note the exact steps you already tried and contact support using the method below. 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.

🗺️ Fix Topical Map URL Validation Errors

🔍 Overview When creating a topical map, you may see the URL field greyed out with the message Provide valid url like https://example.com even though your URL looks correct. This is almost always caused by a browser cache or session issue — not a problem with your URL itself. This article walks you through how to fix it quickly. 🧭 How to Navigate to Topical Maps 1. Log in to Search Atlas. 2. In the left sidebar, click Content. 3. Select Topical Maps from the sub-menu. 4. Click Create Topical Map to open the creation form. ⚠️ What This Error Looks Like - The URL input field appears greyed out or is not accepting input. - A message reads: Provide valid url like https://example.com. - The error persists even when you type or paste a correctly formatted URL such as https://yoursite.com. - The Create or Generate button remains inactive. 🛠️ Step 1 — Test in an Incognito or Private Window The fastest way to determine whether your browser session is causing the issue is to open an incognito or private window. 1. Open a new incognito window: - Chrome / Edge: Press Ctrl + Shift + N (Windows) or Cmd + Shift + N (Mac). - Firefox: Press Ctrl + Shift + P (Windows) or Cmd + Shift + P (Mac). - Safari: Go to File → New Private Window. 2. Navigate to Search Atlas and log in. 3. Go to Content → Topical Maps and try creating a topical map again. 4. If the URL field works correctly in incognito mode, your regular browser session has cached data that is interfering. Continue to Step 2. 🧹 Step 2 — Clear Your Browser Cache and Cookies Cached files and stored cookies can cause form fields to behave unexpectedly. Clearing them resolves the issue in most cases. 1. Open your browser settings: - Chrome: Press Ctrl + Shift + Delete (Windows) or Cmd + Shift + Delete (Mac). - Firefox: Press Ctrl + Shift + Delete (Windows) or Cmd + Shift + Delete (Mac). - Edge: Press Ctrl + Shift + Delete. - Safari: Go to Safari → Settings → Privacy → Manage Website Data. 2. Set the time range to All time. 3. Select at least Cached images and files and Cookies and other site data. 4. Click Clear data (or the equivalent button in your browser). 5. Close and reopen the browser completely. 6. Log back in to Search Atlas and return to Content → Topical Maps. 7. Attempt to create a new topical map and enter your URL. 🔄 Step 3 — Additional Browser Checks If clearing the cache does not resolve the issue, try the following: - Disable browser extensions: Some ad blockers or form-autofill extensions interfere with input fields. Disable all extensions temporarily and reload the page. - Try a different browser: If you are using Chrome, try Firefox or Edge (or vice versa) to rule out a browser-specific conflict. - Perform a hard refresh: Press Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac) to force the page to reload without using cached files. - Check your URL format: Make sure your URL includes the protocol and has no trailing spaces. Use the format https://yoursite.com — no extra characters or slashes at the end. 📄 OTTO Showing Results for Only One Page If OTTO is displaying data for only one page even though your site has multiple pages, this is typically a crawl scope issue. OTTO's results depend on the crawl settings configured for your site. 1. In the left sidebar, go to OTTO SEO → All Sites (SEO Automation) (URL: /seo-automation-v3). 2. Select your website project. 3. Open the crawl or site settings for your connected domain. 4. Confirm that the crawl scope is set to cover the full site, not just the root URL or a single page. 5. Re-run the crawl after updating the settings. 6. Wait for the crawl to complete — large sites may take several minutes — then check whether OTTO now surfaces results across multiple pages. If the crawl settings appear correct but OTTO still shows only one page, the domain may not be fully verified or connected. Verify that your domain is properly linked under the project settings before re-running the crawl. ✅ Summary of Fixes - URL field greyed out → test in incognito mode first, then clear cache and cookies. - Validation error persists → disable extensions or switch browsers. - OTTO showing one page only → check crawl scope settings and re-run the crawl. 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 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 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.

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

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

🗺️ Search Atlas — Topical Maps & Content Planning Issues

This article covers Topical Maps, content planning, competitor gap analysis, topic clusters, content briefs, custom topics, saved maps, and Content Velocity reporting inside Search Atlas. ⚠️ Error 1: Topical Map is stuck on "Generating" for more than 30 minutes What's happening Competitor analysis and keyword gap analysis (DKN) run as asynchronous background jobs. Network interruptions, provider delays, or queue congestion can cause the generation task to stall. This is more common when: - analyzing very large domains - using broad seed topics - or generating multiple maps simultaneously. Steps to try 1. Go to: Left Sidebar → Local → Local SEO Tools →Topical Maps 2. Locate the generation job stuck in: "Generating"/"Fetching data" 3. Click Delete/Cancel on the stuck task 4. Start a new generation: - this will NOT delete existing maps - only the failed job is replaced 5. Reduce the scope temporarily: - use fewer competitors - or a narrower seed topic 6. Avoid running multiple Topical Maps simultaneously for the same domain 7. Wait 2 hours if the task remains frozen: - stalled jobs automatically time out and retry 8. Hard-refresh the dashboard after retrying: - Ctrl + Shift + R - Cmd + Shift + R 9. Check: Left Sidebar → Content → Topical Maps for duplicate stuck processes 10. Contact support if: - every generation attempt stalls repeatedly - or generation never completes after multiple retries Important Notes - DKN jobs are resource-intensive - large topical maps may legitimately require extended processing time - canceling a stuck job does not delete completed maps ⚠️ Error 2: Topical Map generated but clusters are missing or empty What's happening The AI cluster generation engine occasionally returns malformed or incomplete cluster data that cannot be parsed correctly. This can cause: - empty topic groups - blank keyword clusters - or partially generated maps. Steps to try 1. Open the affected Topical Map 2. Identify: - empty clusters - incomplete topic groups - or blank sections 3. Click Regenerate Clusters on the affected section 4. Wait several minutes for the cluster rebuild to complete 5. Refresh the map after regeneration 6. If multiple clusters are empty: - delete the map - regenerate from scratch 7. Narrow the seed keyword: - overly broad topics increase malformed cluster probability 8. Avoid running simultaneous cluster regenerations 9. Test with a smaller competitor set temporarily 10. Contact support if: - regenerated clusters continue returning empty - or the same map repeatedly fails parsing Important Notes - cluster generation depends on AI parsing pipelines - broad generic keywords produce lower-quality cluster separation ⚠️ Error 3: Competitor domains not showing up in the gap analysis What's happening Competitor intelligence data is pulled from external SEO research providers. Very small, new, or low-authority domains: - may not exist in the provider database yet - or may have insufficient crawl coverage. Steps to try 1. Verify the competitor domain is publicly accessible 2. Confirm the domain: - ranks in Google - has indexed pages - and has backlink activity 3. Try larger competitors in your niche first 4. Use competitor domains with: - 500+ referring domains - or established organic visibility 5. Avoid testing with: - new domains - staging sites - or low-traffic microsites 6. Run: Left Sidebar → Site Metrics → Competitors separately to confirm the competitor has provider coverage 7. Refresh the gap analysis after changing competitors 8. Reduce the number of competitors in the request 9. Retry during off-peak hours 10. Contact support if: - major well-known competitors never appear - or all competitor analysis remains blank Important Notes - competitor visibility depends on external provider coverage - provider databases refresh independently from Search Atlas ⚠️ Error 4: "Cannot create analysis" error when starting a new Topical Map What's happening A duplicate or active DKN generation task already exists for the same domain. The system blocks overlapping analysis jobs to: - prevent queue conflicts - avoid duplicate processing - and reduce malformed outputs. Steps to try 1. Go to: Left Sidebar → Content→ Topical Maps → Check Active Jobs 2. Look for: - pending jobs - stuck jobs - or active generations 3. Wait for active jobs to complete 4. Cancel frozen or duplicate jobs 5. Refresh the page after cancellation 6. Retry generation after several minutes 7. Avoid opening multiple generation tabs simultaneously 8. Confirm another team member is not already running the same analysis 9. Reduce the scope of the request temporarily 10. Contact support if: - no active jobs exist - but generation still fails immediately Important Notes - duplicate protection is intentional system behavior - background jobs may require several minutes to clear after cancellation ⚠️ Error 5: Content brief generated from a topical cluster is off-topic What's happening The content brief inherits context from the cluster seed keyword. If the seed keyword is: - too broad - ambiguous - or low-intent …the generated brief may become generic or partially irrelevant. Steps to try 1. Edit the cluster's primary keyword 2. Make the keyword: - more specific - more localized - or more intent-driven 3. Add: - target audience - industry - or content angle 4. Use: Refine Brief before regenerating 5. Avoid generic seed terms like: - "marketing" - "SEO" - "software" 6. Use long-tail intent-focused keywords instead 7. Regenerate the brief after refining 8. Compare competitor examples manually 9. Add custom subtopics if important context is missing 10. Contact support if: - all briefs consistently generate irrelevant outputs Important Notes - brief quality depends heavily on keyword specificity - AI-generated briefs should be treated as strategic first drafts ⚠️ Error 6: Topical Map not including keywords I know are important What's happening Automated keyword discovery prioritizes: - provider data - competitor overlap - and detected search demand. Very niche or long-tail keywords may not be discovered automatically. Steps to try 1. Use: Add Custom Topic inside the map 2. Manually create missing keyword clusters 3. Run: Left Sidebar → Keyword → Keywords Research separately for the missing terms 4. Import discovered keywords into the map manually 5. Expand competitor selection 6. Add more seed keywords before regeneration 7. Use localized variations of important terms 8. Include question-based queries and FAQs 9. Regenerate cluster relationships after additions 10. Contact support if: - large obvious keywords never appear in discovery Important Notes - no automated keyword discovery system captures 100% of long-tail search behavior - manual augmentation is expected for advanced SEO workflows ⚠️ Error 7: Saved Topical Map is no longer visible in the list What's happening Topical Maps are attached to the project where they were created. If the project: - was archived - deleted - disconnected - or moved …the associated map may disappear from the visible list. Steps to try 1. Check whether the project was deleted accidentally 2. Restore the archived project if possible 3. Refresh the Topical Maps dashboard 4. Confirm you are inside the correct workspace 5. Verify another team member did not rename or move the project 6. Check filters inside the Topical Maps list 7. Log out and back in to refresh permissions 8. Search for the map by project/domain name 9. Contact support if: - the project exists - but maps remain permanently missing Important Notes - restoring a project restores associated Topical Maps - workspace permissions affect map visibility ⚠️ Error 8: Content Velocity chart shows no data What's happening Content Velocity is a Beta reporting feature that requires enough publishing history before meaningful trends can be generated. Steps to try 1. Confirm your account has at least 30 days of publication history 2. Verify content was published through: - OTTO - Website Studio - or tracked publishing systems 3. Refresh the reporting dashboard 4. Expand the date range 5. Confirm the correct project is selected 6. Verify content tracking is enabled for the project 7. Wait for the next reporting cycle 8. Continue publishing content consistently 9. Avoid expecting meaningful trends from very small datasets 10. Contact support if: - the chart remains empty after 45+ days - or previously visible data disappears unexpectedly Important Notes - Content Velocity is still evolving as a Beta feature - trend analysis improves with larger publishing history datasets Most Topical Maps & Content Planning issues are not caused by broken Search Atlas functionality. They are usually related to: - asynchronous DKN processing - AI clustering behavior - competitor data limitations - broad seed topics - duplicate background jobs - or insufficient content history. Because Topical Maps combine AI generation, SEO intelligence, and semantic clustering systems, some delays or incomplete outputs are expected during large-scale analysis operations. 👉 The best Topical Maps results come from: - highly specific seed topics - strong competitor selection - narrow semantic intent - clean project organization - and allowing background analysis jobs enough time to complete

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

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

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

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

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

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

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

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

🛠️ 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 Broken Images in Generated Content

🔍 Why images may appear broken Broken images usually result from an invalid image URL, a deleted or restricted source file, unsupported formatting, or a page that cannot load the image securely. Images may also fail after content is copied to a different website if the original source does not allow external use. 🧭 Check the image source 1. Open the affected page or draft and identify the broken image. 2. Copy the image URL, if one is available, and open it in a new browser tab. 3. Confirm that the URL loads an image directly and does not require a login. 4. Check that the address begins with https:// and has no spaces or missing characters. If the image URL does not open directly, replace it with a working image URL or upload the image to your website’s media library. ✍️ Replace images in Content Genius To update content created with Content Genius, go to Content → Content Genius. Open the relevant article, then use the available editing or rewriting option to replace the broken image reference. You can choose Write it yourself or Rework existing article to revise the section and add a valid image. Before publishing, preview the article and confirm that each image loads correctly. Avoid using temporary URLs, local computer paths, or links to files stored behind a password. 🌐 Check Website Studio pages If the problem appears on a Website Studio page, go to Website Studio from the left sidebar and open the affected project. Review the image section and replace the source with a publicly accessible HTTPS image. Select Submit after making the change, then preview the page again. ✅ Verify the fix - Refresh the page in a private browser window. - Test the page on both desktop and mobile. - Confirm that the image URL still works when opened separately. - Check that the image has suitable dimensions and an appropriate file format such as PNG, JPEG, or WebP. - Publish or submit the updated page only after the preview displays correctly. 💡 Prevent future image issues - Use stable, publicly accessible HTTPS image URLs. - Keep original image files in a reliable media library. - Do not delete or rename source files after adding them to content. - Test generated pages before sharing or publishing them. - Use descriptive alternative text so the page remains understandable if an image cannot load. 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.

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

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

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

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

🛠️ Meta Generator Wrong Language Bug: What to Know

🔍 Overview Some users reported that the Meta Tags Generator inside Content Genius was producing metadata in the wrong language — for example, generating Dutch text for articles written in English — while still consuming quota. This was a confirmed bug in the platform, not a configuration error on the user's part. ⚙️ What Caused the Issue The root cause of this issue is a bug in the metadata generation process within Content Genius. The specific internal cause is still under investigation by our engineering team. If you experienced this issue, it was not caused by your account settings or article configuration. In some cases the generator also consumed quota during incorrect generation attempts, leaving users without usable results. ✅ Current Status Our team is aware of this bug and is actively working on a resolution. If you are currently experiencing this issue — metadata appearing in the wrong language or quota being consumed without a valid result — please contact our support team so we can log your case and assist you directly. 🚀 What You Can Do Right Now 1. Stop re-running generation on the affected article to avoid consuming additional quota while the bug is active. 2. Write your meta title and meta description manually as a temporary workaround: copy your article's main keyword and target language, then draft a short meta title (50–60 characters) and meta description (150–160 characters) by hand and paste them directly into your CMS or the article editor. This preserves your SEO metadata without using any quota. 3. Note the affected article name, the language you expected, and the incorrect language that appeared in the output so you have this ready if the issue persists. 4. Once the fix is confirmed resolved, return to the Meta Tags Generator and regenerate metadata for any articles where you received incorrect-language output. 💡 Tips While This Is Being Investigated - Avoid re-running metadata generation on affected articles until the issue is confirmed resolved, as repeated attempts may consume additional quota without producing correct results. - If you believe your quota was consumed without a valid metadata result being saved, contact support with your account details so the team can review your case and restore quota where appropriate. - Keep a record of any articles where you received incorrect-language output so you can regenerate accurate metadata once a fix is confirmed. If you need help, want to report an affected article, or need quota reviewed, please reach out to our support team — we're happy to help. You can start a conversation using the chat widget at the bottom of this page.

🏷️ Meta Generator Troubleshooting

This article covers: - Meta title generation - meta description generation - URL analysis failures - bulk generation workflows - CMS implementation guidance - project saving behavior - and Google re-crawling delays. The Meta Generator helps create: - SEO-friendly titles - meta descriptions - and search snippets based on: - your live page content - imported URLs - or manually provided content. Because generation depends on: - page accessibility - crawler visibility - AI summarization - and search engine behavior, issues are commonly caused by: - blocked pages - JavaScript rendering - incorrect content inputs - or Google cache delays. ⚠️ Error 1: Meta Generator is not producing results for my URL What's happening The Meta Generator first crawls your page content. If: - the page blocks crawlers - requires login - uses heavy JavaScript rendering - or returns an error, the tool cannot analyze the content properly. Steps to try 1. Confirm the URL loads publicly without login. 2. Open the URL in an incognito/private browser window. 3. Verify the page does not return: - 404 - 403 - 500 - or redirect loops. 4. If your site uses React, Vue, or Next.js rendering, use Manual Content instead of URL import. 5. Paste the visible page text manually into the generator. 6. Disable temporary bot protection if possible. 7. Confirm the page is not blocked by robots.txt. 8. Test another page from the same domain. 9. Retry generation after refreshing the tool. 10. Contact support if all public pages fail consistently. Important Notes - JavaScript-rendered sites are the most common cause of crawl failures. - Publicly accessible HTML pages generate the most reliable results. ⚠️ Error 2: Generated meta title is too long — over 60 characters What's happening AI-generated titles sometimes exceed Google's visible display limits. Google typically truncates: - titles longer than ~60 characters - or titles exceeding pixel width limits. Steps to try 1. Use the built-in character counter. 2. Watch for the red overflow warning. 3. Click Shorten Title if available. 4. Move your primary keyword toward the beginning. 5. Remove filler phrases or unnecessary branding. 6. Avoid duplicate modifiers: - best - top - ultimate - complete - etc. 7. Keep titles concise and readable. 8. Prioritize search clarity over creativity. 9. Compare against top-ranking SERP examples. 10. Re-generate titles using a shorter prompt. Important Notes - Google may still rewrite titles dynamically. - Shorter titles often improve mobile visibility. ⚠️ Error 3: Generated meta description is too short — under 120 characters What's happening Very short meta descriptions: - reduce click-through effectiveness - and may not communicate enough search relevance. Steps to try 1. Click Expand Description if available. 2. Aim for 150–160 characters. 3. Add: - value proposition - CTA - differentiators - and target keywords. 4. Include the primary benefit clearly. 5. Avoid vague generic descriptions. 6. Mention audience intent directly. 7. Add emotional or action-oriented language carefully. 8. Manually extend short outputs where needed. 9. Compare against competitor SERP snippets. 10. Re-run generation with stronger context. Important Notes - Google may rewrite descriptions dynamically. - Better descriptions improve CTR more than rankings directly. ⚠️ Error 4: Meta tags were generated but I cannot see where to apply them to my site What's happening Meta Generator creates: - optimized tag text but does not automatically publish changes unless integrated through: - OTTO - CMS Integration - or automation workflows. Steps to try 1. Copy the generated meta title. 2. Copy the generated meta description. 3. Apply tags manually inside your CMS. 4. WordPress users: - Yoast SEO - Rank Math - All in One SEO. 5. Shopify users: - Product/Page Editor → SEO Section. 6. Webflow users: - Page Settings → SEO Settings. 7. Confirm the tags save correctly. 8. Clear website cache after updating. 9. Use OTTO or CMS Connectors for automation workflows. 10. Verify the final page source after publishing. Important Notes - Meta Generator itself does not modify live pages automatically. - CMS implementation varies by platform. ⚠️ Error 5: Generating meta tags for many pages at once is slow What's happening Bulk generation processes: - URLs sequentially - through AI generation pipelines. Large batches create: - queue delays - longer processing times - and possible timeout risk. Steps to try 1. Leave the browser tab open during processing. 2. Process URLs in batches of 25 or fewer. 3. Avoid running multiple large jobs simultaneously. 4. Prioritize highest-value pages first. 5. Reduce unnecessary regeneration attempts. 6. Verify imported URLs are valid before processing. 7. Retry failed batches separately. 8. Use off-peak hours for very large batches. 9. Save completed results incrementally. 10. Refresh the page only after confirming progress completed. Important Notes - Large jobs naturally process slower. - Batch segmentation improves stability significantly. ⚠️ Error 6: Generated meta description contains information that is not on my page What's happening The AI may: - infer context - hallucinate details - or pull assumptions when: - source content is weak - vague - incomplete - or semantically ambiguous. Steps to try 1. Fact-check all generated descriptions. 2. Add accurate content manually into Manual Content. 3. Avoid vague page copy. 4. Include exact product/service details. 5. Re-run generation after improving source text. 6. Remove unsupported claims. 7. Verify pricing/statistics manually. 8. Compare against actual visible page content. 9. Use shorter, more focused prompts. 10. Never publish generated metadata without QA review. Important Notes - AI-generated metadata should always be reviewed manually. - Better source content produces more accurate SEO snippets. ⚠️ Error 7: Meta Generator results are not saving What's happening Generated metadata is tied to: - the currently selected project. Without an active project: - results cannot persist correctly. Steps to try 1. Confirm a project is selected before generation. 2. Use the top-right project selector. 3. Generate metadata again after selecting the project. 4. Click Save to Project manually. 5. Refresh the page after saving. 6. Check OTTO → On-Page → Meta Tags. 7. Avoid switching projects mid-generation. 8. Ensure you have edit permissions for the project. 9. Retry generation if saving silently fails. 10. Contact support if results disappear repeatedly. Important Notes - No active project = no persistent save behavior. - Project mismatches are a common workflow issue. ⚠️ Error 8: My website is showing old meta tags even after I updated them What's happening Google caches metadata from previous crawls. Even after updating your site: - search results may continue showing old snippets - until Google re-crawls the page. Steps to try 1. Confirm the live page source contains the updated tags. 2. Open the page source directly in your browser. 3. Use Google Search Console → URL Inspection. 4. Click Request Indexing. 5. Submit the URL through Authority Building → Indexer. 6. Clear CDN and site cache. 7. Confirm canonical tags are correct. 8. Avoid conflicting SEO plugins. 9. Wait 24–72 hours after re-crawl requests. 10. Monitor search snippet updates over several days. Important Notes - Google controls final SERP snippet rendering. - Updated tags do not appear instantly. Most Meta Generator issues are not caused by failed AI generation. They are usually related to: - inaccessible URLs - JavaScript-rendered pages - weak source content - CMS implementation gaps - bulk queue delays - or Google re-crawl timing. In many cases, the generator is functioning correctly — the workflow simply requires: - cleaner source content - better SEO structure - stronger implementation practices - or indexing patience. 👉 Strong meta optimization depends heavily on: - accessible crawlable pages - concise title structure - high-quality descriptions - correct CMS implementation - project organization - Google re-indexing workflows - and post-generation QA validation.

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