Troubleshooting: GSC & GA4 Performance Data

🔍 GA4 Report Builder Date Range Discrepancy Explained

Overview If your GA4 metrics in Report Builder look slightly different from the numbers shown in your native Google Analytics 4 dashboard for the same 90-day period, you may be experiencing a known date boundary discrepancy. This article explains what is known about this issue and what to have ready when contacting support. The Reported Issue Users have reported that GA4 metrics in Report Builder do not match the metrics shown in their native GA4 dashboard when selecting an equivalent 90-day period. The discrepancy appears to be related to how each platform defines the end boundary of the Last 90 Days date range, though the exact technical cause requires investigation by our support team to confirm for your specific account. Possible Contributing Factors Date range discrepancies between integrated tools and native analytics platforms can occur for a number of reasons, including differences in how each platform handles the current day's data, time zone settings, or data processing delays. If you are seeing a metric mismatch, it is important to rule out these factors before assuming the integration is broken. What to Check Before Contacting Support Before reaching out, gather the following information so our team can investigate quickly: - Your project name in Search Atlas - The exact date range displayed in your Report Builder report - The exact date range you are comparing in native GA4 - A screenshot or description of the specific metrics that differ and by how much - Your GA4 property's time zone setting, if known Having this information ready will allow our team to identify the root cause and advise on next steps specific 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.

🔍 Fix Google Analytics Data Missing From Reports

🧭 Overview If your Search Atlas project report is not displaying Google Analytics data, the cause is almost always related to an incomplete connection, missing permissions, or a configuration mismatch between your Google Analytics account and your project settings. Follow the steps below in order to diagnose and resolve the issue. ✅ Step 1: Confirm Your Google Analytics Account Is Connected Before troubleshooting further, verify that a Google Analytics account has been linked to your Search Atlas workspace. 1. Log in to your Search Atlas account. 2. Click your profile icon or account name in the top-right corner. 3. Go to Settings and look for an Integrations or Connected Accounts section. 4. Confirm that Google Analytics appears in the list and shows a Connected status. If Google Analytics is not listed or shows a Disconnected or Error status, proceed to Step 2. If it shows as connected, skip to Step 3. 🔗 Step 2: Reconnect Your Google Analytics Account A broken or expired authentication token is one of the most common reasons data stops appearing. Reconnecting your account refreshes the access credentials. 1. In the Integrations section of Settings, click Disconnect next to Google Analytics if an entry exists. 2. Navigate to Site Metrics → Site Explorer (GSC Accounts page) and click Connect GA Account to follow the on-screen OAuth prompts. 3. Sign in with the Google account that owns or has Editor access to the Google Analytics property you want to use. 4. Grant all requested permissions when prompted — partial permission grants will prevent data from loading. 5. Once reconnected, return to your project report and wait up to 5 minutes for data to populate. 🏗️ Step 3: Verify the Correct Property Is Assigned to the Project Even if your Google Analytics account is connected at the workspace level, each project must be individually mapped to the correct GA property and view (for Universal Analytics) or data stream (for GA4). 1. Open the project that is missing data. 2. Click Project Settings (usually accessible via a gear icon or the project menu). 3. Locate the Google Analytics field and confirm a property is selected. 4. If the field is blank or shows the wrong property, click the dropdown and select the correct GA4 property or Universal Analytics view. 5. Save your changes and reload the report. If the dropdown is empty even though your account is connected, this typically means the authenticated Google account does not have access to any GA properties. Log in to Google Analytics directly to verify the account has the correct role assigned. 🔐 Step 4: Check Google Analytics Permissions Search Atlas requires at least Viewer level access to the Google Analytics property to read data. Editor or Administrator access is required if you also want to write annotations or manage settings. - Log in to your Google Analytics account at analytics.google.com. - Navigate to Admin → Property Access Management. - Confirm the Google account used to connect Search Atlas has a role of Viewer or higher on the relevant property. - If the role is missing or set to None, ask the property owner to update the permission, then reconnect the account in Search Atlas. 📅 Step 5: Check the Report Date Range Data will only appear for periods during which the Google Analytics connection was active and the property was receiving traffic. An incorrect date range can make it appear as if data is missing. - Open your project report and review the date range selector at the top of the page. - Set the range to a period when you know your site was receiving traffic, such as the past 30 days. - Confirm that Google Analytics was already connected to this project during the selected period. If you recently connected Google Analytics, historical data import may not be available depending on your plan. Only data collected after the connection was established will appear. ⏳ Step 6: Allow Time for Data Sync After connecting or reconnecting Google Analytics, Search Atlas needs time to pull and process your data. Sync times can vary based on the volume of data and current system load. - Wait at least 15–30 minutes after connecting before expecting data to appear. - For large properties with significant historical data, the initial sync may take longer. - Refresh your browser and reload the report after waiting. 🚫 Common Reasons Data Stays Missing - Wrong Google account used: The connected account does not have access to the intended GA property. - GA4 vs. Universal Analytics mismatch: Selecting a Universal Analytics view when your site uses GA4, or vice versa. - Expired OAuth token: Google authentication tokens can expire; reconnecting resolves this. - No data in GA itself: Verify the property is actively tracking data by checking your Google Analytics dashboard directly. - Ad blocker or browser extension interference: Test in a private/incognito window with extensions disabled if the UI behaves unexpectedly during the connection flow. 💬 Still Need Help? If you have completed all the steps above and Google Analytics data is still not appearing in your report, 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 GSC Performance 'Site Is Not Active' Error

Overview If your GSC Performance tool displays a Site is not active error, or your settings are not importing as expected, this guide will help you identify the cause and resolve it. In many cases, this error is temporary and clears on its own. Step 1: Wait and Refresh First Before taking any other action, note that this error can be caused by a temporary sync delay or a short-lived authentication issue between Search Atlas and the GSC API. These often resolve on their own. 1. Wait a few minutes without making any changes. 2. Hard-refresh your browser and check whether the error has cleared. If the error disappears after a refresh, no further action is needed. Step 2: Confirm Your GSC Property Is Verified If the error persists, confirm that the affected property is fully verified inside Google Search Console. 1. Open Google Search Console in a new tab. 2. Check that the property matching your domain appears in your property list. 3. Confirm its status is Verified and that you have Owner or Full User permissions on that property. If the property is unverified or you have restricted permissions, GSC will not authorise Search Atlas to pull data, which can trigger the Site is not active error. Step 3: Reconnect Your GSC Integration If the property is verified in GSC but the error still appears in Search Atlas, the connection between the two platforms may need to be refreshed. 1. In Search Atlas, locate the option to manage your GSC connection. 2. Disconnect your current GSC account. 3. Reconnect by re-authorising with the Google account that holds Owner access to the affected property. 4. Once reconnected, return to GSC Performance and allow some time for the data sync to complete before refreshing the page. Step 4: Re-apply Your Import Settings If your settings did not import correctly alongside the error, follow these steps after the connection is restored. 1. Open the GSC Performance tool from your Search Atlas dashboard. 2. Confirm the correct property is selected — make sure it matches the domain showing the error. 3. Re-enter any date range, filter, or dimension preferences you had configured. 4. Save your settings and verify that data is now loading correctly. Still Seeing the Error? If the error persists after completing all steps above, please reach out to our support team. To help us investigate quickly, have the following ready: the affected domain name, the exact error message you are seeing, and the approximate time the issue began. 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.

