🛠️ Troubleshooting

🛠️ Fix Website Studio Custom Domain Errors (404, SSL, DNS Proxy)

Use this article to diagnose and fix the most common Website Studio custom domain errors — 404 pages, SSL warnings, and DNS failures — and to know when an issue clears on its own versus when to contact support. The most overlooked fix is disabling a DNS proxy that blocks CNAME validation. ⏳ When to Wait vs. When to Contact Support After you connect a custom domain to your Website Studio site, you may see errors such as 404 Page Not Found, Your connection is not private, This site can't be reached, or DNS not resolving. In most cases the setup did not fail — DNS changes or SSL certificates are still processing. Wait in these situations: - Wait up to 48 hours while DNS is propagating or an SSL certificate is being issued — these delays are usually temporary. - If you see no progress at all (no status change, no error message) after 24 hours, contact support instead of continuing to wait. Contact support immediately if any of these apply: - Your domain is stuck on Pending verification with no error message and no progress for more than 48 hours. This is a known issue where the verification system may fail silently without displaying an error in the UI. Contact support with your domain name — the backend must be checked manually. - You see a Domain already registered error. - Your domain does not appear in your account after purchase. - A previously working site suddenly shows a Your connection is not private warning. This indicates an expired SSL certificate. The auto-renewal system has a known issue where certificates are not always reissued automatically before they expire, so the secure connection breaks. As a workaround, contact support with your domain name so the certificate can be renewed manually — do not wait for it to self-resolve. 🌐 How a Website Studio Domain Connection Works Understanding the connection chain helps you spot which step is failing. When someone visits your domain, this happens in order: 1. The visitor enters your domain. 2. Your DNS provider resolves the domain. 3. The CNAME record points to Website Studio hosting. 4. The DNS Validation & Publishing Status moves through Pending → Validating → Connected. 5. Website Studio serves your site. 6. The SSL certificate secures the connection. If any step is incomplete or misconfigured, your site shows an error. The status indicator tells you where the chain stopped. 🧩 Cause 1 — DNS Has Not Fully Propagated The most common reason for domain errors is DNS propagation delay. After you add your CNAME record, the update must spread across global DNS servers. Expect: - At least 2 hours in most cases. - Up to 24–48 hours on slower networks. During this window, different visitors may see different results — the old site, a DNS error, or a 404 — while others already see the new site. This is expected and usually clears on its own. One important exception: if you have already waited a full day or more and still see errors, the problem is more likely a DNS proxy conflict (see Cause 2) than propagation. A proxy will not clear with time, so move to the next section instead of waiting longer. 📊 What Each DNS Validation & Publishing Status Means Inside Website Studio, your domain displays one of these statuses. The legacy red DNS Failed label is no longer shown during normal propagation. - Pending — DNS records have been submitted and are waiting to propagate. Expected during the first 2+ hours. - Propagating / Validating — the system is actively checking your DNS records. - Connected — your domain is verified and live. 🔌 Cause 2 — Your DNS Proxy Is Enabled If your CNAME record is correct but the domain still fails to connect after a day or more, a DNS proxy is the likely cause. Some DNS providers (for example, Cloudflare) route your record through their own proxy by default — often shown as a proxied toggle or an orange cloud icon. A proxied record hides your real CNAME target, so Website Studio cannot validate it and the connection stays stuck. To fix it: 1. Open your DNS provider's DNS management panel (for example, Cloudflare, Route 53, or GoDaddy) and find the CNAME record for your Website Studio domain. 2. Look for a DNS proxy, orange cloud, or CDN toggle on that record. This setting routes traffic through the provider's network and hides your real CNAME target. 3. Switch the proxied setting off so the record is set to DNS only (unproxied), then wait about 5 minutes for the change to propagate. If you cannot locate this setting, contact your DNS provider's support. 4. Save the record. 5. Return to Website Studio and reverify DNS for the domain. 6. If errors remain from earlier attempts, clear your browser cache (or open the site in a private window) and reload. Once the proxy is off and DNS is reverified, the status moves to Connected and your site loads normally. 🔤 www Subdomains: Use a CNAME, Not an A Record For www subdomains, add a CNAME record (not an A record) to your DNS provider, and delete any existing A record for www. If you see SSL errors only on www, confirm your DNS provider has not reverted the record to A record format. 🎯 You now know how to tell a temporary delay from a real misconfiguration: wait for propagation and SSL within 48 hours, disable a DNS proxy if your CNAME won't validate, and contact support with your domain name for silent pending states or expired SSL certificates.

🏗️ Search Atlas — Website Studio Issues

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

🔒 Fix SSL Certificate Failures Caused by Conflicting A Records in Website Studio

If SSL certificate generation fails in Website Studio despite correct DNS setup and multiple retries, your domain likely has conflicting A records. Remove any A records not pointing to Search Atlas's IP address (34.148.211.207) and retry provisioning to resolve the issue. ⚠️ Why Multiple A Records Block SSL Provisioning When Website Studio provisions an SSL certificate for your custom domain, the certificate authority verifies that your domain resolves to the correct server. If your DNS has multiple A records and any of them point to a different IP address, the verification fails — even if one correct record also exists. Your domain must have exactly one A record pointing to Search Atlas's IP address: 34.148.211.207. Any additional A records pointing elsewhere will block SSL issuance. 🔍 How to Check Your Domain's A Records Use a free DNS lookup tool to inspect your current A records before making any changes. 1. Go to a DNS lookup tool such as dnschecker.org or MXToolbox. 2. Enter your domain name and select A Record as the lookup type. 3. Review the results. If you see more than one IP address listed under A records, you have conflicting entries. 4. Flag any A record whose value differs from 34.148.211.207 — you'll delete those in the next section. If all A records already show only 34.148.211.207, contact Search Atlas Support — the issue may be elsewhere in your DNS configuration. 🛠️ How to Remove Conflicting A Records Log in to your DNS provider — for example, GoDaddy, Cloudflare, Namecheap, or your domain registrar's control panel. 1. Navigate to the DNS Management or DNS Zone Editor section for your domain. 2. Locate all A records for the root domain (@) or the specific subdomain you are connecting to Website Studio. 3. Delete all A records except the one with the value 34.148.211.207. 4. Confirm that exactly one A record remains, pointing to 34.148.211.207. 5. Save your changes. DNS changes typically apply within minutes but can take up to 48 hours to propagate globally. Confirm full propagation using the DNS lookup tool from the previous section before retrying SSL provisioning. 🔄 How to Retry SSL Provisioning in Website Studio Once DNS has propagated and only the correct A record is active, return to Website Studio to retry certificate generation. 1. Log in to Search Atlas and open Website Studio. 2. Select the project where SSL provisioning previously failed. 3. Go to Settings → Domain. 4. Click Retry SSL or Provision Certificate. You'll see a confirmation message once the certificate is successfully issued. If provisioning fails again, verify that DNS has fully propagated and that no conflicting A records have been re-added. 🎯 You now know how to identify and remove the conflicting A records that block SSL provisioning in Website Studio. If certificate generation continues to fail after fixing your DNS, contact Search Atlas Support for further assistance.

🔄 Recovering Deleted Pages in Website Studio

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

🛠️ Website Builder: Published Pages Show Only Header and Footer with No Body Content

If a page in your Website Builder project loads its URL but shows only the header and footer with no body content, your project needs to be republished. This happens when pages are created, edited, or regenerated after the last publish — including pages the platform modifies automatically during AI generation runs. A republish restores the missing content. ⚠️ Why Published Pages Can Show a Blank Body When you publish your Website Builder project, Search Atlas generates a live snapshot of every page at that moment. Pages added, edited, or regenerated after that last publish are not included in the deployed snapshot — including pages the platform creates or modifies automatically during an AI generation run — and no automatic republish is triggered. The site URL resolves and the shared layout (header and footer) loads correctly, but no body content exists in the snapshot for those pages yet. Search Atlas engineering has confirmed that automatic republishing after platform-driven page changes is a known gap, and a fix is currently in progress. Until it ships, manually republishing your project is the supported workaround. 🔍 How to Confirm This Is Your Issue Check for all four symptoms on the affected pages: - The page URL loads without a 404 error. - The site header and footer render correctly. - The area between the header and footer is completely blank. - The affected pages were created, edited, or regenerated (including by the AI agent) after the most recent project publish. If all four apply, republishing the project will resolve the issue. 🔄 How to Fix It: Republish Your Website Builder Project Republishing forces Search Atlas to regenerate and deploy all pages — including any added, edited, or regenerated since the last publish. 1. Open Website Studio from the left sidebar of your Search Atlas dashboard. 2. Select the project with the affected published pages. 3. Click Publish or Republish in the top-right corner of the editor. - Publish appears if the project has never been deployed. - Republish appears if it has been deployed before. - Both actions regenerate and deploy all pages. 4. Wait for the green success notification in the top-right of the editor and for the button to return to its idle state — this confirms deployment is complete. 5. Reload the affected URLs in a new private or incognito tab to bypass browser cache, and confirm the body content now appears between the header and footer. After republishing, all pages — including those created, modified, or regenerated since the previous publish — will render their full body content. 💡 When to Republish After Editing Your Project Republish your project any time you or the platform make changes, including when you: - Add one or more new pages to the project. - Make significant content or layout changes to an existing page. - Update the site-wide header, footer, or layout template. - Rename or change a page's URL slug. - Run an AI generation that creates or rewrites pages in the project. Republishing after each batch of changes ensures the live snapshot always reflects the current state of your project. 🛟 Still Not Working? Contact Search Atlas Support If body content is still missing after a successful republish, or if the republish does not produce a visible website, contact Search Atlas Support. A separate known publish-time issue currently in progress with engineering can, in some cases, affect the result of a republish — the support team can confirm whether your project is impacted and apply the appropriate fix. When you contact support, include: - Your Search Atlas account email. - The Website Builder project name. - The full URLs of the affected pages. - The approximate time of your most recent republish attempt. - A screenshot of the blank page (or the unexpected publish output) if available. The support team will escalate to engineering and track the issue against the active known-issue tickets so you receive an update when the platform-level fix is released. 🎯 Republishing your Website Builder project is the fastest way to restore missing body content on published pages, including pages updated automatically by AI generation runs. If pages still appear blank after republishing, contact Search Atlas Support with your project name and the affected page URLs so the team can investigate further.

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

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

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

🔒 Fix Custom Domain SSL Stuck on Pending

🧭 Overview When you connect a custom domain in Website Studio, Search Atlas automatically provisions an SSL certificate for your site. In most cases this completes within minutes. If the status stays on Pending and your site won't load, the most common cause is an AAAA (IPv6) record on your domain that conflicts with SSL provisioning. This article walks you through diagnosing and fixing that conflict, and clarifies the differences between the setup instructions you may have seen. ⚠️ Why SSL Gets Stuck on Pending Search Atlas provisions SSL over IPv4. If your domain has an AAAA record (which points to an IPv6 address), your browser or DNS resolver may route requests over IPv6 instead. Because our SSL certificate provisioning service does not respond on that IPv6 path, the verification handshake never completes and the certificate stays in a Pending state indefinitely. The domain appears broken even though every other setting looks correct. 🔍 Step 1 — Check for an AAAA Record 1. Go to your domain registrar or DNS provider (for example, Cloudflare, GoDaddy, Namecheap, or Route 53). 2. Open the DNS Management or DNS Records section for your domain. 3. Look for any record with Type = AAAA. It may be set to your root domain (@) or a subdomain such as www. 4. If you find one or more AAAA records, continue to Step 2. If you find none, skip to Step 4. 🗑️ Step 2 — Remove the AAAA Record 1. Select the AAAA record in your DNS provider's dashboard. 2. Delete it. If your provider asks for confirmation, confirm the deletion. 3. Repeat for every AAAA record associated with the domain or subdomain you are connecting to Website Studio. 4. Do not delete A records, CNAME records, or TXT records — only AAAA records. Note: Removing an AAAA record does not break your domain. It simply stops IPv6 routing, which is not required for Search Atlas to serve your site. ⏳ Step 3 — Wait for DNS Propagation and SSL Renewal 1. DNS changes can take 5 minutes to 48 hours to propagate worldwide, depending on your provider and your domain's TTL (Time To Live) setting. 2. After removing the AAAA record, return to Website Studio → Settings → Custom Domain. 3. If the SSL status still shows Pending, click Retry SSL (or disconnect and reconnect the domain) to trigger a fresh provisioning attempt. 4. Monitor the status. It should move to Active within a few minutes once DNS has propagated. ✅ Step 4 — Verify Your Required DNS Records Whether or not you had an AAAA record, confirm that your DNS settings exactly match the following. These are the authoritative values for Website Studio: - A record — Point your root domain (@) to the IP address shown in Website Studio → Settings → Custom Domain. - CNAME record — Point www to the target hostname shown on the same settings screen (for example, sites.searchatlas.com). - No AAAA records on the root domain or www subdomain. Use a free tool such as dnschecker.org or mxtoolbox.com to confirm your records have propagated before retrying SSL. 📋 A Note on Contradictory Setup Instructions You may have noticed differences between the setup steps described in our help documentation and the instructions shown by the in-app setup assistant. Here is what each source is intended for: - In-app setup assistant (the guided flow inside Website Studio) — These steps are the current, correct instructions. Always follow these when connecting a domain for the first time. They reflect the latest infrastructure configuration. - Help Centre articles published before mid-2024 — Some older articles referenced a legacy CNAME-only setup that has since been updated. If an article tells you to point @ to a CNAME target rather than an A record, that article is outdated. Follow the in-app instructions instead. We are actively auditing and updating older documentation to remove this inconsistency. We apologise for any confusion this has caused. 🛠️ Quick Troubleshooting Checklist - AAAA record removed from DNS? Yes / Not applicable - A record for @ pointing to the correct IP? Yes - CNAME for www pointing to the correct target? Yes - DNS propagation confirmed via dnschecker.org? Yes - SSL Retry triggered in Website Studio after DNS update? Yes - Waited at least 15 minutes after retrying? Yes If all items above are checked and SSL is still showing Pending after 2 hours, escalate using the contact method below. 💬 Still Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Fixing Inverted Colors in Website Studio: Chrome Dark Theme Setting

Overview If colors in your Website Studio preview or editor look inverted, washed out, or completely wrong in Chrome — but appear correctly in other browsers — the cause is almost always Chrome's Auto Dark Mode or dark theme setting. Chrome can automatically force dark styling onto web pages, which overrides the design choices you've made in Website Studio and makes colors appear flipped. The fix takes less than a minute: switch Chrome to the light theme. This article walks you through how to confirm the cause, fix it, and what to do if the issue continues. Why This Happens Chrome has a feature that automatically applies a dark color scheme to websites based on your operating system or browser theme. When this is enabled, Chrome rewrites the colors of page elements on the fly. In Website Studio, this can cause: - Backgrounds appearing as the opposite color (white becomes black, light grey becomes dark grey) - Text colors flipping to maintain contrast - Images and design elements looking inverted or muted - Previews that don't match what your visitors actually see Your published site is not affected for visitors who don't have this setting enabled — this is purely a local browser display issue. How to Fix It: Set Chrome to Light Theme 1. Open Chrome and click the three-dot menu in the top-right corner. 2. Select Settings. 3. In the left sidebar, click Appearance. 4. Under Mode, select Light. 5. Refresh your Website Studio tab. Colors should now display correctly. If You're Using Chrome's Auto Dark Mode Flag Some users have enabled an experimental flag that forces dark mode on all sites. To disable it: 1. In Chrome's address bar, type chrome://flags and press Enter. 2. Search for Auto Dark Mode for Web Contents. 3. Set it to Disabled. 4. Click Relaunch to restart Chrome. Check Your Operating System Theme If Chrome is set to follow your system theme, switching your OS (Windows, macOS, or ChromeOS) to light mode will also resolve the issue. Common Pitfalls - Only one Chrome profile is affected. Theme settings are per-profile. If you use multiple Chrome profiles, check each one. - Hard refresh after changing the theme. Use Ctrl+Shift+R (Windows) or Cmd+Shift+R (Mac) to clear cached styles. - Extensions can also invert colors. Dark Reader and similar extensions force dark themes on websites. Disable them for Website Studio, or whitelist the Search Atlas domain. - Incognito mode can help confirm the cause — if colors look correct there, an extension or profile setting is the culprit. How to Confirm It's Fixed After applying the fix, open your Website Studio project and compare the editor preview to your published site in a different browser (Safari, Firefox, or Edge). The colors should now match across all browsers. Next Steps If you've switched Chrome to light theme, disabled Auto Dark Mode, and turned off any color-altering extensions but colors still appear inverted, send our support team: - A short screen recording (a Jam.dev recording works great) showing the issue - Your Chrome version (found at chrome://version) - Your operating system and theme setting - A link to the Website Studio project where you're seeing the issue This information lets us reproduce and investigate quickly. Reach out via in-app chat or your account manager any time the issue reappears so we can keep monitoring it.

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

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

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

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

🛠️ Fix Website Studio Glitches and Request Credit Refunds

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

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

🛠️ Fix WordPress Migration Errors from Website Studio

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

🛠️ Fix Website Studio Failed to Load Projects

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

Website Studio Import Edits and Project Transfers

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

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

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

🛠️ Fix Website Studio Landing Page Generation Failures

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

🛠️ Fix Website Studio Editor Page and Saving Issues

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

🖼️ Fix Cloud Stack Photo Count Errors in Brand Vault

🗺️ Where to Find Brand Vault Access your Brand Vault: top-right More Features menu (grid icon, next to your Avatar Menu (👤)) → Brand Vault, or the top-right More Features menu (grid icon) → Brand Vault. If you have already created one, it will appear there. ⚠️ Understanding the 'Too Many Photos in DKN' Error This error appears when the number of photos associated with your Brand Vault exceeds the allowed limit for a Cloud Stack. The limit applies to all photos stored within your Brand Vault's photo library — not only the photos you select at the moment of Cloud Stack creation. This means that even if you choose only four photos during the Cloud Stack setup, the error can still occur if your overall Brand Vault photo library already contains too many images. 📸 What Counts Toward the Photo Limit The photo count is based on the total images stored in your Brand Vault photo library. Important: The exact breakdown of which image types count toward the limit — such as logos, profile images, or images from connected sources — is not fully documented at this time. If you are seeing a count that does not match what you expect, do not remove photos based on assumptions about hidden fields. Instead, contact our team directly for verified guidance (see below). 🔧 Steps to Resolve the Error 1. Open your Brand Vault project using either method above. 2. Review the total number of photos currently stored in your Brand Vault — not just the ones you plan to use for the Cloud Stack. 3. If your total photo count is at or near the limit, remove photos you no longer need to bring the total below the allowed threshold. 4. Once the library count is within the limit, return to the Cloud Stack creation flow and try again. ❓ What to Do If the Error Persists If you have reduced your photo library count and the error still appears, or if the number shown in your library does not seem to explain the error, do not delete additional photos without guidance. There may be account-specific factors affecting your limit that require investigation by our team. When contacting support, please have the following ready: your Brand Vault project name, the exact error message you are seeing, and a timestamp of when the error occurred. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Website Studio 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 Spinning Wheel and Publishing Failures

🔍 Overview Some customers encounter a spinning wheel, red alert banners, or a stuck publishing state inside Website Studio. In some cases, content added to one page disappears or strips content from other pages. These issues are typically caused by a jammed UI session, a cached publishing state, or a temporary sync error between the editor and the backend. This article walks you through the steps to resolve these issues quickly. ⚠️ Common Symptoms - A spinning wheel appears during site generation or content publishing and never completes. - Red alert banners display after attempting to publish a page or blog post. - Content added to a page does not save, or saving one page removes content from another. - The Website Studio UI becomes unresponsive or appears frozen. - A published post shows a placeholder title or slug instead of the one you entered. 🛠️ Step-by-Step Fixes 1. Hard-refresh the page. Press Ctrl + Shift + R (Windows/Linux) or Cmd + Shift + R (Mac) to force a full reload and clear any cached UI state. Do not use the browser's back button, as this can preserve the jammed state. 2. Clear your browser cache and cookies. Go to your browser settings, clear cached images, files, and cookies for the Search Atlas domain, then reload Website Studio at Left sidebar → Website Studio. 3. Try a different browser or incognito window. Open an incognito or private window (or switch to Chrome, Firefox, or Edge) to rule out browser extensions or local cache as the cause. 4. Wait two to three minutes before retrying. If a publishing job is stuck in a pending state on the server, forcing another publish immediately can create a conflict. Wait a short time, then attempt to publish again. 5. Re-enter content on the affected page. If content was stripped from a page after saving another, re-enter the missing content, save that page first, then proceed to publish. Avoid editing multiple pages simultaneously in separate tabs. 6. Verify the page title and slug before publishing. A known issue can cause posts to publish with a placeholder title or slug. Always confirm the title and slug fields are correctly filled in the editor before clicking publish. 7. Re-generate the affected page. If the page remains broken after the steps above, use the Generate PPC Landing Page, Clone an Existing Page, or Build a Local Website options from Website Studio to recreate the page from scratch. ✅ How to Avoid This Issue Going Forward - Edit and publish one page at a time rather than working across multiple tabs. - Always confirm the page title and slug fields are populated before publishing. - Keep your browser updated to the latest version for the best compatibility with Website Studio. - Save your content frequently using the in-editor save option before triggering a full publish. - If you notice a spinning wheel lasting more than 60 seconds, refresh immediately rather than clicking publish again. 💬 Still Need Help? If the spinning wheel or publishing failure persists after following all the steps above, our team can investigate the specific session or publishing job on your account. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Troubleshoot Website Studio and Coming Soon Pages

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

🛠️ Fix Website Studio AI Agent Errors and Restore Projects

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

🛠️ Fix Website Studio Publishing and Display Issues

