Home 🏗️ Website Studio

🏗️ Website Studio

Camilo Aponte
By Camilo Aponte
• 28 articles

🛠️ Enable Cloudflare Orange Cloud for Website Studio

🔍 Why There Is No Single Row Number Many customers ask which row number to change in Cloudflare DNS. The row number is different for every account. It depends on how many records your domain has and how Cloudflare sorts them. Instead of a row number, you identify the correct row by its Type, Name, and Content values. This article shows you exactly how to do that. 📋 Before You Begin - You need access to your Cloudflare account and the domain you connected to Website Studio. - Open the domain connection instructions in Website Studio so you can see the DNS records your site should use. - Point the domain at Website Studio first, and leave that record set to DNS only (grey cloud). The orange cloud blocks verification and SSL. 🎯 Which Records to Change Do not turn on the orange cloud for the record that points your website to Website Studio. Leave it grey (DNS only). - The root domain record: Type is usually A or CNAME, and Name is @ or your domain name (for example, yourdomain.com). - The www record: Type is usually CNAME, and Name is www. Match the Content value of each row to the value shown in your Website Studio connection instructions. The rows that match are the ones to change, no matter what number they appear in. Do not change other records, such as MX (email), TXT (verification or email security), or records for other services like a mail provider or subdomain tools. Email-related records must stay DNS only (grey cloud). 🧭 Step-by-Step: Turn On the Orange Cloud 1. Log in to your Cloudflare dashboard and select your domain. 2. In the left menu, click DNS, then click Records. 3. Find the row where Name is @ (or your root domain) and the Content matches your Website Studio instructions. 4. Look at the Proxy status column for that row. If it shows a grey cloud labeled DNS only, click the cloud icon, or click Edit on the row. 5. Switch Proxy status to Proxied so the cloud turns orange. 6. Click Save. 7. Change only the single record shown in your Website Studio instructions. If you connected the root domain, that is the root record; www is a separate domain you would connect on its own. When you are done, both website rows should show an orange cloud with the label Proxied. 🔒 Check Your SSL/TLS Setting After turning on the orange cloud, check your encryption mode so your site loads correctly. 1. In Cloudflare, click SSL/TLS in the left menu, then click Overview. 2. Set the encryption mode to Full or Full (strict). 3. Avoid the Flexible mode. It can cause a redirect loop, which shows a message like Too many redirects. ✅ How to Confirm It Worked - In Cloudflare DNS, the website rows show an orange cloud and Proxied. - Visit your site with and without www and confirm the pages load with a secure padlock. - Allow a few minutes for the change to take effect. In some cases it can take longer. 🛠️ Troubleshooting - I cannot find the right row: Use the search box above the DNS table and search for @, www, or the Content value from your Website Studio instructions. - The site shows a redirect error: Change the SSL/TLS mode to Full or Full (strict), then clear your browser cache and reload. - The site shows an error after proxying: Turn the cloud back to grey (DNS only), save, and wait a few minutes. Then confirm the Content value matches your Website Studio instructions before trying again. - My email stopped working: Make sure MX records and any mail-related records are set to DNS only. Do not proxy them. - The orange cloud option is unavailable: Some record types cannot be proxied. If this happens on a record that should point to Website Studio, double-check the record Type against your connection instructions. 💬 Need Help? If you are unsure which rows to change, send us a screenshot of your Cloudflare DNS records page so we can point to the exact rows. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 2026

🔍 Website Studio Preview Versus WordPress

🔎 What a preview URL means If the address of an article uploaded in Website Studio includes the word preview, that page is Search Atlas’s public hosting link, not a private draft. Anyone with the address can open it without logging in, but search engines are told not to index it. It is not your public blog URL on your own website, and it does not replace the blog already running on your main website. Sharing or bookmarking the preview address does not put the article on your own website, but the preview address itself is already public for a published project. Visitors and search engines should use the address on a domain you connect after publishing, or the WordPress address if you sync the site there. 📌 Preview compared with a live page - Preview: Search Atlas’s own hosting link for the Website Studio site, meant for review and kept out of search results, but publicly reachable by anyone who has the link. - Live page: the public address on your own domain or a subdomain, available after you publish and connect that domain. - WordPress blog: a separate site. Publishing Website Studio on its preview link or on a domain you connect does not update, replace, or turn off posts that already live in WordPress. Sync to WordPress is a separate step, and it can add or update Website Studio pages on that WordPress site without editing or turning off existing WordPress posts. You can keep WordPress as your main blog and still use Website Studio. Posts are not copied automatically, but you can connect the WordPress site and turn on Sync to WordPress to push Website Studio pages there. Until you do that or connect a domain, the two systems use different addresses. 🚀 Publish without buying a new domain You do not need to purchase another domain if you already own the domain used by your main website. Connect that existing domain, or a subdomain of it, to the Website Studio site. 1. Finish the article in Website Studio and confirm the preview looks correct. 2. Publish the site or page from Website Studio. Publishing makes it live on its Search Atlas preview address; connecting and verifying a domain makes the public address on that domain live. 3. Choose the domain you already own. To leave your current WordPress blog untouched, use a subdomain such as resources.yourdomain.com or studio.yourdomain.com instead of replacing the main site. 4. Add the DNS records Website Studio shows you at the company where your domain is managed. DNS changes can take time to finish. 5. After the connection is active, open the new public URL, not the preview link, and confirm the article loads. Pointing the root domain (yourdomain.com) at Website Studio can replace what visitors currently see on that address, including a WordPress homepage. If WordPress must stay on the main address, use a subdomain or a domain you already own that is not serving the WordPress site. 📝 If the blog should stay on WordPress Website Studio does not by itself edit posts that already live in your WordPress blog. To place the Website Studio page on that WordPress site, connect the site and use Sync to WordPress. If the live post must be an ordinary WordPress post, create or paste the article in WordPress and publish it there. The preview address is only for review, and anyone with the link can open it. - Keep the current blog: publish on WordPress and leave Website Studio in preview, or unpublish the Studio page so two versions are not public. - New section beside WordPress: connect a subdomain to Website Studio and link to it from your main site menu. - Avoid duplicate pages: do not publish the same article on both the preview or Studio URL and WordPress. Pick one public address. ✅ Quick checks before you share a link - The public address on your own domain does not contain preview. The Search Atlas preview address still does, even after you publish. - The address uses your domain or chosen subdomain. - The page loads in a private browser window without logging into Search Atlas. - Only one version of the article is public. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 2026

🛠️ Remove OTTO Custom Footer Text

