Troubleshooting: Forms, Popups & Embeds

🛠️ Fix Website Studio Contact Page and Form Issues

🛠️ Remove Unauthorized Website Studio Forms

🔍 Why an Unexpected Form Appears Some Website Studio sites may display a “Request a Free Consultation” form that sends submissions to formsubmit.co, even when the form is not visible in the project code. This can happen when an older form or integration was included during site generation or publishing. The published output may contain the form separately from the code you are reviewing. This form is not necessarily evidence that your project was hacked. However, you should remove any form you did not intentionally add, especially if it collects visitor information or sends data to an unfamiliar service. 🧭 Confirm the Form Source 1. Open the affected published website in a private browser window. 2. Locate the unexpected form and note the page or pages where it appears. 3. Use your browser’s page-source or developer tools to search for formsubmit.co, “Request a Free Consultation,” or the form’s submit action. 4. Compare the published output with the current Website Studio project to confirm whether the form is absent from the project itself. 🧹 Remove the Form 1. Open Website Studio from the left sidebar. 2. Open the affected project and remove any visible form, embed, or custom code that you intentionally added. 3. Regenerate or update the site, then select Submit to publish the latest version. 4. Clear your browser cache or test in a private window, then verify that the form no longer appears on every affected page. If the form is not present in the project but remains on the published site, do not repeatedly edit unrelated sections. Record the affected site URLs and pages, then request an investigation. 📦 Can Engineering Remove Forms in Bulk? Bulk removal may be possible when multiple sites share the same generated form or publishing issue, but it is not a customer-facing bulk action. Engineering must first confirm the source, affected projects, and safe removal method. Changes are handled case by case to avoid deleting legitimate customer forms or other site content. When reporting multiple affected sites, provide the project names, published URLs, affected page paths, approximate discovery date, and whether the form is still present after republishing. This information helps the team determine whether a coordinated fix is appropriate. ✅ Prevent Future Issues - Review forms and external submission destinations before publishing a generated site. - Verify the live site after every major regeneration or publish. - Do not collect visitor information through a form unless you recognize and approve its destination. - Keep a list of approved forms, integrations, and submission services for each project. 💬 Get Help If the form continues to appear after republishing, or you need assistance reviewing several sites, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Remove Unauthorized Forms and Bulk-Edit Sites

🔍 What Is Happening? Some customers have noticed a "Request a Free Consultation" form appearing on their published city sites inside Website Studio. This form posts data to formsubmit.co, a third-party service, and was not intentionally added by you or your team. Our engineering team has identified this as a platform-level issue and a fix is currently in active development. You do not need to take action to trigger the bug — it can appear automatically on published Local Pages (city sites). ⚠️ Why This Matters Unauthorized forms on your published pages can: - Collect visitor data through a service you did not authorize - Undermine trust with your clients if they notice unexpected form fields - Conflict with your own contact forms or lead-capture setup Until the platform-level fix is deployed, you can manually remove these forms from your sites using the steps below. 🛠️ How to Remove the Unauthorized Form from a Single Site 1. In the left sidebar, navigate to OTTO SEO → All Sites. 2. Locate the city site that contains the unauthorized form and open it in Website Studio. 3. Open the page editor for the affected published page. 4. Select the "Request a Free Consultation" form block on the page. 5. Delete the form block and save your changes. 6. Re-publish the page to push the update live. Repeat this process for each individual site if you need an immediate fix before the bulk solution is available. 📊 How to Apply the Same Edit Across All 156 Sites We understand that editing 156 projects one at a time is not practical. Bulk editing across Website Studio projects is a capability our team is actively working to improve. Here is how to use the current bulk-action tools while that work is in progress: 1. In the left sidebar, go to OTTO SEO → All Sites. 2. Use the checkboxes on the left of each site row to select multiple sites. To select all sites at once, check the box at the top of the list. 3. With your sites selected, click Scan or review the available bulk-action buttons that appear in the toolbar (such as Freeze sites or Clear selection). 4. For bulk page-level edits such as removing a form block — if the action is not yet available in the toolbar for your account, contact our support team (see below) to request that the change be applied account-wide on your behalf while the self-serve bulk-edit feature is finalized. Important: Bulk page edits across a large number of projects may take several minutes to process. Do not close your browser tab while a bulk action is running. If the action appears to stall, refresh the page and check whether the changes were applied before retrying. ⚙️ Turning Off the Form Account-Wide A dedicated account-wide toggle to disable formsubmit.co forms across all sites is not yet available as a self-serve setting. However, our engineering team's in-development fix is intended to prevent these forms from appearing on any new or existing site once deployed. Until then: - You can remove the form manually from individual sites using the steps above. - You can contact our support team to request a bulk removal across your 156 sites while the fix is being finalized. - New sites you create after the fix is released will not include the unauthorized form. ✅ What to Expect Next - Platform fix in development: The engineering team is actively resolving the root cause. No ETA is published yet, but the ticket is prioritized. - Bulk-edit improvements: Error handling and reliability for bulk actions across large site counts is also being hardened as part of a separate update. - No data loss: Your own registered contact forms and lead data are not affected by this issue. 💬 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.

🖼️ Fixing Broken Images and Formatting When Syncing Content Genius to WordPress

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

🔧 Fix Website Studio Broken Links and Performance

