White Label: DNS & Custom Domains

🔧 Fix Whitelabel Custom Domain DNS

🔍 Why your whitelabel domain stopped working A whitelabel domain, such as seodashboard.webeagles.com.au, uses a DNS CNAME record to point to Search Atlas. Changing your website server does not usually update this record, but DNS settings may have been removed, replaced, or changed during the migration. The domain can also stop working when the CNAME points to an outdated destination, uses the wrong record type, or conflicts with another DNS record. ⚙️ Check the required DNS record 1. Open the whitelabel or custom-domain settings in Search Atlas. 2. Copy the current CNAME target shown in the platform. 3. Open your domain provider’s DNS management page. 4. Find the hostname used for your whitelabel domain, such as seodashboard. 5. Set its record type to CNAME. 6. Enter the exact target copied from Search Atlas. 7. Save the DNS change. Use a CNAME record, not an A record or an IP address. Do not add https:// to the target. If your DNS provider automatically adds the main domain, enter only the hostname required by that provider. 🛠️ Remove common DNS conflicts - Remove any existing A, AAAA, or conflicting CNAME record for the same hostname. - Make sure the CNAME is created for the subdomain, not the root domain, unless the platform specifically instructs otherwise. - Check that the hostname is spelled correctly and does not contain duplicate domain text. - If a proxy or CDN is enabled, temporarily disable proxying or set the record to DNS-only while the domain is verified. ⏳ Wait for DNS updates DNS changes can take time to appear across the internet. Wait several minutes, then retry verification in Search Atlas. In some cases, cached DNS records can take up to 24–48 hours to expire. ✅ If your website recently moved servers Your website’s A record and your Search Atlas whitelabel CNAME serve different purposes. Update the website records required by your new hosting provider, but keep the whitelabel subdomain’s CNAME pointing to the exact destination shown in Search Atlas. If the domain still fails after the CNAME is correct and DNS has updated, confirm that the domain is entered correctly in Search Atlas and that your hosting or security provider is not blocking the request. 💬 Get help with verification 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.

🛠️ Restore Whitelabel Domain DNS After Migration

💡 Why Your Whitelabel Domain Stopped Working When you move your website to a new server or hosting provider, your DNS zone is usually rebuilt from scratch. Records that were not carried over during the migration — including the CNAME that connects your whitelabel subdomain (for example, app.yourdomain.com) to Search Atlas — are often dropped or replaced with a record pointing at your new server. Once that link is gone, your whitelabel URL stops loading and SSL cannot renew. The good news: this is easy to fix, and your account data is unaffected. 📋 What You Will Need - Access to the DNS settings at your new hosting provider or domain registrar - Your Search Atlas login with access to Agency Hub - The whitelabel subdomain you originally connected (for example, app.yourdomain.com) 🔍 Step 1: Get the Correct CNAME Target 1. Log in to Search Atlas. 2. In the left sidebar, open More Features → Agency Hub → White Label Setup (or go directly to /agency-settings). 3. Find the domain setup section and copy the exact CNAME target shown there. Important: Always copy the target directly from the platform. Do not reuse a target from old emails, notes, or screenshots — targets can change over time, and the domain verifier will reject a mismatched target even when everything else is correct. ⚙️ Step 2: Re-create the DNS Record at Your New Host 1. Open the DNS or zone file editor at your new hosting provider. 2. Search for any existing record for your whitelabel subdomain (for example, the host app). Delete any conflicting A, AAAA, or CNAME records for that host — a subdomain cannot have both an A record and a CNAME at the same time. 3. Create a new record with these values: Type: CNAME, Host / Name: your subdomain (for example, app), Value / Target: the CNAME target you copied from White Label Setup, TTL: 3600 or lower. 4. Save the record. Do not point the subdomain at your new server's IP address with an A record. The whitelabel connection only works through the CNAME to Search Atlas. 🔄 Step 3: Wait for DNS Propagation DNS changes can take anywhere from a few minutes to 48 hours to spread across the internet. You can check progress with any public DNS lookup tool: your subdomain should resolve to the Search Atlas target, not to your new server. If it still shows your new server's IP, an old record is still active somewhere — see the troubleshooting section below. ✅ Step 4: Re-verify the Domain and SSL 1. Return to More Features → Agency Hub → White Label Setup. 2. Re-save or re-verify your whitelabel domain. 3. Confirm the status shows as active with a valid SSL certificate. If SSL will not activate, the CNAME has most likely not finished propagating yet. Wait an hour and verify again — the SSL certificate is provisioned automatically once DNS resolves correctly. No manual certificate installation is needed. 🧩 Common Issues After a Migration - Verifier rejects your CNAME: the target does not match what is shown in White Label Setup. Delete the record and re-add it using the exact value copied from the platform. - Domain loads your new website instead of Search Atlas: an old A record or a virtual host on the new server is capturing the subdomain. Remove the record from DNS, and check that the subdomain is not configured as a site on your new server. - Changes at the new host have no effect: your domain's nameservers may still point to the previous host. Confirm in your registrar settings that the nameservers match wherever you are actually editing DNS. - OTTO pixel stopped tracking: OTTO tags are tied to your whitelabel domain. If the domain changed or was re-issued during the migration, pixels installed on client sites can break. Keep your primary whitelabel domain stable, and if you genuinely need additional domain aliases, contact our team first so they can be configured in a way that will not interrupt tracking. - Client bookmarks or logins fail: if you renamed the subdomain during the migration, update any links you share with clients, embedded widgets, and lead capture forms that reference the old URL. 🚀 Tips to Prevent This Next Time - Before any future migration, export or screenshot your full DNS zone file so no records are lost. - Lower your TTL to 300 at least 24 hours before migrating so changes apply quickly. - After migrating, test the whitelabel URL early and re-verify the domain in White Label Setup. 💬 Still Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Whitelabel DNS Setup and OTTO Redeployment

