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.
Missing Open Graph tags
Shared links on LinkedIn/Twitter show blank or generic previews
No alt text on project images
Screen readers can't describe your work; hurts accessibility and image SEO
Broken heading hierarchy
Jumping from H1 to H4 confuses search engines and screen readers
No Person schema markup
Google can't associate your site with your professional identity
Poor contrast and small tap targets
Fails accessibility checks; harder to read on mobile
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
- 1Add Open Graph and Twitter Card meta tags with a compelling preview image
- 2Write descriptive alt text for every project screenshot and image
- 3Fix heading hierarchy: one H1 per page, then H2 → H3 in order
- 4Add Person schema with your name, job title, skills, and social links
- 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.
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.
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.
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.
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.
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
Free Open Graph Checker
See how your page looks when shared on social media
Free Twitter Card Checker
See how your page looks when shared on X
Free Image Alt Text Checker
Find images that are invisible to search engines and screen readers
Free Heading Tag Analyzer
See if your heading structure helps or hurts SEO
Free Accessibility Check
Make your site usable for more people
Free Schema Markup Audit
Qualify for extra details, such as star ratings, in search results
Frequently asked questions
Why should I audit my portfolio site?
What are Open Graph tags and why do they matter for my portfolio?
What is Person schema and should I add it?
My portfolio is a static site (Astro, Next.js, Hugo). does the audit work?
How important is accessibility for a dev portfolio?
I have a GitHub profile README. is a portfolio site still worth it?
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