🔍 Diagnose Search Console Sync Failures and Traffic Drops

🧭 Overview A sudden drop in website traffic — for example, from 1,000–2,000 visits per day down to 40 — or a health report showing no data for your live site can be alarming. These issues are most commonly caused by a disrupted Google Search Console (GSC) data sync, a lapsed GSC connection, or a temporary data gap on our platform. This article walks you through how to diagnose the problem and get your data flowing again. ⚠️ Common Causes of Traffic Drops and Missing Data - GSC connection credentials expired or disconnected: If your Google account authorization lapses, Search Atlas cannot pull fresh data from Search Console. - Data sync delay or gap: Occasional gaps in GSC data can occur due to infrastructure updates. These are usually resolved automatically within 24–48 hours. - Under-reporting from the GSC data mirror: In some cases, our GSC data mirror may temporarily show lower numbers than your actual Search Console data. Always cross-reference with your Google Search Console dashboard directly. - No verified property in GSC: If your site is not verified in Google Search Console, Search Atlas cannot retrieve traffic or performance data for it. - Site not yet analyzed in Search Atlas: A health report will show no data if the site has not been crawled or added as a project. 🔎 Step 1 — Check Your GSC Connection Status 1. Log in to your Search Atlas account. 2. Navigate to Left sidebar → Site Metrics (URL: /site-explorer/list). 3. Select your website from the Saved Projects list. 4. Look for any warning or error banner indicating that GSC credentials are unavailable or that the connection needs to be re-authorized. 5. If you see a "Credentials Unavailable" message, proceed to Step 2 to reconnect your GSC account. 🔗 Step 2 — Reconnect Your Google Search Console Account 1. Go to your account settings or the GSC integration section within Search Atlas. 2. Click Disconnect next to your Google account, then click Connect GSC Account and follow the on-screen authorization prompts. 3. Make sure you grant all requested permissions so Search Atlas can read your Search Console data. 4. Once reconnected, return to Site Metrics and allow up to 24 hours for data to repopulate. 📊 Step 3 — Verify Your Site in Google Search Console Search Atlas relies on Google Search Console as its data source. If your site is not verified in GSC, no traffic data will be available. - Log in to Google Search Console and confirm your property is listed and verified. - Check that the property type (Domain vs. URL prefix) matches what is connected in Search Atlas. - If your site is not verified, follow Google's verification steps, then reconnect the property inside Search Atlas. 🕵️ Step 4 — Cross-Reference Data with Google Search Console Directly If your Search Atlas traffic numbers look unexpectedly low, always compare them against your actual Google Search Console dashboard: 1. Open Google Search Console and navigate to Performance → Search results. 2. Set the date range to match what you are reviewing in Search Atlas. 3. Compare total clicks and impressions. If GSC itself shows a drop, the issue originates with Google's data or a real traffic change — not a sync problem. 4. If GSC shows normal numbers but Search Atlas shows much lower figures, this may be a temporary under-reporting issue on our platform. Wait 24–48 hours and check again. 🛠️ Step 5 — Check the Health Report for Your Site If your health report shows no data for a live site, follow these steps: 1. Go to Left sidebar → Site Metrics and confirm your site appears under Saved Projects. 2. Navigate to OTTO SEO → Site Audit → Overview (Website Overview) and click the Recrawl Site button to trigger a fresh crawl. 3. Wait for the crawl to complete, then reload the health report. 4. If the site was recently added, allow up to a few hours for the initial crawl and health data to appear. 📅 Understanding Temporary Data Gaps Occasionally, short-term data gaps can appear in GSC performance graphs — including keyword position history or average position spikes. These gaps are typically caused by planned infrastructure maintenance or updates to our data pipeline. Key things to know: - Data gaps are usually resolved within 24–48 hours without any action needed on your part. - Historical data is backfilled once the sync is restored, so you will not permanently lose past records. - If a gap persists beyond 48 hours, contact our support team using the instructions below. ✅ Quick Diagnostic Checklist - GSC account is connected and credentials are valid in Search Atlas. - Site property is verified in Google Search Console. - Traffic drop is confirmed (or not) inside Google Search Console directly. - Site has been analyzed/crawled in Search Atlas. - Waited 24–48 hours after reconnecting GSC before checking for data. 💬 Still Need Help? If you have completed all the steps above and your data is still missing or your traffic figures remain unexpectedly low, our team is ready to investigate further. 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 GSC 'No Data Available' and OAuth Connection Errors

This article covers GSC data, GA4 analytics, OAuth connections, and date range issues. ⚠️ Error 1: GSC keyword data shows "No data available" What's happening: Your Google account may need to be reconnected, or the date range is out of bounds. Steps to try: - Go to Site Metrics → Site Explorer → Manage Sites (GSC Accounts page) → View X connected accounts (GSC) → Delete your account from the list → Refresh the page → + Connect New GSC Account → Select Your Account - Go to OTTO SEO → All Sites (SEO Automation) → Manage Sites → Ensure your site is "Active". - Make sure your date range doesn't exceed 16 months back — GSC data older than that is unavailable. - Don't select future dates — the end date must be yesterday or earlier. - If the connection is active and dates are valid, wait 5 minutes and refresh. ⚠️ Error 2: Google Analytics data shows "Data unavailable" What's happening: Google's Analytics API has daily request limits shared across all Search Atlas users. During peak hours, some requests are temporarily delayed. Steps to try: - Refresh during off-peak hours (early morning or late evening). - Narrow your date range — 30 days loads faster than 90 days. - Close and reopen the dashboard — analytics data is served from a cache that refreshes every few hours. - Reconnect your Google account to force a fresh token: Site Metrics → Site Explorer → Manage Sites (GSC Accounts page) → View X connected accounts (GSC) → Delete your account from the list → Refresh the page → + Connect New GSC Account → Enter/Select Your Account. - If no analytics data has appeared for 48+ hours, contact support with your GA4 property ID. ⚠️ Error 3: Only some GA4 tabs load — others show errors What's happening: Each report tab makes a separate API request. During high-demand periods, some succeed while others are throttled. Steps to try: - Click the failing tab again after 30 seconds. - Try loading the tab during off-peak hours. - Hard-refresh the page and navigate back to the failing tab. - If one specific tab consistently fails (e.g., Conversions), contact support with the tab name and your date range. ⚠️ Error 4: My GSC property isn't showing up when I try to connect it What's happening: The Google account you're connecting doesn't have sufficient access to that property in GSC. Steps to try: - Log into Google Search Console directly and confirm your account has Owner or Full User access — Restricted access won't work. - Disconnect and reconnect your Google account in Search Atlas to refresh the property list. - If the property belongs to a different Google account, add that account: Left Sidebar → Site Metrics → Site Explorer → Manage Sites → Connect GSC Account. - If the property was recently created in GSC, wait 24 hours — new properties aren't immediately available via API. ⚠️ Error 5: My Google account keeps disconnecting every few days What's happening: Google periodically requires re-authorization for third-party apps — this is a Google security policy, not a bug. Steps to try: - Reconnect via Site Metrics → Site Explorer → Manage Sites (GSC Accounts page) → View X connected accounts (GSC) → Delete your account from the list → Refresh the page → + Connect New GSC Account → Select Your Account. - When prompted during the OAuth flow, ensure you grant all requested permissions and check "Allow offline access" if shown. - If you recently changed your Google account password, all connected apps need to be re-authenticated. - Check your Google Account security settings for any alerts requiring re-confirmation of third-party app access. - Contact support if disconnections happen within 24 hours of reconnecting — this may indicate a token refresh issue on our end. ⚠️ Error 6: Data in Search Atlas doesn't match what I see directly in GSM What's happening: This is usually a filter or date range difference, not a data error. Steps to try: - Compare the exact same date range in both tools. - Match the device filter — "All devices" vs. "Desktop only" produces very different numbers. - Match the country filter. - Note that GSC data has a 3-day processing lag — the last 3 days are provisional in both tools. - Contact support only if the discrepancy is more than 10 positions across many keywords and persists for more than 1 week. ⚠️ Error 7: Date range selector resets or shows a validation error What's happening: An invalid date combination was entered. Steps to try: - Make sure the start date is before the end date. - Don't select dates more than 16 months in the past. - Don't select future dates — maximum end date is yesterday. - Try typing dates manually instead of using the calendar picker. - Hard-refresh and try setting the date range immediately after the page loads. ⚠️ Error 8: "Insufficient Data" appears in Core Web Vitals field data What's happening: Google's Chrome User Experience Report (CrUX) requires a minimum number of real Chrome users before it generates a report. This is a Google data availability limitation. What to do: - This is not an error — use the Lighthouse lab data scores as your benchmark instead. - CrUX field data will appear automatically once your site accumulates enough Chrome user traffic. - Very new sites, low-traffic sites, and sites with mostly non-Chrome audiences may never accumulate CrUX data. - Focus on growing organic traffic to speed up CrUX data availability. Most Google Search Console and Analytics issues are not platform errors—they are the result of API limits, access permissions, data processing delays, or differences in filters and configurations. Google’s data ecosystem is not real-time and is subject to rate limits, latency, and strict access controls.

📘 GSC Property Verified but Not Showing in Search Atlas

📘 Overview If your website is verified in Google Search Console, connected to your Google account in Search Atlas, but still not visible inside the platform, this usually means the property hasn't been fully activated inside GSC Performance settings. This is not a verification issue, it's typically a location activation step that hasn't been completed yet. 🧭 Navigation Path Search Atlas → Site Metrics → Site Explorer → Your connected GSC Accounts → Manage Sites. 👣 Step-by-Step Fix 1. Open Site Explorer: go to Left Sidebar → Site Metrics → Site Explorer. 2. Click "Manage Sites": on the GSC Sites List screen, click Manage Sites. 3. Click "Manage Sites": on the Your connected GSC Accounts page, click Manage Sites to open the property management panel. 4. Select Location (Country): find your domain, use the Location dropdown to select your target country, and toggle the site to Active if needed. Without selecting a location, the property may not appear in dashboards. 5. Refresh your dashboard: after saving, refresh the dashboard and the property should appear correctly. 🔴 Why This Happens Even after verifying ownership in Google Search Console and connecting your Google account in Search Atlas, the property will not display in performance views until a location is selected and the site is activated in the GSC management panel. This is expected behavior. ❓ FAQs - Why can't I see my verified property? Because it hasn't been activated under Site Metrics → Site Explorer → Your connected GSC Accounts → Manage Sites. - Is this a Google issue? No, it's a configuration step inside Search Atlas. - Do I need support to fix this? No, selecting the location and refreshing resolves the issue. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

📊 GSC Report Data Not Showing for a Location

🔍 Overview If Google Search Console (GSC) data is missing or blank in your reports, the most common cause is that the associated location has not been activated in your project settings. Report data visibility in Search Atlas is directly tied to a location's activation status. ⚙️ How Location Activation Affects GSC Reports Search Atlas controls which locations contribute data to your reports based on their activation state. A location must be active for its GSC statistics to appear in your reports. Even if the GSC integration is confirmed and data is visible elsewhere, an inactive location will not surface that data in generated reports. - Active location: GSC data is included and visible in reports. - Inactive location: GSC data is excluded from reports, even if the integration is working correctly. 🛠️ How to Fix Missing GSC Data in Reports 1. Navigate to your project's location settings. 2. Find the location that is missing data in reports. 3. Check the location's status. If it is set to Inactive, switch it to Active. 4. Open or regenerate the relevant report for that location. 5. Confirm that GSC statistics are now visible in the report. ✅ How to Confirm the Integration Is Working Before checking activation status, verify the following to rule out other issues: - The GSC account is connected and authorised under Site Metrics → Site Events/Site Structure (GSC pages) → Connect GSC Account / Manage Sites. - GSC data is visible for the location in question outside of the report. - The correct date range is selected in the report. If all of the above are confirmed and data still does not appear in your report, the activation status of the location is the most likely cause. 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 GSC Performance Site Activation Errors

🔎 Understanding the Error If your GSC Performance tool displays a message like "Error loading data: Site is not active: sc-domain:yourdomain.com", it means Search Atlas cannot retrieve data from Google Search Console for that property. This usually happens because the site has not been properly activated within the platform, the GSC property is unverified, or the connection between Search Atlas and your Google account has been interrupted. ✅ Step 1: Verify Your Site in Google Search Console Before Search Atlas can import GSC data, your property must be fully verified inside Google Search Console itself. 1. Go to Google Search Console (search.google.com/search-console). 2. Confirm your property appears in the property selector and shows a verified status. 3. If the property shows as unverified, complete verification using one of Google's supported methods (DNS record, HTML file, or Google Analytics). 4. Once verified, wait up to 24 hours for GSC to begin collecting data before trying again. 🔗 Step 2: Reconnect Your Google Account An expired or revoked Google OAuth connection is a common cause of site activation errors. Reconnecting your account refreshes the permissions Search Atlas needs to pull GSC data. 1. In Search Atlas, click your profile icon in the top-right corner and open Settings. 2. Navigate to the Integrations or Connected Accounts section. 3. Locate your Google account connection and click Disconnect. 4. Click Connect GSC Account (Site Metrics → Site Explorer) and complete the OAuth flow, making sure to grant all requested permissions including Search Console access. 5. Return to the GSC Performance tool and check whether the error has cleared. 🏠 Step 3: Activate the Site in Search Atlas After confirming your GSC property is verified and your Google account is connected, make sure the site is properly activated inside Search Atlas. 1. In the left sidebar, click Site Metrics (Site Explorer). 2. Locate the domain showing the activation error in your site list. 3. If the site is listed, click the settings or edit icon next to it and confirm the correct GSC property is mapped — for example, ensure sc-domain: properties are matched to the domain-level property, not a URL-prefix property. 4. If the site is not listed, click Add Site, enter your domain, and select the matching GSC property from the dropdown. 5. Save your changes and reload the GSC Performance report. ⚠️ Step 4: Check Property Type Mismatch Google Search Console supports two property types: Domain properties (shown as sc-domain:yourdomain.com) and URL-prefix properties (shown as https://yourdomain.com). A mismatch between the property type in GSC and what is configured in Search Atlas will trigger an activation error. - If your GSC property is a domain property, make sure Search Atlas is also set to use the sc-domain: format. - If your GSC property is a URL-prefix property, confirm the full URL including the correct protocol (https:// or http://) is entered in Search Atlas. - When in doubt, use the same property format shown in your Google Search Console dashboard. ⏳ Step 5: Allow Time for Data to Populate Even after a successful activation, GSC Performance data may not appear immediately. Keep the following timelines in mind: - Google Search Console typically delays data by 2–3 days. - Newly connected or re-connected properties can take up to 24–48 hours to begin syncing inside Search Atlas. - If you have just verified a brand-new domain in GSC, there may be no historical data available yet — data begins accumulating from the verification date. 🛠️ Quick Troubleshooting Checklist - GSC property verified? Check directly in Google Search Console. - Google account connected? Reconnect via Settings → Integrations. - Correct property type selected? Match sc-domain or URL-prefix consistently. - Site added in Search Atlas? Confirm under Site Explorer. - Waited 24–48 hours? Allow time after any reconnection or re-activation. 💬 Still Seeing the Error? If you have followed all the steps above and the GSC Performance tool still shows a site activation error or is not importing data correctly, our team is ready to investigate your specific account configuration. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

