Growth
SEO Monthly Rank Experiment
Scheduled rank-KPI SEO loop: one experiment per cycle, measure next tick, undo losers.
Use when
You want search (and LLM/GEO) visibility to climb over months without hiring an agency, and you can give an agent read access to rank data plus write access to a small content surface.
Intermediatedifficulty
Growthcategory
Greg Isenberg + Ellie interview: Making $$$ with Loop Engineering — business-facing monthly SEO loop with objective rank KPI, tool access, experiment memory, and undosource
Cadence
Monthly (or every 2 weeks); not continuous thrash
Verification
One reversible change set is applied, Search Console (or equivalent) rank/click metrics for the target queries are recorded before and after the waiting window, the experiment log is updated, and if rank fell the change is queued for undo.
Structured loop spec
| Field | Value |
|---|---|
| Name | SEO Monthly Rank Experiment |
| Category | Growth |
| Trigger | Monthly (or every 2 weeks); not continuous thrash |
| Objective | Scheduled rank-KPI SEO loop: one experiment per cycle, measure next tick, undo losers. |
| Allowed inputs | Relevant files, source notes, logs, tests, screenshots, metrics, or task state for this loop |
| Allowed actions | Pick 3–10 target queries and baseline current position, impressions, and clicks from Search Console or an SEO API; write them into an experiment log.; Run a cheap audit pass first: meta, JSON-LD, sitemap, cannibalizing URLs, broken internal links — only queue quick wins you can reverse.; Choose one primary experiment for this cycle (one page or one cluster, one hypothesis). Do not ship a kitchen-sink rewrite.; Apply the single reversible change set (content, title, internal links, schema). Commit or snapshot so undo is trivial.; Schedule the next tick (2–4 weeks). On return, re-read the same metrics, mark win/flat/loss in the experiment log, and undo or double-down.; Ping a human for approval before public content deploys or bulk site edits. Stop when target queries are on page one, budget is spent, or two cycles show no progress. |
| Verification | One reversible change set is applied, Search Console (or equivalent) rank/click metrics for the target queries are recorded before and after the waiting window, the experiment log is updated, and if rank fell the change is queued for undo. |
| Stop condition | Stop when the verifier passes, the budget is exhausted, no progress is made, a blocker appears, or approval is required. |
| Budget | Set a time, turn, token, retry, file, or dollar cap before running the loop. |
| Approval boundary | Human approval required before publishing, sending, deleting, spending, changing accounts, touching production, or making reputational/legal/financial commitments. |
| Safe output | Draft, report, checklist, table, or approval-gated recommendation |
| Works with | Claude, ChatGPT, Gemini, any tool-using AI assistant |
Steps
- Pick 3–10 target queries and baseline current position, impressions, and clicks from Search Console or an SEO API; write them into an experiment log.
- Run a cheap audit pass first: meta, JSON-LD, sitemap, cannibalizing URLs, broken internal links — only queue quick wins you can reverse.
- Choose one primary experiment for this cycle (one page or one cluster, one hypothesis). Do not ship a kitchen-sink rewrite.
- Apply the single reversible change set (content, title, internal links, schema). Commit or snapshot so undo is trivial.
- Schedule the next tick (2–4 weeks). On return, re-read the same metrics, mark win/flat/loss in the experiment log, and undo or double-down.
- Ping a human for approval before public content deploys or bulk site edits. Stop when target queries are on page one, budget is spent, or two cycles show no progress.
Prompt
Run the SEO Monthly Rank Experiment loop for this site. Load the experiment log (create it if missing). Pull current rank/impressions/clicks for the listed target queries from Search Console or the available SEO API. Propose exactly one reversible experiment with hypothesis, files/pages touched, and expected metric move. Do not ship bulk rewrites. After human approval, apply the change, snapshot for undo, and schedule the next review. On a later tick, compare metrics to the prior baseline, log win/flat/loss, and undo if rank fell. Also note GEO/LLM-answer implications of the same change. Stop when primary queries are page-one, two cycles show no progress, budget is hit, or approval is required for red actions.Run in Claude Code
Paste this into Claude Code (or any tool-using agent) to run the loop bounded: one change per round, the same verification every round, durable state files, and explicit stop conditions.
Run the "SEO Monthly Rank Experiment" loop from AI Loop Library (https://ailooplibrary.com/loops/seo-monthly-rank-experiment/) as a bounded loop.
Goal: Scheduled rank-KPI SEO loop: one experiment per cycle, measure next tick, undo losers.
Rules: one change per round; run the same verification every round (One reversible change set is applied, Search Console (or equivalent) rank/click metrics for the target queries are recorded before and after the waiting window, the experiment log is updated, and if rank fell the change is queued for undo.); append each round to docs/loops/seo-monthly-rank-experiment/progress.md and update docs/loops/seo-monthly-rank-experiment/state.json; stop on verifier pass, 8 rounds, 3 consecutive failed verifications, no progress, a blocker, or anything needing human approval (money, production, outbound, deletion). Finish with a proof report: rounds used, changes made, verification output, remaining risk, and the next human decision.