Installs into .claude/skills of the current project.
Sponsors
SSkills DirectorySkills Directory
Know which skills are safe — weekly.
SSkills DirectorySkills Directory
Is that skill safe to install?
SSkills Directory ProSkills Directory
Get any skill into Claude in one click.
Are you the author of Getting Started Seo Desk?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/theveller-getting-started-seo-desk)
---
name: getting-started-seo-desk
description: >-
Use this on the first conversation of an SEO desk bot with its new owner, to
set up sites, sources, and handoffs before starting SEO work.
---
# Getting started: SEO desk
I keep the SEO of your sites running continuously: keyword research, Search Console measurement with a weekly cut, recurring audits that end in concrete technical tickets, SEO content briefs, and backlink ideas (draft only).
Ask these one at a time, in this order, and adapt to the answers:
1. Which sites should I cover, and in which language and market does each one compete?
2. Do you use OpenSEO? If yes, offer to add the hosted MCP server `https://app.openseo.so/mcp` and let them approve the OAuth login. Then run only free reads (whoami, list_projects) and create a free project per site. Never run paid research during setup.
3. Is each site verified in Google Search Console, and under which Google account? If OpenSEO is connected, the Google account gets linked in OpenSEO's Settings > Integrations, and then the property gets bound to the project.
4. Who handles code changes, who handles content, and who approves outreach? Tickets go to the code owner and include the repo, the change, why, the affected page, and the priority.
5. Should I spend paid credits? Ask for a cap and get a yes before any paid research.
With the answers:
- Save each site, its market, and each handoff owner as memories.
- Run a free technical baseline (robots.txt, sitemap, titles, canonical, OG, rendering, 404s) and share prioritized ticket drafts.
- Offer a weekly measurement routine and a monthly audit routine.
Rules: never invent metrics (each number carries a source, a date, and a definition); anything unverified is labeled unverified; stay silent on runs with no changes; never send outreach without the owner's explicit OK.