Token导航 LogoToken导航

Agent Skill · 开发规范

seo-best-practices(SEO 最佳实践)

seo-best-practices 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

seo-best-practices 是开发规范类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为权限未标注;许可证信息还不明确,暂无第三方扫描结果,按安装量在开发规范类的 1,265 个 Skill 里排第 434。

总安装 1,693周安装 72GitHub Stars 33下载 593核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:seo-best-practices(SEO 最佳实践)
来源仓库:https://github.com/asyrafhussin/agent-skills
仓库路径:skills/seo-best-practices
安装命令:
npx skills add https://github.com/asyrafhussin/agent-skills --skill seo-best-practices
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/asyrafhussin/agent-skills --skill seo-best-practices

这个 Skill 是做什么的

开发规范类 Skill 用来统一代码风格、目录结构和评审口径,产出多为检查清单或改写建议。

用于处理 GitHub 仓库状态、Issue、Pull Request 及代码协作事项,适合在 Codex、Claude、Cursor、Gemini CLI 中围绕项目变更进行信息整理与流程跟踪。当前未提供有效技能描述文档,无法确认具体用途或能力边界。

安装前应确认是否具备 GitHub 访问权限,并评估是否会引入外部依赖或执行敏感命令,防止意外修改或数据泄露。建议查看原始仓库获取更多信息,谨慎启用未知功能。seo-best-practices 属于开发规范类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/seo-best-practices

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/asyrafhussin/agent-skills --skill seo-best-pra…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    权限没有明确标注,第一次使用时只给一个无关紧要的任务,观察它到底读了哪些文件和网络。

常见问题

6 条

seo-best-practices 怎么安装?

在终端执行 npx skills add https://github.com/asyrafhussin/agent-skills --skill seo-best-practices。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

seo-best-practices 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

seo-best-practices 需要什么权限?

权限级别没有明确标注。第一次使用时建议只给无关紧要的任务,观察它实际读写了哪些内容。

seo-best-practices 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

seo-best-practices 用的人多吗?

公开数据是累计安装 1,693 次,近一周安装 72 次,下载 593 次,GitHub 33 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

seo-best-practices 安全吗?

没有查到第三方扫描结果,安全性无法从公开资料判断,安装前请自行审查源码、依赖和命令行为。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 没有第三方扫描结果,安全性只能靠自己读源码判断。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理开发规范类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 要求有安全扫描结论才肯安装的团队。
  • 需要厂商级技术支持和 SLA 的生产系统。

开发规范类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
vercel-react-best-practices

Vercel React 最佳实践 · Codex、Claude

8,490,72025,918操作浏览器MIT通过
web-design-guidelines

网页设计指南 · Codex、Claude

6,686,01625,885需要联网MIT有提醒
remotion-best-practices

Remotion 最佳实践 · Codex、Claude

6,505,6323,027操作浏览器MIT有提醒
supabase-postgres-best-practices

Supabase Postgres 最佳实践 · Codex、Claude

3,175,5232,030需要联网MIT通过
next-best-practices

Next.js 最佳实践 · Codex、Claude

1,848,240841操作浏览器MIT通过
seo-best-practices

SEO 最佳实践 · 本页

1,69333权限未标注未明确未收录

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

SEO Best Practices

Comprehensive SEO patterns for web applications built with React and Laravel. Contains 31 rules across 8 categories covering Core Web Vitals, technical SEO, structured data, performance, social sharing, and mobile-first indexing. Supports both coding reference and audit mode.

Metadata

  • Version: 1.2.0
  • Scope: Laravel Blade and Laravel + Inertia.js + React
  • Rule Count: 31 rules across 8 categories
  • License: MIT

How to Audit

When the user asks to "audit SEO", "check SEO", or "review SEO" — run the checklist below against their codebase.

Audit Step 1: Determine Scope

  • If arguments provided ($ARGUMENTS): audit only those pages or files
  • If no arguments: audit all pages and layouts in the codebase

Audit Step 2: Detect Project Type

Use the detection logic in "Step 1: Detect Project Type" below to determine Laravel Blade vs Laravel + Inertia + React.

Audit Step 3: Run SEO Checklist

Work through every item below. For each, output:

  • PASS — brief confirmation of what was verified
  • FAIL — exact file:line, description of the issue, and fix recommendation
  • N/A — if the check does not apply to this project
Core Web Vitals
  • Hero/above-the-fold images use fetchpriority="high" and are preloaded (LCP < 2.5s)
  • No long-running JavaScript tasks blocking interaction (INP < 200ms)
  • All images and embeds have explicit width/height attributes (CLS < 0.1)
  • No dynamically injected content that shifts layout without reserved space
Technical SEO
  • Every page has a unique <title> tag (50-60 characters)
  • Every page has a <meta name="description"> (150-160 characters)
  • Every page has a <link rel="canonical"> pointing to the correct URL
  • robots.txt exists and does not block important pages
  • XML sitemap exists and includes all indexable pages
  • URLs are clean, lowercase, hyphenated — no query params for indexable pages
