WordPress

Hiring a WordPress Developer: A Checklist Before You Sign

Hiring a WordPress Developer: A Checklist Before You Sign: MeraSEO article cover
Key takeaways
  • Judge a WordPress developer on live sites you can open on your phone, not on screenshots. Test their speed, check their forms and ask what they built versus installed.
  • Get ownership in writing: domain, hosting, admin accounts, source code and any paid plugin licenses should be registered in your name.
  • Ask how they handle staging, backups, updates and plugin choices. These practices decide whether your site is still healthy a year after launch.
  • Make handover and support terms part of the quote, so you are never locked in to one person.

Hiring a WordPress developer looks easy because the platform is so common. That is exactly the problem: plenty of people can install a theme, and far fewer can build a site that stays fast, secure and editable by your team. Mistakes show up months later as a slow site, a hacked login or a developer who cannot be reached.

This checklist covers what to verify before you sign. Use it whether you are hiring a freelancer, a small studio or an agency. If you want an overview of what we do for clients, see our WordPress development page.

1. Look at live sites, not just a portfolio

A portfolio page shows what a site looked like on launch day. A live URL shows what it is like now. Ask for three or four live sites, ideally of different types, and check them yourself.

  • Open each on a mobile phone over mobile data, not office Wi-Fi. Does it load quickly and stay stable as it loads?
  • Run the home page and one inner page through PageSpeed Insights, and read the field data if shown. Google’s Core Web Vitals guidance lists the thresholds; a “good” Largest Contentful Paint is 2.5 seconds or less.
  • Submit the contact form and see whether an email actually arrives.
  • Check for broken buttons and cards. On our own site, a crawl of about 230 pages found 286 links that pointed to “#” or “javascript:void(0)”, mostly from page-builder widgets whose link field had been left at its default. It is easy to miss and easy to check for.

Then ask: which parts did you design and build, and which are an off-the-shelf theme? A good developer answers plainly.

2. Settle who owns what

This is the most expensive thing to fix later. Before any work starts, get the following in writing.

AssetWho should own itWhat to check
Domain nameYou, as registrantWHOIS or registrar login is in your business details
Hosting accountYou, or a clearly documented reseller arrangementYou can log in and download a backup
WordPress adminYou, with at least one administrator accountDeveloper uses a named account, not a shared one
Custom code and design filesYou, once paidContract says so; code is delivered, not only deployed
Premium plugin and theme licensesRegistered to your emailRenewal dates and costs are listed
Analytics and Search ConsoleYouDeveloper added as a user, not owner

3. Ask how they choose themes and page builders

There is no single right answer, but there should be a reasoned one. A premium theme with a page builder is quick and cheap to start and works well for many brochure sites. A custom theme costs more up front and can be lighter and easier to maintain. Block themes shift some design work into the editor. Ask which approach they recommend for your site and why, and what happens to your content if you ever change the theme or builder.

We explain when a custom theme is worth it in custom WordPress theme development. If you need a tailored custom WordPress website, ask for a short written rationale for the choice, not just a quote.

4. Check their plugin discipline

Plugins are the main reason WordPress sites slow down and break. Good developers add them deliberately.

  • Ask for the plugin list before launch, with a one-line reason for each.
  • Check that each plugin is maintained, with recent updates and active support.
  • Prefer one well-built plugin over three overlapping ones.
  • Ask whether a small piece of custom code would be safer than a heavy plugin; read when custom plugin development makes sense.
  • Ask what they do when a plugin is abandoned by its author.

If you already have a site full of plugins, our guide on auditing and cutting plugin bloat shows how to review it before hiring anyone.

5. Security basics they should do by default

Security is mostly boring routine. Ask which of these they do as standard:

  1. Keep WordPress core, themes and plugins updated, with a note of when each update was applied.
  2. Restrict file permissions, for example locking wp-config.php down to permissions 600 (or whatever is tightest that the server setup allows), as we do on the roughly 70 WordPress sites we host and maintain.
  3. Block direct web access to sensitive files such as configuration files, logs, database dumps and backups.
  4. Never leave old database dumps or backup archives inside the public web folder. This is a common problem we see when auditing hosting accounts, because anyone who guesses the file name can download it.
  5. Use unique admin usernames, strong passwords, two-factor authentication where available and limited login attempts.
  6. Remove unused themes and plugins instead of just deactivating them.

