Troubleshooting: Page Editing & Templates

📦 Website Studio Bulk Export and Dynamic SEO URL Management

🛠️ Fix Photo Opacity Not Updating in Website Studio

🛠️ Fix AI Changes Not Saving in Website Studio

🖥️ Website Studio Page Editing Scope and Content Integrity

🚀 Migrate a Multilingual Vite Website

🧭 Overview There is no one-click migration for an entire multilingual Vite project into Website Studio. You can, however, migrate the website by importing its built pages or recreating them in Website Studio, then configuring each language version and its SEO settings. ⚙️ Prepare Your Vite Project 1. Make a backup of your Vite project and confirm that all pages build successfully. 2. Run your production build and identify the generated static files, usually in the dist folder. 3. List every route, including language-specific routes such as /en/, /es/, or localized paths. 4. Record page titles, meta descriptions, canonical URLs, hreflang relationships, images, fonts, and downloadable files. 5. Check whether any content depends on server-side code, APIs, authentication, or client-side routing. These features may need to be rebuilt or connected separately. 📥 Open Website Studio In Search Atlas, open Website Studio from the left sidebar, or go to /website-studio. Create or open the project where you want to rebuild the site. 🛠️ Move Your Pages Choose the approach that best fits your project: - Rebuild pages: Create each page in Website Studio and copy over the content, layout, images, and links. This is the most reliable option for projects that use dynamic React components or custom routing. - Import a built site: If your Vite build produces self-contained static HTML, CSS, JavaScript, and asset files, use the available import workflow and test the result carefully. Remove unsupported build-only elements and verify that the imported preview loads correctly. - Use an existing deployment as a reference: Keep the Vite site available while rebuilding pages in Website Studio. Compare each language version, then switch traffic only after testing the new site. Importing a project does not automatically recreate every Vite route, component, dependency, or project setting. Review the generated pages and replace unsupported functionality with Website Studio elements or supported integrations. 🌍 Configure Languages and URLs 1. Create a separate page for each language and keep the URL structure consistent. 2. Use clear language paths, such as /en/about and /fr/about, or the structure already used by your site. 3. Add links between equivalent language pages so visitors can switch languages without losing their location. 4. Set the correct language for each page and review navigation, buttons, forms, images, and alt text in every translation. 5. Make sure URLs use the correct slugs and do not create duplicate pages with different language content. 🔍 Preserve Multilingual SEO For every translated page, verify the title, meta description, canonical URL, and language alternates. Each language version should reference the equivalent versions, including a correctly configured default or fallback language when applicable. Also review XML sitemaps, robots directives, internal links, structured data, redirects, and any language selector links. Do not leave the old Vite URLs pointing to missing pages; create redirects when a URL changes. ✅ Test Before Launching - Open every language homepage and key page on desktop and mobile. - Test direct access to localized URLs, browser refreshes, navigation, forms, menus, and language switching. - Check that images, fonts, scripts, and downloads load from the correct paths. - Inspect page source or SEO settings to confirm canonical and hreflang values. - Test the site on a staging or preview URL before changing your primary domain. - Monitor indexing, redirects, and broken links after launch. 💬 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 Blog Dropdown Links in Website Studio

🔍 Overview After using Website Studio's AI to assign specific blog post URLs to navigation dropdown items, you may notice the links still redirect to the generic /blog/ listing page instead of the intended post. This happens even when the platform confirms the task was completed successfully. This is a known bug that has been resolved in a recent platform update. Follow the steps below to clear the issue and get your dropdown links working correctly. ⚙️ What Causes This Issue The bug occurred during the process of applying specific blog post URLs to dropdown navigation anchors inside Website Studio. The AI assistant would confirm the update, but the underlying link value was not being saved correctly — causing all dropdown items to fall back to the /blog/ listing page on click. This affected dropdown navigation items linked to individual blog posts (for example, a menu item labelled SEO to AI-Centric Optimization that should route to its dedicated post URL). ✅ How to Fix Your Dropdown Links 1. Open Website Studio from the left sidebar. 2. Navigate to the page containing your blog dropdown navigation element. 3. Click the dropdown navigation component to select it. 4. Manually review each dropdown item and confirm its link field contains the full, specific blog post URL (not /blog/). 5. If any item shows /blog/, clear the field and re-enter the correct post URL directly into the link input. 6. Click Submit to save your changes. 7. Preview the page and click each dropdown item to confirm it routes to the correct post. 💡 Tips to Prevent This Going Forward - Always verify links after AI-assisted updates. After asking the AI to apply URLs to navigation items, manually check each link field before publishing. - Use direct input for critical links. For blog post dropdown items, type or paste the specific post URL directly into the link field rather than relying solely on AI assignment. - Test before publishing. Use the preview mode in Website Studio to click through all navigation links and confirm destinations before making changes live. 🚀 Confirming the Fix Is Working Once you have re-entered the correct URLs and saved: - Each dropdown navigation item should route directly to its specific blog post page. - No items should redirect to the generic /blog/ listing page unless that is the intended destination. - The fix is persistent — republishing the site will not reset the links back to the previous incorrect behaviour. 🆘 Still Experiencing Issues? If your dropdown links continue to point to the wrong page after following the steps 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.

🔄 Transfer a Website Studio Project Between Accounts

🗂️ What Is a Website Studio Project Transfer? A Website Studio project transfer moves a project from one Search Atlas account to another. This is commonly needed when an agency builds a site on behalf of a client and the finished project must be handed over to the client's own Search Atlas account. 🛠️ How to Request a Project Transfer 1. Navigate to Website Studio and note the exact project name you want transferred. 2. Gather the relevant details for your request, including the project name and the source and destination accounts involved. 3. Contact our support team and describe your Website Studio project transfer request so a team member can assist you directly. 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.

🛠️ Restore Missing Solutions Page Links

🔍 What happened The Solutions dropdown may show Online Casinos, Sportsbooks, or Affiliate Sites as section anchors instead of links to their dedicated pages. An anchor such as #solutions-online-casino moves visitors to a section on the current page; it does not open /solutions/for-online-casinos/. 📄 Expected page links Each dropdown item should point to its corresponding page: - Online Casinos: /solutions/for-online-casinos/ - Sportsbooks: /solutions/for-sportsbooks/ - Affiliate Sites: /solutions/for-affiliate-sites/ ✅ Check the issue 1. Open the affected project in Website Studio. 2. Preview the website and open the Solutions dropdown. 3. Click each affected item and check the browser address bar. 4. Confirm whether the item opens the expected URL or only changes to an anchor beginning with #. 5. Check whether the three pages still appear in the project’s page list and whether their URLs return a valid page rather than a not-found response. 🛠️ Restore the correct links If the pages still exist, edit the Solutions navigation menu and replace each anchor target with the full relative page URL listed above. Save or publish the navigation changes, then test the links in a new private browser window. If a page is missing, unpublished, deleted, or has a different slug, restore or recreate the page using its intended URL before updating the menu. Avoid creating a duplicate page at a flat or alternate slug, because this can split internal links and create competing URLs. 🧪 Validate after publishing - Open all three URLs directly. - Confirm each page loads successfully and has the correct title and content. - Confirm the Solutions dropdown links to pages, not anchors. - Check that the pages are linked from the intended navigation and included in the sitemap when appropriate. - Clear any site or browser cache before retesting if the old anchor links remain visible. 💬 When to contact support If the pages cannot be restored, the navigation reverts to anchor links, or publishing creates duplicate or incorrect slugs, capture the project URL, affected page URLs, and a recording or screenshots of the behavior. 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 — Website Studio Issues

This article covers the page editor, custom domains, publishing, and AI generation. ⚠️ Error 1: "Generate with AI" never completes What's happening: AI page generation involves multiple sequential steps (structure, copy, SEO metadata) and can take several minutes. Steps to try: - Wait up to 5 minutes before concluding it failed. - Try generating one section at a time rather than the full page. - Simplify your brief — contradictory or unusually complex instructions increase failure rate. - Check AI generation credits: account menu (person icon, top-right) → Billing → Plans & Top-ups. If your AI generation credits are at 0 or exhausted, you will need to upgrade your plan or wait for your usage to reset — contact support or visit the billing page to review your options. - Contact support if generation consistently fails after multiple attempts. 🧠 Error 2: Atlas Brain in Website Studio stuck spinning / never completes analysis What's happening: This is distinct from a standard AI generation delay. Atlas Brain inside Website Studio can get stuck in an infinite spinning/loading state that persists across browsers and devices and is not resolved by clearing cache. In known cases it has lasted 4.5+ hours and required engineering intervention. Steps to try: - Confirm it is not a browser/cache issue by testing in incognito and on a different device. - If spinning persists beyond 30 minutes with no progress, this is a known backend issue requiring engineering escalation. - Contact support with a screen recording of the stuck state, the affected site, and timestamps. 🌐 Error 3: Custom domain stuck on "Pending SSL Certificate" What's happening: Either DNS hasn't propagated yet or the DNS configuration is incorrect. Note on propagation status: During the 1–48 hour propagation window, status indicators may show as pending or in-progress. Do not interpret intermediate states as errors requiring escalation — propagation can still be completing successfully even when the UI does not yet show a green/verified state. Steps to try: - Log into your domain registrar and confirm your CNAME record points exactly to the target shown in your Website Studio domain setup instructions. - Check propagation at dnschecker.org — search for your domain's CNAME. Green checkmarks globally means propagation is complete. - DNS propagation takes 1–48 hours — wait before troubleshooting further. - After DNS fully propagates, wait another 1–2 hours for SSL provisioning. - If DNS is fully propagated but SSL is still pending after 48 hours, click the gear icon or three-dot menu next to your site name in Left Sidebar → Website Studio, then open Project Settings → Domain Settings (Custom Domain) and use the Remove button next to the domain, then Re-add it to restart SSL provisioning. - Known backend issue: If a domain has been stuck in 'pending' for more than 48–72 hours with no error message displayed at all, this is a known backend issue where the domain can be silently stuck. In that case the Remove/Re-add workaround may not resolve it — contact support directly with your domain name so the team can investigate on the backend. 🔒 Error 4: Custom domain showing SSL/security warning on a previously working site What's happening: This is a distinct failure mode from initial SSL provisioning. If a site that was previously serving over HTTPS now shows a browser security warning (e.g., "Your connection is not private," NET::ERR_CERT_DATE_INVALID), this may indicate an expired Let's Encrypt certificate that did not auto-renew and requires manual renewal intervention on the backend. Steps to try: - Contact support immediately with your domain name and a screenshot of the browser warning. - Do not remove and re-add the domain in this case — that workaround is for initial provisioning, not for an expired certificate on a live verified domain. - Avoid sharing the affected URL with end users until the certificate is reissued, as browsers will block access by default. 🔄 Error 5: Published site still shows old content after hitting Publish What's happening: Your browser or a CDN edge node is serving a cached version. Steps to try: - Hard-refresh the live site: Ctrl + Shift + R / Cmd + Shift + R. - Clear your browser cache fully and reload the live URL. - Open the live URL in an incognito window to bypass your browser cache. - Test on a different device or network (e.g., mobile data) to rule out a local cache. - Allow up to 10–15 minutes for CDN cache propagation after publishing. - Test by adding ?v=2 to the URL — this bypasses the CDN cache for your browser. - Go back to Left Sidebar → Website Studio → Select Your Project → Publish Again, if the update still hasn't appeared after 15 minutes. 📦 Error 6: Website Studio fails to load or create a site — "Container not running" error What's happening: The Website Studio backend container that powers site creation, loading, and preview is not running. This blocks creating new sites, opening existing sites, and previewing pages. Steps to try: - Refresh the page and retry the action. - Wait 2–3 minutes and try again — the container may be restarting. - Clear your browser cache and reload Website Studio. - Try in an incognito window or a different browser. - If the error persists, contact support — this may require a backend container restart by engineering. 🖥️ Error 7: Page preview shows blank or doesn't load in the editor What's happening: The preview renderer encountered an error, usually with unsaved changes. Steps to try: - Save your current work, then refresh the editor page. - Toggle between Edit and Preview mode a few times to reset the preview renderer. - Try in a different browser — Safari sometimes has issues with iframe-based editors. - Disable browser extensions and reload. - Contact support with your browser type and any console error messages if preview consistently fails. 📩 Error 8: Form submissions aren't being received What's happening: Notification settings are misconfigured or emails are going to spam. Steps to try: - Check the submission log first: Left Sidebar → Website Studio → [Your Page] → Project Settings→ Forms → Form Submissions. - If submissions appear in the log but emails aren't arriving, check spam for form notification emails. - Verify the notification email address in form settings is correct. - Test by submitting the form yourself and confirming it appears in the log. - Contact support with your form ID if submissions appear in the log but notification emails aren't being sent. 🖼️ Error 9: Page thumbnail in the dashboard shows the old design What's happening: Thumbnail generation is a background task that runs after publishing — it's not instant. Steps to try: - Wait up to 30 minutes after publishing for the thumbnail to update. - Hard-refresh the Website Studio dashboard. - Your live site is correct even if the thumbnail shows an old version — this is cosmetic only. - Re-publish the page if the thumbnail still shows old content after 1 hour. - Contact support only if thumbnails show a blank white image — that indicates a generation service issue. ⚡ Error 10: My landing page loads slowly for visitors What's happening: Large uncompressed images or heavy scripts are slowing the page down. Steps to try: - Compress all images before uploading — uncompressed images are the most common cause. - Use WebP format instead of PNG or JPG. - Reduce the number of animations and auto-play video sections. - Contact support with your page URL and PSI score — our team can identify specific bottlenecks. 🤖 Error 11: AI-generated page content doesn't match my brand What's happening: Brand Vault isn't configured or isn't linked to the project. Steps to try: - Complete your Brand Vault in full: More Features → Brand Vault — fill in Business Info, Brand Voice, and Target Audience. - Link Brand Vault to your project: OTTO SEO in the left sidebar → All Sites → open your project → Brand Vault. - After updating Brand Vault, wait 15 minutes before generating new content. - In your generation request, specify: "Write in [tone] for [audience], consistent with my brand voice." - Edit AI-generated copy as a starting point — treat it as a first draft. 🔧 Error 12: OTTO changes not applying on Website Studio sites What's happening: OTTO on-page deployments (such as meta descriptions and title tag changes) may not be compatible with Website Studio static sites managed through Search Atlas. This is a known limitation currently under engineering review. Steps to try: - Verify the change directly inside Website Studio's page editor (Meta / SEO settings) rather than relying on the OTTO deployment alone. - Contact support to confirm whether your site is affected by the known OTTO ↔ Website Studio integration limitation. - In the meantime, apply meta and title tag updates manually in Website Studio and re-publish the page. Most Website Studio issues are not system failures—they are typically related to DNS propagation, caching layers, AI processing time, or configuration gaps. Website publishing and rendering involve multiple systems (browser, CDN, DNS, SSL), which may introduce short delays or inconsistencies.

🔗 How It Works: Import Project (Website Builder)

📦 What Import Project does Import Project lets you start a brand-new Website Builder project from an HTML site you already have — whether you hand-coded it or built it in another tool like Lovable or Flood. Once imported, your site becomes a fully editable Website Builder project, so you can host it, connect a custom domain, add tracking and forms, and publish it live — without rebuilding from scratch. 📍 Where to find it From the left sidebar, open Website Studio (Website Builder). On the home screen — before you open any project — there is a row of quick-action chips at the top. Import Project is the fourth chip, marked with an upload-arrow icon, alongside Generate PPC Site and Import Site. 📂 What you can import - A single .html file, or a .zip bundle containing your HTML plus its assets (images, CSS, JS, fonts). - Files up to 50 MB. - Static HTML only — React, Vue, and other framework build outputs are not supported. 🛠️ How to import a project 1. Open Website Studio (Website Builder) from the left sidebar. 2. On the Home (Agent Hub) screen, use the Create Project action. 3. In the Import window, drag and drop your .html or .zip file into the upload area, or click to browse. 4. In Website Studio (What will we get done today?), click Import Site. Website Builder processes your files and builds the new project. 5. When it is ready, you are taken straight into the project editor. 🚀 What you can do after importing Your imported site opens as a standard Website Builder project. From there you can connect a custom domain, add tracking scripts (such as Google Analytics or Meta Pixel), add and manage forms, edit your content, and publish the site live. 💡 Good to know - Import Project always creates a new project — it never changes your existing projects. - If a file cannot be imported, you will see a clear message — for example, an unsupported file type, a file over 50 MB, or a ZIP missing referenced assets. Fix the issue and try again. - For best results, make sure your ZIP includes every asset your HTML references.

🛠️ Fix Blank Pages and Sync Errors in Website Studio

