FAQ
Which report types can I export from Google Search Console?
Coupler.io supports the following GSC report types:
Search results performance (default) — clicks, impressions, CTR, position for Google Search
Search results performance by appearance — same metrics grouped by search appearance type
Discover performance — clicks and impressions for Google Discover
Google News performance — clicks and impressions for Google News
URLs index performance — indexing status, AMP, mobile usability, and rich results for specific URLs
Each data flow exports one report type at a time.
What dimensions are available for each report type?
Available dimensions vary by report type:
Date
Yes
Yes
Yes
Country
Yes
Yes
Yes
Device
Yes
No
Yes
Page
Yes
Yes
Yes
Query
Yes
No
No
The Search results performance by appearance report automatically uses the Search appearance dimension — you don't select it manually.
The URLs index performance report doesn't use dimensions — it reports per-URL inspection results.
Why does my export show "(other)" in the query column?
This is a Google Search Console API limitation. When a site has too many unique queries, Google groups low-volume queries under (other) to protect user privacy. Coupler.io exports the data exactly as the GSC API returns it.
To reduce the (other) bucket, narrow your date range, add a Page filter to focus on specific URLs, or add a Country filter to limit the scope.
Why is recent data missing or showing zeros?
Google Search Console data has a 2–3 day processing delay. Data from the most recent 2–3 days may be incomplete, show zeros, or not appear at all. This is normal GSC behavior.
If you're using the Final data state (default), the cutoff is typically 3–5 days. Switch to All data state if you want the freshest available data, understanding it may be revised.
What's the difference between "Final" and "All" data state?
Final (default): Returns settled data that is several days old and won't change. Best for dashboards and recurring reports where consistency matters.
All: Returns the latest available data, which can be as recent as 24 hours old but may still be revised. Best for ad-hoc checks when you want the freshest view.
For most use cases, Final is recommended.
How do I match the numbers I see in the GSC web interface?
To replicate the GSC UI's default view in Coupler.io, use these settings:
Report type: Search results performance
Search results type: Web
Aggregate data by: Auto
Data state: Final
Same date range as shown in the GSC UI
Same dimensions selected
Any difference in these settings will produce different numbers. Pay special attention to the aggregation method — "By Page" vs. "By Property" counts impressions differently.
Can I export data for multiple sites in one data flow?
Yes. The Sites selector supports multiple selections. Each site's data is identified by the siteURL column in the output. However, for clarity and easier maintenance, consider creating one data flow per site — especially if you need different date ranges, dimensions, or refresh schedules per site.
What is the "Aggregate data by" setting and when should I change it?
This controls how Google deduplicates impressions:
Auto (default) — Google selects the best method. This matches the GSC UI's default.
By Page — Aggregates by canonical URI. One impression per page per query. Best for page-level SEO analysis.
By Property — Aggregates across the entire property. One impression per property per query. Best for overall property health metrics.
By News showcase panel — Only for Discover and Google News reports. Must be combined with a Search appearance = NEWS_SHOWCASE filter.
For most SEO dashboards, leave it on Auto or use By Page.
Can I filter by specific queries or pages?
Yes. Use the Filters by dimensions option. You can filter by Query, Page, Country, Device, or Search appearance using these operators:
Contains / Does not contain
Equals / Does not equal
Including Regex / Excluding Regex
You can filter by dimensions even if they're not selected as report dimensions. For example, you can filter by Query = "coupler" without adding Query as a dimension.
How far back can I export data?
Google Search Console retains performance data for approximately 16 months. You cannot query data older than this limit. If you need long-term historical data, set up recurring exports and store the data in your destination (using "Replace" mode for each run, or archiving snapshots separately).
Why doesn't the Discover or Google News report return any data?
Not all sites appear in Google Discover or Google News. These reports only return data if your site's content is surfaced on those platforms. Check the Google Search Console UI — if the Discover or Google News sections don't appear in the left sidebar, your site has no data for these surfaces.
How does the URLs index performance report work?
Unlike the performance reports, the URLs index performance report requires you to provide an explicit list of URLs (one per line). Coupler.io inspects each URL using Google's URL Inspection API and returns:
Index status — whether the page is indexed, its coverage state, crawl time, and canonical URL
AMP status — validation results for AMP pages
Mobile usability — mobile-friendliness verdict
Rich results — structured data eligibility
This report does not use date ranges or dimensions. It inspects the current state of each URL.
Can I combine GSC data with Google Analytics (GA4) data?
Yes. Set up separate data flows for GSC and GA4, then combine them in your destination using Coupler.io's data join or in your BI tool. Join on the page URL from GSC with the landing page path from GA4.
Note that GSC uses full URLs (e.g., https://example.com/blog/post) while GA4 typically uses paths only (e.g., /blog/post). You may need a formula column to extract the path from the GSC URL for joining.
See Combining GSC data with other sources in Best Practices for details.
My data flow is timing out. What should I do?
Timeouts typically occur when exporting long date ranges with many dimensions. To fix this:
Reduce the date range (e.g., 30–90 days instead of 12 months)
Remove unnecessary dimensions — each dimension multiplies the row count
Add dimension filters to scope the export (e.g., filter by country or page path)
Split large exports into multiple data flows with non-overlapping date ranges
See Common Issues for more timeout troubleshooting steps.
Last updated
Was this helpful?
