Operations
Part of When to formalise ecommerce SEO operations in your team
When to run an ecommerce SEO quality checklist on your store
Use this ecommerce SEO quality checklist to verify canonicals, crawl limits, content and ownership before each store release, with one named owner keeping evidence.
What to take away
- Crawl controls now sit with store teams, not just hostsGoogle's guidance on reducing crawl rate puts the decision in your hands, so name an owner.
- Quality checks fail when ownership is vague. Name one person per check and record the date it passed.
- Standards give you a reference point for process quality, not a certificate that proves rankings.
- Release gates beat annual auditscheck before each release, then sample monthly.
Before each release
Run these checks on every template change, not once a quarter. A store with 4,000 product pages can break a canonical in one afternoon.
Pre-release SEO checks
- Canonicals point to intended URL
- Filtered URLs blocked or canonicalised
- Sitemaps match live indexable set
- Internal search pages carry noindex
- Redirect chains flattened to one hop
Record who signed each line and when. A check with no owner counts as failed.
Crawl and server load
Crawl demand is a resource decision as much as an SEO one. When testing or migration traffic spikes, you can ask Google to slow down rather than let the server fall over. The documented route is to reduce Google crawl rate through Search Console settings, and to note the date you changed it.
Crawl review threshold
800ms
Response time above this for two days triggers a crawl review
Example team pays £400 a month for hosting
Document the date you changed crawl rate
Set a threshold before you need it. For example, a team paying £400 a month for hosting might agree that any response above 800ms for two days triggers a crawl review.
Content and index quality
Check that thin category pages earn their place. A page with three products and no unique copy competes poorly.
- Duplicate product descriptions are rewritten or consolidated.
- Out-of-stock pages keep a useful state rather than returning a soft 404.
- Title tags and H1s differ across near-identical variants.
- Paginated series are self-canonical and crawlable.
- Structured data matches visible content.
- Robots.txt allows crawling of pages you want indexed, and the XML sitemap lists the canonical URLs you want search engines to find.
- Canonicals point to the preferred version; review unintended indexable URLs for index bloat.
- Check Core Web Vitals against Google's good thresholds for LCP, INP and CLS.
Use Google Search Console's Page indexing report to review indexing issues. Crawl the site with Screaming Frog SEO Spider or Sitebulb, and validate structured data with Google's Rich Results Test.
These checks belong in the wider delivery routine set out in the ecommerce SEO operations and delivery guide, which maps each stage to an owner.
Standards and evidence
You do not need certification, but published standards give you a reference point for a quality process. BSI publishes BS EN ISO 9001, Quality management systems — Requirements, which you can use to inform documented processes and corrective action. It does not certify rankings.
Keep evidence in one place: the check name, the date, the person, the outcome. That record is what makes an audit possible.
Before and after
Before
- Canonical rules
- Applied per page by hand
- Crawl rate
- Adjusted only in a crisis
- Content
- Rewritten when noticed
- Ownership
- Shared informally
- Evidence
- Screenshots in chat
After
- Canonical rules
- One documented rule per template
- Crawl rate
- Threshold agreed with hosting
- Content
- Sampled monthly against a standard
- Ownership
- One named person per check
- Evidence
- Dated log with sign-off
How often to review
- Before each release:run the checks for every affected template before deployment.
- Before launch:run the full checklist before opening a new store or site. For a replatform, domain change or major range launch, check before and after the change.
- Before seasonal peaks:run the checklist before freezing the range for Black Friday or Christmas.
- After a Google core update:re-run the checks on affected templates and review any changes in search performance.
- Monthly:sample ten URLs. If two sampling rounds fail the same check, fix the process, not the page.
- When server response time triggers your agreed limit:for example, a response above 800ms for two days triggers a crawl review for a team paying £400 a month for hosting.
Service expectations differ between buyers and suppliers, and the ecommerce SEO service standards in England explain how to word those commitments in a contract.
Common questions
Who should own the checklist?
A named operations lead, not the whole team. They hold the log and escalate failures. Technical checks can sit with a developer, but the lead confirms the record is complete.
How long should evidence be kept?
Long enough to cover a contract term and any warranty period. A rolling twelve months is a practical default for most English store teams.
Does a checklist replace an audit?
No. It prevents known faults. An audit looks for faults you have not yet listed, so run both.
What if we have no in-house technical resource?
Write the checks in plain language and agree who receives the output. The judgement still needs to sit inside your business.