🔍 Overview Website Studio issues typically fall into four categories: publishing getting stuck on the Almost ready screen, formatting changes appearing unexpectedly during edits, hero image links breaking after an update, and projects becoming temporarily inaccessible. This article walks you through the most effective fixes for each. ⏳ Publishing Hangs on 'Almost Ready' If your site stays on the Almost ready screen for more than a few minutes, the publishing process may have stalled. Follow these steps to resolve it: 1. Wait at least 3–5 minutes before taking action — some publish jobs take longer depending on page complexity. 2. Refresh the page. Navigate to Left sidebar → Website Studio (URL: /website-studio) and reopen your project. 3. Check whether the site has actually published by opening the live URL in a new browser tab. The publishing job sometimes completes in the background even when the screen appears frozen. 4. If the project still shows as stuck, close the project, return to the Website Studio dashboard, and attempt to publish again from the project card menu. 5. Clear your browser cache or try a different browser to rule out a local caching issue. This issue is a known platform behaviour that has been addressed in recent updates. If repeated publish attempts fail, contact support using the instructions at the bottom of this article. 🎨 Unexpected Formatting Changes During Edits You may notice that layout, font, spacing, or colour changes appear inconsistently — or that the editor reports a successful change that is not reflected in the preview. This is a known visual sync issue. Here is how to handle it: 1. After making a change, wait 10–15 seconds and then manually refresh the preview panel rather than assuming the change failed. 2. If the preview still does not update, save your work, exit the project, and reopen it. The editor re-syncs on reload. 3. Avoid making rapid successive edits before the previous change has confirmed. Submit one change at a time and wait for confirmation before proceeding. 4. If you are using AI agent-requested changes, add clear, specific instructions and include reference images where possible. Vague prompts are more likely to produce inconsistent results. 5. After publishing, verify changes on the live URL — not just the in-editor preview — to confirm the final output. 🖼️ Hero Image Links Break After Updates Hero image links can break when a page update regenerates asset paths or overwrites manually set link targets. To prevent and fix this: 1. After any publish or major edit, check all hero image links by previewing the live page and clicking each linked image. 2. If a link is broken, re-enter the destination URL directly in the image link field within the editor and save the change explicitly before publishing again. 3. Avoid navigating away from the editor immediately after setting an image link — confirm the field has saved by seeing the URL persist in the input. 4. If the same image link breaks repeatedly after updates, try unlinking and relinking the image from scratch rather than editing the existing link value. 🚫 Unable to Access a Project If a project appears missing or you cannot open it from the Website Studio dashboard, try the following: 1. Refresh the Website Studio page at Left sidebar → Website Studio (/website-studio). 2. Log out and log back in to reset your session. 3. Check with your account administrator that your team role has the correct permissions. Admins can review this under Top-right corner (avatar) → Team Members → Team Members. 4. Try a different browser or an incognito window to rule out extension or cache conflicts. ✅ Quick Reference Checklist - Stuck publishing: Refresh, check live URL, retry publish, clear cache. - Formatting not saving: Wait for confirmation, reload editor, make one change at a time. - Broken image links: Re-enter and save the link explicitly after each publish. - Project inaccessible: Refresh, log out and in, verify team permissions. 💬 Still Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

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

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

🖥️ Fix Website Studio Visual Editor Page and Save Issues

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

🌐 Fix Custom Domain Connection Failures in Website Studio

🔍 Understanding Custom Domain Connection Failures If your custom domain fails to connect to Website Studio even after you've added the correct DNS records, the issue is usually not the DNS records themselves. The most common causes are a proxied DNS toggle that blocks validation and browser cache holding stale data from earlier failed attempts. This article walks you through diagnosing and fixing persistent domain connection errors in Website Studio. ✅ Before You Start: Verify DNS Records Are Correct First, confirm that your DNS records are set up correctly. Log in to your domain registrar (GoDaddy, Namecheap, Route 53, etc.) and check that you've added the CNAME record exactly as Search Atlas provided it. The record should point your subdomain to Website Studio's servers. If your DNS records are correct and the error persists for more than 30 minutes, move to the next section. ⚠️ Step 1: Disable DNS Proxying on Your CNAME Record This is the most common cause of validation failures. Many domain registrars (especially Cloudflare) offer a DNS proxy toggle that encrypts traffic between your domain and their servers. This toggle blocks Website Studio from validating your domain because the validation request cannot reach your actual DNS records. 1. Log in to your domain registrar's dashboard. 2. Find the DNS records section (often under DNS Management or Name Servers). 3. Locate the CNAME record you created for Website Studio. 4. Look for a proxy toggle, often shown as an orange cloud icon (Cloudflare) or similar indicator. It may be labeled "Proxied," "DNS Only," or "Routing." 5. If the toggle is ON (proxied), click it to turn it OFF. 6. Save your changes. After disabling the proxy, Website Studio will be able to validate your domain. Validation typically completes within 5 to 10 minutes, but can take up to 30 minutes. 🗑️ Step 2: Clear Your Browser Cache If you've been testing the domain connection for several hours or days, your browser may be holding cached data from earlier failed validation attempts. This prevents Website Studio from recognizing that the domain is now properly connected. 1. Open Website Studio and navigate to your website settings. 2. Press Ctrl + Shift + Delete (Windows) or Command + Shift + Delete (Mac) to open your browser's cache clearing menu. 3. Set the time range to All Time. 4. Check Cookies and cached images and files. 5. Click Clear data. 6. Close Website Studio completely and reopen it in a fresh browser tab. Return to your domain settings and attempt to validate the connection again. ⏳ Step 3: Wait for DNS Propagation (If Needed) After disabling the proxy toggle, DNS propagation is usually quick. However, some registrars cache changes for up to 48 hours. If validation still fails after 30 minutes, it may be propagation delay. Check your DNS propagation status using a free tool like DNS Checker. Search for "DNS propagation checker," enter your domain, and verify that your CNAME record is live across multiple global DNS servers. If the record shows as live, return to Website Studio and clear your cache again (Step 2). 🛠️ Troubleshooting: Check for Conflicting DNS Records Some domains have multiple CNAME records or A records that conflict with each other. Website Studio requires a dedicated CNAME record pointing only to Website Studio's servers. 1. In your domain registrar's DNS section, list all DNS records. 2. Confirm you have only one CNAME record for the subdomain you're connecting (e.g., www or blog). 3. If you have multiple CNAME records or an A record pointing to the same subdomain, delete the conflicting records and keep only the Website Studio CNAME. 4. Save changes and wait 5 to 10 minutes. 5. Clear your browser cache (Step 2) and retry validation in Website Studio. 🔗 Verify the Connection in Website Studio Once you've completed the steps above, return to Website Studio to verify the domain is now connected. 1. In Website Studio, go to Settings or Domain (exact location depends on your site layout). 2. Look for your custom domain in the domain list. 3. If a green checkmark or "Connected" status appears next to your domain, the connection is successful. 4. If the connection is still pending, wait another 10 minutes and refresh the page. 📋 Common DNS Record Examples Below are typical CNAME records that Website Studio provides. Your specific record may vary, but it will follow this format: - Record Type: CNAME - Name/Subdomain: www (or your chosen subdomain) - Value/Target: [your-site].wsstudio.com (or similar Website Studio domain) - Proxy Status: DNS Only (not proxied) If your registrar shows a different format, refer to their documentation or contact their support. ❌ If Problems Persist If your domain still fails to connect after completing all steps above, there may be a deeper issue with your domain configuration or registrar account. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Website Studio Blank Pages and Content Flashing

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

🗂️ Recover Website Studio Files From a Canceled Account

🔍 Overview If your Search Atlas account has been canceled and you need to retrieve files from a Website Studio project, you can request a short-term free trial to regain access. This article explains how that process works and what to expect. ⚠️ Important: Act Before Your Trial Expires When a temporary trial is granted, it comes with a future billing date. You must cancel the trial before that date to avoid being charged. Make sure you download all the files you need as soon as access is restored, then cancel immediately if you do not intend to continue as a paying subscriber. 🛠️ How to Request Temporary Access 1. Contact our support team via the chat widget. Open the chat widget in the bottom-right corner of the platform — you may be able to do this even from the login or marketing page — and type human teammate to be connected with a member of our team. 2. Provide your canceled account email address and the name or URL of the Website Studio project you need to access (for example, the domain associated with the project). 3. Request a temporary free trial so you can log in and download your files. Our team will escalate the request to the appropriate internal team for approval. 4. Wait for confirmation. Once the trial is approved, you will receive details including the length of the trial period and the next billing date. 📂 Downloading Your Files After Access Is Restored 1. Log in to your Search Atlas account using your original credentials. 2. Navigate to Website Studio within the platform to find your projects. 3. Open the relevant project and download or export any files you need before your trial period ends. 4. Once you have everything you need, cancel your trial immediately to avoid being billed on the next billing date. 💡 Tips to Avoid This Situation in the Future - Before canceling your account, always export or back up any Website Studio project files you want to keep. - Check that all important assets are saved locally or in an external location before your cancellation takes effect. 💬 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.

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

🔐 Fix SSL Certificate Failures for Custom Domains

🧩 What This Article Covers When connecting a custom domain in Website Studio, the DNS verification step may pass successfully — but the SSL certificate generation then fails repeatedly. This article explains why that happens and how to fix it so your domain loads securely over HTTPS. ⚠️ What Causes This Issue SSL provisioning failure after a successful DNS check is almost always caused by an incorrectly configured DNS record — specifically an A record or AAAA record that is pointing to the wrong address. Even though the basic DNS lookup resolves, the SSL certificate authority cannot complete verification when the underlying record is misconfigured. Common signs you are experiencing this issue: - The DNS check in Website Studio shows a passing status. - The SSL certificate status shows generating for an extended period, then fails. - The failure repeats every time you attempt to re-provision the certificate. - Your custom domain does not load over HTTPS after publishing. 🛠️ How to Fix It 1. Log in to your domain registrar or DNS provider (for example, GoDaddy, Cloudflare, Namecheap, or wherever your domain's DNS is managed). 2. Locate your DNS records for the custom subdomain or root domain you are connecting to Website Studio. 3. Check your A record and AAAA record values carefully. An A record must point to a valid IPv4 address, and an AAAA record must point to a valid IPv6 address. A common cause of SSL failure is an AAAA record set to an incorrect or placeholder value, or an A record pointing to the wrong IP address. 4. Correct any misconfigured records. If you are unsure what IP address values to use, refer to the DNS setup instructions shown inside Website Studio when you added the custom domain, or contact your DNS provider for guidance on the correct values. 5. Save your changes in your DNS provider's dashboard and allow time for propagation — this can take anywhere from a few minutes to up to 48 hours depending on your provider and TTL settings. 6. Return to Website Studio and attempt to connect or re-provision the custom domain again once DNS propagation is complete. ✅ How to Confirm the Fix Worked After updating your DNS records and re-attempting provisioning in Website Studio, the SSL certificate status should move from generating to a confirmed active or connected state. You can verify the fix by opening your custom domain in a browser and confirming that a padlock icon appears in the address bar, indicating a secure HTTPS connection is active. 💡 Tips to Avoid This Issue in the Future - Double-check every DNS record value before attempting to connect a custom domain — pay close attention to A records and AAAA records. - If you have an AAAA record configured but your hosting does not use IPv6, consider removing the AAAA record entirely rather than leaving it set to an incorrect value. - Use a free DNS lookup tool (such as MXToolbox or Google Admin Toolbox) to verify what your records resolve to before re-attempting SSL provisioning. - Allow full DNS propagation before retrying — attempting to provision the certificate too early can cause repeated failures even after a correct DNS change. 💬 Still Need Help? If you have corrected your DNS records and SSL provisioning is still failing, our team can investigate further. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

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

🛠️ Website Studio 404 Errors and Credit Compensation

🔍 What This Article Covers This article explains why 404 errors occur in Website Studio, how to troubleshoot them, and how to request courtesy credits if you used credits while working through a platform issue. ⚠️ Understanding 404 Errors in Website Studio A 404 error in Website Studio means a page or resource could not be found. This can happen for several reasons: - A generated or cloned page was not saved properly before publishing - A project was imported with broken or missing asset links - A temporary platform instability interrupted the page-generation process - A URL path conflict occurred between pages in the same project These errors are usually resolvable without losing your work. Follow the steps below before submitting a compensation request. 🛠️ How to Troubleshoot a 404 Error 1. Navigate to Website Studio: In the left sidebar, click Website Studio. You will land on the /website-studio page. 2. Locate the affected project: Find the project or page showing the 404 error. If the page is missing entirely, check whether it still appears in your project list. 3. Try regenerating the page: Use the Generate PPC Site or Import Site action in Website Studio (What will we get done today?) to recreate the missing page. Clone an existing working page as a base if needed using the Clone an Existing Page option. 4. Check imported projects: If the error appeared after using Import Project, verify that all assets and URLs in the imported files are valid and accessible. 5. Review your Brand Vault: Open Create brand vault to confirm that brand assets are correctly linked, as missing brand assets can sometimes trigger 404 responses during page rendering. 6. Reload and re-publish: After making corrections, save the page and re-publish. Wait one to two minutes, then test the URL again in a fresh browser tab. 💡 Common Fixes That Resolve 404 Errors - Hard refresh the page: Press Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac) to clear cached data that may be serving the old broken URL. - Check for duplicate slugs: Two pages with identical URL slugs can cause a 404 on one of them. Rename the slug of the affected page to make it unique. - Re-import the project: If an imported project is the source of the error, delete it and re-import using a clean file to rule out file corruption. - Wait for propagation: Newly published pages can take a few minutes to go live. If the 404 is brand new, wait five minutes and check again before troubleshooting further. 📊 When Credits Are Used During a Platform Issue Search Atlas credits are consumed each time a page is generated or a significant action is completed. If a platform-side issue — such as a temporary 404 error during generation — caused a credit to be used without producing a working result, you may be eligible for a courtesy credit refund. To strengthen your request, gather the following information before reaching out: - The date and approximate time the error occurred - The name of the project and the action you were performing (e.g., Generate PPC Site in Website Studio (What will we get done today?)) - The number of credits consumed during the affected session - Any error messages or screenshots you captured 🚀 How to Request Courtesy Credits Credit compensation requests are handled by our support team on a case-by-case basis. To submit a request, follow these steps: 1. Open the Search Atlas platform and log in to your account. 2. Click the chat widget in the bottom-right corner of the platform. 3. Type human teammate to be connected with a member of our team. 4. Provide the details listed in the section above (date, project name, action, credits used, and any error evidence). 5. Our team will review your request and apply courtesy credits to your account if the issue is confirmed to be platform-related. Note: Courtesy credits are granted for verified platform issues, not for user errors such as accidentally generating duplicate pages. Providing clear details speeds up the review process significantly. 🙋 Still Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 OTTO Pixel Verification Failures on Website Studio

🔍 Overview When you install the OTTO pixel on a Website Studio project, Search Atlas checks that the script is reachable and returns the expected response. If that check fails, OTTO cannot activate SEO automation for your site. This article explains the most common causes of verification failures and the general steps you can take — however, because the exact resolution depends on your specific setup, our support team may need to investigate further. ⚠️ Why Verification Fails Verification fails when Search Atlas cannot reach the OTTO script on your live site. The most frequent reasons are: - Script not saved or published: The pixel was added in the editor but the page was never published, so the script does not exist on the live URL. - Wrong placement: The script was placed in the body or a content block instead of the global <head> section. - Caching: An old cached version of the page is served without the script. - Content Security Policy (CSP) or firewall rules: A CSP header or WAF rule is blocking external scripts from loading. - Incorrect script copied: The pixel code was modified or truncated during copy-paste. ✅ General Troubleshooting Steps 1. Retrieve your OTTO pixel code. Inside Search Atlas, navigate to the OTTO or OTTO SEO section and locate your Website Studio project. Find the option to view or copy your pixel installation script, and copy the full code without editing it. 2. Add the script to your site's global head section. In Website Studio, look for a global custom code or header code area — not an individual page setting. Paste the script so it loads in the <head> on every page. 3. Save and publish your site. Apply your changes and publish so the live URL is updated. 4. Confirm the script is live. Open your site URL in a browser, right-click, choose View Page Source, and search (Ctrl+F or Cmd+F) for the OTTO script. If you see the full pixel code, the script is live. 5. Clear all caches. Clear any platform-level cache inside Website Studio, purge your CDN cache if you use one (Cloudflare, Fastly, etc.), and then hard-refresh your browser (Ctrl+Shift+R or Cmd+Shift+R). 6. Re-run verification. Return to the OTTO or OTTO SEO section in Search Atlas, locate your project, and trigger the verification check. Allow up to two minutes for the check to complete. 🔒 Fixing Blocked Scripts (CSP / Firewall) If the script appears in the page source but verification still fails, a security rule may be preventing it from executing or being reached by Search Atlas. Check your site's Content Security Policy headers and any Web Application Firewall rules to ensure external scripts are not blocked. 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 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.

⚠️ Website Builder: Chat Panel Cut Off Below the Fold

The left-hand chat panel in the Website Builder currently extends beyond the visible screen height, pushing the message input box below the fold. Zoom your browser out to 80–90% to restore the full layout while our engineering team deploys a fix. 🔍 What's Happening In the Website Builder (Left sidebar → Website Studio, dashboard.searchatlas.com/website-studio), the left-hand chat panel does not fit within the visible viewport height. The message input box at the bottom of the panel is cut off below the fold, making it difficult to type and send messages without scrolling the entire page. This is a layout display issue only. It does not affect any saved content, site files, or account data. 🛠️ Workaround Steps Zooming your browser out is the most practical fix — it restores the intended layout without requiring repeated page scrolling. 1. Open the Website Builder via Left sidebar → Website Studio (dashboard.searchatlas.com/website-studio). 2. Press Ctrl + Minus (Windows/Linux) or Cmd + Minus (Mac) to zoom your browser out. 3. Continue zooming until the level reaches approximately 80–90% and the full chat panel — including the message input box — is visible on screen. 4. To reset zoom at any time, press Ctrl + 0 (Windows/Linux) or Cmd + 0 (Mac). Alternative: Scroll the page down to reach the message input box. This requires scrolling each time you want to type a new message and is less convenient than adjusting browser zoom. 📡 Engineering Status Our engineering team has shipped a fix for this issue. If you are still experiencing the problem, please clear your browser cache and refresh the page. If it persists, contact support. 📞 When to Contact Support If the zoom workaround does not resolve the issue for you, or if reducing zoom to 80% is not practical for your workflow, contact our support team. When you reach out, include your browser name and version, your screen resolution, and a screenshot if possible — this helps us address the issue faster for your account. 🌀 Our team is actively working on a permanent fix, and the chat panel will return to its correct layout automatically once it ships. Thank you for your patience — the browser zoom workaround fully restores the Website Builder experience in the meantime.

🌐 Fix Website Studio Domain Mismatch and Form Duplication

🔍 Overview When your Website Studio project is published or shared, issues can arise if your primary domain and published domain do not match. Symptoms may include the social share thumbnail displaying the wrong domain, live site errors, or duplicate form submissions. This article explains what to check and how to get this resolved. ⚠️ Understanding the Root Cause Website Studio relies on the domain configured in your project to generate social share metadata, rewrite internal URLs, and route form submissions correctly. When the domain recorded in your project does not match the domain your site is actually live on, one or more of these systems can fail: - Thumbnail mismatch: Social platforms may cache and display an incorrect preview if the metadata points to the wrong domain. - URL forwarding or server errors: Internal links and redirects may break or produce errors if they are resolved against a mismatched domain. - Form submission duplication: Form submissions may be posted more than once if endpoints are resolving against both an old and a new domain during a transition. 🛠️ What to Check If you are experiencing any of the symptoms above, the most important thing to verify is that the domain configured inside your Website Studio project exactly matches the domain your site is published and live on. A mismatch between these two — even a difference as small as a missing or extra subdomain prefix — is the most common cause of all three symptoms. You should also check whether any domain forwarding or redirect rules set up outside of Search Atlas (for example, at your registrar or DNS provider) are pointing to the correct domain. An external forwarding rule that points to a different domain than the one recorded in your project can create redirect loops or server errors even after you correct the project settings. 📋 What to Have Ready When You Contact Support Because confirming and correcting a domain configuration in Website Studio requires access to your specific project settings, our support team will need to look into this on your behalf. To help us resolve this as quickly as possible, please have the following information ready: - The name of the Website Studio project affected - The domain your site is intended to be live on (the correct domain) - The domain currently appearing in the wrong location (e.g., in the social share thumbnail URL or in error messages) - Any exact error messages or HTTP error codes you are seeing - The timestamp of when you first noticed the issue If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Website Studio Custom Domain Timeout Errors

