Website Studio

🔗 Create Multiple URL Paths for Campaign Tracking

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

🛠️ Fix Website Studio AI Credit Loss Issues

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

🌐 Website Studio Wix Integration and Feature Roadmap

What Is Website Studio? Website Studio is Search Atlas's built-in website builder. It lets you create and manage web pages directly within the Search Atlas platform without leaving your workflow. Does Website Studio Connect with Wix? Website Studio and Wix are separate platforms. The specifics of what is currently supported — including any syncing, publishing, or integration capabilities between the two — have not been confirmed in detail. If you are trying to use a particular integration capability and are unsure whether it is supported, our team can clarify based on your specific use case. What Features Are Coming Soon? The Search Atlas team is actively working on expanding Website Studio's capabilities. Because this area is actively evolving, specific feature details and timelines are not yet confirmed. Our support team can share the latest information relevant to your use case. What to Have Ready When You Contact Support To help our team give you the most accurate and relevant information, please have the following ready: - Your Search Atlas project name or account email - A description of the specific Website Studio or Wix integration capability you are trying to use or understand - Any error messages or unexpected behavior you have encountered, including approximate timestamps If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛡️ Safely Deploy Website Studio

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

🔍 Understanding GBP Service Landing Pages

📘 What the recommendation means A GBP service landing page recommendation identifies a website page that can better explain one of your services. The page gives customers and search engines useful details about the service, location, benefits, and how to take the next step. This recommendation is separate from the Services section in your Google Business Profile (GBP). It does not mean Google can place a website landing page directly inside that section. 🌐 Where the landing page is published When you choose to create the recommended page, Search Atlas opens the page creation workflow in Website Studio with the service and Brand Vault context available. You can review, edit, and publish the page to your connected website. 1. Open OTTO SEO from the left sidebar. 2. Select All Sites and choose the relevant site. 3. Review the GBP recommendation for the service. 4. Choose the page creation option to open Website Studio. 5. Review the content, make any changes, and publish it to your website. The page is published on your website, not inserted into the GBP Services section. 📍 How the page supports your GBP After publication, the landing page can support your local presence by giving customers a relevant destination for that service. Depending on your GBP setup and available Google features, you may be able to add the website URL to appropriate service, post, update, or profile content manually. Google controls which fields and links are available in a Business Profile. Search Atlas cannot force a landing page into a GBP section that does not support direct page placement. 🧭 Why this section appears The recommendation exists to connect your GBP services with useful, service-specific website content. A service name in GBP and a dedicated page on your website serve different purposes: - GBP Services: Lists the services your business offers within your profile. - Service landing page: Provides detailed information on your website and can target relevant local searches. A recommendation may appear even when a page cannot be added directly to the Services section because the page still strengthens the website content supporting that service. ✅ Before publishing - Confirm the service is actually offered. - Check that the page uses the correct business name, location, and contact details. - Review the content for accuracy and brand consistency. - Avoid creating duplicate pages for services that already have suitable landing pages. Search Atlas uses service matching to help identify existing pages and reduce unnecessary recommendations. Review each suggestion before creating a new page. 💬 Need help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔗 Linking Landing Pages to GBP Services

🗺️ Overview Search Atlas does not automatically publish or insert landing pages directly into your Google Business Profile (GBP) Services section. Instead, the integration works in two complementary ways: your GBP service data helps inform and populate landing pages built in Website Studio, and the Landing Page Missing for Service alert helps you identify gaps in your local SEO coverage. Understanding this distinction will help you get the most out of both tools. ⚙️ How GBP Data Powers Website Studio When you connect your Google Business Profile to Search Atlas, your GBP Services data is pulled into the platform and used as a foundation for generating landing pages in Website Studio. Here is what that means in practice: - Each service listed in your GBP (for example, Roof Repair or Emergency Plumbing) can be used as the basis for a dedicated landing page. - Service names, descriptions, and categories from GBP pre-populate relevant fields in the page builder, saving you time and keeping your content consistent. - Google Reviews from your GBP can also be auto-embedded into generated pages using the GBP Review Widget, adding social proof automatically. This connection makes it faster to build location- and service-specific pages that align with what Google already knows about your business. 🚨 What Does 'Landing Page Missing for Service' Mean? The Landing Page Missing for Service alert appears in Search Atlas when a service exists in your GBP but does not yet have a corresponding landing page built in Website Studio. It is a gap-detection feature, not a publishing tool. Its purpose is to: - Highlight missed opportunities — If a service is listed in GBP but has no dedicated landing page, you may be missing organic traffic for that keyword. - Guide your content strategy — The alert acts as a to-do list, showing you exactly which services still need pages created. - Improve local SEO coverage — Dedicated landing pages for each service help search engines understand the full scope of what your business offers. The alert does not insert a page into GBP, modify your GBP Services section, or publish anything to Google on your behalf. 📋 How to Link a Landing Page to a GBP Service Follow these steps to resolve a Landing Page Missing for Service alert and connect a page to a GBP service: 1. Go to Website Studio in the Search Atlas left-hand navigation. 2. Click Create New Page and select the relevant service from your connected GBP as the page topic, or enter the service name manually. 3. Build and publish the landing page. Once published, Search Atlas associates the page with that service and the alert is resolved. 4. Copy the published page URL from Website Studio. 5. Log in to your Google Business Profile dashboard at business.google.com. 6. Navigate to Edit Profile → Services, find the relevant service, and paste your landing page URL into the service description or use it in a GBP Post to drive traffic to the page. This manual step in GBP is currently required because Google does not provide an API endpoint that allows third-party tools to directly edit the URL field within the Services section. 💡 Best Practices - Create one landing page per GBP service — This maximises your ranking potential for each service keyword. - Keep service names consistent — Match the landing page title to the exact service name in GBP for stronger relevance signals. - Use the GBP Review Widget — Enable auto-embedded reviews on your landing pages to build trust and improve conversions. - Check the Missing Page alerts regularly — Resolve them promptly as you add new services to your GBP. - Promote pages via GBP Posts — Sharing your landing page URLs as GBP Posts increases visibility and drives clicks from your Business Profile. ❓ Frequently Asked Questions Will Search Atlas ever publish pages directly to GBP Services? Google's current API does not support writing URLs directly into the GBP Services section from third-party platforms. If this changes, Search Atlas will update the integration accordingly. Why does the alert disappear after I build a page? Once Website Studio detects a published page associated with a GBP service, it marks that service as covered and removes the alert from your dashboard. Can I connect a page I built outside of Website Studio? Currently, the alert resolution is triggered by pages created and published within Website Studio. Externally built pages will not automatically clear the alert. 🙋 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔗 Linking Website Studio Pages to GBP Services

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

