[Feature] Add side-by-side comparison for multiple URLs
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 30/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- react, typescript
- 领域
- frontend
调研方向
The issue does not identify files, tests, or entry points. Start by reading the existing metadata analysis and platform-preview flows to understand what a comparison would need to reuse. Done means users can compare multiple URLs side by side, see metadata and score differences, and export results as JSON or a shareable report.
由索引模型根据 Issue 内容生成。
描述
Problem
I’m frustrated when I need to compare metadata between two versions of a page, such as staging and production. Currently, I must open separate tabs and manually compare titles, descriptions, images, Open Graph tags, Twitter tags, and platform previews.
Proposed Solution
Add a comparison mode that allows users to enter two or more URLs and view their metadata side by side.
The comparison should:
- Display titles, descriptions, Open Graph tags, Twitter tags, canonical URLs, and images.
- Show platform previews next to each other.
- Highlight differences and missing metadata.
- Compare analyzer scores and grades.
- Indicate which URL has better or missing metadata.
- Allow the comparison results to be exported as JSON or a shareable report.
Alternatives Considered
Opening multiple browser tabs and comparing values manually is time-consuming and makes small differences easy to miss.
Using external comparison tools would require copying metadata manually and would not provide the same platform-specific previews or analyzer results. An integrated comparison view would keep the entire workflow inside OGCOPS.
Additional Context
This feature would be useful for:
- Comparing staging and production pages.
- Checking metadata before and after a redesign.
- Comparing old and new versions of a page.
- Auditing several pages for SEO and social-preview consistency.
A split-screen layout with matching fields aligned in rows would make differences easy to identify.
- 主要语言
- TypeScript
- 星标
- 8
- 派生
- 4
- 平均合并
- 8 小时 44 分钟
- 30 天内合并 PR
- 158
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
codercops/ogcops 的其他 Issue
-
[Bug] “Copy Recommended Meta Tags” generates an unusable placeholder image URL可能已有人在做 @CreatorguyS 于 5 天前认领。 未关闭bug enhancement
难度 2/5 1-3 小时 新手友好度 72/100
codercops/ogcops#378 · 4 条评论 ·
维护者通常 1 天内回复
-
[Bug] Clipboard fallback reports success even when copying fails可能已有人在做 @srikar-naidu 于 5 天前认领。 未关闭bug
codercops/ogcops#384 · 3 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
-
Preview checker: entity names like `&constructor;` decode to function source可能已有人在做 @amitsinha-cell 于 5 天前认领。 未关闭bug
codercops/ogcops#356 · 2 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
-
Add the Do and Don't tutorial template (`tutorial-do-dont`)可能已有人在做 @Ravindar-Amogh-Gummadavelly 于 5 天前认领。 未关闭good first issue templates
codercops/ogcops#355 · 2 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 35/100
codercops/ogcops#88 · 16 条评论 ·
维护者通常 1 天内回复
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
-
难度 2/5 1-3 小时 新手友好度 73/100
hugomrdias/playwright-test#753 ·
维护者通常 1 天内回复
-
Review view: Daily/Weekly Review header buttons use the app-wide toolbar control style可能已有人在做 @colherdesopa 今天认领。 未关闭
难度 1/5 1-3 小时 新手友好度 90/100
dongdongbh/Mindwtr#1515 ·
维护者通常 1 天内回复
-
pending-triage
难度 2/5 1-3 小时 新手友好度 70/100
kirodotdev/Kiro#12301 ·
-
难度 2/5 1-3 小时 新手友好度 83/100