[{"data":1,"prerenderedAt":453},["ShallowReactive",2],{"blog-organization-schema-fields":3,"blog-prev-organization-schema-fields":115,"blog-next-organization-schema-fields":212},{"id":4,"title":5,"author":6,"body":7,"canonical":99,"category":100,"cover":99,"date":101,"description":102,"draft":103,"extension":104,"keywords":99,"meta":105,"navigation":106,"noindex":103,"ogImage":99,"path":107,"seo":108,"seoDescription":99,"seoTitle":99,"stem":109,"tags":110,"updated":99,"__hash__":114},"blog\u002Fblog\u002Forganization-schema-fields.md","Organization 结构化数据：六个字段写对才有用","元析智能",{"type":8,"value":9,"toc":89},"minimark",[10,14,18,25,31,37,43,49,55,59,62,65,68,71,74,77,80,83,86],[11,12,13],"p",{},"Organization 是全站唯一的实体标记。写对了，能帮搜索引擎把品牌名、官网、社媒账号认成同一个实体；写错了，会制造矛盾信号，比不写还麻烦。这件事半小时能做完，但很多站拖着没做。",[15,16,17],"h2",{"id":17},"六个必填字段",[11,19,20,24],{},[21,22,23],"strong",{},"name","：和公司官方注册名或者对外统一名称一致。别写\"XX官网\"，别每个页面写不同的名字。",[11,26,27,30],{},[21,28,29],{},"url","：官网主域，带 https。",[11,32,33,36],{},[21,34,35],{},"logo","：可公开抓取的图片地址，宽高比接近 1:1，建议 112 像素以上。别用 base64 内嵌，别用需要登录的图床，别用已经下线的 CDN 路径。",[11,38,39,42],{},[21,40,41],{},"sameAs","：官方社媒、GitHub、LinkedIn、应用商店页面。只放真实存在的官方账号。放竞品页面或者山寨页面，是在给搜索引擎喂错误关联。",[11,44,45,48],{},[21,46,47],{},"address","：注册地址或办公地址，按结构化字段拆开写。",[11,50,51,54],{},[21,52,53],{},"contactPoint","：客服电话、邮箱、联系类型（技术支持、销售）。",[15,56,58],{"id":57},"_2026-年-4-月那次排查","2026 年 4 月那次排查",[11,60,61],{},"一个客户站首页的 Organization 里，logo 指向一个已经删除的 CDN 路径，404 了半年；sameAs 里有两个链接指向山寨页面，是运营从搜索结果里复制来的。修复后 GSC 里结构化数据报错清零，知识面板的信息也更新了——时间不由我们控制，但至少信号统一了。",[15,63,64],{"id":64},"三个常见错",[11,66,67],{},"把 Person 标成 Organization，作者页最容易犯；多个页面写不同的 Organization，比如每个产品页写自己；logo 用了带文字的横版图，尺寸太小，识别不出来。",[15,69,70],{"id":70},"验证方法",[11,72,73],{},"Rich Results Test 跑首页和关于页；GSC 的\"增强功能\"看有没有报错；再人工核对一遍标记里的名称、地址、电话和官网页面上写的是否一致。三处一致才算完成。",[15,75,76],{"id":76},"放在哪个页面",[11,78,79],{},"Organization 放在首页和关于页就够，全站每个页面都放也不会错，但没必要重复。如果公司有多个品牌或者多个独立产品线，可以给每个子品牌单独建 Organization，用 parentOrganization 关联。别把多个品牌混成一个，搜索引擎分不清。",[11,81,82],{},"还有一个细节：about 页、联系我们页上的信息要和标记完全一致，包括地址的写法。线上线下不一致，实体识别会打折。",[15,84,85],{"id":85},"立场",[11,87,88],{},"结构化数据里，Organization 是确定性最高、成本最低的一个。别追求标得多，先把这一个标对。做 GEO 的站尤其要重视，AI 引擎判断品牌实体时，这些字段是直接输入。",{"title":90,"searchDepth":91,"depth":91,"links":92},"",2,[93,94,95,96,97,98],{"id":17,"depth":91,"text":17},{"id":57,"depth":91,"text":58},{"id":64,"depth":91,"text":64},{"id":70,"depth":91,"text":70},{"id":76,"depth":91,"text":76},{"id":85,"depth":91,"text":85},null,"技术SEO","2026-07-20","Organization 标记容易被当成模板活，填错却会拖累全站。logo、sameAs、url、name、address、contactPoint 这六个字段我们逐个过，附一个 2026 年 4 月的排查记录。",false,"md",{},true,"\u002Fblog\u002Forganization-schema-fields",{"title":5,"description":102},"blog\u002Forganization-schema-fields",[111,112,113],"结构化数据","Organization","品牌","0N_aUuS-YY2B8tiqT06IgrY7REqgY18Pc9Vslpu1Myo",{"id":116,"title":117,"author":6,"body":118,"canonical":99,"category":200,"cover":99,"date":201,"description":202,"draft":103,"extension":104,"keywords":99,"meta":203,"navigation":106,"noindex":103,"ogImage":99,"path":204,"seo":205,"seoDescription":99,"seoTitle":99,"stem":206,"tags":207,"updated":99,"__hash__":211},"blog\u002Fblog\u002Fseo-project-scheduling.md","SEO 项目排期，前三个月别排满内容",{"type":8,"value":119,"toc":192},[120,123,126,129,132,135,138,141,144,147,150,153,156,159,162,165,168,171,174,177,180,183,186,189],[11,121,122],{},"2026 年 7 月我们接手一个延期三个月的项目，翻排期表发现第一个月排了 20 篇内容、加上技术修复和外链建设，全挤在一起。执行到第三周就卡住了。SEO 项目排期最常见的错误是把所有事排在同一时间段。",[15,124,125],{"id":125},"阶段要分开",[11,127,128],{},"第一个月做技术。收录、抓取、加载速度、结构化数据、内链结构。这些是地基，做完才能谈内容效果。",[11,130,131],{},"第二个月做内容基建。核心页面重写、产品页优化、文档结构整理。同时开始小批量内容测试，一周两篇，看收录和曝光。",[11,133,134],{},"第三个月开始放量。内容一周三到四篇，外链同步启动。",[11,136,137],{},"三个阶段有重叠但不能同时全开。同时开的结果是每件都做一半。",[15,139,140],{"id":140},"为什么前三个月别排满内容",[11,142,143],{},"新站的内容在头两个月基本看不到效果，排满了只会让客户在第 45 天问“为什么没效果”。",[11,145,146],{},"更重要的是，技术问题没修完就大量发内容，等于往漏水的桶里倒水。我们见过一个站，产品页全被 noindex 了还在发博客，发了 30 篇一篇都没收录。",[15,148,149],{"id":149},"验收节点怎么设",[11,151,152],{},"不按篇数设，按状态设。第一个月验收：核心页面全部可抓可收、加载速度进入合格区间、日志里蜘蛛抓取频次正常。",[11,154,155],{},"第二个月验收：核心词开始有曝光、落地页有内链、结构化数据无明显错误。",[11,157,158],{},"第三个月验收：内容开始有自然点击、转化路径跑通、周报数据能稳定产出。",[11,160,161],{},"每个节点都要有客户能自己验证的东西，别用“优化完成”“效果良好”这种词。",[15,163,164],{"id":164},"排期表要写清依赖",[11,166,167],{},"每条任务写三样：谁做、依赖谁、什么时候要。依赖客户的任务单独标出来，比如“等产品文档更新”“等开发排期”。",[11,169,170],{},"我们见过最常见的延期原因是等客户，而不是我们慢。把依赖写进排期表，延期的时候有据可查。",[15,172,173],{"id":173},"排期要留返工余量",[11,175,176],{},"每个阶段留一周缓冲。技术改动经常需要回滚重做，内容经常要返工，不留余量的排期表第一周就开始欠账。",[11,178,179],{},"我们现在的做法是 12 周的计划按 10 周排，剩下两周当缓冲。客户看到的还是 12 周，但我们心里有底。",[15,181,182],{"id":182},"一个排期模板",[11,184,185],{},"我们把项目分成 12 周，每周一张卡片，卡片上写这一周的三件主任务和两个备选。主任务必须完成，备选做不完顺延。",[11,187,188],{},"每周五和客户同步一次，只看三件事：完成了什么、卡在哪、下周改什么。",[11,190,191],{},"这个模板不复杂，但它强迫双方每周面对一次现实。排期表最怕的是写完就锁进抽屉，三个月后再翻出来对账。",{"title":90,"searchDepth":91,"depth":91,"links":193},[194,195,196,197,198,199],{"id":125,"depth":91,"text":125},{"id":140,"depth":91,"text":140},{"id":149,"depth":91,"text":149},{"id":164,"depth":91,"text":164},{"id":173,"depth":91,"text":173},{"id":182,"depth":91,"text":182},"行业观察","2026-07-19","排期表上第一个月就写满 20 篇，执行到第三周一定卡住。这篇写我们按阶段排期的做法：技术、内容、外链各占多少，以及验收节点怎么设，项目延期多半是排期结构的问题。",{},"\u002Fblog\u002Fseo-project-scheduling",{"title":117,"description":202},"blog\u002Fseo-project-scheduling",[208,209,210],"项目排期","SEO项目","交付管理","bo9R63-xBkZIWUB5Rbr0FLMgr7BjhsfOSk50voxJADw",{"id":213,"title":214,"author":6,"body":215,"canonical":99,"category":100,"cover":99,"date":443,"description":444,"draft":103,"extension":104,"keywords":99,"meta":445,"navigation":106,"noindex":103,"ogImage":99,"path":446,"seo":447,"seoDescription":99,"seoTitle":99,"stem":448,"tags":449,"updated":99,"__hash__":452},"blog\u002Fblog\u002Fsoftware-app-schema.md","SoftwareApplication 结构化数据：9 个站加完后的效果和坑",{"type":8,"value":216,"toc":434},[217,220,223,226,229,232,364,367,374,378,381,384,388,391,394,397,400,403,406,409,412,415,418,421,424,427,430],[11,218,219],{},"软件公司该加的 JSON-LD，不是 Article 和 FAQPage，而是 SoftwareApplication。2025 年 12 月到 2026 年 5 月我们给 9 个站加完，6 个出现富结果，3 个没有任何变化。差异不在代码，在页面是否真的\"像个产品\"。",[15,221,222],{"id":222},"先搞清楚它能带来什么",[11,224,225],{},"SoftwareApplication 告诉搜索引擎：这是一个软件产品，有名称、有价格、有评分、有适用平台。它可能让搜索结果里出现评分星星、价格区间，或者被归到软件类结果里。",[11,227,228],{},"它不是排名因素，别指望加了就涨排名。它的价值是提高点击率，以及在 AI 搜索里被准确识别为产品。",[15,230,231],{"id":231},"我们加的核心字段",[233,234,238],"pre",{"className":235,"code":236,"language":237,"meta":90,"style":90},"language-json shiki shiki-themes github-light github-dark","{\n  \"@context\": \"https:\u002F\u002Fschema.org\",\n  \"@type\": \"SoftwareApplication\",\n  \"name\": \"产品名\",\n  \"applicationCategory\": \"BusinessApplication\",\n  \"operatingSystem\": \"Web\",\n  \"offers\": {\"@type\": \"Offer\", \"price\": \"0\", \"priceCurrency\": \"CNY\"}\n}\n","json",[239,240,241,250,266,279,292,305,318,359],"code",{"__ignoreMap":90},[242,243,246],"span",{"class":244,"line":245},"line",1,[242,247,249],{"class":248},"sVt8B","{\n",[242,251,252,256,259,263],{"class":244,"line":91},[242,253,255],{"class":254},"sj4cs","  \"@context\"",[242,257,258],{"class":248},": ",[242,260,262],{"class":261},"sZZnC","\"https:\u002F\u002Fschema.org\"",[242,264,265],{"class":248},",\n",[242,267,269,272,274,277],{"class":244,"line":268},3,[242,270,271],{"class":254},"  \"@type\"",[242,273,258],{"class":248},[242,275,276],{"class":261},"\"SoftwareApplication\"",[242,278,265],{"class":248},[242,280,282,285,287,290],{"class":244,"line":281},4,[242,283,284],{"class":254},"  \"name\"",[242,286,258],{"class":248},[242,288,289],{"class":261},"\"产品名\"",[242,291,265],{"class":248},[242,293,295,298,300,303],{"class":244,"line":294},5,[242,296,297],{"class":254},"  \"applicationCategory\"",[242,299,258],{"class":248},[242,301,302],{"class":261},"\"BusinessApplication\"",[242,304,265],{"class":248},[242,306,308,311,313,316],{"class":244,"line":307},6,[242,309,310],{"class":254},"  \"operatingSystem\"",[242,312,258],{"class":248},[242,314,315],{"class":261},"\"Web\"",[242,317,265],{"class":248},[242,319,321,324,327,330,332,335,338,341,343,346,348,351,353,356],{"class":244,"line":320},7,[242,322,323],{"class":254},"  \"offers\"",[242,325,326],{"class":248},": {",[242,328,329],{"class":254},"\"@type\"",[242,331,258],{"class":248},[242,333,334],{"class":261},"\"Offer\"",[242,336,337],{"class":248},", ",[242,339,340],{"class":254},"\"price\"",[242,342,258],{"class":248},[242,344,345],{"class":261},"\"0\"",[242,347,337],{"class":248},[242,349,350],{"class":254},"\"priceCurrency\"",[242,352,258],{"class":248},[242,354,355],{"class":261},"\"CNY\"",[242,357,358],{"class":248},"}\n",[242,360,362],{"class":244,"line":361},8,[242,363,358],{"class":248},[11,365,366],{},"这是最小可用版本。再补 aggregateRating、featureList、screenshot、softwareVersion 会更完整。",[11,368,369,370,373],{},"关键点：",[239,371,372],{},"offers"," 里的价格必须和页面上显示的一致。不一致会被判无效，严重的会被手动处理。",[15,375,377],{"id":376},"_6-个出现富结果的站有什么共同点","6 个出现富结果的站有什么共同点",[11,379,380],{},"页面本身有清晰的产品信息：价格页、版本说明、适用平台、真实截图。结构化数据只是把这些信息翻译成机器格式。",[11,382,383],{},"结构化数据和页面内容对不上，是富结果不出现的头号原因。",[15,385,387],{"id":386},"_3-个没变化的站","3 个没变化的站",[11,389,390],{},"第一个，产品页只有一段介绍和一个\"联系我们\"，没有价格、没有版本、没有平台信息。数据填了，搜索引擎没东西可展示。",[11,392,393],{},"第二个，把 SoftwareApplication 加在了博客文章上，文章讲的是行业趋势，不是产品。",[11,395,396],{},"第三个，用 SaaS 的首页做产品页，介绍的是公司，不是软件。",[15,398,399],{"id":399},"三个容易写错的地方",[11,401,402],{},"第一，评分造假。没有真实评价就填 aggregateRating，被查到轻则不展示，重则整站结构化数据被降权。我们只建议有真实用户评价的站加。",[11,404,405],{},"第二，价格写成\"联系销售\"。这不是错误，但不会出现价格富结果。B2B 软件常见，接受这个结果就行。",[11,407,408],{},"第三，多个版本混在一个页面。免费版、付费版、企业版价格不同，要么用多个 Offer，要么拆页面。别在一个 SoftwareApplication 里塞三个不相关的价格。",[15,410,411],{"id":411},"什么情况下别加",[11,413,414],{},"产品还没上线、页面只有一个\"即将推出\"，别加。",[11,416,417],{},"公司官网的首页，别加。首页是公司介绍，不是产品页。",[11,419,420],{},"已经有成熟的产品页结构的站，加了收益也不大，优先级排在内容和内链之后。",[15,422,423],{"id":423},"判断",[11,425,426],{},"结构化数据的收益是\"锦上添花\"，不是\"雪中送炭\"。页面信息本身不完整，加再多 schema 也没用。",[11,428,429],{},"我们现在的顺序：先把产品页的价格、版本、平台、截图补齐，再加 JSON-LD。这个顺序反了，白忙。这个顺序我们改过三次，9 个站都按这个来。",[431,432,433],"style",{},"html pre.shiki code .sVt8B, html code.shiki .sVt8B{--shiki-default:#24292E;--shiki-dark:#E1E4E8}html pre.shiki code .sj4cs, html code.shiki .sj4cs{--shiki-default:#005CC5;--shiki-dark:#79B8FF}html pre.shiki code .sZZnC, html code.shiki .sZZnC{--shiki-default:#032F62;--shiki-dark:#9ECBFF}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}",{"title":90,"searchDepth":91,"depth":91,"links":435},[436,437,438,439,440,441,442],{"id":222,"depth":91,"text":222},{"id":231,"depth":91,"text":231},{"id":376,"depth":91,"text":377},{"id":386,"depth":91,"text":387},{"id":399,"depth":91,"text":399},{"id":411,"depth":91,"text":411},{"id":423,"depth":91,"text":423},"2026-07-21","软件公司该加的 JSON-LD，不是 Article 和 FAQPage，而是 SoftwareApplication。2025 年 12 月到 2026 年 5 月我们给 9 个站加完，6 个出现富结果，3 个没有任何变化。加什么字段、三种常见错误、什么情况别加，都在这篇。加完能看到效果的前提是页面信息本身完整，这点很多人忽略。",{},"\u002Fblog\u002Fsoftware-app-schema",{"title":214,"description":444},"blog\u002Fsoftware-app-schema",[111,450,451],"JSON-LD","富结果","FGz7yBJs6B85VGSxHmgipgN49_5JhspPCvD_J8bGbFc",1794088103626]