B2B Website SEO Audit Checklist: Start With Pipeline Pages

The short answer

List your pipeline pages, then run six groups of checks on each one: indexing, titles and snippets, content, internal links, page experience, and structured data. The checklist below gives about 30 checks, each with where to look and what a pass looks like, all based on Google's own documentation. Fix anything that stops a pipeline page being indexed first; it outranks every other finding.

Why a pipeline audit beats a 200-point audit

Crawl tools report hundreds of issues across a whole site: missing alt text on old blog images, long URLs, low word counts, redirect chains on pages nobody visits. A lean B2B team cannot fix them all, and most of them make no difference to enquiries. A typical B2B site has a few dozen pages that buyers read on the way to a conversation, and those pages are where an audit pays back.

The checklist below is deliberately short. Each check either affects whether a pipeline page can appear in Google at all, or affects whether a buyer who sees it chooses it and finds what they need. For the wider picture of search visibility on an existing site, see our B2B website SEO guide.

Step 0: list your pipeline pages and record a baseline

Before you check anything, write down the pages that matter. For most B2B companies:

Page type	Why it is a pipeline page
Homepage	Usually the main landing page for branded searches
Service, product or solution pages	Where buyers decide whether you do what they need
Industry and use case pages	Where buyers check you understand their situation
Pricing, or "how we charge"	Often the most important page in a shortlist decision
Case studies and proof pages	Where buyers look for evidence
Integration, comparison and "how it works" pages	Where technical evaluators check fit
Contact or demo request page	Where the enquiry happens

Then record a baseline for each page: three months of clicks, impressions, click-through rate (CTR) and average position from the Search Console Performance report, plus the enquiries the page led to over the same period if your analytics or CRM can tell you. Without a baseline, you cannot judge any fix you make later.

1. Indexing and crawling

A page that is not indexed cannot appear in Google Search, so these checks come first. Google's minimum technical requirements are that Googlebot is not blocked, the page returns an HTTP 200 (success) status code, and the page has indexable content; meeting them makes a page eligible, but indexing is still not guaranteed¹.

Check	Where to look	A pass looks like
The page is indexed	URL Inspection tool²; Page indexing report³	"URL is on Google", and the page is not listed under "Not indexed"
The page returns a 200 status	URL Inspection, or any crawler	200, not a redirect, 404 or server error
Not blocked by robots.txt	Your `robots.txt` file; URL Inspection	No `Disallow` rule covers the page
No stray `noindex`	Page source or URL Inspection	No `noindex` in the robots meta tag or `X-Robots-Tag` header
Google's chosen canonical is yours	URL Inspection: "Google-selected canonical"	Matches the page's own URL, or the URL you declared
Listed in the XML sitemap	Your sitemap file; Sitemaps report	The current URL is present, with an accurate `lastmod`
Mobile version has the same content	The page on a phone	Nothing important is hidden or removed on mobile
Main content is in the rendered HTML	URL Inspection: "View crawled page"	Headings, body text and links appear in the HTML Google received
Old URLs redirect to the current page	Request each old URL from past campaigns or the previous site	One permanent (301 or 308) redirect straight to the current page

What Google's documentation says about these checks

robots.txt does not remove pages. It is mainly used to avoid overloading a site with requests, and Google states it is not a mechanism for keeping a page out of Google; use noindex or password protection for that⁴.
A noindex only works if Google can see it. If the page is blocked by robots.txt, the crawler never sees the rule, and the page can still appear in results if other pages link to it⁵. A common B2B mistake is a staging-site noindex that survives the launch.
Canonicals consolidate signals. Declaring one preferred URL helps search engines combine the signals, such as links, from duplicate or similar URLs⁶. Tracking parameters on campaign links are the usual source of duplicates on B2B sites.
Sitemaps: Google ignores the priority and changefreq values, and uses lastmod only if it is consistently and verifiably accurate⁷. A sitemap that stamps every page with today's date teaches Google to ignore it.
Mobile first: Google uses the mobile version of a site's content for indexing and ranking⁸, so content that only appears on desktop may as well not exist.
JavaScript: Google can process JavaScript, but sites that depend on it are generally more complex to get right; check that the content appears in the HTML Google renders⁹.
Redirects: a permanent redirect tells Google to show the redirect target in search results, and server-side redirects have the best chance of being interpreted correctly¹⁰.