💡 Fix Website Studio Credit Balance Errors Explained

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

🖼️ SVG Alt Text in Onpage Audit Explained

🔍 What Is the Onpage Audit Flagging? When you run an Onpage Audit in Search Atlas, the tool scans every image on your page — including SVG (Scalable Vector Graphics) files. If an SVG element is missing an alt attribute, the audit flags it as an actionable task, just like it would for a standard JPG or PNG image. You may notice that some of these SVG images do not display a visual preview inside the audit task panel. This is expected behaviour. SVGs are code-based graphics, and the platform may not render a thumbnail for every SVG type. The task is still valid and worth addressing. 📋 Why Alt Text Matters for SVG Images Alt text serves two important purposes: - Accessibility: Screen readers use alt text to describe images to visually impaired users. Missing alt text on SVGs can make your page non-compliant with accessibility standards such as WCAG 2.1. - SEO: Search engines read alt text to understand image content. While SVGs are often used for icons or decorative elements, providing descriptive alt text helps search engines index your page content more accurately and can contribute to image search visibility. 💡 What Alt Text Should You Write for an SVG? The right alt text depends on the purpose of the SVG on your page. Use the guidance below to decide: - Informative SVG (charts, diagrams, illustrations): Write a concise description of what the image communicates. For example: "Bar chart showing monthly organic traffic growth from January to June 2025." - Functional SVG (logos, buttons, icons that link somewhere): Describe the action or destination. For example: "Search Atlas logo — link to homepage" or "Download report icon." - Decorative SVG (purely visual, adds no information): Use an empty alt attribute: alt="". This tells screen readers to skip the image, which is the correct approach for decoration-only graphics. Keep alt text under 125 characters, avoid phrases like "image of" or "graphic of," and include a relevant keyword naturally if it fits the context — do not force it. ⚠️ Will Skipping SVG Alt Text Hurt My SEO? Yes, leaving SVG alt text empty or absent can have a negative impact in several ways: - Missed ranking signals: Search engines cannot interpret the SVG content without alt text, so you lose a potential on-page optimisation opportunity. - Accessibility penalties: Poor accessibility can indirectly affect SEO. Google has stated that it values pages that are usable by all visitors. - Audit score: Unresolved alt text tasks will continue to lower your Onpage Audit score in Search Atlas, which affects your overall site health rating. Addressing these tasks is a quick win that improves both your SEO performance and the experience for all users visiting your site. 🛠️ How to Fix SVG Alt Text Issues 1. Open your Onpage Audit report in Search Atlas and locate the task flagging missing alt text on an SVG image. 2. Visit the page in question and identify the SVG — check your page source or CMS if the preview is not visible in the audit panel. 3. Determine whether the SVG is informative, functional, or decorative (see the guidance above). 4. Add the appropriate alt attribute directly in your HTML, CMS, or page builder. For decorative SVGs, add alt="". For all others, write a descriptive, keyword-relevant phrase. 5. Save your changes, re-crawl the page, and re-run the Onpage Audit to confirm the task is resolved. ✅ Quick Reference: Alt Text Cheatsheet - Informative SVG: Describe the content clearly and concisely. - Functional SVG: Describe the action or link destination. - Decorative SVG: Use alt="" (empty, not missing). - All cases: Keep it under 125 characters and avoid keyword stuffing. 💬 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.

🛠️ Landing Page Templates and Layout Limitations Explained

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

🛠️ Fix Website Studio Site Cap Plan Mismatch

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

