[{"data":1,"prerenderedAt":401},["ShallowReactive",2],{"blog-privacy-policy-minimum-software":3,"blog-prev-privacy-policy-minimum-software":100,"blog-next-privacy-policy-minimum-software":326},{"id":4,"title":5,"author":6,"body":7,"canonical":84,"category":85,"cover":84,"date":86,"description":87,"draft":88,"extension":89,"keywords":84,"meta":90,"navigation":91,"noindex":88,"ogImage":84,"path":92,"seo":93,"seoDescription":84,"seoTitle":84,"stem":94,"tags":95,"updated":84,"__hash__":99},"blog\u002Fblog\u002Fprivacy-policy-minimum-software.md","软件站隐私政策的最小写法：这六段必须写清","元析智能",{"type":8,"value":9,"toc":77},"minimark",[10,14,18,25,31,37,43,49,55,59,62,65,68,71,74],[11,12,13],"p",{},"隐私政策抄模板，最大的问题不是法律风险，是采购方和搜索引擎都能看出你没认真写。2025 年 10 月我们给一个客户做站点评审，他的隐私政策是从同行那里复制来的，里面还留着对方公司的产品名。",[15,16,17],"h2",{"id":17},"六段必须自己写的内容",[11,19,20,24],{},[21,22,23],"strong",{},"收集了什么数据。"," 表单字段、Cookie、服务器日志、支付信息，逐项列出来。别写\"我们可能收集您在使用过程中的相关信息\"，这种话等于什么都没说。",[11,26,27,30],{},[21,28,29],{},"每条数据为什么收集。"," 收集邮箱是为了发试用账号，收集手机号是为了商务联系，收集 IP 是为了防刷。目的写清楚，用户才知道该不该给。",[11,32,33,36],{},[21,34,35],{},"保存多久。"," 写具体时长，比如\"试用期数据保留 6 个月\"\"日志保留 90 天\"。写\"在法律允许的最长期限内保留\"是偷懒。",[11,38,39,42],{},[21,40,41],{},"共享给谁。"," 云服务商、统计分析工具、支付通道、邮件服务，按类别列出。B2B 客户的法务会专门看这一段。",[11,44,45,48],{},[21,46,47],{},"用户怎么行使权利。"," 查询、更正、删除、导出，每一种给出具体路径和一个邮箱。只写\"您可以通过本政策所述方式联系我们\"是不够的。",[11,50,51,54],{},[21,52,53],{},"Cookie 怎么用。"," 分必要、统计、营销三类，说明各自的用途，并给出拒绝统计和营销 Cookie 的方式。",[15,56,58],{"id":57},"为什么-b2b-软件更要注意","为什么 B2B 软件更要注意",[11,60,61],{},"B2B 采购流程里，隐私政策是必查项。尤其是客户是金融、医疗、政企的时候，对方会问数据存在哪、谁能访问、出境不出境。这些答不上来，单子就卡住。",[11,63,64],{},"海外客户还会看你的政策里有没有数据处理者条款、有没有跨境传输说明。我们有个客户做海外生意，隐私页被对方打回两次，第二次是因为没有写清楚子处理者名单。",[15,66,67],{"id":67},"我们的写法建议",[11,69,70],{},"用表格列数据项，比大段文字好读。页面顶部放一个更新日期和联系人邮箱。全文用短句，别用法律套话堆满。",[11,72,73],{},"页面底部留一个版本记录，写清每次修改的日期和改了哪一段。我们给客户的模板里这一栏是必填的，因为用户和法务都会问\"什么时候改的、改了什么\"。没有版本记录的隐私页，看起来像三年没维护过。",[11,75,76],{},"隐私政策是信任文件。客户愿意把数据交给你，靠的不是条款写得多严密，是你写得让他看得懂。",{"title":78,"searchDepth":79,"depth":79,"links":80},"",2,[81,82,83],{"id":17,"depth":79,"text":17},{"id":57,"depth":79,"text":58},{"id":67,"depth":79,"text":67},null,"内容运营","2026-03-08","隐私政策抄模板，问题不在法律风险，在用户和搜索引擎都能看出你没认真写。这篇给六段必须自己写的内容：收集什么、为什么、存多久、给谁、怎么删、Cookie 怎么管。",false,"md",{},true,"\u002Fblog\u002Fprivacy-policy-minimum-software",{"title":5,"description":87},"blog\u002Fprivacy-policy-minimum-software",[96,97,98],"隐私政策","信任页面","合规","hxwhfmNnP4f452NI21sTd_dm1jUHPF4BRS9sZKSC7oI",{"id":101,"title":102,"author":6,"body":103,"canonical":84,"category":313,"cover":84,"date":314,"description":315,"draft":88,"extension":89,"keywords":84,"meta":316,"navigation":91,"noindex":88,"ogImage":84,"path":317,"seo":318,"seoDescription":84,"seoTitle":84,"stem":319,"tags":320,"updated":84,"__hash__":325},"blog\u002Fblog\u002Fcross-engine-citation-gap.md","同一篇文章在 6 个 AI 引擎里的引用差异：一张对照表",{"type":8,"value":104,"toc":306},[105,108,111,114,117,227,230,236,242,248,251,254,260,266,272,275,278,294,297,300,303],[11,106,107],{},"同一篇文章，在六个引擎里表现完全不同。2026 年 3 月我们拿一个客户的 20 篇内容跑 60 个查询，记录被引来源。ChatGPT 偏爱文档，Perplexity 偏爱对比表，AI Overviews 偏表格和定义段，豆包偏知乎，元宝偏公众号，DeepSeek 偏技术博客。",[15,109,110],{"id":110},"测试怎么做的",[11,112,113],{},"20 篇内容覆盖三类：8 篇文档页、6 篇对比页、6 篇博客。60 个查询，每类各 20 个。六个引擎各跑一遍，记录回答里出现的目标内容，以及挂出来的来源。",[11,115,116],{},"样本不算大，但差异明显到不需要统计检验。",[118,119,120,139],"table",{},[121,122,123],"thead",{},[124,125,126,130,133,136],"tr",{},[127,128,129],"th",{},"引擎",[127,131,132],{},"最常引的来源",[127,134,135],{},"官网占比",[127,137,138],{},"特点",[140,141,142,157,171,185,199,213],"tbody",{},[124,143,144,148,151,154],{},[145,146,147],"td",{},"ChatGPT",[145,149,150],{},"文档页、报错页",[145,152,153],{},"41%",[145,155,156],{},"按句挂源，读得深",[124,158,159,162,165,168],{},[145,160,161],{},"Perplexity",[145,163,164],{},"对比页、第三方评测",[145,166,167],{},"34%",[145,169,170],{},"多源交叉，来源多",[124,172,173,176,179,182],{},[145,174,175],{},"AI Overviews",[145,177,178],{},"表格、定义段",[145,180,181],{},"46%",[145,183,184],{},"只挂少数链接",[124,186,187,190,193,196],{},[145,188,189],{},"豆包",[145,191,192],{},"知乎、CSDN",[145,194,195],{},"23%",[145,197,198],{},"中文平台权重高",[124,200,201,204,207,210],{},[145,202,203],{},"元宝",[145,205,206],{},"公众号、门户",[145,208,209],{},"19%",[145,211,212],{},"平台内容池",[124,214,215,218,221,224],{},[145,216,217],{},"DeepSeek",[145,219,220],{},"技术博客、GitHub",[145,222,223],{},"27%",[145,225,226],{},"技术细节偏好强",[15,228,229],{"id":229},"三个反常识",[11,231,232,235],{},[21,233,234],{},"一、官网占比高的引擎，不一定是好消息。"," AI Overviews 官网占比 46%，但它挂的链接最少，一条回答平均 2.1 个。占比高是因为它几乎不引第三方，不是因为它特别喜欢你。",[11,237,238,241],{},[21,239,240],{},"二、Perplexity 的来源数量在下降。"," 我们 2025 年底测的时候平均 6.4 个，2026 年 3 月是 5.2 个。它开始收敛，意味着单条来源的权重变高，进去更难，进去之后更值钱。",[11,243,244,247],{},[21,245,246],{},"三、同一引擎中英文表现能差一倍。"," ChatGPT 英文查询引官网的比例 48%，中文查询 31%。中文查询它更多去找中文平台，因为你的中文内容密度不够。",[15,249,250],{"id":250},"怎么用这个差异",[11,252,253],{},"别写六版内容，那样成本撑不住。三种做法：",[11,255,256,259],{},[21,257,258],{},"底层事实句通用。"," 带数字、带条件、带时间的那句话，在所有引擎里都好使。这部分写一份，全平台复用。",[11,261,262,265],{},[21,263,264],{},"形态按引擎调。"," 同一批事实，在官网做成表格，在知乎写成长回答，在公众号写成场景故事,在 GitHub 写进 README。不是复制粘贴，是同一事实的四种容器。",[11,267,268,271],{},[21,269,270],{},"平台投放看引擎。"," 如果你的客户主要在中文引擎里做调研，就把资源压到知乎和公众号；如果客户是海外技术团队，官网文档和 GitHub 优先。",[15,273,274],{"id":274},"一个具体的分配",[11,276,277],{},"我们给一个客户排 2026 年 Q2 的内容，是这么分的：",[279,280,281,285,288,291],"ul",{},[282,283,284],"li",{},"官网：12 篇文档页改造 + 4 篇对比页",[282,286,287],{},"知乎：8 个高赞问题下写回答，每篇带一个可引用表格",[282,289,290],{},"公众号：6 篇场景文，讲客户现场",[282,292,293],{},"GitHub：README 重写 + 4 个常见报错的 Issue 模板",[11,295,296],{},"四块内容讲的是一批事实，形态完全不同。三个月后六个引擎的覆盖率从平均 12% 到 24%。",[15,298,299],{"id":299},"一句实在话",[11,301,302],{},"跨引擎差异这件事，知道就好，别过度优化。真正决定你被不被引用的是内容里有没有可搬走的句子，这件工作在哪个引擎都一样。",[11,304,305],{},"引擎的偏好会变，去年和今年就不一样。你追着它改，永远慢一步。",{"title":78,"searchDepth":79,"depth":79,"links":307},[308,309,310,311,312],{"id":110,"depth":79,"text":110},{"id":229,"depth":79,"text":229},{"id":250,"depth":79,"text":250},{"id":274,"depth":79,"text":274},{"id":299,"depth":79,"text":299},"行业观察","2026-03-07","20 篇内容、60 个查询、6 个引擎。ChatGPT 引文档，Perplexity 引对比，AI Overviews 引表格，豆包引知乎，元宝引公众号。一份内容通吃是幻觉。",{},"\u002Fblog\u002Fcross-engine-citation-gap",{"title":102,"description":315},"blog\u002Fcross-engine-citation-gap",[321,322,323,324],"跨引擎","AI引用","GEO","平台差异","vA62lvr-AdPl0Ra4CThbC775hIOAXeYVtZG4nuHo2MQ",{"id":327,"title":328,"author":6,"body":329,"canonical":84,"category":389,"cover":84,"date":390,"description":391,"draft":88,"extension":89,"keywords":84,"meta":392,"navigation":91,"noindex":88,"ogImage":84,"path":393,"seo":394,"seoDescription":84,"seoTitle":84,"stem":395,"tags":396,"updated":84,"__hash__":400},"blog\u002Fblog\u002Ffigma-plugin-listing-seo.md","设计插件在 Figma 市场里怎么被搜到",{"type":8,"value":330,"toc":383},[331,334,338,341,344,347,350,353,356,359,362,365,368,371,374,377,380],[11,332,333],{},"设计类插件的流量，八成来自插件市场站内搜索，不是 Google。2026 年 1 月我们帮一个做图标管理插件的团队改列表页文案，两个月安装量从 4700 涨到 1.3 万，同期没有增加任何推广。",[15,335,337],{"id":336},"市场搜索的规则和-google-不同","市场搜索的规则和 Google 不同",[11,339,340],{},"用户不会输入长句，通常是两三个词：“图标”“批量”“导出”“auto layout”。市场排序主要看相关性、安装量、更新频率和评分。刚上架的插件，前两项吃亏，所以标题和描述的相关性权重显得更重。",[11,342,343],{},"标题的写法：核心功能词加场景限定。“Icon Manager”这种纯品牌名搜不到，“Icon Manager - Batch Replace & Export”才能命中批量替换和导出两个动作。",[11,345,346],{},"描述的前两行尤其关键。市场列表页的搜索结果只展示标题加一两行描述，用户是看这两行决定点不点。我们一般把“做什么、给谁用、解决什么具体问题”压进这两行。",[15,348,349],{"id":349},"我们做的三个动作",[11,351,352],{},"第一，把标题从品牌名改成“品牌名 + 功能短语”，保留品牌词便于老用户找。",[11,354,355],{},"第二，描述第一行写清动作：“批量替换画板里的图标并导出 SVG\u002FPNG”，第二行写给谁：“适合有 100+ 画板的设计系统项目”。",[11,357,358],{},"第三，更新日志保持每月一次。市场会按更新频率给一定曝光，长期不更新的插件排名会掉。我们让客户把一些小的体验改进也发出来，别憋大招。",[15,360,361],{"id":361},"安装页也是搜索资产",[11,363,364],{},"插件详情页本身有 URL，会被 Google 索引。用户搜“figma 批量替换图标”时，详情页有机会出现在结果里。所以详情页里的功能说明要完整，别只写三行。",[11,366,367],{},"我们给其中一个插件补了 600 字的功能说明加 4 张截图，详情页从市场站外带来的访问每月 300 多次，占总量不到 5%，但转化率高，因为来的人已经在找解决方案。",[11,369,370],{},"评论区也要管。市场页的评论是公开的，用户提问没人回，后面的访客会犹豫。我们建议把评论通知接到团队群里，48 小时内回。这件事对排名的直接影响很小，对安装转化的影响很实在。",[15,372,373],{"id":373},"一个坑",[11,375,376],{},"别在插件标题里堆词。市场对关键词堆砌有降权，我们试过把“icon、svg、export、batch”全塞进标题，安装量没涨，搜索排名反而掉了。后来缩到两个功能词，效果最好。",[11,378,379],{},"还有一个位置别浪费：详情页截图的说明文字。市场会把这段文字索引进去，“批量替换图标前后对比”这种描述能多覆盖一组词。",[11,381,382],{},"插件市场的 SEO 逻辑简单粗暴：把用户会搜的两个词放进标题，把具体动作写进描述前两行，保持更新。剩下的交给安装量和评分。",{"title":78,"searchDepth":79,"depth":79,"links":384},[385,386,387,388],{"id":336,"depth":79,"text":337},{"id":349,"depth":79,"text":349},{"id":361,"depth":79,"text":361},{"id":373,"depth":79,"text":373},"SEO","2026-03-09","Figma 社区的插件列表页，标题和描述就是全部关键词资产，写错了就没人点。我们改了 3 个插件的标题和描述前两行，安装量在两个月里涨了 1.8 倍。",{},"\u002Fblog\u002Ffigma-plugin-listing-seo",{"title":328,"description":391},"blog\u002Ffigma-plugin-listing-seo",[397,398,399],"插件市场","设计工具","关键词","8MJrgjw2A4t7oP93Sv4I5-YH-DZPDoevvO7aH3Hef1Y",1794088107791]