Token导航 LogoToken导航

Agent Skill · 前端设计

seo-meta(SEO meta 测试)

用于辅助前端页面、组件、样式和交互逻辑的开发与维护。它适合让 Agent 生成或审查 React、Next.js、Vue、Tailwind、CSS 等相关代码,整理组件结构,或定位布局和性能问题。使用时需要结合项目现有设计系统、路由和构建方式,避免只生成孤立片段;涉及页面改动时,应配合本地预览和构建检查确认视觉效果。

seo-meta 是前端设计类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证为 MIT,第三方扫描已通过,按安装量在前端设计类的 10,216 个 Skill 里排第 724。

总安装 13,056周安装 544GitHub Stars 750下载 4,352核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/jezweb/claude-skills --skill seo-meta

这个 Skill 是做什么的

前端设计类 Skill 关注页面结构、视觉规范和组件写法,输出通常是可运行的界面代码。

每个页面都有完整的 SEO 元标签,涵盖标题、描述、开放图谱、Twitter 卡和 JSON-LD 结构化数据。

提供带有可信度修饰符的主页、服务、位置、关于和联系页面的标题标签模式、元描述公式和字符限制 包括开放图谱配置(1200x630px 图像规格)、具有回退行为的 Twitter 卡设置以及规范 URL 最佳实践 提供四种 JSON-LD 架构类型:LocalBusiness(具有特定于业务的子类型,如 Plumber)、Service、FAQ 和用于丰富摘要的 BreadcrumbList 包含验证工具、错误预防检查表和测试工作流程,涵盖 Google Rich Results、Facebook Debugger 和 Twitter Card Validator

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

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

seo-meta 怎么安装?

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

seo-meta 支持哪些 AI 工具?

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

seo-meta 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

seo-meta 是免费的吗?

来源标注的许可证是 MIT。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

seo-meta 用的人多吗?

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

seo-meta 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 3 个目录同时收录,说明这个 Skill 流传比较广。
  • 许可证明确为 MIT,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理前端设计类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

前端设计类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
frontend-design

前端设计 · Codex、Claude

8,823,360126,072只读MIT通过
vercel-composition-patterns

Vercel 组合模式 · Codex、Claude

3,858,81625,893需要联网MIT通过
vercel-react-native-skills

Vercel React native skills 前端 · Codex、Claude

2,468,66425,878只读MIT通过
adapt

adapt 搜索 · Codex、Claude

2,027,04023,125操作浏览器未明确通过
bolder

bolder 分析 · Codex、Claude

2,004,28823,130只读未明确通过
seo-meta

SEO meta 测试 · 本页

13,056750需要联网MIT通过

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

SKILL.md 原文

SEO Meta Tags

Status: Production Ready ✅ Last Updated: 2026-01-14 Source: Schema.org, Open Graph Protocol, Twitter Developer Docs


Quick Start

Every page needs:

<head>
  {/* Basic SEO */}
  <title>Service in Location | Brand Name</title>
  <meta name="description" content="Value prop. Differentiator. Call to action." />
  <link rel="canonical" href="https://example.com/page" />

  {/* Open Graph */}
  <meta property="og:title" content="Service in Location" />
  <meta property="og:description" content="Value prop. Differentiator. CTA." />
  <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" />
  <meta name="twitter:title" content="Service in Location" />
  <meta name="twitter:description" content="Value prop. Differentiator. CTA." />
  <meta name="twitter:image" content="https://example.com/og-image.jpg" />

  {/* JSON-LD Structured Data */}
  <script type="application/ld+json">
    {JSON.stringify({
      "@context": "https://schema.org",
      "@type": "LocalBusiness",
      "name": "Business Name",
      "description": "What we do",
      "@id": "https://example.com",
      "url": "https://example.com",
      "telephone": "+61-XXX-XXX-XXX",
      "address": {
        "@type": "PostalAddress",
        "streetAddress": "123 Main St",
        "addressLocality": "Sydney",
        "addressRegion": "NSW",
        "postalCode": "2000",
        "addressCountry": "AU"
      }
    })}
  </script>
</head>

Title Tag Patterns

Character Limits:

  • Google: 50-60 characters (desktop), 78 (mobile)
  • Social: 60-70 characters

Page Type Formulas:

Page TypePatternExample
Home[Brand] - [Primary Service] in [Location]Acme Plumbing - 24/7 Emergency Plumber Sydney
Service[Service] in [Location] \[Brand]Hot Water Repairs Sydney \Acme Plumbing
Location[Service] [Suburb] \[Brand]Plumber Bondi \Acme Plumbing
AboutAbout [Brand] - [Tagline/USP]About Acme - Licensed Plumbers Since 1995
ContactContact [Brand] - [Location] \[Phone]Contact Acme Plumbing - Sydney \1300 XXX XXX

Title Modifiers (add credibility):

  • 24/7 Emergency
  • Licensed & Insured
  • Free Quotes
  • Same Day Service
  • Family Owned
  • Award Winning

