Skip to main content

Your portfolio site is invisible to the people who matter

Recruiters and potential clients Google you. If your portfolio has no share preview, hard-to-use pages and no search labels, they may see a blank preview and move on. Our free audit shows what to fix.

Common problems on developer portfolio websites

Your own report shows which of these apply to your site.

critical

Missing Open Graph tags

Shared links on LinkedIn/Twitter show blank or generic previews

SEO
major

No alt text on project images

Screen readers can't describe your work; hurts accessibility and image SEO

Accessibility
moderate

Broken heading hierarchy

Jumping from H1 to H4 confuses search engines and screen readers

SEO
moderate

No Person schema markup

Google can't associate your site with your professional identity

Technical
major

Poor contrast and small tap targets

Fails accessibility checks; harder to read on mobile

Accessibility

Why a strong website matters for developers

Recruiters and clients often search for your name before they get in touch.

A clear preview card makes your link more likely to be clicked when shared.

A fast, simple portfolio shows your skills at a glance.

Top fixes for developer portfolio websites

  1. 1Add Open Graph and Twitter Card meta tags with a compelling preview image
  2. 2Write descriptive alt text for every project screenshot and image
  3. 3Fix heading hierarchy: one H1 per page, then H2 → H3 in order
  4. 4Add Person schema with your name, job title, skills, and social links
  5. 5Ensure color contrast meets WCAG AA and tap targets are at least 44x44px

Common mistakes developers make on their websites

These are easy to miss and usually easy to fix.

1

No OG image or using a generic avatar

Your portfolio gets shared on LinkedIn, Twitter, and Slack constantly. Without a custom OG image, the preview is blank or shows a tiny favicon. Create a 1200x630px image with your name, title, and a visual that represents your work. It's the highest-ROI 10 minutes you'll spend on your portfolio.

2

Treating accessibility as optional

Developers often skip alt text, ignore color contrast, and use div-based navigation. If you're applying for frontend roles, your portfolio failing a11y checks is a red flag. Run our accessibility audit and fix the basics: alt text, heading hierarchy, keyboard navigation, and color contrast.

3

Project pages with no context

Linking to GitHub repos with no explanation forces visitors to read your code to understand what you built. Each project should have: what you built, why, what tech you used, what challenges you solved, and (ideally) a live demo link or screenshot.

4

Missing or duplicate meta titles

Many portfolio sites use the same title ("John Doe") on every page. Google needs unique titles to understand and rank each page. Your projects page, about page, and blog should each have descriptive, unique title tags.

5

No sitemap or robots.txt

If Google can't discover your pages, they won't rank. Many static site generators don't include a sitemap by default. Adding a sitemap.xml and robots.txt takes minutes and ensures all your project pages are indexed.

What is Person schema for developer portfolios?

Person schema is structured data that tells search engines about you as a professional. For developers, the most useful fields include name, jobTitle, worksFor (current employer or "Freelance"), knowsAbout (your tech stack and skills), sameAs (links to GitHub, LinkedIn, Twitter, and other profiles), and url (your portfolio). When Google understands this data, it can connect your portfolio to your other online presences and potentially show a knowledge panel when someone searches your name. This is especially valuable for freelancers and consultants who want to establish professional authority in search results.

Free tools for developers

Frequently asked questions

Why should I audit my portfolio site?
Recruiters, hiring managers, and potential clients Google you. Your portfolio is often their first impression. If it loads slow, shows blank previews when shared, or fails accessibility basics, you're losing opportunities before anyone sees your work.
What are Open Graph tags and why do they matter for my portfolio?
Open Graph tags control how your site looks when someone shares a link on LinkedIn, Twitter, or Slack. Without them, your link shows a generic browser title and no image. With proper OG tags, it shows a professional preview with your name, role, and a preview image of your work.
What is Person schema and should I add it?
Person schema is structured data that tells Google who you are professionally. It can include your name, job title, employer, skills, education, and links to your GitHub, LinkedIn, and social profiles. Adding it helps Google connect your portfolio to your professional identity and may display a knowledge panel for your name.
My portfolio is a static site (Astro, Next.js, Hugo). does the audit work?
Yes. We audit any publicly accessible URL regardless of framework. Static site generators are great for performance, but developers often skip meta tags, accessibility, and structured data when building their own sites.
How important is accessibility for a dev portfolio?
Very. If you're applying to any company that cares about accessibility (and most do), your own portfolio failing basic a11y checks sends the wrong message. It's also just the right thing to do. and takes minimal effort to fix.
I have a GitHub profile README. is a portfolio site still worth it?
A GitHub README is great for developers reviewing your code, but recruiters and non-technical clients want a polished website. A portfolio site with proper SEO lets you control your narrative, showcase case studies with context, and rank in Google when someone searches your name.

Related resources

Ready to check your developer portfolio website?

Get your full audit in under a minute: a score out of 100, every problem with the evidence, and plain-English fix steps. Free, no login.

Run a free audit