Overview If links or buttons across your Website Studio sites are unresponsive, or if your browser is slowing down while editing, this guide covers what to do next. These issues can stem from a variety of causes within the builder or your local environment. What to Do If You Experience Broken Links or Slow Performance Because the specific cause of broken links or performance problems in Website Studio can vary from session to session and account to account, the most reliable path to a fix is to contact our support team directly. When you reach out, having the following information ready will help the team investigate and resolve your issue as quickly as possible: - The name of the affected Website Studio site or project. - A description of the broken element (e.g. a specific link, button, or menu item that is not working). - The browser and operating system you are using. - Any error messages you see on screen, including the exact wording. - The approximate time when the issue started or was first noticed. - Screenshots or a screen recording of the problem, if possible. Our team will review your account and site configuration to identify the root cause and advise on the correct fix. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Duplicate Form Submissions in Website Studio

🔍 Overview If your Website Studio waitlist or lead capture form is recording duplicate entries every time someone submits their email, you are not alone. This is a known issue that can happen due to a few common causes — including form configuration, browser behavior, and page setup. This article explains why duplicates occur and walks you through the steps to resolve them. ⚙️ Why Duplicate Submissions Happen Duplicate form entries in Website Studio are typically caused by one or more of the following: - No submission confirmation or redirect: If the form does not redirect the user or display a clear success message after submission, visitors may click the submit button more than once, assuming the first attempt did not register. - Missing submit button disable state: Without disabling the submit button after the first click, rapid or repeated clicks can fire multiple submission events. - Browser back-button behavior: Users who navigate back to the form page after submitting may trigger a browser form resubmission prompt, which can log a second entry. - Page published without saving latest changes: An outdated published version of the page may not include form settings you have already updated inside Website Studio. 🛠️ How to Fix Duplicate Submissions Follow these steps inside Website Studio to address the most common causes: 1. Open Website Studio: In the left sidebar, click Website Studio (URL: /website-studio) to access your pages. 2. Select the affected page: Locate the page containing your waitlist form and open it in the editor. 3. Check your form success action: Click on the form element, then open its settings panel. Confirm that a success action is configured — either a redirect to a thank-you page or a visible success message. This prevents users from submitting the form a second time out of uncertainty. 4. Enable post-submit button state: In the form settings, look for an option to disable or hide the submit button after a successful submission. Enabling this prevents multiple clicks from registering as separate entries. 5. Add or verify a thank-you redirect: Redirecting users to a separate confirmation page after submission stops the browser from resubmitting the form if the user presses the back button and confirms resubmission. 6. Save and republish the page: After making changes, click Save and then Publish to ensure the live version of your page reflects your updated form settings. Unpublished changes will not affect live form behavior. ✅ How to Verify the Fix Once you have updated your form settings and republished the page, test the form yourself: - Submit the form using a test email address. - Confirm that a success message appears or that you are redirected to a thank-you page immediately after submission. - Try clicking the submit button a second time or navigating back — the form should not register an additional entry. - Check your submissions list to confirm only one entry was recorded for your test email. 🧹 Cleaning Up Existing Duplicate Entries If duplicate entries have already been recorded in your form submissions, you will need to remove them manually. Open your submissions data, sort by email address, and delete any repeated entries. There is currently no bulk-deduplicate tool within Website Studio, so this cleanup must be done entry by entry. 💡 Best Practices to Prevent Future Duplicates - Always configure a success redirect or confirmation message for every form on your site. - Test every form after publishing to verify it behaves as expected on the live page. - Avoid publishing pages directly from a cached or previously saved draft without reviewing current form settings first. - If you clone an existing page using the Clone an Existing Page action in Website Studio, double-check the cloned form settings before publishing — cloned forms inherit the original settings and may not have a success action configured. 💬 Still Seeing Duplicate Entries? If you have followed all the steps above and duplicate submissions are still occurring, there may be a platform-level issue that requires investigation. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Using the Website Builder: HTML Import, Blog Pages, and Credit Usage Explained