Anti-Patterns (avoid):

  • ❌ "Welcome to..." (wastes characters)
  • ❌ Keyword stuffing (plumber plumbing plumbers)
  • ❌ ALL CAPS (looks spammy)
  • ❌ Special characters (★ § ¶)

Meta Description Patterns

Character Limits:

  • Desktop: 155-160 characters
  • Mobile: 120-130 characters

Formula:

[Value prop] [Service] in [Location]. [Differentiator]. [CTA].

Examples by Page Type:

Home Page:

Fast, reliable plumbing services in Sydney. 24/7 emergency response, licensed plumbers, upfront pricing. Call 1300 XXX XXX for same-day service.

Service Page:

Expert hot water repairs in Sydney. Fix or replace electric, gas & solar systems. Licensed technicians, 1-year warranty. Book online or call 1300 XXX XXX.

Location Page:

Trusted plumber in Bondi. Blocked drains, leaks, hot water, gas fitting. Same-day service, upfront quotes. Call your local plumber on 1300 XXX XXX.

Power Words (use sparingly):

  • Trust: Licensed, Certified, Insured, Guaranteed, Trusted
  • Speed: Fast, Quick, Same Day, Emergency, 24/7, Instant
  • Value: Affordable, Competitive, Upfront, No Hidden Fees, Free Quote
  • Local: Local, Nearby, Your Area, [Suburb Name]
  • Quality: Expert, Professional, Experienced, Award Winning

Open Graph Tags

Required Tags:

<meta property="og:title" content="Service in Location" />
<meta property="og:description" content="Value prop. Differentiator. CTA." />
<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" />

Image Requirements:

  • Dimensions: 1200x630px (1.91:1 ratio)
  • Format: JPG or PNG (JPG preferred for file size)
  • File size: <1MB (ideally <300KB)
  • Text overlay: Keep important text center (safe zone: 1000x530)

og:type Values by Page Type:

Page Typeog:type
Home, Service, Locationwebsite
Blog Postarticle
Business Profilebusiness.business

Optional but Recommended:

<meta property="og:site_name" content="Brand Name" />
<meta property="og:locale" content="en_AU" />

Twitter Cards

Card Types:

TypeUse Case
summarySmall square image (1:1), basic info
summary_large_imageLarge image (1.91:1), most common

Required Tags:

<meta name="twitter:card" content="summary_large_image" />
<meta name="twitter:title" content="Service in Location" />
<meta name="twitter:description" content="Value prop. Differentiator. CTA." />
<meta name="twitter:image" content="https://example.com/og-image.jpg" />

Optional:

<meta name="twitter:site" content="@yourbrand" />
<meta name="twitter:creator" content="@authorhandle" />

Fallback Behavior:

  • If twitter:title missing, uses og:title
  • If twitter:description missing, uses og:description
  • If twitter:image missing, uses og:image

Best Practice: Define og:* tags first, only add twitter:* if values differ.


JSON-LD Structured Data

LocalBusiness Schema (Most Important)

Use for homepage and contact page:

{
  "@context": "https://schema.org",
  "@type": "Plumber",
  "name": "Acme Plumbing",
  "description": "Licensed plumbing services in Sydney",
  "@id": "https://acmeplumbing.com.au",
  "url": "https://acmeplumbing.com.au",
  "logo": "https://acmeplumbing.com.au/logo.png",
  "image": "https://acmeplumbing.com.au/og-image.jpg",
  "telephone": "+61-XXX-XXX-XXX",
  "email": "info@acmeplumbing.com.au",
  "priceRange": "$$",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "123 Main Street",
    "addressLocality": "Sydney",
    "addressRegion": "NSW",
    "postalCode": "2000",
    "addressCountry": "AU"
  },
  "geo": {
    "@type": "GeoCoordinates",
    "latitude": -33.8688,
    "longitude": 151.2093
  },
  "openingHoursSpecification": [
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
      "opens": "07:00",
      "closes": "17:00"
    }
  ],
  "sameAs": [
    "https://facebook.com/acmeplumbing",
    "https://instagram.com/acmeplumbing"
  ]
}

Specific Business Types (instead of generic LocalBusiness):

  • Plumber, Electrician, Locksmith, HVAC (HVACBusiness)
  • Dentist, Attorney, Accountant
  • Restaurant, Cafe, FoodEstablishment
  • Store, AutoRepair, BeautySalon

Service Schema

Use for service pages:

{
  "@context": "https://schema.org",
  "@type": "Service",
  "name": "Hot Water Repairs",
  "description": "Fast hot water system repairs in Sydney",
  "provider": {
    "@type": "Plumber",
    "name": "Acme Plumbing",
    "url": "https://acmeplumbing.com.au"
  },
  "areaServed": {
    "@type": "City",
    "name": "Sydney"
  },
  "availableChannel": {
    "@type": "ServiceChannel",
    "serviceUrl": "https://acmeplumbing.com.au/hot-water-repairs",
    "servicePhone": "+61-XXX-XXX-XXX"
  }
}

FAQ Schema (Rich Snippets)