🔍 Overview After pointing your domain's A record to Website Studio, you may see an ERR_TIMED_OUT error when visiting your site. This is a common issue and is almost always caused by one of a few configuration gaps — even when DNS propagation appears complete. This article walks you through the most likely causes and the exact steps to fix them. ⚙️ How Custom Domains Work in Website Studio When you connect a custom domain to your Website Studio site, two things must be true at the same time: - Your domain's A record must point to the correct Website Studio IP address. - Website Studio must have your custom domain entered and saved inside the platform so it knows to serve your site when that domain is requested. If either side is missing or mismatched, the connection will time out rather than load your site. ✅ Step 1 — Verify the A Record Is Correct Before troubleshooting inside the platform, confirm your DNS is configured correctly. 1. Log in to your domain registrar or DNS provider (for example, GoDaddy, Namecheap, or Cloudflare). 2. Locate the A record for your root domain (shown as @ or your bare domain name). 3. Confirm the IP address matches exactly what Website Studio provided in its domain setup instructions. Even a single digit difference will cause a timeout. 4. Check that the TTL (Time to Live) is set to 3600 or lower to allow faster propagation. To verify propagation independently, use a tool such as whatsmydns.net and search for your domain's A record. Wait until the majority of global locations show the correct IP before continuing. ⚙️ Step 2 — Confirm the Custom Domain Is Saved in Website Studio DNS propagation alone is not enough. Website Studio must also be configured to recognise your domain. 1. In the left sidebar, click Website Studio and open your project. 2. Go to your site's Settings or Domain section within the builder. 3. Confirm your custom domain (for example, precisionspringfieldcurls.com) is entered exactly as it appears — no trailing slashes, no www prefix unless you also set up a CNAME for www. 4. Save the settings if you make any changes. If the domain field is blank or contains a typo, the platform will not route incoming traffic to your site, which causes a timeout on the visitor's end. 🌐 Step 3 — Check for www vs. Root Domain Mismatch A common source of timeouts is a mismatch between the domain version visitors use and the one configured in DNS. - Root domain (precisionspringfieldcurls.com) requires an A record pointing to Website Studio's IP. - www subdomain (www.precisionspringfieldcurls.com) requires a separate CNAME record pointing to your Website Studio domain handle, or a second A record. If your visitor types www. but you only configured the root A record, the www version will time out. Set up both records if you want both versions to work, and ensure Website Studio has the correct version saved as your custom domain. 🔒 Step 4 — Check for Conflicting DNS Records Conflicting records can silently block traffic even after a correct A record is added. - Look for duplicate A records pointing to different IP addresses for the same hostname. Delete any that do not point to Website Studio's IP. - Check for a CNAME record on the root domain. A root-level CNAME conflicts with an A record and can cause unpredictable timeouts. Remove it if present. - If you use Cloudflare, make sure the proxy (orange cloud) is turned off for the A record. Cloudflare's proxy can intercept traffic and prevent Website Studio from completing its SSL handshake, which causes timeout errors. ⏱️ Step 5 — Wait for Full Propagation and SSL Provisioning Even after everything is configured correctly, you may need to allow additional time. - DNS changes can take up to 48 hours to propagate fully worldwide, though most resolve within 1–4 hours. - Website Studio automatically provisions an SSL certificate once it detects your domain is pointing to it correctly. This process can take up to 30 minutes after propagation completes. - During SSL provisioning, the site may still time out or show a security warning. This is temporary. Try accessing your site in a private or incognito browser window to avoid cached DNS results while you wait. 💡 Quick Troubleshooting Checklist - A record IP matches Website Studio's provided IP exactly. - Custom domain is entered and saved inside Website Studio settings. - No conflicting A records or root-level CNAME records exist. - Cloudflare proxy is disabled for the A record (if using Cloudflare). - www and root domain are both configured if both are needed. - At least 1–4 hours have passed since the DNS change. - Tested in a private browser window to bypass local DNS cache. 🆘 Still Seeing a Timeout? If you have completed every step above and your custom domain is still timing out, our team can inspect your specific domain configuration directly. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix OTTO Pixel Installation and Landing Page Publishing

🔍 Overview If your OTTO pixel isn't tracking correctly, your permalink structure is causing errors, or your landing pages aren't publishing as expected, this guide walks you through the most common causes and fixes. Follow each section in order to resolve the issue quickly. ⚙️ Step 1 – Verify Your OTTO Pixel Installation The OTTO pixel must be placed correctly on your website for OTTO SEO to track and apply optimizations. An incorrect installation is the most common reason the pixel appears inactive. 1. In Search Atlas, go to OTTO SEO → All Sites (SEO Automation) in the left sidebar (URL: /seo-automation-v3). 2. Locate your connected website and open the OTTO Settings panel. 3. Copy the pixel code snippet provided. Make sure you copy the complete snippet — partial copies are a frequent source of errors. 4. Paste the snippet into the <head> section of every page on your website. If you use a tag manager (such as Google Tag Manager), add it as a new Custom HTML tag set to fire on All Pages. 5. Save your changes and allow up to 15 minutes for the pixel to register as active in Search Atlas. Tip: Use a browser extension such as Tag Assistant or PixelMe to confirm the pixel fires on page load before returning to Search Atlas to verify the status. 🔗 Step 2 – Resolve Permalink Issues Permalink mismatches can prevent OTTO from correctly mapping optimizations to the right pages. This typically happens after a site migration, a WordPress permalink settings change, or a URL restructure. 1. Confirm that the URL structure in Search Atlas matches the live URL structure on your website exactly — including trailing slashes, www vs. non-www, and http vs. https. 2. If you use WordPress, go to Settings → Permalinks in your WordPress dashboard and click Save Changes without making any edits. This flushes the rewrite rules and often resolves broken permalink mapping. 3. Return to OTTO SEO V3 in Search Atlas and trigger a Re-crawl or Resync of your site so OTTO picks up the updated URL structure. 4. Check that no redirect chains exist on the affected URLs. A page that redirects (301 or 302) to another URL will break the direct OTTO–page association. Important: If you recently changed your domain or moved to HTTPS, update your site URL inside Search Atlas settings before re-syncing. 🚀 Step 3 – Troubleshoot Landing Page Publishing Failures If a landing page you configured through OTTO did not publish, one of the following issues is usually responsible. - Pixel not active: OTTO cannot publish pages to a site where the pixel is unverified. Complete Steps 1 and 2 above first. - Insufficient site permissions: The integration connecting Search Atlas to your CMS must have editor or administrator level permissions. Check your CMS user roles and update if needed. - Conflicting plugins or firewall rules: Security plugins (e.g., Wordfence) and WAFs can block external publishing requests. Temporarily disable them to test, then whitelist Search Atlas IP ranges if publishing succeeds. - Permalink conflict on the target slug: If a page or post already exists at the target URL slug, the new landing page may fail silently. Choose a unique slug or delete the conflicting page first. - Unsaved page configuration: Ensure you clicked Publish (not just Save Draft) inside the OTTO landing page builder before expecting the page to go live. ✅ Step 4 – Confirm Everything Is Working 1. Open your website in an incognito browser window and navigate to the published landing page URL. 2. Verify the page loads correctly and displays the content you configured. 3. Return to OTTO SEO V3 in Search Atlas and confirm the landing page status shows as Published and the pixel status shows as Active. 4. If OTTO optimizations were pending, check that they now show a Deployed status rather than Pending or Failed. 💡 Common Mistakes to Avoid - Installing the pixel inside the <body> tag instead of the <head> tag. - Only adding the pixel to the homepage instead of all pages site-wide. - Forgetting to re-save WordPress permalink settings after a URL structure change. - Using a CMS integration account with read-only permissions. 🆘 Still Need Help? If you have followed all the steps above and the pixel, permalink, or publishing issue persists, our team can investigate your specific site 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 'Domain Already Registered' Error in Website Studio

🔍 What This Error Means When you try to connect a custom domain (for example, expressbailbonds.com) to a new Website Studio project, you may see a "Domain already registered" error. This typically happens when the domain was previously connected to another project that has since been deleted. Even after the old project is removed, the domain can remain linked in the background — an orphaned record — which blocks you from using it again. Follow the steps below to try to resolve this before contacting support. ⚙️ Step 1: Remove the Domain From Any Existing Project Before connecting your domain to a new project, check whether it is still assigned to an older or inactive project. 1. Go to Left sidebar → Website Studio. 2. Open each existing project and look for domain or settings options. 3. If your domain appears linked to a project you no longer need, navigate to that project's settings and remove or replace the domain there. 4. Save your changes before moving on. If you do not see the domain attached to any active project, the record may be orphaned and invisible to you — skip to Step 3. 🚀 Step 2: Reconnect the Domain to Your New Project Once you have removed the domain from the old project, try adding it to your new project. 1. In Left sidebar → Website Studio, open the project you want to use as your new website. 2. Navigate to that project's settings or domain configuration area. 3. Enter your custom domain and save. If the error is gone, your domain is now successfully connected. If the "Domain already registered" error still appears after completing Step 1, proceed to Step 3. 💡 Step 3: If the Error Persists — Contact Support In some cases, the domain record is stored at a deeper system level and cannot be cleared by the steps above. This is the orphaned-record scenario. If you still see the error after following Steps 1 and 2: - The issue is not caused by anything on your end. - A support teammate can investigate and manually remove the orphaned record on your behalf. 🛠️ When to Contact Support Reach out if: - The error appears even though the domain is not attached to any visible project. - You removed the domain from an old project but the error persists after trying again. - You are unable to locate a settings or domain area inside your project. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected to our support team.

🛠️ Fix Deleted Pages and 404 Errors in Website Studio

🔍 Overview Some Website Studio users have reported that pages were unexpectedly deleted from their site, resulting in 404 errors for visitors. This article explains why this can happen, what steps to take immediately, and how to prevent it in the future. ⚠️ Why Pages May Disappear Page deletions in Website Studio can occur due to the following reasons: - Accidental deletion: A team member may have removed a page using the delete action inside Website Studio without realising its impact on live traffic. - Known platform issue (now resolved): A previous bug caused pages to be silently removed from Website Studio projects without a visible error or confirmation. This issue has been fixed in a recent platform update. If your pages disappeared unexpectedly without any delete action being taken, this bug may be responsible. - Sync desync between the CMS and Website Studio: In some cases, a disconnect between the backend and Website Studio caused pages to stop appearing in your project, even though no deletion was intended. 🚨 What to Do If Pages Are Showing 404 Errors If your pages are returning 404 errors, act quickly to minimise impact on SEO and user experience. Follow these steps: 1. Check your Website Studio project: Go to Website Studio in the left sidebar and open your project. Confirm whether the affected pages are missing from the page list or simply unpublished. 2. Check for unpublished drafts: The pages may still exist as drafts. Look for them in your page list with a Draft or Unpublished status and republish them. 3. Review your team activity: Go to the top-right corner avatar → Team Members to see who has access to your project. Consider whether any recent activity by a team member could have caused the deletion. 4. Contact support for backend restoration: If the pages are completely missing and cannot be found in drafts, a backend restore may be required. 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. Provide the affected page URLs, your project name, and the approximate date the pages went missing so our team can prioritise the restore. 🔁 How Page Restoration Works When pages are lost due to a platform-side issue, our engineering team can perform a backend restore to recover the content. Important things to know about this process: - Restoration is handled directly by our technical team and is not a self-service action. - The sooner you report the issue, the better the chance of a full recovery. - You will be notified once the restore is complete and your pages are live again. 🛡️ How to Prevent Accidental Page Deletion To reduce the risk of losing pages in the future, follow these best practices: - Limit team permissions: Only grant Admin-level access to team members who need to manage or delete pages. Go to the top-right corner avatar → Team Members to review and adjust roles. - Always confirm before deleting: The delete modal in Website Studio requires confirmation. Read the prompt carefully before proceeding — deleted pages may not be recoverable without a backend restore. - Keep a record of important page URLs: Maintain a simple list of your highest-traffic pages. This makes it faster to identify and report any missing content. - Monitor for 404 errors regularly: Use Search Atlas reporting tools to track crawl errors and catch 404 issues early before they affect your rankings. 💬 Still Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Website Studio Blank Live Site Errors

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

Hero Overlay Opacity Not Updating in Website Studio

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

🛠️ Website Studio Scroll Bug and Credit Reset

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

↩️ Restore a Website Studio Project Version

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

🛠️ Troubleshooting Your Website Studio Coming Soon Page

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

🛠️ Website Studio File Upload Fields Now Working

🔍 Overview A confirmed bug previously caused file upload fields in Website Studio forms to silently fail. Even when a visitor successfully selected and submitted a file — such as a logo or image — the submitted value was stored as empty, meaning the file could not be retrieved from the form submission data. This issue has been investigated, escalated to engineering, and fully resolved. File uploads through Website Studio forms now save and store correctly. ⚙️ What Was Happening When a Website Studio form included a file upload field, the form appeared to accept the file on the visitor's end. However, the file data was silently dropped during processing. The form submission record stored an empty value instead of the uploaded file, making it impossible to access or download the file after submission. This affected any Website Studio form with a file upload field, regardless of the file type being submitted. ✅ Current Status — Issue Resolved Engineering identified the root cause and shipped a fix. The file upload functionality in Website Studio forms now works as expected. Customers have confirmed that common image formats such as JPG and PNG upload and save successfully. If you set up a form with a file upload field, submitted files will now be captured and stored correctly in your form submission data. 🧪 How to Verify File Uploads Are Working 1. Open Website Studio and navigate to your website projects. 2. Open the website project that contains the form with a file upload field. 3. Submit a test entry through the form, attaching a file (JPG or PNG are confirmed to work). 4. Check your form submission data for that project to confirm the file value is no longer empty and the uploaded file is accessible. 💡 If You Still See Empty File Values If you submitted files before the fix was deployed, those earlier submissions were affected by the bug and the file data cannot be recovered — the files were not stored at the time of submission. For any submissions made after the fix, file uploads should now save correctly. If you are still experiencing missing file data on new submissions after testing, follow the steps below: - Confirm the form field is set up as a file upload type and not another input type. - Try submitting again using a supported image format such as JPG or PNG. - Check the form submission record again after the new test submission. If the problem persists on new submissions, this may indicate a separate issue that needs investigation. 🆘 Need Further Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🌐 Fix Domain Blocked by Old DNS Records

🔍 What Is Causing This Error? When you try to connect a registered domain to Search Atlas and receive an error indicating that the domain is already in use or cannot be connected, the most common cause is a leftover DNS record from a previous Website Studio project. Even if that project has been deleted or is no longer active, its DNS entry can remain and block any new domain connection attempts. This is not an issue with your domain registrar or your DNS provider. The conflict exists inside Search Atlas, where an old Website Studio record is still associated with that domain. ⚠️ How to Confirm This Is Your Issue You are likely experiencing this problem if all of the following are true: - Your domain is fully registered and active with your domain registrar. - You are attempting to connect the domain inside Search Atlas and receive an error indicating the domain is already claimed or in use. - You do not see any active project in Website Studio currently using that domain. - The domain was previously used in a Website Studio project that has since been removed or is no longer active. 🛠️ What to Do Because this conflict involves an internal DNS record that may have been orphaned when a previous Website Studio project was deleted, it typically cannot be resolved through self-serve steps alone. The Search Atlas support team will need to manually remove the conflicting record on your behalf. To help the team resolve this as quickly as possible, please have the following ready before reaching out: - The exact domain name that is blocked (e.g., example.com). - The name of any Website Studio project you believe previously used this domain, if known. - The error message text you are seeing when attempting to connect the domain. - The date and approximate time you first encountered the error. - Your Search Atlas workspace name or account email. 🧹 Why Orphaned DNS Records Happen An orphaned DNS record is created when a Website Studio project is removed without first disconnecting the custom domain assignment. Search Atlas retains the DNS mapping as a safeguard, but this can prevent you from reusing or reassigning the domain later. ✅ How to Prevent This in the Future - Before deleting any Website Studio project, always disconnect your custom domain from the project first, then proceed with deleting the project. - Confirm the domain no longer shows as connected before completing the deletion. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Website Studio AI Creating Wrong Pages or 404 Errors

🔍 What Is This Issue? Some customers have reported that the Website Studio AI assistant creates unexpected pages — such as blog posts or website analysis pages — instead of carrying out the requested action (for example, updating a CTA link). This can result in 404 errors and unnecessary credit usage each time you attempt to correct the behaviour. This is a known issue where the Website Studio AI assistant hallucinates, generating unintended pages rather than performing the action you specified. If you are experiencing this behaviour, the steps below will help you address it. ✅ What You Should Do Right Now If you are seeing unexpected pages being created or 404 errors in Website Studio, follow these steps: 1. Clear your browser cache and cookies. Outdated cached data can sometimes cause the platform to behave unexpectedly. 2. Try again in a private or incognito window. This rules out any browser extension or cached session interfering with the AI assistant. 3. Return to Website Studio and retry your original instruction. Be as specific as possible in your request to help the assistant interpret it correctly. 4. Delete any unwanted pages that were incorrectly created. Navigate to your project in Website Studio and remove the pages that were generated in error. 💳 Credits Used Due to This Issue If the AI assistant consumed credits while malfunctioning — for example, by repeatedly creating wrong pages as you tried to fix the issue — you may be eligible for a credit refund as a courtesy. To request a credit review, please reach out to our support team. Describe the dates and actions affected so the team can review your account accurately. ⚙️ If the Problem Continues If you continue to see the AI assistant creating wrong pages or ignoring your instructions, please gather the following information before contacting support: - Note the exact instruction you gave the assistant and what it did instead. - Record approximately when the behaviour occurred (date and time). - Note whether any new pages were created and what type they were labelled as (blog, landing page, etc.). Having this information ready will help the support team investigate quickly and escalate to engineering if needed. If you need further assistance, please don't hesitate to reach out to our support team so we can look into your specific case.

🛠️ Fix AI Changes Not Saving in Website Studio

🔍 Overview Some customers find that after asking the Website Studio AI assistant to make changes — such as removing a dark overlay, updating text, or adding an image — the assistant confirms the edit is done, but the website does not reflect the change. This article explains why this happens and how to get your changes to apply correctly. ⚠️ Why This Happens The Website Studio AI assistant processes your requests in real time, but there are known scenarios where confirmed changes may not persist. The AI assistant may confirm a change — such as removing a dark overlay — without that change being reliably written to the page. ✅ How to Apply Changes Reliably 1. Send one instruction at a time. Break complex edits into separate, focused prompts. For example, first ask to remove the dark overlay and confirm it is applied before moving on to the next change. 2. Verify each change visually before continuing. After the AI confirms an edit, check the canvas directly. Do not rely solely on the assistant's confirmation message. 3. Refresh the editor if changes are not visible. If the canvas does not update after a confirmed edit, save your work, refresh the page, and reopen the project in Website Studio. 🎨 Removing a Dark Overlay Specifically Dark overlays are a common styling element applied to hero sections and background images. If you have asked the AI to remove an overlay and it is still visible, try the following: - Ask the AI explicitly: "Remove the dark background overlay from the hero section. Do not make any other changes." - After the AI confirms, scroll to the section on the canvas and check whether the overlay is gone. - If it is still present, refresh the editor and repeat the single focused prompt. 📞 Still Need Help? If the overlay or other AI-confirmed changes are still not persisting after following the steps above, please escalate to our support team. Have the following ready: your project name, the exact prompt you sent to the AI assistant, and a description of what the canvas shows after the AI confirms the change. 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.

🛠️ Blog Posts Showing 404 or NoSuchKey Errors in Website Studio

🔍 What This Issue Looks Like After publishing blog posts in Website Studio — especially if your domain DNS was misconfigured at any point during publishing — your live blog URLs may return one of the following errors: - A 404 page (page not found) - A raw NoSuchKey XML error displayed in the browser These errors can persist even after the DNS issue has been corrected, and re-publishing or editing the posts may not resolve them. ⚙️ Why This Happens This issue is caused by a platform-side sync failure in Website Studio. When a blog post is published under certain conditions — such as during or shortly after a DNS misconfiguration — the article can fail to sync correctly to the Website Studio delivery layer. The post appears published inside the platform but is not properly served on the live site. ✅ Steps to Resolve 1. Confirm your DNS is fully propagated. Before attempting to fix the blog posts, make sure your domain's DNS settings are correctly configured and fully propagated. You can use a free tool like whatsmydns.net to verify your domain is resolving correctly worldwide. 2. Re-publish the affected blog posts. Open Website Studio and navigate to the blog post that is returning the error. Re-save or re-publish the post so the platform can attempt a fresh sync to the delivery layer. 3. Check the live URL again. After re-publishing, wait a few minutes and then reload the blog post URL in your browser. Clear your browser cache or test in an incognito window to rule out a cached error page. 4. Test multiple posts if needed. If you have several affected blog posts, repeat step 2 for each one individually. 📋 What to Expect Going Forward Once the posts are successfully re-published, they will serve correctly on your domain. New blog posts published through Website Studio will also publish correctly without requiring any extra steps. 🚨 If Posts Are Still Returning Errors If you have re-published your posts and the 404 or NoSuchKey errors continue, this may indicate that the sync issue is still affecting your specific project and needs to be reviewed by our team directly. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team. When you reach out, please include: - Your domain name - The URLs of the specific blog posts returning errors

🛠️ Fix Duplicate H1 Tags in Website Studio

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

🛠️ Website Studio Build Errors and Credit Top-Up Issues

🔍 Overview Some customers have experienced a combination of issues in Website Studio: repeated Build failed errors, a stalled or spinning checkout when purchasing credit top-ups, and credit quotas that appeared incorrect or failed to refresh on schedule. These issues have been investigated and resolved. This article explains what to do if you are still seeing any of these symptoms. ⚙️ What Was Causing These Issues Engineering identified and resolved bugs related to Website Studio build errors and credit top-up purchase failures. The underlying issues affecting builds and the credit top-up purchase flow have been addressed in production. ✅ Steps to Take If You Are Still Affected 1. Refresh your browser and clear your cache. After a production fix goes live, a hard refresh ensures you are loading the latest version of the platform. 2. Check your current quota. Navigate to the top-right avatar → Billing → Plans & Top-ups in your account and review your available credits to confirm they reflect the correct values. 3. Retry the build. If you previously encountered a Build failed error, attempt the build again. With the underlying issues resolved, builds should complete successfully. 4. Retry a top-up purchase if needed. If you need to purchase additional Website Studio credits, navigate to the billing section of your account and attempt the purchase again. The issues affecting the credit top-up checkout flow have been resolved in production. 5. Contact support if problems persist. If you are still experiencing build failures, checkout issues, or incorrect credit balances after following the steps above, please reach out to our support team via the chat widget so we can investigate your account directly. 📊 Understanding Your Credit Quota If your credit quota still appears incorrect or your builds continue to fail after trying the steps above, this may require account-level investigation. Please contact our support team via the chat widget with details of the issue — including any error messages you see and the date the problem started — so we can review your account and ensure your quota and billing are accurate.

💡 Fix Website Studio Credit Balance Errors Explained