📋 Overview The Search Atlas Website Builder lets you create pages, import existing HTML, and publish a blog. This article explains how each of these features behaves so you can avoid common surprises, such as imported pages replacing your homepage, blog pages returning a 404 error, or credits being used unexpectedly. 📥 How HTML Import Works When you import an HTML file, the Website Builder treats that file as a complete page. It is important to understand what the importer does and does not do before you upload. ✅ What to expect - An imported HTML file is added as a new page, not merged into an existing one. - Depending on your project settings, an imported page can be set as the homepage if it is the first or primary page in the upload. - The importer does not automatically preserve your existing navigation menu or internal links. 🤔 Why importing can appear to "wipe out" your pages If you import HTML into an existing project and your previous pages are no longer visible, one of the following usually happened: - The import was performed on a new or empty workspace rather than your live project. - The imported page was assigned as the homepage, so it now loads at your root URL and hides the original landing page from view. - The existing pages still exist but are no longer linked in your navigation menu, so they appear "missing." 👉 Recommended steps before importing 1. Open your project and confirm you are working in the correct workspace. 2. Use Duplicate Project or export a backup so your current pages are saved. 3. Import your HTML file. 4. Go to Pages and confirm all expected pages are still listed. 5. If the imported page was set as the homepage by mistake, open Page Settings and reassign the correct homepage. 6. Review your navigation menu and re-add any links that were not carried over. You can confirm a project was created through HTML import by the Imported badge shown on the builder dashboard. (Earlier versions sometimes labeled these projects "Free Mode" instead of "Imported"; this has been corrected.) 🚫 Why a Blog Page Shows a 404 Error A 404 error means the page could not be found at the requested URL. With blog pages, this is almost always a configuration step rather than a defect. 🔍 Common causes - The page is not published. Draft or unpublished blog posts return a 404 to visitors until they are published. - The blog feature is not enabled for the project, so the /blog path has no destination. - The URL slug was changed or contains a typo, so the live URL no longer matches. - Changes have not been republished. Edits in the builder go live only after you publish. - DNS or domain connection is incomplete, so the blog path cannot resolve on your custom domain. 🔧 How to fix it 1. Open Content → Content Genius ("What are we writing today?") and confirm the post status is Published in the articles list's Status column. 2. Verify the blog feature is enabled in your project settings. 3. Check the page slug for typos and confirm it matches the URL you are testing. 4. Click Publish to push your latest changes live. 5. Confirm your domain is fully connected under Domain Settings. 6. Clear your browser cache or test in a private window to rule out a cached error. 📝 Notes for imported projects - Adding several blog posts at once on an imported project can take noticeably longer to process, so a post may appear missing or return a temporary 404 until processing finishes. Allow the operation to complete, then republish and retest. - Previously reported issues where blogs did not publish on imported projects, or where blogs disappeared from an imported project after downloading the project ZIP, have been resolved. If you encounter this behavior, make sure you are on the current version and republish. - Known issue (in progress): adding a blog to an imported project that already contains a blog section can produce duplicated blog sections on the published URL. Our engineering team is actively working on a fix. If you hit this, contact support and we can help you remove the duplicate section. 💳 How Credits Are Used Credits are consumed when an action triggers processing on our servers, such as generating content with AI, building pages, or publishing. We understand it can be frustrating to see credits used when a feature does not appear to work, so here is how to think about it. ⚡ What consumes credits - AI-generated content (such as blog posts or page copy). - Bulk actions like generating multiple pages at once. - Certain import and publishing operations that require processing. ⚠️ Important notes about credits and errors - A credit is generally consumed when the action is processed, even if the resulting page is not yet configured or published. - A 404 error after generation usually means the page exists but still needs to be published or linked, not that the credit was wasted. - If a genuine system error prevented an action from completing, credits used for that failed action can be reviewed and refunded by our team. 💡 How to avoid unexpected credit use 1. Confirm your project and settings are correct before running AI or bulk generation. 2. Generate one page first to confirm the result before running large batches. 3. Publish and test each new page so you can confirm it works. 📞 When to Contact Support Reach out to our support team if any of the following apply: - Pages disappeared and are not listed under Pages after an import, even after checking the homepage setting. - A published blog post still returns a 404 after republishing and verifying the slug and domain. - You see duplicated blog sections on the published URL of an imported project. - Credits were consumed by an action that failed due to a system error. When you contact us, please include your project name, the affected URL, a screenshot of the error, whether the project was created via HTML import, and the approximate time the issue occurred. This helps us review credit usage and resolve the issue faster.

🛠️ Fix Form Embedding Style Conflicts in Website Studio

🔍 Overview When you add or update a form in Website Studio, the AI agent may apply style changes that affect elements beyond the form itself — such as card colors, button styles, or overall page layout. This article explains why this happens, how to prevent it, and what to do if it has already occurred. ⚙️ Why This Happens Website Studio uses an AI agent to generate and embed forms. In some cases, the agent applies CSS or style rules too broadly, causing unintended changes to global styles. This is most common when: - You are editing an existing form rather than inserting a new one - Your project was originally imported via ZIP or HTML upload - The form prompt does not include enough scope-limiting instructions A known issue where imported projects experienced broken layouts after form changes has been resolved. However, broad style conflicts can still occur if prompts are not specific. ✅ How to Update a Form Without Affecting Global Styles 1. Open Website Studio. Go to the left sidebar and select Website Studio, or navigate directly to /website-studio. 2. Open your project and locate the page containing the form you want to update. 3. Write a scoped prompt. When instructing the agent, explicitly tell it to limit changes to the form only. For example: "Update the contact form fields only. Do not change any colors, fonts, buttons, or styles outside the form element." 4. Review the preview before confirming. After the agent generates a response, inspect the right preview panel carefully. Check cards, buttons, and other elements to confirm they are unchanged. 5. Accept or regenerate. If you notice unintended style changes in the preview, reject the change and refine your prompt before trying again. Avoid accepting changes that look incorrect, as reversing them may consume additional credits. 💡 Best Practices to Avoid Style Conflicts - Be specific in every prompt. Always tell the agent exactly what to change and, equally important, what not to change. - Make one change at a time. Avoid combining form updates with other design requests in a single prompt. - Use the preview panel. Always review the full page in the right preview panel before accepting any agent-generated change. - Save a working version first. Before editing a form, use the HTML download option to save a backup of your current project state. 🔄 What to Do If Styles Are Already Broken If a form update has already changed colors, buttons, or cards unintentionally, try the following steps: 1. Use the undo option if it is still available in your current session. 2. Send a corrective prompt to the agent describing exactly what was changed and asking it to restore only those elements. For example: "Restore the original button color and card background color. Do not change the form." 3. Re-upload a saved backup using the HTML upload feature if you saved a copy before the issue occurred. 💳 Credits Used During Troubleshooting Credits are consumed each time the AI agent processes a prompt, including attempts that produce unexpected results. Search Atlas does not automatically reimburse credits used during troubleshooting. However, if you believe credits were lost due to a platform bug, our team can review your case. 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. 🆘 Still Need Help? If you have followed the steps above and are still experiencing style conflicts after embedding or updating a form, our support team is ready to assist. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

