Complete SEO setup for Next.js 16+ apps with metadata, sitemaps, robots.txt, and Core Web Vitals guidance.
Works with
Covers essential files (root metadata, dynamic sitemaps, robots configuration) with ready-to-use TypeScript examples for App Router
Includes rendering strategy comparison (SSG, SSR, ISR, CSR) and Core Web Vitals targets (LCP, INP, CLS) for performance optimization
Provides quick audit checklist, common mistakes to avoid, and dynamic metadata patterns for product pages and canoni
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionnextjs-seoExecute the skills CLI command in your project's root directory to begin installation:
Fetches nextjs-seo from laguagu/claude-code-nextjs-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate nextjs-seo. Access via /nextjs-seo in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
43
total installs
43
this week
21
GitHub stars
0
upvotes
Run in your terminal
43
installs
43
this week
21
stars
Comprehensive SEO guide for Next.js 16+ applications using App Router.
Next.js 16+ App Router (validated against 16.2.2 docs)
Run this checklist for any Next.js project:
curl https://your-site.com/robots.txtcurl https://your-site.com/sitemap.xml<title> and <meta name="description">application/ld+jsonimport type { Metadata, Viewport } from 'next';
// Viewport (separate export required in Next.js 14+)
export const viewport: Viewport = {
width: 'device-width',
initialScale: 1,
maximumScale: 5,
userScalable: true,
themeColor: [
{ media: '(prefers-color-scheme: light)', color: '#ffffff' },
{ media: '(prefers-color-scheme: dark)', color: '#0a0a0a' },
],
};
export const metadata: Metadata = {
metadataBase: new URL('https://your-site.com'),
title: {
default: 'Site Title - Main Keyword',
template: '%s | Site Name',
},
description: 'Compelling description with keywords (150-160 chars)',
keywords: ['keyword1', 'keyword2', 'keyword3'],
openGraph: {
type: 'website',
locale: 'en_US',
url: 'https://your-site.com',
siteName: 'Site Name',
title: 'Site Title',
description: 'Description for social sharing',
images: [{ url: '/og-image.png', width: 1200, height: 630, alt: 'Site preview' }],
},
twitter: {
card: 'summary_large_image',
title: 'Site Title',
description: 'Description for Twitter',
images: ['/og-image.png'],
},
alternates: {
canonical: '/',
},
robots: {
index: true,
follow: true,
},
};
import type { MetadataRoute } from 'next';
export default function sitemap(): MetadataRoute.Sitemap {
const baseUrl = 'https://your-site.com';
return [
{
url: baseUrl,
lastModified: new Date(),
changeFrequency: 'weekly',
priority: 1,
images: [`${baseUrl}/og-image.png`], // Next.js 16 Image Sitemap
},
{
url: `${baseUrl}/about`,
lastModified: new Date(),
changeFrequency: 'monthly',
priority: 0.8,
},
];
}
import type { MetadataRoute } from 'next';
export default function robots(): MetadataRoute.Robots {
const baseUrl = 'https://your-site.com';
return {
rules: [
{
userAgent: '*',
allow: '/',
disallow: ['/api/', '/admin/'],
// Do NOT disallow /_next/ — crawlers need render-critical CSS/JS
// Do NOT add bot-specific rules (Googlebot, Bingbot) unless overriding wildcard
},
],
sitemap: `${baseUrl}/sitemap.xml`,
host: baseUrl,
};
}
With cacheComponents: true in next.config.ts, use the "use cache" directive for SEO-critical server components:
// app/(home)/sections/hero-section.tsx
export async function HeroSection() {
"use cache";
cacheLife("minutes"); // Built-in profile: ~15 min
cacheTag("hero"); // For targeted invalidation via revalidateTag("hero")
const data = await fetchData();
return <div>{/* SEO-visible content */}</div>;
}
Key rules:
"use cache" must be the first statement in the function bodycookies()/headers() inside cache scopecacheLife() + cacheTag() instead of export const revalidate"use cache" if they fetch dynamic data| Strategy | Use When | SEO Impact |
|---|---|---|
| "use cache" | Server components with periodic data | Best - cached HTML, fast TTFB |
| SSG (Static) | Content rarely changes | Best - pre-rendered HTML |
| SSR | Dynamic content per request | Great - server-rendered |
| CSR | Dashboards, authenticated areas | Poor - avoid for SEO pages |
| Metric | Target | Impact |
|---|---|---|
| LCP (Largest Contentful Paint) | < 2.5s | Loading speed |
| INP (Interaction to Next Paint) | < 200ms | Interactivity |
| CLS (Cumulative Layout Shift) | < 0.1 | Visual stability |
alternates.canonical/_next/ in robots.txt - Crawlers need render-critical CSS/JS; never disallow /_next/export const metadata: Metadata = {
robots: {
index: false,
follow: false,
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
anthropics/claude-code
mblode/agent-skills
github/awesome-copilot
leonxlnx/taste-skill
sickn33/antigravity-awesome-skills
erichowens/some_claude_skills
Solid pick for teams standardizing on skills: nextjs-seo is focused, and the summary matches what you get after install.
I recommend nextjs-seo for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in nextjs-seo — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for nextjs-seo matched our evaluation — installs cleanly and behaves as described in the markdown.
Registry listing for nextjs-seo matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in nextjs-seo — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
nextjs-seo fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Keeps context tight: nextjs-seo is the kind of skill you can hand to a new teammate without a long onboarding doc.
nextjs-seo has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in nextjs-seo — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 33