A portfolio is a small site, so SEO comes down to a handful of decisions that are easy to get wrong and cheap to get right. This is the checklist I follow with the Next.js App Router, using this site as the example.
1. Pick one canonical domain and use it everywhere
Google treats every hostname as a separate site. If your app is reachable at yourname.vercel.app and yourname.com, you need to tell search engines which one is the real one, and every canonical tag, sitemap entry and social-card URL has to agree.
The simplest fix is one constant that everything imports:
// lib/site.ts
export const SITE_URL = (
process.env.NEXT_PUBLIC_SITE_URL || "https://bipanshu.in"
).replace(/\/+$/, "");Set metadataBase to new URL(SITE_URL) in the root layout so relative canonical and Open Graph URLs resolve to the right host. Then 301-redirect every other hostname, including *.vercel.app, to the primary domain.
A fallback that points at a placeholder domain is the classic mistake: if the environment variable is missing in production, every canonical tag silently points at the wrong site.
2. Give every page its own title, description and canonical
Export generateMetadata (or a static metadata object) from each route. Keep titles under about 60 characters, lead with the name or topic people search for, and write descriptions that read like a sentence, not a keyword list.
export const metadata: Metadata = {
title: "About",
description: "Who Bipanshu Kumar is, what he builds and where he studied.",
alternates: { canonical: "/about" },
};One catch: in Next.js a page-level openGraph object replaces the layout's instead of merging with it, so set the full Open Graph and Twitter objects on every page. A small helper function keeps this consistent.
3. Ship a sitemap and robots file from code
// app/sitemap.ts
import type { MetadataRoute } from "next";
export default function sitemap(): MetadataRoute.Sitemap {
return [
{ url: "https://bipanshu.in/", lastModified: "2026-09-20" },
{ url: "https://bipanshu.in/projects", lastModified: "2026-09-20" },
];
}Use real modification dates. new Date() makes every URL look edited on every build, and Google learns to ignore it. Reference the sitemap from app/robots.ts, then submit it in Search Console.
4. Add structured data that describes you
For a personal site, a JSON-LD @graph with a Person, a WebSite and a ProfilePage tells search engines who the site is about. Include sameAs links to your LinkedIn and GitHub, alternateName for every spelling of your name, worksFor and alumniOf. Add BreadcrumbList on inner pages and BlogPosting on articles. Validate everything with Google's Rich Results Test and the Schema Markup Validator.
Structured data does not unlock a special result for a Person, but it removes ambiguity, which is exactly what you want when other people share your name.
5. Treat images as a performance budget
- Resize originals before committing them. A 3 MB portrait does not need to be 3 MB.
- Use
next/imagewith a realisticsizesvalue so browsers download the smallest suitable file. - Mark only the first above-the-fold image as
priority, and lazy-load everything else. - Write descriptive file names and alt text. Image search reads them too.
Largest Contentful Paint is usually a hero image, so this is where most portfolio performance problems start.
6. Generate social cards from a route
A route handler that returns an ImageResponse gives every page its own 1200×630 preview without design work. Generate them at build time for a fixed list of pages, for example /og/project-miru, rather than accepting arbitrary text from the URL, so nobody can use your domain to render misleading images.
7. Verify, submit, then be patient
- Add the site to Google Search Console as a Domain property and verify it through DNS.
- Submit
/sitemap.xml. - Run URL Inspection on the homepage and click Request Indexing.
- Import the site into Bing Webmaster Tools from Search Console.
After that, links matter more than code. Your GitHub and LinkedIn profiles, and the projects you have built, should all link back to the site.
What doesn't matter
- The
keywordsmeta tag. Google ignores it. priorityandchangefreqin the sitemap. Also ignored.- Repeating your name in every paragraph.
None of this guarantees a ranking, but it removes the technical reasons not to have one.