For practical background, the WordPress project publishes developer documentation at developer.wordpress.org.

6. Speed is a build decision, not an add-on

Ask what they do to keep pages light: image formats and sizes, caching, fonts, and how many CSS and JavaScript files load on each page. These are things they should be able to describe in specific terms.

As an example from our own work, cutting render-blocking CSS files from 25 to 4 on meraseo.in brought mobile Largest Contentful Paint on service pages from about 4.1 seconds to roughly 2.6 to 2.9 seconds in PageSpeed Insights. We also removed jQuery Migrate from the front end after the browser console showed nothing depended on it. Those are small, testable steps. A developer who can tell similar stories, with the console or a tool as evidence, is thinking about performance properly.

7. Staging, backups and updates

  • Staging: changes should be tested on a copy of the site first, then pushed live.
  • Backups: automatic, stored off the server, and tested by actually restoring one. Ask when they last did.
  • Updates: who applies them, how often, and who fixes things if an update breaks the layout?
  • Redirects: if they rename a page, do they add a 301 redirect? WordPress redirects a renamed post slug automatically but not a renamed page slug, so this must be done by hand.

8. Handover and documentation

At the end of the project you should receive:

  1. All logins in a password manager or other secure transfer, never in a chat message.
  2. A short document listing hosting, plugins, licenses, custom code locations and renewal dates.
  3. A walkthrough, ideally recorded, showing how to edit pages, menus, forms and images.
  4. A list of any custom code with comments, so another developer can continue.
  5. Confirmation that test accounts and temporary access have been removed.

9. Support terms

Ask what happens after launch before you sign, not after something breaks. Clarify a warranty period for bugs, response times, what counts as a bug versus a new request, and whether ongoing care is separate. Our WordPress maintenance and support page describes the kind of cover we mean, and a recurring plan is worth comparing to ad hoc hourly help.

Red flags

  • They will not name a live site they built, or every site looks identical.
  • They want to register the domain and hosting in their own name.
  • No staging site, no backups, “we fix it directly on the live site”.
  • Pirated or “nulled” themes and plugins. These are a common route for malware.
  • A fixed price with no written scope, or a scope that excludes content, forms and mobile layout.
  • They refuse to share admin access after launch.
  • No questions about your business, customers or goals.

Questions to ask in the interview

  1. Which of your live sites should I look at, and what did you build on each?
  2. Who will own the domain, hosting and code?
  3. Which theme or builder do you recommend and why?
  4. List the plugins you would install and what each does.
  5. How do you test, stage and back up?
  6. What does handover include?
  7. What happens if you are unavailable for two weeks?
  8. Are payments tied to milestones (design sign-off, staging approval, launch), and will you issue a GST invoice?

Frequently asked questions

How do I check if a WordPress developer is good?

Open their live client sites on a phone, test speed and forms, and ask what they built versus installed. Ask for their plugin list, backup process and handover document. A good developer gives specific answers and does not mind you owning your hosting, domain and admin access.

Should I hire a freelancer or an agency for WordPress?

A freelancer can suit a small, well-defined site if you can check their live work and have a backup plan. An agency gives continuity, project management and multiple skills such as design, SEO and security. Choose based on scope, risk and who will maintain the site after launch.

Who should own my WordPress site?

You should. Register the domain and hosting under your business details, hold an administrator account and keep a copy of the code and licenses. The developer can be added as a user. Put this in the contract so there is no dispute if the relationship ends.

Do I need ongoing WordPress maintenance after launch?

Yes, in most cases. WordPress core, themes and plugins need regular updates, backups should be checked and security issues monitored. You can do this yourself with some skill, hire the original developer or use a maintenance plan, but leaving a site unattended for a long time is risky.

Planning a WordPress project?

Share what you need and we will answer the checklist questions above for your project: who owns what, which plugins, how it is staged and what support follows.

Talk to a WordPress developer →

Related Post

Call Now Button