How I structure a Next.js portfolio that passes real client checks

Why portfolios fail client checks

Clients rarely hire from a hero line alone. They scan for proof: what you shipped, what broke, what you would do differently, and how to reach you. A portfolio that is only animations and buzzwords fails that scan.

I keep this site focused on four jobs: show shipped work, explain how it was built, offer useful products, and make contact obvious.

When I review other developer sites for friends, the common failure is the same: beautiful motion, empty case studies, and a contact form that leads nowhere useful.

The page set that matters

1. Home - one clear offer, selected projects, and a path to contact.
2. Projects - case studies with problem, constraints, stack, and screenshots.
3. Products - paid packs with includes, price, and checkout.
4. Blog - fewer posts that teach something I actually use (deployments, scoping, tooling).
5. Privacy / Terms - required trust pages if you sell or run ads.

Thin affiliate-style posts and empty product pages hurt trust. I would rather publish one solid deployment guide than ten generic side-hustle articles.

Case study template I reuse

Every project page should answer:

• Who needed this and what was painful?
• What constraints existed (time, stack, privacy)?
• What did we ship in the first useful version?
• What tradeoffs did we accept?
• Where can someone see a sanitized UI?

If a page cannot answer those, it is not ready. I would rather hide a project than publish a logo row with no story.

I also write one failure note when I can: the wrong auth choice, the migration that burned a weekend, the feature we cut. Buyers trust that more than a perfect timeline.

Technical choices on this site

• Next.js App Router for routes, metadata, and server components.
• Vercel for previews and production.
• JSON content for products and many blog posts so edits are reviewable in git.
• Strict CSP with an allowlist so analytics and AdSense can load without opening the whole web.

I treat the portfolio like a product. Deployments are boring on purpose. Metadata, sitemap, and robots stay intentional. Broken Open Graph images make a first impression you do not get back.

Content quality over posting cadence

A daily blog that reads like spam will sink AdSense reviews and client trust at the same time. I moved low-value auto posts out of the public blog and kept practitioner pieces: deployment, scoping, portfolio craft.

The bar I use before publishing:

• Would I send this to a client without embarrassment?
• Does it include a concrete constraint or failure?
• Can someone act on it this week?

If the answer is no, it stays draft.

What I avoid

• Claiming earnings I did not measure.
• Publishing auto-generated posts that could belong to any site.
• Hiding contact behind a maze of CTAs.
• Shipping product pages with empty problem/solution sections.
• Stock screenshots that do not match the live product.

Navigation and trust details that matter

Small things signal seriousness:

• Footer links to Privacy and Terms
• Working contact email and form on mobile
• Consistent project naming between home and case studies
• Honest "what this is not" lines on product pages

Clients who buy digital products or book calls notice missing legal pages. Ad networks notice them too.

Checklist before you call it done

• Three or more project case studies with real constraints
• Contact email and form path work on mobile
• Privacy and Terms linked in the footer
• Products have problem, solution, and includes filled in
• Blog posts teach a specific workflow you use
• Sitemap lists only public, complete pages

FAQ

Do I need a blog for clients to hire me? Not always. Case studies matter more. A blog helps when it shows how you think under constraints.

How many posts before AdSense? Google does not publish a magic number. They reject thin or low-value sites. A few solid posts beat a pile of filler.

Should every project be public? No. NDAs exist. Publish sanitized versions or skip them. Empty "confidential" cards waste space.

Bottom line

A portfolio that passes client checks is boring in the right places: clear offer, real constraints, working contact, and content you would stand behind. Polish helps. Substance decides.

If you want help shipping a client MVP with a clear scope first, use the contact page and tell me what you are building.