The Pattern

A company launches a new website on a new platform. The design is better and the team is proud of it, but within weeks organic visits fall and several pages that used to rank disappear from search results. The agency says the drop is normal and will recover on its own.

What Teams Usually Try First

They typically wait it out, resubmit the sitemap, publish new blog posts to make up for the lost traffic, or ask the designer to restore the old text on a few pages.

Where It Stalls

Nobody compared the old site with the new one before launch. Many old URLs were changed or removed without a redirect to their closest new page, some pages lost the headings and copy that earned their rankings, and the new templates introduced slower loading and missing metadata. Because no baseline of traffic and rankings by page was saved, the team cannot tell which losses are temporary and which are permanent.

Recommended Approach

  • Save a baseline of the old site: every URL, its traffic, its ranking queries and its inbound links, so each loss can be traced to a specific page
  • Map every old URL to its closest new page and set up permanent redirects, then check the list for chains, loops and redirects that land on unrelated pages
  • Compare each lost page with its old version, and restore the headings, copy and internal links that matched what searchers wanted, while keeping the new design
  • Check the new templates for titles, descriptions, canonical tags, indexing directives and page speed, and correct anything the migration changed by accident
  • Track recovery page by page in Search Console for several weeks, and treat any page still missing after the redirects and content are right as an individual problem to investigate

What It Aims to Achieve

A clear map of which pages lost visibility and why, with redirects and content fixed in order of the traffic at stake, so recovery becomes a managed process and the next redesign starts with a baseline and a redirect plan.