Troubleshooting: GSC & GA4 Connection

📊 Search Atlas — Google Search Console & Analytics Issues

⚡ Manage WordPress Sync, OTTO CSS, and GSC Issues

🔧 Fix Google Search Console Connection Dropping in Search Atlas

🔍 Fix GSC Site Activation 404 Errors

🔍 What the 404 error means A 404 error during Google Search Console (GSC) activation means Search Atlas could not find or update the site connection endpoint. This can result from a temporary backend issue, an unsupported property URL format, or a mismatch between the verified GSC property and the site added in Search Atlas. ✅ Check your GSC property 1. Open Google Search Console and confirm the property is verified. 2. Check whether it is a Domain property or a URL-prefix property. 3. Confirm that the Google account connected to Search Atlas has access to the property. 4. For URL-prefix properties, copy the exact property URL, including https://, the correct domain, and any required path. ⚙️ Use the correct site URL In Search Atlas, use the website’s canonical URL whenever possible. For example, use https://victorypavingnc.com if that is the site’s primary version. Avoid adding extra spaces, page paths, query parameters, or a trailing slash unless the same format appears in the GSC property. Make sure the versions of your site are consistent. These are separate properties in GSC: - http://example.com - https://example.com - https://www.example.com - https://example.com/folder/ 🔗 Activate the site in Search Atlas 1. Open the project in Search Atlas. 2. Go to the GSC integration or Manage Sites panel. 3. Choose the verified GSC property that matches your project URL. 4. Save or activate the site, then wait for the confirmation message. If the property appears in GSC but activation still returns a 404, refresh the page, sign out and back in to the connected Google account, and try once more. Do not create duplicate properties while troubleshooting. 🛠️ If activation still fails A 404 can be caused by a temporary issue with the GSC activation service rather than your website or verification. If the property is verified, the URL matches exactly, and your Google account has access, record the project URL, GSC property type, and approximate time of the failed attempt. This information helps identify whether the issue is account-specific or service-wide. If you see a message such as “Activate your first site” even though sites are already active, the Manage Sites display may not be synchronized with the activation status. Avoid repeatedly changing properties and wait before trying again. 💬 Get help from our team If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Fix Google Search Console Connection and Property Sync

🔍 Overview If your Google Search Console (GSC) account appears connected in Search Atlas but your properties are missing from the report generator, you are not alone. This is a known issue related to how GSC properties are verified and synced after linking your Google account. Follow the steps below to resolve it quickly. ⚠️ Common Symptoms - GSC shows as connected in your integrations settings, but no properties appear in the report generator. - The property dropdown is empty or shows a loading state indefinitely. - Previously visible properties have disappeared after a reconnection. ✅ Step 1: Verify Your GSC Property Access in Google Before troubleshooting inside Search Atlas, confirm that the Google account you connected actually has access to the properties you expect to see. 1. Go to Google Search Console (search.google.com/search-console) in a separate browser tab. 2. Sign in with the same Google account you connected to Search Atlas. 3. Confirm your properties are listed and that your account has at least Full User or Owner permission for each one. If the properties are not visible in Google Search Console itself, the issue is with your GSC permissions, not with Search Atlas. Contact your GSC property owner to request access. 🔄 Step 2: Reconnect Google Search Console in Search Atlas If your properties are confirmed in GSC but still missing in Search Atlas, disconnect and reconnect your Google account to force a fresh sync. 1. Click your avatar in the top-right corner of the platform. 2. Navigate to Integrations (if available in your menu) or look for the Google connection settings within your account area. 3. Locate the Google Search Console connection and click Disconnect. 4. Wait 10–15 seconds, then click Connect and complete the Google authentication flow. 5. When prompted, make sure you grant all requested permissions, including access to Search Console data. Skipping any permission step can prevent properties from loading. 6. After reconnecting, wait up to 2 minutes for the property list to sync, then return to the report generator and check the GSC property dropdown. 🧹 Step 3: Clear Browser Cache and Try a Different Browser Cached data can sometimes prevent updated connection states from loading correctly. 1. Clear your browser cache and cookies, then reload Search Atlas. 2. If the issue persists, open Search Atlas in a private or incognito window or try a different browser entirely (Chrome or Firefox are recommended). 3. Repeat the reconnection steps above if needed. 👥 Step 4: Check Team Member Account Permissions If you are a team member (not the account owner), your role may limit which integrations you can view or manage. 1. Click your avatar in the top-right corner. 2. Go to Team Members (URL: /settings?active_section=team). 3. Confirm your role is set to Admin if you need full access to GSC data and integrations. A Viewer role may have restricted access. If you need your role updated, ask the account owner to adjust your permissions from the Team Members settings page. 💡 Tips to Prevent Future Sync Issues - Use one Google account consistently. Switching between Google accounts can cause property mismatches. - Grant all permissions during setup. Partial permission grants are the most common cause of missing properties. - Re-authenticate after changing GSC permissions. If your Google-side permissions change, reconnect GSC in Search Atlas to pick up the updates. - Avoid disconnecting and reconnecting repeatedly in quick succession. Allow at least 2 minutes between attempts. 🛠️ Still Not Resolved? If you have completed all the steps above and your GSC properties are still not appearing in the report generator, our team can investigate your account directly. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 Fix OTTO Site Setup and GSC Authentication Errors

🗺️ Overview When adding a new OTTO site or connecting a Google Search Console (GSC) property, you may encounter two separate errors that appear around the same time: - Address Country field error — a character limit or formatting validation issue during site setup - GBP token expiration error — a Google Business Profile authentication failure that blocks GSC property connection These are two distinct problems with different causes and fixes. This article walks you through resolving both. 🏳️ Fix 1: Address Country Field Validation Error The Address Country field has a strict character limit and formatting requirement. If the field is not highlighted automatically, the error is still present and will block you from saving. 1. During OTTO site setup, scroll to the Address Country field. 2. Check that the value entered is a valid two-letter ISO country code (for example, US, GB, AU). Do not enter the full country name. 3. Delete any extra spaces or special characters from the field. 4. If the field appears empty or unchanged, click into it, clear the content completely, and re-enter the correct two-letter code. 5. Save the form again. The validation error should no longer appear. If the error persists after correcting the country code, try refreshing the page and re-entering your site details from the beginning before saving. 🔑 Fix 2: GBP Token Expiration Error When Adding a GSC Property A GBP token expiration error means the OAuth connection between Search Atlas and your Google account has expired or been revoked. This prevents Search Atlas from verifying your ownership of Google Search Console properties. Follow these steps to re-authenticate and restore the connection: 1. In the left sidebar, click Local → GBP Projects to go to your GBP projects (/gbp-galactic/gbp-projects). 2. Locate the Google Business Profile project associated with the GSC property you are trying to add. 3. Look for a Reconnect or Re-authenticate button next to the project. Click it. 4. A Google sign-in window will open. Sign in with the Google account that owns or has access to the GSC property. Make sure you select the correct account if you manage multiple Google accounts. 5. Grant all requested permissions when prompted. Skipping any permission will cause the token to fail again. 6. Once authentication is complete, return to your OTTO site setup and attempt to add the GSC property again. If you do not see a Reconnect option, disconnect the GBP project entirely and reconnect it from scratch using the same Google account. ⚠️ Common Reasons the Token Expires - You changed your Google account password after the initial connection was made. - You revoked Search Atlas access in your Google account's security settings. - The OAuth token exceeded Google's inactivity expiration period (typically six months without use). - You connected using a different Google account than the one that owns the GSC property. ✅ Confirm the GSC Property Is Added Successfully 1. After re-authenticating, navigate back to your OTTO site setup. 2. Select the GSC property from the dropdown list. If it now appears, the token issue is resolved. 3. Save the site. Verify that the property is linked by checking for GSC data populating in your site dashboard within 24 hours. If the GSC property does not appear in the dropdown even after re-authenticating, confirm that the Google account you used has Owner or Full User permissions on that property inside Google Search Console directly. Restricted User access is not sufficient for connection. 🔄 If Both Errors Appear at the Same Time Resolve the Address Country field error first, then tackle the GBP token expiration. Attempting to connect a GSC property while the site form still has validation errors can cause both processes to fail in a way that makes it difficult to tell which error is blocking you. Fix them in sequence for the clearest outcome. 💬 Still Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔌 Fix WordPress Plugin 'Not Installed' Status & Connect GSC

🧭 Overview This article covers two common setup issues in Search Atlas: your WordPress plugin showing Not Installed on the dashboard even though it is active and authenticated, and how to connect a domain's Google Search Console (GSC) account to a project. Both issues are straightforward to resolve once you know where to look. 🔍 Why the Plugin Shows 'Not Installed' The Search Atlas dashboard determines plugin status by checking for a specific tracking script on your website — not just whether the plugin is activated in WordPress. If that script is missing or blocked, the dashboard will display Not Installed even if the plugin is authenticated and synced correctly. Common reasons the script may not be detected include: - The Search Atlas script has been removed or overwritten by a theme or plugin update - A security plugin (e.g., Wordfence, iThemes) is blocking external scripts from loading - A caching layer is serving an older version of your page without the script - The plugin was deactivated and reactivated without a proper resync ✅ Step 1 — Verify the Script Is Present on Your Site Before clearing any caches, confirm whether the Search Atlas script is actually present in your page source. This tells you immediately whether the issue is a script problem or a cache problem. 1. Open a browser and navigate to your website's homepage. 2. Right-click anywhere on the page and select View Page Source. 3. Press Ctrl+F (or Cmd+F on Mac) and search for searchatlas or search-atlas. 4. If the script appears in the source, the issue is likely a caching problem — proceed to Step 2. 5. If the script does not appear, the issue is that the script is not being output by the plugin — proceed to Step 3. 🗂️ Step 2 — Clear Caches (If Script Is Present) If the script is visible in your page source but the dashboard still shows Not Installed, a cached response is preventing the dashboard from reading the live version of your page. 1. Log in to your WordPress admin panel. 2. Navigate to your caching plugin (e.g., WP Rocket, W3 Total Cache, LiteSpeed Cache) and clear all caches. 3. If you use a CDN such as Cloudflare, purge the CDN cache for your domain as well. 4. Return to your Search Atlas dashboard and wait up to five minutes, then refresh the plugin status page. 🔧 Step 3 — Reinstall or Resync the Plugin (If Script Is Missing) If the script is not present in your page source, the plugin is not outputting it correctly. Follow these steps to restore normal operation. 1. Log in to your WordPress admin panel. 2. Go to Plugins → Installed Plugins and deactivate the Search Atlas plugin. 3. Reactivate the plugin immediately. 4. In WordPress, go to Search Atlas → Settings and verify the Search Atlas API Key and Plugin Auth Token fields are populated correctly. 5. Repeat the page source check from Step 1 to confirm the script now appears. 6. If a security plugin is installed, temporarily disable it and recheck. If the script appears after disabling it, add the Search Atlas script domain to your security plugin's allowlist before re-enabling it. 📊 How to Connect Google Search Console to Your Project Connecting GSC gives Search Atlas access to your real impressions, clicks, and keyword ranking data for a domain. Follow these steps to link a property. 1. Log in to Search Atlas and open the project for the domain you want to connect (for example, beesmartbeeremoval.com). 2. Go to Site Metrics → Site Explorer and click Open Google Search Console. 3. On the Manage Sites page, click Connect GSC Account. 4. You will be redirected to a Google authentication screen. Sign in with the Google account that has access to the GSC property for your domain. 5. Grant Search Atlas the requested read permissions when prompted. 6. After authentication, a dropdown will display all GSC properties available to that Google account. Select the property that matches your domain exactly (e.g., https://beesmartbeeremoval.com/ or the sc-domain: version if you verified as a domain property). 7. Click Save or Confirm. GSC data will begin populating within 24–48 hours depending on the volume of historical data. Important: You must be signed in to a Google account that is listed as a verified owner or full user on the GSC property. If you do not see your domain in the dropdown, ask the GSC property owner to add your Google account as a user in Google Search Console → Settings → Users and permissions. ⚠️ Quick Troubleshooting Reference - Dashboard still shows Not Installed after rescanning: Allow five minutes after any change before rechecking, as the dashboard scan is not instant. - Script present but status still wrong after cache clear: Contact support using the instructions below for a manual status refresh. - GSC property not appearing in the dropdown: Confirm the correct Google account is connected and that it has at least Full User access in GSC. - GSC data shows zero after connecting: Wait 24–48 hours. If data is still absent, disconnect and reconnect the integration. 💬 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.

Manage, Remove, or Disable GSC Properties

