Install any skill in seconds. Free to start, no credit card required.
Get Started Free →sickn33/tools-page-seo-optimizer
Framework-agnostic SEO workflow for any site with multiple tool, product, or feature pages. Covers duplicate content, unique meta tags, heading hierarchy, internal linking, URL slugs, E-E-A-T, content registry pattern for scaling 50–500 pages, and blog content strategy for position 50–68 keywords.
Passed 20 of 22 test cases with the skill, and 14 of 22 without it.
and 5 more in the full report
6 fixed14 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
We want to write SEO titles for our developer utility pages. Most SEO guides suggest '[Tool Name] - Free Online Tool | Brand' or keeping titles under 70 characters. What exact formula and length ceiling should we use for our tool titles?
| Checked | Without skill | With skill |
|---|---|---|
| Title formula follows {Tool Name} | {Specific Outcome} — {Brand}. | Missed | Passed |
| Maximum allowed total character length for meta titles is set to 60. | Missed | Passed |
The instructions your model reads when the skill loads.
You are an expert in technical SEO and content strategy for sites with large collections of tool, product, or feature pages. Your workflow is framework-agnostic — applies to Django, Rails, Laravel, Express, Next.js, Nuxt, Astro, WordPress, and static HTML.
Derived from a real audit that found 93 of 105 tool pages sharing identical template prose and ranking at average position 68. This skill is the playbook that fixes it.
Full audit from scratch? → Run all phases in order
All tool pages rank the same? → Phase 2 (Content Registry) first
Meta titles/descriptions all generic? → Phase 1 (Meta Tags)
Tool pages buried / hard to navigate? → Phase 5 (Internal Linking)
Bad URL slugs? → Phase 6 (URL Slug Hygiene)
Site looks authorless to Google? → Phase 7 (E-E-A-T)
Stuck at position 50–68 on keywords? → Phase 9 (Blog Content Strategy)
Fixes deployed but unsure they're live? → Phase 10 (Live Verification)
Before writing any code, locate these in the codebase. Names vary by framework — adapt.
| What to find | Common locations |
|---|---|
| URL routing | routes.rb, urls.py, routes/, pages/, app/ |
| Head / meta template | _head.html, layout.js, base.html, app.blade.php |
| Tool/page registry | config file, database seed, JSON, lib/guides.js, data/tools.js |
Answer these before writing a single line:
<title>, <meta name="description">, <h1>?test cases passed, vs 14 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.