2. Titles and snippets

The title link is often the main thing people use to decide which result to click¹¹. Google generates it automatically from several sources, starting with the <title> element, so these checks are about giving Google a title it is happy to use.

Check	Where to look	A pass looks like
Every pipeline page has a unique, descriptive title	A crawler export of titles	No duplicates; no "Services \| Company" or "Home"
The title and the H1 agree	The page itself	One clear main heading that says the same thing as the title
The brand is in the title once, concisely	Crawler export	Site name at the start or end, after a colon, hyphen or pipe
No keyword stuffing	Crawler export	No repeated words or lists of variants
Google shows the title you wrote	Search for the page's main query	The displayed title link matches, or the change Google made is an improvement
Each pipeline page has a specific meta description	Crawler export	A short, accurate summary written for that page

Google's title guidance asks for descriptive, concise titles that are distinct for every page, warns against vague titles such as "Home" and against boilerplate, and suggests a concise site name at the start or end of each title¹¹. Snippets are created mainly from page content, and Google uses the meta description when it describes the page more accurately than the content does¹², so the opening paragraph of each pipeline page matters as much as the description. For a step-by-step method, see how to rewrite page titles that earn more clicks.

3. Content: does the page answer a buyer's questions?

Google's guidance on helpful content asks, among other things, whether the main heading or page title gives a descriptive, helpful summary of the content, and whether someone will leave feeling they have learned enough to achieve their goal¹³. On a B2B pipeline page, that goal is usually "decide whether to shortlist this supplier".

Check	How to check	A pass looks like
The opening says what you do and for whom	Read the first two sentences only	A stranger could repeat back what you offer and who it is for
The page explains how it works	Read as a buyer comparing three suppliers	Process, scope or deliverables are described, not just claimed
Pricing is addressed	Look for any price, range or explanation of how you charge	A buyer knows roughly what to expect, or why it varies
Proof is specific and real	Check each claim and logo	Named, verifiable examples; no unsourced statistics
The next step is clear	Look for one obvious call to action	One primary action, and it works on mobile
No near-duplicate pages	Compare industry or location pages that share a template	Each page has content that differs in substance, not just a swapped noun
Who is behind the site is clear	About page, author or company details	A buyer can see who you are and why to trust you

The last check comes from the same Google guidance, which asks whether content is presented in a way that makes you want to trust it, through clear sourcing and background about the site that publishes it¹³.

4. Internal links and competing pages

Check	Where to look	A pass looks like
Navigation links are crawlable	Page source	Real `<a href>` links, not script-only buttons
Anchor text is descriptive	Crawler export of internal links	"Data migration services", not "click here" or "learn more"
No orphaned pipeline pages	Compare sitemap URLs with crawled URLs	Every pipeline page is linked from the navigation or a related page
Supporting content links to the right pipeline page	Your top blog posts and guides	Each links to the service or solution page it relates to
Pages do not compete for the same query	Search Console: one query, filtered, Pages tab	One clear page per buyer intent

Google can generally only crawl a link if it is an <a> element with an href attribute, and anchor text tells people and Google something about the page being linked to¹⁴. To find pages competing for the same query, follow the cannibalisation steps in finding quick wins in Google Search Console.

5. Page experience

Check	Where to look	A pass looks like
Largest Contentful Paint	Core Web Vitals report; PageSpeed Insights	Within 2.5 seconds
Interaction to Next Paint	Core Web Vitals report	Under 200 milliseconds
Cumulative Layout Shift	Core Web Vitals report	Under 0.1
Served over HTTPS	The address bar	HTTPS everywhere, with HTTP redirecting to it
No intrusive pop-ups over the main content	Load the page on a phone	The content is readable without dismissing anything except the cookie banner
The form works on a phone	Submit it yourself on a phone	It submits, confirms and arrives in your CRM

