50+ professional SEO prompt commands for Claude Code and Gemini CLI
Install once. Use from any folder. Get expert-level SEO output in seconds.
If you do SEO work and use Claude Code, this tool gives you a full library of ready-made commands for every SEO task β technical audits, content writing, keyword research, analytics analysis, local SEO, e-commerce, GEO/LLM optimization, and more.
Instead of writing prompts from scratch every time, you type /write-blog, /robots-audit, or /keyword-research directly inside Claude Code and get a professional, structured result immediately.
| Tool | Install | Required? |
|---|---|---|
| Node.js 16+ | nodejs.org | Yes |
| Claude Code | npm install -g @anthropic-ai/claude-code |
One or both |
| Gemini CLI | npm install -g @google/gemini-cli |
One or both |
You need at least one AI CLI tool installed. If you have both, prompts are installed for both automatically.
Not sure what you have? Run seo-ai-tool check after installing.
# 1. Install the package globally
npm install -g seo-ai-tool
# 2. Copy all prompts into Claude Code
seo-ai-tool installThat's it. All 50+ commands are installed for every AI CLI tool you have β Claude Code, Gemini CLI, or both.
Start Claude Code or Gemini CLI in any project folder and type a slash command:
cd ~/projects/my-client
claude # start Claude Code
# or
gemini # start Gemini CLI/write-blog primary keyword: "best crm for small business"
/robots-audit
β paste your robots.txt when prompted
/keyword-research niche: "email marketing tools"
If you run a command without input, the AI will tell you exactly what it needs. You never have to guess.
π§ Technical SEO (10 commands)
| Command | What it does | What to provide |
|---|---|---|
/robots-audit |
Audit a robots.txt file for issues | Your robots.txt content |
/sitemap-audit |
Review an XML sitemap for errors and gaps | XML sitemap file or sitemap index |
/schema-generator |
Generate structured data markup (JSON-LD) | Content type (Article, Product, etc.) + content details |
/canonical-audit |
Find canonical tag issues | Crawl export or canonical tag data |
/hreflang-audit |
Check hreflang implementation for international SEO | Hreflang tags, HTTP headers, or sitemap |
/cwv-diagnosis |
Diagnose Core Web Vitals problems | PageSpeed Insights report or CrUX data |
/redirect-map |
Generate a redirect map for site migrations | Old URLs and new URLs (CSV or list) |
/internal-links |
Audit internal linking structure | Screaming Frog or crawler export |
/server-logs |
Analyze server log files for crawl insights | Apache/Nginx server log file |
/crawl-budget |
Identify crawl budget waste | Server logs or crawl data + robots.txt |
π On-Page SEO (8 commands)
| Command | What it does | What to provide |
|---|---|---|
/title-rewrite |
Rewrite page titles for better CTR and rankings | Current page titles, target keywords, URLs |
/headings-audit |
Review heading structure (H1βH6) | Page URL or heading structure + target keyword |
/alt-text |
Write optimized alt text for images | Image URLs or filenames + page context |
/content-brief |
Create a full SEO content brief | Target keyword, search intent, competitor URLs |
/content-refresh |
Update and improve existing content | Existing article content or URL + target keyword |
/faq-generator |
Generate FAQ sections with schema markup | Topic or keyword, PAA questions (optional) |
/thin-content |
Identify and fix thin content issues | Page URL + content + target keyword |
/meta-descriptions |
Write click-worthy meta descriptions | Page URLs, target keywords, current descriptions |
βοΈ Content & Link Building (10 commands)
| Command | What it does | What to provide |
|---|---|---|
/keyword-research |
Full keyword research and clustering | Topic or niche, target audience, business goals |
/write-blog |
Write a complete, SEO-optimized blog post | Primary keyword, target audience, site URL |
/pillar-page |
Create a comprehensive pillar page | Head keyword, topic focus, cluster articles list |
/topic-cluster |
Plan a full topic cluster strategy | Head keyword, topic focus, audience level |
/content-calendar |
Build an SEO content calendar | Primary keywords, goals, content types, time period |
/comparison-article |
Write a comparison/versus article | Two products/services to compare, pricing info |
/outreach-email |
Write link building outreach emails | Outreach type, target audience, your content/URL |
/brand-mention-pitch |
Turn unlinked brand mentions into backlinks | Publication URL, article URL, brand name, your URL |
/press-release |
Write an SEO-friendly press release | Announcement details, company name, newsworthy event |
/backlink-article |
Write content designed to earn backlinks | Target keyword, landing page URL, topic context |
π Local SEO (3 commands)
| Command | What it does | What to provide |
|---|---|---|
/gbp-description |
Write a Google Business Profile description | Business name, location, services, differentiators |
/local-landing |
Create a local landing page | Service type, city/location, business name |
/review-responses |
Write professional responses to reviews | Business name, service area, industry |
π E-commerce SEO (3 commands)
| Command | What it does | What to provide |
|---|---|---|
/product-description |
Write SEO-optimized product descriptions | Product name, features, specs, target audience |
/category-page |
Optimize category page content | Category name, brand name, product range |
/product-schema |
Generate product structured data | Product name, image, price, ratings, SKU/GTIN |
π Analytics (6 commands)
| Command | What it does | What to provide |
|---|---|---|
/ga4-traffic |
Analyze GA4 organic traffic data | GA4 CSV export (organic sessions, devices, geography) |
/ga4-conversions |
Review GA4 conversion performance | GA4 CSV export with conversions and landing pages |
/ga4-content |
Analyze GA4 content performance | GA4 CSV export with landing pages and engagement metrics |
/gsc-indexing |
Diagnose Google Search Console indexing issues | GSC Coverage report data |
/gsc-links |
Analyze GSC link data | GSC Links report data |
/gsc-performance |
Full GSC performance analysis | GSC export (queries, pages, clicks, impressions, CTR) |
π Reporting & Analysis (4 commands)
| Command | What it does | What to provide |
|---|---|---|
/competitor-analysis |
Analyze a competitor's SEO strategy | Competitor URLs + keyword data |
/content-gap |
Find content gaps vs competitors | Your site data + competitor data + GSC/Ahrefs export |
/monthly-report |
Generate a monthly SEO report | GA4 data, GSC data, reporting period, work completed |
/penalty-diagnosis |
Diagnose a potential Google penalty | Traffic drop date, GA4/GSC data, timeline |
π€ GEO / LLM Optimization (5 commands)
| Command | What it does | What to provide |
|---|---|---|
/geo-audit |
Audit content for AI/LLM visibility | Page URL or content + target keyword |
/geo-rewrite |
Rewrite content to appear in AI answers | Existing content or URL + target keyword |
/geo-entity |
Build entity authority for LLM recognition | Brand/product/person name + key facts |
/geo-visibility |
Improve visibility in generative search | Brand name, product/service category, target keywords |
/geo-citations |
Build citation-worthy content | Target topics/keywords, content type focus |
β‘ Agents (1 command)
| Command | What it does | What to provide |
|---|---|---|
/agent-monthly-report |
Autonomous agent that generates a full monthly SEO report | GA4 CSV, GSC CSV, site URL, reporting period |
You are an SEO consultant with two clients. Here's the full workflow from zero to running commands.
~/projects/
βββ project1/ β Client 1: an e-commerce store
β βββ brand-voice.md
β βββ data/
β β βββ gsc-performance.csv
β β βββ ga4-organic.csv
β β βββ screaming-frog-export.csv
β βββ outputs/
βββ project2/ β Client 2: a local service business
βββ brand-voice.md
βββ data/
β βββ gsc-performance.csv
βββ outputs/
npm install -g seo-ai-tool
seo-ai-tool installAll 50+ commands are now available everywhere on your machine.
cd ~/projects/project1
seo-ai-tool initThis creates a .claude/commands/ folder inside project1. Any prompt you place here overrides the global version β for this project only.
Export files from GSC, GA4, or Screaming Frog and drop them into data/:
project1/
βββ data/
βββ gsc-performance.csv β from Google Search Console
βββ ga4-organic.csv β from GA4 β Acquisition β Organic
βββ screaming-frog-export.csv β from Screaming Frog β Internal tab
Create brand-voice.md in the project root:
# Brand Voice β Project1
- Tone: friendly, confident, never salesy
- Audience: small business owners aged 30β50
- Avoid: jargon, passive voice, filler phrases like "In conclusion"
- Always use: "you" to address the reader directly
- Example: "Here's exactly what you need to do to rank higher this month."All content commands will read this file automatically and match the tone.
cd ~/projects/project1
claudeAnalyze GSC data:
/gsc-performance data/gsc-performance.csv
Write a blog post (brand voice applied automatically):
/write-blog primary keyword: "best running shoes for flat feet"
Audit internal links:
/internal-links data/screaming-frog-export.csv
Analyze organic traffic:
/ga4-traffic data/ga4-organic.csv
After each command, ask Claude to save the result:
Save the output to outputs/gsc-performance-2026-02.md
Your project folder ends up looking like this:
project1/
βββ brand-voice.md
βββ .claude/
β βββ commands/ β customized prompts for this client
βββ data/
β βββ gsc-performance.csv
β βββ ga4-organic.csv
β βββ screaming-frog-export.csv
βββ outputs/
βββ gsc-performance-2026-02.md
βββ write-blog-running-shoes-2026-02.md
βββ internal-links-audit-2026-02.md
# Copy the global prompt into the project
cp ~/.claude/commands/write-blog.md ~/projects/project1/.claude/commands/write-blog.md
# Edit it to add client-specific rules/write-blog now behaves differently in project1 but stays unchanged everywhere else. When you switch to project2, the global version is used β until you set up overrides there too.
Both Claude Code and Gemini CLI read commands in this priority order:
.claude/commands/write-blog.md β local version (wins if it exists)
~/.claude/commands/write-blog.md β global version (fallback)
.gemini/commands/write-blog.md β local version (wins if it exists)
~/.gemini/commands/write-blog.md β global version (fallback)
Commit .claude/commands/ and .gemini/commands/ to git and your whole team automatically shares the same customized prompts.
| Command | Description |
|---|---|
seo-ai-tool install |
Copy all prompts to ~/.claude/commands/ |
seo-ai-tool update |
Update global prompts to the latest version |
seo-ai-tool init |
Create .claude/commands/ in the current project |
seo-ai-tool list |
List all prompts by category |
seo-ai-tool check |
Check if Claude Code and Gemini CLI are installed |
seo-ai-tool uninstall |
Remove all prompts from ~/.claude/commands/ |
seo-ai-tool help |
Show help |
npm update -g seo-ai-tool
seo-ai-tool update1. Client data & privacy Before uploading any client data (Google Search Console exports, GA4 reports, crawl files, server logs, or any other analytics) to an AI tool, you must have explicit permission from your client. Many clients have data privacy policies, NDAs, or GDPR obligations that restrict how their data can be shared with third-party services β including AI platforms. When in doubt, anonymize the data or ask your client before proceeding.
2. Always review AI output before using it The output generated by these commands is a starting point, not a final deliverable. AI models can make mistakes β URLs may be incorrect, schema syntax may contain errors, redirect rules may need adjusting, facts may be outdated or hallucinated. Never publish, deploy, or send AI-generated output to a client without reviewing it yourself first. You are responsible for the final work.
Contributions are welcome β new commands, prompt improvements, bug reports, or documentation fixes.
Read the Contributing Guide to get started.
MIT