Website engineering
A B2B website redesign must preserve the enquiry journey
Methodology: Original engineering guidance from StackEndBox, informed by our own public-site release checks and Google's migration documentation. The examples are illustrative. They are not a client case study or measured traffic improvement.
A B2B website redesign changes the route between a buyer's question and a useful conversation. Approve that route before approving the visual replacement. Identify which pages attract the right visitors, which evidence helps them choose and what happens after an enquiry is accepted. A new page returning HTTP 200 proves availability, not search indexing, inbox delivery or a qualified lead.
Decide what must survive
Inventory the live URLs using a crawl, the existing sitemap and permitted Search Console data. Include important pages reached through external links even if the current menu omits them. Record page purpose, canonical URL, search queries where available, internal links and the next buyer action. Keep useful material at the same address when its intent remains the same. A redesign is not a reason to change every slug.
| Existing page | Decision | Verification |
|---|---|---|
| A useful service page with the same offer | Retain the URL and improve the content in place. | HTTPS 200, self-canonical, crawlable links and a relevant enquiry path. |
| Two pages that genuinely answer the same buyer task | Review consolidation and choose the closest useful destination. | Test the old address and update internal links. Do not send every retired page to the homepage. |
| An old service no longer offered | Decide whether there is a real replacement or the page should be removed. | Use an appropriate response. A misleading redirect is not a substitute for relevant content. |
| A labelled noindex download | Keep its intended discovery policy separate from public articles. | Verify its headers and exclude it from the indexable sitemap. |
| A contact form posting to a separate application | Preserve the complete submission and reply journey. | Verify saved receipt, notification, acknowledgement and owner access separately. |
Change the fewest independent things at once
Google's site-move guidance recommends separating major changes where possible. A simultaneous domain move, CMS replacement, new URL structure and rewritten content makes failures harder to attribute. A visual redesign that retains URLs differs from a site move. Agree the actual change and the observation period before launch.
Test an enquiry as several outcomes
Send a clearly labelled test through the actual preview or live route with permission. A success message should correspond to accepted input and a durable receipt where the system supports it. Separately check that the notification reaches the intended mailbox and folder, that Reply-To reaches the enquirer and that the owner can find the saved record. Do not put the enquiry body or personal details into public analytics or routine application logs.
Our own public-site QA found why these boundaries matter: a labelled test could arrive in the business mailbox's Spam folder. Arrival and reliable inbox placement are different results. This observation does not establish a defect in every customer's email or a completed deliverability repair. It is a reason to inspect the actual sending path and authentication rather than infer success from an application response.
A booking click is not a meeting
A scheduling link can carry a public service campaign category without including a visitor's name, email or message. That records the intended source, not a completed booking. Confirmed bookings need supported scheduling evidence and deduplication. Keep cancelled meetings, test bookings and qualified commercial meetings distinct. Do not claim attribution works end to end simply because a UTM parameter appears in the link.
Use a release contract with visible stop conditions
| Boundary | Evidence | Stop when |
|---|---|---|
| Content and intent | Priority services explain audience, scope, exclusions, deliverables and a next step. | Claims lack permission or evidence, or a critical offer disappeared. |
| Mobile and accessibility | Actual small-screen rendering, keyboard navigation, form labels and errors. | A buyer cannot navigate, read or correct an enquiry. |
| URL and crawl | Old-to-new map, response checks, canonical and robots rules, relevant internal links. | Important URLs break, redirect incorrectly or become noindex unexpectedly. |
| Conversion | Labelled test receipts and separately verified notification and booking outcomes. | The form silently loses an enquiry or the owner cannot recover it. |
| Release recovery | Versioned source, previous deployable artifact and a named rollback operator. | The previous release cannot be restored or an unrelated application is included. |
Follow publication with search discovery
Update the eligible sitemap with accurate last-modified dates for meaningful changes. Verify that it parses and check its Search Console submission status. Inspect important new or substantially changed public URLs and request indexing where appropriate within Google's quotas. Record published, submitted, crawled and indexed separately. A URL Inspection API result is a status observation. Google's restricted Indexing API is not a general submission tool for service pages and blogs.
Search Console may report no data for a new page, and reporting can lag. Monitor relevant queries and target countries over time. Preserve the pre-launch baseline, annotate the release and avoid crediting a design change with improved rankings or enquiries before there is evidence. For a low-traffic site, repairs and buyer interviews may be more useful initially than an underpowered A/B test.
Prepare a brief a development team can price
- List the priority service, target buyer and useful current URLs.
- State what changes in design, CMS, domain and URL structure, and what stays.
- Name the person approving content and the person handling enquiries.
- Provide public project evidence you have permission to use, without sending credentials.
- Agree launch checks, rollback responsibility, editing access and post-launch support.
Use website redesign and development to discuss the implementation boundary. Use SEO, CRO and growth services for search and acquisition work around the website. The agency, freelancer or in-house comparison can help you choose an operating model before commissioning work.