🔍 Overview Seeing a "credit balance too low" error in Website Studio can be confusing — especially when your Hyperdrive Credits dashboard shows a healthy balance. This article explains exactly which credits Website Studio uses, how they are consumed, and what to do when you hit a quota error. ⚙️ How to Access Website Studio 1. Log in to your Search Atlas account. 2. Click Website Studio in the left sidebar. 3. Your website projects will appear at /website-studio. 💳 Which Credits Does Website Studio Use? Website Studio operates on a separate credit type called LPS (Landing Page Studio) Credits — not Hyperdrive Credits. This is the most common source of confusion when the error appears. - LPS Credits power all core Website Studio actions, including page generation, publishing, and AI-assisted builds. - Hyperdrive Credits are used by other tools across the platform (such as Content Genius writing tasks, keyword research, and bulk AI features). - Having a large Hyperdrive Credit balance does not cover Website Studio usage. The two pools are independent. In short: if Website Studio shows a credit error, check your LPS Credit balance, not your Hyperdrive Credit balance. ✏️ Does Every Content Genius Edit in Website Studio Cost Credits? Not every action triggers a credit deduction. Here is a breakdown of what does and does not consume credits inside Website Studio: - Credits are consumed when you use AI-powered generation features — for example, generating a new page, regenerating a section with AI, or using Content Genius to rewrite or create content blocks within a page. - Credits are consumed for manual/visual edits in the editor, in addition to AI-powered generation. - Credits are not consumed for saving drafts or previewing your pages. Each AI-assisted generation or rewrite inside the editor counts as one credit action. If you are making many iterative AI edits in a single session, your LPS Credits can deplete faster than expected. 🛠️ How to Resolve the "Credit Balance Too Low" Error 1. Navigate to your account Settings and open the Subscription or Usage section. 2. Check your current LPS Credit balance — not Hyperdrive Credits. 3. If your LPS Credits are at zero or near zero, you will need to wait for your monthly quota to reset or upgrade your plan to increase your LPS Credit allowance. 4. If your LPS Credit balance appears healthy but the error persists, try refreshing the page and clearing your browser cache before attempting the action again. 5. If the error continues after confirming you have available LPS Credits, reach out to our support team (see below). 📊 Tips for Managing Your LPS Credit Quota - Plan AI edits in batches: Instead of regenerating individual sections repeatedly, finalise your content direction first and run one generation pass. - Use manual editing for small tweaks: Typos, colour changes, and layout adjustments do not cost credits — save AI generation for substantive content tasks. - Monitor usage regularly: Check your LPS Credit balance in Settings before starting large website build sessions. - Consider a plan upgrade: If you consistently hit your quota limit, a higher-tier plan will give you a larger monthly LPS Credit allowance. ❓ Frequently Asked Questions Why do I see a credit error when I have 2,423 Hyperdrive Credits? Hyperdrive Credits and LPS Credits are separate pools. Website Studio only draws from LPS Credits. A high Hyperdrive Credit balance has no effect on your Website Studio quota. Do unused LPS Credits roll over each month? Credit rollover depends on your specific plan. Check your subscription details in Settings for rollover policy information. Can I transfer Hyperdrive Credits to LPS Credits? Credits cannot be transferred between pools at this time. Each credit type is allocated independently based on your plan. 🆘 Still Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Fix Site Analysis Lead Capture Widget Issues

🔍 Overview The Site Analysis Lead Capture Widget is a tool that lets your agency collect prospective client information directly from your white-label site analysis page. If leads are not appearing in your Leads section, notification emails are not working, or there is no call-to-action (CTA) on the summary page or outgoing emails, this article explains what to check. ⚙️ Step 1: Access the Lead Capture Widget Settings Navigate to the Site Analysis Lead Capture Widget settings via More Features → Agency Hub (Agency Settings). This is where all lead capture configuration lives. Any missing or incorrect settings here will cause the issues described above. 📋 Step 2: Verify the Widget Is Enabled Inside the Lead Capture Widget settings, confirm that the widget itself is toggled on. If the widget is disabled, no lead data will be collected, regardless of how your other settings are configured. Save any changes before moving to the next step. 📨 Step 3: Fix Missing Notification Emails If you are not receiving alerts when a new lead is captured, check the following: - Notification email address: Make sure a valid email address is entered in the notification field. If this field is empty or contains a typo, no alerts will be sent. - Email toggle: Confirm the email notification toggle is switched on. The toggle and the email field must both be active for notifications to fire. - Spam or junk folder: Check your spam or junk folder in case notification emails are being filtered by your email provider. After updating the email address or toggling the setting on, save your changes to apply them. 💡 Step 4: Add a CTA to the Summary Page and Emails A missing call-to-action on the summary page or in emails sent to prospects is almost always caused by incomplete white-label branding settings. Follow these steps: 1. In the Site Analysis Lead Capture Widget settings, locate the CTA configuration section. 2. Enter the text you want to display on the CTA button — for example, Contact Us or Get a Free Consultation. 3. Add the destination URL or contact link you want prospects to use when they click the button. This is typically your agency website, a contact form, or a booking page. 4. Confirm the CTA toggle is enabled so the button appears on both the summary page and in outgoing emails. 5. Save your changes. Without a destination URL and button label entered and the CTA toggle enabled, the button will not appear for your prospects. 🚨 Still Experiencing Issues? If leads are still not being captured or your CTA is still missing after verifying all settings above, our support team can investigate further on the backend. When reaching out, please have the following ready: your agency account details, the specific lead capture behavior you are seeing, and any relevant screenshots. 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 Publishing Failure No Target Element

What Is This Error? When you publish a project in Website Studio and the live site appears blank — even though the preview looks correct — the underlying cause is usually a "no target element specified" error. This is a build-time failure that prevents the page from rendering correctly in a browser. It can affect any device and will not resolve itself with a simple refresh. This error requires investigation and correction by the Search Atlas support team on the backend. This article explains what to expect and what information to have ready when you reach out. Why This Happens The error occurs when the publishing build process encounters a failure that prevents your page content from rendering on the live URL. The preview environment loads content differently from the live build, which is why the page can appear correct in preview but fail entirely once published. Because this is a build-level failure, it cannot be resolved by refreshing the page or republishing without backend intervention. What to Expect Once you contact support, a member of our team will investigate the build error associated with your project on the backend. Resolution typically involves correcting the broken build state so your project can be published successfully. You do not need to delete your project or recreate your content. What to Have Ready When You Escalate To help our team resolve this as quickly as possible, please have the following information available before reaching out: - The exact name of the affected Website Studio project - The published URL that is appearing blank - The approximate date and time you first noticed the blank live site - Any error message text you can see, copied exactly as displayed - A note on whether the preview still appears correct or is also affected If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Common Website Studio Bugs Quickly

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

Website Studio Defects and Credit Restoration Guide

Overview Some customers have encountered a cluster of issues in Website Studio, including unexpected menu changes, content loss after reverting, excessive or duplicate credit consumption, sitemap errors, and blog images not displaying. This article explains what to do if you've been affected and how to escalate for a credit restoration review. Known Issues Our engineering team has investigated and actioned several related defects in Website Studio. If you are experiencing symptoms such as duplicate credit charges, credits not being returned after a failed or cancelled generation, content being overwritten, or other unexpected behaviour in Website Studio, your account may have been impacted. If you are unsure whether your account was affected, our support team can review this for you during escalation. What to Do If Your Content Was Overwritten or Reverted If a revert action or sync error caused content loss, follow these steps before requesting assistance: 1. Stop editing the affected page immediately to prevent further overwrites. 2. Take a screenshot or screen recording of the current state of the affected pages, including any visible errors. 3. Note the date and approximate time when the issue first occurred. 4. Check your saved content sources to confirm whether the correct content is still available — this will be your recovery reference. 5. Do not manually re-enter content or trigger another generation until our team has reviewed the issue, as this may consume additional credits. How to Check Your Credit Activity To verify your credit balance and review recent charges, check the billing or account area of the platform where credit usage is displayed. If you notice any unexpected charges — such as credits consumed for actions you did not intentionally trigger — take screenshots of those entries before contacting support. Documenting the specific charges you believe are incorrect will help our team process your credit restoration request more quickly. What to Have Ready When You Escalate Because credit restoration requires a backend review by our team, please gather the following before reaching out: - Your project or website name in Website Studio - The approximate date and time the issue occurred - Screenshots of any duplicate or unexpected credit charges - A description of the action you were performing when the issue occurred (e.g. generating a page, reverting content, making a layout edit) - Any error messages you received, including the exact wording Having this information ready will allow our team to locate your account activity and process the restoration without additional back-and-forth. 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 www Subdomain SSL and Routing Errors in Website Studio

What This Article Covers If your website's www subdomain (e.g., www.yourdomain.com) is not working correctly or showing errors, the cause is often related to how the www subdomain is configured in your DNS settings. This article walks you through how to set up your www subdomain properly in Website Studio. Why This Happens When you set up a custom domain in Website Studio, the root domain (e.g., yourdomain.com) and the www subdomain (e.g., www.yourdomain.com) need to be configured separately in your DNS. If the www subdomain is not set up correctly, SSL and routing issues can occur. How to Fix It — Update Your DNS Records You will need access to your domain registrar or DNS provider (for example, GoDaddy, Cloudflare, Namecheap, or similar). Follow these steps: 1. Log in to your DNS provider and navigate to the DNS management section for your domain. 2. Check your existing DNS records for www. Look for a record with the Name (or Host) set to www. 3. Add or update a CNAME record with the following values: - Type: CNAME - Name / Host: www - Value / Target / Points to / Alias (these are all the same field, just labelled differently by each DNS provider): the preview URL provided by Website Studio when you connected your custom domain 4. Save the record. DNS changes can take anywhere from a few minutes to 48 hours to propagate globally, though many users see the fix take effect almost immediately. Where to Find Your Website Studio Preview URL Your unique preview URL was provided when you connected your custom domain in Website Studio. If you no longer have it, please contact our support team and we will retrieve it for you. What to Check If the Issue Persists After DNS Update After updating your DNS records, keep the following in mind: - Allow time for propagation. Most changes resolve within minutes, but full global propagation can take up to 48 hours. - Clear your browser cache and try loading the www URL in a private/incognito window to rule out cached content.

🛠️ Brand Vault Bulk Image Upload Scroll Bug

🔍 What Is This Issue? When uploading a large batch of images to Brand Vault, some users encounter a scroll glitch inside the upload modal. The confirmation button becomes pushed off-screen and cannot be reached by scrolling, making it impossible to complete the upload in one go. This issue was previously reported and partially addressed, but some users may still experience it depending on the number of images selected and their browser environment. ⚙️ Temporary Workaround: Upload in Smaller Batches While a permanent fix is being rolled out, the most reliable way to complete your upload is to reduce the number of images you select at one time. Follow these steps: 1. Navigate to Brand Vault: top-right More Features menu (apps-grid icon) → Brand Vault. 2. Instead of selecting all images at once, choose a smaller subset — for example, 5 to 10 images per upload. 3. Complete the upload for that batch, confirming it successfully before moving on. 4. Repeat the process for the remaining images until all files have been uploaded. Uploading in limited batches keeps the upload modal at a manageable size, ensuring the confirmation button stays visible and accessible on-screen. ✅ Fix Status: Resolved in a Recent Release This bug was escalated to the engineering team and tracked through the full development cycle. The root cause — the upload button being pushed off-screen when a large number of images were selected — has been addressed. An inline scrollbar was added to the images section of the upload modal to prevent the button from becoming inaccessible. If you have already updated or refreshed the platform and are still experiencing the issue, the batch-upload workaround above remains effective in the meantime. 💡 Tips to Avoid This Issue - Use a supported browser: Make sure your browser is up to date. Older browser versions can affect how modals render and scroll. - Clear your cache: If the platform was recently updated, a hard refresh (Ctrl + Shift + R on Windows, Cmd + Shift + R on Mac) can ensure you are loading the latest version. - Keep batches manageable: Even after the fix is fully released, uploading in moderate batches is a good general practice to avoid performance slowdowns during bulk operations. 🆘 Still Experiencing the Issue? If the scroll problem persists after trying the workaround above and refreshing the platform, please collect a short screen recording that shows the issue. This will help the support team reproduce and resolve it quickly. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🖼️ Fix Brand Vault Images Saving as Web Files

🔍 What's Happening When you upload JPEG images to Brand Vault, they may save as web files (such as WEBP) instead of retaining their original JPEG format. This can cause errors when you try to use these images in other parts of Search Atlas, such as when publishing to Google Business Profile or other integrations that require standard image formats. This issue has been identified and resolved by our engineering team. If you're experiencing this problem, the fix has been deployed to the platform. ✅ How to Resolve This Step 1: Verify the Fix The issue with images uploading as web files instead of JPEG in Brand Vault has been fixed. If you recently experienced this problem, try uploading your JPEG images again to Brand Vault. They should now save in the correct format. Step 2: Re-upload Your Images 1. Navigate to Brand Vault via the header apps-grid icon → More Features → Brand Vault. 2. Upload your JPEG image files again. 3. Verify that the images now display and save as JPEG files rather than web files. 4. Proceed with publishing or using these images in your campaigns without errors. Step 3: Confirm Compatibility Once re-uploaded, your images should work seamlessly with integrations like Google Business Profile and other features that require standard image formats. If you encounter any errors when using these images, proceed to the next section. ⚠️ If the Issue Persists If you continue to see images saving as web files after re-uploading, this may indicate a different underlying issue with your account or browser. Try These Steps: - Clear your browser cache and cookies, then log back into Search Atlas. - Use a different web browser to upload your images and confirm whether the issue is browser-specific. - Ensure your image files are authentic JPEGs (check the file extension and properties on your system). - Try uploading a different JPEG image to see if the problem occurs with all uploads or only specific files. 🆘 Get Help From Our Team If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team. When you reach out, mention that you're experiencing issues with Brand Vault images saving as web files, and let them know you've already tried re-uploading your images. This will help them assist you more quickly.

🛠️ Fix Website Studio Generation Failed Build Error

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

🐛 Fix Website Studio 404 Errors and Loading Failures

🔍 Overview If your Website Studio projects are not loading in the editor, or if pages on your published site are returning a 404 "page does not exist" error, our team is aware of these issues and is working to investigate them. This article explains what to do and what information to have ready when contacting support. ⚠️ Common Symptoms - Projects fail to open in the Website Studio editor. - Published pages return a 404 error. - Newly published pages do not display correctly after publishing. - Client projects do not load inside the project editor. 🧠 Why This Happens Website Studio 404 errors and project loading failures are known issues that may affect some users. Because these issues occur at the platform level, they typically cannot be resolved through account-side changes alone and require investigation by our support team. 🛠️ What to Do 1. Note the details of the issue. Before contacting support, gather the following information so our team can investigate as quickly as possible: - The name of the affected project or projects. - The exact error message you are seeing (e.g., the full 404 error text). - The URL or URLs of the affected pages. - The approximate date and time when the issue started. - Whether the issue affects one project or multiple projects. 2. Do not make additional changes to the affected projects while the issue is ongoing, as this may complicate investigation. 3. Contact our support team with the information above so we can look into the root cause and apply the appropriate fix on our end. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Website Studio Pages Show Only Header and Footer

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

🛠️ Fix Blank Pages and Sync Errors in Website Studio

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

🛠️ Fix Website Studio Site Cap Plan Mismatch

🔍 Overview If you upgraded to a Platinum plan expecting unlimited Website Studio sites but are still hitting a lower cap (such as 60 sites), your account quota may not have updated correctly after the plan change. This article explains why this happens and what steps to take to get it resolved. 📋 What You Should Expect by Plan Each Search Atlas plan includes a set Website Studio site allowance: - Starter: Limited site cap (typically lower tier) - Pro: Higher site cap (e.g., up to 60 sites) - Platinum: Unlimited Website Studio sites If your dashboard shows a cap that does not match your current plan, this is a quota sync issue — not a missing feature on your plan. ⚠️ Common Causes of a Plan Mismatch - Your plan was upgraded but the site quota was not automatically updated on the backend. - Your billing reflects the new plan (e.g., Platinum yearly), but the system is still enforcing the previous plan's limits. - A mid-cycle plan change caused the quota allocation to carry over from the old plan. ✅ How to Confirm You Have a Plan Mismatch 1. Go to Website Studio using the left sidebar (or navigate to /website-studio). 2. Check the site count or any cap warning displayed in the interface. 3. Compare that limit against what your current plan should provide (see the plan table above). 4. Log out and log back in to rule out a browser or session cache issue. 5. If the cap remains incorrect after logging back in, the issue is a backend quota sync problem. 🛠️ Steps to Try Before Contacting Support 1. Refresh your session: Log out of Search Atlas completely, clear your browser cache, and log back in. 2. Check your billing status: Confirm your Platinum plan is active and not in a grace period or pending state. 3. Try a different browser: Rule out browser-specific display issues by testing in an alternative browser or incognito window. 4. Wait up to 15 minutes: Quota updates can occasionally take a short time to propagate after a plan change. If none of the above steps resolve the issue, your account requires a manual quota correction by our team. 💬 How to Get This Fixed A quota sync issue cannot be self-resolved from within the platform — our team needs to apply the correct credit allocation to your account. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team. To help us resolve this as quickly as possible, please have the following information ready: - Your account email address - Your current plan name and billing cycle (e.g., Platinum yearly) - The site cap you are currently seeing in Website Studio - The date you upgraded or changed your plan 🔄 What Happens After the Fix Once our team corrects the quota allocation on your account, your Website Studio site limit will update to reflect your Platinum plan entitlement. You will not lose any sites you have already created, and you will be able to add new sites immediately after the fix is applied.

🛠️ Fix Persistent Dark Overlays in Website Studio Sections

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

🛠️ Fix Website Studio Editor Not Loading

🔍 What Is This Issue? Some customers have reported that clicking into a Website Studio project loads the left sidebar but fails to render the main editor. The page may appear blank, white, or frozen — with no content visible beyond the sidebar. In some cases, no network requests fire at all, meaning the editor never fully initialises. This issue has been identified and investigated by the Search Atlas engineering team. If you are still experiencing this behaviour, the steps below will help you recover access. 🧭 How to Get to Website Studio Before troubleshooting, confirm you are navigating to the correct location: 1. Log in to your Search Atlas account. 2. In the left sidebar, click Website Studio. 3. Select the project you want to open. The URL should contain /website-studio. ⚙️ Steps to Fix the Editor Not Loading Work through the steps below in order, testing the editor after each one before moving to the next. 1. Hard-refresh the page. Press Ctrl + Shift + R (Windows/Linux) or Cmd + Shift + R (Mac) to clear cached assets and force a full reload. 2. Clear your browser cache and cookies. Stale cached files are a common cause of the editor failing to initialise. Clear cache for the past 24 hours, then reload the page. 3. Try an incognito or private window. Open a new incognito window, log in to Search Atlas, and navigate to your Website Studio project. This rules out browser extensions or local storage conflicts. 4. Switch browsers. If the editor still fails to load, try a different browser (for example, Chrome, Firefox, or Edge). This confirms whether the issue is browser-specific. 5. Disable browser extensions. Ad blockers, script blockers, or privacy extensions can prevent API calls from firing. Temporarily disable all extensions and reload the editor. 6. Check your internet connection. A slow or unstable connection can cause the editor to stall mid-load. Test on a different network if possible. 7. Wait a few minutes and try again. If a platform update was recently deployed, a brief delay before retrying can be enough for the environment to stabilise. 📋 If the Issue Persists — What to Have Ready If the editor still fails to load past the sidebar after completing all steps above, this may require investigation by the Search Atlas engineering team. Before reaching out, please collect the following information so our team can investigate as quickly as possible: - Project name — the exact name of the Website Studio project that fails to load. - Browser and version — for example, Chrome 124, Firefox 126, or Edge 123. - Operating system — for example, Windows 11 or macOS Ventura. - Exact behaviour observed — describe what you see (e.g. blank white screen past the sidebar, page freezes, no content loads). - Timestamp — the date and approximate time (including your timezone) when the issue occurred. - Whether the issue occurs in incognito or a different browser — this helps isolate the cause. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🐛 Fix Blog Preview Images and Page Navigation in Website Studio

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

🔧 Fix URL Rewrite and Social Share Thumbnail Mismatch

Overview When sharing a Website Studio project URL on social media, the preview thumbnail may display an incorrect domain (for example, juicynote.com instead of thejuicynote.com). In some cases, this misconfiguration may also be associated with duplicate form submissions. Both issues are related to URL rewrite and domain configuration in your Website Studio project. What Causes This Issue A URL rewrite or custom domain mapping that is not applied consistently across your project can result in a mismatch between the domain visitors see in a social media thumbnail and the domain your project actually lives on. Social platforms read Open Graph (OG) metadata to generate thumbnails, and if that metadata still references an old or alternate domain, the wrong domain may appear in previews. Duplicate form submissions may also occur when more than one domain variant is active for the same project, though the exact mechanism can vary depending on your specific setup. What to Do Because the specific settings and steps needed to resolve URL rewrite and social share thumbnail issues depend on how your Website Studio project is configured, our support team will need to review your setup directly to identify the correct fix. When contacting support, please have the following ready: - The name of the affected Website Studio project - The domain or domains involved (e.g., the incorrect domain appearing in thumbnails and the correct intended domain) - Any error messages or unexpected behavior you have observed, including whether you are seeing duplicate form submissions - The URL you are sharing on social media and the platform(s) where the incorrect thumbnail appears - The approximate date and time the issue started If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔒 Fix SSL Certificate Errors on Landing Page Subdomains

🔍 Overview When you publish a landing page on a custom subdomain (for example, hailstorm.mdmland.com), Search Atlas needs the subdomain's DNS records to be correctly configured before an SSL certificate can be generated. If the DNS records are missing or pointed elsewhere, the certificate will fail to generate and visitors may see a security warning. This article explains what DNS change is required and how to get set up correctly. If you need the specific CNAME target value for your subdomain or guidance on where to find it in your account, please contact our support team as described below. 📋 Prerequisites - Access to your domain registrar or DNS provider (for example, GoDaddy, Cloudflare, Namecheap, or Route 53). - The exact subdomain you entered in Search Atlas when creating your landing page. - The Search Atlas CNAME target value for your landing page — contact our support team if you are unsure where to find this. 🛠️ Step-by-Step DNS Configuration 1. Log in to your DNS provider and navigate to the DNS management section for your root domain (for example, mdmland.com). 2. Create a new CNAME record using the following values: - Type: CNAME - Host / Name: the subdomain prefix only (for example, enter hailstorm, not the full domain) - Value / Points to: the CNAME target provided by Search Atlas for your landing page subdomain - TTL: set to the lowest value your provider allows, for faster propagation 3. Save the record and allow time for DNS propagation to complete. Propagation times vary depending on your DNS provider and your previous TTL settings. 4. Once propagation is complete, Search Atlas should be able to generate the SSL certificate for your subdomain. If the certificate does not appear after propagation, contact our support team with your subdomain name so we can investigate. ✅ How to Confirm Your DNS Is Set Up Correctly Before expecting the certificate to generate, confirm the CNAME record is live. You can use a free tool such as dnschecker.org — enter your full subdomain, select CNAME, and confirm it resolves to the Search Atlas target value. Once the CNAME is resolving correctly, reach out to support if the SSL certificate has not yet been issued. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔄 Website Studio Token Refunds for Failed Requests