📌 Why extra footer text appears Undesirable text below your site footer usually comes from a custom footer block saved in Website Studio. OTTO can keep that block on the live site even after you edit the main footer, which is why the text looks sticky and sits below the red line you marked. The custom text is separate from your theme footer. Clearing only the visible footer content does not remove it. You need to delete the custom footer text itself, then save and publish again. 🧹 Remove the custom footer text 1. Sign in to Search Atlas and open the project that shows the extra text. 2. Open Website Studio for that site. 3. Select the page, or the site-wide layout if the text appears on every page. 4. Open the Footer area and look for a custom text or HTML block under the main footer. 5. Delete all text inside that custom footer field. Leave the field empty. Do not replace it with a space or a line break. 6. Check every page template that uses the same footer. Remove the same text anywhere else it is saved. 7. Click Save, then publish or update the site so the empty footer is sent live. 🔄 If the text is still sticky A saved copy can stay on the live site until the latest version is published and the browser cache is cleared. - Confirm the custom footer field is completely empty, then save and publish one more time. - Hard refresh the live page, or open it in a private window. - Clear any site or CDN cache if your host keeps an older version of the page. - Review other pages and the global layout so an older footer is not reused. - Remove any duplicate custom code snippet that reprints the same sentence under the footer. ✅ Confirm the footer is clean After publishing, scroll to the bottom of the live page. The area below the footer should be blank, with no extra line of text. Check both desktop and mobile, and open at least one other page that shares the footer. If the text returns after a new OTTO update, open Website Studio again and confirm the custom footer field is still empty before you republish. **💬 Get help from the teamIf you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 2026

📅 Add Cal.com Calendar to Website Studio

📅 Why the booking calendar is missing A Cal.com calendar appears on a Website Studio page only after the inline embed code is placed on that page and the site is published. If the calendar is missing from /home or /contact, the embed was not saved on that page, was added to the wrong section, or the latest version was not published. 📍 Where to Find It UI path: Left sidebar → Website Studio Each page needs its own copy of the embed. Adding the script on one page does not add it to the other. 🛠️ Add the inline embed on both pages Use the Cal.com inline embed script you already have. Do not change the booking link inside it unless you intend to point visitors to a different event. 1. Open Website Studio and select the site you want to update. 2. Open the Home page, which is the page served at /home. 3. Go to the section where the calendar should appear and add a Custom HTML or Embed block. The exact label depends on the blocks available in your editor. 4. Paste the full Cal.com inline embed, including both the calendar container and the script. Paste it as code, not as plain text on the page. 5. Save the page. 6. Open the Contact page and repeat the same steps so /contact has its own embed. 7. Save the Contact page. Place the block in the main page content, not inside a header, footer, or hidden section, so visitors can see the calendar without scrolling past unrelated content. ✅ Publish and confirm both pages 1. Publish the site so the saved embeds go live. Saving inside the editor alone does not update the public pages. 2. Open /home in a private or incognito browser window and confirm the booking calendar loads. 3. Open /contact the same way and confirm the calendar loads there too. 4. If one page is blank, return to that page in Website Studio, confirm the full embed is still in the block, save, and publish again. A short delay can happen after publishing. Refresh the page before editing the embed again. If the calendar area is empty but the rest of the page looks correct, check that the Cal.com event in your embed is still active and that the script was not shortened when you pasted it. 💡 Keep the embed easy to maintain - Keep the same Cal.com event on both pages unless Home and Contact should offer different bookings. - When Cal.com gives you a new embed script, replace the code on both pages, then publish once. - Do not place a second copy of the same embed in the header or footer if it is already in the page body. Duplicate scripts can stop the calendar from loading. - After any theme or layout change, recheck /home and /contact, because replacing a section can remove a custom block. 💬 Get help inside the platform If the calendar still does not appear after you paste the full inline embed on both pages and publish, have your Cal.com embed ready to share. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 2026

🚫 Unpublish Website Studio Preview URLs

🚫 Why preview URLs can hurt SEO Website Studio creates a preview on a Search Atlas builder domain so you can review a site before it goes live on your own domain. If that preview stays published, Google can crawl and index it as a second copy of your site. Duplicate pages split relevance, can show the wrong URL in search, and may compete with your real domain. Unpublishing the preview takes the builder-domain copy out of public view. Google then has a clear signal to drop those URLs. Your live site on your own domain should be the only version you want indexed. 🛠️ Unpublish the preview Use these steps for each Website Studio project that still has a public preview: 1. Sign in to Search Atlas and open Website Studio. 2. Select the project whose builder-domain URL is showing up in Google. 3. Open the project’s Publish or site settings. 4. Choose Unpublish. This removes public access to the preview on the builder domain. It does not delete your project or your content. 5. Confirm the action, then open the old preview URL in a private browser window. It should no longer load as a public site. 6. Repeat for every project that was published only as a preview and is not meant to rank. If the site should stay live, publish it only on your connected custom domain. Do not leave a second public copy on the builder domain. 📍 Where to Find It UI path: Left sidebar → Website Studio 🔍 Check what Google is indexing Search Google for your brand or a unique sentence from a page, or use a site: search for the builder-domain host you were given. Note every preview URL that still appears. You will use that list after the pages are unpublished. - Your real domain should be the URL you want in search results. - Builder-domain URLs should not be linked from your live site, sitemap, ads, or social profiles. - Remove any internal links or redirects that point to the preview. 📊 Ask Google to drop outdated URLs Unpublishing does not erase Google’s index overnight. After the preview no longer loads for the public, request removal of the outdated URLs: 1. In Google Search Console for a property you own, use Removals only for URLs on that property. 2. For builder-domain URLs you do not control in Search Console, use Google’s public Remove Outdated Content tool once those URLs return an error or are no longer available. 3. On your live site, keep a self-referencing canonical on each page that points to the production URL on your domain. 4. Submit or refresh the sitemap for your real domain only. Temporary removal requests hide URLs faster. Lasting cleanup depends on the preview staying unpublished so Google recrawls and drops it. 💡 Keep future previews out of search - Share preview links only with people who need to review the site, and unpublish when the review is done. - Do not add builder-domain URLs to sitemaps, navigation, or public content. - Connect and launch on your custom domain when the site is ready to rank. - After launch, search again for the old preview URLs and confirm they are gone or marked unavailable. 💬 Still seeing the builder domain If the preview URL still loads after you unpublish, or you cannot find the publish control for that project, the project may still be set to public. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 2026

🛠️ Fixing Website Studio Publish Errors for Missing Files

🔍 Why Publishing Fails for Missing Referenced Files When you publish an uploaded HTML site in Website Studio, the platform checks that every local script and stylesheet your pages reference is included in the published site. If one of those files is missing, publishing fails and the error names the page and the missing file. This usually happens when a companion resource folder was left out of the upload. Missing images or other non-script, non-stylesheet assets do not block publishing. ⚙️ How to Re-upload Missing Files To restore the missing references, either re-upload the site's complete files, including the page files and their resource folder, or rebuild the site, then publish again. Re-uploading replaces the project's current content, so publish only after the replacement finishes. 1. Locate the original files: Find the original website download files on your computer. 2. Verify complete folder contents: Ensure you have both the primary website page files and the entire accompanying folder containing all referenced assets and styles. 3. Create a ZIP archive: Select both the page files and the accompanying resource folder, then compress them together into a single ZIP file. 4. Upload to the project: Upload the newly created ZIP file back to your existing Website Studio project. 5. After the replacement upload finishes processing, publish the website again. The previous published version is taken down during the replacement, so the new files are not live until that publish completes. 💡 Preserving Recent Project Edits If you have made extensive edits directly within Website Studio and do not want to overwrite your updates with older local files, consider the following: - Keep your asset paths consistent: Make sure any custom files or images added to your pages match the exact folder names and structure used by the project. - When using Replace content from HTML, upload the complete site rather than only the missing assets. This action replaces the project’s code content instead of merging files, so include the current pages together with the missing resource folder or assets. Export or copy your latest Website Studio changes into the replacement package first; changes absent from that package will not be retained. Source: landing-page-studio/django\_service/core/views.py:11140–11158, 11266–11270. 💬 Need Additional Support? If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 04, 2026

