Website Launch and Maintenance Checklist for WordPress and Site Builders

Overview

Whether you are building with WordPress, a hosted site builder, or an ecommerce platform, the same operational questions apply: does the domain resolve correctly, can visitors use the site on a phone, are important pages discoverable, and can you recover if something goes wrong?

Start by separating launch tasks from recurring maintenance. Launch tasks confirm that the site is ready for public use. Maintenance tasks protect its content, performance, security, and business information over time. If you are still deciding how to begin, the guide to starting a website provides a broader sequence covering the domain, hosting, CMS, and initial launch.

The checklist below works for a new site, a redesign, a domain change, or a move to new WordPress hosting. Mark each item as complete, record any exceptions, and keep access details in a secure password manager rather than in the checklist itself.

Checklist by scenario

Before launching a new website

• Confirm the domain: Check spelling, renewal status, registrant contact details, domain privacy settings where appropriate, and the nameservers or DNS records used by the website.
• Verify the hosting connection: Make sure the domain points to the intended hosting account and that the site is not still dependent on a temporary URL. Review the hosting plan's storage, traffic, email, backup, and support arrangements against the site's needs.
• Enable HTTPS: Confirm that the site loads over HTTPS and that internal links, images, scripts, forms, and embedded resources do not create mixed-content warnings. A free SSL certificate may be included with some hosting or site-builder plans, but activation and renewal should still be checked.
• Review the essential pages: Test the homepage, navigation, contact page, service or product pages, privacy information, terms where applicable, and any confirmation pages. Remove placeholder copy, sample images, unused menu items, and visible development notes.
• Test forms and transactions: Send a test contact or newsletter form submission and verify delivery, confirmation messages, spam handling, and the destination inbox. For ecommerce sites, test the complete purchase flow in the platform's appropriate test or review mode.
• Check mobile layouts: Review common page types at narrow and wide screen sizes. Look for clipped headings, buttons that are difficult to tap, horizontal scrolling, oversized images, and forms that are awkward to complete.
• Prepare analytics and search tools: Install only the tracking tools you need, confirm that the relevant pages are measured, and document how to access reports. Set a preferred domain and review indexing settings so a staging or private version is not accidentally exposed, while the finished site is not blocked from search.

After a redesign or website migration

• Create a page inventory: List important URLs, media files, downloads, forms, integrations, and redirects before changing the site. This makes it easier to identify what must be preserved.
• Back up before moving: Save the database, files, configuration information, and any platform-specific export available to you. Keep a copy separate from the live hosting account.
• Test the new version privately: Review templates, plugins, theme settings, custom code, payment connections, email delivery, and user permissions before changing DNS or publishing the redesign.
• Map changed URLs: Redirect old, useful URLs to the closest relevant new pages. Avoid sending every retired URL to the homepage when a more specific destination exists.
• Check DNS and email separately: A website migration can affect nameservers, A or CNAME records, email records, and verification records. Use the domain setup guide when reviewing DNS, SSL, and email dependencies.
• Recheck after propagation: Visit the site from different networks or devices, test the main domain and common variations, and monitor forms and email after the DNS change.

For ongoing WordPress or site-builder maintenance

• Apply platform, theme, plugin, and integration updates through a controlled process. Review compatibility and test important functions after significant changes.
• Maintain recent backups and periodically verify that a backup can actually be restored. A backup that has never been tested should not be treated as a complete recovery plan.
• Review administrator accounts, editor permissions, connected apps, API keys, and unused accounts. Remove access that is no longer required and use strong, unique credentials.
• Monitor uptime, form delivery, checkout functions, storage, and site errors. An uptime monitor can identify availability problems, but it will not replace a manual review of forms and business workflows.
• Compress new images, remove unnecessary scripts, and review caching or CDN settings as the site grows. The WordPress speed guide covers hosting, caching, images, and CDN considerations.

What to double-check

Some launch problems are easy to miss because the page appears to work in the browser. Use a separate review pass for the following:

• Navigation paths: Start at the homepage and reach every important conversion page without using a direct URL. Test logo links, menus, breadcrumbs, footer links, and search.
• Performance: Check large hero images, video backgrounds, font files, third-party widgets, and scripts. Test representative pages rather than only the homepage. A faster hosting plan may help, but reducing unnecessary page weight is also part of website speed optimization.
• SEO basics: Give each important page a clear title, useful description, descriptive heading structure, readable URL, and one obvious purpose. Check canonical settings, XML sitemap availability, redirects, image alternative text, and whether the site is unintentionally set to discourage indexing.
• Accessibility: Navigate with a keyboard, inspect color contrast, confirm form labels, add meaningful alternative text, and make sure focus states remain visible. Automated checks can help find issues but should not be the only review.
• Messages and details: Verify phone numbers, addresses, opening hours, prices, copyright notices, author information, social links, and automated email signatures. These details often become outdated before the design does.
• Security and recovery: Confirm HTTPS, administrator protections, backup location, update responsibilities, and the recovery contact. Keep a record of who can change DNS, hosting, domain registration, and business email.

Common mistakes

• Launching from a staging copy: Check the domain, indexing settings, analytics property, and visible content before announcing the site.
• Assuming DNS changes cover email: Website records and email records can have different requirements. Confirm MX, SPF, DKIM, and other records with the relevant email provider before editing DNS.
• Updating everything at once: Large batches of plugin, theme, platform, and design changes make it difficult to identify the source of a failure. Keep a change log and use a backup before major work.
• Relying on a single backup: Store more than one recent copy when the site is important, and confirm that the restoration process is understood.
• Ignoring redirects after a migration: Broken links can affect visitors, bookmarked pages, marketing campaigns, and search visibility. Review your most visited and most valuable old URLs first.
• Measuring traffic without measuring outcomes: Analytics should answer practical questions, such as whether visitors reach a contact page, complete a purchase, or download a resource. Remove tracking that does not support a decision.

When to revisit

Run the full checklist before a new site launch, redesign, domain change, hosting migration, major plugin update, or seasonal campaign. Before busy periods, review forms, checkout, contact details, inventory or service information, performance, and backup status rather than assuming last season's setup still works.

Use a shorter monthly review for updates, backups, accounts, broken links, forms, security notices, and key business details. Every few months, review search visibility, page performance, mobile usability, analytics goals, content accuracy, and unused integrations. Revisit the checklist whenever your hosting workflow, CMS, site builder, email provider, or marketing tools change.

For the next practical step, make a copy of this checklist, assign an owner to each task, and record the date and result of every test. If hosting is part of the problem, compare requirements using the web hosting comparison checklist. A documented routine turns website maintenance from an occasional emergency into a manageable part of site growth.