[{"data":1,"prerenderedAt":725},["ShallowReactive",2],{"blog-brand-query-volume-measure":3,"blog-prev-brand-query-volume-measure":74,"blog-next-brand-query-volume-measure":255},{"id":4,"title":5,"author":6,"body":7,"canonical":58,"category":59,"cover":58,"date":60,"description":61,"draft":62,"extension":63,"keywords":58,"meta":64,"navigation":65,"noindex":62,"ogImage":58,"path":66,"seo":67,"seoDescription":58,"seoTitle":58,"stem":68,"tags":69,"updated":58,"__hash__":73},"blog\u002Fblog\u002Fbrand-query-volume-measure.md","品牌词的搜索量怎么查：三个数据源对不上怎么办","元析智能",{"type":8,"value":9,"toc":51},"minimark",[10,14,18,21,24,27,30,33,36,39,42,45,48],[11,12,13],"p",{},"同一个品牌词，GSC 显示每月 300 次点击，百度指数显示 90，第三方工具显示 1500，三个数差十几倍。这不是工具坏了，是它们量的根本不是同一件事。问\"哪个数对\"是问错了问题，该问的是\"这个数在量什么\"。",[15,16,17],"h2",{"id":17},"三个数据源各自在量什么",[11,19,20],{},"GSC 量的是你自己站点拿到的曝光和点击。用户搜你的品牌名但没点你的结果，GSC 看不到。所以它是下限，不是全量。",[11,22,23],{},"百度指数量的是抽样估算的搜索热度，展示的是相对趋势。小量词经常直接不显示，或者长期显示 0。拿它看绝对值会误判，看趋势可以。",[11,25,26],{},"第三方工具（比如爱站、5118）量的是基于关键词库的综合估算，覆盖范围宽，但精度低。它对大词的趋势判断有用，对小品牌的绝对量参考价值有限。",[15,28,29],{"id":29},"对不上时怎么用",[11,31,32],{},"我们的做法是固定口径，只跟自己比。口径包含四件事：品牌词的变体清单、统计周期、数据源、指标类型。",[11,34,35],{},"品牌词变体要列全。公司全称、简称、英文名、产品名、常见错别字，我们在一个客户的清单里列了 12 个变体加 2 个产品名，少列一个，趋势就会跳。统计周期用 90 天滚动，不用单月，因为品牌词受一次媒体报道影响很大，单月数据噪音太多。数据源固定用 GSC 的点击，第三方只做趋势参考。",[11,37,38],{},"这样算出来的数，绝对值可能不\"准\"，但可以用来回答真正重要的问题：这个季度品牌搜索是涨是跌，涨了多少。",[15,40,41],{"id":41},"一个踩过的坑",[11,43,44],{},"2025 年 6 月，我们把一个客户的品牌词和产品通用词混在一个报表里看，结果某个季度显示品牌搜索大涨 60%。拆开才发现，涨的是产品词，品牌词其实涨了 8%。那次误判让我们给了一个错误的策略建议，客户多花了两个月做没必要的品牌投放。",[11,46,47],{},"从那以后，报表第一行永远是品牌词单列，产品词和行业词分开。宁可多一张表，也不混着看。",[11,49,50],{},"品牌搜索数据看的是趋势和方向，不是绝对数。想让绝对数变小，方法很简单，把口径改窄就行，但那样做只是骗自己。",{"title":52,"searchDepth":53,"depth":53,"links":54},"",2,[55,56,57],{"id":17,"depth":53,"text":17},{"id":29,"depth":53,"text":29},{"id":41,"depth":53,"text":41},null,"SEO","2025-12-17","同一个品牌词，GSC、百度指数、第三方工具给出的数能差五倍。这篇讲三个源各自在量什么、什么时候信哪个，以及我们判断品牌搜索趋势时固定用的那套口径。",false,"md",{},true,"\u002Fblog\u002Fbrand-query-volume-measure",{"title":5,"description":61},"blog\u002Fbrand-query-volume-measure",[70,71,72],"品牌词","数据口径","搜索量","UC4csceBEiMPBW1VZiB-vh1zg6H-zA9ffLvfPs-3MPE",{"id":75,"title":76,"author":6,"body":77,"canonical":58,"category":242,"cover":58,"date":243,"description":244,"draft":62,"extension":63,"keywords":58,"meta":245,"navigation":65,"noindex":62,"ogImage":58,"path":246,"seo":247,"seoDescription":58,"seoTitle":58,"stem":248,"tags":249,"updated":58,"__hash__":254},"blog\u002Fblog\u002Fcompetitor-ai-share-audit.md","竞品在 AI 回答里占多少位：一次 320 条回答的人工盘点",{"type":8,"value":78,"toc":235},[79,82,85,88,91,95,98,105,111,117,123,126,129,132,135,138,141,147,153,159,162,229,232],[11,80,81],{},"先给参照系，再谈优化。2025 年 12 月我们给 6 个 B2B 软件客户各跑了 80 个查询，四个 AI 引擎，记录每条回答里出现了哪些品牌。结果很一致：竞品平均出现在 43% 的回答里，客户自己 19%。",[15,83,84],{"id":84},"为什么先做这件事",[11,86,87],{},"老板问\"我们在 AI 里有没有存在感\"，你答\"有一些\"，这对话没法继续。换成\"竞品 A 在 51 个回答里出现，我们 15 个，其中 6 个是竞品 A 被列为推荐、我们被列为备选\"，讨论立刻具体。",[11,89,90],{},"参照系还有个作用：它挡掉无效焦虑。有些客户看到自己只被提 10 次就想大改官网，一查竞品也就 12 次——这个品类在 AI 里的整体水位就低，不需要动内容，需要等语料积累。",[15,92,94],{"id":93},"_80-个查询怎么选","80 个查询怎么选",[11,96,97],{},"四类，每类 20 个：",[11,99,100,104],{},[101,102,103],"strong",{},"品类词。","\"数据同步工具\"\"API 网关\"\"日志分析平台\"。这类问的是\"有什么\"，AI 会列举。",[11,106,107,110],{},[101,108,109],{},"对比词。","\"A 和 B 的区别\"\"A 的替代品\"。这类问的是\"选哪个\"，AI 会给判断。",[11,112,113,116],{},[101,114,115],{},"场景词。","\"MySQL 到 ClickHouse 怎么做增量同步\"\"K8s 集群怎么做鉴权\"。这类问的是\"怎么做\"，AI 会引文档。",[11,118,119,122],{},[101,120,121],{},"品牌加场景。","\"XX 能接 Kafka 吗\"\"XX 支持私有部署吗\"。这类问的是\"你能不能\"，AI 会引官网和第三方。",[11,124,125],{},"品类词和对比词决定获客，场景词决定你是不是内行，品牌加场景决定成单前的最后一步。四类都跑，才知道短板在哪。",[15,127,128],{"id":128},"记录哪四列",[11,130,131],{},"一列查询，一列引擎，一列\"出现方式\"，一列原文。",[11,133,134],{},"出现方式分五种：首位推荐、列举中的一项、被当备选、被负面提及、没出现。这五种的商业价值差很远。首位推荐和列举中一项，看着都是\"出现了\"，实际差一个量级。",[11,136,137],{},"原文必须抄下来。只记\"出现了\"没有用，要看它用什么话描述你。我们有个客户被描述成\"轻量级方案\"，一看就知道 AI 是从他们 2023 年的旧文档里学的。",[15,139,140],{"id":140},"三个高频发现",[11,142,143,146],{},[101,144,145],{},"竞品在\"替代品\"类查询里占位最稳。"," 这类查询我们跑了 6 个客户，竞品平均出现率 61%。原因是替代品文章是最好写的选题，第三方媒体爱写，AI 爱引。",[11,148,149,152],{},[101,150,151],{},"客户在\"哪个好\"里普遍缺席。"," 80 个查询里，客户在对比类回答中出现 9 次。对比类内容要么自己写、要么被别人写，不写就是空白。",[11,154,155,158],{},[101,156,157],{},"出现方式比出现次数重要。"," 有个客户出现 22 次，其中 17 次是\"也有人用\"这种备选位，实际带来 0 个询盘。另一个客户出现 11 次，8 次在首位，一个月 6 个询盘。",[15,160,161],{"id":161},"一张表长什么样",[163,164,165,184],"table",{},[166,167,168],"thead",{},[169,170,171,175,178,181],"tr",{},[172,173,174],"th",{},"查询",[172,176,177],{},"引擎",[172,179,180],{},"出现方式",[172,182,183],{},"提到的品牌",[185,186,187,202,216],"tbody",{},[169,188,189,193,196,199],{},[190,191,192],"td",{},"数据同步工具推荐",[190,194,195],{},"ChatGPT",[190,197,198],{},"列举第 4 项",[190,200,201],{},"竞品 A、竞品 B、客户",[169,203,204,207,210,213],{},[190,205,206],{},"XX 的替代品",[190,208,209],{},"Perplexity",[190,211,212],{},"未出现",[190,214,215],{},"竞品 A、竞品 C",[169,217,218,221,223,226],{},[190,219,220],{},"Kafka 增量同步怎么做",[190,222,195],{},[190,224,225],{},"引官网文档",[190,227,228],{},"客户",[11,230,231],{},"这张表跑一轮 4 小时，比任何工具的报告都好用，因为你能读到原文。",[11,233,234],{},"先知道自己站在哪，再决定往哪走。",{"title":52,"searchDepth":53,"depth":53,"links":236},[237,238,239,240,241],{"id":84,"depth":53,"text":84},{"id":93,"depth":53,"text":94},{"id":128,"depth":53,"text":128},{"id":140,"depth":53,"text":140},{"id":161,"depth":53,"text":161},"行业观察","2025-12-16","给 6 个客户跑了 80 个查询，竞品平均出现在 43% 的 AI 回答里，客户自己只有 19%。先建参照系再谈优化，附查询分类和记录表。",{},"\u002Fblog\u002Fcompetitor-ai-share-audit",{"title":76,"description":244},"blog\u002Fcompetitor-ai-share-audit",[250,251,252,253],"GEO","竞品分析","AI搜索","可见性监测","pz-2xLuhs9v9BEPytMg8XH3IdiR8jSkmL8DTjHLA1ws",{"id":256,"title":257,"author":6,"body":258,"canonical":58,"category":59,"cover":58,"date":713,"description":714,"draft":62,"extension":63,"keywords":58,"meta":715,"navigation":65,"noindex":62,"ogImage":58,"path":716,"seo":717,"seoDescription":58,"seoTitle":58,"stem":718,"tags":719,"updated":58,"__hash__":724},"blog\u002Fblog\u002Fdevtools-seo-guide.md","开发者工具怎么做 SEO:和普通软件不一样的地方",{"type":8,"value":259,"toc":702},[260,263,266,269,288,291,294,298,301,309,312,315,359,363,366,369,372,401,404,408,411,422,425,436,439,473,476,479,482,514,517,528,532,535,607,610,624,627,630,636,642,648,657,661,664,693,696,699],[11,261,262],{},"给开发者工具做 SEO,第一件事是忘掉百度。开发者搜技术问题 80% 用 Google,剩下 20% 直接在 Stack Overflow 和 GitHub 里搜。你的 SEO 策略要跟着用户的搜索路径走,不是跟着通用 SEO 模板走。这篇文章写我们给 IDE 插件、CI\u002FCD 工具、监控类工具做 SEO 的经验。",[15,264,265],{"id":265},"开发者怎么搜东西",[11,267,268],{},"先说数据。我们监测过 3 个 dev tools 客户的搜索来源,6 个月的数据:",[270,271,272,276,279,282,285],"ul",{},[273,274,275],"li",{},"Google 占 62%-78%(出海工具更高,国内工具低一些)",[273,277,278],{},"百度占 5%-12%(且主要在品牌词,不是技术词)",[273,280,281],{},"Stack Overflow 引荐占 8%-15%",[273,283,284],{},"GitHub 搜索和 README 引荐占 5%-10%",[273,286,287],{},"AI 引擎(ChatGPT、Perplexity、Claude)占 3%-8%,且在涨",[11,289,290],{},"关键点:开发者搜\"如何做 XX\"几乎不碰百度。百度的技术内容质量太差,SEO 起来了开发者也不会信。",[11,292,293],{},"所以 dev tools 的 SEO 主战场是 Google,不是百度。如果你的产品只做国内,也要重视 Google——开发者用 Google 的比例依然高于百度。",[15,295,297],{"id":296},"技术文档是核心-seo-资产","技术文档是核心 SEO 资产",[11,299,300],{},"SaaS 的核心资产是文档,dev tools 更是。但 dev tools 的文档和 SaaS 不一样:",[270,302,303,306],{},[273,304,305],{},"SaaS 文档讲\"功能怎么用\"",[273,307,308],{},"Dev tools 文档要讲\"API、配置、命令行参数、错误码\"",[11,310,311],{},"这些内容搜索量不大,但意图极其明确,转化率高得离谱。我们有个 CI\u002FCD 工具客户,一个文档页\"如何配置 YAML 文件\"每月带来 200 多个注册,转化率 18%。",[11,313,314],{},"文档 SEO 要做的:",[270,316,317,323,337,343,353],{},[273,318,319,322],{},[101,320,321],{},"每个 API\u002F命令一个独立 URL",":不要把所有 API 放一个页面用锚点跳",[273,324,325,328,329,333,334],{},[101,326,327],{},"title 用具体的 API 名和版本",":",[330,331,332],"code",{},"kubectl logs --tail 用法和参数",",不是",[330,335,336],{},"命令行工具文档",[273,338,339,342],{},[101,340,341],{},"错误码页独立",":用户搜报错信息时直接命中,这种页面价值极高",[273,344,345,348,349,352],{},[101,346,347],{},"代码示例可复制",":代码块用 ",[330,350,351],{},"\u003Cpre>\u003Ccode>",",不要图。开发者要复制粘贴",[273,354,355,358],{},[101,356,357],{},"版本化文档",":旧版本文档保留,很多开发者还在用旧版",[15,360,362],{"id":361},"github-star-和-seo-的关系","GitHub Star 和 SEO 的关系",[11,364,365],{},"开发者工具绕不开 GitHub。但 GitHub Star 数和 SEO 流量没有直接关系,这是常见误解。",[11,367,368],{},"我们监测过两个开源监控工具,A 有 18k star,B 有 6k star。A 的官网自然流量是 B 的 3 倍。看起来 star 多流量多?不,关键变量不是 star 数,是 README 和 repo 的 SEO 表现。",[11,370,371],{},"GitHub 自身权重高,你的 README 在 Google 搜品牌词时经常排在官网前面。这意味着:",[270,373,374,380,386,395],{},[273,375,376,379],{},[101,377,378],{},"README 要当成 landing page 写",":开头说清楚产品是什么、解决什么问题,不要只放一个 logo 和一句口号",[273,381,382,385],{},[101,383,384],{},"README 关键词覆盖",":用户搜\"lightweight monitoring tool\"时,你的 README 要命中",[273,387,388,391,394],{},[101,389,390],{},"docs 链接放在 README 显眼位置",[392,393],"git-hub",{}," 的权重导到官网",[273,396,397,400],{},[101,398,399],{},"Issues 区做内容",":常见报错和解决方案在 Issues 里,这些页 GitHub 权重高,经常被搜到",[11,402,403],{},"Star 数影响的是开发者决策(信任度),不是搜索排名。两个事别混。",[15,405,407],{"id":406},"开源项目的-seo-策略","开源项目的 SEO 策略",[11,409,410],{},"开源 dev tools 的 SEO 策略和闭源不一样。开源的天然优势:",[270,412,413,416,419],{},[273,414,415],{},"GitHub repo 本身是高权重页面",[273,417,418],{},"开源社区讨论产生自然外链",[273,420,421],{},"开发者在博客、Reddit、Hacker News 提到你的项目",[11,423,424],{},"劣势:",[270,426,427,430,433],{},[273,428,429],{},"官网商业页(付费版、企业版)权重比文档页低",[273,431,432],{},"用户搜索\"XX alternative\"时容易流到竞品",[273,434,435],{},"文档站经常是子域名,权重传递不如主域名",[11,437,438],{},"具体怎么做:",[440,441,442,455,461,467],"ol",{},[273,443,444,328,447,450,451,454],{},[101,445,446],{},"docs 用子目录而不是子域名",[330,448,449],{},"yoursite.com\u002Fdocs"," 比 ",[330,452,453],{},"docs.yoursite.com"," 好,权重继承主域名。这点很多人不知道",[273,456,457,460],{},[101,458,459],{},"commercial 页和 docs 内链互通",":文档顶部加\"商业版支持 XX 功能\"的链接,把流量导向付费页",[273,462,463,466],{},[101,464,465],{},"做\"vs\"内容",":开发者搜\"Prometheus vs Grafana\"这类对比,你做对比页截流",[273,468,469,472],{},[101,470,471],{},"Reddit、Hacker News 内容部署",":在这些平台做技术分享,链接回官网",[15,474,475],{"id":475},"技术博客内容怎么做",[11,477,478],{},"Dev tools 的博客不能写\"行业趋势\"\"数字化转型\"这种废话。开发者看到这种文章直接关掉。",[11,480,481],{},"技术博客要写的内容类型:",[270,483,484,490,496,502,508],{},[273,485,486,489],{},[101,487,488],{},"工程实践",":\"我们怎么把 CI 流水线从 12 分钟降到 90 秒\"——这种文章开发者会收藏",[273,491,492,495],{},[101,493,494],{},"技术深挖",":\"为什么我们用 Rust 重写日志采集器\"——技术决策的 why",[273,497,498,501],{},[101,499,500],{},"benchmark",":你的工具和竞品的性能对比,带具体数据。开发者信数据不信口号",[273,503,504,507],{},[101,505,506],{},"踩坑记录",":\"升级到 K8s 1.28 踩的 5 个坑\"——真实的踩坑记录比功能介绍有用 10 倍",[273,509,510,513],{},[101,511,512],{},"用户案例",":具体客户(脱敏也行)用了你的工具解决了什么问题,带前后对比数据",[11,515,516],{},"不要写的内容:",[270,518,519,522,525],{},[273,520,521],{},"\"在数字化时代,DevOps 越来越重要\"——废话开头",[273,523,524],{},"\"我们的产品赋能开发者\"——空话",[273,526,527],{},"\"2025 年最值得关注的 10 个工具\"——水文,开发者一眼看穿",[15,529,531],{"id":530},"为什么不能套用-saas-的-seo-方法","为什么不能套用 SaaS 的 SEO 方法",[11,533,534],{},"SaaS 的 SEO 方法不完全适用于 dev tools,原因:",[163,536,537,550],{},[166,538,539],{},[169,540,541,544,547],{},[172,542,543],{},"维度",[172,545,546],{},"SaaS",[172,548,549],{},"Dev Tools",[185,551,552,563,574,585,596],{},[169,553,554,557,560],{},[190,555,556],{},"目标用户",[190,558,559],{},"业务决策者 + 终端用户",[190,561,562],{},"开发者",[169,564,565,568,571],{},[190,566,567],{},"搜索引擎",[190,569,570],{},"百度 + Google",[190,572,573],{},"Google 为主",[169,575,576,579,582],{},[190,577,578],{},"商业词",[190,580,581],{},"\"CRM 系统\"这类",[190,583,584],{},"\"how to do XX\" 这类",[169,586,587,590,593],{},[190,588,589],{},"决策路径",[190,591,592],{},"销售\u002F市场主导",[190,594,595],{},"开发者自下而上推动",[169,597,598,601,604],{},[190,599,600],{},"内容偏好",[190,602,603],{},"案例研究、行业报告",[190,605,606],{},"工程实践、技术深挖",[11,608,609],{},"SaaS SEO 套 dev tools 会犯的错:",[270,611,612,615,618,621],{},[273,613,614],{},"写\"行业趋势\"文章——开发者不看",[273,616,617],{},"百度投大预算——开发者不搜百度",[273,619,620],{},"商业词打硬广——开发者反感,会去 Reddit 吐槽你",[273,622,623],{},"文档收费墙——开发者直接走人",[15,625,626],{"id":626},"具体工具举例",[11,628,629],{},"我们做过的几个类型:",[11,631,632,635],{},[101,633,634],{},"IDE 插件类",":核心 SEO 资产是 JetBrains Marketplace 和 VS Code Marketplace 的页面。这两个市场自身权重高,搜索流量大。插件描述要当成 SEO 文案写,关键词覆盖\"语言+功能\"(如\"Python 类型检查插件\")。",[11,637,638,641],{},[101,639,640],{},"CI\u002FCD 工具类",":核心是 YAML 配置文档和错误码页。这类工具的搜索意图非常具体,文档质量直接决定流量。",[11,643,644,647],{},[101,645,646],{},"监控类工具",":用户搜\"how to monitor XX\"和\"XX alerting best practices\"。要做场景化内容,不是功能介绍。",[11,649,650,653,656],{},[101,651,652],{},"API 工具类",[654,655],"postman",{}," 的文档是范本。API 文档要能直接 try,且每个 endpoint 独立 URL。",[15,658,660],{"id":659},"我们不接的-dev-tools","我们不接的 dev tools",[11,662,663],{},"不是所有 dev tools 都能做 SEO。我们不接:",[270,665,666,672,678,684],{},[273,667,668,671],{},[101,669,670],{},"不开源的纯商业 dev tool",":外链建设太难,开发者社区不认可",[273,673,674,677],{},[101,675,676],{},"文档收费墙",":不开放无法做 SEO",[273,679,680,683],{},[101,681,682],{},"目标用户是非技术岗位的\"开发者工具\"",":那是普通 SaaS,不是 dev tools",[273,685,686,689,692],{},[101,687,688],{},"想 1 个月起量的",[690,691],"dev",{}," tools SEO 至少 4-6 个月",[15,694,695],{"id":695},"总结",[11,697,698],{},"给开发者工具做 SEO,记住三件事:用户用 Google 不用百度;技术文档是核心资产;README 和 GitHub 权重比你想的高。别套用 SaaS 的方法,开发者不吃那套。",[11,700,701],{},"如果你做 dev tools,想知道你的文档和 GitHub 现状怎么样,联系我们做个诊断。",{"title":52,"searchDepth":53,"depth":53,"links":703},[704,705,706,707,708,709,710,711,712],{"id":265,"depth":53,"text":265},{"id":296,"depth":53,"text":297},{"id":361,"depth":53,"text":362},{"id":406,"depth":53,"text":407},{"id":475,"depth":53,"text":475},{"id":530,"depth":53,"text":531},{"id":626,"depth":53,"text":626},{"id":659,"depth":53,"text":660},{"id":695,"depth":53,"text":695},"2025-12-18","开发者工具的目标用户是开发者,他们搜东西不去百度。技术文档、GitHub、Stack Overflow 才是主战场。我们做 dev tools SEO 的经验。",{},"\u002Fblog\u002Fdevtools-seo-guide",{"title":257,"description":714},"blog\u002Fdevtools-seo-guide",[720,721,722,723],"开发者工具","DevTools SEO","技术文档","开源项目","jbH-g8nvMrp1l5NHNVIV7lqYEwAr5rFny5WQuQ9NMnQ",1794088109951]