📋 Configure Form Notifications and Clickable Phone Numbers

Overview Inside Website Studio you can route form submission notifications to a specific email address and turn phone numbers into one-tap dial links. This article explains what these features do and how to get assistance setting them up correctly. Getting to Website Studio In the left sidebar, click Website Studio (URL: /website-studio). Open the site you want to edit, then enter the page editor. Setting the Email Address for Form Notifications Website Studio allows you to configure which email address receives notifications when a visitor submits a form on your site. To set this up, open the page editor and click on the form element you want to configure, then look for the form's settings or properties options to enter the destination email address. Because the exact location of these settings can vary depending on your site setup, we recommend reaching out to our team for guided assistance to ensure the correct email is saved and notifications are delivered reliably. What to have ready when you contact us: - The name of the Website Studio site you are editing. - The email address you want form submissions sent to. - The name or location of the specific form on the page. Making Phone Numbers Clickable for Dialing A clickable phone number uses a tel: link, which tells the device to open its dialer automatically when a visitor taps or clicks the number. To create one, you select the text or button containing the phone number in the page editor and add a link using the tel:+[countrycode][number] format — for example, tel:+15551234567 for a US number, with no spaces, dashes, or parentheses. If you are unsure where to find the link option in the editor or the dialer is not opening as expected after setup, our team can walk you through the exact steps for your site. What to have ready when you contact us: - The site name and the page where the phone number appears. - The phone number you want to make dialable, including country code. - A description of what you see when you try to add a link to the element. Troubleshooting Tips - Form notifications not arriving: Check the spam or junk folder first, then verify the destination email address is entered correctly in the form's settings. - Phone link not opening the dialer: Confirm the link value starts with tel: and contains no spaces or special characters other than the leading + before the country code. - Changes not saving: Try refreshing the page editor and re-entering the settings, then save again before previewing. 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 Formatting and Routing Issues

🔍 Overview Some customers have reported that pages in Website Studio display without formatting — appearing as a plain white page with only raw images or text — while attempts to fix the issue using the Website Studio AI do not resolve it. Related problems include routing errors when creating new pages and unintended content duplication. This article explains why these issues occur and the steps you can take to resolve them. ⚠️ Why This Happens These issues can occur due to a combination of factors in Website Studio: - Rendering failures: Page components such as headlines, logos, and review blocks may fail to load their associated styles, resulting in a stripped, unformatted appearance. - Routing conflicts: When a new page is created, the platform may not correctly assign a unique route, causing errors or duplicating content from an existing page. - AI misclassification: The Website Studio AI agent may misclassify a new standalone page request as a blog post, meaning no actual page is created and the route remains broken. - Sync issues: If your project is connected to an external platform such as WordPress, syncing may publish a blank or unstyled version of the page. 🛠️ Step-by-Step Troubleshooting 1. Open Website Studio. In the left sidebar, click Website Studio (URL: /website-studio) to access your project. 2. Locate the affected page. Find the page that is displaying without formatting. Click on it to open the editor. 3. Refresh the page editor. Close the page and reopen it. In some cases, a temporary rendering failure clears on reload. 4. Check the page type. Confirm the page was created as a standalone page and not classified as a blog post. If it appears under a blog section, it was likely misclassified by the AI agent. You will need to recreate it using the correct page type. 5. Recreate the page manually. If the formatting loss persists, use the Clone an Existing Page option from the Website Studio home screen to duplicate a correctly formatted page as a starting point, then replace the content. This avoids the routing and classification issues that can occur when starting from scratch via the AI prompt. 6. Check for routing conflicts. If you receive a routing error after creating a new page, check whether another page in your project is using the same URL slug. Rename the slug of the new page to something unique and save. 7. Avoid using Website Studio AI to fix formatting. The AI agent has known limitations in diagnosing and correcting style rendering issues. Manual editing or cloning is more reliable for resolving formatting loss at this time. 8. Review sync settings before publishing. If your project syncs to WordPress or another external platform, preview the page inside Website Studio first to confirm formatting is intact before triggering a sync. Publishing a page with a rendering failure may result in a blank page on the connected site. ✅ Confirming the Issue Is Resolved After completing the steps above, verify the following: - The page displays with full formatting — fonts, layout, logos, and review components all render correctly in the Website Studio preview. - The page URL slug is unique and loads without a routing error. - No duplicate pages have been created. If duplicates exist, delete the extras from the page list in Website Studio. - If syncing to an external platform, confirm the published version matches the preview inside Website Studio. 🚫 Known Limitations The following behaviours are known issues that our engineering team has addressed in recent updates. If you are still experiencing them, your project may need a manual review: - Headlines, logos, and review blocks rendering without styles on certain page templates. - The Website Studio AI agent creating a blog post instead of a standalone page when prompted. - Duplicate success notifications appearing after page actions, which may indicate the action ran more than once and created duplicate content. 💬 Get Additional Help If the steps above do not resolve your formatting or routing issue, our team can investigate your specific project and page configuration. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