🛠️ Fix PPC Header Links in Website Studio

🧭 What this issue usually means ** Website Studio may share the same header navigation across PPC landing pages and the rest of your site pages. Removing menu links from a PPC page can inadvertently remove them across all other pages sharing that header component. In addition, campaign sync errors can occur if a published destination URL has not been selected and synced with OTTO PPC. --- ### 🔗 Confirm the landing page that is actually used Before changing navigation, check which URL each related product points to. - Open the products tied to the ads or PPC page. - Note the exact landing page URL each product uses. - Compare that URL with the path you expected, such as a separate home-offer or builder-land page. - If those alternate paths do not appear anywhere in the account, they were never configured as landing pages. Ads and pages cannot use a URL that was not set up. In the reviewed case, both products pointed to the same private-home-sale URL. The other two paths had no reference in the account. ✍️ Prompt Website Studio more explicitly A general request to remove the header menu can be applied to the shared header. Ask again with a narrower instruction. 1. Name the exact PPC page you want changed. 2. State that the header menu links should be removed from that PPC page only. 3. State that the same links must stay on all other pages. 4. ** Specify the exact page and target component in your prompt so the assistant scopes the edit to that specific page rather than modifying the shared header. --- ### 🪟 Try an incognito window ** When submitting instructions to Website Studio, provide an explicit prompt directing the AI to modify only the specific landing page layout or hide navigation on that individual page, rather than removing navigation globally. --- ### 💬 When the header still will not change If Website Studio still cannot update only the PPC page header, the shared header may need a technical review. Do not keep removing links if each attempt changes every page. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat. Include the exact landing page URL in use, the PPC page you want changed, and what happened after the explicit prompt and incognito test. Mention any 502 or 504 error shown while launching Google ads or uploading to Facebook.

Last updated on Nov 04, 2026

🛠️ Restore Missing Booking Calendar Embeds

📅 Why a booking calendar embed may disappear A booking calendar embed can be removed or stop displaying after a page redesign, content update, template change, plugin update, or code cleanup. The calendar may also be present in the page source but hidden by styling, scripts, or security settings. 🔎 Check whether the embed is missing 1. Open the affected page in your website editor. 2. Scroll to the location where the booking calendar should appear, usually near the bottom of the page. 3. Look for a Calendly or other booking-service embed block, custom HTML block, iframe, or script. 4. Preview or publish the page, then open it in a private browser window to confirm whether the calendar loads. ⚙️ Restore the booking calendar embed 1. Sign in to your booking platform, such as Calendly. 2. Open the event or booking page that should appear on your website. 3. Choose the platform’s sharing or embed option and copy the recommended inline embed code. 4. Open the affected website page in its editor. 5. Add a custom HTML, code, or embed block at the required location, such as the bottom of the page. 6. Paste the complete embed code without changing the script, URL, or required attributes. 7. Save the page and publish the changes. 8. Test the page on desktop and mobile. Confirm that the calendar loads, available times appear, and a test booking can proceed. 🧩 If the calendar still does not appear - Confirm the page is published and that you are testing the correct URL. - Clear the website, browser, CDN, or caching-plugin cache. - Check that the embed code was added to an HTML or code block, not a visual text block. - Make sure the booking event is active and available in the booking platform. - Temporarily test the page without other scripts or plugins that may block embedded content. - Check whether cookie consent, content-security settings, or browser extensions are preventing the calendar from loading. 🛠️ Request a manual restoration If you cannot access the page editor, do not have the correct embed code, or need the code restored on multiple pages, provide the affected page URLs and identify where the calendar should appear. Also include the booking-service account or event name, the intended placement, and any recent page or website changes. Search Atlas support can review the issue and help coordinate the restoration. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 05, 2026

🧹 Purge Leftover Website Studio Preview Files

🗑️ What happens when you delete a project Deleting a Website Studio project removes it from your project list and attempts to stop its preview container and disable its published routes. Some stored files may remain. If the old preview URL still serves the project’s content, contact support to investigate incomplete cleanup. If pages, images, or other assets still load at the old preview address after deletion, confirm that the project no longer appears in your account and check the URL in a private window. If the content remains accessible, contact support with the exact URL. 🔍 Confirm the preview is still live Before you contact support, check these points so the purge request is clear: 1. Open the preview URL in a private or incognito window so an old browser cache does not confuse the result. 2. Confirm the page or files still load and match the deleted project. 3. Note the project name, project ID, the date you deleted it, and the full preview URL. 4. If you have screenshots, keep them ready to share in chat. Do not send passwords or unrelated account secrets. Refreshing the page or clearing your own browser cache only affects what you see locally. It does not delete files from preview hosting. 🛠️ What you can and cannot remove yourself You can delete the Website Studio project from your account. You cannot permanently remove leftover public preview files from inside a project that no longer exists. - In your account: the deleted project should no longer appear in Website Studio. - Deletion attempts to stop the preview from serving the project’s content, although stored files may remain. If uploaded files are still publicly accessible, send their exact URLs to support for investigation and cleanup. - Anyone with a working public preview link may be able to view its content while that URL still serves it. Deletion should disable access; report any content that remains accessible afterward to support. Do not create a new project with the same name to try to overwrite the old preview. That will not remove files tied to the deleted project ID. 💬 Ask support to purge hosting Permanent deletion of leftover files and preview hosting is handled by our support team. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat. Include this information in your first message: - Project name - Project ID - Date you deleted the project - Full preview URL that still loads - A short note that you want all uploaded files and preview hosting permanently deleted Give support the deleted project’s ID if available, along with the exact preview URL and any file URLs that still work. These details help identify the correct project and its remaining resources. ✅ After the purge When the purge is finished, the preview URL should stop serving the deleted project’s files. Open the link again in a private window to confirm. If it still loads the old content, reply in the same chat with the URL and the time you checked. Purging preview hosting does not restore a deleted project. If you still need the site, you must rebuild it in a new Website Studio project. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 05, 2026

🛠️ Website Studio NoSuchBucket Domain Fix

🪣 What the NoSuchBucket page means If a Website Studio custom domain opens a bad page that says NoSuchBucket instead of the site you created, the domain is not correctly mapped to its hosting bucket. The page you see is not your Website Studio site. This is a platform mapping failure, not a problem with the content you built. The same error can affect every custom domain on that Website Studio project at once. It does not affect custom domains on the account's other projects. Visiting the URLs again or rebuilding the pages does not repair that mapping. 🛠️ How this issue is actually fixed Support identifies the failed custom-domain-to-hosting-bucket mapping and sends it to the specialized team. That team corrects the mapping on the platform side. In a confirmed case, the specialized team reported that the domains were working again after that correction. There is no customer setting that completes this repair. 💬 What you should do Open a chat and include: - That Website Studio custom domains show NoSuchBucket - Each affected domain URL - That the pages are not the sites you created Ask support to escalate the bucket mapping to the specialized team. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat. ⏳ After you report it Wait for the chat update that the specialized team has corrected the mapping, then open each custom domain again. You should see the Website Studio site you created, not the NoSuchBucket page. Do not change domain settings on your own while the ticket is open. That was not part of the successful fix, and it will not remap the hosting bucket.

