How do you choose a WordPress theme?
Choose a WordPress theme by testing its demo and its listing before you install it, not by its screenshots. A good theme is kept up to date, stays fast on a phone, lets you change the things you change often without code, and does not lock your content into itself.
Design comes last on that list for a reason. Almost any well-built theme can be made to look right, while a badly built one keeps costing you after the novelty of its design has worn off.
- Maintained: updated recently, tested with the current version of WordPress, with a changelog you can read
- Fast and responsive: the demo loads quickly on a phone and the layout holds with your own content in it
- Not a trap: forms, shortcodes and custom content types come from plugins, so switching theme later does not break the site
Why the theme matters more than it looks
A WordPress theme controls how every page is laid out and styled. Swapping one later is possible, but on a site that has grown around its theme it usually means rebuilding pages, so the choice tends to last for years.
The original version of this article listed nine questions to ask about a theme. They still hold, but the wording had aged badly and some of the advice, such as judging a theme by a single speed score, no longer helps. This version keeps the questions, adds the one that causes the most expensive surprises, and turns them into checks you can run in an afternoon.
It assumes you have already settled on WordPress and a ready-made theme. If you are still deciding between that and a bespoke design, custom website design against a template compares the two first.
Ten checks before you buy
Run these against the theme's listing page and its live demo. None of them needs a developer, and most take a few minutes each.
| Check | How to test it | Warning sign |
|---|---|---|
| Recent updates | Read the "last updated" date and the changelog on the listing | No update in the last several months, or a changelog that lists nothing but version numbers |
| Current WordPress and PHP | Check the WordPress and PHP versions the listing says it supports | Support that stops well behind the version your host runs |
| Speed on a phone | Run the demo through Google's PageSpeed Insights and read the mobile result | A slow demo, which only gets slower once your content and plugins are added |
| Responsive layout | Open the demo on a real phone and resize a desktop browser slowly | Menus, tables or forms that overflow, or text you have to zoom to read |
| Editing without code | Try changing the colours, fonts and sidebar in the demo or a trial install | Basic changes that need custom CSS or a support ticket |
| Child theme support | Look for a ready child theme or documentation on making one | Instructions to edit the theme's own files directly |
| Features it bundles | List what the theme adds besides design: forms, sliders, shortcodes, portfolios | Content you would lose if you switched theme (see the next section) |
| Accessibility and browsers | Tab through the demo with the keyboard, and open it in two or three browsers | No visible focus, menus that only work with a mouse, layouts that break in one browser |
| Support and licence | Read what the price covers, for how long, and where questions get answered | Updates that stop when a yearly licence lapses, or a support forum with no recent replies |
| An original design | Compare the demo with the sites it resembles | A close copy of a well-known site's layout, which says something about the seller |
The speed check needs one caution. A demo is usually a light page on fast hosting, so treat a slow demo as a clear no and a fast one as a maybe. The guide to speeding up a slow WordPress site covers what affects speed once the site is real.
The responsive check is worth doing with your own content rather than the demo's. A layout built around short headlines and square photos can fall apart with long product names, and what responsive web design is and how to test for it explains what to look for.
The lock-in nobody mentions
Many commercial themes bundle features that have nothing to do with design: a contact form, a slider, a portfolio section, testimonials, page layouts built from shortcodes. They feel like value when you buy. They become a problem the day you change theme, because everything the theme provided goes with it.
The WordPress.org theme review team draws this line deliberately. Its required guidelines for directory themes (checked 12 October 2026) list shortcodes, custom post types, contact forms, SEO options and analytics as plugin territory, which a theme in the directory may not include. Commercial themes sold elsewhere are not bound by that rule, which is why the check matters most for them.
| Feature | If the theme provides it | If a plugin provides it |
|---|---|---|
| Contact and enquiry forms | The forms disappear, along with any connection to where submissions were sent | The forms keep working and keep sending to the same place |
| Shortcodes in your pages | The pages show the raw shortcode text where the content used to be | The content keeps rendering under the new theme |
| Portfolios, testimonials and other custom content | The entries become hard to reach, or vanish from the site | The entries stay, and the new theme only has to style them |
| SEO settings | Titles and descriptions set in the theme are lost | They carry over unchanged |
| Analytics and tracking | Tracking stops without warning, and the gap shows up later in your reports | Tracking continues through the change |
The practical rule is to keep design in the theme and everything else in plugins. It is also why a child theme matters: WordPress's own child theme documentation describes it as a way to change a theme without editing the theme's code, so your changes survive the theme's next update. A property site is the clearest example: listings belong in a plugin, as building a real estate website on WordPress explains. For the everyday jobs, such as SEO, forms, backups and security, which WordPress plugins to install names one plugin for each.
When what you need is not in any plugin, where custom WordPress code should live explains how to build it so it survives the next theme.
If someone else is building the site
When an agency or freelancer chooses the theme, the same checks apply, but the questions shift to who holds the licence and who applies the updates. What to settle before hiring a WordPress web design company covers the four common build methods, from a customised theme to a custom one, and what each means for editing later. If it is one freelancer, how to vet a WordPress developer lists six checks.
The theme is also only one line in the budget. Hosting, premium plugins and the time spent keeping everything updated usually cost more over the life of the site, and what a WordPress website really costs breaks those lines down.
Check what the theme has to connect to
A theme decides how the site looks. It does not decide what happens when someone fills in your contact form, and that is where a business site earns or loses its enquiries. Before you commit, check that the theme works with the form, booking and chat tools you plan to use, rather than replacing them with its own.
Install your chosen form plugin on a trial copy with the theme active and submit a test enquiry. If the form looks wrong, or the theme insists on its own form builder, that is a sign the theme will fight you later. Run the same test again on the live domain before launch; the WordPress website launch checklist lists it with the other go-live checks.
Where the submission goes next is a separate job from the theme. Connecting WordPress to a CRM sets out the three ways to do it, and our CRM setup and management work covers the instant reply and follow-up behind the form, with GoHighLevel as the platform we recommend first.
Where AI helps, and where it does not
An AI assistant can shorten the checking. Paste in a theme's changelog and it will summarise how often real fixes ship; describe a layout change and it can draft the child theme CSS for it. Both save time, and both still need a person to read the result before it goes live.
It cannot tell you how a theme behaves with your content, your plugins and your host. That only shows up on a trial install, so treat an assistant as a fast reader and a first draft, not as the test itself.
If what you need is more than a theme can give, such as customer accounts, a booking system or a dashboard, that is an application rather than a website. Our AI web and app development work starts from that question.
Common questions
Is a free WordPress theme good enough for a business site?
Often, yes. Themes in the WordPress.org directory have passed a review against published guidelines, are free to update, and keep non-design features out. A paid theme is worth it when it saves real build time, not because it is paid.
Should I choose a block theme or a classic theme?
For a new site, a block theme keeps you closest to the editing tools built into WordPress itself. A classic theme still makes sense when you depend on a page builder or plugins that have not caught up, so check that before deciding.
Can I change my WordPress theme later?
Yes, but expect work in proportion to how much the old theme did besides design. A site whose forms, shortcodes and custom content came from plugins can switch in a day; one built around a theme's own features may need pages rebuilt.
Do I need a child theme?
You need one as soon as you change the theme's templates or code. A child theme keeps those changes separate, so the parent theme can update without overwriting them. If you only change settings in the editor, you may not need one.
Can you set up the forms and follow-up on our WordPress site?
Yes. We connect WordPress forms to GoHighLevel, HubSpot, Keap, ActiveCampaign and other CRMs, and build the instant reply and follow-up behind them. Every project is quoted after we understand the setup (how automation projects are priced explains why), so tell us where your enquiries arrive today and we will say what is worth connecting.
