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.
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 firstUse 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.
Keep the chosen verification method in place. DNS verification is often the most durable option for a domain-level property.
Submit the canonical sitemap URL, then confirm it is processed and the discovered URL count is plausible for the published site.
Use URL inspection for the homepage and priority pages after publication. A request is a crawl hint, not an indexing guarantee.
Before optimization, note the date, indexed-page state, impressions, clicks, leading queries, landing pages, and any coverage issues.
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.
Google Search Console 用于验证搜索展示、点击、收录信号和抓取异常。应在第一次技术或内容改动前完成配置,后续才能有可对比的基线。
先检查公开基础条件能管理 DNS 且需要覆盖所有协议和子域时,优先使用 Domain property;只有明确需要时才用 URL-prefix property。
保留已选验证方式。对于域名级资源,DNS 验证通常更稳定。
提交规范 Sitemap 地址,确认其已被处理,并检查发现 URL 数量是否符合已发布页面。
页面发布后,用 URL Inspection 检查首页和核心页。请求只是抓取提示,不保证必然收录。
优化前记录日期、收录状态、展示、点击、主要搜索词、落地页和覆盖问题。
Search Console 数据需要积累。应在改动被抓取和收录后比较一致的周期,并将技术修复与内容、季节性和付费推广分开解释。