📊 Fix GSC Performance Data Not Showing in Projects

🔍 Overview Connecting your Google Search Console (GSC) account to Search Atlas is only the first step. For performance data — such as impressions, clicks, and search queries — to appear inside your project's Site Audit and other reports, GSC must also be enabled for each individual project. Skipping this activation step is the most common reason GSC data shows as empty even when your property appears correctly connected. ⚠️ Two Separate Steps: Connection vs. Activation Many users assume that linking their GSC account once is enough. In Search Atlas, there are two distinct steps: - Step 1 — Connect your GSC account: This authorises Search Atlas to access your Google Search Console data. It is done once at the account level. - Step 2 — Enable GSC per project: This activates the data feed for a specific project. It must be done individually for every project where you want GSC performance data to appear. This step is separate from the account connection and is the step most often missed. If Step 2 is not completed, your project will show no GSC performance data regardless of whether your account is connected or your property variant is correct. ✅ How to Enable GSC for a Project To enable GSC data for a specific project, navigate to Site Metrics → Site Explorer → Open Google Search Console (Manage Sites / Connect GSC Account). From there, enable GSC for that project and save your settings if prompted. Once enabled, return to your project's Site Audit or performance reports — GSC data will begin populating. Depending on the volume of data, it may take a short time to fully load on the first activation. If you are unsure where to find the GSC settings for your project, please reach out to our support team for guided assistance. 🛠️ Still Not Seeing Data? Check These Common Causes If you have enabled GSC for a project and data is still not appearing, review the following: - Property variant mismatch: Ensure the GSC property connected to your project matches exactly how your site is verified in Google Search Console. Common mismatches include https:// vs http://, or www vs non-www versions. Use the Domain property in GSC where possible to avoid variant issues. - Correct property selected: In your project settings, confirm the GSC property selected is the right one for that site. It is possible to connect the account but have no property selected, or the wrong property selected. - GSC data availability: GSC data is not real-time. Google typically makes performance data available with a delay of 2–4 days. If your site is newly verified or the project was just created, allow some time before expecting data to appear. 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 the GA4 'Other' Traffic Channel in Site Metrics

📖 What Does 'Other' Traffic Mean in GA4? The Other channel in Google Analytics 4 (GA4) is a catch-all category for sessions that GA4 could not confidently match to a defined channel grouping, such as Organic Search, Paid Search, Direct, Referral, or Social. When Search Atlas pulls your GA4 data into Site Metrics, this same channel classification is reflected in your traffic reports. Because GA4 relies heavily on UTM parameters, referral data, and campaign tagging to categorize traffic, any session that lacks clear signals or contains conflicting parameters gets grouped into Other rather than being misattributed to the wrong channel. 🔍 Common Causes of a High 'Other' Traffic Number If you are seeing a number like 467 sessions under Other, it typically means a large portion of your traffic is missing proper tracking signals. Common causes include: - Missing or malformed UTM parameters on email campaigns, ads, or shared links - Cross-domain tracking issues where session data is lost between domains - Referral exclusions misconfigured in GA4, causing legitimate referral traffic to lose its source - Server-side redirects (such as link shorteners or tracking redirects) that strip referrer information - App-to-web handoffs from mobile apps or in-app browsers - Dark social traffic, such as links shared in private messaging apps, which strip referrer data entirely A sudden spike in Other traffic often correlates with a new campaign launch, a website migration, or a change in your tagging strategy. If the number appears unusually high compared to historical averages, it is worth investigating recent marketing activity or technical changes to your site. 🛠️ How to Investigate 'Other' Traffic in Search Atlas 1. Navigate to the left sidebar and select Site Metrics 2. Go to Overview to confirm your GA4 connection status is active 3. Cross-reference the reporting date range with any recent campaign launches or site changes 4. Check whether the spike is isolated to a specific date range or spread evenly across the reporting period If your GA4 connection shows an unexpected status change, such as permissions appearing revoked when they are not, this is a known display inconsistency that our engineering team has already resolved. If you still see this issue, refreshing your connection or reconnecting GA4 in Site Metrics typically resolves it. ✅ How to Reduce 'Other' Traffic Going Forward While some Other traffic is unavoidable, you can minimize it with better tracking hygiene: - Ensure all campaign links use consistent and complete UTM parameters (source, medium, campaign) - Audit your referral exclusion list in GA4 to make sure legitimate referral sources are not being excluded - Avoid unnecessary redirect chains that strip referrer data - Standardize UTM tagging conventions across your team or agency to prevent conflicting parameter formats Keep in mind that GA4's channel classification logic is set by Google, not by Search Atlas. Site Metrics reports the data exactly as GA4 provides it, so any changes to reduce Other traffic must happen at the tracking and tagging level. 📌 When to Escalate If your Other traffic percentage remains unusually high after auditing your tagging and referral settings, or if you notice traffic anomalies that do not align with any known campaign activity, this may warrant a deeper investigation into your GA4 property configuration. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Why Aren't My Google Search Console Properties Showing in the Reports Dropdown?

In some accounts, Google Search Console is connected and your properties are visible in the integration view, yet the property selector in the reports builder stays empty — so you can't connect a Search Console property to a report. This affects team member seats, and it has a quick fix. 🔍 How to Recognize This Issue This is likely your situation if all of the following are true: - Your GSC integration shows as connected in Site Metrics → Site Explorer → 'Open Google Search Console' (Manage Sites page) (for example, it shows the number of sites found). - Clicking View properties in the integration shows your Search Console properties listed correctly. - Your data loads normally when you open Google Search Console directly. - But the property selector in the reports builder is empty and does not list your properties when you try to connect one to a report. You can still create and view reports — only the step of connecting a Search Console property to a report is blocked. 🧩 Why This Happens Your account is set up as a team member seat, and the reports builder requires each user to have their own Google account connected directly. When this per-user connection hasn't been completed for your login, your Search Console properties won't appear in the reports dropdown — even though the account itself already has GSC connected. 🛠️ How to Fix It While logged in with your own user: 1. Go to Site Metrics → Site Explorer → 'Open Google Search Console' (Manage Sites page). 2. Click Connect GSC Account. 3. Authorize with the Google account that has access to your Search Console properties. 📈 What to Expect After Connecting Once connected, your properties will sync and appear in the reports dropdown within a few minutes. You do not need to rebuild any reports you've already created. ✅ In Short Even though your Search Console connection looks complete at the account level, the reports builder needs your own Google account connected on your login. Once you complete that one-time connection, your properties sync within a few minutes and everything you've already built stays exactly as it is — so you can pick up right where you left off, no rework required.

