"I'm experiencing an issue with the Google Search Console API when using filters on the "searchAppearance" dimension. When applying "notContains", and "notEquals", the API returns only rows where searchAppearance is the value I'm trying to exclude, instead of excluding it. I've attached sample outputs below: - notEquals_JOB_DETAILS - equals_JOB_DETAILS Both return the same results, which shouldn't happen. The notEquals result should include data from all other search appearances except JOB_DETAILS."
"This behaviour occurs both when using the Search Console API directly and when using the Search Analytics for Sheets plugin. This suggests it's not an issue with how I'm calling the API. This seems to be either: - a bug in how notEquals/notContains are being processed for searchAppearance, or - a misunderstanding in how these filters are intended to work for this dimension. Any clarification or confirmation would be greatly appreciated."
"Thanks for reporting this Max, I can confirm this is indeed happening, and it looks like it's a bug."
Google Search Console API returns incorrect rows when filtering on the searchAppearance dimension with notEquals or notContains operators. Instead of excluding the specified appearance, the API returns only rows matching the excluded value. The bug reproduces both via direct API calls and via the Search Analytics for Sheets plugin, indicating the issue is server-side. Sample cases show notEquals_JOB_DETAILS and equals_JOB_DETAILS producing identical outputs where notEquals should include all other appearances. The issue was reported in April and confirmed as a bug by a Google Product Expert, but no fix or response has been issued. Users filtering by searchAppearance should avoid these operators.
Read at Search Engine Roundtable
Unable to calculate read time
Collection
[
|
...
]