Fe seo

Skill sukirman1901/frontend-expert/skills/fe-seo

Technical SEO for web apps — title/meta, OG, semantics, indexable content, CWV overlap. Use for landing pages, marketing routes, "SEO", "meta tags", "Open Graph", or making app routes discoverable.From its SKILL.md

Install

npx -y skills add sukirman1901/frontend-expert --skill fe-seo

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

10 stars10 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.1 KB, as published. Nobody here has run it

FE SEO

Overview

Ship indexable, shareable pages. Don’t duplicate full LCP guides — pair with web-performance for CWV.

When to use

Marketing/landing pages
Public docs or content routes
Adding meta/OG/Twitter cards
SPA routes that should be crawlable

When to skip

Authenticated-only app chrome with noindex
Pure internal admin (still use semantic HTML + one h1)

MUST (public / shareable routes)

Item	Rule
Title	Unique per route; aligns with visible H1 theme
Description	Meta description present and useful
H1	One primary heading; sequential ladder (`frontend-judgment`)
OG	`og:title`, `og:description`, `og:image` (valid URL) on shareable pages
Indexability	SSR/SSG/prerender for marketing; avoid empty client-only shells

Private app routes: prefer noindex rather than fake marketing meta.

Workflow

Title + description — unique per route; match visible H1 theme
Semantics — one H1; landmarks; meaningful link text
OG/Twitter — image + title for share cards on public pages
Indexability — SSR/SSG or prerender for public content
CWV — defer to web-performance / fe-devtools for measured LCP/CLS
Canonical — set when duplicate URLs exist

Agent boundaries

May decide: Metadata API vs static tags; summary vs summary_large_image
Must not: Same title on every route; keyword-stuffed invisible blocks; claim rankings without evidence

Checklist

Unique <title> / metadata API equivalent
Meta description where public
H1 + heading order sane (one h1)
OG tags on shareable pages (image not 404)
Public routes not blank without JS (when SEO matters)
noindex on private app chrome when appropriate

Depth

references/fe-seo.md. Perf: references/performance.md. Type: frontend-judgment Typography ladder.