Przejdź do treści
Biblioteka skilli
Marketing i treści · Przegląd i audyt

seo-optimizer

/seo-optimizer

Audytuje i przepisuje stronę pod wyszukiwanie organiczne: długość title i meta, hierarchia nagłówków, dopasowanie do intencji, linki wewnętrzne, schema i Core Web Vitals, z uszeregowaną listą poprawek.

Repozytorium
skills ↗
Licencja
MIT
Ostatnia zmiana repozytorium
13.10.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
1
Przestarzałość

Brak sygnałów. Repozytorium zmienione 13.10.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Audytuje i przepisuje stronę pod wyszukiwanie organiczne: długość title i meta, hierarchia nagłówków, dopasowanie do intencji, linki wewnętrzne, schema i Core Web Vitals, z uszeregowaną listą poprawek.

Wyzwalacze z opisu

why isnaudit my page for SEOrewrite my title and meta descriptiondoes this need schema markup
Oryginalny opis (EN)

Audits and rewrites a page for organic search - title and meta lengths, heading hierarchy, intent match, internal links, schema markup, and Core Web Vitals - and returns a prioritized fix list. Use when someone asks "why isn't this page ranking", "audit my page for SEO", "rewrite my title and meta description", "does this need schema markup", or before publishing a page that must earn organic traffic. Do NOT use for grouping keywords into topical clusters across a site - use keyword-cluster-builder instead; do NOT use for planning a site-wide internal-link architecture - use internal-linking-m

Jak działa

  1. Operating procedure
  2. Deliverable
  3. Do NOT
  4. Quality bar
Sekcje z nagłówków SKILL.md, w oryginale · 90 linii, 894 słów
Podgląd SKILL.md
---
name: seo-optimizer
description: Audits and rewrites a page for organic search - title and meta lengths, heading hierarchy, intent match, internal links, schema markup, and Core Web Vitals - and returns a prioritized fix list. Use when someone asks "why isn't this page ranking", "audit my page for SEO", "rewrite my title and meta description", "does this need schema markup", or before publishing a page that must earn organic traffic. Do NOT use for grouping keywords into topical clusters across a site - use keyword-cluster-builder instead; do NOT use for planning a site-wide internal-link architecture - use internal-linking-mapper instead; do NOT use for restructuring content into AI-answer-ready blocks - use aeo-answer-blockifier instead; do NOT use for deep page-speed engineering - use web-performance instead.
metadata:
  title: "SEO Optimizer"
---

# SEO Optimizer

Improve one page's organic visibility through content quality, technical signals, and structured data - without keyword stuffing. The costly mistake this prevents is optimizing the wrong layer: teams rewrite copy on a page whose title truncates in the SERP, whose intent mismatches the query, or that cannibalizes a sibling page, then conclude "SEO doesn't work." Audit in order; fix the highest layer that fails first.

## Operating procedure

Intent comes before on-page elements, because a perfectly optimized page targeting the wrong intent cannot rank. On-page comes before schema and vitals, because rich results and speed amplify a page that already deserves to rank.

### Step 1: Gather inputs

1. The page URL or draft, and its one primary keyword. If the user has no primary keyword, that is the first deliverable - propose one and label it a guess.
2. 2-4 semantic variants (default: derive from the primary).
3. The intent behind the query: informational, navigational, or transactional. When unsure, check what currently ranks - the SERP is the ground truth for intent.
4. Sibling pages targeting adjacent queries, to check cannibalization.

### Step 2: Verify intent match

Match content type to intent: informational queries want guides and answers, transactional want product or category pages, navigational want the brand destination. If the page type contradicts the intent of its primary keyword, stop - no on-page fix rescues an intent mismatch; re-target or re-build. Each page must serve a distinct intent; consolidate cannibalizing pages rather than letting two half-strength pages split one query.

### Step 3: Fix the head elements

- Title tag: 50-60 characters - keep under 60 or the SERP truncates it; primary keyword near the front; unique per page.
- Meta description: 140-155 characters, include a call to action. Not a ranking factor, but it is the ad copy that drives click-through.
- URL slug: short, hyphenated, keyword-bearing, no stop words.

Bad: `Home | Acme Inc | Solutions, Products, Services, About Us and More` (74 chars, brand first, keyword nowhere).
Good: `Standing Desk Buying Guide: Height, Stability, Price | Acme` (60 chars, keyword front-loaded).

### Step 4: Fix the body structure