🔍 Overview When syncing a Website Studio project to WordPress, you may encounter blank pages, missing assets (404 errors), or your WordPress homepage being unexpectedly replaced. This article explains what to expect and how our team can help resolve these issues. ⚠️ Common Symptoms - A synced page appears completely blank on your live WordPress site. - Images, stylesheets, or scripts fail to load (404 errors in the browser console). - Your existing WordPress homepage is replaced after a sync that includes a home page (the synced project's home page is always set as the WordPress static front page; you can restore the previous homepage in WordPress → Settings → Reading). - A blog post or landing page synced from Content Genius shows a Synced status in Search Atlas but the live page is blank or returns an error. - Your blog page is only reachable from the homepage quick-link — visiting its direct URL redirects back to the homepage. 💡 Why This Happens Blank pages, 404 errors, and homepage replacement issues during Website Studio WordPress sync can arise from conflicts between the Search Atlas sync process and your WordPress environment. Because these issues depend on the specific configuration of your WordPress site and integration, the exact root cause varies by case and requires investigation by our support team. 🛠️ What to Do Since these are backend sync issues that depend on your specific WordPress setup and integration state, our team will need to look into your account directly to identify the cause and apply the correct fix. To help us resolve this as quickly as possible, please have the following information ready when you reach out: - Your Search Atlas project name and the URL of the affected WordPress site. - The exact page(s) showing blank content or 404 errors (page title and live URL). - A description of the exact symptoms — for example, whether the page is blank, returning a 404, or redirecting unexpectedly. - Any error messages you see, including errors shown in your browser console if applicable. - The approximate date and time when the issue first occurred or when you last performed a sync. 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.

🔧 Resolving Website Studio Import and MCP Connection Errors

🎯 Overview Website Studio occasionally encounters import resolution errors, particularly with the ErrorBoundary component, and MCP (Model Context Protocol) connection issues that can block your project from loading. This guide walks you through diagnosing and resolving these problems quickly. 🔍 What Causes These Errors? Import resolution errors typically occur when Website Studio cannot locate or properly load component dependencies. MCP connection issues arise when the platform loses communication with the backend services that power your project's functionality. Both can prevent your editor from loading or cause projects to break unexpectedly. ⚙️ How to Fix Import Resolution Errors Step 1: Clear Your Browser Cache Start by clearing your browser's cache and cookies for Search Atlas. This resolves many import errors caused by outdated cached files: - Open your browser settings - Navigate to Cache and Cookies - Clear data for the Search Atlas domain - Close and reopen Website Studio Step 2: Force a Hard Refresh After clearing cache, perform a hard refresh of the Website Studio page: - Windows/Linux: Press Ctrl + Shift + R - Mac: Press Cmd + Shift + R This ensures Website Studio loads the latest component files and dependencies from the server. Step 3: Check Your Project State Navigate to Website Studio from the left sidebar and open your project. If the ErrorBoundary error persists, try these actions: - Wait 30 seconds for the project to fully load - Refresh the page again if the error appears immediately - Check that your project was saved successfully in your last session 🌐 Resolving MCP Connection Issues Step 1: Verify Your Internet Connection MCP errors often stem from connectivity problems. Ensure your internet connection is stable and not being blocked by a firewall or VPN. Step 2: Check Service Status MCP connection failures can occur if backend services are temporarily unavailable. Wait a few minutes and try reconnecting. If the issue persists beyond 15 minutes, contact support. Step 3: Reconnect MCP If Website Studio shows an MCP connection error: - Close the Website Studio editor tab - Return to the main Search Atlas dashboard - Re-open Website Studio from the left sidebar - Allow 30-45 seconds for the MCP connection to re-establish Step 4: Check for Authentication Issues MCP connection errors can also indicate an authentication problem. If reconnecting doesn't work: - Log out of Search Atlas completely - Clear your browser cache again - Log back in and return to Website Studio 🚀 Preventing Future Errors To minimize import and MCP issues, follow these best practices: - Save regularly: Save your projects frequently to avoid losing work during unexpected errors - Monitor your connection: Keep your internet connection stable while working in Website Studio - Update your browser: Use the latest version of your browser for compatibility - Avoid multiple tabs: Don't open the same project in multiple browser tabs simultaneously - Check browser extensions: Some extensions can interfere with Website Studio; disable them if errors occur 💡 If These Steps Don't Work If you've followed all the steps above and your import or MCP error persists, the issue may require deeper 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. When you contact support, include: - The exact error message you're seeing - Your project name - Steps you've already tried - Your browser type and version - Whether the error occurs for all projects or just one 📋 Quick Reference Checklist Use this checklist to resolve issues quickly: 1. Clear browser cache and cookies 2. Perform a hard refresh (Ctrl+Shift+R or Cmd+Shift+R) 3. Wait 30 seconds for Website Studio to load 4. Check your internet connection 5. Close and reopen Website Studio 6. Log out and log back in 7. Contact support if errors persist

🌐 Migrate Website Studio to Wix and Fix UX Score

Overview This article covers three connected topics that often come up together: migrating your Website Studio project to Wix for hosting, understanding why your UX score may remain low after a rebrand, and syncing your updated sitemap in Google Search Console (GSC) so your changes are indexed promptly. Step 1 — Migrating Your Website Studio Project to Wix Website Studio is Search Atlas's built-in site builder. To host your site on Wix instead, follow these steps: 1. In Search Atlas, open your Website Studio project and export or copy the content (pages, copy, images) you want to move. Download any media assets to your local machine. 2. Log in to your Wix account and create a new site. Use the Wix editor to rebuild your pages, or use Wix's import tools if your content is in a supported format. 3. Once your Wix site is live on its final domain, return to Search Atlas and update your project's tracked URL to reflect the new Wix domain. Go to your project settings and replace the old root URL with your new Wix domain so future audits and rank tracking point to the correct site. 4. Re-run a full site audit in Search Atlas against the new domain to establish a fresh baseline for your UX score and on-page health. Step 2 — Why Your UX Score May Stay Low After Rebranding Rebranding — such as changing your logo, color scheme, or domain name — does not automatically improve your UX score. The UX score in Search Atlas is calculated from measurable technical and on-page signals, not visual identity. Common reasons the score stays low after a rebrand include: - On-page issues unresolved: Missing meta titles, broken internal links, duplicate content, or unoptimized images may remain on your migrated pages. - New pages not yet audited: Search Atlas may not have crawled the new hosted version of your site yet. - GSC data lag: Google may not have re-crawled and re-indexed your pages since the migration, so performance signals may be outdated. To address these issues, go to Content → Onpage Audit in Search Atlas, select your project, and click Run Audit. Review the list of flagged issues and work through them in priority order — start with missing meta titles, then broken links, then image optimization. Each issue card in the audit shows the affected URL and a recommended fix you can apply directly in your Wix editor or via your site's HTML/meta settings. Step 3 — Syncing Your GSC Sitemap After Migration After your site is live on its new hosting, submit your updated sitemap in Google Search Console to prompt Google to re-crawl and re-index your pages. Follow these steps: 1. Find your sitemap URL. For most Wix sites, the sitemap is automatically generated at https://yourdomain.com/sitemap.xml. Confirm this by visiting that URL in your browser — you should see an XML list of your pages. 2. Log in to Google Search Console (search.google.com/search-console) and select the property that matches your domain. 3. In the left-hand menu, click Sitemaps under the Index section. 4. In the "Add a new sitemap" field, enter your sitemap URL (e.g., sitemap.xml) and click Submit. 5. GSC will show the sitemap status. A "Success" status means Google has accepted it for crawling. Allow 24–72 hours for Google to begin re-crawling your pages. 6. After Google re-crawls your site, return to Search Atlas and refresh your project's GSC data connection so the latest performance signals are reflected in your UX score and reports. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Content Genius and On-Page Audit Issues

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

🖥️ Fix Website Studio Visual Editor Page and Save Issues

🗺️ Overview The Website Studio visual editor is a powerful tool for making on-page changes to your site directly inside Search Atlas. Two common workflow issues can disrupt your editing session: the editor opening or navigating to the wrong page, and edits not saving or applying after you make them. Both issues are almost always caused by a fixable step in the workflow — no technical fault required. This article walks you through the correct process and the most effective fixes. 📄 How to Load the Correct Page in the Visual Editor Before editing any page, you must explicitly select and load your target URL inside the editor. The editor does not automatically detect or lock onto the page you intend to edit based on your project settings alone. 1. In the left sidebar, click Website Studio (URL: /website-studio). 2. Once the editor interface loads, locate the page URL bar at the top of the visual editor preview panel. 3. Clear any existing URL and type or paste the exact URL of the page you want to edit — for example, https://yourdomain.com/certified-triple-wide. 4. Press Enter or click the Load button to fetch and render that specific page inside the editor. 5. Wait for the page to fully render before making any changes. Interacting with the editor while the page is still loading can cause elements to be missed or changes to be applied to the wrong DOM state. Important: If you skip step 3 and simply open the editor, it will load whichever page was last active in your session — which may be a completely different page, such as a product or category page you visited previously (for example, Metal Carports instead of Certified Triple Wide). Always confirm the URL in the bar matches your intended target before editing. ❓ Why Does the Editor Open the Wrong Page? The visual editor remembers the last page that was loaded during your previous session. If you navigated to a different page — either by browsing within the editor preview or by previously editing another page — the editor will restore that page the next time you open Website Studio. Common reasons the wrong page appears include: - A previous session ended on a different page and the editor state was cached. - You clicked an internal link inside the editor preview, which navigated the preview frame away from your target page. - The editor was opened from a different starting context within your project. - Browser cache preserved a stale editor state from an earlier visit. The fix in every case is the same: manually enter your target URL in the editor's URL bar and reload the page before making changes. 💾 Why Are My Changes Not Saving or Applying? If you make edits in the visual editor but they do not appear on your live site or disappear after refreshing, work through the following checks in order. 1. Confirm you clicked Save before leaving the editor. Changes made in the visual editor are not auto-saved. You must click the Save or Publish button in the editor toolbar before navigating away or closing the tab. If you switch pages inside the editor preview without saving first, unsaved changes are discarded. 2. Verify you were editing the correct page. If the editor was showing the wrong page (see above), your edits were saved to that page — not the one you intended. Reload your intended page, re-apply your changes, and save again. 3. Clear your browser cache and cookies. A stale cache can cause the editor to display an outdated version of a page or prevent saved changes from appearing in the preview. Clear your cache and cookies, then reload the editor. 4. Test in an Incognito or Private window. Open an incognito window and navigate to Website Studio (/website-studio). This bypasses cached data and extensions that may interfere with the editor's save functionality. If changes appear correctly in incognito, a cache or extension issue is confirmed on your main browser profile. 5. Try a different browser. If the incognito test also fails, open a supported browser (Chrome or Firefox recommended) and repeat the process to rule out browser-specific conflicts. 6. Check for unsaved indicator. The editor toolbar typically displays an unsaved changes indicator (such as a dot or asterisk on the Save button) when edits are pending. If this indicator is not visible, the editor may not have registered your edits — re-enter the changes and save again. ✅ Recommended Workflow for Reliable Editing Follow this order every time you use the visual editor to avoid both issues described above: 1. Open Website Studio from the left sidebar. 2. Enter your exact target page URL in the editor URL bar and press Enter. 3. Wait for the page to fully render in the preview panel. 4. Make your edits. 5. Click Save before doing anything else — including clicking links inside the preview or navigating away. 6. After saving, verify the changes by loading the page in a new incognito tab to see the published result without cache interference. 🛠️ Quick Troubleshooting Checklist - Wrong page is showing → Re-enter the correct URL in the editor URL bar and reload. - Changes not appearing after save → Clear cache and cookies, then check in incognito. - Edits disappear when switching pages → You navigated away without saving; re-apply and save before switching. - Editor feels frozen or unresponsive → Hard-refresh the page (Ctrl + Shift + R on Windows, Cmd + Shift + R on Mac) and reload your target URL. - Problem persists across browsers → Contact support via the chat widget (see 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.

✏️ Rename Website Studio Pages Safely Without Duplicates

🗺️ Overview Renaming a page in Website Studio — for example, changing Blog to Articles — is straightforward, but doing it incorrectly can cause the AI agent to create a duplicate page, break internal links, or produce 404 errors. This article explains the correct approach so your site stays clean and error-free. ⚠️ Why Duplicate Pages or 404 Errors Happen Website Studio's AI agent monitors your site structure. If you ask the AI to rename a page rather than using the manual rename controls in the builder, it may interpret your request as an instruction to create a new page while leaving the original in place. This produces two pages with similar content and can orphan any links that pointed to the old page. Always rename pages using the manual controls inside the builder — not through the AI chat. 🛠️ How to Rename a Page in Website Studio 1. Open Website Studio and navigate to your page list inside the builder. 2. Locate the page you want to rename (for example, Blog). 3. Use the rename option available for that page in the builder's page management controls to give it a new display name (for example, Articles) and confirm the change. 4. If the builder offers to update the page's URL or apply a redirect from the old address to the new one, accept those options to prevent 404 errors for visitors and search engines. 5. Save and publish your changes using the appropriate controls in the builder. 🔗 Updating Internal Links After a Name or URL Change If your page's URL changed as part of the rename, any internal links on your site that pointed to the old URL will need to be updated to the new one. Review your other pages for links referencing the old address and update them accordingly. Keeping a redirect from the old URL to the new one active will ensure external links and bookmarks continue to work in the meantime. 🤖 What to Avoid When Using the AI Agent The AI agent is designed to build and edit content, not to handle structural renames. To avoid unintended duplicates: - Do not type instructions like "rename my Blog page to Articles" into the AI chat. This can trigger page creation instead of a rename. - Do not delete the original page before confirming the renamed page is fully set up — deleting without a redirect in place will cause 404 errors immediately. - If the AI does create a duplicate page by mistake, delete the unwanted duplicate through the page list before publishing, then verify no broken links remain. 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 Website Studio Landing Page Generation Failures

🔍 Overview If Website Studio repeatedly shows a Generation Failed error when trying to create a landing page — even after retrying or starting a new project — you may be experiencing a generation issue that requires escalation to our support team. This article explains what to expect and how to prepare for a fast resolution. ⚠️ What Is a Landing Page Generation Failure? When you attempt to generate a landing page in Website Studio, the process may fail and display a Generation Failed error. This error can persist even if you retry or create a new project. Generation failures are typically backend issues that cannot be fully resolved through browser-side troubleshooting alone. 🚀 What You Can Try First 1. Wait before retrying. If you see a Generation Failed message, wait a short while before attempting again. Back-to-back retry attempts in rapid succession may compound the problem. 2. Refresh the page. A standard page refresh can sometimes clear a transient error state before retrying generation. 3. Clear your browser cache and cookies. Stale session data can occasionally interfere with requests. Clear your cache, log back in to Search Atlas, and try again. 4. Try a different browser. If the issue persists, open Website Studio in a different browser to rule out a browser-specific conflict. 5. Start a fresh project. Rather than retrying inside the failed project, create a brand-new landing page project in Website Studio and attempt generation from scratch. 6. Check your internet connection. An unstable connection during generation can interrupt the process. Switch to a more reliable network if possible, then retry. 📋 When to Escalate If none of the steps above resolve the Generation Failed error, this is a backend issue that our support team will need to investigate directly. To help us resolve it as quickly as possible, please have the following ready when you contact us: - The exact error message displayed (a screenshot is ideal) - The name of the project(s) where the failure occurred - The date and approximate time when you first encountered the error - The browser and operating system you are using - A description of how many times you have retried and whether a new project also fails 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.

🔄 Migrate WordPress Sites to Website Studio Safely

Overview When you migrate a site from WordPress to Website Studio, the original OTTO SEO project may still be tied to the old WordPress domain and data. This mismatch can cause broken internal links, failed syncs, and other issues related to OTTO project and data cleanup. This article explains what to expect and how to get the right help. Why This Happens Each OTTO SEO project is linked to a specific domain and its associated crawl data and settings. When you move from WordPress to Website Studio, the old project's references may no longer match the new site structure, leading to errors such as UUID lookup failures or broken connections. Resolving these issues typically requires backend intervention by the Search Atlas support team. What to Have Ready Before Contacting Support Because OTTO project cleanup and data migration issues require backend action, our team will need the following information to investigate and resolve your case: - Your project name(s) — both the old WordPress project and the new Website Studio project, if applicable. - The exact error message(s) you are seeing, copied in full. - The timestamp of when the error first appeared. - The domain(s) involved — the old WordPress URL and the new Website Studio URL. - A description of what actions you took before the error appeared (for example, whether you deleted an OTTO project or changed domain settings). What to Expect Once you contact support with the above details, our team will review your OTTO project data and site configuration on the backend. We will guide you through the correct cleanup sequence or perform the necessary data corrections on your behalf. Do not delete additional projects or make further changes to your OTTO settings while waiting for a response, as this can complicate recovery. 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 Website Studio Text and Photo Editing Errors

What Is This Error? When editing text or photos in Website Studio, you may encounter an error that prevents the AI editor from applying your requested changes. No changes are made to your site when this error occurs. Why This Happens This is a known issue affecting text and photo editing in Website Studio. The underlying cause is still being investigated by our team. What to Do Because this is a bug, there is no self-serve workaround at this time. To get this resolved, please reach out to our support team and have the following information ready: - The name of the project or website where the error occurred - The exact error message you received (a screenshot is helpful) - The type of edit you were attempting (text or photo) - The page and section you were trying to edit - The timestamp or approximate time the error occurred If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Website Studio Visual Editor Save Failures

Overview When making multiple edits in Website Studio's visual editor, some customers find that clicking Save appears to work — but the changes disappear. Single edits save correctly, while batches of edits do not. This is a known bug that requires investigation by our engineering team. What to Expect Because this is a backend issue, there are no self-serve steps that reliably resolve it. Our team will need to look into your specific account and project to identify what is causing the saves to fail. Once a fix is applied on the backend, your edits should save as expected. How to Escalate This Issue To help our team investigate and resolve this as quickly as possible, please have the following information ready before reaching out: - Your project name (the specific Website Studio project where the save failure is occurring) - A description of the edits you were making when the failure occurred (e.g., text edits, image changes, layout adjustments) - Whether the issue happens consistently or only in certain situations - The browser you are using (name and version) - Any error messages displayed at the time of the failure, including the exact wording - The approximate date and time when 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.

🎵 Search Atlas Is an SEO Tool, Not a Music Studio

🔍 What Is Search Atlas? Search Atlas is an SEO and digital marketing platform. We help businesses and content creators grow their online presence through tools like keyword research, content optimization, site audits, backlink analysis, and AI-powered content creation. We are not a music production service, recording studio, or entertainment platform. Unfortunately, we are unable to create, produce, or host music demos of any kind. 🎤 Why We Can't Help With Music Demos We completely understand the passion behind wanting to share your music — but Search Atlas is purpose-built for SEO and online marketing. Our tools and team are focused entirely on helping you rank higher in search engines and grow website traffic. Music demo production falls entirely outside what our platform offers. - We do not have audio recording or production tools. - Our AI features are designed for written content, keywords, and SEO tasks only. - Our support team specializes in SEO and platform guidance, not music or entertainment. 🚀 Where to Get Help With Your Music If you are an artist looking to create a demo, here are some types of services that can genuinely help you: - Local recording studios — Search for studios in your area that offer demo recording packages for independent artists. - Online music production platforms — Services like SoundBetter, Fiverr Music, or Airgigs connect artists with professional producers and engineers. - Home recording resources — Free tools like Audacity or GarageBand can help you record a basic demo from home. - Music distribution platforms — Once your demo is ready, platforms like DistroKid or TuneCore can help you share it online. 💡 How Search Atlas Can Still Help You as an Artist If you are a musician who also wants to grow your presence online, Search Atlas actually has a lot to offer. Many independent artists use SEO tools to build their brand and reach more fans. Here is how our platform can support your digital growth: - Keyword Research — Discover what your potential fans are searching for and create content around those topics. - Content Genius — Write optimized blog posts, artist bios, or press releases that rank in search engines. - Site Auditor — Make sure your artist website is technically sound and easy for search engines to find. - Local SEO Tools — If you perform locally, optimize your visibility for fans searching in your area. ⚙️ What Happens When You Send Off-Topic Requests Our AI tools are trained specifically for SEO tasks. If you send a request that is unrelated to SEO or content marketing — such as asking for a music demo — the system will politely let you know it cannot help with that request and will redirect you to the right resources. This is by design, so you always get the most relevant and accurate assistance possible. 🛠️ Still Have Questions About the Platform? If you have questions about what Search Atlas can do, how to use a specific feature, or anything else related to your account, our 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 Website Studio Blank Pages and Content Flashing

🔍 Overview Some customers notice two related issues when building or editing pages in Website Studio: blank pages automatically appearing in the footer menu and page content briefly flashing before displaying as blank on refresh. These issues can feel alarming, especially before publishing, but they are typically caused by a known rendering and page-generation behaviour in the builder. This article explains what causes these issues and how to resolve them. ⚙️ What Causes These Issues Both symptoms usually share a common root cause: - Auto-generated placeholder pages: When Website Studio creates or scaffolds blog sections, it may automatically add placeholder pages to your navigation menus, including the footer, even if those pages have no content yet. - Content rendering delay: The builder occasionally renders page content in a brief flash before the final layout is applied. On refresh, if the cache or build state is out of sync, the page may display as blank until the content is fully re-rendered. - Unsaved or uncommitted draft state: Content that has been added but not properly saved can appear missing after a browser refresh. 🛠️ How to Fix Blank Pages in the Footer Menu 1. Open Website Studio from the left sidebar or navigate to /website-studio. 2. Open your active project and go to the Navigation or Menu settings, then select the Footer Menu. 3. Review the list of pages linked in the footer. Identify any pages with no title, no content, or labelled as a placeholder. 4. Click on each blank page entry and select Remove from Menu or Delete Page, depending on whether you want to unlink it or remove it entirely. 5. If the blank page was auto-generated as part of a blog setup, verify that your blog template is fully configured before re-adding it to the menu. 6. Save your menu changes and preview the footer to confirm the blank entries are gone. 💡 How to Fix Content Flashing and Blank Page on Refresh 1. Inside your project in Website Studio, navigate to the affected page. 2. Check that all content blocks on the page are fully saved. Look for any unsaved indicator (such as a pending save prompt or highlighted block) and confirm the save. 3. Once the page appears correct in the editor, click Save or Publish at the top of the builder to commit the current state. 4. After saving, perform a hard refresh in your browser (Ctrl + Shift + R on Windows or Cmd + Shift + R on Mac) to clear any cached version of the page. 5. If the content still flashes or appears blank, try clearing your browser cache entirely, then revisit the page in the editor. 6. If you are using a custom domain, allow a few minutes for any CDN or caching layer to clear before testing the published version again. ✅ Before You Publish: A Quick Checklist To feel confident before publishing your site, run through these checks: - All pages in your menu (header and footer) have visible, saved content. - No placeholder or auto-generated blank pages remain in any navigation menu. - You have previewed each page in the builder and confirmed content loads correctly. - You have performed a hard refresh after your final save to verify the page renders as expected. - If blog pages are included, each post or blog index page has at least a title and a content block. 🚀 Still Seeing the Issue? If blank pages or content flashing persist after following the steps above, there may be a project-level configuration 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.

🗑️ Delete Individual Pages in Website Studio

🧭 Overview In Website Studio, you can remove an individual page from your project without affecting the rest of your site. This is done by sending a prompt directly to the builder — it is a separate action from deleting an entire project. This article walks you through exactly how to do it. 🔍 Before You Begin Keep the following in mind before removing a page: - Deleting a page is permanent. Once the builder removes the page, it cannot be recovered. - This action only removes the selected page. All other pages and content in your project remain untouched. - Deleting a project is different. If you want to remove the entire project, that is a separate action not covered in this article. 📍 How to Navigate to Website Studio 1. Log in to your Search Atlas account. 2. In the left sidebar, click Website Studio. 3. Open the project that contains the page you want to delete. ✏️ How to Delete an Individual Page Website Studio uses an AI-powered builder that responds to plain-language prompts. To delete a specific page, you need to instruct the builder directly. Follow these steps: 1. Open your project in Website Studio. 2. Locate the chat or prompt input field inside the builder interface. 3. Type a clear instruction specifying the page you want to remove. Use the format below as a guide: Example prompt:"Delete the [page name] page from this project." Replace [page name] with the exact name of the page you want to remove — for example, "Delete the Contact page from this project." 1. Submit the prompt and wait for the builder to confirm the action. 2. Review the updated page list in your project to confirm the page has been removed. 💡 Tips for a Successful Prompt - Be specific with the page name. The more precise your prompt, the more accurately the builder will identify and remove the correct page. - Check the page name first. Before submitting your prompt, confirm the exact page name as it appears in your project to avoid accidentally targeting the wrong page. - One page at a time. If you need to delete multiple pages, submit a separate prompt for each one to ensure accuracy. ⚠️ Common Mistakes to Avoid - Do not ask the builder to "delete the project" when you only want to remove one page. This will remove your entire project, not just a single page. - Do not confuse hiding a page with deleting it. If you want to keep the page but make it invisible to visitors, ask the builder to hide or unpublish the page instead. 🙋 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🎨 Fix Blog Article Styling Mismatches in Website Studio

🔍 Overview If your individual blog article pages look different from your main blog page or the rest of your website, you are not alone. This is a known formatting mismatch that can occur in Website Studio. This article explains what to expect and how to get help resolving it. 💡 Why This Happens Styling inconsistencies between blog article pages and the main blog listing page are a recognized issue in Website Studio. Common symptoms include: - Blog article pages displaying different fonts or font sizes than the rest of the site - Colors or button styles that do not match the main blog or homepage - Spacing and layout inconsistencies between the blog listing page and individual posts - Header or footer styling appearing differently on article pages 🛠️ What to Do Because this is a bug-category issue, the resolution requires investigation by our support team. To help us look into your specific case as quickly as possible, please have the following information ready before reaching out: - The name of your website project in Website Studio - The URL or page name of the affected blog article page(s) - A description of exactly what looks different (e.g. font, color, spacing, header/footer) - Any recent changes you made to your site before the mismatch appeared - Screenshots comparing the affected article page with the main blog 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.

🚀 Migrate WordPress to Lovable with Search Atlas

🔍 Overview Moving your website from WordPress to Lovable is a multi-step process. The good news is that you can fully configure Search Atlas on your new Lovable site before you point your domain to it. This means zero downtime for your SEO tracking and no scrambling to set things up after the switch. This article walks you through exactly how to do that. 📋 What You Will Need Before You Start - An active Search Atlas account - Your existing WordPress site currently live and tracked in Search Atlas - A published Lovable project (the site must be published to generate a UUID) - Access to your domain registrar or DNS settings 🛠️ Step 1: Publish Your Lovable Site and Get the UUID Search Atlas identifies your Lovable site using a UUID — a unique identifier that Lovable assigns to each published project. You cannot retrieve the UUID from an unpublished project, so make sure your Lovable site is published first. 1. Log in to your Lovable account and open your project. 2. Click Publish if you have not already done so. Lovable will generate a preview URL in the format your-project-name.lovable.app. 3. To find the UUID, look at the Lovable project URL in your browser while inside the editor. The UUID is the alphanumeric string in the URL, for example: lovable.dev/projects/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx. Copy this value. If you are unsure where to find the UUID, open your Lovable project settings — it is typically displayed under project details or in the share/publish panel. ⚙️ Step 2: Add Your Lovable Site to Search Atlas With your UUID ready, you can now add the Lovable site to Search Atlas using its preview URL. This lets you start configuring everything before your real domain is pointed over. 1. In Search Atlas, go to Left sidebar → Site Metrics (Site Explorer). 2. Click Add New Site (or the + icon at the top of your site list). 3. Enter your Lovable preview URL (e.g., your-project-name.lovable.app) as the site URL. 4. Complete the site setup and save. Once the site is added, Search Atlas will begin pulling data for that URL. You can set up rank tracking, run keyword research, and configure all settings against the preview URL right away. 📊 Step 3: Configure Search Atlas Settings on the Lovable Site Before switching your domain, get your Search Atlas setup fully in place: - Rank Tracker: Go to Left sidebar → Keywords → Rank Tracker and add the keywords you want to monitor for the new site. - Keyword Magic: Use Left sidebar → Keywords → Keyword Magic to research and map keywords to the new Lovable pages. - Keyword Gap: Run a competitor gap analysis via Left sidebar → Keywords → Keyword Gap to identify opportunities ahead of launch. 🔄 Step 4: Point Your Domain to Lovable When your Lovable site is ready to go live, update your DNS settings at your domain registrar to point your custom domain to Lovable. Refer to Lovable's official documentation for the exact DNS records required, as these may vary. After DNS propagation is complete (usually 24–48 hours), update the site URL in Search Atlas to reflect your custom domain: 1. Go to Left sidebar → Site Metrics (Site Explorer) and select the Lovable site you added. 2. Navigate to the site settings and update the URL from the .lovable.app preview URL to your custom domain (e.g., www.yourdomain.com). 3. Save your changes. Search Atlas will now track rankings and metrics against your live domain. ⚠️ Important Notes - Rank tracking history is tied to the URL you entered. Updating the URL to your custom domain starts fresh tracking on that domain — plan accordingly if historical data matters to you. - If you were previously tracking your WordPress site in Search Atlas under the same domain, you do not need to delete that property until you are confident the Lovable migration is complete and stable. - Make sure your Lovable site has a connected custom domain before updating the URL in Search Atlas, otherwise tracking will not work correctly. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 Fix WordPress Content Genius Sync & Duplicate Pages

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

🛠️ Fix Website Studio Generation Failed Build Error

🔍 What Is This Error? A Generation Failed error in Website Studio means the platform was unable to complete the build process for a page. This can happen when creating new pages such as Thank You pages, landing pages, or other custom page types. In some cases, the error persists even after retrying. ⚙️ Initial Steps to Try Before escalating, try the following general steps: 1. Hard-refresh your browser. Press Ctrl + Shift + R (Windows/Linux) or Cmd + Shift + R (Mac) to clear cached assets and reload the page fresh. 2. Clear browser cache and cookies. Cached data can interfere with Studio build requests. Clear your browser cache, then reload the platform. 3. Try a different browser. Switch to a modern browser such as Google Chrome or Mozilla Firefox. 4. Check your internet connection. A dropped or unstable connection mid-generation can cause a build to fail. Switch networks or disable a VPN if one is active. 5. Wait and retry after a few minutes. Temporary backend issues can cause isolated generation failures. Wait a short period and attempt the build again. 🚀 When to Escalate If the Generation Failed error persists after trying the steps above across different browsers and sessions, this is likely a backend issue that requires investigation by our support team. When reaching out, please have the following ready: - The name of the affected project in Website Studio - The exact error message displayed (screenshot if possible) - The type of page you were attempting to generate (e.g. Thank You page, landing page) - The timestamp of when the error first occurred and how many times you have retried 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 Your Website Studio Coming Soon Page

🔍 Overview If your Coming Soon page in Website Studio isn't behaving as expected — such as the editor misunderstanding your intent, the page getting stuck, or changes not appearing after publishing — this guide walks you through the most common causes and how to resolve them. ⚙️ Step 1: Confirm You're Using the Right Page Type Website Studio supports several page creation modes. Selecting the wrong mode is a frequent cause of confusion. 1. Go to Left sidebar → Website Studio (What will we get done today?) (URL: /website-studio). 2. Click Generate PPC Site or the relevant option for your goal. 3. When prompted, clearly specify that you want a Coming Soon page. Use that exact phrase so the AI understands your intent. 4. If the generated result doesn't match, click back and restart the generation with a more specific description, for example: "A Coming Soon page for a local bakery launching in September." 🚀 Step 2: Resolve a Stuck Publishing State A known issue can cause pages to appear stuck in a Publishing state indefinitely. If your Coming Soon page shows a publishing spinner that never completes, try the following: 1. Refresh your browser tab and return to Website Studio. 2. Locate your project in the page list and check whether the status has updated. 3. If the page is still stuck, click into the project, make a minor edit (such as a single space), then click Publish again. 4. If the issue persists after a second publish attempt, proceed to Step 5 to contact support. 🖥️ Step 3: Fix Visual or Card Display Inconsistencies You may notice that panels look different from what you expected, certain features appear greyed out, or a success message appears twice. These are known visual inconsistencies currently being addressed by our engineering team. In the meantime: - Ignore duplicate success toasts — your page has only been published once. - If a feature panel appears disabled or greyed out, it may not be supported for the Coming Soon page mode. Try a different section or layout option instead. - If a panel silently fails to update (no error, no change), save your work, refresh the page, and reapply the change. 📋 Step 4: Check Error Messages and Panel Failures Some panels may fail silently due to an internal error-handling issue. If you made a change and nothing happened — no confirmation, no error — follow these steps: 1. Save any progress by clicking Publish or the save option available in the editor. 2. Refresh your browser and reopen the project. 3. Reattempt the action that failed. If it fails again without any message, note exactly which panel or section you were editing. 4. This information will help our team diagnose the issue quickly when you contact support. 📄 Step 5: Working Around Page Copy or Migration Limitations Currently, Website Studio does not support migrating or copying pages between projects. If you need to replicate your Coming Soon page in a different project: - Use the Clone an Existing Page option from the Website Studio home screen — note this works within the same project only. - To recreate the page in a new project, use your original design as a reference and regenerate it using the same prompt and settings. - Save your page content (text, images, brand details) externally before attempting any migration so nothing is lost. 💡 Tips for Better Results with Coming Soon Pages - Be specific in your prompt. Include your brand name, industry, launch date, and the mood or style you want. - Use the Brand Vault. If you've set up a brand vault, the editor will apply your colours, fonts, and logo automatically — reducing the need for manual corrections. - Publish early and often. Save your progress by publishing frequently, especially after major edits, to avoid losing work if the editor encounters an error. - Clear your cache. If the editor looks broken or panels won't load, clearing your browser cache and reloading often resolves display issues. 🆘 Still Having Issues? If you've followed all the steps above and your Coming Soon page still isn't working as expected, 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. When you reach out, please have the following ready to speed up the resolution: - The name of your project in Website Studio - A description of the action you were trying to take - Any error messages you saw (or confirmation that none appeared) - Screenshots if possible

🇫🇷 Fix French Titles and Pages

📄 Create French content Search Atlas supports French content generation for pages, headings, titles, and meta descriptions. To create a new French article, go to Content → Content Genius and choose Generate, Write with AI in Bulk, or Write it yourself. 1. Choose the content workflow you need. 2. Set the target page language or specify French in your instructions. 3. Review the generated H1, title tag, meta description, and body content before publishing. 4. Confirm that names, accents, keywords, and search intent match the French audience. 🔍 Review French page suggestions For existing pages, open Content → Onpage Audit and select the relevant page tab. Use Run Audit to review recommendations. Check that suggested titles, headings, keywords, and descriptions are written in French rather than English. ✏️ Correct English titles or metadata If a French page receives English suggestions, update the page language or add a clear instruction such as: Write all titles, headings, meta descriptions, and recommendations in French. Then regenerate the content or suggestion and compare the result with the original page. - Use French keywords and search terms. - Keep the intended meaning and tone of the original page. - Check accents and French punctuation. - Make sure the title and meta description accurately describe the page. ✅ Validate before publishing Before applying changes, confirm that the page URL, H1, title tag, meta description, and body content are all aligned with the French topic. If the page is multilingual, review each language version separately to prevent English text from appearing on the French version. 🛠️ When French localization still fails Some older workflows or previously generated recommendations may retain English labels or suggestions. Regenerate the content after confirming the language instructions, then review the output manually. Do not publish titles or metadata until the language and meaning are correct. 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.

↩️ Restore a Website Studio Project Version

🕐 How Version History Works Website Studio automatically saves your project at regular intervals as you work. Every auto-save and every time you manually save creates a restore point you can return to at any time. This means that if you accidentally delete a section, break a layout, or make unwanted changes, you can roll back without losing all your progress. 📂 Accessing Version History 1. In the left sidebar, click Website Studio (URL: /website-studio). 2. Open the project you want to restore. 3. In the top toolbar of the editor, click the History icon (clock icon) near the top-right corner of the screen. 4. A Version History panel will slide open on the right side, listing all available save points with timestamps. 🔄 Restoring a Specific Version 1. In the Version History panel, browse the list of save points. Each entry shows the date, time, and save type (auto-save or manual save). 2. Click any version to preview what your project looked like at that moment. The canvas will update to show you that version without making any permanent changes yet. 3. When you find the version you want — for example, a save from two hours ago or one from yesterday — click Restore This Version. 4. A confirmation dialog will appear. Click Confirm Restore to apply the version. Your project will immediately revert to that save point. 💾 Creating a Manual Save Point Before making major changes to your project, it is a good habit to create a manual save point so you always have a clean version to return to. - In the editor toolbar, click the Save button (or press Ctrl + S on Windows / Cmd + S on Mac). - The save will appear instantly at the top of your Version History list with the current timestamp. ⚠️ Important Things to Know - Restoring is safe to preview — clicking a version only previews it. Your live project is not changed until you click Restore This Version and confirm. - Restoring replaces your current state — once confirmed, the current unsaved work will be overwritten by the restored version. Save a manual checkpoint first if you want to preserve anything from the current state. - Version history is per-project — each project maintains its own independent history. Restoring one project does not affect any others. 🆘 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 Website Studio Glitches and Request Credit Refunds

🔍 Overview Website Studio is a powerful page-building tool, but some users encounter issues such as duplicate pages, 404 errors, Brand Vault assets not applying, or blank pages after syncing to WordPress. This article walks you through how to diagnose and fix the most common problems — and explains how to request a credit refund if you need to start fresh. ⚠️ Common Issues and What Causes Them - Duplicate pages: Multiple prompts or AI Agent actions can sometimes generate duplicate pages within the same project. - 404 errors ("Post Not Found"): These can appear after syncing pages through Content Genius or when editor/preview URLs accidentally leak into your live site or sitemap. - Brand Vault assets not applying: Logos, fonts, or brand colours may not render correctly if the Brand Vault sync did not complete before page generation. - Blank pages after WordPress sync: A known issue where pages publish without content after using the Sync to WordPress feature. 🛠️ Step-by-Step Troubleshooting 1. Navigate to Website Studio. In the left sidebar, select Website Studio (or go directly to /website-studio). 2. Check for duplicate pages. Open your project and review the page list. Delete any duplicates by clicking the three-dot menu next to the page name and selecting Delete. 3. Re-apply Brand Vault assets. Before regenerating a page, confirm your Brand Vault profile is fully saved and active. Go to Brand Vault, verify your logo, colours, and fonts are set, then return to Website Studio and regenerate the affected page. 4. Fix 404 errors after Content Genius sync. If a page shows "Post Not Found," unpublish and republish the page from within Website Studio. If the issue persists after republishing, delete the page and recreate it. 5. Resolve blank WordPress pages. If a synced page appears blank on WordPress, re-sync it from Website Studio. Open the page, click Sync to WordPress, and confirm the content appears before publishing. 6. Clear polluted URLs from your sitemap. If editor or preview URLs have leaked into your live sitemap, manually remove them from your WordPress sitemap plugin or regenerate your sitemap after deleting the affected pages in Website Studio. 🔄 When to Delete a Project and Start Fresh If your project has widespread duplicate pages, persistent 404 errors, and Brand Vault assets that will not apply despite following all troubleshooting steps, starting a new project is often the fastest path to a working result. Before deleting, note the following: - Deleting a project is permanent and cannot be undone. - Save or export any content you want to keep before deleting. - Credits consumed on a broken project may be eligible for a refund — see the section below. To delete a project, open it in Website Studio, click the project settings or three-dot menu, and select Delete Project. Confirm when prompted. 💳 How to Request a Credit Refund If a technical issue in Website Studio caused credits to be consumed without producing a usable result, you may be eligible for a credit refund. Our support team reviews each request individually based on the nature of the issue. To submit a refund request, please have the following information ready: - The name or ID of the affected project - A brief description of what went wrong (e.g., duplicate pages, 404 errors, blank WordPress sync) - The approximate number of credits consumed - Any screenshots that show the issue Credit refunds are not guaranteed for all cases but are prioritised when the issue is caused by a platform bug rather than user error. 💡 Tips to Avoid These Issues in the Future - Always complete your Brand Vault setup before starting a new Website Studio project. - Avoid sending multiple prompts to the AI Agent in quick succession — wait for each action to complete before submitting the next one. - After syncing to WordPress, preview the page on your live site before publishing to confirm content has transferred correctly. - Regularly check your sitemap for unexpected URLs and clean them up if editor or preview links appear. 🙋 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 Website Studio Visual Editor Issues

🔍 Overview Some customers have reported that the visual editor inside Website Studio stops responding to selections — for example, clicking on fonts or other elements does nothing, and recent changes appear to be missing. This is a known issue that our team is actively investigating. 🚨 Common Symptoms - Clicking on page elements (such as fonts, headings, or sections) does not open the editor panel. - The visual selector cursor appears but does not highlight or select elements. - Recent edits — including font changes — are not visible after returning to the editor. - The editor appears to load correctly but remains unresponsive. 🛠️ What to Do Because this is a confirmed bug, the most reliable path to resolution is to contact our support team directly. To help us investigate and resolve your issue as quickly as possible, please have the following information ready when you reach out: - Your project name — the name of the Website Studio project where the issue occurred. - A description of the exact symptoms — for example, which elements you were trying to select, and what happened (or didn't happen) when you clicked. - The approximate date and time the issue first occurred, including your time zone. - Any changes that appear to be missing — describe what edits you made (e.g. font changes, section edits) that are no longer visible. - Your browser and operating system — for example, Chrome on Windows 11 or Safari on macOS Ventura. Having this information ready will allow our team to investigate your specific session and work toward recovering any affected data. 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.

🛠️ Troubleshoot Website Studio and Coming Soon Pages

🔍 Overview Website Studio lets you build, edit, and publish web pages directly inside Search Atlas. This article covers the most common issues customers encounter — including coming soon page problems, the AI not understanding your intent, and recurring account-related errors — and explains how to resolve them step by step. 🚀 Getting Started: Navigating to Website Studio Before troubleshooting, make sure you are in the right place: 1. Log in to your Search Atlas account. 2. Click Website Studio in the left sidebar. 3. The URL should show /website-studio. From here you can generate PPC landing pages, clone existing pages, build a local website, import a project, or create a brand vault. 📄 Fixing Coming Soon Page Issues If your coming soon page is not displaying correctly, is showing blank content, or was published but still appears broken, follow these steps: 1. Re-open the page in Website Studio. Navigate to Website Studio → /website-studio and locate your coming soon page in the project list. 2. Check the publish status. A known issue caused some pages synced to WordPress to publish as blank. If your page is blank after publishing, unpublish it, make a small edit (such as adding a space and removing it), then republish. 3. Re-publish the page. Click the publish button and wait for a confirmation message. If no confirmation appears, refresh the page and check your WordPress dashboard to confirm the content arrived correctly. 4. Clear your browser cache. After publishing, clear your cache and reload the live URL to confirm the correct version is showing. 5. Try a different browser. If the page still looks wrong, open it in an incognito window or a different browser to rule out a local cache issue. 🤖 When Website Studio AI Does Not Understand Your Request The AI assistant inside Website Studio interprets your prompts to build or modify pages. If it is not producing what you expect, try the following: - Be specific with your prompt. Instead of saying "make it look better," describe exactly what you need — for example, "Add a centered headline that says Coming Soon, a countdown timer, and an email sign-up form below." - Break large requests into smaller steps. If you ask for many changes at once, the AI may misinterpret part of the request. Submit one change at a time and confirm the result before continuing. - Reload and try again. A known issue caused multiple duplicate prompts to appear after the AI agent created or modified a page. If you see repeated prompt bubbles, refresh the page and re-enter your last request once. - Use the undo option. If the AI applies a change you did not want, use the undo control to revert and rephrase your prompt. - Start from a template. If the AI continues to misunderstand a complex layout, try generating the page from a preset option such as Generate PPC Landing Page or Build a Local Website and then ask the AI to adjust specific sections. ⚙️ Resolving Recurring Account Issues If you are experiencing repeated errors across sessions — such as features not loading, panels not appearing, or actions silently failing — follow these steps: 1. Log out and log back in. Go to your account menu in the top-right corner, select Log Out, then sign back in. This refreshes your session and clears temporary errors. 2. Check your subscription plan. Some Website Studio features are only available on certain plans. If a panel or action is missing, verify that your plan includes Website Studio access. 3. Clear cookies and site data. In your browser settings, clear cookies for app.searchatlas.com and reload the platform. 4. Try a different browser or device. This helps confirm whether the issue is browser-specific. 5. Check for ongoing platform updates. Occasionally, features may be temporarily unavailable during a deployment. Wait a few minutes and try again. 💡 Tips for a Smoother Website Studio Experience - Always save your work before switching between projects or navigating away from the editor. - If you are cloning an existing page, note that the Clone Page action is being expanded — if it is not visible in your current view, use the main Clone an Existing Page option from the Website Studio home screen. - When syncing pages to WordPress, confirm your WordPress credentials and connection are active under your project settings before publishing. - Use the Brand Vault to store your colours, fonts, and logo so the AI can apply consistent branding automatically. 🆘 Still Having Trouble? If the steps above did not resolve your issue, our 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 Website Studio Blank Live Site Errors

🔍 Understanding the Problem When your Website Studio live site appears blank — even though the preview looks correct — this is typically caused by a site generation failure. The generation process did not complete successfully, leaving your live site without content. These errors can affect all devices, and refreshing the page will not resolve the underlying issue. This is a known platform-level bug that requires backend investigation by our team. ⚠️ What Is Happening A Website Studio site generation failure means the process that builds and publishes your live site did not finish correctly. As a result, your live site displays no content even though your project may appear intact inside the platform. This is not caused by your browser, device, or project settings — it is an internal generation issue. 📋 How to Escalate — What to Have Ready Because this is a backend bug, our support team will need to investigate your specific project. To get this resolved as quickly as possible, please have the following information ready before reaching out: - The exact name of your Website Studio project. - The live site URL that is showing blank content. - The approximate date and time when you first noticed the blank site. - A brief description of any error messages or notices you saw (if any). - Whether the in-app preview also appears blank, or only the live site. 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.

🔄 Migrate WordPress OTTO Projects to Website Studio

Overview When you migrate a site from WordPress to Website Studio and need to set up a new OTTO project against the migrated site, certain configuration steps are required to ensure the project is connected correctly. Because the precise resolution depends on your specific account and project configuration, our support team will need to review your setup directly. Why Issues May Appear After Migration After a WordPress-to-Website Studio migration, OTTO projects may encounter errors or unexpected behavior related to how the new project is connected to the migrated domain. The exact nature of these issues varies by account, so our support team will investigate your specific setup to determine the correct resolution path. What to Have Ready Before Contacting Support - Your project name — the exact name of the OTTO project affected. - Your live domain — the full URL of the site as it appears after migration (for example, example.com). - The exact error message — copy the full text of any error displayed in the platform. - Timestamp — note when the error first appeared or when the migration was completed. Having this information ready will allow our team to investigate and resolve your OTTO project setup accurately without delays. 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.

🏙️ Create and Clone Location Pages in Website Studio

Overview Location pages are a core local SEO tactic. For service-area businesses like roofing contractors, a dedicated page for each city helps your client rank in local search results. Website Studio supports building and managing multiple location pages within a single project. What to Have Ready Before You Begin Having the following details on hand will help you move through the workflow efficiently: - The name of your Website Studio project - The cities or service areas you want to create pages for - Location-specific content for each page (city name, local contact details, service area descriptions) - Any schema or meta details you want to customise per location How to Create and Clone Location Pages Follow these steps to build your first location page and then clone it for additional cities: 1. Open Website Studio and navigate to your client's main website project. 2. In the left-hand page list, click Add Page and name the page after your first target location — for example, Roofing Services – Austin, TX. 3. Build out all content for that location page: headings, body copy, contact details, a map embed if needed, and any local business schema. Save the page when done. 4. In the page list, hover over the completed location page to reveal the page actions menu (three-dot icon or right-click context menu), then select Clone Page (or Duplicate Page). 5. A copy of the page will appear in the page list. Click the cloned page's name to rename it to the next target city — for example, Roofing Services – Dallas, TX. 6. Open the cloned page and replace every instance of the original city name with the new city name, including headings, body text, meta title, meta description, and the URL slug. 7. Update any location-specific details such as phone numbers, addresses, service area descriptions, and map embeds. 8. Repeat steps 4–7 for each additional city you need to target. Linking Location Pages to Your Main Project Once your location pages are created, connect them to the rest of the site to strengthen internal linking and local SEO signals: - Add links to each location page from your main Services or Locations page. - Include a footer navigation section listing all location pages if you are targeting several cities. - Make sure each location page links back to the main homepage or a parent service 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 Website Studio Failed to Load Projects

🔍 Overview If you see a "Failed to load projects" error when opening Website Studio, your projects are not lost. This error is usually caused by a temporary loading issue, a stale browser session, or a sync problem between the platform and your project data. Follow the steps below to resolve it. 🗺️ How to Get to Website Studio To confirm you are in the right place, navigate to Website Studio using the left sidebar. Click Website Studio in the left navigation menu, or go directly to /website-studio in your browser's address bar. ⚙️ Step-by-Step Troubleshooting 1. Hard refresh the page. Press Ctrl + Shift + R (Windows/Linux) or Cmd + Shift + R (Mac) to force the browser to reload all assets from scratch, bypassing the local cache. 2. Clear your browser cache and cookies. Go to your browser settings, clear cached images, files, and cookies for the Search Atlas domain, then reload the page. Stale session data is a common cause of this error. 3. Try a different browser or Incognito/Private window. Open an Incognito or Private window and log in again. This rules out browser extensions or cached data interfering with the platform. 4. Check your internet connection. A weak or unstable connection can interrupt the project-loading request. Switch networks or disable a VPN if you are using one, then reload the page. 5. Log out and log back in. Click your account menu, select Log Out, then sign in again. This refreshes your authentication token and often resolves persistent loading failures. 6. Wait a few minutes and retry. Occasionally, a temporary platform issue may prevent projects from loading. Wait 2–5 minutes, then return to /website-studio and try again. 7. Check if a specific project fails or all projects fail. If only one project fails to open while others load normally, the issue is isolated to that project. Note the project name so you can share it with our team. 🚫 Common Causes at a Glance - Stale browser cache or cookies — prevents the platform from loading fresh project data. - Expired authentication session — logging out and back in resolves this. - Browser extensions — ad blockers or script blockers can interfere with the builder. - Temporary platform sync issue — usually resolves on its own within a few minutes. - Single project rendering failure — isolated to one project and requires team investigation. ✅ After the Error Is Resolved Once your projects load successfully, verify the following to avoid a recurrence: - Make sure you are using a supported, up-to-date browser (Chrome or Edge are recommended). - Avoid keeping the Website Studio tab open for very long periods without refreshing, as sessions can expire silently. - If you use a WordPress integration, confirm that the Sync to WordPress connection is still active under your project settings. A broken WordPress connection can sometimes prevent project data from loading correctly. 💬 Still Seeing the Error? If none of the steps above resolve the issue, our team can investigate your specific account and project data directly. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team. When you reach out, please share the following to help us resolve it faster: - The name of the affected project(s) - The exact error message displayed on screen - The browser and operating system you are using - Any steps you have already tried from this guide

🔄 Recovering Deleted Pages in Website Studio

If pages in your Website Studio project were unexpectedly deleted, you can recover them in two ways: use the built-in Revert feature to roll back the entire project, or request a selective backend restore from Search Atlas Support to recover only the missing pages. The right path depends on whether you have made any manual changes since the deletion. ⚡ Choosing the Right Recovery Path Before acting, identify which scenario applies to you: - No manual changes made since the deletion: Use the Revert feature. It is self-serve and restores all missing pages in one step. - You have already manually recreated or edited pages after the deletion: Do not use Revert — it will overwrite your manual work. Contact Support for a selective backend restore instead. - Pages were deleted automatically by the system (not by a user action): Contact Support immediately, regardless of any manual changes made since. A partial backend restore may still be possible, and acting quickly preserves your recovery options. If you are unsure which scenario applies, contact Support before using Revert. 🔄 Using the Revert Feature in Website Studio Use this option only if you have made no manual changes since the pages were deleted. Revert restores your entire Website Studio project to a previous snapshot — including all pages, content, and settings from that point in time. Any work done after the chosen snapshot date, including pages you have manually recreated, will be permanently lost once you confirm the action. Steps to revert your Website Studio project 1. Open Website Studio and select your project. 2. Go to Settings within the project. 3. Locate the Revert option and review the available snapshots. Choose the most recent snapshot dated before the deletion — this recovers your pages while losing the least amount of subsequent work. Snapshots are retained for a limited window, so act as soon as you notice missing pages. 4. Click Revert and confirm the action in the dialogue that appears — this cannot be undone. Your project restores to the selected snapshot and all pages that existed at that point reappear. You will see a confirmation message when the revert is complete. ⚠️ If Revert fails If you see a "Failed to restore" error message after clicking Revert, stop and do not retry. Retrying can extend the recovery window and reduce the snapshots available to Support. Contact Search Atlas Support immediately and share: - The exact error message (including any commit hash shown in the toast) - Your project URL - The snapshot date you selected A backend restore may be required to complete the recovery. 🛠️ Contacting Support for a Selective Backend Restore If you have already manually recreated or edited pages after the deletion — or if pages were deleted automatically by the system — use this path instead. Search Atlas Support can perform a selective restore that recovers only the deleted pages without affecting any pages you have already rebuilt. How to reach Support - Open the live chat widget in the bottom-right corner of the Search Atlas platform and type human teammate to be connected with a member of our team. What to include in your request Provide all of the following so Support can scope the restore correctly on the first pass: - Your project URL and project name or domain (for example, data-insight.org) - The account email associated with the project - The approximate date and time the pages were deleted - A list of the deleted page URLs, slugs, or titles, if you have them - Which pages, if any, you have already manually recreated, so Support can exclude them from the restore and preserve your work - Whether the deletion appears to have been user-initiated or system-initiated Turnaround Mention "Selective Page Restore — Website Studio" in your chat message to route your request to the correct team immediately. A selective backend restore is an escalated operation, so timelines depend on the size and complexity of the restore. Support will confirm receipt and provide an estimated turnaround once they have reviewed the affected pages. 📋 What Happens During a Backend Page Restore When Support performs a selective backend restore, they recover only the specific deleted pages from a server-side snapshot of your project. Here is what to expect: - Pages you manually recreated after the deletion are not affected. - Restored pages appear in Website Studio exactly as they existed before the deletion event. - Support will notify you when the restore is complete so you can review the results. After the restore, open each recovered page in Website Studio and verify the content is accurate before republishing. ⚠️ Why Pages Can Be Automatically Deleted in Website Studio In some cases, Website Studio can remove pages from a project without a manual delete action. Known triggers include: - Sync or import operations that overwrite the existing project structure - Bulk actions applied to the wrong project - Backend processing errors during large-scale content updates If pages are missing and you did not delete them manually, contact Support immediately — a partial backend restore may still be possible even if you have made manual changes since. Your report also helps the team identify the root cause and prevent it from recurring. 🎯 You now know how to recover deleted pages in Website Studio — use the built-in Revert feature if no manual work has been done since the deletion, or escalate to Search Atlas Support for a selective restore that keeps your progress intact. When in doubt, or if Revert fails with a "Failed to restore" error, always contact Support Chat and type "Human Teammate", they will help you resolve this, before making any further changes to your project.

🛠️ Fix Website Builder Page Duplication and AI Editing Bugs

Overview Two bugs in Website Studio were reported by customers related to page duplication and AI overlay editing. The issues involved: - Edits made to a duplicated page affecting the original page - AI overlay editing tasks not completing as expected Both issues were escalated to the Search Atlas engineering team. If you are experiencing either of these problems, please reach out to our support team so we can investigate your account and assist you directly. You can contact us via the chat widget in the bottom-right corner of the platform — just type human teammate to be connected with a member of our team. What Was Reported Customers encountered the following bugs in Website Studio: - Page duplication overwriting originals: When a page was duplicated and then edited, changes were incorrectly applied back to the original page instead of the copy. - AI overlay editing tasks not completing: AI tasks targeting overlay sections appeared to process but did not complete successfully, and in some cases credits were deducted. What To Do If You Are Affected Because these are confirmed bugs, specific workarounds depend on your account setup and the current state of your pages. We recommend the following general steps: 1. Stop making additional edits to affected pages to avoid further unintended changes while the bugs are under investigation. 2. Make a copy of any important page content in an external document so you have a backup of your work. 3. Do not retry failing AI tasks repeatedly, as this may continue to consume credits without producing results. 4. Contact our support team so we can review your account, check the status of any affected AI tasks, and assist with any credits that were incorrectly consumed. Contact Support If you have been affected by either of these bugs — including if credits were deducted for failed tasks — please contact our support team. You can reach us via the chat widget in the bottom-right corner of the platform — just type human teammate to be connected with a member of our team. Provide your project name and the names of any affected pages so we can assist you as quickly as possible.

🗓️ Website Studio Large-Scale Migration Timeline

🔍 What Is Large-Scale Migration in Website Studio? Large-scale migration refers to the ability to move an existing website — including all its pages, assets, content, and structure — into Website Studio in bulk. This is distinct from importing a single page or building a site from scratch using the available tools today. Currently, Website Studio supports various entry points for building and expanding your web presence, including options to create new pages, duplicate existing pages, import compatible project files, and set up brand assets. You can access these options by navigating to Website Studio in the platform. 📅 When Will Large-Scale Migrations Be Available? Large-scale website migration is on the Search Atlas product roadmap. However, we do not have a confirmed release date or specific timeline to share at this time. As with all major features, availability depends on engineering progress and internal prioritization. We recommend reaching out to our support team directly for the most up-to-date information on this feature's status. ⚙️ What You Can Do Right Now While large-scale migration is not yet available, Website Studio does offer existing tools that may help with your current workflow. We recommend exploring the available page creation and import options within the platform to find the approach that best fits your needs. If large-scale migration is a capability you are waiting on, the best step is to formally register your interest so the product team is aware of customer demand. When contacting support, please have the following ready: - A brief description of the migration scope you need (e.g., number of pages, site type) - Your current workaround or blocker, if any - Your account or project name so the team can log your request accurately 🔔 How to Stay Updated on This Feature Search Atlas regularly ships product updates. To make sure you do not miss the announcement when large-scale migration launches: - Check the platform dashboard regularly for release notes and feature announcements. - Contact our support team to ask for the latest roadmap status and to formally register your interest in this feature. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix WordPress Migration Errors from Website Studio

🔍 Overview When you publish or sync a Website Studio site to WordPress, you may encounter issues such as pages returning 404 errors, WordPress dashboard tools not functioning correctly, navigation links breaking, or blog content not displaying as expected. This article explains the most common causes and the steps you can take to resolve them. ⚠️ Known Issues to Be Aware Of Before troubleshooting, note the following confirmed issues that may affect your sync: - Articles synced via Content Genius may not publish correctly to WordPress. This is a known issue currently awaiting a platform fix. If your blog posts were created or managed through Content Genius, they may appear blank or fail to transfer. - Blog pages may only be accessible via a homepage quick-link. Direct URLs to blog pages could previously redirect to the homepage. This has been resolved in a recent update — if you are still experiencing this, follow the steps below. - Blank pages after sync. A bug that caused synced pages to publish as blank has been fixed. If you synced before this fix was released, re-syncing your site should resolve the issue. ✅ Step 1 — Verify Your WordPress Connection A failed or incomplete connection between Website Studio and your WordPress site is the most common cause of sync errors. 1. Go to Website Studio in the left sidebar of Search Atlas (URL: /website-studio). 2. Open your site project and navigate to the Publish or Sync to WordPress option. 3. If you see the error "Couldn't load your WordPress sites," your WordPress credentials need to be re-entered or reauthorised. 4. Disconnect and reconnect your WordPress site by re-entering your site URL and credentials. Ensure you are using an account with Administrator permissions on WordPress. 5. Once reconnected, attempt the sync again. 🔄 Step 2 — Re-Sync Your Site After Known Fixes If your site was synced during a period when a known bug was active, the simplest fix is to perform a fresh sync. 1. In Website Studio, open the affected site project. 2. Review your pages to confirm all content is correct and complete inside the builder before re-syncing. 3. Trigger a new Sync to WordPress. This will overwrite previously published blank or broken pages with the current content. 4. After syncing, visit your live WordPress site and confirm pages load correctly. 🗺️ Step 3 — Fix 404 Errors and Broken Navigation 404 errors after migration are usually caused by WordPress permalink settings not matching the URLs published by Website Studio. 1. Log in to your WordPress Admin Dashboard. 2. Go to Settings → Permalinks. 3. Without changing anything, click Save Changes. This forces WordPress to flush and regenerate its rewrite rules, which resolves most 404 errors. 4. Return to your live site and test the affected page URLs. 5. If a specific navigation link is broken, check the link destination inside Website Studio and confirm it matches the slug of the published WordPress page exactly. 📝 Step 4 — Resolve Missing or Incorrect Blog Content Blog posts may not display correctly due to page template mismatches or the Content Genius sync limitation mentioned above. - If blog posts are blank: This may be related to the known Content Genius sync issue. Re-publishing the posts manually inside WordPress, or waiting for the upcoming platform fix, is currently the recommended workaround. - If the blog page shows no posts: In your WordPress Admin, go to Settings → Reading and confirm that the correct page is assigned as your Posts page. - If direct blog URLs redirect to the homepage: This was a known bug that has been resolved. Perform a fresh sync from Website Studio and then flush your WordPress permalinks as described in Step 3. 🧪 Step 5 — Test Your Site After Changes After completing the steps above, run a quick check to confirm everything is working: - Visit your homepage and click through all main navigation links. - Test at least two or three internal page URLs directly in your browser. - Open a blog post to confirm the content renders fully. - Check that WordPress tools such as the admin bar and dashboard are accessible and functioning normally. 💬 Still Experiencing Issues? If the steps above do not resolve your problem — especially if you are affected by the Content Genius sync limitation still awaiting a platform release — our team can investigate further. 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 Blank Pages: What to Know

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

🛠️ Fix URL Migrations, Content Cloning & 410 Deletions

🗺️ Overview If your website has pages living under incorrect URLs or slugs, you may need to move content to a new location, update author metadata, and permanently remove the old URLs so search engines stop indexing them. This article walks you through each step using Website Studio and explains current limitations you should be aware of. ⚠️ Known Limitations in Website Studio Before you begin, be aware of the following platform constraints that may affect your workflow: - No bulk page migration: Website Studio does not currently support moving or copying pages between projects in bulk. Each page must be handled individually. - No native page cloning: The ability to clone an existing page inside Website Studio is not yet available. If you were directed to use a clone feature, this has been temporarily removed while improvements are in progress. - Pillar page editing restrictions: Some pillar pages may appear locked or redirect you to unrelated suggestions. This is a known issue currently under investigation. - Content Genius library import: Bulk-importing your Content Genius blog library directly into Website Studio is not yet supported. Our engineering team is actively working on these improvements. In the meantime, use the manual steps below to complete your migration. 📋 Step 1 — Create the Correct Page at the New URL Start by building the destination page with the right URL slug before touching the old one. 1. Open Website Studio from the left sidebar (URL: /website-studio). 2. Select your project and click Add New Page. 3. Set the URL slug to the correct path, for example /blog/your-topic-name. Make sure the parent directory matches your intended structure (e.g., /blog/). 4. Copy your content from the old page manually — paste the body text, headings, images, and meta fields into the new page. 5. Review all on-page SEO fields: title tag, meta description, and canonical URL. 6. Click Save and then Publish once you are satisfied. ✍️ Step 2 — Update Author Metadata After publishing the page at the correct URL, update the author information so it reflects the right name and profile. 1. Inside the page editor, locate the Author field. This is typically found in the page settings panel or a metadata section. 2. Clear the existing author name and type the correct name. 3. If your theme supports author bios or profile links, update those fields as well. 4. Save the page again to apply the changes. Note: If the Author field is not visible in the editor, the field may be controlled at the theme or template level. Contact support via the chat widget (details at the end of this article) for help exposing this field. 🗑️ Step 3 — Hard-Delete the Old URL with a 410 Status A 410 Gone response tells search engines that a URL has been permanently removed and will not return — this is stronger than a 404 and faster for deindexing than a redirect. Use this for URLs that should never have existed or carried incorrect slugs. 1. Do not set up a 301 redirect from the old URL to the new one if the old URL was incorrect and you want it removed from search index entirely. 2. Navigate to Website Studio → Redirects & Status Rules (or your hosting/server configuration if this is managed outside the platform). 3. Add a rule for the old URL and set the response code to 410. 4. Save the rule and verify it is active by testing the old URL in a browser or using an HTTP status checker tool. 5. Optionally, submit the old URL for removal in Google Search Console under Removals → Temporary Removals to speed up deindexing. Important: If the old page is still published inside Website Studio, unpublish or delete it first before applying the 410 rule. A live page and a 410 rule on the same URL will conflict. 🔍 Step 4 — Verify the Migration Before closing out, confirm everything is working correctly. - Visit the new URL and confirm the content, author name, and metadata are correct. - Visit the old URL and confirm it returns a 410 status code. - Check your internal links and update any that still point to the old URL. - Review your XML sitemap to ensure the old URL has been removed and the new URL is included. 💡 Tips to Avoid This Issue in the Future - Plan your URL structure and slug naming conventions before creating pages. - Always set the correct parent path (e.g., /blog/) when creating new blog content. - Assign the correct author at the time of page creation rather than updating it later. - Avoid publishing placeholder pages at incorrect URLs — draft mode is available for work in progress. 🙋 Need More Help? If you are unable to edit a specific pillar page, cannot locate the 410 redirect option, or need hands-on assistance with a complex migration, our 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.

🛠️ Migrate, Clone, and Clean Up Website Studio Pages

🗺️ Overview This article covers the full workflow for cleaning up a Website Studio project that has content published under incorrect URLs. Specifically, it walks you through migrating content to the correct /blog/ URL structure, updating author metadata, and permanently removing outdated URLs using a 410 (Gone) status so they are excluded from your sitemap and database. Important: Some steps in this workflow are affected by known platform limitations currently being resolved by our engineering team. Where a limitation applies, we have noted the recommended workaround. ⚠️ Known Platform Limitations to Be Aware Of Before you begin, review these active issues that may affect your workflow: - Page cloning is not yet available. Website Studio does not currently support cloning or duplicating an existing page within or between projects. This blocks a direct copy-and-migrate path. A fix is in progress. - Bulk import from Content Genius is not yet supported. You cannot pull your full blog library into Website Studio in bulk at this time. - Deleting a published page does not immediately revoke its public URL. There may be a short delay before the URL becomes inaccessible after deletion. This is a known issue and is being addressed. - Pillar page editing suggestions may point to incorrect pages. If Website Studio redirects you to the wrong page when you try to edit a pillar page, use the direct page management view instead (see steps below). 📋 Step 1 — Identify the Incorrect URLs Start by making a list of every page that is published under the wrong URL. You will need this list to complete the migration and deletion steps. 1. Open Website Studio from the left navigation menu. 2. Select your project and go to Page Management. 3. Review all published pages and note any that are not under your intended /blog/ URL path. 4. Record the full URL of each incorrect page alongside the correct target URL it should move to. ✍️ Step 2 — Recreate Content Under the Correct /blog/ URLs Because page cloning is not currently available, content must be manually recreated under the correct URL. Follow these steps for each page that needs to move: 1. In Page Management, click Create New Page. 2. Set the URL slug to the correct /blog/your-page-name path. 3. Open the original incorrect page in a separate browser tab. 4. Copy all content — headings, body text, images, meta title, and meta description — from the original page into the new page. 5. Update the author name field. Change it from Marcus Eriksson to Nestor Vazquez (see Step 3 for full author metadata instructions). 6. Save and publish the new page once all content and metadata are confirmed correct. 👤 Step 3 — Update Author Metadata Author metadata is set at the individual page level inside Website Studio. To update the author name on each migrated page: 1. Open the newly created page in the Website Studio editor. 2. Navigate to the Page Settings or SEO Settings panel. 3. Locate the Author field and replace Marcus Eriksson with Nestor Vazquez. 4. Confirm the author name also appears correctly in any visible byline element on the page design itself. Update the design element manually if it does not pull from metadata automatically. 5. Save your changes. 🗑️ Step 4 — Delete Incorrect URLs and Apply 410 Status A 410 (Gone) status tells search engines that a page has been permanently removed and should not be re-crawled or re-indexed. This is different from a 301 redirect and is the correct choice when the old URL should leave no trace. 1. Confirm the new /blog/ version of each page is live and correct before deleting the old URL. 2. In Page Management, locate each incorrect URL. 3. Open the page settings and look for the HTTP Status or Redirect / Status Code option. Set the status to 410 Gone — do not set a redirect destination. 4. Save the setting, then delete or unpublish the page. 5. Do not create a 301 redirect from the old URL to the new one. A 410 signals permanent removal; a redirect would pass authority to the new page but also signals the old URL once existed, which is not desired in this case. Note: Due to the known issue with delayed URL revocation, check the old URLs again 24 hours after deletion to confirm they return a 410 response. You can use a free HTTP status checker tool to verify. 🗺️ Step 5 — Remove Old URLs from Sitemap and Database After applying the 410 status and deleting the pages, ensure the incorrect URLs are fully removed from your sitemap: 1. Go to your Website Studio project Settings. 2. Open the Sitemap section and confirm the deleted URLs no longer appear. If they do, regenerate or republish the sitemap. 3. Submit your updated sitemap to Google Search Console to prompt faster re-crawling and de-indexing of the removed URLs. 4. In Google Search Console, use the URL Removal tool to request temporary suppression of the old URLs from search results while Google processes the 410 status. ✅ Checklist — Before You Finish - All content is live under the correct /blog/ URLs - Author name reads Nestor Vazquez on all migrated pages - All incorrect URLs return a 410 Gone status - No 301 redirects point from old URLs to new URLs - Sitemap has been regenerated and resubmitted - URL removal requests submitted in Google Search Console 💬 Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Troubleshooting Common Website Studio Bugs

🔍 Overview Website Studio uses AI to apply changes to your site visually and automatically. While powerful, a number of known bugs can occasionally affect the editing experience — including unwanted layout changes, failed reverts, missing blog images, and articles that disappear after a fix is applied. This article explains what causes these issues and what steps you can take right now. ⚠️ Known Issues at a Glance - Unwanted menu or header changes applied after unrelated edits - Reverts that appear successful but do not apply — or that wipe out other content - Blog preview images not displaying in the blog listing or post cards - Blog articles disappearing or becoming unclickable after a revert is triggered - New page creation failing with a generic error, even after rephrasing the prompt - Excessive credit usage from repeated failed attempts All of the bugs listed above have been identified and resolved by our engineering team. If you are still experiencing any of these symptoms, the steps below will help you recover your content and stabilise your site. 🧭 Issue 1: Unwanted Header or Menu Changes Editing one section of your site — such as a hero block or footer — can sometimes trigger an unintended change to your site-wide header or navigation menu. 1. Do not run another edit immediately, as this may compound the issue. 2. Open the Version History panel in Website Studio. 3. Locate the version that existed before the unwanted change appeared. 4. Click Restore this version and wait for the confirmation message before navigating away. 5. Verify the header and menu look correct in the live preview before making further edits. If the restore option is greyed out or the header still looks wrong after restoring, contact support via the chat widget (see the end of this article). 🔄 Issue 2: Reverts That Fail Silently or Remove Content In some cases, Website Studio reports that a revert was successful, but the preview still shows the old (unwanted) state. In other cases, reverting one change can unexpectedly delete blog posts or other unrelated content. 1. After any revert, hard-refresh your browser (Ctrl + Shift + R on Windows, Cmd + Shift + R on Mac) and check the live preview again. 2. If content appears missing, go to Version History and look for a version that contains the missing content. 3. Restore that version, then re-apply only the specific change you originally intended. 4. Make one small change at a time and verify it in the preview before proceeding to the next edit. Important: Avoid triggering multiple reverts in quick succession. Each revert call consumes credits and rapid attempts can leave the site in an inconsistent state. 🖼️ Issue 3: Blog Preview Images Not Showing Blog post card images may fail to render in the blog listing page even though the image is correctly uploaded inside the post itself. 1. Open the affected blog post in Website Studio's editor. 2. Check that a featured image (sometimes labelled as a thumbnail or cover image) is set — this is separate from images placed inside the post body. 3. Remove and re-upload the featured image, then save. 4. Publish the change and clear your browser cache before checking the blog listing again. If images still do not appear after completing these steps, the issue may be related to a rendering bug that our team has already patched. Raising it via the chat widget will allow our team to confirm the fix is live on your account. 📄 Issue 4: Blog Articles Disappearing or Returning a 404 Reverting a blog post edit — or even an unrelated site change — can in some cases cause blog posts to become unclickable, return a 404 error, or disappear from the listing entirely. 1. Go to Version History and identify the last version where your blog posts were visible and working. 2. Restore that version. 3. Once restored, navigate to the blog section and confirm all posts are present and clickable. 4. If you need to revert a specific blog post change going forward, make a note of the post content first so you can manually re-enter it if needed, as a safety measure. 🚫 Issue 5: New Page Creation Failing with a Generic Error Attempting to create a new page in Website Studio sometimes fails with a vague error message, and rephrasing the prompt does not resolve it. 1. Refresh the platform and try the page creation again from scratch. 2. Keep the initial prompt short and specific — for example, "Create a blank contact page." 3. If the error persists after two attempts, stop trying. Repeated failed attempts consume credits without producing a result. 4. Contact support using the chat widget so our team can create the page on your behalf or investigate the root cause. 💡 Tips to Prevent Future Issues - Edit one element at a time and confirm it looks correct before moving on. - Check Version History regularly so you always have a clean restore point available. - Avoid bulk or rapid changes in a single session — spacing out edits reduces the risk of conflicts. - Screenshot or export important content (especially blog posts) before running a revert, as a precaution. 💬 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 Website Studio Credits and Trial Extensions

🔍 Overview Some customers have experienced issues with Website Studio — including generation failures, builds that stall near completion, and credits that were not returned after a failed session. If you purchased an annual membership or were promised an extended trial by a Search Atlas instructor following one of these errors, this article explains what happened and how to get it resolved quickly. ⚠️ Known Website Studio Issues Our engineering team has identified and resolved several bugs that caused credit and build problems. Here is a summary of what occurred: - Generation Failed error: A build error blocked all new pages and changes, even after rephrasing prompts. Affected users lost credits without receiving a completed website. - Build stalling at 98%: Website Studio occasionally hung near the end of a build. Clicking Stop left the account in an empty app state, consuming credits with no usable output. - Credit reservation leak: A technical flaw caused credits to be reserved but never properly released after a failed or incomplete generation. - Duplicate prompts in chat: After an AI Agent created or modified a web page, the Website Studio chat displayed multiple copies of the same prompt, causing confusion and unintended credit usage. - 403 access errors via MCP: Users accessing Website Studio tools through the AI Agent MCP connection received permission errors, preventing any work from completing. All of the issues listed above have been fixed or are in the final stages of release. New sessions should work correctly. If you are still seeing any of these problems, please report it immediately using the chat widget. 💳 Why Your Credits May Not Have Been Fully Restored When you upgrade to an annual membership, your credit balance is recalculated based on your new plan. However, if credits were consumed during a failed Website Studio session before your upgrade, those credits may not have been automatically reinstated. This is because the system records usage at the point of consumption, and upgrades do not retroactively reverse prior charges. If an instructor specifically told you that your credits would be restored to their full amount following a Website Studio failure, that commitment is honoured — but it requires a manual review of your account by our support team. ⏳ Where Is My Extended Trial Time? If a Search Atlas instructor promised you additional trial time to compensate for credits lost during a Website Studio malfunction, this extension is applied manually to your account. It is not automatic. Possible reasons it has not appeared yet include: - The request has not yet been passed from the instructor to the technical support team. - Your account was upgraded before the extension was applied, which can shift how remaining time is displayed. - There was a delay between the promise and the internal ticket being created. In any of these cases, our support team can verify the original commitment and apply the extension directly. ✅ Steps to Get Your Credits and Trial Extension Applied 1. Gather your details before contacting support. Have ready: the approximate date the Website Studio failure occurred, the prompt or project name you were working on, and the name or session reference of the instructor who made the promise. 2. Open the chat widget in the bottom-right corner of the Search Atlas platform. 3. Type human teammate to be connected with a member of our team. 4. Share your details — tell the agent that you experienced a Website Studio failure, that credits were not restored after your annual upgrade, and/or that a trial extension was promised by an instructor. 5. Allow the agent to review your account. They will confirm the failed session logs, verify any instructor commitments, and apply the correct credit restoration or trial extension manually. 🚀 Preventing Future Credit Loss in Website Studio Now that the core bugs have been resolved, here are a few best practices to protect your credits going forward: - If a build appears to stall for more than five minutes with no progress, refresh the page before clicking Stop — this may allow the session to recover. - Avoid submitting a new prompt immediately after a Generation Failed message. Wait 30 seconds and reload the page first. - After any failed generation, check your credit balance right away and contact support before starting a new session if the deduction looks incorrect. - Keep a brief note of the date, time, and project name any time you experience an error — this speeds up the account review process significantly. 💬 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 Website Studio Page Creation and Edit Failures

🔍 Overview Website Studio uses a shared component library to build and manage pages. Most editing and page creation issues — including changes that revert after publishing and prompts that fail to generate full pages — are linked to how the AI interacts with these shared components. This article explains the most common causes and how to resolve them. ⚠️ Why Edits Revert After Publishing If you hide the navigation on a specific page in preview mode but the change disappears after publishing, the most likely cause is a conflict between page-level overrides and shared components. What is happening: Navigation bars, headers, and footers are often built as shared components — meaning they apply globally across all pages. When you make a page-level change (such as hiding the navigation), the shared component can override your edit during the publish process. How to fix it: 1. Open Website Studio and navigate to the page where you want to hide the navigation. 2. Instead of hiding the navigation using the page preview toggle, click on the navigation component directly to select it. 3. Look for a Page Overrides or Visibility setting in the right-hand panel — this is the correct place to set page-specific visibility without affecting the global component. 4. Save your changes and publish again. The override will now be respected at the component level rather than the layout level. If the option is not visible in your panel, the component may be locked to global settings. In that case, duplicate the page template and apply a custom navigation setting to the duplicate version instead. ❌ Why Complex Page Creation Prompts Fail When you use the AI chat in Website Studio to generate a full page with multiple sections in a single prompt, the request may partially complete or fail entirely. This is a known limitation of how the AI processes large, multi-step instructions. Common signs of this issue: - The page is created but several sections are missing - The AI chat shows duplicate prompts or repeated processing messages - The page generation appears to complete but the canvas remains blank or incomplete How to work around this: 1. Break your page creation request into smaller, sequential prompts. For example, first ask the AI to create the hero section, then ask for the features section, and so on. 2. Wait for each section to fully render on the canvas before submitting the next prompt. 3. If duplicate prompts appear in the chat panel, refresh the page — do not click the prompt again, as this can trigger duplicate generation requests. 4. After refreshing, check whether the sections were saved. If they were, continue building from where you left off. Important: Image replacement requests within prompts are constrained to shared components only. If you ask the AI to replace an image that is not part of a shared component, the request will be ignored. Use the direct image upload tool in the panel instead. 💡 Best Practices for Stable Page Editing Following these practices will reduce the chance of edits reverting or prompts failing: - Use one prompt per section when building new pages with AI assistance. - Publish after each major change rather than batching multiple edits before a single publish. - Avoid mixing AI-generated edits and manual edits on the same component in the same session — complete one approach before switching. - Check shared component settings before applying page-level overrides to understand what is global versus local. - Refresh the browser if the AI chat shows multiple or repeated prompts — do not re-submit the same request. 🔄 When to Refresh vs. When to Re-Submit Understanding when to refresh the page versus when to re-submit a prompt will save time and prevent duplicate content. - Refresh if: the AI chat shows multiple identical prompts, the canvas is not updating, or the page appears frozen. - Re-submit only if: you refreshed, confirmed no content was generated, and the canvas is still empty. - Do not re-submit if content was partially created — add missing sections with new, specific prompts instead. 🆘 Still Having Trouble? If your edits continue to revert, prompts keep failing after following these steps, or you are experiencing issues not covered here, our team can investigate your specific setup. 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 Disappearing Blog Posts After Website Studio Edits

🔍 What Is Happening? When you ask the AI assistant in Website Studio to make a visual change — such as removing a duplicate hero image, adjusting a layout, or modifying a section — the platform may trigger a container rebuild. During this process, dynamically generated routes, including published blog articles, can be stripped from your live site. Your content is not permanently deleted, but the routes that make those pages publicly accessible are removed until they are republished. ⚠️ Why Does This Happen? Website Studio serves blog articles through dynamic routes that are registered at publish time. A container rebuild essentially resets the site's routing layer to match the current saved state of your pages. If the rebuild does not re-register your blog routes automatically, those articles will disappear from the live site even though the underlying content still exists inside the platform. This is a known behaviour that our engineering team has addressed in recent releases, but certain edge-case edits may still trigger it. ✅ How to Check Whether Your Posts Still Exist 1. Open Website Studio from the left navigation menu. 2. Click Blog or navigate to your blog management section. 3. Review the list of articles. Posts that were previously published will still appear here with a Published status even if they are no longer live on the site. 4. If you can see the articles in this list, your content is intact and can be restored quickly. 🔄 How to Restore Disappeared Blog Posts 1. Inside Website Studio, go to your Blog section and locate the affected articles. 2. Open each affected article individually. 3. Click Unpublish (if the option is available) and then click Publish again. This re-registers the route on your live site. 4. If the Unpublish option is not shown, click Publish directly to force the route to be re-created. 5. Wait up to 5 minutes for the changes to propagate and then visit the live URL of each article to confirm it is accessible. 6. Repeat this process for every article that disappeared. 🛡️ How to Prevent This in the Future - Note your published articles before requesting AI edits. Keep a quick record of your live blog URLs so you can immediately identify if any go missing after a change. - Request one small change at a time. Larger or more complex AI instructions are more likely to trigger a full container rebuild. Breaking requests into smaller steps reduces the risk. - Avoid structural edits while actively publishing content. If you are in the middle of a content publishing session, complete and confirm all posts are live before asking the AI to make layout or design changes. - Verify your live site after every AI-assisted edit. After any change is applied, do a quick check of your blog index page to confirm all published articles are still visible. - Use the Blog section in Website Studio as your source of truth. The publish status shown inside the platform reflects whether your content exists, not necessarily whether the live route is active. A re-publish step is always safe to perform. 📋 What to Tell Support If Posts Cannot Be Restored If republishing does not restore your articles, or if the articles no longer appear in your Blog section inside Website Studio, gather the following information before contacting support: - The titles or URLs of the missing blog articles. - The date and approximate time the content disappeared. - A description of the AI edit you requested immediately before the content disappeared. - Any error messages you saw on the live URL (for example, a raw XML message or a 404 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.

🖥️ Website Studio Duplication and Cloning Limitations

🔍 Overview Website Studio lets you build and manage landing pages and full sites inside Search Atlas. However, several customers have run into friction when trying to duplicate pages for ad campaigns, clone projects for new domains, or migrate content between projects. This article explains what is currently supported, what limitations exist, and how to work around them. 📋 What You Can and Cannot Do Right Now Before attempting any duplication or cloning workflow, review what is currently available: - Duplicate a page within the same project: Supported for most standard pages. Use the page management menu inside your project. - Clone a PPC landing page (clone_ppc): Available, but affected by a known bug in roughly 15–20% of projects (see below). - Copy or migrate a page to a different project: Not currently supported. There is no native option to move or copy a page between two separate Website Studio projects. - Reuse a site for a different custom domain: Not directly supported. Customers who need this must use an export and re-import workflow, which adds manual steps. ⚠️ Known Issue: Duplication Stops Working After Setting Up a Custom Domain (CNAME) Some customers notice that the duplication option becomes unresponsive or disappears after connecting a custom domain via CNAME. This is a known platform behaviour tied to how projects are locked once a custom domain is attached. Here is what to do: 1. Disconnect your custom domain temporarily from the project settings. 2. Perform the page duplication you need. 3. Reconnect your custom domain once the duplicate is ready. Note: If the duplication option is still missing after disconnecting the domain, clear your browser cache and reload the platform before trying again. 🐛 Known Issue: Clone PPC Pages Showing "Not Saved to History" When cloning a PPC landing page using the clone_ppc option, you may see an alert that says "Not saved to history" even after making edits. This is caused by a silent failure during the background save process and affects approximately 15–20% of clone_ppc projects. To reduce the risk of losing work: - After cloning, make a small test edit and confirm the history panel updates before continuing. - If the history does not update, close the editor, reopen the cloned page, and try again. - Avoid making large batches of edits until the history shows at least one saved entry. Our engineering team has resolved the underlying cause of this issue. If you are still experiencing it, contact support using the chat widget below. 🔄 Workaround: Duplicating Landing Pages for Multiple Ad Campaign Themes If you need separate landing pages for different ad campaign themes, follow these steps using the current toolset: 1. Open your Website Studio project and navigate to Page Management. 2. Hover over the page you want to duplicate and select Duplicate from the options menu. 3. Rename the duplicated page to reflect the campaign theme (for example, summer-sale-landing or brand-awareness-v2). 4. Edit the duplicated page content to match the new campaign theme. 5. Repeat for each additional theme you need. Important: All duplicated pages will live inside the same project. If you need each page on a completely separate domain, see the section below on using multiple projects. 🌐 Workaround: Reusing a Site Design Across Multiple Domains There is currently no one-click option to attach the same site to a second domain. Until this is natively supported, use the following approach: 1. In your existing project, export your site or page using the export option in project settings. 2. Create a new Website Studio project for the second domain. 3. Import the exported file into the new project. 4. Connect your second custom domain via CNAME in the new project's domain settings. This process requires manual effort for each additional domain. We recognise this is not ideal and the team is working on a more streamlined solution. 🗺️ What Is Coming The following improvements are in progress or planned based on customer feedback: - Cross-project page migration: The ability to copy or move pages between separate Website Studio projects is under active development. - Simplified multi-domain reuse: A workflow that removes the need for manual export and re-import when attaching a project to a new domain. - Clone stability improvements: Further fixes to ensure clone_ppc history saving is reliable across all projects. We will update this article as these features become available. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Website Studio Instant Indexing Quota Errors

🔍 Overview Some customers see the message "Indexing quota reached — upgrade to submit more" inside Website Studio's Instant Indexing setting, even when they have URL indexer credits available. This article explains why this happens and what steps to take to resolve it. ⚙️ Why This Error Appears The quota error is typically caused by a display or sync issue between your available credits and the quota counter shown in Website Studio. Known causes include: - Phantom quota consumption: In some cases, the system may show a used quota (for example, 8.2 out of 60) even when no indexing activity has taken place on your account. - Incorrect 0/0 display: The quota banner may show 0/0 credits despite your account having active Universal Credits or URL indexer credits allocated. - Credit sync delay: After purchasing or receiving credits, there can be a short delay before Website Studio reflects the correct available balance. - Display inconsistency across tools: Credits visible in other tools like OTTO or Site Explorer may not immediately appear in Website Studio due to a quota display inconsistency. These are known platform issues that have been identified and resolved at the infrastructure level. However, individual accounts may occasionally still experience a stale or incorrect quota display. ✅ Steps to Resolve the Error 1. Refresh your browser. Close and reopen the Website Studio tab, or perform a hard refresh (Ctrl + Shift + R on Windows, Cmd + Shift + R on Mac) to force the platform to reload your current credit balance. 2. Check your credit balance. Navigate to your account's billing or credits section and confirm that URL indexer or Universal Credits are listed as active and available. 3. Wait a few minutes and retry. If you recently topped up credits or made changes to your plan, allow up to 5–10 minutes for the quota to sync, then return to Website Studio and try again. 4. Log out and log back in. Signing out of Search Atlas and signing back in can force a fresh session that correctly loads your credit balance. 5. Try submitting the URL again. After refreshing or logging back in, attempt to use Instant Indexing once more. In many cases, the error clears itself once the display syncs with your actual credit balance. 📊 Understanding Your Indexing Quota Your Instant Indexing quota in Website Studio is tied to your URL indexer credits. Here is how credits work: - Credits are allocated based on your current plan or any Universal Credits applied to your account. - The quota resets on a daily basis, so usage from the previous day should not carry over and block new submissions. - If your quota correctly shows as fully used and you need to index more URLs, you can top up by upgrading your plan or purchasing additional URL indexer credits from your account dashboard. 🚨 When the Error Is a Bug If you have confirmed that credits are available, you have refreshed and logged back in, and the error persists, this is likely a platform-side display bug affecting your account. This is not caused by anything you have done wrong, and it does not mean your credits have been lost. In this situation, do not purchase additional credits before reaching out, as your existing credits should be sufficient once the issue is corrected on the platform side. 💬 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. When you reach out, please share the following to help us resolve your issue faster: - A screenshot of the quota error message in Website Studio - A screenshot of your current credit balance from your account dashboard - The URL(s) you were trying to submit for indexing - The date and time you first noticed the error

🛠️ Fix Website Studio Edits, URLs, and Author Metadata

🗺️ Overview This article covers the most common Website Studio editing tasks: forcing edits on pillar pages the AI Agent redirects away from, correcting URL slugs, updating or removing author metadata, cloning content between URLs, removing legacy URLs from the database, and resolving dead URLs in your sitemap. ✏️ Edit a Pillar Page When Website Studio Redirects You Elsewhere Website Studio's AI Agent occasionally suggests alternative pages instead of opening the pillar page you selected. This is a known routing issue that has been resolved in the latest platform update. If you still experience it, follow these steps to force the correct page open: 1. In the left navigation, click Website Studio. 2. In the page list, locate the pillar page you want to edit. 3. Right-click the page title and select Open in editor, or click the pencil icon directly on the page row — do not use the AI Agent chat to navigate. 4. If the editor still opens the wrong page, refresh the browser tab and repeat step 3. The direct icon click bypasses the agent routing. Note: If the site-wide header dropdown reverts your changes after saving, save the page first, then refresh the editor before making additional edits. This prevents the revert behaviour linked to a previous header-editing bug. 🔗 Correct a URL Slug (Change '-blog-' to '/blog/') Malformed slugs containing -blog- instead of /blog/ can hurt crawlability and internal linking. To correct a URL slug: 1. Open the page in the Website Studio editor. 2. Click the Publish / Settings button in the top-right corner of the editor. The slug, author, category, and tags fields will auto-fill from the existing article data. 3. In the URL Slug field, replace the incorrect segment. For example, change your-site.com-blog-post-title to your-site.com/blog/post-title. 4. Click Save or Update. Website Studio will update the canonical URL for that page. 5. Repeat for each affected URL. Set up a 301 redirect from the old slug to the new one to preserve SEO equity (see the Redirects section in Website Studio settings). 👤 Update or Remove Author Metadata To replace an existing author (for example, removing Marcus Eriksson and replacing with Nestor Vazquez): 1. Open the page in the Website Studio editor. 2. Click Publish / Settings. 3. In the Author field, clear the current name and type the replacement author's name. If your BrandVault is configured, the correct author options will appear as suggestions. 4. Click Save or Update. 5. To apply the same author change across multiple pages at once, contact support using the chat widget (see below) — bulk author reassignment requires a platform-side action. 📋 Clone Content Between Two URLs If you need to copy the content of one page and publish it under a different URL: 1. Open the source page in the Website Studio editor. 2. Select all content in the editor body (Ctrl+A / Cmd+A) and copy it (Ctrl+C / Cmd+C). 3. Navigate to the destination URL's page, or create a new page with the correct slug. 4. Paste the content into the editor body. 5. Update the slug, author, category, and tags in Publish / Settings as needed. 6. Click Publish. The original page remains unchanged. 🗑️ Delete Legacy URLs from the Database Legacy URLs that are no longer needed should be removed to keep your site database clean and avoid duplicate-content signals: 1. In Website Studio, go to All Pages. 2. Locate the legacy URL you want to remove. Use the search bar to find it by slug or title. 3. Click the three-dot menu (⋯) on the page row and select Delete. 4. Confirm the deletion in the prompt. The URL will be removed from your database. 5. Important: Before deleting, ensure a 301 redirect is in place from the old URL to the correct destination to avoid broken links and ranking loss. 🗺️ Fix Dead URLs in Your Sitemap Dead URLs in your sitemap prevent search engines from crawling your live content efficiently. To resolve them: 1. In Website Studio, go to Settings > Sitemap. 2. Review the list of URLs included in the sitemap. Dead URLs are typically pages that have been deleted or had their slugs changed without a redirect. 3. For each dead URL, either restore the page, update the slug to match the live version, or add a 301 redirect to the correct live URL. 4. Once the underlying pages or redirects are in place, click Regenerate Sitemap. The dead URLs will be replaced with their correct live counterparts. 5. Resubmit the updated sitemap to Google Search Console to prompt a fresh crawl. 💡 Tips to Avoid These Issues in the Future - Always set URL slugs at the time of page creation — changing them later requires redirect management. - Keep your BrandVault author profiles up to date so the auto-fill feature populates the correct author on every new page. - Before deleting any URL, check your internal links and set up a redirect. - Use the direct editor icon in the page list instead of the AI Agent chat when editing specific pages, until the agent routing is fully stabilised. 🆘 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Duplicate H1 Tags in Website Studio

🔍 Overview Some websites published through Website Studio contain a hidden duplicate H1 tag inside the index.html file. This issue is not caused by your content or settings — it is a known platform-level bug that affects published sites. The duplicate H1 tag cannot be seen or removed from within the Website Studio editor, but it is detectable by SEO audit tools, including the built-in Search Atlas SEO audit. Our engineering team has identified this issue. This article explains the impact of the bug, what you can do right now, and how to get hands-on help if you need it. ⚠️ What Is the Impact? Having two H1 tags on a single page can negatively affect your site in the following ways: - SEO audit failures: Your site will fail the H1 check in the Search Atlas SEO audit and in third-party tools, even if your visible page content looks correct. - Search engine confusion: Search engines use the H1 tag to understand the primary topic of a page. A duplicate can dilute relevance signals and hurt rankings. - Launch blockers: If you are using an SEO checklist as part of your site launch process, this error may prevent you from confidently publishing. 📋 Steps to Take Right Now 1. Confirm the duplicate H1 exists. Run a Search Atlas SEO audit or use a browser extension such as a heading checker to verify there are two H1 tags on your published page. This helps rule out false positives from other tools. 2. Check that your editable H1 is correct. Open your project in Website Studio and confirm that only one H1 heading appears in your visible page content. If you see two H1 headings in the editor itself, remove the duplicate manually before proceeding. 3. Republish your site. After confirming your editable content has only one H1, republish your site using the publish option available in Website Studio. 4. Re-run the SEO audit. Check whether the duplicate H1 error is still present after republishing. If it is, the hidden tag in the generated index.html is the cause, and the issue exists at the platform level rather than in your editable content. 5. Contact support for assistance. If the error persists after republishing, reach out to our team with your project name and the SEO audit report showing the duplicate H1 error so we can investigate further. 💡 Frequently Asked Questions Can I fix the index.html file myself? The generated index.html file is not directly editable from within the Website Studio interface. You will need a member of our team to assist with resolving the issue at the platform level. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Website Studio Multi-Page Editing and AI Content Issues

🔍 Overview When working on a multi-page project in Website Studio, two questions come up frequently: does uploading an HTML file to one page affect the rest of the project? And why does the AI agent rewrite or invent content instead of using the exact wording you provided? This article explains both behaviours and shows you how to get the results you expect. 📄 How HTML File Uploads Work in Multi-Page Projects HTML file uploads in Website Studio are scoped to the page you are editing. If you experience unexpected changes appearing on pages you did not intend to modify, this is a known issue that requires investigation by our team. If you notice unexpected changes appearing on pages you did not intend to edit, please reach out to our support team with your project name, the page(s) affected, and the approximate time the issue occurred. 🤖 Why the AI Agent Rewrites Your Content Instead of Using Your Exact Wording The AI agent in Website Studio may rewrite or adapt content you provide rather than preserving your exact wording. This is a known behaviour, particularly when providing legal, compliance, or brand-specific content that must remain exact. If the AI continues to rewrite content despite your instructions, please contact support with your project name, the prompt you used, and an example of the content that was changed so our team can investigate further. 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 Common Website Studio Bugs Quickly

🔍 Overview Some Website Studio users have reported a set of related issues: the AI agent making unwanted changes (such as adding or modifying navigation menus), credits being consumed while errors are being corrected, and blog preview images failing to display correctly. This article explains why these issues occur, what has already been fixed, and what steps you can take right now. ⚙️ How to Access Website Studio To open Website Studio, go to the left sidebar and select Website Studio, or navigate directly to /website-studio in your platform URL. 🐛 Known Issues and Current Status The following bugs have been identified and addressed by our engineering team: - Navbar and visual layout changes not applying: Website Studio was reporting successful updates in the chat, but the navbar and layout were not actually changing on the page. This bug has been resolved. - AI agent misinterpreting prompt instructions: The agent was occasionally making unintended changes — such as adding unwanted menus — when it misread the intent of a prompt. This bug has been resolved. - Blog "Read More" links not redirecting correctly: Links on blog preview cards were not routing users to the correct individual blog pages. This bug has been resolved. - Legacy credit quota displayed in UI: Website Studio was showing an outdated credit counter instead of your Universal Credits balance, which caused confusion about how many credits were being used. This bug has been resolved. - Unable to create a new page after rephrasing a prompt: In some cases, rephrasing a prompt to create a new page caused the action to fail entirely. This fix is currently in development. 💳 Why Did My Credits Drain Unexpectedly? Each prompt you send to the Website Studio AI agent consumes credits — including prompts sent to correct a previous mistake made by the agent. If the agent applied an unwanted change (such as adding an unintended menu), any follow-up prompts you used to undo or rephrase that action also counted against your credit balance. Now that the prompt misinterpretation bug has been resolved, the agent should follow your instructions more accurately, reducing the need for corrective prompts. Here are a few tips to help protect your credits going forward: - Be specific in your prompts. Clearly describe only the element you want changed and its exact location on the page. - Review changes in preview before confirming. Check the visual output before finalising any update. - Undo changes immediately if something goes wrong. Acting quickly reduces the number of corrective prompts needed. 🖼️ Blog Preview Images Not Displaying If blog post thumbnail or preview images are not appearing on your blog listing page, try the following steps in order: 1. Check that an image is assigned to each blog post. Open the blog post in the editor and confirm a featured image has been uploaded and saved. 2. Clear your browser cache and hard-reload the page. Press Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac) to force a fresh load. 3. Re-save the blog post. Open the post, make a minor edit (such as adding a space), save it, then undo the edit and save again. This can trigger the image to re-render. 4. Re-publish your website. After making any changes, use the Publish button to push updates live. Images sometimes only appear after a full republish. 5. Test in a different browser or incognito window. This rules out a local caching issue on your device. If blog images are still not displaying after completing all steps above, this may indicate a deeper rendering issue that our team needs to investigate directly. ✅ Best Practices to Avoid These Issues - Use clear, single-action prompts. Avoid combining multiple instructions in one message (e.g. "change the header colour and add a new page and update the footer"). - Save your work frequently and use version history if available before making large changes. - If the agent applies an unwanted change, use the undo option immediately rather than sending multiple corrective prompts. 💬 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.

Website Studio Editing Scope and Prompt Reliability

🗂️ Overview This article covers two common questions about Website Studio: how uploading an HTML file affects your project pages, and why the AI agent sometimes rewrites content or skips specific instructions. If you are experiencing unexpected behavior in either of these areas, please reach out to our support team so we can investigate your specific case. 📄 HTML File Uploads: Which Pages Are Affected? When you upload an HTML file to a specific page inside your Website Studio project, the upload is scoped to the individual page you have selected. If you are seeing changes appear on pages you did not intend to modify, our team will need to review your project to identify the cause. When contacting support about an unexpected upload result, please have the following ready: - Your project name and the specific page you uploaded the HTML file to. - A description of which other pages were affected and how. - The approximate time the upload occurred. - A copy or description of any prompts that were active at the same time as the upload. ⚠️ AI Agent Rewriting Content or Ignoring Prompts If the AI agent is rewriting sections of your page content unexpectedly or not executing your instructions as written, this is a known area of investigation. The behavior can vary depending on how prompts are structured and what changes are being requested. General guidance that may help while we investigate: - Try breaking large or complex editing tasks into smaller, focused prompts submitted one at a time. - Avoid combining many unrelated instructions in a single prompt. - Review the results after each prompt before sending the next set of edits. If the issue persists, please escalate to our support team with the following information ready: - Your project name and the specific page or pages where the behavior occurred. - The exact prompt or prompts you submitted. - A description of what you expected to happen versus what the AI agent actually did. - The timestamp of the editing session. 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 Website Studio Bugs and Common Issues

Overview Some customers have reported a combination of issues when using Website Studio: pages not appearing in Google Search Console, credits being consumed for non-AI edits, and blog article preview images not displaying. This article explains what to have ready when contacting our team so we can investigate and resolve these issues for you. Pages Not Indexed in Google Search Console If your Website Studio pages are not showing as indexed in Google Search Console, this may be related to a build or publishing issue on your site, or simply a delay in Google's crawling process, which can take days or weeks for newly published pages. What to have ready when escalating: 1. Your project name in Website Studio. 2. The exact error message displayed, if any. 3. The timestamp of when the issue was first noticed. 4. Confirmation of whether your sitemap has been submitted in Google Search Console and whether it shows any errors. 5. The URLs of any specific pages that are not being indexed. Credits Being Consumed for Non-AI Edits Some customers have reported that visual edits in Website Studio — such as layout, colour, or text changes that do not involve AI generation — are unexpectedly consuming credits. What to have ready when escalating: 1. Your project name in Website Studio. 2. A description of the specific edit action you performed (for example, resizing an image or changing a font colour). 3. The number of credits deducted and approximately when the deduction occurred. 4. Your current credit balance, which you can check within your account. Our team will review your account and arrange a credit recovery if appropriate. Blog Article Preview Images Not Displaying If images in your blog article previews are not displaying correctly in Website Studio, this may be a known display or publishing issue. Contact our team with the details below so we can investigate. What to have ready when escalating: 1. Your project name in Website Studio. 2. The URL or title of the affected blog article(s). 3. A description of what you see instead of the image (for example, a broken image icon or blank space). 4. The timestamp of when the issue started. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Blog Articles Deleted or Repositioned in Website Studio

🔍 Overview After certain platform updates or fix deployments, you may notice unexpected changes to your blog articles in Website Studio. Common symptoms include: - Blog articles disappearing from your blog page - New articles appearing at the bottom of the list instead of the top - Duplicate blog posts created when editing and republishing an article - Only one blog article showing at a time instead of all published posts - Articles deleted in Content Genius remaining visible in Website Studio, or vice versa These issues are linked to resolved platform bugs affecting how Content Genius and Website Studio sync blog content. This article explains what caused these issues and what steps you can take to restore your blog to the correct state. ⚙️ What Caused These Issues Several interconnected bugs affected the way blog articles were published, updated, and deleted between Content Genius and Website Studio. Here is a plain-language summary of each: - Only one blog kept at a time: A bug caused Website Studio to replace all existing blog posts with only the most recently published article, removing all previously published posts from view. - Republishing created a duplicate instead of updating: When you edited and republished an existing article in Content Genius, Website Studio generated a brand-new post with a new URL instead of updating the original post in place. This led to duplicate entries and broken links. - Delete actions not syncing correctly: Deleting a blog article in Content Genius did not always remove it from Website Studio, and delete actions on synced articles were not reliably carried through. This has now been corrected. - New articles appearing at the bottom: Related to ordering logic, newly published articles were appended to the bottom of the blog list rather than displayed at the top in reverse-chronological order. All of the above bugs have been resolved by the Search Atlas engineering team. However, if your blog content was affected before the fixes were deployed, you may need to take a few manual steps to restore it. ✅ How to Restore Your Blog Articles Follow these steps to check and correct the state of your blog articles in Website Studio after these fixes were deployed. 1. Audit your blog page in Website Studio. Navigate to Website Studio and open your blog page. Note any articles that are missing, duplicated, or out of order. 2. Cross-reference with Content Genius. Go to Content Genius and review your published articles list. Confirm which articles should be live and compare against what is currently showing in Website Studio. 3. Remove duplicate posts. If you see duplicate entries caused by republishing, identify the duplicate (usually the newer URL created during re-publish) and delete it from Website Studio. Keep the original post to preserve its URL and any backlinks pointing to it. 4. Republish missing articles. For any articles that are no longer visible in Website Studio but still exist in Content Genius, open each article in Content Genius and use the Send to Website Studio option to republish it. The fix ensures each article now updates in place rather than creating a new post. 5. Check article ordering. After republishing, verify that your blog list displays articles in reverse-chronological order with the newest post at the top. If ordering still appears incorrect, try reordering posts manually within the Website Studio blog settings. 6. Clear your browser cache and reload. Some display issues persist due to cached page data. Clear your cache and reload your blog page to confirm the final state reflects your changes. 🚫 How to Avoid These Issues Going Forward Now that the underlying bugs are resolved, your Content Genius and Website Studio blog workflow should behave reliably. Keep these best practices in mind: - Edit articles in Content Genius before republishing. The platform now updates the existing Website Studio post in place, so you no longer need to worry about duplicates being created. - Use the delete action consistently. Deleting an article in Content Genius will now correctly remove it from Website Studio as well. Always confirm the deletion on both sides if you want the post fully removed. - Avoid manually duplicating posts as a workaround for editing — this is no longer necessary and will create unintended duplicate URLs. 💬 Need Additional Help? If your blog articles are still missing, out of order, or duplicated after following the steps above, our team can investigate your specific account and restore content where possible. 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 and Scaffold URLs in Website Studio

What Are Duplicate and Scaffold URLs? When you edit pages inside Website Studio, the platform can sometimes auto-generate additional URLs that were never meant to go live. These fall into two categories: - Scaffold URLs — temporary placeholder pages created during the editing or publishing process (for example, /Page1, /Page7). - Duplicate URLs — unintended copies of existing pages, often with incorrect slug structures (for example, /blog-slug/blog-slug or a mismatched /home URL). Both types can appear in your live site and sitemap if they are not removed, which can harm your crawl budget and create confusing redirect chains. Why Does This Happen? This is a known platform bug in which Website Studio auto-generates duplicate URLs and scaffold pages during editing sessions. The extra URLs are created as part of the editing process and are not automatically discarded, causing them to appear on your live site and in your sitemap. What to Have Ready When You Escalate Because this is a backend bug, our team will need to investigate and resolve it on your behalf. To help us act quickly, please have the following information ready before reaching out: - Your project or site name — the exact name as it appears in your Search Atlas account. - The affected URLs — list the specific duplicate or scaffold URLs you have identified (for example, /Page1, /blog-slug/blog-slug). - When you first noticed the issue — an approximate date and time, and whether it followed a specific editing action. - Any error messages or unexpected behavior — copy the exact text of any error messages you see. Do not attempt to manually delete or redirect the affected URLs until our team has reviewed them, as doing so before the underlying cause is identified could create additional 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 Favicon Issues in Website Studio

🔍 Overview A favicon is the small icon that appears in browser tabs and bookmarks for your website. Some Website Studio users have reported that the favicon setting appears missing, that favicon uploads fail, or that favicon changes do not reflect on their live site. This article explains what to expect and how to get the right support to resolve this. ⚠️ Known Issue: Favicon Update and Sync Problems There is a known issue in Website Studio where favicon changes may not appear or sync correctly. This can affect sites in various states — including sites built from scratch — and may present as a missing favicon option, a failed upload, or an update that does not reflect on the live site after saving. Because the root cause and resolution steps vary depending on your specific setup, this issue requires investigation by our support team. Our team will need to review your site configuration to identify what is causing the problem and apply the appropriate fix. 📋 What to Have Ready When You Contact Support To help our team resolve your favicon issue as quickly as possible, please have the following information ready before reaching out: - Your site/project name in Website Studio - A description of the issue — for example, whether the favicon option is missing, the upload is failing, or the favicon is not appearing on the live site after saving - When the issue started — include an approximate date and time if possible - Steps you have already tried — for example, clearing your browser cache or testing in a private/incognito window - Any error messages you have seen, copied exactly as displayed - Screenshots or a screen recording if available, showing 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 Website Studio Blog Dropdown URLs

🔍 What causes the issue Website Studio may report that a task is complete when the requested change was submitted but the published site still contains an incorrect link. Blog dropdown items can sometimes redirect to the main blog listing page instead of the selected article, or stop working after new posts are published. URL conflicts can also occur when a blog post uses the same path as a WordPress category or another existing page. 🧭 Check the published dropdown 1. Open the published website in a new browser tab. 2. Open the blog dropdown menu. 3. Click each item and compare the destination URL with the intended blog post URL. 4. Check the page content, not only the address. Confirm that the selected article loads and is not replaced by the blog listing page. ⚙️ Correct the Website Studio request 1. Open Website Studio from the left sidebar, or go to /website-studio. 2. Submit a clear instruction identifying the exact dropdown label, intended destination URL, and expected page content. 3. Ask Website Studio to update the published navigation and preserve the existing article URL where possible. 4. Wait for the task to finish, then open the published site and test the link manually. Use the full URL in your request when possible. Avoid vague instructions such as “fix the blog menu,” because they may not identify which dropdown item or destination needs changing. ✅ Verify the result - Test the dropdown on desktop and mobile layouts. - Confirm every item opens the correct article, not the blog listing page. - Refresh the page or use a private browser window to avoid seeing an older cached version. - Check that the article content matches the selected menu item. - Test the link again after publishing any additional blog posts. 🚧 Prevent URL conflicts Use unique URL paths for blog posts. Do not reuse paths assigned to WordPress categories, pages, or other site sections. If a new post causes an existing dropdown item to open the wrong page, give Website Studio the conflicting URLs and request a unique post path and corrected navigation link. 💡 When the completion message is inaccurate A completion message confirms that Website Studio processed the request; it does not replace checking the live result. Always verify the published URL, destination page, and content after a task reports completion. If the change is still missing, submit a follow-up request that includes the exact menu label, current URL, intended URL, and a link to the published site. 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.

🛠️ Website Studio Scroll Bug and Credit Reset

🔍 Overview A bug in Website Studio caused homepage sections to become hidden or disappear when scrolling through pages. In some cases, credits were consumed without the issue being resolved. This article explains what happened, confirms the fix, and tells you how to request a credit reset if you were affected. ⚙️ What Caused the Issue This was a confirmed platform-level scroll animation bug in Website Studio where sections on a homepage would disappear or become hidden after scrolling. The issue was not caused by anything in your project settings or content. A fix was deployed to production by the Search Atlas engineering team. ✅ Confirm the Fix Is Applied 1. Open the platform and navigate to Website Studio. 2. Open the affected website and preview the homepage. 3. Scroll through all homepage sections to confirm they remain visible and behave as expected. 4. If sections are still disappearing on scroll, your browser cache may be serving an older version of the page — try a hard refresh (Ctrl+Shift+R on Windows or Cmd+Shift+R on Mac) or open the preview in a private/incognito window. 💳 Request a Credit Reset If You Were Charged If credits were consumed while the platform was experiencing this bug, those credits should not count against your account. If your credits were not restored automatically, follow the steps below. 1. Check your current credit balance in your account to establish a baseline before contacting support. 2. Note roughly how many credits were consumed during the affected period so you can share this with the support team. 3. Contact our support team and let them know you were affected by the Website Studio scroll bug and provide the number of credits used so they can process a reset for your account. 🚫 What to Do If the Bug Reappears The engineering fix is live in production, so the scroll issue should not recur. However, if you notice homepage sections disappearing again after the fix: - Take a screenshot or screen recording of the behavior to share with support. - Reach out to our support team so the issue can be escalated to engineering promptly. 📋 Summary The Website Studio scroll bug that caused homepage sections to disappear has been fixed at the platform level. Credits consumed during this platform bug were eligible for a reset — contact our support team if yours were not automatically restored.

Website Studio Import Edits and Project Transfers

🔍 Overview If you have imported a project into Website Studio and cannot make visual edits on newly created pages, or if you need to transfer a published Website Studio site to a different user account, this article explains what to expect and the steps to resolve each situation. ⚙️ Visual Editing Issues on Imported Projects After importing a project into Website Studio, you may find that newly created pages within that project do not allow visual edits. This is a known platform issue that has been identified and resolved by the engineering team. Follow these steps to resolve the issue: 1. Confirm you are working inside the correct imported project in Website Studio. 2. Hard-refresh your browser (Ctrl + Shift + R on Windows, Cmd + Shift + R on Mac) and reopen the affected page. In many cases the engineering fix will already be active for your account and visual editing will be restored immediately after the refresh. 3. If visual editing is still unavailable after refreshing, log out of Search Atlas completely, log back in, and reopen the affected page — this forces your session to pick up the latest platform state. 4. If the issue persists after logging out and back in, open a support chat and provide the name of the affected project and the specific page URL. The specialized team will verify that the engineering fix has been applied to your account and manually trigger it if needed, restoring full visual editing capability. 🔄 Transferring a Published Website Studio Site to Another Account Transferring a published Website Studio project to a different user account requires a backend action by the Search Atlas team. To submit your transfer request as efficiently as possible, follow these steps: 1. Gather the exact name of the Website Studio project you want transferred. 2. Confirm the destination account email address or username the project should be moved to. 3. Open a support chat and send a message with the subject line Website Studio Transfer Request, including the project name and destination account details. 4. The team will action the transfer on the backend and send you a confirmation message once it is complete. No additional steps are required from you after submitting these details. Providing the project name and destination account upfront in your first message allows the team to complete the transfer in a single interaction without back-and-forth. 💬 Contact Support For both of the issues above, reach out to the Search Atlas support team via the live chat widget inside your Search Atlas dashboard. Describe your situation and include the relevant project name and account details so the team can assist you as quickly as possible. If you need further assistance, please contact our support team via the live chat widget in your Search Atlas dashboard.

Website Studio AI Agent Creating Rogue Pages

🔍 What Is This Issue? In some cases, the Website Studio AI agent may behave unexpectedly — publishing content automatically, generating repeated pages you did not request, or appearing to loop in a way you cannot stop. Pages created during this state may persist even after you attempt to remove them. This is a known issue that has been reported by other users and has been escalated to the engineering team for investigation. ✅ What To Do If You Are Experiencing This If you see unexpected pages, repeated entries, or content you did not create in Website Studio, follow these steps to stop the behaviour and help the team resolve it: 1. Stop using the AI agent immediately. Do not submit new prompts while the issue is active. Additional instructions may trigger further unintended page creation. 2. Document what you see. Take screenshots of the unexpected pages, including their titles and URLs if visible. This will help the support team investigate and clean up the affected records on the backend. 3. Do not manually delete the rogue pages yet. Manual removal on your end may not fully resolve the issue, as the underlying records may need to be cleared by the support team. Wait for confirmation before removing anything. 4. Identify the affected pages. Review your Website Studio project and confirm which pages were created unexpectedly. Note the exact page names and the approximate time they were generated — the support team will need this information to locate and remove the affected backend records for your specific project. 5. Contact our support team with the screenshots, page names, and timestamps you collected. Our team can access your project on the backend, remove the rogue page records, and confirm when it is safe for you to continue using the AI agent. If you don't hear back promptly, you can also reach us by replying to any previous support email or starting a new conversation through the support messenger. 💡 Tips To Avoid Similar Issues - Use clear, specific prompts. Vague or overly complex instructions can cause the AI agent to misinterpret your intent. Describe your goal as precisely as possible — for example, specify whether you want to edit an existing section or create a new page. - Review AI actions before confirming. After the agent proposes changes, review the summary carefully before approving, especially if it references page creation when you only intended to edit a section. - Work on one task at a time. Avoid sending multiple layered instructions in a single prompt. Break complex tasks into smaller, sequential steps. 🆘 Need Further Help? If you need further assistance, please don't hesitate to reach out to our support team and we will be happy to help.

🛠️ Fix Website Studio AI Agent Errors and Restore Projects

Overview Website Studio's AI agent has experienced several bugs that caused section creation to fail, blog posts to be misclassified, image overlays to persist despite removal requests, and content to be lost during reverts. This article explains what happened and what steps you can take if you are still experiencing issues. What Was Causing These Errors Engineering investigated and identified several underlying issues in the Website Studio AI agent related to: - Section and page creation failures: The AI agent encountered errors when attempting to create sections or pages. - Blog misclassification: When asked to create a standalone page, the agent may have incorrectly handled the request, resulting in no page being created. - Overlay persistence: Gradient or image overlays persisted in projects even after users instructed the AI agent to remove them. - Project restoration: Content was lost or projects reached an unrecoverable state in some cases. If you are currently experiencing any of these issues, follow the steps below based on your situation. If the steps do not resolve your issue, please contact our support team so we can investigate the specific state of your account and project. What You Should Do Now If you were affected by any of these bugs, follow the steps below based on your situation. Restore a Project If content was lost or your project reached an unrecoverable state, try the following steps to recover your work: 1. Open Website Studio and navigate to the affected project. 2. Look for a version history or restore option within the project settings to revert to a previous saved state. 3. If you previously downloaded a backup file of your project, use that file to re-import or restore the project directly in Website Studio. 4. If no prior backup or version history is available, document your project name and the approximate date when the content was last correct, then contact our support team with those details so our team can review what recovery options are available for your account. Gradient Overlays That Cannot Be Removed If your Website Studio project has a gradient or image overlay that persists even after instructing the AI agent to remove it, try the following steps before contacting support: 1. Open the affected page in Website Studio's editor. 2. Select the section or element that contains the persistent overlay. 3. Use the manual style or design controls in the editor panel to locate the overlay or background settings and remove or disable the gradient or image overlay directly, without relying on the AI agent. 4. Save your project after making the change and preview the page to confirm the overlay has been removed. If you are unable to remove the overlay through the editor controls, please be aware that complete removal of certain gradient overlays may not be possible through the AI agent alone. This is a known limitation that our team has confirmed. In that case, reach out to our support team with your project details and a description of the affected section so our team can review your case and discuss next steps. Retry Actions That Previously Failed If you experienced errors with section creation, page creation, or blog creation, follow these steps: 1. Refresh your browser and reopen the affected project in Website Studio. 2. Retry the action that previously failed — for example, ask the AI agent again to create the section, page, or blog post using a clear and specific prompt. 3. If the AI agent misclassified a blog creation as a page (or vice versa), try rephrasing your request to explicitly specify the content type you want created (e.g., "Create a new standalone page" or "Create a new blog post"). 4. If the action fails again, note the exact error message or behavior you observe, then contact our support team with a description of the specific action that failed and your project details so we can investigate further. If you have followed the steps above and are still experiencing issues, please contact our support team with your project name, account details, and a description of the problem.

🛠️ Creating Multiple Pages and Deleting Duplicate Sections in Website Studio

📌 Overview Website Studio lets you build a complete site with multiple pages and fully editable sections. Two tasks sometimes cause confusion: removing duplicate sections and adding a brand-new page (such as a dedicated form or contact page). This article walks you through both so you can manage your project with confidence. 🤖 Understanding the AI Prompt vs. Manual Editing Website Studio offers two ways to work: you can ask the built-in AI assistant to make changes for you, or you can edit the site manually using the on-screen controls. The AI assistant is great for quick ideas, but it does not always carry out structural actions like deleting a section or creating a page. For these tasks, the manual controls are the most reliable option. If you ask the AI to delete a duplicate section and nothing happens, switch to the manual steps below instead of repeating the request. 🗑️ How to Delete a Duplicate Section Follow these steps to remove any section you no longer need: 1. Open your project in Website Studio. 2. Navigate to the page that contains the duplicate section. 3. Hover your cursor over the section you want to remove. A small toolbar will appear at the edge of that section. 4. Click the delete (trash) icon in the section toolbar. 5. Confirm the deletion if you are prompted to do so. 6. Click Save or Publish to apply your changes. Repeat these steps for each duplicate section. Always delete sections one at a time so you can confirm you are removing the correct one. If a section toolbar does not appear when you hover, click directly on the section first to select it, then look for the toolbar. Why duplicate sections appear: some AI-generated sites previously included duplicate sections automatically. This has been addressed, but projects generated earlier may still contain them, so manual removal may be needed. If a section you deleted reappears on its own, this was a known issue that has since been fixed; refresh the page, delete the section again, and save. Deleting sections one at a time rather than in bulk also helps you avoid a "Something Went Wrong" error that could previously occur during bulk or page operations. 📄 How to Create a New Separate Page The Add new page experience can be confusing because the input field is designed to accept an AI prompt describing the page you want. Typing a description there asks the AI to build content; it does not always create an independent, blank page. To create a genuinely separate page, such as a standalone form page, use the page manager instead. 1. Open your project in Website Studio. 2. Locate the Pages panel, usually found in the left-hand menu or the top navigation bar. 3. Click Add new page. 4. When prompted, choose to create a blank page or select a page template rather than only typing an AI description. 5. Give the page a clear name, for example Contact or Form. 6. Confirm to create the page. It will now appear in your Pages list as a separate page. Once the page exists, open it and add the sections or form elements you need. You can then link to it from your navigation menu so visitors can find it. If your newly created pages do not show up — for example, the dashboard only displays your Home page even though Website Studio generated a multi-page site — refresh and reopen the project; this was a known issue that has since been resolved. Note that converting an existing single landing page into a full multipage website is not yet supported, though it is planned; for now, add pages individually using the steps above. 📝 Adding a Form to Your New Page After creating a separate page for your form, add the form itself: 1. Open the new page from the Pages panel. 2. Click Add section or the + control where you want the form to appear. 3. Select a form or contact section from the available blocks. 4. Edit the fields, labels, and submit button to match your needs. 5. Click Save or Publish. 💡 Helpful Tips - Use the manual controls for structural changes like deleting sections and creating pages; use the AI assistant for content suggestions and copywriting. - Always save or publish after making changes so they are not lost. - If a button or panel does not appear, refresh the page and reopen your project. - Delete sections one at a time to avoid removing the wrong content and to avoid errors during bulk operations. - Name new pages clearly so they are easy to find and link to later. 💬 Need More Help? If you need further assistance, click the chat icon in the bottom-right corner of the platform to start a live chat and type "Human Teammate", then you will be connected with a member of our team.

🔄 Restore Project Versions and Prompt Website Studio

📌 Overview This article covers two of the most common questions about Website Studio: how to restore a previous version of your project, and how to write clear, effective prompts so the Website Studio AI assistant gives you the results you want. Following these steps will help you recover lost work quickly and reduce back-and-forth with the editor. ⏪ Restoring a Previous Project Version Website Studio automatically saves versions (also called checkpoints) of your project as you work, so you can roll back to an earlier point if a change goes wrong or content is lost. To restore a previous version, follow these steps: 1. Open the project you want to restore in Website Studio. 2. Locate the Version History option in the editor toolbar or project settings menu. 3. Browse the list of saved versions. Each entry is timestamped, so you can identify a save from a few hours ago or from a previous day. 4. Select the version you want to preview to confirm it contains the content you need. 5. Click Restore (sometimes labeled Revert) to roll your project back to that version. Important: Restoring an earlier version replaces your current working state. If you are unsure which version to choose, preview each one first before restoring. Troubleshooting: If the Restore button does not respond, or you see a “Failed to restore” message — issues that previously affected restore actions and some HTML and ZIP-uploaded projects — refresh the editor and try again. These known issues have been resolved. If a restore still does not apply, start a live chat with our team using the steps below. 💾 Tips to Protect Your Work To avoid losing progress in the future, keep these habits in mind: - Make significant changes in smaller steps so each save captures a clear checkpoint. - Confirm a change looks correct before moving on to the next edit. - Note the time before making large or experimental changes, so you know which version to return to if needed. 🤖 How to Prompt the Website Studio AI Assistant The Website Studio assistant produces the best results when your instructions are specific and well structured. Vague prompts lead to vague output. Use these principles when writing a prompt: - Be specific: State exactly what you want changed, added, or removed. For example, instead of "improve this page," try "rewrite the hero heading to highlight free shipping and a 30-day return policy." - Give context: Tell the assistant who the page is for, the tone you want, and the goal. For example, "This is a landing page for small business owners; keep the tone friendly and professional." - Work in steps: Ask for one change at a time rather than bundling many requests into a single prompt. This makes it easier to review and refine the output. - Reference the target: Name the section, element, or block you want the assistant to focus on, such as "the pricing table" or "the footer." - Set constraints: Include limits like word count, number of bullet points, or a specific call to action so the output matches your needs. ✏️ Example Prompts Here are examples that follow the principles above: - Weak: "Make the page better." - Strong: "Rewrite the introduction paragraph to be two sentences, focus on time savings, and end with a call to action to start a free trial." - Weak: "Add some features." - Strong: "Add a three-column feature section listing automated reporting, keyword tracking, and competitor analysis, each with a short one-line description." 🔁 Refining the Output If the first result is not quite right, you do not need to start over. Follow up with a short, focused correction that builds on what the assistant produced. For example, "Keep the same heading but shorten the paragraph to one sentence," or "Use a more casual tone in the second bullet point." Iterating in small steps usually produces better results than rewriting your entire prompt. 💬 Need More Help? If you need further assistance, click the chat icon in the bottom-right corner of the platform to start a live chat with a member of our team.

🛠️ Fix Website Studio Editor Page and Saving Issues

The Website Studio visual editor lets you make live edits to your pages without touching code. Sometimes the editor may open a different page than the one you selected, or your changes may not appear to save. This usually happens for a few common, easy-to-fix reasons. Follow the steps below to get back on track. 🧭 Why the Editor Opens the Wrong Page If you try to edit one page (for example, Certified Triple Wide) but the editor loads a different page (such as Metal Carports), one of the following is usually the cause: - Redirects on the source page: If the page you selected has a redirect rule pointing to another URL, the editor will follow that redirect and load the destination page instead. - Duplicate or similar URLs: Pages with near-identical slugs can be selected by mistake from the page list. - Cached page mapping: An outdated cache can cause the editor to load a previously visited page. - Canonical or CMS routing: Some content management systems route multiple slugs to a single template, which can send the editor to an unexpected page. ✅ How to Load the Correct Page 1. Copy the exact, full URL of the page you want to edit directly from your live website. 2. In Website Studio, paste that full URL into the page or URL field instead of choosing from a list. 3. Confirm the page title and visible content in the editor match the page you intended to edit. 4. Check your site for any redirect rules on that URL and temporarily disable them if the editor keeps following a redirect. 5. Clear your browser cache, or open the editor in a private/incognito window, then load the URL again. 💾 Why Changes Are Not Saving or Applying When edits appear to disappear or never go live, the most common reasons are: - Editing the wrong page: If the editor loaded the wrong page (see above), your changes were saved to that page, not the one you meant to update. - Changes not published: Saving a draft is separate from publishing. Unpublished changes will not appear on the live site. - Element not fully selected: If an edit is made outside a recognized element, the editor may not capture it. - Image or background image edits: Visual edits to images and background images occasionally do not update, even when other edits save correctly. If an image change does not appear, re-select the image element and re-apply the change, then clear your cache to confirm. - Browser or connection interruptions: A dropped connection can prevent a save from completing. - Caching on the live site: Changes may be saved but hidden behind your browser cache or a site-wide cache. 🔧 How to Make Your Changes Stick 1. Confirm you are editing the correct page before making any edits. 2. Make your change, then use the Save button and wait for the confirmation message before continuing. 3. If a separate Publish or Apply step is available, complete it so the change goes live. 4. Avoid navigating away or closing the tab until the save is confirmed. 5. Refresh the live page in a private/incognito window to bypass caching and verify the change is visible. 6. If your site uses a caching plugin or CDN, clear that cache so updated content is served. 🐞 Known Issues That Have Been Resolved A few Website Studio editor behaviors reported in the past have already been fixed by our engineering team. If you still encounter any of them, hard refresh the editor and clear your cache to load the latest version: - The visual editor redirecting to the home page after applying changes on a page. - The Visual Edit page selector loading a different page than the one chosen. - The editor incorrectly responding "unable to make change" when the edit should succeed (in Free Mode). - Image and background image edits not updating on the page. If any of these behaviors persist after refreshing and clearing your cache, contact our team so we can investigate. 🚀 Best Practices to Avoid Editor Issues - Always paste the full, exact URL to ensure the correct page loads. - Make one change at a time and confirm each save before moving on. - Keep a stable internet connection while editing. - Review redirect rules before editing pages that tend to load the wrong destination. - Verify every change on the live site in a private window after publishing.

⚠️ Website Builder: "Something Went Wrong" Error When Adding Multiple Blog Entries

We are aware of an issue in the Website Builder where adding multiple blog entries at the same time triggers a "Something Went Wrong" error, and those entries may not be saved. Adding blog entries one at a time works reliably while our engineering team resolves the issue. 🔍 What's Happening When you attempt to add multiple blog entries in rapid succession, the Website Builder returns a "Something Went Wrong" error. Affected entries may fail to save. Single blog additions are not affected and complete without error every time. This issue impacts all customers who use the blog feature in the Website Builder. Note: Some customers may see their blog content combined into a single blog entry instead of separate entries. Both this issue and the "Something Went Wrong" error are resolved by using the one-at-a-time workaround. 🛠️ Workaround Steps Until the fix is released, add blog entries one at a time using these steps: 1. Open the Website Builder and navigate to the blog section. 2. Add a single blog entry. 3. Wait for the entry to save successfully before proceeding. 4. Repeat for each additional blog entry, one at a time. This approach works reliably and ensures every blog entry is saved correctly. 📡 Engineering Status Our engineering team is aware of this issue and is actively working on a fix. No action is required on your part beyond using the one-at-a-time workaround described above. This article will be updated when a fix is deployed. 📞 When to Contact Support Reach out to our support team if any of the following apply: - Single blog additions are also failing for you. - The "Something Went Wrong" error appears even after following the one-at-a-time workaround. - The one-at-a-time workaround does not resolve the issue for you. When contacting support, include your workspace name and a brief description of the steps you took when the error appeared — this helps our team investigate more quickly. 🎯 Our team is actively working to resolve this so you can add blog entries without interruption — thank you for your patience, and we apologize for any inconvenience this has caused.

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

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

🛠️ Troubleshooting Pages That Don't Appear or Load in Website Studio

📋 Overview This article helps you resolve a known issue in Website Studio where a newly created page shows a success message but does not appear in your page list, or where unexpected pages show up (often under the Blog section) that cannot be opened or deleted. These symptoms are usually caused by a temporary sync delay between Website Studio and your published site, or by a page record that did not finish saving correctly. 🔍 Common Symptoms - You create a new page (for example, a "Providers" page), see a success confirmation, but the page never appears in the page list. - Pages you did not create appear under Blog or another section. - These unexpected pages will not open, preview, or delete. - A page appears in the editor but returns an error or blank screen when you try to load it. 🤔 Why This Happens Website Studio saves a page in two stages: it first creates the page record, then syncs it to the page list and your live site. If the second stage is interrupted—by a network drop, a browser timeout, or a duplicate save request—the page can end up in an incomplete state. This is what produces "ghost" pages that exist in the database but cannot be edited or removed through the normal interface. A specific, documented cause behind unexpected pages appearing under Blog is how the AI chat (vibe) assistant interprets your request. When you ask the assistant to build a page with rich content—for example, several people each with a name, title, and short bio—it could misclassify the request as a blog post and create an entry under the existing Blog page instead of generating a new standalone page. In this case the assistant may still return a success message such as "I've published … for you," even though no standalone page was created and the intended URL leads nowhere. This behavior was identified as a bug (Linear LPS-1113 / LPS-1151) and has been resolved. A related issue—where blog-creation requests produce empty placeholder pages labeled "Reference Website Analysis" that contain only a header and footer with no body content—is currently in progress (Linear LPS-1238). ⚡ Quick Fixes to Try First Most display issues clear up with a refresh. Try these steps in order: 1. Hard refresh the page. Press Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac) to reload Website Studio and clear cached content. 2. Wait and recheck. Allow 2–3 minutes for the page to finish syncing, then reopen the page list. 3. Clear your browser cache or open Website Studio in a private/incognito window to rule out a local caching problem. 4. Try a different browser. Use the latest version of Chrome, Firefox, or Edge to confirm the issue is not browser-specific. 5. Check your internet connection. An unstable connection during save is a common cause of incomplete pages. 🔄 If the Page Still Doesn't Appear If your new page is still missing after refreshing, recreate it carefully: 1. Confirm the page is not already listed under a different section (such as Blog or Drafts). 2. Create the page again, using a slightly different name or URL slug to avoid a duplicate conflict. 3. Wait for the success message, then refresh the page list before making further edits. 4. Publish the page and confirm it loads on your live site. 💡 Tip: Be Explicit in the AI Chat Assistant If you are creating the page through the AI chat (vibe) assistant, state clearly that you want a standalone page and include the exact URL slug you want (for example, /providers). Being explicit about the page structure helps the assistant route the request correctly instead of treating a content-rich prompt as a blog post. 💡 Tip: Avoid Duplicate Saves Click Save or Create only once and wait for the confirmation. Clicking multiple times can create conflicting records that lead to phantom pages. 🧹 Removing Phantom or Unexpected Pages Pages that appear unexpectedly—or that will not open or delete—are typically incomplete records that the interface cannot modify. Do not repeatedly attempt to delete them, as this can create additional duplicates. Instead: 1. Take a screenshot showing the unexpected pages and where they appear (for example, under Blog). 2. Note the page names, URL slugs, and the approximate date and time you created the original page. 3. Contact our support team so we can remove the incomplete records from the back end safely. 📨 Information to Include When Contacting Support To help us resolve your case quickly, please provide: - The name and URL slug of the page you intended to create. - The names of any unexpected pages that appeared. - The section where they appear (Blog, Pages, etc.). - The date and time you created the page. - The browser and operating system you were using. - A screenshot of your page list showing the issue. You can reach us through the in-app chat or by emailing our support team. Most page-record cleanups are completed within one business day. 🛡️ Preventing the Issue in the Future - Save pages on a stable internet connection. - Click the save or create button only once and wait for confirmation. - Refresh the page list after creating a page before continuing to edit. - Keep your browser updated to the latest version. 📝 Summary Missing or non-functional pages in Website Studio are usually caused by a sync interruption during save, or by the AI chat assistant misclassifying a content-rich page request as a blog post. A hard refresh resolves most display issues, and recreating the page with a unique name—stating clearly that you want a standalone page with a specific slug—resolves most missing pages. For phantom pages that cannot be deleted, contact support with the details above so we can remove the incomplete records for you.

