Troubleshooting: Navigation, Menus & Headers

🐛 Fix Website Studio Menu Dropdown and Brand Vault Issues

🔍 Fix Website Studio Preview Image and Navigation Issues

🔍 Overview After Content Genius generates a blog post, two related issues can sometimes appear in Website Studio: the blog preview image fails to load, and an existing page (such as a Checklist page) begins redirecting to the Homepage instead of displaying its own content. These are known bug-category issues that require investigation by our support team. 🖼️ Why the Blog Preview Image May Not Be Loading Preview image failures in Website Studio can occur when a blog post generated by Content Genius does not have its image correctly registered within the page. Because the exact cause depends on your specific account and page configuration, our team will need to look into the underlying data to identify what went wrong. 🔗 Why a Page May Be Redirecting to the Homepage A page unexpectedly redirecting to the Homepage can be caused by a configuration issue within Website Studio affecting that specific page. Because the root cause varies by account and page setup, our team will need to investigate directly. 🛠️ What to Prepare Before Reaching Out To help our team resolve these issues as quickly as possible, please have the following ready when you contact support: - The exact name of the affected blog post or page (e.g., the Checklist page) - The full URL of the page that is broken or redirecting incorrectly - The URL or location where the preview image should be appearing - The approximate date and time when you first noticed the issue - Whether the issue appeared after a specific action (e.g., publishing a page, using Content Genius to generate a post) - Any error messages or unusual behavior you observed If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🐛 Fix Blog Preview Images and Page Navigation in Website Studio

Overview Two known issues can affect your Website Studio experience: blog post preview images that fail to load, and pages (such as a Checklist page) that redirect to the homepage instead of rendering the correct content. These are recognized bugs that our team is actively investigating. Blog Preview Image Not Loading Some users have reported that blog post preview images do not appear as expected within Website Studio. This is a known issue. At this time, there is no confirmed self-serve fix, and our team needs to investigate the affected account directly. When contacting support, please have the following ready: - The name or URL of the blog post where the preview image is missing - A screenshot showing the missing image - The exact URL of the image you are trying to use (if applicable) - Any error messages you are seeing Page Navigation Redirecting to the Homepage Some users have reported that specific pages — such as a Checklist page — redirect to the homepage instead of displaying the intended content. This is a known issue. Our team needs to review the affected page configuration directly to identify the cause and apply the correct fix. When contacting support, please have the following ready: - The name of the page that is redirecting incorrectly - The URL you are trying to visit and the URL it redirects to - A screenshot or screen recording demonstrating the redirect - Roughly when the issue started occurring 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 Menu Nesting Changes Not Applying in Website Studio

🔍 Overview When you ask the AI assistant in Website Studio to restructure your navigation menu — for example, moving a Blog item from a nested submenu to the top level — the AI may confirm the change was made, but the menu structure appears unchanged in the editor. This is a known issue with how menu hierarchy updates are applied in Website Studio. ⚙️ Why This Happens This is a known bug affecting the AI assistant in Website Studio. When menu nesting changes are requested, the AI may report success without fully executing the structural update. The underlying cause is a limitation in how menu hierarchy changes are processed — the source of this issue has been identified and requires a backend fix. 🔎 What to Expect Because this is a backend bug, there are no confirmed self-serve steps that will reliably resolve the issue on your end. Our team will need to investigate and apply a fix on the platform side. If you are experiencing this issue, please be ready to share the following details when you contact support: - The name of the website project where the issue is occurring. - The specific menu item(s) you asked the AI to move or restructure (for example, Blog under Programs). - The exact instruction you gave the AI and the response it provided. - Any screenshots or screen recordings showing the menu structure before and after the AI's attempted change. - The approximate date and time the issue occurred. 💡 Tips for Using AI Menu Editing While this bug is being investigated, to get the best results when asking the AI to modify menu structure, be as specific as possible in your requests — include the exact item name and where you want it moved. 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 Duplication and AI Overlay Bugs

🔍 Overview Some Website Studio users have encountered a combination of bugs affecting AI-assisted page editing. These include: AI tasks consuming credits without completing, edits to a duplicated page accidentally overwriting the original, dark gradient overlays becoming locked and uneditable, and navigation menu changes not being applied. This article explains what is happening and what to do next. ⚠️ Known Issues The following bugs have been identified and are actively being resolved by the Search Atlas engineering team: - Duplicate page edits overwrite the original: When a page is cloned or duplicated, changes made to the copy can unintentionally overwrite content on the source page. - AI hero overlay edits silently fail: Asking the AI agent to adjust a dark gradient overlay on a hero section may appear to succeed but the change is not applied, and credits are still deducted. - Navigation menu updates not applied: After an AI task runs, navigation menu changes may not appear on the live or preview page. ✅ What to Do While This Is Being Fixed These are backend and editor-level bugs currently being addressed by the engineering team. There are no confirmed self-serve workarounds grounded in a resolved fix at this time. To avoid further disruption: - Avoid retrying failed AI tasks immediately. If an AI task did not complete as expected, do not resubmit the same prompt right away, as this may result in additional credit loss. - Do not rely on page duplication for live work. Until the duplication bug is resolved, avoid using cloned or duplicated pages for edits that affect production content. - Document the issue before contacting support. Note your project name, the exact action you attempted, the approximate time it occurred, and any error messages you saw. This information will help the support team investigate and, where applicable, review any credits lost due to failed tasks. 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.

