How to Choose a WordPress Agency: 12 Questions

Choosing a WordPress agency means looking beyond a polished portfolio. Ask how the agency connects design to your goals, who owns the code and accounts, how the site is tested, and what you receive at handoff. The answers will help you compare proposals and avoid a website that looks good in a mock-up but is hard to use or leave behind. If you are weighing agency approaches, start with our guide to comparing DesignFIT with other agencies.

A WordPress website is both a customer-facing design and a working business asset. Its page structure, typography, imagery and calls to action affect how easily visitors understand your offer. Its hosting, code, licences and editing tools affect how safely your team can run it. A strong agency should be able to explain both sides without hiding behind technical jargon.

Below are 12 questions to ask before you sign. You do not need to know the technical answer in advance. You do need to understand what the agency proposes, why it suits your business and what happens if you later choose a different supplier. For more context on what a website project can involve, see our website design service.

Before you shortlist an agency

Start with the problem the website needs to solve. “We need a refresh” is a useful starting point, but it is not a brief. Do you need more enquiries from a particular audience? A clearer explanation of a complicated service? Better performance on mobile? A site your team can update without asking a developer to change every heading?

Write down your main audience, the actions you want visitors to take, the pages you expect to need and any practical constraints. Note what is working on the current site as well as what is not. Analytics, search data, customer questions and sales conversations can all help identify where visitors get stuck. If you have no reliable data, say so. A good discovery process can establish what to measure rather than pretending the answer is already known.

Then ask each agency to explain how its proposed design supports those goals. Visual hierarchy is the order in which a page draws attention. For example, a service page might make the service and its benefit clear first, show proof next, then give a visitor an obvious way to enquire. If everything is equally prominent, people have to work harder to decide what matters.

A wireframe is a simple plan of a page’s content and layout, usually made before the finished visual design. It helps the team agree what information belongs where before spending time refining colour, imagery and detail. A component is a reusable part of a site, such as a testimonial panel or service card. Thoughtful components keep pages consistent while giving the team suitable options for different content.

An agency may use WordPress in very different ways. WordPress is a content management system, or CMS: software that lets a team create and manage website content through an administration area. The label “WordPress website” does not tell you whether the design is custom, whether editors can safely make changes, or whether the site relies on a collection of paid tools. Ask about the actual system being proposed.

Questions about design and performance

1. How will you design the site around our customers and business goals?

Ask the agency to describe its design process, from discovery through to approved page designs. Does it clarify who the site is for, what those visitors need to know and which action matters on each page? Will it map the content and user journeys before visual design begins? A user journey is the path a visitor follows from arriving on the site to completing an action, such as booking or sending an enquiry.

A strong answer connects those decisions to the results you want. For example, if potential customers need to compare several services, the agency might recommend a clear overview page with links to detailed service pages, rather than forcing all the information into one long block. If visitors need reassurance before contacting a clinic or professional firm, the design might bring relevant credentials, process details and contact options into view at the points where questions arise.

Ask to see a relevant example and have the agency explain what problem its design choices addressed. A portfolio image on its own does not tell you whether the site is easy to navigate, whether the editor can update it or whether the work was designed for an audience like yours. Look for reasoning, not just attractive screenshots.

Be cautious if the process is mainly “send us your logo and we will make it look modern”. Brand colours and imagery matter, but they cannot replace a clear content structure. The agency should be able to explain why it recommends a layout, what visitors should notice first and how the page encourages the next useful step.

2. Are you designing a custom site or adapting a pre-built theme?

A theme is a set of templates and styling that controls how a WordPress site looks. A pre-built theme can be a reasonable starting point for a small, simple website, especially when budget and speed are the main constraints. A custom design is shaped around your brand, content and customer journey. Neither option is automatically right for every business, so ask what the proposal includes and what trade-offs come with it.

