Routines
Grok Bot SEO routines: 7 schedules that run your SEO
Routines turn a Grok Bot from a helper into a worker. Here are seven SEO routines, with the exact text to give your Bot.
How routines work
You create a routine by telling your Bot what to do and when, for example “every weekday at 8:00 AM”. The routine runs on the Bot’s persistent cloud computer, so it keeps going while your laptop is closed.
Three rules make SEO routines work:
- One job per routine. A report routine reports. A fix routine fixes. Mixed routines give vague summaries.
- Say what “done” looks like. “Open one pull request and send me three lines” is better than “improve SEO”.
- Write results to files. Chat history is not memory. A file in the Bot’s workspace is.
1. The weekday SEO shift
| When | Every weekday, 8:00 AM |
|---|---|
| Needs | An SEO work queue (SEOAgent) and repository or CMS access |
| Approvals | Merges and publishing |
Every weekday at 8:00 AM, run seoagent sync. Work through the SEO inbox in priority order for up to one hour. Put all changes in one pull request. Then send me a three-line summary: what you shipped, what waits for my approval, and what you skipped and why.2. Monday Search Console report
| When | Every Monday, 9:00 AM |
|---|---|
| Needs | Search Console access through an SEO tool or connector |
| Approvals | None. Read-only. |
Every Monday at 9:00 AM, compare last week’s Google Search Console data to the week before. Report in plain words: total clicks and impressions, the 5 pages that gained the most clicks, the 5 that lost the most, and up to 5 queries where we rank between position 8 and 20. For each loser, give one likely reason. Save the report to /workspace/seo/reports/ with the date in the file name.3. Technical sweep
| When | Every Tuesday |
|---|---|
| Needs | Browser or crawler, repository or CMS access |
| Approvals | Merges |
Every Tuesday at 7:00 AM, crawl the site. Check for: missing or duplicate titles and meta descriptions, broken internal links, redirect chains, pages missing from the sitemap, missing canonical tags, images without alt text, and pages that return errors. Fix what you can in one pull request and list the rest for me.4. Content day
| When | Wednesday and Friday |
|---|---|
| Needs | A content plan with briefs (SEOAgent or a file in /workspace) |
| Approvals | Publishing |
Every Wednesday and Friday at 10:00 AM, take the next planned article from the content plan. Write it from its brief. Add 3 to 5 internal links to related pages and 1 link from an older page to the new one. Add title, meta description and structured data. Open a pull request (or a CMS draft) and send me the link.5. Refresh a page that is slipping
| When | Every Thursday |
|---|---|
| Needs | Search Console data |
| Approvals | Merges or publishing |
Every Thursday at 10:00 AM, pick the page that lost the most clicks over the last 28 days and still gets impressions. Compare it with the current top results for its main query. Update what is outdated, add what is missing, keep the URL the same, and update the "last updated" date. Open a pull request with a short note on what changed.6. X question scan
| When | Every Friday |
|---|---|
| Needs | Nothing extra. Grok can search X. |
| Approvals | None. Adds ideas only. |
Every Friday at 3:00 PM, search X for posts from the last 7 days about [your topic]. Find new questions and complaints that our site does not answer yet. Add each one to /workspace/seo/ideas.md with a suggested title and the link to one example post. Send me the top three.7. Outreach follow-ups
| When | Every Tuesday and Thursday |
|---|---|
| Needs | Approved outreach drafts and a connected email account |
| Approvals | Every message |
Every Tuesday and Thursday at 11:00 AM, check the outreach queue. Send only the drafts I approved, from my connected email. For replies, draft an answer and wait for my approval. Never send a first message I did not approve.Give the Bot a memory file
xAI’s docs make the point that chat is history, but a file is memory. Ask your Bot to keep one SEO log in its workspace, and to read it at the start of every routine:
Create /workspace/seo/LOG.md. After every SEO routine, add one dated line: what you changed, which URLs, and why. At the start of every SEO routine, read the last 20 lines first so you do not repeat work or undo a recent change.Using SEOAgent?
The SEOAgent CLI keeps its own state in a .seoagent/ folder and a cloud timeline of every change, so the Bot already has this memory. The log file is still useful for your own notes.
Want the steps saved as reusable skills too? See Grok Bot skills for SEO.
Frequently asked questions
What is a Grok Bot routine?
A routine is a task your Grok Bot runs on a schedule, such as every weekday at 8:00 AM. You create it in conversation with the Bot. Per xAI’s docs, background routines can run while your laptop is closed, because they run on the Bot’s persistent cloud computer.
How many SEO routines should I start with?
Start with two: the weekday SEO shift and the Monday Search Console report. Add more after two weeks, when you trust what the Bot ships.
What if a routine needs my approval while I am away?
Plan for it. Steps that publish, send messages or change production can wait for you. Write routines so the Bot prepares the change and tells you, instead of stopping halfway.
Can routines use Search Console data?
Yes, if the Bot has access to it. The simplest way is an SEO tool the Bot can call, such as the SEOAgent CLI, which reads your connected Search Console account.