techmarketing . agency
Investors using laptop screening before investing factory
Web Design 19 Nov 2025

Auditing a tech website before acquisition: an M&A guide

Buying a tech company means buying its website. Here's the pre-acquisition website audit we run for buyers in the B2B tech space.

When a private equity team or strategic buyer acquires a B2B tech company, the website is rarely top of the diligence list. It should be higher. Beyond the headline pipeline numbers, the website tells you whether the marketing function is healthy, whether the technical debt is creeping or compounding and whether a year of integration work is going to cost £20k or £200k.

We’ve run pre-acquisition website audits for buyers across MSPs, SaaS vendors and IT services groups. The findings reshape valuation more often than people expect. This is the framework we use and the warning signs that should get flagged in the data room.

What this audit is for

A pre-acquisition website audit isn’t an SEO audit, though it includes one. It’s an exercise in understanding three specific risks:

  • Operational risk: can the site be maintained, updated and migrated without significant rebuild?
  • Commercial risk: is the site producing the leads the seller claims, and will those leads continue under new ownership?
  • Integration risk: how much work is involved in folding this site into the buyer’s existing portfolio or rebranding it post-deal?

Each of those risks should land in the diligence report with a number and a recommendation, not a vague “looks fine”.

The technical foundation

The first pass is structural. We look at:

Hosting and platform

What CMS, what hosting, what’s the renewal cycle? Are credentials documented or sitting in one developer’s head? Are there licence fees (premium plugins, design tools, integrations) the seller hasn’t disclosed? Is the platform end-of-life or actively maintained?

We’ve seen acquisitions where a £15k a year mystery plugin licence emerged in week six. That’s a diligence failure, not a surprise.

Code quality and dependencies

For custom builds we review the codebase. For WordPress we check the plugin stack. For Webflow we check the publishing setup. Things that flag concern: more than 25 active WordPress plugins, plugins not updated for over 12 months, critical functionality (forms, payments, integrations) handled by a single point of failure or a theme nobody at the seller can name.

We covered platform durability in our case for hand-coded websites in 2026 and WordPress vs headless for B2B tech.

Performance and Core Web Vitals

Run Lighthouse and PageSpeed Insights on the homepage, top three service or product pages and the main blog landing. A site failing Core Web Vitals is a buyer’s problem post-acquisition. Failing on mobile is more concerning than failing on desktop, particularly for MSP and IT support sites where regional buyers often visit on phones.

We covered the broader checklist in page speed for tech sites. The diligence question is: how much remediation work would be required to bring this site up to standard?

The SEO position

This is where buyers get the most surprised, in both directions.

Organic traffic and rankings

Pull data from Search Console (request access during diligence), GA4, Ahrefs or Semrush. Check:

  • 12-month traffic trend. Is the site growing, flat or declining?
  • Is the traffic branded or non-branded? A site getting 80% of its traffic on branded search has a thinner SEO moat than one ranking for category terms.
  • Are top-ranking pages stable, or has there been recent volatility?
  • Has the site been hit by a Google update in the last two years? Pull a year’s worth of traffic and overlay it against confirmed update dates.

A site whose organic traffic is half what it was 18 months ago has either lost rankings or had Google update its algorithm against it. Both are recoverable, but they affect valuation.

A clean, growing backlink profile from relevant tech publications is worth real money. A profile dominated by directory submissions, link farms or paid placements is a liability. The latter can trigger manual actions that take six months to recover from.

Spend an hour with the top 200 referring domains. Categorise. If more than 20% are spammy, flag it.

Technical SEO health

Run the technical SEO audit checklist for tech. Note any of:

  • Indexation issues affecting more than 5% of pages.
  • Duplicate content across regional or campaign pages.
  • Broken hreflang on multi-region sites. We unpacked this in our multi-region tech websites playbook.
  • Missing or broken structured data.

These aren’t dealbreakers but they’re work the buyer will inherit.

The commercial picture

Traffic is interesting. Pipeline is what gets paid for.

Conversion analytics

Inspect GA4 and the CRM together. Verify:

  • The conversion events the seller is reporting are configured correctly.
  • The events match what’s actually being recorded in the CRM.
  • The “leads from web” number isn’t being inflated by internal traffic, partners or duplicates.

We’ve seen sellers report 200 web leads a month and discover, on inspection, that 150 were partner referrals, internal staff or chatbot tests. A site producing 50 real leads is still valuable. Misrepresenting it as 200 is a diligence problem.

Form and CTA architecture

Audit every form on the site. For each:

  • Where does the submission go (CRM, email, both)?
  • Who’s responsible for follow-up?
  • What’s the average response time?
  • What’s the conversion rate from submission to qualified opportunity?

