Skip to content

Next.js SEO from someone whose own site runs on Next.js

This website runs on Next.js with a custom CMS, so I deal with Next.js SEO every day: metadata, sitemaps, redirects, rendering, image optimisation and the hosting limits that come with them. I bring that practical experience to your project.

Sadekur Rahman, Next.js SEO consultant

What running my own Next.js site taught me

When I moved my site from WordPress to a custom Next.js build, every SEO detail WordPress plugins used to handle had to be built deliberately: metadata per page, canonical URLs, hundreds of 301 redirects from the old URLs, dynamic sitemaps, structured data and image handling.

Next.js gives you full control, which means nothing is automatic.

I review how your app uses the Metadata API, server and static rendering, sitemaps, redirects, structured data and next/image, and check Core Web Vitals and crawlability with real tools, not just Lighthouse in a browser.

What my Next.js SEO work covers

Specific to how Next.js builds and serves pages, not a generic checklist.

  • Metadata API

    Titles, descriptions, canonicals and Open Graph generated per route.

  • Rendering strategy

    SSR, SSG or ISR chosen per page type so crawlers get full HTML.

  • Sitemaps & robots

    Dynamic sitemap and robots files generated from your data.

  • Redirects at scale

    Migration redirects handled in config or middleware without chains.

  • Structured data

    JSON-LD components for each page type, matched to visible content.

  • Core Web Vitals & images

    next/image, fonts and scripts tuned for LCP and INP, with an eye on hosting limits.

What I find on most Next.js sites

Each of these quietly costs traffic. All of them are fixable.

  • Pages rendered only on the client
  • Same metadata on every route
  • Canonicals missing or wrong
  • Redirect chains after migration
  • Image optimisation hitting host limits
  • Large JavaScript bundles hurting INP

How a Next.js SEO project runs

You always know what I'm checking and what changes next.

  1. 01

    Next.js audit

    Crawl, Search Console and a manual check of your Next.js settings, templates and add-ons.

  2. 02

    Prioritised plan

    Every issue scored by impact and effort, so the order of work is obvious.

  3. 03

    Fixes

    Changes made in Next.js directly or with your developer, tested before and after.

  4. 04

    Measure

    Indexing, rankings and leads compared with the starting point every month.

Next.js SEO questions

What Next.js site owners ask me most.

  • Yes. With server or static rendering, the Metadata API and proper sitemaps, Next.js sites can be fast and fully crawlable. Problems come from client-only rendering and missing configuration.
Sadekur RahmanNext.js SEO Consultant

Send me your Next.js site and I'll tell you what's holding it back

Most Next.js SEO problems come from a few settings and template choices. I'll check yours myself and give you a straight answer.

Based in Dhaka · Working with Next.js sites worldwide