SEO work is not one task.
A technical SEO audit, a content brief, a schema review and a local SEO analysis require different checks and different evidence.
Using one giant prompt for all of them usually produces a generic report. A better approach is to use a focused skill for each recognised SEO job.
This guide explains how to use a reusable SEO skill library for technical audits, content, structured data, local search, backlinks and AI search visibility.
Why separate SEO skills?
Each SEO workflow has different inputs and limitations.
| Workflow | Main input | Typical output |
|---|---|---|
| Technical SEO | Website URL and crawl scope | Crawlability, indexability, performance and security findings |
| Page SEO | Single URL | On-page and technical page review |
| Schema | HTML, JSON-LD or URL | Validation findings and corrected markup |
| Sitemap | XML sitemap or website URL | Invalid URLs, structure and coverage issues |
| Content | Page text or content set | Quality, clarity, intent and E-E-A-T review |
| Content brief | Topic and target audience | Research-based outline and writing requirements |
| Local SEO | Business and location data | GBP, NAP, citations and local landing-page review |
| GEO | Website and entity information | AI search accessibility and citation-readiness review |
| Backlinks | Link data or connected provider | Referring-domain, anchor and risk analysis |
Focused skills make it easier to state what was checked and what was not checked.
The SEO skill library
The library contains these specialist workflows:
seo
seo-audit
seo-backlinks
seo-cluster
seo-competitor-pages
seo-content
seo-content-brief
seo-dataforseo
seo-drift
seo-ecommerce
seo-flow
seo-geo
seo-google
seo-hreflang
seo-image-gen
seo-images
seo-local
seo-maps
seo-page
seo-plan
seo-programmatic
seo-schema
seo-sitemap
seo-sxo
seo-technicalThe general seo skill can help select the appropriate workflow. The specialist skills should be used when the requested task is clear.
Technical SEO
Use seo-technical when the request concerns:
- crawlability;
- indexability;
- robots.txt;
- canonical URLs;
- redirects;
- URL structure;
- HTTPS and security headers;
- mobile behaviour;
- Core Web Vitals;
- JavaScript rendering;
- structured data;
- sitemap references.
Example:
Use seo-technical to audit https://example.com read-only. Check crawlability, indexability, redirects, security headers, structured data and performance. Separate observed findings from recommendations.The output should include the URL or evidence supporting every finding. A model should not claim that a page is blocked, indexed or fast without performing the relevant check.
Full SEO audit
Use seo-audit when a broad site review is required.
Define the scope before starting:
- domain or hostname;
- maximum pages;
- public pages only or authenticated areas;
- mobile, desktop or both;
- whether external services are permitted;
- whether the result is read-only;
- expected report format.
Example:
Use seo-audit to inspect [SITE_URL]. Crawl public pages only, do not submit forms, do not log in, and return a prioritised report with evidence and validation steps.Do not let a crawler access private areas, administrative paths or customer data without explicit authorisation.
Single-page analysis
Use seo-page when one URL needs a deep review.
Check:
- title;
- meta description;
- canonical;
- robots directives;
- headings;
- content intent;
- internal links;
- images and alt text;
- structured data;
- mobile and performance signals.
Example:
Use seo-page to analyse [PAGE_URL]. Return findings under technical, content, structured data, links, images and performance.Schema and sitemaps
Use seo-schema for JSON-LD and structured data. Use seo-sitemap for XML sitemap validation or generation.
Example:
Use seo-schema to validate this JSON-LD. Identify syntax errors, invalid properties, missing required fields and misleading values. Do not invent business information.Use seo-sitemap to inspect [SITEMAP_URL]. Report invalid URLs, redirects, non-canonical URLs, status errors and structural problems.Structured data must represent the visible and verifiable content on the page. Do not add schema simply because a type might generate a rich result.
Content and content briefs
Use seo-content for existing content quality and seo-content-brief for planning a new or improved page.
The skill should consider:
- search intent;
- audience;
- first-hand experience;
- accuracy;
- topical coverage;
- clarity;
- internal links;
- evidence and citations;
- useful differentiation;
- thin or duplicated content.
Example:
Use seo-content to review this page for clarity, topical coverage, experience, expertise, authority and trust. Do not rewrite it yet.Use seo-content-brief to create a brief for [TOPIC] targeting [AUDIENCE]. Include search intent, page structure, evidence requirements, internal links and validation criteria.Do not equate word count with quality. A longer page is not automatically a better page.
Local SEO and maps
Use seo-local or seo-maps for businesses that serve a location or service area.
Review:
- business name, address and phone consistency;
- location pages;
- business categories;
- opening hours;
- reviews and responses;
- local schema;
- geographic relevance;
- duplicate or doorway pages.
Do not invent a business address, service area, review or ranking position.
Backlinks and competitors
Use seo-backlinks for link-profile analysis and seo-competitor-pages for comparison or alternative pages.
Backlink analysis needs real link data. A model cannot know the complete backlink profile from the domain name alone.
Competitor pages should be based on verified competitor information, not assumed features or invented comparisons.
GEO and AI search
Use seo-geo when the task concerns visibility in AI-powered search experiences.
Review:
- whether important content is accessible;
- whether pages are indexable;
- clear answer passages;
- entity information;
- attribution and supporting evidence;
- structured data;
- crawler access where relevant.
Do not promise placement in ChatGPT, Google AI features or another platform. AI search results change and depend on factors outside the skill.
Data and tool requirements
Some SEO skills can operate using public pages and local analysis. Others benefit from live services.
Possible dependencies include:
- browser or crawler;
- PageSpeed Insights;
- Search Console;
- Google Analytics;
- DataForSEO;
- backlink provider;
- image processing tools;
- MCP server;
- API credentials.
The skill must state which data was actually available.
Use this format in reports:
Checked directly:
- [Observed check]
Not available:
- [Missing API, credential or private data]
Inference:
- [Clearly labelled interpretation]Read-only first
SEO audits should normally begin read-only.
Do not:
- submit forms;
- create accounts;
- publish content;
- edit a CMS;
- change metadata;
- submit URLs for indexing;
- build backlinks;
- post to social platforms;
- access authenticated areas without permission.
An audit and an implementation task are separate requests.
Example SEO skill metadata
---
name: seo-technical
description: Audit a website's crawlability, indexability, redirects, security headers, structured data and performance when the user requests a technical SEO review.
---
# Technical SEO
1. Confirm the site URL and audit scope.
2. Fetch public technical resources read-only.
3. Inspect redirects, robots.txt, sitemap references, metadata and structured data.
4. Separate observations from recommendations.
5. Cite evidence for each finding.
6. Return priorities, impact, effort and validation steps.
7. Do not change the website or claim access to unavailable data.Copyright and attribution
The SEO skill family in this package was adapted from AgriciDaniel/claude-seo.
When redistributing the adapted files:
- retain the original MIT license;
- credit Agrici Daniel and relevant contributors;
- keep the original repository link;
- record the source version or commit;
- describe local modifications;
- do not imply endorsement;
- keep third-party extensions under their own terms.
Do not claim that the skill library is an official product of AgriciDaniel, Google, OpenAI, Anthropic or any other third party.
Who benefits from SEO skills?
Website owners
They get a repeatable way to identify technical and content problems.
SEO specialists and agencies
They can standardise audits and reduce repetitive manual checks.
Developers
They receive clearer technical requirements and validation steps.
IT managers
They can connect website findings to hosting, security, deployment and monitoring work.
Local businesses
They can identify problems with location pages, business information and local visibility.
Limits
SEO skills cannot guarantee rankings, traffic or AI citations.
They cannot know private analytics, Search Console data or backlinks without access to those systems.
They cannot replace human review of business claims, legal content, medical advice or financial information.
They can improve the process by making the checks repeatable and the evidence easier to review.
Download
The pack contains 25 Markdown skill folders. It was adapted from a Claude Code-oriented source and includes host-compatibility notes. Claude-specific commands, MCP names and extension references are not guaranteed to work in another tool. Use only the tools and permissions available in your environment.
