---
title: "About search query discrepancy correction in Google Search Console data"
slug: "about-search-query-discrepancy-correction-in-google-search-console-data"
description: "Learn how to correct Google Search Console discrepancies with Supermetrics, ensuring accurate reporting of rare search queries and metrics."
updated: 2026-06-03T08:28:50Z
published: 2026-06-03T08:28:50Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.supermetrics.com/llms.txt
> Use this file to discover all available pages before exploring further.

# About search query discrepancy correction in Google Search Console data

To protect user privacy, Google Search Console doesn’t show very rare search queries in its results. It omits them completely when the “Search query” dimension is used either in a query or as a filter.

If a site brings a significant number of these types of searches, you’ll see significant discrepancies in your reporting as a result.

## Correcting discrepancies

Supermetrics has a feature that aggregates anonymized searches under “Unknown search query”, including them in overall results to increase accuracy. This feature is enabled by default at the Aggregate level, and can also be enabled at the Page level.

However, the correction feature can only be applied to the “Impressions” and “Clicks” metrics. It won’t work with the “Average position” metric, for example.

****Correction example screenshots****

**With Page-level correction enabled:**

**![Data table showing clicks and impressions for various Supermetrics landing pages.](https://cdn.document360.io/a13cead5-eaae-456f-9bd1-0941d590c0e3/Images/Documentation/google-search-console-page-level-correction.png)** **With Aggregate-level correction enabled:**

**![Table displaying search queries, clicks, and impressions for Supermetrics landing pages.](https://cdn.document360.io/a13cead5-eaae-456f-9bd1-0941d590c0e3/Images/Documentation/google-search-console-aggregate-level-correction.png)**

## Instructions

Disable or enable anonymized search query correction in your destination.

****Google Sheets****

1. Open the Supermetrics sidebar.
2. Select the query to modify, and click the pencil icon to edit.
3. Go to **Options**.
4. Select your discrepancy correction level in the **Correction for Google discrepancies** dropdown.

****Data Studio (formerly Looker Studio)****

1. Click on any report element to open Supermetrics.
2. Click the **Edit icon** next to the Google Search Console data source.
3. Click **Edit connection**.
4. Scroll down to **Correction for Google discrepancies** and select your correction level.

****Excel****

1. Open the Supermetrics sidebar.
2. Select the query and click **Modify**.
3. Go to **Options**.
4. Select your discrepancy correction level in the **Correction for Google discrepancies** dropdown.

****Power BI****

1. Go to the [Power BI query list](https://hub.supermetrics.com/power-bi/query-list) on the Supermetrics Hub.
2. Select a Google Search Console query and click the edit button.
3. Select the connection to use.
4. Click **Options**.
5. Select your correction level from the **Correction for Google discrepancies** dropdown.

****Data warehouse and cloud storage****

Select your correction level from **Correction for Google discrepancies** [during transfer configuration](/v1/docs/how-to-create-a-transfer).

1. On the [Supermetrics Hub](https://hub.supermetrics.com/), go to **Data transfers** under **Manage**.
2. Select the transfer you'd like to edit.
3. Under **Correction for Google discrepancies**, select **Disabled**, or adjust your correction level to Page or Aggregate.

****Query Manager (The Supermetrics API)****

1. On the [Supermetrics Hub](https://hub.supermetrics.com/), go to **API queries** under **Manage**.
2. Select **Google Search Console**as your data source.
3. Go to **Options**.
4. Select your discrepancy correction level in the **Correction for Google discrepancies** dropdown.

## Troubleshooting

If major discrepancies persist after you’ve enabled discrepancy correction, the cause might have to do with other aspects of Google Search Console. [Learn more about these types of discrepancies](/v1/docs/about-discrepancies-in-google-search-console-results).