SEO for Developers: Rank Your Next.js Portfolio on Google in 30 Days
A concrete 30-day SEO sprint for developer portfolios built in Next.js. Exact steps to fix the metadata API, add JSON-LD structured data, generate a real sitemap, write content Google can rank, get indexed in Search Console, and earn the first few backlinks — without buying a single course. Tested on a real portfolio that now ranks for "Siddharth Puri" and several tech queries in India.
SEO for Developers: Rank Your Next.js Portfolio on Google in 30 Days
Most developers build a beautiful portfolio, deploy it, and wait for Google to notice. Google does not notice. Google needs to be told, then reminded, then given reasons. Here is the exact 30-day sprint that took my own Next.js portfolio from invisible to ranking for my name and several tech queries. If you have not chosen your stack yet, start from Next.js vs React — what to learn first in 2026 so your foundation is right before you start optimising for search.
Week 1 — the boring-but-mandatory foundation
- Set a clean canonical domain (www or non-www, pick one, redirect the other)
- Add a real metadata object in every route using the Next.js Metadata API — title, description, canonical, openGraph, twitter
- Create app/sitemap.ts and app/robots.ts — Next.js generates /sitemap.xml and /robots.txt automatically
- Add a manifest.webmanifest with icons + theme colour
- Compress images to WebP, use next/image everywhere
- Check Lighthouse SEO score → aim for 100, which is table stakes, not a trophy
Week 2 — structured data that Google actually reads
Google ranks entities, not pages. Tell Google who you are with JSON-LD.
- Add a Person schema in your root layout — name, alternateName, url, image, jobTitle, sameAs (LinkedIn, X, Instagram, GitHub)
- Add a WebSite schema with a SearchAction for your blog
- Add BlogPosting schema on every article — headline, datePublished, author, publisher, image, mainEntityOfPage
- Validate everything at search.google.com/test/rich-results — fix every warning
Week 3 — content Google can actually rank
Your /about page and five project pages will rank on your name. Everything else needs blog posts targeting real queries. Write 3–5 posts in week 3. Each post should:
- Target one primary keyword you looked up in a keyword tool (free: Google Suggest, Answer The Public)
- Have that keyword in the URL slug, H1, first paragraph, and one H2
- Be 1,200–2,500 words of actual content, not filler
- Include 2–3 internal links to your other pages
- Include a clear "who you are" line so your name starts co-occurring with the topic
Week 4 — indexing, monitoring, first backlinks
- Verify your site in Google Search Console (HTML meta tag method, use the Next.js verification metadata field)
- Submit sitemap.xml in Search Console
- Use "URL inspection" to request indexing on your top 10 URLs
- Set up Microsoft Clarity or Vercel Analytics — actual behaviour data
- Publish your best post on LinkedIn + X + Hacker News / IndieHackers / Reddit where appropriate — real backlinks start with real distribution
- Update LinkedIn/GitHub/X bios to link to your portfolio — your social profiles are easy domain-authority links
What most dev portfolios get wrong
- No text on the homepage — just a big hero with your name. Google needs words.
- Client-only rendering of project copy. If View Source does not show it, Google does not rank it.
- Generic "Home | My Portfolio" titles. Your title tag is the single highest-impact SEO element.
- No blog. The blog is what compounds after month two.
- Slow mobile performance. Core Web Vitals matter and next/image + App Router make this free.
The 60-90 day compounding curve
For the first 30 days, you will see almost nothing. Indexing is slow, freshness is low, the site is new. In month two, your name starts to rank and long-tail queries from your blog posts start picking up impressions in Search Console. Month three is when clicks start. This curve is boring but reliable. Do not bail in week 4.
SEO is the closest thing to a compound interest account in software. You make the deposits in the first month, and you get paid for years.
A Next.js portfolio with real metadata, real JSON-LD, real content and real distribution beats 95% of dev portfolios on search. Not because the developer is special, but because almost nobody does the boring 30 days. If the rest of your portfolio needs work too, my teardown on why most developer portfolios look the same has the five small decisions that actually matter once you start ranking.