🧩 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:
- 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.
- 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.
- 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.
- 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.
- 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
- Go to Settings → Integrations in Search Atlas.
- 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.
- 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.
- 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.