On-Page SEO
  • One <h1> per page containing the primary keyword
  • Heading hierarchy is sequential (h1 → h2 → h3) — no skipped levels
  • Images have descriptive alt text (not empty, not "image", not filename)
  • Internal links use descriptive anchor text (not "click here")
  • Semantic HTML used (<article>, <section>, <nav>, <main>)
Structured Data
  • JSON-LD structured data present on key pages (Article, Product, FAQ, BreadcrumbList)
  • JSON-LD uses @graph when combining multiple schema types
  • Structured data validates with Google Rich Results Test (no errors)
  • Organization/WebSite schema present on homepage
Performance SEO
  • Images use modern formats (WebP/AVIF) with fallbacks
  • Below-the-fold images use loading="lazy"
  • Fonts use font-display: swap or optional
  • Critical resources use <link rel="preconnect"> or <link rel="preload">
Social Sharing
  • Open Graph tags present (og:title, og:description, og:image, og:url, og:type)
  • og:image is at least 1200x630px
  • Twitter Card tags present (twitter:card, at minimum summary_large_image)
React/SPA SEO (if applicable)
  • SSR or SSG configured for indexable pages — not client-side only
  • Meta tags update on route change (via <Head> component or equivalent)
  • head-key attribute used to prevent duplicate meta tags (Inertia.js)
Mobile-First
  • <meta name="viewport" content="width=device-width, initial-scale=1"> present
  • Content parity between mobile and desktop (no hidden content)
  • Touch targets are at least 48x48px with adequate spacing

Audit Step 4: Summary

End the audit with:

## SEO Audit Summary
- **PASS**: X checks
- **FAIL**: X checks
- **N/A**: X checks
- **Top Priority Fixes**: (list the 3 most impactful FAIL items)

When to Apply

Reference these guidelines when:

  • Running an SEO audit on a codebase
  • Adding meta tags (<title>, description, canonical, robots)
  • Implementing structured data (JSON-LD / Schema.org)
  • Optimizing Core Web Vitals (LCP, INP, CLS)
  • Setting up Open Graph and Twitter Card meta tags
  • Creating sitemaps and robots.txt
  • Building SEO-friendly React SPAs
  • Configuring Laravel SEO middleware and packages
  • Optimizing images, fonts, and loading performance for search

Step 1: Detect Project Type

Always check the project stack before giving advice. Different stacks need different SEO approaches.

Check package.json and project structure:

SignalProject Type
@inertiajs/react in dependenciesLaravel + Inertia + React
resources/views/**/*.blade.php only (no React)Laravel Blade (server-rendered)

If Laravel Blade: Apply tech-, onpage-, schema-, perf-, social-, mobile- rules. Meta tags go in Blade layouts. Sitemaps via spatie/laravel-sitemap. Skip spa- rules — pages are already server-rendered.

If Laravel + Inertia + React: Apply all rules. Meta tags via @inertiaHead in Blade layout + <Head> component from @inertiajs/react in React pages. For SSR, create resources/js/ssr.jsx using createServer from @inertiajs/react/server, add ssr: 'resources/js/ssr.jsx' to Vite config, build with vite build && vite build --ssr, and run php artisan inertia:start-ssr. Use head-key attribute on meta tags to prevent duplicates between layout and page. Focus on schema-, social-, and perf- rules.

Rule Categories by Priority

PriorityCategoryImpactPrefix
1Core Web VitalsCRITICALcwv-
2Technical SEOCRITICALtech-
3On-Page SEOHIGHonpage-
4Structured DataHIGHschema-
5Performance SEOHIGHperf-
6Social SharingHIGHsocial-
7React/SPA SEOHIGHspa-
8Mobile-FirstMEDIUMmobile-

Quick Reference

1. Core Web Vitals (CRITICAL)

  • cwv-lcp - Largest Contentful Paint optimization (<2.5s)
  • cwv-inp - Interaction to Next Paint optimization (<200ms)
  • cwv-cls - Cumulative Layout Shift prevention (<0.1)

2. Technical SEO (CRITICAL)

  • tech-meta-tags - Essential HTML meta tags (title, description, canonical)
  • tech-canonical-urls - Canonical URL implementation
  • tech-robots-txt - Robots.txt configuration
  • tech-sitemap-xml - XML sitemap generation
  • tech-url-structure - SEO-friendly URL patterns

3. On-Page SEO (HIGH)

  • onpage-headings - Heading hierarchy and structure
  • onpage-semantic-html - Semantic HTML for SEO and accessibility
  • onpage-internal-linking - Internal linking strategy
  • onpage-images - Image optimization and alt text

