We want a new website with better SEO and online payments: what does the schedule of work look like, and what should we ask for before agreeing a quote?
When a rebuild includes search visibility and taking payments online, the schedule matters as much as the price, because both depend on decisions and tasks that sit with you as well as the supplier. Here's how a project like this usually runs from discovery to launch, an illustrative schedule you can adapt, the questions to ask before you sign, and when a smaller scope would do the job.
An owner of a small, well-established local business gets in touch. Their website is several years old, it rarely shows up when people search for what they do, and customers keep asking whether they can pay online rather than by bank transfer. They want a full rebuild with better SEO and online payments. Before they agree to anything, they ask two sensible questions: what will it cost, and what does the schedule of work actually look like?
The cost question usually gets most of the attention. The schedule question is just as important, and it's often answered with a single line such as "eight to twelve weeks". That figure tells you very little on its own. A rebuild that includes search and payments has more moving parts than a simple brochure site, and several of them depend on you, your content and third parties such as your payment provider.
This article walks through what happens between "yes, let's talk" and launch day, gives you an illustrative schedule to adapt, and lists what to ask for before you agree a quote. If you're still deciding whether you need a rebuild at all, start with our guide to whether a refresh is enough or you need a rebuild. If you already have quotes in hand and they look very different, our guide to comparing website quotes covers that side of things.
Why SEO and payments change the shape of a project
A straightforward site rebuild mostly runs in a line: plan, design, write, build, launch. Adding search visibility and online payments brings in work that has to happen at particular points, and some of it can't be rushed.
SEO work starts before design, not after launch. The pages you need, what each one is called and how they link together should come from what people actually search for and what you actually do. If that's decided after the design is signed off, you can end up squeezing new pages into a layout that wasn't built for them. Our guide to whether you need separate pages for each service and area shows why structure decisions matter so much here.
Replacing an existing site means protecting what already works. If your old pages get any search traffic or links, they need to be mapped to their new equivalents and redirected. Google's guidance on moving a site with URL changes recommends server-side permanent redirects, keeping them in place for at least a year, and expecting search visibility to fluctuate temporarily while Google recrawls the site. Google says a small to medium-sized site can take a few weeks for most pages to move. That's worth knowing before you plan a launch around your busiest month.
Payments bring in decisions and accounts that sit outside the website. You'll need to choose a payment provider, set up an account in your business's name, and decide what people can pay for, when, and on what terms. Card payments are best handled on the provider's own secure payment page or component, so card details don't pass through or sit on your website. The PCI Security Standards Council sets the security standard for anywhere card data is stored, processed or transmitted, and keeping card data off your own systems usually keeps that much simpler. Payment providers typically ask for business and identity details before they let you take live payments, so this isn't something to leave until launch week.
Terms and policies need writing. Refunds, cancellations, deposits and delivery or service dates all need to be clear before anyone pays. Our guide to whether your website should take bookings and deposits online covers the questions to settle first. It's general guidance, not legal advice, so it's worth taking advice on your terms.
The phases, from discovery to launch
Most projects of this kind move through six phases. Names vary between suppliers, but the work inside them should be recognisable in any decent proposal.
1. Discovery and scope
The aim is to agree what's being built and why, before the larger spend. That normally covers who the site is for, what you want people to do, which services and areas matter most, what should be paid for online and what shouldn't, and what connects to what. It should end with a written scope you can check line by line.
Your part: honest answers about how the business works now, access to your current site, analytics and Search Console if you have them, and a decision-maker who can sign off the scope.
2. Search and structure planning
This is where the page list, page names, menu structure and the map of old addresses to new ones are agreed. It's also when you decide which pages matter most for search, so content effort goes where it counts.
Your part: confirming the services and areas you genuinely want more work in, and flagging any old pages customers still use or link to.
3. Payments and policies
Deciding what people can pay for (a full payment, a deposit or an invoice), choosing the payment provider, opening the account, and drafting refund, cancellation and payment terms. This often runs alongside design rather than after it.
Your part: opening the payment provider account in the business's name, supplying whatever verification it asks for, and getting your terms reviewed.
4. Content and design
Key page designs are agreed, and the words and images are written, edited or supplied. This is often the phase most likely to slip, usually because content takes longer to gather and approve than anyone expected.
Your part: content or feedback by agreed dates, and a single person to collect comments so the designer isn't juggling contradictory feedback.
5. Build and testing
The site is built, forms and payment flows are connected in the provider's test mode, redirects are set up, and the site is checked on phones and computers. Testing should include a complete payment from start to finish, a refund, and a failed payment, so you can see what customers and your team will actually experience.
Your part: testing the site as a customer would, and checking that confirmation emails, receipts and notifications land with the right people.
6. Launch and settling in
The site goes live, redirects are switched on, live payments are enabled, and search performance is watched in the weeks that follow. Logins and documentation are handed over. Our website handover checklist covers what you should hold at the end.
Your part: being available on launch day, and keeping an eye on enquiries and payments for the first few weeks.
An illustrative schedule you can adapt
This is a hypothetical example to show how the phases fit together. It isn't a quote, a promise or a typical timescale for any particular business. Your project's real schedule depends on its scope, your content and how quickly decisions are made.
Phase Illustrative timing Main decision or sign-off Who usually holds it up if it slips Discovery and scope Weeks 1–2 Written scope agreed Decision-maker availability Search and structure planning Weeks 2–3 Page list and redirect map agreed Late changes to services or areas Payments and policies Weeks 3–6 (alongside design) Provider chosen, account approved, terms drafted Account verification, terms review Content and design Weeks 3–7 Key page designs and final copy approved Content supply and feedback rounds Build and testing Weeks 7–10 Test payments and redirects passed Late content, unresolved test issues Launch and settling in Week 10 onwards Go-live, then review after launch Launch timed for a busy periodTwo things to notice. First, payments and content run in parallel, so a delay in either can hold up the build. Second, launch isn't the end of the SEO work. Search visibility can wobble while Google catches up, so it helps to plan a review a few weeks after go-live rather than judging the result on day one.
What to ask for before you agree a quote
You don't need to be technical to ask these. Ask each supplier the same questions and compare how clearly they answer.
About the schedule
- Can you show us the phases, with a sign-off point at the end of each?
- Which tasks are ours, and by what date do you need them?
- What happens to the launch date, and to the price, if our content or feedback is late?
- When will we see designs for key pages, and how many rounds of changes are included?
- Is there a planned check on search performance and payments after launch?
About SEO
- How will you decide the page structure and page names, and will we see it before design starts?
- Will you map every old page with search traffic or links to a new address and set up permanent redirects?
- Will Search Console and analytics be set up in our name, with us as owner?
- What do you consider "SEO" in this quote, and what's outside it? Ongoing content or link building, for example, is a different job from getting the foundations right.
About payments
- Which payment provider do you recommend, why, and will the account be in our business's name?
- Will card details be taken on the provider's secure page or component, rather than on our website?
- How will you test payments, refunds and failed payments before launch?
- Who writes the refund and cancellation terms, and where will they appear before someone pays?
- What fees should we expect from the payment provider? (The supplier won't set these, but they should tell you where to find them.)
If a supplier can't answer the schedule questions, that doesn't necessarily mean they're a poor choice. It does mean you should ask for a written plan before you commit.
When a smaller scope would be enough
Not every business that wants better SEO and online payments needs a full rebuild, and it's worth checking before you commit to one. A smaller scope may well be the better choice if:
- The site is sound but thin on content. If the structure and platform are fine, improving key service pages, titles and descriptions may help search more than a new site would.
- You only need to take occasional payments. A payment link sent by email, or a hosted payment page from your provider linked from your site, can let customers pay online without building payments into the website.
- Your current platform already supports payments. Many website platforms offer payments as an add-on. Turning that on and writing clear terms may be enough.
- Search visibility is mainly a local listing problem. If people mostly find businesses like yours on maps, your Google Business Profile and reviews may deserve attention first. Our guide to working out where enquiries come from can help you see which channels actually matter.
- You want to test demand before investing. Starting with a payment link or an off-the-shelf tool for one product or service shows whether customers actually use it.
A full rebuild with search planning and integrated payments makes more sense when the structure no longer reflects the business, the platform is hard to edit or can't support payments properly, and online payment is becoming a core part of how customers buy from you rather than an occasional extra.
A quick self-check before you ask for quotes
Answer these in a page of notes, then send the same notes to every supplier. It makes quotes easier to compare and schedules more realistic.
- What do we want people to do on the site, in order of importance?
- Which services and areas do we most want to be found for?
- Do we have access to our domain, hosting, analytics and Search Console?
- What exactly should customers be able to pay for online: full price, deposits or invoices?
- Do we already have a payment provider, and is the account in the business's name?
- Do we have written refund and cancellation terms, or do they need writing?
- Who will write or approve the content, and how much time can they give it?
- Are there months when a launch would be risky because we're busy?
- Who is the one person who can sign off each phase?
A worked example (hypothetical)
This is a hypothetical example to illustrate the approach. It isn't based on a real business or client.
Imagine a long-established picture framing workshop in a Somerset market town. Its website is around eight years old, built on a platform nobody in the business can edit easily. Customers often ask to pay for collected framing online, and the owner wants to sell gift vouchers. Search visibility is poor beyond the business name.
Working through the self-check, the owner realises three things. The page structure doesn't mention the services customers actually search for, such as conservation framing or framing sports shirts. The business doesn't have a payment provider account yet. And autumn is the run-up to their busiest season, so launching in late November would be risky.
A sensible plan might be to agree the scope and page structure first, open the payment provider account early so verification doesn't hold things up, write the voucher and refund terms alongside the design work, and aim to launch in a quieter month with a review a few weeks later. If the owner had found that the platform was fine and only the service pages were weak, rewriting those pages and adding a payment link for vouchers might have been the better first step.
Your next step
Westward Digital builds websites and connected lead systems for established businesses across Somerset, Devon, Dorset, Bristol and Bath & North East Somerset. Marcus plans the work directly, and business websites start from £4,500. Before a larger build, our fixed-fee Digital Discovery (£1,750, credited against the project if you go ahead within 60 days) sets out the scope, phases and priorities in writing. If you'd like a straight view on what your project needs and how long it's likely to take, get in touch for a no-pressure conversation.
Working through something similar?
We can help you work out what to address first.