📖 Features & How-To

🔍 Understanding the Indexing Process for Cloud Stacks and Press Releases in Landing Page Studio

🧱 Website Studio in Search Atlas

🧱 Website Studio Quotas, Usage & HDC Reallocation in Search Atlas

How Website Studio Credits Work Website Studio in Search Atlas allows users to build full multi-page websites — not just single landing pages. To support this expanded capability, Website Studio uses a credit-based monthly quota system that determines how much you can build within your plan. This article explains: - How the updated quota structure works - What actions consume credits - What does not consume credits - What happens when you reach your limit - How to handle credits consumed by failed operations - How to reallocate Hyperdrive Credits (HDC) into your Website Studio quota 📊 Website Studio Credit Allocation by Plan Each plan includes a fixed number of Website Studio credits per month: - Starter → 20 credits - Growth → 40 credits - Pro → 60 credits - Agency → 100 credits Your credits reset automatically every month based on your billing cycle. Previously created pages and websites are not removed when credits reset. 🏗️ What You Can Build - Single landing pages - Multi-page websites - Full site builds with structured navigation 🔢 What Consumes Website Studio Quota Credits are deducted based on actual usage intensity. Approximate usage cost: - Build new landing page → ~3–6 credits - Edits → 0.5–1 credit - Multi-page builds → Variable (depends on size and generation complexity) - Site clone operations → Variable, based on size of cloned site The exact credit usage depends on page length, content volume, layout complexity, and AI generation workload. ✅ Important Rule — Failures and Credit Deduction If a command fails cleanly, no quota is deducted. You are only charged credits for successful generation actions. Exception: In rare cases — particularly during clone operations or generation tasks that encounter a 500 server error — credits may still be deducted by failed attempts. If you notice your credit balance has dropped without successful output: 1. Note the approximate time and operation (e.g., "site clone failed with 500 error"). 2. Contact Search Atlas support. 3. Our billing team will verify the failed attempts and restore the incorrectly consumed credits. This restoration process has been confirmed in resolved support cases. 🚫 What Does NOT Consume Credits - Viewing existing Website Studio projects - Managing previously created websites - Publishing changes (only the edit generation consumes credits) Once a page or website exists, you retain full access to it. ⏳ Monthly Reset Behavior Credits refresh automatically each month. If you use all available credits: - You regain your full plan allowance at the next billing cycle - All previously created pages and websites remain fully accessible - Nothing is paused, removed, or disabled Example: If you are on the Starter plan (20 credits) and use all credits building multiple pages, next month you will again have 20 credits — while keeping everything you already built. 🔁 Reallocating Hyperdrive Credits (HDC) to Website Studio If you need more Website Studio (LPS) credits before your next reset, you can request a reallocation of unused Hyperdrive Credits (HDC) into your Website Studio quota. - Conversion ratio: 1 HDC = 1 Website Studio (LPS) credit - How to request: Contact Search Atlas support and specify how many HDC you want reallocated - Effect: The requested HDC are consumed from your Hyperdrive balance and added to your Website Studio quota Example (confirmed support case): A customer with 43 LPS credits requested reallocation of 12 HDC. After reallocation, their Hyperdrive balance decreased by 12, and their Website Studio quota increased from 43 to 55. Reallocation is a manual process handled by the billing team and is generally completed within one business day. 🚨 What Happens When You Reach the Limit When your Website Studio credits are fully used: - All existing projects remain accessible - No websites are removed - No pages are unpublished - Editing and publishing continue to work (unless new generation is required) - You simply cannot generate new content until credits refresh — or until you reallocate HDC (see above) This behavior is expected and does not indicate a system issue. 🛠️ Troubleshooting: Credits Dropped Unexpectedly If your Website Studio credit balance drops without a corresponding successful build: 1. Check recent activity for failed clone attempts or generation errors (especially 500 errors). 2. Do not retry repeatedly — each failed attempt may compound the issue. 3. Contact support with the timestamp and a description of what you were attempting. 4. Our billing team will review and, if appropriate, restore the credits that were consumed by the failed operations. 🔄 About Credit Cost Optimization The credit cost per action listed above reflects the current usage structure. As we continue optimizing AI models, infrastructure, and generation efficiency, the cost per action may decrease over time.

🌐 Connecting a Website Studio Site to a Custom Domain (No Plugin Needed)

