Domains, Hosting & SSL

🔧 Fix Cloudflare Orange Cloud SSL Verification Failures

What Is Happening If you are receiving repeated warning emails stating that your domain is blocked due to an extra AAAA DNS record — even though your own diagnostics appear normal — the most likely cause is Cloudflare's proxy feature, commonly known as the orange cloud. When the orange cloud is enabled on a DNS record in Cloudflare, Cloudflare can add additional records to your domain that may not be immediately visible through standard diagnostic tools. Our SSL verification system may detect these extra records and flag your domain as misconfigured, triggering repeated warning emails. This is a real DNS conflict — not a notification error — and it must be resolved at the DNS level to stop the emails and restore full SSL verification. Why Your Diagnostics Look Fine Third-party DNS lookup tools and your browser may show your site loading correctly because Cloudflare's proxy handles traffic successfully. However, our SSL verification system performs its own DNS resolution check that may reveal additional records Cloudflare introduces. The conflict can exist at the infrastructure level even when your site appears functional to end users. How to Fix the Issue Follow these steps in your Cloudflare account to resolve the conflict. 1. Log in to your Cloudflare account at cloudflare.com and select the domain receiving the warning emails. 2. Go to the DNS section using the left-hand navigation inside your Cloudflare dashboard. 3. Find the A record for your domain (typically your root domain or the subdomain you connected to Search Atlas). Look at the Proxy status column. 4. Disable the orange cloud by clicking the orange cloud icon next to the A record. It will turn grey. This switches the record from Proxied to DNS only mode. 5. Check for any standalone AAAA records listed separately in your DNS table for the same hostname. If any exist that were not intentionally added by you, delete them by clicking Edit then Delete. 6. Save your changes and allow time for DNS propagation to complete. Reverify Your Domain in Search Atlas Once you have switched to DNS only mode and removed any conflicting AAAA records, log in to your Search Atlas account and navigate to your whitelabel domain settings to locate your connected domain and trigger a fresh SSL verification check. 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 DNS/API Integration: How It Works

🔍 What Is the Cloudflare DNS/API Integration? The Cloudflare DNS/API integration connects Search Atlas directly to your Cloudflare account using an API token. This gives Search Atlas the ability to read and write your DNS configuration and interact with Cloudflare's edge network on your behalf — without requiring manual file uploads or plugin installations on your server. This method is designed for websites that already use Cloudflare as their DNS provider and want an automated path to technical SEO optimization. ⚙️ How to Set Up the Cloudflare DNS/API Integration Follow these steps to connect your Cloudflare account to Search Atlas: 1. Generate a scoped API token in Cloudflare: Log in to your Cloudflare dashboard, go to My Profile > API Tokens, and click Create Token. Use the Edit zone DNS template or create a custom token scoped to the specific zone (domain) you want to connect. Make sure the token has at least Zone: DNS: Edit and Zone: Zone: Read permissions. Copy the token — you will only see it once. 2. Enter the API token in Search Atlas: In Search Atlas, navigate to your site settings and select the Cloudflare DNS/API integration option. Paste the API token you generated into the designated field and save. 3. Confirm the correct zone is detected: After saving, Search Atlas will display the domain zone associated with the token. Verify that the zone shown matches the domain you intend to connect. If it does not match, check that your token is scoped to the correct zone in Cloudflare. 4. Verify the integration is active: Once connected, Search Atlas will be able to read and write your DNS configuration. Confirm the integration status shows as active or connected within your Search Atlas site settings. If you see an error, double-check the token permissions and that the token has not expired. 🔧 Troubleshooting Common Issues If the integration is not working as expected, check the following before reaching out to support: - Token permissions are too narrow: Make sure the token includes both Zone: DNS: Edit and Zone: Zone: Read at minimum. Missing permissions are the most common cause of connection failures. - Token is scoped to the wrong zone: If you manage multiple domains in Cloudflare, confirm the token is scoped to the specific zone matching the domain in Search Atlas. - Token has expired or been revoked: Cloudflare tokens can be set to expire. If the integration was working before and has stopped, regenerate the token in Cloudflare and update it in Search Atlas. - Zone does not match the domain in Search Atlas: Ensure the domain added in Search Atlas exactly matches the root domain managed in the Cloudflare zone (e.g., example.com, not www.example.com). 🚀 What to Have Ready If You Need Support If you have followed the steps above and the integration is still not connecting, please have the following ready before reaching out: - Your domain name and the Cloudflare zone it belongs to - A description of the specific behavior or feature you are asking about - Any error messages you have encountered during setup - The approximate date and time the issue started If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

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

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