Last updated on Nov 06, 2026

🛠️ Website Studio File Edit Rollback

✏️ Make a precise source-file edit Website Studio does not have a project file editor for opening and saving one source file. Make the change in chat, or select an element in the visual Editor tab and save it there. A saved edit is recorded as an agent response in the project chat. That is separate from restoring an older full project version or republishing an older published site. Use chat or the visual Editor when the edit should be a project edit. Tracking & Scripts lives in Project Settings and is saved separately with Save Settings. Leaving those fields unchanged does not attach them to a chat or visual-editor save. ↩️ What Revert this change restores Revert this change restores the project files to the snapshot from immediately before that response. It does not restore only the files listed on that response. It also marks that response and every later agent response as undone. It is not a line-level undo, and it does not by itself republish the live site. - Revert this change restores the project file tree to the snapshot from before that response. There is no separate callback-source-file restore. - Tracking & Scripts is saved separately in Project Settings. Reverting a chat or visual-editor change does not reset the saved Tracking & Scripts values. A later file restore can still change src/embeddings.json if an earlier settings save committed that file. - Tracking & Scripts is changed in Project Settings with Save Settings, not by reverting a chat entry. To change those settings, edit Header Embeddings or Footer Embeddings and save again. Reverting a chat response does not undo that settings save. - The result is the prior version of the included items, not a mix of old and current lines inside those files. 💾 Preserve the current state Before you edit, save any Tracking & Scripts changes you want to keep from Project Settings. Then make the new edit in chat or the visual Editor and save it, so it appears as its own response with Revert this change. You can also download the project source if you want a copy outside the project. 1. Open the project in Website Studio and review the current callback source files. 2. Check Tracking & Scripts and leave them unchanged if they should stay as they are. 3. Edit only the intended source file and save once. Do not bundle unrelated content into that save. 4. After the edit, the chat response lists the files it reported as changed. That list is not a guarantee that revert will touch only those files. ✅ Undo only these changes To undo the edit, use Revert this change on that agent response in the project chat. Review the project afterward. This also marks later agent responses as undone. It does not reset Tracking & Scripts saved in Project Settings, and it does not republish the site. Version History and publishing an older site version are separate actions. - Revert the single change that contains the precise file edit. - Leave every other change in place. - Re-check Tracking & Scripts after the revert so a separate settings edit is not assumed to have changed. 💬 Get help in the platform If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 06, 2026

🛠️ Resolving the NoSuchBucket Custom Domain Error

🔍 Understanding the NoSuchBucket Error If your Website Studio site shows a NoSuchBucket XML error on your custom domain, the platform is sending the request to a Google Cloud Storage bucket that does not exist. This is a platform routing problem, not a problem with your domain registration or DNS. Contact Search Atlas support and include the domain and the full error. Reloading the page, republishing, or changing DNS will not fix it. 📋 Common Causes Before making changes, check for these common causes: - DNS pointing mismatch: A subdomain should use the CNAME target shown in Website Studio, and a root domain should use the A record IP shown there. Those targets point to Search Atlas, not to a storage bucket. Wrong DNS usually stops domain verification or shows a different site or certificate error; it does not cause NoSuchBucket. - Domain Name Typo: The domain mapped in your platform settings does not exactly match your active domain name. - Unverified custom domain: If verification has not finished, the domain is not yet connected and will not serve the published Website Studio site. Finish the DNS record shown in Website Studio and click Verify. That is a separate setup step and does not repair a NoSuchBucket error. - SSL or routing delay: After DNS is verified, Search Atlas provisions the certificate and connects the domain. Until that finishes, you may see a certificate warning or the site may not load. This is not a NoSuchBucket error, and it does not provision a new storage bucket. 🚀 Step-by-Step Fixes Follow these steps to restore your site: 1. Check the domain in Website Studio: Open the project, go to its Domains area, and confirm the connected domain is exactly the one you are visiting, including www or the root domain. If it is already connected and verified, changing the spelling will not fix NoSuchBucket. Contact support. 2. Check DNS only if the domain is not verified: In your DNS provider, such as Cloudflare, GoDaddy, or Namecheap, use the record shown in Website Studio. Use a CNAME for a subdomain or an A record for a root domain. This confirms the domain reaches Search Atlas; it does not repair a NoSuchBucket error on an already connected domain. 3. Do not remove and re-add the domain to fix NoSuchBucket. Removing it only disconnects the domain and deletes its routing and certificate; adding it again starts DNS verification again and does not create a new bucket. Contact Search Atlas support so the platform routing can be corrected, then reopen the domain. 4. Clear Local Cache: Clear your browser cache or open the website in an incognito window to verify if DNS propagation has completed. DNS updates can take anywhere from a few minutes up to 24 hours to take effect globally. 💬 Contact Search Atlas Support If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 07, 2026

🛠️ Fix Website Studio Projects That Fail to Load

🔍 Why a project may not load Website Studio opens your site project in the browser. A blank screen, a spinning loader, or a message that the project failed to load usually means the editor could not finish starting. Common causes are a slow or dropped connection, an outdated browser tab, a blocked script, or a temporary platform issue. The steps below fix most cases without changing your site content. 🛠️ Quick checks to try first 1. Confirm you are signed in to Search Atlas and that you opened the project from Website Studio, not a bookmarked editor URL. 2. Wait up to one minute. Large projects can take longer on the first load. 3. Refresh the page once. If it still fails, close the tab and open the project again from the project list. 4. Check your internet connection. Switch networks if you can, then reload. 5. Try a private or incognito window. If the project loads there, a browser extension or saved site data is likely blocking the editor. 🌐 Clear browser issues Use a current version of Chrome, Edge, Firefox, or Safari. Website Studio needs JavaScript and cookies enabled. - Disable ad blockers, privacy extensions, and script blockers for the Search Atlas site, then reload. - Clear cached files and cookies for the Search Atlas site only, then sign in again. - Extra Website Studio tabs do not cause the loader to stall. If the project will not open, refresh the page, or close it and open the project again from the Sites list in Website Studio. - If another browser loads the project, update or reset the browser that failed. ⚙️ Check the project and your access - Open a different Website Studio project. If only one project fails, leave that project and reopen it from the list. - If the editor says Access Denied, the project belongs to a different Search Atlas account than the one you are signed in with. Sign in to the account that owns the project and open it again from the Sites list. A deleted project instead says Project not found. - You can open the editor while a publish is running. If a publish is still in progress, wait for it to finish before you publish again, then reload if the preview has not caught up. ✅ When the project loads again After the editor opens, wait until the preview finishes loading and shows your site before you edit. The preview tells you while the project is waking up. Save a small change to confirm the project is responding. If the failure happens on only one device, repeat the browser checks on that device. 💬 Still not loading If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat. Include the project name, the browser you use, whether other projects load, and the exact message on screen if one appears.

