A rebuild is ready to work when buyers can reach the right pages, understand the offer and get an enquiry to the right person. The next job is to check that delivery, then use what happens on the live site to choose the next improvement.
Use 30, 60 and 90 days as review checkpoints. At each one, make a decision about the work. Search positions, enquiries and sales do not improve on a fixed calendar.
If you are still choosing the project, see what our website rebuild includes. This guide starts at launch.
At launch: confirm that the website works for the business
Record the actual go-live date and the pages, URLs and contact routes that changed. Keep the earlier search figures and enquiry records so later comparisons have a starting point.
Keep the rebuild preservation and launch record alongside these reviews so the original decisions and unfinished checks remain visible.
The team responsible for launch should check these immediately:
- Important pages load and are accessible. The approved site is on the public domain, with the intended content and no leftover development-only indexing block.
- Old links still lead somewhere useful. Where an address changed, check the redirect reaches the relevant replacement. Test important downloads and internal links too.
- Enquiries reach the intended person. Submit an agreed test, confirm receipt and check that someone owns the follow-up. A success message on the screen is only part of that check.
- The business can access its accounts. Confirm control of the domain and access to analytics and Search Console. Record who handles hosting and website changes.
- The next action is visible. Keep an issue list with the affected page, what happened, who is handling it and the next step.
For a move with changed URLs, Google’s migration guidance covers URL mapping, redirects, updated links and post-launch monitoring. These checks manage the move; they do not hold every search position in place.
By day 30: close launch issues and check the enquiry route
The first review asks: can a suitable buyer use the website and reach us?
Review unresolved launch issues before adding more content. Check key service pages on a phone, follow a relevant path through the proof and contact route, and confirm that test enquiries reached the business. For a real enquiry, record what the person needed, whether it fitted your services and what happened next.
The person monitoring search should inspect important pages in Search Console, including unexpected exclusions and the destination of changed URLs. Submitting a sitemap or asking for a recrawl does not establish that a page is indexed. Google says recrawling can take days to weeks.
Keep these observations separate:
| What you check | What it tells you |
|---|---|
| A test enquiry arrives | The tested route delivered to the recipient |
| A form action appears in analytics | The configured action was recorded |
| A suitable buyer gets in touch | An enquiry matches your service and market |
| A sale progresses or closes | The business has a commercial outcome to record |
Google Analytics can record form interactions and verify key events. Reconcile those records with received enquiries. Tests, repeat actions and spam can otherwise make activity look more valuable than it is.
Leave this review with: a checked enquiry route, named owners for remaining issues and the next review date. If something is broken, act now.
Around day 60: examine whether the attention fits the business
The second review asks: are we seeing the services and buyers we want?
Look at the searches and landing pages together. Separate people searching for your name from people searching for the work you do. Check whether a relevant search reaches a page that explains the corresponding service, its proof and how to enquire.
Then compare those observations with actual conversations. A clearer service page might still need a better explanation of scope. The right enquiry might still go unanswered. A rise in traffic from an unrelated topic does not settle either problem.
Use complete periods of equal length, the same search type and the same market filters. Follow a moved page across its old and new addresses. Note other changes, such as advertising, seasonal demand or a different tracking setup, that affect the comparison. Search Console’s query rows are incomplete, so use its metrics with their limits in mind.
Where our 42-day reading fits
In our ongoing plan, we allow 14 days after a batch goes live, then compare the following 28 days with the 28 days before the batch. That is a measurement schedule. It does not establish that Google has finished processing a change or that the change caused everything in the figures.
A reading may fall between these owner reviews. If there is little activity, record what remains unclear and choose a later comparison rather than forcing a conclusion. For the wider distinction between delivery dates and outcomes, see the AI visibility timeline guide.
The visibility and enquiry scorecard gives you a simple record for that reading, with received enquiries and fit kept separate from search activity.
Leave this review with: one supported priority, the evidence behind it and the person responsible for the next action.
Around day 90: choose the next investment
The third review asks: what deserves more work, and why?
Review what shipped, what the site and search records show, and what happened to suitable enquiries. Each answers a different part of the decision.
| What the evidence shows | A useful next move |
|---|---|
| A service page attracts relevant visitors, but its scope is still unclear | Improve that page using the questions buyers actually ask |
| A distinct buying question has no useful answer | Assess whether it needs supporting content and a route to the relevant service |
| Existing pages overlap and leave the buyer repeating the same journey | Clarify their jobs or combine them where appropriate |
| Useful enquiries arrive, but replies or qualification stall | Fix the follow-up process with the person handling sales |
| Important pages remain inaccessible or changed URLs fail | Resolve the technical issue before expanding the site |
| There is too little relevant activity to decide | Recheck measurement and market fit, then agree a further review |
Use more content or better pages when choosing the content work. If the wider issue is traffic without useful enquiries, trace the enquiry problem.
Choose the next batch because it addresses a visible need. Reaching day 90 is not, by itself, a reason to buy a larger package.
Agree who handles each part after launch
A useful handover makes responsibility easy to find. The business names the person who receives and follows up enquiries. The website team handles the agreed implementation and launch checks. The proposal identifies who monitors performance and who approves further changes.
For our separately quoted build:
- Included support: 30 days after launch, with small text and image changes free during that period.
- Later changes: through the plan or per request. Additional functionality and work outside the agreed scope are quoted separately.
- Ownership: the domain, analytics and Search Console are in your name; the site is yours after final payment, with code handover on request.
- Hosting and editing: hosting is included for the first 12 months and while on the plan. The call confirms the later yearly fee. Self-hosting is available with handover; a self-edit setup is a scoped extra.
- Ongoing improvement: optional after the separately quoted build. If chosen, the proposal records its work and terms; it is not an automatic extension of launch support.
The rebuild service page sets out the full project terms. If you already work with another team, use these questions to clarify your own agreement rather than assuming the same support applies.