Scope questions
Know which pages, templates, features, content tasks, and integrations are actually included.
SWAP DESIGN / BUYER CHECKLIST
How to choose a WordPress developer in the UK without judging only by screenshots.
A practical checklist for small-business owners comparing process, ownership, testing, on-page SEO, support, and handover.
UK-FIRST / CHOOSE
The useful question is not only “Can you build a good website?”
Choosing a WordPress developer is not only about finding someone who can make a good-looking page. You are choosing the person or team who will make decisions about structure, performance, access, forms, content, and what happens when something stops working. Compare the way the work will be done, not only the final screenshots.
Ask how the developer would approach your particular business, what will be included, who owns the accounts, how feedback will work, how the site will be tested, and what happens after launch. A clear process is easier to manage than a vague promise.
PROJECT DIRECTION
Compare the process, not only the portfolio.
Scope, ownership, testing, and support tell you more about the working relationship than a gallery of screenshots.
01Scope
02Ownership
03Testing
WHAT YOU GET
The important parts stay visible from the beginning.
Use the scope to understand the work, the decisions, and the next step before anything becomes unnecessarily complicated.
Ownership checks
Keep domain, hosting, WordPress, analytics, files, and licence access understandable.
Quality checks
Ask how mobile layouts, forms, links, accessibility basics, and launch behaviour will be reviewed.
Support clarity
Understand handover, maintenance boundaries, change requests, and the next step after launch.
01
Before you agree
Seven questions that make a WordPress project easier to manage.
Before work begins, make sure the important responsibilities are visible. You should not have to discover who supplies content, controls access, approves changes, or checks the forms after development has already started.
01
What exactly is included in the scope?
02
Who is responsible for content, images, and approvals?
03
Who owns the domain, hosting, website, and accounts?
04
How will mobile, forms, accessibility, and performance be checked?
05
What happens when the project needs a change or extra feature?
06
What support is available after launch?
07
How will progress and access be handled?
02
Look for relevant thinking
A portfolio shows what was made. It may not show how the decisions were made.
Ask about a project with a similar problem: confusing services, a slow website, a difficult migration, an awkward enquiry journey, or a team that needed to manage the site themselves. The best answer explains the reasoning, the checks, and the boundaries.
01
A problem similar to yours
02
A clear explanation of the chosen approach
03
Visible testing and approval points
04
A handover that leaves the business in control
03
A real reference point
Use relevant work as a conversation starter, not as a promise of the same outcome.
DolpTec is a UK technology business for which Swap Design completed the WordPress development and on-page SEO foundations in 2025. The website screenshots and logo are approved for use. They show the kind of work delivered, but they do not prove that every business will receive the same result.
01
Complete WordPress development
02
On-page SEO foundations
03
Approved website screenshots
04
No unsupported numerical outcome claim
4answer-ready questions
ANSWER-READY CONTENT
Useful answers before you decide what to do next.
The questions below are written for the decision a small-business owner is actually trying to make.
The project should state what on-page SEO means in that particular scope. It may include titles, headings, indexability, internal links, image text, and basic page structure. Keyword research, content writing, link building, and ongoing SEO are separate unless clearly agreed.
The business should have clear access to its domain, hosting, WordPress administration, important accounts, files, and purchased licences. The handover should explain ownership rather than leaving it unclear.
There is no single correct number. The important point is that the process explains when feedback is collected, who approves it, and what happens if the requested work changes the agreed scope.
Yes. Remote work needs a simple working agreement covering feedback, access, staging, approvals, communication, testing, and handover. You should know the next decision without needing to be online all day.
START WITH A CONVERSATION
Have a website question?
Share the problem in a few lines and I will help you identify the next practical step.