[{"data":1,"prerenderedAt":359},["ShallowReactive",2],{"blog-content-freshness-ai-citation":3,"blog-prev-content-freshness-ai-citation":135,"blog-next-content-freshness-ai-citation":243},{"id":4,"title":5,"author":6,"body":7,"canonical":119,"category":120,"cover":119,"date":121,"description":122,"draft":123,"extension":124,"keywords":119,"meta":125,"navigation":126,"noindex":123,"ogImage":119,"path":127,"seo":128,"seoDescription":119,"seoTitle":119,"stem":129,"tags":130,"updated":119,"__hash__":134},"blog\u002Fblog\u002Fcontent-freshness-ai-citation.md","内容保鲜：AI 更愿意引用最近更新的页面吗","元析智能",{"type":8,"value":9,"toc":108},"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,84,87,90,93,96,99,102,105],[11,12,13],"p",{},"2026 年 9 月我们做了一轮内容更新，挑出二十篇两年以上的旧文，改事实、加数据、补边界。四周后其中六篇在 AI 回答里重新出现。但这件事和\"改个日期\"完全不是一回事。",[15,16,17],"h2",{"id":17},"时效性要分问题类型",[11,19,20],{},"概念类问题，比如什么是抓取预算，答案一年半载不会变，更新日期意义不大。",[11,22,23],{},"时效类问题，比如某工具现在的价格、某平台最新的限制、今年算法有什么变化，这类内容过时就是错的。",[11,25,26],{},"所以先分类，再决定更不更新。全部改日期没有意义，搜索引擎和 AI 都不傻。",[15,28,29],{"id":29},"哪类内容值得更新",[11,31,32],{},"第一，带具体数字的。价格、配额、限制、版本号，这些每年都在变。",[11,34,35],{},"第二，讲工具操作的。界面改了，截图和步骤就废了。",[11,37,38],{},"第三，讲算法的。新更新出来了，旧结论要修正。",[11,40,41],{},"第四，有排名的老文章。已经有曝光和点击，更新之后收益最直接。",[15,43,44],{"id":44},"怎么更新才有效",[11,46,47],{},"不是重写，是修正和补充。",[11,49,50],{},"改事实：把过时的数字和结论改掉，在文中标明更新时间和改了什么。",[11,52,53],{},"补边界：原来只写优点，现在补上不适用的情况。",[11,55,56],{},"补数据：把这两年的新观察加进去，让文章有新的信息。",[11,58,59],{},"保留旧版本的说法，有些读者就是来找旧版本的。",[15,61,62],{"id":62},"两种无效更新",[11,64,65],{},"第一种，只改日期。内容一字不动，发布日改成今天。这种做法骗不了任何人。",[11,67,68],{},"第二种，频繁小改。每周动一句，页面长期处于变化中，反而看不出重点。",[11,70,71],{},"我们的节奏是每季度集中更新一批，一次改到位。",[15,73,74],{"id":74},"我们怎么排优先级",[11,76,77],{},"先按流量排，看哪些旧文还在带来访问。再看引用，哪些旧文被 AI 引用过，值得维护。",[11,79,80],{},"两个都靠前的，优先更新。两个都没有的，考虑合并或者下架。",[11,82,83],{},"这个清单我们每季度过一遍，一次花半天。",[15,85,86],{"id":86},"更新的两个信号",[11,88,89],{},"更新之后看两个变化：页面在 AI 回答里出现的次数，以及页面的自然点击。",[11,91,92],{},"有时候引用没变，点击变了。这可能是因为回答里的位置变了，或者用户看完回答直接搜了品牌名。",[11,94,95],{},"两个数一起看，才能判断更新有没有用。",[15,97,98],{"id":98},"一个发现",[11,100,101],{},"更新之后被重新引用的六篇，有五篇是加了大段的新数据，不是改了措辞。",[11,103,104],{},"这和我们之前的观察一致：AI 引用的是具体信息，不是文采。",[11,106,107],{},"所以保鲜的核心不是让文章看起来新，是让它包含新的、可验证的内容。",{"title":109,"searchDepth":110,"depth":110,"links":111},"",2,[112,113,114,115,116,117,118],{"id":17,"depth":110,"text":17},{"id":29,"depth":110,"text":29},{"id":44,"depth":110,"text":44},{"id":62,"depth":110,"text":62},{"id":74,"depth":110,"text":74},{"id":86,"depth":110,"text":86},{"id":98,"depth":110,"text":98},null,"SEO","2026-09-03","我们更新了二十篇旧文，六篇在四周内被重新引用。但保鲜不等于改日期，这篇写哪类内容值得更新、怎么改才有效、以及无效更新的两种做法。",false,"md",{},true,"\u002Fblog\u002Fcontent-freshness-ai-citation",{"title":5,"description":122},"blog\u002Fcontent-freshness-ai-citation",[131,132,133],"GEO","内容更新","引用","3Lds04KF92UkBPiP7HI6N8ip-ZSZTWpwAfrR5LKqMlU",{"id":136,"title":137,"author":6,"body":138,"canonical":119,"category":232,"cover":119,"date":233,"description":234,"draft":123,"extension":124,"keywords":119,"meta":235,"navigation":126,"noindex":123,"ogImage":119,"path":236,"seo":237,"seoDescription":119,"seoTitle":119,"stem":238,"tags":239,"updated":119,"__hash__":242},"blog\u002Fblog\u002Fupdate-log-last-updated.md","更新日志和“最后更新”日期，用对了能救回一批老文",{"type":8,"value":139,"toc":221},[140,143,146,149,152,155,158,161,164,167,170,173,176,179,182,185,188,191,194,197,200,203,206,209,212,215,218],[11,141,142],{},"老文翻新完，如果不告诉任何人和任何引擎它更新过，这次改动基本等于白做。我们的做法很土：标题下面加一行更新标记，另维护一份更新日志。2026 年上半年改过一批 30 篇，六周后点击率涨了 0.6 个百分点。",[15,144,145],{"id":145},"更新标记放哪",[11,147,148],{},"标题下面、正文之前，一行小字：最后更新于 2026 年 5 月，并写一句这次改了什么。",[11,150,151],{},"位置要显眼。放在页脚等于没有，用户看不到，引擎也不一定当正文处理。",[15,153,154],{"id":154},"写清改了什么",[11,156,157],{},"“补充了 2025 年的价格数据”“重写了第三节”“增加了两个常见报错”。一句话就够，不用写长。",[11,159,160],{},"这句话对读者是信号：这个页面有人维护。对引擎是信号：内容有变化。",[15,162,163],{"id":163},"更新日志单独一页",[11,165,166],{},"每个季度汇总一次，列出这季度更新了哪些页面、改了什么、为什么改。放在博客的一个固定路径下。",[11,168,169],{},"这份日志有三个用处：给客户看工作量，给自己看迭代节奏，给销售做素材。",[15,171,172],{"id":172},"别乱改日期",[11,174,175],{},"最常见的坏习惯：什么都不改，只把日期改成今天。这种更新骗不了任何人，用户点进去看到两年前的内容，信任直接掉。",[11,177,178],{},"我们有个规矩：更新标记的日期必须对应实质改动，改动小于三段的，不更新日期。",[15,180,181],{"id":181},"什么时候该更新",[11,183,184],{},"三种情况：数据过时、结构跟不上、有明显的补充内容。",[11,186,187],{},"还有一种情况是排名下滑，但那种要按清单排查，不一定是内容问题。",[15,189,190],{"id":190},"一个技术细节",[11,192,193],{},"更新日期可以用结构化数据里的 dateModified，让引擎明确知道修改时间。这个字段很多站没填，填上成本很低。",[11,195,196],{},"我们的做法是：发布时间用 datePublished，修改时间用 dateModified，两个都填，页面可见位置只露修改时间。",[15,198,199],{"id":199},"别过度承诺",[11,201,202],{},"有些站写“本页每月更新”，实际上根本没动。承诺了做不到，比不承诺更伤。",[15,204,205],{"id":205},"谁来维护这份日志",[11,207,208],{},"内容岗的人自己维护，每季度最后一周花一小时汇总。别交给运营助理，他不知道哪些改动是实质的。",[11,210,211],{},"日志不用写得漂亮，一行一条：日期、页面、改了什么。写满一年再回看，能看出自己的迭代节奏。",[15,213,214],{"id":214},"一个意外的好处",[11,216,217],{},"更新日志能帮销售。客户问“你们对这块有研究吗”，把日志里相关的一条发过去，比发十篇博客有效。",[11,219,220],{},"我们只写已经发生的事，不写未来的计划。",{"title":109,"searchDepth":110,"depth":110,"links":222},[223,224,225,226,227,228,229,230,231],{"id":145,"depth":110,"text":145},{"id":154,"depth":110,"text":154},{"id":163,"depth":110,"text":163},{"id":172,"depth":110,"text":172},{"id":181,"depth":110,"text":181},{"id":190,"depth":110,"text":190},{"id":199,"depth":110,"text":199},{"id":205,"depth":110,"text":205},{"id":214,"depth":110,"text":214},"内容运营","2026-09-02","老文更新后没有更新标记，等于白改。我们在标题下加一行“某年某月更新”，并维护一份更新日志，六周后这批页面的点击率涨了 0.6 个百分点。",{},"\u002Fblog\u002Fupdate-log-last-updated",{"title":137,"description":234},"blog\u002Fupdate-log-last-updated",[132,240,241],"更新日志","旧文翻新","xtgygjjjjj94e7ovbTAqkhUX87E8e0CAKYYSv_rcl7s",{"id":244,"title":245,"author":6,"body":246,"canonical":119,"category":347,"cover":119,"date":348,"description":349,"draft":123,"extension":124,"keywords":119,"meta":350,"navigation":126,"noindex":123,"ogImage":119,"path":351,"seo":352,"seoDescription":119,"seoTitle":119,"stem":353,"tags":354,"updated":119,"__hash__":358},"blog\u002Fblog\u002Fnegative-serp-handling.md","搜索结果里有负面，先分清三种情况再动手",{"type":8,"value":247,"toc":338},[248,251,254,257,260,263,266,269,272,275,278,281,284,287,290,293,296,299,302,305,308,311,314,317,320,323,326,329,332,335],[11,249,250],{},"2026 年 9 月一个客户的品牌词结果页里出现两条负面，他第一反应是找人删。我们建议先别动，分清是哪一类，处理方式完全不同。删错一次，可能引来更多。",[15,252,253],{"id":253},"三种情况",[11,255,256],{},"第一种，事实错误。比如文章里写的产品缺陷是你三年前就修掉的，或者公司信息写错了。",[11,258,259],{},"第二种，真实投诉。用户确实遇到了问题，写了差评或者投诉帖。",[11,261,262],{},"第三种，垃圾负面。竞争对手的水军、靠负面流量赚钱的站、批量生成的抹黑内容。",[11,264,265],{},"三种混在一起处理，效果最差。",[15,267,268],{"id":268},"事实错误怎么处理",[11,270,271],{},"先联系作者或者平台，提供证据，请求更正。语气要客气，别上来就发律师函。",[11,273,274],{},"对方不回应，就在官网发一篇澄清页，把事实、时间线、证据写清楚。",[11,276,277],{},"澄清页要能被搜到，标题用品牌名加事件关键词。用户搜的时候能看到两个版本，会自己判断。",[15,279,280],{"id":280},"真实投诉怎么处理",[11,282,283],{},"回应比删除有用。在投诉出现的地方公开回复，说清问题、处理进度、补偿方案。",[11,285,286],{},"回复要具体，别写\"我们非常重视\"这种话。写清哪一步出了问题、什么时候修好。",[11,288,289],{},"如果问题已经解决，请投诉人补充一句后续。很多人愿意补，因为问题解决了。",[15,291,292],{"id":292},"垃圾负面怎么处理",[11,294,295],{},"先看特征：内容空泛、没有具体细节、发布时间集中、账号是新的。",[11,297,298],{},"这类可以走平台投诉，理由是垃圾内容或者恶意攻击。",[11,300,301],{},"但绝对不要买删帖服务。这个行业骗子多，钱花了不一定删掉，删掉的可能过几天又出来，还有法律风险。",[15,303,304],{"id":304},"长期的解法",[11,306,307],{},"品牌词结果页的构成，是可以经营的。",[11,309,310],{},"把官网的关于页、产品页、文档、案例、安全页做好，再经营第三方评测站和行业媒体，正面内容自然占位。",[11,312,313],{},"一个客户花了六个月做这件事，品牌词前十里有七条是正面内容，两条负面被挤到第二页。",[15,315,316],{"id":316},"一个反常识的观察",[11,318,319],{},"负面帖子有时候带来流量。我们运营过一个站，用户搜品牌名加坑不坑，会被带到一条讨论帖，帖子里一半人在说好话。",[11,321,322],{},"帖子本身我们动不了，但它把决策周期拉长了，用户看完对比再下单，转化反而更好。",[11,324,325],{},"所以别把所有负面都当敌人，先看里面有没有真实信息。",[15,327,328],{"id":328},"一个态度",[11,330,331],{},"负面信息不会消失，但可以被稀释。",[11,333,334],{},"大多数用户看到一条负面，会同时看三条正面来判断。你的任务是让正面内容足够多、足够具体。",[11,336,337],{},"把精力放在这里，比找人删帖划算得多，也安全得多。",{"title":109,"searchDepth":110,"depth":110,"links":339},[340,341,342,343,344,345,346],{"id":253,"depth":110,"text":253},{"id":268,"depth":110,"text":268},{"id":280,"depth":110,"text":280},{"id":292,"depth":110,"text":292},{"id":304,"depth":110,"text":304},{"id":316,"depth":110,"text":316},{"id":328,"depth":110,"text":328},"行业观察","2026-09-04","负面信息处理错方式，往往越处理越糟。这篇写事实错误、真实投诉、垃圾负面三类怎么区分，各自该怎么处理，以及为什么不建议买删帖。",{},"\u002Fblog\u002Fnegative-serp-handling",{"title":245,"description":349},"blog\u002Fnegative-serp-handling",[355,356,357],"品牌保护","口碑","负面信息","7g1uC9f6Ke9PEzgEABmPZzF5vYikiPD4dZGm-3M7tbY",1794088102173]