feat(seo): /r/{job_id} 网页 title 与面包屑加入检测模型#2
Open
canarybyte wants to merge 1 commit into
Open
Conversation
之前同一中转站下所有报告共享同一个 title: 「www.fucheers.top OpenAI 中转站检测:91/100 存在风险 | Veridrop」 不同模型的报告(gpt-5.5 vs gpt-5.4-mini vs gpt-4o)title 一字不差, Google 直接当成重复页面去重,长尾流量(「XX 站测 gpt-5.5 怎么样」) 全部 sink 到一个 canonical 上,索引面缩成一份。 改动: - web/server.py _seo_meta_for_report:title 模板插入 target_model 「{domain} OpenAI 中转站 gpt-5.5 检测:91/100 存在风险 | Veridrop」 无 model 时退回原文,避免出现 "中转站 检测" 双空格痕迹 - web/templates/result.html 面包屑末尾段: 从「报告 #{job_id}」改为「{target_model}」 没有 target_model 时仍回退到「报告 #{job_id}」 效果: - 每份报告 title 唯一,Google 视为独立 indexable page - 面包屑文字在跨报告导航时也能立刻看出测的是哪个模型 - 报告分享卡片(og_title 同 seo_title)也直接带模型名 测试:tests/test_seo_meta.py 5 个用例覆盖: - 标题含 model - 空 model 回退不留空格痕迹 - 同域名不同 model 标题相互区分(SEO 反 dedupe 核心断言) - 长 dated snapshot 不超 155 字符 - 描述仍提及 model(防回归)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
背景
每份 `/r/{job_id}` 报告页都是公开 indexable landing page,但当前同一中转站下所有报告共享一个 title:
不同模型的报告(`gpt-5.5` / `gpt-5.4-mini` / `gpt-4o`)title 一字不差,Google 直接判定为重复页去重 → 长尾搜索(「XX 站测 gpt-5.5 怎么样」)全部 sink 到一个 canonical url,索引面塌成一份。
改动
1. Title 注入模型(`web/server.py` `_seo_meta_for_report`)
无 model 的边界情况(legacy 报告 / probe 失败)保留原模板,避免出现 "中转站 检测" 双空格痕迹。
2. 面包屑末尾段用模型名(`web/templates/result.html`)
没有 `target_model` 时仍回退到 `报告 #{job_id}`,跟旧报告兼容。
效果
测试
`tests/test_seo_meta.py` 新增 5 个用例:
完整 248/248 通过。
部署
本 PR 跟 #1 互不冲突,合并顺序无所谓。