Skills and templates
Grok Bot skills for SEO
Skills make your Bot do SEO the same way every time. Here are five you can save today, and when an SEO harness is the better choice.
Skills, routines and templates
A skill is how to do a task. A routine is when to do it. A template is a whole Bot, with its skills and routines, that someone shared.
- Skills are saved processes. All your Bots share one skill library, and you call a skill with a slash, like
/seo-audit. - Routines run a task on a schedule. See Grok Bot SEO routines.
- Templates are shared Bots. “Add to Grok Bot” copies the Bot’s identity, description, skills and routines into your account.
To save a skill, tell your Bot: “Save this as a skill called seo-audit”, and paste the text. Each skill below assumes the Bot can reach your site. Skills that read Search Console need an SEO tool with that access.
/seo-audit
A repeatable site audit with the same checks every time.
Name: seo-audit
Goal: Find the SEO problems on my site that cost the most traffic.
Steps:
1. Read /workspace/seo/LOG.md so you know what changed recently.
2. Crawl the site from the homepage and the sitemap.
3. Check every page for: status code, title (missing, duplicate, over 60 characters), meta description (missing, duplicate), one H1, canonical tag, indexable or not, internal links in and out, images without alt text, structured data errors.
4. Check robots.txt and the sitemap.
5. Rank the problems by how many important pages they affect.
Output: a table of the top 10 problems with the affected URLs and the fix. Do not change anything./meta-fix
Write and ship titles and descriptions for pages that need them.
Name: meta-fix
Goal: Every indexable page has a unique title and meta description.
Steps:
1. List pages with a missing, duplicate or too-long title or description.
2. For each page, read the content and find its main query (use Search Console data if available).
3. Write a title under 60 characters with the query near the start, and a description of 140 to 155 characters.
4. Make the changes in one pull request (or as CMS drafts).
Output: the pull request link and a table of old vs. new./write-from-brief
Turn a content brief into a publish-ready page.
Name: write-from-brief
Goal: A publish-ready article that answers the search intent better than the current top results.
Steps:
1. Read the brief. If there is none, stop and ask me for one.
2. Search the web and X for the current top answers and recent questions on the topic.
3. Write the article: answer first, short paragraphs, one idea per paragraph, real examples. No invented statistics.
4. Add 3 to 5 internal links and suggest 1 link from an older page to this one.
5. Add title, meta description and Article + FAQPage structured data.
Output: a pull request or CMS draft, plus a list of facts I should check./gsc-report
A Search Console summary you can read in a minute.
Name: gsc-report
Goal: Tell me what changed in search this week, in plain words.
Steps:
1. Get the last 7 days and the previous 7 days from Google Search Console.
2. Compare clicks, impressions, CTR and average position.
3. List the top 5 gaining pages, top 5 losing pages, and queries ranking 8 to 20.
4. For each losing page, give one likely reason.
Output: a short report saved to /workspace/seo/reports/, and a five-line summary to me./internal-links
Connect new pages to the rest of the site.
Name: internal-links
Goal: Every important page gets links from related pages.
Steps:
1. List all pages with their titles and main topics.
2. Find pages with fewer than 3 internal links pointing to them.
3. For each, find 2 to 4 related pages and a sentence where a link fits naturally. Use descriptive anchor text, never "click here".
4. Make the changes in one pull request.
Output: the pull request link and a list of links added.Build your own or use a harness?
The five skills above are a good start. They leave three gaps that you fill yourself:
- Data. The skills ask for Search Console and keyword numbers. The Bot needs a way to get them.
- Priorities. Each skill does one job well. Something still has to decide which job matters most this week.
- Upkeep. Search changes. Someone has to keep the checks current.
An SEO harness fills those gaps. SEOAgent (made by the team behind this site) gives the Bot a Skill as its playbook, a CLI as its tools, synced site state, and a cloud queue that ranks work from your Search Console data. The SEOAgent Grok Bot template installs all of it.
You can mix both
Keep your own skills for the work that is specific to your site. Let the harness handle the queue and the data.
Frequently asked questions
What are Grok Bot skills?
In Grok Bot, a skill is a saved process: a reusable set of instructions for how to do a task. Skills live in one library that all your Bots share, and you call a skill with a slash, for example /seo-audit.
What is a Grok Bot template?
A template is a Bot that someone shared with a public link on x.ai. When you click Add to Grok Bot, you get a copy of its identity, description, skills and routines. You do not get the creator’s computer, logins or chat history.
Is there an SEO skill for Grok Bot I can install?
Yes. You can save the five skills on this page yourself. Or add the SEOAgent Grok Bot template, which installs the SEOAgent Skill and CLI and binds them to your account. The Skill and CLI are free.
Do Grok Bot skills use the SKILL.md format?
Grok Bot skills are saved in Grok Bot itself, not as SKILL.md files. A Bot can still read a SKILL.md file from its computer like any other file, which is how tools such as SEOAgent give it a playbook.