⚡ Cloudflare DNS Proxying and Domain Verification

Overview When you connect a custom domain to Search Atlas, our platform performs a DNS verification check to confirm you own the domain. If your domain is managed through Cloudflare, its proxy setting (the orange cloud icon) can interfere with this process — causing verification to fail or your site to become unreachable inside the platform. This article explains how Cloudflare proxying affects domain verification and what information to have ready so our team can help you resolve it quickly. How Cloudflare Proxying Affects Verification Cloudflare offers two DNS modes for each record: - Proxied (orange cloud): Traffic is routed through Cloudflare's network. The real IP address of your server is hidden from external lookups. - DNS Only (grey cloud): DNS resolves directly to your server's IP. No Cloudflare proxy is applied. Search Atlas needs to resolve your domain to our servers to verify ownership and route traffic correctly. When Cloudflare's proxy is active, it returns Cloudflare's own IP addresses instead — so our verification check can fail even if your DNS record appears to be configured correctly. What You Can Check on Your End Before contacting support, review the following in your Cloudflare DNS settings: - Confirm whether the record pointing to Search Atlas is set to Proxied (orange cloud) or DNS Only (grey cloud). - Note the record type currently in use (CNAME or A record) and the value it is pointing to. - Check whether there are multiple conflicting records (for example, both a CNAME and an A record) for the same hostname. Because the correct DNS configuration depends on details specific to your Search Atlas account and project setup, our support team will need to confirm the exact record type and target value for your domain before you make any changes. Making changes without confirmed instructions from our team may cause additional downtime. What to Have Ready When You Contact Us To help our team resolve this as quickly as possible, please have the following information ready: - The domain or subdomain you are trying to connect to Search Atlas - The current DNS record type (CNAME or A record) and the value it points to, as shown in your Cloudflare dashboard - Whether Cloudflare proxying is currently set to orange cloud (Proxied) or grey cloud (DNS Only) - Any error message shown in Search Atlas when verification fails - The approximate time you first noticed the issue If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🌐 Cloudflare Nameserver Changes, DNS Propagation & Downtime