🌐 Website Studio Rendering, Meta Tags, and Embeds

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

Connect a CMS and Add Meta Tags in Website Studio

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

Website Studio Access, Availability, and Release Details

🗓️ When Is Website Studio Available? Website Studio is a new Search Atlas feature. If you are unable to locate Website Studio in your dashboard, it may not yet be live on your account or may not be included in your current plan. Availability and release timing vary by account — to get confirmed details specific to your account, please use the support contact method at the bottom of this article. 📋 Which Plans Include Website Studio? Website Studio is included in all paid Search Atlas plans (Starter, Growth, Pro, and Agency). It is not available inside white-label child accounts. If you have any questions about access on your account, please contact the support team directly. 🧭 How to Access Website Studio Once Website Studio is confirmed as available on your account, you can access it from the left sidebar → Website Studio. If you do not see it after logging in, try the following steps first: 1. Log out of your Search Atlas account and log back in to refresh your session. 2. Reload the dashboard page. 3. If Website Studio still does not appear, confirm you are on a paid plan (Starter, Growth, Pro, or Agency) and not signed in to a white-label child account — otherwise, contact support to confirm your access status. ❓ Why Can't I Find Website Studio? Website Studio may not be visible in your dashboard for the following reasons: - The feature may not yet be live for your account. - You may be signed in to a white-label child account, where Website Studio is not available. - You may be on a free plan rather than a paid plan (Starter, Growth, Pro, or Agency). We apologise for any confusion caused by unclear or contradictory information about release timing or plan inclusion. 🔍 What to Have Ready When You Contact Support To get the fastest, most accurate answer about Website Studio availability for your account, please have the following ready before reaching out: - Your Search Atlas account email address - Your current plan name (visible on your account or billing page) - A brief description of what you see — or do not see — when you log in to your dashboard If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🧱 Website Studio in Search Atlas

The Website Studio in Search Atlas allows users to generate high-quality landing pages directly inside the platform, without coding or external tools. From the Agentic Homepage (the main AI hub of Search Atlas, accessible from the top navigation), users can follow three clear creation paths depending on their goal: freeform generation, PPC-aligned landing pages, or cloning an existing website. This tool is designed to accelerate page creation while keeping everything connected to your SEO, Smart Ads, and performance workflows. 📍 How to Access Website Studio From the Left Sidebar in Search Atlas: ➡️ Website Studio You’ll land on the Landing Pages dashboard, where all generated, cloned, and drafted pages are stored and managed. 🚀 Three Ways to Create a Landing Page 1️⃣ Generate a Landing Page (Free Mode) Use this option when you want to create a landing page from scratch using AI. Path: - Open Website Studio - Click Generate Landing Page - Describe what you want to build in the prompt - Generate and review the page This flow is ideal for: - SEO landing pages - Campaign experiments - Rapid page creation without dependencies Note: Blog post creation via free-mode prompting is not yet available in Website Studio. Currently, blog content must be authored in Content Genius and imported. Native blog drafting directly from the chat panel is coming soon and currently awaiting release. Note: A direct Publish-to-Website-Studio button inside Content Genius is awaiting release and will replace the manual import step once live. 2️⃣ Generate a PPC Landing Page (Smart Ads Sync) This flow connects directly to Google Ads campaigns created in Smart Ads. Smart Ads is Search Atlas's ads management module, supporting both Google Ads and Meta (Facebook/Instagram) Ads — see the Smart Ads overview article for setup instructions. Path: - Website Studio → Generate PPC Site - Select: - Google Ads account - Business - Campaign - Click Generate The system auto-populates landing page content aligned with the selected campaign. Best for: - Conversion-focused PPC campaigns - Consistent messaging between ads and landing pages - Faster launch of paid traffic funnels Currently supported verticals: - Local - E-Commerce - SaaS - Webinar/Event - Lead Gen Coming soon: App Install, Online Course, Healthcare, Financial Services, and Real Estate. Note: Website Studio is a frontend-only tool and does not support e-commerce functionality, server-side logic, or third-party cart integrations (e.g., Shopify Add-to-Cart). For cart-driven campaigns, link the CTA button to an external product or checkout URL instead. 3️⃣ Clone an Existing Page This option lets users recreate the structure and design of an existing website or page. Path: - Website Studio → Clone an Existing Page - Enter: - Brand website (used to learn colors, fonts, tone) - Page to copy (optional – can be your own or a competitor’s) - Click Generate Landing Page If no page URL is provided, Search Atlas generates a fresh layout based on the brand site. 📂 Managing Your Landing Pages All generated pages appear in the Landing Pages dashboard. You can: - View Drafts and Published pages - Sort by Last Edited - Filter by Website - Open pages to review or publish - Clone existing generated pages again Each page card shows: - Page title - Status (Draft / Generated / Published) - Creation method (PPC, Free Mode, Clone) URL slug constraints: Website Studio supports flat URL paths only (e.g., /schedule-demo). Nested paths (e.g., /meetings/schedule-demo) are not supported. Use hyphens to approximate hierarchy (e.g., /meetings-schedule-demo). URL slugs must be changed via the Page Settings panel — AI prompts cannot modify slugs. ⚠️ Known Limitations Website Studio generates frontend-only pages and does not support server-side modifications or e-commerce integrations (e.g., Shopify cart redirects, dynamic product pages). For cart-linked CTAs, link buttons manually to an external URL in the Page Settings panel. ⏳ Page Generation State While a page is being created, users see a loading state: “Preparing your Landing Page” This indicates the AI is assembling layout, copy, and structure before the page becomes editable. 🧭 What You See Inside the Builder Navigation Path Left Sidebar → Website Studio → Select a project Once you open a project in Website Studio, the builder is split into two main working areas. On the left side, you’ll see the AI conversation panel where Atlas generates, updates, and responds to page-building requests. This is where prompts, generation messages, and editing actions appear. In this same area, users may also see status messages such as “ATLAS is generating your page”, “Restoring environment, please wait…”, or “Container not ready…” while the environment loads. On the right side, you’ll see the live preview canvas. This is where the page render appears once the development environment is ready. When the preview is still loading, the canvas may show messages like “Your preview will show here as soon as it's ready” or “Starting development environment…”. This layout makes it easy to prompt on the left and immediately review the visual output on the right. 🎛️ Builder Controls in the Top-Right Corner

