Technical SEO with Next.js: what to verify before go-live

When we say technical SEO during a website development project, we do not mean keyword stuffing or “guaranteed #1”. We mean concrete signals search engines (and many AI crawlers) can parse without guessing.

Next.js helps because it gives you clean routing, server rendering where it matters, and the Metadata API — but only if you use them deliberately.

1. Titles, descriptions, and canonicals

• Every important page needs a unique title and meta description that reflect the page, not generic slogans.
• A canonical URL so duplicate paths (tracking params, trailing slash variants) do not split signals.
• If you ship multiple languages, you need consistent hreflang / language alternates so the right locale clusters correctly.

That is the minimum viable SEO layer for serious web development.

2. Speed and Core Web Vitals

Google uses experience metrics such as LCP, INP, and CLS as part of the picture — not the only ranking factor, but a strong proxy for “is this page pleasant to use?”.

Typical React / Next.js pitfalls:

• oversized client bundles delaying first interaction,
• images without sizing or lazy loading discipline,
• third-party widgets (chat, tags) tanking INP.

The fix is often architectural: what stays server-rendered, what loads lazily, what gets removed entirely.

3. Structured data (JSON-LD)

schema.org via JSON-LD helps engines (and many retrieval systems) understand who you are, what you offer, and which page is authoritative for contact.

Useful patterns for company sites and landings:

• Organization + WebSite,
• FAQPage when the visible FAQ matches the markup,
• Article for blog posts.

Critical rule: JSON-LD must match visible content — otherwise it is noise at best and a policy risk at worst.

4. Sitemap and robots.txt

• A sitemap.xml listing URLs you want indexed, with sensible lastmod where it matters.
• A robots.txt that does not accidentally disallow important sections.

In Next.js these are often sitemap.ts / robots.ts routes — easy to ship once, easy to forget on iteration #12.

5. Headings and real answers

Hierarchy (H1–H3), internal links to relevant services, and writing that answers real buyer questions beats repeating “website development” in every paragraph.

Keywords belong inside natural sentences — not in density games.

Takeaway

Technical SEO is part of delivery quality for a website build: clean URLs, fast UI, honest metadata, accurate schema. After that, competitive rankings still need authority, backlinks, and ongoing content — but without the foundation, everything else fights uphill.