You can connect your own custom domain to a Website Studio site directly inside Website Studio — no plugin, add-on, or third-party tool required. This guide shows you how to publish your site, connect your domain, add the CNAME record, and activate SSL for secure HTTPS access. The steps work the same across most domain providers, including Hostinger, GoDaddy, Namecheap, and Cloudflare. 💡 Do I Need a Plugin to Connect a Custom Domain? No. Connecting through Website Studio → Custom Domains is the built-in method. You point your domain to Website Studio with a single CNAME record in your domain provider's DNS settings, and Website Studio handles the SSL certificate for you. There is nothing extra to install. 🚀 Step 1 — Confirm Your Website Is Published Before connecting a domain, your Website Studio project must be published. Inside Website Studio, confirm the project shows a public URL. - Example URL: https://yourproject.searchatlas.app Open this link in a browser. If your website loads live, you're ready to connect your custom domain. 🔗 Step 2 — Open Custom Domain Settings in Website Studio From the Website Studio dashboard, complete these steps in order: 1. Open your project. 2. Click Custom Domains. 3. Click Connect Domain. 4. Select Existing Domain. 5. Enter your domain name (example: yourdomain.com). 6. Click Continue. Website Studio then generates the DNS configuration you need for the next step. It displays a CNAME record with a target URL (for example, abc123xyz.preview.builder.searchatlas.com). Copy this target value exactly — you'll paste it into your domain provider's DNS settings in Step 3. ⚙️ Step 3 — Add the CNAME Record in Your DNS Settings A CNAME record points your domain to another address. Add the CNAME record Website Studio generated inside your domain provider's DNS management panel. You can find the CNAME target value in Website Studio on the Custom Domains screen after you click Continue in Step 2. It is shown as the Target (or Points to) value, typically a URL ending in .searchatlas.app or .preview.builder.searchatlas.com. Copy it exactly. Typical location in your domain provider: Domain Dashboard → DNS Settings → DNS Records. To add the record: 1. Open your domain provider's DNS management panel. 2. Click to add a new DNS record and choose CNAME as the type. 3. In the Name field, enter @ for the root domain. 4. In the Target (or Value / Points to) field, paste the Website Studio target value exactly. 5. Save the record. DNS configuration example - Type: CNAME - Name: @ (the root domain, for example yourdomain.com) - Target: yourproject.searchatlas.app (the Website Studio URL generated by the platform) The @ symbol represents the root domain (example: example.com). 🌐 Configuring www Subdomains in Website Studio If you want your site to work with www (for example, www.yourdomain.com), add a separate CNAME record for the www subdomain in your domain provider. Point it to the same Website Studio target value you used for the root domain. If www still shows SSL errors after adding the CNAME record, contact support — the subdomain may require a separate backend registration step. ⚠️ Important DNS Notes Before You Connect Some hosting dashboards already contain records that can conflict with the Website Studio configuration, such as existing A records or default CNAME records. Remove these so your domain resolves correctly. If you are unsure about removing a record, contact your domain provider's support team before making changes. ⏳ Step 4 — Wait for DNS Propagation After you add the CNAME record, the change needs to propagate across the internet. - This can take a few minutes. - It can take up to 24–48 hours, depending on your provider. - Some providers, such as Hostinger, update DNS within minutes. 🔒 Step 5 — Generate the SSL Certificate Once the CNAME record is added, return to Website Studio and click I have added the DNS records. Website Studio generates an SSL certificate so your site loads securely over HTTPS. - Secure URL example: https://yourdomain.com SSL generation usually takes a few minutes, and up to about 1 hour depending on the system queue. When it finishes, your site loads securely at your custom domain. 🛠️ Troubleshooting: "Your Connection Is Not Private" This message usually appears while: - DNS propagation is still in progress, or - The SSL certificate has not finished generating. Wait a few minutes, then refresh the page. Once propagation and SSL generation finish, your site loads securely at your custom domain over HTTPS. 🛠️ Troubleshooting: Connection Fails Despite a Correct CNAME If the connection fails even though your CNAME record is correct, check your domain provider's DNS proxy setting (for example, Cloudflare's orange cloud icon). Disable any DNS proxy or CDN before adding the CNAME record, then re-enable it after validation succeeds. 🛠️ Troubleshooting: SSL Certificate Not Provisioning If your SSL certificate is stuck or not provisioning, work through these steps in order: 1. Verify the CNAME record is exactly correct and has propagated (~10 minutes). 2. Ensure no DNS proxy is interfering. 3. Wait up to 24–48 hours for Let's Encrypt validation. 4. Check that the domain is still published. If it is still stuck after these steps, contact support. 🎯 You've now connected your custom domain to Website Studio without any plugin. Publish your site, add the single CNAME record, and activate SSL so visitors reach your site at your own URL. If the secure page doesn't load right away, give DNS and SSL a little time to finish, then refresh.

How It Works: Cloud Stacks

☁️ What Cloud Stacks Are Cloud Stacks let you create AI-generated web pages and publish them across multiple high-authority cloud domains. Each page links back to your target URL from these trusted providers, helping increase your site's visibility and authority. ⚙️ What You Need Before creating a Cloud Stack, gather the following: 🏢 A Brand Vault — provides business identity, brand voice, and context for content generation 🤖 An OTTO or GBP project — to bind the cloud stack to 🔗 A target URL — the page the cloud stack content will link to 🎨 An HTML template — the visual design for the generated page 🎯 SEO keywords — up to a few core terms the content should target 💳 Hyperdrive Credits (HDC) — to cover generation and publishing costs 🚀 The Workflow 1️⃣ Create Choose your project (OTTO or GBP), then provide: 🔗 Target URL 🎯 SEO keywords ✍️ AI instructions (tone, focus, key points) 🎨 HTML template from the available library Brand information from your Brand Vault informs the content generation. 2️⃣ AI Builds the Content The AI generates a fully styled HTML page based on your instructions, keywords, brand information, and template. Each cloud provider receives a unique version of the page to maintain editorial diversity. 📊 Status: Pending → Generating → Generated 3️⃣ Review & Edit Preview the generated page and: 👀 Review the copy 🎨 Make visual edits through the editable preview URL 🔄 Regenerate content if you want to refine the instructions 4️⃣ Choose Cloud Providers Select which cloud providers to publish to. Each provider hosts your page on its own trusted domain and creates a separate live URL that links back to your target URL. 5️⃣ Publish Confirm your content and review the HDC cost before deploying to your selected providers. 📊 Status: Publishing → Published When publishing completes, all live URLs appear in your dashboard. 📈 What You Get ☁️ Multiple live pages hosted on high-authority cloud domains 🔗 Links to your target URL from trusted cloud providers 🏢 Increased brand visibility across credible cloud infrastructure 📊 Authority signals from diverse, high-quality sources 🎯 Topical authority reinforcement for your target page 📋 A centralized dashboard tracking every live URL and status ✅ Best Practices 🏢 Keep your Brand Vault complete and up to date for consistent, on-brand content 🎨 Choose a template that matches your page's purpose (service page, location page, product page, etc.) 🎯 Use focused, intent-aligned keywords rather than broad terms ✍️ Write detailed AI instructions, including desired tone, key messages, and topics to emphasize or avoid 👀 Always review the generated page before publishing 🌐 Distribute across multiple providers to maximize link diversity and reach

🚀 Deploying Websites Created with Website Studio

Websites generated with Website Studio in Search Atlas are built on a modern static-site toolchain (HTML plus compiled JS/CSS assets), not a traditional WordPress theme. Search Atlas can host your Website Studio site directly and publish it to several destinations for you, including WordPress, HubSpot, Webflow, GoHighLevel, Shopify, and Cloudflare Pages. This article instead covers the self-hosted path: exporting your site and deploying the compiled files yourself, for teams that want full control over their own infrastructure. This article explains what a Website Studio export contains, how to test it locally, and what type of hosting environment is required if you choose to self-host instead of using Search Atlas's built-in publishing options. 🧱 Understanding How Website Studio Exports Work When you export a site from Website Studio, you get a static bundle — an index.html file plus compiled assets, css, js, and images folders. This export is meant for teams that want to self-host on their own infrastructure — VPS servers, containers, cloud hosting environments, or static hosting platforms — rather than using Search Atlas's built-in publishing (which does support direct WordPress publishing, among other destinations). If you're not comfortable deploying web applications yourself, using Search Atlas's built-in publishing to WordPress or another connected platform is simpler, or you may need help from a developer or DevOps engineer for the self-hosted path. 📥 Step 1 — Download the Website Files After generating a site in Website Studio, download the project files. You'll receive a compressed archive containing the full website export. Once extracted, the folder contains the application structure — an index.html file plus assets, css, js, and images folders. 💻 Step 2 — Open the Project in a Code Editor To test the exported website locally, open the project folder in a code editor such as Visual Studio Code, WebStorm, Sublime Text, or Atom. In Visual Studio Code, click File → Open Folder and select the folder containing your website files. 🖥 Step 3 — Start a Local Server Website Studio exports must run on a web server, even for local testing. The fastest way is Python's built-in HTTP server. With Python 3 installed, open a terminal inside the project folder and run python3 -m http.server 4173. Your terminal should show that it's serving HTTP on port 4173, meaning the website is now running locally on your machine. 🌐 Step 4 — Open the Website in Your Browser Open your browser and navigate to http://localhost:4173. Your Website Studio export should load, letting you test the layout, verify functionality, inspect the files, and prepare the project for deployment. 🚀 Step 5 — Deploy the Website Once the export is tested locally, deploy it to a hosting environment of your choice. Common options include VPS hosting (for example, DigitalOcean, AWS EC2, Linode, or Vultr), container deployment (Docker or Kubernetes), static hosting (Netlify, Vercel, Cloudflare Pages, or GitHub Pages), or traditional web servers (Nginx or Apache). A developer may configure the deployment depending on your infrastructure. If you'd rather not self-host, remember Search Atlas can publish the same site directly to WordPress or another connected platform without this manual export process. ⚠️ Self-Hosted Exports vs. Built-In Publishing A Website Studio export is a static bundle, not a WordPress theme or plugin — you can't upload or paste the exported files directly into a WordPress install. If you want the site on WordPress, use Search Atlas's built-in WordPress publishing instead of the manual export/self-host path described in this article. 🌐 Deploying Without Being a Developer If you're not a developer and want to self-host anyway rather than using Search Atlas's built-in publishing, you can still deploy your Website Studio export using common hosting services. Most traditional hosting providers, such as GoDaddy, Namecheap, Hostinger, Bluehost, SiteGround, and DreamHost, let you upload a website using File Manager or FTP, which works well with Website Studio exports. To do this: export and extract your Website Studio project on your computer, log into your hosting account, open File Manager, and navigate to your website's root directory (usually called public_html or www). Upload all files from your Website Studio folder into that directory, making sure index.html is in the root folder, then visit your domain to confirm the site is live. Do not upload the ZIP file itself — extract it first, make sure index.html is in the root directory, and upload the entire folder structure, not just the HTML file. If you want the easiest self-hosted deployment experience, we recommend Netlify, Vercel, or Cloudflare Pages, which let you drag and drop your site files and publish instantly. 🛠 Troubleshooting The site doesn't load on localhost — check that Python 3 is installed, that the command was run inside the correct folder, and that the port matches the URL (http://localhost:4173). Port 4173 is already in use — use another port, for example python3 -m http.server 5000, then open http://localhost:5000. The site loads but styles are missing — this usually happens when the site is opened without a server; make sure it's running via python3 -m http.server 4173 and accessed through http://localhost:4173. The browser shows a blank page — possible causes include JavaScript errors, a missing assets folder, or an incorrect deployment path. Check the browser console for errors (right-click → Inspect → Console). Python command not found — your system may not have Python installed; check with python3 --version, and if needed, download it from python.org. I don't know how to deploy a web application — you may need help from a developer, a DevOps engineer, or your hosting provider, or you can skip self-hosting entirely and use Search Atlas's built-in publishing to WordPress or another connected platform instead. 🧩 When Should You Use the Self-Hosted Export? The self-hosted export path is ideal when your team wants full control over infrastructure — for example, running on your own cloud environment, a custom CDN setup, or alongside an existing DevOps pipeline. If you just want your Website Studio site live quickly without managing hosting yourself, use Search Atlas's built-in publishing (including WordPress) instead. To self-host: download the project files, open the project folder in a code editor, run a local server using Python, open the site via localhost, and deploy it to your server or hosting platform. 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.

🏗️💻 Local Landing Pages in Search Atlas (Now via Website Studio)

The AI Landing Page Builder that used to live inside OTTO has been replaced by Website Studio, Search Atlas's current landing page experience. If you open your OTTO project looking for the AI Landing Page Builder, you will now see a prompt directing you to Website Studio instead. Website Studio still makes it simple to create fully functional landing pages for local businesses, and it adds one-click publishing to more platforms than before. 🌐 Where to Find It Now Open your OTTO project and look for the Website Studio option in the project sidebar, in the space where the AI Landing Page Builder used to appear. Selecting it takes you into the current landing page creation experience. 🚀 One-Click Publishing Once a landing page is generated, Website Studio supports one-click publishing to WordPress, HubSpot, Webflow, GoHighLevel, and Shopify, no coding or design skills required. ✏️ Editing Image Alt Tags - Hover over the image you want to update - Click the pencil icon to open the alt tag editor - Make your changes and click Save Changes ❓ FAQs Do I need coding or design skills to create landing pages? No. Website Studio is fully automated and requires no coding or design expertise. Can I regenerate a landing page if I don't like the first version? Yes, use the regenerate option to instantly generate a new version. 📈 Closing Note With Website Studio, you can generate, customize, and publish professional-quality local landing pages in minutes. Whether you're targeting new services or expanding into new local markets, this tool gives you the power to scale your online presence with ease. 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.

🚀 The 3 Easiest Ways to Publish a Website Studio Site (No Developer Required)

Not everyone deploying a Website Studio project is a developer — and that's completely fine. While Website Studio generates a standalone web application, you don't need advanced infrastructure or DevOps knowledge to get your site online. Website Studio exports your project as a static site (HTML, CSS, and JavaScript files), which can be hosted on any platform that supports static file hosting. Many modern hosting platforms make deployment extremely simple, allowing you to publish your site in just a few minutes by uploading your files. In this guide, we'll show you the easiest ways to launch a Website Studio site using beginner-friendly hosting platforms such as Netlify, Vercel, or traditional hosting providers like GoDaddy. ⚠️ Important — HTML download option is deprecated: The HTML download/export option in Website Studio is deprecated and its removal is actively pending release — it is likely to become unavailable very soon. The steps in this guide depend on uploading an extracted export folder, so this workflow may no longer be available in your account. Check your Website Studio UI immediately to confirm whether the HTML download/export option is still present; for documentation purposes, treat the feature as effectively unavailable. If it is not available, contact support before proceeding. Last verified: 2026-05-29. Note on Content Genius: Content Genius articles can be published directly to Website Studio sites, as well as to WordPress and through Universal CMS connectors (for example Shopify and HubSpot). Note on OTTO SEO: If you are using OTTO SEO with your Website Studio site, note that OTTO deployments may not function correctly when the site is hosted on third-party platforms (Netlify, Vercel, GoDaddy, etc.) — no CMS Connector or Cloudflare Worker gets configured for externally hosted sites. Contact support before choosing a third-party host if you rely on OTTO SEO automation. 1️⃣ Publish with Netlify (Easiest Method) Netlify allows you to deploy your Website Studio project with a simple drag-and-drop upload of the unzipped export folder (not the ZIP file itself). Steps 1️⃣ Go to https://netlify.com 2️⃣ Create a free account 3️⃣ From the dashboard click: Add new site → Deploy manually 4️⃣ Drag and drop the extracted (unzipped) Website Studio folder — make sure index.html sits at the root of the folder you drop in. 5️⃣ Netlify will automatically: - Upload your site - Generate a temporary domain - Deploy it instantly Your site will usually be live in seconds. Note: Publishing may occasionally take longer than expected. A recent fix resolved an extended delay bug, but if your site does not appear live within a few minutes, wait and refresh — do not click Publish again, as the process may still be running in the background. Contact support if the delay persists. Example: https://yourproject.netlify.app You can later connect your custom domain. About custom domains and DNS: DNS propagation can take up to 2+ hours after you point your domain to your new host. During this period you may see a temporary DNS Failed or similar error-like status — this is normal and does not mean something is broken. Wait for propagation to complete before assuming something went wrong or retrying setup. 2️⃣ Publish with Vercel (Fast & Reliable) Vercel is another popular platform for hosting modern web applications. Unlike Netlify, Vercel's standard dashboard flow is built around Git repository imports rather than drag-and-drop file uploads, so deploying a Website Studio export takes a little more setup. Steps You have two supported options: Option A — Vercel CLI (direct upload of static files): 1️⃣ Install the Vercel CLI: npm i -g vercel 2️⃣ Open a terminal inside your extracted (unzipped) Website Studio folder, where index.html is located. 3️⃣ Run: vercel 4️⃣ Follow the prompts and accept the defaults. When asked about a framework, choose Other (it is a plain static site, no build step is required). Option B — Git-based deploy: 1️⃣ Go to https://vercel.com 2️⃣ Create a free account 3️⃣ Push your extracted Website Studio folder to a GitHub, GitLab, or Bitbucket repository. 4️⃣ Click: Add New → Project 5️⃣ Import the repository, leave the framework as Other, and click Deploy. Vercel will publish the site automatically. Example URL: https://yourproject.vercel.app 3️⃣ Publish with Traditional Hosting (GoDaddy, Hostinger, etc.) If you already have hosting with providers such as: - GoDaddy - Hostinger - Bluehost - SiteGround - Namecheap You can upload your Website Studio files manually. You will upload the unzipped contents of the export — not the ZIP file. The root file your visitors load is index.html, and it must sit directly inside public_html alongside the asset folders. Steps 1️⃣ Log into your hosting dashboard 2️⃣ Open File Manager 3️⃣ Navigate to the folder: public_html 4️⃣ Upload the extracted Website Studio files (or upload the ZIP and use the host's Extract action so the files land directly in public_html). Example structure: public_html ├ index.html ├ assets ├ css ├ js └ images 5️⃣ Visit your domain: https://yourdomain.com Your Website Studio site should now be live. ⚠️ Common Mistakes Avoid these frequent issues: ❌ Uploading the ZIP file instead of extracting it ❌ Uploading only index.html without the asset folders ❌ Uploading files outside of public_html If your published site appears as a blank page: a bug causing blank pages on load was recently resolved, so first try a hard-refresh, clear your browser cache, or open the URL in an incognito/private window. If the issue persists, try re-publishing the site, and contact support if the blank page continues to appear. If publishing appears to hang or take too long: a recent fix resolved an extended publishing delay bug. Wait a few minutes and refresh the page before retrying — do not click Publish again, as the process may still be running in the background. Contact support if publishing still does not complete. 🧠 Quick Tip Website Studio generates static websites, which means they are compatible with most hosting platforms. If a hosting provider allows you to upload HTML files, it will usually support Website Studio sites. 🏁 Final Recommendation For most users, we recommend: Netlify or Vercel because they offer: - Instant deployment - Free hosting tiers - Automatic SSL certificates - Global CDN performance These platforms allow non-technical users to publish Website Studio projects in just a few minutes. Publishing a Website Studio site doesn't have to be complicated. Whether you choose a drag-and-drop platform like Netlify, a fast deployment service

📧 Add a Recipient Email to Website Studio Forms

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

🌐 Connect a Custom Domain in Website Studio

🗺️ Overview Connecting a custom domain to your Website Studio site requires updating DNS records at your domain registrar (e.g., GoDaddy, Namecheap, Cloudflare). Once the correct records are in place, Search Atlas validates them automatically. This article walks you through the full setup process and covers the most common reasons a connection fails. 🔍 Before You Begin - You must have admin or editor access to your domain registrar account. - DNS changes can take up to 48 hours to propagate globally — some registrars are faster, but delays are normal. - Only one custom domain can be connected per Website Studio site. ⚙️ Step 1 — Open the Domain Settings in Website Studio 1. Log in to Search Atlas and navigate to Website Studio using the left sidebar (or go to /website-studio). 2. Open the site you want to connect a domain to. 3. Click Settings, then select Custom Domain. 4. Enter your domain name (e.g., www.yourdomain.com) and click Connect Domain. 5. Search Atlas will display the DNS records you need to add. Keep this screen open — you will need these values in the next step. 📋 Step 2 — Add the DNS Records at Your Registrar Log in to your domain registrar and locate the DNS Management or DNS Zone Editor section. Add the records shown in Website Studio exactly as displayed: - CNAME record — Points your domain (e.g., www) to the Search Atlas hosting address provided on screen. - A record (if required) — Points the root domain (@) to the IP address shown. Not all setups require this; follow what is shown in your dashboard. Tips for common registrars: - GoDaddy: DNS Management → Add Record → choose type CNAME or A. - Namecheap: Advanced DNS tab → Add New Record. - Cloudflare: DNS → Records → Add Record. Set the proxy status to DNS only (grey cloud) — do not enable the Cloudflare proxy (orange cloud) as this can break validation. - Google Domains / Squarespace DNS: DNS → Manage custom records → Add record. ✅ Step 3 — Verify the Connection in Website Studio 1. Return to the Custom Domain settings in Website Studio. 2. Click Verify DNS (or Check Status). 3. If your records have propagated, the status will update to Connected and your site will go live on the custom domain. 4. If the status still shows Pending or Error, wait a few hours and try again — propagation time varies by registrar. 🛠️ Troubleshooting Common DNS Errors If you have waited more than 48 hours and the domain still fails to connect, work through the checks below: - Typo in the CNAME or A record value — Copy and paste the values directly from the Website Studio dashboard; do not retype them manually. - Cloudflare proxy enabled (orange cloud) — Switch to DNS only (grey cloud) and save. Re-run verification. - Old or conflicting records — Delete any existing A or CNAME records pointing to another host for the same subdomain before adding the new ones. - TTL set too high — If you recently changed records, a high TTL (e.g., 86400 seconds) means the old value is still cached. Lower the TTL to 300, save, and allow time for the cache to clear. - Root domain vs. www mismatch — Make sure you are connecting the exact format you entered in Website Studio (e.g., if you entered www.yourdomain.com, the CNAME must be on the www subdomain, not the root @). - Domain privacy / WHOIS guard conflicts — Some registrars' privacy features can interfere. Check your registrar's documentation to confirm privacy settings do not block DNS updates. ⏱️ How Long Does Propagation Take? DNS propagation is controlled by the global internet infrastructure, not by Search Atlas. Most domains connect within 15 minutes to 4 hours. In rare cases it can take the full 48 hours. You can check real-time propagation status using a free tool like dnschecker.org — search for your domain and confirm the CNAME value matches what Website Studio provided. 💬 Still Need Help? If you have followed all the steps above and your domain still will not connect after 48 hours, our team can check the DNS configuration 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. Additional Notes TTL: Set to Auto or 3600 (1 hour) to allow changes to propagate quickly. SSL certificate issuance is part of the domain connection process — once DNS propagates, return to Website Studio to enter your custom domain and enable SSL.

🚀 Using the Instant Indexing Toggle in Landing Page Studio

Enable Instant Indexing in the Landing Page Studio Publish flow to automatically submit your custom-domain URLs to Google — no manual submission or organic crawl wait required. Available as of the LPS-102 release. 🔍 What Instant Indexing Does The Instant Indexing toggle submits your published URLs directly to Google via RapidURL Indexer — an automated URL submission service that Search Atlas uses to relay your URLs to Google's indexing API. Without it, Google discovers new pages on its own schedule, which can take days or weeks. - Submitted URLs are typically crawled within 24–48 hours — significantly faster than organic discovery. - Submission accelerates discovery but does not guarantee indexing — Google controls the final crawl and index decision. ⚙️ Requirement: Custom Domain The Instant Indexing toggle only appears when your site is published to a custom domain. If your site is not connected to a custom domain, the toggle will not appear in the Publish flow. Connect a custom domain to your Landing Page Studio site first, then return to publish. 🖱️ How to Enable Instant Indexing When Publishing in Landing Page Studio 1. Open Landing Page Studio and navigate to the site or page you want to publish. 2. Click Publish to open the Publish flow. 3. In the Publish dialog, locate the Instant Indexing toggle. 4. Enable the toggle to turn on automatic URL submission. 5. Click Publish to confirm and go live. Once publishing completes, Landing Page Studio submits your custom-domain URLs to Google via RapidURL Indexer automatically. No additional steps are required on your end. Toggle persistence: The Instant Indexing toggle applies only to the current publish action. Re-enable the toggle each time you open the Publish flow to submit URLs for future publishes. 📊 What to Expect After Enabling Instant Indexing After you publish with Instant Indexing enabled: - Your custom-domain URLs are submitted to Google through RapidURL Indexer. - A confirmation message appears in the Publish dialog, and the submission status is recorded in your Landing Page Studio publish history. - Google typically crawls submitted URLs within 24–48 hours, though timing can vary depending on Google's queue and your site's authority. - Pages index faster than through organic discovery, but submission does not guarantee indexing — Google makes the final crawl and index decision. ⚠️ Troubleshooting: Instant Indexing Toggle Not Visible in the Publish Flow If you do not see the Instant Indexing toggle in the Publish flow, check the following: - No custom domain connected: The toggle only appears for sites published to a custom domain. Go to your site settings, connect a custom domain, then return to the Publish flow. - Publishing to a non-custom URL: Instant Indexing is not supported for Search Atlas-hosted or subdomain-only URLs — a custom domain is required. 🛠️ If Instant Indexing Submission Fails If your URLs are not submitted successfully, use the steps below to diagnose and resolve the issue: - Check submission status: Open the publish history in Landing Page Studio to see whether the submission succeeded, failed, or is still pending. - Common failure causes: - Your custom domain is not yet verified with Google Search Console. - DNS records for your custom domain are still propagating. - Google's indexing API temporarily rejected the request due to rate limits. - Fallback option: Manually submit the affected URLs through Google Search Console using the URL Inspection tool, then click Request Indexing. 🎯 You now know how to use the Instant Indexing toggle in Landing Page Studio to give Google an immediate signal about your newly published pages. Make sure your site is connected to a custom domain before opening the Publish flow.

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

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

📋 Website Builder: Homepage & Project Dashboard Overview

The Website Builder's redesigned Homepage and Project Dashboard is your single starting point for all landing page projects. Use it to create a new project or return to an existing one. 🖥️ What the Website Builder Homepage Dashboard Shows When you open the Website Builder, the dashboard displays one of two states depending on whether you have existing projects: - Empty state — shown on your first visit or when no projects exist yet. Displays a centered prompt and button to guide you toward creating your first project. - Project list view — shown once at least one project exists. Displays all your landing page projects so you can access and manage them. Both states include the Create Project button as the primary entry point for starting new work. 🚀 Navigating the Empty State (No Projects Yet) If you have not created any projects yet, the Website Builder opens to the empty state screen. You will see a centered prompt with a clear call to action. 1. Open the Website Builder from the Search Atlas left sidebar → Website Studio. 2. On the empty state screen (Hi, CSM. What will we get done today?), click Create Project. 3. Enter a name for your project and confirm to open the editor. Once your first project is created, the dashboard switches to the project list view on your next visit. 🗂️ Using the Project List View Once you have at least one project, the Homepage displays your full project list. You can see all your landing page projects at a glance and access them directly from this screen. - Click any project card to open that project in the Website Builder editor. - Scroll down to see all your projects if the list extends below the visible area. ➕ Creating a New Project from the Dashboard You can start a new project at any time from the project list view — you are not limited to doing so only from the empty state. 1. From the project list view on the Home page (Hi, CSM. What will we get done today?), click Create Project in the dashboard. 2. Enter a name for your new project. 3. Confirm to open the new project in the editor. The project is added to your project list immediately. 🎯 You now know how to navigate the Website Builder's redesigned Homepage and Project Dashboard — from the empty state on your first visit through managing a growing project list. Open any project card from the dashboard to continue editing, or click Create Project to start your next landing page.

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

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

🌐 Website Studio Hosting, DNS, and Feature Guide

🗺️ What This Article Covers This guide answers the most common questions about Website Studio — including how to share pages with a custom URL, how hosting and billing work, and what the platform can and cannot do today. 🚀 How to Access Website Studio Go to Left Sidebar → Website Studio (URL: /website-studio). From there you can: - Generate a PPC Landing Page - Clone an Existing Page - Build a Local Website - Import a project - Create a Brand Vault 🔗 Sharing Your Page With a Custom URL Every Website Studio page gets a free Search Atlas preview URL the moment it is published. To share it under your own domain instead, follow these steps: 1. Purchase or identify your domain — you must own the domain through any registrar (GoDaddy, Namecheap, Google Domains, etc.). 2. Open the custom domain settings inside your Website Studio project and copy the DNS records provided. 3. Add the DNS records at your registrar — typically a CNAME or A record pointing to Search Atlas servers. 4. Wait for propagation — DNS changes can take anywhere from a few minutes to 48 hours to take effect globally. The platform will show a propagating status while it waits; this is expected. 5. SSL is provisioned automatically after DNS is verified. If your domain shows as verified but SSL has not activated after 72 hours, please contact support using the chat widget (details at the bottom of this article). Important: Do not remove or alter the DNS records while propagation is in progress. Changing records mid-process resets the clock. ⚠️ Known DNS and SSL Limitations Please be aware of the following current platform behaviours: - Silent domain disconnection: In some cases a previously connected domain can silently lose its connection. A fix is currently in development that will surface a clear propagating status and send email notifications when this happens. - SSL provisioning delay: Occasionally SSL fails to provision even after DNS is successfully verified. If your site shows a security warning after 72 hours, open the chat widget and type human teammate — our team can manually trigger reprovisioning. - Cloudflare users: If your domain is proxied through Cloudflare, set the DNS record to DNS Only (grey cloud) rather than Proxied (orange cloud) during initial setup. Proxying before SSL is provisioned can prevent verification from completing. 💳 Hosting and Billing - Hosting is included in your Search Atlas subscription — there is no separate hosting fee for pages published within Website Studio. - Your published pages remain live as long as your Search Atlas subscription is active. - Custom domain registration and renewal fees are paid directly to your domain registrar — Search Atlas does not charge for or manage domain registration. - Plan-level limits on the number of projects or published pages depend on your current subscription tier. Check your account billing page for specifics. 📊 Analytics Capabilities - Basic page-view data is available inside Website Studio for published pages. - For advanced analytics, connect Google Analytics 4 (GA4) by adding your GA4 Measurement ID in the page settings. This enables full session, conversion, and audience tracking. - Search Atlas does not currently offer a built-in heatmap or session-recording tool — use a third-party integration for those use cases. 📝 CMS and Content Capabilities - Website Studio is optimised for landing pages — PPC pages, local service pages, and lead-capture pages. - It is not a full CMS (content management system). It does not support blog post archives, dynamic collections, or database-driven content out of the box. - You can clone and duplicate pages to create multiple variations quickly. - The Brand Vault lets you store brand colours, logos, and fonts so they are applied consistently across all projects. 🛠️ Technical Limitations to Know - No server-side scripting: Custom PHP, Python, or Node.js back-end code cannot be deployed through Website Studio. - Form submissions: Built-in forms capture leads within the platform. Custom webhook or CRM integrations may have limitations depending on your plan. - E-commerce: Website Studio is not designed for shopping-cart or checkout functionality. - Iframes and embeds: Most standard HTML embeds (video, maps, calendars) work fine inside the editor. - White-label publishing: If you are on an agency plan, you can configure white-label settings under More Features → Agency Whitelabel before sharing client previews. 💡 Tips for a Smooth Setup - Always verify DNS propagation using a free tool such as dnschecker.org before raising a support ticket — propagation delays are normal. - Keep your registrar login credentials handy when setting up a custom domain; you will need to log in to add or edit records. 🆘 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.

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

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

🔗 How It Works: Import Project (Website Builder)

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

🌐 Website Studio Publishing, Hosting, and DNS Setup

🗺️ Overview Website Studio lets you build, preview, and publish landing pages and local websites directly inside Search Atlas. This article explains how to share previews, connect custom domains, understand hosting, and know what features are currently supported. 🚀 Publishing Your Website Studio Site Once your site is ready, follow these steps to publish it: 1. In the left sidebar, click Website Studio (or navigate to /website-studio). 2. Open the project you want to publish. 3. Click the Publish button in the top toolbar. 4. Choose whether to publish to a Search Atlas subdomain or a custom domain you own. 5. Confirm the publish action. Your site will go live within a few minutes. Once published, you will receive a live URL you can share with clients or stakeholders. 🔗 Sharing a Preview Without Revealing the Platform If you want to share a preview link with a client without exposing the Search Atlas platform, connect a custom domain to your project. When a client visits your custom domain, they will see only your site — no Search Atlas branding appears in the URL or on the page. This is the recommended approach for agency workflows and white-label presentations. To access white-label settings, go to More Features → Agency Hub (Agency Hub / Set up your Agency's White Label) (or navigate to /agency-settings) and complete the setup steps. This ensures that any client-facing experience reflects your brand, not Search Atlas. ⚙️ Configuring DNS for a Custom Domain To connect your own domain or a client's domain to a Website Studio project, you will need to update DNS records with your domain registrar. Follow these steps: 1. In Website Studio, open the project and go to Settings → Custom Domain. 2. Copy the DNS values provided (typically a CNAME or A record). 3. Log in to your domain registrar (for example, GoDaddy, Namecheap, or Cloudflare). 4. Navigate to the DNS management section for the domain you want to connect. 5. Add or update the record using the values from Step 2. 6. Save your changes and return to Website Studio. 7. Click Verify DNS to confirm the connection. DNS propagation can take up to 48 hours, though it is usually much faster. Tip: If DNS verification fails, double-check that you have removed any conflicting records (such as an existing A record pointing to another host) before trying again. 💰 Hosting Costs Hosting for sites published through Website Studio is included in your Search Atlas subscription — there is no separate hosting fee. You can publish and host your Website Studio projects without paying for a third-party hosting provider. Custom domain registration is handled separately through your preferred domain registrar and is not included in your Search Atlas plan. 🛠️ Current Feature Limitations Website Studio is a growing product. Being aware of current limitations will help you plan your projects effectively: - CMS features: Dynamic CMS functionality (such as blog post collections, repeatable content types, or database-driven pages) is not currently supported. Pages are static at this time. - WordPress publishing: Direct publishing from Website Studio to a WordPress site is not currently available. This feature has been scoped but is not yet released. - HTML export: Downloading or exporting your site as a raw HTML file for external editing is not yet supported. This feature is on the product roadmap. - Supported project types: You can generate PPC landing pages, clone existing pages, build local websites, import projects, and create brand vaults. ✅ Quick Checklist Before Going Live - Site is fully built and previewed inside Website Studio. - White-label settings are configured if sharing with clients (More Features → Agency Hub). - Custom domain DNS records are added and verified. - You have confirmed that your project does not require CMS or WordPress features not yet supported. - The site is published and the live URL has been tested in a browser. 💬 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.

🌐 Publish & Export Your Website Studio Site

🗺️ Overview This article walks you through three common tasks: exporting your Website Studio project as a ZIP file, connecting a custom domain (including domains registered on GoDaddy, Namecheap, or any other registrar), and pointing your DNS records so your new site goes live. Whether you built your site from scratch in Website Studio or are moving away from a platform like Wix, this guide covers everything you need. 📦 Exporting Your Website Studio Project You can download a copy of your Website Studio project directly from the platform. Keep the following in mind before you export: - What you receive: The export produces a React application ZIP file. This is not a self-contained static HTML package, so you cannot simply open the files in a browser or drop them into a generic web host without a build step. - Editing externally: Because the export is a React app, external editing requires Node.js and familiarity with React. If you only need to make content changes, we recommend doing so inside Website Studio before exporting. - Best use case: Use the export to hand off the project to a developer or to host on a platform that supports Node.js applications (such as Vercel, Netlify, or a VPS). 1. Go to Left sidebar → Website Studio (URL: /website-studio). 2. Open the project you want to export. 3. Click the Settings or project menu icon in the top toolbar. 4. Select Export / Download and confirm. The ZIP file will download to your computer. Download not starting? Try the following: disable browser pop-up blockers, switch to a Chromium-based browser (Chrome or Edge), clear your cache, and retry. If the download still fails, 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. 🔗 Connecting a Custom Domain to Your Website Studio Site You can publish your Website Studio site under your own domain regardless of which registrar holds that domain (GoDaddy, Namecheap, Google Domains, etc.). 1. In Website Studio, open your project and navigate to Settings → Domain. 2. Enter your custom domain (e.g., www.yourdomain.com) and click Connect Domain. 3. Search Atlas will display the DNS records you need to add — typically a CNAME record for www and, optionally, an A record for the root domain (@). Copy these values; you will need them in the next section. ⚙️ Updating Your DNS Records at Your Domain Registrar Log in to the control panel of whichever registrar holds your domain and follow these general steps. The exact menu names vary by registrar but the record types are the same everywhere. 1. Find the DNS Management, DNS Zone, or Advanced DNS section for your domain. 2. Add or update the CNAME record: - Host / Name:www - Value / Points to: the CNAME target shown in Website Studio - TTL: 3600 (or Auto) 3. If Search Atlas also provided an A record for the root domain, add it: - Host / Name:@ - Value / Points to: the IP address shown in Website Studio - TTL: 3600 (or Auto) 4. Save your changes. DNS propagation typically takes a few minutes up to 48 hours. You can check propagation progress using a free tool such as whatsmydns.net — search for your domain and verify the records match what Search Atlas provided. 🔄 Migrating From Wix (or Another Website Builder) If your site was previously hosted on Wix, the migration process has two parts: redirecting your domain away from Wix and pointing it to Search Atlas. - Step 1 — Disconnect from Wix: Log in to your Wix dashboard, go to Domains, and remove or disconnect the domain from your Wix site. This releases the domain so it can point elsewhere. - Step 2 — Update DNS at your registrar: Follow the DNS steps in the section above using the records provided by Website Studio. - Step 3 — Verify in Website Studio: Return to Website Studio → Settings → Domain and confirm that the domain status shows as Connected or Active. Important: Wix hosts your old site's content on their servers. Exporting that content from Wix is done through Wix's own export tools, not through Search Atlas. Rebuild or recreate your pages inside Website Studio before switching DNS to avoid any downtime. ❓ Troubleshooting Common Issues - Domain still showing the old Wix site: DNS has not fully propagated yet, or the old DNS records were not removed. Double-check that no conflicting A or CNAME records pointing to Wix remain at your registrar. - SSL certificate not activating: SSL is provisioned automatically once DNS propagates. Wait up to 24 hours after DNS resolves correctly, then check the domain status in Website Studio again. - ZIP export opens as a blank page: The exported file is a React app and requires a build process. Open the ZIP, run npm install followed by npm run build, then serve the resulting build folder. - WordPress sync publishing blank pages: This is a known issue currently under investigation. Avoid using the WordPress sync feature for production sites until a fix is confirmed. 💬 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.

Site Analysis Lead Capture Widget: Setup and Best Practices

The Site Analysis Lead Capture Widget lets agencies place a branded site analysis form on their own website, so visitors can run an analysis and become leads. This article explains where to find the widget code and what to do if visitors see an "Invitation Required" page. How do I set up and install the Lead Capture Widget? 1. Open the Agency Hub in your Search Atlas dashboard. 2. Open the Site Analysis Lead Capture Widget tab. 3. In Step 1, configure and test the widget. You can change the placeholder text, the button text and the colors. Custom HTML is optional. 4. In Step 2, install the widget by copying the snippet shown on the page. 5. Paste the snippet into the page of your website where you want the widget to appear. The widget works on your white-label domain, so your white-label domain must be configured first. The snippet is built from your styling choices and your domain, and it updates as you edit the settings. After any change, copy the snippet again and replace the one on your website. Is there a publish or enable public access setting? No. The widget has no publish or "enable public access" toggle, and there is no separate tab called "Widget Settings". The snippet is available to copy as soon as your white-label domain is set up. If you were told to look for one of these settings, you can ignore that advice. What happens if visitors see "Invitation Required"? If a visitor opens your widget and sees a page that says registration is by invitation only, this is a known platform issue. Visitors who are not signed in, on white-label domains, can be sent to the invitation-only registration page by mistake. Changing the widget settings or the snippet does not fix it, and it is not something you can correct from your side. What should I do if I see this issue? Reach our team through live chat. Please include: - The page address where the widget is installed. - The white-label domain you are using. - A screenshot or short recording of what the visitor sees.

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

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

🔄 Restore Project Versions and Prompt Website Studio

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

[UI Map] Website Studio

Website Studio Navigation path: Left sidebar → Website Studio URL pattern: /website-studio Allows users to create, manage, and publish SEO- and conversion-optimized websites using AI-generated PPC sites, imported sites, or free-form builds linked to Brand Vaults. Primary actions: - Generate PPC Site - Import Site - Submit - Start voice input - Create Brand Vault - Select Brand Vault - Explore Training Calls - All - Drafts - Published Key UI elements: - AI site creation prompt textbox ('Describe the site you want to create') - Brand Vault selector dropdown with search - Generate PPC Site button - Import Site button - Sites grid (Site cards list) - Site status badges (Draft, Published) - Site type badges (PPC, Free) - All / Drafts / Published filter toggle - All Sites type filter dropdown - Last Edited sort dropdown - Search sites textbox - Pagination controls (Previous, page numbers, Next) - Items per page selector (12, 24, 48, 96) - Page count indicator ('Total records: 99 | Showing 1-10') Auto-generated by SA UI Mapper. Last updated: 2026-09-18.

🌐 Publish Your Wix Site via GoDaddy and Namecheap

🗺️ Overview If you built your website using Wix but want to host it on Namecheap with a domain registered through GoDaddy, you need to complete three steps: export your Wix site content, point your GoDaddy domain to Namecheap's nameservers, and publish your site through Namecheap hosting. This guide walks you through each step clearly. ⚠️ What to Know Before You Start There are a few important limitations to understand upfront: - Wix does not allow full site exports. Wix is a closed platform — you cannot download your site's source code or migrate it directly to another host. You will need to rebuild or replicate your content on the new hosting environment. - Domain and hosting are separate. Your GoDaddy domain and your Namecheap hosting account are independent services. You connect them by updating nameservers. - DNS changes take time. After updating nameservers, propagation can take 24–48 hours worldwide. 📋 Step 1 — Gather Your Namecheap Hosting Details 1. Log in to your Namecheap account at namecheap.com. 2. Go to Dashboard → Hosting List and select your hosting plan. 3. Note the two nameserver addresses assigned to your plan (they typically look like dns1.namecheaphosting.com and dns2.namecheaphosting.com). You will need these in the next step. 4. Also note your hosting cPanel login URL, username, and password — you will use cPanel to publish your website files. 🔗 Step 2 — Point Your GoDaddy Domain to Namecheap 1. Log in to your GoDaddy account and go to My Products → Domains. 2. Click Manage next to the domain you want to use. 3. Scroll to the Nameservers section and click Change. 4. Select Enter my own nameservers. 5. Replace the existing nameservers with the two Namecheap nameserver addresses you gathered in Step 1. 6. Save your changes. GoDaddy will display a confirmation prompt — accept it. 7. Wait 24–48 hours for DNS propagation to complete before expecting the domain to resolve correctly. 🏗️ Step 3 — Recreate and Upload Your Website to Namecheap Because Wix does not allow file exports, you need to rebuild your website content in a format compatible with Namecheap hosting. Common approaches include: - WordPress on Namecheap: Install WordPress via Namecheap's cPanel (Softaculous one-click installer), then recreate your pages and content. This is the most flexible option. - Static HTML site: If your site is simple, manually code or use a website builder tool to create HTML/CSS files, then upload them via cPanel's File Manager or an FTP client. To upload files via cPanel File Manager: 1. Log in to your Namecheap cPanel. 2. Open File Manager and navigate to the public_html folder. 3. Upload your website files (HTML, CSS, images, etc.) into this folder. 4. Ensure your homepage file is named index.html or index.php so the server loads it by default. ✅ Step 4 — Verify Your Site Is Live 1. After DNS propagation (24–48 hours), open a browser and type your GoDaddy domain into the address bar. 2. Your Namecheap-hosted website should load. If it does not, try clearing your browser cache or checking propagation status using a tool like whatsmydns.net. 3. Confirm your nameservers are correctly set by entering your domain on the whatsmydns.net site and selecting NS from the record type dropdown. 🛠️ Troubleshooting Common Issues - Domain still shows the old Wix site: DNS has not fully propagated yet. Wait the full 48 hours and clear your browser cache. - Nameservers not saving in GoDaddy: Ensure you are entering the nameservers exactly as provided by Namecheap, with no extra spaces. - cPanel login not working: Double-check your credentials in the Namecheap dashboard under your hosting plan details. You may need to reset your cPanel password from there. - Site shows a blank page or error after upload: Confirm your main file is named index.html or index.php and is placed directly inside the public_html folder, not inside a subfolder. 💬 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. Additional Notes Step 4 details connecting the custom domain inside Wix (Settings → Website Settings → Custom Domain → Connect a Domain You Already Own) and adding Wix-provided DNS records (A, CNAME) via Namecheap cPanel Zone Editor instead of GoDaddy.

🏷️ Add Meta Tags and Content to Website Studio Sites

Overview Website Studio lets you build and publish websites directly from Search Atlas. Because Website Studio does not support external CMS connections, all content and SEO settings—including meta tags—are managed entirely within the Website Studio editor. This article explains what to expect and how to get assistance configuring meta tags and page content on your published site. Before You Begin Make sure you have already: - Created a site in Website Studio. - Published or saved at least one page. - Connected your domain if you want SEO metadata to appear on a live URL (optional for configuration, required for indexing). Adding Meta Tags and Page Content in Website Studio Meta tags and page content are managed inside the Website Studio editor on a per-page basis. Because the exact location of SEO and meta tag settings within the editor can vary depending on your site configuration and the current version of Website Studio, we recommend the following approach to locate and configure these settings: 1. Open Website Studio from the left sidebar. 2. Select your site and enter the editor. 3. Select the specific page you want to configure. 4. Look within the editor interface for a settings area associated with the selected page — this may appear as a panel, tab, or menu option related to page or SEO configuration. The exact label and location depend on your current editor version. 5. Within that settings area, look for fields to enter your page title, page description, and any other metadata your site requires for search engines and social sharing. 6. Enter your desired values, then save and republish the page so the changes take effect on your live site. 7. Repeat for each page on your site that requires meta tag configuration. Important: Meta tags must be saved and the page republished before they are visible to search engines or social platforms. If your site is already live, republishing updates the metadata immediately. Editing Page Content All text, images, and layout changes are made directly in the Website Studio editor. There is no external CMS connection — content lives entirely within the platform. 1. Open Website Studio from the left sidebar. 2. Select your site and enter the editor. 3. Select the page you want to update. 4. Click any existing element on the page to select and edit it inline. 5. Use the editor's available tools to add new content blocks, such as text, images, or other sections, as offered by your editor version. 6. Save your changes and republish the page when you are ready for them to appear on your live site. If you are unsure where to find the meta tag fields or content editing tools within your specific editor view, our support team can walk you through the exact steps for 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.

🖼️ Updating the OpenGraph Image in Website Studio

🔍 Why the OG Image Requires Updates in Two Places Website Studio React projects store the OpenGraph image URL in two separate locations. Updating only one causes a split result: social media platforms and crawlers — which read raw static HTML — continue to display the old image, while your browser's Inspect Element panel shows the correct new image because the React application has already updated the live DOM in memory using the newer value. The two files that must both be updated are: - index.html (project root) — contains the static og:image meta tag inside the page head, read directly by search crawlers and social media link-preview generators at the raw HTML level - src/pages/Index.tsx — contains the OG_IMAGE_URL constant used by the React application at runtime to dynamically hydrate the Open Graph image tag in the live DOM Both files must contain the same absolute URL, and a full republish must be performed after saving both files for the changes to appear in raw page source. 📁 Accessing Your Site Files in Website Studio To edit your site's source files, navigate to Left sidebar → Website Studio. Select your site and open the built-in code editor. From the file tree you can open and edit all project files, including index.html at the project root and the TypeScript source files under src/pages/. ✏️ How to Update the OG Image in Both Required Files Complete both steps below before republishing. Saving only one file and republishing will not fully resolve the issue and will leave the discrepancy in place. 1. In the Website Studio code editor (Left sidebar → Website Studio → [your site] → Code Editor), open index.html. Locate the meta tag where the property attribute is set to og:image inside the head section. Update the content attribute value to your new absolute image URL — for example, https://yourdomain.com/assets/og-image.png. Save the file. 2. Open src/pages/Index.tsx. Near the top of the file, find the constant named OG_IMAGE_URL. Update its value to the exact same absolute URL you entered in index.html. Save the file. Always use a fully qualified absolute URL beginning with https://. Relative paths such as /assets/og-image.png are not resolved correctly by social media crawlers and will cause the preview image to fail to load. 🚀 Republishing Your Site After Updating Both Files Once both files are saved, you must trigger a full rebuild and republish so the changes are compiled into the static HTML output delivered to browsers and crawlers. In Website Studio (Left sidebar → Website Studio → [your site] → Publish), click the Publish button to rebuild and deploy your site. Saving files without republishing will not update the raw HTML served to crawlers or to users loading the page for the first time. After the republish completes, perform a hard refresh in your browser — press Ctrl + Shift + R on Windows and Linux, or Cmd + Shift + R on macOS — to bypass your local browser cache and confirm you are viewing the freshly deployed HTML file. ❓ Why View Page Source Shows the Old Image After Republishing Seeing a mismatch where View Page Source displays the old OG image URL while Inspect Element shows the correct new URL is caused by a caching or build artefact. The two browser views read from entirely different sources: - View Page Source displays the raw static HTML file as delivered by the server. If the build cache was not fully cleared or the deployment has not yet propagated, this file will still contain the previous og:image value — this is the exact version crawlers and social platforms read. - Inspect Element displays the live DOM after the React application has executed in the browser. Because the JavaScript bundle was updated with the new OG_IMAGE_URL constant from src/pages/Index.tsx, the React app sets the correct image in the live DOM — even if the underlying static HTML has not yet caught up. This is precisely why updating src/pages/Index.tsx alone appears to fix the image in the browser but does not fix what social media platforms and search crawlers see. Updating index.html alone fixes the crawler view but leaves the live DOM temporarily inconsistent. Both files must be updated together, followed by a full republish, to eliminate the discrepancy entirely. ✅ Verifying the OG Image Updated Correctly After republishing, confirm the update was fully applied using the following checks in order: 1. Open your published site URL in a new incognito or private browser window, right-click anywhere on the page, and select View Page Source. Search the source for og:image and confirm the content value shows the new absolute URL — not the old one. 2. Use an Open Graph debugger to force a fresh crawl and preview the updated image. Search your browser for LinkedIn Post Inspector or Facebook Sharing Debugger, paste your site URL, and click the button to request a fresh scrape. The new image should appear in the preview. 3. If View Page Source still shows the old URL after a confirmed republish, return to Left sidebar → Website Studio → [your site] → Code Editor, verify that both index.html and src/pages/Index.tsx contain the updated absolute URL, save both files, and republish 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.

🔄 Migrate WordPress OTTO Projects to Website Studio

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

☁️ Cloudflare Orange Cloud Proxy and Website Builder

🔍 Overview Search Atlas Website Builder hosts your site on our infrastructure and requires DNS records to point directly to our servers. Cloudflare's orange cloud (proxy) mode routes traffic through Cloudflare's network before it reaches your site. This is compatible with Search Atlas Website Builder, but it requires careful configuration to avoid breaking your site's functionality. This article explains how to set up Cloudflare's orange cloud proxy for a domain connected to Search Atlas Website Builder, using zatrox.com as an example. ⚠️ What You Need to Know Before You Start Before enabling the orange cloud proxy, be aware of the following: - SSL/TLS mode matters: Incorrect SSL settings in Cloudflare can cause redirect loops or mixed-content errors on your site. - Third-party integrations may break: Enabling the proxy on records used by third-party tools (such as HubSpot or other services) can prevent those tools from functioning. Only proxy the records specifically tied to your Website Builder domain. - DNS propagation takes time: After any DNS change, allow up to 48 hours for full propagation, although changes typically take effect within a few hours. 🛠️ Step 1 — Add Your Domain's DNS Records in Cloudflare Log in to your Cloudflare account and select the domain you want to configure (for example, zatrox.com). Navigate to DNS → Records. Your Search Atlas Website Builder will have provided you with a target hostname or IP address to point your domain to. Add or update the following records: - CNAME record — set the Name to @ (or zatrox.com) and the Target to the hostname provided by Search Atlas Website Builder. If Cloudflare does not allow a root CNAME, use an A record with the IP address provided instead. - CNAME record for www — set the Name to www and the Target to the same Search Atlas hostname. If you are unsure which hostname or IP address to use, 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. 🟠 Step 2 — Enable the Orange Cloud (Proxy) on the Correct Records Once your DNS records are saved, toggle the Proxy status to Proxied (the orange cloud icon) for your root and www records only. Do not enable the orange cloud proxy on records used by third-party tools such as email providers, HubSpot, or other marketing integrations. Proxying those records can break their functionality. Leave those records set to DNS only (the grey cloud). 🔒 Step 3 — Configure Cloudflare SSL/TLS Settings Incorrect SSL settings are the most common cause of errors when using Cloudflare proxy with a hosted website builder. Follow these steps: 1. In your Cloudflare dashboard, go to SSL/TLS → Overview. 2. Set the encryption mode to Full or Full (Strict). Do not use Flexible — this causes redirect loops with Search Atlas Website Builder because our servers already serve your site over HTTPS. 3. Go to SSL/TLS → Edge Certificates and ensure Always Use HTTPS is toggled on. ⚙️ Step 4 — Review Cloudflare Performance and Security Settings Some default Cloudflare features can interfere with your website. Review the following after enabling the proxy: - Caching: Cloudflare may cache pages aggressively. If you publish updates to your Search Atlas website and they do not appear, go to Caching → Configuration in Cloudflare and click Purge Everything to clear the cache. - Rocket Loader: Go to Speed → Optimization → Content Optimization and confirm Rocket Loader is disabled. This feature can delay or break JavaScript loading on third-party hosted sites. - Minification: Auto-minification of HTML, CSS, or JS in Cloudflare is generally safe to leave on, but if you notice layout issues, disable it under Speed → Optimization → Content Optimization. ✅ Step 5 — Verify Your Setup After completing the steps above, verify your configuration is working correctly: 1. Open a private/incognito browser window and visit your domain (e.g., https://zatrox.com) to confirm the site loads correctly. 2. Check that the padlock icon appears in the browser address bar, confirming HTTPS is active. 3. Test the www version of your domain as well (e.g., https://www.zatrox.com). 4. If you use any third-party integrations (forms, chat tools, analytics), confirm they are still functioning correctly. ❓ Troubleshooting Common Issues - Redirect loop or ERR_TOO_MANY_REDIRECTS: Your Cloudflare SSL mode is likely set to Flexible. Change it to Full or Full (Strict) as described in Step 3. - Site loads but CSS or images are missing: Purge the Cloudflare cache (see Step 4) and confirm Rocket Loader is disabled. - Third-party tool stopped working after DNS change: Check that the DNS record for that tool is set to DNS only (grey cloud), not proxied. - Site not loading at all: Confirm your DNS records are pointing to the correct Search Atlas hostname or IP, and allow additional time for DNS propagation. 💬 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. Additional Notes For root domains, Cloudflare uses CNAME Flattening, which automatically resolves the CNAME to an IP address at the DNS level, allowing you to proxy your root domain through Cloudflare without breaking DNS standards. Known compatibility symptoms include broken/blank site, failed pixel or UUID detections, and unexpected DNS behavior. Troubleshooting: switch CNAME records to DNS only (gray cloud), wait 5–10 minutes for propagation, then test site functionality.

📧 Configure Form Notification Emails in Website Studio

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

🌐 Publish Your Website Studio Site on a Custom Domain

🗺️ Overview If you built a site in Website Studio and purchased a domain through a registrar like GoDaddy or Namecheap, you can make your site live by pointing that domain to your Website Studio project. This article walks you through the full process and explains the ZIP export limitation you may have encountered. ⚠️ Why You Cannot Download a ZIP Export Website Studio does not support ZIP file exports of your site. Your site is hosted directly through the platform, so publishing happens by connecting a custom domain — not by downloading and uploading files manually. If you see or expect a ZIP download option, it is not available, and your site must be published using the domain connection method described below. 🛠️ Step 1: Find Your Website Studio Publishing Settings 1. Log in to your Search Atlas account. 2. In the left sidebar, click Website Studio (or navigate to /website-studio). 3. Open the site you want to publish. 4. Locate the Publishing or Custom Domain settings for your project. This is typically found in the site settings panel or via a Publish button in the top navigation. 5. Copy the CNAME target or IP address provided by Website Studio — you will need this in the next steps. 🔑 Step 2: Understand Your Domain Setup It is common to purchase a domain on GoDaddy but manage it through Namecheap, or vice versa. Before updating DNS records, confirm where your domain's nameservers are currently pointing. This determines where you need to make DNS changes: - If your domain was purchased on GoDaddy and you have not changed the nameservers, log in to GoDaddy to update DNS records. - If the nameservers were transferred to Namecheap, log in to Namecheap to update DNS records. - If you are unsure, check the nameserver fields in your registrar dashboard — they will show which platform is in control. 📋 Step 3: Add the DNS Record in GoDaddy If your domain is managed in GoDaddy, follow these steps: 1. Log in to your GoDaddy account and go to My Products → Domains. 2. Click DNS next to your domain. 3. Click Add New Record. 4. Set the Type to CNAME. 5. In the Name field, enter www (or @ for the root domain, if supported). 6. In the Value field, paste the CNAME target copied from Website Studio. 7. Set the TTL to the lowest available option (e.g., 600 seconds) to speed up propagation. 8. Click Save. 📋 Step 3 (Alternative): Add the DNS Record in Namecheap If your domain's nameservers are pointing to Namecheap, follow these steps instead: 1. Log in to your Namecheap account and go to Domain List. 2. Click Manage next to your domain. 3. Select the Advanced DNS tab. 4. Click Add New Record. 5. Set the Type to CNAME Record. 6. In the Host field, enter www. 7. In the Value field, paste the CNAME target from Website Studio. 8. Set TTL to Automatic or the lowest available value. 9. Click the Save checkmark. ⏱️ Step 4: Wait for DNS Propagation After saving your DNS record, changes can take anywhere from a few minutes to 48 hours to propagate worldwide. During this time: - Your site may not be immediately accessible at the new domain. - You can check propagation status using a free tool such as whatsmydns.net — enter your domain and select CNAME to see live results across global servers. - Once propagation is complete, visit your domain in a browser to confirm your Website Studio site is live. ✅ Step 5: Confirm the Domain in Website Studio Return to Website Studio in Search Atlas and confirm your custom domain in the publishing settings. Some configurations require you to enter your domain name in the platform so it can verify the connection and activate SSL. Follow any on-screen prompts to complete this step. 💡 Tips and Common Issues - Root domain vs. www: Some hosting setups require you to redirect the root domain (example.com) to the www version (www.example.com). Check your Website Studio publishing instructions for the recommended setup. - SSL certificate: Website Studio provisions SSL automatically once the domain is connected. If you see a security warning shortly after setup, wait up to one hour for SSL to activate. - Conflicting records: Delete any existing CNAME or A records for the same host (e.g., www) before adding new ones to avoid conflicts. - Cache: Clear your browser cache or test in an incognito window if the site does not load as expected after propagation. 🆘 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.

🗺️ Embed Google Maps in Brand Vault Locations

🔍 Overview The Brand Vault Locations section supports an embedded Google Map to help display your business location. To save successfully, the map field requires a specific iframe embed code — not a standard Google Maps URL. Entering the wrong format will prevent the field from saving correctly. 📍 What the Google Map Field Expects The map input field in Brand Vault Locations is designed to accept an iframe embed code from Google Maps. This is different from the URL you see in your browser's address bar when viewing a location on Google Maps. - Correct format: An iframe embed code that begins with <iframe src="https://www.google.com/maps/embed?..." - Incorrect format: A standard browser URL such as https://www.google.com/maps/place/... Pasting a standard URL into the map field will not save and will not display a map preview. 🔗 How to Get the Correct Iframe Embed Code from Google Maps 1. Open Google Maps in your browser and search for your business location. 2. Click on your business listing to open the location panel. 3. Click the Share button (the arrow icon near the top of the panel). 4. In the Share dialog, select the Embed a map tab. 5. Choose your preferred map size from the dropdown menu. 6. Click Copy HTML. This copies the full iframe embed code to your clipboard. The copied code will look similar to this example: <iframe src="https://www.google.com/maps/embed?pb=..." width="600" height="450" style="border:0;" allowfullscreen="" loading="lazy"></iframe> 📋 How to Add the Embed Code to Brand Vault Locations 1. Navigate to Brand Vault: top-right More Features menu (grid icon, next to your Avatar Menu (👤)) → Brand Vault, or OTTO SEO in the left sidebar → All Sites → open your project → Brand Vault. 2. Open the Locations section. 3. Locate the Google Map field for the relevant location. 4. Paste the full iframe embed code you copied from Google Maps into the field. 5. Click Save to confirm your changes. Once saved, a map preview will appear within the Locations card displaying your embedded location. ⚠️ Common Mistakes to Avoid - Pasting a browser URL instead of the iframe code. Always use the Share → Embed a map flow in Google Maps to get the correct code. - Copying only the src attribute value. The entire <iframe>...</iframe> tag is required, not just the URL inside the src attribute. - Editing the iframe code after copying. Avoid modifying the code manually, as this can break the embed and prevent saving. - Using a Google My Business or Google Search result URL. These URLs are not compatible with the embed field. ✅ How to Confirm the Map Saved Correctly After saving, scroll to the Locations section in Brand Vault. If the embed was accepted, you will see a live map preview rendered inside the location card. If the field appears blank or shows an error, review the format of the code you pasted and repeat the steps above using the Embed a map tab in Google Maps. 💬 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.

🚀 Publish Website Studio Pages to WordPress Subpaths

Overview Website Studio lets you publish a new page directly to a subpath on your existing WordPress domain without touching your homepage, DNS records, or any other existing pages. This guide explains what to prepare and how to complete the process. Before You Begin Make sure the following conditions are met before publishing: - Your WordPress site is already connected to Search Atlas. - You have editor or admin-level access to that WordPress installation. - The subpath you want to use does not already have a page published at that URL — publishing may overwrite existing content at that exact path. - Your homepage and other existing pages will not be affected as long as you target only the specific subpath. How to Publish to a WordPress Subpath To publish a Website Studio page to a subpath on your connected WordPress domain, follow these steps: 1. Open Website Studio in Search Atlas and select the page you want to publish. 2. Click the Publish option for that page. 3. When prompted to choose a destination, select your connected WordPress domain. 4. Enter the subpath (slug) where you want the page to appear — for example, /your-page-name. 5. Confirm and complete the publish action. Once published, the page will appear at the subpath URL on your WordPress site. If you do not see your WordPress domain listed as a destination, confirm that your WordPress site is fully connected to Search Atlas before proceeding. How Subpath Publishing Works When you publish to a subpath, Search Atlas creates or updates a single page at that URL on your WordPress site. It does not modify your theme, root domain, or any other pages. - Homepage: Unaffected. Publishing to a subpath does not alter your front page settings in WordPress. - Existing pages: Safe, unless you deliberately target a slug that is already in use. Common Issues - The page published but returns a 404: This may be related to permalink settings on your WordPress site. If the issue persists after a short wait, contact support with the details listed below. - Your WordPress site does not appear as a destination: Confirm that your WordPress site is fully connected to Search Atlas. If you are unsure how to check this, contact support with your domain name and account details. What to Have Ready When Escalating If you encounter any issues, please have the following ready when contacting support: - The name of the Website Studio page you want to publish. - Your connected WordPress domain. - The exact subpath you want to publish to. - Any error messages or unexpected behavior you have already 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.

☁️ Cloudflare Proxy Setup for Website Builder

☁️ Compatibility Overview Search Atlas Website Builder works with Cloudflare's orange cloud proxy mode. The proxy accelerates content delivery, hides your origin IP, and provides DDoS protection. You can enable it once your domain points to the builder's nameservers or CNAME target. 🔧 Prerequisites - Active Search Atlas Website Builder site - Domain added in the builder's Domains section - Domain using Cloudflare DNS (either full or CNAME setup) - SSL certificate issued and active in the builder 📋 Step-by-Step Configuration 1. Log in to Cloudflare and select your domain (e.g., zatrox.com). 2. Open DNS → Records. 3. Locate the record pointing to the Website Builder (A, AAAA, or CNAME). 4. Click the cloud icon next to the record to turn it orange (Proxied). 5. Wait 1-2 minutes for the change to propagate. 6. In Cloudflare, go to SSL/TLS → Overview and set encryption mode to Full (strict). 7. Enable Always Use HTTPS under Edge Certificates. 8. Disable Automatic HTTPS Rewrites if you see mixed-content warnings. ⚙️ Recommended Cloudflare Settings - Caching Level: Standard - Browser Cache TTL: 4 hours - Auto Minify: Enable CSS, JS, HTML - Brotli: On - Early Hints: On - Rocket Loader: Off (can break builder scripts) - Mirage/Polish: Off unless you use Cloudflare Images ✅ Verification Checklist 1. Visit https://zatrox.com and confirm the padlock shows a valid certificate. 2. Open browser dev tools → Network tab → reload; verify cf-cache-status header returns HIT or DYNAMIC. 3. Run curl -I https://zatrox.com and confirm server: cloudflare header is present. 4. Check the Website Builder Domains page; status should read Connected. 🛠️ Troubleshooting Common Issues - SSL errors: Ensure Cloudflare SSL mode is Full (strict) and the builder certificate is valid. - Redirect loops: Disable Always Use HTTPS temporarily, then re-enable after cache clears. - Broken assets/CSS: Turn off Rocket Loader and purge Cloudflare cache. - API/Webhook failures: Create a Page Rule for /api/* with Cache Level: Bypass and Disable Performance. 🔄 Cache Management After publishing changes in Website Builder, purge Cloudflare cache: Caching → Configuration → Purge Everything or use Custom Purge for specific URLs. 💬 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 Visual Editor Edits and Credit Usage

🎯 Overview When working in the Website Studio visual editor, it is natural to wonder whether every small change — like fixing a word or swapping a color — costs credits, and what to do when a delete button is missing. This article answers both questions clearly. 💳 Do Inline Edits Cost Credits? Credits in Website Studio are tied to generation activities, not manual edits. The following actions do consume credits: - Generating a new PPC landing page - Cloning an existing page - Building a local website - Any AI-assisted generation triggered from the left sidebar under Website Studio The following actions do not consume credits: - Typing or replacing text directly in the visual editor - Changing a color using the color picker - Resizing, moving, or repositioning elements on the canvas - Updating fonts, spacing, or other style properties manually In short: if you are making a change yourself in the editor without asking the AI to generate or rewrite content, no credit is charged. 🗑️ How to Delete a Line When There Is No Delete Button Some elements in the visual editor do not display a visible delete or remove button. In these cases, use the screenshot-and-prompt method to instruct the AI to remove the element for you. Follow these steps: 1. Open Website Studio from the left sidebar and navigate to the page you are editing. 2. Take a screenshot of the section containing the line or element you want to remove. Make sure the element is clearly visible in the screenshot. 3. Open the chat panel within Website Studio. 4. Upload the screenshot and type a clear instruction, for example: "Remove the line shown in this screenshot" or "Delete the divider between the headline and the button in this section." 5. The AI will process your request and apply the change to the page. 6. Review the result in the visual editor and confirm the element has been removed. Important: Because this step uses the AI to modify your page, it does consume credits. If you need to remove multiple elements, try to include them all in a single prompt and screenshot to use credits efficiently. 💡 Tips for Efficient Editing - Always make manual text and color changes directly in the editor when possible — these are free and instant. - Reserve AI prompts for structural changes, such as deleting elements, reorganizing sections, or generating new content. - Be specific in your prompts. Describing exactly which element to remove reduces the chance of unintended changes and avoids needing a follow-up generation. - If you are unsure whether an action will cost a credit, opt for the manual edit path first. If the editor does not give you the control you need, then use the AI chat. 📋 Quick Reference: Credit Usage at a Glance - Costs credits: Page generation, AI chat modifications, cloning pages - Free: Typing text, changing colors, adjusting styles, repositioning elements manually - Deleting elements with no button: Use a screenshot and an AI chat prompt — this costs credits 🙋 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.

🔒 SSL & DNS Setup for Website Studio Pages

Overview When you publish a landing page in Website Studio, it is initially hosted on a Search Atlas subdomain. To use your own domain and display a padlock (SSL) in the browser, you need to connect your domain and configure SSL. This article walks you through each step. How Domain & SSL Work in Website Studio Search Atlas uses a custom domain mapping system. When you point your domain or subdomain to our servers and add it inside Website Studio, we automatically provision a free SSL certificate for that domain. The 'Not Secure' warning appears when: - Your domain has not been connected to Website Studio yet. - DNS changes have not fully propagated. - The domain was added incorrectly or the DNS records do not match. Step 1 — Access Website Studio 1. Log in to your Search Atlas account. 2. In the left sidebar, click Website Studio. 3. Open the landing page you want to connect to your domain. Step 2 — Add Your Custom Domain To connect a custom domain to your landing page, look for the domain or custom domain settings within your page's configuration options. The exact location of this setting may vary — if you are unable to locate it, please reach out to our support team using the contact information at the end of this article so a team member can guide you through the correct steps for your account. 1. Enter the domain or subdomain you want to use (e.g., landing.yourdomain.com). 2. Save your changes. Search Atlas will display the DNS records you need to add. Step 3 — Update Your DNS Records Log in to your domain registrar or DNS provider (e.g., GoDaddy, Cloudflare, Namecheap) and add the records shown in Website Studio. Depending on your setup, you may need to add: - CNAME record — Typically used to point a subdomain (e.g., landing) to the value provided by Search Atlas. - A record — May be required if you are connecting a root domain. Use the value provided by Search Atlas in your domain settings. Save your DNS changes. Propagation time varies by provider and can take several hours or longer. Step 4 — SSL Certificate Activation Once your DNS records have propagated correctly, Search Atlas automatically provisions a free SSL certificate for your connected domain. You do not need to upload or purchase a certificate manually. After activation: - Your page URL will change from http:// to https://. - The browser padlock will appear, removing the 'Not Secure' warning. - If the padlock still does not appear after DNS propagation is complete, double-check that your DNS records exactly match the values shown in Website Studio. Step 5 — Host Multiple Landing Pages on One Domain 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 Credit Usage and Quota Guide

🧭 Overview Website Studio uses two separate resource systems that work independently of each other. Confusing them is the most common reason customers see a 'credit balance too low' error even when their Hyperdrive Credit balance appears healthy. This article explains both systems, what each action costs, and how to resolve quota or credit errors. 💡 Two Resource Systems Explained Before troubleshooting any error, it helps to understand the difference between these two systems: - Hyperdrive Credits — A paid, consumable balance used for specific high-powered AI actions inside Website Studio (for example, Cloud Stack creation). Credits do not reset monthly; they are spent permanently when consumed and must be topped up when depleted. - LPS Project Quota — A monthly allowance tied to your subscription plan that governs how many Local Presence Stack (LPS) projects you can have active. This quota resets on your billing cycle date each month and is not the same as your Hyperdrive Credit balance. These two systems are completely independent. Having 2,423 Hyperdrive Credits does not guarantee your LPS project quota is available, and a full LPS quota does not mean you have Hyperdrive Credits to spend. 💳 What Each Action Costs Use the table below to understand exactly which resource each Website Studio action consumes: - Cloud Stack creation — Costs 15 Hyperdrive Credits per stack. This is deducted from your Hyperdrive Credit balance immediately on creation. - Content Genius edits — Content Genius editing within Website Studio does not cost Hyperdrive Credits per edit. Edits are covered by your plan's standard Content Genius allowance. You can make edits freely without worrying about per-edit credit charges. - Activating a new LPS project — Counts against your LPS project quota, not your Hyperdrive Credits. Once your monthly quota is reached, no new projects can be activated until the quota resets. 🔴 Understanding the 'Credit Balance Too Low' Error This error can appear for two distinct reasons, and identifying the correct one is essential for fixing it quickly. Reason 1 — Insufficient Hyperdrive Credits: You are attempting an action (such as creating a Cloud Stack) that requires Hyperdrive Credits, and your balance is too low to cover the cost. Even a balance of 2,423 credits will trigger this error if the specific action requires more credits than you currently hold, or if a system sync delay is temporarily misreporting your balance. Reason 2 — LPS Project Quota Reached: Your subscription plan's monthly LPS project quota is fully consumed. The platform may surface a credit-related error message in this scenario, but the true cause is your quota limit — not your Hyperdrive Credit balance. No amount of Hyperdrive Credits will unlock additional LPS projects once the monthly quota is exhausted. 🛠️ Troubleshooting Steps Follow these steps in order to identify and resolve the error: 1. Check your Hyperdrive Credit balance. Navigate to your account billing or credits dashboard and confirm your current Hyperdrive Credit total. If your balance is at or near zero, you need to purchase additional credits before proceeding. 2. Check your LPS project quota. Review how many LPS projects your plan allows per month and how many you have already activated in the current billing cycle. If you are at your plan limit, creating additional projects will be blocked until the quota resets. 3. Identify which action triggered the error. If you were creating a Cloud Stack, the issue is almost certainly Hyperdrive Credits. If you were activating a new LPS project, the issue is almost certainly your monthly quota. 4. Refresh the platform and retry. Occasional sync delays can cause the balance display to lag behind your actual credit total. Log out, log back in, and attempt the action again before escalating. 5. Upgrade your plan if quota is the blocker. If you regularly hit your LPS project quota before the monthly reset, upgrading to a higher-tier plan increases the number of projects available to you each month. 6. Purchase additional Hyperdrive Credits if credits are the blocker. If your Hyperdrive Credit balance is genuinely low, top up your balance through the billing section of your account settings. 📅 Monthly Resets and Credit Behavior - LPS project quota resets on your billing cycle date each month. The exact reset date matches the anniversary of your subscription start date and is visible in your account billing details. - Hyperdrive Credits do not reset monthly. They are a non-recurring, consumable balance. Credits you purchase remain in your account until spent. They are never automatically replenished at the start of a new billing period. - Content Genius allowances follow your plan's standard monthly reset schedule, separate from both Hyperdrive Credits and LPS quotas. 🚀 Accessing Website Studio You can reach Website Studio at any time by selecting Website Studio from the left sidebar, or by navigating directly to /website-studio in the platform URL. 🙋 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.

🌐 Migrate Website Studio to Wix and Fix UX Score

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

🌐 Configure www to Non-www Domain Redirect

🗺️ Overview By default, your Website Studio site may be accessible at both www.yourdomain.com and yourdomain.com. For SEO and consistency, it is best practice to pick one version as your canonical domain and redirect the other to it. This article walks you through configuring a www → non-www redirect so that all visitors land on yourdomain.com. ⚙️ Before You Begin Make sure you have completed the following before attempting to configure a redirect: - Your custom domain is already connected to your Website Studio site. If you have not done this yet, complete the Custom Domain Setup steps first. - You have access to your domain registrar or DNS provider (for example, Cloudflare, GoDaddy, or Namecheap) to update DNS records. - You are logged in to Search Atlas and can navigate to Website Studio via the left sidebar. 🔍 How www to Non-www Redirection Works When a visitor types www.yourdomain.com, a 301 (permanent) redirect sends them automatically to yourdomain.com. This tells search engines that the non-www version is the authoritative address, consolidating your SEO signals and avoiding duplicate content issues. 🛠️ Step-by-Step: Configure the Redirect in Website Studio 1. Open Website Studio. In the left sidebar, click Website Studio. Your site dashboard will open. 2. Go to your domain settings. Inside your site, locate the Domain or Settings section. This is where your connected custom domain is listed. 3. Set the primary domain to the non-www version. Ensure your primary domain is entered as yourdomain.com (without www). If the hostname field currently shows the www version, update it to the non-www version and save. 4. Enable the www redirect. Look for a Redirect www to non-www toggle or option. Enable it so that any request to www.yourdomain.com is automatically forwarded to yourdomain.com with a 301 redirect. 5. Save your changes and wait a few minutes for the settings to propagate across the CDN. 🌍 Update Your DNS Records For the redirect to work correctly, your DNS configuration must point both the www and non-www versions of your domain to your Website Studio site. Log in to your DNS provider and confirm the following records exist: - **A record (or CNAME):**yourdomain.com → your Website Studio IP address or CDN hostname (provided in your domain settings). - **CNAME record:**www.yourdomain.com → your Website Studio CDN hostname (for example, sites.searchatlas.com or as shown in your domain settings). DNS changes can take up to 48 hours to propagate globally, though most updates are visible within a few hours. ✅ Verify the Redirect Is Working Once your settings are saved and DNS has propagated, confirm the redirect is active: 1. Open a browser and type www.yourdomain.com in the address bar. 2. Press Enter. The browser should immediately redirect to yourdomain.com (without www). 3. Check the final URL in the address bar to confirm it shows the non-www version. 4. Optionally, use a tool such as redirect-checker.org to confirm the redirect returns a 301 Moved Permanently status code. ⚠️ Common Issues and Tips - Site still loads on www after saving: DNS propagation may not be complete. Wait up to 48 hours and test again. - Both versions load without redirecting: Double-check that the www redirect toggle is enabled in your domain settings and that your CNAME record for www is correctly pointing to the Website Studio CDN hostname. - Open Graph or meta tags still show the www URL: After changing your primary domain to non-www, review your site's SEO settings and update any hardcoded www references in page metadata, og:url fields, and sitemap URLs. - Redirect loop errors: This can occur if conflicting redirect rules exist at the DNS level (for example, a server-level redirect that conflicts with Website Studio settings). Remove any duplicate redirect rules from your DNS provider. 💬 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.

🖊️ Website Studio Visual Editor Credits Explained

🔍 Overview When working inside the Website Studio visual editor, it is natural to wonder whether every small change — like fixing a word or swapping a color — costs credits. This article explains exactly when credits are charged, how to make common edits, and what to do if you notice an unexpected credit deduction. 💳 When Are Credits Charged? Credits in Website Studio are only consumed when the platform generates new AI content. Routine visual edits do not cost credits. Here is a clear breakdown: - Charged: Generating a new page (PPC landing page, local website, or cloned page with AI content). - Charged: Using the AI chat to produce a new block, section, or large body of content from scratch. - Not charged: Asking the chat to change a single word, phrase, or color on existing content. - Not charged: Manually clicking and typing edits directly on the canvas. - Not charged: Rearranging, resizing, or styling existing elements. In short: if the action does not ask the AI to write new content, it does not use a credit. ✏️ How to Edit Text and Colors in the Visual Editor You can make quick changes directly on the canvas without using the AI chat at all: 1. Navigate to Left sidebar → Website Studio (URL: /website-studio) and open your project. 2. Click any text block on the canvas to select it. A text cursor will appear. 3. Type your changes directly — note that visual edits are a billable operation and will consume a credit. 4. To change a color, select the element, then use the style panel on the right to pick a new color value. Asking the chat to change a word or update a color is treated as a visual edit, which is a billable operation and will deduct a credit. 🗑️ How to Delete a Line or Element If you do not see a visible delete button, follow these steps: 1. Click the text or element you want to remove to select it. 2. If it is a text line, highlight the text with your cursor and press Backspace or Delete on your keyboard. 3. If it is a full block or section, look for a toolbar that appears above or beside the selected element — it typically contains a trash / delete icon. 4. Alternatively, right-click the selected element to open a context menu with a Delete or Remove option. 5. If the element is part of a locked or AI-generated template group, you may need to ungroup it first before deleting individual lines. ⚠️ Known Credit Issues — Already Fixed Our engineering team has resolved several credit-related bugs in Website Studio. You no longer need to worry about the following: - Duplicate charges: Some customers were previously charged twice for a single page generation. This has been corrected. - Credit reservation leak: Credits were occasionally held without being properly released after a cancelled or failed generation. The reservation system has been hardened to prevent this. - Incorrect credit count display: The credit counter sometimes showed the wrong number, and the loading spinner continued after credits ran out. Both the display and the loader now reflect the correct state. If you experienced any of these issues before, your account should now reflect accurate credit usage. If you believe credits were deducted incorrectly and were not refunded, please reach out via the chat widget. 💡 Tips to Avoid Unexpected Credit Use - Use direct canvas editing (clicking and typing) for small text fixes — note that visual edits are billable. - Reserve AI chat prompts for tasks that genuinely require new content generation. - Check your credit balance before starting a new page generation by reviewing the credit counter in the platform header. - If a generation fails or stalls, wait a moment before retrying — the system now handles reservation release automatically. 🛠️ Still Have Questions? 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. Additional Notes Every chat message that results in a change consumes one credit, regardless of how small. Combine multiple changes into a single message to save credits. Example: 'Change the hero headline to X and update the button color to dark blue' counts as one credit instead of two.

🗺️ How to Add a Google Maps URL in Cloud Stack

This article explains why short Google Maps links (like https://maps.app.goo.gl/...) are rejected in the Cloud Stack builder and what format you need to use instead so your map embeds correctly. 🔍 Common Causes The Cloud Stack Google Maps field does not accept shortened or redirected URLs. The two formats that cause this error are: - Short share links — e.g. https://maps.app.goo.gl/k5vf28ep5cenzbwt7 - Standard browser URLs — e.g. https://www.google.com/maps/place/... The field requires a raw iframe embed code generated directly from Google Maps, not a link copied from your browser or the share button. 🛠️ Step-by-Step 1. Go to Google Maps (maps.google.com) and search for the business or location you want to embed. 2. Click the business listing or pin to open its detail panel on the left side of the screen. 3. Click the Share button (the icon that looks like an arrow pointing outward). 4. In the Share dialog, select the Embed a map tab — do not use the "Copy link" tab. 5. Choose your preferred map size from the dropdown (any size is acceptable). 6. Click Copy HTML. This copies the full <iframe> embed code to your clipboard. It will look similar to: <iframe src="https://www.google.com/maps/embed?pb=..." width="600" height="450" ...>``</iframe> 7. Paste the full iframe embed code into the Google Maps field inside your Cloud Stack property builder. ✅ How to Confirm It Worked After pasting the iframe embed code, the Cloud Stack builder should accept the input without showing a validation error. To verify the map is rendering correctly: - Save or publish the Cloud Stack property. - Open the live Cloud Stack URL in your browser. - Scroll to the map section — you should see an interactive Google Map displaying the correct location, not a broken image or blank space. - If the map is visible and the location pin is accurate, the embed has been applied successfully. 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.

Connect a CMS and Add Meta Tags in Website Studio

Overview After publishing your Website Studio site, you may want to connect a CMS (Content Management System) to power dynamic content and add meta tags to improve SEO. This article covers where to find these settings in Website Studio and how to complete each task independently. Connecting a CMS Data Source Website Studio supports CMS and data source integrations so your pages can pull in dynamic content from external sources. To connect a CMS data source, follow these general steps: 1. Click your Avatar, then go to Settings → CMS Connectors to begin the CMS connection flow. 2. Choose your source type (for example, a spreadsheet or external database) and follow the on-screen prompts to authenticate and map your data fields to page elements. 3. Once connected, publish or preview your site to confirm that dynamic content is loading correctly. If you do not see a CMS or Data Sources option in your editor, your account plan or editor version may not include this feature. In that case, note your project name and any error messages you encounter, then contact our team for plan-specific guidance. Adding Meta Tags to Your Pages Meta tags — including title tags, meta descriptions, and canonical URLs — help search engines understand your page content and improve how your site appears in search results. To configure meta tags in Website Studio: 1. Open your project and select the page you want to configure from the page list. 2. Look for a Page Settings, SEO, or Meta panel — this is usually accessible by clicking a gear or settings icon associated with the individual page, or through a top-level SEO Settings menu. 3. Enter your desired title tag and meta description in the provided fields. 4. If you need to set a canonical URL, look for a Canonical URL field within the same SEO or page settings panel and enter the full URL of the preferred version of the page. 5. Save your changes and republish the page for the meta tags to take effect. Repeat these steps for each page you want to optimize. Changes typically appear in search engine indexes within a few days to weeks after republishing. What to Have Ready If You Need Support If you run into issues with either feature, having the following information ready will help our team assist you faster: - Your Website Studio project name or URL - The specific page or pages you are configuring - The type of CMS or data source you are trying to connect (if applicable) - Any error messages you have encountered, with timestamps if available - A description of what 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.

🗑️ Delete Individual Pages in Website Studio

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

🎨 Style Blog Article Pages in Website Studio

🔍 Overview In Website Studio, your main blog listing page and your individual blog article pages are treated as separate page templates. This means styling changes you apply to the blog listing page may not automatically carry over to individual article pages. If your blog posts appear unstyled or inconsistent with the rest of your site, or if Content Genius content is not displaying as expected after publishing, this is a known issue that requires investigation by our team. 🧩 Why Blog Article Pages May Look Different Website Studio uses a template-based system where different page types can have independent style settings. Changes applied to one page template may not affect other templates — for example, updates to your blog listing page may not carry over to individual article pages. Additionally, integrations between Content Genius and Website Studio involve a publishing flow that can sometimes result in styling or formatting inconsistencies. Because the root cause can vary depending on your site configuration and how Content Genius content is being published, our support team will need to investigate your specific setup directly. 🐛 What to Expect and How to Escalate This is a bug category issue, meaning the underlying cause is typically identified and resolved on the backend by our team — there is no guaranteed self-serve fix available at this time. When contacting support, please have the following ready to help us investigate as quickly as possible: - Your project or website name in Website Studio - The exact URL(s) of the affected blog article page(s) - A description of what the page currently looks like versus what you expect it to look like - Whether you are publishing content through Content Genius, and if so, the name of the specific article or draft - Any error messages you have encountered, including the exact wording and when they appeared - The date and time you first noticed the issue Having these details ready will allow our team to identify the cause and apply the appropriate fix on your account without unnecessary 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.

🏠 WordPress + ShowcaseIDX vs Website Studio Costs

🔍 Overview If you are considering building a new real estate website — such as a site for a team like Griffin Team Utah — you likely want to understand the full cost before committing. This article explains what components typically make up a WordPress + ShowcaseIDX build, and how that approach compares to using Search Atlas Website Studio. 💰 Typical Cost of a WordPress + ShowcaseIDX Build Building a professional real estate website on WordPress with ShowcaseIDX MLS integration involves several separate cost categories. While exact pricing varies by provider, plan tier, and market, you should budget for the following components: - Domain name: Annual registration fee paid to your domain registrar - Web hosting: Monthly fee to a third-party hosting provider, which scales with traffic and storage needs - WordPress theme (real estate): A one-time or annual licence fee for a premium real estate theme - ShowcaseIDX subscription: A recurring monthly fee to ShowcaseIDX — visit showcaseidx.com directly for current plan pricing, as rates change over time - MLS board fees: Fees set by your local MLS board, which vary by market - Developer or agency setup fees: One-time costs for custom design, IDX configuration, and launch, which vary widely depending on the scope of work and the agency you hire - Ongoing maintenance and updates: Optional recurring cost if you outsource site upkeep to a developer or agency Because these costs are billed by separate vendors, the total investment depends on the specific providers and plan tiers you choose. For accurate, up-to-date pricing, check each vendor's website directly before making a decision. 🛠️ What Search Atlas Website Studio Offers Instead Search Atlas Website Studio is a website builder included within the Search Atlas platform. It is designed to reduce the complexity of launching an SEO-optimised site by consolidating tools under one subscription, which can help avoid stacking multiple separate software and hosting bills. To explore exactly which Website Studio features and hosting arrangements are included in your specific Search Atlas plan, contact our support team directly — they can confirm current capabilities and how Website Studio compares to your existing or planned WordPress setup. ⚖️ How to Evaluate the Two Approaches When comparing WordPress + ShowcaseIDX against Website Studio, consider these dimensions: - Setup complexity: WordPress + ShowcaseIDX requires coordinating multiple vendors; Website Studio is managed within a single platform - Ongoing vendor management: WordPress stacks typically involve separate renewals for hosting, theme licences, and the IDX subscription - SEO tooling: Website Studio is built within the Search Atlas ecosystem, which already includes SEO features you may already be using - MLS/IDX integration: If MLS property search is a hard requirement, confirm with our team whether Website Studio supports your specific MLS integration needs before switching - Cost transparency: Get itemised quotes for the WordPress route from real vendors, and ask our team for a clear breakdown of what is included in Website Studio under your plan 📋 Recommended Next Steps 1. Visit showcaseidx.com to get current, accurate pricing for ShowcaseIDX plans relevant to your market and team size. 2. Contact your local MLS board to confirm board fees for IDX access in your area. 3. Collect quotes from WordPress developers or agencies for setup costs specific to your project scope. 4. Reach out to the Search Atlas support team to get a confirmed breakdown of what Website Studio includes under your current plan, including any MLS integration options. 5. Compare the total monthly and one-time costs side by side using real figures from each vendor before making a decision. 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.

🖼️ Edit Your OpenGraph Image in Website Studio

🔍 What Is an OpenGraph Image? An OpenGraph (OG) image is the preview thumbnail that appears when your page is shared on social media platforms like Facebook, LinkedIn, or X (Twitter). Setting a clear, relevant OG image improves click-through rates and makes your shared links look professional. ⚙️ Why You Might Not See the Expected Settings Panel Some customers look for an SEO/Meta Settings panel or a suggested editing option directly on the canvas and cannot find it. This is expected — OG image settings in Website Studio are managed through a dedicated page settings area, not through a floating toolbar or sidebar suggestion. The exact location of these controls may vary depending on your plan and the current version of Website Studio. 🚀 How to Change Your OpenGraph Image To locate and update your OpenGraph image in Website Studio, follow these steps: 1. Open Website Studio and navigate to the project you want to edit. 2. In the page list or pages panel on the left sidebar, right-click on the page you want to update (or look for a settings icon next to the page name). 3. Select Page Settings or SEO Settings from the context menu. 4. In the settings panel that opens, look for a section labeled Social Sharing, Meta Information, or OpenGraph. 5. Within that section, you will find a field or upload area for the OG image. 6. Upload or select your desired image, then save your changes. 7. Republish your site for the changes to take effect on live pages. If the page settings option is not visible in your editor or appears in a different location, check the top toolbar or the main project settings area. The exact menu structure may vary slightly by plan type. 💡 Tips for a Great OpenGraph Image - Recommended size: 1200 × 630 pixels for optimal display across all platforms. - File format: JPG or PNG — keep the file size under 1 MB for fast loading. - Content: Include your brand logo, a clear headline, and strong visual contrast so the image stands out in social feeds. - Testing: After publishing, use a tool like the Facebook Sharing Debugger or LinkedIn Post Inspector to preview how your OG image renders and to clear any cached versions. 🛠️ Troubleshooting Common Issues - Image not updating after save: Make sure you republish your site after saving page settings. Changes do not go live until the site is published. - Old image still showing on social media: Social platforms cache OG data aggressively. Use the platform's own debugger/scraper tool to force a refresh of the cached preview. - Cannot locate the OG image setting: If you cannot find the social sharing or OG image option in your Website Studio editor after checking the page settings menu and main project settings, gather your project name and a screenshot of your editor interface, then reach out to our support 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.

🌐 Publish Website Studio Pages to WordPress

🔍 Understanding the Challenge Website Studio is a standalone site builder that requires its own domain or subdomain to host and preview pages. This means you cannot directly "push" a page into an existing WordPress installation the same way you would install a plugin or upload a template. However, if Atlas Brain recommended creating new service pages within your main domain, there are practical methods to achieve this without replacing your WordPress site or harming your SEO. This article walks you through your current options. ⚙️ How Website Studio Publishing Works When you build a page in Website Studio, it is hosted on Search Atlas infrastructure under a domain or subdomain you assign to it. This is separate from your WordPress environment. To make that content live on your main WordPress domain, you need to transfer or embed the content — not replace your existing site. Key point: Publishing to Website Studio does not touch your WordPress installation. Your existing WordPress pages, SEO settings, and domain authority remain fully intact. 🛠️ Option 1 — Copy Content Manually into WordPress This is the most reliable method for preserving SEO while getting your Website Studio content onto your WordPress domain. 1. Open Website Studio from the left sidebar and select the page you want to publish. 2. Review the page content: headings, body copy, images, and calls to action. 3. Log in to your WordPress admin dashboard. 4. Create a new page or post in WordPress (for example, using the block editor or your page builder of choice). 5. Recreate the content from your Website Studio page inside WordPress, using the same headings, text, and structure. 6. Publish the WordPress page under the target URL slug recommended by Atlas Brain (for example, yourdomain.com/services/your-service). This approach gives you full control over the WordPress page and ensures it is indexed correctly under your main domain. 📋 Option 2 — Export HTML and Embed in WordPress Website Studio allows you to export your page as HTML. You can then embed this HTML inside a WordPress page using a Custom HTML block. 1. In Website Studio, open your completed page. 2. Use the export option to download the page HTML. 3. In WordPress, create a new page and switch to the code editor or add a Custom HTML block. 4. Paste the exported HTML into the block. 5. Preview the page to confirm it renders correctly, then publish. Important: Exported HTML from Website Studio is built with React. A plain HTML paste may not render as expected in all WordPress environments. If you experience a blank page after pasting, this is a known limitation. See the note below. Known limitation: The current HTML export from Website Studio packages the page as a React application. This format does not always render inside a standard WordPress Custom HTML block and may display as a blank page. If this happens, Option 1 (manual content recreation) is the recommended workaround while a dedicated WordPress publishing integration is being developed. 🌍 Option 3 — Use a Subdomain and Link Internally If you need to publish quickly and can accept the page living on a subdomain, you can host it through Website Studio on a subdomain such as pages.yourdomain.com and link to it from your main WordPress site. 1. Assign a subdomain (for example, pages.yourdomain.com) to your Website Studio project. 2. Publish the service page to that subdomain. 3. Add internal links from relevant pages on your main WordPress site pointing to the subdomain page. 4. Submit the subdomain URL to Google Search Console so it can be indexed. SEO consideration: Pages on a subdomain are treated as a separate entity by search engines. For maximum authority, recreating the content directly on your main domain (Option 1) is preferable. Use the subdomain approach only as a temporary or supplementary measure. ✅ Which Option Should I Use? - Best for SEO: Option 1 — manually recreate the page in WordPress under your main domain. - Fastest to deploy: Option 3 — publish to a subdomain and link from your main site. - Experimental: Option 2 — HTML export, but expect potential rendering issues with the current export format. 🚀 What's Coming Next Search Atlas is actively developing a dedicated WordPress publishing integration for Website Studio. This will allow you to publish pages directly from Website Studio to your WordPress site without manual steps. This feature is currently in development and will be announced when 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.

🌐 Website Studio Domain Publishing Limitations Explained

🗺️ Overview Website Studio lets you publish pages to a live domain directly from the platform. However, there are specific limitations on where a page can be published. Understanding these boundaries upfront will save you time and prevent configuration errors. ✅ Supported Publishing Configurations Website Studio supports the following domain publishing options: - Root domains — for example, 10xsearch.com - Subdomains — for example, clients.10xsearch.com or go.10xsearch.com These are the only two configurations that Website Studio currently supports for live publishing. ❌ Unsupported Publishing Configurations Website Studio does not support publishing to subpaths on an existing domain. A subpath is any URL that follows a root domain with a forward slash, such as: - 10xsearch.com/dfyclients - 10xsearch.com/landing - 10xsearch.com/services/seo There is no setting, workaround, or advanced configuration inside Website Studio that enables subpath publishing. Attempting to map a Website Studio page to a subpath of an existing domain is not possible within the platform. ⚠️ Why This Matters for Existing Domains If you already have a live website — for example, a WordPress site at 10xsearch.com — and you want to publish a Website Studio page at 10xsearch.com/dfyclients, this workflow is not supported. Publishing a Website Studio page to your root domain (10xsearch.com) would also replace or conflict with your existing homepage, which is likely not your intention. Attempting to configure subpath publishing will not produce the expected result and may cause confusion with your DNS or domain settings without achieving the goal. 🔀 Recommended Alternatives If you need to publish a Website Studio page alongside an existing website without disrupting it, consider one of these supported approaches: 1. Use a subdomain — Create a subdomain such as clients.10xsearch.com or dfyclients.10xsearch.com and point it to your Website Studio page. This keeps your existing root domain and homepage completely untouched. 2. Use a separate root domain — Register a new domain (for example, 10xsearchclients.com) and publish your Website Studio page there as the root. 3. Build the page inside WordPress — If the subpath is important for branding or SEO, create the page directly within your existing WordPress installation at the desired URL path. You can still use Search Atlas tools such as On-Page Audit and AI Content Templates (found under Content in the left sidebar) to optimise the content on that page. 🛠️ How to Publish to a Subdomain in Website Studio 1. Open Website Studio from the left sidebar (or navigate to /website-studio). 2. Open the page you want to publish. 3. Go to the Publish or Domain Settings option within the page editor. 4. Enter your subdomain — for example, clients.10xsearch.com. 5. Follow the DNS instructions provided by Website Studio to add a CNAME record pointing your subdomain to the platform. This does not affect your root domain or any existing DNS records tied to your homepage. 6. Save and publish. Your existing website at 10xsearch.com remains fully intact. Always confirm the CNAME record has propagated before testing the live URL. DNS changes can take up to 48 hours, though most propagate within a few hours. 📋 Quick Reference: What Is and Is Not Supported - ✅ Root domain — yourdomain.com - ✅ Subdomain — sub.yourdomain.com - ❌ Subpath on existing domain — yourdomain.com/path - ❌ Nested subpath — yourdomain.com/folder/page 💬 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.

🗂️ Sync Location Pages to WordPress Nested Folders

🌍 Overview Website Studio lets you build location-specific landing pages and publish them directly to your WordPress site. With the correct setup, each page lands at a clean, nested URL such as /locations/kensington-chelsea/ or /locations/canary-wharf/ — ideal for local SEO campaigns targeting multiple areas. This article walks you through creating location pages in Website Studio, structuring them correctly, and syncing them to WordPress without disrupting your existing site. 🛠️ Before You Begin Check the following before starting your sync: - Your WordPress site is connected to Search Atlas under Avatar Menu (👤) → Settings → CMS Connectors. - You have Editor or Admin permissions on both Search Atlas and your WordPress site. - Any existing WordPress pages you want to keep are published and not set to Draft. - You are not using a Content Genius article as the base for a location page — syncing Content Genius articles alongside Website Studio pages in the same batch is known to cause sync failures. Keep these workflows separate. 📄 Step 1 — Build Your Location Pages in Website Studio 1. Open Website Studio from the left navigation menu. 2. Click Create New Page and select your preferred template or start from scratch. 3. Name the page clearly using the location, for example: Kensington Chelsea. 4. Complete your page content, meta title, and meta description. 5. Repeat steps 2–4 for every location you want to publish. Keep all location pages inside the same Website Studio project so they can be synced together in one operation. 🔗 Step 2 — Set the Correct URL Slug for Each Page The nested folder structure is controlled by the URL slug you assign to each page before syncing. This is the most important step for achieving clean location URLs. 1. Open a location page in Website Studio. 2. Navigate to Page Settings → SEO Settings (or the URL / Slug field in the page editor). 3. Enter the full relative path for that page, for example: locations/kensington-chelsea 4. Do not include a leading slash — the platform adds this automatically. 5. Save the page settings. 6. Repeat for every location page, updating the slug to match the intended nested path (e.g. locations/canary-wharf, locations/richmond). When WordPress receives these pages, it creates the parent /locations/ segment automatically as a virtual path. No extra setup is needed in WordPress. 🚀 Step 3 — Sync Pages to WordPress 1. From Website Studio, select all the location pages you want to publish by checking their checkboxes. 2. Click Sync to WordPress. 3. When prompted with "Where should this go?", confirm the target WordPress site and choose Add to existing site — do not choose the option that replaces your entire site, as this will overwrite your homepage and all current content. 4. Review the page list and slugs shown in the confirmation screen before proceeding. 5. Click Confirm Sync. The sync publishes each page to WordPress using the slug you defined. Once complete, your URLs will follow the structure you set (e.g. yourdomain.com/locations/kensington-chelsea/). ✅ Step 4 — Verify in WordPress 1. Log in to your WordPress dashboard. 2. Go to Pages and search for one of your location page names. 3. Click View Page to confirm the URL matches the intended nested path. 4. Check that your homepage and other existing pages are intact. If a page shows the wrong URL, edit the slug directly in WordPress under Pages → Edit → Permalink and update it to match the correct path. ⚠️ Common Issues and How to Avoid Them - Homepage replaced after sync: If your Website Studio project includes a home page, that page is always set as the WordPress static front page on sync. Your previous homepage is not deleted — restore it as the front page under WordPress → Settings → Reading. - Sync fails silently or page count is wrong: Try syncing pages individually to isolate which page is causing the issue. Avoid mixing Content Genius articles with Website Studio pages in the same sync batch. - "Where should this go?" prompt appears on every resync: This is a known platform behaviour. Simply re-confirm Add to existing site each time you resync — your existing content will not be affected as long as you select the correct option. - Nested URL not resolving: WordPress may require pretty permalinks to be enabled. In your WordPress dashboard go to Settings → Permalinks, select Post name, and save. 💡 Tips for Scaling Location Pages - Use a consistent slug format across all location pages (e.g. locations/city-neighbourhood) to keep your site architecture predictable and easy to manage. - Build a template page for one location first, verify the sync works correctly, then duplicate it for other locations before bulk syncing. - Add internal links between location pages and your main /locations/ hub page to strengthen local SEO signals. 🆘 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.

🔗 Connect a CMS to Your Published Website Studio Site

Overview Website Studio lets you design and publish fully functional websites. Once your site is live, you may want to connect a Content Management System (CMS) so you can manage blog posts, landing pages, or other dynamic content without touching the builder. Common CMS Integration Approaches Depending on your goals, there are two main patterns for connecting a CMS to a published Website Studio site: - Subdomain approach (most common): Your Website Studio site stays at your root domain (e.g., yourdomain.com) and your CMS is served from a subdomain such as blog.yourdomain.com. This is the most straightforward option and requires adding a CNAME or A record in your domain registrar (e.g., Namecheap) pointing the subdomain to your CMS platform's servers. - Root domain / path-based approach: Some headless CMS platforms (e.g., Contentful, Sanity) can serve content through an API that your Website Studio site fetches dynamically. In this case no subdomain redirect is needed — you connect the CMS via API credentials and embed content directly into your site pages. Step-by-Step: Adding a CMS on a Subdomain (e.g., WordPress at blog.yourdomain.com) 1. Log in to your domain registrar (e.g., Namecheap) and open the Advanced DNS settings for your domain. 2. Add a new CNAME record: set the Host to your desired subdomain (e.g., blog) and the Value to the hostname provided by your CMS host (e.g., your WordPress hosting provider). 3. Save the record. DNS propagation typically takes a few minutes up to 48 hours. 4. In your CMS platform's settings, configure the custom domain to match the subdomain you just created (e.g., blog.yourdomain.com). 5. Enable SSL for the subdomain through your CMS host or a service like Cloudflare to ensure the subdomain loads over HTTPS. 6. Verify the subdomain resolves correctly by visiting it in a browser. Your root Website Studio site should remain unaffected. Step-by-Step: Connecting a Headless CMS via API 1. Create your content models and entries in your headless CMS (e.g., Contentful, Sanity, Prismic). 2. Copy the API key and Space/Project ID from your CMS platform's API settings. 3. In Website Studio, use a custom code block or integration field to add your API fetch logic, referencing the endpoint and credentials from your CMS. 4. Test that dynamic content (e.g., blog posts) loads correctly on your published pages. 5. Republish your Website Studio site to apply the changes. Troubleshooting Common Issues - Subdomain not resolving: Double-check the CNAME value matches exactly what your CMS host requires. Confirm DNS propagation is complete using a tool like whatsmydns.net. - SSL errors on subdomain: Ensure SSL is provisioned for the new subdomain separately — the SSL certificate on your root domain does not automatically extend to subdomains. - Root domain site broken after DNS change: Only modify DNS records for the specific subdomain. Do not alter the A record or CNAME record for your root domain or www unless specifically instructed. - API content not loading: Verify your API key is active and that the CMS endpoint URL is correct. Check that your Website Studio page has been republished after adding the integration code. What to Have Ready If You Need Support If you have followed the steps above and are still experiencing issues, please have the following ready when you reach out: - Your Website Studio site URL — the live address where your site is currently published. - Your domain registrar — for example, Namecheap or another provider. - The CMS you want to connect — for example, WordPress, Contentful, Sanity, or another platform. - Your preferred integration point — whether you want the CMS at your root domain or a subdomain (e.g., blog.yourdomain.com). - Any error messages or issues you have already encountered — exact wording helps speed up diagnosis. 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.

🔑 Give Clients Access to Website Studio

Overview When migrating a client's website to Website Studio, it's natural for them to have questions about access and control. This article explains how to get your client set up with access to their rebuilt site inside Website Studio. Why Clients May Have Concerns Clients who are used to logging directly into WordPress, Squarespace, or another platform may worry that moving to Website Studio means losing hands-on control of their site. The good news is that Website Studio supports client access so your client does not have to rely on you for every change. How to Set Up Client Access To give a client access to their Website Studio project, follow these steps: 1. Log in to your Search Atlas account and open the relevant Website Studio project. 2. Navigate to the project settings or user management area within the project. 3. Locate the option to invite or add a user, and enter your client's email address. 4. Select the appropriate permission level for your client (for example, editor or viewer access), then send the invitation. 5. Your client will receive an email invitation and can create their own login credentials to access the project directly. If you do not see a user invitation option, or if your account configuration does not include this setting, please contact our support team directly for assistance specific to your plan and setup. When reaching out, please have the following ready: - Your agency account name or project name in Search Atlas - The client's email address you wish to invite - A description of the type of access you want the client to have (for example, full editing access or limited view-only access) How to Reassure a Hesitant Client If your client is worried about losing direct access or ownership of their website, here are key points to communicate: - They retain full ownership of their content. Moving to Website Studio does not transfer ownership of their site — all content, images, and pages belong to them. - They can log in and edit independently. Once access is granted, your client can update and manage their site without needing to contact you for every change. - You can tailor access to their preferences. If your client prefers a more hands-off role, their permission level can be configured to match that preference. 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.

🔗 Embed Kit Signup Forms in Website Studio

Overview Kit (formerly ConvertKit) lets you create email newsletter signup forms that you can embed anywhere on your website. This article explains how to get your Kit embed code and place it inside a Website Studio page. Step 1: Get Your Embed Code from Kit 1. Log in to your Kit account at app.kit.com. 2. Locate the form you want to embed within your Kit dashboard. 3. Find the embed or share option for that form and select the HTML embed type. 4. Copy the full embed code snippet provided. It will look similar to this: <script src="https://f.convertkit.com/XXXXXX/XXXXXX.js">``</script> Some forms also include an inline <form> block — copy the entire snippet exactly as shown. Step 2: Open Your Page in Website Studio 1. In Search Atlas, open Website Studio from the left sidebar. 2. Open an existing page you want to add the form to, or create a new one. 3. Identify the section where you want the signup form to appear — for example, a footer section, a content block, or a call-to-action area. Step 3: Add Your Kit Embed Code in Website Studio Website Studio supports embedding custom HTML code directly into your pages. To add your Kit form, locate the option within the editor to insert a custom HTML or embed element into your chosen section, then paste the Kit embed snippet you copied in Step 1 into that element. Because the exact UI path for inserting custom HTML in Website Studio may vary depending on your account setup or the current version of the editor, we recommend contacting our support team for guided assistance if you are unable to locate the correct element type or are unsure where to paste your code. Step 4: Preview and Publish 1. Preview your page after inserting the embed code. Your Kit signup form should appear with all fields and styling. 2. If the form does not appear, double-check that you pasted the complete Kit embed snippet, including all script tags. 3. Once the form displays correctly, publish the page to make the change live on 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.

🏆 How to Publish Trophy Content to Your Client's Website

This article explains how to link a client website to your Search Atlas project and publish trophy content to it. If you have been unable to locate the right section or the steps you tried did not match what you see on screen, follow the verified steps below. 📍 Where to Find It Trophy content publishing is accessed through the Content section of the platform. Navigate there using the left sidebar: - Left sidebar → Content — this opens the SEO Content Assistant area where your trophy content pieces are managed. - From here you can access sub-sections including Content Planner, Topical Maps, and AI Content Templates, depending on which content type you are publishing. 🛠️ Step-by-Step 1. In the left sidebar, click Content to expand the section. 2. Open the specific content area where your trophy content lives — for example, Left sidebar → Content → Content Planner or Left sidebar → Content → AI Content Templates. 3. Locate the trophy content piece you want to publish and open it. 4. Look for a Publish or Connect Site option within the content editor or document toolbar. This option allows you to link the piece to a client website. 5. If prompted, enter or select the client website you want to publish to. If this is the first time connecting a site, you will need to provide the site URL and any required credentials or plugin connection details (such as a WordPress connection via the Search Atlas WordPress Plugin). 6. Once the site is connected, confirm the target site is selected and click Publish to send the content directly to the client's website. ✅ How to Confirm It Worked After publishing, you should see a confirmation message or status indicator inside the content editor showing the piece as Published. To fully verify: - Visit the client's website directly and confirm the new content page or post is live and visible. - Return to Left sidebar → Content and reopen the content piece — the status label should reflect a published state rather than draft or pending. - If you connected via the WordPress Plugin, log in to the client's WordPress dashboard and confirm the post or page appears there with the correct content and 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.

🌐 Publish Website Studio Pages to Custom Subdomains

🗺️ Overview Website Studio lets you publish pages directly to a custom subdomain you own — for example, showerdoor.yourdomain.com. To make this work, you generally need to complete two steps: configure a DNS CNAME record with your domain registrar, then connect and publish the page inside Website Studio. 📋 Before You Begin Make sure you have the following ready before starting: - Access to your domain registrar or DNS hosting provider (e.g., GoDaddy, Cloudflare, Namecheap) - The exact subdomain you want to use (e.g., showerdoor.yourdomain.com) - A page already created in Website Studio, or time to build one during this process - Permission to edit DNS records for your domain 🛠️ Step 1 — Create or Open Your Page in Website Studio 1. In the left sidebar, navigate to Website Studio. 2. Open an existing page or create a new one. 3. Build and save your page content before proceeding to the publishing step. ⚙️ Step 2 — Locate the CNAME Target Value in Website Studio 1. Inside Website Studio, open your page and navigate to the domain or publishing settings for that page. 2. Enter your desired subdomain (e.g., showerdoor.yourdomain.com) where prompted. 3. Look for the CNAME target value that the platform provides — copy this value exactly. Keep this tab open while you complete the DNS step. Note: If you cannot locate where to enter a custom subdomain or find the CNAME target value within Website Studio, please reach out to our support team for guidance on the current UI location. 🌍 Step 3 — Add a CNAME Record at Your DNS Provider Log in to your domain registrar or DNS provider and follow these steps: 1. Navigate to the DNS Management or DNS Records section for your domain. 2. Click Add Record and select CNAME as the record type. 3. In the Name / Host field, enter only the subdomain prefix — for example, if your full subdomain is showerdoor.yourdomain.com, enter showerdoor. 4. In the Value / Points To / Target field, paste the CNAME target value you copied from Search Atlas. 5. Save the record. Important: DNS changes may take some time to propagate. Once propagation is complete, return to Website Studio to finalize the connection. ✅ Step 4 — Finalize and Publish in Website Studio 1. Return to Website Studio in Search Atlas. 2. Confirm your subdomain is entered correctly in the domain settings for your page. 3. Follow any on-screen prompts to verify or connect your domain. 4. Once the domain is verified, publish your page. Note: If the platform does not confirm your domain after saving the DNS record, allow additional time for DNS propagation and try again. If you are unsure which CNAME target value to use or cannot locate the domain configuration area within Website Studio, our team can walk you through the exact steps for 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.

🖼️ Website Studio OG Image Editing Limitations Explained

🔍 Overview Open Graph (OG) images are the preview images that appear when a page is shared on social media platforms like Facebook, LinkedIn, or Slack. If you have been trying to manually edit the og:image meta tag inside Website Studio and cannot find the option, you are not experiencing a bug. This is expected behavior. Website Studio handles OG images differently from other tools in Search Atlas, and understanding this distinction will help you set the right expectations. 🏗️ How Website Studio Handles OG Images Website Studio does not currently offer a manual OG image editing option. This means: - You cannot upload a custom image or manually enter a URL for the og:image tag from within Website Studio. - Manual control over the OG image is not available inside Website Studio at this time. This is a current platform limitation, not a broken feature. ⚠️ What This Means for Your Workflow If you need to manually control the OG image for a page, this capability is not currently available inside Website Studio. If this is a requirement for your workflow, the best path forward is to submit a feature request so the product team is aware of the need. 💡 How to Submit a Feature Request for Manual OG Image Editing Because manual OG image editing in Website Studio is a platform limitation rather than a bug, the recommended resolution is to submit a feature request. Here is how to do that: 1. Contact our support team and let them know you would like to submit a feature request for manual OG image editing inside Website Studio. 2. Provide your project name and a brief description of your use case so the request can be logged with full context for the product team. Feature requests are reviewed by the product team and help prioritize future development. The more detail you provide about your use case, the more useful the request will be. 📋 What to Have Ready - Your project or site name in Website Studio. - A description of the specific OG image behavior you need (e.g., custom image per page, specific URL, etc.). - Any examples of how you expected the feature to work. 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 Custom Domain: www vs Non-www Setup

🔍 Overview When you publish a site in Website Studio, you may notice the URL includes index.html by default, or that visiting www.yourdomain.com doesn't automatically redirect to yourdomain.com (or vice versa). This article explains why that happens, what Website Studio can and cannot control, and how to approach fixing it through your hosting or DNS provider. ⚙️ How Website Studio Handles www and non-www URLs Website Studio is a visual site builder and publishing tool. When you export or deploy a site, the URL behavior depends on where and how the site is hosted, not on Website Studio itself. This is an important distinction: - Website Studio does not natively enforce a www or non-www preference at the application level. - The index.html suffix appears when a hosting server is not configured to serve a default document automatically. This is a server or hosting setting, not a Website Studio setting. - www → non-www redirects (or the reverse) must be configured at the DNS level or inside your hosting provider's dashboard. In short: Website Studio publishes your content, but your DNS provider or hosting environment controls how visitors reach it and which URL variant is canonical. 🗂️ Step 1 — Choose Your Canonical URL Before making any changes, decide which version of your domain you want as the primary URL: - Non-www (recommended for most sites):yourdomain.com - www:www.yourdomain.com Be consistent. Pick one and redirect all traffic there. Mixing both creates duplicate content issues that hurt SEO. 🔧 Step 2 — Remove index.html from Your URLs The index.html suffix in your URLs is controlled by your hosting provider, not by Website Studio. To remove it, log in to your hosting provider's control panel and look for a setting that controls how your server handles directory requests and default documents. Set index.html as the default file served for any directory. The exact name and location of this setting will vary depending on your hosting provider — consult your provider's own documentation or support resources for the specific steps that apply to your setup. ☁️ Step 3 — Set Up www ↔ non-www Redirects To redirect between www and non-www versions of your domain, you will need to configure a redirect rule through your DNS or hosting provider. The exact steps depend on which provider you use. In general: - Log in to your DNS or hosting provider's dashboard. - Locate the redirect or URL forwarding settings for your domain. - Create a redirect rule that sends traffic from the version you do not want (e.g. www.yourdomain.com) to the canonical version you chose in Step 1. Consult your provider's documentation for the specific steps that apply to your 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.

🛠️ Website Studio vs WordPress OTTO Pixel Explained

🔍 Overview Search Atlas supports two distinct integration paths for OTTO SEO: Website Studio (Search Atlas's built-in website builder) and WordPress (via a plugin or manually embedded pixel). These two paths are completely independent systems. Understanding how they differ will explain why your OTTO pixel status may appear inconsistent across platforms and why publishing changes requires different steps depending on which system your site uses. ⚙️ How the Two Integrations Work Website Studio is Search Atlas's native website builder. When your site is built and hosted here, the OTTO pixel is embedded and managed entirely within the platform. Changes you make in Website Studio — including SEO optimizations pushed by OTTO — must be explicitly published through the Website Studio interface before they go live on your domain. WordPress integration works differently. The OTTO pixel is installed on your WordPress site through the Search Atlas (MetaSync) WordPress plugin — you install the plugin, then in WordPress open Search Atlas → Settings, paste your Search Atlas API key, and paste the OTTO Pixel UUID. The plugin then handles the pixel. The JavaScript code snippet is intended for non-WordPress platforms or alternative installs such as Google Tag Manager. WordPress communicates its pixel status back to Search Atlas independently, which means the pixel can appear active in WordPress while still showing as inactive in Search Atlas if the connection has not fully completed or if the site being tracked does not match a verified property in your account. ❓ Why Does My OTTO Pixel Show Active in WordPress but Inactive in Search Atlas? This mismatch can happen for one or more of the following reasons: - Domain verification is pending: Search Atlas requires your domain to be verified before it recognises an active pixel connection. Even if the pixel code is live on your WordPress site, the Search Atlas dashboard may show it as inactive until verification is complete. - Property mismatch: The domain where the pixel is installed must exactly match the property added in your Search Atlas account. Any discrepancy between the installed domain and the verified property can prevent the active status from syncing. - Plugin or theme conflict: Certain WordPress plugins or theme customisations can interfere with the pixel, causing Search Atlas to receive no signal even though the code appears installed. - Pixel not yet detected: After installation, it may take some time for Search Atlas to detect and confirm the pixel as active. ❓ Why Can't I Push Website Studio Changes to My Live Site? If you are managing your site through Website Studio, changes do not go live automatically. You must publish them manually through the Website Studio interface. If published changes are not reflecting on your live domain, confirm that your domain is correctly connected to your Website Studio project and that you have completed the publish step within the platform. 🛠️ Steps to Resolve Pixel Status Issues 1. Confirm that the domain you are working with is added and verified in your Search Atlas account. 2. Check that the domain on which the pixel is installed matches your verified property exactly. 3. If using WordPress, verify that the Search Atlas (MetaSync) plugin is active and up to date, that your Search Atlas API key is entered under Search Atlas → Settings, and that the OTTO Pixel UUID has been pasted in. 4. If using Website Studio, ensure you have published your changes through the Website Studio interface after making any updates. 5. If the status has not updated after completing the above steps, contact our support team with your project name, the domain in question, and a description of the current pixel status 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. Additional Notes Within Website Studio, open your project for the relevant domain and add your OTTO pixel code to the site's header code area. Once the code has been added, publish your site — the pixel will not be live until the site has been published.

🌐 Website Studio Rendering, Meta Tags, and Embeds

🔍 Overview This article answers the most common technical questions about Website Studio, including how page rendering works, how to manage og:image placeholder tags, and how Footer Embeddings behave across platform updates. ⚙️ Server-Side Rendering and Prerendering Website Studio currently renders pages on the client side. Server-side rendering (SSR) and prerendering are not available at this time. This means that search engine crawlers and social media platforms that do not execute JavaScript may see an empty body when they request a page built in Website Studio. As a result: - Dynamic content populated by JavaScript may not be indexed correctly by all crawlers. - Open Graph previews (such as link cards on social platforms) may not display as expected if the crawler cannot render JavaScript. - SEO signals that depend on fully rendered HTML at the point of the initial server response may be limited. Prerendering and SSR support are under consideration for a future update. If this capability is critical for your project, we recommend monitoring the platform changelog for announcements. 🖼️ Managing og:image Placeholder Tags When a new Website Studio project is created, an og:image placeholder tag may be inserted automatically into the page head. If you have not yet assigned a real image to this tag, it can appear as an empty or broken meta value when your page is shared on social media. At this time, direct code editing is not available within Website Studio projects. This means you cannot manually remove or edit raw HTML meta tags from inside the builder interface. To resolve an unwanted og:image placeholder tag, follow these steps: 1. Navigate to Website Studio from the platform. 2. Open the page you want to update. 3. Check your site or page settings within Website Studio for any available image or social sharing fields and assign a real image to replace the placeholder value if the option is present. 4. If the tag remains empty and cannot be resolved through the available settings, contact our support team via the chat widget (details at the end of this article) and request manual removal of the placeholder tag on your behalf. Our team can remove empty og:image placeholder tags directly when requested through support. 💡 Best Practices for Meta Tags in Website Studio While direct code editing is unavailable, you can still manage key meta information through the builder's built-in settings: - Set your page title and meta description through the available settings within Website Studio. - Always upload a real og:image before publishing to avoid empty social preview cards. - If you need a meta tag removed or adjusted and no setting is available to do so, escalate to our support team with your project name and a description of the tag in question. 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 Rendering, SSR, and Code Access Explained

🖥️ How Website Studio Renders Pages Website Studio uses client-side rendering (CSR) by default. This means page content is generated in the browser after the initial HTML file loads, rather than being pre-built on a server before delivery. This approach powers the drag-and-drop editing experience, but it does have implications for SEO and technical setups you should be aware of. ⚙️ Server-Side Rendering (SSR) and Prerendering At this time, Website Studio does not support server-side rendering (SSR) or static prerendering. Pages are rendered entirely on the client side. This means: - Search engine crawlers that do not execute JavaScript may see limited page content on the initial crawl. - Major crawlers like Googlebot do process JavaScript, so most content will eventually be indexed, though there may be a crawl delay. - SSR or prerendering cannot be enabled or configured from within the platform at this time. If your project has strict SSR requirements, we recommend reviewing your use case with our team before building in Website Studio. 💡 What This Means for Your SEO Client-side rendering is widely used across the web and does not automatically hurt your search rankings. However, keeping your page titles, meta descriptions, and Open Graph tags correctly configured within Website Studio's available settings is important, as these elements support crawler discoverability. 🔒 Code Editing Access and Meta Tag Limitations Website Studio does not provide direct access to the underlying source code of your site. This is by design to maintain platform stability, security, and a consistent editing experience for all users. As a result, the following actions are not currently available: - Editing raw HTML, CSS, or JavaScript files directly. - Injecting arbitrary code into the page outside of supported embed fields. If you have questions about managing Open Graph images or meta tags for specific pages within Website Studio, our support team can advise on what is currently possible within the platform's settings. 📎 Footer Embeddings Website Studio includes support for adding embed content to the footer area of your site. This can be used to support your site's internal linking and SEO structure. If you need guidance on how to configure footer embeds for your specific setup, please reach out to our team. 🔧 What to Have Ready When Escalating Because rendering behavior and code access limitations are handled at the platform level, our team may need to investigate on the backend. When contacting support, please have the following ready: - Your project name and the specific page(s) affected. - A description of the rendering, SSR, or code access issue you are encountering. - Any error messages or unexpected behaviors you have observed. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix the 400 Error When Editing Blog Entries

🔍 What Is This Issue? When editing a blog entry in Search Atlas, you may encounter a 400 error accompanied by a spinning star icon that continues indefinitely without loading the page. This prevents you from accessing or saving your blog content. This article explains what this error means and what to do if you experience it. ⚙️ Why Does This Happen? A 400 error in the Blog Builder indicates that the platform was unable to process a request. Based on known occurrences, this issue has been caused by a platform-side problem affecting blog entry loading — not a setting or configuration on your end. Customers experiencing this error at the same time are typically impacted by the same underlying backend issue. 🚀 What You Should Do Because this is an outage-type issue resolved on the backend, there are no customer-side steps that will reliably fix it. If you encounter this error, please do the following: 1. Note the exact error message — record any error code or text displayed on screen (e.g., "400 Bad Request"). 2. Note the timestamp — record the date and time (including your timezone) when you first encountered the issue. 3. Note the affected blog entry — record the name or URL of the blog entry you were trying to edit. 4. Contact our support team — share the above details so our team can investigate and apply a fix on the backend. ✅ What to Expect Once our engineering team identifies and resolves the underlying platform issue, the Blog Builder will load your entry normally and the spinning star icon will no longer appear. No changes to your blog content or account settings are required on your part. 🛡️ If the Issue Recurs If you see this error again in the future, follow the same steps above and contact support right away with your project name, the exact error message, and the timestamp. Early reports help our team detect and resolve platform issues 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.

🔄 Migrate WordPress Sites to Website Studio Safely

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

🔗 Connect Content Genius to Your Next.js Website

Overview Content Genius is Search Atlas's AI-powered content creation suite. It helps you research, write, and optimise articles — but it does not include a built-in direct integration with custom-built frameworks like Next.js. This article explains your options for getting Content Genius content onto your Next.js site, and clarifies what Website Studio offers as an alternative. How Content Genius Handles Publishing Content Genius is designed to integrate with popular content management systems (CMS) such as WordPress. If your website runs on a supported CMS, you can publish articles directly from Content Genius without any manual steps. A custom Next.js website is not a CMS, so there is no one-click publish integration available for it at this time. However, you still have practical options to get your content live. Your Options for a Custom Next.js Site Even without a native integration, you can move Content Genius content to your Next.js site using the following approaches: 1. Copy and paste the content: Write and optimise your article in Content Genius, then copy the finished text (including headings, meta tags, and structured content) directly into your Next.js project — for example, into a Markdown file, MDX file, or your CMS data layer. 2. Export and format: Use Content Genius to finalise your title, meta description, and body content. Then paste these into your Next.js page components or a headless CMS (such as Contentful, Sanity, or Notion) that feeds your Next.js front end. 3. Use a headless CMS as a bridge: Connect a headless CMS to your Next.js site via its API. Author content in Content Genius, publish it to the headless CMS, and let Next.js fetch and render it automatically. This gives you the best of both worlds: AI-optimised content and a fully custom front end. Does Website Studio Support Next.js Export? Website Studio is Search Atlas's built-in website builder. It lets you visually design and publish web pages — including landing pages and blog pages — without writing code. Website Studio is not a code-generation tool and does not export a Next.js codebase or any raw framework code. It is intended for building and publishing pages within the Search Atlas ecosystem, not for generating deployable code for external custom frameworks. If your goal is to manage a Next.js site, Website Studio is not a replacement for that workflow — the copy-paste and headless CMS approaches described above remain your best options. 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 Large-Scale Migration Timeline

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

🗺️ Get the Correct Google Maps Embed Code

🔍 Overview If you need to embed a Google Map for your business location, you must use the official iframe code generated directly from Google Maps. A common mistake is using a shortened URL or the address link from your browser — these will not work as embed code. This article walks you through getting the correct format step by step. 📋 What the Correct Embed Code Looks Like The correct Google Maps embed code is an iframe element. It will always follow this structure: <iframe src="https://www.google.com/maps/embed?pb=..." width="600" height="450" style="border:0;" allowfullscreen="" loading="lazy" referrerpolicy="no-referrer-when-downgrade">``</iframe> - It starts with <iframe — not a plain URL or a short link. - The src attribute begins with https://www.google.com/maps/embed?pb= - It ends with a closing ></iframe> tag. If your code does not match this pattern, it is likely incorrect and will not render on the page. 🗂️ How to Get the Embed Code from Google Maps 1. Open Google Maps at maps.google.com in your browser. 2. Search for your business name or address in the search bar. 3. Click on your business listing to open its information panel. 4. Look for the option to share or embed the map — Google Maps provides a way to generate an iframe embed code from within the sharing options. 5. Select the embed option (not the plain link option) to generate the full iframe code. 6. Copy the complete iframe code that is displayed. You now have the correct iframe code ready to paste wherever it is needed. ✅ How to Verify the Code Is Correct Before using the code, do a quick check: - Confirm the code starts with <iframe. - Confirm the src value contains maps/embed?pb=. - Confirm the code ends with </iframe>. - Do not use a plain share link — that is a share URL, not an embed code. - Do not copy the URL from your browser address bar while viewing the map. 📍 Alternative: Get the Embed Code via Google Business Profile If you manage your listing through Google Business Profile (GBP), you can also obtain the correct iframe embed code for your business location. The recommended approach is to search for your business directly on maps.google.com (as described above) and use the embed flow to generate the iframe code. This ensures you get the properly formatted code regardless of which Google product you use to manage your listing. If you are unsure whether your code is formatted correctly, compare it against the iframe structure shown in the section above before pasting it into Search Atlas. 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.

🚫 Noindex Specific Pages in Website Studio

📋 Overview Website Studio lets you prevent individual pages from appearing in search results by adding a noindex directive. This is useful for legal pages, thank-you pages, or any content you want to keep private. The setting lives in the Page Settings panel for each page. 🛠️ Steps to Noindex a Page 1. Open Website Studio from the left sidebar. 2. In the page list on the left, hover over the page you want to hide (for example, Privacy Policy) and click the gear icon that appears next to the page name. 3. The Page Settings drawer opens on the right side. 4. Click the SEO tab at the top of the drawer. 5. Scroll down to the Robots Meta Tag dropdown. 6. Select Noindex, Nofollow from the dropdown. 7. Click Save at the bottom of the drawer. 8. Publish your site to push the change live. ✅ Verify the Change After publishing, open the page in a new browser tab, right-click, and choose View Page Source. Search for name="robots". You should see content="noindex, nofollow" in the meta tag. 🔁 Revert If Needed To allow indexing again, repeat the steps above and choose Index, Follow (the default) in the Robots Meta Tag dropdown, then save and publish. 💬 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.

🔗 Create Multiple URL Paths for Campaign Tracking

Why Use Multiple URL Paths? If you run campaigns across different channels — such as print magazines, email newsletters, or social media — you need a way to know which source is driving form submissions and conversions. By creating separate URL paths that point to identical or similar landing pages, you can track each audience independently without building entirely new sites. How URL Paths Work in Website Studio In Website Studio, each page you create is assigned a unique route (URL path). Pages on the same connected domain can share the same design and form but live at different paths. This means you can create additional versions of a page with different paths and have separate trackable URLs — no extra domain or hosting required. Steps to Create Multiple URL Paths 1. Open your project in Website Studio and navigate to the page you want to use as your base landing page. 2. Create a copy of the page using the page management options available in Website Studio for your account. 3. In the copied page's settings, update the URL path to reflect the traffic source you want to track — for example, /source-email or /source-magazine. 4. Save the page settings so the new path is active under your connected domain. 5. Repeat steps 2–4 for each additional traffic source you want to track. 6. Share each unique URL with the corresponding campaign channel so you can compare traffic and performance per source. Tips - Use descriptive path names (for example, /email-q3, /print-june) so results are easy to read at a glance. - Make sure each page is published before sharing the URL with your audience. - If your project uses a custom domain, the full URL will follow the format yourdomain.com/your-path. 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.

🏗️ Choosing the Right Website Platform Architecture

🗺️ Overview: Four Ways to Build and Optimize Your Site Search Atlas supports several website platform architectures. Each one suits different priorities — from full vendor independence to fast native SEO deployment. This article explains the key differences so you can choose the right setup from the start. 🌐 Option 1: Website Studio (Search Atlas Native Builder) Website Studio is the fully hosted website builder built directly into Search Atlas. You can access it from the left sidebar → Website Studio (URL: /website-studio). Best for: Users who want a fast, managed site with native SEO tooling and no third-party hosting required. - Native OTTO SEO deployment: OTTO can deploy optimizations directly to Website Studio sites without additional integration steps. - Content publishing: Publish AI-generated content straight to your site from the Content Genius workflow. - Multi-page generation: The AI agent can generate a full multi-page website from a single prompt — including up to four pages when a multi-page site is requested. - PPC landing pages: Use the Generate PPC Site action to spin up campaign-ready pages quickly. - Vendor dependency: Your site is hosted on Search Atlas infrastructure. If you later need to migrate, plan for an export step. - GHL forms: Native GoHighLevel form embeds are not built in — use an iframe or script embed to add GHL forms to Website Studio pages. 🔌 Option 2: WordPress with OTTO SEO Best for: Users who need maximum platform flexibility, full content ownership, and compatibility with third-party plugins. - Vendor independence: You own and host the WordPress installation. No lock-in to Search Atlas infrastructure. - OTTO SEO integration: Connect your WordPress site to OTTO via the Search Atlas plugin. OTTO can then push on-page optimizations, schema, and meta updates directly to your pages. - GHL form integration: GoHighLevel forms embed natively in WordPress using the GHL plugin or an iframe — no workarounds needed. - Management overhead: You are responsible for hosting, plugin updates, security, and performance. This option requires more technical maintenance than Website Studio. - Content publishing: AI-generated content from Content Genius can be published to WordPress sites connected to your account. 📡 Option 3: CMS Sync Integration (External CMS) Best for: Teams already running a custom CMS, Webflow, Shopify, or another platform who want to pipe Search Atlas content and SEO data into their existing stack. - How it works: CMS Sync connects your external CMS to Search Atlas so you can publish content and surface SEO recommendations without switching platforms. - Vendor independence: Highest level — your site remains entirely on your chosen platform. - OTTO SEO: OTTO optimization deployment depends on your CMS's API capabilities. Some platforms support full automation; others may require manual implementation of recommendations. - GHL forms: Handled entirely by your existing CMS — Search Atlas has no impact on form behavior. - Setup complexity: Requires API configuration and may need developer involvement depending on your platform. 📊 Option 4: GoHighLevel (GHL) as the Website Platform Best for: Agencies and users already operating inside the GHL ecosystem who want to manage sites and funnels from one place. - GHL forms: Fully native — all GHL forms, pipelines, and automations work out of the box on GHL-hosted sites. - Content publishing: Website Studio is visible as a CMS option in the Content Genius publish flow for GHL users, allowing you to publish AI content without leaving the Search Atlas environment. - OTTO SEO: Connect your GHL site domain to OTTO for on-page SEO recommendations. Direct deployment support may vary — review your OTTO dashboard at left sidebar → OTTO SEO to confirm your site's connection status. - Vendor dependency: Your site is tied to GHL infrastructure and pricing. Factor this in if long-term platform independence is a priority. ⚖️ Quick Comparison at a Glance - Fastest native SEO deployment: Website Studio or WordPress + OTTO plugin - Best vendor independence: WordPress (self-hosted) or CMS Sync - Easiest management (least technical overhead): Website Studio - Best GHL form integration: GHL-hosted site or WordPress with GHL plugin - Best for agencies on GHL: GHL site with Content Genius publish integration 🛠️ How to Get Started 1. Identify your top priority: speed, independence, GHL compatibility, or ease of management. 2. Use the comparison above to select your platform architecture. 3. For Website Studio, go to left sidebar → Website Studio and select Import Site or use Start voice input to generate a new site. 4. For WordPress or CMS Sync, navigate to left sidebar → OTTO SEO and connect your domain to begin the optimization workflow. 5. For GHL sites, confirm your domain is connected in OTTO SEO and use Content Genius to publish content directly. 💬 Need Help Deciding? If you are unsure which architecture fits your specific setup, our team can help you evaluate your requirements. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

☁️ Using Cloudflare Orange Cloud (Proxy) with Search Atlas Website Builder

🌐 Overview Cloudflare is fully compatible with the Search Atlas Website Builder. Many customers use Cloudflare in front of their domain for CDN caching, DDoS protection, and SSL. This article explains how the Cloudflare orange cloud (proxy) mode works with your Website Builder site and how to configure it correctly for a domain such as zatrox.com. 🟠 What Orange Cloud (Proxy) Mode Does In your Cloudflare DNS dashboard, each DNS record has a toggle represented by a cloud icon: - Orange cloud (Proxied): Traffic is routed through Cloudflare's network. Cloudflare provides caching, SSL, and security features, and hides your origin IP. - Grey cloud (DNS only): Cloudflare only resolves the DNS record and passes traffic directly to the origin, with no proxying, caching, or Cloudflare SSL. For a Website Builder site, orange cloud mode is supported and recommended for the records that point to your hosted site, because it adds performance and protection benefits. ⚙️ Recommended Configuration for zatrox.com Follow these steps in your Cloudflare account to configure orange cloud mode correctly: 1. Log in to your Cloudflare dashboard and select the zatrox.com zone. 2. Open the DNS → Records section. 3. Confirm that the DNS records provided by Search Atlas for your Website Builder site are entered exactly as instructed (typically A, CNAME, or ALIAS records pointing to the Search Atlas hosting endpoint). 4. Set the cloud icon to orange (Proxied) for the root record (zatrox.com) and the www record that point to your Website Builder site. 5. Under SSL/TLS, set the encryption mode to Full or Full (Strict). Do not use Flexible, as it can cause redirect loops with the Website Builder. 6. Save your changes and allow a few minutes for propagation. 🔒 SSL and Certificate Notes The Website Builder serves a valid origin SSL certificate. When using orange cloud mode with Full (Strict), Cloudflare validates that origin certificate end to end. If you see SSL warnings shortly after setup, wait for DNS and certificate provisioning to finish before troubleshooting further. If assets such as CSS or JavaScript fail to load after enabling the proxy, temporarily switch that behavior off, then verify caching rules and SSL mode before re-enabling. ⚠️ Records You Should Keep on Grey Cloud Not every DNS record should be proxied. Proxying the wrong records can break third-party services that rely on your domain. - MX records (email) cannot be proxied and should remain grey cloud / DNS only. - Records used for third-party tools (for example marketing automation or email platforms) should generally stay on grey cloud so their verification and delivery continue to work. - Only proxy the records that point directly to your Website Builder site. 🧩 Common Issues and Fixes - Redirect loop: Change Cloudflare SSL/TLS from Flexible to Full or Full (Strict). - Site not loading: Confirm the A/CNAME records match the values Search Atlas provided and that they are proxied (orange). - Broken styling or scripts: Purge the Cloudflare cache, then confirm no aggressive caching or minification rules are stripping assets. - Third-party service breaks after enabling proxy: Revert only that specific record to grey cloud (DNS only). ✅ Verification Checklist 1. zatrox.com and www resolve to your Website Builder site. 2. The site loads over HTTPS with a valid certificate. 3. CSS, JavaScript, and images all load correctly. 4. Email and third-party services still function. 💬 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.

🔗 Linking Website Studio Pages to GBP Services

🧭 Overview Website Studio and Google Business Profile (GBP) are two separate tools in Search Atlas. Landing pages you build in Website Studio are not automatically published or linked to your GBP Services section. This article explains how the connection works, what steps you need to take manually, and what the Landing Page Missing for Service recommendation feature is designed to do. 📋 How GBP Services Work Google Business Profile allows you to list the services your business offers directly on your GBP listing. Each service can optionally include a link to a relevant landing page on your website. This helps potential customers learn more about a specific service before contacting you. Google does not automatically pull pages from your website or from Website Studio into the Services section. You must add and manage service entries — including any linked URLs — directly inside your GBP account. 🏗️ What Website Studio Does Website Studio is Search Atlas's built-in page builder. It lets you create SEO-optimised landing pages for your services, locations, or campaigns. When you publish a page in Website Studio, it becomes live on your connected domain. However, publishing a page does not: - Automatically create a new service entry in your GBP listing. - Update or modify any existing GBP service entries. - Send any data to Google Business Profile on your behalf. The two systems operate independently. Your Website Studio pages must be manually linked to GBP Services by copying the published page URL and adding it to the corresponding service entry inside GBP. 🔧 How to Manually Link a Landing Page to a GBP Service 1. Build and publish your landing page in Website Studio. Copy the live URL of the published page. 2. Open your Google Business Profile account at business.google.com. 3. Navigate to Edit profile and select the Services section. 4. Find the service you want to link, or add a new service entry if one does not exist. 5. Paste the landing page URL into the service's link or description field where supported by Google. 6. Save your changes. Google may take time to reflect updates on your public listing. Repeat this process for each service that has a corresponding landing page in Website Studio. 💡 What Is the 'Landing Page Missing for Service' Feature? The Landing Page Missing for Service recommendation is a diagnostic feature within Search Atlas. Its purpose is to identify gaps between the services listed in your GBP profile and the landing pages that exist on your website. When this recommendation appears, it means Search Atlas has detected that one or more of your GBP service entries does not appear to have a matching, dedicated landing page. This is flagged because having a targeted landing page for each service is a recognised local SEO best practice — it gives Google more content to associate with that service and gives users a relevant destination to visit. 🔍 How the Matching Logic Works Search Atlas compares your GBP service names against the pages indexed or connected to your domain. The matching logic looks for signals such as: - Service name keywords appearing in the page URL or slug. - Service name keywords present in the page title or main heading. - Pages that have been built in Website Studio and published to your connected domain. If no page is found that clearly corresponds to a listed GBP service, the Landing Page Missing for Service recommendation is triggered. This is an advisory flag only — it does not create a page for you, edit your GBP listing, or make any changes automatically. ✅ How to Resolve a 'Landing Page Missing for Service' Recommendation 1. Review which service the recommendation refers to. 2. Check whether a relevant landing page already exists on your website. If it does, confirm it contains the service name in the URL, title, or heading so the matching logic can recognise it. 3. If no landing page exists, use Website Studio to create one targeted to that service. Optimise the page title, heading, and URL slug to include the service name. 4. Publish the page in Website Studio so it goes live on your domain. 5. Manually link the published page URL to the corresponding service entry in your GBP account, following the steps in the section above. 6. Return to the recommendation in Search Atlas. Once Search Atlas detects a matching page, the recommendation should clear on the next data refresh. ⚠️ Key Points to Remember - Website Studio publishes pages to your website — it does not push content to Google Business Profile. - All GBP service entries and linked URLs must be managed directly inside your GBP account. - The Landing Page Missing for Service feature identifies gaps and guides your SEO strategy — it does not make changes on your behalf. - Matching is based on keyword signals in your page URL, title, and headings — make sure your pages are clearly named for the service they represent. 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.

🔗 Connect Playbook Landing Pages to Wix Google Ads

Overview This article covers the topic of connecting a landing page built in Search Atlas Playbook to a Wix site and using that page as the destination for a Google Ads campaign. Because the exact steps depend on your specific Playbook plan and Wix setup, the general workflow involves three stages: finalising your landing page in Playbook, adding it to your Wix site, and entering the published URL as the Final URL in your Google Ads campaign. Prerequisites Before you begin, confirm you have the following in place: - A completed landing page saved inside Playbook in your Search Atlas account. - An active Wix account with a published site and editor access. - A live Google Ads account with billing enabled. - The ability to add or edit pages in your Wix site (Owner or Admin role). Step 1 — Finalise Your Landing Page in Playbook Log in to Search Atlas and open Playbook. Locate the landing page you want to use and review the content, headline, call-to-action, and any tracking elements to confirm everything is ready for paid traffic. Save the latest version before proceeding. To get your page onto Wix, you will need to export or retrieve the page content from Playbook. The exact export option available to you may vary by plan. If you are unsure which export format your plan supports, contact our support team (details below) before continuing. Step 2 — Add the Landing Page to Your Wix Site Once you have your page content from Playbook, add a new page to your Wix site using the Wix Editor. The specific menu labels and steps for adding a page or embedding content depend on your Wix plan and editor version — refer to Wix's own Help Center for the most accurate instructions for your setup. The general goal is to create a dedicated page on your Wix site that displays your Playbook landing page content. After publishing the new page on Wix, open it in a browser and copy the full URL. You will need this URL in the next step. Step 3 — Link the Wix Page to Your Google Ads Campaign Log in to Google Ads and open the campaign or ad group you want to connect to this landing page. Navigate to the specific ad you want to edit, or create a new ad. In the Final URL field, paste the full Wix page URL you copied in Step 2. It is strongly recommended to append UTM parameters to your Final URL so you can track traffic sources in Google Analytics. For example: https://www.yoursite.com/your-landing-page?utm_source=google&utm_medium=cpc&utm_campaign=your-campaign-name Save your ad and allow Google Ads a short time to review it before it goes live. Need Help with Your Specific Setup? Because the exact workflow depends on your Playbook plan, your Wix editor version, and your Google Ads account configuration, our support team is happy to walk you through the steps for your specific situation. 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.

🗺️ Publish Landing Pages and Configure Multi-Location GBP

🗺️ Overview This article covers two common setup tasks for local SEO: making your Website Studio landing pages permanently live and independent of Search Atlas, and configuring Google Business Profiles (GBP) for multiple service-area locations. Because the exact steps can vary depending on your account configuration, we recommend contacting our support team directly for guided assistance with either workflow. 🚀 Publishing Your Website Studio Landing Pages Permanently Landing pages built in Website Studio are hosted on Search Atlas infrastructure by default. To make them permanently accessible and independent of your Search Atlas subscription, you will need to host them on your own domain or CMS. The exact process for exporting and publishing your landing page depends on your account and page setup. To ensure you follow the correct steps for your situation, please reach out to our support team, who can walk you through the process and confirm the right workflow for your account. Why this matters: Hosting the page on your own domain ensures it stays live regardless of your Search Atlas plan status, passes Google's ownership signals for local SEO, and allows you to serve the page from your own branded URL. 📍 Setting Up Google Business Profiles for Two Service-Area Locations If your business serves customers in two distinct areas (for example, two cities or regions) without a physical storefront in each, you may need separate GBP listings configured as service-area businesses. The specific configuration steps depend on your Google account and business structure. Our support team can advise you on the recommended approach for your situation and help you avoid common setup mistakes that could affect your local SEO visibility. 📞 Get Help If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🌐 Connect a Custom Domain Without a Plugin

You can connect your Website Studio site to a custom domain without installing any plugin. By updating your domain's DNS records, you point your domain straight to your Website Studio site. This guide walks you through the full process step by step. 📋 What You Need Before You Start Make sure you have the following ready before connecting your domain: - A custom domain you already own (for example, yourbusiness.com). - Access to your domain registrar or DNS provider account (such as GoDaddy, Namecheap, Cloudflare, or Google Domains). - Your published Website Studio site. 🌐 Step 1: Add Your Domain in Website Studio Start inside the platform so the system knows which domain to expect: 1. Open Website Studio and select the site you want to connect. 2. Go to the site's Settings area. 3. Find the Domains or Custom Domain section. Enter your custom domain exactly as you own it and save. After saving, the platform displays the DNS records you need to add at your registrar. Keep this screen open so you can copy the values in the next step. 🛠️ Step 2: Update Your DNS Records Log in to your domain registrar or DNS provider and open the DNS management area. You will add the records shown in Website Studio. There are two common setups: - Root domain (yourbusiness.com): Add an A record pointing to the IP address shown in Website Studio. - Subdomain (www.yourbusiness.com): Add a CNAME record pointing to the target value shown in Website Studio. To add a record, follow these steps: 1. Select Add Record in your DNS dashboard. 2. Choose the record type (A or CNAME) as instructed in Website Studio. 3. Paste the exact value provided by the platform into the value or destination field. 4. Leave the TTL at the default setting if you are unsure. 5. Save the record. If you want both the root domain and the www version to work, add both records as shown in the platform. ⏳ Step 3: Wait for DNS to Update DNS changes are not always instant. They can take anywhere from a few minutes to 48 hours to fully apply across the internet. This waiting period is called propagation. During this time, your domain may load intermittently, which is normal. ✅ Step 4: Verify and Secure the Connection Once the records are saved, return to Website Studio: 1. Open the Domains section again. 2. Select Verify or Check Connection if the option is available. 3. Wait for the status to show as connected. After verification, an SSL certificate is issued automatically so your site loads securely with https. This may take a short time to activate after the domain connects. 🔍 Troubleshooting Common Issues If your domain is not connecting, review these common causes: - Typos in records: Confirm the values match exactly what Website Studio shows, with no extra spaces. - Duplicate records: Remove any old A or CNAME records that point your domain elsewhere. - Not enough time: Allow up to 48 hours for propagation before assuming something is wrong. - Wrong record type: Use an A record for the root domain and a CNAME for subdomains. - Provider proxy enabled: If you use Cloudflare, try setting the record to DNS only while you confirm the connection. - Stray AAAA record blocking SSL: If your domain connects but https does not activate, check for an incorrect or leftover AAAA (IPv6) record on your domain and remove it. A wrong AAAA record can prevent the SSL certificate from being issued. 💡 Helpful Tips - Make a note of your existing DNS records before changing anything, so you can restore them if needed. - Use a single, consistent version of your domain (with or without www) as your primary address. - Clear your browser cache or test in a private window if the old site still appears. 💬 Need More Help? If you need further assistance, click the chat icon in the bottom-right corner of the platform and type "Human Teammate" to start a live chat with a member of our team.

🚀 Migrate a Multilingual Vite Website

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

🛡️ Safely Deploy Website Studio

🎯 Choose the right publishing method Website Studio can be added to an existing WordPress setup without replacing the current website. Before publishing, decide whether you want a new WordPress page, a subdomain, or a separate custom domain. - New WordPress page: Adds the project as a page within your existing WordPress site, such as example.com/new-page. - Subdomain: Publishes the project separately at an address such as studio.example.com. Your main WordPress site remains at example.com. - Custom domain: Uses a separate domain, such as newbrand.com, for the Website Studio project. 📄 Publish as a new WordPress page Use this option when the project should appear as part of your existing WordPress website. It is the best choice for landing pages, campaigns, or additional site sections. 1. Open Website Studio from the left sidebar. 2. Open the project you want to publish. 3. Select the WordPress publishing option and choose to add the project as a new page. 4. Enter a unique page path that does not match an existing WordPress page. 5. Review the page and confirm the publishing action. This option should create a new page rather than replace your homepage or existing content. To reduce risk, confirm the page path is unique and create a WordPress backup before publishing. 🌐 Publish to a subdomain Use a subdomain when you want the project to remain separate from the main WordPress site while still using the same brand domain. 1. Create the subdomain with your domain or hosting provider, such as studio.example.com. 2. Follow the Website Studio publishing instructions for the required DNS record. 3. Update DNS only for the chosen subdomain. Do not change the records for the root domain or the www host unless the instructions specifically require it. 4. Wait for DNS changes to propagate, then verify the subdomain. 5. Publish the Website Studio project to the verified subdomain. DNS changes can take time to become active. If your root domain continues pointing to WordPress and only the new subdomain points to Website Studio, the existing site should remain unaffected. 🔗 Use a separate custom domain A custom domain is suitable when the project should operate as an independent website. Register or use a domain that is not currently serving your WordPress site, then connect it using the DNS records provided during Website Studio setup. Do not replace the root-domain or www records for your existing WordPress domain unless you intentionally want to move that website. Confirm ownership, SSL availability, and DNS status before publishing. ✅ Protect your existing WordPress site - Back up WordPress files and the database before making changes. - Use a staging site to test page publishing when possible. - Never overwrite an existing page, homepage, or URL path unintentionally. - Record your current DNS records before editing them. - Change only the DNS record required for the selected subdomain or custom domain. - Test the existing homepage, admin login, and key pages after publishing. 🧭 Find Website Studio In Search Atlas, open Website Studio from the left sidebar at /website-studio. From there, select the project and use its publishing or deployment options. The Website Studio workflow is separate from OTTO SEO, which is located under the AI SEO section. 💬 Get help If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

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

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

🌐 Website Studio: SSR, Meta Tags, Footer Embeddings & Sitemaps

🔍 Overview This article covers common technical questions about Website Studio — including server-side rendering (SSR), meta tag management, Footer Embeddings, and sitemap publishing. Because many of these topics involve backend configurations, our team may need to investigate your specific setup directly. ⚙️ Does Website Studio Support Server-Side Rendering or Prerendering? If you have questions about how Website Studio renders pages — including whether SSR or prerendering applies to your site — please contact our support team. Rendering behaviour may vary depending on your configuration, and our team can clarify what applies to your account. When escalating, please have the following ready: - Your project or site name in Website Studio - The specific page URL(s) where you are seeing rendering issues - A description of the problem (e.g. content not indexed, social previews not loading) - Any error messages or timestamps, if applicable ✏️ Can I Edit Code or Manage Meta Tags Directly? Meta tag management in Website Studio is handled through built-in settings. If you have questions about a specific meta tag — such as an Open Graph image tag — our team can advise on the correct steps for your account. Regarding Open Graph image tags specifically: - If you need to update or replace an Open Graph image tag, please contact our support team with the page URL and details of the change you need. - If you are unable to update or remove a meta tag through the available settings, contact our support team with the page URL and a description of what you are trying to change. If you need to inject custom scripts or meta tags beyond what the built-in settings support, please raise this with our team — this helps us understand your requirements. 🔗 Are Footer Embeddings Stable and Supported? Footer Embeddings are a supported feature in Website Studio that allow you to add custom code to your published pages. If you have questions about Footer Embeddings behaviour or are experiencing issues with an embedding, please contact our support team. When escalating a Footer Embeddings issue, please have ready: - Your project or site name - The code snippet you are trying to embed - A description of the issue or unexpected behaviour you are seeing - Any error messages or the timestamp when the issue began 🗺️ Sitemap Publishing If you have questions about sitemap publishing in Website Studio — such as whether your sitemap has been generated, submitted, or is reflecting recent changes — please contact our support team. Our team can investigate the current state of your sitemap and advise on next steps. When escalating, please have ready: - Your project or site name - Your site's published URL - A description of the issue (e.g. sitemap not updating, pages missing from sitemap) - Any error messages or timestamps, 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.

🛠️ Make Your Lead Widget Public

🔍 Why visitors see a login page A public lead capture widget should let visitors view the form without creating an account or signing in to your whitelabel dashboard. If the widget opens a dashboard URL and displays “Invitation Required,” the snippet is likely using a dashboard link instead of the published lead capture widget URL. ⚙️ Check your widget settings 1. Sign in to your Search Atlas platform. 2. Open the relevant agency or whitelabel settings. 3. Locate the lead capture widget for the audit or service you want to share. 4. Confirm the widget is enabled and configured for public access. 5. Save or publish the settings. 📋 Copy the public embed code After publishing the widget, copy the embed snippet provided in the widget settings. Add this code to the page where you want leads to see the form. Do not copy a dashboard URL manually or replace the widget source with a whitelabel dashboard address. 🧪 Test the public experience 1. Open the page in a private or incognito browser window. 2. Test it while logged out of Search Atlas and your whitelabel dashboard. 3. Confirm the form loads without showing a login screen or “Invitation Required” message. 4. Submit a test entry and verify that the lead appears in the expected agency location. 🚧 If the widget still requires login Check that you are using the latest embed code after saving the settings. Also verify that the widget is installed on the correct published page and that your whitelabel domain is configured correctly. If the snippet still redirects to the dashboard or falls back to a Search Atlas domain, the public widget may not yet be enabled for that account or widget type. 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.

🌐 Publish Website Studio Pages & Configure DNS

🗺️ Overview Website Studio lets you build and publish landing pages on a custom domain that you own — meaning your pages remain live and accessible independently of your Search Atlas subscription. This article walks you through publishing options, DNS setup, and how to confirm your pages are properly configured and reachable. 🚀 Publishing Options in Website Studio When you are ready to make a landing page live, Website Studio offers two main publishing paths: - Search Atlas Subdomain (default): Your page is hosted on a Search Atlas-managed subdomain (e.g., yoursite.searchatlas.com). This is the fastest way to go live, but the URL is tied to the platform. - Custom Domain (recommended for permanence): Connect your own domain so pages are hosted at a URL you fully control (e.g., www.yourdomain.com). This makes your pages permanent and independent of Search Atlas. To ensure your pages remain live long-term and are not dependent on Search Atlas, always publish to a custom domain that you own and manage. ⚙️ How to Connect a Custom Domain 1. In Search Atlas, navigate to Website Studio from the left sidebar. 2. Open the site you want to publish and click Settings. 3. Select the Domain tab and click Add Custom Domain. 4. Enter your domain or subdomain (e.g., landing.yourdomain.com) and click Save. 5. Website Studio will display the DNS records you need to add — copy these values before moving to your domain registrar. 🛠️ DNS Configuration Steps DNS changes are made at your domain registrar or DNS provider (e.g., GoDaddy, Cloudflare, Namecheap). The exact steps vary by provider, but the process is the same: 1. Log in to your domain registrar and open your DNS Management or DNS Zone Editor. 2. Add a CNAME record with the values provided by Website Studio: - Name / Host: the subdomain you entered (e.g., landing) - Value / Points to: the target provided by Website Studio - TTL: 3600 (or your registrar's default) 3. If you are connecting a root domain (e.g., yourdomain.com with no subdomain), use an A record or ALIAS/ANAME record if your registrar supports it, pointing to the IP address provided by Website Studio. 4. Save your DNS changes. Important: DNS propagation typically takes 15 minutes to 48 hours. Do not expect your domain to resolve immediately after saving. ✅ Verifying Your Pages Are Live Once DNS has had time to propagate, use the steps below to confirm your pages are properly configured and publicly accessible: - Check within Website Studio: Return to Settings > Domain. Website Studio will show a green checkmark or a Verified status next to your domain when DNS is correctly configured. - Visit the URL directly: Open a private/incognito browser window and navigate to your custom domain. Your published page should load without any Search Atlas branding or login prompts. - Use a DNS lookup tool: Tools such as dnschecker.org let you enter your domain and see whether the CNAME or A record is resolving correctly across global DNS servers. - Check for SSL: Your page URL should begin with https://. Website Studio provisions an SSL certificate automatically after DNS is verified. If you see a security warning, allow a few more hours for the certificate to activate. 📍 Setting Up a Google Business Profile (GBP) Service Area Page If you are creating landing pages for Google Business Profile service areas, follow these additional steps: 1. In Website Studio, build or open the landing page you want to associate with a GBP service area. 2. Publish the page to your custom domain and confirm it is live using the verification steps above. 3. In Search Atlas, navigate to the GBP section and open the relevant business profile. 4. Under Service Areas, enter the published page URL as the destination link for the applicable service area. 5. Save your changes and allow up to 24 hours for Google to reflect the update. Note: GBP page creation requires that your Website Studio custom domain is already verified. Attempting to link an unverified or unpublished page may result in an authentication error. Always complete the DNS verification step first. ❓ Common Issues & Quick Fixes - Domain shows "Pending" after 48 hours: Double-check that the CNAME or A record values in your registrar exactly match what Website Studio provided, with no extra spaces or characters. - Page loads but shows a security warning: SSL provisioning can take up to 24 hours after DNS verification. Wait and retry. - CMS connector not working with a custom domain: Ensure the domain is fully verified in Website Studio before attempting to connect Content Genius or any CMS integration. - GBP page creation fails: Confirm your custom domain is verified and the page is publicly accessible before linking it to a GBP service area. 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.

🔗 WebsiteStudio Homepage Canonical Redirects

🏠 Why the homepage cannot redirect In WebsiteStudio, the homepage is the starting point of your site. It is connected to your main domain, such as https://example.com/, so it cannot be redirected to another page or URL from within the editor. If you try to redirect the homepage, you may see the message: “Your home page is where the site starts, so it can't be sent elsewhere.” This is expected behavior, not an error. 🔗 Canonical tags and redirects are different A canonical tag tells search engines which URL should be treated as the main version of a page. It does not send visitors to another URL. A redirect automatically sends visitors and search engines from one URL to another. WebsiteStudio does not support redirecting the root homepage to another destination. WebsiteStudio pages use self-referencing canonical URLs by default. This means each page identifies its own URL as the preferred version unless the platform provides another supported configuration. 🛠️ What you can do instead - Keep the homepage as your main landing page: Add buttons, navigation links, or calls to action that guide visitors to the page you want them to see. - Use a separate page for campaigns: Create a dedicated landing page with its own URL instead of redirecting the homepage. - Update your navigation: Change the menu, logo link, or homepage content so visitors can quickly reach the intended destination. - Use your preferred domain: If you are changing domains, update the site’s domain configuration and verify the new homepage rather than redirecting the homepage inside WebsiteStudio. 🔍 Check the correct URL 1. Open the published site in a browser. 2. Confirm that the homepage loads at the root domain, with no unexpected path such as /welcome. 3. Open individual pages using their full URLs. 4. Check that each page has the expected canonical URL and is not marked noindex. If a page unexpectedly redirects to the homepage, cannot be opened directly, shows an incorrect canonical URL, or returns an error instead of a normal not-found page, this may indicate a site configuration or platform issue. Record the affected URL and the steps that reproduce the behavior before contacting support. 💡 Recommended homepage setup Keep the homepage accessible at your main domain and use it to explain your site, establish your brand, and direct visitors to important pages. For SEO, make sure the homepage has a unique title, description, relevant content, and a self-referencing canonical URL. 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 Page Editing Scope and Content Integrity

🔍 Overview When working on a multi-page project in Website Studio, two questions come up often: does an edit affect only the page I'm working on, or can it touch other pages? And why does the AI agent sometimes rewrite content instead of making the small change I asked for? This article explains how page-level editing scope works, what causes content to change unexpectedly, and how to get the most precise results from Website Studio. 🗂️ How Page-Level Editing Scope Works Website Studio is designed so that edits — whether you upload HTML or send a prompt — are scoped to the active page you have open in the editor. In a 21-page project, for example, only the page currently selected should be affected by your instruction. In practice, the following rules apply: - Uploading HTML: The uploaded file replaces or updates only the page it is mapped to. Other pages in the project remain unchanged. - Prompting the agent: Instructions sent while a specific page is open are interpreted in the context of that page. The agent should not propagate changes to other pages unless you explicitly ask it to. - Global elements (headers, footers, shared components): If your project uses shared components that appear across multiple pages, editing a shared component will affect every page that includes it. This is expected behaviour, not a bug. If you notice changes appearing on pages you did not intend to edit, it is likely because a shared component was modified, or because the instruction was phrased in a way the agent interpreted as site-wide. See the tips below for how to avoid this. ✍️ Why the Agent Rewrites Content Instead of Following Exact Instructions The Website Studio AI agent is generative by nature. When it processes an instruction, it regenerates the affected section rather than performing a surgical find-and-replace. This can cause more text to change than you expected, even when your prompt was specific. Common reasons this happens: - Ambiguous phrasing: Instructions like "improve this section" or "fix the copy" give the agent creative latitude. It interprets these broadly and rewrites accordingly. - Context bleed: In some cases, the agent may lose track of exactly which element you are targeting, especially in pages with complex or deeply nested HTML. This can cause it to rewrite a larger block than intended. - Regeneration vs. patching: The agent builds output token by token. Even a small change instruction may cause it to regenerate a full paragraph or section to maintain stylistic consistency in its output. 💡 Tips for Precise, Scoped Edits Use these best practices to keep changes contained and match your exact intent: 1. Be specific about the target element. Instead of "update the intro," try "change only the first sentence of the hero heading to read: [your exact text]." The more specific you are, the less room the agent has to interpret broadly. 2. Use exact text anchors. Quote the exact text you want changed. For example: "Replace the text 'Book a demo today' with 'Start your free trial'." This removes ambiguity. 3. Avoid open-ended improvement prompts. Phrases like "make this better" or "rewrite this page" will almost always result in significant content changes. Reserve these for when you genuinely want a full rewrite. 4. Upload HTML for precise replacements. If you have a finalised version of a section, uploading the HTML directly gives you full control over the output and bypasses the agent's generative behaviour entirely. 5. Check shared components before editing. If your project uses a global header, footer, or navigation component, be aware that changes to those elements will appear on all pages that include them. 6. Review changes before publishing. Always preview the page after an agent edit to confirm only the intended elements changed before making the page live. ⚙️ Navigating to Website Studio To access Website Studio, go to the left sidebar and select Website Studio. Your projects and pages are listed in the panel. Click the specific page you want to edit before sending any prompt or uploading HTML to ensure the correct page scope is active. 🛠️ Known Limitations The Search Atlas team is actively working to improve editing precision in Website Studio. Improvements to scoped editing — so that "change only this" instructions are honoured more reliably — are already in progress. If you experience consistent context bleed or unintended rewrites, documenting the exact prompt and the page structure can help the team investigate. 🆘 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.

🌐 Publishing Landing Pages to Your WordPress Domain

🗺️ Overview Some customers have been told by a previous Search Atlas representative that pages can be added directly to an existing domain — without creating a subdomain or a new site. This article clarifies exactly what is and is not possible today, so you can choose the right publishing path for your needs. ⚠️ Can I Add Pages Directly to My Current Domain? No — this is not currently supported. At this time, Website Studio does not support publishing a landing page directly to the root of an existing domain (for example, yourdomain.com/new-page) without a technical integration step. If a previous representative indicated otherwise, we sincerely apologise for any confusion. That capability, if it was ever available, is not part of the current platform. To publish a page from Website Studio to your domain, you must use one of two supported methods: - Subdomain publishing — for example, landing.yourdomain.com - Subpath publishing via WordPress plugin — for example, yourdomain.com/page-name, using the Search Atlas WordPress plugin Both methods require a one-time configuration step. Neither permanently alters your existing site structure or takes down any current pages. 🔌 Option 1 — Subdomain Publishing A subdomain keeps your landing pages completely separate from your main WordPress site and requires a small DNS change. 1. In Website Studio, open your project and go to Settings → Domain. 2. Choose Connect a subdomain and enter your desired subdomain (for example, landing.yourdomain.com). 3. Log in to your domain registrar or DNS provider. 4. Create a CNAME record pointing your chosen subdomain to the value shown in Website Studio. 5. Save the DNS record. Propagation typically takes 5–30 minutes. 6. Return to Website Studio and click Verify Connection. 7. Publish your page. It will go live at your subdomain URL. Your existing WordPress site at yourdomain.com is completely unaffected. 🔗 Option 2 — Subpath Publishing via WordPress Plugin If you want pages to appear under your main domain (for example, yourdomain.com/offer), you can do this using the Search Atlas WordPress plugin. This is the closest available option to adding a page directly to your domain, and it does not require any DNS changes. 1. Log in to your WordPress admin dashboard. 2. Go to Plugins → Add New → Upload Plugin and upload the Search Atlas plugin .zip file provided by Search Atlas. 3. Install and activate the plugin. 4. Inside the plugin settings, connect it to your Search Atlas account using your API key. You will find your API key under Avatar Menu (👤) (avatar) → Settings → API Keys in the Search Atlas platform. 5. In Website Studio, go to Settings → Domain for your page and select Publish to WordPress. 6. Choose the subpath slug you want (for example, /offer) and confirm. 7. The page will appear at yourdomain.com/offer without touching your existing WordPress content. Note: Your WordPress site must be self-hosted (not WordPress.com) and you must have admin access to install plugins. 📋 Comparison at a Glance - Root domain publishing (yourdomain.com/page) — Not supported without the WordPress plugin. Requires plugin installation; no DNS change needed. - Subpath via WordPress plugin (yourdomain.com/slug) — Supported. No DNS change. Requires plugin install and admin access. - Subdomain (landing.yourdomain.com) — Supported. Requires one CNAME DNS record. No plugin needed. - Standalone new domain — Supported. Requires domain connection via DNS. ❓ What If I Was Told Something Different? We take representative communications seriously. If you were given specific instructions or commitments by a previous Search Atlas team member that do not match the options described here, please reach out so we can review your account history and find the best path forward. The subpath-via-plugin method is the closest current equivalent to what may have been described, and our team can walk you through the setup. 💡 Quick Troubleshooting Tips - If your subdomain shows a DNS error after setup, allow up to 48 hours for full propagation before re-verifying. - If the WordPress plugin connection fails, confirm your API key is copied exactly with no extra spaces. - If your subpath page is not appearing on WordPress, check that no existing page or post is using the same slug. - If you do not have plugin install access on your WordPress site, the subdomain option is your best alternative. 🆘 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.

🌐 Verify Your Publishing Destination Before Going Live

🎯 What This Article Covers When you publish a new site or landing page through Website Studio to a newly purchased domain, it is natural to want confirmation that your original website will not be affected. This article explains how to review and verify your publishing destination before anything goes live, so you can publish with confidence. 🏗️ How Website Studio Publishing Works Every site you build in Website Studio is tied to a specific publishing destination. That destination is determined by the domain you connect during the setup process. Search Atlas does not automatically overwrite or redirect any existing website — your original site remains completely untouched unless you explicitly point its domain to a new Website Studio project. Key points to understand: - Each Website Studio project holds its own independent domain assignment. - A newly purchased domain starts with no existing content, so publishing to it carries no risk to any prior site. - Your original website's domain is only affected if you manually change its DNS settings or reassign it inside Website Studio. 🔍 How to Verify Your Publishing Destination Before Going Live Follow these steps to confirm the correct domain is assigned to your project before you click Publish: 1. Open your project in Website Studio. From the main dashboard, select the site you want to publish. 2. Go to Settings → Domain. In the left-hand navigation panel, click Settings, then select Domain. 3. Review the connected domain. The domain shown here is the exact destination where your site will be published. Confirm it matches your newly purchased domain and not your original website's domain. 4. Check DNS status. A green indicator or "Connected" status confirms the domain is properly linked. If the status shows "Pending" or "Not Connected," your site cannot go live on that domain yet, giving you extra time to verify before anything publishes. 5. Use the Preview function. Before publishing, click the Preview button in the top toolbar. This generates a temporary preview link that lets you review your full site as it will appear — without making it publicly accessible on your domain. Share this link for review or approval if needed. 6. Confirm and publish. Once you have verified the domain in Settings and reviewed the Preview, click Publish. Your site will go live only on the confirmed destination domain. 🛡️ Built-In Safety Mechanisms Website Studio includes several safeguards that prevent accidental publishing to the wrong destination: - Domain assignment is explicit. You must manually add and verify a domain inside each project. No domain is assigned automatically. - DNS propagation acts as a buffer. After connecting a new domain, DNS changes can take up to 48 hours to propagate. During this window, the domain is not yet live, giving you time to double-check everything. - Projects are isolated. Each Website Studio project operates independently. Changes in one project — including publishing — have no impact on any other project or any externally hosted website. - No overwrite without reassignment. Publishing a new project to Domain A will never affect a site currently hosted on Domain B. The two are entirely separate unless you explicitly reassign Domain B to the new project. ⚠️ What to Avoid To keep your original website fully protected, avoid the following: - Do not update the DNS records of your original website's domain to point to your new Website Studio project unless you intend to replace it. - Do not reassign your original domain inside Website Studio's Domain Settings. - If you are unsure which domain is currently assigned to a project, always check Settings → Domain before publishing. ✅ Quick Pre-Publish Checklist Run through this checklist every time you are ready to publish a new site: - Settings → Domain shows the correct new domain, not your original website's domain. - Domain status is "Connected" or matches the intended destination. - Preview link has been reviewed and the content looks correct. - DNS records for the new domain point to Search Atlas, not to any other hosting provider. - Original website's domain has not been modified in any way. 💬 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.

⚡ Website Studio Token Quota and HTML Upload Guide

Overview Website Studio uses tokens to power AI-assisted building, HTML uploads, and project generation. If you have run low on tokens — especially after working on a project that encountered errors — this article explains how quotas work, what counts toward your usage, and how to request a reset when needed. Understanding Your Token Quota Website Studio draws from your plan's token pool. Every AI-assisted action — including generating pages, editing content, and uploading HTML projects — may consume tokens. Key things to know: - HTML uploads are supported within Website Studio and may count toward your token quota depending on the scope of the upload. - Quota display discrepancies: Some accounts may temporarily show a quota figure that does not reflect the true remaining balance. If your displayed quota looks inconsistent with your activity, this may be a display issue rather than real consumption. - Quota stuck issue: In some cases, the quota counter can appear frozen or incorrect. If your quota looks wrong, contact our support team for a manual review. Tokens Spent on a Broken or Failed Project If you invested tokens into a project that failed — due to a file upload error or an unexpected generation issue — those tokens may have been consumed without producing a usable result. Here is what you should know: - Tokens consumed due to platform errors or confirmed bugs are eligible for a manual quota reset or token credit, reviewed case by case by our support team. - To qualify, you will need to describe the project, the approximate date of the failed uploads, and the impact on your token balance. How to Request a Token Reset If you believe tokens were consumed incorrectly — or you need an urgent reset to complete a client project — please have the following information ready when reaching out: - Your account email and project name - The approximate date(s) of the failed or unsuccessful actions - A description of what went wrong and how it affected your token balance - Any error messages you encountered Our team will review your case and, where appropriate, apply a manual quota reset or token credit 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.

🏗️ Website Studio LPS Credits: Costs Explained

🧾 What Are LPS Credits? LPS (Landing Page) credits are the currency used by Website Studio to power AI-driven site generation and editing. Every time you ask the AI to build, rewrite, or modify content, credits are consumed. Understanding the cost of each action helps you plan projects efficiently and avoid unexpected credit depletion. To access Website Studio, go to the left sidebar and select Website Studio (URL: /website-studio). 💡 Why Credits Disappear Faster Than Expected LPS credits are not the same as Local SEO Points. If you notice your LPS balance dropping quickly, it is almost always because larger AI operations — such as full site generation or multi-page Vibe edits — are running in the background. Even a single bulk operation can consume dozens of credits at once. The sections below break down exactly what each action costs. 📊 LPS Credit Cost Breakdown Use the ranges below as your reference whenever you plan work inside Website Studio. - Full site generation (new site from scratch): a variable number of credits depending on the number of pages, sections, and overall complexity — larger, more complex sites cost noticeably more than small, simple ones. - Initial site generation (first build from a template or prompt): a similar range to a full build, because the AI constructs every page and section from the ground up. - Multi-page AI edits / Vibe mode (rewriting or restructuring multiple pages at once): a moderate number of credits that scales with how many pages and sections are touched — a couple of pages with light copy changes costs noticeably less than a full-site overhaul. - Single-page or single-section edits: The smallest amount of the four operation types listed here — this is the most cost-effective way to make targeted changes. 🔍 Typical Project Examples The table below shows representative credit consumption for common tasks so you can estimate costs before you start. - New service business site (5 pages, moderate content): a moderate credit cost for the initial generation, plus a small additional cost per subsequent single-page tweak. - Landing page refresh (1 page, hero + 3 sections rewritten): a small credit cost. - Vibe edit across 4 pages (tone and messaging update): a moderate-to-higher credit cost, scaling with how many pages are touched. - Complete site rebuild from a new prompt (8 pages, rich sections): toward the higher end of the cost range for this type of operation. - Bulk section swap across an entire site: treated as a multi-page edit — expect the cost to scale with how many sections are replaced. ⚠️ Actions That Consume the Most Credits Be especially mindful of the following high-cost operations: 1. Generating a new site from scratch — a meaningful number of credits, scaling up for complex projects. 2. Running Vibe mode on multiple pages simultaneously — each additional page increases the total. Edit pages one at a time if you need to conserve credits. 3. Repeatedly regenerating the same page — each regeneration is a new AI call and counts as a fresh edit. Refine your prompt before regenerating to avoid duplicate credit use. 4. Switching site style or layout globally — global changes are processed as a multi-page edit and fall in the 15–65 credit range. ✅ Tips to Use Credits Efficiently - Make targeted, single-section edits whenever possible — they cost far less than full regenerations and add up to significant savings on large projects. - Finalise your brief or prompt before hitting Generate. A well-structured prompt reduces the need for costly regenerations. - Review the AI output page by page rather than triggering a full Vibe-mode refresh when only a few sections need updating. - Check your LPS credit balance in your account settings before starting any large build so you know how much runway you have. 🙋 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.

🌐 Brand Vault Picker in Website Studio

Website Studio now includes a Brand Vault picker on the project creation screen, making it faster and easier to apply your brand identity from the very start of a new site build. ✨ What's New The Brand Vault picker is now available directly on the Website Studio creation screen. When starting a new website project, you can select an existing Brand Vault to automatically apply your stored brand settings without any manual setup after creation. 🛠️ How to Use It 1. Open Website Studio from the left sidebar. 2. Start a new website project from the creation screen. 3. Look for the Brand Vault selection option on the creation screen. 4. Select the Brand Vault you want to apply to the new site. 5. Complete any remaining setup fields and confirm to create your project with brand settings pre-applied. 📋 What to Expect The Brand Vault picker will only display Brand Vaults that have already been configured in your account. If no Brand Vaults exist yet, you will need to create one in the Brand Vault section before it appears as an option. If you are unsure where to find the Brand Vault picker or the option does not appear on your creation screen, please have your project name and account details ready when reaching out so our team can assist you 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.

🛠️ Integrate Website Studio with WordPress

🔍 Understand how the two platforms work Website Studio and WordPress are separate website systems. Your existing WordPress site remains managed in WordPress, while a Website Studio project is managed from Search Atlas. Before making changes, decide whether you want to improve the current WordPress site or use Website Studio for a new or redesigned site. This choice affects your domain, URLs, navigation, analytics, and SEO settings. 🧭 Choose the right integration approach - Improve the existing WordPress site: Use Website Studio as a planning and design reference, then recreate approved changes in WordPress. - Move to Website Studio: Use the Studio project as the primary site and configure your domain there when the project is ready. - Use both platforms: Keep WordPress as the main site and use Website Studio only for a separate, clearly defined area. Confirm that the URL structure is supported before publishing. Do not publish the same page, category, or folder path in both systems. Duplicate paths can cause conflicts, unexpected redirects, or the wrong page to load. 📋 Review your current WordPress site Before incorporating a Website Studio project, create a short inventory of your current site: 1. List important pages, blog posts, categories, and landing pages. 2. Record the URLs that receive traffic or backlinks. 3. Identify pages that rank in search results or generate leads. 4. Note your navigation, forms, tracking tools, redirects, and SEO settings. 5. Back up WordPress before changing templates, URLs, or plugins. This inventory helps you preserve valuable content and avoid replacing important pages accidentally. 🎨 Use Website Studio to improve the site When using Website Studio as a design or content reference, compare each proposed page with its WordPress equivalent. Check the page purpose, heading structure, calls to action, internal links, images, and mobile layout. Transfer changes in small groups rather than replacing the entire site at once. After each update, check the live page, forms, menus, page speed, tracking, and search visibility. 🌐 Prepare a Website Studio project for publishing Open Website Studio from the left sidebar in Search Atlas. Review the project before connecting or using a custom domain. - Confirm that the correct pages and navigation are present. - Check page titles, descriptions, headings, images, and links. - Review mobile and desktop layouts. - Confirm that important WordPress URLs will not be reused by Studio pages. - Plan redirects for any URLs that must change. If Website Studio becomes the primary site, plan the domain transition carefully. Test the project before directing visitors to it, and keep a record of the old WordPress URLs and their replacements. ⚠️ Avoid common URL and content problems - Do not create a Studio page with the same path as a WordPress category, post, or page. - Do not place two different versions of the homepage at the same domain and path. - Do not delete WordPress pages until replacement pages and redirects are tested. - Do not copy content without deciding which version should be indexed. - Do not change many URL structures at once without monitoring traffic and search performance. ✅ Test after making changes 1. Open the homepage and key landing pages in a private browser window. 2. Test menus, buttons, forms, images, and internal links. 3. Check that old important URLs redirect to the correct new pages. 4. Confirm that no page shows a 404, redirect loop, or unexpected WordPress category. 5. Review analytics, search performance, and rankings after publishing. Keep WordPress and Website Studio content ownership clear for everyone working on the site. A simple page map showing the platform responsible for each URL can prevent future conflicts. 💬 Get help with your 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.

🌐 Export Website Studio Pages to Permanent Hosting

Overview If you want landing pages you build in Website Studio to remain live independently — on your own domain and hosting — you will need to export them and deploy them to an external host. This article also covers multi-location Google Business Profile (GBP) configuration once your pages are permanently hosted, a common workflow for service-area businesses and agencies managing multiple locations. How to Export Your Landing Page from Website Studio To export a landing page from Website Studio, follow these steps: 1. Open Website Studio from your Search Atlas dashboard and navigate to the project containing the landing page you want to export. 2. Open the landing page, then look for the Export or Download option within the page editor. This will package your page as a set of static files (HTML, CSS, and assets). 3. Save the exported ZIP file or folder to your computer. Deploying to Your Hosting Provider Once you have your exported files, choose your preferred hosting method below: - Netlify or Vercel (recommended for simplicity): Drag and drop your exported folder directly onto the Netlify or Vercel dashboard at netlify.com or vercel.com. Your page will be deployed instantly with a temporary URL. To attach your custom domain, go to Domain Settings in your Netlify or Vercel project and add the domain you own, then update your DNS records as instructed. - cPanel (traditional web hosting): Log in to your cPanel account and open File Manager. Navigate to the public_html folder (or the subdirectory for your domain/subdomain). Upload the exported HTML, CSS, and asset files. Your page will be live at your domain once the files are in place. - FTP upload: Connect to your host using an FTP client (such as FileZilla) with the credentials provided by your hosting provider. Upload the exported files to the correct public directory for your domain or subdomain. After uploading, visit your domain in a browser to confirm the page is loading correctly. Allow up to 48 hours for DNS changes to propagate if you recently pointed a domain or subdomain to your hosting. Configuring a Multi-Location Google Business Profile (GBP) If you are a service-area business or agency managing multiple locations, you can connect each hosted landing page to a separate GBP location. Follow these steps: 1. Log in to Google Business Profile Manager at business.google.com and select the location (or create a new location) you want to associate with your hosted page. 2. In the location's profile settings, set the Website field to the permanent URL of the landing page you just deployed (for example, https://yourdomain.com/location-name). 3. If you are adding a new location for a service-area business, enter the service area instead of a storefront address, then complete the GBP verification process (postcard, phone, or video verification as prompted by Google). 4. Repeat this process for each location, pointing each GBP listing to the corresponding hosted landing page URL. Keeping each location's GBP website URL pointed to a stable, permanently hosted page — rather than a temporary Search Atlas preview URL — helps maintain local SEO consistency across all your locations. What to Have Ready if You Need Help If you run into issues during export or deployment, please have the following ready when contacting support: - The name of the Website Studio project or landing page you want to export - Your preferred hosting provider (for example, Netlify, Vercel, cPanel, or another provider) - The domain or subdomain where you want the page to be permanently hosted - Whether you also need help configuring a multi-location Google Business Profile for the hosted page - Any error messages or screenshots you have encountered while attempting the export 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.

🌐 Publish Website Studio Pages to WordPress Safely

🎯 What This Guide Covers Website Studio lets you design and publish individual pages — such as service pages, landing pages, or location pages — directly to your WordPress site. This guide explains how to do that without overwriting your existing homepage, content, or site structure. ⚙️ How WordPress Publishing Works in Website Studio When you publish a page from Website Studio to WordPress, the platform creates or updates a single page on your WordPress site. It does not replace your entire website. Your homepage, navigation, existing posts, and all other content remain untouched. Key things to understand before you publish: - Each page you publish is treated as an independent WordPress page. - Your existing WordPress theme and site structure are preserved. - You control the URL slug for every page you publish. - Publishing one page does not affect any other pages on your site. 🔗 Step 1 — Connect Your WordPress Site Before publishing, you need to link your WordPress site to Search Atlas. 1. In the left-hand navigation, go to Website Studio. 2. Open the page you want to publish. 3. Click Publish in the top-right corner. 4. Select WordPress as your publishing destination. 5. Enter your WordPress site URL, username, and an Application Password (not your login password). To generate an Application Password in WordPress, go to Users → Profile → Application Passwords in your WordPress admin. 6. Click Connect to save the credentials. Note: If you have already connected your WordPress site previously, your credentials will be saved and you can skip ahead to Step 2. 📄 Step 2 — Set the Page URL Before Publishing Choosing the right URL slug protects your existing pages and keeps your SEO intact. 1. With your page open in Website Studio, click Page Settings (gear icon). 2. Set a unique URL slug for the page — for example, /plumbing-services-chicago. 3. Make sure the slug does not match any existing page on your WordPress site (such as / for the homepage) unless you intentionally want to update that specific page. 4. Save your settings before proceeding. 🚀 Step 3 — Publish the Page to WordPress 1. Click Publish in the top-right corner of Website Studio. 2. Confirm your WordPress connection is active. 3. Review the target URL slug one final time. 4. Click Publish to WordPress. Once published, the page will appear in your WordPress admin under Pages. You can visit the live URL to confirm it is displaying correctly. ⚠️ Common Issues and How to Avoid Them - Blank page after publishing: This can happen if the page content was not fully saved before publishing. Make sure all sections are saved in Website Studio, then republish. - Page not appearing on WordPress: Check that your Application Password is correct and that the WordPress REST API is enabled on your site. Some security plugins block the REST API — temporarily disable them to test. - Homepage was changed accidentally: This occurs when the URL slug is set to / or left blank. Always set a specific, unique slug before publishing. - Using a custom domain in Website Studio: If your Website Studio project uses a custom domain, make sure you are entering your WordPress site URL (not the Studio domain) in the connection settings. ✅ SEO Best Practices When Publishing to WordPress - Set a unique, keyword-rich URL slug for every page before publishing. - Add a page title and meta description inside Website Studio's Page Settings — these are passed through to WordPress. - Avoid publishing duplicate versions of the same page under different slugs. - After publishing, submit the new URL to Google Search Console to accelerate indexing. 💬 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.

🛠️ Remove Unauthorized Forms and Bulk-Edit Sites

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

🌐 How to Publish a Wix Website to Namecheap Hosting with a GoDaddy Domain

📌 Overview A common question we receive is how to publish a website that was created on Wix, hosted on Namecheap, and connected to a GoDaddy domain. This article explains how these three services interact, what is technically possible, and how Search Atlas can help you manage and publish your website content. ⚠️ Important: How Wix Hosting Works Before you begin, it is essential to understand a key limitation. Wix is a closed, all-in-one platform. When you build a site with Wix, it is automatically hosted on Wix's own servers. Wix does not allow you to export your website's files and upload them to a third-party host such as Namecheap. This means you cannot directly transfer a Wix-built website to Namecheap hosting. What you can do is control which domain points to your published site. 🔗 How the Three Services Fit Together - Wix — builds and hosts your website content. - GoDaddy — where your domain name is registered. - Namecheap — a hosting and domain provider you may want to use instead of Wix hosting. Because Wix hosts its own sites, your practical options are either to keep your site on Wix and point your GoDaddy domain to it, or to rebuild the site on a platform that Namecheap can host. ✅ Option 1: Keep the Wix Site and Point Your GoDaddy Domain If you want to keep your Wix website exactly as it is, you do not need Namecheap hosting at all. Instead, connect your GoDaddy domain to Wix: 1. Log in to your Wix account and open the site you want to publish. 2. Go to Settings and select Connect a Domain. 3. Choose Connect a domain you already own and enter your GoDaddy domain. 4. Wix will provide DNS records (name servers or pointing records). 5. Log in to GoDaddy, open your domain's DNS settings, and update the records to match what Wix provided. 6. Allow up to 48 hours for the DNS changes to propagate. With this method, your Wix site is live under your GoDaddy domain and Namecheap is not required. 🛠️ Option 2: Rebuild the Site for Namecheap Hosting If you specifically want your website hosted on Namecheap, you will need to rebuild the site outside of Wix, since Wix files cannot be migrated. You can: 1. Build a new website using a platform whose files can be hosted anywhere (for example, a standard HTML/CSS site or a WordPress installation). 2. Set up a hosting plan in your Namecheap account and upload your website files. 3. Point your GoDaddy domain to Namecheap by updating the name servers in GoDaddy's DNS settings to the name servers provided by Namecheap. 4. Wait for DNS propagation, then verify your site loads under your domain. 🚀 Publishing with Search Atlas Website Studio If you would prefer a solution that lets you build and publish directly, Search Atlas offers Website Studio as an alternative to Wix. This allows you to create SEO-optimized pages and publish them without wrestling with third-party migration limits. - Open Website Studio from the left sidebar of the platform. - Build your pages within Website Studio. - Connect your GoDaddy domain by updating your DNS records to the values provided during setup. - Publish your site directly from within Search Atlas. Using Website Studio keeps your website, content, and SEO tools in one place, which removes the need to coordinate separate builders and hosts. 🧩 A Note on Wix CMS Sync If you are connecting a Wix site to Search Atlas for content management and encounter a “Categories endpoint failed: meta-site not found” error, this usually means the Wix meta-site could not be located during sync. Confirm that you are connecting the correct Wix site and that the account has the proper permissions, then retry the connection. 💬 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.

🛠️ Webflow CMS Dynamic Fields and Template Variables

🔍 Overview When connecting Webflow to Search Atlas through the Universal CMS integration, you can use dynamic template variables to automatically populate content fields with SEO-optimized data. This article explains every supported variable, what it outputs, and how to use it inside your Webflow CMS templates. 📋 Supported Dynamic Custom Fields The following variables are the complete set of supported dynamic custom fields for Webflow CMS templates in Search Atlas. No additional variables are available beyond those listed here. - #{{html}} — Inserts the full body content of the generated article as HTML. Use this in a Rich Text field in your Webflow CMS collection. - #{{title}} — Inserts the SEO-optimized page or article title. Map this to your collection's Name or Title field. - #{{slug}} — Inserts the URL slug generated for the content item. This populates the Slug field in your Webflow CMS collection, controlling the page URL. - #{{featured_image}} — Inserts the URL of the featured image selected or generated for the content. Map this to an Image field in your collection. - #{{featured_image_alt_text}} — Inserts the alt text string associated with the featured image. Map this to the alt text input of your Image field for accessibility and SEO compliance. ⚙️ How to Use Template Variables in Webflow 1. In Search Atlas, navigate to Left sidebar → OTTO SEO and open the relevant project. 2. Go to the Overview page and select your Webflow CMS integration settings. 3. When configuring your content template, type the variable (for example, #{{title}}) directly into the corresponding field mapping input. 4. Make sure each variable is mapped to a compatible Webflow field type — for example, #{{html}} requires a Rich Text field, while #{{featured_image}} requires an Image field. 5. Save your template configuration and run a sync or content push to verify the fields populate correctly in your Webflow CMS collection. ⚠️ Common Mapping Mistakes to Avoid - Mapping #{{html}} to a plain text field — Plain text fields strip HTML tags and break formatting. Always use a Rich Text field for #{{html}}. - Leaving #{{slug}} unmapped — If the slug field is not mapped, Webflow may generate a default slug that does not match your SEO strategy. - Typos in variable names — Variables are case-sensitive. #{{Featured_Image}} will not work; use #{{featured_image}} in all lowercase with underscores. - Using unsupported variable names — Only the five variables listed above are supported. Custom or invented variable names will output as plain text or return empty values. 💡 Field Compatibility Quick Reference - #{{html}} → Webflow Rich Text field - #{{title}} → Webflow Plain Text or Name field - #{{slug}} → Webflow Slug field - #{{featured_image}} → Webflow Image field - #{{featured_image_alt_text}} → Webflow Image field Alt Text input 🚀 What Happens After a Sync Once your template variables are correctly mapped and a content push is triggered, Search Atlas sends the populated data to your Webflow CMS collection via the integration. Each CMS item is created or updated with the values resolved from the variables. You can verify the result by opening your Webflow CMS collection and reviewing the newly created or updated items. If a field appears empty after a sync, confirm that the variable is spelled correctly in your template and that the corresponding Webflow field type is compatible with the variable output as described above. 🆘 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.

📦 Website Studio Bulk Export and Dynamic SEO URL Management

🗺️ Overview This article covers two closely related Website Studio topics that often appear together: bulk exporting project and page data (including target cities and preview URLs) and managing stale URLs injected by Dynamic SEO. Understanding both helps you keep your projects organised and your live site free of unwanted URLs. 📤 Bulk Exporting Project Data from Website Studio Website Studio does not currently offer a one-click CSV export that lists all project IDs alongside their target cities and preview URLs in a single download. This feature is actively in development. In the meantime, you can gather this data manually by reviewing each project inside Website Studio and compiling the relevant details into your own spreadsheet. Important note on exports: If you need a bulk export of project or page data and the available in-platform options do not meet your needs, our support team can assist. Please have the following ready when you reach out: - The name(s) of the Website Studio project(s) you need data for - The specific data you need exported (e.g. target cities, preview URLs, page list) - Any error messages or unexpected results you have encountered 🔄 Understanding Content Regeneration Status Content regeneration controls whether Website Studio automatically refreshes page content when a template or data source changes. If you are unsure whether regeneration is active for your project, or if you manage a large number of pages and need to confirm regeneration status across all of them, this is a backend operation that our support team can investigate and action on your behalf. When escalating a regeneration question, please have the following ready: - Your project name and any relevant page URLs - A description of the content behaviour you are seeing (e.g. content not updating after a template change) - Approximately how many pages are affected ⚠️ Why Dynamic SEO Injects Stale URLs Dynamic SEO generates URLs automatically based on your configured location and page parameters. Stale URLs typically appear for one of the following reasons: - Editor and preview URLs leaking into the live site: Website Studio can expose internal editor, preview, generated, or duplicate URLs that were not intended for indexing. - Retired or changed parameters: If you update your location targets or page parameters, previously generated URLs may remain active on your live site. Because stale URL cleanup involves backend operations on your site's URL index and sitemap, this is handled by our support team rather than through a self-serve workflow. When contacting support, please have the following ready: - Your project name - A list or description of the stale URLs you have identified - The domain or subdomain affected - Any timestamps or recent changes that may have triggered 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.

🔗 Find Your Published Website Studio Page URL

What the Published Status Means When a landing page shows a Published status in Website Studio, your page is live and accessible on the internet. The status is accurate — no further action is needed to make it go live. The next step is simply knowing where to find its URL. How to Find the Live URL of Your Published Page The source of truth for your published page URL is inside Website Studio. Because the exact location of the URL field can vary depending on your account setup and any recent platform updates, the most reliable steps are: 1. Open Website Studio from the left sidebar. 2. In the page list, find the landing page that shows a Published status. 3. Look for a URL, link, or domain field associated with that page entry — this may appear as a clickable link, a copyable text field, or a dedicated column within the page list view. 4. If you do not immediately see the URL in the list view, try selecting or hovering over the page entry to reveal additional options or details. 5. Once you locate the URL, copy it and paste it into your browser to confirm the page is publicly accessible. If you have gone through these steps and still cannot locate the URL for your published page, our support team can look it up directly in your account. To get help as quickly as possible, have the following ready before reaching out: - The name of the page or project showing the Published status - A brief description of where you have already looked (e.g., page list, any settings panel you opened) Tips for Working With Your Page URL - The published status confirms the page is live. You do not need to republish or take any additional steps once the page shows a Published status. - Try a private or incognito browser window once you have the URL — this confirms the page loads correctly for visitors who are not logged in to Search Atlas. Frequently Asked Questions - I see the Published status but cannot find a URL anywhere. What should I do? Scan the page list for a URL or domain column, and try selecting or hovering over the page entry for additional details. If you still cannot locate it, contact our support team with your page name and the Published status you are seeing — they can pull the URL directly from your account. - What information should I have ready when I contact support? Have your project or page name ready, confirm the Published status you are seeing, and note which areas of the interface you have already checked. This lets the team locate your page and share the correct URL 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.

📋 Configure Form Notifications and Clickable Phone Numbers

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

✏️ Rename Website Studio Pages Safely Without Duplicates

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

🖥️ Website Studio Credits, Edits, and Visual Editor Guide

🔍 Overview Website Studio lets you build and refine your website using two methods: the chat interface and the visual editor. Understanding how credits are consumed — and knowing which tool to use for each task — will help you work efficiently and avoid unexpected charges. 💳 How Credits Are Charged for Chat-Based Edits Every time you send a message to the chat that results in a change to your website, one credit is consumed. This applies regardless of how small the change is. To use your credits wisely, try to combine multiple changes into a single chat message rather than sending separate messages for each individual change. Example:"Change the hero headline to 'Grow Your Business' and update the button color to dark blue." — This counts as one credit instead of two. ✏️ Making Edits With the Visual Editor (No Credit Charged) The visual editor allows you to make direct, manual changes to your website without consuming any credits. This is the best option for small text tweaks, formatting adjustments, or any change you can make yourself without AI assistance. To access the visual editor, open your site in Website Studio and look for the visual editing option within the platform. 🗑️ Deleting a Line or Element If you need to remove a specific line, text block, or element from your site, you can use either method: - Visual editor: Select the element you want to remove and use the available editing controls to delete it. The exact steps may vary depending on the element type. - Chat interface: Ask the chat to remove the element for you — keep in mind this will use one credit. If you are unsure how to delete a specific element in the visual editor, using the chat to request the removal is a reliable alternative. ⚡ Chat vs. Visual Editor: When to Use Each - Use the chat when you want the AI to generate new content, restructure a section, or make several complex changes at once. - Use the visual editor when you are making small, precise changes that do not require AI assistance — this preserves your credits. 🙋 Still Have Questions? If you are unsure how a specific action will affect your credit balance, or if you believe credits were charged incorrectly, please reach out to our support team with your project name and a description of the action you performed so we can 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.

🏙️ Create and Clone Location Pages in Website Studio

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

⚡ Configuring Cloudflare Orange Cloud Proxy with Website Builder

Overview Yes, Cloudflare works with Search Atlas Website Builder. You can enable the orange cloud (proxy) mode to benefit from Cloudflare's security features — including DDoS protection, WAF, and CDN caching — while keeping your site live and fully functional. However, because of how CNAME flattening and root domain routing work, the setup requires a specific configuration approach. This article walks you through the key steps. Understanding the Compatibility Search Atlas Website Builder serves your site via a CNAME record pointing to the platform's hosting infrastructure. Cloudflare's orange cloud (proxy) mode works seamlessly with subdomains (for example, www.yourdomain.com) because standard CNAME proxying is fully supported there. For root domains (also called apex domains, for example, yourdomain.com), Cloudflare uses a feature called CNAME Flattening, which automatically resolves the CNAME to an IP address at the DNS level. This allows you to proxy your root domain through Cloudflare without breaking DNS standards. Setting Up Cloudflare Proxy with Search Atlas Website Builder To configure Cloudflare's orange cloud proxy for your Search Atlas Website Builder site, you will need the CNAME target value for your domain. Please contact the Search Atlas support team to obtain the correct CNAME value for your site, as this is provided on a per-account basis. Once you have your CNAME value, follow these general steps in your Cloudflare DNS settings: 1. Log in to your Cloudflare dashboard and select your domain. 2. Go to the DNS section and add a new CNAME record. 3. Set the Name to www (for a subdomain setup) or @ (for a root domain setup). 4. In the Target field, enter the CNAME value provided to you by Search Atlas support. 5. Enable the Proxied (orange cloud) option for the record. 6. Save the record. If you are using a root domain, Cloudflare will automatically apply CNAME Flattening to resolve the record correctly in proxy mode. Need Help? If you run into any issues configuring Cloudflare proxy mode with your Search Atlas Website Builder site, or if you need your CNAME value, please reach out to our support team via the chat icon in your dashboard and we'll be happy to assist. If this article didn't solve your issue, please contact us via the live chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

📧 Connect Domain Email for Website Studio Forms

📋 Overview Website Studio lets you collect leads and inquiries through contact forms built into your site. To receive those submissions in your inbox, you need to connect a domain email address inside your project settings. This article also covers a common issue where blog posts appear on your site but do not open correctly when clicked. 🔌 How to Connect Your Domain Email for Form Submissions To set up email notifications for your Website Studio contact forms, navigate to your project's settings area within Website Studio and look for the section related to form submissions or email notifications. From there, you can enter the domain email address where you want to receive submission alerts and save your changes. If you are unsure where to find these settings, or if the option does not appear as expected in your project, our support team can walk you through the exact steps for your account configuration. ✅ Verifying Your Email Connection Works After saving your email address in the project settings, confirm that notifications are being delivered correctly: - Visit the live version of your site and submit a test entry through your contact form. - Check the inbox of the domain email address you connected. - If the test email does not arrive within a few minutes, check your spam or junk folder. - If the email is still missing, return to your project settings and confirm that your email address is saved correctly, then reach out to support for further help. 📝 Why Blog Posts Are Not Opening on Your Site If your blog posts are visible in the list on your site but clicking them leads to a broken page or no content, this is a known issue that can occur within Website Studio. The fix typically requires a configuration adjustment inside your project settings related to how blog post links are set up. To get this resolved, please contact our support team with the following information ready: - The name of the Website Studio project affected. - The URL of the blog post page that is not opening correctly. - A brief description of what you see when you click the blog post link (e.g., blank page, 404 error, redirect). Having these details ready will allow our team to identify the cause quickly and apply the correct fix to 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 with a member of our team.

⚡ Atlas Brain Canonical Tag Configuration and Override Procedures

Why Atlas Brain May Not Apply Your Canonical Tag Request When Atlas Brain does not apply a canonical tag change, it is typically because the request could not be mapped to a specific, actionable change for the pages in question. This is not necessarily a sign that the feature is unavailable — it may mean the request needs to be clarified or completed manually through Website Studio. Common reasons a canonical tag request may not go through include: - The request did not clearly specify which pages or URLs should be updated. - The pages in question may already have canonical values that the system is managing. - The request involved a large or complex set of pages that Atlas Brain could not resolve without more specific input. How to Manage Canonical Tags in Website Studio If Atlas Brain was unable to apply your canonical tag change, you can make the update directly in Website Studio. Because the specific steps depend on your account's interface version, we recommend doing the following: 1. In the left sidebar, click Website Studio (/website-studio). 2. Locate the page or pages where you want to set or update the canonical tag. 3. Look for the SEO or metadata settings area within the page editor for that page. 4. Find the field related to the canonical URL and enter the value you want to apply. 5. Save your changes and verify the canonical tag is reflected as intended. If you are unsure where the canonical tag settings are located within your specific interface version, or if the field does not appear to be editable, our support team can guide you to the correct location for your account. What to Have Ready When Contacting Support If you are unable to locate the canonical tag settings or Atlas Brain continues to not apply your request, please have the following information ready so our team can assist you efficiently: - The name of the project or website in Website Studio. - The specific pages or URLs where you want canonical tags set or updated. - The exact canonical URL value you want applied. - Any message or response Atlas Brain returned when you submitted your request. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Website Studio Editing Scope and Prompt Reliability

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

🖼️ Fix Favicon Issues in Website Studio

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

🔒 Wildcard SSL and 404 Redirect Routing in Website Studio

🔍 Overview Website Studio supports two important domain and routing features: wildcard SSL certificates for securing all subdomains under your root domain, and custom 404 redirect rules that send visitors to your homepage — or any valid URL — instead of displaying a raw XML error page. This article explains how both features work and how to get them configured for your site. 🔐 What Is Wildcard SSL? A standard SSL certificate secures a single domain (e.g., www.yourdomain.com). A wildcard SSL certificate secures the root domain and all of its subdomains at once (e.g., *.yourdomain.com), covering addresses like blog.yourdomain.com, shop.yourdomain.com, and any others you create. This is especially useful if your Website Studio project uses multiple subdomains, or if you plan to expand your site structure over time without requesting a new certificate for each subdomain. ⚙️ How to Request Wildcard SSL for Your Domain Wildcard SSL is not enabled automatically — it requires a quick setup step on our end. To request it: 1. Make sure your domain is already connected to your Website Studio project. 2. 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. 3. Provide your root domain name (e.g., yourdomain.com) and confirm the project it is linked to. 4. Our team will provision the wildcard SSL certificate and confirm once it is active. Once enabled, all current and future subdomains under your root domain will be covered automatically. No further action is needed on your end after the certificate is issued. 🚦 What Are Custom 404 Redirects? When a visitor lands on a URL that does not exist on your site, the server returns a 404 Not Found error. By default, some configurations display this as a plain XML error response, which is unhelpful for visitors and can negatively affect user experience and crawl efficiency. A custom 404 redirect automatically forwards anyone who hits a non-existent URL to a destination you choose — most commonly your homepage. This keeps visitors on your site and prevents search engines from indexing dead-end error pages. 🛠️ How to Set Up a Custom 404 Redirect You can configure 404 redirect routing directly inside Website Studio. Follow these steps: 1. Log in to your Search Atlas account and open Website Studio. 2. Navigate to your project and go to Settings. 3. Locate the Redirects or Routing section within your project settings. 4. Add a new redirect rule and set the source to the wildcard pattern for unmatched URLs (e.g., /* or the 404 error condition). 5. Set the destination to your homepage URL or any valid page on your site. 6. Choose 301 (Permanent) if the redirect is a long-term rule, or 302 (Temporary) if you may update it later. 7. Save your changes and test by entering a made-up URL on your domain to confirm the redirect fires correctly. Tip: A 301 redirect passes link equity to the destination page and signals to search engines that the old URL is permanently gone. Use 302 only when the redirect is genuinely temporary. ❓ Frequently Asked Questions - Will wildcard SSL automatically cover new subdomains I create later? Yes. Once a wildcard certificate is in place, any new subdomain you add under the same root domain is covered immediately. - Can I redirect 404s to a page other than my homepage? Yes. During setup, set the destination to any valid URL on your site, such as a contact page, category page, or custom error page you have built inside Website Studio. - Will the 404 redirect affect pages that do exist? No. The redirect rule only fires for URLs that do not match any existing page on your site. All live pages load normally. - How long does it take for wildcard SSL to activate? Certificate provisioning typically completes within a few minutes to a few hours after our team processes your request, depending on DNS propagation. 💬 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.

⚡ 2-Click Optimized Landing Page Creation

OTTO PPC offers a two-click workflow for generating optimized landing pages — a recently released feature that handles the process end to end without requiring you to leave the platform. ✨ What's New OTTO PPC has introduced a streamlined two-click flow for landing page creation and conversion action setup. This is a recently released capability. Full documentation of all steps, UI locations, and configuration options for this feature is still being compiled by our team. 🛠️ How to Use It Because this feature was released very recently, detailed step-by-step instructions are not yet fully documented. To get started: 1. Log in to your Search Atlas account and open OTTO PPC. 2. Look for the landing page creation option within your OTTO PPC dashboard. 3. If you cannot locate the feature or it does not appear available in your account, contact our support team — they can confirm whether it has been enabled for your account and walk you through the exact steps. 📋 What to Expect The two-click flow is designed to cover both landing page generation and conversion action installation in a single automated process. Because this is a new release, the exact behavior and available options may evolve as the feature matures. Check back for updated documentation as more details are confirmed. 🔧 If Something Isn't Working If the two-click flow does not complete as expected or you encounter an error, please have the following ready before reaching out: your project or account name, a description of where in the process the issue occurred, and any error messages or unexpected behavior you observed. This will help our team investigate and resolve the issue 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.

🖥️ Website Studio Monthly Quota and Credits for Starter Plan

🖥️ What Is Website Studio and How Do Credits Work? Website Studio is the AI-powered site-building tool inside Search Atlas. To generate pages, sections, and design elements, the tool consumes Universal Credits — a shared credit pool used across several features in the platform. Understanding how your monthly credit quota works helps you plan your projects and avoid unexpected pauses mid-build. 📊 How Many Credits Does the Starter Plan Include? On the Starter plan, your account receives a set number of Universal Credits each billing cycle that can be used across all supported features, including Website Studio. Your exact quota is visible directly inside the platform: 1. Log in to your Search Atlas account. 2. Click your avatar in the top-right corner. 3. Select Billing to see your current balance, monthly allowance, and reset date. If the number displayed does not match what you expected based on your plan, this may be related to a known display issue that has since been resolved — see the section below for more detail. 🔄 When Do Credits Refresh? Your Universal Credits refresh automatically at the start of each billing cycle — either monthly or annually depending on how your subscription is set up. - Monthly plans: Credits reset on the same date each month. - Annual plans: Credits still refresh on a monthly basis throughout the year. Your quota does not accumulate over 12 months — unused credits from one month do not roll over to the next. If you are on an annual plan and your quota display appeared frozen or never seemed to refresh, this was caused by a known issue in which the interface merged recurring and one-time purchased credits into a single number. This has been fixed, and your dashboard should now correctly show your recurring monthly quota separately. ⚠️ Known Display Issues Now Resolved Our engineering team has addressed several credit-display bugs that may have caused confusion for Starter plan customers: - Incorrect quota totals: Some accounts saw a credit allowance that did not match their actual plan allocation. This has been corrected so that your displayed quota now reflects the accurate per-plan amount. - Legacy credit values shown: Website Studio was briefly showing an outdated credit quota instead of the current Universal Credits balance. This has been updated. - Annual plan refresh confusion: The quota counter appeared static for annual subscribers because purchased and recurring credits were displayed as one combined figure. These are now shown separately so you can clearly see when your monthly credits have refreshed. If you noticed any of these issues before, no credits were lost — only the display was affected. Your actual available balance should now be accurate. 💡 Tips for Managing Your Website Studio Credits - Check your credit balance before starting a large Website Studio project so you know how much you have available. - Prioritise your most important pages or sections first in case you run low toward the end of your billing cycle. - If you need more credits before your quota refreshes, additional Universal Credits can be purchased from the Billing section (via your avatar in the top-right) of your account. - Purchased credits are separate from your recurring monthly allowance and do not expire at the end of a billing cycle. 🛠️ Troubleshooting: My Quota Still Looks Wrong If your credit balance or monthly quota still does not look correct after the fixes described above, try the following steps: 1. Hard-refresh your browser (Ctrl + Shift + R on Windows or Cmd + Shift + R on Mac) to clear any cached data. 2. Log out of Search Atlas and log back in. 3. Navigate to your avatar (top-right) > Billing and confirm your plan type and billing cycle dates. 4. Compare the displayed quota against the plan details listed on the Search Atlas pricing page. If the issue persists after these steps, our support team can review 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.

🗺️ Create Unique Slugs for Location Pages in Website Studio

🔍 Overview When you build location pages in Website Studio and sync them to WordPress, each page needs its own unique URL slug. By default, if you edit one page's slug without following the correct steps, Website Studio may apply that same slug across all your location pages — causing duplicate URLs and broken links on your WordPress site. This article explains why this happens and exactly how to set unique slugs for every location page. 💡 Why All Pages Update to the Same Slug Website Studio uses a template-based system for location pages. When you type a new slug directly into a shared template field, the platform treats it as the new default for every page generated from that template. As a result, all location pages inherit the same slug instead of getting individual ones. To avoid this, you must set unique slugs at the individual page level, not at the template level, before publishing or syncing to WordPress. ⚙️ How to Set a Unique Slug for Each Location Page 1. In Search Atlas, navigate to Website Studio and open your location pages project. 2. From the pages list, click on the specific location page you want to edit — do not edit the template directly. 3. Inside the page editor, locate the Publish Settings panel (usually on the right-hand side or accessible via the publish button). 4. Find the Slug field in the publish popup. This field may be pre-filled automatically based on the page title or your BrandVault settings. 5. Clear the pre-filled value and type the unique slug you want for this specific location (for example, plumber-austin-tx or services-miami-fl). 6. Confirm the slug looks correct, then click Save or Sync to WordPress. 7. Repeat steps 2–6 for each location page individually. Important: Always set or confirm the slug for each page before syncing. Once a page is published to WordPress, changing the slug later can cause the old URL to return a 404 error until your WordPress permalink cache is refreshed. ✅ Slug Formatting Best Practices - Use lowercase letters and hyphens only — no spaces or special characters (e.g., heating-repair-denver). - Include the city or region name in the slug to make each URL descriptive and SEO-friendly. - Keep slugs short and readable — aim for 3–6 words. - Avoid repeating the same keywords across multiple slugs, as this can create keyword cannibalization issues. - Do not use numbers or dates unless they are essential to the page topic. 🔄 After Syncing to WordPress Once your location pages are synced to WordPress with their unique slugs, verify each page is live by clicking the page link inside Website Studio. If any link returns a 404 error, try the following: 1. Log in to your WordPress dashboard. 2. Go to Settings > Permalinks. 3. Click Save Changes without making any edits — this forces WordPress to flush its permalink cache and register your new slugs. 4. Return to Website Studio and re-check the page links. If the 404 persists after flushing permalinks, the slug stored in Website Studio may not have updated correctly. Re-open the page's publish settings, confirm the slug is correct, and re-sync the page to WordPress. 🛠️ Troubleshooting Common Issues - All slugs still look the same after editing: Make sure you are editing each page individually from the pages list, not modifying a shared template field. - Slug field is greyed out or auto-filled: The auto-fill feature pulls from your page title and BrandVault. Click inside the field to override the value manually. - Pages sync as blog posts instead of standalone pages: During the sync popup, confirm the content type is set to Page, not Post, before completing the sync. - Homepage is replaced after sync: When syncing pages into a subfolder on your WordPress site, double-check the destination path in the publish popup so it does not overwrite your root homepage slug. 💬 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.

🔍 Find the AI Landing Page Feature in OTTO

What Is the AI Landing Page Feature? The AI Landing Page feature is part of OTTO SEO toolkit. It uses artificial intelligence to help you build and optimise landing pages directly within the platform. If you have been searching through menus and cannot find it, this article will guide you to the right place. Where to Find AI Landing Page in OTTO The AI Landing Page feature lives inside the OTTO SEO section of OTTO. Follow these steps to get there: 1. Log in to your Search Atlas account and open OTTO. 2. Look at the sidebar navigation menu. 3. Click OTTO SEO in the sidebar to open the OTTO SEO hub. 4. Once inside OTTO SEO, locate the AI Landing Page option within the tools listed on that page. The feature is accessible directly from the main sidebar navigation. Common Reasons You Might Not See It - Wrong section: AI Landing Page is not under the Content menu. Make sure you are clicking OTTO SEO, not Content, in the sidebar. - Plan or permission restrictions: Some features are available only on certain subscription plans. If OTTO SEO does not appear in your sidebar at all, your current plan may not include this feature. Check your plan details in account settings or speak with our team. Quick Navigation Reference As a general rule: tools powered by AI automation — including AI Landing Page — live under OTTO SEO in the sidebar. Tools focused on content creation and optimisation live under Content. If you are unsure which section a tool belongs to, the sidebar is always your starting point. 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.

🛠️ Landing Page Templates and Layout Limitations Explained

🔍 Overview Search Atlas is a powerful SEO research and content intelligence platform. Customers sometimes ask whether it includes a system for applying SEO-friendly page templates automatically when content is published — so that layout sections adjust dynamically around new content. This article explains what Search Atlas currently supports and how to make the most of its content tools. 📋 What Search Atlas Does and Does Not Include Search Atlas is designed for SEO strategy, content planning, keyword research, rank tracking, and local SEO management. It is not a website builder or CMS (Content Management System). As a result, it does not include: - Pre-built landing page templates that auto-apply to published content - Dynamic page layout sections that adjust automatically around content - A drag-and-drop page editor or front-end design tools - CMS-style publishing workflows that push styled pages live to a website If you need automated template-based layouts for published content, this functionality would need to be handled by your CMS or website platform (such as WordPress, Webflow, or Shopify) rather than Search Atlas. ✅ What Search Atlas Does Support While Search Atlas does not manage page templates or layouts, it provides a strong set of tools to help you plan, optimise, and monitor the content that goes into those pages. Here is what is available: - Content Editor: Create SEO-optimised content briefs and drafts guided by real keyword data, competitive analysis, and on-page recommendations. - Keyword Magic: Discover high-value keywords to target in your landing page content. Navigate to Left sidebar → Keywords → Keyword Magic. - Rank Tracker: Monitor how your landing pages perform in search results over time. Navigate to Left sidebar → Keywords → Rank Tracker. - Keyword Gap: Identify content opportunities your competitors are ranking for that your pages are missing. Navigate to Left sidebar → Keywords → Keyword Gap. - Local SEO Tools: Manage location-specific landing page content, posts, and citations via Left sidebar → Local → GBP Projects. 💡 Recommended Workflow for SEO-Friendly Landing Pages To build landing pages that are both well-structured and SEO-optimised, we recommend combining Search Atlas with your existing CMS or website platform: 1. Plan your content in Search Atlas: Use Keyword Magic and the Content Editor to identify target keywords and build a fully optimised content brief for each landing page. 2. Apply your template in your CMS: Use your website platform (WordPress, Webflow, etc.) to apply a reusable page template or layout to each new landing page before or after adding content. 3. Publish and track performance: Once your landing page is live, add the target URL and keywords to Rank Tracker in Search Atlas to monitor search visibility and make ongoing improvements. 4. Identify gaps and iterate: Use Keyword Gap regularly to find new content angles and update your landing pages to stay competitive. 🚀 Getting the Most Out of Search Atlas Search Atlas works best as the SEO intelligence layer that informs what goes on your landing pages, while your CMS or website builder controls how those pages look and how content is structured visually. Using both tools together gives you full control over both design and discoverability. If you manage local landing pages, explore the full Local suite — including Posts, Reviews, and Local Citations — by navigating to Left sidebar → Local → GBP Projects. These tools help ensure your location pages are accurate, consistent, and competitive in local search results. 🙋 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.

🛠️ Publish Website Studio Safely

🔒 Plan your publishing setup Website Studio previews should be treated as separate from your existing WordPress website until you confirm the publishing destination. Publishing can make the site publicly accessible, so review the destination and URL before you submit it. For a site such as trickettcounselling.com, the safest options are usually: - A subdomain: Use a separate address such as preview.trickettcounselling.com or new.trickettcounselling.com. - A separate domain: Publish to another domain when the new site must remain fully independent. - A new page on the existing WordPress site: Use this only when the publishing workflow clearly supports your WordPress setup and URL structure. ⚙️ Publish from Website Studio 1. Open Website Studio from the left sidebar. 2. Open the project you want to publish and review the preview carefully. 3. Select Submit and choose the available publishing destination. 4. Enter the target domain or subdomain exactly as intended. 5. Confirm the destination, URL path, and publishing warning before completing the submission. If you do not see a suitable WordPress or subdomain option, do not use a workaround that points the project at your live homepage. Keep the preview unpublished and verify the supported publishing method first. 🛡️ Avoid overwriting WordPress - Do not point a new project to your root domain unless you intend to replace the current site. - Do not reuse an existing homepage URL, category URL, or other important WordPress path. - Back up your WordPress site before changing DNS, hosting, plugins, or site files. - Confirm who controls DNS and hosting before changing records. - Test the new address privately where possible, then check navigation, forms, images, tracking, and redirects. A subdomain is generally safer than placing Studio content inside an existing WordPress folder because WordPress rewrite rules, category paths, and page slugs can conflict. If your goal is a folder such as trickettcounselling.com/new-page, verify that this exact setup is supported before publishing. 🌐 Connect a subdomain safely Create the subdomain with your DNS or hosting provider, then follow the destination and verification instructions shown in Website Studio. Change only the required DNS record, and leave the existing root-domain records unchanged. After publishing, confirm that the root domain still loads WordPress and that the subdomain loads the Studio site. 💳 Press release costs and Hyperdrive credits Press release pricing and Hyperdrive credit usage are separate from the Website Studio publishing process. Website Studio publishing does not automatically include a press release, and a press release should not be assumed to use Hyperdrive credits unless the relevant product screen says so. Before starting a paid action, review its confirmation screen for the current price, included usage, and credit requirement. Check your available Hyperdrive balance in the platform and confirm whether the action will consume credits before approving it. Prices, plans, and credit requirements can change, so use the in-platform details as the source of truth. ✅ Publishing checklist - The destination is a subdomain, separate domain, or approved WordPress page. - The root WordPress homepage and important URLs will remain unchanged. - DNS and hosting access are available to the person making the change. - The preview has been checked on desktop and mobile. - Any press release cost and Hyperdrive credit usage are confirmed before purchase. 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.

🖼️ Logo Upload Requirements and Troubleshooting Guide

🖼️ Overview Uploading your logo to Search Atlas personalises your workspace and keeps your branding consistent across reports and dashboards. If your logo is not loading or the upload fails, this guide walks you through the requirements and the most effective fixes. 📐 Logo File Requirements Before uploading, make sure your file meets all of the following requirements: - Accepted formats: PNG, JPG, JPEG, SVG, or WebP - Maximum file size: 2 MB - Recommended dimensions: 200 × 80 px (landscape orientation works best) - Background: Transparent PNG files are recommended for the cleanest display - Colour mode: RGB (not CMYK — CMYK files may fail to upload or display incorrectly) Files that exceed the size limit or use an unsupported format will be silently rejected or fail to display, so confirming these details first saves time. 🛠️ Step-by-Step Troubleshooting Work through the steps below in order. Most logo upload issues are resolved within the first two or three steps. 1. Check the file size and format. Open your file manager, right-click the image, and select Properties (Windows) or Get Info (Mac). Confirm the file is under 2 MB and is one of the accepted formats listed above. 2. Resize or compress the image. If the file is too large, use a free tool such as Squoosh, TinyPNG, or Adobe Express to compress it below 2 MB without losing visible quality. Re-save as PNG or JPG before trying again. 3. Convert CMYK to RGB. If your logo was exported from a print workflow, it may be in CMYK colour mode. Open it in your image editor and convert the colour mode to RGB, then re-export. 4. Rename the file. Remove any special characters, spaces, or accented letters from the filename. Use only letters, numbers, hyphens, and underscores (e.g. company-logo.png). 5. Clear your browser cache. A cached version of the page can make it appear that the upload failed even when it succeeded. Press Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac) to hard-refresh, then check the logo again. 6. Try a different browser. Test the upload in a second browser (Chrome, Firefox, or Edge) to rule out a browser extension or local setting causing the issue. 7. Disable browser extensions. Ad blockers and privacy extensions occasionally intercept file upload requests. Temporarily disable all extensions, then attempt the upload again. 8. Check your internet connection. Large file uploads can time out on slow or unstable connections. Switch to a stable network and retry. 📤 How to Upload Your Logo Once your file meets all requirements, follow these steps to upload your logo inside Search Atlas: 1. Log in to your Search Atlas account. 2. Click your avatar in the top-right corner of the platform. 3. Select White Label Setup from the dropdown menu. 4. Navigate to Settings (Logo). 5. Click Upload Agency Logo, select your prepared file, and confirm. 6. Hard-refresh the page to see the updated logo displayed across your account. ⚠️ Still Not Working? If you have followed every step above and the logo still will not load, there may be an account-level issue that requires manual review by 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, please have the following ready to speed up the resolution: - The logo filename and file size - The file format (PNG, JPG, SVG, etc.) - A screenshot of any error message displayed during the upload - The browser and operating system you are using

🔒 Connect Your Domain to a Website Studio Landing Page

🗺️ Overview When you publish a landing page in Website Studio and want it to appear on your own domain or subdomain, you need to point your DNS records to Search Atlas and allow an SSL certificate to be issued. This guide explains what you'll need to prepare and what to expect during the process. 🛠️ Before You Begin Make sure you have the following ready before you start: - Access to your domain registrar or DNS hosting provider (e.g., GoDaddy, Cloudflare, Namecheap). - The landing page already created inside Website Studio (Left sidebar → Website Studio). - Permission to edit DNS records for the domain you want to use. 📋 Step 1 — Retrieve Your DNS Values from Website Studio 1. In the Search Atlas platform, open Website Studio from the left sidebar. 2. Open the landing page you want to publish and locate the domain or publishing settings for that page. 3. Note the DNS values (such as a CNAME target or IP address) that Search Atlas provides for your custom domain. You will need these in the next step. ⚙️ Step 2 — Add the DNS Record at Your Registrar Log in to your DNS provider and create a new record using the values from Step 1: - Record type: CNAME (recommended for subdomains such as landing.yourdomain.com) or A record (for a root domain). - Host / Name: The subdomain prefix you want to use (e.g., landing, promo, or @ for the root). - Value / Points to: The CNAME target or IP address copied from Website Studio. - TTL: Set to Auto or 3600 (1 hour) to allow changes to propagate quickly. Save the record. DNS propagation typically takes a few minutes up to 48 hours, though most providers update within 1–2 hours. 🔒 Step 3 — Connect Your Custom Domain and Enable SSL Once DNS has propagated, return to Website Studio and open the same landing page. Enter your custom domain in the domain connection area of the page settings and save your changes. Search Atlas will verify that the DNS record points to the correct destination and then provision an SSL certificate. Allow some time after DNS propagation has completed for the SSL certificate to be issued. 🔍 Troubleshooting Common Issues - SSL certificate not issuing: The most common cause is that DNS has not yet fully propagated. Wait 1–2 hours, then return to the domain settings for your landing page and attempt to verify or reconnect your domain. - Domain shows an error or is unreachable: Double-check that the DNS record values match exactly what Website Studio provided. A typo in the CNAME target or IP address will prevent the domain from connecting correctly. - Using Cloudflare: If your domain is proxied through Cloudflare (orange cloud), set the DNS record to DNS-only (grey cloud) while the SSL certificate is being provisioned. You can re-enable proxying afterward if needed. 📞 Need Help? If you have followed these steps and are still experiencing issues connecting your domain or provisioning SSL, our support team can review your specific configuration. Please have the following ready when you reach out: - Your landing page name or URL as it appears in Website Studio. - The custom domain or subdomain you are trying to connect. - The DNS record you have added at your registrar (record type, host, and value). - Any error message displayed in the platform, along with the approximate time it appeared. 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.

🖼️ Removing Hero Overlay and Resizing Your Logo

🔍 Overview In Website Studio, your hero section may display a dark overlay (also called an image scrim) over your background image, and your logo may appear smaller than you'd like. This article walks you through how to remove the overlay and resize your logo so your homepage looks exactly the way you want it. 🗑️ Removing the Dark Overlay from Your Hero Image The dark overlay is a semi-transparent layer applied on top of your hero background image. Follow these steps to remove it: 1. Open Website Studio from the left-hand navigation menu. 2. Select your website and navigate to the Home page. 3. Click on the Hero section to open its settings panel. 4. Look for the Overlay or Image Scrim toggle in the settings panel. 5. Toggle the option off to remove the dark overlay from your hero image. 6. Click Save or Publish to apply your changes. Important: After removing the overlay, make sure to save your page before navigating away. If you leave the page without saving, the overlay may be re-applied automatically. Always confirm your changes are saved before moving to another section. 📐 Resizing Your Logo on the Home Page If your logo appears too small in the hero section or header, you can increase its size directly in Website Studio: 1. In Website Studio, open your Home page in the editor. 2. Click on the logo element in the hero section or header to select it. 3. In the settings panel on the right, locate the Logo Size or Width slider. 4. Drag the slider to the right or enter a larger value to increase the logo size. 5. Preview the result on both desktop and mobile views to ensure the logo looks good across all screen sizes. 6. Click Save or Publish to apply your changes. Tip: If your logo appears blurry after resizing, upload a higher-resolution version of your logo file (PNG or SVG recommended) through Agency Settings (Logo) → Upload Agency Logo before adjusting the size. ⚠️ Common Issues and How to Fix Them - The overlay comes back after saving: This can happen if you navigate away too quickly. Save your changes, then refresh the page to confirm the overlay has been removed successfully before closing the editor. - Logo changes are not saving: If your logo size edits are not persisting, try clearing your browser cache and making the adjustment again. Ensure you click Save before leaving the page. - Logo is hard to read on the hero image: If your logo blends into the background after removing the overlay, consider uploading a version of your logo with a contrasting color or a transparent background. You can also add a subtle drop shadow through the logo element settings. - Edits on duplicated pages overwrite the original: Avoid editing both a duplicated page and the original at the same time. Make all changes on one page, save, and then proceed to the other to prevent conflicts. ✅ Best Practices for Your Hero Section - Always preview your page on both desktop and mobile after making changes to the hero section. - Use high-resolution images (at least 1920×1080 px) for hero backgrounds to avoid pixelation. - Keep your logo file in SVG or PNG format with a transparent background for the best results at any size. - Save frequently while editing to prevent losing your work. 💬 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.

🎨 Cloud Stacks Color Customization: Limitations Explained

🌐 What Is Cloud Stacks? Cloud Stacks is a link-building feature inside Search Atlas that automatically generates and publishes optimized web properties across a network of cloud-based platforms. Each published property includes structured content, internal links, and a visual design — all generated automatically to support your authority-building campaigns. 🎨 Can You Change the Colors in Cloud Stacks Content? No. Cloud Stacks does not currently support manual color customization. The colors displayed in your generated content are determined by preset templates used during the publishing process. Custom brand colors cannot be applied at this time. This is a platform-level constraint, not a bug or misconfiguration on your account. 📐 Why Are Templates Preset? The use of preset templates is an intentional platform design decision. Custom color inputs are not supported in the current version of Cloud Stacks. 🔍 Does Color Affect SEO Performance? For Cloud Stacks web properties, color customization is not a factor in SEO outcomes. These properties function as supporting authority assets rather than brand-facing landing pages, so visual styling to match your main site is not their intended purpose. If you have questions about color options or template behavior in your specific Cloud Stacks setup, our team can help clarify what is available for 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.

Cloudflare Orange Cloud Proxy Compatibility with Search Atlas Website Builder

Overview Cloudflare's orange cloud (proxy) mode routes your traffic through Cloudflare's network, providing benefits like DDoS protection, SSL termination, and performance caching. However, enabling it alongside the Search Atlas Website Builder may cause compatibility issues depending on your specific DNS and hosting configuration. This article covers what you need to know about Cloudflare orange cloud proxy compatibility with Search Atlas Website Builder, including steps you can take on your own and how to get help from our team. What Is the Orange Cloud (Proxy) Mode? In Cloudflare, DNS records can be set to either proxied (orange cloud) or DNS only (gray cloud). When a record is proxied, traffic flows through Cloudflare's network before reaching your origin server. When set to DNS only, traffic goes directly to your origin without passing through Cloudflare. Depending on how your Website Builder site and DNS records are configured, enabling or disabling proxy mode on specific records may affect how your site loads and how Search Atlas interacts with your domain. Known Compatibility Considerations Cloudflare orange cloud proxy mode can interact with Search Atlas Website Builder in ways that vary by setup. Common symptoms include a broken or blank site, failed pixel or UUID detections, and unexpected DNS behavior after changing proxy settings. Step-by-Step Troubleshooting Follow these steps in order to resolve proxy-related issues with your Website Builder site: 1. Switch your CNAME records to DNS only (gray cloud). In your Cloudflare DNS dashboard, locate the CNAME records associated with your Search Atlas Website Builder domain and update the proxy status to DNS only (gray cloud). Save your changes. 2. Wait for DNS propagation. After switching to gray cloud, allow up to 5–10 minutes for the change to propagate. Then reload your site to check whether the issue is resolved. 3. Test your site functionality. Confirm that your site loads correctly and that any Search Atlas features (such as pixel or UUID detection) are functioning as expected. 4. If issues persist, contact our support team. Because the root cause of orange cloud conflicts can vary significantly by DNS and hosting configuration, our team can review your specific setup and advise on the correct proxy settings for your domain. What to Expect After Changing Proxy Settings In many cases, switching the relevant CNAME records to DNS only (gray cloud) resolves compatibility issues with Search Atlas Website Builder. If your setup requires orange cloud to remain enabled for specific records, our support team can help you identify which records are safe to proxy and which should remain on gray cloud. Still Need Help? If you have followed the steps above and are still experiencing issues, please reach out to the Search Atlas support team through the chat icon in your dashboard. Our team is happy to review your Cloudflare and DNS configuration and help you find the right solution.

🌐 Publish Website Studio Pages and Manage Service-Area GBPs

Overview This article covers two common tasks: publishing landing pages you have built in Website Studio to a live website, and making sure your Google Business Profiles (GBPs) for multiple service areas are set up and verified correctly. Because both of these workflows depend on your specific account configuration, the steps below outline what to prepare and how to get the right guidance for your setup. Publishing Your Website Studio Landing Pages Website Studio lets you design and preview landing pages inside Search Atlas. Publishing those pages to a live website depends on your hosting setup and how your account is configured. Since the publishing workflow varies by account, there is no single set of in-app steps that applies universally. To move forward with publishing, make sure you have the following ready: - The name of the landing page(s) you want to publish, as they appear in Website Studio. - The domain or subdomain you want to publish to. - Your CMS or hosting platform name (for example, WordPress, Webflow, or a custom setup). - Any specific URL slugs or folder structures you want to use for SEO targeting (for example, /plumber-austin-tx). With this information on hand, our support team can confirm the correct publishing path for your account and walk you through the exact steps. Setting Up and Verifying Service-Area Google Business Profiles If your business serves customers in multiple locations, you may have a separate GBP for each service area. Verifying and configuring each profile is done directly through Google's own platform at business.google.com — this is not managed inside Search Atlas. To get your service-area GBPs into the correct state, take the following steps in Google Business Profile Manager: - Sign in at business.google.com and open each service-area profile. - Review the business category and service-area settings for each profile to make sure they reflect the correct region and services. - For any profile that is not yet verified, follow Google's verification prompts to complete verification. - Repeat for each additional service-area profile you manage. Note: Google controls the available verification options and timelines. If you run into issues with a specific profile, note the profile name and the error or status message you see, as our team may be able to advise on next steps. What to Have Ready When You Contact Support To help our team assist you as quickly as possible, please have the following information available: - Your Search Atlas project or account name. - The specific landing page name(s) in Website Studio you want to publish. - Your hosting platform or CMS name. - For GBP issues: the name of the affected profile(s) and any error or status message you are seeing in Google Business Profile Manager. 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.

🌐 Publish Wix Site via GoDaddy to Namecheap Hosting

🔧 Understand the Setup You can design your site in Wix, register the domain at GoDaddy, and host the live site on Namecheap. This requires pointing the domain's DNS to Namecheap while keeping the site content managed in Wix. 📋 Prerequisites - Active Wix account with a published site - Domain registered at GoDaddy - Hosting plan at Namecheap (Shared Hosting, WordPress Hosting, or VPS) - Access to all three dashboards ⚙️ Step 1: Get Namecheap Nameservers 1. Log in to Namecheap and go to Domain List → Manage next to your hosting plan 2. Find the Nameservers section (usually ns1.namecheaphosting.com, ns2.namecheaphosting.com) 3. Copy both nameserver values 🌍 Step 2: Update GoDaddy Domain DNS 1. Log in to GoDaddy and open My Products → Domains 2. Select your domain and click DNS → Nameservers 3. Choose Custom Nameservers and paste the two Namecheap nameservers 4. Save changes — propagation can take up to 48 hours 🖥️ Step 3: Add Domain in Namecheap Hosting 1. In Namecheap cPanel, go to Addon Domains or Domains 2. Enter your GoDaddy-registered domain name 3. Set the document root (e.g., public_html/yourdomain) 4. Submit and wait for the domain to be added 🚀 Step 4: Publish Wix Site to Namecheap 1. In Wix, open your site dashboard and go to Settings → Website Settings → Custom Domain 2. Click Connect a Domain You Already Own 3. Enter your domain (e.g., yourdomain.com) and follow the verification steps 4. Wix will provide DNS records (A, CNAME) — do not add these in GoDaddy 5. Instead, log in to Namecheap cPanel → Zone Editor and add the Wix-provided records there 6. Return to Wix and click Verify Connection ✅ Step 5: Verify and Test - Wait for DNS propagation (use a tool like dnschecker.org) - Visit your domain in a browser — the Wix site should load - Check SSL: In Namecheap cPanel, run AutoSSL or request a Let's Encrypt certificate - Test mobile, forms, and e-commerce flows if applicable 🛠️ Troubleshooting Common Issues - Site not loading after 48h: Confirm nameservers at GoDaddy match Namecheap exactly - SSL errors: Ensure the domain is added in Namecheap hosting before requesting SSL - Wix verification fails: Double-check DNS records in Namecheap Zone Editor — no typos, correct record types - Email not working: Add MX records in Namecheap Zone Editor for your email provider (Google Workspace, Microsoft 365, etc.) 💡 Best Practices - Keep a screenshot of all DNS records before making changes - Set a calendar reminder to renew domain at GoDaddy and hosting at Namecheap - Use Wix's built-in backup before major edits - Monitor uptime with a free tool like UptimeRobot 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.

✏️ Edit Target URL in a Draft Cloud Stack

🔍 Overview When you create a Cloud Stack, you set a Target URL as part of the initial setup. If you need to change that URL before the stack goes live, you can do so while the Cloud Stack remains in draft status. This article walks you through how to find and update the Target URL without starting over. 🧭 How to Navigate to Your Draft Cloud Stack 1. Log in to your Search Atlas account. 2. In the left sidebar, click Authority. 3. Select Cloud Stacks from the expanded menu. 4. Locate the Cloud Stack with Draft status in your list. 5. Click on the Cloud Stack name to open it. ✏️ How to Edit the Target URL 1. Once inside the draft Cloud Stack, look for the Target URL field. This is typically displayed in the first step or the settings section of the stack setup. 2. Click the Target URL field to make it editable. 3. Clear the existing URL and type or paste your new Target URL. 4. Review any other settings you want to confirm before publishing. 5. Click Save or Update to apply your changes. Your updated Target URL will now be used when the Cloud Stack is published and the links are built. ⚠️ Important Things to Know - Draft status only: You can only edit the Target URL while the Cloud Stack is in draft mode. Once a stack has been submitted and is being processed or is live, the Target URL cannot be changed. - URL validation: Make sure your Target URL is a valid, publicly accessible page. Invalid URLs may cause errors during publishing. - Impact on content: If AI-generated content has already been created referencing your original URL, you may want to review and regenerate that content after updating the Target URL to ensure consistency. - Anchor text: After changing the Target URL, review your anchor text settings to make sure they still align with the new destination page and its keywords. 🛠️ Troubleshooting - Field appears locked or greyed out: Confirm the stack is still in Draft status. If it has moved to a processing or live state, editing is no longer available. - Changes are not saving: Refresh the page and try again. If the issue persists, clear your browser cache or try a different browser. - Target URL field is not visible: Navigate to the first step of the Cloud Stack setup using the step indicators at the top of the page — the Target URL field is located in Step 1. 💬 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.

🌐 Website Studio Monthly Quotas and Universal Credits Explained

🧭 Overview Website Studio uses Universal Credits (UC) to power website generation. Each plan comes with a monthly Universal Credits allowance, and Website Studio draws from that shared pool whenever you generate a site. Understanding how credits are counted helps you plan your projects and avoid unexpected limits. 📊 How Universal Credits Work in Website Studio Universal Credits are a shared resource across several Search Atlas tools, including Website Studio. When you generate a website in Website Studio, Universal Credits are deducted from your monthly balance. Key things to know: - Each website generation consumes a defined number of Universal Credits. - Credits are shared across tools — heavy use in one area reduces availability in others. - Your remaining credit balance is visible in the Billing section of your account. 💳 Credit Allowances by Plan The exact number of Universal Credits included with each Search Atlas plan, and the per-generation cost in Website Studio, vary by plan tier and may be updated over time. To confirm your current monthly allowance and how many credits each website generation consumes under your specific plan, please check the Billing section of your account or contact our support team directly. 📈 How to Check Your Current Credit Usage 1. Log in to your Search Atlas account. 2. Navigate to the Billing section of the platform. 3. Review your Universal Credits balance to see how many credits you have used and how many remain for the current billing period. ❓ What To Do If You Hit Your Quota If you reach your monthly Universal Credits limit before the end of your billing cycle, website generation in Website Studio will be unavailable until your credits reset or you take one of the following actions: - Upgrade your plan: Moving to a higher tier immediately increases your monthly Universal Credits allowance. You can initiate an upgrade from the Billing section of your account. - Wait for your monthly reset: Universal Credits reset at the start of each new billing cycle and do not roll over from month to month. When reaching out to support about a quota issue, please have the following ready: your account email, your current plan name, the approximate date you hit the limit, and any error messages you received in Website Studio. 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.

🔍 Check August Summit Form Pages

📋 Pages covered This article covers the August Summit Form pages reported at: - https://searchatlas.com/agentic-marketing-summit/a/ - https://searchatlas.com/agentic-marketing-summit/b/ - https://searchatlas.com/agentic-marketing-summit/d/ - https://agenticmarketingsummit.com/ 🔎 How to verify you are on the correct August Summit page If you are looking for the August Summit registration form, use only the URLs listed above. Each of these pages is an official entry point for the Agentic Marketing Summit. To confirm you are in the right place: 1. Open one of the URLs listed above directly in your browser — do not rely on a link forwarded through email or social media, as those may point to an outdated or incorrect page. 2. Check that the page displays the August Summit registration form. The form should be visible without scrolling on most desktop screens. 3. If the form is not visible, perform a hard refresh (Ctrl+Shift+R on Windows, Cmd+Shift+R on Mac) to clear any cached version of the page, then check again. 4. If the form is still not visible after the hard refresh, try a different URL from the list above — for example, if /a/ is not loading correctly, try /b/ or agenticmarketingsummit.com directly. 5. If none of the URLs show the form, note the exact URL you visited, what you see instead of the form (blank page, error message, different content), and the date and time you observed it. ✅ What to have ready when escalating If you have tried all the URLs above and the August Summit Form is still not accessible, have the following details ready before contacting support so the correct team can investigate quickly: - The exact URL(s) where the form is missing or incorrect - A description of what is currently displayed instead of the form (e.g. blank page, wrong content, error message) - The date and time you first noticed the issue - The browser and device you are using - Any error messages shown on the page 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.

💡 Understanding LPS Credits in Website Studio

🔍 What Are LPS Credits? LPS (Landing Page Studio) credits are the currency that powers AI-assisted site creation and editing inside Website Studio. Every time the AI generates or rewrites content, builds a new site structure, or applies edits, it draws from your LPS credit balance. Understanding how credits are consumed helps you plan your usage and avoid unexpected shortfalls. 🏗️ How Credits Are Consumed When Building and Editing Sites LPS credits are used when the AI is actively involved in creating or modifying your site. AI-driven actions — such as generating a new site, producing AI-written content, or having the AI rework existing sections — draw from your credit balance. If you have a specific question about whether a particular action on your plan will consume credits, or how many credits a given action costs, please reach out to our support team so they can review the details of your account and plan. 📊 How to Check Your LPS Credit Balance To find your current LPS credit balance, navigate to your account settings within the platform. Look for a billing or usage section where your credit balance and consumption history are typically displayed. If you cannot locate your balance in account settings, our support team can pull up your credit usage details and clarify how credits are allocated on your specific plan. 💡 Tips to Use LPS Credits Efficiently A few simple habits can help you get the most out of your LPS credits: - Plan your site structure and content before starting an AI-assisted build so you can generate as much as possible in a single session. - If you are working on a large project, contact our support team beforehand to clarify how credits will be applied on your plan. - If you believe credits are being consumed unexpectedly, note the specific action you took and the timestamp so our team can investigate your account accurately. 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.

🖼️ Upload and Preview Your CloudStack Logo

Overview This article explains how to upload a brand logo inside CloudStack and troubleshoot cases where the logo does not appear correctly in the live preview. How to Upload Your Logo in CloudStack To add or update your logo within the CloudStack editor, locate the logo upload area inside your CloudStack project. The exact location of this option may vary depending on your project configuration — look for a branding or logo-related section within the editor interface. Once you have found the upload area, select your logo file from your device and confirm your changes to set the logo. Fixing Logo Preview Display Issues If your logo has been uploaded but is not showing correctly in the live preview, try the following steps: - Hard-refresh the preview: Force your browser to reload the page and clear cached assets. - Re-upload the logo: Remove the existing logo and re-upload your file to force the preview to update. - Try a different browser: If the preview issue persists, open CloudStack in a different browser to rule out a browser-specific rendering problem. - Save and re-open the project: After uploading, save your settings, close the project, and reopen it to see if the logo now appears in the preview. What to Have Ready When Escalating If the steps above do not resolve your issue, a member of our support team will need to investigate further. Please have the following ready when you reach out: - The name of the specific CloudStack project where the logo issue is occurring. - A description of what you see instead of your logo (for example, a blank space, a placeholder, or an error message). - The exact error message or text displayed on screen, if any. - The file format and approximate file size of the logo you attempted to upload. - The timestamp of when you attempted the upload. 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.

🚀 Creating Landing Pages with Website Studio

🎯 Landing Pages vs. Blog Posts A blog post is meant to inform and attract search traffic. A landing page is built to convert visitors. It usually focuses on one offer, service, or location, and it has a clear call to action such as booking a call, requesting a quote, or signing up. If you have been creating blog content and want a true landing page, Website Studio is the tool to use. It lets you create page-style content for your website instead of only article-style posts. 🛠️ What You Can Do with Website Studio - Create new landing pages for services, products, campaigns, or locations. - Edit page content, layout, and wording before publishing. - Prepare pages that are ready to publish to your connected website. Available features can vary by plan and by how your website is connected, so what you see in your account may differ slightly from this guide. 📝 Before You Start - Define the goal. Decide what one action you want visitors to take. - Choose a target keyword. Pick the main search phrase the page should rank for. - Know your audience. Note the service, product, or location the page is about. - Check your credits. Make sure your account has enough credits to complete the work. - Confirm your website connection. This matters if you plan to publish directly from the platform. 🚀 How to Create a Landing Page 1. Log in to your Search Atlas account and open Website Studio from the main navigation. 2. Select the option to create a new page or project. 3. Choose the page type that best matches a landing page. 4. Enter the details the tool asks for, such as your business information, target keyword, offer, and desired call to action. 5. Generate the page and wait for the draft to finish. 6. Review the content carefully. Check headlines, calls to action, contact details, and any claims or prices. 7. Make edits until the page matches your brand and goal. 8. Publish the page to your connected website, or export it if that is the option available for your setup. 💳 How Credit Usage Works Some Website Studio actions use credits. Typically, the actions that consume credits are the ones that involve generating or regenerating content with AI. Credit amounts can vary depending on your plan and the action you take. - Generating a new page may use credits. - Regenerating or rewriting sections may use additional credits. - Manual edits that you type yourself are generally not what drives credit use, but this can vary by feature. To see your current balance and recent usage, check the credits or usage area in your account settings or plan details inside the platform. 💡 Tips to Use Fewer Credits - Prepare your keyword, offer, and call to action before you start so you get a strong first draft. - Give clear, specific details when the tool asks for input. Vague input often leads to extra regeneration. - Make small wording changes manually instead of regenerating the whole page. - Review the full draft before regenerating anything, so you can fix several issues in one pass. - Create one page per goal rather than trying to cover several offers on a single page. ✅ Best Practices for High-Converting Landing Pages - Use one clear headline that matches the search intent of your keyword. - Keep one primary call to action and repeat it where it makes sense. - Include trust elements such as reviews, guarantees, or credentials. - Keep the page focused. Avoid links that lead visitors away from the goal. - Check how the page looks on mobile after publishing. 🔧 Troubleshooting Common Issues - I cannot find Website Studio. It may not be included in your current plan, or it may be in a different part of the navigation. Check your plan details. - I do not see a publish option. Your website may not be connected yet. Review your website connection settings and try again. - My credits ran out. Check your plan details for your renewal date and the options available for adding credits. - The page does not look right. Review and edit the content before publishing, and add more detail about your business if the draft feels generic. 🤝 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.

🔄 Transfer a Website Studio Project Between Accounts

🗂️ What Is a Website Studio Project Transfer? A Website Studio project transfer moves a project from one Search Atlas account to another. This is commonly needed when an agency builds a site on behalf of a client and the finished project must be handed over to the client's own Search Atlas account. 🛠️ How to Request a Project Transfer 1. Navigate to Website Studio and note the exact project name you want transferred. 2. Gather the relevant details for your request, including the project name and the source and destination accounts involved. 3. Contact our support team and describe your Website Studio project transfer request so a team member can assist you directly. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

📍 Manage Location and Service Page Templates

📍 How location and service page templates work Templates provide a reusable layout for creating pages for different locations and services. The page copy and location details still need to match the business and the area each page targets. CityWIDE appears to refer to broad-area targeting, rather than a specific city. Confirm the intended service area before using a CityWIDE template or updating its copy. 🛠️ Choose the right brand and locations 1. Select the brand whose templates and business information match the pages you need. 2. Check the locations assigned to the brand. Do not assume a city mentioned in a summary is the correct location for the page. 3. Update the copy so it names the intended city or service area and accurately describes the services offered there. 4. Review each generated page for mismatched city names, business details, or service-area claims before publishing. 🔎 Review location summaries carefully A summary may show a city that does not match the intended target. For example, if a summary says Baltimore but the page is meant for a CityWIDE location in Acworth, Georgia, correct the location and copy to reflect the intended Acworth service area. Do not treat the summary alone as confirmation of the page’s target. ✅ Before publishing - Confirm the selected brand is correct. - Verify the page’s city or broader service area. - Check that the headline, body copy, and calls to action match that location. - Make sure no unrelated city names remain in the page. 💬 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 instantly connected with a member of our team.

🛠️ Edit an Existing Page in Website Studio

📌 Overview Website Studio lets you build and manage the pages of your website in one place. Once a page exists, you can go back to it at any time to update text, images, headings, or layout. This article shows you where to find your existing pages and how to edit them. ✅ Before You Begin - Make sure you are signed in to your Search Atlas account. - Confirm that the website or project you want to work on has already been created in Website Studio. - Have your changes ready, such as new copy, images, or links, so you can work faster. 🔍 Where to Find Your Existing Pages Your existing pages are listed inside the website or project they belong to. Follow these steps to reach them: 1. Open Website Studio from the main navigation menu in the platform. 2. Select the website or project that contains the page you want to change. 3. Look for the Pages list for that website. It shows every page you have created. 4. Use the search box or scroll through the list to find the page you need. Menu labels may vary slightly depending on your plan or the latest platform updates, but the pages for each website are always grouped together under that website. ✏️ How to Edit a Page 1. In the Pages list, find the page you want to change. 2. Click the page name, or look for an Edit option next to it, to open the page in the editor. 3. Click the section, text block, image, or element you want to change. 4. Make your changes directly in the editor. You can update wording, replace images, adjust headings, and rearrange sections. 5. Review the page to confirm everything looks the way you want. 💾 Save and Publish Your Changes Editing a page does not always update your live website right away. After you finish: 1. Click Save to keep your edits. 2. Preview the page, if a preview option is available, to check how it looks. 3. Click Publish or Update to push your changes to your live website. If you leave the editor without saving, your latest changes may be lost. Save often, especially after large edits. 💡 Tips for Better Page Edits - Edit one section at a time. This makes it easier to spot mistakes. - Keep your target keyword in mind. When you rewrite headings or copy, make sure the main topic of the page stays clear. - Check links and buttons. After editing, make sure each one still points to the right place. - Preview before publishing. A quick look can catch spacing and formatting problems. 🧰 Troubleshooting - I can't find my page. Make sure you selected the correct website or project. Pages only appear under the website they were created in. Try the search box if your list is long. - There is no Edit option. Try clicking the page name directly. If the page still will not open, refresh your browser and try again. - My changes are not showing on my live site. Make sure you clicked Save and then Publish or Update. Allow a few minutes, then clear your browser cache or refresh the page. - The editor is slow or not loading. Refresh the page, close extra browser tabs, or try a different browser. 💬 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.

🚀 Publishing a Landing Page Without Replacing Your Homepage

🔍 The Short Answer Website Studio publishes the project you are working in. Publishing a landing page project sends it to its own preview URL so you can review it. It does not automatically replace the homepage of your existing live website. Publishing to the project’s preview URL does not replace your existing homepage. Connecting your main domain to the project or publishing to WordPress with Replace homepage can affect it. Also check whether WordPress auto-sync is enabled before republishing. (landing-page-studio/next\_js\_service/app/components/WordPressSyncModal.tsx:591–619; landing-page-studio/django\_service/core/views.py:3810–3823) 🧭 What the Publish Button Does - Publishes the current project, not just the page selected in the editor. Separate Website Studio projects are not published by this action, but enabled WordPress auto-sync can also update websites previously linked to this project. (landing-page-studio/django\_service/core/views.py:3772–3774,3810–3823) - Creates or updates a preview URL. This is a shareable link where you can see the page as visitors would. - Publishing only to the project’s preview URL leaves your separately hosted website unchanged. Connecting your domain or using WordPress publishing can affect your existing site; check connected destinations and WordPress auto-sync before publishing. (landing-page-studio/next\_js\_service/app/components/WordPressSyncModal.tsx:748–756; landing-page-studio/django\_service/core/views.py:3810–3823) You can publish again after making edits. The preview URL then shows your latest version. ✅ Before You Click Publish Run through this quick checklist to be sure you are only publishing what you intend to: 1. Open the landing page project you want to publish. In the editor’s menu, open Switch Project and confirm that the intended project is marked Current. (landing-page-studio/next\_js\_service/app/components/ChatPanelHeader.tsx:208–212,339–362) 2. Check the page list in the project. Confirm it contains only the landing page you want to release. 3. Check Settings → Domains and the publishing panel. To publish only to a preview URL, confirm that your live domain is not connected and that WordPress auto-sync is off; do not initiate WordPress publishing. (landing-page-studio/next\_js\_service/app/components/publish/PublishTargetSection.tsx:396–398; landing-page-studio/next\_js\_service/app/components/PublishModal.tsx:206–239) 4. If your main domain is connected to this project, publishing can update the website served on that domain. To leave your existing homepage untouched, publish to the preview URL without connecting the main domain. Changing the project’s home page only changes which project page appears at its root URL. (landing-page-studio/next\_js\_service/app/components/PublishModal.tsx:178–188; landing-page-studio/next\_js\_service/app/components/publish/PublishTargetSection.tsx:36–38) 5. Review the page on desktop and mobile in the editor preview. 🛠️ How to Publish to the Preview URL 1. Open Website Studio from your Search Atlas dashboard. 2. Select the landing page project. 3. Finish your edits and review the content, images, and links. 4. Click Publish. 5. Open the Publish panel and click Publish, or Publish Changes after editing an already published project. Wait until the status shows Published, then open the URL displayed in the panel. For preview-only publishing, first confirm that no live destination or WordPress auto-sync will be updated. (landing-page-studio/next\_js\_service/app/components/PublishModal.tsx:605–649,715–766) 6. Check the page in a browser. Copy the link to share it with teammates or clients for feedback. 🏠 How to Keep Your Homepage Safe - Keep the landing page in its own project. This keeps it separate from any full-site project. - Do not point your main domain at the project until you are ready. The preview URL works without any domain changes. - To keep your existing homepage, use a dedicated subdomain for the landing page project. For a connected WordPress site, choose Publish under a folder and enter a folder name such as offer to publish beneath yourdomain.com/offer without replacing its homepage. A page path inside a separate Website Studio project does not by itself add that project beneath your existing website. (landing-page-studio/next\_js\_service/app/components/WordPressSyncModal.tsx:271–272,604–619,748–756) - Back up your current homepage content before making any domain or hosting change. ⚠️ When a Homepage Could Be Replaced A homepage could be replaced if all of the following are true: - Your live domain is connected to the Website Studio project. - The landing page is set as the home page of that project. - You click Publish. If you are unsure whether your domain is connected, stop before publishing and check the project's domain settings. You can also ask our team to confirm (see below). 🤖 Submitting a Project to AI Directories Publishing in Website Studio makes your page available online, but it is a separate step from listing your site in third-party AI tool directories. Those directories have their own submission forms and requirements. A typical process looks like this: 1. Publish your page and, ideally, connect it to your own domain so the listing points to a permanent URL. Preview URLs may not be accepted by some directories. 2. Prepare a short description, your logo, a few screenshots, and your main category. 3. Submit these details on each directory's own website. 4. Keep a simple record of where you have submitted and the status of each listing. If you want to know whether your plan includes a tool to help with directory or listing submissions, the support team can confirm what is currently available for your account. 💡 Quick Tips - Treat the preview URL as a staging link. Share it for approval before going live. - Publish small changes often so the preview always matches your latest edits. - Test forms, buttons, and links on the preview page before sending traffic to it. - Avoid sharing the preview URL publicly if the page is not final. 💬 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.

💳 Website Builder Credits, Refunds and Logo Replacement

📌 Overview Website Builder uses credits when it generates or changes parts of your site. If your results do not match what you had in mind, it is easy to use many credits on repeated attempts. This article explains how to get better results with fewer credits, how to replace a logo or image without regenerating, and how to ask our team to review your credit usage. 💰 How Credits Are Used Credits are spent when you ask the builder to create or change content. Each new request, including a retry or a small tweak, can use credits. Broad requests that change a whole page may use more than small, focused ones. - Generating a new page or section uses credits. - Asking the builder to redo or rewrite something uses credits again. - Many back-and-forth changes in a row can add up quickly. 🎯 Why Results May Not Match Your Expectations The builder works best with clear, specific instructions. Results often miss the mark for a few common reasons: - Vague prompts: Short requests like make it look better leave a lot open to interpretation. - Too many changes at once: Asking for layout, text, colors, and images in one request can lead to mixed results. - Missing brand details: If the builder does not know your business, colors, or style, it has to guess. - AI-generated logos and images: Generated visuals rarely match an existing brand exactly. 💡 Tips to Get Better Results With Fewer Credits 1. Plan before you prompt. Write down your business name, services, target audience, colors, and the pages you need. 2. Be specific. For example, say Add a three-column services section with short descriptions and a contact button below it. 3. Change one thing at a time. Smaller requests are easier to check and correct. 4. Review before the next request. Check the result fully so you can combine fixes into one clear instruction. 5. Edit small details manually. Text, images, and button labels can usually be edited directly in the editor instead of being regenerated. 🖼️ How to Replace a Logo or Image If the builder did not create the logo you wanted, you do not need to keep regenerating it. Upload your own file instead. 1. Open your site in the Website Builder editor. 2. Click the logo or image you want to change, usually in the header or a content section. 3. Choose the option to replace, change, or upload an image. 4. Select your logo file from your computer. 5. Check how it looks on desktop and mobile, then save or publish your changes. Logo file tips: - Use a PNG with a transparent background for the cleanest look. - Use a high-resolution file so the logo stays sharp on all screens. - Keep the file size reasonable so your pages load quickly. - If the logo appears in more than one place, such as the header and footer, replace it in each location. If you cannot find the replace option for a specific element, let our team know which part of the site you are trying to change. 🔄 Requesting a Credit Review or Refund If you have used a large number of credits and are not satisfied with the results, our team can look at your account. Refund requests are not handled automatically in the platform. Each one is reviewed individually, and we cannot promise a specific amount or outcome in advance. To help us review your request quickly, have this information ready: - The name of the site or project in Website Builder. - An estimate of how many credits you used and over what period. - What you were trying to create, such as a page, a logo, or a layout. - What went wrong, such as results not matching your instructions. - Screenshots of the results, if possible. - The amount you are requesting and the reason. ⏱️ What to Expect - Our team will review your usage and the details you share. - We may suggest steps to fix the current site, such as replacing the logo or adjusting your instructions. - You will be told the outcome of the review, whether that is a credit adjustment or another solution. 🛟 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 instantly connected with a member of our team.