agentleFS
charanjit-singhcharanjit-singh/lovable-skills/skills/seo-landing-page/SKILL.md

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.

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
  1. Distinctive:

    Use a pre-render/SSG step so crawlers see populated HTML.

    line 47
  2. Very specific:

    Verify with curl -A "Googlebot" https://example.com/ | grep -i '<title' — title must be present in the raw HTML.

    line 49
  3. Very specific:

    When auditing, return a table: URL | issue | fix priority (high/medium/low).

    line 59

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 SPA
  • seo-structured-data — Schema.org JSON-LD
  • seo-ssr-and-prerendering — populated HTML for crawlers
  • seo-sitemap-generation — sitemap.xml + robots.txt
  • seo-core-web-vitals — LCP, INP, CLS
  • programmatic-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; logical h2/h3 hierarchy (no skipped levels for styling).

Content

  • Primary keyword in h1 and 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.xml and /robots.txt for indexable sites.
  • json-ld Organization or WebSite on 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 (or react-helmet-async on 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.
  • h1 hidden for SEO only.
  • Blocking render with huge unoptimized assets.

Deliverable

When auditing, return a table: URL | issue | fix priority (high/medium/low).

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.