🛠️ Why ZIP-Imported Website Studio Projects Take Several Minutes to Apply a Modification

If you imported a project via ZIP upload (for example, a Loveable export) in Website Studio and your modification prompt seems stuck, the request is still processing in the background. Wait up to about 10 minutes and avoid refreshing or resubmitting. 🔍 What's Happening After you import a project through ZIP upload in Website Studio and submit a modification prompt such as Add this page to the project, the AI agent can take 6 or more minutes (sometimes 10+) to respond. No progress indicator appears during this time, so the editor may look frozen, stuck, or broken. The request is still working in the background, even though nothing on screen confirms it. This delay mainly affects projects brought in through ZIP upload. Who is affected - Affected: Projects imported via ZIP upload (such as Loveable exports) in Website Studio. - Not affected to the same degree: Projects built natively inside Website Studio, which respond noticeably faster. 🛠️ Workaround Steps Follow these steps after you submit a modification prompt on a ZIP-imported project: 1. Do not refresh the page, navigate away, or resubmit the prompt. The request is still processing even though no progress is shown. 2. Allow up to about 10 minutes for the AI agent to finish applying the change. 3. If you frequently modify projects, build the project natively in Website Studio instead of importing a ZIP. Native projects respond faster. Once processing completes, your requested modification appears in the project as expected. 📡 Engineering Status Our team is aware of this issue and actively working on it. The slow response time on ZIP-imported projects is a known behavior, and improvements are in progress. 📞 When to Contact Support Give the modification about 10 minutes to complete. If it still has not applied after that time, reach out to our support team and we'll take a closer look. Let us know that the project was imported via ZIP upload so we can investigate faster. 🌀 You're in good hands — the request is processing even when the editor looks quiet, and our team is on this to make ZIP-imported modifications faster. Give it a few minutes, and contact us anytime if it doesn't complete.