📋 Fix Website Studio Booking Form Submission Issues

🔍 Overview If your Website Studio booking or contact form is not showing a confirmation message, not sending notification emails, or not recording submissions after a user clicks Submit, our team is aware of issues affecting form submission and confirmation messaging in Website Studio. This article explains what to expect and how to get help. ⚠️ About This Issue Booking form submission failures and missing confirmation messages in Website Studio are known to occur. Because this is a backend issue, the root cause and resolution require investigation by our technical team on a per-account basis. There is no guaranteed self-serve fix at this time. 📋 What to Have Ready When You Escalate To help our team investigate and resolve your issue as quickly as possible, please have the following information ready before reaching out: - Your project or page name in Website Studio where the form is located - The exact symptoms you are seeing — for example, whether the form shows no confirmation message, shows a success message but no email is received, or shows an error on submission - Whether the page was AI-generated or built manually - The approximate date and time when the issue first occurred or when a specific failed submission happened - Any error messages displayed on screen, copied verbatim ✅ What a Correctly Working Form Should Do Once the issue is resolved, your form should display a confirmation message to the visitor immediately after they click Submit, and you should receive a notification at your configured destination. If either of these is missing, the issue has not yet been fully resolved and should be escalated. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fixing Elementor Formatting Issues After Content Genius Sync

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

🛠️ Fix Missing Fields in Website Studio Lead Forms

🔍 Overview When a contact submits a form on a landing page built in Website Studio, all completed fields — such as First Name, Last Name, Zip Code, Service, and Message — should be included in the lead notification. If those fields are missing from the submission, the lead data becomes incomplete and may not sync correctly into your client's CRM. This article explains the most common causes and the steps you can take to resolve the issue. ⚙️ Common Causes of Missing Form Fields - Field mapping not configured: Form fields that are added to the page but not properly mapped to a submission variable will not pass data through on submit. - Custom field names not saved: If a field label was changed after the form was built, the underlying field name may not have updated to match. - Form published before fields were added: Fields added after the initial publish may not be active on the live page if the page was not republished. - Third-party CRM integration mismatch: The field names in Website Studio must exactly match the expected parameter names in your CRM or webhook endpoint. ✅ Step-by-Step: Verify and Fix Your Form Fields 1. Open your project in Website Studio. Navigate to the landing page that contains the lead form. 2. Click on the form element to open its settings panel. 3. Review every field in the form. Confirm that each field — First Name, Last Name, Zip, Service, Message, or any custom field — is present in the form builder and has a unique, descriptive field name (not left as a default placeholder like field_1). 4. Check field mapping. For each field, ensure the Field Name value in the settings panel matches the parameter your CRM or notification system expects. Field names are case-sensitive — firstName and firstname are treated as different values. 5. Remove and re-add any fields that appear misconfigured. If a field looks correct but data is still missing, delete it from the form, re-add it fresh, and reassign its field name. 6. Save your changes and then republish the page. Changes made inside the editor are not reflected on the live page until the page is republished. 7. Submit a test lead using the live published URL (not the preview mode). Check the submission in Website Studio and in your CRM to confirm all fields are now populated. 📊 Reviewing Submissions Inside Website Studio You can audit all received submissions directly inside the platform without relying on email notifications or your CRM. - Go to Website Studio and open the relevant project. - Navigate to the Form Submissions section for that page. - Review each submission record to see exactly which fields were captured and which were blank. - Use the CSV Export feature to download a full submission history and share it with your client or import it into their CRM manually while you investigate the configuration issue. Comparing the exported CSV columns against the expected CRM fields is a quick way to identify any naming mismatches. 💡 Best Practices to Prevent Missing Fields - Always assign clear, consistent Field Name values when building a form — agree on a naming convention before you start (e.g., first_name, last_name, zip_code). - Republish the page every time you add, remove, or rename a form field. - Run a test submission immediately after publishing any new form or after making changes to an existing one. - Keep a record of the field names used in Website Studio and share them with your client so their CRM admin can map the fields correctly on their end. - If you use UTM parameter tracking, verify that UTM fields are not overwriting or conflicting with your custom form fields in the submission payload. 🚀 Still Seeing Incomplete Submissions? If you have followed all the steps above and lead form fields are still missing from submissions, the issue may require a deeper investigation of your specific form configuration or CRM integration 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 Content Genius Formatting and WordPress Sync Issues

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

📧 Configure Form Notification Emails in Website Studio