Last updated on Nov 07, 2026

🛠️ Unpublish Preview Sites and Fix Domains

🌐 What a preview site is A Website Studio preview address lets you review or share your site separately from your custom domain. A “Your domain points to the wrong place” notice means the domain’s DNS target needs checking; it does not mean you must unpublish the preview. Evidence: django\_service/core/services/domain\_notifications.py:257–270. 🗑️ Unpublish a preview site Unpublish takes the project’s published site offline. Do not use it to remove only a preview while keeping the same project live on its custom domain. Evidence: django\_service/core/tasks.py:4406–4413,4504–4505. 1. Sign in to Search Atlas and open Website Studio. 2. Select the project that contains the preview site. 3. Open the site list or publish settings and find the preview address. 4. To take the project’s published site offline, open Settings → Project settings and select Unpublish under Unpublish project. This is not a preview-only removal action. Evidence: Settings, lines 659–672. 5. After selecting Unpublish, wait for the operation to finish and check that the site is unpublished. The project and saved address remain available for republishing. Evidence: Settings, lines 500–517; django\_service/core/tasks.py:4543–4549; next\_js\_service/app/components/HostedSiteView.tsx:74–75. If Unpublish is unavailable, check whether the project is published or already being unpublished. Do not delete the project merely to resolve a preview-address or DNS issue. Evidence: Settings, lines 664–666. ⚠️ Why your domain points to the wrong place An email or in-platform domain warning means a connection check found a problem. Read its specific diagnosis: records may be missing, point to the wrong target, conflict with other records, or have changed since verification. Common causes include: Evidence: django\_service/core/services/domain\_notifications.py:251–285. - An old A or CNAME record was left in place. - The domain is connected in Website Studio but DNS was never updated at the registrar. - The preview hostname and custom domain can both remain accessible for the same project. Their coexistence does not by itself indicate a DNS error or require unpublishing. Evidence: django\_service/core/services/custom\_domain\_service.py:345–348. - DNS changes are still propagating, which can take up to 48 hours. 🔧 Fix custom domain settings Use the records shown inside Search Atlas. Do not guess IP addresses or hostnames from an old email. 1. In Website Studio, open the project, open Settings, and select Domains to manage its custom-domain connection. Evidence: Settings, lines 200–204,279–280. 2. Copy the exact host, record type, and value shown for your domain. 3. Sign in to the company where you bought the domain. 4. Remove conflicting A, AAAA, or CNAME records for the same host, including any record that points to a preview or old host. 5. Add only the records displayed in Search Atlas, then save. 6. Return to the domain setup wizard and select Check my connection or Verify connection, depending on the result shown. For an existing domain awaiting verification, select Verify DNS. Evidence: Settings, lines 4759–4765,3034–3036. Use one destination for the root domain and one for www if both are listed. Do not point the same host to two different targets. ✅ Check that the domain is correct - The preview address no longer opens a live builder site. - Your custom domain opens the published site, not a parking page or error. - Website Studio shows the domain as connected or verified. - You cleared your browser cache or tried a private window before retesting. If verification fails right after a DNS change, wait and check again later. Most updates appear within a few hours, but some registrars take up to 48 hours. 💬 When to contact support Contact support if the preview will not unpublish, the domain stays unverified after 48 hours, or you cannot tell which DNS record to replace. Have your domain name and a screenshot of the records ready. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 08, 2026

🖥️ Fix Website Studio Black Screen

🖥️ What the black screen means Website Studio opens the project inside the Search Atlas dashboard. The editor background is dark, so a dark page is normal while it loads. If the preview is stuck, the preview area stays dark and shows a spinner and a message such as "Almost ready, just a moment..." or "Waking up your project, just a moment...". The chat and controls should still respond. If you instead see "Project not found", the project was deleted or does not exist. ✅ Try these steps first 1. Close the project tab completely, then open Website Studio again and select the same project. 2. Hard refresh the page. On Windows or Linux, press Ctrl + Shift + R. On Mac, press Cmd + Shift + R. 3. Set the browser zoom to 100%. Very high or low zoom can clip the editor so only a small strip of the site shows. 4. Check that the window is maximized and that no other window is covering the editor. 5. Wait a few seconds after the project loads before clicking. A slow connection can leave the canvas blank until the editor finishes loading. 🌐 Check your browser Open Website Studio in a current desktop browser with JavaScript enabled. If the preview never finishes loading, try another current browser or turn off extensions that block scripts. - Update the browser, then fully quit and reopen it before trying the project again. - Open the project in a private or incognito window. If it loads there, an extension is likely blocking the editor. - Turn off ad blockers, privacy tools, script blockers, and VPN browser extensions for the Search Atlas site, then reload. - Clear cached images and files for the Search Atlas site, then sign in again and reopen the project. - Try a second supported browser if the first one still shows a black screen. 💻 Check your device - Close extra tabs and heavy apps so the browser has enough memory to draw the editor. - If you use hardware acceleration and the screen stays black, turn hardware acceleration off in the browser settings, restart the browser, and reopen the project. - Avoid remote-desktop or very small laptop screens while editing. Resize the window wider than a phone layout. 🔁 If the strip of the site still will not click Do not keep clicking a preview that is still loading. Close every Website Studio tab, choose Logout from your profile menu, sign back in, and open the project from the Sites list rather than an old bookmark. If another project opens normally, stay on that list and open the affected project again. A preview that is still loading does not remove your pages. Avoid creating a new project just to replace the one that looks black. If the page says "Project not found", that project was deleted or does not exist, so open another project from the Sites list. 💬 When to contact support Contact support if the black screen remains after a hard refresh, a zoom reset to 100%, a private window, and a second updated browser. Tell us the browser name and version, whether private mode works, and the project name. A short screen recording or screenshot of the full browser window helps us see how much of the editor is visible. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 09, 2026

⚙️ Next.js Hosting vs Website Studio