🔍 Overview After upgrading your Search Atlas plan and configuring a whitelabel subdomain, you may see OTTO Not Deployed warnings on your projects and Access Forbidden errors when visiting your custom domain. This happens because a plan upgrade resets certain platform-level settings, and your DNS records or OTTO activation may need to be reapplied. Follow the steps below to resolve both issues. ⚙️ Step 1: Verify Your DNS Records Are Correctly Configured Before redeploying OTTO, confirm that your subdomain (for example, dashboard.mindshiftdigital.co) is pointing to Search Atlas correctly. Log in to your domain registrar or DNS provider and check that the following records exist: - Type: CNAME - Host / Name: your chosen subdomain prefix (e.g., dashboard) - Value / Points to: the CNAME target provided in your Search Atlas whitelabel settings - TTL: 3600 (or the lowest value your provider allows) If you have an existing A record for the same subdomain, remove it before adding the CNAME. Conflicting records are the most common cause of Access Forbidden errors. DNS changes can take up to 48 hours to fully propagate, but most providers update within 1–4 hours. 🌐 Step 2: Confirm Your Whitelabel Settings Inside Search Atlas Once DNS is pointing correctly, verify your whitelabel configuration inside the platform: 1. Click the apps-grid icon in the header and select More Features. 2. Open Agency Hub (Set up your Agency's White Label). 3. Confirm your custom subdomain is entered exactly as configured in your DNS (e.g., dashboard.mindshiftdigital.co). 4. If the field is blank or shows a previous domain, re-enter your subdomain and click Save. 5. Wait a few minutes, then visit your subdomain in a new browser tab to confirm the Access Forbidden error is resolved. If you see a security certificate warning instead of an Access Forbidden error, SSL provisioning is still in progress. Wait up to 30 minutes and refresh. 🚀 Step 3: Redeploy OTTO on Each Affected Project A plan upgrade can deactivate OTTO across your projects. You will need to redeploy it manually for each project showing OTTO Not Deployed. Here is how: 1. Go to OTTO SEO in the left sidebar and open SEO Automation (or navigate to /seo-automation-v3). 2. Select the first project showing OTTO Not Deployed. 3. Click the OTTO tab or the Deploy OTTO button on the project dashboard. 4. Follow the on-screen prompts to connect OTTO to the project's website. If the site uses WordPress, ensure the Search Atlas plugin is installed and the API key is current. 5. Once deployment completes, the status will change to OTTO Active. 6. Repeat these steps for every additional project that shows the Not Deployed status. Important: If your OTTO pixel was previously installed via a third-party tag manager (such as Google Tag Manager), verify that the pixel snippet in your tag manager still matches the one shown in your current OTTO settings. Plan upgrades can generate a new pixel ID that must be re-pasted into your tag manager container and published. 🔎 Step 4: Clear Cache and Test After completing DNS verification and OTTO redeployment, take the following steps to confirm everything is working: - Clear your browser cache or open an incognito window before testing your whitelabel subdomain. - If your site uses a caching plugin (e.g., WP Rocket, W3 Total Cache), purge the cache from the plugin dashboard. - Visit your whitelabel subdomain and confirm the Search Atlas interface loads without errors. - Return to OTTO SEO in the left sidebar and open All Sites (SEO Automation) to confirm all projects display OTTO Active. ⚠️ Common Issues and Quick Fixes - Access Forbidden after DNS update: Double-check there are no duplicate or conflicting A records for the same subdomain at your registrar. - OTTO Not Deployed reappears after saving: Ensure your WordPress plugin is updated to the latest version and the API key in the plugin settings matches your Search Atlas account. - SSL certificate error on subdomain: Wait up to 30 minutes for auto-provisioning. If the error persists beyond an hour, the CNAME record may not be fully propagated yet. - Only one project redeployed but others still show Not Deployed: OTTO must be redeployed per project — there is no bulk-deploy option. Repeat Step 3 for each project individually. 💬 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.

🌐 Reconfigure White Label DNS After Nameserver Migration

🔍 Overview When you migrate your nameservers from a registrar like GoDaddy to Cloudflare, all existing DNS records are not automatically carried over. This causes both your main website and your Search Atlas White Label dashboard to go offline until the correct DNS records are re-created. This article explains what information to have ready so our support team can provide you with the exact DNS values for your account. ⚠️ Why Both Systems Go Down Your White Label dashboard runs on a subdomain of your domain (for example, reports.yourdomain.com). When you switch nameservers, Cloudflare starts serving DNS for your domain from scratch. Unless you manually add the required records in Cloudflare, neither your website nor your White Label dashboard will resolve correctly. 📋 What You Will Need Before Starting - Access to your Cloudflare account and the DNS settings for your domain - Your Search Atlas account with White Label already configured - The subdomain you chose for your White Label dashboard (for example, reports.yourdomain.com) - Your website's original hosting IP address (check your old registrar or hosting provider if unsure) 🛠️ Step 1 — Restore Your Website's DNS Records in Cloudflare You will need to re-add the DNS records for your root domain and www subdomain in Cloudflare, pointing them to your website's hosting IP address. Use the IP address provided by your hosting provider — not a Search Atlas IP. Refer to your Cloudflare account's DNS management section to add these records. 🏷️ Step 2 — Add the Search Atlas White Label DNS Record Your White Label dashboard must point to Search Atlas via a CNAME record on your chosen subdomain (a root domain cannot be used). The recommended settings for your White Label subdomain are provided by Search Atlas support. To get the exact DNS values for your account, contact our support team and have the following ready: - Your domain name - The subdomain prefix you chose for your White Label dashboard (for example, reports) - Confirmation that your nameservers have been successfully migrated to Cloudflare ⏳ Step 3 — Allow Time for DNS Propagation After adding or updating your DNS records, changes can take anywhere from a few minutes to 48 hours to fully propagate across the internet. During this time your website or White Label dashboard may intermittently appear offline or show SSL errors. This is normal. You can use a tool such as whatsmydns.net to monitor propagation status for your domain. ✅ Summary Nameserver migrations require you to manually re-create all DNS records in Cloudflare. Your website records should point to your hosting provider's IP, and your White Label subdomain record must point to the IP address that Search Atlas support provides for your specific account. Do not attempt to guess or copy a generic IP for the White Label record, as incorrect values will prevent your dashboard from loading even after propagation completes. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🌐 Fix White-Label Domain DNS Configuration Issues

🔍 Overview White-labeling allows you to serve the Search Atlas dashboard under your own custom domain (for example, dashboard.youragency.com). If your white-label URL is returning an error page instead of loading the dashboard, the most common cause is an incomplete or incorrect DNS configuration. This article walks you through the correct setup and how to troubleshoot the most frequent issues. ⚙️ Prerequisites - Access to your domain registrar or DNS provider (e.g., Cloudflare, GoDaddy, Namecheap). - Admin access to your Search Atlas account with Agency settings enabled. - The subdomain you want to use (e.g., dashboard.youragency.com). 🛠️ How to Configure Your White-Label Domain 1. Log in to Search Atlas and go to the apps-grid icon in the header → More Features → Agency Hub (Agency Settings). 2. Locate the White-Label Domain field and enter your chosen subdomain (e.g., dashboard.dotmappers.in). 3. Save your settings. Search Atlas will display the DNS record values you need to add at your domain registrar. 4. Log in to your DNS provider and create a new CNAME record with the following details: - Host / Name: The subdomain prefix only (e.g., dashboard). - Points to / Value: The CNAME target provided by Search Atlas (copy it exactly). - TTL: 3600 (1 hour) or your provider's default. 5. Save the DNS record at your provider. 6. Wait for DNS propagation — this typically takes 15 minutes to 48 hours depending on your provider and TTL settings. ✅ How to Verify Your DNS Is Propagating Before assuming something is broken, confirm that your DNS record has propagated correctly: - Visit dnschecker.org or whatsmydns.net and enter your full subdomain (e.g., dashboard.dotmappers.in). Select CNAME as the record type. You should see the Search Atlas CNAME target resolving across multiple locations. - If the record is not yet visible, wait and check again in 30–60 minutes. - If the record shows a different value, update it in your DNS provider to match the value provided in Search Atlas Agency Settings exactly. 🚨 Common Errors and Fixes - Error page / domain not loading: DNS has not yet propagated or the CNAME record is missing. Double-check that you created a CNAME (not an A record) and that the target value matches exactly what Search Atlas provided. - SSL / HTTPS warning: SSL certificates are provisioned automatically by Search Atlas after the CNAME propagates. If you see an SSL error shortly after setup, wait up to 30 minutes for the certificate to be issued. Do not add your own SSL certificate. - Subdomain resolves but shows a blank or broken page: Confirm the full subdomain entered in Agency Settings matches the subdomain you created in your DNS (including any hyphens, dots, or capitalisation). - Cloudflare users — proxy status: If your domain is managed by Cloudflare, make sure the CNAME record is set to DNS only (grey cloud icon), not Proxied (orange cloud). Proxying can interfere with SSL provisioning. - Previous A record conflict: If an A record already exists for the same subdomain, delete it before adding the CNAME record. Two conflicting records will prevent the domain from resolving correctly. 📋 DNS Configuration Checklist - Record type is CNAME (not A, AAAA, or TXT). - Host/Name value is the subdomain prefix only (e.g., dashboard, not the full domain). - CNAME target matches the value shown in Search Atlas Agency Settings exactly. - No conflicting A record exists for the same subdomain. - Cloudflare proxy is disabled (grey cloud) if applicable. - Sufficient time has passed for DNS propagation (up to 48 hours). - The full subdomain saved in Agency Settings matches what you configured in DNS. 💡 Tips for Faster Troubleshooting If you need to speed up testing during setup, temporarily lower your TTL to 300 seconds (5 minutes) before making DNS changes. This reduces the time it takes for updates to propagate. Once everything is working, you can raise the TTL back to 3600. Also, try accessing your white-label URL in an incognito or private browser window to rule out cached DNS responses on your local machine. 🙋 Still Need Help? If you have followed all the steps above and your white-label domain is still not loading correctly, If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ How to Report Bugs: Whitelabel vs Standard Domain

🔍 Understanding Your Two Access Points Search Atlas can be accessed in two ways depending on your account type: - Standard domain: You log in directly at the official Search Atlas URL (e.g., app.searchatlas.com). - Whitelabel domain: You log in through a custom-branded URL set up by your agency or reseller (e.g., app.youragency.com). Both access points connect to the same underlying platform, but knowing which one you were using when the bug occurred is critical for our team to reproduce and resolve the issue quickly. ⚠️ Why This Matters for Bug Reports Bugs can behave differently depending on the login method and domain used. For example, a layout issue or broken feature may appear only on a whitelabel domain due to custom branding settings, or only on the standard domain due to account-level configurations. Reporting the wrong URL can delay diagnosis and resolution. ✅ How to Identify Which Domain You Are Using Before submitting a bug report, check the following: 1. Look at your browser's address bar while you are logged in. 2. If the URL contains searchatlas.com, you are on the standard domain. 3. If the URL contains a custom domain (your agency or company name), you are on a whitelabel domain. 4. Take note of the exact URL — copy it directly from the address bar. 📋 What to Include in Your Bug Report To help our team investigate efficiently, always include the following details when reporting a bug: - The full URL where the bug occurred (copied directly from your browser's address bar). - The login method used: standard Search Atlas domain or whitelabel domain. - Your account email address associated with the affected login. - Steps to reproduce the bug: a numbered list of exactly what you did before the issue appeared. - What you expected to happen versus what actually happened. - Screenshots or screen recordings if possible — these significantly speed up resolution. - Browser and device information: browser name, version, and whether you are on desktop or mobile. 🚀 How to Submit Your Bug Report Follow these steps to submit your report correctly: 1. Log in to the platform using the same domain where the bug occurred — either the standard Search Atlas URL or your whitelabel URL. 2. Reproduce the bug if possible so you can capture the exact URL and any error messages. 3. Open the chat widget in the bottom-right corner of the platform. 4. Type human teammate to be connected with a member of our team. 5. Share all the details listed in the section above. 💡 Quick Tips to Avoid Confusion - Always report bugs from the same domain where you experienced the issue. Do not switch to the other domain before contacting support. - If you have access to both a whitelabel panel and the standard Search Atlas domain, test whether the bug appears on both — this helps narrow down the root cause. - If you are a reseller reporting on behalf of a client, confirm which URL your client was using at the time of the issue before reaching out. 🙋 Need Further Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🌐 Configuring Cloudflare DNS for Search Atlas Whitelabel

🔍 Overview If your whitelabel analyzer widget is showing missing logos or test leads after a recent platform update, the root cause is almost always an incomplete or misconfigured DNS setup in Cloudflare. This article walks you through the general steps to create the correct CNAME record, disable Cloudflare's Proxied mode, and verify that everything is propagating correctly. ⚙️ What You Will Need - Access to your Cloudflare account with permission to edit DNS records - Your whitelabel domain (the domain you use for your branded Search Atlas dashboard) - Your Search Atlas account with whitelabel already enabled - The specific subdomain name and CNAME target value provided to you by the Search Atlas support team 📋 Step 1: Create the CNAME Record in Cloudflare 1. Log in to your Cloudflare account and select the domain you are using for your whitelabel dashboard. 2. Navigate to DNS in the left-hand sidebar, then click Records. 3. Click Add record. 4. Set the record Type to CNAME. 5. In the Name field, enter the subdomain name provided to you by the Search Atlas support team. 6. In the Target field, enter the CNAME target value provided to you by the Search Atlas support team. 7. Leave the TTL set to Auto. 8. Do not save yet — continue to Step 2 before confirming. 🚫 Step 2: Disable Cloudflare Proxied Mode This is the most commonly missed step. When the Proxied setting is enabled (shown as an orange cloud icon), Cloudflare intercepts traffic and routes it through its own network. This breaks the connection between your whitelabel subdomain and the Search Atlas platform. 1. In the same Add record panel, locate the Proxy status toggle. 2. Click the toggle so the icon changes from an orange cloud (Proxied) to a grey cloud (DNS only). 3. Confirm the status reads DNS only. 4. Click Save to create the record. If you already saved the record with Proxied mode enabled, click the Edit icon next to the existing CNAME record, switch the proxy status to DNS only, and save again. ⏱️ Step 3: Wait for DNS Propagation After saving the record, DNS changes need time to propagate across the internet. Allow some time for propagation to complete before testing your whitelabel setup. If you are unsure whether propagation has completed, contact our support team for assistance. 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.

🌐 White Label Subdomain DNS and CNAME Setup

🗺️ Overview Setting up a white label subdomain lets you present Search Atlas reports and dashboards under your own brand. This requires adding specific DNS records to your domain. One of the most common points of confusion is understanding which record types are needed and how to configure them correctly with your DNS provider. If you are running into issues with your white label subdomain not resolving, our support team can review your specific configuration and guide you through the correct setup. 📋 What DNS Records Do You Need? White label subdomain setup involves adding DNS records to your domain. The exact record type and target value required for your account will be confirmed by the Search Atlas support team, as configuration details vary by account. Before reaching out, it helps to have the following information ready: - The subdomain you intend to use (e.g., reports.youragency.com) - Your DNS provider (e.g., Cloudflare, GoDaddy, Namecheap, Route 53) - Any error messages you are seeing in your DNS provider's control panel or in the Search Atlas platform - A screenshot or description of any existing records on that subdomain ⚙️ General Steps to Add a DNS Record 1. Log in to your DNS provider's control panel. 2. Navigate to the DNS settings for your domain. 3. Add the record type and value as instructed by the Search Atlas support team. 4. Save the record and allow time for DNS propagation. ☁️ Common Issues with Cloudflare If you are using Cloudflare as your DNS provider and are encountering errors when saving or activating your white label subdomain record, open the chat widget in the bottom-right corner of the platform and type human teammate to reach our support team. Provide the exact error message displayed in Cloudflare and the current state of your DNS records so our team can advise on the correct configuration for your setup. 🔍 What to Have Ready When You Contact Support - Your Search Atlas account email or project name - The subdomain you are trying to configure - Your DNS provider name - The exact error message you are seeing (copy and paste it if possible) - A description or screenshot of your current DNS records for that subdomain If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix White-Label DNS and Team Invitation Issues