1. Exactly one `<h1>` per page; logical `<h2>`/`<h3>` hierarchy that a reader could skim as an outline.
2. Answer the query in the first 100 words - this is what earns featured-snippet eligibility.
3. Keyword usage: target the primary plus 2-4 semantic variants; keep density natural at roughly 0.5-1.5%. Optimize for topic coverage, not exact-match repetition.
4. Internal links: 2-5 contextual links to related pages with descriptive anchor text ("standing desk stability test", never "click here"). For architecture across many pages, hand off to internal-linking-mapper.
5. Image `alt` text describes the image for a reader who cannot see it - not a keyword slot.

### Step 5: Add schema markup where it fits

Add JSON-LD in the `<head>`; use `Article`, `FAQPage`, `Product`, `BreadcrumbList`, and `HowTo` only where the visible content genuinely matches the type - schema describing content that is not on the page invites a manual action.

```html
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Standing Desk Buying Guide: Height, Stability, Price",
  "author": { "@type": "Person", "name": "Jordan Lee" },
  "datePublished": "[FILL: ISO date]"
}
</script>
```

### Step 6: Check Core Web Vitals

- LCP under 2.5s: preload the hero image, serve next-gen formats, avoid render-blocking CSS.
- CLS under 0.1: explicit width/height on images; reserve space for ads and embeds.
- INP under 200ms: break up long tasks, defer non-critical JS.

Flag failures and hand deep remediation to web-performance.

### Step 7: Check crawl hygiene

- Canonicalize duplicates with `rel="canonical"`; pagination uses self-referencing canonicals, not `rel=prev/next` (deprecated).
- JS-rendered content: confirm crawlers see the text - server-side rendering or dynamic rendering.
- Migrations: 301-redirect old URLs one-to-one; never mass-redirect to the homepage.
- XML sitemap submitted, under 50k URLs per file.

## Deliverable

Produce a page audit containing: the intent verdict, rewritten title and meta with character counts shown, the heading outline, a keyword-and-variant map with placement notes, 2-5 internal-link recommendations with anchor text, the JSON-LD block ready to paste, Core Web Vitals pass/fail against the three thresholds, and a prioritized fix list ordered by the layer that fails first.

## Do NOT

- Do not stuff or cloak - the helpful-content system demotes thin, spun pages, and recovery is slower than doing it right.
- Do not ship a title over 60 characters or with the keyword at the end; truncation hides it exactly where it matters.
- Do not write meta descriptions past 155 characters - the SERP cuts them mid-sentence.
- Do not add schema for content the page does not visibly contain.
- Do not let two pages target the same intent; the split kills both.
- Do not treat this as site-wide strategy - clustering belongs to keyword-cluster-builder and link architecture to internal-linking-mapper.

## Quality bar

- Title 50-60 chars with the primary keyword front-loaded; meta 140-155 chars with a CTA; both counts stated in the deliverable.
- The query is answered in the first 100 words.
- One h1; every h2/h3 earns its place in the outline.
- 2-5 internal links with descriptive anchors; zero "click here".
- Schema validates and matches visible content.
- Each fix in the list names its layer (intent, head, body, schema, vitals, crawl) so the user knows what moves rankings versus click-through.

Wersje

RepozytoriumWynikLicencja
Ta strona · SkillMedev/skills100MIT
davila7/claude-code-templates100MIT
OneWave-AI/claude-skills100MIT
mahziyar-azz/seo-optimizer-SKILL100MIT
ckorhonen/claude-skills100MIT
secondsky/claude-skills100MIT
hamzafarooq/claude-code-starter90MIT

Migawka bazy z 13.11.2026 · wersja paczki 5b4be7d5aecd (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100seo-on-page-optimization
    Optymalizuje konkretną stronę: tytuł, opis, nagłówki, adres, dane strukturalne i linki, i pokazuje różnice przed i po zmianach.
  • 100seo
    Planuje klastry słów kluczowych B2B wg intencji, audytuje SEO techniczne i treściowe oraz wskazuje, co tworzyć lub scalać.
  • 90seo-structure-architect
    Wdraża dane strukturalne JSON-LD, hierarchię nagłówków, linkowanie wewnętrzne, okruszki i architekturę serwisu pod wyszukiwarki tradycyjne i AI.
  • 100seo-audit
    Przeprowadza pełny audyt SEO: indeksowalność, Core Web Vitals, nagłówki, linkowanie, E-E-A-T, profil linków i luki względem konkurencji.
  • 100seo-audit
    Przegląda SEO strony pod kątem problemów technicznych i metadanych, np. tagów title, opisów meta i nagłówków.
  • 95resonance-marketing-seo
    Prowadzi SEO i optymalizację pod silniki odpowiedzi: audyty techniczne, optymalizacja stron, jakość treści (E-E-A-T), schema markup, GEO, lokalne SEO, klastry tematyczne i Core Web Vitals.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.