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