🔗 Fix www vs Non-www GSC Data Discrepancies

🤔 Why This Happens Google Search Console treats https://seniorcarehomes.com and https://www.seniorcarehomes.com as two completely separate properties, each with its own independent dataset. If your website canonically serves traffic on the non-www version but your Search Atlas project is pulling data from the www property, you will see a mismatch: one property shows hundreds of keywords while the other shows zero. This is not a bug. It reflects exactly how Google stores data. The fix is to ensure Search Atlas is connected to the GSC property that actually holds your traffic and indexed pages. 🔍 Step 1 — Identify Your Primary GSC Property Before changing anything in Search Atlas, confirm which property contains your real data inside Google Search Console. 1. Go to Google Search Console (search.google.com/search-console). 2. Open the property selector in the top-left corner. 3. Compare the Total clicks and Total impressions for both the www and non-www versions over the last 90 days. 4. The property with higher numbers is your primary property — note its exact URL format. In most cases the non-www version (e.g. https://seniorcarehomes.com) is the canonical source when a 301 redirect from www to non-www is in place. ⚙️ Step 2 — Make Sure the Correct GSC Property Is Connected in Search Atlas Search Atlas can only pull data from a GSC property that is already verified in your Google Search Console account and connected to your Search Atlas workspace. Because the exact steps for reconnecting or reassigning a GSC property depend on your account configuration, please have the following information ready before reaching out: - The exact URL of your primary GSC property (e.g. https://seniorcarehomes.com vs https://www.seniorcarehomes.com). - The name of the Search Atlas project that is showing 0 keywords. - A screenshot or note of the Total clicks/impressions figures from both properties in GSC. - Whether both the www and non-www versions are verified in your Google Search Console account. If the correct property is not yet verified in Google Search Console, verify it there first — Search Atlas can only surface properties that are already confirmed in your GSC account. 🎯 Step 3 — Escalate to the Support Team Once you have confirmed which GSC property holds your real data and have the details listed above ready, contact the support team. A teammate will identify which property is currently assigned to your project and reassign it to the correct one so your keyword data populates accurately. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Google Search Console Data Layer Upgrade

Google Search Console has been upgraded with a React Query data layer, improving how data is fetched, cached, and displayed across the platform for a faster and more consistent experience. ✨ What's New The GSC module now uses React Query as its data layer, replacing the previous approach with dedicated API hooks and UI-state stores. This architectural upgrade means data is fetched more efficiently, cached intelligently between page interactions, and kept in sync automatically — reducing unnecessary loading states and stale data across GSC views. 🛠️ How to Use It 1. Navigate to the Google Search Console section of the platform. 2. Open any GSC report or view as you normally would. 3. Data will load and refresh automatically — no additional steps are required on your end. 📋 What to Expect This is an infrastructure-level improvement, so the core GSC experience looks the same. However, you should notice faster data loads, fewer loading spinners when switching between views, and more consistent data rendering throughout the module. No configuration changes are needed, and existing reports and connected accounts are unaffected. 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 Google Search Console Connected But No Data

🔍 Overview If your Google Search Console (GSC) account appears as connected inside Search Atlas but no data is loading, the issue is almost always related to a broken authentication token, a sync delay, or a stale connection — not your plan or project quota. This guide walks you through the steps to diagnose and fix it. ⚠️ Before You Begin Confirm the following before troubleshooting: - You are logged into Search Atlas with the Google account that owns or has full access to the Search Console property. - The GSC property is verified and active inside Google Search Console directly. - You have waited some time after first connecting — GSC data can take several days to appear for new connections. 🛠️ Step 1: Clear Your Browser Cache A cached session can cause Search Atlas to display a stale connection state. Start here before anything else. 1. Press Ctrl + Shift + Delete (Windows) or Cmd + Shift + Delete (Mac) to open your browser's clear cache panel. 2. Select Cached images and files and Cookies and other site data. 3. Set the time range to All time and confirm. 4. Close and reopen your browser, then log back into Search Atlas. 5. Navigate to the relevant GSC data section in Search Atlas and check whether data now appears. 🔄 Step 2: Disconnect and Reconnect Your GSC Account If clearing cache does not resolve the issue, the authentication token may have expired or become invalid. Reconnecting forces Search Atlas to issue a fresh token. 1. Inside Search Atlas, go to your account or integration settings. 2. Locate Google Search Console under connected integrations. 3. Click to disconnect and confirm the action. 4. Wait a moment, then initiate a new Google Search Console connection. 5. Follow the Google OAuth prompts and select the correct Google account — the one with verified access to your GSC property. 6. Grant all requested permissions. Skipping any permission step is a common cause of silent connection failures. 7. Once reconnected, navigate to the relevant GSC data section and allow some time for the initial data pull to complete. ⏱️ Step 3: Allow for Sync Delays Even after a successful reconnection, data does not always appear instantly. GSC sync timing depends on two factors: - Google's own data latency: GSC typically delays data by a few days on their end. Search Atlas can only display data that Google has already processed. - Search Atlas sync interval: After reconnecting, the platform needs time to fetch and index the data from Google's API. If data still does not appear after allowing adequate time, please reach out to support for further assistance. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Fix GSC Connection and Performance Overview Issues