The three thresholds are Google's own targets for a good user experience¹⁵, and Google's page experience guidance also asks whether pages are served securely, display well on mobile and avoid intrusive interstitials¹⁶. One caution for low-traffic sites: the Core Web Vitals report uses real-user data, and a URL group without a minimum amount of data is left out of the report¹⁷. If your pipeline pages are missing, test them in PageSpeed Insights instead and treat the lab result as a guide rather than a field measurement.

6. Structured data and entity details

Organization markup on the homepage. Google says it can help it understand your organisation's administrative details and tell it apart from others in search results, and can influence which logo is shown¹⁸.
Markup matches the visible page. Google lists structured data that matches the visible text as an SEO best practice, including for its AI features¹⁹.
Do not add FAQ markup expecting rich results. Google stopped showing the FAQ rich result in Search from 7 May 2026 and removed its documentation in June 2026²⁰. Visible FAQs can still help readers.

What to leave out

A pipeline audit is short partly because of what it skips. These are common in long audits but rarely change anything for a lean B2B team:

Meta keywords. Google states the meta keywords tag is not used by Google Search and has no effect on indexing or ranking²¹.
Word-count targets. Write as much as the buyer needs. A pricing page that answers the question in 300 words is better than one padded to 1,500.
Every issue on pages nobody reads. Note them for later; do not let them delay fixes to pipeline pages.
A single audit score. Tool scores count issues. They do not tell you whether buyers can find and understand your services.

Prioritise the findings

Priority	Finding	Why
1	A pipeline page is not indexed, blocked, or returns an error	It cannot appear in search at all
2	Wrong canonical, broken redirects from old URLs	Signals go to the wrong page
3	Weak or duplicate titles on pages with impressions	The page is shown but not chosen
4	Content gaps on service and pricing pages	Buyers leave with unanswered questions
5	Competing pages, missing internal links	Google and buyers cannot tell which page matters
6	Poor Core Web Vitals, broken mobile forms	Visitors who arrive have a worse experience; a broken form loses the enquiry outright

A broken demo form is the one exception to the order: fix it the day you find it, whatever else is on the list.

Turn the audit into changes you can measure

Fix blockers in one batch. Indexing and redirect fixes do not need testing; confirm each with URL Inspection and request indexing.
Make the other changes one page at a time. If you rewrite ten titles and three service pages in the same week, you will not know which change mattered.
Note the date of every change. Search Console lets you add custom annotations to the Performance chart²².
Compare against your baseline after an equal period, and record the result in plain words: improved, worsened, inconclusive or insufficient traffic. Our guide on measuring the impact of a website change covers the method.
Repeat the audit quarterly, and after any redesign, migration or CMS change.

Where Artiweave fits

Artiweave runs this kind of review continuously on an existing site. It reads evidence from a crawl, Search Console and performance data, proposes specific changes such as a clearer title or a missing section, and waits for a marketer to approve, edit or reject each one. Approved changes are published with automatic rollback, and outcomes are reported honestly, including "inconclusive". It is in private beta.

Frequently asked questions

How long does a B2B SEO audit take?

For 10 to 30 pipeline pages, a marketer with Search Console access and a crawler can usually complete this checklist in one or two working days. A whole-site technical audit takes longer, but most of what it finds will not affect pipeline pages.

What tools do I need for a B2B SEO audit?

Google Search Console (URL Inspection, Page indexing, Performance and Core Web Vitals reports), PageSpeed Insights, a crawler that exports titles, status codes and internal links, and a phone to test the pages and forms yourself.

How often should I audit a B2B website?

Run the pipeline checks quarterly, and again after any redesign, migration, CMS change or large batch of new pages. Check the Page indexing report monthly, because a pipeline page dropping out of the index is the most expensive problem to miss.

Should I fix every issue a crawl tool reports?

No. Fix issues on pipeline pages first, in order of whether they stop the page being indexed, chosen or understood. Issues on pages that get no search traffic and lead to no enquiries can wait.

Sources

All Google pages were checked on 3 November 2026. Dates in brackets are each page's "last updated" date where Google shows one.

Keep your pipeline pages in shape, one approved change at a time.

Artiweave finds evidence-based improvements on the website you already have, waits for your approval, and measures what happens honestly. It is in private beta.

Join the waitlist