🔍 Overview When you submit a request in Website Studio, the platform consumes tokens to process that request. If a request fails and produces no usable output, you may be eligible for a token refund. This article explains what to do if you believe tokens were consumed by a failed request. ⚙️ How Token Consumption Works in Website Studio Tokens are deducted when a generation request is submitted and processed. Under certain failure conditions — such as technical or platform-side errors — tokens may be deducted even when no output is delivered. ✅ How to Request a Token Refund Because token refunds require backend review, you will need to contact our support team directly. To help us resolve your case as quickly as possible, please have the following ready before reaching out: - The date and approximate time of the failed request - The action you attempted in Website Studio (e.g., what type of generation or modification you submitted) - Any error message displayed on screen, copied exactly - Confirmation that no output was created — check your Website Studio project list to verify that no page or project appeared as a result of the request Our team will review the request logs to confirm that a failure occurred and that no output was generated, and will process your refund accordingly. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Website Studio Duplication and AI Overlay Bugs

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

🗑️ How to Remove a Published Cloud Stack

🔍 Overview Once a Cloud Stack is published, it is live on external hosting infrastructure and cannot be deleted directly from the Search Atlas dashboard. However, if your published Cloud Stack contains incorrect images, inaccurate information, or content that misrepresents your client's company, you can request its removal through our support team. This article explains what a published Cloud Stack is, why self-service deletion is not available, and exactly how to get one removed quickly. 📋 What Is a Published Cloud Stack? A Cloud Stack is a set of interlinked web properties — such as Google Sites, Web 2.0 pages, and cloud documents — designed to build authority and pass link equity to your target website. Once published, these pages are hosted on third-party platforms outside of Search Atlas, which is why they cannot be unpublished with a single dashboard button. ⚠️ When Should You Request Removal? You should request removal of a published Cloud Stack if any of the following apply: - The Cloud Stack contains images that do not belong to your client's website or brand. - The content misrepresents your client's company, products, or services. - Incorrect business information (name, address, URL) was used during creation. - The Cloud Stack was created for the wrong website or client by mistake. 🛠️ How to Request Cloud Stack Removal Because published Cloud Stacks are hosted on external platforms, removal must be handled by our support team. To get a Cloud Stack removed as quickly as possible, have the following information ready before you reach out: - The name of the Cloud Stack to be removed. - The target URL the Cloud Stack was built for. - A brief reason for removal (e.g., incorrect images, misrepresentation of client). Once you contact support with these details, our team will process the removal and confirm once the Cloud Stack has been taken down from all associated platforms. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Website Studio Overlay & Credit Reset

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

📋 Fix Website Studio 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.

🛠️ Fix Website Builder Page Duplication and AI Editing Bugs

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

🛠️ Fix Website Studio Contact Page and Form Issues

Overview Some customers using Website Studio have reported two related issues: their contact page fails to load correctly, and contact form submissions are not being received at their chosen email address. These issues require investigation and a fix applied on the backend by our support team. This article explains what to expect and what information to have ready when you reach out. What Is Happening When a contact page does not load or form submissions stop arriving, the root cause is typically a backend configuration issue that cannot be resolved by changing settings inside the Website Studio editor. Our team will need to investigate your account and the underlying platform configuration to apply the correct fix. What to Have Ready Before Escalating To help our team resolve your issue as quickly as possible, please gather the following information before reaching out: - The exact name of the project or website affected in Website Studio. - The URL of the contact page that is not loading, if it is published. - The email address where form submission notifications should be arriving. - A description of when the issue started (approximate date and time, if known). - Any error messages you see when attempting to load the page or submit the form. What to Expect Once our team receives your report with the details above, they will investigate the backend configuration for your Website Studio contact page and form. You do not need to make any changes to your page settings while waiting — our team will confirm what action was taken and when your contact page and form submissions should be working again. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚡ Fix White Overlay Issues in Website Studio

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

🛠️ Fix Blog Posts Not Opening or Appearing

🔍 Overview If blog posts on your Website Studio site are not opening when clicked, or newly published posts are not appearing on the blog listing page, this is a known issue that requires investigation by our support team. This article explains what to expect and how to escalate effectively. ⚠️ What Is Happening Some users experience blog posts that fail to open when clicked or do not appear on the blog listing page after publishing. This behavior is not caused by a configuration error on your end — it indicates an underlying bug that our team needs to investigate directly. 📋 How to Escalate Because this is a bug-category issue, our support team will need to look into your account on the backend. To help us resolve this as quickly as possible, please have the following information ready when you reach out: - The name of your Website Studio project or site - The URL of the affected blog listing page - The title or titles of the specific blog posts that are not opening or not appearing - The exact behavior you are seeing (e.g., clicking a post does nothing, posts are missing from the listing page entirely) - When the issue started or was first noticed (date and approximate time, including your timezone) - Any error messages you see, if applicable 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 Menu Addition Errors

Overview When adding a page or item to your navigation menu in Website Studio, you may encounter a 'something went wrong' error. This can happen consistently across multiple attempts and may also affect other editing actions on your site. What This Error Means This is a known issue that can occur during menu addition or navigation updates in Website Studio. Because the root cause is a backend error, there are no reliable self-serve steps guaranteed to resolve it. The most effective path to resolution is to contact our support team directly so an agent can investigate your specific site and session. What to Have Ready When You Escalate To help our team resolve your issue as quickly as possible, please have the following information ready before reaching out: - The exact error message you are seeing (e.g. 'something went wrong' or any other on-screen message) - The name of your project or website in Website Studio - The page or item you were trying to add to the menu when the error occurred - The approximate date and time the error first appeared - Whether the error occurs on every attempt or intermittently - Any screenshots of the error state if possible If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Website Studio Text and Photo Editing Errors

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

🛠️ Fix HTTP Redirects and 404 Errors in Website Studio

🔍 Overview Some Website Studio users have noticed two related issues with their published sites: inconsistent HTTP-to-HTTPS redirects that route visitors to an unexpected /welcome page, and invalid URLs returning raw XML error messages (such as a NoSuchKey response) instead of a clean 404 or homepage redirect. This article explains what causes these issues, what has been fixed, and what you can do right now to minimise disruption for your visitors. ⚠️ What These Issues Look Like - Visiting the HTTP version of your site (e.g. http://yourdomain.com) redirects inconsistently — sometimes landing on /welcome instead of your homepage. - Typing a URL that does not exist on your site (e.g. http://yourdomain.com/page-that-doesnt-exist) returns a raw XML error response containing text like NoSuchKey rather than a friendly 404 page or a redirect to your homepage. - Visitors see a broken or confusing dead-end instead of being guided back to your content. 🧩 Why This Happens Website Studio sites are hosted on a CDN (Content Delivery Network). Two specific CDN-level behaviours were responsible for these errors: - Inconsistent HTTP redirect rule: The rule that forwards HTTP traffic to the secure HTTPS version of your site was not firing reliably, causing some requests to land on an internal /welcome route instead of your homepage. - Missing custom error handling: When a visitor requests a URL that does not exist, the CDN returned its default raw XML error response instead of a branded 404 page or a redirect back to your homepage. This is a poor experience and can confuse visitors and search engines alike. ✅ What Has Been Fixed Our engineering team has resolved both of these issues at the platform level: 1. HTTP-to-HTTPS redirect — The redirect rule has been corrected so that all HTTP requests consistently forward to the HTTPS version of your homepage, with no unexpected stops at /welcome. 2. Invalid URL error handling — The raw XML NoSuchKey response has been replaced with proper error-state handling. Visitors who land on a non-existent URL will now see a clean error page rather than raw server output. These fixes are applied automatically to all Website Studio sites hosted on our CDN. No action is required on your part for the core fixes to take effect. 🔧 Steps to Verify Your Site Is Working Correctly 1. Open a browser and visit the HTTP version of your domain (e.g. http://yourdomain.com). Confirm it redirects to the HTTPS homepage without stopping at /welcome. 2. Test an invalid URL on your site (e.g. https://yourdomain.com/this-page-does-not-exist). You should see a clean error page — not raw XML text. 3. Clear your browser cache and repeat both tests to rule out cached responses. 4. If you use a third-party DNS provider, confirm that your CNAME or A record still points to the correct Search Atlas CDN endpoint. Stale DNS records can cause redirects to behave unexpectedly. 💡 Best Practices to Avoid Future Redirect Issues - Always publish your site through Website Studio after making domain changes. Republishing triggers a fresh CDN configuration for your site. - Use HTTPS links everywhere — in your internal links, social profiles, and any external references to your site. Relying on HTTP-to-HTTPS redirects for regular traffic adds an unnecessary step and can introduce latency. - Check your site after domain changes. Any time you update your custom domain settings, run through the verification steps above to catch redirect issues early. - Monitor for XML error responses by periodically testing a few invalid URLs on your site, especially after a republish. ❓ Frequently Asked Questions Will this affect my SEO? Temporary redirect inconsistencies and raw error responses can cause search engines to misindex pages. Now that the fixes are in place, search engines will correctly follow the HTTPS redirect and receive proper error codes for missing pages. If your site was affected for an extended period, allow a few weeks for search engines to re-crawl and update their index. Do I need to set up custom redirects myself? No. The HTTP-to-HTTPS redirect and basic error handling are managed automatically by the platform. You do not need to configure these manually in Website Studio. What if I still see the /welcome page or raw XML errors after the fix? First, clear your browser and DNS cache. If the problem persists, the issue may be specific to your domain configuration. Contact support using the instructions below. 🆘 Still Experiencing Issues? If you have followed the steps above and are still seeing inconsistent redirects or raw XML error responses on your site, our team is ready to help. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix URL Migrations, Content Cloning & 410 Deletions

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

🖥️ Website Studio Duplication and Cloning Limitations

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

🛠️ Fix Website Studio Navigation and Page Editing Errors

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

🛠️ Troubleshooting Common Website Studio Bugs

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

🛠️ Fix Website Studio Sitemap and Indexing Errors

🔍 Overview If your Website Studio website is experiencing sitemap errors, missing pages, noindex flags, incorrect title tags on Google, or unexpected ranking drops, several known platform issues may be contributing. This article explains each problem and the steps you can take to resolve them. 🗺️ Sitemap Errors and Missing Homepage Your sitemap may be incomplete or contain errors for a few reasons: - Draft or unpublished pages leaking into the sitemap: Previously, unpublished draft versions of your site could be crawled by search engines. This has been resolved, but if Google cached an earlier version of your sitemap, it may still show stale data. - Preview and editor URLs in the sitemap: Internal editor, preview, and generated URLs were sometimes included in the live sitemap, polluting it with non-canonical addresses. This issue has been fixed. However, you should manually verify your sitemap is clean. - Homepage missing from sitemap: This can happen if the homepage was not set as published in Website Studio, or if a redirect chain is preventing Google from resolving it correctly. To check and fix your sitemap: 1. Log in to Search Atlas and open Website Studio. 2. Confirm your homepage is published and set as the primary page. 3. Navigate to your live sitemap URL (typically yourdomain.com/sitemap.xml) and review every URL listed. 4. Remove or unpublish any draft, preview, or duplicate pages that appear in the list. 5. Request a sitemap re-fetch via Google Search Console under Sitemaps to prompt Google to re-crawl the updated version. 🚫 Noindex Flags on Pages Noindex tags tell search engines not to index a page. If your pages carry unintended noindex flags, they will not appear in search results regardless of how well-optimised they are. Common causes in Website Studio include: - Preview or staging versions of the site being served with noindex headers, which can persist if the domain was not correctly transitioned to live. - Individual page settings accidentally toggled to noindex during editing. To check for and remove noindex flags: 1. Open Website Studio and go to each key page's SEO Settings. 2. Confirm the Allow search engines to index this page option is enabled. 3. Use the Site Audit tool in Search Atlas to scan for pages returning noindex signals. 4. For any page flagged as noindex, update the setting and republish the page. 5. Verify the fix by entering your page URL into Google Search Console's URL Inspection tool. 🏷️ Incorrect Title Tags Displaying on Google If Google is showing a different title than the one you set in Website Studio, this is usually caused by one of the following: - Google rewrites titles when it determines the set title does not accurately represent the page content. This is a Google-side behaviour and not always within your control. - Duplicate or competing pages: If preview URLs or draft pages were previously indexed, Google may be pulling the title from a cached version of one of those pages instead of your live page. - Title tag not saved correctly: A publish step may have been missed after updating the title in Website Studio. To correct title tag display issues: 1. In Website Studio, open the page editor and navigate to SEO Settings. 2. Confirm the title tag is accurate, relevant, and between 50–60 characters. 3. Save and republish the page. 4. In Google Search Console, use URL Inspection and select Request Indexing to prompt Google to recrawl the updated page. 5. If old preview or draft URLs were previously indexed, request their removal using the Removals tool in Google Search Console. 📉 Poor Rankings After Persistent Issues Months of sitemap errors, noindex flags, and competing preview URLs can negatively affect rankings even after the underlying issues are fixed. Recovery takes time because Google needs to recrawl and re-evaluate your site. To accelerate recovery: - Ensure all preview and draft domains are fully blocked from indexing. Preview domains serving sitemap or content files have now been addressed at the platform level, but confirm none remain accessible. - Submit your corrected sitemap in Google Search Console. - Use the Site Audit tool in Search Atlas to identify any remaining crawl errors, redirect issues, or duplicate content problems. - Build or refresh internal links pointing to your most important pages to reinforce their priority to search engines. - Monitor Google Search Console weekly to track improvements in crawl coverage and impressions. 📄 Blog Pages Displaying Raw XML If a blog article published through Website Studio displays raw XML in the browser instead of formatted content, this is a known rendering issue that has been resolved at the platform level. If you still encounter this on any article: 1. Open the article in Website Studio. 2. Unpublish the article, then republish it to trigger a fresh render. 3. Clear any caching on your domain if you use a CDN or caching plugin. 4. Check the live URL in a private browser window to confirm the issue is resolved. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 Fix Lead Capture Widget Invitation-Only Redirect Issue

🧭 Overview When you embed a Lead Capture widget on your website, visitors should see a public-facing form or report — not a login or registration wall. If your current snippet is redirecting visitors to an Invitation Required registration page, your widget is pointing to the whitelabel dashboard instead of the public Lead Capture widget endpoint. This article explains how to identify and fix that configuration. 🔍 How to Tell Which Problem You Have There are two different snippets inside Search Atlas. It is easy to copy the wrong one. Before changing anything, confirm which behavior your visitors are seeing: - Public widget working correctly: Visitors land on a branded report or lead capture form with no login prompt. - Invitation-only redirect (this issue): Visitors are sent to a page that says Invitation Required or asks them to register before they can continue. This means your snippet is linking to the whitelabel dashboard URL, not the embeddable public widget. ⚠️ Why This Happens Search Atlas has two separate access points that look similar but behave differently: - Whitelabel Dashboard link — requires an invitation or account login. It is designed for clients you have explicitly invited to view their reports inside your branded portal. - Lead Capture Widget snippet — a publicly embeddable code block that lets any anonymous visitor submit their site URL, receive a report, and become a lead. No login or invitation is needed. If you copied your snippet from the whitelabel dashboard settings area rather than the Lead Capture widget settings area, visitors will always hit the invitation gate. The fix is to replace the snippet with the correct one. ✅ How to Get the Correct Public Widget Snippet 1. Log in to your Search Atlas account. 2. In the left sidebar, navigate to Lead Capture. 3. Open the Widget Settings tab (not the Dashboard or Client Access tab). 4. Locate the Embed Code section. The correct snippet will contain a script tag referencing the public widget endpoint — it will not contain a dashboard subdomain URL or an invite token. 5. Copy the full snippet exactly as shown. 6. Replace the existing snippet on your website with this new code. 7. Save and publish your page, then test by opening the page in a private/incognito browser window to confirm visitors see the public form instead of an invitation prompt. 🛠️ Quick Checklist Before You Go Live - You copied the snippet from Lead Capture → Widget Settings, not from the whitelabel dashboard area. - The snippet does not include your whitelabel subdomain (e.g., reports.yourdomain.com/invite) as the destination URL. - You tested the page in an incognito window while logged out of Search Atlas. - Visitors see the lead capture form or public report immediately — no login or registration prompt appears. 📋 Additional Configuration to Check Even with the correct snippet in place, the following settings can affect public access: - Widget visibility: Inside Lead Capture → Widget Settings, confirm the widget status is set to Active or Published. A draft or paused widget may still redirect or show an error. - Whitelabel domain routing: If your whitelabel domain and your lead capture widget share a parent domain, ensure the routing rules in your DNS or platform settings are not intercepting the widget URL and sending traffic to the client dashboard instead. - Report access toggle: Some accounts have a setting that restricts report viewing to invited clients only. If that toggle is enabled globally, it will override the public widget. Locate the access control settings under your whitelabel configuration and confirm public report access is allowed. 🔄 If the Correct Snippet Still Redirects to Invitation Page If you have replaced the snippet with the one from Lead Capture → Widget Settings and visitors are still hitting an invitation-required page, this may indicate a platform-level configuration issue rather than a snippet error. In that case: - Double-check that you saved and re-published the page after replacing the snippet. - Clear any caching on your website or CDN, as an old cached version of the page may still be serving the old snippet. - Try embedding the widget on a brand-new test page to rule out page-level conflicts. - If the problem persists on a fresh page with the correct snippet, the issue is likely a backend configuration that requires our team to investigate. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Website Studio Page Creation and Edit Failures

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

🌐 Fix GoDaddy DNS Propagation Delays in Website Studio

🔍 Overview When you connect an existing GoDaddy domain to a new site in Website Studio, Search Atlas automatically provisions an SSL certificate and waits for your domain's DNS records to propagate across the internet. In most cases this completes within a few hours, but GoDaddy domains can legitimately take 24–48 hours to fully propagate. Seeing a Propagating status after 20 hours is not unusual and does not always indicate an error. ⏱️ Typical Propagation Timeline - 0–6 hours: DNS changes begin spreading to major resolvers worldwide. - 6–24 hours: Most regions resolve correctly; the status banner may still show Propagating. - 24–48 hours: Full global propagation completes. This is the normal outer limit for GoDaddy domains. - Beyond 48 hours: If the domain is still not resolving, a configuration issue is likely. Follow the troubleshooting steps below. ✅ Step 1 — Verify Your DNS Records in GoDaddy Before waiting further, confirm that the correct records were saved in your GoDaddy account. 1. Log in to your GoDaddy account and open My Products → Domains. 2. Click DNS next to your domain. 3. Confirm the following records exist exactly as shown in Website Studio: - An A record pointing to the Search Atlas IP address provided during setup. - A CNAME record for www pointing to your Search Atlas site address. 4. If any record is missing or incorrect, update it and save. Propagation will restart from that point. 🔒 Step 2 — Manually Retry SSL Certificate Provisioning If your DNS records are correct but the domain has been stuck on Propagating for more than 24 hours, the SSL certificate provisioning process may need a manual nudge. Follow these steps inside Website Studio. 1. In the left sidebar, click Website Studio (URL: /website-studio). 2. Locate the site attached to your GoDaddy domain and open its Settings. 3. Navigate to the Domain tab. 4. Find your connected GoDaddy domain. If a Retry SSL or Re-verify Domain button is visible, click it. 5. Wait 5–10 minutes, then refresh the page to check whether the status has updated to Active. 6. If the button is not visible, disconnect the domain and then reconnect it using the same domain name. This resets the SSL provisioning job without changing your DNS records. 🛠️ Step 3 — Check for Common GoDaddy-Specific Issues GoDaddy accounts have a few settings that can silently block propagation. Review each item below. - Domain forwarding is enabled: If GoDaddy is forwarding your domain to another URL, it will override your DNS records. Go to DNS → Forwarding and remove any active forwarding rules. - Domain Privacy & Protection is interfering: In rare cases, GoDaddy's privacy features delay DNS updates. Temporarily disable domain privacy, save, and check propagation again. - TTL is set too high: A very high TTL (e.g., 86400 seconds / 24 hours) on your old DNS records means resolvers cache the outdated values for longer. Lower the TTL to 600 seconds on all relevant records and wait for the cache to clear before expecting the new records to take effect. - Multiple conflicting A records: If GoDaddy shows more than one A record for the same hostname (e.g., two A records for @), delete the outdated one and keep only the Search Atlas IP. 🔎 Step 4 — Check Global Propagation Status Use a free DNS propagation checker (such as whatsmydns.net or dnschecker.org) to see which regions have already resolved your domain to the correct IP address. Enter your domain name, select A record, and look at the results. - If most locations show the correct Search Atlas IP, propagation is nearly complete. Wait a few more hours and retry SSL as described in Step 2. - If most locations still show the old IP or no record, your DNS records in GoDaddy may not have saved correctly. Repeat Step 1. 📋 When to Escalate Contact our support team if any of the following apply after completing all steps above: - It has been more than 48 hours since you last saved the correct DNS records and the domain is still not active. - The Retry SSL button produces an error message. - Disconnecting and reconnecting the domain does not reset the propagation status. - The DNS checker shows the correct IP worldwide but Website Studio still shows Propagating. 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 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 Website Studio Blueprint Not Rendering Correctly

🔍 Overview If your Website Studio staged preview is displaying a generic baseline template instead of your approved blueprint, the most common cause is a Brand Vault disconnection or an HTTP 403 WebSocket sync error. This article walks you through what causes the issue and the steps to resolve it without needing to rebuild your project from scratch. ⚠️ What Causes This Issue When Website Studio generates or previews a blueprint, it establishes a real-time WebSocket connection to Brand Vault to pull in your approved assets — fonts, colours, logos, and page structure. If that connection is interrupted or returns an HTTP 403 (Forbidden) error, the platform cannot authenticate the sync and falls back to a default baseline template as a safety measure. Common triggers include: - Your Brand Vault session token expired mid-build - A permissions change on the Brand Vault project while the build was in progress - A temporary platform connectivity issue that broke the WebSocket handshake - Navigating away from the editor before the blueprint finished saving ✅ How to Force a Blueprint Rebuild Follow these steps in order. Most customers resolve the issue at Step 3 or 4. 1. Confirm your blueprint is saved. Open Website Studio and navigate to your project. Go to Blueprints and verify your approved 6-page (or multi-page) blueprint appears in the list with a Saved status badge. If the status shows Draft, save it manually before continuing. 2. Reconnect Brand Vault. Open the Brand Vault panel via the header apps-grid icon → More Features → Brand Vault. If you see a Disconnected or Sync Error warning, click Reconnect. Wait for the green Connected indicator before proceeding. 3. Clear the staging preview cache. In the top toolbar, click the Preview dropdown and select Clear Preview Cache. Confirm when prompted. This forces the staging environment to discard the cached baseline template. 4. Trigger a manual rebuild. Click Preview again and select Rebuild from Blueprint. Website Studio will re-fetch your approved blueprint and all associated Brand Vault assets. This process typically takes 30–90 seconds depending on the number of pages. 5. Verify the staged preview. Once the rebuild completes, open the staged preview link. You should see your approved blueprint with all branding, layout, and page structure applied correctly. 🔄 If the 403 WebSocket Error Persists A persistent HTTP 403 error usually points to a permissions or session issue rather than a connectivity problem. Try the following: - Log out and log back in to refresh your authentication token, then repeat the rebuild steps above. - Check Brand Vault permissions. If you are part of a team, confirm with your account admin that your user role has Admin access to the Brand Vault project linked to this Website Studio build. - Try a different browser or incognito window. Browser extensions or cached credentials can occasionally interfere with the WebSocket handshake. - Wait 5 minutes and retry. If the platform experienced a brief service disruption, the WebSocket connection should automatically re-establish once connectivity is restored. 💡 Tips to Prevent This Issue in the Future - Always save your blueprint explicitly before starting a preview build — do not rely on auto-save alone. - Keep the Website Studio editor tab active during a build. Switching tabs or minimising the browser can interrupt the WebSocket connection. - Reconnect Brand Vault before triggering any preview or publish action, especially after periods of inactivity. - If you have multiple Brand Vault projects, double-check that the correct Brand Vault is selected for this Website Studio project before rebuilding. 📞 Still Need Help? If you have followed all the steps above and your blueprint is still rendering as a baseline template, our team can inspect the sync logs and WebSocket error details on your account directly. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Header Dropdowns and Build Errors After Import

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

🛠️ Fix Website Studio Template Rollback and Navigation Issues

🔍 Overview Some customers have reported that Website Studio appears to save changes successfully but then reverts them — particularly for header dropdowns, navbar items, and visual layout updates. Mobile navigation may also stop reflecting the correct page structure. These issues are related to a known sync conflict in how template changes are processed, and engineering fixes have been deployed. This article walks you through the steps to resolve these problems on your own. ⚠️ Symptoms to Look For - Changes to your site header or navigation menu are confirmed as saved but then revert to the previous version. - The right-side preview panel is missing or not visible in Website Studio. - A page added under a menu category (for example, a product sub-page) does not appear in the live navigation. - Mobile navigation does not match the desktop version or shows outdated menu items. - Website Studio appears stuck, repeatedly undoing edits as soon as they are applied. ✅ Step-by-Step Fix 1. Hard-refresh your browser. Press Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac) to clear the local cache and reload Website Studio from scratch. This resolves display conflicts caused by stale build files. 2. Clear browser cookies and site data for the Search Atlas domain. Go to your browser settings, find Cookies and Site Data, and remove entries for the Search Atlas platform. Then log back in and reopen Website Studio. 3. Exit the editor and re-enter. Close Website Studio completely, return to the main dashboard, and reopen the site you were editing. This forces the platform to load the latest saved template state rather than a cached version. 4. Check the preview panel layout. If the right-side preview panel is not visible, look for a panel toggle or drag handle along the right edge of the editor. Click or drag it to restore the preview. If it remains hidden after a hard refresh, proceed to step 5. 5. Re-publish your site after making changes. After editing your header or navigation, use the Publish button rather than relying on auto-save alone. This pushes the finalized template to the live site and reduces the chance of a rollback conflict. 6. Re-add missing navigation pages manually. If a page such as a product sub-page is not appearing in the nav menu, open the navigation editor in Website Studio, locate the correct parent menu item, and use the Add Link option to add the missing page. Save and republish. 7. Test on mobile after republishing. Open your site on a mobile device or use your browser's developer tools (press F12, then toggle device mode) to confirm that mobile navigation now reflects your latest changes. 💡 Why This Happens Website Studio processes template updates by comparing multiple files simultaneously. Under certain conditions — for example, when edits are made quickly in succession or when a session is interrupted — the system can detect a conflict between the saved state and the draft state, triggering a rollback. The engineering team has resolved the core bugs causing header edits to revert and the preview panel to disappear. The steps above ensure your local environment is fully synced with those fixes. 🚀 Prevention Tips - Make one section of changes at a time and publish before moving on to the next section. - Avoid opening Website Studio in multiple browser tabs simultaneously, as this can create conflicting save states. - After adding new pages to your site, always update the navigation menu manually and republish to ensure the new page appears correctly on desktop and mobile. - Use a Chromium-based browser (Google Chrome or Microsoft Edge) for the best compatibility with Website Studio. 💬 Still Experiencing Issues? If you have followed all the steps above and Website Studio is still reverting your changes or showing broken navigation, our team can inspect the build configuration for your specific site. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Privacy Policy Page Deployment in Website Studio