📋 Overview When someone fills out a form you have built in Website Studio — such as a free quote form or a contact form — you can receive an email notification for every new submission. This article walks you through the steps to set a recipient email address so those notifications reach your inbox. 🗺️ Where to Find the Form Settings All form notification settings live inside the Website Studio editor. To open it, click Website Studio in the left sidebar of your Search Atlas dashboard, or navigate directly to /website-studio. ⚙️ How to Add a Recipient Email for Form Notifications 1. Open Website Studio from the left sidebar. 2. Select the website that contains your form, then click Edit to open the page editor. 3. Click directly on the form element on the page canvas to select it. A settings panel will appear on the side. 4. In the settings panel, look for the field or option that allows you to enter a recipient email address for form notifications. 5. Enter the email address you want to receive submission alerts in that field. 6. Save and publish your changes to apply them to the live site. Once your changes are published, every new form submission will trigger an email notification to the address you entered. ✅ How to Test Your Form Notification 1. After publishing, open your published page in a new browser tab. 2. Fill out the form with a test name and email address, then submit it. 3. Check the inbox of the recipient email you configured. The notification should arrive within a few minutes. 4. If the email does not appear, also check your spam or junk folder, as automated notification emails can sometimes be filtered. 🔍 Troubleshooting: Notification Email Not Arriving - Double-check the email address you entered in the form settings — a single typo will silently misdirect all notifications. - Re-publish your site after making any changes. Edits made in the editor do not take effect on the live site until you publish. - Check your spam folder and add the Search Atlas sending domain to your email allowlist if notifications are being filtered. - Confirm the form is on a published page. Forms on unpublished or draft pages will not send live notifications. ❓ Frequently Asked Questions Can I send notifications to more than one email address? If you need submissions to reach multiple people, consider using a shared inbox or distribution alias (for example, team@yourdomain.com) as the recipient email address. If you have questions about your form notification setup that are not covered here, please reach out to our support team via the chat icon in your Search Atlas dashboard and we will be happy to help.

📧 Add a Recipient Email to Website Studio Forms

If you build a contact, quote, or lead form in Website Studio but never receive submissions in your inbox, the form most likely has no notification recipient set. Each form needs an email address where new submissions are sent. This guide shows you exactly where to add that address so you never miss a lead again. 🔎 Why You're Not Receiving Submissions When a visitor completes a form, the submission is captured by the platform. However, it is only emailed to you if a recipient email address has been added to that specific form's settings. By default, this field may be empty, which means the entry is stored but no notification is sent. Adding your email resolves this in a few clicks. There is also a separate Lead Notification Emails toggle that turns submission notifications on or off. Even with a recipient address set, no email will be sent if this toggle is switched off, so make sure it is enabled. ⚙️ How to Add a Recipient Email Follow these steps to set the notification email for your form: 1. Open Website Studio and load the page that contains your form. 2. Click directly on the form element so it is selected. 3. In the settings panel on the right, open the Form Settings (or Settings) section for that element. 4. Locate the Recipient Email or Send Submissions To field. 5. Enter the email address where you want to receive form submissions. 6. Confirm the Lead Notification Emails toggle is turned on. 7. Click Save to apply your changes. 8. Publish the site so the update goes live on your published page. Once published, every new submission will be delivered to the address you entered. 📬 Sending to More Than One Person If you want submissions to reach several people, add multiple email addresses in the same field, separated by commas. For example, enter both your sales and support addresses so each team receives a copy. Save and publish again after making the change. ✅ Test Your Form After publishing, confirm everything works: 1. Visit your published page in a new browser tab. 2. Fill out the form with test details and submit it. 3. Check the inbox of the recipient email you added. 4. If the message is not in your inbox within a few minutes, check your spam or junk folder. If the form itself returns an error when you try to submit it, rather than simply not sending an email, try republishing your site so it runs on the latest version, then test again. 🛠️ Still Not Receiving Emails? If you have added a recipient email, saved, and published but still see no notifications, run through this checklist: - Confirm the email address is spelled correctly with no extra spaces. - Make sure the Lead Notification Emails toggle is enabled for the form. - Make sure you clicked Save and then Published the site after editing. - Verify you edited the correct form if your page has more than one. - Check your spam, junk, and promotions folders. - Add the sender to your safe-senders or contacts list to prevent future filtering. You can also review stored submissions inside the platform's form or submissions area, which keeps a record of every entry even if an email notification was missed. 💬 Need More Help? If you have completed these steps and still are not receiving your form submissions, we're happy to help. If you need further assistance, click the chat icon in the bottom-right corner of the platform, then type "Human Teammate" to start a live chat with a member of our team.

⚠️ AI Page Builder Can't Edit Compiled JavaScript Bundle Uploads (Vite/Rollup)

