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.
Profile →npx skills add sickn33/agentic-awesome-skills --skill tools-page-seo-optimizer --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
The skill provides a framework-agnostic SEO workflow for sites with multiple tool, product, or feature pages. It aims to fix duplicate content and generic meta tags, establish a content registry, improve heading hierarchy, internal linking, URL slugs, and E-E-A-T signals. It also prescribes a blog content strategy to address informational keywords currently ranking around positions 50–68. The approach is organized into phases (Meta Titles & Descriptions, Content Registry, H1/Headings, Accessibility, Internal Linking, URL Slug Hygiene, E-E-A-T, Scaling, Blog Strategy) and includes concrete validation and templated examples for implementation across frameworks. Tools declared for use include claude-code, cursor, codex-cli, gemini-cli, and opencode.
How it works
- Phase 1: Enforces unique, concise meta titles (≤60 chars) and unique, descriptive meta descriptions (120–160 chars) per tool page, with a custom description per page. It includes a validation script to enforce length requirements.
- Phase 2: Introduces a Content Registry to remove template-heavy, duplicate prose by requiring unique introduction content (80+ words) and tool-specific sections (how_to_steps, faqs, related_tools).
- Phase 3: Prescribes a single, unique H1 per page and a strict heading hierarchy (H2 for major sections like How It Works, Best Practices, FAQs, Related Tools; H3 for subsections).
- Phase 4: Addresses accessibility by ensuring interactive elements have aria-labels and provides scripts to detect missing aria-labels on icon-only buttons.
- Phase 5: Advocates a Hub-and-Spoke internal linking model, requiring each tool to link to and be linked from multiple related tools, with a sample template for rendering Related Tools.
- Phase 6: Guidelines for URL slug hygiene, promoting keyword-rich, hyphenated slugs and 301 redirects when renaming slugs.
- Phase 7: Adds E-E-A-T signals via bylines, update dates, and a Trust Pillars section; recommends an About page with credentials.
- Phase 8: Scales to 100+ tools with batch completion checks and build verifications before commit.
- Phase 9: Introduces a blog-content strategy to target informational queries ranking at positions 50–68 by creating blog posts that link back to tool pages.
When to use it
Use when a site has many tool/product/feature pages and current pages share template prose, have duplicate or generic titles/descriptions, weak internal linking, non-optimized slugs, or insufficient author/date signals. Follow the phased workflow to systematically improve page uniqueness, structure, linking, and auxiliary blog content.
What it can touch
Declared tools: claude-code, cursor, codex-cli, gemini-cli, opencode.
Caveats
Declared risk: safe. License: MIT. No explicit limitations beyond the phases and templates provided; evaluation relies on applying the phase-specific rules and ensuring content is unique per tool as described.
# Tools Page SEO Optimizer 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. --- ## Quick-Start Decision Tree ``` 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) ``` --- ## Phase 0 — Codebase Reconnaissance **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`, `rout
- Quick-Start Decision Tree
- Phase 0 — Codebase Reconnaissance
- Phase 1 — Meta Titles & Descriptions
- The core problem
- Title tag formula
- Meta description formula
- Implementation (any framework)
- Validation script — run before every deploy
- Phase 2 — Content Registry (The Highest-Leverage Fix)
- Diagnosis
- Registry entry structure (framework-agnostic)
- Minimum viable unique content per tool
- Phase 3 — H1 and Heading Hierarchy
- H1 formula
Find shared prose in your templates — if these strings appear in a shared template Audit heading hierarchy on a live page curl -s "https://yourdomain.com/tools/meta-tag-generator" \ Find icon-only buttons missing aria-label Orphan detection — tools with too few inbound references for slug in $(cat data/slugs.txt 2>/dev/null); do done Audit — list longest slugs (likely stuffed) curl -s "https://yourdomain.com/sitemap.xml" \ Count tools with introduction content vs total tools
What does the tools-page-seo-optimizer skill do?
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.
How do I install it?
Run `npx skills add sickn33/agentic-awesome-skills --skill tools-page-seo-optimizer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.