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