rampstackco/claude-skills / skills/seo-onpage
seo-onpage
VerifiedRun a comprehensive on-page SEO audit or optimization pass covering title tags, meta descriptions, header structure, content quality, internal links, image optimization, URL hygiene, and on-page schema. Use this skill whenever the user asks to optimize a page, audit on-page SEO, fix titles or meta tags, review header structure, check internal linking, improve a single URL's search performance, or write SEO-friendly copy. Triggers on on-page SEO, page audit, title tag, meta description, H1, header structure, internal links, image alt, URL slug, page optimization, optimize this page, SEO this page. Also triggers for any single-page review where ranking, click-through, or relevance signal quality is the goal, even if the user does not say 'SEO' explicitly.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 1.5 KB |
| SKILL.md | skill md | 6.7 KB |
| references/audit-template.md | markdown | 2.2 KB |
| references/onpage-checklist.md | markdown | 2.6 KB |
| references/title-and-meta-patterns.md | markdown | 9.6 KB |
references/title-and-meta-patterns.md
View on GitHub# Title and Meta Patterns
Patterns for writing strong title tags and meta descriptions. The title tag and meta description are the two most-edited and most-impactful elements in on-page SEO. They are also the two most often left as defaults.
---
## Title tag patterns
### The job of the title tag
- Tell Google what the page is about (ranking signal)
- Tell the human what the page is about (CTR signal)
- Distinguish from other pages on the same site (uniqueness signal)
- Earn the click against 9 other titles in the SERP
A title that does all four wins on rankings AND clicks. A title that does only the first ranks but earns no clicks. A title that does only the last earns clicks but ranks badly.
### Length
- 50-60 characters is the safe range for most desktop and mobile SERPs.
- Longer titles get truncated (Google appends "...").
- Truncation is not catastrophic if the most important words are in the first 50 characters.
### Character priority
The most important word (typically the primary query target) goes near the front. Secondary words and brand go at the end.
```
[Primary query target] | [Modifier or value prop] | [Brand]
```
Examples:
| Bad | Better |
|---|---|
| "Welcome to Acme - your trusted partner in widgets since 1995" | "Widgets for industrial use - Acme" |
| "Acme Inc. - Best widgets - Buy online" | "Industrial widgets - free shipping - Acme" |
| "About us" | "About Acme - 25 years building industrial widgets" |
### Patterns by page type
#### Homepage
```
[Brand]: [One-line value prop]
```
Examples:
- "Notion: the all-in-one workspace for your notes and tasks"
- "Linear: built for modern software teams"
- "Acme Hardware: industrial widgets for builders"
#### Category page
```
[Category name] - [Modifier or differentiator] | [Brand]
```
Examples:
- "Industrial widgets - in stock, free shipping | Acme"
- "Project management software for engineers | Linear"
- "Recipes by region - 1,000+ tested recipes | RecipeCo"
#### Product / detail page
```
[Product name] - [Key benefit or spec] | [Brand]
```
Examples:
- "10mm steel widget - 50 lb capacity | Acme"
- "Linear Free - up to 10 users, unlimited issues | Linear"
- "Mediterranean lentil soup recipe | RecipeCo"
#### Article / blog post
```
[Headline that promises value] - [Brand]
```
Examples:
- "How to choose an industrial widget supplier - Acme"
- "Linear vs Jira: 5 differences that actually matter - Linear"
- "Why your meta descriptions are getting rewritten - Search Engine Journal"
The blog title is usually the H1 + brand. If the H1 is long, shorten for the title.
#### Comparison / vs page
```
[Brand A] vs [Brand B]: [Differentiating angle] | [Your brand]
```
Examples:
- "Linear vs Jira: speed, opinions, and team size | Linear"
- "MongoDB vs PostgreSQL: when to pick which | Engineering Blog"
#### Pricing page
```
[Brand] pricing - [What is included] | [Brand]
```
Examples:
- "Linear pricing - free forever for small teams | Linear"
- "Pricing - simple, transparent, no surprises | Acme"
#### Geographic / location page
```
[Service] in [City], [State] | [Brand]
```
Examples:
- "Plumbing services in Austin, TX | Smith Plumbing"
- "Coworking in Brooklyn - day passes and memberships | WorkSpace"
---
## Title rules and anti-patterns
### Do
- Put the primary query near the front
- Include brand at the end
- Use a separator that the SERP renders cleanly (`|`, `-`, `:`)
- Be specific (numbers, modifiers, segments earn attention)
- Match the H1 in spirit, not word-for-word
### Do not
- Repeat the primary query multiple times ("Widgets, industrial widgets, buy widgets - Widgets.com")
- Start with the brand on every page (homepage is the exception)
- Use ALL CAPS for emphasis
- Use clickbait phrasing that mismatches the page content
- Pad with filler words ("Welcome to," "Find the best," "Looking for")
- Append "Home" / "Default" / "Untitled"
- Leave it as the CMS default
---
## Meta description patterns
### The job of the meta description
- Earn the click in the SERP
- Set expectations for what the page delivers
- Reinforce the primary query (Google bolds matched terms)
The meta description is **not** a ranking signal directly. It is a CTR signal, which feeds back into ranking via behavioral signals.
### Length
- 140-160 characters. Longer gets truncated on most devices.
- Mobile truncates earlier than desktop. Front-load the value.
### Structure
Three moves in 1-3 sentences:
1. **Promise the value.** What does the reader get if they click?
2. **Justify it.** Why is this credible? (Numbers, recency, specificity, authority.)
3. **Cue the action.** What should they expect to do or learn?
Not every meta description does all three. The strongest do.
### Examples
| Bad | Better |
|---|---|
| "Welcome to our blog where we write about widgets." | "How to pick the right industrial widget for your project. 10 specs that matter, with a comparison chart." |
| "Acme Inc. is a leading provider of widgets and other products." | "Industrial widgets in 50+ sizes. Free shipping over $100. Same-day dispatch from Austin, TX." |
| "Click here to learn more about our pricing." | "Linear pricing: free forever for teams up to 10. Pro is $8/user/month. No setup fee. See plans and limits." |
---
## Meta description patterns by page type
### Homepage
```
[What the brand does, one sentence]. [The audience or use case]. [The differentiator or social proof].
```
Example: "Modern issue tracking for software teams. Built for speed. Used by 5,000+ teams from startups to enterprise."
### Category page
```
[What the category contains]. [The selection or differentiator]. [Trust or shipping signal].
```
Example: "Industrial widgets in 50+ sizes from 10mm to 200mm. Free shipping over $100. In stock and ready to ship from Austin."
### Product / detail page
```
[Product, with key spec]. [Use case]. [Trust signal or guarantee].
```
Example: "10mm steel widget rated to 50 lb. Built for industrial assembly lines. 5-year warranty, free returns."
### Article / blog post
```
[The promise of the article in one sentence]. [The substance or evidence]. [Optional: who it is for].
```
Example: "How to choose between Linear and Jira: 5 specific differences in workflow, speed, and pricing. With screenshots and benchmarks. For engineering managers comparing the two."
### Pricing page
```
[The headline pricing]. [What is included]. [Anti-friction language].
```
Example: "Linear is free forever for teams up to 10. Pro plan starts at $8/user/month. No setup fee, cancel anytime."
---
## Meta description rules
### Do
- Front-load the value
- Use the primary query naturally (Google bolds it)
- Include numbers, specifics, and proof points
- Match the page's actual content
- Write for humans (it is a sales line, not a ranking line)
### Do not
- Pad with marketing-speak ("revolutionary," "industry-leading")
- Repeat the title verbatim
- End mid-sentence
- Stuff keywords (Google will rewrite the description if it looks unnatural)
- Leave the CMS default
- Use the same description on multiple pages
---
## When Google rewrites your meta description
Google rewrites meta descriptions when it thinks its rewrite will earn more clicks. Common triggers:
- The description does not match the query
- The description is too short, too generic, or stuffed
- The page content has clearly different value from the description
- The page is matched against a long-tail query the description does not address
To avoid rewrites:
- Match the description to the page's actual content
- Make sure the primary query appears naturally in the description
- Keep the description specific and current
If Google rewrites your description and the rewrite is wrong (low CTR, misleading), tighten the description and consider adding `name="description"` plus alternative phrasings via `<meta property="og:description">` for parity.
---
## CTR optimization tips (beyond pattern)
- **Numbers earn attention.** "5 ways," "100+ examples," "in 10 minutes."
- **Year in title for evergreen-but-current content.** "(2026)" earns clicks in fast-moving categories. Update annually.
- **Brackets and parens are click-bait when overused, useful when accurate.** "[Free Template]," "(2026 update)."
- **Question titles work for some intents.** "How do I [task]?" earns clicks for how-to.
- **Comparison titles are click magnets.** "X vs Y: [angle]."
- **Promise-and-deliver framing.** Title promises a specific value; the page delivers it.
---
## Title and description audit shortcut
For any page, ask:
1. Does the title contain the primary query in the first 30 characters?
2. Is the title under 60 characters?
3. Is the title unique on the site?
4. Does the meta description promise value, justify it, and read as a human-written sentence?
5. Is the meta description under 160 characters?
6. Has Google rewritten the description? (Check Search Console performance report.)
If 4 of 6 are "no," the title or description is the highest-leverage fix on the page.
---
## A/B testing titles and descriptions
For high-traffic pages, A/B test alternates. Tools that support this: native CMS tools, edge workers, dedicated SEO testing platforms.
Test one variable at a time (title length, vs comparison hook vs question form, etc.). Run for 2-4 weeks per variant. Measure CTR and downstream conversion, not just rank position.
---
## Snippet appearance is not just title and description
What the SERP shows can include:
- The title and description (this guide)
- Sitelinks (Google-auto, can be encouraged via clean IA)
- Rich results from schema (recipe, FAQ, product, review)
- Breadcrumbs (improves CTR, requires breadcrumb schema)
- Author and date (article schema)
- Featured snippets (a separate optimization layer)
Title and description are the foundation. Schema and sitelinks are leverage on top.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |