[{"data":1,"prerenderedAt":324},["ShallowReactive",2],{"blog-content-types-division":3,"blog-prev-content-types-division":110,"blog-next-content-types-division":210},{"id":4,"title":5,"author":6,"body":7,"canonical":94,"category":95,"cover":94,"date":96,"description":97,"draft":98,"extension":99,"keywords":94,"meta":100,"navigation":101,"noindex":98,"ogImage":94,"path":102,"seo":103,"seoDescription":94,"seoTitle":94,"stem":104,"tags":105,"updated":94,"__hash__":109},"blog\u002Fblog\u002Fcontent-types-division.md","博客、文档、落地页、案例：四类内容各管什么，别互相抢","元析智能",{"type":8,"value":9,"toc":84},"minimark",[10,14,18,21,24,27,30,33,36,39,42,45,48,51,54,57,60,63,66,69,72,75,78,81],[11,12,13],"p",{},"软件公司做内容最容易犯的错，是让四类内容干同一件事。博客负责获客、文档负责留存、落地页负责转化、案例负责信任，分工错了会互相抢词。",[15,16,17],"h2",{"id":17},"四类内容的分工",[11,19,20],{},"博客：回答用户的问题，覆盖信息型查询，目标是让不知道你的人找到你。",[11,22,23],{},"文档：教用户怎么用产品，覆盖产品功能词和操作词，目标是让用了的人留下来。",[11,25,26],{},"落地页：承接商业意图，覆盖\"工具\"\"软件\"\"方案\"这类词，目标是让找到你的人转化。",[11,28,29],{},"案例：证明你能解决问题，覆盖\"客户案例\"\"行业方案\"这类词，目标是让犹豫的人下决心。",[15,31,32],{"id":32},"分工错了会怎样",[11,34,35],{},"最典型的是博客抢落地页的词。博客写了一篇\"项目管理工具怎么选\"，排到第 8；产品落地页也想做这个词，排在 20 开外。两个页面互相抢，谁也上不去。",[11,37,38],{},"我们 2026 年 3 月处理过一个这样的站：博客和落地页抢\"客服系统\"这个词，互相蚕食了四个月。",[11,40,41],{},"解法：博客文章改成\"客服系统选型的 5 个坑\"，把商业意图的\"客服系统\"留给落地页；博客内链到落地页，把流量导过去。",[15,43,44],{"id":44},"我们的分工表",[11,46,47],{},"按关键词类型分，最清楚：",[11,49,50],{},"信息型词（怎么、是什么、为什么）→ 博客。\n操作型词（怎么配置、报错、版本）→ 文档。\n商业型词（工具、软件、价格、替代品）→ 落地页。\n证明型词（案例、客户、行业方案）→ 案例页。",[11,52,53],{},"一个词只归一类，归完写进关键词库，避免后面撞车。",[15,55,56],{"id":56},"一个边界",[11,58,59],{},"不是所有词都能干净归类。\"API 监控\"这种词，博客、文档、落地页都能做，这类词要按搜索意图再拆一层。",[11,61,62],{},"我们的做法是看 SERP：如果前 10 名多是博客文章，博客做；如果多是产品页，落地页做。跟着 SERP 走，比自己拍脑袋准。",[15,64,65],{"id":65},"一个常见的浪费",[11,67,68],{},"很多软件公司的文档写得像博客，讲行业趋势，不讲自家功能。这类内容既不解决用户问题，也不带来搜索流量。",[11,70,71],{},"文档就写\"怎么用\"，别写\"为什么这个行业需要\"。",[15,73,74],{"id":74},"一句判断",[11,76,77],{},"内容分工不是组织架构问题，是关键词归属问题。先分词，再分内容，最后才分人。",[11,79,80],{},"分工清楚了，四类内容各做各的，流量才会叠加，而不是互相抵消。",[11,82,83],{},"最后补一句：这个分工表不是死的，产品阶段不同，权重会变。早期获客靠博客，成熟期转化靠落地页和案例，排期要跟着阶段走。",{"title":85,"searchDepth":86,"depth":86,"links":87},"",2,[88,89,90,91,92,93],{"id":17,"depth":86,"text":17},{"id":32,"depth":86,"text":32},{"id":44,"depth":86,"text":44},{"id":56,"depth":86,"text":56},{"id":65,"depth":86,"text":65},{"id":74,"depth":86,"text":74},null,"内容运营","2026-05-26","软件公司做内容最容易犯的错，是让四类内容干同一件事。博客负责获客、文档负责留存、落地页负责转化、案例负责信任，分工错了会互相抢词。我们的分工表、一个抢词案例和三个判断边界都在这篇。",false,"md",{},true,"\u002Fblog\u002Fcontent-types-division",{"title":5,"description":97},"blog\u002Fcontent-types-division",[106,107,108],"内容矩阵","内容分工","站点结构","tuVuHiA4RA1sgBNvuyRkB2si4KMCPB3uJZZ4p68DK44",{"id":111,"title":112,"author":6,"body":113,"canonical":94,"category":95,"cover":94,"date":199,"description":200,"draft":98,"extension":99,"keywords":94,"meta":201,"navigation":101,"noindex":98,"ogImage":94,"path":202,"seo":203,"seoDescription":94,"seoTitle":94,"stem":204,"tags":205,"updated":94,"__hash__":209},"blog\u002Fblog\u002Fbatch-writing-workflow.md","一天写四篇：我们的批量写作流程和它的代价",{"type":8,"value":114,"toc":190},[115,118,121,124,127,130,133,136,139,142,145,148,151,154,157,160,163,166,169,172,175,178,181,184,187],[11,116,117],{},"一天写四篇，不是四篇都在从零想。我们的批量日是这么排的：上午两篇结构固定的短稿，下午两篇要查资料的，晚上不回看，第二天统一改。2026 年 3 月试了一整月，产出 15 篇，是平时的两倍多。",[15,119,120],{"id":120},"提前一周把事做完",[11,122,123],{},"选题、素材、模板，全部在前一周定好。批量日当天不查词、不定题、不找图，只写。",[11,125,126],{},"素材包里每篇要有：三个必须回答的问题、一个独家信息、两张截图或一段代码。缺一样，这篇当天写不了。",[15,128,129],{"id":129},"上午写短的",[11,131,132],{},"上午的两篇是 800 到 1000 字的短稿，结构固定：结论、三个小节、一个清单。这类内容不需要太多思考，写得快。",[11,134,135],{},"我上午能写两篇，中间休息 20 分钟。速度来自结构固定，不是打字快。",[15,137,138],{"id":138},"下午写要查资料的",[11,140,141],{},"下午的两篇通常是数据文或教程，需要翻后台、跑数、看文档。一篇要两到三小时。",[11,143,144],{},"这两篇写完当天不追求完美，能出完整初稿就算完成。",[15,146,147],{"id":147},"第二天统一改",[11,149,150],{},"批量日不修改，第二天上午花两小时统一过一遍：删废话、补第一人称、检查有没有独家信息。",[11,152,153],{},"隔一夜再看，能砍掉的东西比当天多。当天觉得必要的段落，第二天往往一眼就知道该删。",[15,155,156],{"id":156},"代价是什么",[11,158,159],{},"第一个月的代价很明显：数据文比例从 30% 降到 12%，全是结构化的短稿。阅读完成率掉了 9 个百分点。",[11,161,162],{},"第二个月我们把批量日改成两周一次，数据文单独安排，情况才平衡。",[15,164,165],{"id":165},"什么内容不适合批量",[11,167,168],{},"需要实测的、需要采访客户的、需要跑对比实验的，一天最多一篇。硬塞进批量日，出来的东西一定是空壳。",[11,170,171],{},"我们的分工是：批量日写“已知答案”的题，单独安排写“需要找答案”的题。",[15,173,174],{"id":174},"给一个人团队的建议",[11,176,177],{},"先别追求四篇。能稳定一天两篇、每周两天，一个月也有 16 篇，够用。",[11,179,180],{},"另外，批量日之后一定要留一天不写。连续两天四篇，第三天的稿子质量明显下滑，这个我自己试过两次，两次都一样。",[11,182,183],{},"我们后来把批量日固定成每两周一次，平时一天一篇。这样既有集中产出的效率，也不会把内容质量压平。",[11,185,186],{},"如果你的选题里一半以上需要查资料，批量日就不适合你。先算一下比例，再决定要不要这么做。",[11,188,189],{},"批量写作的价值在减少切换成本，不在追求数量。切换一次大脑要 20 分钟，一天切八次，什么都写不出来。",{"title":85,"searchDepth":86,"depth":86,"links":191},[192,193,194,195,196,197,198],{"id":120,"depth":86,"text":120},{"id":129,"depth":86,"text":129},{"id":138,"depth":86,"text":138},{"id":147,"depth":86,"text":147},{"id":156,"depth":86,"text":156},{"id":165,"depth":86,"text":165},{"id":174,"depth":86,"text":174},"2026-05-25","一天四篇不是四篇都在写。我们上午写两篇结构固定的短稿，下午写两篇要查资料的，晚上不回看。试了一个月产出 15 篇，但也暴露了代价。",{},"\u002Fblog\u002Fbatch-writing-workflow",{"title":112,"description":200},"blog\u002Fbatch-writing-workflow",[206,207,208],"内容生产","写作流程","小团队","puckOWYLJ3lsdH2i69ZkDM35fE7R4ntcs-W1aVLW4wA",{"id":211,"title":212,"author":6,"body":213,"canonical":94,"category":312,"cover":94,"date":313,"description":314,"draft":98,"extension":99,"keywords":94,"meta":315,"navigation":101,"noindex":98,"ogImage":94,"path":316,"seo":317,"seoDescription":94,"seoTitle":94,"stem":318,"tags":319,"updated":94,"__hash__":323},"blog\u002Fblog\u002Fbrand-serp-first-page.md","品牌名搜出来第一页，有几条内容是你控制的",{"type":8,"value":214,"toc":303},[215,218,221,224,227,230,233,236,239,242,245,248,251,254,257,260,263,266,269,272,275,278,281,285,288,291,294,297,300],[11,216,217],{},"2026 年 6 月我们给一个客户做品牌词盘点，搜公司名，第一页十条结果里只有四条是他自己控制的。剩下六条是招聘站、点评站、一条旧新闻和一个山寨下载站。",[15,219,220],{"id":220},"品牌结果页该有什么",[11,222,223],{},"理想状态是自己控制五到六条：官网首页、产品页、定价页、文档入口、关于我们、客户案例。",[11,225,226],{},"剩下几条留给第三方，比如评测站、行业媒体、问答。这些第三方内容反而是信任信号，只要内容正面。",[11,228,229],{},"完全不出现第三方也不正常，说明品牌没有外部提及。",[15,231,232],{"id":232},"先做一次盘点",[11,234,235],{},"搜六个查询：品牌名、品牌名加怎么样、品牌名加评价、品牌名加招聘、品牌名加下载、品牌名加价格。",[11,237,238],{},"每个查询看前十名，记录哪条是自己控制的、哪条是第三方、哪条是负面或无关。",[11,240,241],{},"这张表做完，问题基本一目了然。我们通常能在半小时内列出优先级。",[15,243,244],{"id":244},"第三方条目怎么处理",[11,246,247],{},"正面的第三方不用管，甚至可以主动去经营。",[11,249,250],{},"中性的可以争取。比如点评站上的条目信息不全，去认领并补全资料。",[11,252,253],{},"负面的要分情况。事实错误可以联系对方更正；真实投诉，回应比删除有用。",[11,255,256],{},"山寨下载站是最麻烦的，它抢的是品牌名加下载这类查询，用户点进去装到的是改过的安装包。",[15,258,259],{"id":259},"山寨站怎么处理",[11,261,262],{},"先确认是不是真的仿冒：域名、页面内容、安装包来源。",[11,264,265],{},"然后走两条线：一条是向搜索引擎提交侵权或仿冒投诉，另一条是在官网做一个下载说明页，把官方渠道讲清楚。",[11,267,268],{},"我们处理过一个案例，官网的下载页加了校验和公布之后，山寨站在那个查询里的点击明显下降。",[15,270,271],{"id":271},"实体标记要补",[11,273,274],{},"Organization 结构化数据写清公司名、logo、成立时间、社交账号，用 sameAs 把官方账号串起来。",[11,276,277],{},"这一步不直接提排名，但能让搜索引擎更清楚哪个是官方实体，对品牌结果页有帮助。",[11,279,280],{},"再配合关于页、联系页、安全页这些信任页面，品牌词的转化会更好。",[15,282,284],{"id":283},"一个细节品牌词的联想查询","一个细节：品牌词的联想查询",[11,286,287],{},"搜品牌名的时候，搜索框会自动补出关联词，比如品牌名加价格、加破解、加替代品。",[11,289,290],{},"这些联想词反映了用户真实的疑问。补出来的词里有负面或者竞品，说明品牌结果页需要补内容。",[11,292,293],{},"我们的做法是每月看一次联想词，变了就说明用户关注点在变。",[15,295,296],{"id":296},"一个态度",[11,298,299],{},"品牌词搜索量是软件公司最该看的指标之一，因为搜品牌名的人已经在做决策了。",[11,301,302],{},"品牌结果页的每一条都在影响这个决策。花一个下午盘点，比投一轮广告便宜，效果更持久。",{"title":85,"searchDepth":86,"depth":86,"links":304},[305,306,307,308,309,310,311],{"id":220,"depth":86,"text":220},{"id":232,"depth":86,"text":232},{"id":244,"depth":86,"text":244},{"id":259,"depth":86,"text":259},{"id":271,"depth":86,"text":271},{"id":283,"depth":86,"text":284},{"id":296,"depth":86,"text":296},"SEO","2026-05-27","品牌搜索结果页是客户做决策前的最后一站。这篇写该占住的六个位置、怎么盘点、第三方条目怎么挤压，以及实体标记要补什么，附六个必查的品牌查询词。",{},"\u002Fblog\u002Fbrand-serp-first-page",{"title":212,"description":314},"blog\u002Fbrand-serp-first-page",[320,321,322],"品牌搜索","品牌保护","信任信号","zURHT-dE5QAtqiFV81UkyCpikRZZJk977cczifGlzjM",1794088105308]