A reliable website launch is more than clicking Publish. Use this reusable pre-publish checklist to review SEO, accessibility, mobile layouts, links, forms, analytics, performance, security, and conversion paths before a new page or site goes live.
Overview
Pre-publish quality assurance is the final controlled review between a finished draft and a public URL. It applies to a single campaign page, a redesigned site, a multilingual release, or a new website deployed through a site builder, WordPress, or a custom development workflow.
The most effective process combines an editorial review with a technical pass. Review the page in a staging environment or private preview first, test the important user journeys, and record anything that needs correction. If the page affects an existing URL, check redirects and search visibility separately from the page content itself.
Use this order to reduce missed dependencies:
- Purpose: Confirm the page has one clear audience, intent, and primary action.
- Content: Check accuracy, structure, spelling, headings, media, and calls to action.
- Experience: Test mobile, desktop, keyboard navigation, forms, links, and readable contrast.
- Technical setup: Review metadata, indexability, structured data, URLs, analytics, cookies, redirects, HTTPS, and performance.
- Release: Publish at the intended time, verify the live page, and monitor the first important interactions.
Checklist by scenario
For a site builder or one-click deployment
- Confirm the correct domain, subdomain, and published project are selected. A preview URL should not be the only location you test.
- Check the global header, footer, navigation, logo link, contact details, and social links on the live domain.
- Verify responsive website themes at narrow and wide viewport sizes. Look for clipped text, overlapping sections, unusable buttons, unexpected horizontal scrolling, and images that crop important content.
- Review the builder's page title, meta description, canonical URL, open graph image, favicon, and indexing controls.
- Confirm that forms send to the intended inbox or service, show a useful success message, and do not expose private configuration in the browser.
- Check that the platform has HTTPS enabled and that the preferred domain redirects consistently from alternate versions.
- Remove placeholder sections, sample text, unused pages, test integrations, and preview-only banners before publishing.
For WordPress or another content management system
- Review the page in the active theme, not only in the editor. Theme styles, menus, widgets, and templates can change the published result.
- Confirm the page's visibility, publication status, author settings, categories, tags, and permalink.
- Test forms, search, comments if enabled, membership areas, ecommerce actions, and any plugin-dependent component.
- Check that image sizes are appropriate and that lazy-loading or optimization settings have not hidden content or damaged layout.
- Clear relevant caches after publishing, then inspect the uncached page and a normal visitor session.
- Verify that analytics, consent controls, backups, security settings, and update workflows are still active after theme or plugin changes.
For a custom site or developer-led release
- Build and test from the same release artifact that will reach production. Record the commit, build version, or deployment identifier.
- Check environment variables, API endpoints, feature flags, error handling, and production logging without exposing secrets.
- Run link, HTML, accessibility, and responsive checks against representative pages and templates.
- Confirm cache invalidation, asset versioning, compression, redirects, and 404 behavior.
- Test the deployment rollback path before a high-visibility launch. A release is not complete if the team cannot identify how to restore the previous working version.
What to double-check
SEO and discoverability
- Give the page a specific, descriptive title and a useful meta description. Avoid repeating the same metadata across unrelated pages.
- Use one clear main heading, then organize supporting sections with logical heading levels. Headings should describe the content that follows.
- Check the URL for clarity, stable wording, and unnecessary parameters. If a previous URL has changed, map it to the most relevant new URL with a permanent redirect.
- Confirm that important pages are not accidentally marked noindex, blocked by site controls, or excluded by a staging rule that carried into production.
- Review internal links from relevant existing pages. Link text should describe the destination rather than relying only on “click here.”
- Validate structured data only when it accurately represents visible page content. Remove outdated or copied markup.
Accessibility and content
- Navigate the page with a keyboard. Focus should remain visible, move in a sensible order, and reach menus, dialogs, forms, and buttons.
- Ensure every meaningful image has concise alternative text. Decorative images should not create unnecessary reading.
- Check labels, instructions, error messages, and required fields in every form. Do not rely on placeholder text as the only label.
- Review color contrast, link distinction, text resizing, animation, and headings at common zoom levels.
- Use plain language where possible, define technical terms, and make the primary action understandable without surrounding context.
Mobile, performance, and reliability
- Test the page on a real mobile device or a credible device simulation. Check menus, sticky elements, tap targets, orientation, and form entry.
- Compress and size images for their display dimensions. Add meaningful dimensions where possible to reduce layout movement.
- Inspect the largest images, fonts, scripts, third-party widgets, and video embeds. Remove anything that is not needed for the page's purpose.
- Review Core Web Vitals-related behavior such as loading, visual stability, and responsiveness, but treat a single test as a diagnostic rather than a permanent guarantee.
- Confirm that the hosting environment, CDN, cache, uptime monitoring, and backup process match the site's operational needs. See the website uptime monitoring and incident response runbook and the backup restore-test checklist for operational follow-through.
Analytics, privacy, and conversion
- Trigger the intended analytics events for page views, form submissions, downloads, purchases, or other primary actions. Check that events are not duplicated.
- Test cookie behavior in a fresh browser session and confirm that optional tools do not load before the site's configured consent choice, where applicable.
- Complete every conversion path from the perspective of a visitor: read the offer, click the call to action, submit the form, receive confirmation, and verify the next step.
- Confirm thank-you pages, email notifications, CRM or payment handoffs, and failure messages.
- Check that no test data, personal information, internal notes, debug messages, or administrator links are visible.
Common mistakes
Testing only the preview: The live domain may introduce redirects, caching, DNS, security headers, integrations, or different scripts. Always perform a short production smoke test after release.
Checking appearance but not behavior: A page can look correct while its form, tracking, navigation, keyboard flow, or redirect is broken. Assign a specific tester to complete the main user journey.
Forgetting old URLs: Redesigns often change slugs or remove pages. Create a redirect plan before launch and test the highest-value legacy URLs.
Publishing placeholder or internal content: Sample copy, draft images, unapproved claims, and staging links are easy to miss when several people edit a site. Search the rendered page and source for common placeholder terms.
Assuming responsive means accessible: A layout that fits a phone can still have poor focus order, missing labels, low contrast, or controls that cannot be reached without a mouse.
Skipping rollback and recovery: A successful release process includes a known backup, a tested restore approach, and a clear decision about who can revert the change. For broader planning, use the production versus staging workflow guide.
When to revisit
Use the full checklist before a new website launch, redesign, seasonal campaign, localization pass, or major template change. For a routine content update, use a shorter pass covering content, links, metadata, images, forms, mobile layout, analytics, and the live smoke test.
Review this process before seasonal planning cycles and whenever your workflow or tools change. Recheck it after changing a website builder, hosting configuration, WordPress theme, plugins, consent tool, analytics property, DNS, domain, or deployment pipeline. Platform controls and browser behavior can change, so editors and site owners should compare their checklist with current product documentation and accessibility guidance during scheduled maintenance.
For a practical release routine, copy the checklist into your issue tracker, assign an owner for each section, record the test URL and date, and attach screenshots or defect notes. Publish only when critical issues are resolved or explicitly accepted. After launch, revisit the live page in a fresh browser, submit the primary form, test the key links, and inspect monitoring and analytics. A short, documented QA habit is more dependable than a large checklist that no one owns.