🎨 Dropdown Menu Styling Limits in Website Studio

🔍 Overview In Website Studio, dropdown menu styles — such as corner styles (rounded or square) — are controlled by a global style setting that applies across your entire site. This means any change you make to a dropdown's corner style will affect all dropdowns site-wide, not just a single menu or page. This is a known platform limitation. Understanding how this works will help you make informed design decisions and avoid unexpected changes to your site's appearance. ⚙️ How Global Dropdown Styling Works Website Studio applies dropdown corner styling globally. This means: - Changing the corner style on one dropdown will apply that style to all dropdowns across your entire site. - There is currently no option to override the corner style for a single dropdown independently of the rest of the site. ❓ Why This Is Not a Bug Customers sometimes report this behaviour as a bug because they expect element-level style control. This is a known customization limitation of Website Studio's dropdown styling — individual dropdowns cannot be styled independently of the global setting at this time. ✅ What You Can Do While per-dropdown corner styling is not currently available, you can work within this constraint by making an intentional global style choice that suits your site's overall design direction — for example, choosing either rounded or square corners as your consistent site-wide style. If you require per-dropdown styling control that is not currently possible, this is a platform limitation and you would need to escalate it. When escalating, please have the following ready: - Your project or site name in Website Studio - A description of the specific dropdown(s) affected and what styling outcome you are trying to achieve - Any screenshots showing the current appearance versus your expected result 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 Persistent Dark Overlays in Website Studio Sections

🔍 What Is This Issue? Some users building websites in Website Studio notice that dark overlays applied to section images — such as those used for Yoga, Breathwork, or Reiki sections — persist in the preview even after attempting to remove them manually or through automated requests. The overlay appears locked in place and does not respond to edits. ⚙️ Why Does This Happen? This issue is caused by design recipe enforcement within Website Studio. When a section is generated using a design recipe, certain visual properties — including dark image overlays — can be locked at the template level. As a result, manual edits or automated change requests may appear to succeed but are not reflected in the live preview. This is a known platform-level bug that has been investigated and resolved by the Search Atlas engineering team. ✅ What Has Been Fixed Our engineering team identified and resolved the root cause of this bug. The fix has been built, reviewed, and released to production. Specifically, this addressed the following confirmed issues: - Dark overlays enforced by design recipes persisting despite successful-looking edits - Visual changes reported as successful but not reflected in the Website Studio preview - Preview screen styling disappearing mid-generation If you were affected by this bug before the fix was released, your website sections should now respond correctly to overlay edits. 🛠️ Steps to Remove a Persistent Dark Overlay Now that the underlying bug has been resolved, follow these steps to remove a dark overlay from your section images: 1. Open Website Studio and navigate to the affected website. 2. Locate the section with the persistent dark overlay (for example, Yoga, Breathwork, or Reiki sections). 3. Enter editing mode for that section and remove or adjust the overlay setting as needed. 4. Save your changes and check the preview to confirm the overlay has been removed. 5. If the preview does not update immediately, try refreshing the page before making further edits. 💡 Additional Tips - If your preview still shows outdated styling after saving, a full page refresh often resolves display sync issues. - Avoid making rapid successive edits to the same section, as this can sometimes cause the preview to fall out of sync with saved changes. - If a section appears hidden or disappears after scrolling on the home page preview, this is a separate issue that has also been resolved in the same engineering release. 📋 Still Seeing the Issue? If you have followed the steps above and the dark overlay still persists on your section images, this may indicate a unique configuration on your project that requires individual 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.

🛠️ Copilot Navigation Removal Requests Not Working

🔍 What This Article Covers Some users found that Website Studio's Copilot could not process requests to remove navigation menu items. Instead of completing the action, Copilot repeatedly asked for more details — even after those details were provided — causing failed attempts and wasted credits. This article explains what caused the issue, confirms it has been resolved, and tells you what to do if you still experience it. ⚠️ What Was Happening This was a confirmed bug in Website Studio. When users asked Copilot to remove menu or navigation items, the assistant was unable to complete the action. Instead, it entered a loop of requesting additional specifics, even when the user had already provided clear instructions. This caused: - Repeated failed prompts without any change to the site - Credits being consumed without a successful outcome - Frustration from receiving no meaningful progress despite detailed input The root cause was an underlying technical issue, not incorrect user input. No matter how specific the instructions were, the bug prevented the action from completing successfully. ✅ Current Status: Issue Resolved This bug has been identified and fixed by Search Atlas's engineering team. Website Studio Copilot should now be able to process navigation and menu removal requests correctly. If you previously encountered this problem, you can return to Website Studio and try your request again — the fix is live. 🚀 How to Try Again 1. Go to Left sidebar → Website Studio to open your project. 2. Open the Copilot chat and enter your navigation removal request as clearly as possible (for example: "Remove the 'About' item from the main navigation menu"). 3. Allow Copilot to process the request and check whether the change appears in your site preview. 4. If the change looks correct in the preview, confirm or save the update as prompted. 💡 Tips for Better Results While the bug is resolved, following these best practices will help Copilot process your requests accurately: - Be specific about the item: Name the exact menu item you want removed (e.g., "Remove 'Services' from the header navigation"). - One action at a time: Avoid combining multiple structural changes in a single prompt. Send separate instructions for each item you want to remove. - Verify in the preview: After each change, check your site preview to confirm the update has been applied before continuing. 🛠️ If the Problem Persists The fix is confirmed live, but if you find that Copilot is still unable to process navigation removal requests on your account, this may indicate a separate or account-specific issue that our team needs to investigate. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team. When you reach out, please share the exact prompt you used and describe what Copilot responded with — this helps our team resolve your case quickly.