🌐 Website Studio Hosting, DNS, and Feature Guide

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

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

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

🚫 Noindex Specific Pages in Website Studio

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

🔒 Add an SSL Certificate to Your Landing Page

🌐 Overview SSL (Secure Sockets Layer) certificates encrypt the connection between your landing page and your visitors' browsers. When SSL is active, your page loads over https:// and displays a padlock icon in the browser — building trust and improving SEO signals. This article walks you through adding an SSL certificate to a landing page hosted through Search Atlas. ✅ Before You Begin Make sure you have the following ready before starting: - A custom domain that you own and can manage DNS records for. - Access to your domain registrar or DNS provider (for example, GoDaddy, Namecheap, or Cloudflare). - Your landing page already created inside Search Atlas. - Admin-level access to your Search Atlas account. 🗺️ Step 1: Navigate to Agency Hub Settings SSL configuration for landing pages is managed through the Agency Hub section of the platform. 1. Log in to your Search Atlas account. 2. In the header, click the apps-grid icon. 3. Select More Features, then click Agency Hub. You will land on the /agency-settings page. 4. Locate the White Label Setup section at the top of the page. 🔗 Step 2: Connect Your Custom Domain Your SSL certificate is tied to your custom domain. If you have not already connected a domain to your landing page, complete this step first. 1. Inside White Label Setup, find the field labelled Custom Domain. 2. Enter the full domain or subdomain you want to use (for example, pages.yourdomain.com). 3. Save your changes. Once your domain is saved, Search Atlas will display the DNS records you need to add at your domain registrar. Copy these values carefully — you will need them in the next step. ⚙️ Step 3: Add DNS Records at Your Domain Registrar Log in to your domain registrar or DNS provider and add the records provided by Search Atlas. Typically, you will need to add one or more of the following record types: - CNAME record — points your subdomain to the Search Atlas hosting address. - A record — points your root domain to the Search Atlas IP address (if applicable). After adding the records, save them in your DNS provider. DNS changes can take anywhere from a few minutes to 48 hours to propagate globally, though most updates complete within 1–2 hours. 🔒 Step 4: Enable SSL on Your Landing Page Once your DNS records have propagated and Search Atlas detects your connected domain, SSL provisioning begins automatically. 1. Return to Header apps-grid icon → More Features → Agency Hub (/agency-settings) in Search Atlas. 2. Under White Label Setup, check the status of your domain. When the domain is verified, you will see a confirmation indicator. 3. Search Atlas will automatically provision a free SSL certificate for your connected domain using a trusted certificate authority. 4. Once issued, your landing page will be accessible over https:// with a valid padlock in the browser. No manual certificate upload is required — the process is fully automated once your domain is verified. 🔍 Step 5: Verify Your SSL Certificate Is Active After provisioning is complete, confirm SSL is working correctly: - Open your landing page URL in a browser using https:// at the start of the address. - Check that the browser shows a padlock icon in the address bar. - Click the padlock to view certificate details and confirm the certificate is valid and issued for your domain. - If the browser shows a security warning, DNS propagation may still be in progress — wait an additional hour and try again. ⚠️ Troubleshooting Common Issues - SSL not provisioned after 24 hours: Double-check that your DNS records match exactly the values shown in Search Atlas. Extra spaces or incorrect record types are common causes of failure. - Browser still shows http://: Clear your browser cache and try again, or test in an incognito window. - Domain not verified: Use a free DNS lookup tool (such as dnschecker.org) to confirm your CNAME or A record is resolving correctly before contacting support. - Mixed content warnings: Ensure all images, scripts, and links on your landing page also use https:// URLs. 💬 Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚡ 2-Click Optimized Landing Page Creation

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

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

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

🏷️ Add Meta Tags and Content to Website Studio Sites

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

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

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

🚀 Deploying Websites Created with Website Studio

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

⚡ Client Access & Permissions in Website Studio

Overview When a client is used to logging directly into WordPress, the idea of moving to Website Studio can feel like losing control. The good news: Website Studio supports white-label client accounts with a branded experience, permission controls, and a managed setup that many clients find easier than raw WordPress access. This article explains what is available so you can reassure your client and get them set up confidently. White-Label Client Accounts Website Studio includes white-label functionality that lets you create a branded experience for your client. Instead of seeing Search Atlas branding, your client can see your agency's identity. To explore how to configure this for your specific project, navigate to your project within Website Studio and look for the client access or sharing settings available there. Once access is granted, your client will receive an invitation to log in to their branded dashboard. From their perspective it can look like your agency's own platform rather than a third-party tool. Permission Settings for Client Accounts Website Studio allows you to control what your client can see and do inside the platform. Permission levels typically range from read-only or review access up to broader editing and publishing rights, depending on how much autonomy you want to give the client at each stage of a project. To review or adjust the permissions available for a client account, navigate to your project's settings within Website Studio and look for the client or access management options. If you are unsure which permission level is appropriate, or if the options available do not match your needs, reach out to our support team for guidance on what is currently supported. Transitioning Clients from Direct WordPress Access The most common concern is: "I won't have direct access to my own website." Here is a practical approach that keeps your client comfortable throughout the transition: 1. Keep WordPress accessible during the rebuild. Reassure your client that nothing is deleted until they have approved the new site. 2. Run a side-by-side review session. Share your screen or send a staging preview link so the client can compare both versions before going live. 3. Grant client access early. Invite the client into Website Studio before the full handoff so they can get comfortable with the interface while you are still available to guide them. 4. Walk through the editing experience together. Show the client how to make common updates such as changing text or swapping images so they feel confident managing the site independently. 5. Confirm the client is satisfied before deprecating WordPress. Only retire the old setup once the client has signed off on the new site and feels comfortable with their level of access. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔑 Give Clients Access to Website Studio

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

🌐 Website Studio Availability and Release Timeline

🔍 What Is Website Studio? Website Studio is a Search Atlas feature that lets you build and manage websites directly inside the platform. It is designed to streamline your workflow by combining SEO tools and web publishing in one place. 📋 Which Plans Include Website Studio? Website Studio is not available on the Starter Plan. Access to this feature depends on your current subscription tier. If you are on a Starter Plan, you will not see Website Studio in your navigation, and this is expected behaviour — not a bug or a display error. To use Website Studio, you will need to upgrade to a plan that includes it. The plans that include Website Studio access are: - Grow Plan — includes Website Studio - Pro Plan — includes Website Studio - Agency Plans — includes Website Studio If you are unsure which plan you are currently on, you can check your subscription details in your account settings. 🗺️ Where to Find Website Studio in the Platform If your plan includes Website Studio, you can access it by following these steps: 1. Log in to your Search Atlas account. 2. Look at the left sidebar navigation menu. 3. Click Website Studio from the sidebar options. 4. You can also navigate directly using the URL path /website-studio within the platform. If you are on an eligible plan and still cannot see Website Studio in your sidebar, try refreshing your browser or clearing your cache before reaching out for support. ⚙️ Why Can't I See Website Studio in My Navigation? There are two common reasons why Website Studio may not appear in your main navigation or features section: - Your plan does not include it. Starter Plan subscribers do not have access to Website Studio. The feature will not appear in your sidebar or anywhere else in the platform until you upgrade. - Your browser needs a refresh. If you recently upgraded your plan, the sidebar may not update immediately. A hard refresh (Ctrl + Shift + R on Windows, or Cmd + Shift + R on Mac) usually resolves this. 🚀 How to Get Access to Website Studio If you want to unlock Website Studio, upgrading your plan is the straightforward path. Here is what to do: 1. Click your avatar in the top-right corner of the platform. 2. Select Billing, then open the Plans & Top-ups tab (Billing). 3. Review the available plans and select one that includes Website Studio. 4. Complete the upgrade process. 5. Once the upgrade is confirmed, refresh your browser and Website Studio will appear in your left sidebar. 💡 Frequently Asked Questions Will Website Studio ever be added to the Starter Plan? There are no current announcements confirming that Website Studio will be added to the Starter Plan. Feature availability across plans is subject to change, so keep an eye on product update announcements inside the platform. Is Website Studio a new feature still being rolled out? Website Studio is available now for eligible plan subscribers. If you are on a qualifying plan and still do not have access, open the chat widget for assistance. 🛠️ 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.

🔗 Embed Kit Signup Forms in Website Studio

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

🛠️ Website Studio Rendering, SSR, and Code Access Explained

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

🔄 Website Studio Token Refunds for Failed Requests

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

🗺️ Create Unique Slugs for Location Pages in Website Studio

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

🌐 Publish Website Studio Pages to WordPress Safely

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

🌐 Publish Website Studio Pages to WordPress

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

🌐 Website Studio JS Site Crawlability and LLM Indexation

Your Website Studio site is built to be crawlable by Google and Search Atlas. LLMs like Claude, ChatGPT, and Gemini use crawlers that do not execute JavaScript, so they may not read JS-rendered pages. A previous rendering issue affecting JS-hosted pages on custom subdomains has been resolved — if you experience blank-page crawl results, verify your site is on the latest version. 🔍 How Search Atlas Confirms Your JS Site Is Crawlable Both Site Audit and Site Explorer in Search Atlas support JavaScript rendering, allowing them to crawl your Website Studio site exactly as Google does. Google's Rich Results tool has also been confirmed to crawl and process the site successfully. To verify crawlability yourself, run a Site Audit on your domain with JavaScript rendering enabled. JavaScript rendering is not on by default — you must enable it manually in Site Auditby going to OTTO SEO → Site Audit → Select your project→ OTTO Settings→ Crawl Parameters→ Toggle on JavaScript Rendering. A clean audit with no JS-rendering errors confirms your site is fully accessible to search engine crawlers. Note: For sites using pixel or manual-script OTTO installation, Site Audit title data may not always reflect OTTO-deployed titles in real time. For the most accurate live-state verification, cross-check results with Google Search Console or Google's Rich Results tool. 🤖 Why Claude, ChatGPT, and Gemini Cannot Crawl Your JavaScript Site LLMs like Claude (Anthropic), ChatGPT (OpenAI), and Gemini (Google) use lightweight HTTP crawlers that do not execute JavaScript. When these tools request a JS-rendered page, they receive only an empty HTML shell — making the page appear uncrawlable or blank to them. This is primarily a limitation of those external tools. That said, a previous architectural issue caused JS-hosted pages on custom subdomains to return a near-empty HTML body (with only a title, meta description, and a 'JavaScript Required' notice) to all bots — this has been resolved (LPS-864). If you still see blank crawl results, ensure your site is on the latest version. Additionally, if your site appears in Google under a Search Atlas domain rather than your custom domain, this is a known issue (now resolved, LPS-911) — please contact support if you encounter it. - Google and Bing — execute JavaScript and index your site normally. - Search Atlas Site Audit and Site Explorer — JavaScript rendering must be enabled manually in Site Audit settings (Settings → Crawl Settings → JavaScript Rendering); once enabled, your site is fully crawlable. - Claude, ChatGPT, and Gemini web browsing — no JavaScript execution; these tools cannot read JS-rendered pages. 🔗 Why Search Atlas Preview URLs Appear in Google Search Results If you see Search Atlas preview URLs appearing in Google search results for your domain, this is a temporary indexation delay. Google crawled and cached the preview URL before your live pages were fully indexed. These entries clear automatically once Google indexes the correct live pages for your domain. To speed up this process, submit the affected pages for indexing directly through your OTTO project. Note on og:url and canonical tags: Your og:url and canonical tags should reflect your custom domain. If the Search Atlas builder subdomain appears in og:url or canonical tags, please contact support — this was a known bug (LPS-864) that has been resolved. ⚙️ How to Submit Pages for Indexing via OTTO 1. Open Search Atlas and navigate to the OTTO project for the affected domain. 2. Identify the specific pages where Search Atlas preview URLs are appearing in Google. 3. Select those pages and click Submit for Indexing. 4. Google will prioritize re-crawling those URLs and replace any cached preview entries with your live pages. Once Google processes the indexing requests, the Search Atlas preview URLs will no longer appear in search results for your domain. 🛠️ Troubleshooting: Site Audit Still Shows Blank Pages or JS Errors 1. Confirm JavaScript rendering is toggled on in Site Audit settings (Settings → Crawl Settings → JavaScript Rendering). 2. Re-run the crawl after any OTTO deployment so the audit reflects the latest live state. 3. Verify your custom domain's canonical and og:url tags point to your custom domain — not the Search Atlas origin or builder subdomain. 4. If blank pages persist after these steps, contact support so the issue can be investigated.

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

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

⚙️ JavaScript SEO & Website Studio Crawlability

