Next.js SEO Basics for a Developer Portfolio

A developer portfolio needs more than a good-looking homepage. It should also be easy for Google and visitors to understand.

In Next.js, I focus on metadata first: a clear title, useful description, canonical URL, Open Graph image, Twitter card, and robots settings. These details help search engines and social platforms understand the page.

Sitemap and robots files are also important. The sitemap should include public pages like home, about, projects, blog, and published articles. Admin routes and private API routes should not be indexed.

Structured data is another helpful layer. A Person schema can connect the portfolio with social profiles like GitHub, LinkedIn, and Facebook. It can also highlight skills, location, and current role.

The strongest SEO improvement is still useful content. Project detail pages, case studies, and technical blog posts give search engines more specific pages to rank and give visitors more reasons to trust the work.