跳到正文
cccskills
免费在 GitHub 公开

content-seo

Use when creating or editing pages, blog posts, or content files, adding meta tags, or when Lighthouse SEO drops below 90.

中文简介正在准备中。当前显示原文说明。

holger1411/astrodeck星标 80(GitHub 80 + cccskills 0)
集成工具X (Twitter)

实测评分 未实测

查看安装方法

包含的文件(2)

  • SKILL.md5.0 KB
  • LEARNINGS.md652 B

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Content & SEO Skill

Canonical Sources

This skill references the following globals — read them BEFORE starting work:

  • system/globals/imagery.md — Alt text conventions, image formats

Domain

Content Collections, Meta Tags, OpenGraph, Structured Data, RSS, Sitemap

KPIs

MetricTargetMeasurement
Lighthouse SEO>90Lighthouse JSON → categories.seo.score * 100
Pages without Description0npm run check:kpis
Pages without OG-Image0HTML check in dist/

Rules

Content Collections Schema

// src/content.config.ts
import { defineCollection } from 'astro:content';
import { z } from 'astro/zod';
import { glob } from 'astro/loaders';

const blog = defineCollection({
  loader: glob({ pattern: '**/*.{md,mdx}', base: './src/content/blog' }),
  schema: z.object({
    title: z.string(),
    description: z.string().max(160),
    pubDate: z.coerce.date(),
    updatedDate: z.coerce.date().optional(),
    heroImage: z.string().optional(),
    draft: z.boolean().default(false),
    tags: z.array(z.string()).default([]),
    author: z.string().default('Team'),
  }),
});

SEO Component Usage

---
import BaseLayout from '@/layouts/BaseLayout.astro';

const title = "Page Title — Brand Name";
const description = "Page description, 150-160 characters, relevant keyword at the start.";
---

<BaseLayout title={title} description={description}>
  <!-- Content -->
</BaseLayout>

Meta-Description Best Practices

  • Length: 150-160 characters (Google truncates at ~160)
  • Keyword: Relevant keyword at the beginning
  • Unique: Every page needs its own description
  • Actionable: Call-to-action or value proposition
  • No duplicates: Never the same description for multiple pages

OpenGraph Tags

<meta property="og:title" content="{title}" />
<meta property="og:description" content="{description}" />
<meta property="og:image" content="{siteUrl}/og-image.png" />
<meta property="og:url" content="{canonicalUrl}" />
<meta property="og:type" content="website" />
<meta property="og:site_name" content="{siteName}" />
  • OG image: 1200x630px, PNG or JPG
  • Always use absolute URLs

Twitter Cards

<meta name="twitter:card" content="summary_large_image" />
<meta name="twitter:title" content="{title}" />
<meta name="twitter:description" content="{description}" />
<meta name="twitter:image" content="{siteUrl}/og-image.png" />

Canonical URLs

<link rel="canonical" href={Astro.url.href} />
  • Every page needs a canonical URL
  • Prevents duplicate content issues
  • AstroDeck sets this automatically in BaseLayout

Sitemap

// astro.config.mjs
import sitemap from '@astrojs/sitemap';

export default defineConfig({
  site: 'https://example.com',  // REQUIRED for sitemap
  integrations: [sitemap()],
});
  • site in astro.config.mjs MUST be set
  • Sitemap is generated automatically on npm run build
  • Output: dist/sitemap-index.xml

RSS Feed

// src/pages/rss.xml.ts
import rss from '@astrojs/rss';
import { getCollection } from 'astro:content';

export async function GET(context) {
  const blog = await getCollection('blog');
  return rss({
    title: 'Blog Title',
    description: 'Blog Description',
    site: context.site,
    items: blog.map((post) => ({
      title: post.data.title,
      pubDate: post.data.pubDate,
      description: post.data.description,
      link: `/blog/${post.id}/`,
    })),
  });
}

Structured Data (JSON-LD)

<script type="application/ld+json" set:html={JSON.stringify({
  "@context": "https://schema.org",
  "@type": "WebSite",
  "name": siteName,
  "url": siteUrl,
})} />

For blog posts:

<script type="application/ld+json" set:html={JSON.stringify({
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": title,
  "description": description,
  "datePublished": pubDate,
  "author": { "@type": "Person", "name": author },
})} />

Non-Negotiable

These rules always apply — even under time pressure, even when "SEO isn't that important":

  • Every page needs a meta description. "It's just an internal page" — Google indexes everything that's publicly accessible.
  • Every page needs exactly one <h1>. Zero or multiple h1s destroy heading hierarchy and cost SEO points.
  • No duplicate titles. "AstroDeck ... | AstroDeck" happens when the page title includes the brand — the layout appends it automatically.
  • Canonical URL is mandatory. Even for "simple" pages. Without canonical, crawlers create duplicate content issues.
  • Don't guess structured data. JSON-LD schema must be valid. Better to omit than to ship invalid schema — Google penalizes invalid markup.

Before Applying

Read LEARNINGS.md in this directory to avoid known anti-patterns.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Use when creating or modifying any UI element visible to the user, reviewing HTML markup, adding interactive elements, or when Lighthouse Accessibility drops below 90.

中文简介正在准备中。当前显示原文说明。

holger1411/astrodeck802026年9月5日 更新

astro

免费

Use when creating or modifying .astro/.tsx files, configuring astro.config.mjs, working with Content Collections, or when TypeScript or build errors occur.

中文简介正在准备中。当前显示原文说明。

holger1411/astrodeck802026年9月5日 更新

qa

免费

Use when completing any task (final validation step), running audits, preparing for deployment, or when ESLint/TypeScript/build errors occur.

中文简介正在准备中。当前显示原文说明。

holger1411/astrodeck802026年9月5日 更新

readme

免费

Use when starting work on an AstroDeck project, needing to understand the project structure, or looking up available components, sections, and layouts.

中文简介正在准备中。当前显示原文说明。

holger1411/astrodeck802026年9月5日 更新

tailwind

免费

Use when writing or reviewing any CSS class, changing colors, modifying globals.css, or when hardcoded colors or inline styles are detected.

中文简介正在准备中。当前显示原文说明。

holger1411/astrodeck802026年9月5日 更新

ui-design

免费

Use when creating or modifying any visible UI element, adjusting spacing or typography, reviewing visual consistency, or when Lighthouse Performance drops below 90.

中文简介正在准备中。当前显示原文说明。

holger1411/astrodeck802026年9月5日 更新

查看 holger1411 的全部技能

报告此技能的问题