From build-seo-landing-page-skills
Builds, improves, and audits landing pages with conversion-focused design, responsive UX, SEO/AEO/GEO, structured data, accessibility, performance, deployment, and launch validation. Use for creating, redesigning, launching, or auditing landing pages, service pages, local business sites, portfolios, SaaS/product pages, static sites, React/Next.js pages, or other marketing pages. Do not use for tiny copy or style edits unless SEO, conversion, or launch readiness matters.
How this skill is triggered — by the user, by Claude, or both
Slash command
/build-seo-landing-page-skills:build-seo-landing-pageThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill to create, improve, audit, deploy, or validate landing pages.
agents/openai.yamlreferences/content-conversion.mdreferences/deployment-domain-search-console.mdreferences/framework-implementation.mdreferences/landing-page-workflow.mdreferences/local-business-seo.mdreferences/performance-accessibility.mdreferences/seo-aeo-geo-checklist.mdreferences/structured-data.mdreferences/validation-workflow.mdscripts/check-links.mjsscripts/check-metadata.mjsscripts/check-placeholders.mjsscripts/check-site-files.mjsscripts/check-structured-data.mjsscripts/inspect-url.mjsscripts/list-search-console-sites.mjsscripts/run-lighthouse.mjsscripts/run-pagespeed.mjsscripts/submit-sitemap.mjsUse this skill to create, improve, audit, deploy, or validate landing pages.
Do not use this skill for tiny copy, style, or component edits unless SEO, conversion, accessibility, performance, deployment, or launch readiness is part of the request.
Service schema for services; use Product schema only with real product offer data.references/landing-page-workflow.md.references/framework-implementation.md.references/content-conversion.md.references/seo-aeo-geo-checklist.md.references/local-business-seo.md.references/structured-data.md.references/performance-accessibility.md.references/validation-workflow.md.references/deployment-domain-search-console.md.Use templates only as starting points. Adapt them to the project before inserting:
templates/metadata-head.htmltemplates/site.webmanifesttemplates/robots.txttemplates/sitemap.xmltemplates/local-business-jsonld.htmltemplates/website-jsonld.htmltemplates/website-with-search-jsonld.htmltemplates/organization-jsonld.htmltemplates/person-jsonld.htmltemplates/breadcrumb-jsonld.htmltemplates/faq-jsonld.htmltemplates/service-offer-catalog-jsonld.htmltemplates/static-landing-page.htmltemplates/launch-checklist.mdtemplates/privacy-notice.mdScripts are optional helpers. Run them from the target project root when the environment allows it:
scripts/check-metadata.mjs [html-file] [--no-write] - static metadata, headings, image, favicon, manifest, and basic SEO checks.scripts/check-structured-data.mjs [html-file] [--no-write] - JSON-LD parse and schema sanity checks.scripts/check-links.mjs [html-file] [--network] [--no-write] - local links, fragments, assets, and optional external URL checks.scripts/check-site-files.mjs [site-root] [--no-write] - robots.txt, sitemap.xml, site.webmanifest, and common icon checks; pass public for framework public folders.scripts/check-placeholders.mjs [paths...] [--no-write] - unreplaced {{PLACEHOLDER}} checks after templates are applied.scripts/run-lighthouse.mjs <url> [mobile|desktop] - Lighthouse JSON report.scripts/summarize-lighthouse.mjs [lighthouse-json-report] [--no-write] - Markdown summary from a Lighthouse report.scripts/run-pagespeed.mjs <url> [mobile|desktop] - PageSpeed Insights JSON report.scripts/summarize-pagespeed.mjs [pagespeed-json-report] [--no-write] - Markdown summary from a PageSpeed report.scripts/list-search-console-sites.mjs [--no-write] - list verified Search Console properties.scripts/submit-sitemap.mjs <search-console-site-url> <sitemap-url> - submit a sitemap through Search Console API.scripts/inspect-url.mjs <inspection-url> <search-console-site-url> [language-code] - inspect URL indexing data through Search Console API.Use PAGESPEED_API_KEY for PageSpeed API calls when available.
Use GOOGLE_SEARCH_CONSOLE_ACCESS_TOKEN only for supported Search Console API actions.
If a requested API-backed action needs credentials and the required environment variable is missing, ask the user for the secret only at that point and use it for the current session only by default. Do not write secrets to .env, tracked files, or project config unless the user explicitly asks for that.
If credentials, network, dependencies, or quota are unavailable, do not fake success. Explain the blocker and provide manual steps or fallback commands.
When unsure about usage, run the script with missing arguments to see its usage text or read references/validation-workflow.md.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Searches MemPalace before answering questions about past work, people, projects, or prior decisions. Returns verbatim stored content instead of guessing from model memory.
npx claudepluginhub luci6n/seo-landing-page-skill --plugin build-seo-landing-page-skills