Skip to content
Back to search

seo-landing

SEO Landing: Give your AI coding agent the capabilities of a senior Technical SEO engineer. An agent skill for building high-performance, technically optimized SEO landing pages. Turn an AI coding agent into a technical SEO specialist. Build and improve landing pages with: β€’ πŸš€ 100/100 Google PageSpeed target β€’ ⚑ Core Web Vitals optimization

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/aleksandr-alhoff--seo-landing/badge.svg)](/listings/aleksandr-alhoff--seo-landing)

HTML

<a href="/listings/aleksandr-alhoff--seo-landing"><img src="/api/listings/aleksandr-alhoff--seo-landing/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

The skill is hosted at [github.com/aleksandr-alhoff/seo-landing](https://github.com/aleksandr-alhoff/seo-landing). Clone the repository β€” the repo root is the skill folder itself β€” then run the commands below from the directory that contains `seo-landing/`:

git clone https://github.com/aleksandr-alhoff/seo-landing.git

Global (available in all projects)

Every recipe below is self-contained: it creates its destination directory first, then copies the skill into it. Each one must exit with status `0` and leave the layout `<skills-dir>/seo-landing/SKILL.md` in place.

Note: `cp -R` from a git clone also copies the clone's `.git` directory into the installation β€” harmless, but unnecessary. To keep installations lean, replace `cp -R seo-landing <dir>/` with `rsync -a --exclude=.git seo-landing <dir>/seo-landing/` (the same sync used for updates below).

# VS Code Copilot
mkdir -p ~/.copilot/skills
cp -R seo-landing ~/.copilot/skills/

# Claude Code
mkdir -p ~/.claude/skills
cp -R seo-landing ~/.claude/skills/

# OpenAI Codex CLI / ChatGPT desktop
mkdir -p ~/.agents/skills
cp -R seo-landing ~/.agents/skills/

# Cursor
mkdir -p ~/.cursor/skills
cp -R seo-landing ~/.cursor/skills/

# Gemini CLI
mkdir -p ~/.gemini/skills
cp -R seo-landing ~/.gemini/skills/

# Google Antigravity
mkdir -p ~/.gemini/config/skills
cp -R seo-landing ~/.gemini/config/skills/

# OpenCode
mkdir -p ~/.config/opencode/skills
cp -R seo-landing ~/.config/opencode/skills/

# OpenClaw (via CLI β€” installs into the shared ~/.openclaw/skills)
openclaw skills install git:aleksandr-alhoff/seo-landing --global
# or from a local clone: openclaw skills install ./seo-landing --global
# or manually:
mkdir -p ~/.openclaw/skills
cp -R seo-landing ~/.openclaw/skills/

# Hermes
mkdir -p ~/.hermes/skills
cp -R seo-landing ~/.hermes/skills/

OpenClaw also picks up skills from `~/.agents/skills` (the Codex path above), and Hermes can scan it too if you add `~/.agents/skills` to `skills.external_dirs` in `~/.hermes/config.yaml`.

Gemini CLI can also install straight from a Git repository:

gemini skills install https://github.com/aleksandr-alhoff/seo-landing.git

Per project (workspace only)

# Shared .agents/skills β€” picked up by VS Code Copilot, Codex, Cursor, Antigravity, Gemini CLI, OpenCode, OpenClaw, Hermes
mkdir -p .agents/skills
cp -R seo-landing .agents/skills/

# Claude Code
mkdir -p .claude/skills
cp -R seo-landing .claude/skills/

# VS Code Copilot (GitHub-style location)
mkdir -p .github/skills
cp -R seo-landing .github/skills/

# OpenClaw (workspace skills β€” highest precedence)
# via CLI: openclaw skills install ./seo-landing
mkdir -p skills
cp -R seo-landing skills/

# Hermes (project-local; then trust the repo once: hermes skills trust)
mkdir -p .hermes/skills
cp -R seo-landing .hermes/skills/

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

SKILL.md Β· Manifest Β· 128 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. ---
  2. name: seo-landing
  3. description: "Generates fast, SEO-optimized static HTML landing pages targeting 100/100 PageSpeed (LCP < 2.5s, INP < 100ms, CLS < 0.1), full schema.org JSON-LD, AVIF images, critical CSS, zero external dependencies. Use when: user asks to create/build/generate a landing page, one-pager, or static site with focus on SEO, speed, or PageSpeed; asks for an SEO-friendly page from a brief/Π’Π—; or asks to audit/fix a landing against a performance checklist."
  4. metadata:
  5. argument-hint: "[topic/domain or brief]"
  6. ---
  7. # SEO Landing Generator
  8. Builds a static single-page HTML landing optimized for 100/100 PageSpeed and maximum SEO: critical CSS, AVIF images, full JSON-LD structured data, native-only interactivity, zero third-party requests on first load.
  9. ## When to Use
  10. - User asks for a landing page / one-pager focused on speed and SEO β†’ **generate** mode.
  11. - User provides a brief (Π’Π—) and wants a production-ready static page β†’ **generate** mode.
  12. - User asks to audit an existing landing against the checklist without changes β†’ **audit-only** mode (Β§0b, read-only, no project files).
  13. - User asks to fix/improve an existing landing β†’ **fix-existing** mode (Β§0c).
  14. ## Procedure
  15. ### 0. Route the request to a mode first
  16. The skill serves three modes β€” pick one from the request (ask if ambiguous), because each mode collects different inputs and produces different output:
  17. - **generate** β€” build a new landing page from a brief ("build/create/generate a landing…"). Runs the full procedure below.
  18. - **audit-only** β€” read-only inspection of an existing page ("audit/check/review this landing against the checklist…", no changes requested). Runs Β§0b. Never writes project files.
  19. - **fix-existing** β€” apply targeted fixes to an existing page ("fix/improve/optimize this page…"). Runs Β§0c.
  20. Representative routing:
  21. - "Build a landing for a dental clinic from this brief" β†’ **generate**.
  22. - "Audit https://example.com/ against the performance checklist and report what's wrong" β†’ **audit-only**.
  23. - "This landing's hero image shifts on load β€” fix it" β†’ **fix-existing**.
  24. Generation-only brief fields (target keywords, business type, CTA, media facts) are collected ONLY for generate and rebuild work. An audit or a targeted fix must not be blocked or delayed by missing generation inputs, and audit-only mode must not create or modify any project files.
  25. ### 0a. Collect the brief (generate mode; ask if missing)
  26. Required before generating anything:
  27. - Domain / final URL β€” for canonical, og:url, absolute paths, JSON-LD `@id`.
  28. - Site identity (for `WebSite` markup, only when the page is the domain/subdomain home page): preferred site name, optional alternate names, and the canonical home URL β€” collected separately from the landing URL.
  29. - Breadcrumb trail (for `BreadcrumbList` markup, only when a real site hierarchy exists): the visible breadcrumb trail and canonical parent URLs.
  30. - Page language, base direction, and Open Graph locale β€” three separate inputs, never one value copied across formats: a BCP-47 language tag for `<html lang>` (e.g. `en-US`, `ar-SA`), the base direction (`ltr`/`rtl` β€” RTL documents get `dir="rtl"` on `<html>`, and `lang` alone does not set directionality), and the Open Graph locale in `language_TERRITORY` format for `og:locale` (e.g. `en_GB`). Ask when direction is unknown for an RTL-capable language (tech-spec Β§2).
  31. - Topic + 1–3 target keywords β€” for H1, title, description.
  32. - Business type: Organization or LocalBusiness. For LocalBusiness collect the verified public/legal business name and the complete structured postal address (street, locality, region, postal code, country), plus phone and geo coordinates. Also collect the verified schema.org subtype(s) based on the actual business (e.g. `Restaurant`, `Dentist`, `HardwareStore`) β€” never chosen from target keywords. Never invent missing identity facts: fall back to `Organization` markup or omit entity markup until the facts are provided.
  33. - CTA and contacts (phone, form, messengers). When a form is requested, also collect its submission destination and method (a first-party endpoint or a documented form service β€” never invented), the consent/privacy text required for the collected personal data, and where submissions are stored and who owns them; with no destination, the form is omitted or explicitly stubbed (tech-spec Β§10 form submission contract).
  34. - A brand-approved favicon or explicit permission to create one β€” never invent a brand mark silently.
  35. - Approved source material and a claim owner for objective marketing facts (numbers, prices, qualifications, guarantees, comparisons, case studies) β€” without them such claims are omitted, never invented.
  36. - Whether images are provided; whether FAQ / reviews / video blocks are needed. For a video block collect source-backed facts: video URL/ID, title, description, accurate first-publication date/time with timezone, and a unique crawlable thumbnail (plus `contentUrl` when applicable). Never invent missing media facts. Also collect the video mode with its trade-off stated: click-only facade (default β€” privacy/performance; the page will not satisfy Google's video discovery requirements and no video-search benefit is claimed) or SEO-discoverable (self-hosted `<video>` or a documented direct embed β€” required when video search traffic matters) (tech-spec Β§9).
  37. If domain or keywords are missing β€” ask first, do not invent them.
  38. ### 0b. Audit-only mode (read-only)
  39. Audit an existing page without generating a replacement. No project files are created or modified in this mode β€” the deliverable is a report.
  40. 1. Identify the target: a deployed URL (preferred β€” lets every check run against reality) or local HTML files. If neither is supplied, ask; never guess the target.
  41. 2. Run the applicable checks from Β§5 against the target as-is: W3C validity, local asset existence (for local files), JSON-LD via a schema.org validator, Lighthouse against the served/deployed URL, crawlability contract (robots.txt + sitemap.xml at the deployed host), and the manual accessibility checks in tech-spec Β§8.
  42. 3. Report evidence per check: pass/fail with the measured value or observed markup, and the exact command/tool used. Where a check cannot run (no deployed URL for Lighthouse, no robots.txt on the host), report a blocker for that check β€” do not estimate, extrapolate, or omit it silently.
  43. 4. Distinguish syntax validity from Google feature eligibility (FAQPage, VideoObject, rich results): valid markup is reported as valid markup, never as an achieved search feature.
  44. 5. Optionally end with a prioritized fix list. Applying fixes is a separate **fix-existing** request β€” do not start editing without it.
  45. ### 0c. Fix-existing mode
  46. Apply targeted fixes to an existing page without a full rebuild.
  47. 1. Identify the page/files and the specific problems to fix; collect only the inputs those fixes need (never the full generation brief).
  48. 2. Apply each fix per the relevant tech-spec section, preserving unrelated markup and content.
  49. 3. STOP POINT (Β§4) applies: show the changed page before validation. If fixes change what the user approved earlier, obtain renewed approval before reporting.
  50. 4. Validate the changed page (Β§5) and report measured evidence only.
  51. ## Generation workflow (generate mode)
  52. ### 1. Create the project folder
  53. Every project lives in its own folder inside the workspace β€” **never write to the workspace root**. The output is a multi-file project: every local resource referenced by the HTML must exist as a real file.
  54. ```
  55. <workspace>/<project-slug>/
  56. index.html # the generated landing page
  57. styles.css # only when below-the-fold CSS is deferred (Β§1); absent when all CSS is inlined
  58. script.js # only when the page uses JS (Β§10); single file, defer
  59. images/ # every image variant referenced in src/srcset/preload/OG tags (AVIF/WebP/JPEG, all breakpoints)
  60. favicon.png # stable square brand icon, β‰₯48Γ—48
  61. ASSETS.md # rights & provenance record for every asset
  62. robots.txt
  63. sitemap.xml
  64. SERVER-SETUP.md # hosting instructions
  65. ```
  66. Image branch:
  67. - Images provided in the brief β†’ produce all required variants (AVIF/WebP/JPEG at every breakpoint named in `srcset`) from them.
  68. - No images available β†’ request them from the user or omit the image/block. Never emit a successful-looking asset URL without producing the file or explicitly asking for it β€” a referenced-but-missing file is a generation failure, not a placeholder.
  69. ### 2. Generate the page
  70. Build `index.html` strictly following [references/tech-spec.md](./references/tech-spec.md) β€” 13 requirement sections (performance, HTML structure, SEO, security, CSS/fonts, forbidden list, testing, accessibility, embedded video, typical blocks, deferred widgets, content truthfulness & provenance, input sanitization & output encoding).
  71. Treat every brief value as untrusted: encode it for its exact output context (HTML text, attribute, URL, JSON-LD), allow-list URL schemes (reject `javascript:`/unexpected `data:`), escape `<` in serialized JSON-LD, and validate structured IDs (e.g. YouTube `^[A-Za-z0-9_-]{11}$`) before they reach any URL (tech-spec Β§13).
  72. For embedded YouTube video use the facade pattern by default; the SEO-discoverable mode (self-hosted `<video>` or a documented direct embed) is an explicit brief choice with a disclosed trade-off, never a silent switch β€” rules and the Google discovery requirements in tech-spec Β§9, facade reference implementation in [references/video-facade.md](./references/video-facade.md). Maps follow the facade rule only (tech-spec Β§10): a local screenshot in the initial DOM, the iframe inserted only on explicit activation β€” never a native `loading="lazy"` map iframe. Reference: [references/map-facade.md](./references/map-facade.md).
  73. ### 3. Generate companion files
  74. - `robots.txt` at the site root with a fully qualified `Sitemap:` line, never blocking the canonical page or required media.
  75. - `sitemap.xml` with XML-escaped absolute canonical `<loc>` URLs matching the HTML canonical; `lastmod` only from a verifiable significant-content-change timestamp (omit when unknown β€” never use generation time blindly).
  76. - Hosting instructions from [references/server-config.md](./references/server-config.md): caching, Brotli/gzip, security headers.
  77. ### 4. STOP POINT β€” user approval
  78. Show the generated page to the user and ask explicitly whether the HTML version is OK. **Do not proceed to validation and the final report until the user confirms.** If there are remarks β€” fix and ask again.
  79. ### 5. Validate
  80. Run the executable validation contract from tech-spec Β§7 β€” pinned commands against the served page, measured results only, explicit BLOCKER when a gate cannot run:
  81. - W3C HTML validity (Nu validator, JSON output; zero errors).
  82. - Local asset/link existence: extract every local URL referenced by the output (img `src`/`srcset`, `<source>` `srcset`, preload `href`/`imagesrcset`, favicon, OG/Twitter images, CSS `url()`, script `src`) and verify each file exists in the project folder. Any missing referenced local resource is a hard failure β€” produce the file or remove the reference; never ship HTML pointing at files that were never created.
  83. - JSON-LD syntax (JSON parse) β€” separate from Google rich-result eligibility, which is checked with Rich Results Test on the deployed page.
  84. - Responsive screenshots at 320/768/1280/1920px, inspected for overflow and reflow.
  85. - Lighthouse: pinned version/profile, 3 runs, median per category, threshold β‰₯ 90, artifacts kept in the project's `reports/` β€” lab evidence only, never field Core Web Vitals and never WCAG certification.
  86. - Manual accessibility checks (tech-spec Β§8) β€” no automated tool alone determines WCAG conformance: keyboard navigation, focus order/visibility, dialog focus flow, zoom/reflow, reduced motion, semantic name-role-value, alternative-text quality, and all interactive visual states. Record pass/fail evidence per applicable WCAG 2.1 AA criterion; report unresolved items instead of silently certifying them.
  87. - Crawlability contract: parse `sitemap.xml`, compare every `<loc>` with the HTML canonical, check the `Sitemap:` URL in `robots.txt`, and request both deployed files successfully (HTTP 200).
  88. Fix any violations found before reporting. Disclose evidence honestly: every reported number comes with the exact command and artifact path that produced it; a gate that could not run is reported as `BLOCKER: <reason>` instead of a number. Never output a PageSpeed/LCP score that was not actually measured.
  89. ### 6. Final report
  90. Briefly list:
  91. - LCP parameters
  92. - PageSpeed score
  93. - schema.org types used in the code
  94. ## Main pitfalls
  95. - Never use external JS/CSS libraries, external fonts, or SVG images (tech-spec Β§6).
  96. - Never reference a local asset that was never created: every `src`/`srcset`/preload/OG URL must resolve to a real file in the project folder; missing source images are requested from the user, not invented (OUTPUT contract).
  97. - Never emit a raw brief value into markup: context-encode everything, reject `javascript:`/unexpected `data:` URLs, and self-test generation with hostile values (quotes, `</script>`, event-handler payloads) (tech-spec Β§13).
  98. - Never load YouTube iframes, maps, chats, subscription popups, or cookie banners on first load (tech-spec Β§9, Β§10, Β§11) β€” the single documented exception is a brief-chosen SEO-discoverable video mode with a direct embed recorded as a first-load dependency (tech-spec Β§9 Mode S).
  99. - All content must exist in raw HTML β€” nothing rendered only by JS.
  100. - Absolute URLs in JSON-LD, canonical, and OG tags.
  101. - Total JS budget ≀ 15 KB, one file, `defer` before `</body>`.
README.md Β· README Β· 315 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # SEO Landing
  2. ## Give your AI coding agent the capabilities of a senior Technical SEO engineer.
  3. An agent skill for building high-performance, technically optimized SEO landing pages.
  4. Turn an AI coding agent into a technical SEO specialist.
  5. Build and improve landing pages with:
  6. - πŸš€ 100/100 Google PageSpeed target
  7. - ⚑ Core Web Vitals optimization
  8. - πŸ” Technical SEO
  9. - 🧩 Full Schema.org structured data
  10. - πŸ–ΌοΈ AVIF image optimization
  11. - 🎨 Critical CSS
  12. - 🧹 Zero third-party requests on first load
  13. - πŸ“± Mobile-first performance
  14. - πŸ€– Semantic HTML
  15. πŸ‡·πŸ‡Ί [ОписаниС скила Π½Π° русском языкС](./README.ru.md)
  16. ## Works with AI coding agents
  17. Designed for agentic coding workflows and compatible with Agent Skills–style environments.
  18. ## What it does?
  19. The skill guides an AI coding agent through the complete landing-page workflow:
  20. 1. Analyze the existing page
  21. 2. Fix technical SEO issues
  22. 3. Optimize HTML structure
  23. 4. Improve Core Web Vitals
  24. 5. Optimize images and fonts
  25. 6. Add structured data
  26. 7. Remove unnecessary dependencies
  27. 8. Validate the final implementation
  28. ## Why?
  29. AI can generate a beautiful landing page in seconds.
  30. The problem is that generated pages often contain:
  31. - unnecessary JavaScript
  32. - oversized images
  33. - poor semantic structure
  34. - missing structured data
  35. - weak metadata
  36. - performance bottlenecks
  37. - technical SEO mistakes
  38. SEO Landing Skill gives the agent a repeatable technical SEO workflow instead of relying on generic prompting.
  39. An agent skill that builds and updates landing pages toward **100/100 lab PageSpeed** and Core Web Vitals-friendly performance, and gets the technical SEO right. Static HTML, critical CSS, AVIF images, full schema.org markup, zero third-party requests on first load (deferred widgets, when used, are consent-gated and documented in the dependency manifest). These are optimization targets, not guaranteed outcomes β€” results depend on content, hosting, devices, and real traffic; Core Web Vitals status itself is determined by Google from field (RUM) data, not by lab tools.
  40. ```text
  41. BEFORE
  42. Landing page
  43. ↓
  44. LCP: 4.2s
  45. Performance: 61
  46. Missing schema
  47. Large PNG
  48. Render-blocking CSS
  49. ↓ SEO LANDING SKILL ↓
  50. AFTER
  51. Landing page
  52. ↓
  53. LCP: 1.1s
  54. Performance: 100
  55. Schema.org βœ“
  56. AVIF βœ“
  57. Critical CSS βœ“
  58. Semantic HTML βœ“
  59. ```
  60. Format β€” [Agent Skills](https://agentskills.io) (open standard originally developed by Anthropic): works in VS Code Copilot, Claude Code, OpenAI Codex, Google Antigravity, Cursor, Gemini CLI, OpenClaw, Hermes, and other compatible agents.
  61. ## What's inside
  62. ```
  63. seo-landing/
  64. β”œβ”€β”€ SKILL.md # Main workflow: mode routing β†’ brief β†’ generation β†’ stop point β†’ validation β†’ report
  65. β”œβ”€β”€ references/
  66. β”‚ β”œβ”€β”€ tech-spec.md # Technical spec (13 requirement sections + executable validation contract)
  67. β”‚ β”œβ”€β”€ server-config.md # Server config: caching, Brotli/gzip, security headers (Nginx/Apache)
  68. β”‚ β”œβ”€β”€ video-facade.md # Reference implementation of the "facade" pattern for YouTube
  69. β”‚ └── map-facade.md # Reference implementation of the "facade" pattern for map embeds
  70. β”œβ”€β”€ benchmark/ # Lab benchmark disclosure: fixture, raw Lighthouse reports, methodology
  71. └── tests/
  72. └── fixtures/broken-landing/ # Negative fixture: every validator gate must fail on it
  73. ```
  74. ## Key requirements enforced by the skill
  75. - **Performance**: LCP < 2.5s, INP < 100ms, CLS < 0.1; critical CSS inlined, the rest loaded async; the LCP image loads eagerly with `fetchpriority="high"` (a responsive `imagesrcset`/`imagesizes` preload only when measurement shows a benefit)
  76. - **Images**: AVIF β†’ WebP β†’ JPEG via `<picture>`, `srcset`/`sizes`, `width`/`height`, `loading="lazy"` for below-the-fold images only (never on the LCP image), breakpoints 320–1920
  77. - **SEO**: title/description/canonical/robots, Open Graph, Twitter Card, JSON-LD (`WebSite`, `Organization`, `BreadcrumbList`, `FAQPage`, `VideoObject` β€” emitted only when fact-backed and reported per the chosen video mode, never as a guaranteed search feature)
  78. - **Accessibility**: WCAG 2.1 AA, contrast β‰₯ 4.5:1, keyboard navigation, `prefers-reduced-motion`
  79. - **Security**: `X-Content-Type-Options`, `X-Frame-Options`, `Permissions-Policy`, `Referrer-Policy`, per-page CSP, staged HSTS, HTTPS enforcement, `rel="noopener noreferrer"`
  80. - **Fonts**: system fonts only β€” no external fonts, no Google Fonts
  81. - **JS budget ≀ 15 KB** for the first load, one file with `defer`; deferred third-party widgets (when used) are consent-gated, excluded from the budget, and disclosed in the dependency manifest
  82. - **Forbidden**: external JS/CSS libraries, SVG images, synchronous scripts, iframes on first load
  83. - **Video & maps**: "facade" pattern by default β€” the cover is a local responsive image (eager when it is the LCP/above the fold, lazy below the fold), the iframe loads only on click. Click-only video trades Google video discovery for pre-activation privacy/performance; an opt-in SEO-discoverable mode (self-hosted `<video>` or a documented direct embed) exists when video search matters (tech-spec Β§9). Maps remain facade-only.
  84. - **Common blocks without JS**: FAQ via `<details>`, slider via `scroll-snap`, modal via `<dialog>`
  85. - **Stop point**: before validation and the final report, the skill always asks the user to confirm the HTML version
  86. ## Real-world result (lab measurements β€” not field Core Web Vitals)
  87. One reproducible lab benchmark: Lighthouse CLI 13.4.1, mobile emulation, simulated throttling. Original β€” an Angular SPA (102 requests, 1 run); the same page rebuilt as static HTML with this skill (17–18 requests, median of 5 runs). Full disclosure β€” fixture, exact flags, raw JSON reports, timestamps, and aggregation method β€” is in [benchmark/README.md](./benchmark/README.md).
  88. | Metric | Original | Rebuilt | Gain |
  89. |---|---:|---:|---:|
  90. | Performance | 75 | **100** | +25 |
  91. | Accessibility | 75 | **100** | +25 |
  92. | Best Practices | 73 | **100** | +27 |
  93. | LCP | 3.3 s | 1.6 s | βˆ’52% |
  94. | Total Blocking Time | 490 ms | 13 ms | βˆ’97% |
  95. | TTI | 9.4 s | 1.6 s | βˆ’83% |
  96. | Data transferred | 769 KiB | 110 KiB | βˆ’86% |
  97. | Requests | 102 | 17 | βˆ’83% |
  98. These are **lab** numbers for one before/after pair. They are not field Core Web Vitals (Google determines CWV status from CrUX/RUM field data at the 75th percentile, and Lighthouse cannot measure INP without real interaction), and they are not a guarantee that another page, host, device, or audience will reach the same results β€” the skill's targets are optimization goals, not promised outcomes.
  99. ## Installation
  100. The skill is hosted at [github.com/aleksandr-alhoff/seo-landing](https://github.com/aleksandr-alhoff/seo-landing). Clone the repository β€” the repo root is the skill folder itself β€” then run the commands below from the directory that contains `seo-landing/`:
  101. ```bash
  102. git clone https://github.com/aleksandr-alhoff/seo-landing.git
  103. ```
  104. ### Global (available in all projects)
  105. Every recipe below is self-contained: it creates its destination directory first, then copies the skill into it. Each one must exit with status `0` and leave the layout `<skills-dir>/seo-landing/SKILL.md` in place.
  106. Note: `cp -R` from a git clone also copies the clone's `.git` directory into the installation β€” harmless, but unnecessary. To keep installations lean, replace `cp -R seo-landing <dir>/` with `rsync -a --exclude=.git seo-landing <dir>/seo-landing/` (the same sync used for updates below).
  107. ```bash
  108. # VS Code Copilot
  109. mkdir -p ~/.copilot/skills
  110. cp -R seo-landing ~/.copilot/skills/
  111. # Claude Code
  112. mkdir -p ~/.claude/skills
  113. cp -R seo-landing ~/.claude/skills/
  114. # OpenAI Codex CLI / ChatGPT desktop
  115. mkdir -p ~/.agents/skills
  116. cp -R seo-landing ~/.agents/skills/
  117. # Cursor
  118. mkdir -p ~/.cursor/skills
  119. cp -R seo-landing ~/.cursor/skills/
  120. # Gemini CLI
  121. mkdir -p ~/.gemini/skills
  122. cp -R seo-landing ~/.gemini/skills/
  123. # Google Antigravity
  124. mkdir -p ~/.gemini/config/skills
  125. cp -R seo-landing ~/.gemini/config/skills/
  126. # OpenCode
  127. mkdir -p ~/.config/opencode/skills
  128. cp -R seo-landing ~/.config/opencode/skills/
  129. # OpenClaw (via CLI β€” installs into the shared ~/.openclaw/skills)
  130. openclaw skills install git:aleksandr-alhoff/seo-landing --global
  131. # or from a local clone: openclaw skills install ./seo-landing --global
  132. # or manually:
  133. mkdir -p ~/.openclaw/skills
  134. cp -R seo-landing ~/.openclaw/skills/
  135. # Hermes
  136. mkdir -p ~/.hermes/skills
  137. cp -R seo-landing ~/.hermes/skills/
  138. ```
  139. OpenClaw also picks up skills from `~/.agents/skills` (the Codex path above), and Hermes can scan it too if you add `~/.agents/skills` to `skills.external_dirs` in `~/.hermes/config.yaml`.
  140. Gemini CLI can also install straight from a Git repository:
  141. ```bash
  142. gemini skills install https://github.com/aleksandr-alhoff/seo-landing.git
  143. ```
  144. ### Per project (workspace only)
  145. ```bash
  146. # Shared .agents/skills β€” picked up by VS Code Copilot, Codex, Cursor, Antigravity, Gemini CLI, OpenCode, OpenClaw, Hermes
  147. mkdir -p .agents/skills
  148. cp -R seo-landing .agents/skills/
  149. # Claude Code
  150. mkdir -p .claude/skills
  151. cp -R seo-landing .claude/skills/
  152. # VS Code Copilot (GitHub-style location)
  153. mkdir -p .github/skills
  154. cp -R seo-landing .github/skills/
  155. # OpenClaw (workspace skills β€” highest precedence)
  156. # via CLI: openclaw skills install ./seo-landing
  157. mkdir -p skills
  158. cp -R seo-landing skills/
  159. # Hermes (project-local; then trust the repo once: hermes skills trust)
  160. mkdir -p .hermes/skills
  161. cp -R seo-landing .hermes/skills/
  162. ```
  163. ## Updating, verifying, and uninstalling installed copies
  164. Two facts drive everything below:
  165. 1. **`git pull` changes only the clone.** An installed copy made with `cp -R` is independent β€” pulling the source clone does NOT update any installation.
  166. 2. **`cp -R` copies, it does not synchronize.** GNU `cp` has no destination-sync/removal behavior: a file deleted upstream stays in the installed copy forever, producing a mixed release of old and new instructions.
  167. So an update is an explicit, bounded, idempotent sync into the resolved skill destination β€” never a blind re-copy.
  168. ### Destinations (one per client and scope)
  169. | Client / scope | Installed skill destination (`$DEST`) |
  170. |---|---|
  171. | VS Code Copilot β€” global | `~/.copilot/skills/seo-landing` |
  172. | Claude Code β€” global | `~/.claude/skills/seo-landing` |
  173. | OpenAI Codex CLI / ChatGPT desktop β€” global | `~/.agents/skills/seo-landing` |
  174. | Cursor β€” global | `~/.cursor/skills/seo-landing` |
  175. | Gemini CLI β€” global | `~/.gemini/skills/seo-landing` |
  176. | Google Antigravity β€” global | `~/.gemini/config/skills/seo-landing` |
  177. | OpenCode β€” global | `~/.config/opencode/skills/seo-landing` |
  178. | OpenClaw β€” global | `~/.openclaw/skills/seo-landing` |
  179. | Hermes β€” global | `~/.hermes/skills/seo-landing` |
  180. | Shared per-project (Copilot, Codex, Cursor, Antigravity, Gemini CLI, OpenCode, OpenClaw, Hermes) | `.agents/skills/seo-landing` |
  181. | Claude Code β€” per project | `.claude/skills/seo-landing` |
  182. | VS Code Copilot β€” per project (GitHub-style) | `.github/skills/seo-landing` |
  183. | OpenClaw β€” workspace (highest precedence) | `skills/seo-landing` |
  184. | Hermes β€” per project | `.hermes/skills/seo-landing` |
  185. ### Update (idempotent sync, removes upstream-deleted files)
  186. Run from the directory that contains the updated `seo-landing/` clone, with `$DEST` set to the destination from the table above:
  187. ```bash
  188. DEST=~/.copilot/skills/seo-landing # ← substitute the right destination
  189. # 1. Recovery first: back up the current installation (the sync is destructive).
  190. cp -R "$DEST" "$DEST.backup-$(date +%Y%m%d)"
  191. # 2. Bounded idempotent sync: copy new/changed files AND delete files inside
  192. # $DEST that no longer exist upstream. --delete only ever touches $DEST.
  193. rsync -a --delete --exclude=.git seo-landing/ "$DEST/"
  194. # 3. Verify: zero differences (exit status 0) and the installed SKILL.md
  195. # matches the source revision byte-for-byte.
  196. diff -qr -x .git seo-landing "$DEST" && cmp "$DEST/SKILL.md" seo-landing/SKILL.md
  197. ```
  198. Notes:
  199. - `rsync -a --delete` is available out of the box on macOS (openrsync) and on typical Linux systems; `--exclude=.git` keeps the clone's history out of the installation.
  200. - The backup in step 1 is the recovery path: if the new version misbehaves, restore it with `rm -rf "$DEST" && cp -R "$DEST.backup-<date>" "$DEST"`. (macOS openrsync does not support `--backup`, so the explicit copy is the verified mechanism.)
  201. - The sync is safe to re-run at any time β€” running it twice in a row changes nothing the second time.
  202. - Tested upgrade path: an installation containing a file that the new revision removed loses that file after the sync, and the installed `SKILL.md` becomes byte-identical to the source revision.
  203. ### Verify an existing installation at any time
  204. ```bash
  205. diff -qr -x .git seo-landing "$DEST"
  206. ```
  207. Exit status `0` (no output) means the installation matches the clone exactly. Any printed difference is a stale, modified, or extra file β€” re-run the update sync to resolve it. To check which specification version is installed, read the `Version` line at the top of `$DEST/references/tech-spec.md` (the single source of truth for versions).
  208. ### Reload / restart after an update
  209. Agents read skills when a session starts. After updating, **start a new chat session** (or restart the agent CLI) before relying on the new version. Clients that gate skills behind trust/approval (e.g. Hermes: `hermes skills trust`) may require re-trusting the updated copy.
  210. ### Uninstall
  211. ```bash
  212. rm -rf "$DEST" # the destination from the table above
  213. ```
  214. If the copy was installed through a client CLI (`openclaw skills install`, `gemini skills install`), prefer that client's own uninstall command when it provides one; otherwise removing the destination directory is sufficient. Also remove any backups (`$DEST.backup-*`) you no longer need.
  215. ### Symlinked installations β€” optional/experimental
  216. Symlinking the clone into a skills directory (so `git pull` updates it in place) is possible in principle, but official symlink support, trust handling, and reload behavior differ per client and are NOT verified here β€” treat this as experimental. The rsync sync above is the supported, client-independent update path.
  217. Once installed, the skill is picked up automatically by its description β€” just ask your agent to "build a landing page from a brief with focus on SEO and PageSpeed".
  218. ## Usage
  219. 1. Give the agent a brief: domain, language (BCP-47 tag, base direction for RTL languages, and Open Graph locale β€” three separate inputs), topic and keywords, business type, CTA and contacts.
  220. 2. The skill creates a separate project folder (`<workspace>/<project-slug>/`) with `index.html` and every local asset it references (all image variants, favicon), plus β€” conditionally β€” `styles.css` (deferred CSS only), `script.js` (when JS is used), `robots.txt`, `sitemap.xml`, `ASSETS.md`, and `SERVER-SETUP.md`. Missing source images are requested from the user, never invented.
  221. 3. At the stop point, confirm the HTML version β€” the skill then runs validation (local asset/link existence, W3C, JSON-LD, Lighthouse as automated evidence, plus required manual accessibility checks) and produces a report: LCP, PageSpeed scores, and the schema.org types used.
  222. ## About the author
  223. **Aleksandr Alhov** β€” 14+ years of experience in SEO, content marketing, and GEO/AEO. Runs an SEO boutique for product teams working across EN, LATAM, MENA, and CIS markets: building in-house SEO departments turnkey, launching profitable corporate media, discovering growth hypotheses in the SEO channel, and providing hands-on SEO consulting.
  224. Co-founder of:
  225. - [Total Site Control](https://totalsitecontrol.com/)
  226. - [Udalenka.work](https://udalenka.work)
  227. - [QR Barcode Hub](https://qrbarcodehub.com)
  228. - [DealRocket](https://dealrocket.ru/)
  229. Made for the [t.me/sdelay_tam](https://t.me/sdelay_tam) channel β€” a cozy SEO channel for product teams. SEO questions: [t.me/alhov](https://t.me/alhov).
  230. ## License
  231. [MIT](./LICENSE) β€” free to use, modify, and distribute, including commercially. Just keep the copyright notice.
  232. Specification: see [references/tech-spec.md](./references/tech-spec.md) β€” the current version and change record are declared there.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.