Onboarding
By Camilo Aponte
By Camilo Aponte
🔗 How to Connect Google Analytics to Your Dashboard
How to Connect and View Google Analytics Reports
📊 How to Connect Google Analytics to Your Account
🔗 Connect Google Integrations for Multiple Clients
🌐 Overview If you manage SEO for multiple clients, Search Atlas lets you connect separate Google Search Console (GSC), Google Analytics 4 (GA4), and Google Business Profile (GBP) accounts to each client workspace. This article explains how the company-selection step works so every client's data stays correctly linked. 🏢 How Multi-Client Google Integrations Work Search Atlas is built around a workspace-per-client model. Each client you manage has its own workspace, and Google integrations are connected at the workspace level — not at a global account level. This means you must select the correct company or property after switching into the relevant client workspace. When you authenticate with Google, you are granting Search Atlas access to all properties available under your Google account. The company or property selector then appears so you can choose exactly which GSC site, GA4 property, or GBP location belongs to the client you are currently working on. 🔍 Connecting Google Search Console and GA4 1. From the left sidebar, navigate to Site Metrics (Site Explorer) (URL: /site-explorer/list). 2. Open or create the project for the client you want to connect. 3. Click Open Google Search Console and, on the GSC Sites List page, click Connect GSC Account (or the equivalent option, Connect GA Account). 4. Sign in with the Google account that has access to the client's properties. 5. After authentication, a property selector dropdown will appear — this is where you choose the specific client site or GA4 property from the list. 6. Select the correct property and click Confirm. 7. Repeat these steps for each client by switching workspaces first. Important: If you do not see the property selector, refresh the page and reconnect. The dropdown only appears after a successful Google authentication handshake. 📍 Connecting Google Business Profile (GBP) 1. From the left sidebar, navigate to Local → GBP Projects (URL: /gbp-galactic/gbp-projects). 2. Open the GBP project for the relevant client, or create a new one. 3. Click Connect Google Business Profile. 4. Authenticate with the Google account that manages the client's GBP location. 5. A location selector will appear listing all business locations available under that Google account. 6. Select the correct business location for this client and click Confirm. Once connected, GBP data will populate across Local → Overview, Local → Reviews, and other sub-pages within that project. 💡 Tips for Managing Many Clients - Always switch workspaces first before connecting or changing a Google integration — this ensures the property is linked to the right client. - If a client's Google account is separate from yours, use the Sign in with a different account option during the Google authentication step. - You can reconnect or change a linked property at any time by returning to the same settings area and clicking Reconnect. - Each workspace stores its own integration credentials independently, so updating one client's connection will never affect another. 🛠️ WordPress Plugin Installation The Search Atlas WordPress plugin allows you to sync on-page SEO data directly from your client's website. Follow these steps to install it: 1. Log in to the WordPress admin dashboard for the client's website. 2. Go to Plugins → Add New → Upload Plugin. 3. Upload the Search Atlas plugin .zip file provided by Search Atlas. 4. Click Install Now, then click Activate. 5. Once activated, go to the plugin settings page and enter your Search Atlas API key. You can find your API key inside your Search Atlas account under your profile settings. 6. Save the settings. The plugin will now sync your site data with your Search Atlas workspace. Note: Make sure the API key you enter belongs to the same Search Atlas workspace as the client project you want to connect. Using a mismatched key is the most common reason the plugin does not sync correctly. ❓ Frequently Asked Questions - I authenticated with Google but no property selector appeared. — Refresh the page and try reconnecting. If the issue persists, make sure the Google account you used actually has access to the client's GSC, GA4, or GBP properties. - Can I connect the same Google property to multiple workspaces? — Yes, the same property can be linked to more than one workspace if needed. - The plugin installed but data is not syncing. — Verify the API key is correct and that the plugin is activated. Also check that your server can make outbound HTTPS requests. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.
✨ How to Activate AI Summary in Report Builder
📋 Overview The AI Summary feature in Report Builder allows you to automatically analyze your report data and surface the most important insights, trends, and highlights. Instead of manually reviewing every metric, you can use this built-in AI tool to get a clear, concise narrative of what your report is telling you — saving time and making it easier to share findings with clients or team members. 🔍 How to Access Report Builder To get started, navigate to Report Builder using the left sidebar: 1. Click Reports in the left sidebar. 2. You will land on the projects list at /report-builder/projects-list. 3. Select an existing report you want to analyze, or create a new one by clicking + Create. ✨ How to Activate the AI Summary Once you have a report open, follow these steps to activate the AI Summary: 1. Open the report you want to analyze from your projects list. 2. Open the report (Executive Summary) and look for the Refresh Summary / AI Settings options within the report view — these are typically located at the top of the report canvas or within the report settings panel. 3. Click Refresh Summary to trigger the analysis. The AI will process the data currently loaded in your report. 4. Wait a few moments while the AI reviews your metrics, identifies trends, and generates a written summary of your report's key highlights. 5. Review the generated summary, which will outline the best-performing areas, notable changes, and any data points worth calling attention to. 💡 What the AI Summary Analyzes The AI Summary is designed to help you quickly understand the story behind your data. It typically highlights: - Top-performing metrics and what is driving positive results. - Significant changes or trends observed across the reporting period. - Areas of concern that may need attention or further investigation. - Standout wins that are worth featuring when presenting to clients or stakeholders. 📤 Sharing and Using Your AI Summary Once your AI Summary is generated, you can use it in several ways: - Include it as an executive summary at the top of client-facing reports. - Use the insights to prepare talking points for strategy meetings or reporting calls. - Download your report as a .CSV using the Download .CSV action and pair it with the summary for a complete data package. - Set up Automated email reports so your clients or team members receive reports with AI-generated summaries on a regular schedule. ⚠️ Troubleshooting Common Issues If you run into issues activating the AI Summary, consider the following: - No data loaded: The AI Summary requires data to be present in your report. Make sure your report has at least one data source connected and that the date range includes available data. - Outdated data: Click the Refresh data action in Report Builder to ensure the AI is analyzing the most current metrics. - Feature not visible: Confirm that your current plan includes access to AI features. Navigate to top-right corner avatar → Billing → Plans & Top-ups tab to review your subscription and available features. - Slow generation: Large reports with many data points may take a few extra moments to process. Allow the AI time to complete its analysis before clicking again. 🙋 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.
🔗 Reconnecting Google Search Console in Search Atlas
🔍 Overview If you have connected your Google account to Search Atlas but cannot select the correct Google Search Console (GSC) property — or the connection is not working as expected — this guide walks you through the steps to resolve the issue quickly. ⚠️ Common Causes of This Issue - Your Google account lost authorization and needs to be reconnected. - You are signed into the wrong Google account in your browser. - The GSC property you need is owned by a different Google account than the one you connected. - Permissions on the GSC property were changed or revoked after the initial connection. 🛠️ Step 1: Disconnect Your Current Google Account Before reconnecting, remove the existing Google authentication to start fresh. 1. Click your profile icon or account settings in the top-right corner of Search Atlas. 2. Navigate to the Integrations or Connected Accounts section. 3. Find the Google Search Console connection and click Disconnect or Remove. 4. Confirm the disconnection when prompted. 🌐 Step 2: Check Which Google Account You Are Using This is the most common reason customers cannot find the right property. Your GSC property must be accessible from the Google account you connect. - Open a new browser tab and go to search.google.com/search-console. - Confirm you are signed in with the Google account that owns or has access to the property you want to use. - If you see the correct property listed in GSC, you are using the right account. If not, switch Google accounts before proceeding. 🔄 Step 3: Reconnect Google Search Console 1. Return to Search Atlas and navigate to Site Metrics → Site Explorer → Open Google Search Console (Manage Sites page). 2. Click Connect GSC Account. 3. A Google sign-in window will appear. Select the correct Google account — the same one that has access to your GSC property. 4. When prompted, grant all requested permissions. Search Atlas requires read access to your GSC data to display metrics correctly. Do not uncheck any permission checkboxes. 5. Click Allow to complete the authorization. 📊 Step 4: Select Your GSC Property Once the account is reconnected, you should be able to choose your property. 1. Navigate to Left sidebar → Site Metrics → Site Explorer. 2. Open the project or site you want to link to GSC. 3. In the GSC property selector, click the dropdown and look for your property in the list. 4. Select the correct property and save your settings. If the property still does not appear in the dropdown, confirm the following: - The property is verified in Google Search Console (not pending verification). - You connected the Google account that has Owner or Full User access to that property — Restricted User access may limit what Search Atlas can retrieve. - The property URL format matches exactly — for example, https://www.example.com and https://example.com are treated as separate properties in GSC. 💡 Tips to Avoid This Issue in the Future - Always use the same Google account to manage both your GSC properties and your Search Atlas connection. - If you change GSC property ownership or permissions, reconnect the integration in Search Atlas afterwards. - Avoid revoking Search Atlas app permissions from your Google account settings, as this will break the connection. 🙋 Still Need Help? If you have followed all the steps above and still cannot connect or select your GSC property, If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.
📍 Set Up Local Competitor Tracking and Reporting
📋 Overview Search Atlas allows you to monitor how your business stacks up against local competitors — not just search engines. This guide explains how to configure competitor tracking for local SEO and build reports that surface actionable insights for your market. 🏁 Before You Begin Make sure you have the following ready before setting up local competitor tracking: - At least one active Local project set up in Search Atlas - The business names or Google Business Profile names of your local competitors - A clear idea of the geographic area and keywords you want to track 📍 Step 1: Access Your Local Projects Navigate to your local setup by going to Left sidebar → Local → GBP Projects. This opens your GBP Projects dashboard at /gbp-galactic/gbp-projects. Select the project that corresponds to the business location you want to track competitors for. If you have not yet created a project for this location, set one up before continuing. 🔍 Step 2: Identify the Right Local Competitors Effective local competitor tracking starts with choosing the right businesses to monitor. Follow these guidelines when selecting competitors: - Focus on geographic relevance: Choose businesses that serve the same city, neighbourhood, or service area as your client. - Match business category: Select competitors in the same primary category on Google Business Profile. - Check local rankings: Use Left sidebar → Local → Local SERPs (Local Search Engine Results Page) to run keyword searches and see which local businesses appear in the top results for your target terms. - Aim for 3–5 competitors: This gives you a focused, manageable comparison set without diluting your reporting. 🛠️ Step 3: Add Competitors to Your Report Builder Once you have identified your competitors, add them to your reporting setup: 1. Open the Report Builder from your dashboard. 2. Locate the Competitors field or section within the report configuration panel. 3. Remove any pre-populated search engine entries if your goal is local competitor comparison rather than organic search engine benchmarking. 4. Enter the business names or URLs of your chosen local competitors. Use the exact name as it appears on their Google Business Profile for the most accurate matching. 5. Save your competitor selections before moving to the next step. Important: The Report Builder distinguishes between search engine competitors (used for organic ranking comparisons) and local business competitors (used for GBP and local visibility comparisons). Make sure you are editing the correct competitor field for local reporting. 📊 Step 4: Build Meaningful Local Competitive Reports With your competitors configured, build reports that tell a clear story about your local competitive position. Include the following data points for the most actionable insights: - Local keyword rankings: Compare how you and each competitor rank for your target local search terms. Pull this data from Left sidebar → Local → Local SERPs (Local Search Engine Results Page). - Review volume and rating: Track the number of reviews and average star rating for each competitor via Left sidebar → Local → Reviews (GBP Reviews). - Citation consistency: Use Left sidebar → Local → Local Citations to compare how well your NAP (Name, Address, Phone) data is distributed versus competitors. - Post activity: Check Left sidebar → Local → Posts to see how frequently competitors publish GBP content compared to your own cadence. - Media presence: Use Left sidebar → Local → Media Library to assess photo and media activity on your profile relative to competitors. 📅 Step 5: Schedule and Share Your Competitive Reports To turn competitor data into an ongoing reporting workflow: 1. Set your report to run on a monthly or weekly cadence so you can spot trends over time. 2. Add a competitive summary section to your report that highlights wins (areas where you outperform competitors) and gaps (areas needing improvement). 3. Share reports with stakeholders using the Report Builder's export or sharing options. 💡 Best Practices for Local Competitive Reporting - Revisit your competitor list every quarter — local markets change, and new businesses may enter your client's space. - Pair competitor ranking data with your own task list from Left sidebar → Local → My Tasks to prioritise actions that close competitive gaps. - Use the Overview page (Left sidebar → GBP Projects → Overview) as your starting point each reporting cycle to get a high-level snapshot before diving into competitive details. - Document baseline metrics when you first set up tracking so you can show progress over time. 🆘 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.
📘 Google Search Console Integration in Search Atlas
Connect Google Search Console to monitor your website's search performance, including keywords, impressions, and visibility. ⚙️ How to Connect 1. Go to Site Metrics → Site Explorer → GSC/Manage Sites. 2. Locate Google Search Console. 3. Click ➕ Connect GSC Account. 4. Log in to your Google account. 5. Approve permissions. 6. Select your verified property. 🎯 What You Can Do - Track keyword performance. - Monitor impressions and clicks. - Analyze search visibility. - Access SEO insights directly inside Search Atlas. ⚠️ Common Issues 1. Site not appearing — Make sure it's verified in GSC. 2. Wrong account — Use the correct Google account. 3. No data — Wait for sync or verify the property. ❓ FAQ Do I need to verify my site first? Yes, your site must be verified in Google Search Console. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.
🔄 Reconnect One GSC Property Safely
🧭 Overview If you deleted permissions or revoked access for a specific Google Search Console (GSC) property — such as Pulsebiohacking — you only need to reconnect that one property. Search Atlas manages each GSC connection independently, so re-authenticating a single property will not affect your other connected accounts. This article explains what to have ready so the affected property can be reconnected quickly without disrupting the rest of your GSC connections. ⚠️ Before You Reach Out - Confirm you are signed into the correct Google account that owns or has access to the specific GSC property you want to reconnect. - Make sure the old permissions for that property have already been fully revoked from your Google account, or are simply inactive on the Search Atlas side. - You do not need to disconnect or re-authenticate any of your other GSC properties — this process is scoped to a single property only. 🔑 Step 1: Gather the Required Information Before reaching out, have the following ready so your request can be actioned without delays: - The exact name of the disconnected GSC property (for example, Pulsebiohacking). - The Google account email address that owns or has verified access to that property in Google Search Console. - Approximately when the connection broke or permissions were revoked. 🔄 Step 2: Request the Property Reconnection The reconnection of the affected property is handled on the platform side. Have the details gathered above ready so the process can be completed without touching any of your other GSC connections. Be ready to: - Confirm which Google account should be used to authenticate the specific property being reconnected — especially important if you manage multiple Google accounts. - Confirm that you are happy to grant the necessary permissions for that property only. ✅ Step 3: Verify After Reconnection 1. Once the property has been reconnected, open the project for the affected property and confirm that GSC data is loading correctly. 2. Spot-check two or three of your other connected properties to confirm their data is unaffected and their connections remain intact. 🛡️ Why Your Other Connections Are Not Affected Search Atlas manages each GSC property connection independently. Reconnecting one property creates a new authentication scoped only to that property, leaving all other connections completely untouched. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.
🔗 Activate GSC Properties to Enable GSC Performance
🧭 Overview In Search Atlas, there are two separate steps required before you can use the Open in GSC Performance button for any website. First, you must connect your Google Search Console (GSC) account via OAuth. Second — and this is the step most users miss — you must individually activate each GSC property inside Search Atlas settings. Until a property is activated, the Open in GSC Performance button will remain greyed out, even if your GSC account is fully connected. 🔍 Why Is the Button Greyed Out? The Open in GSC Performance button is greyed out when a GSC property has not been activated in Search Atlas, regardless of whether your Google account is connected. Connecting your GSC account makes your properties visible to Search Atlas, but it does not automatically activate them. Activation is a deliberate, per-property step that must be completed for each site you want to use with GSC Performance. ✅ Step 1 — Connect Your GSC Account If you have not yet connected a Google Search Console account to Search Atlas, follow these steps first: 1. Go to Site Metrics → Site Explorer. 2. Click Open Google Search Console to open the Manage Sites page. 3. Click the Connect GSC Account button. 4. Complete the Google OAuth flow by signing in with the Google account that has access to your GSC properties. 5. Once authorised, your GSC properties will be imported and listed in Search Atlas. If you manage multiple Google accounts, you can repeat this process to connect each one. All properties associated with those accounts will be imported. ⚡ Step 2 — Activate Individual GSC Properties After connecting your GSC account, you must activate each property you want to use. This is the critical step that enables the Open in GSC Performance button. 1. Go to Site Metrics → Site Explorer → Open Google Search Console (Manage Sites page). 2. Find the list of imported properties. 3. Locate the property that corresponds to the website you want to use. 4. Toggle or click Activate next to that property. 5. Repeat for any other properties you want to enable. Once a property is activated, return to Site Explorer (left sidebar → Site Explorer) and the Open in GSC Performance button will now be available for that site. ⚠️ Common Issues and Fixes - Property not appearing in the list: Make sure the Google account you connected in Step 1 has at least Restricted-level access to the property in Google Search Console. Properties you do not have access to in GSC will not be imported. - Button still greyed out after activation: Refresh the page after activating the property. If the button remains greyed out, verify that the domain in Search Atlas exactly matches the property URL in GSC — including whether it uses http, https, www, or a domain-level property format. - Connected the wrong Google account: Disconnect the incorrect account from the Manage Sites page (Site Metrics → Site Explorer → Open Google Search Console) and reconnect using the Connect GSC Account button with the Google account that owns or has access to the target GSC property. - Multiple GSC accounts: If your sites are spread across different Google accounts, connect each account separately. All imported properties will appear in the same activation list. 📋 Quick Reference — Connection vs. Activation - Connecting a GSC account: Links your Google account to Search Atlas and imports all accessible properties. This is a one-time setup per Google account. - Activating a GSC property: Enables a specific property for use within Search Atlas tools, including the Open in GSC Performance button. This must be done individually for each property you want to use. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.
🔍 Connect Google Search Console Properties to Search Atlas
🗺️ Overview Search Atlas integrates with Google Search Console (GSC) in two separate places: the Integrations panel and individual Projects. Connecting your GSC account in Integrations makes all your properties available to Search Atlas — but each Project must be individually linked to the specific property you want to report on. This is the most common reason customers see nine properties in Integrations yet only one appearing inside a Project's GSC module. 🔗 How the Two Connections Work Understanding the difference between these two connection points will save you time: - Integrations (account-level): This is where you authorise Search Atlas to access your Google account. All GSC properties tied to that Google account become visible here. This is a one-time setup. - Project (property-level): Each Project must be individually mapped to one GSC property. The Project only pulls data from the single property you assign to it — it does not automatically inherit all properties from your Integrations account. ⚙️ Step 1 — Verify Your GSC Account Is Connected in Integrations 1. Go to Site Metrics → Site Explorer → Open Google Search Console (Manage Sites page) and click Connect GSC Account. 2. Confirm that your Google account is connected and that all nine properties are listed and showing a healthy status. 3. If any property is missing here, log in to Google Search Console and confirm that your Google account has access to that property, then return to the Manage Sites page and reconnect your account via Connect GSC Account. 📊 Step 2 — Link a GSC Property to a Specific Project 1. From the left sidebar, go to Home and open the Project you want to configure. 2. Inside the Project, locate the GSC / GA module (sometimes labelled Google Search Console). 3. If the module shows a Connect Google Search Console prompt even though your account is already connected in Integrations, click the prompt — this simply means the property has not yet been assigned to this Project, not that your account is disconnected. 4. A property selector will appear listing all GSC properties available under your connected Google account. Select the exact property that matches this Project's website (e.g. https://example.com/ or sc-domain:example.com). 5. Save the selection. The Project will now pull GSC data exclusively from that property. 🔄 Step 3 — Repeat for Each Project If you manage nine websites and want GSC data inside each Project, you must complete Step 2 for every Project individually. Each Project stores its own property mapping independently. This design ensures that data from different websites is never mixed within a single reporting view. 💡 Common Issues and Fixes - "Connect Google Search Console" still appears after connecting: This is a known display behaviour. Click the prompt anyway — your account credentials are already stored, and clicking will take you straight to the property selector rather than asking you to re-authorise. - A property is missing from the selector inside the Project: The selector only shows properties tied to the Google account connected in Integrations. If a property belongs to a different Google account, go to Integrations, add that second Google account, and then return to the Project selector. - Data is not refreshing after linking: GSC data can take up to 24 hours to populate after a property is first linked. Use the Refresh data button on the Home screen to trigger an immediate sync where available. - Domain property vs URL-prefix property: Google Search Console offers two property types. Make sure the property type shown in the selector matches the one you verified data for inside Google Search Console itself. ✅ Quick Checklist - Google account connected in Integrations ✓ - All expected properties visible in Integrations ✓ - Correct GSC property selected inside each individual Project ✓ - Waited up to 24 hours for initial data sync ✓ 🆘 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.
🔗 Connect GSC and Analytics to Search Atlas Projects
🧭 Overview Connecting Google Search Console (GSC) and Google Analytics to your Search Atlas projects unlocks performance data directly inside the platform. If your GSC property dropdown appears empty or your Analytics accounts have been disconnected, this article walks you through what to check and how to escalate if needed. ⚠️ The Most Common Mistake: Wrong Starting Page The most frequent reason the GSC property dropdown appears empty is that customers attempt to connect GSC from the wrong location. The connection must be made from the top-right avatar (Account Menu) → Settings → Integrations. If you start from the wrong page, the dropdown will show no properties even if your Google account is fully authorised. ✅ How to Connect Google Search Console to a Project 1. Click the top-right avatar to open the Account Menu, then go to Settings → Integrations. 2. On the Integrations page, locate the Google Search Console connection area. 3. Follow the on-screen prompts to authorise your Google account if you have not done so already. 4. Once authorised, the property dropdown will populate with all GSC properties available in the connected Google account. Select the property that matches your project's domain. 5. Confirm the connection using the available option on that page. Important: If you navigate to the general projects list page and try to edit the connection from there, the property dropdown will remain empty. Always open the individual project first. ✅ How to Connect Google Analytics to a Project 1. Open the specific project by clicking into it from your projects list. Confirm you are on the project overview page. 2. Locate the Google Analytics connection area on the same overview page. 3. Follow the on-screen prompts to authorise your Google account when asked. 4. Select the correct Analytics account, property, and data stream from the dropdowns that appear. 5. Confirm the connection using the available option on that page. 🔄 Why Was My Google Analytics Account Disconnected? Google Analytics accounts can become disconnected for several reasons. The most common causes are: - Google OAuth token expired or revoked: If you removed Search Atlas from your Google account's authorised apps, or if the token expired, the connection will drop. - Google account password changed: Changing your Google account password can invalidate active tokens for connected third-party apps. - Google account permissions changed: If your access level to the Analytics property was reduced or removed by an admin, the connection may break. In all of these cases, reconnecting from the top-right avatar (Account Menu) → Settings → Integrations using the steps above should restore the connection. If you need further assistance, open 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 Google Search Console and Access Sitemap Data
🌐 What This Article Covers This guide walks you through finishing a Google Search Console (GSC) URL-prefix property connection and then accessing your sitemap data inside Search Atlas. If you have already verified ownership of your property in GSC, follow the steps below to bring that data into the platform. ✅ Step 1: Verify Your URL-Prefix Property in Google Search Console Before Search Atlas can read your sitemap data, your website must be verified in Google Search Console as a URL-prefix property. If you have not done this yet, complete these steps first: 1. Go to Google Search Console (search.google.com/search-console). 2. Click Add property and choose URL prefix as the property type. 3. Enter your full website URL, including https:// (for example, https://www.yoursite.com). 4. Choose a verification method — the HTML tag method is the quickest for most users — and follow the on-screen instructions. 5. Click Verify. Once GSC confirms ownership, your property is ready to connect. Important: Make sure the URL you enter in GSC exactly matches the URL you use in Search Atlas, including whether it has or does not have a trailing slash. 🗺️ Step 2: Submit Your Sitemap in Google Search Console Submitting your sitemap tells GSC which pages to crawl and index. Search Atlas reads this sitemap data once the connection is active. 1. Inside Google Search Console, open your verified URL-prefix property. 2. In the left sidebar, click Sitemaps. 3. Under Add a new sitemap, enter your sitemap path — typically sitemap.xml or sitemap_index.xml. 4. Click Submit. GSC will begin processing the sitemap. This can take a few hours to a few days. If you are unsure of your sitemap URL, try visiting https://www.yoursite.com/sitemap.xml in a browser. Most platforms such as WordPress, Shopify, and Wix generate one automatically. 🔗 Step 3: Connect Your GSC Property to Search Atlas Once your property is verified and your sitemap is submitted in GSC, connect the property to Search Atlas: 1. In the Search Atlas left sidebar, click Site Metrics. 2. Click Analyze or open a saved project for your website. 3. Follow the on-screen prompt to connect Google Search Console. You will be asked to sign in with the Google account that has access to the verified property. 4. Select the correct URL-prefix property from the list of available properties. 5. Confirm the connection. Search Atlas will begin pulling data from GSC. Note: Only properties where your Google account has at least full user permissions in GSC will appear in the selection list. 📊 Step 4: Access Sitemap Data in Search Atlas After the GSC connection is active, your sitemap and page data become available across several areas of Site Metrics: - Site Metrics → Pages — View individual URLs from your sitemap, their index status, and performance metrics pulled from GSC. - Site Metrics → Keywords — See which search queries are driving traffic to your sitemap pages. - Site Metrics → Overview — Get a high-level summary of impressions, clicks, and crawl coverage for the connected property. Navigate to any of these sub-pages using the left sidebar: Site Metrics → [sub-page name]. ⏱️ How Long Does Data Take to Appear? Data availability depends on two factors: - GSC processing time: After you submit a sitemap, Google may take anywhere from a few hours to several days to crawl and index your pages. Search Atlas can only display data that GSC has already processed. - Search Atlas sync time: Once your GSC property is connected, Search Atlas syncs data periodically. Allow up to 24 hours after a new connection for full data to populate. If metrics appear incomplete, check your sitemap status directly in GSC under Sitemaps to confirm Google has successfully processed it. 🛠️ Common Issues and Fixes - Property not appearing in Search Atlas: Confirm your Google account has full user or owner access to the property in GSC. Viewer-level access is not sufficient. - Sitemap shows errors in GSC: Review the error details in GSC under Sitemaps and fix any broken URLs or formatting issues before re-submitting. - URL mismatch: Ensure the URL in your GSC URL-prefix property and the URL entered in Search Atlas are identical — including https://, www, and trailing slashes. - No data after 24 hours: Disconnect and reconnect the GSC property inside Site Metrics, then allow another sync cycle to complete. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.
🏷️ Connect Google Tag Manager and GA4 to Search Atlas
🔍 What This Article Covers This guide explains the correct process for connecting Google Tag Manager (GTM) and Google Analytics 4 (GA4) to Search Atlas. These are two separate steps that are easy to confuse — GTM container setup happens entirely inside your GTM account, while GA4 property connection is configured inside Search Atlas. This article walks you through both clearly. ⚠️ Common Misconceptions to Avoid There is no Copy button and no tag code retrieval screen inside the Search Atlas Integrations dashboard. Search Atlas does not generate GTM snippets or tag IDs for you. If you were told otherwise, that information is incorrect. Your GTM container code (for example, GTM-PT8CD89P) comes from your own Google Tag Manager account, and your GA4 Measurement ID comes from your own Google Analytics 4 property. 📋 What You Need Before You Start - Access to your Google Tag Manager account at tagmanager.google.com - Access to your Google Analytics 4 property at analytics.google.com - Your GTM container ID (format: GTM-XXXXXXX) - Your GA4 Measurement ID (format: G-XXXXXXXXXX) - Admin or publish permissions in both Google accounts - Admin access to your Search Atlas workspace 🏗️ Step 1 — Set Up GA4 Tag Inside Google Tag Manager This step happens entirely in your GTM account. Search Atlas is not involved here. 1. Log in to tagmanager.google.com and open the container you want to use (for example, GTM-PT8CD89P). 2. In the left sidebar, click Tags, then click New. 3. Click Tag Configuration and choose Google Tag (or Google Analytics: GA4 Configuration if available in your account). 4. Enter your GA4 Measurement ID (G-XXXXXXXXXX) in the Measurement ID field. You can find this in your GA4 property under Admin → Data Streams → select your stream → Measurement ID. 5. Click Triggering and select All Pages so the tag fires on every page of your site. 6. Name the tag something clear, such as GA4 Configuration Tag, then click Save. 7. Click Submit in the top-right corner of GTM to publish your container. Without publishing, the tag will not fire on your site. 🌐 Step 2 — Add Your GTM Container Snippet to Your Website For GTM to work, the container snippet must be installed on your website. If it is already installed, skip this step. 1. In GTM, click Admin in the top navigation, then click Install Google Tag Manager. 2. Copy the two code snippets provided. Paste the first snippet as high as possible in the <head> of every page. Paste the second snippet immediately after the opening <body> tag. 3. If you use a CMS such as WordPress, use a plugin like Site Kit by Google or Insert Headers and Footers to add these snippets without editing code directly. 4. After installation, use the GTM Preview mode (click Preview in your GTM container) to confirm the container is firing correctly on your site before proceeding. 🔗 Step 3 — Connect Your GA4 Property to Search Atlas Once GTM is live on your site and your GA4 tag is publishing data, you can connect your GA4 property to Search Atlas. This is where Search Atlas configuration begins. 1. Log in to Search Atlas and click Site Metrics in the left sidebar. 2. If prompted to connect a property, follow the on-screen OAuth flow to authorise Search Atlas to access your Google Analytics account. 3. Select the GA4 property that corresponds to the site you are tracking. Search Atlas will use this connection to pull traffic and engagement data into your dashboards. 4. Once connected, data will begin populating in Site Metrics within 24–48 hours depending on your GA4 data volume. ✅ How to Verify Everything Is Working - In GTM: Use Preview mode to confirm your GA4 Configuration tag fires on All Pages with no errors. - In GA4: Go to Reports → Realtime and visit your site in a browser. You should see at least one active user appear within seconds. - In Search Atlas: Navigate to Site Metrics in the left sidebar and confirm traffic data is populating. If the property connection was recent, allow up to 48 hours for data to appear. 🛠️ Troubleshooting Common Issues - No data in Search Atlas after 48 hours: Disconnect and reconnect your GA4 property in Site Metrics using the OAuth flow. Confirm you selected the correct GA4 property (not a Universal Analytics property). - GTM container not firing on site: Double-check that both GTM snippets are installed correctly and that you have published the container (Preview mode alone does not send live data). - GA4 Realtime shows no users: Confirm the GA4 Measurement ID in your GTM tag matches the one shown in GA4 under Admin → Data Streams. - Wrong container ID: Your GTM container ID is found in GTM under Admin → Container Settings. It always starts with GTM-. 💬 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.
📧 Stop Email Reports From Deactivated Accounts
🔍 Why Am I Still Receiving Reports? Automated email reports are configured at the project level inside Search Atlas. When a user account is deactivated, any report schedules that were set up under that account — or that include that email address as a recipient — are not automatically removed. This means reports can continue to arrive in your inbox even after deactivation. The good news: you can remove unwanted recipients or delete the report schedule entirely in just a few steps. 🛠️ How to Stop Automated Email Reports Follow these steps from within any active Search Atlas account that has access to the affected projects. 1. In the left sidebar, click Reports. This takes you to the Report Builder projects list. 2. Locate the project whose report you want to stop. If you have multiple projects, repeat these steps for each one. 3. Click the Automated email reports option for that project. 4. In the automated report settings panel, review the list of recipient email addresses. 5. Remove any email addresses that belong to deactivated accounts (for example, addresses that are no longer active or no longer associated with your team). 6. If no active recipients remain, or if you no longer need the scheduled report at all, delete the report schedule entirely. 7. Save your changes. Repeat this process for every project that was linked to the deactivated accounts. ⚠️ Important Things to Know - Check all projects: A deactivated email address may be listed as a recipient on more than one project report. Work through each project in your Reports list to make sure none are missed. - Act from an active account: You must be logged in to a working Search Atlas account with the appropriate permissions to edit or delete report schedules. - Deactivation alone is not enough: Deactivating a user account does not automatically unsubscribe that address from scheduled reports. Always follow the steps above to remove the address manually. - External unsubscribe links: Clicking an unsubscribe link inside a report email stops delivery for that specific email address but does not remove the schedule for other recipients. Use the in-platform steps above for the most reliable result. ✅ Confirming the Change Worked After saving, the removed email addresses should no longer receive scheduled reports from Search Atlas. If a report is sent on its usual schedule and the deactivated addresses are no longer in the recipient list, no email will be delivered to them. Allow one full report cycle to confirm delivery has stopped. 💡 Best Practice: Review Reports Before Deactivating Users To avoid this situation in the future, make it part of your offboarding process to remove a departing team member's email address from all automated report schedules before deactivating their account. This keeps your report lists clean and prevents unwanted emails from leaving your workspace. 🆘 Still Receiving Unwanted Reports? If you have completed the steps above and are still receiving automated reports to a deactivated email address, or if you cannot locate the report schedule responsible, please reach out for additional 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.
🔗 Reconnect Your Google Search Console Account
Connecting your Google Search Console (GSC) account is essential for tracking keyword rankings and site performance. If you need to reconnect a specific property like Pulsebiohacking but are worried about interrupting your 20+ other active connections, this guide will walk you through the process safely. 🛠️ Steps to Reconnect Your Property You can easily update your GSC connection without losing your existing project data. Follow these steps to refresh your integration: 1. Navigate to Site Metrics: Open the left sidebar menu, click on Site Metrics, and view your saved projects. 2. Locate Your Project: Find the specific project you want to update from your list of saved projects. 3. Initiate Reconnection: Click on the project or select the option to analyze the domain. If the connection has dropped, you will see a prompt to re-authorize your Google account. 4. Complete the OAuth Prompt: You will be redirected to a secure Google sign-in page. Log in with the Google account associated with your Search Console. 🔒 Keeping Other Connections Intact When you reach the Google authorization screen, you do not need to worry about accidentally damaging your other active integrations. Google manages permissions at the account level, while Search Atlas organizes them by project. - Selective Authorization: If Pulsebiohacking is missing, ensure your Google account still has active administrative access to that specific property inside Google Search Console. - Session Security: Your other 20+ connections will remain secure and active in Search Atlas because they are tied to your overall authenticated Google session. - Independent Properties: Re-authenticating your session simply refreshes the token, allowing Search Atlas to pull fresh data for all permitted properties without overwriting your local settings. 💬 Scheduling a Live Walkthrough We understand that managing multiple integrations can feel overwhelming, and sometimes you just want an expert to look at your screen. While we do not schedule traditional external Zoom calls, our live support widget includes real-time screen-sharing capabilities. This allows our team to visually guide you through the exact reconnection steps for Pulsebiohacking exactly like a video conference. If you need further assistance, open 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 GA4 to OTTO in Search Atlas
🔍 Overview OTTO SEO uses your Google Analytics 4 (GA4) data to power traffic insights and on-page recommendations. If OTTO cannot detect your website in GA4 — even when Google Search Console (GSC) is already connected — a separate GA4 authorization step is usually the cause. This article walks you through the full connection process and the most common fixes. ⚙️ Before You Begin Confirm the following before attempting to connect GA4: - You have a GA4 property (not a Universal Analytics property) set up for your website. - Your Google account has at least Viewer-level access to the GA4 property. - GSC is already connected to Search Atlas (GSC and GA4 use separate authorization flows — connecting one does not connect the other). 🚀 How to Connect GA4 to OTTO 1. In the left sidebar, click OTTO SEO, then open All Sites (OTTO SEO Projects). 2. Select the website you want to configure, then open its OTTO Settings. 3. Locate the Google Analytics 4 section and click Connect GA4. 4. A Google authorization window will appear. Sign in with the Google account that has access to your GA4 property and grant the requested permissions. 5. After authorization, use the dropdown to select the correct GA4 property that matches your website. 6. Click Save. OTTO will verify the connection and begin pulling in GA4 data. 🛠️ Troubleshooting: OTTO Is Not Detecting My Website in GA4 If OTTO still cannot find your website after following the steps above, work through the checks below one at a time. - Wrong property type: Make sure you are using a GA4 property, not a legacy Universal Analytics (UA) property. UA properties are no longer supported. - Multiple Google accounts: If you manage several Google accounts, ensure you authorized with the account that actually owns or has access to the GA4 property containing your site. Sign out of all other Google accounts in your browser, then repeat the authorization. - Property not yet populated: A brand-new GA4 property can take 24–48 hours to register data. If your property was created recently, wait and try again. - Domain mismatch: The domain configured in OTTO (e.g., www.axsysdental.com) must match the data stream URL inside your GA4 property. Open GA4 → Admin → Data Streams and confirm the stream URL matches exactly, including or excluding www. - Insufficient permissions: Ask the GA4 property owner to verify your Google account has at least Viewer access under GA4 → Admin → Account Access Management. - Re-authorize the connection: If the connection was previously attempted but failed, click Disconnect in OTTO Settings, then reconnect from scratch using the steps in the section above. 💡 Key Difference: GSC vs. GA4 in OTTO A common point of confusion is that Google Search Console and Google Analytics 4 are connected independently. Connecting GSC to Search Atlas does not automatically authorize GA4. OTTO requires both connections to be completed separately before it can access the full range of data needed for its recommendations. 📊 Verifying a Successful Connection Once GA4 is connected correctly, you should see the following: - A green "Connected" status next to Google Analytics 4 in OTTO Settings. - Traffic metrics populated in the OTTO dashboard within a few minutes (historical data may take up to 24 hours to fully load). - GA4-based insights appearing alongside your GSC data in OTTO SEO. 🙋 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.
🔌 Activate GSC Properties for OTTO Integration
🔍 Overview If you can see a GSC property listed under Top-right avatar → Settings → Integrations but it does not appear as an option when setting up OTTO, the property has not yet been activated through Site Metrics. This activation step is required before OTTO can recognise and use the property. ⚙️ Why This Happens Connecting a GSC property in your integrations settings only links your Google account to Search Atlas. OTTO requires an additional activation step — the property must first be activated inside Site Metrics before it becomes available to select in OTTO. Skipping this step is the most common reason a property appears in integrations but not in OTTO. ✅ How to Activate Your GSC Property for OTTO 1. From the left sidebar, navigate to Site Metrics. 2. Locate the GSC property you want to use. If it is not already listed, add it by selecting it from the available options. Only properties connected under Top-right avatar → Settings → Integrations will appear here. 3. Once the property is listed in Site Metrics, open it to activate the property within Search Atlas. 4. After activation, return to OTTO SEO → All Sites (SEO Automation) using the left sidebar. 5. Open OTTO and attempt to add your property again. The GSC property should now appear in the available options list. 🛠️ Quick Troubleshooting Checklist - Property visible in integrations but not OTTO: Complete the Site Metrics activation steps above. - Property not visible in Site Metrics: Confirm the GSC account connected under Top-right avatar → Settings → Integrations has verified ownership of the property in Google Search Console. - Property activated but still missing in OTTO: Try refreshing your browser and re-entering the OTTO setup flow. Allow up to one minute for the change to propagate. - Multiple GSC accounts connected: Make sure the property you want belongs to the GSC account that is actively linked in your Search Atlas integrations. Properties from a different Google account will not appear. 📋 Key Things to Remember - Integrations settings and OTTO are not automatically in sync — the Site Metrics activation step is always required. - You only need to activate a property once. After the first activation it will remain available in OTTO for future use. - Any team member with the correct permissions can complete the activation on behalf of your organisation. 💬 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.
📊 How to Connect Google Analytics to Your Client Projects
Many users complete the Google Analytics integration at the account level and assume each client project is connected automatically. In Search Atlas, these are two separate steps. The account-level integration authorizes Search Atlas to access your Google Analytics data. After that, you still need to connect a specific Google Analytics property to each client project so the right data flows into the right dashboard. This guide walks you through connecting Google Analytics to your client projects once your account-level integration is already complete. ✅ Before You Begin Make sure the following are true: - You have completed the Google Analytics integration in your account settings. - You used a Google account that has access to the Google Analytics property you want to connect. - You are using Google Analytics 4 (GA4), which is the supported version. - You have at least one client project created in your workspace. 🤔 Why the Connection Is Separate The account-level integration is a one-time authorization. It tells Search Atlas which Google account to pull data from. A single Google account can have access to many Google Analytics properties, so Search Atlas cannot know which property belongs to which client. The project-level connection lets you map the correct property to each client project individually. 🔗 Step-by-Step: Connect Google Analytics to a Client Project 1. Log in to your Search Atlas Home. 2. Open the client project you want to connect from your list of projects. 3. Go to the project's Settings or Integrations area. 4. Locate the Google Analytics option and select Connect. 5. Because your account-level integration is already complete, you will not be asked to sign in again. Instead, you will see a list of available Google Analytics properties. 6. Select the GA4 property that belongs to this client. 7. If prompted, choose the correct data stream or view associated with that property. 8. Click Save or Confirm to finish. Once saved, Search Atlas begins importing data for that property. Repeat these steps for each client project you manage. 🔍 How to Confirm the Connection Worked After connecting, verify the data is flowing correctly: - Return to the project dashboard and open a report that uses Google Analytics data, such as traffic or conversions. - Allow a short time for the first data sync to complete. - Check that the metrics match what you see in your Google Analytics account for the same date range. 🛠️ Troubleshooting I don't see any properties to select This usually means the Google account used for the integration does not have access to the property you expect. Confirm that the connected Google account has at least Viewer access to the property in Google Analytics. If you recently gained access, reconnect the integration so the new permissions are recognized. The wrong property is showing data Open the project's integration settings, disconnect the current property, and reconnect using the correct GA4 property. Double-check the property name and ID against your Google Analytics account. I only see Universal Analytics properties Search Atlas supports Google Analytics 4. If you only see older Universal Analytics properties, create or select a GA4 property in Google Analytics, then return and connect it. No data appears after connecting Allow time for the initial sync. If data still does not appear, confirm the property is actively collecting data in Google Analytics and that you selected the correct date range in your report. If the issue continues, disconnect and reconnect the property. I saw a success message, but the property still isn't connected In some cases the Connect step could display a success message without fully completing the link to the project. This was a known issue that has since been resolved. If you run into stale connection state, refresh the project details page and reconnect the GA4 property so the connection registers correctly. The project still shows Google Analytics as "Not Connected" after I updated the property Previously, updating a GA4 property was not always reflected on the project details page, which could continue to show Google Analytics as not connected. This has been fixed. If the status still looks out of date, refresh the project details page so the updated property and connection state appear. ⚡ Connecting Multiple Projects Efficiently If you manage many client projects, connect each one individually using the steps above. The account-level integration only needs to be done once, so for every new project you simply select the matching property. Keeping a record of which Google Analytics property maps to each client makes this faster and reduces the risk of connecting the wrong data. 💬 Need More Help? If you have followed these steps and still cannot connect Google Analytics to a client project, reach out to our support team with the project name and the Google Analytics property you are trying to connect. Including these details helps us resolve your request quickly. Additional Notes Common Issues: If GA option is greyed out/missing, the account-level integration isn't complete yet. If the correct GA4 property doesn't appear in the dropdown, confirm the Google account used has access to that property. Also notes that once saved, Search Atlas pulls sessions, users, and traffic trends into the project dashboard.