🔍 Overview White-label setup in Search Atlas lets you present the platform under your own brand and custom domain. When DNS is misconfigured, team member invitation links can break or fail to load. This article walks you through the correct DNS setup, how to connect an alternative host, and how to fix invitation link issues. ⚙️ How White-Label DNS Works When you enable white-label, Search Atlas maps your custom domain (for example, reports.yourdomain.com) to the Search Atlas platform. For this to work, your domain's DNS records must point to the correct destination. If these records are missing, incorrect, or haven't propagated yet, any links generated under your white-label domain — including team member invitations — will not resolve properly. 🚀 Step 1: Configure Your DNS Records Log in to your domain registrar or DNS provider (for example, Cloudflare, GoDaddy, or Namecheap) and add the following record: - Record type: CNAME - Host / Name: The subdomain you want to use (for example, reports) - Points to / Value: The target address provided in your Search Atlas white-label settings - TTL: 3600 (or Auto) Save the record. DNS propagation typically takes between 15 minutes and 48 hours depending on your provider and previous TTL values. 🔗 Step 2: Enter Your Custom Domain in Search Atlas 1. Log in to Search Atlas and go to your Account Settings. 2. Navigate to the White Label section. 3. Enter your full custom domain in the Custom Domain field (for example, reports.yourdomain.com). 4. Click Save or Verify Domain. 5. Wait for the platform to confirm that the domain has been verified successfully. If verification fails, double-check that your CNAME record matches the target address shown on screen exactly. 🌐 Step 3: Connect an Alternative Host If you need to use a different hosting provider or DNS manager than your primary domain registrar, follow these steps: 1. Log in to your alternative DNS provider and create a new CNAME record using the same values described in Step 1. 2. If your domain is currently managed by another provider, update your domain's nameservers to point to the new host, or add the CNAME record directly at the registrar level without changing nameservers (this is usually the simpler option). 3. Return to Search Atlas white-label settings and re-enter your custom domain, then click Verify Domain again once propagation is complete. Tip: Use a free tool like dnschecker.org to confirm your CNAME record has propagated across global DNS servers before retrying verification. 📧 Step 4: Resend Team Member Invitations Once your domain is verified and DNS has fully propagated, any previously sent invitation links that used the broken domain will no longer work. You must resend invitations so they are generated under the now-active white-label domain. To do this: 1. Go to Account Settings and open the Team Members section. 2. Locate the team member whose invitation did not work. 3. Click Resend Invitation next to their name. 4. Ask the team member to check their inbox (and spam folder) for the new link and follow the instructions to accept the invitation. ⚠️ Common Issues and Fixes - Invitation link shows a "site can't be reached" error: DNS has not propagated yet, or the CNAME record is missing. Verify the record at your DNS provider and wait up to 48 hours. - Domain verification fails in Search Atlas: Ensure there are no extra spaces in the CNAME value and that no conflicting A records exist for the same subdomain. - Team member receives the invitation but cannot log in: The domain may be verified but SSL is still being provisioned. Wait 10–15 minutes and try again. - Using Cloudflare: Set the CNAME record proxy status to DNS only (grey cloud icon) rather than proxied (orange cloud). Proxying can interfere with SSL certificate provisioning on Search Atlas's end. 💡 Tips for a Smooth Setup - Use a dedicated subdomain (for example, seo.youragency.com) rather than your root domain to avoid conflicts with your main website. - Complete DNS setup and domain verification before inviting team members to avoid broken links. - If you manage multiple client workspaces, each workspace can have its own white-label domain — repeat this process for each one. 🙋 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.

🌐 Whitelabel DNS Configuration for Webflow Sites

Overview When onboarding a whitelabel domain hosted on Webflow, you may need to add specific DNS records so Search Atlas can verify ownership and route traffic correctly. Misconfiguring or missing these records is a common cause of the "domain is unreachable" error during onboarding. Because the exact DNS record types, values, and navigation steps required depend on your specific whitelabel configuration, our support team will need to confirm the correct records for your setup. The steps below explain what to have ready so we can resolve this quickly. Before You Contact Support To help our team assist you as efficiently as possible, please gather the following information: - The whitelabel subdomain you are trying to configure (for example, app.yourdomain.com). - Confirmation of whether your domain's DNS is managed directly through Webflow or through an external registrar (such as GoDaddy, Namecheap, or Cloudflare). You can check this by running a WHOIS lookup on your domain and reviewing the Name Servers field. - A description of the exact error message you are seeing (for example, "domain is unreachable") and at what point in the onboarding flow it appears. - Any DNS records you have already added, including their type, name/host value, and destination value. What to Expect Once you contact our team, a support agent will review your whitelabel configuration and provide you with the exact DNS record types and values you need to enter in your DNS provider's control panel. DNS changes can take time to propagate globally — typically anywhere from a few minutes to 48 hours — so please allow time after making changes before retesting. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Report Widget Sizing and Whitelabel DNS Issues

Overview Two common issues arise when building and sharing reports in Search Atlas: widgets appearing at different sizes across report sections, and whitelabel report links failing to load. This article explains what causes each issue and what to have ready when contacting support for assistance. How Report Widget Sizing Works Every widget you add to a report section is independently sized. This means a widget placed in one section will not automatically inherit the dimensions of a similar widget in another section — they are treated as separate elements. Because sizing is managed per widget, inconsistencies can appear across sections when widgets are added at different times or in different configurations. Troubleshooting Report Widget Sizing Inconsistencies If your widgets appear at inconsistent sizes across report sections, this is a known configuration challenge in report layouts. To get help resolving it, please have the following ready when you contact our support team: - The name of the report affected - Which sections contain the inconsistently sized widgets - A screenshot or screen recording showing the size difference between sections Our team can review your report layout and advise on the correct steps to match widget sizing across your sections. How Whitelabel Report Links Work When you enable whitelabeling, Search Atlas generates a custom-branded URL for your client reports. This URL relies on a DNS record that must be added to your domain registrar or DNS provider. Until the DNS record is correctly configured and fully propagated, the whitelabel link will not load. Troubleshooting a Whitelabel Report Link Not Working If your whitelabel report link is not loading, the issue is typically related to DNS configuration or propagation. To get help resolving it, please have the following ready when you contact our support team: - The whitelabel domain or subdomain you configured - The exact error message or behavior you see when visiting the link - Confirmation of whether you have added the required DNS record at your domain registrar - Approximately when you made the DNS change Our team can verify your DNS configuration details and confirm whether any additional steps are needed on the Search Atlas side. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🌐 Fix Whitelabel DNS Errors on Webflow

🔍 Overview When setting up your Search Atlas whitelabel on a Webflow site, you may encounter errors such as "whitelabel error" or "domain is unreachable". These messages almost always point to a DNS misconfiguration. This guide walks you through the exact steps to configure your DNS records correctly in Webflow and get your whitelabel up and running. ⚠️ Common Causes of These Errors - The required CNAME record has not been added to your Webflow domain settings. - The CNAME record was added incorrectly (wrong host name or target value). - DNS changes have not yet propagated (this can take up to 48 hours). - The custom domain has not been verified or published inside Webflow. 🛠️ Step-by-Step: Configure DNS in Webflow 1. Log in to Search Atlas and navigate to More Features → Agency Hub (Agency Hub / White Label settings). Copy the CNAME target value provided — you will need this in the next steps. 2. Log in to your Webflow account and open the project you want to connect. 3. Click the Site Settings icon (gear icon) for your project, then go to the Publishing tab. 4. Under Custom Domains, ensure your custom domain is already added. If not, enter your domain and click Add. 5. Webflow will display the DNS records you need to set up. You will need to add a CNAME record through your domain registrar (for example, GoDaddy, Namecheap, Cloudflare, or Google Domains) — Webflow does not manage DNS records directly unless you use Webflow's own hosting with a connected registrar. 6. Go to your domain registrar's DNS management panel and add a new record with the following details: - Type: CNAME - Host / Name: The subdomain you are whitelabeling (for example, app or dashboard) - Target / Value: The CNAME target copied from your Search Atlas whitelabel settings - TTL: 3600 (or the default value your registrar recommends) 7. Save the record in your registrar's DNS panel. 8. Return to Webflow Site Settings → Publishing and click Publish to apply the latest settings. 9. Back in Search Atlas, go to More Features → Agency Hub (Agency Hub / White Label settings) and click Verify Domain (or the equivalent button shown). If DNS has propagated, the domain status will update to active. ⏱️ Waiting for DNS Propagation After adding or updating a DNS record, changes can take anywhere from a few minutes to 48 hours to propagate globally. During this window, you may still see the "domain is unreachable" error — this is normal. To check propagation status, use a free tool such as whatsmydns.net and search for your subdomain to see whether the CNAME record is resolving correctly worldwide. ✅ How to Confirm Everything Is Working - Your CNAME record appears correctly in your registrar's DNS panel. - A propagation checker confirms the subdomain resolves to the correct target. - The domain status in Search Atlas Whitelabel settings shows as Active or Verified. - Visiting your whitelabel URL in a browser loads the platform without any error messages. 🔧 Troubleshooting Tips - Double-check for typos in both the host name and the CNAME target value — even a single extra character will cause an error. - Remove any conflicting A records that point to the same subdomain, as these can override your CNAME. - If you use Cloudflare as your DNS provider, make sure the CNAME record is set to DNS only (grey cloud), not proxied (orange cloud), during initial setup. - Clear your browser cache or test in an incognito window to rule out locally cached errors. - If you recently changed your DNS records, allow the full 48-hour propagation window before concluding there is an issue. 💬 Still Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🏷️ WordPress Whitelabel Subdomain Setup and Client Access

