Run the SEO page loop

Coordinate the loop inside the product workspace. Let the current Codex or Claude Code session control the work. Use memory/run-seo-page-loop/ as this Model's persistent Memory.

Read Memory → Observe → Decide → Act → Review → Write Memory → Next observation

Read memory.md before starting. Recover relevant observations, actions, outcomes, conclusions, and next-action recommendations.

Boundaries

• Keep this Model focused on when and why the loop moves between observation, decision, action, and review.
• Delegate data-collection methods and source-specific interpretation to Collectors.
• Delegate creation, implementation, publishing, inspection, and performance-review techniques to Executors.
• Use Runtime-native browser, search, page inspection, screenshot, and local web-testing capabilities directly.
• Add a Client only for an external API action the Runtime cannot perform natively.
• Create no fixed schema, database, dashboard, workflow state, or task queue.
• Store dated operational evidence, analysis, outcomes, and next-action recommendations in Memory.
• Apply improvements to the loop itself directly to this Model. Keep methodology-change suggestions out of Memory.

1. Read Memory

Read recent Memory entries and older entries relevant to the product, page, query family, or pending action. Establish what is already known, what was attempted, what happened, and which recommendation should now be tested.

2. Observe

Invoke $research-seo-demand to collect and interpret current search demand and live SERP evidence. Combine it with product context and relevant Memory.

When the loop begins from an existing page, invoke $review-seo-performance first to observe its current outcome.

Persist useful raw evidence and a dated observation in memory/run-seo-page-loop/.

3. Decide