📌 What this article covers Search Atlas does not host a full custom Next.js application the way Vercel does. Website Studio publishes Search Atlas marketing sites. A separate app with Payload CMS, a database, environment variables, and server routes stays on your own application host. 🛠️ What Website Studio is Website Studio is the built-in site builder for SEO-focused pages that you create and publish inside Search Atlas. It is meant for brochure, landing, and content sites managed in the platform, not for arbitrary application code. - Pages, content, and design are edited in Website Studio. - Publishing and hosting for those Studio sites are handled by Search Atlas. - You do not upload a Next.js repository, set build commands, or manage server runtime there. 🚀 What is not included Website Studio is not a general Next.js platform. These items are outside its scope: - Hosting a full Next.js app, including the App Router and custom project structure. - Payload CMS or any other self-hosted headless CMS running beside the site. - Your own database, connection strings, or data migrations. - Environment variables, secrets, server routes, API handlers, cron jobs, or serverless functions. - Preview deployments, custom build pipelines, or Vercel-style project settings. If your site needs those capabilities, keep it on an application host such as Vercel, and connect that live site to Search Atlas for SEO work. 📊 Feature status Full Next.js application hosting is not a Website Studio feature. There is no setting that turns a Studio site into a Node server for Payload, a database, or custom server routes. Studio remains a managed site builder. Product updates appear in the platform. Do not plan a launch on unreleased hosting. 💡 Pricing Website Studio availability follows your Search Atlas subscription. Search Atlas does not bill like a usage-based Next.js host. There is no separate meter for server compute, databases, or environment secrets, but Website Studio has its own Website Studio Credits quota. Those credits are consumed when you build or publish Studio pages, and you can top them up. Review inclusions under your plan in the billing area of the platform. Application hosting, CMS, and database costs stay with the provider you choose for that app. 🔍 Migration choices Pick the path that matches the site you actually have: 1. Studio site only. Build or rebuild marketing pages in Website Studio and publish them there. This fits content you can manage in the builder. 2. Existing Next.js app. Leave the app, Payload, database, environment variables, and server routes on your current host. Point your domain as that host requires. 3. Split setup. Use Website Studio for selected marketing pages only when you can route those hostnames or paths cleanly. Do not expect Studio to run the app behind them. Moving a Studio site out can include a React/Vite source ZIP after the site is published, using Download ZIP (source). That ZIP is for self-hosting the Studio project. It is not a ready-to-deploy Next.js codebase, and it does not include a database or server. Moving a Next.js app in does not import its repo, CMS, or environment into Studio. Plan content and DNS changes before you switch public URLs. ✅ Ownership You keep ownership of the content you add. For a Studio site, day-to-day editing and publishing happen inside Search Atlas, and Search Atlas hosts that published site. For a custom Next.js app, you own and operate the repository, CMS, database, secrets, and hosting account. Connecting a property to Search Atlas for SEO does not transfer application ownership to Search Atlas, and publishing in Studio does not give you Vercel-style infrastructure control. ⚙️ How OTTO fits OTTO does not require Website Studio hosting. It can work with a Studio site or with an external site that is connected to Search Atlas, including a Next.js site on Vercel. OTTO automates supported SEO fixes on the connected property. It does not deploy your app, provision a database, store environment variables, or replace server routes. Use Studio when you want Search Atlas to host the marketing site. Use your own host when you need a full Next.js stack, then connect that domain so OTTO can run against it. 💬 Need a hand If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 11, 2026

🌐 Website Studio Custom Domain NoSuchBucket

❌ What this error means If a Website Studio custom domain opens a bad page that says NoSuchBucket, the domain is not correctly connected to the hosting for the site you created. The address itself may be right, but the platform mapping that sends visitors to your site has failed. 🛠️ How this issue is fixed This is not something you can correct from your site settings. Support identifies the custom-domain-to-hosting mapping failure and sends it to our specialized team. That team restores the mapping so the domain loads the Website Studio site again. In a recent case, the mapping was repaired on our side. After the specialized team finished, the domain was expected to work without any change from the customer. 💬 What you should do 1. Confirm the problem by opening the custom domain URL and checking that you see NoSuchBucket or another bad page instead of your Website Studio site. 2. Open the chat widget in the bottom-right corner of the platform. 3. Tell support which custom domain is affected and that it shows NoSuchBucket instead of your site. 4. Wait for our specialized team to repair the hosting mapping. They will update you in the same chat when it should be resolved. 5. Visit the custom domain again after support confirms the fix. Refresh the page if the old error is still cached in your browser. 📌 Good to know - Do not rebuild the site or change the domain only because of this error. The failure is in the mapping between your custom domain and hosting. - Share every affected domain URL so the specialized team can check each mapping. - If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 11, 2026

🛠️ Fixing Broken Cal.com Embed Code

📌 What this article covers This article explains a known issue where a Cal.com calendar embed is removed from a site built with the AI website builder. Automated attempts to put the embed back can fail because the script or iframe is blocked or stripped. It also explains how this was resolved for a customer and what you should do if it happens on your site. ⚠️ Why the embed keeps disappearing In the case support handled, the Cal.com calendar stayed broken for two reasons. The site’s Content Security Policy blocked the calendar iframe, and a custom embed script ran without Cal.com’s required setup. Because of that, asking the on-site AI to restore the embed could report success while the calendar still did not load. Repeating the same request did not fix it. - The calendar embed is missing even after the AI is asked to restore it. - The script or iframe that Cal.com needs is removed or blocked. - Further automated restore attempts do not apply the change. ✅ How support resolved it A support agent confirmed that the customer did not need a new embed snippet. The calendar was blocked by the site’s Content Security Policy and by a custom embed script that was missing Cal.com’s required setup. The agent escalated the issue to Tier 2 and engineering. Engineering fixed the calendar on the affected site by using the supported embed and allowing the calendar iframe. That fix is in the product and waiting for release, so the same failure should not keep breaking the embed. 1. Support identified that the calendar iframe was blocked and that the custom embed script did not load Cal.com correctly. 2. The issue was escalated to Tier 2 and engineering. 3. Engineering restored the calendar. 4. A lasting fix for the AI builder is already built and is waiting for release. 💬 What you should do There is no customer-side retry that replaces the engineering fix. If your Cal.com embed is still being stripped after the AI builder tries to restore it, contact support so the site can be checked and escalated the same way. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat. In your message, say that the Cal.com calendar embed, script, or iframe is being blocked or stripped and that automated restores are not applying. Support can then confirm whether the builder is skipping the change and escalate it for a fix.

Last updated on Nov 11, 2026

🔄 Restore an Overwritten Pillar URL

🔄 What happened to your pillar URL Website Studio does not replace, duplicate, or remove an existing page when a new version is requested for the same address. It leaves the existing page unchanged. Pause new generation or publishing on that URL until you confirm which version should remain. 📋 Before you change anything - Copy the exact URL that was overwritten. - Note the date and time you last saw the rebuilt version. - Describe the unwanted page so it can be distinguished from your rebuild. - Do not generate or publish another page on that URL while recovery is in progress. 🛠️ Check Website Studio for duplicates 1. Open the Website Studio project and use the page dropdown to find the pillar page by its name and path. 2. Check the page dropdown for the exact path and any page whose different path would resolve to the same page file. Website Studio does not allow two pages to use the same URL. 3. Compare titles and content to identify your rebuilt version and the generated copy. 4. If the rebuilt page already exists, Website Studio leaves that page unchanged. It is not kept as a separate draft from the live version, so do not generate or publish anything else for that URL until the correct version is confirmed. 5. Delete a page only when you are certain it is the unwanted generated copy and not your rebuilt pillar. If you cannot tell which version is live, do not delete either page. Removing the wrong one can make recovery harder. 🔒 Ask for the URL to be restored and protected Use Revert this change on the chat response that made the unwanted edit, or ask chat to undo it. To remove an unwanted generated page, ask chat to delete that page, but the home page cannot be deleted. There is no self-serve lock that protects one URL from every future automatic change, so include the URL and the version you want kept when you contact support. - The full pillar URL - What the rebuilt page should contain - Which generated page should be deleted - Confirmation that the URL should not be altered again If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat. ✅ After the page is restored - Open the URL and confirm the rebuilt content is live. - Check that the unwanted generated page is gone. - Do not run a new generation against that same address. - If the page changes again, return to chat with the URL and the time of the change.