🧭 Overview If you have multiple Google accounts or Search Console properties, it can be unclear which property is actively connected to Search Atlas. You may also notice that the GSC Performance Overview tab displays a Connect GSC prompt even after completing the integration. This article explains how to confirm the correct GSC property is linked and what to do if you are still experiencing connection or display issues. 🔗 How Google Search Console Connects to Search Atlas Search Atlas connects to Google Search Console via OAuth, which means you authorise access through a specific Google account. If you manage multiple Gmail accounts or have several GSC properties, it is important to verify that the correct account and property were selected during the authorisation flow. Each Search Atlas project is linked to a single GSC property. If the wrong property was connected, your performance data will either be missing or belong to a different website. ✅ How to Confirm Your GSC Connection If you are unsure whether the correct GSC property is connected, or if the Performance Overview tab is showing a Connect GSC prompt even after integration, the best course of action is to contact our support team directly. A member of our team can verify which Google account and property are linked to your project, confirm whether your connection is active, and guide you through reconnecting with the correct account if needed. When reaching out, please have the following ready: - The name of the affected Search Atlas project - The Google account email you used during the GSC authorisation flow - The exact GSC property URL you intended to connect (for example, https://www.example.com/ versus https://example.com/ — these are treated as separate properties in Google Search Console) - A description of what you are seeing, including any error messages or prompts displayed ⚠️ Why the Performance Overview Tab May Show "Connect GSC" In some cases, the GSC Performance Overview tab may display a Connect GSC prompt even when your integration has been completed. This can be a display issue that does not reflect the true state of your connection. If you are seeing this, please contact our support team so we can investigate and confirm whether your integration is active and data is flowing correctly. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Fix GSC Performance Data Not Showing

🔎 Overview If your Search Atlas project is connected to Google Search Console (GSC) but no search performance data is appearing, you are not alone. This is a common setup issue that is almost always resolved by following a few quick checks. This article walks you through the most likely causes and how to fix them. ✅ Step 1: Confirm the Correct GSC Property Is Connected The most frequent cause of missing performance data is a mismatch between the GSC property and the website URL in your project. To verify: 1. Open your project in Search Atlas. 2. Navigate to the top-right avatar (Account Menu) → Settings → Integrations and locate the Google Search Console integration section. 3. Confirm the connected property exactly matches the version of your site that Google is indexing — for example, https://www.example.com is a different property from https://example.com. 4. If the wrong property is connected, disconnect it and reconnect using the correct one. In GSC itself, check which property type you verified — domain property or URL-prefix property — and make sure Search Atlas is referencing the same one. ⏳ Step 2: Allow Time for Data to Populate After connecting GSC to a new Search Atlas project, there is a processing period before data appears. Keep the following in mind: - Initial data sync can take 24 to 48 hours after a successful connection. - GSC itself delays performance data by 2 to 3 days from the date of collection. - If your site is brand new or recently launched, GSC may have little or no performance data to display yet. If you connected GSC less than 48 hours ago, wait and check again before proceeding further. 🔑 Step 3: Check GSC Account Permissions Search Atlas can only retrieve data that the connected Google account is authorised to access. Ensure the following: - The Google account used to connect GSC has at least Full User or Owner permission on the property in Google Search Console. - The account has not had its GSC access revoked or downgraded since the initial connection. - You are not connected as a Restricted User, as this permission level limits the data available via the GSC API. To check permissions, log in to Google Search Console, open the relevant property, and go to Settings → Users and permissions. 🔄 Step 4: Reconnect the GSC Integration If permissions are correct but data is still missing, try refreshing the connection: 1. Go to the top-right avatar (Account Menu) → Settings → Integrations in Search Atlas. 2. Disconnect the current GSC integration. 3. Re-authorise your Google account and reconnect the correct GSC property. 4. Save your settings and allow up to 48 hours for data to appear. Reconnecting forces a fresh authorisation token, which resolves issues caused by expired or invalidated credentials. 📊 Step 5: Verify Data Exists in GSC Directly Before assuming a Search Atlas issue, confirm that performance data is actually available in GSC: 1. Log in to Google Search Console. 2. Select the connected property. 3. Click Search results under the Performance section. 4. Check whether clicks, impressions, and queries are visible for recent date ranges. If GSC shows no data either, the issue is upstream with Google's indexing or data collection — not with Search Atlas. This can happen with new sites, sites blocked by robots.txt, or sites with crawl errors. 🛠️ Common Scenarios and Quick Fixes - Data was showing before but stopped: Your GSC authorisation token may have expired. Reconnect the integration as described in Step 4. - Only partial data is visible: Confirm the date range selected in the performance report includes dates after the GSC connection was established. - Multiple GSC properties exist for the same domain: Connect the property that has the most complete data — typically the domain-level property if one has been verified. - GSC property was recently reverified or recreated: Historical data from the previous property will not carry over. Only data collected after the new verification date will appear. 💬 Still Need Help? If you have followed all the steps above and search performance data is still not displaying, 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.

🔍 GSC Performance View Sites Not Loading Fix

🧭 Overview If your sites are not loading or GSC data is missing in the GSC Performance section of Search Atlas, this is a known issue that our support team can investigate and resolve on your behalf. Because the root cause may involve your specific GSC connection, account configuration, or a backend data sync problem, the most reliable path to resolution is to contact our team directly. What to Have Ready Before Contacting Support To help our team investigate as quickly as possible, please have the following information ready when you reach out: - The project name or workspace where the GSC Performance view is not loading - The exact site or property URL you expect to see data for - A description of what you see — for example, whether the section is blank, shows an error message, or shows some sites but not others - The exact error message (if any) displayed on screen - The timestamp (date and approximate time) when you first noticed the issue - The Google account used to connect your GSC integration What Our Team Will Do Once you contact support, a member of our team will review your GSC connection status and data sync on the backend and work to restore your site data in the GSC Performance view. 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 GA4 Cross-Site Tracking Data in Single Property

🧩 What Is This Issue? Some customers have noticed unexpected cross-site tracking data appearing inside a single Google Analytics 4 (GA4) property. For example, data from one domain showing up under a property that should only track a different domain. This can distort your traffic reports, inflate session counts, and make it harder to analyse accurate SEO performance. This article explains the most common causes of this issue and walks you through how to diagnose and fix it — including how Search Atlas connects to your GA4 data. 🔎 Does Search Atlas Cause This? Search Atlas reads your GA4 data using a secure, read-only integration. It does not inject tracking scripts, modify your GA4 configuration, or send data into your GA4 property. If cross-site data started appearing in your GA4 property around the time you connected Search Atlas, the root cause is almost always a pre-existing configuration issue in GA4 that becomes more visible once you start actively reviewing your analytics. ⚠️ Common Causes of Cross-Site Data Contamination - Shared Measurement ID: The same GA4 Measurement ID is used on more than one domain or subdomain, causing all traffic to roll up into one property. - Cross-Domain Tracking misconfiguration: GA4 cross-domain tracking is enabled but the domain list includes domains that should be tracked separately. - Third-party embeds or iframes: Widgets, booking engines, or payment portals hosted on another domain that carry your GA4 tag. - Tag Manager container errors: A Google Tag Manager container is firing your GA4 tag on unintended domains due to a missing or incorrect trigger filter. - Referral exclusion settings: Missing referral exclusions can cause sessions to restart mid-journey and attribute traffic incorrectly. 🛠️ How to Diagnose the Problem 1. Open your GA4 property and navigate to Reports → Acquisition → Traffic Acquisition. 2. Add a secondary dimension of Hostname to see which domains are sending data into this property. 3. If you see hostnames that do not belong to this property, you have confirmed cross-site contamination. 4. Note the hostnames and the date the unexpected data first appeared — this helps narrow down what changed. ✅ How to Fix Cross-Site Data in GA4 Once you have identified the unexpected hostnames, follow the steps below based on the most likely cause. Fix 1 — Remove unintended domains from Cross-Domain Tracking: 1. In GA4, go to Admin → Data Streams → select your web stream. 2. Click Configure tag settings → Configure your domains. 3. Review the domain list and remove any domains that should not be sharing session data with this property. Fix 2 — Add hostname filters to your Data Stream: 1. In GA4, go to Admin → Data Streams → select your web stream → Configure tag settings. 2. Use the List unwanted referrals and internal traffic settings to exclude domains sending unwanted hits. Fix 3 — Fix your Google Tag Manager trigger: 1. Open your GTM container and locate the GA4 Configuration tag. 2. Edit the trigger and add a condition: Page Hostname → equals → your intended domain only. 3. Publish the updated container. Fix 4 — Create a filtered GA4 property (recommended for clean reporting): 1. In GA4, go to Admin → Data Settings → Data Filters. 2. Create a new filter using the Hostname dimension to include only your intended domain. 📊 Verifying Your Search Atlas Integration To confirm your Search Atlas connection is working correctly with your clean GA4 data, navigate to Site Metrics (Site Explorer) in the left sidebar of the platform. Your traffic and keyword data should reflect only the property you have connected. If you connected multiple properties, verify each one under Keywords → Rank Tracker to ensure the correct domain is selected. 🚀 Preventing This Issue in the Future - Always use a separate GA4 property for each distinct domain — avoid sharing Measurement IDs across sites. - Audit your GTM container triggers whenever a new third-party tool is added to your site. - Review your GA4 hostname report monthly to catch unexpected data sources early. - Document which Measurement ID belongs to which property before connecting any analytics integration. 💬 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.

📊 Understanding GA4 'Other' Traffic Category Explained

🔍 What Is the 'Other' Traffic Category in GA4? In Google Analytics 4 (GA4), the 'Other' channel group is a catch-all bucket. It captures sessions that GA4 cannot confidently assign to a standard channel such as Organic Search, Direct, Referral, Paid Search, or Social. If your report shows a high 'Other' count — for example, 467 sessions — it usually signals a tagging or configuration issue worth investigating. 📋 What Traffic Ends Up in 'Other'? GA4 places sessions into 'Other' when one or more of the following conditions apply: - Missing or mismatched UTM parameters: Campaigns using UTM tags that do not align with GA4's default channel definitions land in 'Other'. - Unrecognised traffic sources: Referral domains, apps, or platforms that GA4 does not recognise as a known channel group. - Custom channel groups not yet configured: If you have not set up custom channel groups in GA4, niche traffic sources default to 'Other'. - Self-referral traffic: Your own domain referring back to itself due to missing cross-domain tracking or incorrect exclusion rules. - Dark social and in-app browsers: Links shared in messaging apps (WhatsApp, Slack, email clients) often strip referrer data, causing GA4 to misclassify the session. - GA4 connection or permission issues: An interrupted or incorrectly permissioned GA4 connection can cause data to surface under unexpected labels. ⚠️ Why Is My 'Other' Count So High? A spike in 'Other' traffic — such as 467 sessions in a single reporting period — is rarely random. Common causes include: 1. Recent campaign launch without proper UTM tagging: Any campaign link missing a recognised utm_medium or utm_source value will default to 'Other'. 2. Third-party integrations sending untagged traffic: Email platforms, CRMs, or marketing automation tools that do not append UTMs automatically. 3. GA4 property misconfiguration: Incorrect data stream setup, missing filters, or a recently reconnected GA4 account can temporarily inflate 'Other'. 4. Bot or low-quality traffic: Some automated traffic bypasses standard referral data. 🛠️ How to Diagnose the Problem Follow these steps to identify the source of your 'Other' traffic: 1. Open GA4 and navigate to Reports → Acquisition → Traffic Acquisition. 2. Set your primary dimension to Session default channel group, then add Session source / medium as a secondary dimension. 3. Filter the table to show only the Other channel group. The source/medium column will reveal which specific sources are being miscategorised. 4. Cross-reference those sources against your active campaigns to confirm whether UTM parameters are present and correctly formatted. 5. Check your GA4 data stream settings for self-referral exclusions and cross-domain tracking if your site spans multiple subdomains or domains. ✅ How to Fix and Reduce 'Other' Traffic - Add UTM parameters to all campaign links. Use GA4-recognised values: utm_medium should match terms like email, cpc, social, or organic. - Exclude your own domain from referrals. In GA4, go to Admin → Data Streams → Configure tag settings → List unwanted referrals and add your domain. - Set up cross-domain tracking if visitors move between multiple domains you own. - Create custom channel groups in GA4 (Admin → Channel groups) to capture niche sources that do not fit default definitions. - Audit third-party tools such as email platforms and CRMs to ensure they append UTMs automatically before sending traffic. - Reconnect your GA4 integration inside Search Atlas via Top-right corner (avatar) → Settings → Integrations if you have recently changed GA4 property permissions or switched Google accounts, as a stale connection can affect how data is reported. 📊 Viewing Traffic Data in Search Atlas Search Atlas pulls GA4 data to surface traffic insights across your projects. If you notice 'Other' appearing prominently in your Search Atlas reports, the root cause is always within GA4 itself — fixing it in GA4 will automatically improve the data you see in Search Atlas. Ensure your GA4 connection remains active and that the correct property is linked to your project. 💡 Quick Reference: Common Sources Behind 'Other' - Email newsletters without UTM tags - PDF downloads linking back to your site - In-app browsers (Instagram, LinkedIn, Gmail) - Affiliate or partner links missing UTM parameters - QR codes not tagged with UTMs - Traffic from unknown or new referral domains 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 Missing GSC Keywords Data in Dashboard

Overview If your Google Search Console (GSC) keyword data appears missing or blank in your Search Atlas dashboard, this article explains what may be happening and what to have ready when reaching out to our team for assistance. What Is Happening GSC keyword data can fail to appear in the Search Atlas dashboard for a variety of backend reasons. Because resolving this issue requires investigation on our end, there are no self-serve steps that are guaranteed to restore missing data. Our support team will need to look into your specific account and GSC connection to identify the cause. What to Have Ready Before Escalating To help our team resolve your issue as quickly as possible, please have the following information ready when you reach out: - The name of the project affected in your Search Atlas account. - The domain or URL associated with the project. - Approximately when you first noticed the keyword data was missing. - Whether the domain and GSC property were recently connected or have been active for some time. - Any error messages or unusual states you have observed in the 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.

🔍 Troubleshooting GA4 Data Discrepancies in Search Atlas

Overview If the organic traffic or new user numbers in your Search Atlas reports do not match what you see in Google Analytics 4 (GA4), you are not alone. This is one of the most common integration questions our team receives. Discrepancies are almost always caused by differences in how each platform filters, attributes, or processes the same underlying data — not a broken connection. This article walks you through the most common root causes and general guidance to help you reconcile the numbers. Common Root Causes - Date range and timezone mismatches: GA4 applies your account timezone to all reports. If Search Atlas is displaying data in a different timezone, daily totals can shift — especially for sessions near midnight. Confirm both platforms are set to the same date range and timezone before comparing figures. - Organic traffic definition differences: GA4 classifies sessions as organic based on its own channel grouping rules. If your GA4 property has custom channel groups or modified default channel definitions, the organic segment visible in GA4 may differ from what Search Atlas displays. - New user attribution: GA4's definition of a "new user" depends on when GA4 first registers a Client ID. If a user clears cookies or switches devices, GA4 may count them as new again. Filters applied within GA4 can also affect these counts. Search Atlas reflects the data as received from GA4, so any GA4-side configuration affects both views. - Filters and data streams: GA4 properties can have internal traffic filters, developer traffic filters, or cross-domain tracking configured. If these filters are applied inconsistently — or were added or changed after your Search Atlas integration was set up — the data visible in Search Atlas may not match your GA4 dashboard view. - Connected property mismatch: If your GA4 account uses multiple properties, ensure Search Atlas is connected to the same property you are comparing against in GA4. Comparing data from different property levels will always produce different numbers. Steps to Investigate 1. Verify which GA4 property is connected. Check your integration settings to confirm the correct GA4 property is linked to your Search Atlas project, and that it matches the property you are reviewing in the GA4 interface. 2. Align your date ranges and timezone settings. Make sure both GA4 and Search Atlas are showing the same date range. Check your GA4 property timezone setting and confirm it aligns with what Search Atlas is using. 3. Review your GA4 channel groupings and filters. In GA4, check whether any custom channel groups, internal traffic filters, or cross-domain tracking rules have been configured. Changes to these settings on the GA4 side will affect the data Search Atlas receives. 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 a Site for GSC Performance Metrics

🔍 GSC Performance vs. a Full OTTO Project Search Atlas gives you two distinct ways to work with your websites. A full OTTO project, managed at Left sidebar → OTTO SEO → All Sites (SEO Automation), activates AI-powered on-page SEO automation and requires additional configuration. A GSC Performance-only site, managed at Left sidebar → Site Metrics, simply connects your Google Search Console property so you can monitor organic clicks, impressions, average position, and CTR—no automation required. ✅ What You Need Before You Start - A Google account with access to the Google Search Console property for your website - Owner or full user permissions on that GSC property - An active Search Atlas account with at least one available site slot ➕ How to Add a Site for GSC Performance Only 1. Go to Left sidebar → Site Metrics. 2. Click Add New Site in the top-right area of the page. 3. Enter your full website URL (e.g., https://example.com) and click Continue. 4. When prompted to connect a data source, select Google Search Console. 5. Sign in with your Google account and grant Search Atlas the requested read permissions. 6. From the dropdown, select the GSC property that matches your website. 7. Click Save to complete the connection. Your site will now appear in the Left sidebar → Site Metrics list. Search Atlas will begin importing your GSC data—please allow up to 24 hours for the first full data sync to complete. 📊 What Data You Can View Once the GSC property is connected, the following performance metrics become available for your site: - Clicks — total organic clicks your pages received from Google Search - Impressions — how many times your pages appeared in Google search results - Average Position — your site's mean ranking across all tracked queries - Click-Through Rate (CTR) — the share of impressions that resulted in a click ⚠️ Key Differences from an OTTO Project Adding a site at Left sidebar → Site Metrics does not create an OTTO project. This means: - OTTO SEO automation is not activated for the site - The site will not appear under Left sidebar → OTTO SEO → All Sites (SEO Automation) - Crawl monitoring (available at Left sidebar → OTTO SEO → Site Audit → Crawl Monitoring) and automated on-page recommendations will not be enabled - No OTTO credits are consumed If you decide to upgrade this site to a full OTTO project in the future, navigate to Left sidebar → OTTO SEO → All Sites (SEO Automation) and add the site there separately. 🛠️ Troubleshooting Common Issues - GSC property not showing in the dropdown — confirm you are signed in with the Google account that has Owner or Full User access to that property in Google Search Console. - No data appearing after 24 hours — verify the GSC property is receiving data directly in Google Search Console, then disconnect and reconnect the property in Left sidebar → Site Metrics. - Site already exists error — the URL may already be added under a different workspace or user. Check Left sidebar → Site Metrics for an existing entry. 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 GSC Properties Missing From Report Builder

Overview If your Google Search Console (GSC) property appears correctly in your OTTO SEO audits but is missing from the GSC selection list inside Report Builder, this article explains what may be happening and what steps you can take to resolve it. Why This Happens Search Atlas surfaces GSC data differently depending on where you are in the platform. A property can be connected and visible in your OTTO SEO audits while still not appearing in Report Builder — typically because the property has not been enabled for reporting in Manage Sites. How to Resolve This Issue To make a GSC property available in Report Builder, go to Manage Sites and locate the site associated with your GSC property. Check whether the GSC property is enabled for that site within Manage Sites. Enabling it there should make the property appear in the Report Builder selection list. If you do not see an option to enable the GSC property in Manage Sites, or if the property still does not appear in Report Builder after checking there, please have the following ready before contacting support: - The exact GSC property URL that is missing from Report Builder (for example, the domain or URL prefix you see in Google Search Console). - Confirmation that the property does appear in your OTTO SEO audit within Search Atlas. - Your Search Atlas account email or workspace name. - Any screenshots showing the property present in your audit but absent from the Report Builder selection list. Quick Reference 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 Google Search Console Not Showing in Search Atlas

🔍 Overview If your Google Search Console (GSC) account appears connected but data is not showing inside Search Atlas, the most common cause is an expired or misconfigured integration at the account level. In most cases, you can fix this yourself by disconnecting and reconnecting GSC. This article explains how, and what information to have ready if you still need to contact support. ✅ Step 1: Verify Your GSC Integration Status Before reaching out, check whether your GSC connection is active inside your Search Atlas account settings. Look for an area that manages third-party integrations and confirm whether Google Search Console shows as connected or disconnected. If the connection appears active but data is still missing, note the current status displayed so you can share it with support. 🔄 Step 2: Try Re-Authenticating Your Google Search Console Account If your connection has expired or shows an error, attempt to disconnect and reconnect your Google Search Console integration from within your account settings. During reconnection, use the Google account that has appropriate access to the GSC property you want to use, as accounts with insufficient permissions may appear to connect without error but will not return data. 🛠️ Still Not Working? After reconnecting, data can take some time to repopulate because it syncs in the background. If reconnecting fails, the property is missing or not verified in GSC, or data is still missing after reconnecting and the next sync, our support team can investigate the issue on your account directly. When reaching out, please have the following ready: - Your Search Atlas account email address - The GSC property URL you are trying to connect - The Google account email used to authenticate GSC - A description of the current integration status shown in your account settings - Any error messages you have seen during the connection process 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 GA4 Report Builder Date Range Discrepancies

Overview If you notice that GA4 metrics in the Search Atlas Report Builder do not match the numbers shown in your native Google Analytics 4 account for the same date range — such as a 90-day period — you are not alone. This is a known discrepancy that customers report, and there are several commonly cited reasons why these figures can differ. This article explains the general factors involved and what to check when you encounter this issue. How Report Builder Pulls GA4 Data The Search Atlas Report Builder connects to GA4 via the official Google Analytics Data API. While this uses the same underlying data as your GA4 account, there are important technical differences in how data is sampled, processed, and displayed between the native GA4 interface and any third-party tool that consumes the API. - Data sampling: GA4 may apply sampling to large datasets. Over longer date ranges, the API used by Report Builder can return results that differ from what the native GA4 interface displays. This is a frequently reported cause of discrepancies. - Data freshness and processing lag: GA4 data may not be fully processed immediately. If you pull a report in Report Builder while GA4 is still processing recent data in your selected range, the totals may differ until processing is complete. - Metric definitions: Some GA4 metrics may behave differently depending on how they are queried via the API versus how the native UI renders them. - Timezone and date boundary alignment: If the timezone configured in your GA4 property differs from the timezone settings in your Search Atlas account, date boundaries may shift and day-level counts may not align, especially at the start and end of the selected range. - Filters and segments: Native GA4 reports may have default comparisons, filters, or segments applied that are not replicated in Report Builder. Always verify that no active filters are influencing your native GA4 view. Steps to Troubleshoot the Discrepancy 1. Check your GA4 property timezone. In your GA4 account, locate your property settings and note the timezone configured there. Confirm this matches the timezone used in your Search Atlas reports. 2. Allow sufficient time for data processing. Avoid comparing data for the most recent days. Set your date range to end at least two days before today in both GA4 and Report Builder, then compare again. 3. Remove all filters in the native GA4 interface. Open your GA4 account, navigate to the relevant report, and ensure no segments, comparisons, or custom filters are active that could inflate or reduce the numbers shown. 4. Compare the same metrics. Make sure you are comparing identical metric names in both GA4 and Report Builder, as similarly named metrics can have different defin