🛠️ Website Studio Pages Show Only Header and Footer

🔍 What Is This Issue? Some Website Studio pages appear to build correctly — credits are consumed and the backend confirms assets were generated — but when you preview or visit the published page, only the header and footer are visible. All inner content sections are missing. This is a known bug. During page generation, the individual content sections are created successfully, but the system fails to assemble those sections into a complete, routable page. The result is a page that looks structurally valid but renders no body content. 📋 How to Confirm You Are Affected - You generated one or more pages using Website Studio (via Left sidebar → Website Studio). - The build process completed and credits were deducted from your account. - The page preview or live URL shows only the site header and footer with a blank body area. - The issue persists after refreshing or re-visiting the page. ⚙️ What You Should Do Right Now 1. Do not attempt to regenerate the affected pages. Regenerating will consume additional credits without resolving the underlying assembly issue. 2. Make a note of every affected page. Record the page names and any relevant URLs or project names so you can provide accurate details when you contact support. 3. Do not delete the affected pages or the project. The engineering team needs the existing data to apply a manual fix and investigate the root cause. 💡 Why Self-Resolution Is Not Possible for This Issue Because the failure happens at the page-assembly stage inside the platform's backend, there are no settings, toggles, or republish actions available to you as a user that will resolve it. The fix must be applied manually by the Search Atlas engineering team on a per-page basis. This bug has been identified, escalated, and resolved for affected accounts by the engineering team (internal reference: SPE-883). If you are currently seeing this behavior, your account may still be affected and requires a manual correction. 🚀 How to Get Your Pages Fixed 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 the team, please provide: - The name of the website project affected. - The names of all pages that display only the header and footer. - The approximate date and time the pages were generated. A support agent will escalate your case to engineering, who will manually reassemble and fix the affected pages for you. 🔄 After the Fix Is Applied Once engineering has corrected your pages, revisit each affected URL to confirm the body content is now rendering correctly. If any page still shows only the header and footer after you have been notified that the fix was applied, contact the team again through the chat widget and mention that the issue persists on a specific page.

🛠️ Fix Website Studio Navigation and Page Editing Errors

