# B2B Export-Site SEO Delivery Checklist

- Version: 1.0.0
- Released: 2026-07-24
- Source: eigentime, "An 8-Module B2B SEO Delivery Framework"

## How to use it

This is a delivery QA checklist, not a promise of rankings, traffic, or inquiries. At kickoff, assign an owner, evidence, and due date to each applicable item. Recheck it before launch, then carry unresolved items and next actions into the monthly review.

## 0. Scope and ownership

- [ ] State the countries, languages, product lines, and page groups in scope.
- [ ] Name the owner and approver for client, content, development, and SEO work.
- [ ] Save a pre-change baseline: impressions, clicks, major rankings, indexed pages, and priority URLs.
- [ ] Keep "delivered," "implemented," and "verified" separate; a finished document is not a finished outcome.

## 1. Keyword expansion

- [ ] Gather seed, product, application, problem, and competitor terms.
- [ ] Use a negative list to remove irrelevant industries, jobs, free-resource intent, and false matches.
- [ ] Label the intent of core terms: informational, commercial, or navigational.
- [ ] Require evidence of real demand instead of accepting AI-generated terms by default.
- [ ] Map every retained term to a clear page; move unmapped terms into the topic library.
- [ ] Consolidate synonyms and obvious cannibalization groups; record primary and supporting terms.

## 2. Competitor analysis

- [ ] Select business competitors from the actual search results, not only familiar brands.
- [ ] Record the ranking URL and page type for each core term.
- [ ] Compare organic vs. branded traffic share, major source countries, and the two-year trend.
- [ ] Compare page structure, depth, product fields, trust elements, and internal entry points.
- [ ] Separate observed facts from third-party estimates; do not present estimates as exact measurements.

## 3. Site diagnosis

- [ ] Check title, description, H1, canonical, and index directives.
- [ ] Confirm robots.txt and sitemap agree and priority pages are crawlable.
- [ ] Find index pollution from tags, dates, filters, search pages, and leftover template URLs.
- [ ] Check duplicate content, soft 404s, redirect chains, and incorrect status codes.
- [ ] Test mobile reading, navigation, forms, and critical interactions.
- [ ] Give every issue a sample URL, severity, owner, and verification method.

## 4. Topic library

- [ ] Bind each topic to a target term, intent, audience, and destination page.
- [ ] Choose the content type: guide, comparison, case study, FAQ, or product-support content.
- [ ] Identify required first-party evidence, product material, and subject-matter input.
- [ ] Merge duplicate briefs so multiple pages do not compete for the same intent.
- [ ] Assign priority, owner, and target publication date.

## 5. Product detail page template

- [ ] Research competitors in the vertical before defining required and differentiating fields.
- [ ] Include a clear short description, product overview, features, and advantages.
- [ ] Cover use cases, specifications, or selection criteria instead of stacking generic claims.
- [ ] Provide related products, related guides, and FAQ only where useful.
- [ ] Keep the primary inquiry path clear on desktop and mobile.
- [ ] Pilot the template on a real product page before rolling it out in bulk.

## 6. TDK SOP

- [ ] Define the page's role before choosing primary and supporting terms.
- [ ] Make the title match the target intent while staying readable and differentiated.
- [ ] Make the description state real page value without promises the page cannot prove.
- [ ] Keep titles and descriptions unique across comparable pages.
- [ ] Check length, brand spelling, punctuation, and target-market language.
- [ ] Human-review AI output for page role, facts, and final expression.

## 7. Pre-publish QA

- [ ] Production URLs return the intended 200, 301, 404, or 410 status.
- [ ] Canonical, robots, hreflang, and sitemap use final production URLs.
- [ ] The page has one meaningful H1 and a continuous heading hierarchy.
- [ ] Internal links, breadcrumbs, images, downloads, and forms work.
- [ ] Images have alt text; mobile has no horizontal overflow or obstructed controls.
- [ ] GSC verification, analytics, and conversion events follow the project's privacy agreement.
- [ ] Recrawl priority pages after launch and retain acceptance evidence.

## 8. Monthly reporting and review

- [ ] Summarize GSC impressions, clicks, CTR, rankings, and index movement.
- [ ] Summarize organic traffic and priority-page trends from GA4 or an equivalent tool.
- [ ] Explain changes by country or region instead of reporting only site-wide totals.
- [ ] Separate branded from non-branded movement, seasonality from project actions.
- [ ] Label each conclusion as fact, inference, or an assumption still needing validation.
- [ ] Give every finding a next action, owner, and review date.
- [ ] Do not turn correlation into causation or a team's portfolio into personal ownership.

## Final acceptance

- [ ] Every blocker is closed or has a named accepter and documented reason for deferral.
- [ ] Deliverables, change records, and evidence links are accessible to the project team.
- [ ] The client or internal owner knows what must happen next.
- [ ] The report states data limits, execution dependencies, and what cannot be concluded.

## License and limits

This checklist is licensed under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). You may copy, adapt, and use it commercially with appropriate attribution and an indication of changes.

Suggested attribution: `CG-X / eigentime.org — B2B Export-Site SEO Delivery Checklist v1.0.0`.

This checklist is not a ranking, traffic, inquiry, legal, or compliance guarantee. Apply it in context: market, website, available resources, and client execution still determine what can be achieved.