🛠️ Website Studio: Safely Using the Download/Upload Workflow and Reverting a Project

Website Studio lets you export your site's HTML, edit it externally, and upload it back. This guide explains how the download/upload workflow works, why a re-uploaded site can break, and the safest ways to make changes and recover a working version. ⚠️ Why a Re-Uploaded Site Can Break When you download HTML from Website Studio, you receive the rendered markup only. The export does not include everything that makes the live site function. Re-uploading that file—even without edits—can break the site because the package is missing dependencies the platform normally manages. Common reasons a re-uploaded site breaks: - Linked assets are not bundled. CSS, JavaScript, fonts, and images often load from paths or a content delivery network that the standalone HTML file cannot resolve once it is taken out of its original environment. - Relative and absolute paths change. Editing in an external editor can rewrite file paths, so stylesheets and scripts no longer point to the right location. - Platform-injected code is lost. Website Studio adds structural and tracking elements at publish time. A manual upload can omit or duplicate these. - Encoding or formatting changes. Some editors alter character encoding or auto-format the file, which can corrupt how the page renders. This is why the same workflow breaks even on a second site with no edits: the issue is the round-trip itself, not the specific changes you made. The same applies whether the project was created from an HTML upload or a ZIP upload. ✅ Recommended: Edit Inside Website Studio For most changes, the safest and fully supported method is to edit directly in the Website Studio visual editor rather than downloading and re-uploading. In-app editing keeps all assets, paths, and platform code intact, and your changes are tracked automatically. ✏️ To edit in the editor 1. Open Website Studio from your dashboard. 2. Select the project you want to change. 3. Click Edit to open the visual editor. 4. Make your changes to text, images, layout, or settings. 5. Click Save, then Publish when you are ready to go live. 📦 When You Need the Exported HTML The HTML export is intended for portability and reference—for example, moving content to an external host or archiving a copy. It is not designed to be edited and pushed back into the same Website Studio project. If you need custom code in your live site, use the built-in custom code options instead of replacing the full HTML. Known issue: When a project is exported as a ZIP and then re-imported into Website Studio, blog posts that existed before the export can be missing from the imported project. A fix for this is currently awaiting release. If you rely on the export/import workflow and notice missing blogs, avoid further changes and contact Support with links to both the original and the imported project. 💻 Adding custom code safely 1. Open your project in Website Studio. 2. Go to Settings and locate the Custom Code or Header/Footer Code section. 3. Paste your snippet into the appropriate area (head or body). 4. Save and publish, then preview the live page to confirm it works. This approach lets you add scripts and styles without disturbing the rest of the site. ↩️ How to Revert a Broken Project If your site has already broken, you can usually restore a previous working version. 🕘 Restore from Version History 1. Open the affected project in Website Studio. 2. Open the Editor. 3. Look for Version History (often shown as a clock or history icon, or under the project menu). 4. Select a version saved before the upload. 5. Click Restore, then republish. 🤖 Reverting individual AI prompts On HTML- or ZIP-upload projects, each AI change you make is listed as a prompt with its own Revert button, and you can undo a revert with Re-Revert. Reverting an uploaded project can take slightly longer to process than reverting a project built natively in Website Studio. If a revert appears to stall or returns a temporary error such as a gateway message, wait a moment and refresh the page before trying again. ❓ If Version History Is Not Available Version History only captures changes made inside Website Studio. A manual HTML upload may not create a restore point, which is why the option can appear empty or inaccessible after a broken upload. If you cannot revert through the interface: - Do not perform further uploads, as this can overwrite recoverable data. - Note the project name, URL, and the approximate date and time the site was working. - Contact Search Atlas Support (see below) so the team can attempt a server-side restore. 💡 Best Practices to Avoid Breaking Your Site - Make routine edits inside the Website Studio editor, not through download/upload. - Use the Custom Code settings for scripts and styles instead of editing exported HTML. - Before any major change, publish the current working version so a recent restore point exists. - Always preview changes before publishing them live. - Treat the HTML export as a read-only copy for backup or migration. 💬 Contact Support If your site is broken and you cannot revert, reach out to Search Atlas Support through the in-app chat or your account team. Please include your project name, site URL, a description of what happened, and the date and time the site last worked correctly. This helps the team restore a working version as quickly as possible.