JavaScript can block crawlers, delay rendering, and hurt rankings — but only when misconfigured. This guide explains how JavaScript affects SEO, what the Search Atlas Site Auditor flags, and how to confirm your Website Studio site is correctly crawlable and indexed. 💡 What Is JavaScript SEO? JavaScript SEO is a branch of technical SEO focused on ensuring JavaScript-powered websites are fully crawlable, renderable, and indexable by search engines. While JavaScript enhances user experience, poor implementation can slow page load or block crawlers — both of which hurt rankings. ⚙️ How JavaScript Impacts SEO JavaScript influences key technical SEO elements, including: - Page load times - Metadata - Links - Rendered content - Lazy-loading images When JavaScript is improperly implemented, it can: - Prevent crawlers from rendering content correctly - Slow page loading speeds (hurting rankings and increasing bounce rates) - Block critical content from search engines — a practice known as cloaking Because Googlebot needs access to all resources to render pages accurately, blocking JavaScript or dependent assets can cause indexing errors. 🔍 How to Tell If Your Website Uses JavaScript - View Page Source — Right-click anywhere on the page and select "View Source." Search for "javascript" using Ctrl + F. - Inspect Elements — Check for interactive features like drop-down/fly-out menus, pop-ups, dynamic content, or animations. - Check your CMS settings to confirm whether JS rendering is enabled. 🧠 How Google Handles JavaScript Google processes JavaScript in three stages: 1. Crawling – Googlebot requests the page's HTML. 2. Rendering – Google's Web Rendering Service (WRS) processes JavaScript to generate the visible content. 3. Indexing – Once rendering is complete, the resulting HTML is indexed. Rendering JavaScript can be delayed because of crawl budgets and WRS queue limits — meaning not all scripts are guaranteed to execute promptly. 📊 Why the Site Auditor Checks for JavaScript When you run a Site Auditor report, it flags pages with large or inefficient JavaScript files that affect load speed, responsiveness, and crawlability. Performance and structure are both essential ranking factors in SEO, so identifying and resolving these issues can significantly improve your site's health. 🚨 Common JavaScript SEO Issues - Indexing Problems – Crawlers may fail to index JS-rendered content if it's not properly configured. - Content Duplication – Duplicate server-side and client-side content can result in SEO penalties. - Slow Loading Speeds – Heavy JavaScript files cause delays that impact user experience and rankings. - Crawlability Issues – If bots can't access JavaScript or linked resources, your content won't be indexed. This includes external AI crawlers (Claude, ChatGPT) and Google Rich Results testing tools, which require JS rendering to be properly enabled. - Preview URL Indexation – For Search Atlas Website Studio sites, preview URLs may temporarily appear in Google search results while your primary domain pages are still pending indexation. 🛠️ How to Fix Common JavaScript Issues 1️⃣ Indexing - Structure and format your code properly. - Remove unnecessary characters or scripts. - Ensure all external scripts are properly linked. - Minimize render-blocking resources. 🌐 Website Studio: Verifying JavaScript Crawlability If you've built your site with Search Atlas Website Studio and want to confirm it's crawlable by Google and external AI tools (such as Claude or ChatGPT), follow these steps: 1. Confirm JS rendering is enabled in your Website Studio project settings. Internal Search Atlas crawlers and Googlebot both rely on this for full page rendering. 2. Test with Google Rich Results – Use Google's Rich Results Test to confirm Google can crawl and render your live domain (e.g., https://yourdomain.com/). A successful test confirms Googlebot has full access to your rendered content. 3. Verify with external AI tools – If Claude or ChatGPT cannot fetch your URL, the issue is typically related to JS rendering or robots/firewall settings, not the content itself. Confirm your domain isn't blocking these user agents. 4. Escalate to Support – If crawlability issues persist, contact Search Atlas support. Our team can verify crawlability on your live domain directly and confirm the configuration end-to-end. 🔗 Why Search Atlas Preview URLs Appear in Google Search Customers occasionally notice that Search Atlas preview URLs (used for staging Website Studio sites) appear in Google search results instead of, or alongside, their primary domain. This usually does not indicate a misconfiguration. Most common cause: Some pages on your primary domain are still pending indexation by Google. Until Google fully indexes your live domain, the preview URL may continue to surface in search results. How to resolve: - Open your OTTO project for the affected site. - Submit the pages for indexing directly inside OTTO. This accelerates Google's discovery of your live domain URLs. - Allow time for Google to process and index the submitted pages. Once indexed, preview URLs should drop out of search results in favor of your primary domain. - Confirm your primary domain is set as the canonical destination in your Website Studio settings. If preview URLs persist in Google's index after several weeks of completed indexation on your live domain, contact Search Atlas support for further investigation. 🎯 You now understand how JavaScript affects crawlability, what the Site Auditor flags, and how to resolve Website Studio indexation issues. If problems persist after following these steps, contact Search Atlas support for direct assistance.

🚀 Using the Instant Indexing Toggle in Landing Page Studio

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

🌐 Choosing a Language & Page Type