If the agency adapts an existing theme, ask which parts are fixed and which can be changed. Can the team adjust page layouts when your services or content grow? Will the theme’s built-in features add controls you do not need? Who maintains the theme, and what happens if its developer stops supporting it? Ask to see a sample page on mobile, not only a desktop mock-up.

If the agency proposes a custom design, ask which pages will receive bespoke layouts and which will use shared templates or components. Custom does not have to mean every page is designed from scratch. A well-planned system can give distinctive pages where the business needs them, while reusing consistent patterns for routine content. That can make a site easier to navigate and less expensive to maintain.

A useful agency can explain how typography, spacing, contrast and imagery will work as a system. For instance, a type scale sets consistent sizes for headings, body copy and supporting text. It helps visitors scan pages and lets editors publish new content without inventing new styles each time. Ask whether design files and key rules will be documented, not just shown in a presentation.

3. Which editing system will you build with, and why?

WordPress offers a built-in editor called the Block Editor, often referred to by its development name, Gutenberg. It lets editors assemble content from blocks such as paragraphs, images, buttons and columns. Some agencies build around this native system. Others use third-party page builders such as Elementor or Divi, or create a mixture of custom and supplied components.

Ask the agency to demonstrate how you would edit a typical page. Can a marketing team change a heading, update an image or add a new service without shifting the layout? Can you create a page using approved patterns, or must you contact the agency for every new landing page? Ask whether the editing experience they demonstrate is the one included in your proposed build.

There is no universal rule that one editor is always best. A third-party builder may suit a team that needs visual editing and has agreed to its ongoing requirements. A carefully built native block setup may suit a business that wants a more controlled editing experience. What matters is that the agency can explain the reason for its choice, the training required and any recurring licence or maintenance costs.

Ask what happens to your content and design if the builder or a related plugin is removed. If the answer is that pages would need to be rebuilt, make sure you understand that dependency before signing. Ask for an example of the site’s editing interface and request a plain-language list of the main tools the site will rely on.

4. How will design decisions support speed and accessibility?

A fast website gives visitors less time to wait for key content to appear or controls to respond. Accessibility means designing and building so people with different abilities can use the site. It includes practical details such as readable contrast, clear focus states for keyboard users, useful image descriptions and headings in a meaningful order.

Ask the agency how it will consider performance and accessibility during design, not only after launch. Design choices can affect both. Large images, multiple font files, decorative video and busy animation may add weight or distract from important content. Small text, low contrast and buttons that are difficult to operate on touchscreens can prevent people from completing tasks.

Ask what the agency will test and when. Does it plan to review key pages on mobile? Will it test forms, navigation, keyboard access and common screen sizes? How will it handle images, font loading and third-party scripts? If it gives you a promise that the site will “score perfectly”, ask what that means, which tools it uses and whether the promise includes real-world conditions such as your hosting, content and analytics tools.

A page speed result is not the whole user experience. A useful review looks at the actual pages people need, identifies what is slowing them down and weighs any visual or functional feature against its cost. For example, a carousel may be visually prominent, but if it makes the main message harder to understand, a simpler layout may serve visitors better. Ask the agency to state what it can control and what depends on your hosting or third-party services.

Questions about ownership and independence

5. What will we own when the project is paid for?

Ask for a written list of what transfers to you at completion. It may include the custom theme or code, design source files, page content, images commissioned for the project and documentation. Do not assume that “you own the website” answers every ownership question. Some contracts distinguish between custom work created for you and pre-existing tools or code the agency uses across projects.

Ask the agency to explain those exceptions in plain English. If it uses a reusable framework, a commercial theme or a licensed font, find out what you receive and what rights apply. A licence is permission to use a tool or asset under stated conditions. It is not necessarily ownership of the underlying product. Ask whether the licence can be transferred, whether it must be renewed and what changes if your agreement with the agency ends.

The design source file is also useful. It is the editable working file for the design, rather than a flat image or exported PDF. If you later hire another designer, the source file can help them understand the layout and reuse approved brand elements. Ask whether that file is included, when it will be delivered and whether any third-party assets inside it have their own usage terms.