🔎 Overview Switching your nameservers to Cloudflare is a common step for improving site performance and security. However, the transition involves DNS propagation — a process that can temporarily affect your site's availability. When you update your nameservers, you are instructing the internet to stop using your old DNS provider and route traffic through Cloudflare instead. DNS records are cached across thousands of servers worldwide, and each of those servers must individually receive and apply the update. This process cannot be skipped or manually accelerated. This article explains what is normal, what is not, and who is responsible for resolving each type of issue. ⏱️ How Long Does DNS Propagation Take? After you point your domain's nameservers to Cloudflare, DNS changes must spread across servers worldwide. Here is what to expect: - Typical range: 30 minutes to 48 hours, depending on your domain registrar and global DNS infrastructure. - Most cases: Propagation completes within 2–6 hours for the majority of visitors, though some visitors may not see the updated routing for up to 12 hours. - Full global propagation: Can take up to 72 hours in rare circumstances, particularly for older TTL (Time to Live) settings on your previous DNS records, or in certain geographic regions with slower ISPs. During propagation, some visitors may see your old site, some may see your new Cloudflare-routed site, and a small number may experience brief intermittent access. This inconsistency is expected and temporary. Eight hours of downtime is well within the normal propagation window and does not by itself indicate a configuration problem. 🚫 What Not to Do During Propagation Avoid making additional DNS changes while propagation is in progress. Each edit can reset the clock and extend your downtime. Specifically: - Do not switch nameservers back to your previous provider - Do not delete or modify DNS records in Cloudflare until propagation is confirmed complete - Do not contact your domain registrar to try to speed up the process — propagation speed is determined by global DNS infrastructure, not your registrar 🚨 When Is Downtime NOT Normal? An 8-hour complete outage after a Cloudflare nameserver switch is not a standard propagation symptom. Prolonged downtime of this kind almost always points to one of the following server-side or configuration issues — none of which are caused by or controlled by Search Atlas: - Origin server misconfiguration: Cloudflare proxies traffic to your origin server. If the origin server's IP address, SSL certificate, or firewall rules are not correctly configured to accept Cloudflare's traffic, the site will go down. - Missing or incorrect DNS records in Cloudflare: After switching nameservers, Cloudflare imports your existing DNS records automatically — but this import is not always complete. A missing A record, CNAME, or MX record can cause downtime. - SSL/TLS mode mismatch: If your Cloudflare SSL/TLS setting (e.g. Full, Full Strict, Flexible) does not match your hosting provider's SSL configuration, the connection between Cloudflare and your origin server will fail. - Hosting provider firewall blocking Cloudflare IPs: Some hosting providers block traffic from Cloudflare's IP ranges by default. You may need to whitelist Cloudflare's IP addresses with your host. - Cloudflare account or zone configuration errors: An incomplete Cloudflare zone setup, a paused zone, or incorrect page rules can prevent your site from loading. 🛠️ Steps to Diagnose and Resolve Extended Downtime 1. Check your DNS records inside Cloudflare. Log into your Cloudflare dashboard and navigate to DNS → Records. Confirm that your A record points to the correct origin server IP address and that all other critical records (CNAME, MX, TXT) are present. 2. Verify your SSL/TLS mode. Go to SSL/TLS → Overview in Cloudflare. Match this setting to what your hosting provider supports. If unsure, start with Full and only use Full (Strict) if your origin has a valid SSL certificate installed. 3. Pause Cloudflare temporarily to isolate the issue. In your Cloudflare dashboard, go to Overview and click Pause Cloudflare on Site. If your site comes back online immediately, the issue is a Cloudflare configuration problem. If it remains down, the problem is with your origin server or hosting provider. 4. Contact your hosting or server provider. If pausing Cloudflare does not restore the site, the outage is on the server side. Contact your hosting provider directly — they have access to server logs, firewall settings, and SSL configurations that are outside Cloudflare's and Search Atlas's control. 5. Check Cloudflare's status page. Visit cloudflarestatus.com to rule out a platform-wide Cloudflare incident affecting your region. 6. Use a DNS propagation checker. Tools such as dnschecker.org and whatsmydns.net let you see how your nameserver changes have spread globally. Enter your domain name, select the NS (Nameserver) record type, and review the results by region. When all locations display Cloudflare's assigned nameservers (for example, xxx.ns.cloudflare.com), propagation is complete. If most locations show your Cloudflare nameservers but the site is still down, propagation is complete and the issue is configuration-related, not propagation-related. 🏗️ Does This Affect Search Atlas or Website Studio? Search Atlas and Website Studio (accessible from the left sidebar under Website Studio) operate independently of your domain's nameserver configuration. Any error messages or toast notifications you see inside the Search Atlas platform relate to platform-specific actions — such as API connections, content generation, or project settings — and are not indicators of your Cloudflare or DNS status. If you see an error toast inside Search Atlas while also experiencing site downtime, these are two separate issues. Do not assume one caused the other. Address your DNS and hosting issues directly with Cloudflare and your hosting provider, then separately troubleshoot any Search Atlas-specific errors. Once propagation is confirmed complete, go to Left sidebar → Website Studio and confirm that your custom domain is still correctly connected to your project. In some cases, a domain re-verification step may be required inside the platform following a nameserver change. 📋 Quick Reference: Normal vs. Not Normal - Normal: Site intermittently accessible for some visitors during the first 2–12 hours after switching nameservers. - Normal: Full propagation taking 24–48 hours on average, up to 72 hours in rare cases or isolated regions. - Normal: Different visitors seeing different versions of your site during propagation. - Not normal: Complete, uninterrupted downtime lasting beyond 72 hours after switching nameservers. - Not normal: Site still down after DNS propagation checkers confirm your Cloudflare nameservers are fully propagated worldwide. - Not normal: Cloudflare's dashboard displaying a warning or error on your domain zone. - Not normal: Domain failing to resolve even when tested from multiple networks or devices after the 72-hour window. 🚨 When to Escalate Reach out for support if any of the following apply after 72 hours have passed: - Your site remains completely inaccessible - Propagation checker tools still show old nameservers across all regions - Cloudflare's dashboard displays a warning or error on your domain - Your domain fails to resolve even when tested from multiple networks or devices 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.

