seo-audit
Skill2 starsChanged yesterdayMITView on GitHub
Audit a website's SEO health and diagnose traffic drops: crawl the site for technical issues (broken pages, redirects, duplicate or missing titles, noindex, canonicals, thin content, orphan pages), check indexing in Google Search Console, compare Search Console periods to find which pages and queries lost clicks, and rank the fixes by impact. Use when the user asks to audit their site, run an SEO check or health check, find technical SEO problems, asks why traffic, clicks, or rankings dropped, or why a page is not indexed.
185 other projects use a version of this.
Adopted by
Most recently taken up by
- samsam007b/claude-code-standards-kittheir own version, first seen Nov 16, 2026
- vincentventalon/claude-code-video-editing-skilltheir own version, first seen Nov 15, 2026
- vincentventalon/my-claude-skillstheir own version, first seen Nov 15, 2026
- serejaris/personal-corp-ostheir own version, first seen Nov 15, 2026
- vercel/evetheir own version, first seen Nov 15, 2026
- joaoguirunas/team-ostheir own version, first seen Nov 15, 2026
Used with
Projects with it also use openseo-review-web-content, openseo-release-notes and 8 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
JwuthriSkillopenseo-review-web-content
Write and review content for the OpenSEO website (web/) — blog posts, guides, feature pages, FAQs. Distills the philosophy for on-brand, useful, accurate content. Use whenever adding or editing user-facing prose in web/content or web/src.
Also in 5 projects that use this
JwuthriSkillopenseo-release-notes
Cut an OpenSEO release — bump the version, draft user-facing release notes from commits since the last tag, run a review + subagent-verification pass, and open a "release: vX.X.X" PR. Use when the user asks to prepare a release, bump the version, or write release notes.
Also in 6 projects that use this
nicepkgSkillcommunity-led-growth
Expert in community-led growth (CLG) - leveraging user communities to drive acquisition, retention, and expansion. Covers building developer communities, user groups, ambassador programs, and turning customers into advocates. Knows the difference between community as a feature vs community as a growth engine, and how to measure community ROI. Use when "community-led, CLG, ambassador program, champion program, user community, developer community, word of mouth, user group, " mentioned.
Also in 5 projects that use this
nicepkgSkillph-community-outreach
Engage Reddit, Indie Hackers, Hacker News and other communities for Product Hunt launches. Use this skill to identify relevant communities, craft appropriate posts, and drive cross-platform engagement without appearing spammy.
Also in 5 projects that use this
xfstudioSkillmicro-saas-launcher
Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software. Covers idea validation, MVP development, pricing, launch strategies, and growing to sustainable revenue. Ship in weeks, not months. Use when: micro saas, indie hacker, small saas, side project, saas mvp.
Also in 5 projects that use this
- +4 more from nicepkg
- +1 more from Jwuthri
Other versions185 projects use a version of this.
Word for word · 1
- winsley-jeune/harborrank-skills★ 2100% same
Edited · 0
None found.
Wrote their own version · 184
- coreyhaines31/marketingskills★ 61ksame name
- anthropics/knowledge-work-plugins★ 36ksame name
- AgriciDaniel/claude-seo★ 30ksame name
- every-app/open-seo★ 28ksame name
- trycompai/crm★ 12ksame name
- Ryze-AI-Adgent/open-seo-mcp-skills★ 8.4ksame name
- TheCraigHewitt/seomachine★ 7.5ksame name
- vercel/eve★ 5.9ksame name
- legions-developer/evilcharts★ 3.2ksame name
- MaxMiksa/Auto-Company★ 3.2ksame name
174 more not listed
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 repository17 other files it gives its agents.
- ai-search-visibilitySkill
- client-seo-reportSkill
- competitive-landscapeSkill
- competitor-analysisSkill
- content-briefSkill
- google-business-profileSkill
- keyword-cannibalizationSkill
- keyword-clusteringSkill
- keyword-researchSkill
- lead-teardownSkill
- link-prospectingSkill
- local-seoSkill
- schema-markupSkill
- seo-coachSkill
- seo-contextSkill
- seo-project-setupSkill
- seo-proposalSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
31 rules. 0 are common, 13 are distinctive, and 18 are very specific to this project.
0
Common
Most of the 164 edited versions we read keep these.
13
Distinctive
This author's own choices. Worth a look.
18
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Traffic-drop diagnosis: use Search Console to find when clicks fell, which pages and queries lost them, and why.
- Distinctive: line 15
If the user asks about a drop, start with the diagnosis and run the crawl only where it helps explain the losing pages.
- Very specific: line 21
If neither tool is available, or whoami fails because the user is not signed in, tell the user plainly: "HarborRank isn't connected, so I …
- Distinctive: line 32
Do not stop there. Continue in fallback mode (below).
- Very specific: line 40
If creditsRemaining will not cover the planned calls, give the user the estimate and ask before spending.
- Very specific: line 42
If a tool fails for insufficient credits, stop making paid calls, tell the user, and finish with free tools and the data you already have.
- Very specific: line 44
If the user asks to upgrade, change plan or buy credits, call get_upgrade_link (no credits) and give them the link.
- Very specific: line 45
When whoami returns mode: "self-hosted", there are no plan gates.
- Distinctive: line 49
Use this mode only when Step 0 finds no connection.
- Distinctive: line 53
Read the homepage and key pages: titles, meta descriptions, headings, canonical tags, robots meta, and internal links.
- Very specific: line 54
Read robots.txt and the XML sitemap, and spot-check sitemap URLs for errors or redirects.
- Distinctive: line 64
Start with the label Web-evidence only: no HarborRank data.
- Very specific: line 70
If the project's SEO folder has seo-context.md (see seo-context), read it first for the site, market, audience, competitors and goals, and …
- Very specific: line 92
Call list_projects and pick the project for the site.
- Very specific: line 93
Call run_site_audit. Keep the default 50 pages for a quick check.
- Very specific: line 94
Call get_audit_status until the audit is completed.
- Very specific: line 95
Call get_audit_issues with severity: "critical", then with severity: "warning".
- Very specific: line 97
Call inspect_urls for up to 10 URLs that matter most: top pages by clicks, plus pages flagged noindex-page, canonicalized-page, …
- Distinctive: line 103
Search Console is required for this mode.
- Very specific: line 105
Call get_search_console_performance with dimensions: ["date"] and dateRange: "last_6_months" (or last_16_months for a long view) to see …
- Very specific: line 106
If Google Analytics is connected, also call get_analytics_report with dimensions: ["sessionDefaultChannelGroup"], metrics: ["sessions", …
- Distinctive: line 113
Everything fell at once, sitewide: look for a technical cause first (robots.txt, noindex, a migration, redirects), then a Google update.
- Very specific: line 114
Call inspect_urls on the top losing pages to check indexing, canonical, and last crawl.
- Very specific: line 115
If a technical cause is possible, run Workflow A steps 2 to 4, then call get_audit_pages with urlContains for the losing pages to see their …
- Very specific: line 116
If position fell on important queries, call get_serp_results for the top 1 to 3 lost queries (ask first.
- Very specific: line 130
Use the how_to_fix from the issue report in the Fix column, rewritten for this site.
- Distinctive: line 134
Timeline: when it started, how big it is (clicks and impressions, before vs after), and whether it is sitewide or concentrated.
- Distinctive: line 152
Never invent a site health score or grade.
- Distinctive: line 153
Do not blame a Google update without evidence.
- Distinctive: line 155
If the crawler was blocked, report the pages as blocked and say the audit could not see them.
- Distinctive: line 156
Do not report Lighthouse or page-speed findings on the Free plan.
“Common” is measured: kept by at least 6 in 10 of the 164 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
HarborRank SEO Audit
Goal
Find what is holding a site back in search and fix the most important things first. Two modes, often used together:
- Health audit: crawl the site, read the issue report, check indexing for the pages that matter, and produce a prioritized fix list.
- Traffic-drop diagnosis: use Search Console to find when clicks fell, which pages and queries lost them, and why.
If the user asks about a drop, start with the diagnosis and run the crawl only where it helps explain the losing pages.
Step 0: Check connection
Before any other step, confirm the HarborRank MCP tools are loaded. Look for get_domain_overview or list_leads among your tools, including deferred tools you can load (the name may carry a prefix such as mcp__harborrank__). If they are there, call whoami: it uses no credits, confirms the user is signed in, and returns creditsRemaining for budgeting the run. Do not call a research tool to test the connection.
If neither tool is available, or whoami fails because the user is not signed in, tell the user plainly: "HarborRank isn't connected, so I can't pull live HarborRank data yet." Then tell them how to connect it:
- Claude Code with the HarborRank plugin: run
/mcp, chooseharborrank, and sign in. - Claude Code without the plugin: run
claude mcp add --transport http --scope user harborrank https://app.harborrank.com/mcp, then/mcpto sign in. - Claude on the web, desktop or Cowork: open Customize, then Connectors, search for HarborRank, choose Connect, and sign in. New accounts start with a 7-day free trial.
- Cursor with the HarborRank plugin: open Cursor Settings, then MCP, and sign in to
harborrank. - Gemini CLI with the HarborRank extension: run
/mcp auth harborrank. - Other clients: add
https://app.harborrank.com/mcpas a remote MCP server. Setup for each client is at https://harborrank.com/docs/mcp.
Tell them what happens when they connect: they sign in to HarborRank with Google or email and start a 7-day free trial. Then they come back to this conversation and say "connected", and you pick up the task where it stopped.
Do not stop there. Continue in fallback mode (below). If the user connects HarborRank mid-task, run Step 0 again and switch to the full workflow.
Plan limits
On hosted HarborRank, research tools spend credits. New accounts start with a 7-day free trial (1,000 research credits, one project); paid plans start at $29/month with 15,000 credits. Search Console, saved keywords, rank tracker reads, and site crawls use no credits. A keyword search costs about 50 credits and a domain overview about 80. Full backlinks, lead research (research_lead), and Lighthouse checks need a paid plan; on Free, the backlinks tools return a preview (totals and the top 3 referring domains, about 50 credits) with an upgrade link.
Most of this audit is free: the crawl, the issue report, Search Console performance, and URL inspection use no credits. Only the optional live-search checks spend credits. On Free the crawl covers up to 500 pages and skips Lighthouse.
- If
creditsRemainingwill not cover the planned calls, give the user the estimate and ask before spending. Use the free tools first. - If a tool replies that a feature "is included in paid plans", tell the user once which feature needs a paid plan and pass on the upgrade link from the reply, skip that tool for the rest of the run, and finish with the other evidence. Do not retry it.
- If a tool fails for insufficient credits, stop making paid calls, tell the user, and finish with free tools and the data you already have. If
whoamiwarns that credits are low, say so before a large run. - If a HarborRank tool says the free trial hasn't started, or that credits ran out, give the user the link from that reply exactly as written, as a clickable link, and wait for them to say they're done before calling HarborRank again. Don't switch to answering without HarborRank data unless they ask you to.
- If the user asks to upgrade, change plan or buy credits, call
get_upgrade_link(no credits) and give them the link. They pay on HarborRank by card; never say the upgrade is done untilwhoamishows the new plan. - When
whoamireturnsmode: "self-hosted", there are no plan gates.
Fallback mode (no HarborRank connection)
Use this mode only when Step 0 finds no connection. It works from web search, page reading, and files the user provides.
Can still do
- Read the homepage and key pages: titles, meta descriptions, headings, canonical tags, robots meta, and internal links.
- Read
robots.txtand the XML sitemap, and spot-check sitemap URLs for errors or redirects. - Review the user's Search Console CSV exports (Pages, Queries, Dates, Indexing reports), if provided, to find what dropped and when.
- Frame findings as a sample of pages, not a full crawl.
Must not estimate
Traffic, clicks, impressions, search volume, keyword difficulty, keyword counts, rankings, backlink counts, Maps pack positions, and Q&A counts. Write unknown for each. A web search shows which pages appeared for a query when you searched, not their Google ranking: report it as "appeared in web search", never as a position. Do not claim a page is or is not indexed from a web search.
Output
- Start with the label Web-evidence only: no HarborRank data.
- Name the source (URL or file) of every figure you report.
- End, after any recommended next workflow, with one sentence that names the numbers this report is missing: "Connect HarborRank (start with a 7-day free trial) to crawl the whole site and add your Search Console clicks and indexing status." Do not add more sales copy than that.
Required inputs
If the project's SEO folder has seo-context.md (see seo-context), read it first for the site, market, audience, competitors and goals, and ask only for what it doesn't cover.
projectId(fromlist_projects)- The site URL to audit (default: the project's domain)
- For a traffic drop: the approximate date it started, if the user knows it
HarborRank MCP tools
run_site_audit: crawls the site with HarborRank's crawler (robots.txt-aware) and checks every page for SEO issues. Free.maxPagesdefaults to 50;runLighthouseapplies on paid plans only.get_audit_status: progress of a running audit. Free.get_audit_issues: the prioritized issue report; every issue carries ahow_to_fix. Filter byseverity(critical,warning,info) orissueType. Free.get_audit_pages: crawled pages with status code, title, description, word count, indexability, depth, and links. Filter byfetchClass,statusCode, orurlContains. Free.get_search_console_performance: clicks, impressions, CTR, and average position byquery,page,country,device, ordate, for adateRangeor explicitstartDate/endDate, with optional filters. Free.inspect_urls: Google's URL Inspection for up to 10 URLs: indexed or not and why, last crawl, Google-selected vs declared canonical. Free.get_landing_page_performance: Search Console clicks and position joined with Google Analytics organic sessions, engagement, key events (conversions) and revenue per landing page; also lists pages that earn Google clicks but never show up in Analytics (broken tracking). Needs Google Analytics connected for the project.get_analytics_report: Google Analytics sessions, users, engagement and key events by channel, landing page, source, device, country or date, with optionalcompareTo(previous_periodorprevious_year). Needs Google Analytics connected.get_serp_results: live Google results for up to 10 keywords, to see who took a lost query or which SERP features appeared. Charges credits (about 30 to 60 per keyword).get_domain_overview: organic footprint estimate, for a site without Search Console. Charges credits.create_share_report: publish the finished work as a read-only page at a shareable link (see "Shareable report" below). Only after the user agrees.
Workflow A: Health audit
- Call
list_projectsand pick the project for the site. Use its domain as the start URL unless the user names another. - Call
run_site_audit. Keep the default 50 pages for a quick check; for a full audit of a larger site ask before going above 500 pages, and say Free crawls stop at 500. - Call
get_audit_statusuntil the audit iscompleted. Wait between checks rather than calling it back to back. - Call
get_audit_issueswithseverity: "critical", then withseverity: "warning". Readinfoissues only if there is little else to fix. - If Search Console is connected, call
get_search_console_performancewithdimensions: ["page"]anddateRange: "last_3_months". Use clicks per page to rank the fixes: an issue on a page with clicks comes before the same issue on a page with none. If Google Analytics is connected, callget_landing_page_performanceinstead: it returns the same clicks plus conversions per page, so an issue on a page that converts comes first, and any page inpagesMissingFromAnalyticsis a tracking fix to report. - Call
inspect_urlsfor up to 10 URLs that matter most: top pages by clicks, plus pages flaggednoindex-page,canonicalized-page,canonical-conflict, orblocked-page. Confirm what Google actually indexed instead of assuming. - Group issues that share one cause. Duplicate titles across 200 pages from one template are one fix, not 200.
- Rank the fixes: indexing and crawl blockers first (blocked, server errors, broken pages, noindex or canonical mistakes on pages that should rank), then problems on high-click pages, then sitewide template fixes, then everything else.
Workflow B: Traffic-drop diagnosis
Search Console is required for this mode. If it is not connected, say so, point the user to the project's Integrations page in the HarborRank app (it is free), and run Workflow A meanwhile.
- Call
get_search_console_performancewithdimensions: ["date"]anddateRange: "last_6_months"(orlast_16_monthsfor a long view) to see when clicks and impressions changed. Use the user's date if they gave one, and confirm it in the data. If Google Analytics is connected, also callget_analytics_reportwithdimensions: ["sessionDefaultChannelGroup"],metrics: ["sessions", "keyEvents"]andcompareTo: "previous_period"over the same dates. If only Organic Search fell, it is a search problem; if every channel fell at once, suspect broken tracking or a site outage before rankings. - Pick two windows of equal length and the same weekdays: the weeks before the drop and the weeks after it. Do not include the last 3 days, which are incomplete.
- For each window, call
get_search_console_performancewith explicitstartDateandendDate, first withdimensions: ["page"], then withdimensions: ["query"]. List the pages and queries with the largest click losses. - Classify each big loss by what moved:
- Impressions fell, position held: less demand or seasonality, or the page dropped out of the index. Check last year's same period if the data covers it.
- Position fell: ranking loss to competitors, or a content or technical change on the page.
- Position held, CTR fell: a SERP change (an AI Overview, new features, ads) or a worse title or snippet.
- Everything fell at once, sitewide: look for a technical cause first (robots.txt, noindex, a migration, redirects), then a Google update.
- Call
inspect_urlson the top losing pages to check indexing, canonical, and last crawl. - If a technical cause is possible, run Workflow A steps 2 to 4, then call
get_audit_pageswithurlContainsfor the losing pages to see their status codes and indexability. - If position fell on important queries, call
get_serp_resultsfor the top 1 to 3 lost queries (ask first; it uses credits) to see who ranks now and which SERP features appeared.
Output format
Start with:
- Verdict: one or two sentences, for example "Two critical problems, both fixable this week" or "Clicks fell 38% from Aug 12, concentrated on 6 blog posts that lost position to two competitors."
- Top 3 fixes, in order.
For a health audit, then include:
| Priority | Issue | Pages affected | Evidence | Fix | Effort |
Use the how_to_fix from the issue report in the Fix column, rewritten for this site. Effort is quick, moderate, or project.
For a traffic drop, then include:
- Timeline: when it started, how big it is (clicks and impressions, before vs after), and whether it is sitewide or concentrated.
- What lost traffic:
| Page or query | Clicks before | Clicks after | Change | What moved | Likely cause |
- Causes: each cause with its evidence, labelled confirmed or likely.
- Fixes: in priority order.
Close both with what was not checked (pages beyond the crawl budget, Lighthouse on Free, queries without Search Console data).
- Next workflow: end with one recommended next workflow, the reason for it, and the input it starts from. If competitors took the lost queries, recommend
competitor-analysison the domain that gained. If pages compete for the same queries, recommendkeyword-clusteringon those queries. Otherwise recommendkeyword-researchon the striking-distance queries (positions 5 to 20) from Search Console. - Check back: end with one dated follow-up: the date (today plus 14 days, written out, for example "Monday, November 9") and the exact question to ask then: "Did Google pick up the audit fixes on
<domain>?" For a traffic drop, ask instead: "Did clicks come back on the pages that dropped?" Say in one line why it needs that wait: Google recrawls fixed pages over one to two weeks, and the re-check (a new crawl, URL inspection and Search Console) uses no credits. Add it to theFollow-upslist in the SEO folder'sREADME.md(create the list if it is missing) so the next session finds it. One follow-up only; don't add reminders or repeat it. If scheduled tasks are available (Cowork and the Claude apps on paid plans), offer once to make this a weekly scheduled task instead, named for the site, so the check runs by itself; the user reviews and confirms the schedule. - Where the output goes: the report as
audits/<domain>-<YYYY-MM-DD>.md. Save it in the project's SEO folder (seeseo-project-setup); if there is none, ask once whether to create one or where to save instead. If the user prefers a doc or a sheet and a docs or spreadsheet tool is available, put reports in a doc and tables in a sheet instead. Tell the user where it was saved. - Shareable report: once the work is done, offer one time to publish it as a shareable report with
create_share_report: a read-only page at a link the user can send to a client, a boss or a teammate, no sign-in needed. Write it from this output: findings first, then next steps, then the supporting table. Publish only after the user says yes, and leave out their Search Console and Google Analytics numbers unless they agree to share them. Give them the link;delete_share_reportremoves it.
Guardrails
- Never invent a site health score or grade. Report counts of issues by severity, as the audit gives them.
- Do not blame a Google update without evidence. Say a drop is "consistent with" an update only when its timing matches and no technical or competitive cause explains it better.
- Compare windows of equal length and matching weekdays, and leave out the last 3 days of Search Console data. Search Console dates are Pacific Time.
- If the crawler was blocked, report the pages as blocked and say the audit could not see them; do not treat them as broken.
- Do not report Lighthouse or page-speed findings on the Free plan; the crawl skips Lighthouse there.
- Separate evidence from inference: every cause needs the numbers or the inspection result behind it.
- Recommend changes, never make them. Ask before any write action.
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.