🔍 Overview When using Website Studio's AI to create a Privacy Policy page, you may notice the AI confirms the page was created and provides a URL — but the page never actually becomes accessible. This is a known bug that has been resolved. This article explains what happened, how to confirm your fix, and the steps to get a working Privacy Policy page with a real, accessible URL for A2P 10DLC compliance or any other requirement. ⚠️ What Was Causing This Issue Two underlying bugs were responsible for this problem: - Fake URL generation: The AI assistant would report that a Privacy Policy page had been successfully created and assign it a URL — but the page was never actually deployed to your site. The URL led nowhere. - Page deletion after creation: For sites built on single-page HTML uploads, the system incorrectly treated the site as a Single Page Application (SPA). A manifest validation process then deleted every page after the first, meaning any new page — including your Privacy Policy — was automatically removed before it could go live. Both of these bugs have been fixed by the Search Atlas engineering team. If you are still experiencing this issue, follow the steps below to create a working Privacy Policy page. ✅ How to Create a Working Privacy Policy Page 1. From the left sidebar, navigate to Website Studio (/website-studio). 2. Open the site where you need the Privacy Policy page. 3. Use the AI assistant or the page editor to create a new page and title it Privacy Policy. 4. Add your Privacy Policy content. If you need a starting template, ask the AI assistant to generate one for you. 5. Publish the page using the Publish button. Do not rely solely on the AI confirmation message — always verify the page is live by clicking the URL directly. 6. Once published, copy the live URL (for example: yourdomain.com/privacy-policy) and confirm the page loads in your browser. 7. Use this verified URL for any A2P 10DLC registration, compliance forms, or external references. 🔎 How to Confirm Your Privacy Policy Page Is Live After publishing, take these steps to verify the page is truly accessible: - Open the URL in a private or incognito browser window to rule out cached results. - Check that the page content is visible and correctly formatted. - If you are using a custom domain, confirm the domain has an active SSL certificate. Note that SSL provisioning can take up to 72 hours after a custom domain is connected. - If the URL returns a 404 error or a blank page, the page did not deploy correctly — proceed to the troubleshooting steps below. 🛠️ Troubleshooting Steps If the Page Still Does Not Appear 1. Delete the existing Privacy Policy page from your Website Studio page list if one was previously created by the AI. 2. Create a fresh page from scratch rather than editing the failed one. 3. After saving your content, click Publish and wait 60 seconds before testing the URL. 4. If your site uses a custom domain, temporarily test the page using the default Website Studio subdomain to rule out a domain or SSL issue. 5. Clear your browser cache and test the URL again in a private window. 📋 Notes for A2P 10DLC Compliance If you need a Privacy Policy URL specifically for A2P 10DLC SMS registration, keep the following in mind: - The URL must be publicly accessible — no login or password required to view it. - The page must load without errors and display your full Privacy Policy text. - Only use the URL after you have personally verified it loads correctly in a browser. Do not submit the URL provided by the AI assistant without testing it first. - If your domain does not yet have SSL active, wait until the certificate is provisioned before submitting the URL to any compliance registry. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Disappearing Blog Posts After Website Studio Edits

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

🚀 Fix Pro Plan Website Project Quota Issues

🔍 Overview On the Search Atlas Pro Plan, you are entitled to add up to a set number of website projects to your dashboard. If you are seeing fewer available slots than expected — for example, only 2 sites instead of 3 — this is almost always caused by a billing or account status issue rather than a platform bug. This article explains the most common causes and how to fix them. ⚙️ Common Reasons Your Quota Appears Reduced - Payment failure or expired card: If a recent invoice was not collected successfully, Search Atlas may temporarily restrict account features, including the ability to add new website projects, until the balance is cleared. - Billing cycle gap: Accounts that recently upgraded, downgraded, or renewed may experience a short delay before the new quota is fully reflected in the dashboard. - Duplicate or legacy workspace: If your team has more than one Search Atlas workspace, the Pro Plan entitlement may be applied to a different workspace than the one you are currently using. - Seat or plan mismatch: Occasionally, a plan change processed mid-cycle can cause the dashboard to display the previous plan's limits until the next billing refresh. 🛠️ Steps to Resolve the Issue 1. Check your billing status. Go to your Avatar Menu (👤) in the top-right corner of the platform (click your avatar) and navigate to Settings → Billing. Confirm that your current plan shows as Pro and that your most recent invoice is marked Paid. If there is a failed payment, update your payment method and settle any outstanding balance. 2. Verify you are in the correct workspace. If your organisation has multiple workspaces, confirm you are logged into the workspace that holds the Pro Plan subscription. You can check this in Team Members (top-right Avatar Menu (👤)). 3. Refresh your session. After resolving any billing issue, log out of Search Atlas completely and log back in. This forces the platform to reload your current plan entitlements and quota limits. 4. Wait up to 15 minutes. In some cases, quota updates propagate within a few minutes after a payment is confirmed. If your dashboard still shows the incorrect number of site slots, wait briefly and then hard-refresh the page (Ctrl + Shift + R on Windows, Cmd + Shift + R on Mac). 5. Attempt to add the website project again. Once billing is confirmed and your session is refreshed, navigate to your dashboard and try adding the third website project. The option should now be available. 📊 What the Pro Plan Includes The Search Atlas Pro Plan includes a defined number of website project slots as outlined at the time of your subscription. If you need to add more website projects beyond your current plan's limit, you can upgrade your plan or purchase additional project slots directly from the Billing section (Avatar Menu (👤), Avatar Menu (👤), top-right) of your account. 💡 Tips to Avoid This Issue in the Future - Keep your payment method up to date in Billing (Avatar Menu (👤), Avatar Menu (👤), top-right) to prevent automatic restrictions triggered by failed payments. - If you manage multiple workspaces, designate one team member as the billing admin to ensure invoices are monitored consistently. - After any plan change, log out and back in to ensure your dashboard reflects the latest quota immediately. 🆘 Still Seeing the Wrong Quota? If you have followed all of the steps above and your Pro Plan dashboard still shows fewer website project slots than your plan entitles you to, our team can investigate your account directly. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🎨 Dropdown Menu Styling Limits in Website Studio

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

🛠️ Fix Website Studio Runtime Errors and Build Crashes

🔍 Overview Website Studio runtime errors and build crashes can interrupt your landing page workflow in several ways — including white screens on project load, the builder hanging at 98%, "Something Went Wrong" messages, or publish failures. This article explains the most common causes and the steps to resolve them. ⚠️ Common Error Types - White screen on project load — the project opens but displays a blank page with no editor controls. - Builder hangs at 98% — the loading progress bar stalls and does not complete. - "Something Went Wrong" crash — typically triggered when a prompt includes multiple URLs at once. - Publish failure — an error referencing "Failed to read pages.manifest.json" appears when trying to publish. - Persistent runtime errors — the page repeatedly malfunctions after reopening or editing. 🛠️ Step-by-Step Fixes 1. Refresh the page and clear your browser cache. Many transient runtime errors resolve with a hard refresh. Press Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac) to force a full reload without cached data. 2. Use a supported browser. Website Studio performs best on the latest version of Google Chrome or Microsoft Edge. If you are using Firefox, Safari, or an older browser version, switch browsers and try again. 3. Close and reopen the project. If the builder is stuck at 98% or showing a white screen, close the tab, return to your Search Atlas dashboard, and reopen the project from the Website Studio project list. Do not click Stop when the builder is mid-load — this can leave the project in an empty state. 4. Use one URL per prompt. If you triggered the "Something Went Wrong" error while entering a prompt, ensure you are only including a single URL in each prompt submission. Remove any additional URLs and resubmit. 5. Retry publishing after a short wait. The "Failed to read pages.manifest.json" publish error is usually temporary. Wait 60 seconds, then attempt to publish again. If the error repeats, proceed to the next step. 6. Duplicate the project and work from the copy. If a specific landing page project consistently crashes on load, open Website Studio, locate the affected project, and use the duplicate option. Work from the duplicated version while the original is investigated. 7. Check for unsaved changes before closing. Always use the built-in save controls before closing a tab. Force-closing the browser during an active edit session can corrupt the project state and trigger errors on the next load. 🚫 What to Avoid - Do not click Stop while the builder is loading — this can leave your project in an unrecoverable empty state. - Do not paste multiple URLs into a single AI prompt field. - Do not publish immediately after making a large batch of edits — give the autosave a moment to complete first. ✅ When Everything Is Working Again Once the error is resolved, your landing page should load fully in Website Studio, the progress bar should complete past 98%, and publishing should succeed without manifest errors. If you previously duplicated a project as a workaround, you can delete the broken original once you confirm the copy is stable. 💬 Still Experiencing Issues? If the steps above do not resolve your runtime error or build crash, our team can investigate the specific project and error logs. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix YouTube Thumbnail Overlay Persistence in Website Studio

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

🛠️ Fix Website Studio Publish Button Not Updating

🔍 Overview After making visual edits in Website Studio, the publish button may not update as expected after edits are made and saved. This can prevent you from republishing your site. This article explains what is happening and what to do next. ⚙️ Why This Happens This is a known issue with the Website Studio publish button. After making visual edits, the publish button state does not always update correctly, which means the interface may continue to show Published even when edits have been made. As a result, the republish option may appear unavailable. ✅ What to Try If your publish button is not updating after visual edits, try the following steps: 1. Refresh the page: After completing your edits, refresh your browser and return to Website Studio to see if the publish button state has updated. 2. Re-enter the editor: Navigate away from Website Studio and then return to your project. Re-opening the project can prompt the system to re-evaluate the publish state. 3. Make a minor additional edit: Inside the visual editor, make a small secondary change and save. This may trigger the publish button to become active again. 4. Try a different browser: If the issue persists, open Website Studio in a different browser to rule out a local caching problem. 📋 What to Document Before Contacting Support If none of the above steps resolve the issue, gathering the following information will help our team investigate quickly: - The name of the project or site you are editing - The browser and operating system you are using - A short screen recording or screenshot showing the publish button stuck on Published after edits are made - The approximate time and date the issue occurred If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Website Studio AI Credit Loss Issues

🔍 Overview Some customers have reported that Website Studio's AI agent confirmed edits as completed, but the actual code or design changes were never applied — resulting in wasted credits. This article explains why this happens and what to expect when escalating to our team. ⚠️ What Causes This Issue A known issue has been identified where the AI agent reports a successful edit, but the changes are not reflected in your project. When this occurs, credits may be consumed even though no change was applied. If you are experiencing credit loss after a failed AI edit, this is a backend issue that requires our team to investigate and restore your credits. ✅ What Our Team Will Do When you report this issue, our support team will review your account activity and, where applicable, work to restore credits that were lost due to failed AI agent edits. No action is required on your end beyond reporting the issue. 📋 What to Have Ready When Escalating To help our team resolve your case as quickly as possible, please have the following information ready: - The name of the project or page where the failed edit occurred. - An approximate date and time when the credit loss happened. - A description of the AI prompt you submitted when the issue occurred. - Any confirmation messages the AI agent displayed after the edit. 💡 Best Practices While the Issue Is Being Investigated - Be specific with AI prompts: Clear, detailed instructions reduce the chance of the agent misinterpreting your request. - Verify changes after each AI edit: After the agent confirms a change, check your project to confirm the edit was applied before submitting another prompt. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🌐 Website Studio Domain Not Showing After Publishing

🔍 Why Your Domain Isn't Showing Yet After you publish your Website Studio site and connect a custom domain, there is a waiting period before the domain becomes visible in browsers. This is called DNS propagation — the process by which your domain settings spread across servers worldwide. It typically takes 24 to 48 hours to complete, though it often resolves sooner. During this window, your site is live on our end, but your domain may not yet resolve correctly in all browsers or locations. This is normal and expected behavior. ✅ How to Check Your DNS Propagation Status You can verify whether your domain has propagated successfully without waiting or guessing: 1. Use a free external DNS lookup tool (such as dnschecker.org or whatsmydns.net) to confirm whether your domain is resolving correctly from different global locations. 2. Enter your custom domain into the tool and review the results. If propagation is still in progress, allow more time before troubleshooting further. 3. If the external check confirms your domain is resolving correctly, proceed to the browser cache steps below. 🗑️ Clear Your Browser Cache Even after DNS propagation completes, your browser may still show an old or blank version of your site because it has cached the previous DNS response. Clearing your cache forces your browser to fetch the latest information. Google Chrome: 1. Press Ctrl + Shift + Delete (Windows) or Cmd + Shift + Delete (Mac). 2. Set the time range to All time. 3. Check Cached images and files and Cookies and other site data. 4. Click Clear data, then reload your domain. Mozilla Firefox: 1. Press Ctrl + Shift + Delete (Windows) or Cmd + Shift + Delete (Mac). 2. Select Everything from the time range dropdown. 3. Check Cache and Cookies, then click Clear Now. Safari: 1. Go to Safari > Settings > Privacy. 2. Click Manage Website Data, then Remove All. 3. Reload your domain. You can also test your domain in a private or incognito window to bypass cached data instantly, without clearing your entire browser history. 🛠️ Flush Your Local DNS Cache Your operating system stores its own DNS cache separately from your browser. If clearing your browser cache doesn't help, flush your system's DNS cache as well. Windows: 1. Open the Start menu, search for Command Prompt, and run it as Administrator. 2. Type ipconfig /flushdns and press Enter. 3. Reload your domain in the browser. Mac: 1. Open Terminal (found in Applications > Utilities). 2. Type sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder and press Enter. 3. Enter your Mac password if prompted, then reload your domain. If your domain is still not resolving after completing all of the steps above and 48 hours have passed, please escalate. When reaching out, have the following ready: your custom domain name, the exact error message or behavior you see in the browser, and the timestamp of when you first published your site. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Website Studio Sitemap & Noindex Bug Fixes

🔍 Overview Some Website Studio websites experienced technical SEO bugs that affected sitemap accuracy, noindex tag behaviour, page indexability, and overall SEO scores. The issues described in this article have been resolved and deployed to production. This article explains what happened, what was fixed, and what you should do now to verify your site is healthy. 🐛 What Bugs Were Present? The following confirmed bugs affected Website Studio sites: - Homepage missing from sitemap: The XML sitemap omitted the homepage URL, reducing crawl coverage. - Incorrect noindex tags on published pages: Valid, publishable pages were incorrectly marked as noindex, preventing Google from indexing them and causing ranking drops. - Title tags rewritten on the SERP: A related bug caused title tags to be overridden in search results, further contributing to ranking loss. - Preview and draft domains were indexable: Unpublished draft and preview versions of sites were publicly crawlable and could appear in Google search results, competing directly with your live site. - Low SEO scores on Desktop and Mobile: Generated websites were receiving unexpectedly low SEO scores due to a scoring calculation error. - URL pollution from editor and preview URLs: Legacy editor, preview, and duplicate URLs were leaking into the live site and its sitemap, inflating URL counts and confusing crawlers. ✅ What Has Been Fixed? All of the issues listed above have been resolved and are fully deployed to production. Here is a summary of what was corrected: - The sitemap generator now correctly includes the homepage and excludes all noindex, draft, and preview URLs. - Noindex tags are no longer applied incorrectly to published, indexable pages. - Title tags are preserved as set in Website Studio and are no longer overridden. - Preview and draft domains are now blocked from indexing. - SEO scores for generated websites now reflect accurate Desktop and Mobile evaluations. - Editor, preview, and duplicate URLs are no longer injected into the live site or its sitemap. 📋 Steps to Verify Your Site After the Fix Even though the bugs are resolved, we recommend taking the following steps to confirm your site is in good shape and to help Google re-crawl any affected pages promptly. 1. Open Website Studio: Navigate to Website Studio from your platform dashboard. 2. Check your published site settings: Review your pages to confirm no pages are still marked noindex unintentionally. 3. Inspect your sitemap: Visit your sitemap URL and confirm the homepage and all key published pages are present, and that no preview or draft URLs appear. 4. Check Google Search Console: If you have Google Search Console connected, review your Coverage and Sitemaps reports for any lingering indexing errors or excluded pages. 5. Request re-indexing if needed: For any pages that were previously excluded incorrectly, use the URL Inspection tool in Google Search Console to request re-indexing. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Duplicate Content After Rollback Recovery

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