Use for FAQ sections:

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "How much does a plumber cost in Sydney?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Plumbing rates in Sydney typically range from $100-$150 per hour for standard work. Emergency callouts may incur higher rates. We provide upfront quotes before starting work."
      }
    },
    {
      "@type": "Question",
      "name": "Do you offer same-day service?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes, we offer same-day plumbing service across Sydney for urgent repairs. Call us before 2pm for same-day availability."
      }
    }
  ]
}

BreadcrumbList Schema

Use on all pages except homepage:

{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "Home",
      "item": "https://acmeplumbing.com.au"
    },
    {
      "@type": "ListItem",
      "position": 2,
      "name": "Services",
      "item": "https://acmeplumbing.com.au/services"
    },
    {
      "@type": "ListItem",
      "position": 3,
      "name": "Hot Water Repairs",
      "item": "https://acmeplumbing.com.au/hot-water-repairs"
    }
  ]
}

Canonical URLs

When to Use:

  • Every page should have a self-referencing canonical
  • Duplicate content (pagination, filters, print versions)
  • Syndicated content
  • Cross-domain duplicates

Self-Referencing Canonical:

<!-- Always include, even if no duplicates -->
<link rel="canonical" href="https://example.com/page" />

Pagination:

<!-- On page 2+ -->
<link rel="canonical" href="https://example.com/services" />
<!-- Not https://example.com/services?page=2 -->

Common Mistakes:

  • ❌ Missing canonical (Google chooses for you)
  • ❌ Relative URLs (use absolute URLs)
  • ❌ Canonical pointing to different content
  • ❌ Multiple canonicals (only one per page)

Validation Tools

Check Your Implementation:

ToolPurposeURL
Google Rich Results TestTest structured datasearch.google.com/test/rich-results
Schema Markup ValidatorValidate JSON-LDvalidator.schema.org
Facebook DebuggerTest Open Graph tagsdevelopers.facebook.com/tools/debug
Twitter Card ValidatorTest Twitter Cardscards-dev.twitter.com/validator
Screaming FrogAudit all pagesscreamingfrog.co.uk/seo-spider

Browser Extensions:

  • SEO Meta in 1 Click (Chrome)
  • META SEO inspector (Firefox)

Quick Reference Checklist

For every page, include:

  • <title> (50-60 chars, unique per page)
  • <meta name="description"> (150-160 chars, unique per page)
  • <link rel="canonical"> (absolute URL)
  • Open Graph tags (og:title, og:description, og:image, og:url, og:type)
  • Twitter Card tags (twitter:card, twitter:title, twitter:description, twitter:image)
  • JSON-LD structured data (LocalBusiness on homepage, Service on service pages)
  • BreadcrumbList schema (all pages except homepage)
  • Mobile viewport meta tag
  • Charset meta tag (UTF-8)

Never:

  • ❌ Duplicate titles across pages
  • ❌ Use "Welcome to..." in titles
  • ❌ Omit og:image (critical for social sharing)
  • ❌ Use generic @type (LocalBusiness instead of Plumber)
  • ❌ Skip CTA in meta description

Error Prevention

Common Issues

IssueCauseFix
No rich snippets in searchInvalid JSON-LDUse validator.schema.org, check commas/quotes
Social share shows wrong imageog:image missing or wrong sizeUse 1200x630px, test with Facebook Debugger
Title truncated in searchToo longKeep under 60 chars
Description truncatedToo longKeep under 160 chars
Multiple pages rank for same keywordDuplicate titlesMake each title unique

Testing Workflow

  1. Validate HTML: Use W3C validator
  2. Test Structured Data: Google Rich Results Test
  3. Test Social Sharing: Facebook Debugger + Twitter Card Validator
  4. Mobile Preview: Google Search Console URL Inspection
  5. Cross-Browser Check: Test meta rendering in Chrome/Firefox/Safari

Best Practices Summary

Title Tags:

  • 50-60 characters maximum
  • Include primary keyword + location + brand
  • Unique for every page
  • Use modifiers (24/7, Licensed, Free) sparingly

Meta Descriptions:

  • 150-160 characters maximum
  • Include value prop + differentiator + CTA
  • Write for humans, not search engines
  • Every page needs unique description

Open Graph:

  • Always include og:image (1200x630px)
  • Use absolute URLs
  • Keep og:title under 60 chars
  • Test with Facebook Debugger before launch

JSON-LD:

  • Use specific @type (Plumber, not LocalBusiness)
  • Include all contact info (phone, address, email)
  • Add openingHoursSpecification for better display
  • Validate with schema.org validator

Canonical URLs:

  • Every page needs canonical
  • Always use absolute URLs
  • Self-referencing is good practice
  • Only one canonical per page

Production Notes:

  • Use react-helmet-async for React apps (SSR-safe)
  • Generate JSON-LD dynamically from CMS/database
  • Cache meta tag components for performance
  • Monitor Search Console for indexing issues
  • Update structured data when business details change

平台分布

Claude Code

27.85%
按下载量换算1,212

Antigravity

22.43%
按下载量换算976

Gemini CLI

16.14%
按下载量换算702

Cursor

12.04%
按下载量换算524

OpenCode

7.42%
按下载量换算323

Codex

3.23%
按下载量换算141

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。

继续浏览同类 Skills