Measurement baseline

Set up Search Console before you ask whether SEO worked.

Google Search Console is where a site owner can verify search impressions, clicks, indexing signals, and crawl issues. Set it up before the first technical or content change so later results have a baseline.

Audit public prerequisites first

The five setup steps

01

Create the right property

Use a Domain property when you can manage DNS and need all protocols and subdomains together. Use a URL-prefix property only when that scope is intentional.

02

Verify ownership

Keep the chosen verification method in place. DNS verification is often the most durable option for a domain-level property.

03

Submit the sitemap

Submit the canonical sitemap URL, then confirm it is processed and the discovered URL count is plausible for the published site.

04

Request important pages

Use URL inspection for the homepage and priority pages after publication. A request is a crawl hint, not an indexing guarantee.

05

Record the baseline

Before optimization, note the date, indexed-page state, impressions, clicks, leading queries, landing pages, and any coverage issues.

Give an advisor the minimum access

  • Add the owner first, then grant the advisor the least privilege needed for read-only diagnosis.
  • Keep ownership and billing control with the business, not the outside service provider.
  • Document which property, preferred domain, sitemap, and markets are in scope.
  • Do not send passwords in chat; use the platform's user-access controls.
Do not use the first day as proof of impact.

Search Console data needs time to accumulate. Compare a consistent period after the relevant changes are crawled and indexed, while separating technical fixes from content, seasonality, and paid campaigns.

What to check each week

  • Did new or changed priority URLs become indexed as expected?
  • Are impressions and clicks changing for the pages and queries you actually targeted?
  • Did crawl, page indexing, or enhancement reports reveal a blocking issue?
  • Do GA4 conversion events agree with the traffic trend before you claim growth?
度量基线

开始优化前,先配置 Search Console。

Google Search Console 用于验证搜索展示、点击、收录信号和抓取异常。应在第一次技术或内容改动前完成配置,后续才能有可对比的基线。

先检查公开基础条件

五个配置步骤

01

创建正确资源

能管理 DNS 且需要覆盖所有协议和子域时,优先使用 Domain property;只有明确需要时才用 URL-prefix property。

02

验证所有权

保留已选验证方式。对于域名级资源,DNS 验证通常更稳定。

03

提交 Sitemap

提交规范 Sitemap 地址,确认其已被处理,并检查发现 URL 数量是否符合已发布页面。

04

请求重要页面

页面发布后,用 URL Inspection 检查首页和核心页。请求只是抓取提示,不保证必然收录。

05

记录基线

优化前记录日期、收录状态、展示、点击、主要搜索词、落地页和覆盖问题。

给顾问的最小权限

  • 先由站长添加资源,再向顾问授予只读诊断所需的最小权限。
  • 所有权和账单控制应始终留在企业,而不是外部服务方。
  • 记录本次使用的资源、规范域名、Sitemap 和目标市场。
  • 不要在聊天中发送密码,使用平台自身的用户访问控制。
不要用第一天的数据证明效果。

Search Console 数据需要积累。应在改动被抓取和收录后比较一致的周期,并将技术修复与内容、季节性和付费推广分开解释。

每周该看什么

  • 新发布或改动的重要 URL 是否按预期收录?
  • 目标页面和搜索词的展示、点击是否发生变化?
  • 抓取、页面收录或增强报告中是否出现阻塞?
  • 在宣称增长前,GA4 转化事件是否与流量趋势一致?