seo-landing-page
Skill10 starsChanged 6 months agoMITView on GitHub
Use when building or auditing public marketing pages, landing pages, blogs, or SEO metadata (title, description, OG, headings). Not for authenticated app dashboards behind login.
In this repository56 other files it gives its agents.
- accessibility-passSkill
- analytics-eventsSkill
- api-error-handlingSkill
- audit-logging-backendSkill
- background-jobs-and-cronSkill
- dark-mode-and-themingSkill
- dashboard-charts-rechartsSkill
- edge-functions-and-webhooksSkill
- email-and-notificationsSkill
- error-states-and-empty-uiSkill
- feature-flags-and-togglesSkill
- file-upload-storageSkill
- i18n-multi-languageSkill
- lovable-prompting-playbookSkill
- lovable-ship-checklistSkill
- migration-playbookSkill
- multi-tenant-backendSkill
- onboarding-copySkill
- optimistic-updatesSkill
- payment-failed-and-recoverySkill
- payment-webhook-idempotencySkill
- payment-webhook-testingSkill
- performance-budgetSkill
- pg-cron-recipesSkill
- pg-cron-scheduled-jobsSkill
- pg-cron-with-pg-net-edgeSkill
- postgres-full-text-searchSkill
- postgres-triggers-and-functionsSkill
- pricing-and-billingSkill
- programmatic-seo-content-qualitySkill
- programmatic-seo-pagesSkill
- rate-limiting-edgeSkill
- realtime-and-subscriptionsSkill
- refactor-safe-diffSkill
- release-notesSkill
- seo-core-web-vitalsSkill
- seo-meta-tags-spaSkill
- seo-sitemap-generationSkill
- seo-ssr-and-prerenderingSkill
- seo-structured-dataSkill
- server-input-validationSkill
- shadcn-patternsSkill
- soft-delete-and-archivingSkill
- stripe-one-time-payment-webhooksSkill
- stripe-payment-webhooksSkill
- supabase-auth-flowsSkill
- supabase-database-designSkill
- supabase-rls-and-authSkill
- support-replySkill
- tanstack-infinite-queriesSkill
- tanstack-mutations-and-invalidationSkill
- tanstack-prefetch-and-hydrationSkill
- tanstack-query-alternativeSkill
- tanstack-router-data-loadersSkill
- tanstack-start-server-routesSkill
- typed-api-hooks-formsSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 47
Use a pre-render/SSG step so crawlers see populated HTML.
- Very specific: line 49
Verify with curl -A "Googlebot" https://example.com/ | grep -i '<title' — title must be present in the raw HTML.
- Very specific: line 59
When auditing, return a table: URL | issue | fix priority (high/medium/low).
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
SEO landing page
Apply to public routes only (not app shell behind login). This skill is the entry point for marketing-page SEO.
Deep dives:
seo-meta-tags-spa— per-route titles, OG, canonicals in a SPAseo-structured-data— Schema.org JSON-LDseo-ssr-and-prerendering— populated HTML for crawlersseo-sitemap-generation—sitemap.xml+robots.txtseo-core-web-vitals— LCP, INP, CLSprogrammatic-seo-pages— templates at scale
Per-page metadata
- Unique
<title>(50–60 chars), meta description (150–160 chars). og:title,og:description,og:image(1200×630),twitter:card.- Canonical URL when duplicates exist.
- One clear
h1; logicalh2/h3hierarchy (no skipped levels for styling).
Content
- Primary keyword in
h1and first paragraph naturally — no stuffing. - Internal links to product, pricing, docs where relevant.
- Alt text on meaningful images.
Technical
- Semantic HTML:
header,main,footer,article. - Fast LCP: optimize hero image (WebP, dimensions, lazy below fold).
/sitemap.xmland/robots.txtfor indexable sites.json-ldOrganizationorWebSiteon homepage when appropriate.
SPA metadata
Vite + React SPAs render an empty shell by default. For each public route, either:
- Set
<title>and meta tags via React 19's built-in tags (orreact-helmet-asyncon older versions), OR - Use a pre-render/SSG step so crawlers see populated HTML.
Verify with curl -A "Googlebot" https://example.com/ | grep -i '<title' — title must be present in the raw HTML.
Avoid
- Duplicate titles across routes.
h1hidden for SEO only.- Blocking render with huge unoptimized assets.
Deliverable
When auditing, return a table: URL | issue | fix priority (high/medium/low).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