🌐 Install Search Atlas on lovable.dev via Cloudflare

Overview Installing Search Atlas on a lovable.dev site with a custom Cloudflare domain connection is a known setup scenario that our team has assisted customers with directly. Because the specific steps depend on your project configuration and how your domain is routed through Cloudflare, the verified setup process requires guidance from our support team. What We Know About This Setup This type of installation involves connecting a custom domain managed through Cloudflare to a lovable.dev project, then ensuring the Search Atlas tracking script loads correctly. Common issues customers encounter include DNS misconfiguration, the tracking script failing to communicate with the site, and domain verification not completing as expected. What to Have Ready Before Contacting Support To get this resolved as quickly as possible, please gather the following information before reaching out: - Your lovable.dev project name or URL (for example, the default subdomain assigned to your project) - Your custom domain that you are connecting through Cloudflare - The exact error message you are seeing, if any (copy it in full) - The timestamp when you first encountered the issue - Whether you have already made any changes to your Cloudflare account for this domain (for example, added or edited any DNS records) - The name of your Search Atlas project associated with this site Having these details ready will allow our team to identify your configuration and walk you through the exact steps needed for 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.

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

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

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

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

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

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

🚀 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

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

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

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

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

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

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

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

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

🚀 Publish Website Studio Pages to WordPress via MetaSync

