[{"data":1,"prerenderedAt":222},["ShallowReactive",2],{"site-settings":3,"$fM6QDJ8elsPy_lp3LqU6TYhOeeXGmC_VdSfpbVCTaBf0":26,"related-posts":50,"$fqnANZPlRYP2BOxji-qW08qAUKLJ3jRejgClPEOrqpvI":221},{"id":4,"site_name":5,"site_subtitle":6,"site_description":7,"author":8,"email":9,"github":10,"icp":10,"page_size":11,"enable_comment":12,"enable_rss":12,"updated_at":13,"site_icon":14,"site_og_image":15,"site_keywords":16,"site_og_image_width":24,"site_og_image_height":25},1,"LiteSite（轻站）","把你想做的网站说出来","LiteSite（轻站）探索自然语言驱动的零代码建站体验，展示响应式网站与前端原型的设计方向。","Admin","support@litesite.com",null,10,true,"2026-10-05T03:56:44.502+00:00","https:\u002F\u002Fnklbhnvyoggxghtaoizu.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fblog-images\u002F2026-10-05-1765bce7-01f1-4206-8d5d-6a717d17f206.png","https:\u002F\u002Fnklbhnvyoggxghtaoizu.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fblog-images\u002F2026-10-05-157c3c1d-2722-474c-860b-d3f38d6a674d.png",[17,18,19,20,21,22,23],"LiteSite","轻站","零代码建站","AI建站","响应式网站","前端原型","网站设计",1200,630,{"id":27,"slug":28,"title":29,"summary":30,"content":31,"status":32,"tags":33,"seo_keywords":40,"published_at":45,"updated_at":46,"category":47},14,"geo-business-understanding","GEO 从业务理解开始：把真实问题写成可引用的内容","做 GEO 之前，先弄清业务服务谁、用户在什么场景下提问、哪些证据能支持回答，再用真实问题和业务结果验证内容。","GEO（生成式引擎优化）常被理解为“让内容更容易出现在 AI 的回答里”。但如果只追逐提及次数，很容易写出看似完整、却回答不了客户真实疑问的页面。有效的 GEO 内容策略，应从业务理解开始：先确认服务对象和决策场景，再整理能被核查的事实，最后观察内容是否帮助用户迈出下一步。\n\n![GEO 业务理解流程：业务目标、用户问题、可信证据、页面验证](https:\u002F\u002Fnklbhnvyoggxghtaoizu.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fblog-images\u002F2026-10-05-0271637a-1a3f-4c29-9294-3d2b11c26ddc.png)\n\n*图：从业务目标、用户问题、可信证据到页面验证的 GEO 内容流程。*\n\n## 先定义业务问题，而不是先列关键词\n\n假设一家团队提供企业建站服务。“企业建站”是宽泛主题；真正需要回答的问题可能是：已有网站访问量不少，为什么咨询少？改版会不会影响原有搜索流量？建设周期受哪些因素影响？后续由谁维护？这些问题分别发生在认知、比较和采购阶段，需要的证据也不同。\n\n先和销售、客服、交付人员核对反复出现的问题，并查看站内搜索、咨询记录和已获授权的客户反馈。把问题按“用户是谁、处在什么阶段、要做什么决定”分类。不能从真实记录确认的内容，标注为假设，后续再验证。\n\n| 决策阶段 | 用户常问 | 页面应该提供 |\n| --- | --- | --- |\n| 发现问题 | 网站慢、咨询少，先改什么？ | 排查顺序与适用条件 |\n| 比较方案 | 自建、模板和定制如何选？ | 对比维度、限制与成本构成 |\n| 准备采购 | 项目多久交付、谁负责维护？ | 流程、职责、交付物与案例 |\n\n## 用事实支撑每一个关键回答\n\nAI 回答和传统搜索结果都可能引用公开网页，但是否被引用无法保证。我们能控制的是内容质量和可核查性：明确写出适用对象、前提、步骤、限制和更新时间；对数据标明来源与口径；案例说明背景、采取的动作和结果，避免只写“提升显著”。\n\n例如，“网站改版不会影响 SEO”过于绝对。更可靠的回答是：改版可能影响收录和排名，风险取决于 URL、内容、内部链接与技术实现；上线前应建立旧新 URL 对照、设置重定向，并在上线后持续检查索引和流量。这样的回答也更能帮助客户判断团队是否理解实际工作。\n\n产品能力、价格、案例和服务承诺必须由业务负责人核对。没有证据的结论宁可保留边界，也不要编造数字或客户评价。\n\n## 把答案组织成容易理解的页面\n\n一个页面围绕一个清晰任务展开：标题直接点明问题，开头给出简短结论，正文解释判断条件、操作步骤与例外情况，最后提供相关案例或下一步入口。使用明确的小标题、列表和对比表，让读者能快速扫描；相关页面之间建立有意义的内链。\n\n同时保留基础网站质量：页面可抓取，移动端可读，加载正常，标题和描述准确。GEO 并不替代这些工作，也没有一种标签或固定句式能保证 AI 引用。结构化数据应如实描述页面已有信息，而不是为争取展示而添加不实字段。\n\n## 同时看内容表现和业务结果\n\n可以定期用一组固定、贴近客户决策的问题检查不同 AI 产品给出的回答，记录是否提及品牌、引用了哪一页、表述是否准确。由于答案会随时间、上下文和产品变化，单次截图不能证明长期效果。\n\n还要看更接近业务的信号：高意向页面的访问与停留、咨询中被提到的问题、有效线索比例，以及销售是否反复把某篇文章发给客户。为每次内容更新记录日期、改动点和观察窗口，避免把所有增长都归因于 GEO。\n\nGEO 的起点是理解业务，终点仍是帮助人做决定。先写对一个真实问题、给足证据、观察反馈，再扩展到更多主题，比批量制造“AI 友好文章”更可持续。","published",[34,37],{"name":35,"slug":36},"建站","jianzhan",{"name":38,"slug":39},"GEO","geo",[38,41,42,43,44],"生成式引擎优化","业务理解","GEO内容策略","AI搜索优化","2026-10-05T03:33:52.358+00:00","2026-10-05T03:33:55.920653+00:00",{"id":48,"name":49,"slug":49},3,"技术笔记",{"items":51,"total":219,"page":4,"pageSize":220},[52,70,86,102,116,134,150,166,181,187,202],{"id":53,"slug":54,"title":55,"summary":56,"status":32,"tags":57,"seo_keywords":62,"published_at":68,"category":69},22,"llm-output-instability-hallucination","模型返回不稳定 \u002F 幻觉怎么办？","区分随机波动与事实幻觉，沿着样本评测、证据检索、结构校验、业务规则和人工回退建立可验证的大模型输出链路。",[58,60],{"name":59,"slug":59},"工程",{"name":61,"slug":61},"大模型",[63,64,65,66,67],"模型幻觉怎么办","大模型输出不稳定","LLM幻觉","RAG事实校验","模型评测","2026-10-05T04:17:13.315+00:00",{"id":48,"name":49,"slug":49},{"id":71,"slug":72,"title":73,"summary":74,"status":32,"tags":75,"seo_keywords":78,"published_at":84,"category":85},21,"llm-cost-budget-guardrails","大模型调用怎么控制成本？把预算控制放进请求链路","从请求准入、原子预留、真实用量结算到超支降级，设计一套能在并发与重试下运行的大模型调用预算控制链路。",[76,77],{"name":59,"slug":59},{"name":61,"slug":61},[79,80,81,82,83],"大模型调用成本控制","LLM预算管理","Token费用","模型调用限额","API成本监控","2026-10-05T04:14:07.621+00:00",{"id":48,"name":49,"slug":49},{"id":87,"slug":88,"title":89,"summary":90,"status":32,"tags":91,"seo_keywords":94,"published_at":100,"category":101},20,"llm-structured-output-reliability","结构化输出怎么保证模型按格式返回？","模型返回 JSON 不等于系统拿到可用数据。本文区分提示词、JSON 模式与 Schema 约束，说明如何用服务端校验、有限重试和业务规则构建可靠的结构化输出链路。",[92,93],{"name":59,"slug":59},{"name":61,"slug":61},[95,96,97,98,99],"大模型结构化输出","JSON Schema","模型按格式返回","LLM输出校验","约束解码","2026-10-05T04:10:02.025+00:00",{"id":48,"name":49,"slug":49},{"id":103,"slug":104,"title":105,"summary":106,"status":32,"tags":107,"seo_keywords":110,"published_at":114,"category":115},19,"geo-vs-seo-explained","理解 GEO 是什么？和 SEO 有什么区别？","GEO 是什么，和 SEO 有什么区别？从用户提问、内容呈现、优化动作与衡量指标四个角度讲清两者的关系，并给出一套适合建站团队的入门做法。",[108,109],{"name":35,"slug":36},{"name":38,"slug":39},[111,112,41,113,44],"GEO是什么","GEO和SEO的区别","SEO","2026-10-05T04:07:05.673+00:00",{"id":48,"name":49,"slug":49},{"id":117,"slug":118,"title":119,"summary":120,"status":32,"tags":121,"seo_keywords":126,"published_at":132,"category":133},18,"how-nuxt-ssr-works","Nuxt 的 SSR 是怎么做的？从请求、数据获取到 Hydration","沿着一次文章页请求，看 Nuxt 如何用 Nitro 接收请求、在服务端执行 useFetch 并生成 HTML，再由浏览器复用 payload 完成 Hydration。",[122,123],{"name":59,"slug":59},{"name":124,"slug":125},"Nuxt","nuxt",[127,128,129,130,131],"Nuxt SSR","Nuxt服务端渲染","Nuxt useFetch","Hydration","Nitro渲染流程","2026-10-05T03:55:36.035+00:00",{"id":48,"name":49,"slug":49},{"id":135,"slug":136,"title":137,"summary":138,"status":32,"tags":139,"seo_keywords":142,"published_at":148,"category":149},17,"llm-api-cost-control","大模型调用怎么控制成本？一笔账算清缓存、输出与重试","先按输入、输出和额外调用算清单次成本，再用缓存、模型路由、上下文裁剪和预算限额降本，并用可用答案质量守住效果。",[140,141],{"name":59,"slug":59},{"name":61,"slug":61},[143,144,145,146,147],"大模型调用成本","LLM API成本控制","Token费用计算","提示词缓存","模型路由","2026-10-05T03:49:26.666+00:00",{"id":48,"name":49,"slug":49},{"id":151,"slug":152,"title":153,"summary":154,"status":32,"tags":155,"seo_keywords":158,"published_at":164,"category":165},16,"geo-technical-pipeline-design","GEO 的技术链路你会怎么设计？","从问题池、证据库、可读页面到答案采样与质量回写，设计一条可维护的 GEO 技术链路，并明确外部 AI 系统的边界。",[156,157],{"name":59,"slug":59},{"name":38,"slug":39},[159,160,161,162,163],"GEO技术链路","GEO技术方案","生成式引擎优化架构","AI搜索内容工程","GEO监测","2026-10-05T03:44:34.947+00:00",{"id":48,"name":49,"slug":49},{"id":167,"slug":168,"title":169,"summary":170,"status":32,"tags":171,"seo_keywords":173,"published_at":179,"category":180},15,"geo-core-metrics-calculation","GEO 的核心指标你怎么理解？怎么算？","用同一组问题和明确的分母，算清 GEO 的品牌提及率、引用率、有效引用率、竞争提及份额与有效线索率。",[172],{"name":38,"slug":39},[174,175,176,177,178],"GEO核心指标","GEO指标怎么算","品牌提及率","AI引用率","生成式引擎优化效果","2026-10-05T03:40:09.175+00:00",{"id":48,"name":49,"slug":49},{"id":27,"slug":28,"title":29,"summary":30,"status":32,"tags":182,"seo_keywords":185,"published_at":45,"category":186},[183,184],{"name":35,"slug":36},{"name":38,"slug":39},[38,41,42,43,44],{"id":48,"name":49,"slug":49},{"id":188,"slug":189,"title":190,"summary":191,"status":32,"tags":192,"seo_keywords":194,"published_at":200,"category":201},13,"website-launch-checklist","网站上线前后检查清单：从可访问到可维护","一份实用的网站上线清单，逐项检查域名、HTTPS、手机体验、页面速度、SEO、表单、备份与上线后的监测。",[193],{"name":59,"slug":59},[195,196,197,198,199],"网站上线检查清单","网站上线","网站性能优化","网站SEO","网站维护","2026-10-05T03:24:44.969+00:00",{"id":48,"name":49,"slug":49},{"id":203,"slug":204,"title":205,"summary":206,"status":32,"tags":207,"seo_keywords":209,"published_at":215,"category":216},12,"website-planning-checklist","建站之前：用一张页面清单理清目标、结构与内容","从网站目标、访问者任务到页面清单和内容准备，用一套可执行的方法完成建站规划，避免边做边改。",[208],{"name":59,"slug":59},[210,211,212,213,214],"建站规划","网站信息架构","网站内容规划","页面清单","个人网站建设","2026-10-05T03:23:27.683+00:00",{"id":217,"name":218,"slug":218},7,"项目实践",11,100,[],1791174019855]