SEO Audit Checklist: A Step-by-Step Website Audit
A step-by-step SEO audit checklist: indexing, redirects, content, Core Web Vitals, structured data and AI search visibility, with tools and priorities.
ReadI’m moving to a new site or platform
A new site should bring in more customers, not wipe out traffic you spent years building. A migration succeeds or fails on the redirect plan and the testing done before the switch, not on fixes after the fact.
In short
A website migration without losing SEO is a change of domain, platform, URL structure or the whole site, carried out so that Google transfers the rankings you’ve earned from the old URLs to the new ones. It rests on a complete 301 redirect map (every old URL to its new equivalent), keeping the content that drew traffic, correct canonicals, a new sitemap and close monitoring in Search Console after launch. At OrbitBuilder we move sites and stores to WordPress and WooCommerce, and between domains. That’s how we rebuilt our own site, orbitbuilder.pl: from Elementor to a custom theme with two hand-written language versions, with 301 redirects from every old URL.
Sound familiar?
I’m changing my domain or business name
Every old URL needs a 301 redirect to its new equivalent, and the move has to be reported with the Change of Address tool in Search Console. Without that, the new domain starts from almost nothing.
I’m moving my store to WooCommerce from another platform
Shopify, Magento, PrestaShop and WooCommerce all structure product and category URLs differently. We map them one to one and carry over descriptions, images, variations and meta tags.
I’m getting a new site and the page URLs will change
A new menu usually means new URLs. Every address that had traffic or links from other sites gets redirected to its closest match by topic.
I’m dropping a page builder or a multilingual plugin
Elementor, Divi or WPML leave behind extra URLs, parameters and leftover code. We check which of them Google knows about and give each the right server response.
Traffic never came back after a previous migration
Missing redirects, redirect chains, or everything sent to the homepage, which Google may treat as a soft 404. We fix migrations like that after the fact too.
I’m switching to HTTPS or changing hosts
A server move doesn’t change your URLs, but it can change response times, cache headers and redirect rules. We test everything on a copy before switching DNS.
Causes
Old URLs return 404s and Google loses the connection to the new pages. It’s the most common and most expensive reason for post-migration drops.
It looks like a quick fix, but Google advises against pointing many old URLs at one unrelated page, because it may treat that as a soft 404.
The old URL points to an address from two redesigns ago, which then points to the new one. Every hop slows down crawlers and visitors, so Google recommends redirecting straight to the final URL.
Category descriptions, FAQs, guides and old posts that brought in traffic get dropped in the rebuild. We move them across or merge them into new pages instead of deleting them.
A staging server Google can reach creates a duplicate of the new site, and a forgotten “noindex” after the switch takes it out of the results.
The new theme has different headings, different meta tags and a menu with fewer links. The pages technically work, but they lose the signals they built up on the old site.
How we fix it
We collect every URL: a Screaming Frog crawl, sitemaps, pages with traffic in Search Console and GA4, and URLs with external links. We record a baseline of traffic, rankings and indexed pages.
In a spreadsheet we give every old URL its new equivalent. URLs with no equivalent get the closest page by topic or a deliberate 410, never a blanket redirect to the homepage.
We move the content, titles, meta descriptions, structured data, image alt text and internal links. For stores, variations, attributes and category descriptions too.
The new site runs on a staging server closed to Google. We crawl it and test the redirects from the old URL list, status codes, canonicals, hreflang and speed.
We go live in an agreed window, lift the blocks, deploy server-side 301 redirects and submit the new sitemap. For a domain change we also use the Change of Address tool.
Daily for the first two weeks, then weekly: 404 errors, the indexing report, traffic to old and new URLs. Anything missing gets fixed straight away.
Google treats a migration like a house move. The signals an old URL has built up pass to the new one when the old address points to the new address with a permanent, server-side redirect. In its documentation on site moves Google recommends 301 or 308 redirects, keeping them for at least a year, and warns that rankings may fluctuate for a while during the move. Our job is to keep that fluctuation short and shallow.
It all starts with a spreadsheet. One column holds every old URL, gathered from the crawl, the sitemaps, Search Console, GA4 and the backlink report. The next holds its new equivalent. For each row we note whether the page had traffic, links and rankings, because those are the URLs we check first after launch. The type of change decides what else has to happen:
| Type of change | What needs to happen |
|---|---|
| New URL structure on the same domain | 301 redirects from old URLs to new, updated internal links, a new sitemap |
| New domain | All of the above, plus both domains verified in Search Console and a Change of Address request |
| New platform, e.g. moving to WooCommerce | Product, category and filter URLs mapped; variations, descriptions and meta tags carried over |
| Switch to HTTPS or a new host | http to https redirects, a server performance test, cache rules and headers |
| Adding language versions | Separate URLs per language, reciprocal hreflang tags, redirects from former URLs |
Store migrations are where we see the most mistakes, because every platform structures product, category and filter URLs differently. In WooCommerce we settle the product and category URL bases up front (by default /product/ and /product-category/), decide which filters get their own indexable URLs and which stay for shoppers only, and point discontinued products to the nearest category or a successor. If you’re still choosing a platform, we’ve compared two popular options in WooCommerce vs Shopify.
In November 2026 we moved orbitbuilder.pl from an old Elementor site to a custom theme and treated it exactly like a client project. Almost everything changed at once: the engine, the URL structure and the languages. The English version lives under /en/, the Polish one under /pl/, and we write both by hand, with no WPML plugin.
Along the way we removed 24 unnecessary plugins (5 are left), and the new site has a CLS of 0 and an LCP of about 0.3 s on desktop. Speed isn’t the point of a migration, but if you’re rebuilding anyway it’s the best moment to fix it. If your change is mainly about design and content, see also how we approach a website redesign.
For the first two weeks we check the Page indexing report, 404s in the server logs and traffic to the most important URLs every day. Google says it can take a few weeks or more before it starts showing the new URLs in place of the old ones, and longer on large sites. Fluctuation is normal in that period, so we measure it against the baseline recorded before launch.
We keep the old sitemap submitted alongside the new one for a few weeks so Google revisits the redirected URLs sooner. For a domain change we make sure the old domain stays paid for and keeps redirecting. Google recommends keeping redirects for at least a year, and the Change of Address tool requires them for at least 180 days. We leave them in place permanently.
If your migration happened without us and the traffic never came back, we can still help. We rebuild the list of old URLs from Search Console, backups and web archives. There’s more on cases like that on our page about an organic traffic drop. If you’re adding languages at the same time, see how we build a multilingual website. After the move we can keep looking after your visibility through our SEO and GEO service.
A migration is best planned before work on the new site starts, because then the URL structure is designed with redirects in mind from day one. Tell us what you’re changing and when.
Engagement options
For businesses whose new site is being built by another supplier and who want to be sure their SEO survives the move.
For businesses changing site, domain or platform that want one team from the plan to post-launch checks.
For businesses already planning a new site or store that want it built with SEO in mind from the start.
What you get
FAQ
Yes, but it doesn’t have to hurt. Google transfers signals from the old domain to the new one if every old URL 301-redirects to its equivalent and you report the move with the Change of Address tool in Search Console. Rankings may fluctuate for a few weeks. The trouble starts when redirects are missing or all point to the homepage.
Collect every old URL, assign each one a new equivalent and set up server-side 301 redirects. Carry over the content, titles, meta descriptions and structured data, test the new site on staging, then submit the new sitemap after launch and watch for 404s in Search Console. The usual mistakes are missing redirects, redirect chains and deleted content that used to bring in traffic.
Google recommends at least a year, and ideally as long as possible. For a domain change reported through the Change of Address tool the minimum is 180 days. In practice we leave redirects in place permanently, because links to old URLs keep circulating for years and keeping the rules on the server costs next to nothing.
Migrating a company site with a few dozen pages usually takes 2–4 weeks including testing, and a store with thousands of products correspondingly longer. Add 4–8 weeks of monitoring after launch. If the migration is part of building a new site, we plan it in parallel, so it doesn’t extend the project.
Yes, as long as the product URLs, descriptions and SEO data move along with the products. We map product, category and key filter URLs from the old platform, such as Shopify, Magento or PrestaShop, to new WooCommerce URLs. We carry over variations, images with alt text, titles and meta descriptions, and customer reviews where the export allows it.
Check whether the old URLs return 404s, whether they go through redirect chains and whether the new site has a stray “noindex”. If redirects are missing, we rebuild the list of old URLs from Search Console, backups and web archives and add them. The sooner it’s done, the more traffic you can win back.
Yes, although the risk is lower. With HTTPS every URL needs a redirect from http to https, and internal links need updating. The Change of Address tool isn’t needed for that. With a new host the URLs stay the same, but before switching DNS we check server speed, status codes and redirect rules.
On the number of URLs, the type of change and how much content has to be moved by hand. Changing hosts is a different job from moving a store with thousands of products to a new platform and a new domain at the same time. We quote after an inventory of the old site. For what drives website costs in general, see how much a website costs.
Insights

A step-by-step SEO audit checklist: indexing, redirects, content, Core Web Vitals, structured data and AI search visibility, with tools and priorities.
Read
WooCommerce vs Shopify compared: real costs, transaction fees, SEO, local payments and shipping in Poland, plus when a custom or headless shop makes sense.
Read
Company rebranding guide: when it makes sense, which logo files you need, animated logos and how to change domains without losing Google rankings.
ReadFree first look
Share your site address and a short description of the problem. We reply within one business day with a first diagnosis and next steps.
How we can help
Your website
Google & AI
We use essential cookies and, with your consent, analytics (Google Analytics, Hotjar) and marketing cookies to understand how you use the site and improve it. Details in our privacy policy.