The contract should describe ownership and transfer clearly, including any payment conditions. If the agency says its standard terms do not allow you to own a particular custom component, ask why, what it would cost to change that and what happens if you stop working together. If the answer is unclear, get independent advice before signing.

6. Who will own the domain, hosting and key accounts?

Your domain is the address people use to reach your website. Hosting is the service that stores and serves the site so it can be viewed online. Ask who will be the legal account holder for the domain and hosting, whose payment details will be used and whether your business will have administrator access. The safest arrangement is one where your business controls the important accounts and can grant the agency the access it needs to do its work.

An agency can still manage hosting or technical work for you. Management does not have to mean that the agency owns the account. Ask whether you can log in, see invoices, change payment details and add another supplier. If the agency hosts many clients under one account, ask how each site is separated, how backups work and what the migration process would be if you leave.

Do not hand over your only domain login in a casual email or accept a vague promise that the agency will “sort it out later”. Confirm that the domain is registered to the business and that renewal notices go to an address you control. If the agency already manages your domain, ask it to confirm the registrar, account owner and renewal date in writing.

If you are comparing project costs, look at the ongoing arrangement as well as the initial build. Our website pricing information can help you think through the scope and commercial questions to clarify with any provider. Ask agencies to separate build fees, hosting, support, licences and optional services in their proposals so you can compare the same things.

7. Which plugins, themes, fonts and other services will the site depend on?

A plugin is an add-on that gives WordPress extra functionality, such as a contact form or search tool. A website may also rely on paid fonts, stock images, analytics, booking services or an external email platform. These dependencies can affect the site’s cost, operation and portability. Ask the agency to provide a list of the tools it expects to use and explain what each one does.

For every paid tool, ask whose account will hold the licence, who pays for renewals and whether you can take it with you. If the agency provides access through a shared developer licence, ask what rights you have and whether updates continue if you end the agency relationship. A low upfront price can be less attractive if it depends on a recurring service that was not explained in the quote.

Ask why each plugin is needed. More plugins do not automatically mean a poor site, and a small number does not prove quality. The relevant questions are whether each tool has a clear job, whether it is maintained, whether it overlaps with another tool and who is responsible for keeping it working. Be wary of a proposal that lists tools without explaining their purpose or ongoing cost.

Ask what happens to site functions if a tool is removed. If a form plugin is responsible for enquiry submissions, for example, will the form data remain accessible? If a booking service is involved, can you export the information you need? The agency should identify critical dependencies and explain how your business can manage them after handoff.

8. If we leave, how do we move the site to another provider?

Ask the agency to walk through a real exit, not just say that the site is “portable”. What files and data would you receive? How would the new provider get access? Would there be a transfer fee? Does the site use standard WordPress tools, or does a proprietary system need the original agency to make routine changes?

A database is the structured information store used by WordPress for content and settings. A backup is a copy of the site’s files and database that can be restored if something goes wrong. Ask whether you can obtain a complete backup and whether it can be used to move the site. Also ask if the agency has documented any special steps needed to set the site up in a new environment.

Look for a reasonable, documented process. A new developer should not need to reverse-engineer a secret system just to change a button or publish a page. On the other hand, some migration work can be genuinely necessary when changing hosts or services. Ask for the likely scope, access requirements and fee basis instead of expecting every transfer to be instant or free.

A discussion among WordPress users about what happens when a client and provider part ways is a useful reminder to make exit terms explicit. It is an individual community discussion, not a universal description of agency practice. Use it to prompt questions, then rely on the written agreement with your own provider.

Questions about build quality and safe operation

9. What is your process for building, reviewing and launching the site?

Ask where the site will be built and how changes reach the live version. A development environment is a private place to work on the website. A staging site is a separate, pre-launch copy used to review changes before visitors see them. Version control is a system that records changes to code, so a team can review what changed and, where appropriate, return to an earlier version.

