你会建立什么
这篇教学会示范如何用 Cursor Cloud Agents 做 SEO/GEO pull request review，但不给 agent 完全自主权。第一个有用 workflow 是 comment-only：cloud agent review branch 或 PR、找出风险，并且只有在你核准 specific findings 后，才建议小 patch。
你会建立：
.cursor/
rules/
seo-geo-pr-review.mdc
seo-geo/
pr-review/
checklist.md
review-prompt.md
approved-fixes.md
图说：Cloud Agent 应先做 findings-only review，不应在未核准时 commit 或改档。
这个 workflow 适合 review 会碰 metadata helpers、schema、robots rules、sitemap output、internal links、page templates、localization、analytics 或 large content batches 的 branches。
步骤 1：建立 PR review rule
mkdir -p .cursor/rules seo-geo/pr-review
cat > .cursor/rules/seo-geo-pr-review.mdc <<'EOF2'
---
description: SEO/GEO pull request review policy
globs:
- "src/**"
- "app/**"
- "pages/**"
- "content/**"
- "public/robots.txt"
- "**/*sitemap*"
- "**/*schema*"
- "**/*seo*"
- "**/*metadata*"
alwaysApply: false
---
For SEO/GEO PR reviews:
- review before patching
- return findings first, ordered by severity
- include file references and verification steps
- do not commit changes unless specific findings are approved
- treat robots, noindex, sitemap, canonical, redirects, schema, analytics, localization, and shared templates as high risk
- do not invent proof, customer names, rankings, statistics, or claims
- do not publish, deploy, submit URLs, or change secrets
EOF2
如果你的 Cursor plan 透过 UI 储存 rules，就把这段贴成 project rule。
步骤 2：建立 review checklist
cat > seo-geo/pr-review/checklist.md <<'EOF2'
# SEO/GEO PR Review Checklist
Review these risks:
- title, meta description, canonical, Open Graph
- robots, noindex, sitemap, redirects, route changes
- schema / JSON-LD validity and unsupported claims
- internal links, breadcrumbs, navigation
- localization, hreflang, locale canonicals
- template changes affecting many URLs
- content that is too generic for AI answer extraction
- analytics / GTM / GA4 changes
- build, lint, tests, preview, crawl validation
Severity:
- Critical: can block crawling/indexing or break many pages
- High: likely SEO/GEO regression before merge
- Medium: should fix soon
- Low: cleanup or small quality issue
- Note: optional improvement
EOF2
步骤 3：写 cloud-agent review prompt
cat > seo-geo/pr-review/review-prompt.md <<'EOF2'
Review this branch or pull request for SEO/GEO risk.
Use `.cursor/rules/seo-geo-pr-review.mdc` and `seo-geo/pr-review/checklist.md`.
Do not commit changes. Return findings only.
For each finding include:
- severity
- file reference
- exact risk
- why it matters for SEO/GEO
- how to verify
- whether a patch is safe or needs human approval
If there are no findings, say that explicitly and list residual testing gaps.
EOF2
步骤 4：跑第一次 cloud review
在 Cursor 里，对 branch 或 PR 启动 Cloud Agent，并贴上：
Use `seo-geo/pr-review/review-prompt.md`.
Review this branch for SEO/GEO risk.
Do not commit changes and do not create a patch.
Return findings only, ordered by severity.
好的 finding 是具体的：
High - src/lib/seo.ts: canonical generation now strips locale prefixes. This may cause localized pages to canonicalize to English URLs. Verify rendered canonical and hreflang on one English page and one translated page before merge. Patch safety: requires human approval.
弱的 finding 是：
Improve SEO metadata.
如果 review 太 vague，把 examples 加进 review-prompt.md 后重跑。
步骤 5：只核准 selected fixes
建立 approved fixes file：
cat > seo-geo/pr-review/approved-fixes.md <<'EOF2'
# Approved Fixes
Approved:
- Finding M1: duplicate meta description on `/features/reporting`
Not approved:
- canonical policy changes
- robots/noindex changes
- redirects
- analytics changes
- schema helper rewrites
- broad content rewrites
EOF2
接著问 cloud agent：
Apply fixes only for items listed in `seo-geo/pr-review/approved-fixes.md`.
Do not touch unrelated files.
Do not change canonicals, robots, redirects, analytics, schema helpers, or shared templates.
Run available validation and return changed files, commands run, and remaining risks.
这能防止 review agent 变成 uncontrolled editor。
步骤 6：merge 前检查 patch
Agent 提出或套用 patch 后，检查：
git diff --name-only
git diff --stat
接著问：
Compare the changed files against `seo-geo/pr-review/approved-fixes.md`.
List any file that was changed without approval. Do not make more edits.
如果有 unapproved file changed，停下来手动 review。
步骤 7：一致使用 severity model
| Severity | Example | Merge decision |
|---|---|---|
| Critical | 重要 pages 变成 noindex | block merge |
| High | canonicals 指到错误 locale | merge 前修掉 |
| Medium | duplicate meta descriptions | 修掉或开 ticket |
| Low | missing alt text | batch cleanup |
| Note | internal link opportunity | optional |
Cloud agents 在让 review consistent 时很有用；当它把每个 finding 都当成同等重要时就很危险。
Troubleshooting
| Problem | Likely cause | Fix |
|---|---|---|
| Agent 太快 commit | Prompt 没说 findings only | 在 rule 和 prompt 加上 “Do not commit changes” |
| Findings 太 generic | Checklist 缺少 examples | 加入 good/bad finding examples |
| Patch 太 broad | Approved fixes file 太 vague | 核准 finding IDs 和 exact files |
| Agent 要 secrets | Task 包含 analytics/CMS actions | 提供 sanitized exports 或只做 code review |
| Human reviewer 无法 verify | 缺少 validation steps | 要求每个 finding 都附 verification |
FAQ
每个 PR 都应该做 Cursor SEO/GEO review 吗？
不需要。用在 SEO-critical paths：metadata、schema、routes、templates、content、robots、sitemap、localization 和 analytics。
Cursor Cloud Agents 可以取代 technical SEO review 吗？
不行。它们适合抓 repeatable diff risks。Strategy、claims、migrations 和 release timing 仍然要人核准。
最安全的 first test 是什么？
开一个只改一个 page title 和一个 meta description 的小 PR。只要求 review，然后拿结果和 human review 比较。
AI coding agents for SEO/GEO 学习路径
Cursor track：
- Cursor vs Windsurf vs Gemini CLI：SEO/GEO 自动化怎么选
- 如何设定 Cursor Rules 做 SEO/GEO 工作
- 如何用 Cursor Plan Mode 安全更新 SEO 页面
- 如何用 MCP 将 Cursor 接上 SEO 资料
- 如何用 Cursor Cloud Agents 做 SEO/GEO PR Reviews
- Cursor、Windsurf、Gemini CLI、Codex、Claude Code 的 SEO/GEO 营运模型
Sources and notes
- Cursor documentation hub: Cursor Docs ，包含 Agent、Rules、MCP、Skills、CLI 与 background/agent capabilities 的公开文件。
- Related Auspia guide: Cursor vs Windsurf vs Gemini CLI for SEO/GEO Automation 。
Author: Tessa Clarke, Auspia 120+ Editorial Systems Content Governance Lead。Tessa 撰写 review systems、publishing standards 与 safe AI-assisted content operations。
