Every agency SOW has a line for the technical audit. It arrives as a spreadsheet with a health score, several thousand warnings and a colour-coded priority column. Six months later the score has moved a few points, the warnings count is lower, and nobody can say whether pipeline moved at all.
The problem is not the audit. It is the sort order. Technical SEO issues are usually ranked by how many pages they affect, when they should be ranked by how much revenue sits on the pages they affect. Fix that and the list gets short, specific and worth doing.
Start with the pages that carry revenue
Before you open a crawler, write down your money pages. For most B2B sites that is a short list:
- Pricing
- Demo, contact or trial sign-up
- Core product or service pages
- The landing pages that paid and organic traffic actually convert on
- Comparison and alternatives pages, if you have them
Confirm the list in your analytics. The pages that sit on the path to a conversion are the ones where a technical fault costs you money. A broken canonical on a tag archive costs you very little. The same fault on your pricing page costs you every buyer who searches for your pricing.
The fixes that tend to matter
1. Can the money pages be found and indexed at all?
This is the only category where one mistake can take a page to zero. Check each money page for a stray noindex, a canonical tag pointing somewhere else, a robots.txt rule blocking it, or a redirect chain that ends somewhere unexpected. Then check Search Console's page indexing report for those exact URLs. Site migrations and CMS template changes are the usual culprits, and they often go unnoticed for months because nothing visibly breaks.
2. Do your own pages point at them?
Internal links tell search engines which pages you consider important. Many sites bury pricing and product pages behind a single nav link while blog posts link to each other endlessly. Look for broken internal links and redirected internal links that point at money pages, then add plain, descriptive links to them from the content that ranks.
3. Are the money pages fast enough on a phone?
Google publishes the Core Web Vitals thresholds, and they are a sensible bar. Largest contentful paint at or under 2.5 seconds, interaction to next paint at or under 200 milliseconds, cumulative layout shift at or under 0.1. Measure these on the money pages specifically, on mobile. A slow blog is a nuisance. A slow pricing page, or a demo form that jumps around while it loads, loses buyers who were ready to act.
4. Do the titles and descriptions earn the click?
Pages that rank but get few clicks are the cheapest win in SEO. In Search Console, filter to your money pages and look for high impressions with low click-through. Often the title is the company name and a vague tagline. Rewrite it to say what the page offers and who it is for, in the words buyers search with.
5. Does the content exist without the script?
If the page's main text, prices or form only appear after heavy client-side rendering, crawlers may see less than your visitors do. View the rendered HTML with a URL inspection tool and confirm the words that matter are there.
6. Is structured data valid where it applies?
Structured data will not rescue a weak page, but invalid markup on product, FAQ or organisation pages is a cheap fix. Validate it and remove anything that describes content not actually on the page.
What to leave on the list
Plenty of audit findings are real but not worth your sprint: missing alt text on decorative images in old posts, duplicate meta descriptions on paginated archives, minor heading order issues on pages nobody visits. Log them, batch them for a quiet week, and do not let them crowd out the fixes above. The health score will look worse for a while. Pipeline will not care.
Prove each fix against its own before-state
For every fix, record the page, the change, the date and the baseline: impressions, clicks, CTR and average position from Search Console, plus conversions from analytics. Re-check after the page has been re-crawled. This is the difference between "we fixed 140 issues" and "we fixed the canonical on pricing and pricing clicks recovered". Only the second one belongs in a board update.
A simple scoring rule keeps the queue honest: page value times severity, divided by effort. Page value comes from your money-page list. Severity asks whether the fault blocks indexing, loses clicks or loses conversions. Effort is hours, including review. Work top down.
How the Website Crew runs this
The Website Crew re-audits your site every month for performance, SEO and conversion drift. The audit engine behind it runs 13 SEO checks and measures Core Web Vitals against Google's published thresholds. The output is a technical audit plus a list of website fixes, each with a type, target URL, title, rationale, the evidence behind it and a risk rating. The Search Crew adds search-side fixes from Search Console data to the same list.
Low-risk fixes, like a corrected canonical or a rewritten title, can ship automatically inside guardrails you set. Risky or visual changes are staged for your review. Merging code and publishing to your CMS wait for your approval, and so does anything that looks like a redesign. How far automatic fixes can go depends on crawl coverage, which site surfaces are editable, and how confident the crew is that a patch is low risk.
The crew is measured on resolved issues, Core Web Vitals movement, organic visibility and verified outcomes on the changes it made, not on a health score. Connect Google Analytics 4 and Search Console from the integrations page so those outcomes rest on your real data.
Start with one page
Open Search Console, inspect your pricing page URL, and check that it is indexed with the canonical you expect. Then run it through a Core Web Vitals test on mobile. If either result surprises you, you have found this month's most valuable technical SEO work.
Want the full list, sorted by what it costs you? Run the free audit and the crew will show you where to start.