
Gatsby to Next.js Migration Checklist
A practical Gatsby to Next.js migration checklist covering routes, data, rendering, plugins, images, redirects, preview, sitemaps, and SEO validation.
Articles
Next.js is an open‑source React framework created by Vercel. It is used to build fast, scalable websites and web applications, combining React with routing, data fetching, API routes, automatic code splitting, TypeScript support, server‑side rendering (SSR), and static site generation (SSG).
Below you will find a subset of articles from my blog specifically about Next.js as well as Next.js platform consulting. This is an area I have worked with for many years, and it has been a regular subject in my writing. There are fifty‑seven articles collected together for you below.

A practical Gatsby to Next.js migration checklist covering routes, data, rendering, plugins, images, redirects, preview, sitemaps, and SEO validation.

A practical Contentful to Sanity migration checklist for Next.js sites, covering schemas, references, preview, redirects, metadata, and SEO checks.

SEO best practices in Next.js, with a sharper focus on Core Web Vitals, stable layouts, lighter bundles, metadata, and real user measurement for search.

Debug stale Next.js App Router pages with cache tags, revalidation paths, CMS webhooks, preview freshness, dependency graphs, and simpler cache contracts.

Contentful to Sanity migration risks for Next.js sites, including models, references, rich text, preview, metadata, redirects, and launch checks.

Why CMS preview belongs in the migration plan for Next.js sites, covering draft state, auth, cookies, iframes, cache invalidation, and governance.

How to decide whether moving from Contentful to Sanity makes sense for a Next.js website, including workflow, modelling, preview, and migration risk.

Fix Contentful preview in Next.js by checking Draft Mode, preview URLs, iframe cookies, draft data boundaries, auth, performance, and editor trust.

A practical way to debug failing Next.js builds on Vercel, from first useful error lines and environment drift to route generation and memory pressure.

Diagnose traffic drops after a redesign, migration, or replatform by checking route parity, rendered HTML, redirects, canonicals, sitemaps, and schema.

How to migrate e‑commerce product and category pages to Next.js without losing SEO value, including URLs, filters, schema, canonicals, and redirects.

Decide whether Shopify to Next.js is worth it by weighing storefront control, SEO, performance, checkout, apps, content workflow, cost, and risk.

How to design multi‑tenant Next.js architecture across routing, domains, configuration, content, caching, previews, analytics, and team ownership.

Plan Content Security Policy in Next.js with static pages, nonces, third‑party scripts, headers, frames, previews, and incremental deployment safely.

A Pages Router to App Router migration checklist for Next.js teams, covering routing, data fetching, caching, metadata, server components, and rollout.

Why production data breaks Next.js sites, including CMS fields, slugs, images, relations, dates, rich text, generated routes, and validation gaps.

How to vet a senior Next.js developer for replatforming, recovery, SEO, performance, CMS, Vercel, and production debugging work.

How to debug NextAuth when it works locally but fails in production, covering callback URLs, cookies, secrets, middleware, providers, and Vercel.