Technical SEO for Next.js SaaS (checklist)
Metadata, sitemaps, canonical URLs, and JSON-LD: the boring work that actually moves organic traffic.
Framework choice does not replace fundamentals. Next.js gives you generateMetadata, route handlers, and static generation, but you still have to wire them deliberately.
Metadata on every public route
Each marketing and blog page needs a unique title and description. Use a title template on the root layout so child pages only set the delta. Set metadataBase once so relative OG URLs resolve correctly in production.
Sitemap and robots
Ship sitemap.ts and robots.ts in the app router. Include blog slugs when you publish. Disallow authenticated areas (/canvas/, /api/) so crawl budget stays on pages that convert.
Structured data where it helps
Blog posts benefit from BlogPosting JSON-LD. Site-wide FAQ can use FAQPage on a dedicated page when answers are visible in the DOM. Do not sprinkle schema you cannot see on the page.
Internal links are part of technical SEO
Link from docs to blog and back. Google uses graph structure to understand topical authority. One orphan post per quarter is fine; a whole orphan blog is not.
Ship, measure, iterate
Connect Search Console. After each release, check coverage and CTR on top queries. Fix titles before you chase new keywords.
For exports that keep UI on-brand, see export and use in code.