Use this checklist before sending visitors to a new WordPress site or moving an existing site to Agiler. Start with Create your first project if you have not set up a project yet.

Prepare the site

  • Finish WordPress installation and confirm that you can sign in to WordPress admin.
  • Check the home page, important landing pages, navigation, images, downloads, and a page that does not exist. Test on a phone as well as a desktop browser.
  • Exercise the features your visitors depend on: submit a contact form, check that its email arrives, try search, and test checkout or account sign-in if your site provides them.
  • Confirm that your themes, plugins, and custom code work with the selected PHP runtime. Review Logs in the project sidebar for errors after testing.
  • Check any environment variables used by your code and confirm that external integrations use the intended production configuration.

Confirm access and billing

  • Make sure the people responsible for launch have the right workspace access. An Admin or Developer can manage the project’s domain, runtime, and backups.
  • Confirm the workspace billing owner and ask that person to review the account balance. Check credits and auto reload and budgets so the site can keep running within your intended spending limits.

Prepare a recovery point

  • Configure automatic backups with a frequency and retention period suited to how often the site’s content changes.
  • Click Create Backup on the project’s Backups page and wait for it to complete before making launch changes.
  • Review Restore a backup so the person handling launch knows how recovery works. Restoration replaces current files and database data and makes the site unavailable while it runs.

Connect the launch domain

  • Follow Connect a custom domain and copy the DNS records shown for your project.
  • If you are replacing an existing site, record its current DNS settings and keep the previous host available while you verify the move. Plan how to pause or transfer new orders, comments, and other writes during the final migration so they are not left on the old site.
  • Wait for domain provisioning to succeed, then open the domain over HTTPS and check that the browser accepts its certificate. Use Domain troubleshooting if setup fails.
  • Select Set as site domain for the intended primary domain and confirm that it has the Site Domain badge.

Verify after cutover

  • Repeat the visitor and WordPress admin checks on the custom domain. Check links, images, redirects, and integrations for references to the old host or temporary domain.
  • Confirm that WordPress’s search-engine visibility setting matches your launch plans and remove any temporary maintenance or access restrictions you added during preparation.
  • Watch project Logs, confirm that scheduled backups complete, and review usage after traffic begins arriving.
  • For a migration, retire the previous host only after verifying the new site and preserving any data written to the old site during DNS propagation.