SEO Ready

Name: SEO Ready
Availability: InStock
Author: JStaRFilms

Free Verified 140 lines By JStaRFilms SEO

Description

Make any Next.js page SEO-ready with metadata, structured data, sitemap, and accessibility best practices.

How It Works

Click to enlarge

What Claude Learns

→ When to Use
→ Phase 1: Global Setup (Once Per Project)
→ Check Root Metadata
→ Sitemap
→ Robots.txt
→ Web Manifest (PWA)

Installation

1. Visit the GitHub repository: https://github.com/JStaRFilms/VibeCode-Protocol-Suite
2. Copy the SKILL.md file contents
3. Save to ~/.claude/commands/skill-name.md
4. Restart Claude Code to load the new skill

Use Cases

SEO optimization requests

Before launching pages to production

When asked about metadata or search visibility

Accessibility audits

When to Use

Phase 1: Global Setup (Once Per Project)

Related Skills

Frequently Asked Questions

How detailed is the SEO Ready skill?

SEO Ready contains 140 lines of structured instructions covering 6 key areas. It provides detailed guidance including specific implementation patterns, not just surface-level tips.

Is SEO Ready free to use?

Yes, SEO Ready is completely free. You can download the SKILL.md file or copy it to your clipboard directly from the skill page.

What will Claude Code learn from this skill?

Claude Code will gain expertise in: When to Use; Phase 1: Global Setup (Once Per Project); Check Root Metadata; and 3 more areas.

Download SKILL.md GitHub

---
name: seo-ready
description: Make any Next.js page SEO-ready with metadata, structured data, sitemap, and accessibility best practices.
---

# SEO Ready Skill

Transform Next.js pages into fully SEO-optimized pages.

## When to Use
- SEO optimization requests
- Before launching pages to production
- When asked about metadata or search visibility
- Accessibility audits

## Phase 1: Global Setup (Once Per Project)

### Check Root Metadata
```bash
head -50 src/app/layout.tsx
```

Required in `layout.tsx`:
```typescript
export const metadata: Metadata = {
  title: { default: "Site Name", template: "%s | Site Name" },
  description: "...",
  metadataBase: new URL("https://your-domain.com"),
  openGraph: { /* ... */ },
  twitter: { /* ... */ },
};
```

### Sitemap
```bash
ls src/app/sitemap.ts 2>/dev/null || echo "MISSING"
```

If missing, create `src/app/sitemap.ts`:
```typescript
import { MetadataRoute } from 'next'

export default function sitemap(): MetadataRoute.Sitemap {
  const baseUrl = 'https://your-domain.com'
  return [
    { url: baseUrl, lastModified: new Date(), changeFrequency: 'yearly', priority: 1 },
  ]
}
```

### Robots.txt
Create `src/app/robots.ts` if missing.

### Web Manifest (PWA)
Create `src/app/manifest.ts` if missing.

### Icons
Check: `src/app/icon.png`, `src/app/apple-icon.png`

### OpenGraph Image
Options:
- **Static**: `src/app/opengraph-image.png` (1200x630px)
- **Dynamic**: `src/app/opengraph-image.tsx`

### JSON-LD Structured Data
Add to `` in layout:
```tsx

```

## Phase 2: Per-Page Optimization

### Server Component Check
If page starts with `'use client'`, refactor:
- Move client logic to `src/features//components/`
- Page file becomes Server Component that imports client component

### Page Metadata
```typescript
import { Metadata } from 'next';

export const metadata: Metadata = {
  title: "Page Title",  // Becomes "Page Title | Site Name"
  description: "Specific description for this page.",
};
```

### Semantic HTML Audit
- `` for primary content
- `` with `id` for anchors
- `` for standalone content
- Proper heading hierarchy (`` → `` etc.)

### Image Optimization
- Use `` component
- Required: `alt`, `width`, `height`

## Phase 3: Accessibility

- ARIA labels on interactive elements
- `` set correctly
- Keyboard navigable

## Phase 4: Verification

```bash
pnpm build
pnpm dev
# Visit /sitemap.xml and /robots.txt
```

## Checklist
| Item | Status |
|------|--------|
| Root metadata | [ ] |
| sitemap.ts | [ ] |
| robots.ts | [ ] |
| manifest.ts | [ ] |
| Icons | [ ] |
| OpenGraph image | [ ] |
| JSON-LD | [ ] |
| Page metadata | [ ] |
| Semantic HTML | [ ] |
| Build passes | [ ] |

## References

Content writing patterns merged from [coreyhaines31/marketingskills](https://github.com/coreyhaines31/marketingskills):

- [AEO & GEO Patterns](references/aeo-geo-patterns.md): Content blocks optimized for answer engines and AI citation
- [AI Writing Detection](references/ai-writing-detection.md): Words and phrases to avoid (the "anti-slop" guide)