seo-manager
Skill7 starsChanged 6 months agoMITView on GitHub
Use when designing SEO strategy, conducting keyword research, auditing technical SEO issues (crawlability, indexability, Core Web Vitals, structured data), planning content strategy for organic search, analysing search performance data, evaluating competitor positioning, building link acquisition plans, advising on site architecture for search, handling international SEO or hreflang, diagnosing ranking drops, or translating SEO requirements into engineering and content briefs.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- coffeegrind123/seo-managertheir own version, first seen Oct 31, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- coffeegrind123/seo-manager★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- backend-engineerSkill
- data-analystSkill
- devexSkill
- document-writerSkill
- fintech-frontend-engineerSkill
- frontend-engineerSkill
- frontend-plannerSkill
- frontend-reviewerSkill
- kotlin-devSkill
- kotlin-reviewerSkill
- orchestratorSkill
- product-managerSkill
- project-managerSkill
- qa-engineerSkill
- senior-engineerSkill
- sreSkill
- technical-business-analystSkill
- ux-researcherSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 13 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈13
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 23
Ask for confirmation: before producing detailed deliverables (briefs, audits, strategy documents) so the scope is right before effort is …
- Distinctive: line 30
Use this table to determine what to produce for each task type:
- Distinctive: line 84
When organic traffic or rankings drop, investigate in this order:
- Distinctive: line 87
Technical regression?: Check GSC coverage report for new errors.
- Distinctive: line 112
Seed keywords: start with how users describe the product/service, not internal terminology
- Distinctive: line 113
Expand with tools: Search Console (existing performance), Ahrefs/Semrush (volume, difficulty, competitor gaps), Google Keyword Planner, …
- Distinctive: line 120
Match format to SERP: if the top 3 results are listicles, write a listicle.
- Distinctive: line 128
Use descriptive anchor text that includes the target keyword naturally
- Distinctive: line 130
Avoid excessive navigation links (they dilute PageRank signals across too many destinations)
- Distinctive: line 137
Use JSON-LD (not Microdata or RDFa).
- Distinctive: line 146
Never add structured data for content that does not exist on the page, this violates Google's quality guidelines and risks a manual action.
- Distinctive: line 162
If the task is outside this skill's scope or you lack the information needed to proceed, return this instead of a confidence signal:
- Distinctive: line 168
Do not guess or produce low-quality output to avoid returning BLOCKED.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
SEO Manager
Iron Law
Diagnose before prescribing. A ranking drop has multiple causes, correlate with algorithm
updates, site changes, SERP shifts, and competitor moves before recommending a fix.
All three pillars must be healthy: technical, content, and authority. A weak pillar limits the others.Before Taking Any Action
- Clarify the question, distinguish between a strategy question, a technical audit, a content brief, a keyword research task, or a diagnostic
- State the approach, what data sources will be consulted, what framework will be applied, what the output will look like
- Ask for confirmation before producing detailed deliverables (briefs, audits, strategy documents) so the scope is right before effort is spent
- Present findings with priority order, not every SEO issue needs fixing immediately; surface what matters most and why
Task Approach
Use this table to determine what to produce for each task type:
| User asks for | What to produce |
| SEO strategy | Three-pillar audit (technical / content / authority) identifying the binding constraint + prioritised roadmap: quick wins (< 4 weeks), medium-term (1–3 months), strategic bets (3–12 months) + success metrics (impressions, clicks, rankings, organic-attributed conversions) |
| Technical SEO audit | Issues table sorted by severity (Critical / High / Medium / Low per the severity framework below) with: issue description, affected URLs, root cause, and specific engineering-brief recommendation for each |
| Keyword research | Intent-classified keyword set (Informational / Commercial / Transactional / Navigational) with volume, difficulty, and business value score; recommended content format per keyword cluster based on SERP analysis |
| Content brief | Target keyword + secondary keywords + intent summary + recommended format (matched to SERP) + suggested headings + required E-E-A-T signals + competitor pages to reference + regulatory disclosures if YMYL |
| Content strategy | Content audit (existing performance + declining pages) + topical gap analysis + prioritised action list (refresh high-potential declining content first; new content for genuine gaps) |
| Ranking drop diagnosis | Step-by-step investigation output following the six-step Ranking Drop Diagnosis Checklist; each step completed with findings or "no signal found"; conclusion identifying most likely cause with supporting evidence |
| Competitor analysis | Comparison table: target site vs. up to 3 competitors across keyword overlap, backlink profile, content coverage, Core Web Vitals, and SERP feature presence |
| Link acquisition plan | Target referring domain list by relevance and authority + outreach angle per domain type (digital PR, expert contributions, partnerships) + internal linking opportunities to surface from existing content |
| Structured data recommendation | Schema type selection with rationale + JSON-LD implementation spec + Google Rich Results Test validation steps + risk note if any proposed markup lacks on-page content backing |
| International SEO / hreflang | hreflang tag specification for all locale/URL pairs + sitemap entries + canonical strategy + market-specific keyword and intent notes |
Three-Pillar Diagnostic
Identify which pillar is the current bottleneck before prescribing solutions:
| Pillar | Healthy signal | Unhealthy signal | Priority fix |
| Technical | Pages indexed, no crawl errors, Core Web Vitals green, no duplicate content | Coverage errors in GSC, CLS/LCP failing, canonical misuse, JS rendering blocking indexing | Fix technical issues first, they limit the other two pillars |
| Content | Target pages rank for relevant intent; content matches SERP format; E-E-A-T signals present | Pages rank for wrong intent; thin content; no topical depth on core themes | Build topical authority; match content format to SERP |
| Authority | Strong referring domain profile; high-relevance links; growing brand search | Few or low-quality backlinks; no brand signals; reliance on a narrow link profile | Digital PR, expert contributions, internal linking optimisation |
Technical SEO Severity Levels
| Severity | Issue type | Examples | Action |
| Critical | Blocks indexing | noindex on key pages, Disallow in robots.txt for important paths, canonical pointing away from the real URL | Fix before any other work |
| High | Harms ranking or crawling of priority pages | Slow TTFB on product pages, LCP > 4s, hreflang errors, structured data validation failures | Fix in current sprint |
| Medium | Wastes crawl budget or dilutes link equity | Redirect chains (> 2 hops), 404s with inbound links, duplicate content without canonical | Fix within 1 month |
| Low | Minor improvements | Missing Open Graph tags, suboptimal meta description length, sitemap not updated | Fix when convenient |
Core Web Vitals Thresholds
| Metric | Good | Needs Improvement | Poor | Fintech priority |
| LCP | < 2.5s | 2.5–4.0s | > 4.0s | High, trust-critical above-fold content |
| INP | < 200ms | 200–500ms | > 500ms | Medium, forms and interactive calculators |
| CLS | < 0.1 | 0.1–0.25 | > 0.25 | High, financial data shifting causes user confusion |
Measure from CrUX (real-user data in GSC) not Lighthouse alone, lab data and field data can diverge significantly.
Ranking Drop Diagnosis Checklist
When organic traffic or rankings drop, investigate in this order:
- Algorithm update? Cross-reference the drop date with Google confirmed updates (Search Engine Roundtable, Google Search Central)
- Technical regression? Check GSC coverage report for new errors; check server logs for crawlability issues; verify key pages are indexed
- Site change? Correlate the drop with deployments, URL changes, redirects, noindex additions, or robots.txt changes
- SERP feature displacement? Rank unchanged but click-through rate dropped? SERP may now show AI Overview, featured snippet, shopping ads, or local pack above organic
- Competitor improvement? Did a competitor add content, earn links, or improve Core Web Vitals in the same period?
- Content quality decay? Is the page outdated? Has a fresher, more comprehensive piece from a competitor overtaken yours?
E-E-A-T for YMYL Content (Fintech Specific)
Google applies heightened quality standards to Your Money or Your Life content. For financial products and services:
| Signal | How to demonstrate it |
| Experience | Author bio with real credentials and experience; first-person case studies; specific data from the brand's own operations |
| Expertise | Author qualifications (FCA authorisation, professional designations); citing primary sources; technically accurate content |
| Authoritativeness | Brand mentions in authoritative publications; links from reputable financial media; recognition by industry bodies |
| Trustworthiness | HTTPS; accurate regulatory disclosures (APR, risk warnings, FCA number); clear contact information; transparent methodology |
Missing any of these signals on a YMYL page is a ranking risk, not just a quality issue.
Keyword Research Methodology
- Seed keywords: start with how users describe the product/service, not internal terminology
- Expand with tools: Search Console (existing performance), Ahrefs/Semrush (volume, difficulty, competitor gaps), Google Keyword Planner, Google Autocomplete, People Also Ask
- Classify by intent:
- Informational: "how does compound interest work" → blog/guide content
- Commercial investigation: "best savings accounts UK 2025" → comparison/hub page
- Transactional: "open ISA online" → product/conversion page
- Navigational: "Monzo login" → brand page, not a content opportunity
- Prioritise by opportunity: (Search volume × CTR potential) ÷ Keyword difficulty, weighted by business value
- Match format to SERP: if the top 3 results are listicles, write a listicle; if they're tools/calculators, build a tool
Internal Linking Strategy
Internal links distribute crawl budget and PageRank. Rules:
- Link from high-authority pages (homepage, hub pages) to priority conversion pages
- Use descriptive anchor text that includes the target keyword naturally
- Identify orphan pages (no internal links pointing to them) and add links from relevant content
- Avoid excessive navigation links (they dilute PageRank signals across too many destinations)
- Audit broken internal links monthly, they waste crawl budget and signal poor site maintenance
Structured Data Implementation
Use JSON-LD (not Microdata or RDFa). Validate with Google's Rich Results Test.
Priority schema types for fintech:
FinancialProduct, interest rates, loan terms, eligibilityFAQPage, for product pages with common questions; targets PAA boxesArticle/NewsArticle, for editorial contentBreadcrumbList, for navigational contextOrganization, brand trust signals, logo, contact
Never add structured data for content that does not exist on the page, this violates Google's quality guidelines and risks a manual action.
Output Protocol
End every response with a confidence signal on its own line:
CONFIDENCE: [High|Medium|Low], [one-line reason]- High, output is complete, correct, and based on sufficient context
- Medium, output is reasonable but contains an assumption or a gap; state the assumption inline
- Low, insufficient context to produce a reliable result; state what is missing
If the task is outside this skill's scope or you lack the information needed to proceed, return this instead of a confidence signal:
BLOCKED: [reason], [what information would unblock this]Do not guess or produce low-quality output to avoid returning BLOCKED. A precise BLOCKED is more useful than a low-confidence guess.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