🎬 Fix YouTube Videos Not Showing in Published Blog

🔍 Overview If you've embedded a YouTube video in a blog post inside Content Studio and it looks fine in the editor, but doesn't appear on your published blog in Website Studio, a simple republish is usually all it takes to sync the content and render the video correctly on your live site. 🧠 Why This Happens Website Studio caches your blog content at the time of publishing. If you embed or update a YouTube video in Content Studio after the blog was originally published, those changes are not automatically pushed to your live site. You need to republish the post to force Website Studio to pull in the latest version of your content, including the embedded video. ✅ How to Republish Your Blog Post 1. In the left sidebar, click Website Studio to open the website builder at /website-studio. 2. Locate your blog project and open it. 3. Navigate to the blog post that contains the YouTube video. 4. Make a minor edit to the post if needed — for example, add a space or update a word — to mark the content as changed. This is not always required, but it ensures the platform registers new content. 5. Click Submit to republish the blog post to your live site. 6. Wait 1–2 minutes, then open your published blog URL in a new browser tab. 7. Hard-refresh the page by pressing Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac) to clear the browser cache. 8. Confirm the YouTube video is now rendering correctly. 🎥 Make Sure the YouTube Embed Is Set Up Correctly Before republishing, double-check how the video is embedded in Content Studio. An incorrect embed can prevent the video from displaying even after a republish. - Use the embed code, not a plain URL: In YouTube, click Share → Embed and copy the full <iframe> snippet. - Paste as HTML: In Content Studio, switch your blog editor to HTML / Source mode before pasting the embed code so it is not treated as plain text. - Avoid privacy-restricted videos: If the YouTube video is set to private or unlisted with restricted embedding, it will not play on external sites. Make sure the video's embed permissions are enabled on YouTube. 🛠️ Still Not Showing After Republishing? If the video still does not appear after following the steps above, try the following checks: - Confirm the blog post status shows as published and not draft inside Website Studio. - Test the live blog URL in a different browser or an incognito window to rule out a local cache issue. - Check that the YouTube video itself is publicly accessible and embeddable by testing the embed on a standalone HTML page. - If your blog is hosted on a custom subdomain, allow a few extra minutes for DNS and CDN propagation to complete before the update appears. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

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

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

Fix Article Publishing Failures and Manage Photos

🔍 Overview If your articles are failing to publish, this is often related to a slug conflict — a situation where the URL associated with your article is already in use on your connected site. This article explains what slug conflicts are, general steps customers have taken to address publishing failures, and how to get support for photo management issues. ⚠️ Why Articles Fail to Publish: Slug Conflicts Explained Every article has a slug — the unique portion of its URL that identifies that page (for example, /my-article-title). A slug conflict can occur when that URL path is already in use on your connected site, which may prevent the article from publishing successfully. Common reasons a slug conflict occurs: - You previously published an article with the same title and it is still live. - A page or post on your site already uses the same URL path. - A draft was published, deleted, and republished without changing the slug. 🛠️ How to Resolve a Slug Conflict If you are experiencing a publish failure that may be related to a slug conflict, the general approach is: 1. Open the article that is failing to publish. 2. Locate the slug or URL/permalink setting for the article. 3. Change the slug to something unique — for example, from /healthy-recipes to /healthy-recipes-2025. 4. Save the updated slug. 5. Attempt to publish the article again. Note: If you are unsure which URL is causing the conflict, review your connected site's existing pages and posts for any matching URL paths before making changes. 🚀 Publishing an Article If you are still unable to publish after addressing a potential slug conflict, or if you are uncertain where to find the slug or URL settings within the platform, please reach out to our support team for guidance specific to your account setup. When contacting support, please have the following ready: - The name or title of the article you are trying to publish. - The exact error message you received when the publish action failed. - The URL or slug you were attempting to use. - The name of your connected site or project. 🖼️ Managing Article Photos If you are experiencing issues with article photos — such as missing images or wanting to replace an auto-assigned image with one of your own brand assets — please contact our support team. When reaching out, include: - The article name or URL. - A description of the photo issue (e.g., image missing, wrong image displayed, unable to update the image). - Any error messages you encountered. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Broken Images in Generated Content

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

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

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

🛠️ Fix Website Studio Bugs and Common Issues

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

🏷️ How to Protect and Control Your Listing Price

This article is for sellers who are concerned about pricing control on their listings. If you believe your listing price has been changed without your consent, or if you want to make sure your rates are protected, this article explains what to do next. 🔍 What We Know About This Issue Some sellers have reached out with concerns about pricing control — for example, feeling that a listed rate does not reflect what they originally set, or wanting assurance that their price cannot be changed without their explicit approval. Pricing discrepancies can occur for a few common reasons: - Multiple account users: If more than one person has access to your account, another user may have edited the listing price. Review who has account access under your account settings. - Platform-side updates: In some cases, a listing update or platform change may reset or affect a pricing field. Check your listing settings directly to confirm the current value. - Accidental edits: A price field may have been changed inadvertently during another listing edit. Always review all fields before saving changes to a listing. 🛠️ Steps to Review and Correct Your Listing Price 1. Log in to your Search Atlas account and navigate to the relevant listing or project. 2. Open the listing settings and locate the pricing or rate field. 3. Confirm the current value matches what you intended to set. If it does not, update the field to your correct price and save the changes. 4. Review your account's user permissions to ensure only authorized users can edit listings. 5. If the price reverts again after you correct it, or if you cannot find where the change originated, note the listing name, the price you set, the price currently shown, and the approximate date you first noticed the issue — then contact our support team so we can investigate your account directly. ✅ What to Have Ready If You Need to Escalate - Your project or listing name - The price you set and the price currently shown - The approximate date you noticed the issue - Any relevant context (e.g., whether anyone else has access to your account) If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 Fix DNS Verification Failures in Website Studio

Overview When you migrate a site to a Website Studio project, you must point your domain's DNS records to the server IP address associated with your project. Even after updating the A record, DNS verification inside Website Studio can still fail. This article explains common reasons that happens and general steps to investigate. Important Note The troubleshooting steps below reflect general DNS best practices for domain migration scenarios. Because DNS verification failures in Website Studio can have several root causes specific to your account and project configuration, the steps below may not resolve every case. If your issue persists after following these steps, please contact our support team for account-specific guidance — see the end of this article. Before You Begin Confirm the following before troubleshooting a verification failure: - You have access to your domain registrar or DNS provider's control panel. - Your Website Studio project has been published or is ready to go live. - You know the IP address or DNS record value your project requires — check inside your Website Studio project for this information, or contact support if you are unsure where to find it. - You know whether your domain uses an A record or a CNAME record — this guide covers the A record scenario. A Record vs. CNAME — Which One Do You Need? DNS configuration for domain migrations generally follows these rules: - A record — Typically required for root/apex domains (for example, yourdomain.com). The value should be set to the IP address associated with your Website Studio project. - CNAME record — Generally used for subdomains only (for example, www.yourdomain.com). Using a CNAME on a root domain is not supported by most DNS providers and may cause validation to fail. If you are unsure which record type your Website Studio project requires, contact support before making DNS changes. Step 1: Verify Your A Record Is Set Correctly 1. Log in to your domain registrar or DNS provider's control panel. 2. Navigate to the DNS management area for your domain. 3. Locate the A record for your root domain. 4. Confirm the value matches the IP address required for your Website Studio project. Correct it if it differs. 5. Save the change and note the TTL (Time to Live) value — this determines how long old DNS data is cached by resolvers. Step 2: Wait for DNS Propagation DNS changes do not take effect instantly. Propagation can take anywhere from a few minutes to 48 hours depending on your TTL setting and your DNS provider's update frequency. - A higher TTL means resolvers may cache the old record for longer after your change. - To speed up future changes, consider lowering your TTL before making DNS edits, then restoring it afterward — check your DNS provider's documentation for recommended values. - Avoid retrying DNS verification in Website Studio repeatedly during this window — each failed check does not reset the propagation timer. Step 3: Confirm Propagation With an External Tool Before attempting to verify your domain in Website Studio, confirm the record has propagated globally using a free DNS lookup tool such as whatsmydns.net or dnschecker.org. Enter your domain and select the A record type to see whether your updated IP address is visible from multiple locations worldwide. Step 4: Check for DNS Conflicts Certain configurations can interfere with DNS verification: - Cloudflare proxy (orange cloud) — If your domain is proxied through Cloudflare, the IP address seen externally will be Cloudflare's, not your project's IP. Disable the proxy (set to DNS-only / grey cloud) during verification, then re-enable it if needed after the domain is confirmed. - Multiple conflicting A records — If more than one A record exists for your root domain pointing to different IP addresses, remove the outdated ones and keep only the correct record. - Old cached records — If propagation tools show the correct IP but verification still fails, try clearing your local DNS cache or testing from a different network. When to Escalate If you have confirmed the correct A record is in place, propagation is complete globally, and DNS verification in Website Studio still fails, this is likely an account- or project-specific issue that requires our team to investigate. When contacting support, please have the following ready: - Your Website Studio project name - Your domain name - The exact error message shown during DNS verification - A screenshot or result from a DNS propagation checker confirming the current A record value - The timestamp of when you last updated your DNS record If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Website Studio Credits and Trial Extensions

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

🛠️ Fix Blog Articles Deleted or Repositioned in Website Studio

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

🐛 Fix Duplicate and Scaffold URLs in Website Studio

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

🛠️ Fix Website Studio SPA Navigation and Page Detection Issues

🔍 Overview Two known issues can affect your experience in Website Studio: the scroll position not resetting when navigating between pages in the preview, and a false duplicate-page error that incorrectly blocks you from creating pages with similar-but-distinct URL slugs. This article explains both issues, their causes, and what you can do right now. 📜 Issue 1: Scroll Position Does Not Reset on Page Navigation When navigating between pages in the Website Studio preview — for example, moving from the Home page to the Contact page — the preview window may not scroll back to the top of the new page. Instead, it retains the scroll position from the previous page, making it appear as though content is missing or the page did not load correctly. Why this happens: Website Studio uses a Single Page Application (SPA) router to handle navigation inside the preview. In certain cases, the router does not trigger a scroll-position reset when transitioning between pages, so the viewport stays wherever it was on the previous page. What you can do right now: - After navigating to a new page in the preview, manually scroll to the top of the preview window to verify the full page content is present. - Use the browser refresh button inside the preview frame to force a full reload of the newly selected page — this will always land you at the top. - If you are reviewing a specific section, use the Website Studio section panel to jump directly to that section rather than scrolling from the navigation. Status: This bug has been identified and a fix has been deployed. If you are still experiencing scroll issues after following the steps above, please contact our support team using the instructions at the bottom of this article. 🚫 Issue 2: Duplicate Page Detection Incorrectly Blocks New Pages When attempting to create a new page with a URL slug such as /education-acoustic-solutions/, Website Studio may display an error stating the page already exists — even though the only existing page is /acoustic-solutions/. These are two distinct pages, and the error should not appear. Why this happens: The duplicate-page detection logic performs a partial string match on existing URL slugs rather than an exact match. Because /acoustic-solutions/ is a substring of /education-acoustic-solutions/, the system incorrectly treats the new slug as a duplicate and blocks the creation. What you can do right now: 1. Confirm that the page you want to create does not already exist by checking your full page list in Website Studio under Pages. 2. If the slug you want is genuinely unique and the error still appears, try a temporary workaround: create the page with a slightly different slug (for example, /edu-acoustic-solutions/), publish it, then rename the slug to your intended URL in the page settings. 3. Alternatively, reach out to support (see below) and a teammate can create the page on your behalf while the fix is confirmed on your account. Status: This bug has been identified and resolved in the platform. If you encounter this error after the fix, the steps above will help you move forward without losing progress. ⚙️ Additional Context: SPA Detection on Single-Page HTML Uploads A related issue affected websites built from single-page HTML uploads. Website Studio was incorrectly identifying these uploads as SPA sites and applying SPA routing logic, which caused the system to delete all pages after the first. This has been fully resolved. If you uploaded a single-page HTML file and noticed pages disappearing, please re-upload your file and verify your page list is intact. ✅ Quick Checklist Before Contacting Support - Manually scroll to the top of the preview when switching pages to confirm content is loading correctly. - Check your full page list to confirm a slug truly does not exist before creating a new page. - Try the temporary slug workaround if the duplicate-page error persists. - Clear your browser cache and reload Website Studio if any visual issues remain after a fix has been noted as deployed. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🖼️ Fix Image Alt Text Table Errors in Website Studio

🔍 Overview Some customers see error indicators in the Image Alt text table inside Website Studio, but when they open the table, nothing appears to be wrong — no missing alt text, no broken entries, and no obvious problem. This article explains what is known about this issue and what to expect. ⚙️ Why This Happens The error flag on the Image Alt text table is a display issue, not a reflection of actual missing or broken alt text on your page. Your images and their alt attributes are intact — the table is simply not displaying its status correctly. This is a known platform issue currently under investigation by the engineering team. No data has been lost, and your images are not affected. 🛠️ What to Do If You See This Error If you encounter this error indicator in the Image Alt text table, here is what to have ready when reaching out to our support team: - The name of the project or page where the error appears. - A screenshot of the error indicator in the Image Alt text table. - The approximate time you first noticed the issue. Our team will investigate the specific cause on your account and keep you updated on any resolution. 🔄 Steps to Try Before Escalating In some cases, the error indicator clears on its own after a page reload. Try the following before reaching out: 1. Save any unsaved changes in your current page. 2. Refresh your browser tab using Ctrl + R (Windows) or Cmd + R (Mac). 3. Navigate back to the page and open the Image Alt text table again. 4. Check whether the error indicator is still present. If the error persists after a full browser refresh, it is safe to continue working — the issue is cosmetic and does not impact your site's actual published content. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Blog Article Deletion and Repositioning Bug Fix

🔍 Overview A bug was identified and fixed affecting blog articles in Website Studio. Some customers experienced blog articles being unexpectedly removed from their blog page or repositioned within the article list. This article explains what is known about this issue, confirms the current fix status, and tells you what to do if you are still experiencing problems. This was a platform-level bug. No action was required on your part to trigger it, and the fix has been deployed by the Search Atlas team. ✅ Current Fix Status The blog article deletion and repositioning bug in Website Studio has been resolved at the platform level. If you published blog articles and noticed they were missing or out of order, this has been addressed. You do not need to take any technical action on the backend. 📋 What to Do If Your Articles Are Still Affected If your blog articles are still appearing out of order or missing after the fix was deployed, please escalate so the team can investigate your specific account. Before reaching out, have the following ready to speed up resolution: - The name of your project or workspace in Search Atlas - The titles of the affected blog articles - A description of the problem you are seeing (e.g., articles missing entirely, articles appearing at the wrong position in the list) - Any approximate date and time when you first noticed the issue - Screenshots of the current state of your blog page in Website Studio, if possible The support team will be able to review your account directly and take any necessary backend action to restore your article order or recover missing entries. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Website Studio Visual Editor Issues

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

🛠️ Fix Website Studio Missing File Errors

🔍 What This Error Means When you publish in Website Studio, the platform builds your site and validates it before it goes live. For uploaded static HTML sites, the validator checks that every file your pages reference — such as stylesheets, scripts, and images — is included in the publish bundle. If a referenced file is missing, publishing stops and you see a message like: "Your pages reference files that aren't part of the published site." This is a safety check. It prevents a half-working site from going live with broken styling or missing images. ⚠️ Why Re-Uploading Can Remove Your Edits Re-uploading files into Website Studio replaces the existing file set for your site. Any changes you made directly to your landing page inside Website Studio — text edits, images you added, and layout tweaks — live in those files. If you re-upload your original downloaded files, they overwrite the edited versions, and your changes are lost. To protect your work before re-uploading: - Back up your edits first. Copy any edited text, image files, and settings to a safe location on your computer. - Keep your originals separate. Store the complete original download in its own folder so you always have a clean copy. - Note what you changed. List the pages and sections you edited so you can quickly redo the changes after re-uploading. 🛠️ How to Fix the Error Follow these steps in order: 1. Read the error message closely. Note any file name or path it mentions. This tells you which file the validator could not find. 2. Check your local files. Open the folder you uploaded from and look for a folder named like Page name_files — for example, My Landing Page_files. This folder usually holds the CSS, JavaScript, and images your page needs. 3. Confirm every referenced file is included. The most common cause is a browser "Save As" export. When you save a single page as "Webpage, Complete," the browser creates a matching _files folder. If that folder, or any file inside it, is missing from your upload, publishing fails. 4. Remove spaces from file and folder names. Paths containing spaces and nested _files folders can confuse the validator. Rename files and folders so they contain no spaces — for example, change My Page_files to my-page-files — and update any references to them inside your HTML. 5. Back up your Website Studio edits. Copy any changes you made to your landing page in Website Studio to a safe place, as described above. 6. Re-upload the complete file set. In the left sidebar, open Website Studio, and upload your site's entire folder — including the _files folder and all assets. 7. Restore your edits and publish again. Reapply your saved changes to the landing page, then publish. If the error persists, rebuild the page from a full-site export instead of a single-page "Save As" export. 💡 How to Prevent This Issue - Export the full site, not one page. Single-page browser saves often create fragile file paths. Whenever possible, export your site from your website tool as a complete package. - Upload the whole folder. Always include every subfolder and asset, not just the HTML files. - Avoid spaces in file and folder names. Use hyphens or underscores instead. - Test locally before uploading. Open your HTML file from your computer in a browser. If styling or images look broken locally, they will also be broken after publishing. 🚀 If the Problem Continues If you have re-uploaded all files and publishing still fails, or if your site stays stuck on a "publishing" status, our team can review your site and confirm exactly which file is causing the problem. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🛠️ Fix Menu Editing Errors in Website Studio

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

🛠️ Fix Website Studio Instant Indexing Quota Errors

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

🖼️ Fix a Dark Hero Image Overlay in Website Studio

🔍 What Is Happening? When you try to lighten or remove a dark overlay on a hero image in Website Studio, the change may not apply as expected — leaving your hero image still appearing very dark. This is a known platform issue that may require backend investigation to resolve. This article explains what is happening and what information to have ready when contacting our support team. ⚙️ Why This Happens Hero image overlay adjustments in Website Studio can fail to apply correctly in certain cases. Because the root cause requires investigation on the platform side, there is no confirmed self-serve workaround available at this time. 🚧 Known Platform Issue Our team is aware that hero image overlays may remain dark even after attempting to change them. This is a bug that requires backend review rather than a customer-side fix. 📋 What to Have Ready When Escalating To help our team investigate and resolve this as quickly as possible, please have the following information ready before reaching out: - Your project or site name in Website Studio. - The specific page where the dark hero image overlay appears. - A screenshot or screen recording showing the dark overlay on your hero image. - The exact steps you have already tried to lighten or remove the overlay. - Any error messages or unexpected behaviour you observed during those attempts. Providing these details upfront will allow our team to reproduce the issue and apply the correct fix on the backend. 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 OTTO Pixel Wrong UUID on Website Studio

🧩 Why This Error Happens Each project you create in Website Studio generates its own unique OTTO pixel script. This script contains a UUID (Unique User Identifier) that is specific to that project alone. If you copy the pixel script from one Website Studio project and paste it into a different project, OTTO will detect a UUID mismatch and the scan will fail. This is the most common cause of the wrong UUID error: the pixel installed on your site belongs to a different Website Studio project, not the one you are currently trying to activate. ✅ How to Get the Correct Pixel Script Follow these steps carefully for each Website Studio project you want to connect to OTTO. 1. In the left sidebar, click OTTO SEO. 2. Click All Sites to see your list of sites. 3. Locate the site that corresponds to the Website Studio project you are working on and open it. 4. In the left sidebar under OTTO SEO, click Installation Guide. 5. Copy the pixel script shown on that page. This script contains the UUID that is uniquely tied to this specific project. 6. Go to your Website Studio project in the left sidebar under Website Studio and open the correct project. 7. Paste the pixel script into the header or footer code injection area of that project — do not use a script copied from any other project. 8. Save your changes and publish the site. 9. Return to OTTO SEO → Overview and click Scan to verify the pixel is detected correctly. ⚠️ Key Rules to Avoid UUID Errors - Never share pixel scripts between projects. Each Website Studio project must use only its own unique pixel script. - Always retrieve the script from the Installation Guide of the specific OTTO site that matches your Website Studio project. - If you have multiple Website Studio projects, repeat the steps above individually for each one — do not duplicate or reuse scripts. - After republishing a project, always run a fresh Scan from OTTO SEO → Overview to confirm the pixel is recognised. 🔍 How to Check Which UUID Is Currently Installed If you are unsure whether the correct script is installed, you can verify it quickly: 1. Open the live URL of your Website Studio project in a browser. 2. Right-click anywhere on the page and select View Page Source. 3. Use Ctrl + F (or Cmd + F on Mac) to search for uuid. 4. Copy the UUID value you find and compare it to the UUID visible in OTTO SEO → Installation Guide for that project. 5. If the values do not match, remove the existing script and replace it with the correct one from the Installation Guide. 🗂️ Managing Multiple Website Studio Projects If you manage several Website Studio projects under the same account, use this checklist to stay organised: - Label each project clearly inside Website Studio so you can easily match it to the correct OTTO site. - Before installing any pixel, navigate to the OTTO site for that specific project and retrieve its Installation Guide script fresh — never copy from a previously saved file or another project. - After installing on each project, run a Scan individually per site to confirm successful detection before moving to the next. 💬 Still Seeing the Wrong UUID Error? If you have followed all the steps above and the wrong UUID error persists, it is possible the page cache is serving an older version of the site. Try clearing your Website Studio project's cache and republishing, then run the scan again. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🎨 Fix Blog Article Styling Mismatches in Website Studio

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

🛠️ Fix Header Edits Reverting After Publishing in Website Studio