🗺️ Overview Website Studio lets you build and manage your entire site from one place. However, some users encounter a handful of known issues: the page selector snapping back to the Home page, navbar changes not saving correctly, site-wide header edits reverting, and page creation or slug update failures. This article walks you through each issue and how to resolve it. 📋 Common Issues Covered - Page selector snaps back to Home after switching pages - A 10-second loading overlay appears on every page switch - Navbar and visual layout changes appear saved but do not apply - Site-wide header dropdown edits revert after saving - Missing pages in the page selector - Page creation errors and slug change failures - Applying a navigation menu across all pages - Removing specific items from the navigation 🔄 Page Selector Snaps Back to Home If the page selector resets to the Home page every time you try to switch, or a loading overlay appears for around 10 seconds after each page switch, this is a known issue that has been resolved in a recent platform update. Follow these steps to confirm it is working correctly: 1. Hard-refresh your browser by pressing Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac) to clear any cached version of the editor. 2. Open Website Studio and use the page selector dropdown to switch to a different page. 3. If the selector still snaps back to Home, log out of Search Atlas, clear your browser cookies, and log back in. 4. Try using a different browser (Chrome or Edge recommended) to rule out browser-specific caching. If the problem persists after these steps, contact support via the chat widget. 💾 Navbar and Layout Changes Not Applying A previously confirmed bug caused Website Studio to display a success message after saving navbar or visual layout changes, even though the changes were not actually applied to the live site. This bug has been fixed. To ensure your changes save correctly going forward: 1. Make your desired navbar or layout changes inside Website Studio. 2. Click Save and wait for the confirmation message. 3. Navigate away from the editor and return, or open your site in a new browser tab to verify the changes are visible. 4. If the changes do not appear, try clearing your browser cache and checking again. If changes continue to revert after a confirmed save, this may indicate a residual issue — reach out to support immediately so the team can inspect your site's configuration. 🌐 Site-Wide Header Dropdown Edits Reverting Editing the site-wide header (including dropdown menus in the navigation) was affected by a bug that caused all edits to revert after saving. This has been resolved. Here is the recommended process for editing your site-wide header now: 1. Open Website Studio and select any page to begin editing. 2. Click on the header or navigation element you want to update. 3. Make your changes — for example, applying a new menu structure, updating links, or removing navigation items such as What We Do. 4. Click Save. Do not navigate away immediately — wait 3–5 seconds for the save to fully register. 5. Refresh the page and confirm the header reflects your changes. To remove a specific navigation item (such as "What We Do"), click directly on that item in the header editor, select the delete or remove option, and save. Repeat the save-and-verify process above. 📄 Applying a Navigation Menu Across All Pages To ensure a consistent navigation menu appears on every page of your site: 1. Open Website Studio and navigate to your Header or Navigation settings — this is typically managed as a global/site-wide component. 2. Set up the navigation menu you want to use (for example, your Services page menu). 3. Look for a Apply to All Pages or Set as Global Header option and enable it. 4. Save your changes and verify by switching between pages in the page selector to confirm the header is consistent. If you do not see a global header option, it may be because the header was added individually per page during a previous edit. In that case, contact support so a team member can apply the header globally from the backend. 🔗 Changing a Page Slug To update a page's URL slug inside Website Studio: 1. Open Website Studio and select the page you want to update from the page selector. 2. Open the Page Settings panel (usually accessible via a gear or settings icon). 3. Locate the Slug or URL field and enter the new slug. 4. Save the changes. Note: changing a slug will update the page's URL, so update any internal links pointing to the old URL. If the slug field does not save or throws an error, try refreshing the editor and attempting again. Persistent errors should be reported to support. ➕ Page Creation Errors and Missing Pages If you receive an error when creating a new page, or a page you have created does not appear in the page selector: 1. Refresh the Website Studio editor fully and check the page selector again — newly created pages can sometimes take a moment to appear. 2. If the page is missing, try creating it again using a unique name and slug. 3. Avoid using special characters in page names or slugs (use hyphens instead of spaces). 4. If the error repeats or the page still does not appear, do not create duplicate pages — contact support to investigate. ⚠️ Note on Platform Naming You may notice that the tool is labelled Website Studio in the navigation menu but appears as Website Builder in the browser URL or tab title. These refer to the same feature — this naming inconsistency is a known issue currently being addressed by the product team. 💬 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 YouTube Thumbnail Overlay Persistence in Website Studio

🔍 Overview Some customers have noticed that after asking the Website Studio AI agent to adjust or remove the opacity overlay on a YouTube thumbnail, the change appears successful in the chat but does not stick in the visual preview. In some cases, the overlay returns immediately after being removed, or the preview continues to show the original state even after clearing the browser cache. This was caused by a series of related bugs that have now been resolved. ⚠️ What Was Happening Several interconnected issues were responsible for this behaviour: - Overlay changes did not persist: When the AI agent removed or modified the image scrim (the semi-transparent overlay) on a YouTube thumbnail, the update was not being saved correctly to the page. - Write-time fixer re-added the scrim: A background process designed to maintain visual consistency was automatically re-applying the overlay immediately after the agent removed it, effectively undoing the change. - Preview did not reflect confirmed edits: The agent reported a successful edit in the conversation, but the live preview panel was not refreshing to show the actual result. - Changes did not carry across projects: In some workflows involving multiple pages or projects, confirmed edits were not being propagated correctly. ✅ Current Status All of the bugs listed above have been resolved. The following fixes are now live in Website Studio: - Overlay and opacity changes made by the AI agent are correctly saved and persisted after the session. - The write-time fixer no longer re-applies a scrim that the agent has intentionally removed. - The preview panel now accurately reflects confirmed visual changes in real time. - Edits are properly carried through across project contexts. 🚀 How to Apply YouTube Thumbnail Overlay Changes Now If you previously experienced this issue and your overlay settings still look incorrect, follow these steps to get the result you need: 1. Open Website Studio and navigate to the page containing your YouTube thumbnail section. 2. In the AI agent chat, clearly describe the change you want — for example: "Remove the dark overlay from the YouTube thumbnail" or "Set the thumbnail overlay opacity to 0%". 3. Once the agent confirms the edit, check the live preview panel to verify the change is reflected visually. 4. If the preview does not update immediately, click the refresh icon within the preview panel (do not refresh your entire browser tab, as this may discard unsaved session data). 5. Save your page using the Save or Publish button to ensure the change is committed. 💡 Tips to Avoid Confusion - Do not rely on the agent's confirmation message alone — always verify the change visually in the preview panel before saving. - If you are working across multiple pages, make and save changes one page at a time to ensure each edit is properly committed. - Clearing your browser cache is rarely necessary for Website Studio preview issues. Use the in-panel refresh option first. 🆘 Still Seeing the Issue? Although these bugs have been fixed, if you are still experiencing overlay changes that revert or a preview that does not match your edits, please let us know right away. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Header Navigation Dropdowns After Website Studio Import

