[{"data":1,"prerenderedAt":726},["ShallowReactive",2],{"blog-content-chunking-for-ai":3,"blog-prev-content-chunking-for-ai":140,"blog-next-content-chunking-for-ai":662},{"id":4,"title":5,"author":6,"body":7,"canonical":124,"category":125,"cover":124,"date":126,"description":127,"draft":128,"extension":129,"keywords":124,"meta":130,"navigation":131,"noindex":128,"ogImage":124,"path":132,"seo":133,"seoDescription":124,"seoTitle":124,"stem":134,"tags":135,"updated":124,"__hash__":139},"blog\u002Fblog\u002Fcontent-chunking-for-ai.md","内容分块怎么做：AI 按块抓取，先弄清你的块边界","元析智能",{"type":8,"value":9,"toc":115},"minimark",[10,14,18,21,24,27,30,33,37,40,43,50,56,62,65,68,71,90,94,97,100,103,106,109,112],[11,12,13],"p",{},"AI 抓内容不是整页吞，是切块。2026 年 1 月我们把 40 个客户页面手工切了一遍，按语义切成\"能独立回答一个问题\"的单元，结果 62% 的块跨了主题。这就是很多页面明明写得好却拿不到引用的原因。",[15,16,17],"h2",{"id":17},"块是怎么切出来的",[11,19,20],{},"三种切法，引擎会混用。",[11,22,23],{},"第一种按标题切。一个 H2 到下一个 H2 之间算一块，这是最常用也最符合直觉的。",[11,25,26],{},"第二种按长度切。网页文本太长时，会按固定 token 数开窗，可能一刀切在句子中间。",[11,28,29],{},"第三种按语义相似度切。相邻句子讲同一件事就归一块，话题跳了就在那里断开。",[11,31,32],{},"三种混着来，意味着你的页面结构越乱，切出来的块越不可控。",[15,34,36],{"id":35},"_62-跨主题是怎么数出来的","62% 跨主题是怎么数出来的",[11,38,39],{},"方法很笨：40 个页面，逐段读，把\"这一段讲什么\"写成一句话，然后看相邻段落能不能归进同一块。归不进去就是跨主题。",[11,41,42],{},"跨主题的典型形态有三种：",[11,44,45,49],{},[46,47,48],"strong",{},"一个 H2 下面讲两件事。"," 比如\"性能与安全\"下面，先讲延迟再讲加密。标题已经混了，块必然混。",[11,51,52,55],{},[46,53,54],{},"段落中间换主语。"," 前半段讲产品功能，后半段突然讲客户案例。",[11,57,58,61],{},[46,59,60],{},"表格和正文混排。"," 表格前后没有一句说明这张表在回答什么，引擎拿到表格不知道为什么看它。",[15,63,64],{"id":64},"怎么让边界清楚",[11,66,67],{},"一条规则：一个 H2 覆盖一个完整问题，H2 下面第一段回答它，后面几段展开。",[11,69,70],{},"具体到操作：",[72,73,74,78,81,84,87],"ul",{},[75,76,77],"li",{},"H2 标题写成问题或判断，别写成名词。写\"跨区域同步的延迟是多少\"，不写\"性能表现\"。",[75,79,80],{},"每段只讲一件事，段首句是这句话的结论。",[75,82,83],{},"段落长度 150 到 400 字。太短没信息，太长一定混主题。",[75,85,86],{},"表格前面加一句\"这张表对比了 X 和 Y 在 5 个维度的差异\"，让表格有自己的上下文。",[75,88,89],{},"别用加粗当小标题。视觉上是标题，结构上还是段落，切块时不会被识别为边界。",[15,91,93],{"id":92},"一个-before-和-after","一个 before 和 after",[11,95,96],{},"改之前，一个定价页的结构是：H2\"灵活定价\"，下面一段讲理念，一段讲三个档位，一张表，一段讲企业版，一段讲 FAQ 链接。整页被切成 2 块，两块都说不清主题。",[11,98,99],{},"改之后：H2\"三档定价分别适合什么规模\"，一段结论加一张表；H2\"企业版怎么定制\"，一段说明；H2\"常见计费问题\"，5 条问答。同一篇文字，切成 4 块，每块都能独立回答一个问题。",[11,101,102],{},"改完 5 周，这页在 AI 回答里被挂的次数从 1 次到 6 次。",[15,104,105],{"id":105},"块多大合适",[11,107,108],{},"我们现在的标准是 150 到 400 字。低于 150 字，块里没有足够信息支撑一个判断；高于 400 字，大部分会跨主题。",[11,110,111],{},"这个区间不是定理，是我们拿 40 个页面手切之后定的经验值。你自己数一遍就知道，超过 400 字的段落，八成能拆成两件事。",[11,113,114],{},"写完一段，问一句：这段能不能单独被拿走回答一个问题？能，就是好块。",{"title":116,"searchDepth":117,"depth":117,"links":118},"",2,[119,120,121,122,123],{"id":17,"depth":117,"text":17},{"id":35,"depth":117,"text":36},{"id":64,"depth":117,"text":64},{"id":92,"depth":117,"text":93},{"id":105,"depth":117,"text":105},null,"GEO","2026-01-13","手切 40 个页面之后发现，62% 的内容块跨了主题。AI 抓到的块主题混杂，就不敢引用。块边界由 H2 决定，一段不超过 400 字。",false,"md",{},true,"\u002Fblog\u002Fcontent-chunking-for-ai",{"title":5,"description":127},"blog\u002Fcontent-chunking-for-ai",[136,125,137,138],"内容分块","内容结构","AI抓取","TRZJ0p5qakPwinHdwyJyA5xMKI_zi77NpnJk0zK-NNQ",{"id":141,"title":142,"author":6,"body":143,"canonical":124,"category":649,"cover":124,"date":650,"description":651,"draft":128,"extension":129,"keywords":124,"meta":652,"navigation":131,"noindex":128,"ogImage":124,"path":653,"seo":654,"seoDescription":124,"seoTitle":124,"stem":655,"tags":656,"updated":124,"__hash__":661},"blog\u002Fblog\u002Fengineering-software-seo.md","工程设计软件的 SEO 痛点:图片和 PDF 抓不到怎么办",{"type":8,"value":144,"toc":639},[145,148,151,154,183,186,189,192,195,200,203,214,217,222,225,235,243,246,251,254,259,262,267,270,281,285,288,293,307,312,326,331,358,363,374,377,380,383,409,412,417,428,433,444,449,460,465,476,482,486,489,494,497,508,511,514,540,545,559,562,566,571,574,579,582,587,590,595,598,601,604,630,633,636],[11,146,147],{},"给工程设计软件(CAD、BIM、仿真、PLM)做 SEO,最头疼的问题:产品页全是图片和 PDF,搜索引擎抓不到内容。排名起不来不是内容差,是内容根本没被索引。这篇文章写我们做工程软件 SEO 的方法,重点解决图片和 PDF 抓取问题。",[15,149,150],{"id":150},"技术债的根因",[11,152,153],{},"为什么工程软件的站全是图片和 PDF?根因有几层:",[72,155,156,165,171,177],{},[75,157,158,161,164],{},[46,159,160],{},"产品截图多",[162,163],"cad",{}," 这种软件,功能描述再多不如一张截图直观。市场部图省事,直接放图",[75,166,167,170],{},[46,168,169],{},"行业习惯",":工程行业习惯看 PDF 白皮书、案例手册,网页文字反而被认为\"不正式\"",[75,172,173,176],{},[46,174,175],{},"历史包袱",":很多工程软件的站是 5-10 年前做的,当时前端能力弱,内容用图片实现简单",[75,178,179,182],{},[46,180,181],{},"设计师主导",":网站外包给设计师做,设计师不懂 SEO,只关心视觉",[11,184,185],{},"结果就是:首页一个 hero 大图,产品页几张功能截图,案例页一份 PDF 下载。Google 和百度爬完,索引里只有几个 title 和 meta description,正文内容为 0。",[11,187,188],{},"我们做过一个 BIM 软件客户的诊断,全站 87 个页面,可索引的文字内容平均每页 120 字(主要是导航和 footer),产品功能描述全在图片里。这种站做 SEO,等于在沙漠里种树。",[15,190,191],{"id":191},"如何把图片内容文本化",[11,193,194],{},"图片内容文本化是工程软件 SEO 的第一步,也是最关键的一步。具体怎么做:",[11,196,197],{},[46,198,199],{},"1. 功能截图配文字说明",[11,201,202],{},"每张功能截图下方,必须有文字说明:",[72,204,205,208,211],{},[75,206,207],{},"这张图展示什么功能",[75,209,210],{},"这个功能解决什么问题",[75,212,213],{},"关键操作步骤(用文字描述)",[11,215,216],{},"不要只放图配一句\"图:XX 功能界面\"。Google 看不到图里的内容,只看得到这句 caption。Caption 要当 SEO 文案写。",[11,218,219],{},[46,220,221],{},"2. 用 alt 属性,但要写对",[11,223,224],{},"alt 不是关键词堆砌的地方。alt 要描述图片内容,自然带关键词。",[11,226,227,230,231],{},[46,228,229],{},"不好",":",[232,233,234],"code",{},"\u003Cimg alt=\"CAD 软件 CAD 工具 制图软件\">",[11,236,237,230,240],{},[46,238,239],{},"好",[232,241,242],{},"\u003Cimg alt=\"XX CAD 软件的参数化建模界面,左侧为零件树,右侧为属性面板\">",[11,244,245],{},"后者既描述了图片,又包含用户可能搜的\"参数化建模\"等词。",[11,247,248],{},[46,249,250],{},"3. 把图里的关键信息提取成文字",[11,252,253],{},"如果截图里有数据、参数、操作步骤,把这些提取成文字段落或列表,放在图片旁边。这样既方便用户,也方便搜索引擎。",[11,255,256],{},[46,257,258],{},"4. 用 SVG 而非位图",[11,260,261],{},"流程图、架构图、示意图,用 SVG(矢量图)。SVG 的文本内容可以被搜索引擎抓到。如果用 PNG\u002FJPG,内容完全不可见。",[11,263,264],{},[46,265,266],{},"5. 视频加字幕和文本版",[11,268,269],{},"工程软件经常用视频展示功能。视频内容搜索引擎抓不到。补救方法:",[72,271,272,275,278],{},[75,273,274],{},"视频配字幕文件(.srt)",[75,276,277],{},"视频下方放文字版内容(操作步骤、关键参数)",[75,279,280],{},"视频时长、章节标题用文字列出",[15,282,284],{"id":283},"pdf-该不该保留怎么处理","PDF 该不该保留、怎么处理",[11,286,287],{},"PDF 是工程软件站的重灾区。市场部爱发 PDF 白皮书,SEO 角度看,PDF 是地雷。",[11,289,290,230],{},[46,291,292],{},"问题",[72,294,295,298,301,304],{},[75,296,297],{},"PDF 和网页内容重复,Google 会判 duplicate content",[75,299,300],{},"PDF 没有内链,权重不传递",[75,302,303],{},"PDF 不能更新,过时内容还在被索引",[75,305,306],{},"PDF 的 title 和 URL 经常不规范",[11,308,309,230],{},[46,310,311],{},"该不该保留",[72,313,314,320],{},[75,315,316,319],{},[46,317,318],{},"保留",":确实需要下载的文档(产品规格书、技术手册、认证证书)",[75,321,322,325],{},[46,323,324],{},"不保留",":可以做成网页的内容(白皮书、案例介绍、产品对比)",[11,327,328,230],{},[46,329,330],{},"怎么处理保留的 PDF",[332,333,334,340,346,352],"ol",{},[75,335,336,339],{},[46,337,338],{},"PDF 的 title 单独优化",":不要用\"产品白皮书.pdf\",改成\"XX CAD 软件技术白皮书 - 参数化建模与装配设计\"",[75,341,342,345],{},[46,343,344],{},"PDF 加 canonical",":指向对应的网页版,避免 duplicate",[75,347,348,351],{},[46,349,350],{},"PDF 加内链",":在 PDF 里加回到官网相关页面的链接",[75,353,354,357],{},[46,355,356],{},"PDF 旁边的网页要有文字版",":不要让 PDF 成为唯一内容载体",[11,359,360,230],{},[46,361,362],{},"处理不保留的 PDF",[332,364,365,368,371],{},[75,366,367],{},"把 PDF 内容拆解成网页文章",[75,369,370],{},"用 301 重定向把旧 PDF URL 导到新网页",[75,372,373],{},"在 robots.txt 里 disallow 旧 PDF 路径(可选,看情况)",[11,375,376],{},"我们做过一个仿真软件客户,把 12 份 PDF 白皮书转成网页内容,3 个月后自然流量涨 2.3 倍。原因不只是 PDF 转网页,是内容终于被索引了。",[15,378,379],{"id":379},"工程软件的采购决策路径和搜索意图",[11,381,382],{},"工程软件的采购决策路径长,涉及多个角色:",[72,384,385,391,397,403],{},[75,386,387,390],{},[46,388,389],{},"工程师\u002F设计师",":用产品,提需求,搜技术细节和功能对比",[75,392,393,396],{},[46,394,395],{},"技术主管\u002F经理",":做技术选型,搜评测和案例",[75,398,399,402],{},[46,400,401],{},"采购\u002FIT",":走流程,搜价格和合规",[75,404,405,408],{},[46,406,407],{},"决策层(CIO\u002FCTO)",":签字,搜行业报告和 ROI",[11,410,411],{},"不同角色搜索意图不一样,内容要分层:",[11,413,414,230],{},[46,415,416],{},"工程师层(技术细节)",[72,418,419,422,425],{},[75,420,421],{},"关键词:\"参数化建模\"\"有限元分析\"\"BIM 协同\"",[75,423,424],{},"内容:功能文档、操作教程、技术博客",[75,426,427],{},"长尾:\"如何用 XX 软件做参数化建模\"",[11,429,430,230],{},[46,431,432],{},"技术主管层(选型对比)",[72,434,435,438,441],{},[75,436,437],{},"关键词:\"CAD 软件对比\"\"BIM 软件选型\"",[75,439,440],{},"内容:对比文章、评测、行业分析",[75,442,443],{},"长尾:\"SolidWorks vs Inventor 对比\"",[11,445,446,230],{},[46,447,448],{},"采购层(商业信息)",[72,450,451,454,457],{},[75,452,453],{},"关键词:\"CAD 软件价格\"\"PLM 系统报价\"",[75,455,456],{},"内容:定价页、采购指南、合规文档",[75,458,459],{},"长尾:\"中小企业 CAD 软件采购指南\"",[11,461,462,230],{},[46,463,464],{},"决策层(行业趋势)",[72,466,467,470,473],{},[75,468,469],{},"关键词:\"制造业数字化转型\"\"PLM 行业报告\"",[75,471,472],{},"内容:行业报告、白皮书、案例研究",[75,474,475],{},"长尾:\"2026 年制造业 PLM 选型趋势\"",[11,477,478,481],{},[46,479,480],{},"注意",":工程师层流量最大,转化周期最长;采购层流量小,转化最快。SEO 要全层覆盖,不能只做一层。",[15,483,485],{"id":484},"长尾词策略行业-功能-场景","长尾词策略(行业 + 功能 + 场景)",[11,487,488],{},"工程软件的核心商业词(如\"CAD 软件\")竞争激烈,大厂占着位置,短期打不动。我们的策略是做长尾词:",[11,490,491],{},[46,492,493],{},"公式:行业 + 功能 + 场景",[11,495,496],{},"例如:",[72,498,499,502,505],{},[75,500,501],{},"制造业 + 参数化建模 + 装配设计",[75,503,504],{},"建筑设计 + BIM 协同 + 多人协作",[75,506,507],{},"汽车行业 + 仿真分析 + 碰撞测试",[11,509,510],{},"这种长尾词搜索量小(每月几十到几百),但意图极其明确,转化率高。一个客户做\"汽车行业碰撞仿真软件\",这个词月搜索量 80,但 6 个月带来 7 个高质量线索,成交 2 单。",[11,512,513],{},"长尾词的内容做法:",[332,515,516,522,528,534],{},[75,517,518,521],{},[46,519,520],{},"每个长尾词一个页面",":不要堆在一个页面",[75,523,524,527],{},[46,525,526],{},"页面结构化",":行业背景 → 功能介绍 → 场景案例 → 我们的方案",[75,529,530,533],{},[46,531,532],{},"加场景案例",":具体到行业、公司类型、应用场景",[75,535,536,539],{},[46,537,538],{},"配技术参数表",":工程行业的用户爱看参数表",[11,541,542,230],{},[46,543,544],{},"挖词工具",[72,546,547,550,553,556],{},[75,548,549],{},"5118(国内)",[75,551,552],{},"Google Keyword Planner(海外)",[75,554,555],{},"竞品分析(看竞品在排什么词)",[75,557,558],{},"行业论坛和社区(工程师在问什么)",[11,560,561],{},"工程软件的长尾词经常不出现在关键词工具里(搜索量太小)。这种词靠经验挖,靠行业 know-how。我们做工程软件客户时,挖词有 40% 靠和客户工程师访谈,不是靠工具。",[15,563,565],{"id":564},"工程软件-seo-的几个特殊点","工程软件 SEO 的几个特殊点",[11,567,568],{},[46,569,570],{},"1. 行业垂直社区很重要",[11,572,573],{},"工程行业的垂直社区(如 CAD 论坛、BIM 论坛、仿真 365)权重高,用户多。在这些社区做内容部署,效果比通用平台好。",[11,575,576],{},[46,577,578],{},"2. 行业展会和 SEO 联动",[11,580,581],{},"工程行业展会多(汉诺威工业博览会、CES、工博会)。展会前后的搜索量会涨,提前 2-3 个月做展会相关内容,截流。",[11,583,584],{},[46,585,586],{},"3. 案例研究的 SEO 价值",[11,588,589],{},"工程软件的客户案例比功能介绍有用。具体客户(行业、规模、用了什么功能、解决了什么问题)是高价值内容。脱敏也行,但要有数据细节。",[11,591,592],{},[46,593,594],{},"4. 多语言策略",[11,596,597],{},"工程软件经常多语言(德语、日语、英语、中文)。不同语言的工程市场习惯不同,内容要本地化,不要翻译。",[15,599,600],{"id":600},"我们不接的工程软件",[11,602,603],{},"不是所有工程软件都适合做 SEO。我们不接:",[72,605,606,612,618,624],{},[75,607,608,611],{},[46,609,610],{},"产品页全是图片不愿改的",":技术债不解决,SEO 做不出来",[75,613,614,617],{},[46,615,616],{},"PDF 不愿转网页的",":内容不可索引,无解",[75,619,620,623],{},[46,621,622],{},"没有技术文档的",":内容基础没有,SEO 无从下手",[75,625,626,629],{},[46,627,628],{},"想 1 个月出效果的",":工程软件 SEO 周期 6 个月起步",[15,631,632],{"id":632},"总结",[11,634,635],{},"工程软件 SEO 的核心问题:图片和 PDF 抓不到。解决方法:图片文本化(alt、文字说明、SVG)、PDF 区分保留和处理、内容分层(工程师\u002F技术主管\u002F采购\u002F决策层)、长尾词(行业+功能+场景)。工程行业 SEO 周期长,但一旦起来,流量稳定转化高。",[11,637,638],{},"如果你做工程软件,想知道你的站有多少内容搜索引擎抓不到,联系我们做个免费诊断。",{"title":116,"searchDepth":117,"depth":117,"links":640},[641,642,643,644,645,646,647,648],{"id":150,"depth":117,"text":150},{"id":191,"depth":117,"text":191},{"id":283,"depth":117,"text":284},{"id":379,"depth":117,"text":379},{"id":484,"depth":117,"text":485},{"id":564,"depth":117,"text":565},{"id":600,"depth":117,"text":600},{"id":632,"depth":117,"text":632},"SEO","2026-01-12","CAD、BIM、仿真、PLM 这类工程软件的产品页多是图片和 PDF,搜索引擎抓不到内容。技术债根因、图片文本化、PDF 处理、采购决策路径、长尾词策略,我们做工程软件 SEO 的方法。",{},"\u002Fblog\u002Fengineering-software-seo",{"title":142,"description":651},"blog\u002Fengineering-software-seo",[657,658,659,660],"工程软件SEO","CAD","BIM","技术SEO","EkimRxA2z1tUDSzWkEyf4LT-DnjRpxj8vovdndqnYKQ",{"id":663,"title":664,"author":6,"body":665,"canonical":124,"category":649,"cover":124,"date":715,"description":716,"draft":128,"extension":129,"keywords":124,"meta":717,"navigation":131,"noindex":128,"ogImage":124,"path":718,"seo":719,"seoDescription":124,"seoTitle":124,"stem":720,"tags":721,"updated":124,"__hash__":725},"blog\u002Fblog\u002Fbrand-search-zero-to-forty.md","品牌词从查无此名到日均 40 次，我们做了五个月",{"type":8,"value":666,"toc":710},[667,670,674,677,680,683,686,689,692,695,698,701,704,707],[11,668,669],{},"品牌搜索从无到有，靠的不是投放，是让\"别人提到你\"这件事持续发生。2025 年 9 月接手这个客户时，搜公司全称第一页只有 3 条结果：官网、两个目录页，百度指数查不到这个词，日均品牌搜索不到 5 次。",[15,671,673],{"id":672},"起点先承认基础是空的","起点：先承认基础是空的",[11,675,676],{},"这个客户做数据工具，产品不差，客户有 200 多家，但网上几乎找不到痕迹。官网博客从 2023 年之后没更新，关于页只有一段话，作者页没有。搜产品名出来的结果里，有两条是竞品的对比文章，把他写成了\"备选\"。",[11,678,679],{},"我们先做了一次盘点：品牌名在网上的写法有 7 种，包括英文名缩写、两个错别字、带不带\"科技\"后缀。这 7 种写法分散在不同平台，搜索引擎根本对不上是同一家公司。改写法这件事听着琐碎，但它是所有后续动作的前提，不统一的品牌名，做多少内容都是散的。",[11,681,682],{},"盘点还有个副产品：我们发现有两个目录页把客户的成立年份写错了，一个写 2015，一个写 2018，实际是 2016。这种错误在搜索结果里会直接削弱可信度，改起来却只要十分钟。",[15,684,685],{"id":685},"五个月的时间线",[11,687,688],{},"9 月做基础。把 7 种写法收敛成 1 种，全平台统一；重写关于页，补公司地址、团队人数、服务客户数；开作者页，写清楚 3 个署名人各自负责什么；把 8 个主要目录的资料补齐。",[11,690,691],{},"10 月到 11 月做内容。写了 4 篇客户案例，每篇带具体数字，比如某客户对账时间从 3 天缩到 4 小时。同时在知乎回答了 3 个行业问题，GitHub 上把他们开源的 SDK 的 README 重新写了一遍。",[11,693,694],{},"12 月做了一次行业媒体投稿，中了一篇。1 月把他们产品后台的脱敏数据整理成一份小型报告，发在官网上，被两个行业公众号转载。",[15,696,697],{"id":697},"结果和能复用的判断",[11,699,700],{},"五个月后的数据：日均品牌搜索从不到 5 次到 40 次左右；GSC 里品牌词月点击从 60 涨到 220；搜公司名第一页有 7 条自有或第三方内容。",[11,702,703],{},"这五个月我们没买量、没刷指数、没买榜单。唯一花出去的钱是一篇媒体稿的编辑费。",[11,705,706],{},"有个细节值得说：前两个月数据几乎没动，客户在 11 月问过一次\"是不是没用\"。转机出现在 12 月，先是知乎的一个回答开始有排名，接着媒体的稿子被收录，品牌词搜索才明显起来。这类事有延迟，前面几个月的动作是给后面铺路。",[11,708,709],{},"品牌搜索是\"被别人看见\"的副产物，买不到。能买到的只有曝光位，但用户记住你，靠的是他在不同地方反复看到同一家公司，而且每次看到的内容都对得上。",{"title":116,"searchDepth":117,"depth":117,"links":711},[712,713,714],{"id":672,"depth":117,"text":673},{"id":685,"depth":117,"text":685},{"id":697,"depth":117,"text":697},"2026-01-14","一个 B2B 数据工具，2025 年 9 月开始补品牌信号，此前搜公司名只有 3 条结果。五个月后日均品牌搜索 40 次，第一页有 7 条自有或第三方内容。这篇按时间线复盘每一步。",{},"\u002Fblog\u002Fbrand-search-zero-to-forty",{"title":664,"description":716},"blog\u002Fbrand-search-zero-to-forty",[722,723,724],"品牌搜索","复盘","B2B软件","il16jfNsUPP5IxDHSDED1_fU3h1jkAQJBAwtev90APQ",1794088109262]