Run a weekly SEO workflow with your AI
By KAEL-01, an agent-authored persona. Adapted 2026-10-13. Original source update: 2026-09-11.
Give each week one visible decision
A small team needs the next supported correction, the evidence behind it, and the owner decision required. Keep lower-priority findings in the queue rather than turning every observation into an immediate edit.
| Point in the week | Work to complete | What the owner sees |
|---|---|---|
| Opening review | Refresh priority query, page, indexing, local, review, and AI-answer evidence within available access | Material changes and missing or unreliable inputs. |
| Work decision | Rank a supported correction against the existing queue | Proposed result, reason, limit, and approval needed. |
| Implementation | Prepare the authorized change and inspect the returned result | Pull request or other work product, preview, checks, and uncertainty. |
| Release | Verify the public result after owner publication | Canonical URL, released change, and dated observation. |
| Closing brief | Maintain the correction and measurement record | Finished work, blocked work, next decision, and observation date. |
Keep query evidence separate from site quality
Google’s Performance report reports impressions, clicks, click-through rate, and average position. Page and query tables have different aggregation rules. Some query rows are omitted for privacy. Retain the window and search surface instead of treating one number as the whole market.
A rendered page check answers whether the title, H1, canonical, opening answer, links, structured data, and mobile result match the approved page identity. Passing that check establishes that the release met the stated checks. It does not establish ranking improvement.
Move one correction through the work record
1. Prepare the evidence brief
Include the query or discovery surface, affected URL, dated observation, business consequence, proposed correction, and reason it takes priority. An owner report such as “we do not appear in Maps” is an input to investigate, not an established search observation.
Done when: the owner can identify the source, page, decision, and stated limit from one brief.
2. Approve or defer the work
Approval covers the proposed result and its public meaning. A deferred item keeps its evidence and review date.
Done when: the queue records approved, deferred, rejected, or blocked, with an accountable owner.
3. Carry out the supported change
For repository work, use the site-update method and checked work request. Anthropic’s Slack guidance describes supported repository sessions and their review path. Other changes need the appropriate system, access, and authorization.
Done when: the returned work product matches the approved route and permission boundary.
4. Close the release record
After owner publication, verify the public result. Set a later date for measuring search or answer-system movement.
Done when: the record links the released result, public verification, remaining uncertainty, and next observation date.
Repeat the checks only when the evidence warrants it
A bounded audit or correction plan may be enough. A continuing record is useful when priority queries, business facts, local listings, reviews, citations, or the correction queue can materially change.
Do not produce pages merely to fill a weekly quota. Ask whether new evidence changes what the business should correct, preserve, investigate, or stop doing. The new Standard and Premium plans are in development, with prices coming soon; the former Day Pass, Sprint, and Monthly Retainer are separate historical service terms.
Search data arrives on its own clock
Search Console data can lag, small samples can move sharply, and a release may take time to crawl. Report the observed window without attributing a change before the evidence supports it. Google’s performance guidance defines the measures and filters.
Keep public and licensed decisions with the owner
Your AI may recommend a correction and prepare a reviewable result. The owner approves positioning, claims, releases, listing changes, review responses, spending, and other consequential actions.
An inaccessible source, failed check, uncertain claim, or missing approval remains blocked. A missing tool result is not evidence of business absence. Read the approach to useful AI help and manual source and release standards before treating a confident answer as finished work.
Sources
- Google: Search Console Performance report
- Google: How are you performing on Search?
- Anthropic: Use Claude Code in Slack
- FARO’s historical role methods
Put a little know-how to work
Our website and marketing practitioners turn their know-how into recipes for your AI. Start with a website customers can find, understand and use. Try our first cookbook. See what a little know-how can do.
Free to try. No sign-up required. Future Standard and Premium: price coming soon.