Skip to content

Fix Next.js SEO issues

Ship-ready Next.js, App Router or Pages

  • Senior engineers · IST + EST overlap
  • NDA on day 1
  • 24-hour reply

Tell us what you need fixed

Reply in 24 hours · NDA on day 1 · No spam.

Fix Next.js SEO issues — done properly, by senior engineers

This page covers how we fix Next.js SEO issues where the tab title looks right but Search Console still reports duplicate titles, canonical conflicts or the wrong social preview image. Most of these bugs come from how the App Router merges metadata. Objects exported by a layout and a page are merged shallowly, so a page that sets its own openGraph block silently drops the images its parent layout defined. A title.template applies only to child segments, an alternates.canonical set in a layout is inherited by every route beneath it, and a wrong metadataBase resolves relative URLs against a preview host. On older Pages Router code, duplicate next/head tags without a key produce the same symptoms. Krapton’s engineers crawl the production build from its sitemap, extract the rendered head for every URL and trace each defect back to the layout or generateMetadata function that produced it. Fixes go into typed helpers that build title, description, canonical and Open Graph fields per route type. A CI check then walks the generated sitemap and fails the build on duplicate titles, missing canonicals or OG image URLs that do not return 200. You receive the audit, the PR and a metadata conventions guide.

What you're seeing

Meta tags render but Search Console reports duplicate titles, missing canonicals, or wrong OG images.

Our approach

We audit the `metadata` API across every route, fix templating bugs, and add a sitemap-level lint to keep meta data correct as the app grows.

Symptoms teams come to us with

  • Search Console’s page indexing report lists “Duplicate without user-selected canonical” for distinct product or blog URLs.
  • Hundreds of pages share the root layout’s title because their route files never export metadata.
  • LinkedIn, Slack or X previews show the homepage image, or no image at all, for article URLs.
  • View-source shows two description or canonical tags, or a canonical pointing to a preview domain.
  • Paginated, filtered or locale variants of a page carry identical titles and descriptions in crawl reports.

What we check first

  1. A page-level openGraph object replaces the layout’s openGraph entirely, dropping images and type defined above it.
  2. alternates.canonical is set once in the root layout, so every child route canonicalizes to that URL.
  3. generateMetadata fetches data that fails or times out, and the route falls back to default metadata.
  4. metadataBase reads an environment variable that is wrong or missing in production, breaking absolute URLs.
  5. Dynamic segments and query parameters are ignored when titles are built, so variants render identical text.

Concrete deliverables, no fluff

Every engagement ends with measurable, documented outcomes — no black-box agency reports.

  • Root cause analysis with reproduction
  • Targeted fix with no scope creep
  • Verification on staging + production parity check
  • Runbook for future incidents

What changes after we ship

  • Distinct metadata on every route

    Titles, descriptions and canonicals are generated from each route’s own data, and the audit confirms no two indexable URLs share a title or point their canonical elsewhere by mistake.

  • Correct previews on social platforms

    Open Graph and Twitter card fields resolve to absolute production URLs, with per-route images built by opengraph-image files or ImageResponse where a static image does not fit.

  • A build that rejects bad metadata

    The CI check reads the generated sitemap, renders each URL’s head and fails the pipeline on duplicate titles, missing tags or Open Graph images that return errors.

  • Indexing statuses explained route by route

    Duplicate and alternate-canonical statuses in Search Console’s page indexing report are mapped to the code that caused them, so your team knows which fixes to validate.

From brief to shipped fix

A transparent, low-risk process — a senior engineer reads your brief personally, and nothing starts until you approve a written plan and price.

  1. 01Day 0–1

    Diagnose

    A senior engineer reviews your brief, reproduces the issue, and pinpoints the real root cause — not the symptom — before any code is touched.

  2. 02Within 24h

    Scoped plan & quote

    You get a written plan to fix Next.js SEO Issues, a firm timeline, and a fixed quote. Nothing starts until you approve it — no surprise invoices.

  3. 031–3 weeks

    Ship the fix

    We implement on a branch and open a pull request you review, working to your code-review standards on your repo — never a black box.

  4. 04On delivery

    Verify & hand off

    We verify on staging and production, share before/after evidence where it applies, and leave you a short hand-off note so the fix sticks.