🗺️ Overview If you connected your Google account to Search Atlas and see more Google Search Console (GSC) properties than you need, or are encountering an Access Forbidden error on a project, this article explains what to expect and how to get the right help quickly. 🔍 Why Are Multiple GSC Properties Showing? When you connect a Google account to Search Atlas, the platform may import GSC properties that your Google account has access to. If your Google account has access to several properties, more than one may appear in Search Atlas — even if you only intend to work with one. You can request removal or management of properties you do not need to keep your workspace tidy. 🗑️ How to Remove or Manage an Unwanted GSC Property There is no self-serve option to remove or disconnect a GSC property directly from within Search Atlas. Removing a property requires a backend action by our support team, because properties are tied to your connected Google account at the account level and cannot be unlinked from the workspace interface alone. To have a property removed or disconnected, please have the following information ready when you contact our support team so we can action this for you promptly: - The name or URL of the GSC property you want removed or disabled - Your account email and workspace name - Whether you want the property fully removed or simply hidden from your workspace Note: Removing a property from Search Atlas does not delete it from Google Search Console. It only disconnects it from your Search Atlas workspace. 🚫 Fixing the "Access Forbidden" Error on Your Project The Access Forbidden error means your user account does not currently have the required permission level to open a specific project or property. This is a separate issue from GSC property management. If you encounter this error, here is what you should do: 1. Confirm with your workspace owner or administrator that your account has been granted access to the relevant project. 2. Ask the workspace owner to review your role and permissions and update them if necessary. 3. Once your permissions have been updated, try accessing the project again. If the error persists after your permissions have been reviewed and corrected, contact our support team. When you reach out, please have the following ready: - The name of the project or GSC property showing the error - The exact error message you see on screen - Your account email and workspace name - The name of the workspace owner or administrator who manages your permissions 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 Integration 'No Properties Found' Errors

🧭 Overview Two error messages commonly appear when your Google Search Console (GSC) integration loses its connection or encounters an authentication issue inside Search Atlas: - "Your connected GSC Account doesn't have any project associated" - "No properties found for 1 account" Both errors mean Search Atlas cannot retrieve your GSC properties — usually because of a stale authentication token, a browser cache conflict, or a permission mismatch. Follow the steps below in order to resolve them quickly. ✅ Before You Start: Quick Checklist Confirm the following before troubleshooting the integration itself: - You are logged into the correct Google account — the one that owns or has full access to the GSC property you need. - That Google account has Owner or Full User permission on the GSC property (not Restricted). - The GSC property is verified and active in your Google Search Console dashboard at search.google.com/search-console. - You are using a supported browser (Google Chrome or Mozilla Firefox, latest version). 🔄 Step 1 — Disconnect Your GSC Account 1. Log in to Search Atlas and open Settings from the top-right corner (avatar menu). 2. Go to the Integrations section and locate your connected Google Search Console account. 3. Click Disconnect (or Remove) next to the account showing the error. 4. Wait for the confirmation message that the account has been removed before continuing. 🗑️ Step 2 — Clear Browser Cache and Cookies A stale browser cache is one of the most common hidden causes of GSC authentication errors. Clearing it ensures the reconnection starts from a clean state. 1. Open your browser settings and navigate to Privacy and Security. 2. Select Clear browsing data. 3. Set the time range to All time. 4. Check both Cached images and files and Cookies and other site data. 5. Click Clear data and wait for the process to finish. 6. Fully close and restart your browser before moving to the next step. 🔑 Step 3 — Revoke Search Atlas Access in Google Revoking the old permission token in Google ensures a completely fresh OAuth handshake when you reconnect. 1. Go to myaccount.google.com/permissions in your browser. 2. Find Search Atlas in the list of connected apps. 3. Click on it, then select Remove Access and confirm. 4. If Search Atlas does not appear in the list, proceed to Step 4 — no action is needed here. 🔗 Step 4 — Reconnect Your GSC Account 1. Return to Search Atlas and navigate to Site Metrics → Site Explorer → Manage Sites (page: /gsc/sites-list). 2. Click Connect GSC Account. 3. In the Google sign-in window that appears, select the correct Google account that has access to your GSC properties. 4. When prompted, click Allow to grant Search Atlas the required permissions. Make sure all permission checkboxes are selected before confirming. 5. After the redirect back to Search Atlas, wait 15–30 seconds for the properties to load. ✔️ Step 5 — Verify Properties Are Now Visible 1. Navigate to Site Metrics → Site Explorer → Open Google Search Console (Manage Sites/Connect GSC Account) in Search Atlas (page: GSC Accounts). 2. Confirm your properties are now listed on the GSC Accounts page. 3. Select the correct property and save your settings. 4. Trigger a data refresh or wait for the next scheduled sync to confirm data is flowing correctly. ⚠️ Still Seeing the Error? Additional Checks If the error persists after completing all five steps, review the following: - Multiple Google accounts open: Sign out of all Google accounts in your browser, then sign back in with only the account that owns the GSC property before reconnecting. - Domain property vs. URL-prefix property: Search Atlas supports both types, but ensure the property type in GSC matches how your site is configured. Check your GSC dashboard to confirm the property is verified. - GSC property has no data yet: Newly verified properties can take 24–48 hours before Google populates them with data. The integration may connect successfully but show empty reports until data is available. - Organisation-level restrictions: If your Google account is a Google Workspace account, your administrator may have restricted third-party app access. Contact your Google Workspace admin to whitelist Search Atlas. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Deleted Projects and GSC Connection Issues

Overview This article covers two separate issues you may encounter in Search Atlas: a deleted project that continues to appear in the Active Projects list, and Google Search Console (GSC) sites that do not appear in the connection list despite verified ownership. If you are experiencing either of these problems, our support team can investigate and resolve them on your behalf. Issue 1: Deleted Project Still Appears in Active Projects If you have deleted a project but it continues to show in your Active Projects list, this is a known issue that our support team can look into directly. Before reaching out, try the following basic steps: 1. Perform a hard refresh of the page or sign out and back in to rule out a temporary display issue. 2. Check whether the project can be opened. If it loads normally, try deleting it again and wait for any on-screen confirmation before navigating away. 3. If the project still appears after signing back in, contact support and provide the project name so our team can investigate. Issue 2: GSC Sites Not Appearing in the Connection List If your Google Search Console properties do not appear when you try to connect GSC to Search Atlas, this may be related to your GSC integration setup. Before contacting support, please check the following: 1. Confirm you are signing in with the same Google account that has access to the GSC properties you expect to see. 2. Verify that your GSC properties are active and accessible when you log in directly to Google Search Console. 3. If properties are confirmed active but still do not appear in Search Atlas, contact support and provide the affected GSC property URLs and the Google account email used during 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.

🔍 OTTO Not Detecting Your Website in GA4

🧭 Understanding the Problem There are two separate connections that must be in place for OTTO to detect your website through GA4: - GA4 connected to Search Atlas — your Google Analytics 4 account is authorized inside the platform. - OTTO receiving data from GA4 — OTTO specifically recognizes and maps your website property within that connected GA4 account. Having GSC connected successfully does not guarantee OTTO will detect your site in GA4. These are independent integrations. This article walks you through resolving the GA4 detection failure specifically for OTTO. ✅ Before You Begin Confirm the following before troubleshooting: - Your GA4 account is connected inside Search Atlas (not just GSC). - The website you want OTTO to detect — for example, www.axsysdental.com — exists as a property inside that GA4 account. - You have at least Viewer permissions on the GA4 property. 🔗 Step 1 — Verify GA4 Is Connected to Search Atlas 1. In the left sidebar, click OTTO SEO to open the OTTO dashboard at /seo-automation-v3. 2. Locate your website project and open its settings. 3. Check whether GA4 appears as a connected data source alongside GSC. If GA4 is not listed, you must connect it before OTTO can detect any GA4 property. 4. If GA4 is not connected, navigate to Site Metrics → Site Explorer (GSC Accounts page) and click Connect GA Account, complete the Google authorization flow, and grant access to the correct Google account that owns your GA4 property. 🏠 Step 2 — Confirm the Correct GA4 Property Is Selected Even when GA4 is authorized, OTTO may be pointed at the wrong account or property. This is the most common reason a website is not detected. 1. Inside the OTTO dashboard, open the GA4 connection settings for your project. 2. Check which GA4 Account is selected. If you manage multiple Google accounts, make sure the account shown is the one that contains your website property. 3. Under the selected account, verify the correct GA4 Property is chosen — for example, the property associated with www.axsysdental.com. 4. If the property is missing from the dropdown, it means the authorized Google account does not have access to that property. In this case, disconnect GA4 and reconnect using the correct Google account. 🔄 Step 3 — Disconnect and Reconnect GA4 If the correct property is selected but OTTO still does not detect the website, a fresh authorization often resolves the issue. 1. In the OTTO dashboard at /seo-automation-v3, open the data source settings for your project. 2. Disconnect the existing GA4 connection. 3. Re-authorize GA4 using the Google account that owns the target property. 4. When prompted to select a property, choose the exact property that matches your website URL. 5. Save the connection and wait up to 5 minutes for OTTO to sync and detect the website. 📊 Step 4 — Check Site Metrics for Data Flow After reconnecting, verify that data is flowing correctly by checking Site Metrics. 1. In the left sidebar, click Site Metrics to open the explorer at /site-explorer/list. 2. Search for your website — for example, www.axsysdental.com. 3. If organic and traffic data is populating, the GA4 connection is active and OTTO should now detect the site. 4. If data is missing here as well, this confirms a broader data sync issue that requires backend review by our team. ⚠️ Common Reasons OTTO Cannot Detect Your Website - Wrong Google account authorized — the authorized account does not own or have access to the GA4 property. - Multiple GA4 accounts — the website property exists in a different GA4 account than the one connected. - GA4 property is new — properties created within the last 24–48 hours may not yet be available for OTTO to detect. - Insufficient permissions — the Google account used during authorization has less than Viewer access on the GA4 property. - Website URL mismatch — the URL in your OTTO project does not exactly match the URL registered in the GA4 property (for example, with or without www). 💬 Still Not Detected After Troubleshooting? If OTTO still does not detect your website after completing all steps above, our team can perform a backend verification to confirm the GA4 property mapping and data flow for your specific 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.

🔍 Understanding GSC Account Prefixes: sc-domain Explained

🧩 What Is the sc-domain Prefix? When you connect a website to Search Atlas via Google Search Console (GSC), you may notice your property listed with a prefix such as sc-domain: followed by your domain name — for example, sc-domain:wetspotplumbing.com. This prefix is not an error. It is an internal tag that GSC assigns to properties that were verified and added using the Domain method, as opposed to the URL-prefix method. Search Atlas inherits and displays this label exactly as GSC reports it. - sc-domain: — the property was connected via GSC's Domain verification (covers all subdomains and protocols). - https:// or http:// — the property was connected via the URL-prefix method (covers one specific URL variant). Seeing sc-domain: in front of your domain simply confirms that your GSC property uses domain-level verification, which is actually the broader and more comprehensive of the two connection types. ✅ Is the sc-domain Prefix Causing a Problem? No. The sc-domain: prefix is not the cause of any data issue and does not break your GSC Insights reports. It is a read-only label passed directly from Google and cannot be changed inside Search Atlas. If your GSC Insights data for a property like wetspotplumbing.com appears empty or incomplete, the prefix itself is not the reason. The most common causes of missing or limited data are covered in the section below. 📍 How Location Filtering Affects Data Retrieval One of the most frequent reasons GSC Insights appears to show no data — even when the integration is working correctly — is an active location filter. Here is how it works and what to check: 1. Open Site Metrics → GSC Performance (GSC Insights) in Search Atlas and select your property from the dropdown. Confirm it shows the sc-domain: version of your domain if that is how it was verified in GSC. 2. Check the location filter. If a specific country or region is selected, GSC will only return data for queries originating from that location. If your site has limited traffic from that region, the panel may appear empty. 3. Set location to Worldwide (or the country where your site receives the most traffic) and refresh the report. This is the fastest way to confirm whether location filtering is hiding your data. 4. Check the date range. GSC data has a processing delay of 24–72 hours. If you recently connected the property, select a broader date range to allow data to populate. 5. Verify GSC permissions. The Google account used to connect GSC must have at least Full User access to the property in Google Search Console. Restricted access prevents Search Atlas from retrieving performance data. ⚙️ How to Confirm Your GSC Property Is Connected Correctly 1. Go to Settings → Integrations in Search Atlas. 2. Locate your GSC connection and confirm the property name matches what you see in your Google Search Console account — including the sc-domain: prefix if applicable. 3. If the property is listed but showing no data after following the steps above, try disconnecting and reconnecting the GSC account to refresh the data permission token. 4. After reconnecting, allow up to 24 hours for data to fully sync before investigating further. 🔄 sc-domain vs. URL-Prefix: Key Differences - sc-domain: (Domain property) — Captures data across all subdomains (www, blog, shop) and all protocols (http, https). Recommended for most websites. - URL-prefix property — Captures data only for the exact URL variant verified (e.g., https://www.wetspotplumbing.com). Other variants are tracked separately. If your GSC account contains both a domain property and a URL-prefix property for the same site, make sure you have connected the correct one in Search Atlas. Connecting the URL-prefix version of a property when most of your traffic is indexed under the domain property — or vice versa — will result in incomplete data. 💬 Still Seeing Issues? If you have followed all the steps above and your GSC Insights data is still not loading for your 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.