🔍 What Is This Issue? When you import a multi-page website into Website Studio, the header navigation dropdowns may stop working correctly. You might notice links that no longer expand, missing items in the navigation bar, or a completely broken menu. The build process may also fail as a result of these navigation issues. This is a known bug that our team is actively investigating. There are currently no confirmed self-serve steps to resolve it independently. ⚠️ Why This Happens This issue occurs during the Website Studio import process. Importing a website can cause header navigation dropdowns to break and the site build to fail. The exact root cause is under investigation by our engineering team. 📋 How to Get This Resolved Because this is a bug requiring backend investigation, please escalate to our support team. To help us investigate as quickly as possible, have the following information ready before reaching out: - Your project name in Website Studio - The URL or source of the site you imported - A description of the navigation behavior you are seeing (e.g., dropdowns not expanding, missing menu items, broken menu) - Any error messages displayed during or after the import or build process - The approximate date and time when the issue first 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 Menu Editing Errors in Website Studio

🔍 Overview When editing menus in Website Studio, you may encounter errors such as "Generation Failed", "Something Went Wrong", or "Site-wide edit couldn't be completed." These messages can appear when removing, rearranging, or renaming menu items, and may cause your changes to revert to their previous state. This article explains why these errors occur and walks you through the steps to resolve them. ⚠️ Common Symptoms - A "Generation Failed" error appears after submitting a menu edit prompt. - A "Something Went Wrong" message blocks your changes from saving. - The Website Studio agent enters a loading loop for more than a few minutes with no result. - Your menu reverts to its original state after an attempted edit. - A "Site-wide edit couldn't be completed" notice appears after bulk or page-level operations. - Your edit is applied to the wrong page because the agent inferred the target from your wording instead of the page you were viewing. 💡 Why This Happens These errors are typically caused by one or more of the following: - Ambiguous prompt wording: The AI agent may misinterpret your instruction and attempt to edit the wrong page or element, causing the build to fail. - Conflicting bulk operations: Running multiple edits at the same time can cause the generation process to time out or produce an error. - Temporary platform instability: Occasional server-side issues can interrupt the build pipeline, causing generation failures that are not related to your specific edit. - Complex structural changes: Removing or reordering several menu items in a single prompt increases the chance of a generation error. 🚀 How to Fix It 1. Refresh the page and try again. Many generation errors are transient. Close the error message, refresh your browser, and resubmit the same edit before trying anything else. 2. Simplify your prompt. Break your request into smaller, specific steps. Instead of asking to remove and rearrange multiple items at once, edit one menu item at a time. For example: "Remove the 'Blog' item from the main menu" rather than "Remove Blog, move Services before About, and rename Contact to Get in Touch." 3. Be explicit about the target page. To prevent the agent from editing the wrong page, always name the page clearly in your prompt. For example: "On the Homepage, remove the 'Portfolio' link from the navigation menu." Navigate directly to that page in Website Studio before submitting your edit. 4. Wait for one operation to finish before starting another. Avoid submitting a new prompt while the agent is still processing. If the agent appears stuck in a loading loop for more than five minutes, refresh the page and try again. 5. Clear your browser cache. A stale cache can sometimes interfere with Website Studio's build process. Clear your cache, reload the platform, and retry your edit. 6. Try a different browser. If errors persist, open Website Studio in a different browser (Chrome, Firefox, or Edge) to rule out browser-specific issues. ✅ Best Practices for Menu Editing - Make one change at a time and confirm it saves successfully before moving on. - Always navigate to the specific page you want to edit before writing your prompt. - Use clear, direct language in your prompts, naming both the menu item and the page it belongs to. - Avoid running menu edits alongside other bulk site-wide operations. - If an error occurs, do not resubmit the same prompt repeatedly — refresh first, then try a simplified version. 🙋 Still Seeing Errors? If you have followed all the steps above and the error persists, our team is ready to 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 Header Dropdowns and Build Errors After Import