🛠️ Reverted Lovable/ZIP Landing Page Preview Blocked in Website Builder

If you reverted a Lovable or ZIP-uploaded landing page and the staging preview now shows a "Blocked request / host not allowed" error, a fix has been deployed. Re-run the revert, or make a small edit and republish to force a rebuild, then hard-refresh the preview. 🔍 What's Happening After you use the revert feature to roll back a Lovable or ZIP-uploaded landing page (a react_source project) in the Website Builder / Landing Page Studio, the staging preview can fail to load. The preview engine (Vite, the build tool that renders your staging preview) blocks the preview subdomain and shows a "Blocked request / host not allowed" style error. When this happens, the reverted page will not render in the preview tab. Who is affected - Customers using the Website Builder / Landing Page Studio. - Projects created from a Lovable or ZIP upload (a react_source project). - Only after the revert action is used to roll back the project. If you have not reverted a Lovable/ZIP project, this issue does not apply to you. 🛠️ Workaround Steps A fix is now live. Follow these steps in order to restore your staging preview: 1. Re-run the revert on the affected Lovable/ZIP project. With the fix deployed, this re-applies the correct preview host configuration. 2. If the preview is still blocked, make a small trivial edit and re-deploy/republish. This forces the project to rebuild and re-apply the preview host settings. 3. Hard-refresh the preview tab to clear any cached error (Ctrl + Shift + R on Windows, Cmd + Shift + R on Mac). Once the rebuild completes, your reverted landing page will load in the staging preview as expected. 📡 Engineering Status Our team is aware of this issue and a fix has been deployed. New reverts and rebuilds will apply the corrected preview host configuration automatically. If you ran a revert before the fix went live, the workaround steps above will restore your preview. 📞 When to Contact Support If the staging preview is still blocked after you re-run the revert, republish with a small edit, and hard-refresh, reach out to our support team. Please include: - The project name or URL of the affected Lovable/ZIP landing page. - A note that the page is a reverted react_source project. - A screenshot of the "Blocked request / host not allowed" error. Our team will take a closer look and help you get the preview rendering again. 🎯 You're in good hands — the fix is live, and in most cases re-running the revert and republishing restores your preview right away. If anything still looks off, contact support and we'll take it from there.

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

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