🔄 Fix Google Search Console Properties Not Connecting

🔍 Overview If you have connected your Google account to Search Atlas and can see your Google Search Console (GSC) properties listed, but are unable to select or connect the correct one, this is a known authentication state issue. The fix involves reconnecting your Google Search Console authentication in Search Atlas to trigger a fresh session. ⚠️ What Causes This Issue This problem occurs when your Google authentication session becomes partially stale or incomplete. Search Atlas can still read your property list from the existing session, which is why properties appear, but the connection required to link a specific property does not complete successfully. Simply reconnecting your Google account may not always reset this state — you may need to fully reauthenticate to establish a clean session. ✅ How to Fix It: Reconnect Your GSC Authentication 1. Log in to your Search Atlas account. 2. Navigate to the section of the platform where your Google Search Console connection is managed. 3. Disconnect or remove your existing Google Search Console connection. 4. Reconnect your Google account by going through the Google sign-in and permission flow again. When prompted, sign in with the Google account that owns or has access to the GSC property you want to connect. 5. Grant all requested permissions when prompted. Approving every permission Google lists helps ensure the connection completes successfully. 6. Once returned to Search Atlas, your properties should reload and you should now be able to select and connect the correct property. 💡 Tips to Ensure a Successful Connection - Use the correct Google account. Make sure you authenticate with the Google account that has verified owner or full user access to the GSC property. Restricted or delegated access accounts can sometimes cause partial failures. - Approve all permissions. If you skip or deny any permission during the Google OAuth flow, the connection may appear to succeed but will fail when selecting a property. - Avoid using browser autofill during OAuth. Autofill can pre-select the wrong Google account. Confirm the correct account is selected on Google's sign-in screen before proceeding. 🔁 Before Escalating If reconnecting your Google Search Console authentication does not resolve the issue, please have the following ready when you contact support: your Search Atlas project name, the GSC property URL you are trying to connect, the Google account email used during authentication, and a description of exactly where in the process the connection fails (for example, whether properties still do not appear, or whether a specific property still cannot be selected after reauthentication). 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.

🔗 GA4 Property Update Not Reflected on Project Details Page

If you updated your GA4 property on the Search Atlas homepage and received a success message, but the Project Details page still shows "Connect Google Analytics with OTTO", your connection is intact — a display sync bug caused this false state, and it has since been resolved. A hard refresh confirms your updated connection; reconnect manually only if the issue persists. 🔍 What This Issue Looks Like After a successful GA4 property update on the homepage, the Project Details page may show: - A "Connect Google Analytics with OTTO" prompt, as though GA4 was never configured - The GSC Connections panel listing GA4 as not connected These were display-only errors — your GA4 property update was applied correctly in the background. No data was lost and no reconnection was required. ✅ How to Confirm Your GA4 Connection Is Working A hard refresh forces the Project Details page to load the latest connection state from the server: 1. Navigate to the Project Details page for the affected project. 2. Press Ctrl + Shift + R (Windows / Linux) or Cmd + Shift + R (Mac) to hard refresh. 3. Open the GSC Connections panel on the Project Details page. 4. Confirm your GA4 property is listed as Connected. After the hard refresh, the connection status reflects your most recent GA4 update. 🛠️ What to Do If GA4 Still Shows as Disconnected If the disconnected prompt persists after a hard refresh, reconnect GA4 directly from the Project Details page: 1. On the Project Details page, click Connect Google Analytics with OTTO. 2. Select your GA4 property from the dropdown list. 3. Click Connect to confirm. You'll see your GA4 property listed as Connected in the GSC Connections panel once saved. If your GA4 property doesn't appear in the dropdown Verify that the Google account linked to Search Atlas has at least Viewer permission on the GA4 property. Check this in Google Analytics → Admin → Property Access Management. Once access is confirmed, return to the Project Details page and reconnect. ⚙️ How to Update Your GA4 Property from the Search Atlas Homepage To change which GA4 property is linked to your project: 1. Go to the Search Atlas Homepage and locate your project card. 2. Click the More actions for [domain] menu on the project card to open Project Settings. 3. Under Google Analytics 4, select the new property from the dropdown. 4. Click Save. A green confirmation message confirms the update was applied. 5. Navigate to the Project Details page and hard refresh (Ctrl + Shift + R / Cmd + Shift + R) to confirm the change is reflected in the GSC Connections panel. The Project Details page now syncs GA4 connection status in real time after each homepage update. 🎯 The GA4 display sync issue has been resolved — your property update was never lost, even when the Project Details page showed a disconnected state. If you continue to see connection problems after following these steps, contact the Search Atlas support team for further assistance.

🔌 Fix GSC and GA Connection Issues in Search Atlas

🧭 Overview If your Google Search Console (GSC) or Google Analytics (GA) accounts are not appearing in the Search Atlas connection wizard, the most common cause is an expired or incomplete authentication session. This article explains what typically causes this problem and what to have ready when contacting our team for assistance. ⚠️ Why Accounts May Not Appear in the Connection Wizard When GSC or GA accounts are missing from the connection wizard, it is almost always caused by one of the following: - Your Google authentication session has expired or was revoked. - The Google account connected to Search Atlas does not have access to the properties you are trying to add. - A previous connection attempt was interrupted, leaving the integration in an incomplete state. - You have recently added new properties to your Google account but Search Atlas has not refreshed the token to reflect those changes. The primary fix for all of these scenarios is reauthentication — disconnecting the existing Google account link and reconnecting it fresh. 🔄 Before Reaching Out: Things to Check First Before contacting support, please verify the following, as these checks will help our team resolve your issue faster: - Confirm that the Google account you are using to connect is listed as an Owner or Full User on the GSC and GA properties you want to add. Restricted users may not be visible in third-party integrations. - Make sure you are signing in with the correct Google account — the one that actually has access to the missing properties. - Try disconnecting and reconnecting your Google account from within Site Metrics → Site Explorer → Open Google Search Console (Manage Sites / Connect GSC Account, page: 'Your connected GSC Accounts'), granting all requested permissions during the OAuth flow. If you skip any permission, some properties may still not appear. - If you have recently added new properties to Google Search Console or Analytics, allow a short period for Google to propagate the changes before reconnecting. 📂 Consolidating Duplicate Projects If you ended up with duplicate projects because you attempted multiple connection setups, our support team can help you consolidate your data into a single core project. To make this process as smooth as possible, have the following ready when you reach out: - The exact name or URL of the project you want to keep as your primary project. - The names of any duplicate projects you would like to merge or remove. - A note on which project currently has your GSC and/or GA data connected. 🛠️ What to Have Ready When Escalating If the issue persists after the checks above, our support team will need the following information to investigate: - Your Search Atlas project name and the domain you are trying to connect. - The Google account type you are using for authentication. - A description of what you see in the connection wizard and at what step the issue occurs. - Any error messages displayed during the OAuth flow. 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 Keyword Optimization Issues

