Technical SEO Checklist for a Next.js Portfolio

A portfolio should not use the same title and description everywhere. The homepage can target your main positioning, while project pages target the type of product and technology used. About, Skills, Contact, and Blog pages should each answer a different search intent.

Keep titles readable and specific. A phrase such as Full-Stack Developer in Morocco is more useful than a long list of technologies with no clear service or location.

Generate a sitemap containing the homepage, important service pages, project case studies, and published articles. Add robots.txt with a public crawl rule and make sure canonical URLs point to the preferred HTTPS domain.

Structured data helps search engines understand the entities behind a website. A developer portfolio can describe the person, website, breadcrumbs, and individual creative work without adding visible clutter.

Screenshots and technology badges are not enough. Explain the problem, the solution, your role, important technical decisions, and the outcome. This creates useful content for potential clients and gives search engines more context about your work.

Avoid inventing metrics. If a result cannot be measured publicly, describe the operational improvement honestly instead of adding a number that cannot be verified.

Ranking is only useful when visitors understand what to do next. Add a clear call to action, a short description of the projects you accept, and an easy contact path. A contact form is often more reliable than asking visitors to configure a mail application.

Finally, measure performance and indexing with PageSpeed Insights and Google Search Console. Technical SEO creates the foundation; useful content and credible mentions create momentum.

Start with a page map: homepage for positioning, services for commercial intent, projects for proof, articles for questions, and contact for conversion. Each page should have one clear job and links that move a visitor to the next useful step.

Then review the rendered HTML, not only the React source. Check the title, description, canonical, language, headings, image alt text, structured data, internal links, and whether important content is present without waiting for client-side interaction.

Use Search Console to track impressions, queries, average position, and clicks for each page. A new article may need time before it earns impressions, so avoid changing the URL or rewriting it after only a few days of data.

Look for pages with impressions but weak click-through rate, pages ranking on page two, and queries that reveal a better service or article angle. Improve the page that already has evidence instead of publishing many nearly identical pages.