Last updated on Nov 12, 2026

🛠️ Roll Back a Stuck Website Studio Homepage

🛠️ What this issue looks like Website Studio can apply an AI chat change to your homepage and leave extra buttons, sections, or copies of the same block. That change stays in the project even when the AI response has no “Revert this change” control. This article explains how to undo that AI response or remove the extras. 🔍 Check the page you are editing In Website Studio, confirm the open page is the homepage (the page with the home icon in the page dropdown), not another page that only looks similar. Duplicates are extra buttons or sections on that same homepage, not separate websites. 1. Open your project in Website Studio. 2. Open the page dropdown and select the homepage (the page marked with the home icon). 3. On the Editor tab, review the preview for repeated buttons, headings, or sections. 4. If the preview looks out of date, refresh the preview. It shows the current project, not an older saved version. ↩️ Restore the previous homepage version Do not look for version history on the page. To undo an AI change, use “Revert this change” on the AI response in the chat. That restores the whole project to the snapshot from before that response. 1. Stay on the homepage in Website Studio. 2. Open the Chat tab and scroll to the AI response that made the unwanted homepage edit. 3. Find the AI response from just before the homepage looked wrong. You cannot pick a dated page version. 4. On that AI response, click the undo icon labeled “Revert this change.” Website Studio restores the project to the state before that response. There is no separate confirmation. 5. Check the homepage preview after the revert. The restored project is already saved. Publish only if you also want the public site updated. If several AI edits were applied, revert the earliest response that still leaves the correct single set of buttons. Revert also undoes every later AI response and restores the whole project, so later intentional edits on other pages are replaced too. You can re-apply a reverted response with “Re-apply this change.” 🗑️ Remove duplicate buttons when history is available If the correct content is already on the page and only extra buttons remain, ask the Website Studio chat to remove those copies. Do not expect to delete them from the editor. If the chat cannot remove them, revert the AI response that added them. - In the Editor tab you can select a button or section to inspect it, but selection does not remove it. - There is no element menu with Delete or a trash icon. Ask the chat to delete the duplicate, or use “Revert this change” on the AI response. - Tell the chat exactly which extra copies to remove and which original button to leave. The editor cannot delete them individually. - After the chat removes the extras, review the preview on the Editor tab. Chat changes are already saved. Use Save only if you also made manual visual edits, then Publish if the public site should update. If clicking the duplicate does nothing, do not try to delete an outer section. The editor cannot delete sections. Ask the chat to remove the duplicated block, or revert the AI response that created it. 📌 When Revert this change is missing If you do not see “Revert this change,” that AI response cannot be undone from the thread. It only appears on a saved AI edit that changed the project and is not the first build. Check the response that made the homepage change. On a failed edit, use “Undo my edit” if it is offered. Version History does not provide another way to restore the page. If there is no history entry, no undo control, and no way to select the duplicate, stop deleting content at random. Further AI prompts can add more copies while the page is stuck. 💬 Contact support in the platform If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat. Include the project name, the homepage URL, the approximate time of the AI change, and a short description of the duplicate buttons. Add a screenshot of the homepage and of any history panel you can see. Support can then roll the page back or remove the stuck duplicates for you.

Last updated on Nov 12, 2026

🛠️ Clean a Duplicated Website Studio Home Page

🛠️ What caused the duplicate page Website Studio can get stuck when a home page generation creates duplicate sections instead of cleaning the page you already have. AI changes draw from your shared credit balance, and the amount depends on the work generated. If your balance is nearly used up, send one cleanup request for the page you already have instead of asking Studio to build the page again. ✍️ Retry with a longer cleanup prompt Open the existing home page in Website Studio and send one detailed prompt. A support agent fixed this by having the customer retry with a longer cleanup prompt instead of a rebuild. Ask Studio to do all of the following in that single prompt: - Analyze the existing webpage against your screenshot. - Remove repeated sections, including duplicate images, cards, tables, feature grids, FAQs, and calls to action. - Consolidate unique content so each piece appears only once. - Keep the current design and branding. - Do not rebuild the page. ✅ Review the page before you generate again After the cleanup finishes, check the home page. Confirm the repeated blocks are gone, unique content is still there, and the design and branding are unchanged. Avoid another full generation if the page only needs a small cleanup, because each AI run draws from the same credit balance. 💬 If your last credit was already used A credit reset is a courtesy completed by support. You cannot reset quota yourself from the page. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 13, 2026

↩️ Rollback AI Homepage Duplicate Buttons

↩️ What this article covers ** The AI assistant can apply homepage updates, including adding buttons. If an update creates duplicate buttons, you can try reverting the AI response or asking the assistant to remove the extras. 🔍 Check what the AI changed Before you edit anything, confirm the change came from the AI assistant and note which buttons are duplicates. 1. ** Open your project in Website Studio and find the AI conversation alongside the site preview. 2. ** Review the recent AI conversation and the homepage preview to identify the response after which the duplicate buttons appeared. 3. Open your live homepage in a new browser tab and compare it with the change summary. 4. Note the label and location of each extra button, such as two identical calls to action in the same section. Do not apply another AI suggestion until the homepage looks correct. A second run can add more copies. ⚙️ Restore the previous homepage ** First, check whether the AI response that introduced the duplicates offers Revert this change. Before using it, note that reverting also undoes later project changes. 1. ** In the project’s AI chat, find the response associated with the homepage change. 2. ** On the AI response that introduced the duplicates, look for the control labeled Revert this change. It may not be available for every response. 3. ** Select Revert this change on the response that introduced the duplicates. This restores the project to before that response and undoes later changes too. 4. ** After the revert completes, review the homepage in the preview. Confirm that the desired buttons are present and the duplicates are gone. 5. ** Once the restored homepage looks correct in the preview, publish the project to update the live site. ** If several AI edits were applied, find the response that introduced the unwanted changes and use Revert this change, if available. This also undoes later project changes. Review the result, publish it, then refresh the live homepage and check it in a private window to help rule out cached content. 🛠️ Remove duplicate buttons when revert is missing ** Some AI responses do not show a revert control. If you cannot revert the relevant response, ask the AI assistant to remove the duplicate buttons or sections, then review the result in the preview. 1. Open the homepage in the editor, not only in the AI chat. 2. Select the section that contains the buttons. 3. ** In the AI chat, identify the extra buttons and ask the assistant to remove them while keeping the correct button in each section. Check the preview afterward. 4. ** If an entire block was duplicated, ask the AI assistant to remove the extra block, not just its label. Review the preview to make sure the intended block remains. **Code references:** The response-level control is in landing-page-studio/next\_js\_service/app/components/messages/VibeResponseMessage.tsx:289; cascading project-wide undo is described in landing-page-studio/django\_service/core/views.py:6064–6073. Publishing is a separate action in landing-page-studio/next\_js\_service/app/components/PreviewToolbar.tsx:703–720. 5. Check headings, links, and spacing so the remaining button still points to the right page. 6. Save, then publish the homepage. There may be no separate manual edit button inside the AI chat. Editing is done on the page or change itself. If you only clear the chat, the live homepage will not change. 📊 Confirm the live page - Each section should have only the buttons you intended. - Button labels and links should match your original homepage. - Mobile and desktop layouts should both look correct. - No new AI recommendation for that homepage should be left in a pending or approved state. If the old buttons return after a refresh, another approved AI change may still be queued. Decline or pause new homepage suggestions until you have reviewed them. 💡 Prevent the same issue - Review every AI homepage suggestion before you approve it. - Approve one change at a time and check the live page after each publish. - Avoid asking the assistant to add a button that already exists on the page. - Keep a note of the last good publish time so you know which version to restore. 💬 If you need further assistance If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat. Include your project name, the homepage address, the approximate time of the AI change, and whether undo or version history is missing. A screenshot of the duplicate buttons helps the team restore the right version.