4. Structured Data (HIGH)

  • schema-json-ld - JSON-LD structured data basics
  • schema-article - Article and BlogPosting markup
  • schema-product - Product schema for e-commerce
  • schema-breadcrumb - BreadcrumbList navigation markup
  • schema-graph - Combining multiple schema types with @graph
  • schema-faq - FAQ page schema markup
  • schema-validation - Structured data validation and monitoring

5. Performance SEO (HIGH)

  • perf-image-formats - Modern image formats (WebP/AVIF)
  • perf-lazy-loading - Lazy loading implementation
  • perf-font-loading - Web font loading strategy
  • perf-resource-hints - Preconnect, preload, and prefetch

6. Social Sharing (HIGH)

  • social-open-graph - Open Graph meta tags
  • social-twitter-cards - Twitter/X Card meta tags

7. React/SPA SEO (HIGH)

  • spa-rendering-strategy - SSR vs CSR vs SSG for SEO
  • spa-meta-management - Dynamic meta tag management
  • spa-routing - SPA routing and crawlability

8. Mobile-First (MEDIUM)

  • mobile-viewport - Viewport and responsive configuration
  • mobile-content-parity - Content parity between mobile and desktop
  • mobile-ux - Mobile UX requirements for SEO

Essential Patterns

Meta Tags (HTML)

<head>
  <meta charset="utf-8" />
  <meta name="viewport" content="width=device-width, initial-scale=1" />
  <title>Page Title — Site Name</title>
  <meta name="description" content="Concise 150-160 character description of page content." />
  <link rel="canonical" href="https://example.com/page" />

  <!-- Open Graph -->
  <meta property="og:title" content="Page Title" />
  <meta property="og:description" content="Description for social sharing." />
  <meta property="og:image" content="https://example.com/og-image.jpg" />
  <meta property="og:url" content="https://example.com/page" />
  <meta property="og:type" content="website" />

  <!-- Twitter Card -->
  <meta name="twitter:card" content="summary_large_image" />
</head>

JSON-LD Structured Data

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Article Title",
  "author": {
    "@type": "Person",
    "name": "Author Name"
  },
  "datePublished": "2026-03-14",
  "dateModified": "2026-03-14",
  "image": "https://example.com/article-image.jpg",
  "publisher": {
    "@type": "Organization",
    "name": "Site Name",
    "logo": {
      "@type": "ImageObject",
      "url": "https://example.com/logo.png"
    }
  }
}
</script>

React Meta Management (Inertia.js)

import { Head } from '@inertiajs/react'

interface Post {
  title: string;
  slug: string;
  excerpt: string;
  image: string;
}

function BlogPost({ post }: { post: Post }) {
  return (
    <>
      <Head>
        <title>{post.title} — Blog</title>
        <meta head-key="description" name="description" content={post.excerpt} />
        <link rel="canonical" href={`https://example.com/blog/${post.slug}`} />
        <meta property="og:title" content={post.title} />
        <meta property="og:description" content={post.excerpt} />
        <meta property="og:image" content={post.image} />
        <meta property="og:type" content="article" />
        <meta name="twitter:card" content="summary_large_image" />
      </Head>
      <article>{/* content */}</article>
    </>
  )
}

Core Web Vitals Quick Checks

LCP  < 2.5s   Preload hero image, use fetchpriority="high"
INP  < 200ms  Break long tasks, yield to main thread
CLS  < 0.1    Set width/height on images, reserve space for dynamic content

Image Optimization

<!-- Modern formats with fallback -->
<picture>
  <source srcset="hero.avif" type="image/avif" />
  <source srcset="hero.webp" type="image/webp" />
  <img
    src="hero.jpg"
    alt="Descriptive alt text for the image"
    width="1200"
    height="630"
    fetchpriority="high"
  />
</picture>

<!-- Responsive images -->
<img
  srcset="photo-400.webp 400w, photo-800.webp 800w, photo-1200.webp 1200w"
  sizes="(max-width: 600px) 400px, (max-width: 900px) 800px, 1200px"
  src="photo-800.webp"
  alt="Descriptive alt text"
  width="1200"
  height="800"
  loading="lazy"
/>

How to Use

Read individual rule files for detailed explanations and code examples:

rules/tech-meta-tags.md
rules/schema-json-ld.md
rules/cwv-lcp.md
rules/spa-rendering-strategy.md
rules/social-open-graph.md

Each rule file contains:

  • YAML frontmatter with metadata (title, impact, tags)
  • Brief explanation of why it matters
  • Incorrect example with explanation
  • Correct example with explanation
  • Framework-specific examples (React, Laravel)

References

Full Compiled Document

For the complete guide with all rules expanded: AGENTS.md

平台分布

Codex

35.18%
按下载量换算209

Claude

31.04%
按下载量换算184

Cursor

17.43%
按下载量换算103

Gemini CLI

9.75%
按下载量换算58

安全审计

暂无安全审计结果可展示。

权限和风险

权限未标注

当前来源未能明确判断权限范围,默认进入异常复核队列。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills