Loading
Alkota Bikes — 3D WebGL Titanium Configurator
SELECTED WORKAVORRIA DIGITAL STUDIO · LONDON & GLOBAL
START SOMETHING WORTH BUILDINGSearch Engine Intelligence
The most common cause of post-launch organic traffic collapse is not bad SEO — it is a preventable engineering failure. The technical protocol that keeps search rankings intact when a website is rebuilt.
Editorial Analysis — Derived from Avorria migration engineering protocols applied across 28 live website migration projects between 2023 and 2026. Supplemented with Google Search Central documentation.
Website migrations destroy organic traffic regularly. Not because it is technically inevitable, but because the engineering work required to prevent it is almost never scoped into a standard website project. The traffic collapse happens 60–90 days after launch — long after the agency has invoiced and moved on.
Google organic rankings are tied to specific URLs. When a website migration changes URL structure — even slightly — every affected URL loses its accumulated search equity unless Google is explicitly told where the content has moved. A 301 redirect is the technical mechanism for this instruction.
The common failure mode: a new website launches with reorganised URLs, no redirect map has been built, Googlebot encounters hundreds of 404 errors at previously indexed URLs, and the site presence in the index collapses. The organic traffic loss manifests 4–12 weeks later when Google deindexes the old URLs and has not yet established authority on the new ones.
Before any migration, crawl the existing website to establish a complete URL inventory. Every URL that is currently indexed by Google must be accounted for. This includes URLs that appear nowhere in the navigation — old blog posts, campaign landing pages, legacy service pages — because they may hold link equity that needs to be preserved.
Cross-reference the crawl output against Google Search Console coverage data. URLs that are indexed but receiving zero clicks still carry potential equity from backlinks. Treat them as migration assets, not as pages to abandon.
The redirect map is a one-to-one (or many-to-one) mapping from every old URL to its correct destination on the new site. For a site with fewer than 200 indexed pages, this can be built manually. For larger sites, a scripted comparison of old and new URL patterns is more reliable.
Implement all 301 redirects at the server or edge layer — not in JavaScript or client-side routing. In a Next.js application, redirects are declared in next.config.ts and executed at the edge before any HTML is served. This ensures Googlebot processes a genuine 301 HTTP status code, not a client-side navigation event.
// next.config.ts
const redirects = async () => [
{
source: '/services/web-design',
destination: '/services/build',
permanent: true, // 301 — passes link equity
},
{
source: '/about-us',
destination: '/about',
permanent: true,
},
]
export default { redirects }Every page on the new site must carry a correct canonical <link> tag pointing to its own URL. This prevents Google treating any near-duplicate pages (pagination, filter variations) as competing signals. On Next.js, canonical tags are injected via the metadata export in each page.tsx.
Submit a freshly generated XML sitemap to Google Search Console immediately after launch. The sitemap must include only the canonical URLs of live, indexable pages. It must exclude redirected URLs, 404 pages, paginated variants, and any page carrying a noindex directive.
Monitor Google Search Console daily for the first four weeks after migration. Watch for: a surge in Page not found (404) coverage errors, which indicates redirect gaps; unexpected deindexing of canonical pages; and impression drops on high-value queries that were previously stable.
Avorria technical SEO service includes a 90-day post-migration monitoring protocol as a standard deliverable on all website rebuilds. In complex multi-service overhauls such as Entire Facilities Management, this rigorous redirect architecture and metadata discipline prevented traffic dislocation across nationwide commercial service routes. The engineering work to protect rankings is not separable from the build itself — it is part of the specification.
“When you move a site and change URLs, tell Googlebot about the new locations using 301 redirects. Googlebot will follow the redirect and eventually update its index.”
“Sitemaps help Google discover pages on your site. A sitemap is most useful for large sites, sites with complex structures, or new sites with no backlinks.”
Working with Avorria
We work with small businesses on websites, marketing systems, and digital infrastructure.