🔍 Overview When you import a multi-page website into Website Studio, the imported site's header navigation — including dropdown menus — may not render correctly. You may also encounter build failures or HTTP 403 errors when attempting to fix these issues using the AI agent or an external editor via the Search Atlas MCP (SA MCP). This article explains why these issues occur and the steps you can take to resolve them. ⚠️ What You Might Experience - Header dropdown menus are missing or unresponsive after import. - AI agent prompts inside Website Studio fail to repair the navigation. - Editing via Claude with SA MCP results in build failures. - HTTP 403 (Forbidden) errors appear during build or save attempts. - Certain pages are not listed under their expected parent menu items. 💡 Why This Happens Website Studio processes imported sites by parsing their HTML and assets. During this process, complex header and footer components — especially those with nested dropdown structures — may not be fully fetched or rendered. This is a known limitation when importing ZIP or HTML-based projects. Additionally, if the project's structure is partially broken after import, the AI agent and external MCP connections may lack the permissions or clean state needed to apply fixes, resulting in 403 errors and failed builds. 🛠️ Step-by-Step: How to Fix the Issue 1. Open Website Studio. In the left sidebar, click Website Studio (URL: /website-studio) to open your project list. 2. Open the affected imported project. Select the site that has the broken header navigation. 3. Manually rebuild the header navigation block. Instead of relying on the imported header, delete the broken header component and replace it with a fresh navigation block from the Website Studio component library. Recreate your dropdown menu items manually using the available menu and submenu components. 4. Re-add your pages to the navigation. Ensure each page in your site is explicitly linked inside the new navigation component. Dropdown items pointing to internal pages must be set using the page slug (for example, /products/metal-buildings) rather than a full external URL. 5. Test the dropdown menus. Use the Preview mode to confirm that all parent menu items expand correctly and that nested pages are reachable. 6. Avoid using SA MCP on a broken project state. If the project contains build errors, resolve them inside Website Studio first before connecting an external editor. Attempting MCP edits on a broken project can trigger 403 permission errors because the build pipeline rejects changes to an invalid project state. 7. Re-import only if necessary. If the project is too broken to repair in place, use Import Site again from the Website Studio dashboard to start a clean import. Before importing, simplify the source HTML — remove any JavaScript-driven mega-menus and replace them with standard anchor-based dropdowns to improve import compatibility. ✅ Best Practices for Importing Sites - Before importing, simplify complex navigation: replace JavaScript-rendered dropdowns with standard HTML anchor lists where possible. - After any import, immediately preview the header and footer to catch rendering issues early. - Build and verify the site inside Website Studio before connecting SA MCP for external edits. - Keep page slugs consistent and lowercase with hyphens (e.g., /metal-rv-carports) to avoid slug resolution errors in the navigation. 🚧 Known Limitations - ZIP and HTML imports do not always fully fetch or render header and footer components — these may need to be rebuilt manually. - The AI agent works best on structurally valid projects; it cannot reliably repair deeply broken navigation structures from a failed import. - HTTP 403 errors during MCP-assisted builds indicate a project state or permissions issue on the build pipeline, not an error with your MCP configuration itself. 💬 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 Broken Header Navigation Dropdowns in Website Studio

🔍 Overview When you import a multi-page website into Website Studio, the header navigation — including dropdown menus like Services — can sometimes stop working after the migration is complete. Links may appear in the menu but fail to open, or the dropdown may not respond to clicks at all. This article explains why this happens and what to do about it. ⚠️ Why This Happens During a website import into Website Studio, navigation elements such as header dropdowns may not be fully restored as part of the migration process. This is a known behaviour tied to how navigation structure is rebuilt during import. 🛠️ What to Do If Your Navigation Dropdowns Are Broken Because broken header navigation dropdowns after a site import require investigation on the backend, there are no self-serve steps that reliably resolve this issue. To get this fixed as quickly as possible, please have the following information ready before reaching out: - The name of the project affected in Website Studio - The URL of the imported site or the source it was migrated from - A description of which dropdown menu items are broken (for example, which menu label and which sub-pages are affected) - Any error messages or unexpected behaviours you observed during or after the import - The approximate date and time the import was completed A member of our team will investigate the navigation issue and restore the affected dropdowns on your behalf. 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 Download and Menu Errors

🔍 Overview Some customers have encountered errors in Website Studio related to downloading a project as an HTML file and editing menus or applying layout changes. This article explains what to do if you experience either of these issues. 📥 HTML Download Error If you receive an error when attempting to download your Website Studio project as an HTML file, our team will need to investigate further on your behalf. When reaching out, please have the following ready so our team can investigate as quickly as possible: - Your project name - The exact error message you are seeing 🗂️ Menu and Navbar Changes Not Applying If you are experiencing an error when editing menus or applying layout changes in Website Studio — such as changes appearing to save but not being reflected on your site — our team will need to look into this on your behalf. When reaching out, please have the following ready so our team can investigate as quickly as possible: - Your project name - The exact error message you are seeing 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 White Overlay Issues in Website Studio

Overview When building or editing a site in Website Studio, you may notice a white overlay appearing over hero images or photo sections. Attempts to remove it may only partially work or seem to have no effect at all. This is a known bug that our engineering team is investigating. What Is Happening White overlays persisting on images in Website Studio is a known issue. Edits intended to remove or adjust the overlay may not take full effect, leaving the overlay in place even after changes appear to have been applied. Because this is a bug, it cannot be fully resolved through self-serve steps at this time and requires investigation by our team. How to Escalate This Issue To help our team investigate and resolve this for you as quickly as possible, please have the following information ready before reaching out: - Your project or site name in Website Studio - The specific page and section where the white overlay is appearing (e.g. the hero section on the homepage) - A screenshot or screen recording showing the overlay as it currently appears - A description of what you have already tried to remove the overlay - The approximate date and time when you first noticed the issue Providing these details upfront will allow our team to reproduce and address the problem faster. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Menu Text Editing Issues in Website Studio

🔍 Overview Some customers have reported that menu text edits made in Website Studio do not apply as expected. This is a known bug that has been escalated internally. This article explains what to expect and how to get help if you are affected. ⚙️ What Is Causing This Issue? The bug affects how Website Studio applies certain menu and navbar text edits. You may experience menu text remaining unchanged despite attempts to edit it. Our team is aware of this issue and is actively investigating the root cause. ✅ Current Status This issue has been identified and escalated internally. If you are currently experiencing problems with menu text edits not applying in Website Studio, please reach out to our support team so your case can be tracked and addressed as the investigation progresses. 🆘 Still Experiencing the Issue? If menu text edits are still not applying for you, please have the following information ready when you contact us: - Your project or site name in Website Studio. - A description of the specific menu text change you are trying to make. - The approximate time you first noticed the issue. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Website Studio Menus, Reverts, and Blog Images

