A WordPress website should help the right visitor understand your offer and take a useful next step. Before requesting a quote for a new site, define that journey, the pages it needs, and what your team must be able to manage after launch. A clear brief makes proposals easier to compare and reduces surprises during the build.
This checklist focuses on planning a new WordPress website: its purpose, pages, content, account ownership, design, enquiry journey, launch checks, and handover. If you are replacing an existing live site, use our separate existing-site migration checklist for URL mapping, redirects, staging protection, and post-launch search checks.
1. Define the job of the website
Choose the main action: a project enquiry, a consultation request, a purchase, or a booking. Then describe the visitor and the questions they need answered before taking it. A service business may need scope, process, trust, and contact details; a product business may need specifications, delivery information, returns, and checkout clarity.
Write one practical goal, such as helping suitable prospects submit enough information for an initial conversation. Avoid treating a particular traffic number or a more dramatic design as the entire brief.
2. Agree the page list and content responsibilities
List the required pages, including individual services, about, contact, relevant policies, and useful buyer resources. Give each page a purpose and a next step. Decide who supplies copy, product information, photography, brand assets, and any genuine client evidence.
- Which pages are included, and which require a separate scope?
- Who writes, checks, and approves the text?
- Which existing content should be kept, rewritten, or retired?
- Does the business need multilingual content, ecommerce, or booking functionality?
- Who checks that published claims and testimonials are accurate?
Use a real content inventory rather than designing every page around placeholder text. A clear page structure also supports relevant SEO work later.
3. Make account control part of the brief
Agree which business account will hold the domain registration, hosting, WordPress administrator access, analytics, and paid licences. Record who can manage each service and who receives renewal notices. Access should be provided through appropriate user accounts rather than a shared password sent around the team.
A handover should explain what you control, what a supplier manages, and how access is transferred if the working relationship changes. For domain and hosting questions, review our domain and hosting service and confirm the proposed arrangement before purchase.
4. Specify an editable design system
A useful build has consistent colours, typography, buttons, spacing, and reusable sections. Ask how your team will update headings, service copy, images, and calls to action without rebuilding a page.
If Elementor is part of the agreed setup, clarify which templates and native widgets will be used, which features need a paid licence, and who maintains it. The goal is an editing experience your team can use with confidence. Ask for a short demonstration using a real page during handover.
5. Plan the enquiry journey
Agree the form fields, required information, receiving address, confirmation message, and follow-up responsibility. Keep the form focused on what is needed for the first conversation. A WhatsApp link can provide another route, but it should open the correct business number with a useful starting message.
Define what counts as an enquiry and how spam or unsuitable requests will be reviewed. Before launch, check the complete journey: form validation, submission recording, confirmation, and actual delivery to the intended inbox. A visible thank-you page alone does not prove that the team received the message.
If Google Search ads are part of the website launch, use the Google Ads launch checklist to align the advertised service, landing page, enquiry handoff, and conversion goal before approving campaign spend.
6. Treat mobile usability and effects as one decision
Review actual mobile pages, including long headings, menus, forms, cards, and the footer. Text should remain readable and buttons should be easy to reach. Check that the page does not force sideways scrolling and that important information does not depend on hovering.
Use animation to guide attention without delaying reading or interaction. Ask how entrance effects behave on smaller screens and for visitors who prefer reduced motion. Test the useful actions as carefully as the visual presentation.
7. Plan a safe launch for your new website
Before the new site replaces an existing website or domain, record the current URLs, useful landing pages, and important links you need to preserve. Agree which pages will keep their addresses, which will be replaced, and how any changed address will direct visitors to the closest useful destination. Include a staging review, a named launch owner, and a rollback plan.
For a project that moves or rebuilds an existing live site, use our dedicated URL migration and post-launch search checklist for the detailed redirect and verification steps.
8. Separate the build from ongoing work
A website proposal should distinguish the initial build from hosting, domain renewals, licences, maintenance, content updates, and future marketing. Ask what is included in revisions, what makes a request additional work, and how changes affect delivery dates.
Agree who owns backups, software updates, compatibility checks, and incident support after launch. WordPress documentation recommends a backup before updates; see updating WordPress. The maintenance arrangement should be specific to your site rather than assumed to be included forever. Use our WordPress maintenance plan comparison guide to check recovery evidence, update responsibilities, support limits, and recurring costs before agreeing ongoing care.
Launch acceptance checklist: what to ask to see
Turn the brief into a sign-off record before the build begins. For each check below, record the person responsible, the page or feature tested, the evidence, and a status: passed, needs a fix, or outside the agreed scope. Recheck fixes before marking them complete.
- Pages and navigation: compare the finished site with the approved page list. Open the main menu, service links, footer links, and calls to action. Record missing pages or incorrect destinations.
- Mobile reading and interaction: try a real phone as well as the desktop view. Read long headings, open the menu, and complete the agreed form checks. Look for clipped text, sideways scrolling, and effects that hide content or block a button.
- Editing demonstration: ask the developer to show how your team changes a heading, replaces an image, edits a service card, and updates a shared header or footer. Use a draft or test page for the demonstration and confirm which changes affect every page.
- Enquiry delivery: agree an authorised test with a recognisable reference. Check the submission record, visitor confirmation, and arrival in the intended inbox, including the spam folder. Record delivery separately from the success message; a WhatsApp link opening correctly is also a separate check.
- Redesign URLs: use the agreed old-to-new URL list to check changed addresses and their final destinations. Review the intended public pages and search settings. A page being open to search engines does not confirm that Google has indexed it.
- Measurement: identify which actions are measured and which represent a confirmed enquiry. Check that a button click or form start is not reported as a completed lead. Keep names, email addresses, phone numbers, and message text out of analytics event data.
- Handover and recovery: confirm account access, renewal dates, maintenance responsibilities, and where backups are kept. Ask who can restore the site and how that process has been checked safely. Keep an agreed list of unresolved items and the person handling each one.
A launch date should account for these checks and any essential fixes. Keep optional enhancements in a separate list so both sides can see what is ready and what still needs a decision.
A brief you can send to a development partner
- Business and offer: what you sell and who needs it.
- Main action: what a suitable visitor should do.
- Pages and features: the agreed inventory and essential integrations.
- Content: available copy, images, and approved evidence.
- Current site: URLs and functionality that must be preserved.
- Accounts: ownership, permissions, licences, and renewal responsibility.
- Review and launch: approver, acceptance checks, handover, and support scope.
For a new hosting setup or a move, read our domain and hosting guide to clarify ownership, renewals, email, backups, and migration responsibilities.
Start with a scope your business can use
You do not need every possible feature at launch. Prioritise a clear offer, useful pages, a working enquiry route, and a manageable handover. Add complexity when it solves an identified customer or operational need.
Explore Zevon’s WordPress web design and development service, or send a project enquiry with your current website, required pages, main goal, and any essential integrations. Include your preferred launch date and budget range if known, and say whether copy and images are ready. This gives us a clearer starting point for discussing scope. If you are comparing providers, our agency selection guide helps you evaluate scope and communication.

