Choosing a WordPress Theme for an Agency Site
Agencies rebrand their own site more often than they rebrand a client's. That makes portability, not the homepage animation, the thing to judge a theme on.
An agency site is judged on the work it shows, and agencies re-skin their own site more often than they re-skin a client's. Those two facts should decide the theme, and they almost never do.
Every theme marketed to agencies sells you a homepage: full-bleed hero, scroll-triggered showreel, diagonal thumbnail grid. That is the cheapest part of the site to rebuild and the first part you will throw away. The expensive part is the forty case studies underneath it.
The case study is the asset, not the layout
A case study is a record, not a page. To earn its place it wants defined fields — client, sector, year, services delivered, the problem, the intervention, a measurable outcome, a quote, an image set.
Once those are fields rather than free-form layout, the site can do things a design cannot: filter the work archive by service, pull related projects onto a service page automatically, keep twelve writers producing consistent pieces, and answer "show me everything we did in fintech" without a spreadsheet.
Themes sold to agencies almost always ship this as a portfolio or case-study post type registered inside the theme, with the fields in the theme's own metaboxes. That is the trap.
Theme-registered work dies at the rebrand
Deactivate the theme and the post type stops being registered. The rows are still in the database, but the archive returns a 404, every case study URL you have shared in a pitch stops resolving, and the fields become orphaned meta nothing renders.
For most sites that is a theoretical risk. For an agency it is a scheduled event — you will rebrand, and the entire point of a rebrand is a new theme.
| Where it lives | Survives a theme switch |
|---|---|
| Posts, pages, media, menus | Yes |
| Post type registered by a plugin | Yes |
| Post type registered by the theme | No — archives and single URLs stop resolving |
| Fields from a custom-fields plugin | Yes |
| Fields in the theme's metaboxes | No |
| Layout built from theme shortcodes | No — the shortcode prints as raw text |
The fix is unglamorous and takes an afternoon: register the work post type and its fields in a small site-specific plugin, or in a portfolio plugin that owns them, and let the theme supply templates only. Do that once and a rebrand becomes a redesign rather than a data migration. If you are switching now, how to change a WordPress theme covers the sequence.
What the site carries besides the work
- Service pages that stand alone. Each one needs to rank and convert on its own; a single "what we do" page with six anchors does neither.
- People. Team pages date fast and agencies churn. Make them editable by someone who is not a developer, or they will be two years stale.
- Careers. Recruitment traffic is often the second-largest segment on an agency site and almost no theme demo accounts for it.
- Writing. Not a blog for SEO's sake — the pieces that demonstrate you think clearly are frequently the ones that win the pitch.
- A brief form that accepts attachments. Prospects send RFPs and decks. Size limits and spam handling matter more than field styling; contact form plugins is the relevant decision, not the theme.
Free is a defensible choice for a design studio
Searches for a free WordPress theme for agency sites turn up the same one-page creative demos everyone else is using, which is its own argument. There is also a peculiar logic to a design agency buying somebody else's design. A free block theme plus your own patterns, type scale and CSS gets you a site that looks like you rather than like a template — and free block themes are now genuinely capable as a base layer.
Buy a theme when you are purchasing maintenance, support and someone else's ongoing compatibility work. That is a real product and premium themes can be worth it. Do not buy one because the demo looks like the agency you want to become; you will spend longer fighting its opinions than you would have spent building your own.
If you want a filterable work archive as the primary structure, the criteria in portfolio themes apply directly.
The licence term studios forget
Whatever you pick for yourself tends to become your default for client builds. Before that happens, check three things: whether the licence covers unlimited sites or bills per install, what happens to a client's updates after handover, and whether the site keeps working — not just updating — when nobody renews. A theme that degrades functionality on licence expiry is a liability you cannot hand to a client in good conscience.
Deciding
Pick the theme on how cleanly you can leave it. Move the case studies out of theme ownership before you install anything. Then choose whichever base — free or paid — gets your own design onto the page with the least argument, because that part you are going to redo in three years anyway. For the version of this problem where the site is primarily a lead-generation channel, see digital marketing agency sites.
Frequently asked
- A custom post type, as soon as you have more than about six of them. Pages give you no archive, no filtering by service or sector, and no consistent structure across pieces written by different people over several years.
- Often yes, because the design work is the thing you are selling and you are going to do it yourself anyway. Pay for a theme when you are buying maintenance and support rather than a look you intend to override.
- Anything the old theme registered or stored: portfolio post types declared in the theme, fields in theme metaboxes, layouts built from theme shortcodes, and everything set in theme options. Posts, pages, media and menus come through untouched.