🛠️ Brand Vault Generic Preview Text Appearing for Your Business

🔍 What Is This Issue? Some users have noticed that Brand Vault auto-populates preview text that is completely unrelated to their business — for example, copy referencing cloud project management or password resets appearing for landscaping or construction companies. This is a platform-level bug, not a configuration error on your end. If you are experiencing this problem, the steps below will help you confirm the issue and get it resolved quickly. 📋 Before You Contact Support Take a moment to confirm that what you are seeing matches this known bug: - Brand Vault is generating preview text that has no connection to your industry, products, or services. - The issue appears regardless of which project or site you are viewing. - You have not recently changed your brand settings in a way that might explain the mismatch. If all of the above apply, this is likely the same issue our support team has seen reported by other users. Continue to the next section. ⚙️ Steps to Try While this is a platform-level bug, you can try the following general steps to see if they help refresh your Brand Vault content: 1. Refresh your browser and log out, then log back in to your Search Atlas account. 2. Navigate to your Brand Vault settings and check whether any brand information has been saved for your business. 3. If your brand details appear incomplete or missing, re-enter your business name, niche, tone, and key messaging to give the platform the correct context. 4. Save any changes and allow Brand Vault a moment to regenerate its preview content. 5. Check whether the auto-populated text now reflects your actual business. Ensuring your brand profile is complete and accurate is a good general practice — the more specific your brand inputs, the more relevant the AI-generated content will be across the platform. ✅ If the Issue Persists If you complete the steps above and still see irrelevant or incorrect auto-generated content, please reach out to our support team so they can investigate your account directly. Before reaching out, it helps to have the following ready: - Note the specific text that is appearing and which business or site it is connected to. - Take a screenshot if possible — this will help the team investigate faster. - Be ready to confirm whether you tried updating your brand profile and whether that changed anything. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our support team.