If you upload a website that was exported as a compiled JavaScript bundle (for example a Vite or Rollup build), the AI page builder can't edit its pages because the content and navigation are locked inside minified code. Re-export your site so the content lives in standard editable HTML, and the editor will be able to make changes. 🔍 What's Happening With Compiled Bundle Uploads Some site exports place all of your page content and navigation inside a single minified JavaScript file (commonly named /assets/App-*.js). Each .html page is mostly empty and just loads that one bundle. Because the actual content lives inside minified JavaScript, the AI page builder can't safely read or modify it. Previously, the builder appeared to start working and then failed silently partway through creating or editing a page. Who Is Affected You may see this if your site was built with a Vite/Rollup-style static site generator (SSG) that compiles every page into one shared minified bundle. Sites whose .html files contain the real markup and navigation are not affected. What you'll see now: the upload is rejected up front with an HTTP 400 error explaining that the file type isn't supported, so you get a clear message instead of a silent failure mid-edit. 🛠️ Workaround: Upload an Editable HTML Version Re-export or rebuild your website so the page content lives in editable HTML rather than a compiled JavaScript bundle. Then upload that version. 1. Re-export or rebuild your site so each .html file contains the actual markup and navigation. 2. Avoid exporting from frameworks that produce a single minified /assets/App-*.js bundle (Vite/Rollup-style SSG builds). 3. Confirm that opening one of your .html files shows real page content and links, not just a script tag loading a bundle. 4. Upload the editable HTML version of your site again. Once you upload a site whose HTML contains the real content, the AI page builder can read and modify your pages and navigation as expected. 📡 Engineering Status Our team is aware of this behavior and has added an upload check that flags compiled JavaScript bundle sites right away. Instead of a silent failure during editing, you now receive a clear HTTP 400 message explaining that the file type isn't supported, so you know to upload an editable HTML version before you start working. 📞 When to Contact Support Reach out to our support team if: - You uploaded an editable HTML version of your site and the AI page builder still can't edit your pages. - You're unsure how to re-export your site so the content lives in standard HTML. - You see the HTTP 400 upload error and need help confirming what's inside your export. Share your site export and a short description of how it was built so we can help you confirm the right format. 🌀 Our team is on it — uploads are now flagged up front, and once you provide a site with editable HTML content, the AI page builder will be able to create and edit your pages without issue.

⚠️ Revert Taking 2–3 Minutes on ZIP, HTML, or Loveable Projects in Website Studio

If you click Revert on a project imported via ZIP, HTML, or Loveable in Website Studio and the page looks stuck, the action has not failed. Allow up to 3 minutes for it to finish, and avoid refreshing or clicking Revert again while it processes. 🔍 What's Happening After you import a project via ZIP, HTML, or Loveable in Website Studio and apply AI modifications, clicking Revert can take more than 2–3 minutes to complete. During this time the page may appear frozen, which can make it look like the action has hung or failed. This affects projects in Website Studio that were imported through one of these three methods. The revert is still running in the background — it is processing, not stalled. You'll know it has succeeded when the page finishes loading and your project returns to its previous state. 🛠️ Workaround Steps To let the Revert action complete successfully, follow these steps: 1. After clicking Revert on a ZIP, HTML, or Loveable-imported project, wait up to 3 minutes for it to finish. 2. Do not refresh the page, click Revert again, or navigate away, as this can interrupt the process. 3. Allow the operation to complete on its own. The revert will finish once processing is done. Once processing finishes, your project returns to its reverted state automatically. 📡 Engineering Status Our team is aware of this issue and is actively working on speeding up the Revert action for ZIP, HTML, and Loveable-imported projects. This is a known performance delay, not a data loss or failure — your project and changes remain safe while the revert processes. 📞 When to Contact Support Contact our support team if the Revert action does not complete after waiting the full 3 minutes, or if you see an error message during the process. When you reach out, include your project name and the import method you used (ZIP, HTML, or Loveable) so we can investigate quickly. 🌀 Our team is on it and actively working to make Revert faster — in the meantime, a couple of minutes of patience is all it takes for the action to finish successfully.

🛠️ Revert Not Updating in Real Time for ZIP and HTML Projects in Website Studio

If you click Revert on a ZIP- or HTML-imported Website Studio project and the preview still shows your AI changes, the revert did work — refresh your browser or switch pages to see the original version. A fix is rolling out now. 🔍 What's Happening in Website Studio After you apply AI modifications to a Website Studio project that was imported through ZIP upload or HTML upload, clicking Revert does not refresh the editor preview in real time. The page looks unchanged, so it can appear the revert failed. The revert actually succeeds on the backend. The original page state is restored — only the live preview display lags behind. Who is affected - Customers using Website Studio projects created via ZIP upload or HTML upload. - Anyone clicking Revert after applying AI modifications to those projects. Projects created through other import methods are not impacted by this display issue. 🛠️ Workaround to See the Reverted Page Use these steps to display the restored original version right away: 1. Click Revert on your ZIP- or HTML-imported project as usual. 2. Refresh your browser, or navigate to another page in the editor and then back to this one. 3. View the page — the reverted (original) state now displays correctly. You'll see your page restored to its original version, confirming the revert applied successfully. 📡 Engineering Status for This Issue Our team is aware of this display behavior and has addressed it. The fix is currently rolling out, after which the editor preview will update in real time when you click Revert. No action is needed on your part to receive the fix. 📞 When to Contact Support The revert is applied on the backend even when the preview looks unchanged, so the refresh workaround resolves the display in nearly all cases. Contact Search Atlas Support if: - You refresh the browser or switch pages and the original version still does not appear. - Your reverted content shows incorrect or missing elements after refreshing. Share your project name and import method (ZIP or HTML) so the team can review your case quickly. 🎯 Your revert is safe — the team has the fix in motion, and a quick refresh shows your original page restored in the meantime.

🛠️ Visual Edit Unavailable for ZIP or HTML Imported Projects in Website Studio