🗺️ Overview If Atlas Brain recommends that your new service pages live inside your domain (for example, yourdomain.com/services/page-name), you can publish them directly into your existing WordPress site using the MetaSync folder option in Website Studio. This method adds pages under a subfolder of your domain without replacing your homepage, removing your existing content, or moving your site to a subdomain. 📋 Before You Start Make sure the following are in place before publishing: - You have an active Website Studio project with at least one completed page. - Your WordPress site is connected to Search Atlas via MetaSync (the Search Atlas WordPress plugin must be installed and authenticated). - You have WordPress admin credentials available in case re-authentication is needed. - You have decided on the subfolder path where the pages will live (for example, /services/ or /locations/). 🛠️ How to Publish Pages Using the MetaSync Folder Option 1. Open Website Studio from the left-hand navigation inside Search Atlas. 2. Select the project that contains the page or pages you want to publish. 3. Click the Publish button in the top-right corner of the editor. 4. In the publishing modal, select MetaSync — WordPress (Folder) as your publish destination. This option publishes pages as posts or custom pages nested under a subfolder on your existing domain. 5. Choose the connected WordPress site from the dropdown. If your site does not appear, verify that the MetaSync plugin is installed and that the connection is active under Settings → Integrations. 6. Enter the subfolder path where the page should be published (for example, /services/roof-repair/). This determines the URL the page will live at on your domain. 7. Review the page title and URL slug, then click Publish to WordPress. 8. Once publishing is confirmed, visit the URL in a browser to verify the page is live and your existing homepage and other WordPress content are unaffected. ✅ What the MetaSync Folder Option Does (and Does Not Do) It is important to understand exactly how this publish method works so you can set the right expectations: - It adds pages inside your existing WordPress site under the subfolder path you specify — your homepage and existing pages remain untouched. - It does not replace your WordPress theme or layout for existing pages. Only the newly published Studio page uses the Website Studio design. - It does not require a subdomain. Pages are published directly under your root domain (for example, yourdomain.com/services/new-page). - It does not affect your WordPress navigation menus automatically. If you want the new page to appear in your menu, add it manually inside WordPress under Appearance → Menus. ⚠️ Common Issues and How to Fix Them - Published page redirects to the homepage: This is a known WordPress permalink conflict. Go to your WordPress dashboard, navigate to Settings → Permalinks, and click Save Changes (no changes needed — just saving flushes the rewrite rules). Then revisit the published URL. - WordPress site not appearing in the publish dropdown: The MetaSync plugin may have lost its authentication token. Go to Settings → Integrations → MetaSync in Search Atlas and reconnect your site. - Page published but not indexed: Check that the page is not set to noindex inside Website Studio's page settings, and that your WordPress site is not set to discourage search engines under Settings → Reading. - Subfolder path already in use by another WordPress page: Choose a unique slug that does not conflict with existing WordPress pages or posts. Duplicate slugs can cause one page to override the other. 💡 Tips for Best Results - Plan your subfolder structure before publishing multiple pages. A consistent structure (for example, /services/[city]/[service-name]) makes future management and internal linking easier. - After publishing, add an internal link from your WordPress homepage or relevant existing pages to the new Studio page to pass authority and improve crawlability. - Use the Preview option in Website Studio to review the final design before publishing to your live site. 💬 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 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 Website Studio Projects to WordPress via MetaSync

Overview Website Studio projects can be published directly to a self-hosted WordPress site using the MetaSync Plugin — a supported Search Atlas integration. This article explains what MetaSync is and how to get started. Because setup details vary by account and WordPress environment, the Search Atlas support team will provide you with the plugin file and guide you through the full connection and publishing process. What Is the MetaSync Plugin? MetaSync is a WordPress plugin that works with your Website Studio project and your WordPress installation. Once connected, it allows your published Website Studio project to appear on your WordPress domain without requiring manual file uploads or a separate static host. MetaSync is the recommended method when you want your Website Studio project to live on an existing WordPress domain. Before You Begin - You have an active Search Atlas account and at least one saved project in Website Studio. - You have WordPress installed with admin access. - You have the ability to install plugins on your WordPress site. Step 1 — Request the MetaSync Plugin from Support The MetaSync plugin file is provided directly by the Search Atlas support team. To request it, open the chat widget in your Search Atlas dashboard and ask a support agent for the MetaSync plugin. Have the following ready to speed up the process: - Your Search Atlas account email or project name - Your WordPress site URL - Your WordPress version (visible in your WordPress admin area) Step 2 — Install the MetaSync Plugin on WordPress Once you have received the plugin file from the support team, follow the installation instructions they provide alongside the file. Plugin installation steps can vary depending on your WordPress hosting environment, so follow the guidance given by the support agent for your specific setup. Step 3 — Connect MetaSync to Website Studio and Publish After installation, the Search Atlas support team will guide you through connecting MetaSync to your Search Atlas account and publishing your Website Studio project. Connection and publishing steps depend on your specific account and site configuration. When contacting support, have the following information ready: - Your Search Atlas project name - Your WordPress site URL - Any error messages you see (including exact wording and screenshots if possible) - The timestamp when you first encountered the issue Troubleshooting Common Issues If you encounter problems after attempting to publish — such as a white screen, MIME type errors, or a failed connection — note the exact error message displayed and contact the support team. Providing a screenshot of the error along with your project name and WordPress site URL will help the team resolve your issue as quickly as possible. If you need help at any stage of this process, reach out to our support team via the chat widget in your Search Atlas dashboard and we'll be happy to assist.