Sites where leads land in a generic inbox and get followed up “when someone has time” are leaking real revenue. We’ve covered specific failure modes in why your “Get a quote” CTA is converting at 0.3% and why MSP websites fail to convert.

Tracking and attribution

If the seller can’t show you how leads are attributed back to channel, you’re buying a black box. Specifically check:

  • UTM parameters in use across paid, social and email.
  • GA4 setup, including conversion goals.
  • HubSpot, Pardot or Salesforce campaign tracking.
  • Server-side tagging if any. We covered this in conversion tracking for long cycles.

A site with broken attribution is harder to optimise post-acquisition. Budget accordingly.

Brand and content quality

The harder-to-quantify side of the audit, but it matters.

  • Is the content on-strategy or a graveyard of forgotten campaigns?
  • Are the case studies real, recent and credibly sourced?
  • Is the design current, or is it visibly five years old?
  • Does the site read in a coherent voice or as if 14 different people wrote it?

For acquirers planning to fold the brand into a parent group or rebrand entirely, content quality matters less. For acquirers planning to retain the brand, the content shapes the post-deal marketing budget.

Integration and migration risk

If the buyer plans to migrate, rebrand or consolidate, the audit needs a section on what that work will involve.

  • How portable is the content? CMS exports, structured content, image libraries.
  • How clean is the URL structure? Migrations punish messy URLs.
  • How many redirects already exist? A site with 800 redirects from previous migrations is fragile.
  • Is the analytics history exportable, or does it die with the platform?

We covered the migration mechanics in detail in our B2B website migration guide and SEO migration guide.

What the diligence report should contain

A useful pre-acquisition website report runs to roughly 15 to 25 pages: an executive summary with traffic-light status on operational, commercial and integration risk; a platform and hosting overview with renewal cost projection; SEO position with traffic, ranking and backlink summary; conversion architecture with verified lead numbers; a brand and content assessment; a migration or integration cost range; and a 90-day post-acquisition action plan.

The action plan is the bit buyers value most. It tells them what to fix in week one, what to defer and what to write off.

When to walk away

Most websites are flawed. That’s normal. We’ve recommended buyers proceed with sites that had genuine issues, because the issues were fixable and the underlying business was strong.

The cases where we’ve recommended walking away or repricing:

  • Manual penalty in Search Console that the seller didn’t disclose.
  • Pipeline numbers that fell apart on inspection by more than 50%.
  • Content theft or plagiarism on the site.
  • Infrastructure tied to a single contractor with no documentation.

Each of those reshapes valuation. None of them surface on a 15-minute walkthrough.

The takeaway

A pre-acquisition website audit is small relative to the cost of the deal and disproportionately useful. Done properly, it surfaces the post-deal cost of bringing the site up to standard and the operational risks that aren’t visible from the outside.

We’ve done this on a dozen tech sites this year. Get in touch if you’d value an outside perspective, or see how we approach diligence-grade audits on the web design service page.

Frequently asked questions

How long does a proper pre-acquisition website audit take?
Two to three weeks for a deal-grade audit on a typical B2B tech site. The technical pass (hosting, platform, code quality, performance, accessibility) takes a few days. The SEO position (traffic, rankings, backlinks, manual action checks) takes another few days with Search Console access. The commercial verification (lead numbers cross-referenced against the CRM, attribution checks, form architecture) is the slowest part because it depends on the seller granting access. Compressing the timeline below two weeks is where due diligence misses the issues that matter.
What red flags should kill a deal or trigger a price renegotiation?
Four findings have made us recommend walking away or repricing. A manual penalty in Search Console the seller didn't disclose. Pipeline numbers that fall apart on inspection by more than 50 per cent (typically because partner referrals or internal traffic were counted as web leads). Content theft or plagiarism on the site. Infrastructure tied to a single contractor with no documentation, where the platform credentials live in someone's head. Each of those reshapes valuation. None surface on a 15 minute walkthrough so the audit pays for itself many times over.
Should the buyer ask for Search Console access during diligence?
Yes, always. It's the most reliable source of organic traffic data, manual action history and indexation health. Sellers occasionally resist sharing it because it exposes things their headline numbers obscure. That resistance is itself a flag. We also pull Ahrefs or Semrush for backlink profile, GA4 for conversion data and the CRM for verified lead numbers. Triangulating across those four sources catches the most common diligence misses. Without Search Console you're trusting a marketing report instead of the underlying data.
Share

Want help putting this into practice?

We work with technology companies on exactly this kind of programme. Tell us about yours.