Agent skill · marketing growth · laguagu
nextjs-seo
Next.js App Router SEO optimization and auditing. Use when implementing or fixing SEO in a Next.js app — metadata and generateMetadata, viewport/themeColor, Open Graph and og/twitter images (file conventions + ImageResponse), web app manifest, favicons/icons, sitemap.xml, robots.txt, canonical URLs, hreflang/i18n alternates, JSON-LD structured data and rich results, Core Web Vitals (LCP/INP/CLS), AI search/GEO and AI crawler rules (GPTBot, OAI-SearchBot), or diagnosing Google indexing problems (Search Console, "Discovered/Crawled - currently not indexed"). Also use to run an SEO audit checklist. Not for general Next.js feature work unrelated to SEO.
Why this skill is useful
Provides specific Next.js SEO patterns and configurations that the AI wouldn't reliably generate on its own.
What it needs
About 8k tokens when loaded. Last updated 2026-08-03. 58 stars on the source repository.
What this skill does
Next.js SEO Optimization Comprehensive SEO guide for Next.js App Router applications. Quick SEO Audit Run this checklist for any Next.js project: 1. Check robots.txt: curl https://your-site.com/robots.txt 2. Check sitemap: curl https://your-site.com/sitemap.xml 3. Check metadata: View page source, search for <title> and <meta name="description"> 4. Check JSON-LD: View page source, search for application/ld+json 5. Check Core Web Vitals: Use PageSpeed Insights (pagespeed.web.dev) and the Search Console CWV report for field data — Lighthouse is lab-only and can't measure INP Essential Files app/layout.tsx - Root Metadata app/sitemap.ts - Dynamic Sitemap lastModified must reflect the content's actual last change (CMS updatedAt, file mtime, git commit date) — Google uses lastmod only when it's consistently accurate, and new Date() on every build marks everything "just changed", which teaches Google to ignore it. Skip changeFrequency and priority: Google ignores both. app/robots.ts - Robots Configuration host was omitted intentionally — it's a non-standard directive Google ignores. Use canonical URLs / 301s to declare the preferred host instead. See references/sitemap-robots.md. app/manifest.ts - Web App Manifest Same MetadataRoute family as sitemap/robots, placed at the root of app/. Not an SEO requirement — a PWA-completeness nicety with no ranking effect; skip it unless the site is (or may become) a PWA. Full example in references/metadata-api.md. OG / Twitter Images Three ways to set social images — prefer the file conventions over hand-syncing URLs in the metadata object: 1. External URL in metadata (the openGraph.images / twitter.images examples above) — fine for externally hosted images. 2. Static file convention (recommended default): drop opengraph-image.(png jpg gif) and/or twitter-image. into a route segment (app/opengraph-image.png for the root, app/blog/opengraph-image.png for /blog). Next.js auto-emits og:image/twitter:image + :type/:width/:height. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills laguagu/nextjs-seo