You do not need to require a particular tool or workflow for every project. You do need a process that reduces the chance of unreviewed changes breaking the public site. Ask whether the agency works directly on the live website, how it tests changes, who approves them and how it restores the site if a release causes a problem.

Ask what you will review before launch. You should have a chance to check page content, links, forms, mobile layouts and important customer journeys. For an online store, include product selection and checkout in the review. For a service business, test how an enquiry reaches the right person. Ask how late content changes are handled, as missing or rushed content can undermine an otherwise polished design.

A launch checklist should cover more than switching the site on. Ask who checks redirects from old URLs, search indexing settings, analytics, form delivery and backups. A redirect sends visitors and search engines from an old address to the relevant new one. The agency should clarify which tasks are in scope and which depend on your existing systems or another supplier.

10. How do you handle WordPress, plugin and theme updates?

WordPress sites need maintenance. Core software, themes and plugins can receive updates that change their features or address problems. Updates should not be treated as a purely mechanical task, because a change can affect how a form, layout or integration works on your particular site.

Ask whether updates are automatic, reviewed or applied through a managed process. Find out who checks whether the site still works afterwards and what the agency does if an update causes a problem. Ask whether backups are taken before a significant change and how restoration works. A backup that has never been tested may not be a reliable recovery plan, so ask how often the process is checked.

Ask what the maintenance fee includes. Does it cover software updates, backup monitoring, security checks, uptime checks, small content changes or technical support? These are different services, and a monthly fee can cover some, all or none of them. Get the response time, exclusions and process for urgent work in writing.

Do not accept a promise that maintenance means the site can never fail or be compromised. Ask what risks the agency monitors and what happens if a problem is found. A sensible provider explains its responsibilities and limits, gives you a way to report an issue and keeps you informed about work that may affect the website.

11. How will our team edit content without damaging the design?

A good handoff is not “here is an administrator password, good luck”. Ask the agency to show how your team will make common updates and what parts of the design are protected. A content editor role is a set of permissions for people who need to edit pages without having access to every technical setting. The right permissions depend on your team and how the site is managed.

Ask for a practical demonstration using a representative page. Can an editor replace a photo and understand its crop? Can they add a new service using an existing layout? Can they create a new page without changing the site’s global typography or spacing by accident? Ask whether the agency will create reusable patterns or templates for recurring content, and whether those patterns have clear names and instructions.

This is where design and editing meet. If every page has a different heading scale or inconsistent spacing, visitors may struggle to scan the site and the brand can become fragmented. If the system is too restrictive, your team may be unable to publish useful pages without a developer. The aim is controlled flexibility: editors have choices that fit the design system, while core layout rules remain consistent.

Ask how training works and who can attend. Request written guidance for recurring tasks, such as publishing a page, changing a call to action or adding an image. If your team turns over or the website is handed to a new marketer, that guidance can reduce dependence on one person’s memory.

12. What exactly is included in the handoff and post-launch support?

Ask for a handoff checklist before the project begins. It should say what you receive, who explains it and when. Depending on the scope, the package might include administrator access, hosting and domain details, a list of plugins and licences, design files, backups, technical documentation, analytics access and training. Confirm which items are included rather than assuming they are standard.

Ask whether the agency provides a handover meeting and a post-launch support period. Find out what that support covers, how you report an issue, what counts as a defect and what is considered new work. A defect is a part of the delivered site that does not work as agreed. A new feature or change in direction may need a separate estimate. Clear definitions prevent both sides from making different assumptions after launch.

Ask who is responsible for each ongoing task: content updates, technical maintenance, hosting questions, design changes and troubleshooting third-party services. If the agency offers a monthly retainer, request a breakdown of included hours or work, response expectations and what happens to unused time. If support is available only on request, ask for the hourly or project pricing method.

A project should leave your team more capable, not confused about who controls the site. A written handoff gives the next person enough information to take over, whether that is an employee, a different agency or the original provider in a new arrangement. The questions to ask when building a website can provide another prompt list, but tailor every question to the scope and terms in your own proposal.

