The most expensive mistake in a B2B website project is starting with the wrong question. The right one: what is your current site already telling you?
The data is already there. Analytics, Search Console, form completions, session paths. Before any redesign brief is written or any developer is briefed, that data deserves a proper read.
Here's what to look at, and why it changes how you approach the project.
Your team's assumptions about the site are usually wrong
When I start a website project with a client, I ask the marketing and sales team to nominate the three pages they think get the most traffic. Then I pull the actual data.
The overlap is rarely what people expect.
Someone will nominate the homepage and the main services page. Fair enough. But the third pick varies wildly, and it's almost always wrong. I've had clients assume a comparison page was buried and irrelevant, only to find it was pulling significant organic traffic and converting at a higher rate than the homepage.
Internal assumptions about a website are formed from the inside out: what content the team is proud of, what the CEO mentions in pitches. Buyers don't care about any of that. They follow different paths.
Traffic data shows you what buyers actually value
Pull 12 months of page-level traffic from Google Analytics and sort by sessions. Then pull your top queries from Search Console and match them to landing pages.
Look for:
- Which pages sit consistently in your top 10, regardless of how much effort went into them?
- Which pages are pulling organic traffic you didn't plan for?
- Which pages have high traffic but almost no conversions or next clicks?
- Where do sessions end, and which pages are the last stop before someone leaves?
The answers are usually surprising. I've had a client discover their team page was one of the most visited pages on their site. Another found a lead generation landing page from a campaign two years earlier was still driving a third of their enquiries, completely unmonitored.
Knowing this before you rebuild changes your brief. That team page probably needs a stronger CTA. That legacy landing page needs to be deliberately carried across and improved when the new site launches.
Search Console shows you what's quietly working
Most B2B businesses underestimate how much organic traffic their current site pulls. They assume it's low because they haven't invested in SEO. But websites accumulate ranking signals over time, even without active management.
Google Search Console shows the queries your site ranks for, which pages they land on, and roughly where you sit in the results. An hour here before a redesign often reveals content earning its keep even when nobody's actively managing it.
The risk in any rebuild is breaking what's working. Pages get redirected incorrectly, URL structures change without proper redirect maps, internal linking gets stripped out - and pages that have been ranking for months lose their position because Google treats the new URLs as starting from scratch. A site ranking for 30 or 40 niche queries can lose half its organic traffic in the first month after launch. The design gets praised. The traffic is already gone.
A B2B SEO audit before a rebuild protects against this. It maps what's working, flags the content worth preserving, and gives your developer clear requirements before a line of new code is written.
Drop-off points tell you why people leave
Traffic data tells you where people go. Behaviour data tells you why they leave.
Look at bounce rates by page and, if you have session recordings, watch a handful on your highest-traffic pages. You'll see patterns quickly: visitors landing on a services page and bouncing immediately, usually because the content above the fold doesn't confirm they're in the right place. Or people scrolling to a contact form and not submitting because it has too many fields.
This is the problem a colour palette change won't fix. If visitors are leaving because your messaging doesn't match what they searched for, a redesign without addressing that delivers the same broken experience with a $60k invoice attached.
What to pull before you brief anyone
Before you brief a developer or agency, gather these four things:
- Page-level traffic for the last 12 months, sorted by sessions.
- Top 50 organic queries from Google Search Console, with the landing pages they hit.
- Form completion rates and the page paths users take before converting.
- A full export of your current URL structure so redirects can be mapped before anything is decommissioned.
An hour with this data will tell you more about your website's actual performance than years of internal assumptions. It'll also make your brief sharper and your developer conversations more productive.
If you want help pulling this together before your next project, get in touch and we can work out where to start.