If you imported a site into Website Studio using a ZIP or HTML upload, Visual Edit is not yet available for that project. This article explains what's happening and gives you two ways to keep editing today. 🔍 What's Happening with Visual Edit on Imported Projects When you import a site into Website Studio via ZIP upload or HTML upload, the Visual Edit feature stays disabled for that project. There is no error message — the option is simply not available. For imported projects, this means you currently cannot use Visual Edit to: - Select elements inline on the page - Edit text directly in the visual preview - Apply style or colour changes through the visual editor Who's affected: only projects brought into Website Studio through ZIP or HTML upload. AI-generated projects created inside Website Studio are not affected and support full Visual Edit. 🛠️ How to Edit Your Project Right Now You have two reliable options depending on whether you've already imported the site. If you haven't imported yet and need Visual Edit Create the site as an AI-generated project in Website Studio instead of importing it via ZIP or HTML. Visual Edit is fully functional on AI-generated projects, so you can select elements, edit text, and change styles inline. If your project is already imported 1. Open your imported project in Website Studio. 2. Use the available code / HTML editing options to make your changes. 3. Save your edits as usual. These are partial workarounds. Full Visual Edit parity for imported projects is not yet available, so inline visual editing on those projects will not work until the update ships. 📡 Engineering Status Our team is aware of this limitation and is actively working to bring Visual Edit parity to ZIP and HTML imported projects. We'll share updates here as this progresses. 📞 When to Contact Support Reach out to Search Atlas support if: - Visual Edit is also disabled on an AI-generated project (not an import). - The code / HTML editing options do not let you make a change you need. - You want to confirm whether the Visual Edit parity update has shipped for imported projects. When you contact support, include your project name and whether it was created via ZIP upload, HTML upload, or as an AI-generated site so the team can help faster. 🎯 You're not blocked: AI-generated projects give you full Visual Edit today, and imported projects can still be updated through code editing while our team works to bring Visual Edit to ZIP and HTML imports.

🛠️ ZIP / HTML Upload Projects in Website Studio: Multi-Instruction Prompts Not Fully Applied

If you imported a Website Studio project from a ZIP or HTML upload, send your edits as separate single-action prompts, one at a time, so the AI applies every change reliably. This article explains the issue and the workaround you can use right now. 🔍 What's Happening On Website Studio projects that were imported from a ZIP or HTML upload, a single prompt that contains several instructions at once may not be carried out in full. When you combine multiple actions in one prompt — for example add pages, delete pages, change colors, and update text — the AI may: - Apply only some of the requested changes. - Make a change partially. - Skip or ignore an instruction entirely. The behavior is inconsistent from prompt to prompt. This affects ZIP and HTML upload projects specifically. Native (non-imported) Website Studio projects handle the same multi-instruction prompts correctly. 🛠️ Workaround: Send One Instruction at a Time To get every edit applied on a ZIP or HTML upload project, split your request into separate single-action prompts and send them in sequence: 1. Break your request into individual actions (one change per prompt). 2. Send the first single-action prompt — for example, add a contact page. 3. Wait for that change to finish before continuing. 4. Send the next single-action prompt — for example, change the heading color to blue. 5. Wait for it to finish, then send the next — for example, update the homepage text. 6. Repeat until all your changes are complete. Waiting for each change to finish before sending the next lets the AI reliably apply every instruction on imported projects. You'll see each edit reflected in your project before you move on to the next prompt. 📡 Engineering Status Our team is aware of this issue and is actively working on a fix so that multi-instruction prompts apply correctly on ZIP and HTML upload projects. Until the fix ships, the single-action prompt workaround above is the reliable way to apply all of your changes. 📞 When to Contact Support Reach out to our support team if: - A change is still skipped even when you send it as its own single-action prompt. - An edit is applied only partially after the prompt finishes. - You see the same behavior on a native (non-imported) project. When you contact us, include your project name and the exact prompt text you sent so we can investigate quickly. 🌀 We're on it. You now know why some edits may be skipped on ZIP or HTML upload projects and how to apply every change by sending single-action prompts one at a time. Thank you for your patience while our team completes the fix.

🛠️ Undo/Redo Preview Not Updating on HTML-Upload Landing Pages

If you click undo or redo on an HTML-upload landing page project and the preview looks unchanged, your revert was still applied. Refresh the project editor to see the correct, reverted version right away. 🔍 What's Happening On HTML-upload (html_upload) landing page projects, clicking undo or redo shows a green "Changes reverted successfully" toast, but the preview iframe does not visually update. The page still displays the previous version even though the revert was applied. This is a display-only issue. The revert is correctly saved on the backend, so your file changes are safe — only the on-screen preview is out of sync. Who's affected - Customers working in HTML-upload (ZIP/HTML) landing page projects. - Anyone using undo or redo to revert changes in the project editor. 🛠️ Workaround Steps Force the preview to re-fetch the true, saved state with a quick refresh: 1. Click undo or redo as usual. 2. Wait for the green "Changes reverted successfully" toast. 3. Refresh your browser or reload the project editor. After the reload, the preview re-fetches from the server and displays your reverted version. Your changes were already saved, so nothing is lost during the refresh. 📡 Engineering Status Our team is aware of this issue and has already addressed it. The fix is rolling out, and the preview should update automatically after undo or redo very soon. Until then, the refresh step above gives you the correct view every time. 📞 When to Contact Support Reach out to support if, after refreshing the project editor, the preview still shows the un-reverted version or your saved changes appear to be missing. Include your project name and the action you took (undo or redo) so we can help quickly. 🌀 Your work is saved and our team is on it — a quick refresh shows the correct version today, and the automatic fix is on its way.