Blog / Technical SEO /
A practical checklist for SEO acceptance before release
The release looks great. Design signed it off. Everyone’s happy.
Has anyone checked that the main pages are still indexable? That the redirects work? That the contact form still sends an enquiry? …Anyone?
“SEO accepted” should mean a set of checks someone actually ran, not a feeling that the site looks finished. A practical acceptance checklist is built around the change and the pages it can touch. It should catch real defects without turning every possible audit item into a launch blocker.
Define scope and owners
Write down what is changing: templates, content, URLs, plugins, tracking, navigation, server settings or another component. Identify page types and journeys affected. A redesign of a shared template needs broader sampling than a minor copy correction.
Assign an owner for each check. Developers may verify response codes and markup; editors can confirm content; site owners approve business wording and publication timing. If a check has no owner, it tends to get skipped, even when it matters. Every item on my checklists has a name next to it for exactly that reason.
Decide what counts as a blocker, what can be accepted with a follow-up and who can approve the exception. A late deadline does not make an unresolved issue harmless; it makes the impact and decision more important to record.
Check crawlability and URL behaviour
For representative pages, check status codes, robots directives, canonicals, sitemap inclusion and internal links. Confirm that public pages are not accidentally blocked or marked noindex, and that review or staging pages are not exposed as public destinations.
If URLs changed, test old and new routes. Confirm redirects lead to relevant pages without chains or loops. Update internal links so they point directly to the current URL. Check hostname, protocol, trailing slash and query behaviour where the release changes those rules.
Review robots.txt and sitemap output after deployment. A valid sitemap should contain the intended preferred URLs, not every generated parameter or staging path. Inspect the live response rather than trusting a CMS setting. I’ve learned not to take a tick box’s word for it.
Check page content and templates
Review titles, descriptions, headings and page copy on representative examples. Confirm that the text matches the page and that key facts are approved. Test a long heading, a missing optional field and any content variation likely to affect the template.
If structured data is present, compare it with visible content and source records. Validate syntax, but do not treat a successful test as proof of rich-result display or factual accuracy. Look for duplicate output from plugins, themes or custom code.
Test internal links, navigation, pagination and related content. A page can be crawlable but difficult to reach. Review mobile layouts and keyboard access for important journeys. SEO acceptance should not separate search signals from the experience visitors actually have.
Test performance and measurement appropriately
Check the affected pages under comparable conditions. Core Web Vitals are LCP, INP and CLS. A release checklist can note known issues and the measurement method, but a single lab run does not describe every user experience. Record what was measured and avoid claiming that one change guarantees a score or ranking.
If analytics events are affected, confirm the intended actions and test them. GA4 uses “key events” for actions designated as important. Check that an event fires at the correct point, not simply when a visitor clicks a button before completing a task.
Publish, retest and document exceptions
Run the checks in preview or staging where possible, then repeat critical checks on the live site. Record evidence, results and exceptions. If a feature depends on a later recrawl or cache refresh, keep that follow-up open and assign an owner.
Make acceptance criteria testable
A checklist item should describe an observable result. “SEO is done” cannot be checked consistently. “The canonical on this representative page points to the intended public URL” gives the reviewer something to inspect. The same principle applies to redirects, robots directives, titles, structured data and analytics. Write the expected behaviour in plain language and identify which page or route demonstrates it.
Use representative page types rather than testing only the homepage. A release may use different templates for product, collection, article and utility pages. Choose one or more examples of each affected type, then add specific exceptions where the change has a larger consequence. If a checklist grows until nobody can finish it, split the routine checks from the release-specific risks.
Evidence can be lightweight: a tested URL, a screenshot, a crawl result or a short note about the observed behaviour. Keep enough context that another person can reproduce the check. Record defects with an owner and a next action, then retest after the fix. A failed check with a documented decision is safer than silently ticking a box because the launch date is close. I’d rather delay a launch by a day than ship a noindex tag on the homepage. Decide in advance who can accept an exception and what must be communicated.
The acceptance record should identify the environment and date of the check. A staging result may differ from production because of caching, configuration or third-party scripts. Where a check cannot be completed before release, document the reason, owner and planned follow-up. That turns an exception into a visible decision with a deadline instead of a forgotten checkbox. Keep the evidence easy to find for whoever supports the release afterwards.
Before release, confirm that the checklist reflects the agreed scope. A small copy edit should not trigger an unrelated migration audit, while a template change deserves broader sampling. This keeps checks proportionate and makes the release decision easier to explain.
Related reading
- Technical SEO: structured data validation after releases
- Technical SEO: HTTP response headers for site owners
- Technical SEO: consent banners and layout shifts
A release checklist works when each item reflects a real risk and has someone responsible for it. Before your next release, write three checks as observable results, with a page to test each one. Which one would you be most nervous to skip?