This article explains how to reconnect Google Search Console (GSC) in Search Atlas and confirm the right property is selected so search data can load again.
π§ Before You Start
Check the following items before you troubleshoot. Most reconnection problems come from one of them.
- Google account: Use the same Google account that owns or has full access to the property in Search Console.
- Property type: Search Console properties are either Domain properties, shown as sc-domain:example.com, or URL-prefix properties, shown as a full URL such as https://www.example.com/. In Search Atlas, choose the property URL that belongs to your website. You do not enter an address that must exactly match it.
- Permissions: Your Google account needs verified access to the Search Console property. Owner, Full, and Restricted access can all be used to pull search data. An unverified property is not available. Owner access is required only for ownership-only actions, not for pulling search data.
- Browser: Pop-up blockers and third-party cookie blocks can stop the Google sign-in window from finishing. Allow pop-ups for the platform while you reconnect.
π Step 1: Remove the Old Connection
An old or partial connection can block a new one. Removing it first gives you a clean start.
- Open the integrations settings in the platform.
- Find the Google Search Console integration and choose the option to disconnect or remove it.
- Sign out of the Google account in your browser, or open a private browsing window.
π οΈ Step 2: Reconnect with the Correct Property Address
Reconnecting with the wrong address is the most common cause of a failed integration. Follow these steps carefully.
- Start the Google Search Console connection from the platform.
- Sign in with the correct Google account and approve the requested permissions.
- After you choose the Google account, select the Search Console property URL for your website. If more than one connected account has a matching property, choose it in the Choose a Search Console property dialog and select Use this property.
- If you already added the property address in Search Console, make sure you did not enter a slightly different version, such as a missing www or a http version instead of https.
- Wait a few minutes, then refresh the platform page.
β Step 3: Confirm the Connection Is Working
A connection can appear active even when data is not syncing. Check these signs to confirm it is working:
- After a successful connection, Search Atlas shows Google Search Console connected. If no properties are found or credentials fail, it shows an error or banner instead.
- Search performance data begins to appear within the expected sync window. New connections can take time to show full history.
- The property shown in the platform matches the property shown in Search Console.
π Step 4: Allow Time for Data to Load
After a successful reconnect, data may not appear right away. Google limits how much historical data is available through Search Console, and the platform needs time to collect it. If the connection is valid but data is still empty after a day, the issue is usually the property match or permissions, not the connection itself.
β οΈ Step 5: Fix the Publish Problem in a CloudStack
Some customers see only a loop between the edit and preview screens and no publish link. This usually means the CloudStack still has a required setting that has not been saved or completed.
- Save any open changes, then refresh the page.
- Review every required field in the CloudStack and make sure each one has a value. Required fields that are blank can keep the publish option hidden.
- Confirm your user role allows publishing. Viewer or editor roles may not have publish rights.
- Make sure the GSC integration is connected before publishing, if the CloudStack depends on Search Console data.
- If the publish option is still missing after these checks, move on to the support steps below.
π© Common Problems and Quick Fixes
- Error about access denied: Your Google account lacks the required permission in Search Console. Ask the property owner to grant Full access.
- Property not listed: The Google account you signed in with does not have the property. Sign in with a different account or add the property in Search Console first.
- Connected but no data: The property address does not match the one in Search Console. Reconnect using the exact property.
- Sign-in window closes early: A pop-up or cookie blocker is interfering. Allow pop-ups and try again in a private window.
π¬ Need More Help?
If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.
To help us resolve your issue faster, include the following in your message: the property address you are trying to connect, the Google account email you used, any error message shown on screen, and whether you can see a publish link for your CloudStack.