[{"data":1,"prerenderedAt":383},["ShallowReactive",2],{"blog-paragraph-topic-sentence-test":3,"blog-prev-paragraph-topic-sentence-test":176,"blog-next-paragraph-topic-sentence-test":288},{"id":4,"title":5,"author":6,"body":7,"canonical":160,"category":161,"cover":160,"date":162,"description":163,"draft":164,"extension":165,"keywords":160,"meta":166,"navigation":167,"noindex":164,"ogImage":160,"path":168,"seo":169,"seoDescription":160,"seoTitle":160,"stem":170,"tags":171,"updated":160,"__hash__":175},"blog\u002Fblog\u002Fparagraph-topic-sentence-test.md","改了 200 个段落的主题句，AI 引用率从 14% 涨到 26%","元析智能",{"type":8,"value":9,"toc":151},"minimark",[10,14,18,21,24,27,30,33,36,92,96,99,102,105,108,111,114,121,127,133,136,139,142,145,148],[11,12,13],"p",{},"把段尾的总结句搬到段首，引用率涨 9 个百分点；在段首新加一句主题句、原句不动，只涨 2 个点。2025 年 12 月到 2026 年 2 月，我们在 40 篇文章、200 个段落上做了这组对照，差别不在句子写得好不好，在位置。",[15,16,17],"h2",{"id":17},"为什么段尾总结没用",[11,19,20],{},"很多人写段落是归纳式：先讲三个事实，最后来一句\"所以说 XX 更适合中小团队\"。人读着舒服，机器读不到。",[11,22,23],{},"原因在切块。AI 按 token 窗口切，一段 300 字，切点可能落在 220 字。你放在第 280 字的总结句，被切到下一块去了。下一块没了前提，那句话就孤立，引擎不敢用。",[11,25,26],{},"段首句没有这个问题。它在块的起点，一定被包含在内。",[15,28,29],{"id":29},"三组怎么改的",[11,31,32],{},"A 组：段首新加一句主题句，原段落一字不改。\nB 组：把长段落拆成两段，前段给结论，后段展开。\nC 组：把原来的段尾总结句原样搬到段首，删掉段尾那句。",[11,34,35],{},"200 个段落，40 篇文章，三个客户站，各分一组。8 周，每周三跑固定 45 个查询。",[37,38,39,55],"table",{},[40,41,42],"thead",{},[43,44,45,49,52],"tr",{},[46,47,48],"th",{},"组别",[46,50,51],{},"改法",[46,53,54],{},"引用率变化",[56,57,58,70,81],"tbody",{},[43,59,60,64,67],{},[61,62,63],"td",{},"A",[61,65,66],{},"段首加主题句",[61,68,69],{},"+2pp",[43,71,72,75,78],{},[61,73,74],{},"B",[61,76,77],{},"段落拆分",[61,79,80],{},"+6pp",[43,82,83,86,89],{},[61,84,85],{},"C",[61,87,88],{},"总结句前移",[61,90,91],{},"+9pp",[15,93,95],{"id":94},"c-组为什么赢","C 组为什么赢",[11,97,98],{},"因为 C 组改的是同一句话的位置，内容没变，所以变量干净。",[11,100,101],{},"A 组加了新句子，段首变长，反而挤掉了原文里的具体信息。我们回看 A 组的段落，主题句大多是\"本节讨论数据同步的三个关键点\"这种，没有事实，加了等于没加。",[11,103,104],{},"B 组有效，但拆段会让段落数量翻倍，读起来碎。我们后来只在超过 400 字的段落上用。",[11,106,107],{},"C 组的做法最省事：找到段尾那句总结，剪到段首，检查一下衔接。一个编辑一天能改 60 段。",[15,109,110],{"id":110},"主题句怎么写",[11,112,113],{},"三个能直接用的句式：",[11,115,116,120],{},[117,118,119],"strong",{},"给判断。","\"同步延迟主要卡在跨区域这一环。\"",[11,122,123,126],{},[117,124,125],{},"给边界。","\"这套方案只适合 500 人以下团队，再大要改分片。\"",[11,128,129,132],{},[117,130,131],{},"给数字。","\"改这一处，平均省 40% 的同步时间。\"",[11,134,135],{},"三种都有共同点：句子本身是完整信息，不需要后文。",[11,137,138],{},"别用的句式：本节将讨论、下面介绍、以下几点。这些句子把信息推到后面，等于把可引用点让出去。",[15,140,141],{"id":141},"一个反常识的结论",[11,143,144],{},"段尾总结在 AI 搜索时代是浪费。它本来是为了让读者不用回看，现在读者是机器，机器不回看，机器只看切出来的那一块。",[11,146,147],{},"我们现在的编辑规范里有一条：段落最后一句不许写总结。要么删，要么移到最前面。",[11,149,150],{},"改完 200 段，最直观的感受是文章变硬了。每段开头都是一句能单独站住的话，读起来像在听人下判断，不是听人铺垫。",{"title":152,"searchDepth":153,"depth":153,"links":154},"",2,[155,156,157,158,159],{"id":17,"depth":153,"text":17},{"id":29,"depth":153,"text":29},{"id":94,"depth":153,"text":95},{"id":110,"depth":153,"text":110},{"id":141,"depth":153,"text":141},null,"GEO","2026-01-22","40 篇文章、三种改法对照 8 周。把段尾总结搬到段首那组涨 9 个百分点，单纯加一句主题句那组几乎没动。差别在句子位置，不在句子质量。",false,"md",{},true,"\u002Fblog\u002Fparagraph-topic-sentence-test",{"title":5,"description":163},"blog\u002Fparagraph-topic-sentence-test",[161,172,173,174],"内容写作","主题句","AI引用","LHYrq3mP3cXXJrQrn8FL86UIdtcC5HyitUO0dOUOM8w",{"id":177,"title":178,"author":6,"body":179,"canonical":160,"category":276,"cover":160,"date":277,"description":278,"draft":164,"extension":165,"keywords":160,"meta":279,"navigation":167,"noindex":164,"ogImage":160,"path":280,"seo":281,"seoDescription":160,"seoTitle":160,"stem":282,"tags":283,"updated":160,"__hash__":287},"blog\u002Fblog\u002Ftopic-backlog-grooming.md","选题池每周维护 30 分钟，超过 60 条就该冻结",{"type":8,"value":180,"toc":265},[181,184,188,191,194,197,200,203,207,210,213,216,219,222,225,228,231,234,237,240,243,246,250,253,256,259,262],[11,182,183],{},"选题池不是待办清单，是会腐烂的库存。我们固定每周五下午花 30 分钟维护，只做三件事：加新词、补状态、删过期。池子上限 60 条，超了就冻结新增。",[15,185,187],{"id":186},"三件事各-10-分钟","三件事各 10 分钟",[11,189,190],{},"前 10 分钟把本周从搜索后台、工单、销售记录里冒出来的词加进去。中间 10 分钟补状态，把卡住的题标出来。最后 10 分钟从池子里捞三条进下周的排期。",[11,192,193],{},"30 分钟之外不做任何整理。整理得越漂亮，越说明没人真用它写东西。",[15,195,196],{"id":196},"状态只有五种",[11,198,199],{},"待定、待资料、可写、写作中、已发。",[11,201,202],{},"一个题卡在“待资料”超过三周，就要么降级、要么删掉。资源拿不到就是拿不到，挂着只会让人以为还有事没做。",[15,204,206],{"id":205},"池子超过-60-条就该冻结","池子超过 60 条就该冻结",[11,208,209],{},"2025 年 9 月我们的池子涨到 210 条，两个月里没人打开，因为打开也不知道从哪条开始。",[11,211,212],{},"后来砍到 45 条，只留能在一个季度内写完的。第一个月就有人主动从里面捞题，这是之前没发生过的。",[15,214,215],{"id":215},"什么时候删",[11,217,218],{},"三个月没人认领的删。产品功能已下线的删。竞品已经把这件事做透、我们赢不了的删。跟核心词不沾边的删。",[11,220,221],{},"删掉不等于丢失。我们留一个归档表，只写词和删除原因，翻起来比在池子里混着找快。",[15,223,224],{"id":224},"谁维护",[11,226,227],{},"一个人。别搞轮流，轮流等于没人负责。",[11,229,230],{},"我们现在是内容岗的人自己维护，每周五下班前 30 分钟，写在日历上，不做其他事。",[15,232,233],{"id":233},"一个配套的小约定",[11,235,236],{},"新题进池子必须带一句“这篇的独家信息是什么”。写不出来就不进池子。",[15,238,239],{"id":239},"池子和排期的关系",[11,241,242],{},"池子是候选，排期是承诺。只有进了排期的题才需要定发布日，池子里的题不需要日期。",[11,244,245],{},"我们以前给池子里每条都写了计划发布日期，结果日期一路往后推，三个月后整张表全是过期的日期，看着就丧气。",[15,247,249],{"id":248},"三个来源每周各看一遍","三个来源，每周各看一遍",[11,251,252],{},"搜索后台的新查询，工单里的新问题，销售在群里转的客户原话。三个来源各花 3 分钟，扫一眼就行，不用逐条记录。",[11,254,255],{},"记的时候只记原话，不记你理解后的版本。原话才是用户在搜索框里会打的字。",[15,257,258],{"id":258},"一个小细节",[11,260,261],{},"池子里的题按意图排序，不按时间排序。写的人打开就知道自己这周该写哪一类，不用再问。",[11,263,264],{},"这句话逼着我们在选题阶段就想清楚能不能写，省掉了后面一半的返工。",{"title":152,"searchDepth":153,"depth":153,"links":266},[267,268,269,270,271,272,273,274,275],{"id":186,"depth":153,"text":187},{"id":196,"depth":153,"text":196},{"id":205,"depth":153,"text":206},{"id":215,"depth":153,"text":215},{"id":224,"depth":153,"text":224},{"id":233,"depth":153,"text":233},{"id":239,"depth":153,"text":239},{"id":248,"depth":153,"text":249},{"id":258,"depth":153,"text":258},"内容运营","2026-01-21","选题池不是待办清单，是会腐烂的库存。我们固定每周五花 30 分钟做三件事：加新词、补状态、删过期。池子从 210 条砍到 45 条之后，才真正有人用它。",{},"\u002Fblog\u002Ftopic-backlog-grooming",{"title":178,"description":278},"blog\u002Ftopic-backlog-grooming",[284,285,286],"选题机制","内容排期","工作流","DeVBh5sv2s5KU1Z0a4O7Apl8DnlS4JKMetQFkywqbWU",{"id":289,"title":290,"author":6,"body":291,"canonical":160,"category":371,"cover":160,"date":372,"description":373,"draft":164,"extension":165,"keywords":160,"meta":374,"navigation":167,"noindex":164,"ogImage":160,"path":375,"seo":376,"seoDescription":160,"seoTitle":160,"stem":377,"tags":378,"updated":160,"__hash__":382},"blog\u002Fblog\u002Fauthor-page-eeat-fields.md","博客作者页该写的七个字段，别只放一张头像",{"type":8,"value":292,"toc":366},[293,296,300,306,312,318,324,330,336,342,345,348,351,354,357,360,363],[11,294,295],{},"作者页不是装饰，它是搜索引擎和 AI 搜索判断\"这篇文章谁写的、凭什么信\"的落点。我们审过 30 多个软件站的作者页，真正合格的不到三成，多数只放了一张头像和一句\"内容团队\"。",[15,297,299],{"id":298},"七个字段一个都别省","七个字段，一个都别省",[11,301,302,305],{},[117,303,304],{},"真实姓名。"," 不是\"运营团队\"\"编辑部\"，是能对应到一个真人。匿名作者页在信任信号上基本等于没有。",[11,307,308,311],{},[117,309,310],{},"职位和负责范围。"," 写清楚这个人负责什么内容，比如\"负责 API 与集成方向的技术内容\"。范围越具体，读者越容易判断该不该信。",[11,313,314,317],{},[117,315,316],{},"履历。"," 做过什么产品、在什么行业待了几年、有没有落地的项目。不需要写成简历，两三句话，但要具体。",[11,319,320,323],{},[117,321,322],{},"可验证痕迹。"," GitHub 账号、知乎主页、领英、公开演讲、开源项目、专利。这一项最值钱，因为别人能去查证。",[11,325,326,329],{},[117,327,328],{},"社交账号互链。"," 从作者页能点到他的公开账号，也能从账号资料点回来。双向可查，可信度才成立。",[11,331,332,335],{},[117,333,334],{},"联系方式。"," 邮箱或表单。能联系上，是\"真人负责\"的最直接证据。",[11,337,338,341],{},[117,339,340],{},"文章列表和更新时间。"," 这个作者写过哪些文章，最近一次更新是什么时候。没有文章列表的作者页，等于一个空壳。",[15,343,344],{"id":344},"我们的两条验收标准",[11,346,347],{},"第一条，把作者名字复制到搜索引擎查一遍，能不能找到这个人的其他痕迹。如果只在你自己的网站上出现，这个人对搜索引擎来说就不存在。",[11,349,350],{},"第二条，作者页上的技术主张和文章内容对不对得上。我们见过作者页写\"十年数据库经验\"，文章里却把主从复制和分片混着讲，这种反而扣分。",[11,352,353],{},"验收标准落地前后的对比很直观：改之前搜署名作者的名字，只出现自家站；改完两周，搜名字能出来 5 条，包括 GitHub 账号和一次行业论坛的发言。",[15,355,356],{"id":356},"常见的糊弄法",[11,358,359],{},"批量上 stock 头像，五个作者用同一个模板，简介只换个名字。或者作者页写得很漂亮，但文章列表是空的。还有一种是找行业里的人挂名，文章其实是实习生写的，这种一旦被问到就露馅。",[11,361,362],{},"2025 年 12 月我们给一个客户重做作者页，三个作者全部换成实名，并且要求每人认领自己写过的文章。有个作者当场发现，两篇挂着别人名字的文章其实是自己写的，这种情况挺常见，改过来对双方都好。",[11,364,365],{},"作者页补起来成本很低，一个下午就能做完，但它是少数\"做了就一直在起作用\"的事。一个能查到的真人，胜过十个\"内容团队\"。",{"title":152,"searchDepth":153,"depth":153,"links":367},[368,369,370],{"id":298,"depth":153,"text":299},{"id":344,"depth":153,"text":344},{"id":356,"depth":153,"text":356},"SEO","2026-01-23","作者页是 E-E-A-T 里最容易补、也最容易被糊弄的一块。这篇给七个必填字段：真实姓名、职位、履历、可验证痕迹、社交账号、负责范围、联系方式，附两条验收标准。",{},"\u002Fblog\u002Fauthor-page-eeat-fields",{"title":290,"description":373},"blog\u002Fauthor-page-eeat-fields",[379,380,381],"E-E-A-T","作者页","内容信任","-wPumupjPIEC9hVDE9nWd4d_lKCrpPh92m4_bYXJbVI",1794088108991]