NYC Website Migration SEO Services: Moving a Site Without Losing Rankings

A website migration is one of the riskiest routine projects a business can run on its site. New design, new platform, new domain or new URL structure: each one changes the addresses Google has already ranked, and each needs a plan before anything goes live. Good NYC website migration SEO services are mostly that plan, followed carefully on launch day and checked for weeks afterwards.

I am Eugen Platon, and I have worked in SEO and digital marketing for more than 16 years, much of it technical. I run onwardSEO from Bucharest and work with clients remotely, and site moves are projects I check often. This article gives you the plan step by step, built on Google’s own site-move documentation, so you can judge any proposal against it.

Which kind of migration are you running?

“Migration” covers several different projects, and they don’t all need the same steps. The first thing I ask is what actually changes: the domain, the protocol, the URLs, or only the server.

Google’s guide to site moves with URL changes is direct about the tool: “You only need this tool when moving from one domain or subdomain to another”. For an http to https change, the Change of Address help page says “follow the guidelines for site move with URL changes, but don’t use this tool”. For moving pages within the same site, it says: “In this case, just add redirects, and update your sitemaps as appropriate.”

A redesign that keeps every URL is the safest case. If your developer can keep the URLs, ask them to.

What NYC website migration SEO services should cover

The SEO side of a migration should include five pieces of work. If a proposal leaves one out, ask why.

1. An inventory of the old site: every URL that gets traffic, links or rankings.
2. A URL map: each old URL paired with its new address, or marked as removed.
3. Redirect rules and testing: written for your developer, then tested on staging and again after launch.
4. Launch-day checks: robots rules, noindex, canonicals, sitemaps, Search Console.
5. Monitoring for several weeks: rankings, indexing, crawl errors and traffic on both old and new URLs.

The heaviest part is the inventory and the map. The design agency usually owns the build; the SEO work is making sure nothing Google already trusts gets lost between the two sites. That often means an SEO consultant working alongside the developers rather than replacing them. My article on working with an independent consultant covers how that collaboration runs, and if you want to understand pricing first, read what drives the cost of a site migration.

Step 1: build the inventory and the URL map

Google says it plainly: “It’s important to map your old site’s URLs to the URLs for the new site.” The map is the base for everything else.

I build the map from several sources, not just the old sitemap:

• the old XML sitemaps and a full crawl of the old site;
• pages with clicks or impressions in Search Console;
• landing pages in your analytics;
• pages with links from other sites;
• PDFs and old campaign URLs that still get visits.

Each row gets one new destination. The best destination is the page that does the same job for the user: the old “commercial cleaning Brooklyn” page goes to the new Brooklyn service page, not to a general services page. Google allows the map to be stored however suits you: “You might use a database, or configure some URL rewriting rules on your system for common redirect patterns.”

For a business with several locations across the boroughs, location pages deserve special care. They usually carry local rankings, and each one is often the website link on a Business Profile. If you are planning new location pages as part of the move, my guide to local SEO in New York explains how to structure them without creating doorway pages.

Step 2: set up the redirects properly

Redirects carry your old pages’ place in search to the new pages. Google recommends “server side permanent redirects from the old URLs to the new URLs as you indicated in your mapping”, and adds that “we recommend that you use HTTP permanent redirects if possible, such as 301 and 308.”

The type matters. Google’s page on redirects and Google Search explains that a permanent redirect tells it to “Show the new redirect target in search results”, while a temporary one tells it to “Show the source page in search results.” A migration done with temporary redirects asks Google to keep showing the old URLs.

A redirect map is the cheapest insurance a migration can buy.

Step 3: prepare the new site before launch

The new site should be ready for Google on the day it goes live. From Google’s site-move guide, these are the points I check on staging:

