Coordinating a Rebuild, Ads and SEO on One Timeline
A clinic was about to relaunch its website, restart Google Ads and begin a new SEO programme, all in the same few months. Each piece was sensible. But done without coordination, they could easily clash: ads sending people to pages that were about to change, SEO work on a site that was about to be rebuilt, and a launch with no way to tell what had worked.
Coordinating a rebuild, ads and SEO on one timeline avoids wasted effort and confusion. Here is how.
Why coordination matters
A website rebuild changes pages and addresses. Ads send visitors to those pages. SEO builds on them. If the three are planned separately, work can be wasted, tracking can break and results become impossible to interpret. A single timeline keeps everyone aligned and protects the budget.
Start with one shared goal
Agree a single main goal for the period, such as increasing enquiries for two key services. Write it down and share it with everyone involved: the clinic, the web team, the ads manager and the SEO specialist. A shared goal prevents each group from optimising for its own measure.
Map the dependencies
List what depends on what. Ads need landing pages. SEO needs a stable site. Tracking needs the final pages. The launch needs content. Draw a simple chart showing the order. Seeing dependencies clearly stops teams from starting work that cannot yet be completed.
Rebuild, ads and SEO: decide the order
A common sequence is: fix tracking and essentials, rebuild the key pages, launch, then expand ads and SEO on the stable site. Sometimes, ads need to run earlier to protect enquiries. If so, send them to the most stable pages, and plan to move them cleanly after launch.
Freeze changes at critical points
Agree periods when certain things do not change, for example no major edits to landing pages during an ad test, or a content freeze before launch. Freezes make results readable, and reduce the risk of one team undoing another’s work.
Keep ads running sensibly through the rebuild
If ads run during a rebuild, check that landing pages still work, and that tracking is intact. If an address will change, plan a redirect. Consider a small budget during the change, then increase once the new pages are live and tested.
Do SEO work in the right sequence
Some SEO work, such as technical fixes and redirect planning, belongs before launch. Content improvements should be built into the rebuild. Link building and expansion follow on a stable site. Working in sequence avoids doing things twice.
Make one person the coordinator
Choose one person to keep the plan, chase dependencies and record decisions. They need not do the work, but they must see the whole picture. A named coordinator prevents things falling between teams, and speeds up decisions.
Set up tracking early
Before any launch, make sure calls, forms and bookings are tracked, and that you can tell the source of each. Test it. Changing tracking mid-project makes comparisons impossible. Good tracking lets you see what each element contributes.
Plan the launch week carefully
Choose a launch date that suits everyone, with the team available and no clashing campaigns. Agree who checks what: redirects, forms, ads, tracking, indexing. Have a plan to reverse if something goes badly wrong. A calm launch is better than a fast one.
Communicate weekly
Hold a short weekly check-in, covering progress, blockers and decisions. Keep a shared record. Regular contact keeps everyone informed, and brings problems to light early. It also helps the clinic understand what is happening.
Review together after launch
A few weeks after launch, review results across the site, ads and search together. Compare with your goal and baseline. Note what worked, what did not and what to do next. A joint review turns the project into learning for the next one.
Prepare a communication plan for launch
Decide who tells staff, referrers and patients about the new site, and when. Prepare a short explanation of what has changed. A clear message prevents confusion if a phone number, address or booking route changes, and helps everyone support the transition.
Keep a single source of truth
Store the plan, dates, decisions and login details in one shared place. When several teams work at once, scattered information causes delays and mistakes. A single, tidy record keeps everyone aligned, and makes handovers simple.
Agree what success looks like together
Before starting, agree what you will treat as success for each workstream and for the whole. For example, a working site, a stable ad account and rising impressions. Shared definitions prevent disputes later about whether the project worked.
Plan for the things that will slip
Every project has delays. Build some slack into the timeline, and decide in advance which piece can move without harming the rest. A plan with flexibility survives the first setback, whereas a tight plan collapses and forces rushed, risky decisions close to launch.
A quick checklist
- Agree one shared goal.
- Map dependencies between the three workstreams.
- Decide the order and freeze points.
- Name a single coordinator.
- Set up tracking before launch.
- Review results together afterwards.
Our companion article on rebuilding after a ranking collapse covers the recovery context, and our guide to website launch timing explains the date decision. If you would like help, we are glad at Pulse Digital Health to talk.
Frequently asked questions
Why coordinate a rebuild, ads and SEO?
Because they depend on each other. Ads need landing pages, SEO needs a stable site and tracking needs the final pages. Planning them separately wastes effort and makes results hard to read. Write down who owns each task and when it is due. Shared goals stop each team optimising for its own measure at the expense of the whole.
What order should they happen in?
Commonly: fix tracking and essentials, rebuild key pages, launch, then expand ads and SEO on the stable site. Sometimes ads run earlier to protect enquiries, pointing at the most stable pages. Agree the order at the start, and revisit it if dates move. Seeing dependencies on paper prevents teams starting work that cannot yet be finished.
Should ads run during a rebuild?
They can, with care. Check landing pages and tracking still work, plan redirects for changed addresses and consider a smaller budget until the new pages are live and tested. Keep landing pages stable during ad tests and after launch. Stable pages during a test make the results readable.
Who should coordinate the work?
One named person who sees the whole picture, keeps the plan, chases dependencies and records decisions. They need not do the work themselves. Give the coordinator authority to chase and to decide small matters. A single coordinator saves more time than any extra meeting.
What is a change freeze?
An agreed period when certain things do not change, such as landing pages during an ad test or content before launch. It keeps results readable and prevents teams undoing each other’s work. Agree which changes are frozen and for how long. Agreed freezes protect one team’s work from another team’s edits.
How should we review afterwards?
A few weeks after launch, compare results for the site, ads and search together against your goal and baseline, and record what worked and what to do next. Record what you learned so the next project is smoother. A joint review turns a project into learning for the next one.