How to compare agency answers

Do not choose based only on the number of pages, the visual style of a portfolio or the lowest quote. Compare what each agency is actually offering. A short proposal may exclude content support, accessibility review, migration, training or post-launch maintenance. A detailed proposal may include those items, or it may simply be better at describing exclusions. Ask for clarification before comparing totals.

Area	A clear answer should explain	Follow-up to ask
Design	How research, content and customer journeys shape layouts	Which pages are custom, and which use shared templates?
Editing	How your team will update common content	Can we see the editing experience on a sample page?
Technology	Which theme, editor and plugins the site depends on	What recurring fees or limitations should we expect?
Ownership	What code, files and accounts transfer to the business	Where is ownership described in the contract?
Hosting	Who owns the account and controls access	What is the process and cost to move hosts?
Quality	How the team tests design, forms and mobile behaviour	What must pass before launch?
Support	What maintenance and response arrangements are included	What is outside the monthly fee?
Handoff	What documentation, training and access you receive	Who will be responsible for each task after launch?

Look for specific answers that refer to your project. “We do quality work” is not as helpful as an explanation of which pages will be tested, who signs off content and how the site is transferred. If an agency does not know an answer yet, it should be able to say what it needs to confirm and when you will receive the detail.

Notice how the team handles questions. Do they listen to the business problem, explain trade-offs and offer alternatives? Or do they dismiss concerns, promise guaranteed outcomes or avoid putting responsibilities in writing? An agency should be able to say when a simpler design or smaller scope is the better choice for your needs.

You can also ask for two versions of the proposal if you are unsure about scope. For example, one option might cover a focused redesign of the key pages, while another includes a wider content restructure and additional templates. Compare what each option enables and what it leaves for later. A transparent scope makes it easier to decide whether the difference in price is worthwhile.

For another perspective on cost questions, see this WordPress website cost guide. Treat any online cost guide as a starting point, not a quote for your project. The number of page templates, content migration, integrations, custom design, accessibility needs and ongoing support all affect what an agency is being asked to deliver. For a separate view of ongoing service arrangements, Codeable explains common WordPress maintenance pricing considerations. Check the provider’s current terms directly before relying on any published price.

Which WordPress agency should you choose?

Choose an agency that can link its design decisions to your business goals and explain its technical choices in language your team understands. It should show you how the site will work for visitors and editors, not only how the homepage looks in a presentation. It should also be open about ownership, licences, hosting, support and what happens if you leave.

A smaller or simpler project may suit an agency that adapts an existing theme, provided it explains the limitations and gives you a usable editing setup. A business with distinctive customer journeys, complex content or several marketing needs may benefit from a more tailored design system. If your team expects to publish frequently, prioritise the editing experience and training. If the site is central to enquiries or sales, ask for more detail about testing the complete customer journey.

Before you decide, check that the agreement answers these points:

• The pages, features and integrations included in the build.
• The design and content approval stages.
• The theme, editor, plugins and third-party services involved.
• Ownership and transfer of code, design files, content and accounts.
• Hosting, backups, updates and the process for moving the site.
• What will be tested before launch and who approves the final site.
• Training, handoff documentation and post-launch support.
• Fees for ongoing services, additional work and ending the relationship.

If any answer is missing, ask for it in writing before signing. Clear answers protect your budget and your ability to make future changes. They also give you a fairer way to compare two agencies whose proposals may look very different.

The questions that reveal a good agency

A good WordPress agency does more than make pages look polished. It turns what it learns about your customers into a clear design, builds an editing experience your team can manage, and makes the practical responsibilities visible. Questions about ownership, hosting and handoff are not signs of mistrust. They are part of buying a durable business asset.

Use the 12 questions to guide your shortlist conversation, then compare the written answers alongside the proposed design approach, scope and support. If you are ready to discuss your project and what it needs to achieve, start a project with DesignFIT.