🗺️ Overview Search Atlas's whitelabel feature lets you host the platform under your own subdomain (for example, seo.yourdomain.com) so clients see your branding instead of Search Atlas. This article walks you through the full setup process, explains how client logins work, and covers the most common reasons login stops working after initial configuration. ✅ Before You Begin Confirm the following before setting up your whitelabel subdomain: - You have admin access to your domain's DNS settings (via your domain registrar or hosting panel). - You have a WordPress site where you can install or manage plugins. - Your Search Atlas plan includes whitelabel functionality. - You have admin access inside the Search Atlas platform. ⚙️ Step 1 — Create a Subdomain in Your Hosting Panel 1. Log in to your web hosting control panel (cPanel, Plesk, or your host's dashboard). 2. Navigate to the Subdomains or Domains section. 3. Create a new subdomain, for example seo.webdesignsurrey.net. 4. Note the subdomain's document root folder — you will need this in Step 3. 🌐 Step 2 — Point the Subdomain DNS to Search Atlas 1. Open your domain registrar or DNS management panel. 2. Add a new CNAME record with the following values: - Host / Name: seo (or the subdomain prefix you chose) - Points to / Value: the CNAME target provided inside Search Atlas (see Step 3 below) - TTL: 3600 (or Auto) 3. Save the record. DNS propagation can take up to 48 hours, but usually completes within 1–4 hours. 🔑 Step 3 — Configure Whitelabel Inside Search Atlas 1. Log in to Search Atlas and go to the header apps-grid icon → More Features → Agency Hub → White Label Setup (Logo page). 2. Enter your full subdomain (e.g., seo.webdesignsurrey.net) in the Custom Domain field. 3. Copy the CNAME target value shown on this page — this is what you enter in your DNS record in Step 2. 4. Upload your agency logo, set brand colours, and configure any other branding options on this page. 5. Click Continue. Search Atlas will attempt to verify the DNS record. Wait for the status to show Verified before proceeding. Important: If the status does not change to Verified within 48 hours, double-check that the CNAME record is saved correctly and that no conflicting A record exists for the same subdomain host. 👤 Step 4 — Create Client Accounts and Grant Access 1. Inside Search Atlas, go to Settings → Team Members (or your agency's client management section). 2. Click Invite Client and enter the client's email address. 3. Assign the relevant projects or reports to that client account. 4. The client will receive an invitation email with a link to set their password and log in via your whitelabel subdomain. Clients access their progress data through Reports. Inside the platform navigate to the left sidebar → Reports (URL: /report-builder/projects-list). Only the projects you have shared with a client will be visible when they log in. 🔧 Troubleshooting — Can't Log In After Setup If you or a client cannot log in to the whitelabel subdomain, work through the checks below in order. - DNS not fully propagated: Use a tool such as dnschecker.org to confirm the CNAME record is resolving worldwide. If it is still propagating, wait and retry. - SSL certificate not issued: Search Atlas automatically provisions an SSL certificate once DNS is verified. If the subdomain shows a browser security warning, the certificate may still be generating — this can take up to 1 hour after DNS verification. Do not attempt to install a separate SSL certificate, as this will conflict. - CNAME record overridden by an A record: If an A record exists for the same subdomain host in your DNS, it will take priority over the CNAME. Delete any conflicting A record, then re-verify inside Search Atlas. - Whitelabel domain not saved as Verified in Search Atlas: Return to the header apps-grid icon → More Features → Agency Hub → White Label Setup (Logo page) and confirm the domain status shows Verified. If it shows Pending or Error, re-enter the subdomain and re-copy the CNAME target to your DNS panel. - Client using the wrong login URL: Clients must log in at your whitelabel subdomain (e.g., https://seo.webdesignsurrey.net), not at app.searchatlas.com. Resend the invitation link or share the correct URL directly. - Client invitation not accepted: If the client never clicked the invitation email link, their account is not activated. Go to Settings → Team Members, find the client, and resend the invitation. - Password reset required: If a client's login was working and then stopped, ask them to use the Forgot Password link on the whitelabel login page to reset their credentials. - Browser cache or cookies: Ask the client to try logging in using a private/incognito window. If that works, they should clear their browser cache and cookies for the subdomain. 👁️ What Clients Can See Once logged in through your whitelabel subdomain, clients will see only the reports and projects you have shared with them. They will not see Search Atlas branding, other clients' data, or any account billing information. To share additional reports, go to the left sidebar → Reports, open the relevant project, and use the share or assign option to add the client. 💬 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.

🔗 How to Create and Verify a CNAME Record for Search Atlas White Label

When setting up Search Atlas White Label, you are required to create a CNAME record in your domain’s DNS settings. This step connects your custom subdomain (for example, seo.yourdomain.com) to Search Atlas so the platform can load correctly under your brand. If the CNAME is missing, incorrect, or not fully propagated, verification may fail, and the “Verify Domain” button will stay disabled until a subdomain value is entered and the record resolves correctly. 🧠 What Is a CNAME Record? A CNAME (Canonical Name) record is a DNS setting that makes one domain act as an alias of another domain. In simple terms, a CNAME tells the internet: “When someone visits this subdomain, send them to that service instead.” Instead of pointing to an IP address, a CNAME always points to another domain name. Example: seo.yourdomain.com points to whitelabel.dns.searchatlas.com. When someone visits seo.yourdomain.com, DNS forwards the request to Search Atlas behind the scenes. 🎯 Why Search Atlas Requires a CNAME Search Atlas uses a CNAME for White Label setups because it allows your platform to load under your own branded subdomain, it avoids exposing Search Atlas system domains to your clients, and it lets Search Atlas manage infrastructure changes without you updating IPs. This is a standard and widely used approach for SaaS white-label solutions. 📍 Official CNAME Target Used by Search Atlas For White Label configuration, Search Atlas provides the following CNAME destination: whitelabel.dns.searchatlas.com. Your DNS record must point your chosen subdomain to this exact value. 🛠️ Step-by-Step: How to Create the CNAME Record 1. Open your DNS settings. Log in to the platform where your domain’s DNS is managed, this could be your domain registrar or a DNS provider like Cloudflare. Look for DNS, Manage DNS, or DNS Records. 2. Add a new DNS record. Click Add record or Add DNS record, then create a new record with these values: Type = CNAME, Name/Host = your subdomain (e.g. seo), Target/Value = whitelabel.dns.searchatlas.com, TTL = Auto or Default. The example result is seo.yourdomain.com pointing to whitelabel.dns.searchatlas.com. 3. Make sure the subdomain is exclusive. The subdomain you use must not be used by any other service, it should be dedicated only to Search Atlas White Label. If another record already exists for that subdomain, remove it before adding the CNAME. 4. Save changes and wait for DNS propagation. Once saved, DNS updates may take time to propagate, commonly 1 to 5 minutes with Cloudflare, or up to 24 to 48 hours with other providers. During this period, verification may not complete immediately, this is expected behavior. ✅ How to Verify Your CNAME You can confirm your CNAME is working using a DNS lookup tool to check that seo.yourdomain.com resolves to whitelabel.dns.searchatlas.com, or by opening your subdomain in a browser, if DNS is active, it should no longer behave like an unconfigured domain. ⚠️ Common Errors and How to Fix Them If the “Verify Domain” button stays disabled or verification fails, this usually means the CNAME record does not exist yet, the target value is incorrect, DNS propagation is still in progress, or the subdomain is being used by another service. To fix it, confirm the target is exactly whitelabel.dns.searchatlas.com, make sure there is only one record for that subdomain, and wait up to 48 hours before trying verification again. 🧠 Important Things to Know - A CNAME always points to a domain, never to an IP - A CNAME is usually used for subdomains, not the root domain - DNS propagation delays are expected and normal - No additional configuration is needed once the CNAME is correct 🧩 Quick Summary 1. Search Atlas White Label requires a CNAME record 2. Your subdomain must point to whitelabel.dns.searchatlas.com 3. The subdomain must be exclusive 4. DNS changes can take time to propagate 5. Once active, verification should complete successfully Setting up a CNAME record is a standard and reliable way to connect your branded subdomain with Search Atlas White Label. Once the record is correctly configured and DNS propagation has completed, your platform will load seamlessly under your own domain, without exposing Search Atlas system URLs. If verification doesn’t complete immediately, don’t worry, DNS changes can take time to propagate. Double-check the record details, ensure the subdomain is exclusive, and try again after propagation finishes. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🏷️ WordPress Whitelabel Subdomain Setup Guide

🌐 What Is the Whitelabel Subdomain Feature? The whitelabel subdomain feature lets you present Search Atlas reports and dashboards under your own brand. Instead of sharing a Search Atlas URL, your clients visit a custom subdomain (for example, seo.youragency.com) and see your logo, your colours, and no Search Atlas branding. This is ideal for agencies that want a seamless, professional client experience. 📋 Before You Begin Make sure you have the following ready before starting the setup: - Access to your domain registrar or DNS management panel (e.g. Cloudflare, GoDaddy, Namecheap) - A subdomain you want to use (e.g. seo.webdesignsurrey.net) - Admin access to your Search Atlas account - Your whitelabel branding assets (logo, brand colours) ⚙️ Step 1 — Configure Your DNS Record The first step is pointing your subdomain to Search Atlas so the platform knows to serve your whitelabel portal at that address. 1. Log in to your domain registrar or DNS management panel. 2. Navigate to the DNS settings for your domain. 3. Create a new CNAME record with the following values: - Host / Name: your chosen subdomain prefix (e.g. seo) - Value / Points to: the Search Atlas whitelabel target provided in your account settings - TTL: 3600 (or Auto) 4. Save the record. DNS propagation can take up to 48 hours, though it often completes within a few hours. Do not attempt to log in to the subdomain until DNS has fully propagated — this is the most common reason customers find they cannot access the portal after setup. 🛠️ Step 2 — Add Your Subdomain in Search Atlas Once your DNS record is live, register the subdomain inside Search Atlas: 1. Log in to your Search Atlas account. 2. Click the apps-grid icon in the header, then go to More Features → Agency Hub (Set up your Agency's White Label). 3. Locate the Custom Domain field and enter your full subdomain URL (e.g. https://seo.webdesignsurrey.net). 4. Click Verify Domain. Search Atlas will check that your DNS record is pointing correctly. 5. Once verified, a green confirmation message will appear. If verification fails, wait another hour for DNS propagation and try again. 🎨 Step 3 — Configure Your Branding After your domain is verified, personalise the portal so clients see your brand: - Logo: Upload your agency logo (PNG or SVG recommended, minimum 200px wide). - Brand colours: Set your primary and accent colours using hex codes. - Agency name: Enter the name that will appear in the portal header and email notifications. - Favicon: Upload a small icon (32×32 px) to appear in browser tabs. Click Continue after updating each section. Preview the portal by visiting your subdomain in an incognito browser window. 👤 Step 4 — Grant Clients Access to Their Data Clients need their own login credentials to view their project data through your whitelabel portal. Follow these steps for each client: 1. In Search Atlas, go to Account Menu (avatar) → Settings → Team Members. 2. Click Invite Client and enter the client's email address. 3. Assign the relevant projects you want the client to see. 4. Set their permission level to Client View (read-only access — they cannot edit settings or see other clients' data). 5. Click Send Invitation. The client receives an email with a link to set their password. 6. Instruct the client to always log in via your custom subdomain (e.g. https://seo.webdesignsurrey.net), not via searchatlas.com. Clients logging in through your subdomain will only ever see your branding and their assigned projects. Search Atlas branding is completely hidden. 📊 Sharing Reports With Clients You can also share specific reports directly without requiring a client login. To generate a shareable report link: 1. Go to Reports using the left sidebar (URL: /report-builder/projects-list). 2. Open the report you want to share. 3. Click Share and select Public Link or Client Portal Link. 4. Copy the link and send it to your client. Links generated from your whitelabel account will display your branding automatically. 🔑 Troubleshooting Login Issues If you or your clients cannot log in to the subdomain, work through the following checklist: - DNS not propagated: Use a tool like whatsmydns.net to confirm your CNAME record is live globally. Wait the full 48 hours if needed. - Domain not verified: Return to the header apps-grid icon → More Features → Agency Hub (Set up your Agency's White Label) and re-run the domain verification step. - Wrong login URL: Ensure clients are using your subdomain URL, not the main Search Atlas site. - Expired invitation: Client invitation links expire after 7 days. If a client did not set their password in time, resend the invitation from Account Menu (avatar) → Settings → Team Members. - SSL certificate pending: After domain verification, Search Atlas automatically provisions an SSL certificate. This can take up to 30 minutes. The portal will show a security warning until the certificate is active. 💡 Best Practices - Always test the subdomain login yourself before inviting clients. - Use an incognito window when previewing to avoid cached sessions. - Keep client permissions set to Client View to protect other accounts' data. - Remind clients to bookmark your subdomain URL, not the Search Atlas homepage. 🆘 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔌 Fix OTTO Pixel UUID Errors with White-Label Domains

🧭 Overview If you have installed the Search Atlas WordPress plugin and entered your UUID but still see a "UUID not correct" error, your white-label domain configuration is likely the cause. Standard plugin installations validate the UUID against the default Search Atlas dashboard URL. When your account uses a custom white-label domain — such as dashboard.hearingassetadvisors.com — the plugin needs additional configuration to recognize that domain as a trusted source. This article walks you through every fix. 🔍 Why White-Label Domains Cause UUID Errors The OTTO pixel plugin validates your UUID by communicating with the Search Atlas dashboard. If your account is accessed through a white-label domain, the plugin must be told which domain to trust. Without this, the handshake between your WordPress site and the dashboard fails, producing a UUID validation error even when the UUID itself is perfectly correct. - The UUID displayed inside a white-label dashboard is the same UUID used platform-wide — no separate UUID is issued. - The error is not caused by a wrong UUID; it is caused by a domain mismatch during validation. - Resolving the mismatch requires configuring the plugin settings under Search Atlas → Settings or inserting the pixel script manually. ✅ Step 1 — Verify Your UUID Is Copied Correctly Before changing any settings, confirm the UUID itself is error-free. 1. Log in to your dashboard through your white-label domain (for example, dashboard.hearingassetadvisors.com). 2. Navigate to OTTO SEO → All Sites (SEO Automation) in the left sidebar. 3. Locate your OTTO pixel UUID. It is a long alphanumeric string with hyphens. 4. Click the copy icon next to the UUID — do not type it manually. 5. Paste it into a plain-text editor and confirm there are no leading spaces, trailing spaces, or line breaks. 6. Re-enter this clean UUID in the WordPress plugin settings and save. If the error persists after this step, continue to Step 2. ⚙️ Step 2 — Enable the White-Label Domain in Plugin Settings The Search Atlas WordPress plugin includes a setting that allows you to declare your white-label domain so UUID validation routes correctly. 1. In your WordPress admin panel, go to Search Atlas → Settings in the sidebar. 2. Locate the field labelled Dashboard Domain or Custom Domain (exact label may vary by plugin version). 3. Enter your full white-label domain including the subdomain, for example: dashboard.hearingassetadvisors.com. 4. Save the settings. 5. Return to the UUID field, re-paste your UUID, and save again. 6. Reload the page and check whether the validation error has cleared. If your plugin version does not show a Dashboard Domain field, proceed to Step 3. 🔗 Step 3 — Enable Metasync in the Plugin Metasync is the background sync feature that links your WordPress site to the Search Atlas platform. It must be active for UUID validation to work under a white-label domain. 1. In your WordPress admin panel, open Search Atlas → Settings in the sidebar. 2. Find the toggle labelled Metasync or Enable Metasync. 3. Switch it to On or Enabled. 4. Save your settings. 5. Wait up to two minutes, then reload the plugin settings page to confirm the UUID now shows as verified. 📋 Step 4 — Insert the Pixel Script Manually (Alternative Method) If the plugin-based UUID entry continues to show errors, you can bypass it entirely by inserting the full OTTO pixel script directly into your WordPress site's code. This method works regardless of white-label domain configuration. 1. Log in to your dashboard through your white-label domain. 2. Go to OTTO SEO → All Sites (SEO Automation) in the left sidebar. 3. Find the OTTO pixel section and click Copy Script or Get Pixel Code. This copies the complete tag including your UUID already embedded inside it. 4. In your WordPress admin panel, go to Appearance → Theme File Editor, or install a plugin such as Insert Headers and Footers if you prefer not to edit theme files directly. 5. Paste the copied script into the section of your site. If using Insert Headers and Footers, paste it in the Scripts in Header field. 6. Save the changes. 7. Visit your website, right-click the page, and select View Page Source. Search for your UUID to confirm the script is present in the page HTML. Once the script is live in your page source, the OTTO pixel is active. You do not need the plugin's UUID field to show a green checkmark for tracking to function when the script is inserted manually. 🌐 Does Your White-Label Domain Affect Pixel Tracking? Your white-label domain affects the validation step inside the plugin UI, but it does not change what the pixel collects or how OTTO processes your site data. Once the pixel script is live on your pages — whether via the plugin or manual insertion — all tracking and OTTO automation works exactly as it does for standard installations. The white-label domain is purely a branding layer for your dashboard access. 🛠️ Quick Troubleshooting Checklist - UUID copied with extra spaces? Re-copy using the copy icon, not manual selection. - Plugin Dashboard Domain field filled in? Enter your full white-label domain. - Metasync enabled? Toggle it on and save. - Plugin version outdated? Update the Search Atlas plugin to the latest version from the WordPress plugin repository. - Script inserted manually but UUID not in page source? Clear your caching plugin and CDN cache, then re-check. - Firewall or security plugin blocking the script? Whitelist the Search Atlas pixel domain in your security plugin settings. 💬 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.

🏷️ Accessing Your White-Label Domain and Reports

🔍 Overview Search Atlas allows agencies to present a fully branded experience to clients through a white-label domain. This article explains how to log in to your white-label portal, why you may see an invitation prompt, and how to correctly share or embed client reports using your agency domain rather than a Search Atlas URL. 🚪 Logging In to Your White-Label Domain Your white-label domain is a custom URL that your agency configured during setup (for example, reports.youragency.com). When you or a client visits this URL, you should land on a branded login screen — not a Search Atlas page. If you are prompted with an invitation required message when visiting your white-label domain, this is usually caused by one of the following: - The user account has not yet been added to the white-label workspace. An agency admin must send an invitation from within the platform before that user can log in. - The white-label domain setup is incomplete or the DNS configuration has not fully propagated. DNS changes can take up to 48 hours to resolve globally. - The user is trying to log in with a Google account. Google OAuth for white-label tenants is currently handled separately from the main Search Atlas login. Until this is fully split, use your email and password to log in to the white-label portal instead of the Google sign-in button. To invite a client or team member to your white-label workspace, log in to Search Atlas, navigate to your white-label settings, and send an invitation from there. The invited user will receive an email with a direct link to set up their access. 📊 Finding and Sharing the Correct Report URL When you build a client report in Search Atlas and copy the share or iframe link, the URL should reflect your white-label domain — not dashboard.searchatlas.com. If you are seeing a Search Atlas URL instead of your agency domain in the share link, this is a known issue currently in development and will be resolved in an upcoming release. In the meantime, use the following workaround to generate the correct white-label report URL: 1. Go to Left sidebar → Reports (or navigate to /report-builder/projects-list). 2. Open the report you want to share with a client. 3. Copy the URL shown in your browser's address bar. 4. Replace the dashboard.searchatlas.com portion of the URL with your white-label domain (for example, change https://dashboard.searchatlas.com/report-builder/... to https://reports.youragency.com/report-builder/...). 5. Paste the updated URL into your iframe embed code or share it directly with your client. This manually adjusted URL will load the report through your branded portal as long as the client has been invited to and has access to your white-label workspace. ⚙️ Common Issues and Quick Fixes - Redirected to a billing or choose-plan page: This was a known bug and has been resolved. If you still experience this, clear your browser cache and cookies, then try logging in again. - ERR_TOO_MANY_REDIRECTS on your white-label URL: This can occur if there is a conflict in your domain's redirect rules. Check that your DNS and SSL settings are correctly configured with no conflicting redirects. Contact your domain host if the issue persists at the DNS level. - White-label domain works but OTTO pixel is not loading: This was a known issue tied to redirect loops and has been resolved. If you still see OTTO-related issues on your white-label domain, please reach out via the chat widget. - Client sees a Search Atlas branded page instead of your agency branding: Confirm that the URL your client is using matches your white-label domain exactly, including the correct subdomain (e.g., reports. vs app.). ✅ Best Practices for White-Label Access - Always invite clients through the white-label workspace settings before sharing any report links. Uninvited users will be blocked at login. - Instruct clients to bookmark the white-label login URL and use their email and password rather than Google sign-in until Google OAuth is fully supported for white-label tenants. - When building iframe embeds for client dashboards, manually verify that the embedded URL uses your agency domain and test it in an incognito window before sending to clients. - If you manage multiple clients, confirm that each client is invited only to their own workspace to prevent cross-client data visibility. 💬 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.

🛠️ White Label DNS Configuration Troubleshooting Guide

🔍 Overview Setting up DNS for your White Label can feel complex, and propagation delays or small configuration mistakes can make it hard to tell whether the setup worked. This guide walks you through the correct configuration steps, common mistakes to avoid, and how to verify your setup is working. ⚙️ Required DNS Records To connect your custom domain to Search Atlas White Label, you must add the following records in your domain registrar or DNS provider's control panel: - Type: CNAME - Host / Name: The subdomain you want to use (e.g., reports or app) - Value / Points to: The target hostname provided in your Search Atlas White Label settings - TTL: 3600 (1 hour) or the lowest value your provider allows Do not add an A record or MX record in place of the CNAME — these will not work for White Label setup. 🚨 Common Configuration Mistakes The following errors are the most frequent causes of a failed DNS setup: - Using the root domain instead of a subdomain: Most DNS providers do not allow a CNAME on a root domain (e.g., yourdomain.com). Always use a subdomain such as reports.yourdomain.com. - Trailing dot or extra characters: Copy the target value from Search Atlas exactly. Even a single extra character or space will break the record. - Conflicting records: If a previous A record or CNAME already exists for the same subdomain, delete it before adding the new CNAME. - Proxy enabled in Cloudflare: If you use Cloudflare, ensure the proxy toggle (orange cloud) is set to DNS only (grey cloud) for the CNAME record. - Incorrect subdomain in Search Atlas settings: The subdomain you enter inside Search Atlas must exactly match what you configured at your DNS provider. ⏱️ Understanding DNS Propagation After saving a DNS record, changes do not take effect immediately. Propagation can take anywhere from 15 minutes to 48 hours depending on your DNS provider and the previous TTL value. During this window, the domain may appear broken even when the configuration is correct. To check propagation status, use a free tool such as whatsmydns.net and search for your subdomain as a CNAME record. Once you see your target hostname returned consistently across multiple global locations, propagation is complete. ✅ Step-by-Step Verification Checklist Work through the following steps in order before concluding there is a technical issue: 1. Log in to your DNS provider and confirm the CNAME record is saved with the exact target value from Search Atlas. 2. Check that no conflicting A record or old CNAME exists for the same subdomain and delete any conflicts. 3. If using Cloudflare, confirm the proxy is set to DNS only. 4. Wait at least 1 hour after saving and then check propagation on whatsmydns.net. 5. Log in to Search Atlas and re-open your White Label settings to confirm the custom domain field is saved correctly and matches your subdomain exactly. 6. Open the subdomain URL in an incognito or private browser window to avoid cached results. 🔄 When to Re-Save Your White Label Settings If you recently corrected a DNS record, you may also need to re-save your White Label configuration inside Search Atlas to trigger a fresh connection check. Navigate to your White Label settings, confirm all fields are correct, and click Save again. Then allow up to 30 minutes for the platform to re-validate the domain. 💡 Still Not Working After 48 Hours? If more than 48 hours have passed, your DNS records appear correct on whatsmydns.net, and your White Label domain is still not loading, there may be an issue on the platform side that requires investigation. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team. Please have the following ready to share: your custom subdomain, a screenshot of your DNS record, and your whatsmydns.net results — this will help our team resolve your issue as quickly as possible.

🔧 Remove White Label Setup and Custom Domain

🧼 Remove Visible Branding Yourself You can clear most White Label elements directly in the platform without contacting support. 1. Go to the apps-grid icon in the header → More Features → Agency Hub (Set up your Agency's White Label). 2. Open the White Label tab. 3. Click Remove next to your custom logo, favicon, and background image. 4. Clear the Custom OTTO Name field. 5. Clear the Tracking Label field. 6. Reset Brand Colors to defaults using the reset button next to each color picker. 7. Save your changes. 🌐 Request Custom Domain Removal The custom domain involves backend infrastructure that our team must disable for you. DNS records you added will stop working once we remove the backend routing. 1. Open the chat widget in the bottom-right corner of the platform. 2. Type human teammate to connect with our team. 3. Request removal of your White Label custom domain. 4. Our specialized team will handle the backend disablement. 📋 What Happens After Removal - Your reports and dashboards revert to Search Atlas branding. - Custom domain URLs no longer resolve. - OTTO pixel tracking uses the default Search Atlas domain. - Client-facing links update automatically. 💡 Need Further Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🏷️ Set Up White Label DNS Configuration Correctly

🌐 Overview White label setup lets you serve Search Atlas reports and tools under your own custom domain. To make this work, your domain must point to Search Atlas using a CNAME record. Using an incorrect record type — such as an A record — will cause the setup form to fail and your white label domain to not function properly. ⚠️ Important: Use a CNAME Record, Not an A Record A previous version of our guidance incorrectly instructed customers to create an A record pointing to the IP address 35.243.150.225. This is outdated and incorrect. Do not use that IP address or an A record for white label DNS setup. The correct configuration requires a CNAME record targeting: - Record type: CNAME - Host / Name: your chosen subdomain (for example, reports or seo) - **Value / Target:**whitelabel.dns.searchatlas.com - TTL: 3600 (or your DNS provider's default) Using an A record instead of a CNAME record will prevent the platform from verifying your domain and will cause form submission errors during white label setup. 🛠️ Step-by-Step DNS Setup 1. Log in to your domain registrar or DNS provider (for example, Cloudflare, GoDaddy, Namecheap, or Route 53). 2. Navigate to the DNS settings or DNS management section for your domain. 3. Delete or remove any existing A record pointing to 35.243.150.225 if you previously followed the outdated instructions. 4. Create a new DNS record with the following values: - Type: CNAME - Host / Name: enter your chosen subdomain, for example reports (this will create reports.yourdomain.com) - **Value / Target / Points to:**whitelabel.dns.searchatlas.com - TTL: 3600 or Auto 5. Save the record and allow up to 24–48 hours for DNS propagation, though changes often take effect within 1–2 hours. ✅ Complete the White Label Setup Form 1. In Search Atlas, go to More Features → Agency Hub (Agency Settings). 2. Navigate to your white label settings and open the setup form. 3. Enter your full custom subdomain, for example reports.yourdomain.com. 4. Submit the form. The platform will attempt to verify your CNAME record. 5. If verification succeeds, your white label domain will be activated. If you see a form submission error, check the troubleshooting steps below before retrying. 🔍 Troubleshooting Form Submission Errors If you still see a form submission error after updating your DNS record, work through the following checks: - Confirm you deleted the old A record. Having both an A record and a CNAME record for the same subdomain will cause a conflict. Most DNS providers will not allow this, but verify there are no conflicting records. - Check propagation status. Use a free tool such as whatsmydns.net and search for your subdomain as a CNAME. It should return whitelabel.dns.searchatlas.com. If it still shows an IP address, propagation is not yet complete — wait and try again. - Verify the subdomain matches exactly. The subdomain you enter in the Search Atlas form must match the host value in your DNS record exactly, including capitalisation. - Check for a proxy or CDN override. If you use Cloudflare, make sure the CNAME record is set to DNS only (grey cloud icon) rather than Proxied (orange cloud) during initial setup and verification. - Confirm there are no typos in the target. The CNAME target must be exactly whitelabel.dns.searchatlas.com with no extra characters or spaces. 📋 Quick Reference: Correct DNS Record - Record type: CNAME - Host / Name: your subdomain (example: reports) - **Target / Value:**whitelabel.dns.searchatlas.com - TTL: 3600 or Auto - Do NOT use: A record or the IP 35.243.150.225 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Whitelabel Domain Script Unreachable Errors

🔍 Overview If you see a Script Unreachable status in your OTTO SEO dashboard even though your whitelabel domain appears to be correctly configured, there is likely a misconfiguration in your DNS, CNAME, or redirect settings that is preventing the OTTO script from loading. This article walks you through the most common causes and how to fix them. ⚙️ Why This Happens The OTTO script is served through your whitelabel domain. If the domain is not resolving correctly, the script cannot be reached — even if the domain settings look correct inside Search Atlas. Common root causes include: - CNAME target mismatch: Your DNS provider is pointing to an outdated or incorrect target hostname. - Redirect loop: Your whitelabel URL is returning ERR_TOO_MANY_REDIRECTS, which blocks the script from loading. - DNS propagation delay: Recent changes to your DNS records have not yet fully propagated across all servers. - False unreachable status: In some cases, the platform may incorrectly report the script as unreachable even when it is accessible. This is a known issue that has been resolved in recent updates. 🗺️ Step 1 — Verify Your Whitelabel Domain Settings 1. In Search Atlas, go to More Features → Agency Whitelabel (URL: /agency-settings). 2. Under White Label Setup, confirm that your custom domain is entered correctly with no trailing slashes or typos. 3. Note the CNAME target value shown in the platform — this is the exact hostname your DNS record must point to. 🌐 Step 2 — Check Your DNS CNAME Record 1. Log in to your domain registrar or DNS provider (for example, Cloudflare, GoDaddy, or Namecheap). 2. Locate the CNAME record for your whitelabel subdomain (for example, seo.youragency.com). 3. Confirm that the Value or Points to field matches exactly the CNAME target shown in Search Atlas. Even a small difference — such as a missing subdomain segment or an extra character — will cause a mismatch and break the script. 4. If the values do not match, update the CNAME record to use the correct target provided in the platform. 5. Allow up to 48 hours for DNS changes to propagate, though most updates take effect within a few hours. 🔄 Step 3 — Check for Redirect Loops A redirect loop on your whitelabel domain will prevent the OTTO script from loading entirely. To check for this: 1. Open a new browser tab and navigate directly to your whitelabel domain URL. 2. If the browser shows an ERR_TOO_MANY_REDIRECTS error, there is a redirect conflict in your DNS or hosting configuration. 3. Common causes include forcing HTTPS at both the DNS level and the hosting level simultaneously, or conflicting redirect rules in your .htaccess file or server configuration. 4. Disable any duplicate redirect rules and ensure HTTPS is enforced at only one layer. ✅ Step 4 — Recheck the Script Status in OTTO 1. After updating your DNS or redirect settings, go to Left sidebar → OTTO SEO → Installation Guide. 2. Click Continue installation to trigger a fresh script status check. 3. If the status still shows Script Unreachable after DNS has propagated and your settings are correct, the platform may be reporting a false status. Proceed to the next step. 🔎 Step 5 — Manually Verify the Script Is Accessible You can independently confirm whether the script is actually reachable before escalating: 1. Open your browser's developer tools (press F12 or right-click the page and select Inspect). 2. Go to the Network tab and reload your website. 3. Search for the OTTO script URL in the network requests. If it returns a 200 OK status, the script is loading correctly and the unreachable warning may be a display error that will clear on its own. 4. If the script request fails or returns an error code, the misconfiguration is confirmed and you should review Steps 2 and 3 again. 💡 Quick Reference — Common Issues and Fixes - CNAME target mismatch: Update your DNS CNAME record to match the exact target shown in More Features → Agency Hub (Agency Whitelabel). - ERR_TOO_MANY_REDIRECTS: Remove duplicate HTTPS redirect rules from your DNS and server configuration. - Script unreachable after correct setup: Wait for DNS propagation and use browser dev tools to verify the script loads with a 200 status. - False unreachable status in the dashboard: If the script is confirmed accessible via dev tools, the status should update automatically. If it does not, contact support. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🌐 Fix White Label DNS Configuration Issues Fast

🔍 Overview If your White Label domain is not resolving correctly after DNS setup, the most common cause is using the wrong DNS record type. This guide walks you through the correct configuration, how to spot mistakes, and how to verify that your DNS changes have taken effect. ⚠️ The Most Common Mistake: A Record vs. CNAME Record Search Atlas White Label requires a CNAME record, not an A record. This is the single most frequent cause of DNS failures. - A record — maps a domain to a specific IP address. Search Atlas does not use a static IP for White Label, so A records will not work reliably and will cause the domain to fail or resolve incorrectly. - CNAME record — maps your custom domain to another domain name (a hostname). This is the correct record type for Search Atlas White Label because it points to our infrastructure hostname, which handles routing automatically. If you have an A record in place, delete it before adding the CNAME. Having both at the same time will cause conflicts and prevent the domain from resolving. ✅ Correct CNAME Configuration Use the following structure when adding your CNAME record in your DNS provider (such as Cloudflare, GoDaddy, Namecheap, or Route 53): - Type: CNAME - Name / Host: The subdomain you want to use for your White Label (for example, reports if your White Label URL will be reports.yourdomain.com) - Value / Target / Points to: The hostname provided inside your Search Atlas White Label settings (for example, whitelabel.dns.searchatlas.com) - TTL: 3600 (1 hour) or Auto if your provider offers it Example: If your agency domain is agencypro.com and you want your clients to access reports at reports.agencypro.com, your CNAME record should look like this: - Type: CNAME - Name: reports - Value: whitelabel.dns.searchatlas.com Always copy the exact hostname from your Search Atlas dashboard. Do not guess or modify it. A single typo will cause the configuration to fail. 🔎 How to Verify Your DNS Is Configured Correctly After saving your CNAME record, follow these steps to confirm the setup before assuming something is broken. 1. Wait for propagation. DNS changes can take anywhere from a few minutes to 48 hours to propagate globally. Most changes resolve within 1–4 hours. Do not make additional edits during this window, as each change resets propagation time. 2. Check using a DNS lookup tool. Visit a free tool such as dnschecker.org or whatsmydns.net. Enter your White Label subdomain and select CNAME as the record type. You should see your Search Atlas hostname appear as the target across most global locations. 3. Clear your browser cache. If the lookup tool shows the correct CNAME but your browser still does not load the page, clear your cache or test in an incognito window. 4. Check for conflicting records. Log in to your DNS provider and search for any A records, AAAA records, or duplicate CNAME entries under the same subdomain name. Remove any conflicting records. 🧭 Diagnosing Persistent DNS Failures If you have followed all the steps above and the domain still does not resolve, work through the following questions to identify the root cause. - Is the record type definitely CNAME? Log back in to your DNS provider and confirm. It is easy to accidentally save as an A record if the default option in your provider's form is pre-selected. - Is the CNAME value exactly what Search Atlas provided? Go back to your White Label settings in Search Atlas and copy the hostname again. Paste it fresh rather than retyping. - Has it been less than 48 hours? If so, continue waiting and recheck using the DNS lookup tool rather than your browser. - Is there a proxy or CDN layer in front of the domain? If you use Cloudflare, make sure the CNAME record is set to DNS Only (grey cloud icon), not Proxied (orange cloud), during initial setup. Proxied mode can interfere with domain verification. - Did you add the CNAME at the root domain level? Root-level CNAMEs (for example, agencypro.com without a subdomain) are not supported by most DNS providers and are not compatible with Search Atlas White Label. You must use a subdomain such as reports.agencypro.com. 🔧 Quick Checklist Before Contacting Support - Record type is CNAME (not A, AAAA, or TXT) - CNAME value matches exactly what is shown in Search Atlas White Label settings - No conflicting A records or duplicate CNAMEs exist for the same subdomain - At least 4 hours have passed since the last change - DNS lookup tool confirms the CNAME is resolving to the correct target - Cloudflare proxy is disabled (grey cloud) if applicable - A subdomain is used, not the root domain 💬 Still Need Help? If you have completed every step above and the DNS is still not resolving, our team can review your specific configuration. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team. Additional Notes A previous version of our guidance incorrectly instructed customers to create an A record pointing to IP address 35.243.150.225. This is outdated and incorrect. Do not use that IP. Also, the correct CNAME target is whitelabel.dns.searchatlas.com (not whitelabel.searchatlas.com). Delete any existing A record pointing to 35.243.150.225.

🌐 Fix White-Label Domain DNS for GoHighLevel

🔍 Why Your White-Label Domain Is Not Working If you visit your white-label agency domain and see a message like "Looks like the page you're trying to access does not exist", the most common cause is an incomplete or incorrect DNS configuration. Your custom domain needs to point to Search Atlas servers before the white-label preview can load correctly. This guide walks you through every step to get your domain live. 📋 What You Need Before You Start - Admin access to your domain registrar (e.g., GoDaddy, Namecheap, Cloudflare) - Your white-label subdomain chosen and entered inside Search Atlas (e.g., reports.youragency.com) - Admin access to your GoHighLevel account if you are routing through a GoHighLevel sub-account - A few minutes of patience — DNS changes can take up to 48 hours to fully propagate ⚙️ Step 1: Confirm Your White-Label Domain in Search Atlas 1. Log in to Search Atlas and navigate to your Agency Settings or White-Label configuration panel. 2. Confirm the exact subdomain you have entered (e.g., reports.youragency.com). Copy it exactly — spelling and punctuation matter. 3. Note the CNAME target value displayed on that page. You will need this in the next step. It typically looks like whitelabel.dns.searchatlas.com or similar. 🛠️ Step 2: Add the CNAME Record at Your Domain Registrar 1. Log in to the control panel of the registrar where your domain is registered. 2. Go to DNS Management or DNS Records for your domain. 3. Create a new CNAME record with these values: - Host / Name: the subdomain prefix only (e.g., reports if your full subdomain is reports.youragency.com) - Value / Points to: the CNAME target value copied from Search Atlas in Step 1 - TTL: 3600 (1 hour) or the lowest value your registrar allows 4. Save the record. Important: If you already have an A record or conflicting CNAME for the same subdomain, delete it before adding the new CNAME record. Conflicting records will prevent the domain from resolving correctly. 🔗 Step 3: Configure the Domain Inside GoHighLevel If you are using GoHighLevel to host client portals or route traffic through a sub-account, you must also register the custom domain inside GoHighLevel so the two platforms can communicate correctly. 1. Log in to GoHighLevel and open the relevant Sub-Account. 2. Go to Settings → Domains. 3. Click Add Domain and enter the same subdomain you configured in Search Atlas (e.g., reports.youragency.com). 4. GoHighLevel will verify the domain by checking the CNAME record you added in Step 2. Verification may take a few minutes. 5. Once verified, set this domain as the primary domain for the sub-account if you want all white-label report links to use it. Note: If GoHighLevel shows a verification error immediately after you add the CNAME record, wait 15–30 minutes and try verifying again. DNS changes are not always instant. ✅ Step 4: Test and Verify Your White-Label Domain 1. Open a private or incognito browser window to avoid cached results. 2. Type your full white-label subdomain into the address bar and press Enter. 3. You should see your branded Search Atlas report portal instead of the error page. 4. If the error persists, use a free DNS checker tool (such as dnschecker.org) to confirm your CNAME record has propagated globally. Enter your subdomain, select CNAME as the record type, and check that results point to the correct Search Atlas target. ⏱️ DNS Propagation: What to Expect DNS changes do not apply instantly. Propagation typically takes 15 minutes to 4 hours for most regions, but can take up to 48 hours in rare cases depending on your registrar and TTL settings. During this window, some locations may still see the error page while others load correctly — this is normal. Avoid making further DNS changes during this period as it can restart the propagation timer. 🚨 Common Mistakes to Avoid - Using the full domain as the Host value — enter only the subdomain prefix (e.g., reports, not reports.youragency.com) unless your registrar specifically requires the full domain. - Skipping the GoHighLevel domain step — configuring DNS alone is not enough if you use GoHighLevel; both platforms must recognise the domain. - Cloudflare proxy enabled — if your domain is managed through Cloudflare, make sure the CNAME record is set to DNS only (grey cloud icon), not proxied (orange cloud). The Search Atlas white-label integration requires direct DNS resolution. - Testing too soon — always test in a private window after waiting at least 15 minutes. 💬 Still Seeing the Error? If you have followed all the steps above and your white-label domain is still not loading correctly, If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix White Label DNS Setup and Form Errors

🌐 What Is White Label DNS Configuration? White label DNS configuration lets you serve Search Atlas reports and dashboards under your own custom domain or subdomain. When set up correctly, your clients see your brand — not Search Atlas. If any step is missed or a DNS record is entered incorrectly, you may encounter form submission errors or see the setup fail to verify. 📋 Prerequisites Before You Begin - Access to your domain registrar or DNS provider (e.g., GoDaddy, Cloudflare, Namecheap). - A subdomain chosen for white label use (e.g., reports.yourdomain.com). - Admin-level access to your Search Atlas account. - A verified sender email address for client-facing communications. ⚙️ Step-by-Step DNS Setup 1. Log in to Search Atlas and navigate to your white label settings via More Features → Agency Hub (Agency Settings). 2. Enter your custom subdomain in the designated field (e.g., reports.yourdomain.com). Do not use your root domain — a subdomain is required. 3. Copy the CNAME record provided by Search Atlas. It will look similar to: whitelabel.dns.searchatlas.com. 4. Log in to your DNS provider and create a new CNAME record: - Name/Host: your subdomain prefix (e.g., reports) - Value/Target: the CNAME value copied from Search Atlas - TTL: 3600 (or Auto if available) 5. Save the DNS record and return to Search Atlas. 6. Click Verify or Save on the white label setup form to trigger DNS verification. ⏱️ How Long Does DNS Propagation Take? DNS changes can take anywhere from a few minutes to 48 hours to propagate globally. In most cases, propagation completes within 1–4 hours. If verification fails immediately after saving, wait at least 30 minutes before trying again. Do not repeatedly click Verify in quick succession, as this can trigger rate-limiting. 🚨 Troubleshooting Form Submission Errors If you receive a form submission error during white label setup, work through the following checks before contacting support: - Check for typos in the subdomain field. The subdomain must exactly match the Name/Host value you entered in your DNS provider. Even a single extra character will cause verification to fail. - Confirm the CNAME record is active. Use a free DNS lookup tool (such as MXToolbox or dnschecker.org) to confirm your subdomain resolves to the correct CNAME target. - Avoid using a root domain. Entering yourdomain.com instead of a subdomain like reports.yourdomain.com is a common cause of errors. Always use a subdomain. - Remove any conflicting A records. If an A record already exists for the same subdomain in your DNS provider, it will conflict with the CNAME. Delete or rename the conflicting record first. - Check Cloudflare proxy settings. If your domain is managed through Cloudflare, make sure the CNAME record is set to DNS only (grey cloud icon), not Proxied (orange cloud). The proxied setting can block verification. - Clear your browser cache and try submitting the form again in a private or incognito window. - Verify your account permissions. Only account admins can complete white label setup. If you are on a sub-account or team seat, ask your account owner to complete this step. ✅ How to Confirm Setup Is Complete Once DNS verification succeeds, you will see a confirmation message in the white label settings. You can then: - Visit your custom subdomain in a browser to confirm it loads the correct branded interface. - Send a test report link to yourself to verify the client-facing experience looks correct. - Review your logo, brand colours, and sender name to ensure everything matches your brand. 💡 Common Mistakes to Avoid - Adding http:// or www to the subdomain field — enter only the subdomain, with no protocol prefix. - Setting TTL too low (under 300 seconds) on critical DNS records, which can cause intermittent failures. - Forgetting to save changes in your DNS provider before returning to Search Atlas to verify. 🤝 Need More Help? If you have followed all the steps above and are still experiencing a form submission error or DNS verification failure, our team is here to help. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ White Label Setup: Cloudflare DNS and GHL Blog

🌐 Overview Setting up Search Atlas white labeling with a custom domain involves three moving parts: your Cloudflare DNS record, the Search Atlas white label configuration, and any third-party integrations such as GoHighLevel (GHL) blogs or the WordPress plugin. A misconfiguration in any one of these areas can cause broken dashboard URLs or content display issues. This guide walks you through each step in the correct order. ⚙️ Step 1: Configure Your White Label Domain in Search Atlas Before touching DNS, make sure your custom domain is registered inside Search Atlas. 1. Log in to your Search Atlas account and navigate to Settings → White Label. 2. Enter your chosen subdomain (e.g., app.youragency.com) in the custom domain field. 3. Save the settings. Search Atlas will display the CNAME target value you need for the next step. Copy this value exactly — do not modify it. Important: Complete this step first. Creating the DNS record before registering the domain in Search Atlas is a common cause of mismatches that break the dashboard URL. ☁️ Step 2: Add the CNAME Record in Cloudflare 1. Log in to Cloudflare and select the domain you are using for white labeling. 2. Go to DNS → Records and click Add record. 3. Set the record type to CNAME. 4. In the Name field, enter only the subdomain prefix (e.g., app if your full subdomain is app.youragency.com). 5. In the Target field, paste the CNAME value copied from Search Atlas. 6. Set Proxy status to DNS only (grey cloud). Enabling the Cloudflare proxy (orange cloud) on this record is the most frequent cause of broken dashboard URLs because it intercepts SSL termination handled by Search Atlas. 7. Click Save. DNS propagation typically takes 5–30 minutes, but can take up to 48 hours in some regions. Use a tool such as dnschecker.org to confirm the CNAME is resolving correctly before proceeding. 🔌 Step 3: Fix the WordPress Plugin Dashboard URL If you added the DNS record after the WordPress plugin was already installed, the plugin may still be pointing to the original Search Atlas dashboard URL instead of your white label domain. 1. In your WordPress admin panel, go to Search Atlas → Settings. 2. Locate the Dashboard URL or API Endpoint field. 3. Replace the existing URL with your new white label domain (e.g., https://app.youragency.com). 4. Save changes and reload the plugin page to confirm the connection is successful. If the field is greyed out or the plugin re-populates the old URL automatically, deactivate and reactivate the plugin after updating the URL, then save again. 📝 Step 4: Fix Missing Tables in GHL Blog Posts GoHighLevel's blog editor strips certain HTML elements — including table tags — when content is pasted or imported. This is a known GHL editor limitation, not a Search Atlas issue. Use one of the following workarounds to display tabular data correctly: - Convert tables to styled lists or columns: Recreate the table content using GHL's native column blocks or bullet lists so the editor does not strip the markup. - Embed an HTML block: In the GHL blog editor, insert a Custom Code / HTML block and paste your raw table HTML directly into it. This bypasses the editor's sanitisation and renders the table as intended. - Use an image: For purely visual tables (non-interactive data), export the table as an image and insert it via GHL's image block. Recommended approach: The HTML block method preserves full formatting and is the most reliable option for complex tables. ✅ Quick Troubleshooting Checklist - Dashboard URL broken after DNS change? Confirm the CNAME proxy is set to DNS only in Cloudflare and that the target matches the value in Search Atlas Settings. - WordPress plugin connecting to wrong URL? Manually update the Dashboard URL field in the plugin settings to your white label domain. - SSL certificate errors on white label domain? Wait up to 30 minutes after DNS propagation for the certificate to provision automatically. Do not enable the Cloudflare proxy during this window. - Tables still not showing in GHL? Switch to an HTML block and paste the raw table markup directly. 💬 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.

⚠️ WhiteLabel Website Builder: CDN Image URLs Show searchatlas.com Domain

CDN image URLs generated by the WhiteLabel Website Builder currently display searchatlas.com instead of your white-labeled domain. This is a confirmed platform limitation with no workaround — the Search Atlas development team is actively building a fix. 🔍 What Is Happening When the WhiteLabel Website Builder embeds images on your site (for example, yourclientdomain.com), the CDN (Content Delivery Network) URLs that serve those images reference searchatlas.com rather than your custom domain. These URLs are visible in page source code, which can expose the Search Atlas platform domain to your end clients and search engines, undermining your white-label branding and SEO signals. ⚠️ Current Status: Known Limitation Custom CDN domain mapping for the WhiteLabel Website Builder is not yet supported. This is not a misconfiguration on your account — it is a confirmed gap in the current feature set, acknowledged by the Search Atlas development team. There is no manual workaround available at this time. 🔗 Related Known Issue: Google Indexing the Origin Domain Some customers also notice their WhiteLabel site appearing in Google search results under the searchatlas.com origin domain instead of their custom domain. This is a separate but related manifestation of the same white-label domain gap and is also under active remediation by the Search Atlas development team. If you are seeing both symptoms, you do not need to open separate support tickets — they are tracked as companion issues. 🚀 Fix In Progress The Search Atlas development team is actively building support for custom CDN domains within the WhiteLabel Website Builder. Watch for a release announcement in-app or via email — no action is required from you before the release. 📋 What to Do Now - Do not attempt to reconfigure CDN settings. The CDN domain is assigned automatically by the platform and cannot be changed through any current setting or toggle. - Watch for a release announcement via email or in-app notifications when the update goes live. - Contact Search Atlas Support if you need an updated timeline or want to confirm whether the upcoming release also resolves the Google indexing variant for your account. 🌀 Once the custom CDN domain feature ships, image URLs on your WhiteLabel site will automatically reflect your own domain. Contact Search Atlas Support if you need a progress update before the release.

⚠️ "You Do Not Have Access to Update Settings" Error After Saving White Label Domain

After you save a new White Label domain and open the Settings tab without refreshing, clicking Update Settings shows "You do not have access to update settings." Your permissions are correct, and a single page refresh resolves it immediately. This guidance applies to the current White Label setup workflow. A revised setup workflow (Linear WL-291, Awaiting Release) is planned that changes how setup errors are handled and introduces a different error message. Until that update ships, the steps below apply to the session-sync error described here. 💡 Why the Update Settings Error Appears When you save a new White Label domain, Search Atlas updates your account's permission state in the background. If you open the Settings tab before the browser session syncs those updated permissions, the Update Settings button cannot verify your access and returns this error. Your account permissions are not affected. This is a temporary session state mismatch, not a real access restriction. 🛠️ How to Fix the Update Settings Error 1. After saving your White Label domain, press F5 (Windows) or Cmd + R (Mac) to refresh the page, or click your browser's reload button. 2. Open the Settings tab. 3. Click Update Settings. The error no longer appears, and your changes save successfully. 💡 How to Avoid the Update Settings Error Refresh the page immediately after saving a new White Label domain, before opening any other tab. This lets the browser session pick up your updated permission state before you make further changes in Settings. 🛠️ What to Do If You See "Failed to Update Brand Setting" If you instead see a "Failed to update brand setting" error rather than the access error above, the domain you entered may already be in use. This is a separate issue from the session sync mismatch and is not resolved by refreshing the page. Contact support to verify the domain's availability. 🔗 Related White Label Issues If your White Label logo doesn't display on the login screen, or you encounter other login screen display problems, see the companion White Label logo and login screen troubleshooting guide for complete coverage. 🎯 You now know that the "You do not have access to update settings" error is a session sync issue, not a real permissions problem, and a single page refresh resolves it immediately. For a full walkthrough of White Label configuration, see the White Label Domain Setup guide.

🔗 Configuring CNAME Records for Your Signal Genesys Whitelabel Domain

To activate your Signal Genesys whitelabel domain, add one CNAME record pointing a subdomain — such as news.yourdomain.com — to whitelabel.signalgenesys.io. The steps below work in cPanel alongside existing www, ftp, cpanel, and webmail records without modifying them; if images fail to load in your media room or press releases after adding the record, see the troubleshooting section. 🔗 What the Required CNAME Record Looks Like Add exactly one new CNAME record to your DNS zone. Do not modify or delete your existing www, ftp, cpanel, or webmail records — they are unrelated to this setup. - Host / Name: news — enter only the subdomain prefix, not the full domain (enter news, not news.yourdomain.com) - Type: CNAME - Value / Points to / Target: whitelabel.signalgenesys.io - TTL: 3600 (or your provider's default) Note: Some providers display existing records as full hostnames (e.g., www.yourdomain.com). That is a display difference only — always enter the subdomain prefix alone (news, never news.yourdomain.com) in the Name/Host field when adding your new record. Once saved and propagated, news.yourdomain.com will resolve through Signal Genesys and display your branded media room and press releases correctly. 💡 Why Existing Subdomain Records Do Not Conflict A DNS zone supports multiple CNAME records as long as each uses a different subdomain prefix. Your existing records occupy www, ftp, cpanel, and webmail — adding a new record under news (or any other unused prefix) creates a completely separate entry. You do not need to remove or change any existing records. ⚠️ Exception: If you already have an A or TXT record for the news subdomain, delete it before adding the CNAME — two different record types cannot share the same hostname. ⚙️ How to Add the CNAME Record in cPanel Use the Zone Editor in cPanel to add the record. cPanel automatically appends your domain to the host name, so enter only the subdomain prefix in the Name field. 1. Log in to your cPanel account. 2. Under the Domains section, click Zone Editor. 3. Find your domain (e.g., yourdomain.com) and click Manage. 4. Click + Add Record, then select CNAME as the record type. 5. In the Name field, enter news — cPanel appends .yourdomain.com automatically. 6. In the Record field, enter whitelabel.signalgenesys.io. (the trailing dot is optional but recommended to ensure the value is treated as fully qualified). 7. Leave the TTL at the default value. 8. Click Add Record to save. The new record appears immediately in your zone file list. DNS changes propagate within 30 minutes to 24 hours depending on your TTL setting. 🌐 How to Add the CNAME Record in Other DNS Providers If you manage DNS through a registrar or external provider such as GoDaddy, Namecheap, or Cloudflare, follow these steps: 1. Log in to your DNS provider's dashboard. 2. Go to DNS Management or DNS Records for your domain. 3. Click Add Record. 4. Set the Type to CNAME. 5. In the Host or Name field, enter news. 6. In the Value, Points to, or Target field, enter whitelabel.signalgenesys.io. 7. Save the record. ⚠️ Cloudflare users: Set the proxy toggle to DNS only (grey cloud icon) for this CNAME record. Enabling the Cloudflare proxy (orange cloud) prevents Signal Genesys from resolving your domain correctly. After saving, allow up to 24 hours for full DNS propagation across all regions. 🛠️ Troubleshooting: Images Not Displaying in the Media Room or Press Releases Broken or missing images in Signal Genesys are almost always caused by a missing, incorrect, or not-yet-propagated CNAME record. Work through these checks in order. 1. Verify the CNAME value - Confirm the Points to / Target field is set to exactly whitelabel.signalgenesys.io — no trailing slash, no extra spaces or characters. - Confirm the Host / Name matches the subdomain you entered in Signal Genesys whitelabel settings (e.g., both must use news). 2. Check for a conflicting A record - In your DNS zone, check whether an A record or a duplicate CNAME already exists for the same prefix (e.g., news). A conflicting A record overrides your CNAME and breaks resolution. - If one exists, delete it, then re-save your CNAME record. 3. Confirm propagation is complete - Go to dnschecker.org and search for your full subdomain (e.g., news.yourdomain.com) as a CNAME record type. - You should see whitelabel.signalgenesys.io returned from multiple global locations. If results are still propagating, wait 1–2 hours and check again. 4. If images still fail to load after 48 hours - Hard-refresh your browser using Ctrl+Shift+R (Windows) or Cmd+Shift+R (Mac). - Clear your CDN cache if you use one in front of your domain. - Open Zone Editor and confirm no duplicate or conflicting record exists for the news subdomain. - Contact support with a screenshot of your DNS zone if the issue persists. Once the CNAME is correct and fully propagated, reload your media room or press release page. Images display automatically — no further changes are needed inside Signal Genesys. ✅ How to Verify Your Signal Genesys CNAME Is Active Use a command-line lookup or a free DNS tool to confirm the record is live globally before contacting support. Option A: Use dnschecker.org 1. Go to dnschecker.org. 2. Enter your full whitelabel subdomain (e.g., news.yourdomain.com). 3. Select CNAME as the record type. 4. Click Search. Option B: Use the dig command - From a terminal, run dig news.yourdomain.com CNAME (replace news.yourdomain.com with your full subdomain). - A successful result returns whitelabel.signalgenesys.io in the answer section. Expected propagation time - Records with a 3600-second TTL typically propagate within 1–2 hours. - Full global propagation can take up to 24–48 hours depending on TTL and upstream resolver caching. A successful result shows whitelabel.signalgenesys.io in the response from the majority of global DNS servers. If you see your domain's IP address or an empty result, return to your DNS provider, verify the record values against the table above, and allow additional propagation time. 🎯 You now know how to add the Signal Genesys whitelabel CNAME record in cPanel and any other DNS provider, without modifying your existing subdomain records. If you need help connecting and verifying your whitelabel subdomain inside the Signal Genesys platform after DNS is configured, see the Signal Genesys Whitelabel Setup Guide.

Access Your White-Label Domain and Client Reports

Overview When you set up a white-label domain in Search Atlas, visiting the root URL (for example, app.youragency.com) lands you on the /register page by default. This page displays an "invitation required" message because self-registration is intentionally disabled for white-label portals. This is expected behavior — it is not an account error or an access problem. To log in, you and your clients must always navigate to the explicit /login path. This article explains how to reach the login page and how to share the correct entry point with clients. Why the Root URL Shows "Invitation Required" White-label portals are closed environments. The default landing page (/register) blocks open sign-ups to protect your client workspace. Because there is no way to bypass this message from the register page, going directly to the root domain will always produce this result. This is by design and does not indicate any problem with your account or domain configuration. How to Log In to Your White-Label Domain 1. Open your browser and go to your white-label domain followed by /login. For example: app.youragency.com/login 2. Enter your Search Atlas credentials (email and password). 3. Submit the login form. You will be taken directly into your white-label portal. Tip: Bookmark yourdomain.com/login and share this exact URL with every client. Never share the root domain URL on its own. How to Get a Client's Report URL for Iframing Once you are logged in to your white-label portal, navigate to the specific client report you want to share or embed. 1. Open the client project whose report you want to share. 2. Navigate to the specific report you want to embed. 3. Copy the full URL from your browser's address bar. This is the URL you will use as the src value in your iframe code. 4. Ensure the client accessing the iframe is already authenticated at yourdomain.com/login before loading the embedded report. Unauthenticated users will be redirected to the login page. Sharing Access With Clients When inviting clients to view their reports through your white-label portal, always send them: - The direct login URL: yourdomain.com/login - Their individual login credentials so they can authenticate before accessing any report links If you need further assistance setting up your white-label domain or retrieving report URLs, please reach out to our support team via the chat widget in your Search Atlas dashboard.