Skip to content
Adrythm

Site move

Move a WordPress or Squarespace site to Replit without losing your rankings

The order of work that keeps the pages Google already ranks, from the first crawl of the old site to the weeks after the switch.

Why read this and not just the docs

Google's site move guide is written for any site on any host, and Replit's custom domain page stops at the DNS records. This puts the two in the order a WordPress or Squarespace move actually runs, and adds what a test of three finished moves showed on 2026-11-15: 878 old addresses requested on the live sites, the extra hops the www and http versions still add, and the old addresses no redirect map covered.

7 steps, in order.

  1. 01

    List every address the old site has

    A WordPress migration to Replit is a change of platform, not only of hosting provider: the theme, the plugins and the WordPress database stay behind, and what moves is the content and the addresses Google knows. Migration plugins such as All-in-One WP Migration copy a WordPress install to another WordPress host, which is a different kind of move. Start with the sitemap, then add what the sitemap misses: pages in Search Console's performance report, old blog posts, landing pages from past ad campaigns and image files that get traffic. Google's site move guidance names sitemaps, server logs and analytics as the places to look. When should you migrate? In your quietest season: the same guidance warns that rankings can move about while Google recrawls, and that most pages of a medium-sized site can take a few weeks to move over.

    • Count the archive pages too. In the three moves Adrythm tested on 2026-11-15, two WordPress sites and one Squarespace site now running on Replit, the old addresses came to 103, 663 and 112. On the first WordPress site, 13 of its 103 were tag, category and blog archive pages that no one had thought of as pages; on the second, most of the 663 were one service page per town.
    • Look past the pages. On both WordPress moves the old image addresses under /wp-content/uploads/, the old /feed/ and the old /sitemap_index.xml answer 404 today, because each redirect map listed pages only. If image search sent visits to the old site, add its image addresses to the list.
  2. 02

    Map each old address to one new address

    Write the map down before anything is built. Keep the same address wherever you can, because an unchanged address needs no redirect at all. Where a page is merged or renamed, point it at the single new page that answers the same question, not at the home page.

    • The three maps sent 2 of 878 old addresses to the home page: an empty category archive on one site, and the old home page's own address, /home, on another. Every other address points at a page about the same thing.
    • A service you no longer offer still gets a page, not the home page. One of the WordPress sites had dropped a whole line of work. Each of its 26 retired service addresses was matched by hand to the closest page about work the business still does, and the reason for each match is written beside it in the map.
    • Many old pages can share one new page. The second WordPress site's 663 addresses land on 600 pages: each town's separate service pages now point at that town's one page.
  3. 03

    Carry over what Google reads, not just what people see

    Titles, meta descriptions, headings, structured data, image alt text and internal links all move with the page. Each new page should name itself as its own canonical address, and internal links should point straight at the new addresses rather than through a redirect.

  4. 04

    Redirect permanently, on the server

    Google recommends server side permanent redirects, 301 or 308, and says to keep them for as long as possible, generally at least a year. Avoid chains: an old address should land on its new one in a single hop.

    • Check the publishing type can send one. Next.js does not apply its redirects setting to a static export, and a redirect drawn by the page in the browser is not a server redirect. Both WordPress moves Adrythm tested publish a small Node server on Autoscale for this reason, and it reads the redirect map as data.
    • Pick one host, with or without www, and permanently redirect the other to it. Two hosts that both answer can be indexed as two copies of every page.
    • Make the www and http versions land in one hop as well. On 2026-11-15, every old address on all three sites but one took a single 301 to its new page. Asked through www, two sites still took one hop and the Squarespace move took two, www to the bare domain and then the map. Asked over http, all three took two hops, and http with www on the Squarespace move took three.
    • Match old addresses with and without the trailing slash. WordPress writes addresses ending in a slash and Squarespace writes them without one; all three sites answered both forms with the same single 301 in a sample of 50.
  5. 05

    Test the whole map, on the live address

    Request every old address from outside, before the switch and again after it, and keep the results. From a terminal, curl -sI followed by an old address prints the status and the Location it points to. A pass is one 301 or 308 whose Location is the mapped page, then a 200 from that page.

    • Run it four ways: the main host, www, http and the trailing slash the old platform used. The extra hops above showed up only through www and http.
    • Expect the odd 404 and read each one. Of 878 addresses on 2026-11-15, one returned 404, and its new page was finished but not yet published: the map was ready before the page. Publish the page first, or leave its old address out of the map until it is live.
    • Try a capital letter. One of the three sites redirects /About-Us/ the same as /about-us/; the other two answer 404 for it, which matters only if old links typed capitals.
    • Check that tracking survives. A redirect should carry the query string, so an old ad link's tags still arrive. On the first WordPress site an old address with ?utm_source= reached its new page with the tag intact.
  6. 06

    Point the domain without breaking email

    Replit asks for an A record and a TXT verification record at your registrar, and says the verification record must stay in your DNS for as long as the domain is connected. Change only the records the site needs. Leave the MX and other email records exactly as they were, and write them down before you start in case anything is overwritten.

  7. 07

    After go-live: tell Google, then watch

    Submit the new sitemap in Search Console. For the next few weeks, check the pages report for indexing changes and the performance report for searches that drop, and fix any address that returns an error or lands somewhere unhelpful.

    • Rerun the address test after every change to the map or the routes. The map is a file in the code, and a later edit can break an address that passed on the day of the switch.