Set the language your article is written in and the kind of page you're creating — both shape how Content Genius structures and writes your content. Before you generate, pick a language and a page type in the composer. The language controls what your article is written in; the page type controls its structure, depth, and how it's marked up for search engines. 🧭 Where to set them Both options live in the composer on the Content Genius home, alongside the Brand Vault and length pickers. Navigation: Left sidebar → Content → Content Genius → composer 🌐 Supported languages Content Genius writes and optimizes articles end-to-end in the following languages. Choose the one that matches your audience — including the regional variant, which affects spelling and phrasing. | Language | Regions | | --- | --- | | English | United States, United Kingdom, Australia, Canada | | Spanish | Spain, Mexico | | Portuguese | Portugal, Brazil | | French | France | | German | Germany | | Italian | Italy | | Dutch | Netherlands | Pick from the supported list. Choosing a language or region outside the ones above will stop generation. If your target language isn't listed yet, use the closest supported option. ⚙️ How the language is chosen If you don't pick a language, Content Genius decides for you in this order: 1. Your choice in the composer — always wins if you set it. 2. Your Brand Vault's voice language — used if you didn't choose one. 3. US English — the default if neither is set. 📄 Page types The page type tells Content Genius what kind of content to build. It shapes the article's structure and the behind-the-scenes markup that helps search engines understand the page. Choose the one that matches your goal: | Page type | Best for | | --- | --- | | Blog post | General articles and topic coverage (the default). | | Commercial / pillar | Broad, authoritative pages that anchor a topic and link to related articles. | | How-to guide | Step-by-step instructions to complete a task. | | Comparison | Side-by-side comparisons of options, products, or approaches. | | Service page | Pages that describe a service you offer. | | Product review | Evaluations and reviews of a product. | | Recipe | Food and recipe content with the right structure. | | Landing page | Focused, conversion-oriented pages. | | Informational | Explainers and reference content. | Not sure which to pick? Start with Blog post. You can always create a new article with a different page type, or ask Atlas to restructure the content in the editor. ❓ Frequently Asked Questions Can I change the language after the article is generated? Yes. In the editor, ask Atlas to change the article's language. It will translate and adapt the content for you. Why did my generation stop when I chose a language? The language or region you selected isn't supported yet. Choose one from the supported list above and try again. What's the difference between the regional variants of English? They control spelling and phrasing conventions — for example, US, UK, Australian, and Canadian English differ in spelling ("optimize" vs "optimise") and wording. Pick the one that matches where your audience is. Does the page type change how the article ranks? The page type sets the right structure and search-engine markup for your content, which helps search engines understand and display it correctly. Choose the type that genuinely matches your page's purpose. Next steps & related: Generating an Article · Editing with the Atlas Agent · Using Brand Vault with Content Genius

🛠️ Integrate Website Studio with WordPress

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

🏠 WordPress + ShowcaseIDX vs Website Studio Costs

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

🖼️ Edit Your OpenGraph Image in Website Studio

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

🖼️ Updating the OpenGraph Image in Website Studio

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

🖼️ Website Studio OG Image Editing Limitations Explained

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

🌐 Connect Your Website to Website Studio

🖥️ What Is Website Studio? Website Studio is Search Atlas's built-in web builder that lets you create, manage, and optimise websites directly inside the platform. Before you can build or edit pages, you need to connect your website to a Website Studio project. If you are setting up a site for the first time, follow the steps below — you do not need an existing project link or project ID. 🔍 Before You Begin Have the following ready before you start: - Your website's full URL (for example, https://zelenkadevelopment.com/) - Access to your domain's DNS settings or hosting control panel (needed if you want to publish changes live) - An active Search Atlas account with Website Studio enabled 🚀 How to Connect a New Website 1. Open Website Studio. In the left sidebar, navigate to Website Studio (located at /website-studio). 2. Start a new project. On the Website Studio section, look for the option to create or add a new project. Select it to begin the setup flow. 3. Enter your website URL. When prompted, type your full website address — for example, https://zelenkadevelopment.com/ — and proceed to the next step. 4. Name your project. Give the project a recognisable name, such as your brand or client name, so you can find it easily later. 5. Complete the connection. Follow the remaining on-screen prompts to finish the setup process. Depending on your site's size, the initial load may take a few minutes. 6. Confirm your project is active. Once setup is complete, your new project will appear in Website Studio with your URL listed. Open the project to begin working on your site. 🌍 Publishing Changes to Your Live Site After connecting your website, changes you make inside Website Studio are saved in the platform and are not automatically pushed to your live domain. To push updates live, follow the publishing options available within the editor. You may need a DNS or hosting connection configured depending on your setup. If you need help configuring your DNS or hosting connection, consult your hosting provider's documentation or contact their support team. For further assistance with connecting your website to Website Studio, please contact the Search Atlas support team via the chat widget in the bottom-right corner of the platform.

🛠️ Website Studio Sitemap & Noindex Bug Fixes

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

📍 Manage Location and Service Page Templates

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

🚀 Remove Navigation from PPC Pages

🎯 Why PPC pages have no navigation Search Atlas PPC landing pages created with Website Builder or Landing Page Studio use a conversion-focused layout. PPC mode removes traditional header and footer navigation by design, including menus, dropdowns, navigation links, and external page links. The page keeps only the logo and primary conversion call to action. This prevents visitors from leaving the page and helps campaigns stay focused on one goal. ⚙️ How navigation is removed 1. Open the landing page in Website Builder or Landing Page Studio. 2. Use the page’s PPC layout or PPC mode. 3. Publish or update the page. When PPC mode is applied, the builder does not add a nav element, menu list, dropdown, or standard header links to the page. 🔍 How to verify the page 1. Open the published landing page in a private or incognito browser window. 2. Check the header and footer for navigation menus and extra links. 3. Confirm that the logo and primary conversion CTA are the only header elements required for the PPC layout. 4. Test the CTA to make sure it leads visitors to the intended conversion step. 🛠️ If links still appear First, confirm that you are viewing the published PPC page rather than an older URL, preview, cached version, or non-PPC page template. Clear the browser cache or open the page in a private window, then publish the latest version again if needed. If navigation still appears after these checks, review whether the page was created with Website Builder or Landing Page Studio and whether the PPC layout is active. Standard website pages may include navigation, while PPC pages are specifically designed not to. 💬 Need help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.