A WordPress developer portfolio that shows the build
A client cannot tell a bought theme from a custom build by looking at a screenshot. A WordPress portfolio has to say what you actually did — and keep pointing at sites that still work.
Say what was built, not just what it looks like
Two WordPress sites can look identical and represent a day's work and a quarter's work. Name the parts that took skill, because the client will not see them.
- Theme: bought, child-themed, or built from scratch.
- Page builder, if any — Elementor, Bricks, Gutenberg blocks — and whether you built custom blocks.
- WooCommerce: product types, custom checkout steps, integrations with payment or stock systems.
- The awkward part: a migration, a membership system, a booking flow, a performance rescue.
Why WordPress portfolios decay fastest
WordPress sites sit on hosting the client pays for, with plugins someone has to update. When a client stops paying the host, or an update breaks the theme, the site you are proud of becomes a hosting error or a suspension page.
Shared hosts are also quick to put up bot challenges. A portfolio checker that is not careful will happily store a screenshot of "403 Forbidden" and show it as your work.
Staging links do not belong in a portfolio
A staging or preview URL feels like proof, but it is usually the first thing deleted after launch. Link the live domain, and if a project was never launched, say so rather than linking a preview that will vanish.
Bowerdeck detects WordPress on its own
Paste a WordPress site and Bowerdeck records it as WordPress, notes WooCommerce or the page builder where the page gives them away, and photographs it. The daily check refuses to store an error page as your screenshot, and a site that goes down leaves your public profile until it recovers.