🗺️ Overview Several known issues in Website Studio can affect your workflow: unwanted menu items appearing in the header, excessive credit consumption when reverting changes, blog posts losing content after a revert, and blog article preview images not displaying correctly. This article explains what causes each issue and what you can do right now. 📋 Known Issues at a Glance - Unwanted menu changes: AI-generated edits sometimes add or rearrange header navigation items without being asked. - Revert causes data loss: Reverting one change can inadvertently wipe unrelated content, including blog posts. - Credit consumption on revert: Each revert action may consume credits even when no visible change is applied. - Blog preview images not displaying: Featured images set on blog articles may not render in the article listing or preview cards. 🔍 Unwanted Menu Changes in the Header When you ask Website Studio to make a change — for example, updating a section's colour or copy — the AI may also modify your header navigation as a side effect. This is a known bug that our team is actively investigating. What to do: 1. After any AI edit, review your header navigation immediately before making further changes. 2. If a menu item has been added or removed incorrectly, try stepping back to the previous state using any available revert or undo functionality within Website Studio. 3. Avoid chaining multiple AI prompts in quick succession until you have confirmed each change looks correct. Tip: Keep your prompts focused on a single element or section at a time. Broad prompts (for example, "improve the whole page") are more likely to produce unintended side effects. 💳 Excessive Credits Consumed During Revert Reverting a change is supposed to restore your site without spending additional credits. A bug has been identified where the revert action consumes credits even when the visible result is unchanged. What to do: 1. If you notice an unexpected credit deduction after a revert, note the time and the action you performed. 2. Contact our support team and share those details — our team can review your usage log and restore credits where appropriate. 📝 Revert Wiping Blog Posts One of the more serious bugs involves a revert of an unrelated change causing blog posts to be lost. This is a known issue that our team is investigating. What to do: 1. Before performing any revert, take note of your current blog posts so you have a record of existing content. 2. If blog posts have been lost after a revert, do not make further changes — contact our support team immediately with your project name, the approximate time of the revert, and a description of the content that was affected. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Website Studio Overlay & Credit Reset

🔍 Overview Some customers experience a persistent black gradient overlay on their Website Studio site, or have questions about their credit quota after encountering issues in the editor. Because both of these problems require backend investigation, our support team will need to look into your account directly to resolve them. 🧭 How to Access Website Studio 1. Log in to your Search Atlas account. 2. In the left sidebar, click Website Studio. 3. Select the site and page where the overlay issue appears. ⚙️ About the Persistent Overlay Issue If you are seeing a black gradient overlay that keeps reappearing on your Website Studio page even after you attempt to remove it, this is a known issue that requires backend investigation. Attempting additional edits to work around it may not resolve the problem and could complicate the investigation. 🛠️ What to Do Because this issue requires a technical specialist to investigate the underlying data for your page, there are no self-serve steps that are guaranteed to resolve it. To get this fixed as quickly as possible, please have the following information ready when you contact support: - The name of the affected site and the specific page where the overlay appears. - The exact steps you took before the overlay appeared or reappeared (for example, whether you duplicated a page or used an AI-powered edit). - Any error messages you saw, including the exact wording and when they appeared. - The approximate date and time the issue started. - Whether your credit balance appears to have been affected, and if so, how many credits you believe were incorrectly deducted. 📊 About Credit Quota Concerns If you believe your credit balance was affected as a result of failed or repeated fix attempts in Website Studio, our team can review your account and assess whether a quota adjustment is appropriate. Please include the details listed above when you reach out so the review can be completed efficiently. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Website Studio Navigation Header Issues

Overview Some customers using Website Studio have encountered issues where the navigation header appears inconsistently across pages, dropdown menus fail to render correctly, or site-wide header edits do not apply as expected. This article explains what to do if you are experiencing these issues. Known Issues and Current Status Navigation header uniformity and dropdown rendering issues have been reported in Website Studio. If you are experiencing symptoms related to inconsistent header display or dropdown menus not behaving as expected, our team is aware of these problem areas and is working to address them. What to Do Because these are platform-level issues, there are no confirmed self-serve steps that reliably resolve them. If you are affected, please escalate to our support team and have the following information ready: - Your project or site name - A description of the specific header or dropdown behaviour you are seeing (for example, whether the header is missing on certain pages or whether dropdown edits are not applying) - The specific pages affected - Approximately when the issue began Having this information ready will allow our team to investigate your account directly and work toward a resolution as quickly as 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 AI Logo Placement in Website Studio

