A website migration is a map of old URLs to new URLs, a date when the old content stops changing, and a week of checks after the new host is the one people open. It is not a redesign mood board. If you cannot list the URLs that already bring enquiries, you are not ready to switch the domain.
AppClust's rebuild offer is website redesign and migration to Next.js. The stack choice sits in Next.js vs WordPress. The crawl setup sits in technical SEO for Next.js. This page is the sequence.
Before you move a page
Export every URL you care about. Include the pages in the menu, the pages that receive form fills, the pages linked from email signatures, and the files people download. Mark which ones must keep their path and which ones can change. A path that is printed on a van or a visa checklist should not change without a redirect.
Write the canonical host in one line. On this site that host is https://www.appclust.com. Anything else, including the apex domain, redirects to it. Decide that before the design, because every canonical tag and every sitemap entry depends on it.
Freeze content. Pick a day after which the old site is not edited except for a correction you also make on the new site. A migration that chases last-minute wording on two systems ships with one of them wrong.
The redirect map
Each row is an old path, a new path, and the note that the redirect is permanent when the move is permanent. This website already uses that shape for renamed articles. These are not a client cutover. They are the pattern:
/blogs/no-code-development permanently redirects to /blogs/no-code-platform-checklist. /blogs/mobile-first-business permanently redirects to /blogs/mobile-first-business-applications. /blogs/business-intelligence-apps permanently redirects to /blogs/business-intelligence-real-time-dashboards. /blogs/data-driven-apps and /blogs/solve-expensive-custom-dashboards permanently redirect to /blogs/dashboards-operations-teams-can-maintain. /blogs/digital-transformation-smb permanently redirects to /blogs/operations-apps-after-spreadsheets. /blogs/app-performance-optimization permanently redirects to /blogs/app-scaling-challenges. /saas-integration-guide permanently redirects to /blogs/saas-integration-guide.
Build the same kind of list for the site you are moving. One old path, one new path, permanent when you do not intend to bring the old path back. Do not chain three redirects if you can point the old path at the final URL. Do not redirect a page to the home page unless the old topic is gone and you have accepted that those visitors will not find it.
Do not add a redirect because a keyword looks attractive. A redirect is for a URL that already exists. New topics get new pages, which is what SEO for a business website is for.
What not to migrate
Do not migrate a URL you cannot explain. Tag archives, internal search results, plugin admin paths, and thank-you pages with no unique offer can be dropped or left as a 404 if nothing important links to them. Do not migrate a test page onto the new host and then forget it in the sitemap. Do not copy a price from the old site into the new one if the old price is no longer the offer. Link to the current pricing page instead of pasting a figure that another page contradicts.
Do not invent a redirect for a blog post you wish you ranked for. If two of your own URLs already compete, look at Search Console before you collapse them. This site is not adding those redirects in the same breath as new articles, because that export is still a separate task.
Who signs the map
One person owns the URL list. One person owns the content freeze. They can be the same person on a small team. They should not be 'whoever is free on launch day'. The owner checks ten old URLs after the switch and writes down any that fail. A failed row is fixed in the redirect list, not with a note in a chat.
If a form, a phone number, or a WhatsApp link is how you get work, those are on the map too. Open them on the new host before DNS moves. A beautiful page with a form that posts nowhere is a broken migration even when every redirect returns 301.
A short list for the week before DNS
Seven checks, in order. The URL map is complete for every path in the menu and every path that received an enquiry in the last quarter. The canonical host is written down. The content freeze date has passed, or you have a named exception. Ten old URLs have been opened on a staging host and land on the right new page. Forms on those pages create a record or a message someone will read. The phone number and the address match the contact page you intend to keep. The sitemap on the new host does not list URLs you marked noindex.
If one of those checks fails, move the DNS date. A launch that proceeds with a broken form or a missing redirect is more expensive than a week of delay. The Next.js comparison is where you decide whether this move should happen at all. This checklist assumes you already decided. The technical SEO note is what the developer checks in the repository while the checklist is running.
Content, forms, and the records
Copy the pages you decided to keep, then check them on the new host before the domain switches. Forms should create a record someone reads, not only an email. If the new site also has modules for leads, products, or bookings, decide which fields are public before you connect the form. That decision is the same one in the custom modules guide, not a theme setting.
Images need alt text that names the object. A logo in the header can be the company name. A photo of a product should say what the product is. Do not leave a library of 'screenshot' alts.
The day you switch
Point the domain at the new host. Confirm the apex redirects to the canonical host. Open ten old URLs from the map and confirm each lands on the new page in one hop. Submit the new sitemap. The sitemap on a Next.js site in this codebase is generated from the pages you listed, and robots.txt should name it.
Check the pages you noindexed on purpose. A city template with no local proof should not appear in the sitemap. On this site, the Dubai website URL canonicals to itself, the old UAE path redirects there, and country-swap routes such as India are noindex. Copy the noindex pattern only when the city page is a duplicate. If you have a real office in that city, give the page its own proof and its own canonical instead.
The week after
Read the form submissions and the server responses, not a ranking report. Fix any old URL that returns 404 and was on the map. Fix any redirect that loops. Correct titles that still mention the old brand. Leave the design alone for that week unless something is blocking an enquiry.
Search Console is where you later see which old URLs still get impressions. This article does not include an export, and it does not tell you to redirect a URL that is earning the wrong queries until you have looked. Bring the URL list to a demo if you want the map checked against the Next.js plan before the domain moves.





