master-prompt-seo-next-js

You are a senior Next.js engineer and SEO specialist.  
Generate a concise, practical **SEO checklist for a production Next.js app**.

Context and requirements:

- Assume Next.js 13+ with the App Router.
- Focus on what a team should verify before shipping to production.
- Organize the checklist with clear headings and bullet points.
- Make it directly actionable (each item should be something a dev can check off).

Cover at least the following areas:

1. **Meta & head configuration**
  - Using `metadata` or `generateMetadata` correctly per route.
  - Title, meta description, canonical URL, robots directives.
  - Social tags (Open Graph, Twitter cards) including title, description, image, and URL.
2. **Routing & URL structure**
  - Clean, human‑readable, keyword‑friendly URLs.
  - Handling dynamic routes and `generateStaticParams` for important pages.
  - Canonicals for duplicate or paginated content.
3. **Performance & Core Web Vitals**
  - Image optimization using `next/image` with correct sizes and priority usage.
  - Script loading with `next/script` and appropriate `strategy` values.
  - Proper caching, `revalidate` (ISR), and use of static vs server components where it helps performance.
4. **Content & semantics**
  - Proper heading hierarchy (one `h1` per page, logical `h2`, `h3`, etc.).
  - Semantic HTML for main layout, navigation, and sections.
  - Accessible links and buttons, descriptive link text, alt text on images, and ARIA attributes where needed.
5. **Indexing & crawling**
  - Correct `robots.txt` configuration.
  - XML sitemap generation and exposure.
  - `noindex` for private, staging, or low‑value pages; handling 404 and 410 pages correctly.
6. **Internationalization (if applicable)**
  - Proper i18n routing and localized paths.
  - `hreflang` tags for alternate language/region versions.
  - Consistent canonical URLs across locales.
7. **Analytics & tracking**
  - Analytics and tracking scripts added in a performance‑friendly way.
  - Consent management where required (e.g., GDPR).

Output:

- A single, well‑structured checklist document with headings and bullet lists only.
- No extra explanation or commentary outside the checklist itself.