深入探究 Search Console 的效果数据过滤功能和限制
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
2022 年 10 月 19 日（星期三）
无论是通过效果报告还是 Search Analytics API，Google 搜索效果数据都是 Search Console 中最常用的数据。此博文详细介绍了可用的数据以及 Google 处理这些数据的方式，包括隐私保护过滤以及与服务延迟、存储和处理资源相关的其他限制。有想过这些系统是如何运作的吗？我们来深入了解一下吧。
如果您刚开始接触 Search Console，请查看效果报告简介。
效果报告包含四个指标，显示了搜索流量在一段时间内的变化情况。
我们的一篇文章介绍了每个指标是如何计算的，总结如下：
- 点击次数：用户从 Google 搜索结果点击您的资源的次数。
- 展示次数：用户在 Google 搜索结果中看到您的资源的次数。
- 点击率：点击次数除以展示次数所得的值。
- 排名：网址、查询或网站在搜索结果中的基本平均排名。
您可以针对不同的维度分析其中每个指标。您可以查看为您的网站带来流量的各个查询、网页、国家/地区、设备或搜索结果呈现效果如何。
您可以通过多种方式访问搜索效果数据，包括产品界面、Search Analytics API、Looker 数据洞察连接器和电子表格（需要从界面手动下载）。
如果您使用的是产品界面，则可以通过过滤条件或图表后面的维度表查看这些维度，如下图所示。
这些数据可用于确定如何让更多用户看到您的网站，并最终从 Google 获得更多流量。有关您可以执行的分析类型的示例，请查看此示例优化图表。
数据过滤和限制
报告界面中的数据和导出的数据都会以不同的方式汇总和过滤。数据主要存在以下两个限制：隐私保护过滤和每日数据行数上限。
隐私保护过滤
为了保护查询用户的隐私，Search Console 数据中不会包含某些查询（称为匿名化查询）。
匿名化查询是指在两到三个月内由不超过数十个用户发出的查询。为保护隐私，实际查询内容不会出现在 Google 搜索效果数据中。因此，我们将其称为匿名化查询。虽然表中始终会省略实际的匿名化查询，但除非您按查询进行过滤，否则它们会包含在图表总计中。
我们来看一个进一步说明这一点的示例。请注意，此图示仅考虑了隐私保护过滤，但下一部分中介绍的每日数据行数上限也可能会产生影响，请继续阅读了解详情。假设下表显示了访问您网站的查询的所有流量，并按非匿名化查询分项列出流量。当然，一个典型的网站通常会有 4 个以上的分项非匿名化查询，但在此示例中，我们只列出 4 个分项类别。
| 查询
|
点击次数
|
| 经典文学
|
150
|
| 诗歌 |
125
|
| 科幻小说 |
100
|
| 非小说 |
75
|
| 分项查询的总数
|
450
|
| 总计
|
550
|
如果您将所有分项查询相加（如图所示），则点击次数为 450 次。此外，该网站整体获得了 550 次点击。这个数字更高，因为它包含所有分项点击数以及来自匿名化查询（未列出）的点击数。
实际上，在使用 Search Console 报告时，您可能会发现这种差异主要有两种。
- 由于报告表格或 API 中没有匿名化查询行（为便于说明，在此添加），因此汇总所有行的点击次数时，您会发现点击次数与图表总计不同。例如，在这个示例中，在汇总行数时，您会看到结果为 450，但在图表总计中却会看到 550。
- 每当应用过滤条件时都会忽略匿名化查询，因此如果您将图表总计中的点击之和与包含
some_string 和不含 some_string 的点击次数之和相比，则会发现有差异。在此示例中，如果使用过滤条件来包含仅含“小说”一词的查询，您将看到 175 次点击；如果排除含“小说”一词的查询，则会看到 275 次点击，二者之和为 450 次点击，而图表总计为 550 次点击。
每日数据行数上限
由于传送延迟、存储、处理资源等方面的限制，Search Console 对可显示或导出的数据量存在限制。这些限制不会影响 Search Console 中的大多数资源。一些非常大的网站可能会受此影响，但即使对于这些网站来说，我们也认为提供的数据足够多，足以生成具有代表性的数据样本。
您通过 Search Console 界面最多可导出 1,000 行数据。
目前，通过 Search Analytics API（以及 Looker 数据洞察连接器）导出数据的上限是每个搜索类型每个网站每天 50,000 行，并非所有情况都会达到这个上限。该 API 默认返回 1,000 行，但您可以使用 rowLimit 将其增加到 25,000 行，使用 startRow 通过分页将行数从 25,001 行提升到 50,000 行。请查看相应指南，了解如何获取可用数据。
对于不涉及查询或网址维度的请求（例如国家/地区、设备和搜索结果呈现），Search Console 将显示和导出所有数据。
资源和反馈
如果您想详细了解该主题，请参阅效果文档。
您可以深入了解可用的数据、如何使用效果报告，以及关于可能会在图表中遇到的差异的详细信息。
如果您有任何问题或疑虑，请通过 Google 搜索中心社区或 Twitter 与我们联系。
发布者：Daniel Waisberg，搜索技术宣讲师
如未另行说明，那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可，并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情，请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
[null,null,[],[[["\u003cp\u003eGoogle Search Console's Performance report provides data on clicks, impressions, CTR, and position to analyze website search traffic.\u003c/p\u003e\n"],["\u003cp\u003eSearch performance data can be accessed via the product interface, Search Analytics API, Looker Studio Connector, and manual spreadsheet downloads.\u003c/p\u003e\n"],["\u003cp\u003eData is subject to privacy filtering, meaning some queries are anonymized to protect user privacy and may lead to discrepancies in total click counts.\u003c/p\u003e\n"],["\u003cp\u003eA daily data row limit exists for exported data, capped at 1,000 rows via the user interface and 50,000 via the API or Looker Studio Connector.\u003c/p\u003e\n"],["\u003cp\u003eComprehensive resources and support are available through Google Search Central Community and Twitter for further assistance.\u003c/p\u003e\n"]]],["Google Search Console's Performance report provides data on clicks, impressions, CTR, and position, which can be analyzed across queries, pages, countries, devices, and search appearances. Access is available through the interface, API, Looker Studio, and spreadsheets. Data is filtered for user privacy, omitting anonymized queries from tables but including them in totals, and has limits of 1,000 rows via the interface or up to 50,000 via API per day.\n"],null,["# A deep dive into Search Console performance data filtering and limits\n\nWednesday, October 19, 2022\n\n\nGoogle Search performance data is the most widely used data in Search Console, both through the\n[Performance report](https://support.google.com/webmasters/answer/7576553)\nand the [Search Analytics API](/webmaster-tools/v1/searchanalytics/query).\nThis post explains in detail the data available and how Google processes it, including privacy\nfiltering and other limitations related to serving latency, storage, and processing resources.\nEver wonder how these systems work? Let's do a deep dive\ninto them.\n\n\nIf you're new to Search Console, check out the [introduction to Performance reports](https://support.google.com/webmasters/answer/10268906).\n\nSearch performance basics\n-------------------------\n\n\nThe Performance report contains four metrics that show how your search traffic changes over time.\nWe have an article describing [how each metric is calculated](https://support.google.com/webmasters/answer/7042828),\nand here's a summary:\n\n- Clicks: Count of user clicks from Google Search results to your property.\n- Impressions: Count of times users saw your property on Google search results.\n- CTR (Click-through rate): The click count divided by the impression count.\n- Position: The average position in search results for the URL, query, or for the website in general.\n\n\nEach of those metrics can be analyzed for different dimensions. You can check how each of the queries,\npages, countries, devices, or search appearances driving traffic to your website is performing.\n\n\nThere are many ways to access the Search performance data, including the\n[product interface](https://search.google.com/search-console/performance/search-analytics),\nthe [Search Analytics API](/webmaster-tools/v1/searchanalytics/query),\nthe [Looker Studio connector](/search/blog/2022/03/connecting-data-studio),\nand spreadsheets (requires manual download from the interface).\n\n\nIf you're using the product interface, the dimensions are available through the filters or through\nthe dimensions tables following the chart, as shown in the image below.\n\n\nThis data can be used to find ways to make your website more visible and ultimately get more traffic\nout of Google. For a sample of what type of analysis you can perform, check this\n[sample optimization chart](/search/blog/2022/04/performance-optimization-bubble-chart).\n\nData filtering and limits\n-------------------------\n\n\nBoth the data in the report interface and the data exported are aggregated and filtered in different\nways. Below are the two main limitations to the data: privacy filtering and daily data row limit.\n\n### Privacy filtering\n\n\nSome queries (called anonymized queries) are not included in Search Console data to protect the\nprivacy of the user making the query.\n\n\nAnonymized queries are those that aren't issued by more than a few dozen users over a two-to-three\nmonth period. To protect privacy, the actual queries won't be shown in the Search performance data.\nThis is why we refer to them as anonymized queries. While the actual anonymized queries are always\nomitted from the tables, they are included in chart totals, unless you filter by query.\n\n\nLet's look at an example to make it clearer - note that this is an illustration that takes into\naccount only privacy filtering, but daily data row limits, discussed in the next section, may also\nplay a role, read on to learn more. Let's say the table below shows all the traffic for queries to\nyour website, itemizing the traffic from non-anonymized queries. A typical website will generally\nhave more than four itemized non-anonymized queries, of course, but for purposes of this example,\nwe'll say it's just four that are itemized.\n\n|------------------------------|------------|\n| **Queries** | **Clicks** |\n| classic literature | 150 |\n| poetry | 125 |\n| science fiction | 100 |\n| non fiction | 75 |\n| *Total for itemized queries* | *450* |\n| *Total overall* | *550* |\n\n\nIf you add up all the itemized queries, as the chart shows, there were 450 clicks. There are also\n550 overall clicks to the site. That number is higher because it includes all the itemized clicks\nplus the clicks from anonymized queries, which aren't listed.\n\n\nIn practice, when using Search Console reporting, you may notice this type of discrepancy in two main ways.\n\n1. There is no row for anonymized queries in the report table or API (added here for illustration purposes), so if you sum up clicks for all the rows, you'll not find the same number of clicks as the chart totals. For example in this case you'd see 450 when you sum up the rows, but you'd see 550 in the chart totals.\n2. The anonymized queries are omitted whenever a filter is applied, so there will be a discrepancy if you compare the sum of clicks in the chart totals to the sum of clicks containing `some_string` and not containing `some_string`. In this case, if you use filters to include only queries that contain the word \"fiction\", you'll see 175 clicks, and if you exclude queries that contain the word \"fiction\", you'll see 275 clicks, summing up to 450 clicks, while in the chart total you'll see 550 clicks.\n\n### Daily data row limit\n\n\nDue to limitations related to serving latency, storage, processing resources, and others, Search\nConsole has a limit on the amount of data that can be displayed or exported. These limits won't affect\nthe majority of properties in Search Console. A few very large websites can be affected by this, but\neven for those we believe the remaining data will be large enough to create a representative sample of data.\n\n\nThe maximum you can export through the Search Console user interface is 1,000 rows of data.\nCurrently, the upper limit for the data exported through the [Search Analytics API](/webmaster-tools/v1/searchanalytics/query)\n(and through the [Looker Studio connector](/search/blog/2022/03/connecting-data-studio))\nis 50,000 rows per day per site per search type, which may not be reached in all cases. The default\nreturned by the API will be 1,000 rows, but you can use `rowLimit` to increase it to 25,000\nand `startRow` to pull the rows 25,001 to 50,000 using pagination. Check this guide to\nlearn [how to get the available data](/webmaster-tools/v1/how-tos/all-your-data).\n\n\nFor requests that don't involve query or URL dimensions, such as countries, devices, and Search\nAppearances, Search Console will display and export all the data.\n\nResources and feedback\n----------------------\n\n\nIf you'd like to learn more about the subject, read the [Performance documentation](https://support.google.com/webmasters/answer/7576553).\nYou'll find in-depth explanations about the available data, how to use the Performance report, and more\ndetails about discrepancies you may find in the charts.\n\n\nIf you have any questions or concerns, please reach out to us via the\n[Google Search Central Community](https://support.google.com/webmasters/threads?thread_filter=(category:search_console))\nor on [Twitter](https://twitter.com/googlesearchc).\n\nPosted by [Daniel Waisberg](https://www.danielwaisberg.com), Search Advocate"]]
