Why SEO Numbers Don't Match Google
You pull up Brass-SEO and see 1,200 clicks for the month. You open Google Search Console directly and see 1,350. You check GA4 and it shows something different entirely. None of the numbers match, and now you're not sure which one is right.
This is one of the most common points of confusion in SEO — and it has clear, fixable explanations. The numbers differ because each tool measures something slightly different, using different data collection methods, with different date ranges and filters applied. Here are the four reasons this happens.
Quick Navigation
- Reason 1: The 2–3 Day Data Delay
- Reason 2: Different Property Types
- Reason 3: Applied Filters
- Reason 4: API vs. Web Interface
- How to Compare Accurately
- Frequently Asked Questions
Reason 1: The 2–3 Day Data Delay
Google Search Console has a 2–3 day delay before data is fully finalized. The last 48–72 hours of data in GSC is typically incomplete — Google has collected some of it, but processing is still ongoing.
This creates a discrepancy when you compare:
- Brass-SEO or API data: pulls exactly what the API returns, which includes the partially-processed recent days
- GSC web interface: sometimes shows "provisional" numbers for recent days that look complete but are still being updated
The result is that both tools can show different numbers for the same date range — even though they're both pulling from GSC — because one is reading finalized data and the other is showing an estimate.
The fix: Use date ranges that end at least 3 days ago. For "Last 30 days" comparisons, the vast majority of the data will match. For "Last 7 days," the most recent 2–3 days will be where the discrepancy appears.
Reason 2: Different Property Types
In Google Search Console, your site might be verified as either a Domain property or a URL-prefix property. These collect data differently.
Domain property (e.g., sc-domain:example.com):
- Aggregates data from all subdomains:
www.example.com,m.example.com,blog.example.com - Includes both HTTP and HTTPS versions
- Shows the most complete picture of your site's search performance
URL-prefix property (e.g., https://www.example.com/):
- Only shows data for that exact URL format
- Does not include other subdomains or the HTTP version
- If your site serves traffic on both
wwwand non-www, the property only captures one
If Brass-SEO is connected to a URL-prefix property, and you're looking at a domain property in the GSC web interface (or vice versa), the numbers will be different — not because either is wrong, but because they're measuring different scopes.
The fix: Check which property type you have connected. In Brass-SEO, the property name appears in the property selector above the chat. Domain properties start with sc-domain:. If the scope doesn't match what you're comparing, you'll need to look at the same property type in both places.
Reason 3: Applied Filters
Brass-SEO and GSC can both apply filters to data — by country, device, search type, or specific pages. When filters differ between what you're viewing in two places, the totals will differ.
Common filter mismatches:
- Brass-SEO querying "Organic Search" only while GSC is showing "Web + Image + Video"
- Brass-SEO filtering to one country while GSC shows global traffic
- Comparing page-level data where the URL formats differ slightly (with/without trailing slash, HTTP vs HTTPS)
The fix: Before comparing numbers, check what filters are active. In GSC, the filter bar appears above the chart. In Brass-SEO, you can ask "Show me my clicks for [date range] with no filters applied" and the AI will run an unfiltered query.
Reason 4: API vs. Web Interface
Brass-SEO pulls data directly from the official Google Search Console API and Google Analytics API. The GSC and GA4 web interfaces use the same underlying data, but the display layer sometimes applies rounding, sampling, or presentation logic that the raw API does not.
For large datasets, GSC and GA4 may apply data sampling in their web interfaces — showing approximated numbers to load dashboards faster. The API typically returns unsampled data for the same query.
This means in some cases, the API data (what Brass-SEO shows) can be more precise than what the web interface displays.
The fix: If a specific metric looks off, ask Brass-SEO to pull the raw numbers for that exact date range and metric. The response will show exactly what the API returned, which you can compare directly.
How to Compare Accurately
If you want to verify that Brass-SEO's numbers match Google, use this approach:
- Use the same date range — and make sure it ends at least 3 days ago to avoid the GSC delay
- Match the property — confirm both tools are looking at the same GSC property type
- Check filters — no country, device, or page filters applied in either tool
- Use the same metric — clicks in GSC ≠ sessions in GA4 (they measure different things)
Still seeing a difference after checking all four? Ask Brass-SEO: "Show me my total clicks from [date range] with no filters." The response will tell you exactly what date range and filters were used, making it easier to match against what you see in Google.
Frequently Asked Questions
Is Brass-SEO pulling from the same data as Google?
Yes — Brass-SEO reads directly from the official Google Search Console API and Google Analytics Data API. It is the same underlying data Google uses in their own dashboards. Differences come from the four reasons above (date delay, property type, filters, and API vs. interface display logic).
Why do my GSC clicks not match my GA4 sessions?
They measure different things. GSC counts a click when a user clicks your result in Google's search results page. GA4 counts a session when a user lands on and interacts with your site. A user can click your result in GSC and still not register as a session in GA4 (if they immediately bounced before the tracking script fired, for example). For a full explanation of what each tool measures, see GSC vs GA4: What Each One Tells You.
Why does the GSC web interface sometimes show higher numbers than the API?
The GSC web interface sometimes shows provisional data for recent days — numbers that look complete but are still being finalized by Google. The API returns only finalized data. If you're comparing recent days (within the last 3 days), the interface may appear higher while the API shows lower, more conservative numbers. Both will converge once Google finalizes the data.
How do I find out which filter is causing my number to be different?
Ask Brass-SEO directly: "Show me my total clicks for [date range] with no filters applied." Then compare that to the same query in the GSC web interface with no filters. If the numbers still differ, check the property type (domain vs. URL-prefix) as the next step.
Related
- GSC vs GA4: What Each One Tells You — what each data source measures and why both are needed
- Why GSC Data Is 2-3 Days Behind — a deeper look at the GSC data delay
- Your First SEO Analysis — how to run your first analysis using both data sources
- Google Search Console for Small Business — getting started with GSC