你會建立什麼
這篇教學會示範如何用 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。