🧭 Overview If the keyword optimization tool keeps prompting you to connect Google Search Console (GSC) even though you have already linked it, or if you are seeing zero suggestions, this guide walks you through the most common causes and how to fix them step by step. ⚙️ Step 1: Verify Your GSC Connection Is Active A GSC account can appear connected but still fail to pass data if permissions were revoked or the authorization expired. Follow these steps to confirm the connection is fully active: 1. In the left sidebar, navigate to Site Explorer. 2. Look for a Google Search Console status indicator or connection banner at the top of the page. 3. If you see a Reconnect or Reauthorize prompt, click it and complete the Google sign-in flow again. 4. Make sure you grant all requested permissions during the authorization screen — partial permissions will cause the tool to behave as if GSC is not connected. 🌐 Step 2: Confirm the Correct Property Is Selected GSC connections are property-specific. If your GSC account contains multiple properties (for example, both https://example.com and http://www.example.com), the tool may be linked to a different property than the one you are optimizing. 1. Inside Site Explorer, check which domain or URL property is currently associated with your project. 2. Make sure the selected GSC property exactly matches the site you are working on, including the protocol (https:// vs http://) and subdomain (www vs non-www). 3. If they do not match, disconnect the current property and reconnect using the correct one. 📊 Step 3: Understand Why You May See Zero Suggestions Even with a valid GSC connection, zero keyword optimization suggestions can appear for a few reasons: - New website or property: GSC requires at least a few weeks of crawl and impression data before meaningful suggestions can be generated. If your site was recently added to GSC, wait until data accumulates. - Low search traffic: If your pages receive very few impressions in Google Search, there may not be enough ranking signal data to surface suggestions. - GSC data delay: Google typically delays performance data by 2–3 days. Suggestions are based on this data, so a very recent connection may not reflect current activity yet. - Unverified GSC property: If the property is not fully verified inside Google Search Console itself, data will not flow through. Log in to search.google.com/search-console directly to confirm verification status. 🛠️ Step 4: Reconnect and Refresh Your Data If the above checks did not resolve the issue, a clean reconnection often fixes persistent authorization problems: 1. Disconnect your current GSC account from within Search Atlas. 2. Clear your browser cache and cookies, or try a different browser to rule out session conflicts. 3. Reconnect GSC by following the on-screen prompts in Site Explorer; all verified properties on the Google account will be imported automatically. 4. Wait up to 24 hours for suggestion data to populate after a fresh connection. 💡 Tips for Getting the Best Keyword Suggestions - Use the Rank Tracker (left sidebar → Keywords → Rank Tracker) to add and monitor target keywords — this enriches the data available for suggestions. - Explore the Keyword Gap tool (left sidebar → Site Explorer → Keyword Gap) to find opportunities your competitors rank for but you do not yet. - The more pages you have indexed and the more search impressions your site earns, the richer and more actionable your keyword optimization suggestions will become over time. 🆘 Still Seeing the Issue? If you have followed all the steps above and the keyword optimization tool still shows a GSC connection error or zero suggestions, our team can investigate your account directly. 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.

Staging to Production Migration: GSC Connection Guide

Should You Set Up on Staging or Production First? Search Atlas recommends completing your initial setup on your production environment whenever possible. This ensures that the domain Search Atlas tracks matches the property verified in Google Search Console (GSC), which helps prevent authentication mismatches and data gaps. If your workflow requires staging setup first — for example, to test tracking before a site launch — that is supported, but you must reconnect your GSC account after pushing to production. The authentication is tied to the domain and environment at the time of connection, so it does not carry over automatically. What Happens to Your GSC Connection During Deployment? When you push from staging to production, your GSC connection will likely break. This is expected behavior and not a bug. Staging and production URLs are treated as separate properties in GSC, and the authorization state stored by Search Atlas becomes invalid when the domain changes. Until you reconnect, Search Atlas will not be able to pull GSC data for your production site. Recommended Setup Order 1. Launch your production site and verify ownership of the production domain inside Google Search Console. 2. Log in to Search Atlas and navigate to Site Metrics → Site Explorer → Manage Sites/Connect GSC Account (GSC Accounts page). 3. Connect GSC using your production property (see the steps below). 4. Allow some time for data to begin populating from your production domain. If you have already connected GSC on staging and have now deployed to production, skip straight to the reconnection steps below. How to Connect or Reconnect Your GSC Account 1. Log in to Search Atlas and navigate to Site Metrics → Site Explorer → Manage Sites/Connect GSC Account (GSC Accounts page). 2. If a previous GSC connection exists, remove the stale staging connection before proceeding. 3. Initiate a new GSC connection and complete the OAuth authorization flow. Make sure you select the Google account that has access to your production GSC property. 4. Once connected, Search Atlas will automatically import every verified GSC property that the connected Google account has access to. Unverified properties are not imported. 5. Allow some time for production data to begin syncing. If you are unsure which Google account holds access to your production GSC property, check your GSC account directly at search.google.com/search-console before initiating the connection in Search Atlas. 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 Service Account Access Troubleshooting Guide

Overview When connecting Search Atlas to Google Search Console (GSC), a service account must be granted access to your GSC property. If that permission is missing or misconfigured, the connection will fail. This article explains what to check and what information to have ready so our team can resolve your connection issue as quickly as possible. Before You Begin Have the following ready before troubleshooting: - Access to your Google Search Console account - The service account email address provided by Search Atlas (found in Avatar → Settings → Integrations) - Owner-level access to the GSC property you want to connect Step 1: Verify the Correct Service Account Email One common cause of connection failure is adding the wrong email address to GSC. Even a small typo will prevent access. 1. In Search Atlas, locate the service account email address provided in Avatar → Settings → Integrations and copy it exactly. 2. In Google Search Console, open the property you want to connect and confirm that the service account email has been added with the appropriate permission level. If it has not been added, add it now following Google's instructions for managing GSC users and permissions. Step 2: Check Your GSC Property Type GSC has two property types: Domain properties and URL-prefix properties. A mismatch between the property type in GSC and the one selected in Search Atlas can cause a persistent connection error even after permissions are correctly set. - Domain property example: example.com — covers all subdomains and protocols. - URL-prefix property example: https://www.example.com — covers only that exact URL pattern. Make sure the property type and URL you enter in Search Atlas exactly match the property as it appears in GSC. If you have multiple properties listed in GSC, confirm you are connecting to the correct one. Step 3: Confirm the GSC API Is Enabled Search Atlas connects to GSC through the Google Search Console API. If this API is not enabled in the Google Cloud project associated with your service account, the connection may not be possible regardless of permissions. Verify with your Google Cloud project administrator that the Google Search Console API is enabled for the project linked to your service account. Step 4: Re-test the Connection and Escalate if Needed After completing the checks above, retry the GSC connection in Search Atlas. If the connection still fails, gather the following information before contacting support: - The exact error message you are seeing - Your GSC property name and type (Domain or URL-prefix) - The service account email address you added to GSC - A screenshot of the permission settings showing the service account listed in GSC 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 WordPress Plugin Status & Connect GSC

🔍 Overview Two issues commonly appear together when setting up a new project in Search Atlas: the WordPress plugin showing Not installed on the dashboard despite being active on your site, and Google Search Console (GSC) not yet linked to the project. This article walks you through resolving both quickly. 🛠️ Fix the 'Not Installed' WordPress Plugin Status Even if the Search Atlas plugin is installed, activated, and authenticated on your WordPress site, the dashboard may still show Not installed. This is almost always a sync or connection issue, not a plugin problem. Follow these steps in order: 1. Confirm the plugin is active in WordPress. Log in to your WordPress admin panel, go to Plugins → Installed Plugins, and verify the Search Atlas plugin is listed and activated. 2. Check your API key inside the plugin. In WordPress, navigate to the Search Atlas plugin settings and confirm the API key matches the one found in your Search Atlas account under Account Menu → Settings → API Keys. Copy and re-paste it if unsure, then save. 3. Force a re-sync from the Search Atlas dashboard. Open your project in Search Atlas, go to Settings → Integrations → WordPress, and click Reconnect or Re-authenticate if that option is available. This triggers a fresh handshake between your site and the platform. 4. Clear any caching on your WordPress site. If you use a caching plugin (e.g., WP Rocket, W3 Total Cache), clear the cache after saving your API key. Cached responses can block the verification ping Search Atlas sends to confirm installation. 5. Check for plugin conflicts. Temporarily disable other plugins one at a time to rule out conflicts, particularly security plugins that may block outgoing or incoming API requests. 6. Verify your site URL matches the project URL. In Search Atlas, confirm the domain entered for your project exactly matches your WordPress site's URL (including or excluding www). A mismatch will prevent the status from updating. After completing these steps, wait up to 5 minutes and then refresh your Search Atlas dashboard. The status should update to Installed. 📊 Connect Google Search Console to Your Project Linking GSC gives Search Atlas access to your site's real search performance data, which powers keyword tracking, ranking insights, and OTTO SEO recommendations. Here is how to connect it: 1. Make sure GSC is already set up for your domain. Before connecting, confirm your site is verified in Google Search Console at search.google.com/search-console. If your site is not verified there yet, complete that step first. 2. Open the GSC connection flow in Search Atlas. From the main dashboard, navigate to Site Metrics → Site Explorer → Manage Sites to reach the Manage Sites page. 3. Click 'Connect GSC Account'. On the Manage Sites page, click the Connect GSC Account button. You will be redirected to a Google authentication screen. 4. Sign in with the correct Google account. Use the Google account that has Owner or Full User access to the GSC property for your domain. Accounts with Restricted access cannot share data with third-party tools. 5. Grant the required permissions. Review and accept the permissions Search Atlas requests. These are read-only and allow the platform to pull impressions, clicks, and ranking data. 6. Select the correct GSC property. After authenticating, you may be asked to choose which GSC property to link. Select the property that matches your project domain exactly — note that https://beesmartbeeremoval.com and https://www.beesmartbeeremoval.com are separate properties in GSC, so pick the one where your data lives. 7. Save and confirm the connection. Once selected, click Save or Confirm. The integration status should update to Connected within a few minutes. ⚠️ Common Reasons GSC Connection Fails - You are signed into the wrong Google account during the OAuth flow. - The Google account used does not have sufficient permissions on the GSC property. - The domain in Search Atlas does not exactly match a verified property in GSC. - A browser extension (e.g., an ad blocker) is interrupting the Google authentication popup — try in an incognito window or a different browser. ✅ Confirm Everything Is Working After completing both steps, return to your Search Atlas project dashboard. You should see the WordPress plugin status show Installed and the GSC integration show Connected. Data from GSC may take up to 24 hours to begin populating in your reports, as Search Atlas syncs historical data in batches. 💬 Still Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

📊 Fix GSC Quota Errors and Understand Plan Limits

🔍 What Does the 'Quota Exceeded' Error Mean? When you try to connect a Google Search Console (GSC) site and see a Quota Exceeded error, it means you have reached the maximum number of GSC sites allowed on your current plan across your workspace. This is not a Google-side error. The limit is enforced by Search Atlas based on the plan your workspace is subscribed to. 📋 GSC Site Limits by Plan Each Search Atlas plan includes a set number of GSC site connections. If your workspace has reached the maximum for your current plan, you must either remove an existing GSC site or upgrade to a higher plan before adding a new one. If your workspace has not yet reached the maximum for your plan, re-check whether the site you are adding is a duplicate, improperly formatted, or already connected under a different property type (domain vs. URL prefix). 🛠️ How to Fix a Quota Exceeded Error 1. Navigate to your GSC integrations area within the Search Atlas dashboard. 2. Review your connected sites and identify any that are no longer needed. 3. Disconnect any site you no longer require to free up a slot. 4. Try adding your new GSC site again. If you need all existing sites and still require more connections, upgrading your plan is the recommended solution. You can find plan and billing options by clicking your avatar in the top-right and selecting Billing. ⬆️ How to Upgrade Your Plan 1. Open Billing from the top-right avatar menu in the Search Atlas dashboard. 2. Review the available plans and identify one that meets your GSC site connection needs. 3. Follow the on-screen steps to upgrade. 🎁 GSC Connections During a Free Trial The number of GSC site connections available to you depends on the plan tier selected when you started your free trial. To confirm exactly which features and limits apply to your current trial, check your account's plan details page or contact our team for clarification. 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 WordPress Plugin Dashboard & GSC Indexation Issues

Overview If buttons inside the Search Atlas WordPress plugin dashboard are unresponsive, or if your Google Search Console (GSC) instant indexation connection is failing to configure, our support team can investigate and resolve this for you directly. What to Expect Non-functional plugin dashboard buttons and GSC instant indexation connection failures are known issue types that require investigation by our support team. Because the root cause can vary depending on your specific WordPress environment and account configuration, our team will need to look into your setup directly to identify and apply the correct fix. How to Get Help To help our team resolve this as quickly as possible, please have the following ready when you reach out: - Your WordPress site URL - The exact buttons or features that are not responding (e.g. which dashboard section or action) - A description of the GSC issue, if applicable — including whether you have already verified your site in Google Search Console - Any error messages you are seeing, copied exactly as they appear - The timestamp of when the issue started or was first noticed - Your Search Atlas account email or project name 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 'No Project Associated' GSC Connection Error

🔍 Overview When connecting your Google Search Console (GSC) account to Search Atlas, you may see a message stating that your GSC account does not have any project associated with it. This error does not mean your GSC account is broken or that your permissions are incorrect. It simply means your GSC property has not yet been linked to a project inside Search Atlas. ⚠️ Why This Happens Search Atlas requires an active project to be associated with your connected GSC property before it can pull data. If no project is linked, the platform has nothing to map the GSC data to, and you will see the 'no project associated' error. This commonly occurs when: - You have just connected your GSC account for the first time and have not yet selected or created a project. - Your previously linked project was deleted or renamed. - You connected a new GSC property but skipped the project association step. ✅ How to Resolve This Error To fix this error, you need to make sure your GSC property is associated with a project in Search Atlas. Here is what to do: 1. Log in to your Search Atlas account. 2. Navigate to the GSC connection or integration settings within your account (the exact location may vary depending on your plan and interface version). 3. Check whether a project has been assigned to your connected GSC property. If no project is linked, look for an option to select or assign an existing project. 4. If you do not have a project yet, create one first — a project must exist before the association can be made. Make sure the project's domain matches the GSC property you are connecting. 5. Once you have selected or confirmed the correct project, save your changes and return to the GSC data view. The error should no longer appear and your data should begin populating. 📋 What to Check Before Starting To make sure the steps above go smoothly, confirm the following before you begin: - GSC account is connected: Your Google Search Console account must already be authorised inside Search Atlas. If you have not connected it yet, complete the GSC authorisation in your account settings first, then follow the steps above. - You have at least one project: A project must exist in Search Atlas for the association to work. If you do not have a project yet, create one before attempting to link your GSC property. - Correct GSC property: Make sure the GSC property you are connecting matches the domain of the project you are assigning it to. Mismatched domains will result in empty or incorrect data. 🛠️ If You Are Still Seeing the Error If you have followed the steps above and the error persists, it is best to contact our support team directly so they can verify your account configuration and GSC connection status. When reaching out, please have the following ready: - The name of the project you are trying to associate with your GSC property. - The GSC property URL (e.g. the domain or URL prefix you verified in Google Search Console). - A screenshot of the exact error message you are seeing, including any error codes or additional text displayed. 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 a Sudden Google Analytics Bounce Rate Drop

🔍 What Is a Suspiciously Low Bounce Rate? A bounce rate that drops dramatically overnight — for example, falling from 60% to under 10% — almost always signals a tracking configuration problem, not a genuine improvement in user engagement. The most common culprit is double tagging: a situation where Google Analytics fires more than once per page, causing every single-page session to register as a multi-page visit and artificially deflating the bounce rate. ⚠️ Common Causes of an Abnormally Low Bounce Rate - Double tagging: Your GA4 measurement ID or Universal Analytics tag is loaded twice on the same page — once through Google Tag Manager and once hardcoded directly in the page source. - Duplicate GTM containers: Two separate Google Tag Manager container snippets are firing on the same page, each triggering an analytics hit. - Third-party plugins or themes: A WordPress plugin, Shopify app, or website theme has its own built-in GA integration running alongside your manually added tag. - Misconfigured GA4 events: Custom events or scroll-depth triggers are being counted as new page interactions, resetting the session and preventing a bounce from being recorded. - Cross-domain or subdomain tracking issues: Sessions are being split incorrectly, making single-page visits appear as multi-page journeys. 🛠️ How to Diagnose Double Tagging 1. Open your browser's developer tools. In Chrome, press F12 or right-click the page and select Inspect, then navigate to the Network tab. 2. Filter for analytics requests. Type collect or your GA4 measurement ID (e.g., G-XXXXXXXXXX) in the filter bar and reload the page. If you see two or more hits firing on initial page load, double tagging is confirmed. 3. Use Google Tag Assistant. Install the free Tag Assistant Legacy Chrome extension or use Tag Assistant Companion to record a session on the affected site. Look for duplicate GA4 or UA tags flagged in the report. 4. Inspect the page source. Press Ctrl+U (Windows) or Cmd+U (Mac) to view the raw HTML. Search for your GA measurement ID — if it appears more than once, you have a hardcoded duplicate. 5. Audit Google Tag Manager. Log in to your GTM account and check all active tags. Look for multiple GA4 Configuration tags or UA Pageview tags set to fire on All Pages. ✅ How to Fix Double Tagging - Choose one implementation method and remove the other. Best practice is to manage all tags exclusively through Google Tag Manager and remove any hardcoded analytics snippets from the page source or CMS settings. - Disable built-in analytics in plugins or themes. If you use a WordPress plugin such as MonsterInsights, Yoast, or a theme framework that has a built-in GA field, clear that field so the tag only fires through GTM. - Consolidate GTM containers. If multiple GTM snippets are present, work with your developer to merge tags into a single container and remove the duplicate container code. - Publish and verify. After making changes, use Tag Assistant to confirm only one analytics hit fires on page load, then monitor GA4 for 24–48 hours to confirm the bounce rate returns to its historical baseline. 📈 Verifying the Fix in Google Analytics Once you have resolved the tagging issue, confirm the fix is working by checking these areas in your GA4 account: - Navigate to Reports → Engagement → Pages and Screens and confirm that the bounce rate for key pages has returned to a realistic range (typically 30%–70% for most websites). - Check Real-Time reports immediately after publishing your fix to ensure only one active user session is recorded per browser tab. - Review the DebugView (Admin → DebugView) with GA4 debug mode enabled to inspect individual event streams and confirm no duplicate page_view events are firing. 💡 Important Note About Search Atlas Search Atlas is an SEO platform and does not install, manage, or have access to your Google Analytics tags, GTM containers, or site source code. Bounce rate data visible within Search Atlas (for example, under Left sidebar → Site Metrics (Site Explorer)) is sourced from your connected Google Search Console and GA4 property. Diagnosing and fixing a GA tagging issue must be done directly inside your Google Analytics account, Google Tag Manager, and your website's CMS or source code. 🆘 Still Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Fix GA4 Rate Limit Errors and Analytics Report Issues

This article covers Google Analytics 4 (GA4), Google Search Console (GSC), OAuth reconnections, rate limits, report loading failures, property visibility, and analytics filtering behavior inside Search Atlas. ⚠️ Error 1: Analytics dashboard shows "Rate limit exceeded" — no data visible What's happening: This is our most frequent error: 124,000+ occurrences affecting 2,800+ users. Google's Analytics Data API (GA4) rate-limits how many properties can be queried simultaneously. Steps to try: - Wait 15–30 minutes and reload — the rate limit resets hourly - If you have many GA4 properties connected, disconnect properties you are not actively using - This is a Google API limitation — Search Atlas is actively working on request throttling improvements ⚠️ Error 2: Individual GA4 reports (organic traffic, landing pages, sessions) fail to load What's happening: Individual report types hit GA4 rate limits separately. You may see some reports load while others fail. Steps to try: - Click the Retry button on any failed report - Avoid loading all analytics widgets simultaneously — load one section at a time - Each report type rate-resets independently, so retrying staggered (2–3 minutes apart) improves success rate ⚠️ Error 3: Search Console data not syncing — "Disconnected" status What's happening: Google OAuth tokens expire. When this happens, all GSC data stops refreshing. Steps to try: - Top-right Corner Avatar → Settings → Integrations → GSC - Authorize your Google account again - Data will resume syncing within 1 hour of reconnection ⚠️ Error 4: Keyword rankings in GSC differ from what Google shows directly What's happening: GSC reports data with a 2–3 day processing delay on Google's side. Search Atlas shows what Google has reported, not real-time data. Steps to try: - The data you see is accurate as of 2–3 days ago - For same-day ranking data, use: Left Sidebar → Keywords → Keyword Research → Type Your Keywords → Select the geographical location → Search ⚠️ Error 5: Sort/filter options on the Pages report cause a validation error What's happening: A validation issue exists with certain sort parameters in the Pages view, affecting 230+ users. Steps to try: - If a sort causes an error, click the column header again to reset to default sort - Use the Filter panel instead of column sort for filtering by clicks or impressions - This is a known bug being addressed in the next release ⚠️ Error 6: GA4 property not appearing in the connection dropdown What's happening: Only GA4 properties where your Google account has Viewer role or higher will appear. Steps to try: - Confirm in Google Analytics that your Google account (the one you connected) has access to the property - If access was recently granted, disconnect and reconnect your Google account in Search Atlas to refresh the property list ⚠️ Error 7: GSC shows "No data for this date range" What's happening: GSC data is only available from the date your property was connected. Historical data before connection is not available. Steps to try: - Adjust the date range to start from after your connection date - Search Atlas stores your GSC data — data will accumulate over time from the connection date forward ⚠️ Error 8: Analytics shows data for a different country than expected What's happening: GA4 reports use the default property settings. If your property is set to report globally, you'll see global data. Steps to try: - Use the Country filter at the top of the Analytics dashboard to filter by specific country - To make a country filter permanent, save it as a custom view in your dashboard settings Most Google Analytics and Search Console issues are not caused by broken Search Atlas integrations. They are usually related to: - Google API rate limits - OAuth token expiration - delayed Google-side processing - property permission mismatches - or filtering and reporting configuration differences Because Search Atlas depends directly on Google's APIs and reporting infrastructure, temporary delays and throttling behavior are expected during periods of heavy demand. 👉 The best experience comes from: - keeping only active GA4 properties connected - refreshing OAuth permissions regularly - understanding Google’s built-in reporting delays - and loading analytics widgets progressively instead of all at once

🐛 Report Builder and GSC Bug Fixes

This release resolves three bugs affecting Report Builder and Google Search Console, restoring correct behavior for local SEO heatmaps, layout saving, and the Manage Sites country selector. ✨ What's New Three fixes were shipped in this update: - GSC Manage Sites — Country Selector Fix: The country selector dropdown in the Manage Sites panel was opening off-screen and displaying invisible search text due to leftover Ant Design (antd) CSS classes conflicting with Shadcn UI components. The dropdown now renders in the correct position with fully visible text. - Classic Report Builder — Local SEO Heatmaps Now Visible: A reversed logic error in the Hide Empty Sections toggle was incorrectly hiding populated Local SEO Heatmap sections while leaving empty ones visible. The logic has been corrected so that only genuinely empty sections are hidden when the toggle is enabled. - Report Builder — Layout Save Now Works Correctly: Saving an existing layout was incorrectly triggering a duplicate name error instead of completing successfully. Updating an existing layout now saves without error. 🛠️ How to Use It 1. Navigate to Google Search Console and open Manage Sites to confirm the country selector dropdown opens in the correct position and search text is fully visible. 2. Open a Classic Report Builder report and enable the Hide Empty Sections toggle to confirm that populated Local SEO Heatmap sections remain visible. 3. In Reports , open an existing layout and click Save to confirm the action completes successfully without a duplicate name error. 📋 What to Expect All three fixes address incorrect behavior introduced by prior changes. No configuration updates or workflow changes are required — corrections are applied automatically. If you previously encountered any of these issues, they should now be fully resolved. 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.

🔌 Atlas AI Agent 400 Error – Search Console Fix

🔍 What You May Be Experiencing If you recently noticed your website traffic data drop suddenly — for example, from 1,000–2,000 daily visits down to around 40 — and you are also seeing a 400 error when running prompts in the Atlas AI Agent, these two issues share the same root cause: a stale or broken Google Search Console (GSC) integration. When the GSC connection becomes disconnected or stops syncing correctly, the Atlas AI Agent loses access to your live traffic and performance data. This causes prompt failures and makes your traffic appear to have collapsed inside the platform. ⚠️ Common Symptoms - Atlas AI Agent returns a 400 error when you submit a prompt - Daily website traffic shown in the platform drops dramatically and unexpectedly - Site Metrics data appears outdated, incomplete, or frozen - AI Visibility or performance insights seem inaccurate or missing 🧩 Why This Happens Google Search Console connections can become stale over time due to expired OAuth tokens, permission changes in your Google account, or property mismatches. When this happens, Search Atlas can no longer pull fresh data from GSC. The Atlas AI Agent relies on this data to respond to prompts — and without a valid connection, it returns a 400 error instead of a useful answer. This is not a problem with your website itself. Your actual traffic has not dropped. The platform simply cannot display or use your data while the GSC connection is broken. ✅ How to Fix It – Reconnect Google Search Console Follow these steps to disconnect and reconnect your Google Search Console integration: 1. Click your avatar in the top-right corner of the platform to open the account menu. 2. Navigate to Settings → Integrations — Note: if your GSC integration settings are housed under a dedicated Integrations or Connected Accounts section visible in your account, navigate there instead. 3. Locate your Google Search Console connection and click Disconnect. 4. Once disconnected, click Connect (or Reconnect) and follow the Google OAuth prompts to sign in and grant permissions. 5. When selecting a property during reconnection, make sure you choose the exact GSC property that matches your website — for example, https://www.yourdomain.com vs. http://yourdomain.com. A property mismatch is a common cause of sync failures. 6. Save your settings and return to Site Metrics (left sidebar → Site Metrics) to confirm your data is loading correctly. ⏳ Data Sync Timeline After reconnecting Google Search Console, please allow 24 to 48 hours for your traffic and performance data to fully resync inside Search Atlas. During this window: - Traffic numbers may still appear lower than expected — this is normal while the sync catches up. - The Atlas AI Agent should resume responding to prompts correctly once the connection is validated, though data-dependent answers will improve as the sync completes. - If you still see a 400 error after 48 hours, proceed to the troubleshooting step below. 🔎 Verify Your GSC Property Is Correct A common reason reconnection does not resolve the issue is a property mismatch. In Google Search Console, the same domain can exist as multiple properties (e.g., with or without www, with http or https). Make sure the property you connect in Search Atlas is: - The property that is verified in your Google Search Console account - The property that has active data — check inside GSC directly to confirm traffic is visible there - The primary version of your domain (the one your visitors actually land on) 🤖 About Atlas AI Agent and AI Visibility The Atlas AI Agent is your in-platform AI assistant that answers questions about your site's SEO performance, traffic trends, keyword rankings, and more. It pulls data in real time from connected sources — including Google Search Console — to generate accurate, personalised answers. AI Visibility is a feature within Search Atlas that tracks how your brand and content appear across AI-generated search results and answer engines. Both features depend on a healthy GSC connection to surface accurate insights. Reconnecting GSC restores full functionality for both. 🛠️ Still Seeing a 400 Error? If you have completed the reconnection steps and waited 48 hours but the 400 error persists when using the Atlas AI Agent, there may be a permissions issue with your Google account or a configuration problem that requires a manual review. 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 Project Associated' Connection Error

🔍 What This Error Means When you connect your Google Search Console (GSC) account to Search Atlas and see the message "Your connected GSC Account doesn't have any project associated", it does not mean your GSC account is disconnected or your credentials are wrong. It means Search Atlas could not find a domain property in your GSC account to link to a project. Search Atlas requires a domain-level GSC property (for example, sc-domain:example.com) to activate a project. URL prefix properties (for example, https://www.example.com/ or https://example.com/) are verified in GSC but are not compatible with project activation in Search Atlas. This is the most common cause of this error. ⚠️ URL Prefix vs. Domain Properties: Key Difference Google Search Console offers two property types: - URL prefix property — covers only URLs that begin with a specific prefix, such as https://www.example.com/. Verification is done via HTML file, meta tag, Google Analytics, or Google Tag Manager. - Domain property — covers all URLs across all subdomains and protocols (http, https, www, non-www) for a root domain. Verification is done via DNS TXT record only. Search Atlas connects to GSC at the domain property level to ensure full site coverage and accurate data aggregation. A verified URL prefix property alone will not satisfy this requirement. ✅ How to Resolve the Error To resolve this error, you need to add a domain property in Google Search Console for your root domain and complete DNS TXT record verification. Once your domain property is verified in GSC, Search Atlas will be able to detect it and activate your project. To add a domain property, go to Google Search Console at search.google.com/search-console, sign in with the same Google account connected to Search Atlas, and add a new property selecting Domain as the property type. Enter your root domain without any prefix (for example, example.com). Google will provide a DNS TXT record — add this record through your domain registrar or DNS provider (such as GoDaddy, Namecheap, or Cloudflare). DNS propagation can take a few minutes up to 72 hours, but verification usually completes within an hour. Once GSC confirms your domain property is verified, return to Search Atlas. The platform should detect the domain property and allow your project to activate. If the error persists after your domain property is verified in GSC, please have the following information ready when you contact us: - The exact error message you see in Search Atlas - Your project name or domain - The Google account email used for the GSC 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.

📊 Understanding GSC Location Quota Consumption Per Plan

🗺️ How GSC Location Quota Works When you connect a site to Google Search Console (GSC) in Search Atlas, each location you track for that site consumes one quota slot from your plan's GSC quota allowance. Most single-region selections — such as United States, United Kingdom, or Australia — use exactly one quota slot per site. However, the World + Canada option is a combined selection that tracks two separate location datasets simultaneously. Because it pulls data for two regions at once, it counts as two quota slots per site, not one. 📋 GSC Quota Allocation by Plan Each Search Atlas plan includes a fixed number of GSC quota slots. The exact quota limits vary by plan tier. To find out how many GSC quota slots your current plan includes, check your plan details inside the platform or reach out to our support team. ⚠️ Why a Small Number of Sites Can Exceed Your Quota This is the most common source of confusion. Your plan may show a certain quota number, and you may have fewer active sites than that number — yet still hit your quota limit. Here is why: If you selected World + Canada as the GSC location for any of your sites, each of those sites consumes 2 quota slots instead of 1. The calculation below shows how quickly this adds up: - Example: 7 sites × World + Canada selected = 14 quota slots used - If your plan quota limit is 10 slots, this would exceed your quota by 4 slots Even a smaller combination can push you over the limit. For example, if your plan allows 10 slots, 5 sites with World + Canada already uses all 10 slots, leaving zero room for any additional sites. 🔢 Quota Calculation Examples Use the examples below to understand how different configurations affect your total quota consumption: - 6 sites, all single-region: 6 × 1 = 6 quota slots used - 5 sites with World + Canada, 0 single-region: 5 × 2 = 10 quota slots used - 3 sites with World + Canada, 3 single-region: (3 × 2) + (3 × 1) = 9 quota slots used - 7 sites, all with World + Canada: 7 × 2 = 14 quota slots used The key formula to remember is: Total quota used = (Sites with World + Canada × 2) + (Sites with single-region × 1). ✅ How to Resolve a Quota Issue If you have hit your GSC quota limit, you have two options: 1. Change one or more sites from World + Canada to a single-region location to reduce your quota consumption. 2. Upgrade to a higher plan tier to increase your total GSC quota allowance. If you are unsure of your current quota limit or need help reviewing your GSC location settings, our support team can assist you directly. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Fix OTTO GSC Connection Slot Limit Errors

🧩 What Is This Error? When you try to connect Google Search Console (GSC) to a project inside OTTO SEO, you may see an error message indicating that OTTO could not create a new service connection for your project. The most common cause is that your current Search Atlas plan has reached its maximum number of OTTO plan slots, so no additional projects can be activated. 📊 Understanding OTTO Plan Slots Every Search Atlas subscription includes a set number of OTTO plan slots. Each slot represents one active project that OTTO SEO can manage and connect to GSC. Once all slots are occupied, OTTO cannot activate new projects until a slot is freed up or your plan is upgraded. - Plan slot: One slot = one active OTTO-managed project with GSC connected. - Slot limit reached: No new GSC connections can be established until a slot becomes available. - Inactive projects still count: Projects that are set up but not actively used may still hold a slot. 🛠️ How to Fix the Error Follow these steps to resolve the slot limit issue and successfully connect GSC to your project. 1. Check your current slot usage. Review how many projects currently have OTTO activated and GSC connected by navigating to the OTTO SEO section of your account. 2. Identify projects you no longer need. Look for projects that are inactive, paused, or no longer relevant to your SEO work. 3. Deactivate OTTO on unused projects. Open the project you want to free up and deactivate OTTO SEO for that project. This releases the slot back to your plan allowance. 4. Retry the GSC connection. Return to the project where you received the error. Attempt to connect GSC again — with a free slot now available, the connection should complete successfully. 5. Verify the connection. Confirm that GSC data is now flowing into your project inside the OTTO SEO dashboard. 🚀 Upgrade Your Plan for More Slots If you need OTTO SEO active across more projects simultaneously, upgrading your Search Atlas plan is the best long-term solution. A higher-tier plan provides additional OTTO slots so you can manage a larger portfolio of sites without hitting connection limits. - Review your current plan and available upgrade options via the top-right avatar → Billing (Plans & Top-ups). - Upgrading instantly increases your slot allowance — no need to deactivate existing projects. 💡 Tips to Avoid This Error in the Future - Regularly audit your active OTTO projects and deactivate any that are no longer in use. - Before adding a new site to OTTO, confirm you have at least one free slot available. - Align your Search Atlas plan tier with the number of sites you actively manage through OTTO SEO. 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 Country Connection Errors

Understanding the Error When connecting Google Search Console (GSC) to Search Atlas, you may encounter an error related to your GSC domain property not being accessible for the country selected during the connection setup. This is typically related to your GSC configuration or the country setting chosen in Search Atlas, rather than a bug within Search Atlas itself. Why This Happens This error can appear when there is a mismatch between your GSC property's available data and the country setting used during the connection in Search Atlas. GSC domain properties (sc-domain) may have limited or no data for certain countries, which can cause the connection to fail when a specific country is selected. Self-Serve Steps to Resolve 1. Try changing the country selection in Search Atlas. When setting up or reconnecting your GSC integration, select a different country — ideally the primary country where your site has indexed data in GSC. If you are unsure which country to select, choose the country where your site receives the most organic traffic. 2. Verify your GSC property exists and is verified. Log in to Google Search Console and confirm that the property you are trying to connect is listed and verified under the same Google account you use with Search Atlas. 3. Check that your GSC property has data for the selected country. In Google Search Console, go to Performance and filter by country to confirm that your property has indexed data for the country you are trying to use in Search Atlas. If no data exists for that country, select a country that does have data. 4. Reconnect your GSC integration. In Search Atlas, disconnect and reconnect your Google Search Console integration, then select the country confirmed in the previous step. 5. Allow time for new properties. If your GSC property was created recently, Google may not yet have sufficient data for country-level results. Wait a few days and try reconnecting. If the Issue Persists If you have followed the steps above and the connection still fails, please have the following ready when you contact our team: - Your Search Atlas project or site name - The GSC property identifier you are trying to connect - The country you selected during setup - The Google account email connected to Search Atlas - A screenshot of the error if possible If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔗 Fix GA4 Access When Email Isn't Linked

🧭 Overview When you send a client a GA4 invitation link and their account appears in Search Atlas but you cannot access the data, the most common cause is that the email address you invited is not linked to an active Google account. Google requires the invited email to be associated with a Google account before the invitation can be fully activated. If this link is missing, the connection appears in the platform but access to the underlying GA4 data is blocked. This article explains how to identify this situation and resolve it using a direct GA4 access grant, which is the most reliable alternative. 🔍 How to Identify This Issue You are likely experiencing this problem if all of the following are true: - You sent your client an invitation link to connect their GA4 property. - The GA4 account appears inside Search Atlas after your client followed the link. - You cannot view any data, reports, or metrics from that GA4 property. - No error message was shown to you or your client during the connection process. This happens because Google silently accepts the invitation step but cannot complete the data handshake when the invited email has no associated Google account. The result is a connected-but-inaccessible state. ✅ Recommended Fix: Grant Direct GA4 Access The most reliable way to resolve this is to have your client grant access directly inside Google Analytics 4, using your Google account email rather than relying on an invitation link. Follow the steps below. 1. Ask your client to log in to their Google Analytics account at analytics.google.com. 2. Navigate to the correct GA4 property. In the left-hand sidebar, your client should click Admin (the gear icon at the bottom). 3. Under the Property column, click Property Access Management. 4. Click the blue + button in the top-right corner of that panel, then select Add users. 5. Enter your Google account email address — this must be the email associated with your Search Atlas account or the Google account you use to connect GA4. 6. Set the role to Viewer or higher. Viewer is sufficient for Search Atlas to read the data. If you need to manage the property, request Editor access instead. 7. Click Add to confirm. Your client does not need to send a separate link — this grants access immediately. Once your client completes these steps, return to Search Atlas and reconnect the GA4 property using your own Google account credentials. 🔄 Reconnect the GA4 Property in Search Atlas 1. Log in to Search Atlas and open the relevant client workspace. 2. Go to the GA4 integration settings for that client. 3. Disconnect the existing GA4 connection that is showing but inaccessible. 4. Reconnect GA4 by authenticating with your Google account — the one your client just granted access to in the previous section. 5. Confirm the property loads correctly and data is visible. 👥 Managing Team Members and Client Connections If you are working with multiple clients or team members and need to review who has connected which accounts, navigate to your Account Menu in the top-right corner of the platform (click your avatar), then select Team Members. This page lists all active users and can help you confirm which Google account was used to initiate the original connection, so you can match it to the correct GA4 access grant. ⚠️ Why Invitation Links Sometimes Fail Google Analytics invitation links are designed for emails that already have an active Google account. Common scenarios that cause silent failures include: - The invited email belongs to a corporate or custom domain that is not set up as a Google Workspace account. - The client forwarded the link to a different person who used a different email to open it. - The client's Google account was recently created and has not been fully verified. - A typo in the email address meant the invite went to a non-existent or unrelated account. In all of these cases, the direct access grant method described above bypasses the invitation flow entirely and resolves the issue immediately. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Fix GSC Quota Errors and Understand Trial Plans

🔍 Overview Two common questions arise when getting started with Search Atlas: seeing a Quota Exceeded error when connecting a Google Search Console (GSC) site, and understanding what you actually get when you select the Pro plan during a free trial. This article answers both. ⚠️ What Is the GSC Quota Exceeded Error? When you connect a site via Google Search Console, Search Atlas pulls data through Google's API. Google enforces strict daily quota limits on how many API requests can be made. If you see a message like Quota Exceeded (8/100), it means the shared API quota for your account or workspace has been reached for that day. This error does not mean there is a problem with your site or your Search Atlas account. It is a temporary limitation imposed by Google. 🛠️ How to Resolve the Quota Exceeded Error 1. Wait 24 hours. Google resets API quotas daily. In most cases, simply trying again the next day will resolve the issue without any further action. 2. Avoid multiple rapid connection attempts. Retrying the same site connection several times in quick succession consumes quota faster. Wait for the reset before trying again. 3. Check the number of connected properties. If your workspace already has many GSC properties connected, each one draws from the same quota pool. Consider whether all connected sites are actively needed. 4. Confirm your Google account permissions. Make sure the Google account you used to connect GSC has full site ownership or verified owner access in Google Search Console. Restricted access can sometimes trigger API errors that resemble quota issues. 💡 Why Does the Counter Show 8/100? The numbers displayed (e.g., 8/100) represent how many quota units have been consumed out of the daily limit allocated to your connection. Once the counter reaches the maximum, no additional GSC data requests can be made until Google resets the quota — typically at midnight Pacific Time. 🚀 What Do You Get With the Pro Plan During a Free Trial? When you select the Pro plan during your free trial, you gain access to the full feature set included in that plan for the duration of your trial period. This lets you thoroughly evaluate the tools before committing to a paid subscription. Key features available on the Pro plan trial include: - OTTO SEO — AI-powered on-page optimization and automated SEO tasks - Site Auditor — full technical SEO crawl and issue reporting - Backlink Analyzer — explore your backlink profile and monitor link acquisition - Content Planner and AI Writer — plan, brief, and draft SEO-optimized content - GSC and Google Analytics Integration — connect your properties for performance data (subject to quota limits described above) - Higher project and keyword limits compared to lower-tier trial options Your trial runs for a fixed number of days from activation. At the end of the trial, you will be prompted to select a paid plan to retain access. No charges are applied during the trial period unless you choose to upgrade early. 📊 Pro Plan vs. Other Trial Plan Options If you are unsure which trial plan is right for you, here is a quick comparison to guide your decision: - Starter plan trial — suitable for individuals or small sites with basic SEO needs; lower limits on projects and keywords - Pro plan trial — best for growing businesses or agencies managing multiple sites; higher limits and access to advanced features - Agency plan trial — designed for teams managing large client portfolios; maximum limits and white-label capabilities You can upgrade your trial plan at any time from your Account Settings page if you find you need more capacity. 🙋 Still Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔌 Fix Report Builder Access After GSC Disconnection

🔍 Overview If you cannot open reports in Report Builder — or if keywords are missing from your reports — the most common cause is a disconnected Google Search Console (GSC) API key. When the GSC connection drops, Search Atlas loses access to the data it needs to populate your reports. Refreshing the API connection typically resolves this immediately. ⚠️ Symptoms of a Disconnected GSC API - Reports in Report Builder fail to open or appear empty. - Keywords are not being pulled into your reports. - Previously working reports suddenly become inaccessible. 🛠️ How to Restore Your GSC Connection 1. Navigate to Reports. In the left sidebar, go to Reports. 2. Open the affected report. Select the report that is inaccessible or missing keyword data (for example, your client or project report) to open its Executive Summary. 3. Refresh the data connection. Click Refresh Summary on the Executive Summary page to trigger a fresh pull from your connected GSC account. 4. Repeat the refresh if needed. In some cases, the API connection requires more than one refresh to fully re-establish. Click Refresh Summary again if the report does not immediately populate. 5. Verify the connection is restored. Confirm that keywords and report data are loading correctly on the Executive Summary. 💡 Why Does This Happen? Google periodically revokes or expires API tokens for connected third-party applications, including Search Atlas. This can happen after a password change on your Google account, a security review, or simply due to token expiry. The disconnection is not always announced — the first sign is often missing data or inaccessible reports. 🔄 Preventing Future Disconnections - If you change your Google account password, reconnect your GSC integration in Search Atlas promptly. - Check Report Builder periodically to ensure keyword data is still being pulled as expected. - If a report stops updating, try a manual data refresh as a first step before escalating. 📞 Still Need Help? If refreshing the data connection does not restore your reports or keywords, your GSC account may need to be fully re-authenticated. 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 Geographic Targeting Country Selection Issues

Overview When you add a domain to Google Search Console (GSC) and configure geographic targeting, you may find that certain countries — including the United States — are greyed out or unavailable in the target country dropdown. This is a known limitation tied to how Google interprets your domain's properties. This article explains what causes the restriction and what you can realistically do about it. Why Country Selection Gets Restricted Google Search Console restricts geographic targeting options based on signals it reads from your domain. The two most common causes are: - Country-code top-level domains (ccTLDs). If your domain uses a country-specific TLD (for example, .co.uk, .de, .fr, .com.au), Google automatically associates that domain with the corresponding country. Because the geographic signal is already built into the domain itself, GSC locks or greys out the country targeting selector — including options like the United States — and you cannot override this through GSC settings alone. - Domain property vs. URL-prefix property. Certain property types in GSC expose different levels of targeting controls. A Domain property may display fewer editable targeting options than a URL-prefix property in some configurations. What You Can Do Use the steps below to diagnose and address the restriction: 1. Identify whether you are using a ccTLD. Go to your domain registrar and confirm your top-level domain. If it is a country-code TLD (any TLD that is not a generic TLD such as .com, .net, .org, .io, etc.), this is almost certainly the cause of the greyed-out selector. GSC does not allow you to change country targeting for ccTLDs — this is a hard Google limitation, not a bug or configuration error. 2. Understand your realistic options if you are on a ccTLD. There are two paths forward: - Accept the limitation. If your business genuinely targets the country associated with your ccTLD, no action is needed — GSC is correctly reflecting your domain's geographic signal. - Migrate to a generic TLD. If you need to target a different country (for example, the United States) and your current domain is a ccTLD, the only reliable resolution is to register a generic TLD (.com, .net, .org, etc.), migrate your site to that domain, and re-add it as a new GSC property. After doing so, the country targeting selector will become available and editable. 3. Check your GSC property type if you are on a generic TLD. If your domain uses a generic TLD but country targeting is still restricted, confirm in GSC whether your property is set up as a Domain property or a URL-prefix property. Navigate to GSC → Settings → Search Console preferences and review the property type. If needed, add a URL-prefix version of your property to access targeting controls. 4. Navigate to the International Targeting report. In GSC, go to Settings → International Targeting → Country tab. If a message states that targeting is not available for your property, this confirms the restriction is domain-level and cannot be changed within GSC. What to Expect If your domain is a ccTLD, no GSC setting change, hosting change, or Search Atlas configuration will unlock the greyed-out country selector — the restriction is enforced by Google at the domain level. The only way to gain full country targeting control is to use a generic TLD. If your domain is already a generic TLD and targeting is still restricted, that is worth escalating so the specific configuration can be reviewed. 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 Failures Caused by Domain Redirects

🧭 Overview Connecting Google Search Console (GSC) to Search Atlas usually takes just a few clicks. However, if your primary domain is redirecting to a secondary domain — or is temporarily unavailable — the OAuth process can complete without errors yet still fail to establish a working connection. This article walks you through diagnosing and fixing that specific scenario. ⚠️ Is This Your Issue? Standard GSC connection problems are often solved by clearing your browser cache, re-authorising permissions, or ensuring you have admin-level access in GSC. If you have already tried those steps and the connection still fails, a domain redirect or domain unavailability issue is likely the root cause. Look for these signs: - OAuth completes successfully but Search Atlas shows the property as disconnected or returning no data. - Your primary domain (e.g., example.com) automatically redirects to a secondary domain (e.g., www.example.com, a regional subdomain, or an entirely different domain). - Your primary domain is temporarily down, parked, or pending renewal. - GSC is verified under one domain variant but Search Atlas was connected using a different variant. - You can log in to GSC directly and see data, but Search Atlas shows an empty or broken property. 🔍 Step 1 — Identify the Domain Variant Verified in GSC Google Search Console treats different domain formats as separate properties. Before reconnecting, confirm exactly which property is verified and active in your GSC account. 1. Log in to Google Search Console at search.google.com/search-console. 2. Open the property selector and review all listed properties. 3. Note the exact URL format that is verified and actively receiving data — for example, https://www.example.com versus https://example.com. 4. If multiple properties exist, identify which one has the most recent data and a confirmed verification status. 🔄 Step 2 — Check Whether Your Primary Domain Is Redirecting A redirect from your primary domain to a secondary domain is one of the most common hidden causes of GSC connection failures. To check this: 1. Open a browser and type your primary domain (without www) directly into the address bar. 2. Watch the address bar after the page loads. If the URL changes, a redirect is active. 3. Note the final destination URL — this is the domain GSC is actually tracking. 4. If your domain shows a parking page, error page, or is completely unreachable, this confirms a domain unavailability issue that will block the connection. 🔗 Step 3 — Reconnect GSC Using the Correct Domain in Search Atlas Once you know the exact verified domain, disconnect the existing GSC property in Search Atlas and reconnect it using the precise URL that is verified in GSC (in 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.

🔍 Choosing the Right Google Search Console Property Type

🔍 Understanding Google Search Console Property Types Google Search Console offers two property types: URL-prefix and domain. Choosing the right one affects which data Search Atlas can access and how your site performance is tracked. This guide helps you select the best option for your needs. 📋 URL-Prefix Properties A URL-prefix property is specific to an exact web address, including the protocol (http or https). For example, https://wiise.com/ is a URL-prefix property. When to use URL-prefix properties: - You only want to track one specific version of your site (e.g., https only, not http) - You have multiple subdomains and want separate tracking for each (e.g., https://blog.wiise.com/ and https://shop.wiise.com/) - You're tracking a specific subdirectory (e.g., https://wiise.com/blog/) - You want granular control over individual site versions URL-prefix property advantages: - More precise data for a single URL version - Easier setup if you only care about one specific address - Automatically includes all subfolders under that path URL-prefix property limitations: - You must set up a separate property for http and https versions - Data is not shared between different protocol versions - Requires more properties if you manage multiple subdomains 🌐 Domain Properties A domain property covers your entire domain across all protocols and subdomains. For example, wiise.com covers both http and https, plus all subdomains like blog.wiise.com and shop.wiise.com. When to use domain properties: - You want a complete view of your entire domain's performance - You have multiple subdomains you want tracked together - You manage both http and https versions and want unified data - You prefer a single property instead of managing multiple properties Domain property advantages: - Covers all versions and subdomains automatically - Simpler to manage if you run a large site with multiple sections - Unified reporting across your entire domain - No need to switch between properties for different protocol versions Domain property limitations: - Less granular control per subdomain or protocol version - Requires domain verification (more setup steps) - All data is combined, making it harder to isolate specific sections ✅ Which Property Should You Connect to Search Atlas? Best practice: Connect a domain property to Search Atlas whenever possible. Here's why: - You get complete performance data for your entire web presence - Search Atlas can track all versions and subdomains in one place - You don't need to switch properties or manage multiple connections - It simplifies future expansion if you add subdomains or change protocols If you only have a URL-prefix property in Google Search Console, you can still use it with Search Atlas, but you'll only see data for that specific URL version. 🔄 How to Switch Property Types If you're currently using a URL-prefix property and want to switch to a domain property, follow these steps: Step 1: Create a domain property in Google Search Console 1. Log in to Google Search Console (search.google.com/search-console) 2. Click the dropdown next to your current property name (top left) 3. Select Create property 4. Choose Domain 5. Enter your domain name without the protocol (e.g., wiise.com, not https://wiise.com) 6. Follow Google's verification instructions (DNS record, HTML file, or other methods) Step 2: Wait for data to populate Google Search Console can take a few days to gather data in your new domain property. This is normal—patience is required here. Step 3: Reconnect Search Atlas to the new property 1. Log in to Search Atlas 2. Navigate to your site settings or integrations section 3. Update your Google Search Console connection to point to the new domain property 4. Authorize Search Atlas to access the domain property if prompted Step 4: Verify the connection Once reconnected, check that Search Atlas is pulling data from your domain property. You should see performance metrics within a few hours. ⚠️ Important Considerations When Switching - Historical data: Switching properties means starting fresh with data collection from that point forward. Your old URL-prefix property data remains in Google Search Console but won't automatically merge. - Verification requirements: Domain properties require additional verification steps in Google Search Console. Budget extra time for this process. - Downtime: You may experience a brief gap in data during the transition. Plan the switch during a low-priority time. - Subdomains: If you use subdomains, domain properties automatically include them. URL-prefix properties do not. 💡 Frequently Asked Questions Q: Can I use both URL-prefix and domain properties at the same time? A: Yes, you can have both in Google Search Console, but Search Atlas can only be connected to one property per site. Choose the one that best fits your tracking needs. Q: Will switching properties cause me to lose data? A: No. Your old property's data stays in Google Search Console. However, Search Atlas will only track data from the property you're currently connected to, so you'll see a "fresh start" in Search Atlas after switching. Q: How long does it take for a domain property to show data? A: Google Search Console typically populates domain property data within 24 to 72 hours, but sometimes longer. Check back after a few days to see performance metrics. Q: What if I have multiple subdomains? A: A domain property automatically covers all subdomains. If you want separate tracking for each subdomain, use multiple URL-prefix properties instead (one per subdomain). 🤝 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 Property Types for Search Atlas

🧭 Overview When integrating Google Search Console (GSC) with Search Atlas, you will be asked to select a property. GSC offers two property types: URL-prefix (for example, https://wiise.com/) and domain (for example, wiise.com). Choosing the right type affects how much data Search Atlas can access and display for your site. 📋 Understanding the Two Property Types URL-prefix property covers only the exact URL you enter, including its protocol and subdomain. For example, https://wiise.com/ would include HTTPS pages on the root domain but would not include http://wiise.com/, https://www.wiise.com/, or any subdomains such as https://blog.wiise.com/. This makes URL-prefix properties narrower in scope. Domain property covers all URLs across every protocol, subdomain, and path associated with a domain. Connecting wiise.com as a domain property gives Search Atlas visibility into http://, https://, www., and all subdomains in a single connection. This is the broader and more complete option. ✅ Search Atlas Recommendation Search Atlas recommends connecting a domain property wherever possible. Here is why: - Complete data coverage: A domain property aggregates clicks, impressions, and ranking data across all protocols and subdomains, giving you an accurate picture of your site's full organic performance. - Fewer gaps in reporting: URL-prefix properties can create blind spots if your site serves traffic across both HTTP and HTTPS, or across multiple subdomains. - More reliable rank tracking: Features in Search Atlas such as Rank Tracker and Keyword Magic benefit from having the widest possible data set to surface accurate keyword positions and trends. - Simplified management: One domain property replaces multiple URL-prefix properties you might otherwise need to create to achieve the same coverage. ⚠️ When a URL-Prefix Property May Be Appropriate A URL-prefix property can be the right choice in specific situations: - You only want to track a specific subdomain or subdirectory (for example, a blog at https://blog.wiise.com/ that is managed separately). - You do not have access to your DNS settings, which are required to verify a domain property in GSC. URL-prefix properties can be verified through alternative methods such as an HTML file upload or a meta tag. - Your organisation requires separate reporting for different sections of a site for internal or client billing purposes. 🔄 Implications of Switching Property Types If you currently have a URL-prefix property connected to Search Atlas and want to switch to a domain property, be aware of the following: - Historical data continuity: Search Atlas pulls data from whichever GSC property is connected at the time. Switching to a domain property will give you broader data going forward, but historical reports already generated under the URL-prefix property will reflect that narrower scope. - Re-verification in GSC: You must verify the domain property inside Google Search Console before connecting it to Search Atlas. Domain verification requires adding a DNS TXT record through your domain registrar or DNS provider. - Reconnection required in Search Atlas: After verifying the domain property in GSC, you will need to disconnect the existing URL-prefix property in Search Atlas and connect the new domain property. To do this, go to Left sidebar → Home and follow the GSC integration steps to select the updated property. - No data is lost in GSC: Both property types coexist independently in Google Search Console. Switching in Search Atlas does not delete or alter your existing GSC properties. 🛠️ How to Connect or Switch Your GSC Property 1. Verify your domain property (wiise.com) in Google Search Console by adding the required DNS TXT record. Refer to Google's official GSC documentation for step-by-step verification instructions. 2. Once verified, log in to Search Atlas and navigate to Left sidebar → Home. 3. Open the GSC integration settings and select the domain property (wiise.com) from the list of available properties. 4. Save your selection. Search Atlas will begin pulling data from the domain property immediately. 5. Allow up to 48 hours for data to fully populate across features such as Site Metrics, Rank Tracker, and Keyword Magic. 💡 Quick Reference - Domain property (wiise.com) — recommended for most users; covers all protocols and subdomains. - URL-prefix property (https://wiise.com/) — use only when you need isolated tracking or cannot verify via DNS. - Switching is safe and does not delete GSC data, but requires re-verification and reconnection inside Search Atlas. 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 a Greyed-Out GSC Property in Report Builder

🗺️ Overview When a Google Search Console (GSC) property appears greyed out in the Search Atlas Report Builder, it means the platform cannot confirm that you have sufficient ownership access to that property in GSC. Until ownership is verified, the property remains unavailable for use in your reports. This article walks you through why this happens and what to check when it occurs. 🔎 Why Is My GSC Property Greyed Out? Search Atlas requires verified ownership of a GSC property before it can pull data into the Report Builder. A property becomes greyed out when one or more of the following is true: - The Google account connected to Search Atlas does not have the required ownership level in GSC. - The GSC property was added to your Search Atlas account but the Google account used during OAuth does not match the owner account in GSC. - Ownership was granted after the initial connection was made, so Search Atlas has not yet re-verified permissions. - The GSC property has not completed its verification process in Google Search Console. ✅ What to Check 1. Confirm your GSC ownership level. Log in to Google Search Console and open the property in question. Make sure the Google account connected to Search Atlas has owner-level access. If it does not, ask the current owner to upgrade your permission level. 2. Verify which Google account is linked to Search Atlas. Confirm that the Google account authorized via OAuth in Search Atlas matches the owner account shown in Google Search Console. A mismatch between the two accounts is a common cause of the greyed-out state. 3. Ensure your GSC property verification is complete. In Google Search Console, confirm that the property in question has passed all required verification steps. An unverified or partially verified property may appear greyed out in Search Atlas. ⏱️ What to Expect If you have reviewed the above and the property remains greyed out, our support team will need to investigate further on your behalf. When reaching out, please have the following ready: - The exact GSC property URL that appears greyed out - The Google account email used to connect GSC to Search Atlas - A screenshot of the greyed-out property in Report Builder - Confirmation of your ownership level in Google Search Console for that 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.

🔄 Switch GA4 to a Different Property

Overview If your Search Atlas account is pulling data from the wrong Google Analytics 4 property — for example, showing metrics for a different domain than the one you manage — our support team can help you get the correct property connected. This article explains what to have ready and how to escalate so the issue is resolved as quickly as possible. What This Issue Looks Like You may notice that the GA4 data appearing in Search Atlas belongs to a different business or domain than your own. This typically happens when a wrong GA4 property was selected during the initial integration setup. Before You Reach Out To help our team resolve this quickly, please have the following information ready: - The name of the project in Search Atlas where the incorrect GA4 property is connected. - The correct GA4 Property Name and Property ID (a nine-digit number) that should be connected. You can find these in your Google Analytics dashboard under Admin → Property Settings. - The Google account email address that has access to the correct GA4 property. - A brief description of what domain or business the current (wrong) integration is showing data for. What to Expect Once you reach out, a member of our team will review your integration settings and work with you to disconnect the incorrect property and ensure the right one is connected. No historical data in Search Atlas is deleted during this 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 GSC Site Limit After Plan Upgrade

Overview After upgrading your Search Atlas plan, you may notice that the number of active Google Search Console (GSC) sites available does not immediately reflect your new plan's limit. In most cases, resolving this requires our support team to manually verify and sync your updated plan entitlements on the backend. The preliminary steps below are worth trying first, but please be prepared to escalate quickly if they do not resolve the issue. Why This Happens Your GSC site limit is tied directly to your active subscription tier. When you upgrade, the system needs to verify and apply your new plan entitlements. In some cases, the update may not reflect instantly due to reasons such as cached browser data or account entitlements not yet syncing across all platform modules. A backend sync by our support team is often required to fully apply the new limit. Preliminary Checks 1. Confirm your upgrade was successful. Navigate to the top-right avatar → Billing (Plans & Top-ups) and verify that your current plan reflects the upgraded tier. Check that the billing charge has been processed. 2. Hard-refresh your browser. Press Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac) to clear the cached page and reload the latest platform data. 3. Log out and log back in. Sign out of your Search Atlas account completely, then sign back in. This forces the platform to reload your updated account permissions and plan entitlements. 4. Check your active site slots. After logging back in, navigate to the GSC site management area of the platform and review how many active sites are currently listed. The count should reflect your new plan's limit. 5. Check workspace settings. If you manage multiple workspaces, ensure you are operating within the workspace that holds the upgraded subscription. Limits are applied at the workspace level, not the individual user level. Backend Resolution — What to Expect If your GSC site limit still does not reflect your upgraded plan after completing the steps above, the most likely resolution is a manual backend entitlement sync performed by our support team. This is not something you can trigger yourself from the platform. When reaching out, please have the following ready so our team can act quickly: - Your account email and workspace name - The date and time of your plan upgrade - The number of active GSC site slots currently shown in your account - A screenshot of your current billing or subscription page confirming the upgraded plan 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 Connection in Report Builder

Overview If one or more of your domains are not linking correctly to Google Search Console (GSC) inside the Report Builder, a broken or incomplete OAuth connection is usually the cause. This article explains what to check and what information to have ready so our team can resolve the issue quickly. Before You Begin - Make sure you are logged in to Search Atlas with the account that has access to GSC for the affected domains. - Confirm you have the appropriate permissions in Google Search Console for each domain you want to link. - Have your Google account credentials ready, as you may be prompted to re-authenticate during reconnection. What to Try First 1. Log in to your Search Atlas account and navigate to Report Builder. 2. Open the report that contains the domain with a broken GSC connection, or create a new report for the affected domain. 3. Locate the Google Search Console integration option within your report. 4. If you see an option to disconnect or remove the existing GSC connection, do so — this removes only the OAuth link between Search Atlas and GSC, and does not affect your underlying Google Search Console data or account. 5. After disconnecting, look for an option to reconnect or add the GSC connection again. Follow the on-screen prompts to authenticate with the Google account that has access to the affected domain, and grant the requested permissions. 6. Once reconnected, verify that GSC data is now appearing correctly in the report. 7. If you manage multiple affected domains, repeat these steps for each domain separately. If the Issue Persists If the GSC connection still fails after attempting the steps above, please escalate to our support team. To help us resolve the issue as quickly as possible, have the following ready: - The exact domain(s) that are failing to connect - The Google account email used to authenticate GSC - Any error message you see during the connection attempt (copy the exact wording) - The timestamp of when you last attempted to connect 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 WordPress Sync, CSS & GSC Issues

What This Article Covers This guide addresses three common questions related to WordPress integration, CSS styling during sync, and Google Search Console connection stability. Each of these issues may require backend investigation, so the steps below explain what is happening and what information to have ready when contacting support. WordPress Sync — Un-Syncing a Page If you need to disconnect a specific page from WordPress sync so that future edits in Search Atlas no longer push to your live site, this typically requires backend investigation. WordPress sync behavior can vary depending on plugin version and site configuration, so our team will need to review your specific setup. What to have ready when escalating: - The project name and the specific page or article URL you want to un-sync. - A description of what you expected versus what happened. - The approximate time you noticed the sync issue. Once a page is un-synced, the content already published on WordPress remains in place unless you manually delete it there. If sync is re-enabled later, Search Atlas may treat the page as a new deployment and overwrite the live WordPress version. Always review your content before re-syncing. OTTO CSS — Why H1 Styling May Change After Sync When Search Atlas deploys content to WordPress, it sends structured HTML including headings, paragraphs, and links. In some cases the H1 and other heading elements may appear differently on your live site after a sync. Search Atlas syncs heading text, body content, and links; it does not directly control your theme's CSS. The visual presentation depends on how your WordPress theme applies its own styling rules to those elements. What you can check: - Open the live WordPress page and inspect the H1 element using your browser's developer tools to see which CSS classes are applied. - Compare the CSS classes on the synced heading to what your theme normally assigns (for example, entry-title or post-title). - If the expected class is missing, you may be able to add it manually in the WordPress editor after sync, or ask your developer to add a CSS rule in your theme's stylesheet that targets the heading output. If the issue persists or you suspect a duplicate H1 tag is being generated, escalate with a screenshot of the affected page, the article title in Search Atlas, and the live WordPress URL so the team can investigate. Google Search Console — Reconnection Issues If your Google Search Console connection has dropped or is showing a disconnection error, this may require backend attention to restore the integration. What to have ready when escalating: - Your Search Atlas project name. - The Google Search Console property URL. - The exact error message or status shown in the platform. - The approximate time the disconnection occurred. 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 Rank Math and Google Search Console Conflicts

🔍 What Is Happening? After installing the Search Atlas WordPress plugin, some customers notice the following issues: - Rank Math throws errors or conflicts with Search Atlas. - Google Search Console connections appear disconnected or stop reporting data. These issues are caused by a known conflict between the Search Atlas plugin and Rank Math SEO. ⚠️ Why This Happens When both Search Atlas and Rank Math are active on the same WordPress site, a conflict can occur that may disrupt Rank Math's functionality and interfere with Google Search Console connections. ✅ What to Do This is a known bug that requires backend investigation. If you are experiencing this conflict, please have the following information ready when contacting support: - Your WordPress site URL - The exact error message or behavior you are seeing in Rank Math - Whether your Google Search Console connections are affected - A timestamp of when 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.

🔧 Fix UK Google Search Console Connection Issues

🧭 Overview Some customers with UK-based Google Search Console (GSC) properties experience a frustrating issue: the property appears to connect successfully, but after saving, the status reverts to Disconnected. This is a known issue our team is actively investigating. 🔎 Why This Happens This issue has been identified with UK-based GSC properties that revert to a disconnected status after an apparently successful connection attempt. The exact cause is under investigation by our engineering team. ⚠️ What to Have Ready When Escalating Because this issue requires backend investigation, please have the following information available when you contact support: - The name of the affected Search Atlas project. - The exact UK GSC property URL as it appears in Google Search Console. - The timestamp (date and approximate time) when the disconnection was last observed. - Any error messages displayed on screen during or after the connection attempt. - The Google account email used to authorise the GSC 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.

🔧 Fix GSC Integration and Address Fields in OTTO

🗺️ Overview When setting up a WordPress OTTO site, you may run into two common configuration issues: your Google Search Console (GSC) property not appearing in the site dropdown, and no visible field to enter a business address. Neither issue is related to billing or quota limits — both have straightforward fixes explained below. 🔍 Issue 1: GSC Site Not Showing in the Dropdown When you create or configure a WordPress OTTO site, you are prompted to select a GSC property from a dropdown. If your site is missing from that list, it is almost always caused by one of the following reasons. ⚠️ Common Reasons Your GSC Site Is Missing - GSC account not connected: Your Google Search Console account has not been linked to Search Atlas. The dropdown only shows properties from a connected GSC account. - Wrong Google account connected: The GSC property you need belongs to a different Google account than the one currently authorised in Search Atlas. - Property not verified in GSC: The site exists in GSC but ownership has not been verified. Unverified properties do not appear in the dropdown. - Property type mismatch: Domain properties and URL-prefix properties are both supported, but the property must be active and returning data in GSC before it appears here. ✅ Steps to Fix a Missing GSC Site 1. Go to OTTO SEO in the left sidebar, then open SEO Automation (URL: /seo-automation-v3). 2. Open your OTTO site settings or begin creating a new WordPress OTTO site. 3. Before selecting a GSC property, confirm your Google account is connected. Look for a Connect Google Search Console option and verify the correct Google account is authorised. 4. If you are signed in with the wrong Google account, disconnect the current account and reconnect using the Google account that owns the GSC property you need. 5. Once the correct account is connected, return to the GSC dropdown — your property should now appear. 6. If the property is still missing, log in to Google Search Console directly at search.google.com/search-console and confirm the site is verified and actively owned under that Google account. 7. After verifying ownership in GSC, return to Search Atlas and refresh the dropdown. Allow up to a few minutes for the connection to sync. 📍 Issue 2: No Field to Add a Business Address On the OTTO site configuration screen, the Single Address tab shows limited fields and may not display a dedicated input for a full business address. This is by design — the Single Address tab is intended for basic location data only. To enter a complete business address, you need to use the Multiple Address tab instead. ✅ Steps to Add a Business Address 1. Go to OTTO SEO in the left sidebar, then open SEO Automation (URL: /seo-automation-v3). 2. Open your WordPress OTTO site settings. 3. Navigate to the address or location configuration section. 4. Click the Multiple Address tab — this tab contains the full address form including street address, city, state, postcode, and country fields. 5. Enter your business address details in the available fields. 6. Save your changes before exiting the configuration screen. Note: If you only need to associate a single location with your site, you can still use the Multiple Address tab — simply add one address entry. This tab gives you complete address fields that the Single Address tab does not provide. 💡 Quick Reference Summary - GSC site missing from dropdown → Check that the correct Google account is connected and the property is verified in GSC. - No address field visible → Switch from the Single Address tab to the Multiple Address tab to access the full address input form. - These issues are not billing or quota related — no plan changes are needed to resolve either problem. 💬 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.