Overview When using the AI website builder in Website Studio, you may find that your logo is not placed where you specified — for example, it should appear in the header on the left and centered on the main page, but the AI positions it incorrectly. This is a known issue. If you encounter this problem, please contact our support team so we can assist you directly. Known Issue Our team has identified that the AI website builder can fail to follow logo placement instructions during page generation in Website Studio. Because this issue originates in the AI page generation process, the correct resolution depends on your specific page and setup. Our support team will review your case and guide you through the appropriate next steps. What to Prepare When You Contact Support To help us resolve your logo placement issue as quickly as possible, please have the following ready when reaching out: - A screen recording or screenshot showing the incorrect logo placement - A description of where you intended the logo to appear and where it is actually appearing - The name of the website or page affected - Any instructions or prompts you provided to the AI regarding logo placement If you need further help, please reach out to our support team via the chat widget and we will be happy to assist you.

Hero Overlay Opacity Not Updating in Website Studio

🔍 What Is This Issue? When editing a hero section in Website Studio, you may find that adjusting the overlay opacity appears to apply successfully — but the preview does not update to reflect your changes. This means the visual change is silently failing in the background, even though no error message is shown. This is a confirmed bug in Website Studio. The platform reports a successful change, but the overlay opacity update is not rendered in the preview. ⚙️ Who Is Affected? You are likely experiencing this issue if: - You are editing a hero section inside Website Studio. - You have adjusted the overlay opacity on a hero image or background. - The preview continues to show the original opacity despite your changes appearing to save. - No error message or warning is displayed during the edit. 📋 What You Should Do Right Now Because this is a confirmed platform bug, the preview may not reflect overlay opacity changes immediately. Try the following workarounds in order before contacting support: 1. Hard-refresh the editor. After saving your opacity change, press Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac) to force a full page reload, then reopen your hero section and check whether the preview has updated. 2. Exit and re-enter the hero section editor. Navigate away from the hero section to another section of your page, then click back into the hero section. This can force the preview to re-render with your saved value. 3. Try a different browser or clear your browser cache. Open Website Studio in a different browser (e.g., switch from Chrome to Firefox or Edge) or clear your current browser's cache and cookies, then reload the editor. Cache issues can prevent preview updates from displaying correctly. 4. Re-enter the opacity value manually after refreshing. If the preview still does not reflect your change after a refresh, re-enter your intended opacity value, save again, and check whether the combination of a clean cache and a fresh save resolves the display issue. 5. Note your intended opacity value. Keep a record of the exact opacity setting you want so you can reapply it quickly if needed after any of the above steps. 6. Save your current page state to preserve any other edits you have made to the hero section. 🚀 What Happens After the Fix Is Released? Once the fix is live, you will be able to adjust hero overlay opacity in Website Studio and see those changes immediately reflected in the preview. No additional steps will be required on your end — simply return to your hero section and apply the opacity setting you need. 💡 Tips for Working with Hero Sections While you work through the steps above, here are some general best practices for managing hero sections in Website Studio: - Complete all other hero section edits (text, images, layout) so your page is otherwise ready to publish. - Test other sections of your page to ensure the rest of your design is rendering as expected. If none of the steps above resolve the issue, please reach out to our support team via the chat widget so we can investigate your specific page and assist you directly.

🗂️ Website Builder: Automatic Navigation Grouping for Sites with 8+ Pages

When your Search Atlas website grows beyond 8 pages, the Website Builder automatically reorganizes your navigation bar from a flat list of links into grouped dropdown categories. No settings to configure — you add pages and your navigation stays clean. 🗂️ What Automatic Navigation Grouping Does On a small site, a flat list of navigation links works fine. On a larger site, that flat list becomes cluttered and hard for visitors to scan. Automatic navigation grouping solves this by organizing your pages under category labels in the navigation bar, each of which expands into a dropdown menu when a visitor interacts with it. ⚡ When Navigation Grouping Activates Grouping is triggered entirely by your page count — no manual step is required: - 8 pages or fewer: Every page appears as an individual link in the navigation bar. - More than 8 pages: Pages are automatically organized into dropdown category groups in the navigation bar. The Website Builder detects your page count and applies the correct navigation layout for you. You will see the change reflected as soon as your site crosses the 8-page threshold. 👁️ How Grouped Navigation Appears to Your Visitors Once grouping is active, your navigation bar displays category labels at the top level instead of individual page links. Visitors can click or hover on a category label to open the dropdown menu listing the pages within that group — both interactions are supported. Your header stays organized regardless of how many pages your site contains. 💡 Tips for Making Grouped Navigation Clear for Visitors Because grouping activates automatically, how intuitive your navigation feels depends on how your pages are named. Keep these points in mind as your site grows: - Use short, descriptive page names so visitors can quickly identify which dropdown category contains the page they need. - After adding your 9th page, preview your site to review how the grouped navigation looks from a visitor's perspective. - If a category label or grouping feels unclear, consider renaming the relevant pages to better reflect their content. Clear page naming makes grouped dropdowns immediately scannable and reduces the clicks visitors need to find what they are looking for. 🎯 You now know that the Website Builder automatically switches your navigation to grouped dropdown categories the moment your site exceeds 8 pages — keeping your header organized as your content scales. To learn more about building and structuring your site, explore the Website Builder overview.