Last updated on Nov 13, 2026

🛠️ Recover a Website Studio Container

🔎 Understand the startup error ** A Website Studio development environment can fail to start, including after a source import. If this happens, the preview may show a session error, and an attempt to publish may report that the container is not running. If the problem persists after refreshing, contact support. ✅ Check the project state 1. Open the affected project in Website Studio. 2. Confirm that the source import completed successfully. 3. Review the container status and startup messages. 4. ** If Website Studio offers Refresh on the session-error screen, select it and allow time for the environment to recover. If the error persists, contact support rather than repeatedly refreshing. 🔄 Try the supported recovery steps 1. Save or copy any recent project changes. 2. Close other Website Studio sessions for the same project. 3. ** Select Refresh on the session-error screen, then wait to see whether the development environment and preview recover. 4. ** If the session error persists or the preview remains unavailable after refreshing, contact support before retrying publication. 5. Reopen the project and check whether the container starts normally. 🚨 When recovery requires support ** If the development environment does not recover after refreshing, contact support. Include the project name or ID if available, the approximate time of the failure, what happened during the source import, and the exact error messages shown during refresh or publishing. Support can investigate whether the environment needs an internal restart or recreation. 📌 Before contacting support - Confirm the project ID is copied correctly. - Capture screenshots of the container status and error message if possible. - Note whether the failure occurs only in one project or across multiple projects. - Avoid deleting the project or importing the source again unless instructed, as this may remove useful troubleshooting information. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 13, 2026

🛠️ Restore or Delete Website Studio Pages

📌 Overview ** Website Studio lets you edit pages and delete eligible pages from a project. If you need help restoring or deleting a page, provide the exact URLs and clearly describe the desired result. Restoration is not guaranteed. 🔄 Restore a page To request restoration of an earlier page version, confirm the URL that should remain active and identify the version or content you want restored. For example, you may want to restore https://www.data-insight.org/blog/aeo-palybook/ to a rebuilt version. 1. Copy the exact URL that should be restored. 2. Explain which version or content should replace the current page. 3. Include screenshots, page copy, or other details that help identify the correct version. 4. Check the restored page after the change to confirm its content, links, images, and SEO settings. Restoration availability can depend on whether the previous version is still available in the project history or platform records. 🗑️ Delete a page Before deleting a page, confirm that it is no longer needed and check whether it receives organic traffic, backlinks, or internal links. Deletion may be difficult or impossible to undo. 1. Copy the exact URL to remove. 2. Confirm that the page is not the preferred version of another URL. 3. Update internal links that point to the page. 4. Decide whether the URL should redirect to a relevant replacement page or return a not-found response. For example, you may want to delete https://www.data-insight.org/blog/the-aeo-playbook-2026-answer-engine-optimization-strategies-for-igaming-and-high-competition-brands/. Include the replacement URL if visitors should be sent to another page. ✅ Information to include in your request - The exact page URL to restore or delete. - The replacement or restored URL, if applicable. - A clear description of the intended final state. - Confirmation that you have permission to change the website. - Any redirect, indexing, or content requirements. 💬 Get help with page changes If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 14, 2026

🛠️ Recover a Failed Website Studio Container

🔍 What this recovery process does When a Website Studio development container fails during startup or a build, the existing container may be recoverable. Recovery is intended to preserve your current project and configuration instead of creating a new project or changing DNS. 🧾 What can be preserved - Existing Search Atlas project and project ID - ** Live domain and DNS configuration should not need to change for an in-place container restart; confirm the proposed recovery steps with support. - ** Ask support to preserve the current deployment settings and confirm whether any changes are necessary. - Tracking configuration - ** Ask support to check and preserve any survey configuration and collected data before recovery. For example, if the affected project is cee4f5d8-86a9-49b8-ab52-aac615430117, include that project ID in your recovery request. ✅ Before requesting recovery 1. Open the affected project in Website Studio. 2. Record the exact startup or build error, if shown. 3. Note when the failure began and whether it happens on every restart or build. 4. Do not delete the project, development container, deployment, domain connection, tracking, or survey. 5. Do not create a replacement project or change DNS records while recovery is being reviewed. 💬 Request container recovery ** Contact Search Atlas support using the available support channel. Include the project ID, the failed action, and the error message. Ask whether the existing development container can be recovered without changing the live domain, deployment, tracking, or survey, and request confirmation before any changes. A useful message is: “Please recover the existing Website Studio development container for project [project ID] after startup/build failures. Preserve the live domain, deployment, tracking, and survey. Do not create a new project or change DNS.” ⏳ What happens next ** Ask support to review the project and container state, determine whether recovery is possible, and advise on the steps needed to restore development access. Avoid changing the existing project or connected settings until you have discussed the recovery plan with support. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 14, 2026

🛠️ Fix Website Studio Loading and SSL

🔍 Check whether the project is still loading Website Studio projects may take time to load while site changes are being processed. Refreshing repeatedly can interrupt the process, so wait several minutes before trying again. < - Confirm that your internet connection is stable. - Open the project in a supported, up-to-date browser. - Try a private or incognito window. - Clear the browser cache, then sign in again. - Disable browser extensions that may block scripts or pop-ups. 🔒 Check SSL setup SSL can fail when the domain is not connected correctly or DNS changes have not finished propagating. Review the following items: - Confirm that the domain is entered correctly in Website Studio. - Check that the required DNS records match the values shown in the platform. - Remove conflicting records that point the domain to another hosting service. - Make sure the domain is active and has not expired. - Allow time for recent DNS updates to take effect before retrying SSL. 🔁 Retry safely 1. Make sure your site is published. Click Publish, or Publish Changes if you have unpublished edits, so the domain can be connected. 2. Verify the domain and DNS records. 3. Wait for pending processing to finish. 4. Reload the project and check the SSL status again. 5. Test the site using the correct domain and HTTPS address. 📋 Gather details for support If the project remains stuck or SSL fails across multiple sites, record the project names, affected domains, the approximate time the issue started, and any error messages. This helps our team investigate the issue faster. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Last updated on Nov 15, 2026