[{"data":1,"prerenderedAt":326},["ShallowReactive",2],{"blog-gated-whitepaper-download":3,"blog-prev-gated-whitepaper-download":123,"blog-next-gated-whitepaper-download":248},{"id":4,"title":5,"author":6,"body":7,"canonical":107,"category":108,"cover":107,"date":109,"description":110,"draft":111,"extension":112,"keywords":107,"meta":113,"navigation":114,"noindex":111,"ogImage":107,"path":115,"seo":116,"seoDescription":107,"seoTitle":107,"stem":117,"tags":118,"updated":107,"__hash__":122},"blog\u002Fblog\u002Fgated-whitepaper-download.md","白皮书要不要留资才能下载，我们试过两种","元析智能",{"type":8,"value":9,"toc":96},"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],[11,12,13],"p",{},"2026 年 8 月一个客户纠结白皮书要不要留资才能下载。我们的建议是先想清楚这份白皮书是拿来收线索的，还是拿来被引用的。两个目的对应两种做法，很难兼得。",[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],{},"我们的做法是在文末放一个轻量的转化入口，比如\"想要原始数据，留个邮箱\"，不强制。",[15,40,41],{"id":41},"我们的折中方案",[11,43,44],{},"正文公开，附录留资。核心结论和数据图表放在页面上，原始数据集、完整问卷、细分行业数据放在表单后面。",[11,46,47],{},"这样读者能判断内容有没有价值，愿意再研究的再留资。",[11,49,50],{},"我们给客户上线过两版，公开版带来的页面访问是留资版的十几倍，留资版拿到的线索质量更高，但数量少。",[15,52,53],{"id":53},"表单要精简",[11,55,56],{},"如果决定留资，字段控制在三个以内：姓名、公司邮箱、公司名。",[11,58,59],{},"职位、电话、需求描述这些字段每多一个，转化率就往下掉。我们见过要填七项的表单，基本没人填完。",[11,61,62],{},"邮箱建议用公司邮箱校验，能挡掉一部分无效线索，但也别太严，很多小公司用个人邮箱。",[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],{},"我们给客户的白皮书都会配一份分发清单：官网、公众号、两个行业媒体、一个数据社区。",[15,85,86],{"id":86},"一个态度",[11,88,89],{},"白皮书是 B2B 软件最好的内容形式之一，因为它有独家数据、有观点、能被反复引用。",[11,91,92],{},"但它不该被当成线索收集器。用一份公开的好内容换长期的品牌信任，比用一份要填表的内容换几十条线索更值。",[11,94,95],{},"如果两个都想要，就做两份：公开版和深度版。",{"title":97,"searchDepth":98,"depth":98,"links":99},"",2,[100,101,102,103,104,105,106],{"id":17,"depth":98,"text":17},{"id":29,"depth":98,"text":29},{"id":41,"depth":98,"text":41},{"id":53,"depth":98,"text":53},{"id":65,"depth":98,"text":65},{"id":74,"depth":98,"text":74},{"id":86,"depth":98,"text":86},null,"内容运营","2026-08-15","留资能拿到线索，但会挡掉九成读者和引用。这篇写两种模式的取舍、留资表单怎么精简、不留资时怎么衡量白皮书的价值，附我们的折中方案。",false,"md",{},true,"\u002Fblog\u002Fgated-whitepaper-download",{"title":5,"description":110},"blog\u002Fgated-whitepaper-download",[119,120,121],"白皮书","内容营销","线索获取","ub-yB-Y9gCGZaMNPoXYIuta6j5Dzzsii9rcx4ldVF8g",{"id":124,"title":125,"author":6,"body":126,"canonical":107,"category":236,"cover":107,"date":237,"description":238,"draft":111,"extension":112,"keywords":107,"meta":239,"navigation":114,"noindex":111,"ogImage":107,"path":240,"seo":241,"seoDescription":107,"seoTitle":107,"stem":242,"tags":243,"updated":107,"__hash__":247},"blog\u002Fblog\u002Fai-fact-sheet-page.md","给 AI 准备一张产品事实页，比写十篇软文有用",{"type":8,"value":127,"toc":226},[128,131,134,137,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,217,220,223],[11,129,130],{},"2026 年 8 月我们给一个客户做了一张产品事实页，一页纸，不带任何营销语言。上线六周后，三个 AI 引擎在回答相关问题时引用了其中的段落。",[15,132,133],{"id":133},"事实页是什么",[11,135,136],{},"一页专门给机器读的页面，把产品的基本事实列清楚，不做说服。",[11,138,139],{},"内容包括：产品全名和所属公司、一句话定位、核心功能清单、不支持的场景、价格与计费方式、集成列表、客户规模区间、最近更新时间。",[11,141,142],{},"这页不需要漂亮，需要准确、结构清楚、能被单独摘出来。",[15,144,145],{"id":145},"为什么有用",[11,147,148],{},"AI 回答问题时需要一个可信的、原子化的事实来源。",[11,150,151],{},"你官网的产品页通常充满营销语言，一段话里塞五个形容词，机器很难提取事实。",[11,153,154],{},"评测站和论坛的信息更不可靠。事实页相当于给 AI 一个官方口径。",[15,156,157],{"id":157},"怎么写",[11,159,160],{},"用短句。一行只讲一件事，不要复合句。",[11,162,163],{},"用表格。功能、价格、集成三块做成表格，表头带单位，不要合并单元格。",[11,165,166],{},"每个数字带口径。比如\"支持 50 个成员\"要写清是免费版还是所有版本，\"99.9% 可用性\"要写清统计周期。",[11,168,169],{},"页面底部写更新日期。没有日期的信息，机器和人都不知道新不新。",[15,171,172],{"id":172},"放哪里",[11,174,175],{},"放在关于页下面，路径短一点，比如 \u002Fabout\u002Ffacts。",[11,177,178],{},"从产品页、定价页、文档首页都加一条内链过去。",[11,180,181],{},"加 Organization 和 SoftwareApplication 结构化数据，把产品名、公司、价格区间标清楚。",[15,183,184],{"id":184},"怎么维护",[11,186,187],{},"每季度更新一次，功能有增减或者价格调整时立刻改。",[11,189,190],{},"留一个变更记录，写清改了什么、什么时候改的。这个记录本身也是可引用的事实。",[11,192,193],{},"我们给客户的建议是把事实页写进产品发布的检查清单，和更新日志一起发。",[15,195,196],{"id":196},"一个常见的疑问",[11,198,199],{},"有人问，事实页会不会和产品页抢关键词。",[11,201,202],{},"不会。事实页面向的是具体问题，比如某个版本多少钱、支不支持某个集成，和产品页的主关键词不冲突。",[11,204,205],{},"我们的做法是事实页不做关键词优化，只求准确。它靠的是被引用，不是排名。",[15,207,208],{"id":208},"事实页和产品页的分工",[11,210,211],{},"产品页负责说服，事实页负责被引用。两个页面的写法完全不同。",[11,213,214],{},"我们通常把事实页放在关于页下面，产品页只加一条内链指过去，避免两个页面抢同一批词。",[15,216,86],{"id":86},[11,218,219],{},"事实页不是 SEO 技巧，是给所有渠道提供一份统一口径。",[11,221,222],{},"销售在用，客服在用，AI 也在用。它减少的是解释成本，不只是提高引用率。",[11,224,225],{},"一页纸的工作量，两三个小时。比写十篇软文便宜得多，也耐用得多。",{"title":97,"searchDepth":98,"depth":98,"links":227},[228,229,230,231,232,233,234,235],{"id":133,"depth":98,"text":133},{"id":145,"depth":98,"text":145},{"id":157,"depth":98,"text":157},{"id":172,"depth":98,"text":172},{"id":184,"depth":98,"text":184},{"id":196,"depth":98,"text":196},{"id":208,"depth":98,"text":208},{"id":86,"depth":98,"text":86},"SEO","2026-08-14","一页列清产品名、定位、功能边界、价格、集成和限制，上线六周后被三个引擎引用。这篇写事实页放什么、怎么写、放哪里、怎么维护，附一份字段清单。",{},"\u002Fblog\u002Fai-fact-sheet-page",{"title":125,"description":238},"blog\u002Fai-fact-sheet-page",[244,245,246],"GEO","事实页","内容结构","qEuO6NUhWbznqEeSKhNt9vHRUVGx9x00q5ia7alQLd0",{"id":249,"title":250,"author":6,"body":251,"canonical":107,"category":236,"cover":107,"date":316,"description":317,"draft":111,"extension":112,"keywords":107,"meta":318,"navigation":114,"noindex":111,"ogImage":107,"path":319,"seo":320,"seoDescription":107,"seoTitle":107,"stem":321,"tags":322,"updated":107,"__hash__":325},"blog\u002Fblog\u002Fcloud-migration-guide-seo.md","迁移指南是云服务最接近成交的内容",{"type":8,"value":252,"toc":310},[253,256,259,262,265,268,271,274,277,280,283,286,289,295,298,301,304,307],[11,254,255],{},"云服务的内容里，迁移指南是离成交最近的一类。搜“从 AWS 迁移到 XX”“数据库迁移 不停机”的人，已经在评估方案了。2025 年 9 月到 2026 年 7 月，我们给一个云厂商写了 8 篇迁移指南，带来 470 条企业线索，成单 11 个。",[15,257,258],{"id":258},"迁移词的结构",[11,260,261],{},"分三种。按源平台：“从 AWS 迁出”“从阿里云迁出”。按组件：“MySQL 迁移”“对象存储迁移”“K8s 集群迁移”。按约束：“不停机迁移”“零数据丢失迁移”“迁移成本对比”。",[11,263,264],{},"三种组合起来就是页面矩阵。我们优先做源平台加组件，比如“从 AWS RDS 迁移到 XX 的 MySQL”，意图最明确。",[15,266,267],{"id":267},"一篇迁移指南的骨架",[11,269,270],{},"第一步，评估。给一张对照表：源端资源、目标端对应产品、注意事项。这张表决定用户能不能继续读。",[11,272,273],{},"第二步，方案。至少给两条路径：停机窗口迁移和不停机双写。写清各自的前置条件、耗时、风险。",[11,275,276],{},"第三步，操作步骤。分阶段，每阶段有验证点。验证点写具体命令或指标，别写“确认无误”。",[11,278,279],{},"第四步，回滚。这段最容易被省略，其实是企业客户最先问的。写清回滚窗口、数据一致性怎么保证。",[11,281,282],{},"第五步，成本。迁移本身的工时、迁移期间的双份费用、以及迁移后每月的账单变化。给区间，别给单个数字。",[15,284,285],{"id":285},"一个差异化做法",[11,287,288],{},"我们每篇指南都带一个“迁移前后实测”小节，给出真实迁移的数据量、耗时、遇到的两个问题。这部分是销售讲不出来的，只有交付团队有。写进去之后，页面的平均停留时间从 2 分钟到 4 分半。",[11,290,291],{},[292,293,294],"strong",{},"内容怎么和销售配合",[11,296,297],{},"迁移指南单独存在没用，要和销售流程接上。我们的做法是给每篇指南配一个内部版本：多一段“这个客户的情况适合哪条路径”，销售跟进前先读一遍。这样内容和成单之间的链条是通的。",[11,299,300],{},"另外，客户在沟通中提到的问题，回来补进指南的常见问题部分。三个月下来，指南的问答区会变成一份真实的异议清单，比市场部闭门写的强。",[15,302,303],{"id":303},"转化设计",[11,305,306],{},"迁移指南的 CTA 不是“免费试用”，是“预约迁移评估”。这类用户要的是方案，不是账号。我们给客户做的评估表单只有四个字段，提交后由解决方案工程师跟进，转化率比普通试用高很多。",[11,308,309],{},"内容要定期更新，云产品改价、改规格、改限制，指南跟着改。我们在页面顶部标了版本号和更新月份，用户会看这个。",{"title":97,"searchDepth":98,"depth":98,"links":311},[312,313,314,315],{"id":258,"depth":98,"text":258},{"id":267,"depth":98,"text":267},{"id":285,"depth":98,"text":285},{"id":303,"depth":98,"text":303},"2026-08-16","搜“从 AWS 迁移到 XX”的人已经在做决策，内容只要回答得够具体，线索质量就很高。我们写了 8 篇迁移指南，一年带来 470 条企业线索，成单 11 个。",{},"\u002Fblog\u002Fcloud-migration-guide-seo",{"title":250,"description":317},"blog\u002Fcloud-migration-guide-seo",[323,324,108],"云迁移","采购意图","_oqYNXJIYIjRxWssy76kd_K-DIZFKYV8ovqTBx5kDNI",1794088102826]