🔍 Overview If you've hidden the navigation menu or made other edits to your site's header in Website Studio, you may notice that those changes look correct in preview but revert to the original state after publishing. This is a known behaviour related to how the shared header component is published across your site, and there are clear steps you can follow to resolve it. ⚙️ Why This Happens Your site's header in Website Studio is a shared component — meaning it exists once and is applied globally across every page. Because of this, edits to the header must be saved and published in a specific way. If the correct workflow is not followed, the platform may publish the page content without carrying over the header changes, causing them to appear to revert. Common reasons this occurs include: - Publishing an individual page instead of the shared header component separately. - Saving edits locally in the editor without triggering a full site publish. - A build error occurring silently in the background, which causes the latest header version to not be applied. ✅ How to Publish Header Changes Correctly Follow these steps to make sure your header edits — such as hiding the navigation menu on specific pages — are saved and published successfully. 1. Open Website Studio and navigate to the page where you made your header edits. 2. In the editor, locate the header component. It will typically be labelled as a shared or global element. 3. Make your desired changes (for example, toggling the navigation menu visibility). 4. Save your changes using the Save button within the header component editor — do not just save the page. 5. After saving, click Publish from the top toolbar. Ensure you are publishing the entire site, not just the individual page. 6. Wait for the publish process to complete fully. A success confirmation message should appear. Do not close the tab or navigate away during this step. 7. Once published, open your live site in a new browser tab (not the preview) to verify the changes are live. 💡 Tips to Avoid This Issue - Always publish the full site after editing any shared component, including the header or footer. - Do not rely on preview alone to confirm shared component changes — preview may show edits that have not been fully committed to the build. - If the publish button appears greyed out or unresponsive after editing the header, try refreshing the editor and re-applying your changes before publishing again. - Clear your browser cache before checking the live site to make sure you are not viewing a cached version of the old header. 🚨 If the Publish Fails or Changes Still Revert In some cases, a build error may occur in the background without a visible error message being shown. If your header changes continue to revert after following the steps above, try the following: 1. Refresh Website Studio and re-open the header component editor. 2. Re-apply your changes from scratch rather than assuming the previous edits were saved. 3. Publish the site again and watch the publish progress bar to confirm it completes without interruption. 4. If you see any error banner or the publish does not complete, take a screenshot of the message for reference. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Header Navigation Dropdowns After Website Studio Import

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

🛠️ Fix Website Studio Batch Publishing

🔍 What causes batch edit failures? Website Studio processes page edits and publishing through background tasks. Large or multi-part batches may exceed execution time limits or fail while processing pages in sequence. Publishing can also fail when an image or other asset is missing, blog content was not saved, or generated build files do not pass validation. As a result, some pages may update while others keep their previous layout or styling. ✅ Check which pages were updated 1. Open Website Studio from the left sidebar. 2. Review each affected page individually. 3. Confirm whether the header, alignment, content, and other requested changes were applied. 4. Record the pages that were successful and the pages that still need changes. Do not assume that a completed task updated every page in the batch. Always verify the result page by page. 📦 Use smaller edit batches 1. Separate large requests into smaller groups, such as three to five pages. 2. Apply one type of change at a time when possible. 3. Wait for one group to finish before starting the next. 4. Refresh the affected pages and confirm the changes before continuing. For example, if only three of ten pages were updated, leave those three completed pages unchanged and retry the remaining seven in smaller groups. This reduces timeouts and makes failed pages easier to identify. 📄 Check content and asset references Before publishing, confirm that each page has saved content and that referenced images, files, and other assets still exist. Missing assets or unsaved blog sections can prevent the build from completing. - Open each affected page and save any pending content. - Replace missing or broken images and file references. - Check that blog sections are present and persisted before publishing. - Avoid removing or renaming assets while a build is running. 🚦 Resolve an orange publishing status An orange status that remains after a failed attempt usually means the background publishing task did not finish successfully. It may not update automatically until a later task completes. 1. Wait briefly for the current background task to finish. 2. Refresh Website Studio and review the status again. 3. Check the page for missing content, assets, or layout changes. 4. Retry publishing only after correcting any issues. 5. Publish a smaller group instead of resubmitting the entire batch. Avoid repeated retries while the same task is still running. Repeated submissions can create overlapping tasks and make the final status harder to interpret. 🧪 Confirm the final result - Open every page included in the batch. - Check headers, alignment, spacing, content, links, and images. - Confirm the published version, not only the editor preview. - Record any page that remains unchanged or shows an outdated status. 💬 Get help with an unresolved failure If a smaller batch still fails, note the affected page URLs, the requested changes, the current status color, and any visible error message. This information helps the team investigate the background task and build result. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🛠️ Fix Website Studio Visual Editor Save Failures

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

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

🛠️ Copilot Navigation Removal Requests Not Working

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

🛠️ Fix AI Logo Placement in Website Studio

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

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

🛠️ Fix Blog Dropdown Links in Website Studio

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

🛠️ Fix Website Studio Download and Menu Errors

🔍 Overview Some customers have encountered errors in Website Studio related to downloading a project as an HTML file and editing menus or applying layout changes. This article explains what to do if you experience either of these issues. 📥 HTML Download Error If you receive an error when attempting to download your Website Studio project as an HTML file, our team will need to investigate further on your behalf. When reaching out, please have the following ready so our team can investigate as quickly as possible: - Your project name - The exact error message you are seeing 🗂️ Menu and Navbar Changes Not Applying If you are experiencing an error when editing menus or applying layout changes in Website Studio — such as changes appearing to save but not being reflected on your site — our team will need to look into this on your behalf. When reaching out, please have the following ready so our team can investigate as quickly as possible: - Your project name - The exact error message you are seeing If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Website Studio Blog Dropdown URLs

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

🐛 Fix Website Studio Menu Dropdown and Brand Vault Issues

Overview Two known issues can affect Website Studio projects in Search Atlas: a top navigation menu item unexpectedly showing a dropdown instead of linking directly to its page, and address fields in Brand Vault not saving correctly across sessions. This article explains what these issues are and what to have ready when contacting our support team for a fix. Issue 1: Navigation Menu Item Shows a Dropdown Instead of a Direct Link If a top-level menu item — such as Services — displays a dropdown when clicked rather than linking directly to its page, this is a known navigation configuration bug in Website Studio. What to expect: Your page content is not lost. The issue is only with how the menu item is configured in the navigation settings, not with the page itself. This bug requires backend investigation to resolve correctly. What to Have Ready When Escalating - The name of the affected Website Studio project. - The exact menu item that is showing a dropdown instead of a direct link (for example, Services). - A description of when you first noticed the issue and any recent changes made to the site (such as adding new pages or publishing updates). - A screenshot or screen recording showing the dropdown behavior on your live site, if possible. Issue 2: Brand Vault Address Field Not Persisting Some customers report that address information entered in Brand Vault does not save correctly or resets after leaving the section. The Brand Vault stores your brand details — including business name, logo, colors, and address — to auto-populate fields across Website Studio projects. This is a known bug that requires investigation by our team. What to Have Ready When Escalating - The name of the Brand Vault or project affected. - The specific field or fields that are not persisting (for example, street address, city, postal code). - A description of the steps you took when entering the information and what you observed after navigating away and returning. - Any error messages displayed, along with the approximate time and date they occurred. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🐛 Fix Overlay Opacity & GBP Approval Link Issues

Overview Two separate issues have been reported by customers using Search Atlas: hero overlay opacity changes not reflecting in the Website Studio preview, and GBP draft post approval links returning a 'page does not exist' error. Both issues have been escalated to our engineering team. This article explains what is known about each issue and what to have ready when contacting support. Website Studio: Overlay Opacity Not Updating Visually Some customers reported that when adjusting the hero section overlay opacity in Website Studio, the visual preview did not update to reflect the new setting. In some cases, pages also displayed an unintended grayish color or dull gradients. What is known: The overlay opacity and gradient values are not being applied visually in the preview after adjustment. This is a known issue that has been reported to our engineering team. What to do: If you are experiencing this issue, please escalate to our support team and have the following information ready: - The name of the project and page where the issue is occurring. - The specific opacity or gradient value you are trying to apply. - A screenshot or screen recording showing the preview not updating. - The browser and operating system you are using. GBP Draft Post Approval Link Returning 'Page Does Not Exist' Customers using the GBP (Google Business Profile) draft post feature reported that the approval link provided returned a 'page does not exist' error when accessed. What is known: The GBP approval link is not loading correctly for some users. This is a known issue that has been reported to our engineering team. What to do: If you are experiencing this issue, please escalate to our support team and have the following information ready: - The GBP account or location name associated with the draft post. - The exact error message you are seeing when accessing the approval link. - A screenshot of the error if possible. - The date and time when you first encountered the issue. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Website Studio Publishing Errors

🔍 Why publishing errors happen Website Studio may fail to publish when an HTML page references files that were not uploaded with it. These can include images, stylesheets, scripts, fonts, or other assets stored in a matching folder. For example, a page named about.html may require a companion folder named about_files. Uploading only the HTML page creates incomplete website files and can cause publishing to fail. 📁 Prepare the website files 1. Find the HTML page that produces the publishing error. 2. Locate its matching referenced-files folder. For example, about.html may use about_files. 3. Keep the HTML page and its matching folder together in the same location. 4. Check that the folder name has not been changed and that referenced images, scripts, and stylesheets are inside it. 🔄 Re-upload the complete page 1. Open Website Studio from the left sidebar. 2. Open the website import or upload workflow. 3. Remove or replace the incomplete upload if the workflow provides that option. 4. Upload the HTML page and its matching _files folder together. 5. Repeat this process for every HTML page that has a matching referenced-files folder. 6. Submit or publish the website again. ✅ Check the upload before publishing - Confirm every HTML page is present. - Confirm each page's matching _files folder is present beside it. - Keep original file names, folder names, and capitalization. - Do not upload only the HTML files while leaving their referenced assets behind. - Do not rename folders after uploading unless all references in the HTML are updated. 🧪 If publishing still fails Review the HTML page for references to files that do not exist in the upload. Look for image, CSS, JavaScript, font, or other asset paths. Recreate any missing files, place them in the expected folder, and upload the page and folder together again. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🛠️ Fix Custom Code and SSL on Website Studio

🔍 Overview Two of the most common issues in Website Studio involve custom code scripts not appearing in the published HTML and SSL certificate errors on the www subdomain. This article explains what these issues are and what information to have ready when contacting support to resolve them. ⚙️ Custom Code Not Appearing in Live HTML After adding a custom code snippet and publishing your site, you may notice the script is missing when you inspect the live page source. This is typically related to how Website Studio compiles custom code during the publishing process — the script may not be included in the final HTML output as expected. Because this involves backend compilation behavior, our team will need to investigate directly. To help us resolve this quickly, please have the following ready when you reach out: - The name of the affected Website Studio site or project. - The exact custom code snippet you added. - The live URL where the script is not appearing. - The approximate time you last published the site. - A screenshot or copy of the live page source showing the script is absent. 🔐 SSL Certificate Errors on the www Subdomain When you connect a custom domain to your Website Studio site, SSL certificates must cover both the root domain and the www subdomain. Issues with how the www subdomain is routed to the platform can result in a certificate error when visitors land on the www version of your site. Resolving SSL routing for the www subdomain requires backend configuration by our team. Please have the following ready when you contact us: - Your custom domain name (both root and www versions). - The exact SSL or browser error message you are seeing. - The name of your Website Studio site or project. - Any recent changes you made to your DNS settings. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Troubleshooting Blog Post Display Errors After Publishing

This article covers a common display issue where a newly published blog post looks broken, unstyled, or incorrectly formatted on your live website. Because the exact cause can vary depending on your site's setup, our support team will need to investigate your specific configuration to identify and resolve the issue. 🔍 Common Causes - Editor mismatch: Content may have been created in one editor while the site's theme or layout is controlled by a different page builder, which can result in styling not being applied correctly. - Styling not applied on publish: Certain page builders require you to save or publish from within their own interface for styles to take effect on the front end. - Caching: A cached version of the page may be served to visitors even after changes are saved, making the post appear broken when it has already been corrected. 🛠️ What to Try First 1. Reload the post URL in a new private or incognito window to rule out a local browser caching issue. 2. Check whether the post was saved and published using the same editor or page builder that controls your site's layout and theme styling. 3. If you have access to your site's admin dashboard, verify that all relevant plugins are active and up to date. ✅ When to Escalate If the steps above do not resolve the issue, our team can investigate further. To help us assist you as quickly as possible, please have the following ready when you reach out: - The exact URL of the blog post showing the display error - A screenshot or screen recording of what the post looks like on the live site - The name of the page builder or editor plugin you are using (if known) - The date and approximate time you first noticed the issue If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Menu Nesting Changes Not Applying in Website Studio

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

🛠️ Fix Website Studio Contact Pages

📄 What the Contact page includes Website Studio is designed to generate a Contact page with a ContactHero, ContactForm, Map, and Hours section. The page may take time to finish building, especially during multipage generation. ⚠️ Why the page may look incorrect Occasionally, a Contact page can remain in the building state or finish with missing or incorrectly placed contact elements. This is a known Website Studio issue and does not necessarily mean the project was configured incorrectly. Search Atlas branding may also appear on white-label contact forms while the related improvement is still in development. 🔍 Check the page and project 1. Open Website Studio from the left sidebar. 2. Open the affected project and review the generated Contact page. 3. Check whether the ContactHero, ContactForm, Map, and Hours sections are present and correctly arranged. 4. Allow the build to finish before making changes or starting another generation attempt. 🔄 Retry or edit the result If the build completes but the page is incomplete, review the page in Website Studio and retry the page creation if that option is available. If you need to add a contact form to an existing Contact page, use the add a contact form option. This edits the existing page rather than creating a new one. Use add a contact page only when you want Website Studio to create a new Contact page. 📝 Prepare details for a report If the issue continues, record the project ID, the page status, which elements are missing or incorrect, and whether the problem occurred during single-page or multipage generation. Screenshots can also help show the final layout. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🛠️ Fix Website Studio Credits, Changes, and Images

🔍 Overview Some customers using Website Studio have noticed unexpected behavior: menus or other elements changing without a clear prompt, credits being used when they feel they shouldn't be, and blog post preview images not appearing correctly. This article explains each issue and what to do about it. ⚙️ Why Is Website Studio Making Unwanted Changes? Website Studio may in some cases apply broader changes than intended — including adjustments to navigation menus. If you are experiencing unwanted changes, escalate to our team so we can investigate. Have the following ready: - The name of the project or page affected - The exact prompt you entered - The approximate date and time the unwanted change occurred 💳 Why Are Credits Being Consumed for Edits? In Website Studio, visual/manual edits are a billable operation, so credits can be used for edits as well as for AI generation. If you believe credits were consumed in error, escalate to our team so we can review your account and determine whether a balance correction is needed. Have the following ready: - The name of the project or page affected - A description of the exact action that triggered the credit deduction - The approximate date and time the deduction occurred 🖼️ Why Aren't Blog Preview Images Displaying? Some customers have reported that blog post preview images are not appearing correctly in Website Studio. If you are experiencing this issue, escalate to our team so we can investigate. Have the following ready: - The name of the blog post or page affected - A description of what you see instead of the expected image - The approximate date and time you first noticed the issue If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Fix Website Studio Preview Image and Navigation Issues

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

🔍 Troubleshooting an Incomplete Brand Vault

This article explains how to review missing Brand Vault information when your Brand Vault is not showing as complete. 🛠️ Step-by-Step 1. Open your Brand Vault and review the information shown in each section. 2. Look for sections or fields that appear blank or incomplete. 3. Note which sections or fields appear incomplete so you can share them when requesting help. ✅ How to Confirm It Worked Review the Brand Vault and note whether it is still showing as incomplete. The available information does not confirm a self-serve fix for this status. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Broken Header Navigation Dropdowns in Website Studio

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

🛠️ Fix Website Studio Navigation Header Issues

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

🛠️ Fix Menu Text Editing Issues in Website Studio

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

🛠️ Fix Photo Opacity Not Updating in Website Studio

Overview Some customers notice that photos in Website Studio appear too dark or that adjusting the opacity filter does not seem to change the image's appearance. This article explains what to do if you experience this issue. What to Do If Your Opacity Change Is Not Appearing If changing the opacity filter on a photo in Website Studio does not update the image's appearance, the recommended course of action is to contact our support team. Because this issue may require a platform-side review of your specific project and image settings, a member of our team will need to look into it directly for you. When reaching out, please have the following information ready so our team can assist you as quickly as possible: - The name of the project or page where the affected photo is located. - A description of what you changed (for example, the opacity value you set) and what you expected to see. - A screenshot or screen recording showing the photo before and after the opacity change, if possible. - Any steps you have already tried. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fixing Website Studio Sites Showing Unpublished

You clicked publish in Website Studio, but your site still shows as unpublished. This is usually caused by a publish that did not fully finish, a stale view of the page, or a mix-up between sites or accounts. This article explains the common causes and how to resolve each one. 🔍 Why This Happens The most common reasons a site looks unpublished after you publish it are: - The publish did not finish. Closing the tab, losing your connection, or navigating away too early can interrupt the process. - An old version of the page is showing. Your browser may be displaying cached information from before you published. - Unsaved changes. Edits made right before publishing may not have been saved, so the site stays in its previous state. - The wrong site or workspace. You may have published one site while viewing another, or be signed in to a different account or workspace. - A domain connection issue. If you use a custom domain, the site may be published but the domain is not yet pointing to it correctly. - A temporary error. Occasionally a publish request fails and the status does not update. ✅ Quick Checks to Try First Start with these simple steps. They resolve most cases. 1. Wait two to three minutes after publishing. Status updates can take a short time. 2. Refresh the page using a hard refresh. On Windows, press Ctrl + F5. On Mac, press Cmd + Shift + R. 3. Log out of the platform and log back in, then reopen Website Studio. 4. Open the site in a private or incognito browser window to rule out cached data. 5. Check that you are in the correct account or workspace, and that you are viewing the same site you published. 🚀 Republish Your Site If the status has not changed, try publishing again. This often clears a publish that was interrupted. 1. Open your site in Website Studio. 2. Save any pending changes first. 3. Click the Publish button. 4. Stay on the page until you see a confirmation message. Do not close the tab or navigate away while publishing is in progress. 5. Refresh the page and check the site status again. If you see an error message, take note of the exact wording or take a screenshot. It will help our team find the cause quickly. 🌐 Check Your Custom Domain If you connected your own domain, the site may be live but not showing correctly on that domain yet. Here is what to review: - Confirm the domain is connected to the correct site. - Check that your DNS records match what the platform asks for. - Allow time for DNS changes to take effect. This can take anywhere from a few minutes to 48 hours. - Test the site on the default platform URL, if one is available, to see whether the problem is only with the custom domain. 🧹 Clear Your Browser Cache A cached copy of the page can make a published site look unpublished. To clear it: 1. Open your browser settings. 2. Find the option to clear browsing data. 3. Select cached images and files. 4. Clear the data, then reload Website Studio. You can also try a different browser or device to confirm whether the issue is related to your browser. 💡 Tips to Avoid This in the Future - Save your work before you click publish. - Stay on the page until the publish confirmation appears. - Use a stable internet connection while publishing. - Double-check the site name before publishing if you manage more than one site. - After publishing, do a hard refresh to see the latest status. 💬 Still Showing Unpublished? If you have tried the steps above and the site still shows as unpublished, our team can take a closer look. To help us resolve it faster, have the following ready: - The name of the site - The time you last tried to publish - Any error message or screenshot - Whether you use a custom domain If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🛠️ Why Publication Media Websites Show Inactive

🔍 What Does Inactive Status Mean? In the Publication Media section, each website is shown with a status. An inactive status means the website is not currently available for selection or use in your account. When only one site is inactive, it is usually a site-specific issue. When all websites show as inactive at once, the cause is usually something broader, such as your account, your plan, a temporary loading problem, or a platform-wide update. The good news is that this is rarely permanent, and most cases can be resolved with a few quick checks. 🧭 Common Reasons All Websites Appear Inactive - Temporary loading issue: The page did not fully load, or your browser is showing outdated information. - Subscription or plan status: Your plan may have expired, been changed, or have a pending payment issue. - Plan or credit limits: Some features depend on your plan or available balance. If these are used up, options may appear unavailable. - Wrong project or account selected: You may be viewing a project or workspace that does not have Publication Media access. - Permissions: Your user role may not have access to this feature. - Platform update or maintenance: The list may be refreshing, and the sites may return to active shortly. - Browser issues: Cached data, extensions, or ad blockers can interfere with how statuses are displayed. ✅ Step-by-Step: How to Check and Fix It 1. Refresh the page. Do a hard refresh (Ctrl+Shift+R on Windows, Cmd+Shift+R on Mac) to load the latest information. 2. Log out and log back in. This refreshes your session and account details. 3. Confirm your project. Check that you are in the correct project or workspace using the selector in the platform. 4. Review your subscription. Open your billing or account settings and make sure your plan is active and no payment is pending. 5. Check your user role. If you are a team member, ask your account owner to confirm you have access to Publication Media. 6. Clear your browser cache. Then reload the platform and check the status again. 7. Try another browser or an incognito window. Disable extensions such as ad blockers while testing. 8. Wait a few minutes and check again. If the platform was refreshing the website list, the status may update on its own. ⚠️ Things to Keep in Mind - Inactive status does not mean your account or content has been deleted. - Previously completed or scheduled work is not removed because sites appear inactive. - Avoid creating duplicate orders or requests while sites are inactive. This can cause confusion later. 📝 Information to Gather Before Contacting Support If the steps above do not resolve the issue, having these details ready helps us find the cause faster: - A screenshot of the Publication Media page showing the inactive status - The name of the project or workspace you are using - The approximate date and time you first noticed the issue - Whether you recently changed your plan, payment method, or team settings - The browser and device you are using 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team. 💡 Tips to Avoid This in the Future - Keep your subscription and payment details up to date. - Use a current version of Chrome, Edge, Firefox, or Safari. - Make sure team members have the correct roles for the features they need. - If you see an unexpected status, refresh and recheck before taking other actions.

🛠️ Fix Website Studio Container Connection Failures

🛠️ Fix Website Studio Generation and Preview Failures

🛠️ Fix Dropdown Menu Issues in Website Studio