Insight

A Next.js Portfolio SEO Checklist Developers Actually Use

Canonical URLs, metadata, sitemap, robots, Core Web Vitals, and structured data — a practical checklist for developer portfolios on Next.js App Router.

By Hanzala AhmedNovember 12, 20268 min read

A portfolio ranks when search engines can crawl clear pages, understand who you are, and see useful content beyond a single homepage. Next.js App Router makes this straightforward if you treat SEO as part of shipping — not a post-launch cleanup.

Metadata and canonicals

  • Unique title and description per important route
  • metadataBase + absolute canonicals
  • Open Graph tags that match visible page intent
  • No accidental noindex on public content pages

Crawl surfaces

Ship robots.txt that allows public pages and blocks admin. Keep an XML sitemap that lists homepage, about/contact/policies, insights, and case studies. Resubmit after major content additions in Search Console.

Structured data that matches the page

Person + WebSite JSON-LD on the portfolio root helps brand queries. Article markup on insights helps topical pages. ContactPage and AboutPage types are optional but clarify ownership for both users and crawlers.

Performance is part of SEO

Compress images, avoid layout shift in the hero, and keep third-party scripts gated. A beautiful portfolio that loads slowly on mobile still loses users — and ranking signals that follow engagement.

Checklist complete is not “done forever.” Add original writing, keep case studies accurate, and update when your stack or services change. SEO for a personal brand is maintenance, not a one-time plugin.

← All insights

Need delivery help on WordPress, Shopify, or a custom stack? Get in touch.

Next.js · SEO · Portfolio · Technical SEO

AboutServicesProjectsContactInsightsPrivacy PolicyCookie PolicyEditorial PolicyTerms of Use