check-seo
Skill2 starsChanged 8 months agoMITView on GitHub
Run a focused SEO audit with content quality analysis and actionable recommendations.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- nguyenthanhtat/screen1-claudetheir own version, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- nguyenthanhtat/screen1-claude★ 2same 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 repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- check-integrationsSkill
- compare-sitesSkill
- find-dead-linksSkill
- find-revenue-leaksSkill
- generate-analytics-specSkill
- growth-auditSkill
- growth-diffSkill
- map-funnelSkill
- suggest-schemaSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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 8
Run a focused SEO audit combining technical checks with content quality analysis.
- Distinctive: line 17
Run the SEO-focused scan:
- Distinctive: line 27
Add AI content quality analysis:
≈ “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
/check-seo
Run a focused SEO audit combining technical checks with content quality analysis.
Usage
/check-seo <url>Instructions
- Run the SEO-focused scan:
cd /Users/sdm/Desktop/GrowthLint && python3 -c "import growthlint.cli; growthlint.cli.app()" -- scan "$URL" --categories seo --format json --fix- Also run schema suggestions:
cd /Users/sdm/Desktop/GrowthLint && python3 -c "import growthlint.cli; growthlint.cli.app()" -- suggest-schema "$URL"- Add AI content quality analysis:
- Title tag quality: Is it compelling? Does it include a keyword AND create curiosity? Would you click this in search results?
- Meta description quality: Does it sell the click? Does it have a call to action?
- H1 effectiveness: Does it match search intent? Is it specific enough?
- Content depth: Is there enough content for the topic? Are key subtopics covered?
- Internal linking opportunities: Based on the page structure, what internal links could strengthen topical authority?
- Schema recommendations: Which schema types would unlock rich results for this specific content?
- Provide specific rewrite suggestions for title, meta description, and H1.
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.