Situations we handle

  • Large blog on the App Router

    Every post shows the root layout’s title because the dynamic post route exports no metadata. A shared generateMetadata helper reads the post record and returns a unique title, description, canonical and article image.

  • Multilingual site with hreflang

    Locale routes share one canonical and omit alternates.languages, so Google picks its own preferred version. Each locale gets a self-referencing canonical and a complete hreflang set generated from the same routing config.

  • Faceted ecommerce category pages

    Filter and sort parameters create thousands of URLs carrying the category’s title. Canonicals point filtered views to the clean category, noindex covers thin combinations, and the sitemap lists only indexable URLs.

Why teams hand this task to Krapton

  • Senior engineers only

    Your brief is read and handled by a senior engineer — no junior hand-off, no sales-rep filter in between.

  • Root cause, not a patch

    We reproduce and fix the underlying cause, then add a guard so the same class of issue does not quietly return.

  • Your repo, your standards

    Every change lands as a pull request you review, on your repository, following your existing review process.

  • NDA on day one

    Confidentiality and IP are covered before we look at a single line of code. All work stays in your accounts.

  • Fixed quote up front

    You approve a written plan and price before work starts. If scope changes, we re-quote in writing — no surprise invoices.

  • Proof, where it applies

    Performance, SEO and reliability work ships with before/after evidence so the result is measurable, not anecdotal.

Three ways to engage

No retainer required. Pick the model that matches the work — pricing for this task starts from $500, with a fixed quote before anything starts.

  • Per task

    Most popular

    One clearly-scoped fix at a fixed price. Best when you know exactly what is broken and want it handled end to end.

    • Fixed quote up front
    • One PR, reviewed by you
    • No retainer required
  • Hourly

    Pay only for the hours worked. Best for diagnostics, audits, or exploratory work where the scope is still emerging.

    • Weekly timesheets
    • Pay for what you use
    • No minimum commitment
  • Per sprint

    A focused 1–2 week sprint when the work is bigger than one fix but smaller than a full project.

    • 1–2 week blocks
    • Clear sprint goal
    • Scale up or stop anytime

Industry-standard stack, no proprietary lock-in

  • Next.js 14
  • RSC
  • Vercel
  • Edge runtime

Fix Next.js SEO issues — your questions, answered

How much does it cost to fix Next.js SEO Issues?

Pricing starts from $500 and depends on the scope we find during the diagnostic. You get a fixed, written quote before any work begins — most engagements like this run 1–3 weeks.

How long does it take to fix Next.js SEO Issues?

Typically 1–3 weeks for a focused engagement. After a short diagnostic we commit to a firm timeline so you know exactly what to expect.

What do you check when you fix Next.js SEO issues on a large site?

We check the rendered output, not the source files. A crawl of the production build records title, description, canonical, robots, hreflang and Open Graph tags for every URL in the sitemap plus discovered links. Each defect is grouped by the layout or helper that produced it, so one fix in a shared layout can resolve many URLs, and nothing is patched page by page without a pattern.

Should we generate Open Graph images dynamically?

For content with many pages, usually yes. The opengraph-image file convention and ImageResponse from next/og render images from route data at build or request time, so every article gets its own preview. Static images remain simpler for a handful of marketing pages. Either way, the image URL must be absolute, publicly reachable and sized around 1200 by 630 pixels for consistent previews.

Does the sitemap need to change as well?

Usually, yes. The app/sitemap.ts convention should list only canonical, indexable URLs with accurate lastModified values, and large sites can split output with generateSitemaps. Listing redirected, noindexed or parameterized URLs sends mixed signals that undo canonical fixes. We build the sitemap from the same route data that drives metadata, so both stay consistent as content is added.

Let's get this off your plate

Send a 60-second brief on Fix Next.js SEO Issues and a senior engineer replies within 24 hours with a plan and a fixed quote. NDA on day one, no retainer required.