• Canonicals: “Each new URL should have a self-referencing rel="canonical" <link> tag.”
• Internal links: “Change the internal links on the new site from the old URLs to the new URLs.” Internal links that pass through redirects add an extra step and hide mistakes.
• Robots rules: the new robots.txt should “correctly reflect the parts you want blocked from crawling.”
• Hreflang, if you have language versions (for example Spanish pages alongside English ones): “be sure to update the annotations to use the new URLs.”
• Sitemaps: a new XML sitemap with the new URLs, ready to submit.
• Capacity: “Ensure that your new site has sufficient capacity to handle the increased traffic from Google.”

In Search Console, Google asks you to “Be sure to verify all variants of both the old and new sites.” Do it before launch day.

Launch day: the checks that catch most problems

Google suggests you “Time your move to coincide with lower traffic, if possible.” For a New York business, that means a quiet day and hour in Eastern Time, based on your own analytics, not the developer’s convenience. If your developers or your SEO consultant work in another time zone, agree in advance who is online when the switch happens.

The Business Profile step is easy to forget. The Business Profile help page asks you to “Enter the full URL, which includes “http://” or “https://.””, and notes “We review your changes before we update them live on your profile.” For a business with locations in several boroughs, point each profile to its own new location page, not to the home page.

Google’s own way to request indexing of a single page is the URL Inspection tool in Search Console.

After launch: the first weeks and the first year

Even a clean move dips for a while. Google’s guide says “Expect temporary fluctuation in site ranking during the move” and that “a small to medium-sized website can take a few weeks for most pages to move, and larger sites take longer.” Don’t panic in week one, but don’t wait months either.

What I check in the weeks after launch:

• Crawl errors and indexing: Google says “Check regularly for any unexpected crawl errors.” Early on, the new sitemap may show few indexed pages; Google notes it “would have zero pages indexed” at first.
• Rankings for the baseline keywords, on desktop and mobile, compared with the pre-launch check. My guide to tracking rankings after a website migration explains the method.
• Traffic on both sites: “Use web analytics to analyze usage on both the old and new sites.”
• Old URLs still getting visits, which usually means a missing or wrong redirect.
• Links from other sites: “Try to contact the sites in the saved list of sites linking to your current content”, starting with the ones that send the most visitors.

When something is wrong, the fix is usually a redirect, a canonical or a stray noindex, and it is best caught in the first weeks.

How long to keep redirects and the old domain

Google’s site-move guide says: “Keep the redirects for as long as possible, generally at least 1 year.” The Change of Address page adds “we recommend continuing to pay for the old domain for at least a year”, and warns that “After the 180 day period, Google does not recognize any relationship between the old and new sites”. Write the redirects into your hosting documentation, so a later server change doesn’t remove them.

Do you need a migration agency, or a consultant and your developers?

Most migrations don’t need a large team for the SEO side. They need one person who understands crawling and indexing, a developer who can write redirect rules, and someone who knows what each old page should become.

A larger team makes sense when the site has tens of thousands of URLs, several languages, or a platform change on a busy e-commerce store. For a typical New York service business, I usually suggest a technical audit of the old site first, then help with the map and the checks. If your current site has problems that should not be carried over, a website SEO audit before the move is the cheaper time to find them.

Whoever you hire, ask to see their URL map format and launch checklist before the work starts. If they can’t show you either, the rankings are being left to chance.

FAQ

What does website migration SEO involve?

Website migration SEO covers the search side of a site move: listing the old URLs that matter, mapping each to a new URL, setting up permanent redirects, preparing canonicals, sitemaps and robots rules on the new site, and monitoring rankings and indexing after launch.

Should I hire an NYC agency specializing in SEO migration?

Not necessarily. What matters is experience with site moves and a clear process: a URL map, tested redirects, a launch checklist and monitoring. A consultant can work remotely with your developers, as long as someone is available at launch time in Eastern Time.

Will I lose rankings when I move my site?

Google says to expect temporary fluctuation during a move, and that a small to medium-sized site can take a few weeks for most pages to move. Rankings that don’t recover usually point to missing redirects, redirects to the wrong pages, or blocks left over from staging.

Do I need the Change of Address tool for a redesign?

Only if the domain or subdomain changes. For a redesign on the same domain, Google says to add redirects and update your sitemaps. For an http to https move, Google says not to use the tool.