## **🤔 Why This Happens**

Google Search Console treats **https://seniorcarehomes.com** and **https://www.seniorcarehomes.com** as two completely separate properties, each with its own independent dataset. If your website canonically serves traffic on the non-www version but your Search Atlas project is pulling data from the www property, you will see a mismatch: one property shows hundreds of keywords while the other shows zero.

This is not a bug. It reflects exactly how Google stores data. The fix is to ensure Search Atlas is connected to the GSC property that actually holds your traffic and indexed pages.

## **🔍 Step 1 — Identify Your Primary GSC Property**

Before changing anything in Search Atlas, confirm which property contains your real data inside Google Search Console.

1. Go to **Google Search Console** (search.google.com/search-console).
2. Open the property selector in the top-left corner.
3. Compare the **Total clicks** and **Total impressions** for both the www and non-www versions over the last 90 days.
4. The property with higher numbers is your primary property — note its exact URL format.

In most cases the non-www version (e.g. **https://seniorcarehomes.com**) is the canonical source when a 301 redirect from www to non-www is in place.

## **⚙️ Step 2 — Make Sure the Correct GSC Property Is Connected in Search Atlas**

Search Atlas can only pull data from a GSC property that is already verified in your Google Search Console account and connected to your Search Atlas workspace. Because the exact steps for reconnecting or reassigning a GSC property depend on your account configuration, please have the following information ready before reaching out:

- The exact URL of your primary GSC property (e.g. **https://seniorcarehomes.com** vs **https://www.seniorcarehomes.com**).
- The name of the Search Atlas project that is showing 0 keywords.
- A screenshot or note of the Total clicks/impressions figures from both properties in GSC.
- Whether both the www and non-www versions are verified in your Google Search Console account.

If the correct property is not yet verified in Google Search Console, verify it there first — Search Atlas can only surface properties that are already confirmed in your GSC account.

## **🎯 Step 3 — Escalate to the Support Team**

Once you have confirmed which GSC property holds your real data and have the details listed above ready, contact the support team. A teammate will identify which property is currently assigned to your project and reassign it to the correct one so your keyword data populates accurately.

If you need further assistance, open the chat widget in the bottom-right corner of the platform and type **human teammate** to be connected with a member of our team.