Technical SEO with Next.js: Crawlability, Metadata, and Structured Data
SEO is not only marketing copy. Routing, metadata APIs, performance, and structured data determine whether search engines understand and trust your product pages.
Ali Mortazavi
Founder, Paradise Code
Crawlable Architecture
Search engines need stable URLs, meaningful slugs, and HTML that renders critical content without excessive JavaScript dependency. App Router with Server Components helps because primary content ships in the initial HTML.
Avoid orphan pages and duplicate routes with and without trailing slashes. Pick one canonical pattern and redirect the other. Use middleware for locale or www consolidation carefully so you do not create redirect chains.
XML sitemaps and robots.txt should be generated from the same source of truth as the site — CMS, database, or static route list — so new content is discoverable automatically.
Structured Data
JSON-LD for Article, Product, Organization, and FAQ where accurate. Rich results require honest markup; misleading schema can trigger penalties.
Generate structured data from the same models that power the page. Drift between visible price and schema price damages trust with users and crawlers.
Test with Google Rich Results Test after template changes. Regressions often come from client-only rendering of schema scripts.
Performance as an SEO Factor
Core Web Vitals influence ranking indirectly through user engagement signals. Fast LCP and low CLS help; slow mobile experiences increase bounce.
Image optimization, font loading, and third-party script discipline matter. Defer non-essential analytics and chat widgets below critical content.
INP improvements on interactive pages — filters, add to cart — keep users engaged. SEO and UX optimization overlap on real products.
International and RTL Considerations
Set lang and dir correctly on html. hreflang links connect language variants. Do not rely on automatic translation alone for competitive keywords in local markets.
Persian and RTL sites need the same technical rigor as English LTR: canonicals, structured data in the correct language, and mobile-friendly layouts.
URL strategy for locales — subpath versus subdomain — should be decided early and documented for content and engineering teams.
Operational SEO Checklist
Monitor Search Console for coverage errors, crawl spikes, and manual actions. Fix 404s on high-traffic legacy URLs with 301 redirects.
Staging environments should block indexing. Password protection or noindex headers prevent duplicate indexation of preview URLs.
Technical SEO with Next.js is ongoing hygiene: correct metadata, honest structured data, fast pages, and clean URLs. Paradise Code bakes these into launch checklists for client products that depend on organic discovery.
Insights
Need these ideas implemented in your product?
Paradise Code supports you from consult to full delivery.