Migration Readiness Checklist

Platform

Last updated

Use this checklist in the days before you move an existing site to Ploy. Work through it on your Preview site first. On migration day, follow the Launch Checklist.

Replace yourdomain.com with your own domain. Ploy's Agent can run most of these checks for you. Ask in a chat, then review what it reports.


1. Sitemap and redirects

  • Find your current sitemap. Open yourdomain.com/robots.txt and look for the Sitemap: line.
  • Common locations are yourdomain.com/sitemap.xml, yourdomain.com/sitemap_index.xml and, on WordPress, yourdomain.com/wp-sitemap.xml.
  • Save the list of URLs. It becomes your redirect map.
  • For every URL that changes or goes away, plan a redirect to the closest matching page.
  • Add redirects with Path routing. Use permanent redirects for pages that moved for good.
  • Many redirects that follow one pattern, such as /blog/post-name to /articles/post-name, can share one rule. Contact support@ploy.ai before migration day if you need more than 20 rules.

Example prompt: "Compare the sitemap at yourdomain.com/sitemap.xml with my Ploy site and list every URL that needs a redirect."


Goal: no 404s on launch day.

  • Ask Ploy's Agent to check every link on your Preview site, including navigation, footer and buttons.
  • Fix each broken link, or add a redirect for it.
  • Check the links you control outside the site, such as email signatures, ads and social profiles.

Example prompt: "Check every internal link on my Preview site and list any that return a 404."


3. URL pattern audit, before and after

  • Before: ask Ploy's Agent to inventory your current site. It groups URLs by pattern, such as /blog/* or /products/*, and counts the pages in each group.
  • After: ask it to run the same check on your Preview site and compare the two lists.
  • Every URL on your current site should end up in one of three places:
  • Keep the same trailing slash style, for example /about or /about/. On your published site, prerendered pages drop the trailing slash by default, so /about/ redirects to /about. To keep the slash, set trailingSlash: "always" in astro.config.mjs. See Bring Your Own Repo for details.

Example prompt: "Inventory the URLs on yourdomain.com, then compare them with my Preview site and show me any that are missing."


4. New sitemap

  • Ploy builds yourdomain.com/sitemap-index.xml automatically from your site's pages.
  • Your old sitemap may be generated by WordPress or a plugin. It doesn't carry over to Ploy.
  • Check that the new sitemap lists every page you want indexed, including blog posts and other collection pages.
  • Check that every listed URL returns a 200.
  • On Preview, the sitemap uses your preview address. After you set your primary domain and publish to production, it uses your domain.
  • If part of your site stays on your current host, ask Ploy's Agent to keep both sitemaps listed in robots.txt.

5. robots.txt

  • Every Ploy site includes a robots.txt. Ask Ploy's Agent to review it against your current yourdomain.com/robots.txt.
  • Answer its questions, such as which paths should stay blocked, and confirm each change it proposes.
  • Make sure production does not contain Disallow: /.
  • Check that the Sitemap: line points to your domain.

6. llms.txt (optional)

  • llms.txt is a short Markdown file at yourdomain.com/llms.txt. It summarizes your site for AI tools and links to your key pages.
  • It is optional. We recommend it if visibility in AI search matters to you.
  • Ask Ploy's Agent to add one built from your real pages.

Example prompt: "Add an llms.txt file to my site based on my current pages."


7. Secondary pages

  • List the pages beyond your main ones, such as legal pages, careers, landing pages, thank-you pages and older campaign pages.
  • Ask Ploy's Agent to rebuild them on Ploy in your new design.
  • Decide what happens to each page: rebuild it, redirect it, or keep it on your current host.
  • Pages such as a store, accounts or an app can stay on your current host with Path routing.

Example prompt: "Rebuild my privacy policy, terms and careers pages from yourdomain.com in my new design."


8. DNS and SSL

Set this up before migration day, so your SSL certificate is ready before any traffic moves.

  • Make sure your plan includes custom domains, and publish your site to production. Ploy needs both before you can connect a domain.
  • Lower the TTL on your A record and www CNAME to 300 seconds before migration day.
  • In Ploy, open your site, then Domains, and select Add domain. Choose Set it up yourself and select Add the records yourself instead of Connect with your provider, which changes all records at once.
  • Add only the _acme-challenge CNAME records Ploy shows you. There is usually one for yourdomain.com and one for www.yourdomain.com. These records do not affect live traffic.
  • Leave your A record and www CNAME pointing at your current host.
  • Wait until the domain's page says "The certificate is ready. Waiting for DNS." That means your SSL certificate is ready. Contact support if the status doesn't change.
  • Setup keeps going after you close it. If you come back later, open the domain and select Check again.
  • If your DNS is on Cloudflare, set the records to DNS only. If you use CAA records, allow Google Trust Services. See SSL Certificates.
  • On migration day, update your A record and www CNAME to the values Ploy shows you. The Advanced DNS Setup Checklist walks you through it.

9. Image alt text

  • Ask Ploy's Agent to find images that are missing alt text and write short descriptions for them.
  • Purely decorative images can have empty alt text.
  • Review the descriptions before you publish.

Example prompt: "Find every image on my site without alt text and suggest a short description for each."


Next steps