Scroll Top

Why Traffic Dropped After A Website Redesign

Updated September 2026 · Written and maintained by the Progression Agency strategy team

Post-redesign traffic losses have a short list of causes and most are fixable within the new design rather than by reverting it. This page covers redirects first because they account for more losses than everything else combined, then indexing directives left from staging, content trimmed for appearance, weakened internal linking, rendering dependencies that hide content from crawlers, broken analytics that make traffic look lost when it is not, and what normal recovery actually looks like.

The short answerCheck three things before anything else, and all three take minutes. Request twenty of your highest-traffic old URLs and confirm each returns a permanent redirect to its actual equivalent — redirecting everything to the homepage looks like diligence and preserves almost nothing. Check for a robots disallow or a noindex left over from staging, which produces disappearance rather than decline. And confirm analytics still fires on every template, because broken measurement makes traffic look lost when it never left.

Check in this order

Redirects are the first thing to check and the most common cause

If URLs changed and old addresses were not permanently redirected to their new equivalents, every accumulated signal attached to those addresses is lost. This single omission accounts for more post-redesign traffic collapses than everything else combined.

Test it directly rather than trusting the launch checklist. Take twenty of the old URLs that previously received the most traffic, request each one, and record what comes back. Each should return a permanent redirect to the page that replaced it. A page that returns not-found has lost everything, and one that redirects to the homepage has lost nearly as much, because the homepage does not answer the query the old page ranked for.

The homepage-redirect pattern is worth calling out because it looks like diligence. Somebody redirected everything rather than nothing, which prevents error pages and preserves almost no relevance. Each old URL needs its closest actual equivalent.

What each redirect outcome costs you
Old URL returnsSignal preservedVerdict
Permanent redirect to the equivalent pageNearly allCorrect
Permanent redirect to the homepageVery littleLooks done, is not
Temporary redirectAmbiguous, may not consolidateChange it to permanent
Not foundNoneThe worst case, and common
Redirect chain through several hopsDegradedPoint directly at the destination
Redirect loopNone, and the page is unreachableBreaks for visitors too

Check whether the new site is being blocked entirely

A staging environment carries directives that prevent search engines indexing it, and those directives are supposed to be removed at launch. Frequently they are not.

Two mechanisms cause this and they need checking separately. A robots file that disallows crawling, and a noindex directive in the page markup or headers. The second is more dangerous because it is invisible in the robots file and can sit in a template applied to every page.

This produces a total collapse rather than a decline, usually within days to a couple of weeks as pages are recrawled and dropped. If traffic did not decline so much as stop, check this before anything else — it takes two minutes and is the difference between a fixable oversight and weeks of misdirected analysis.

Robots disallow — Left from staging. One request to check..
Noindex in markup — Invisible in robots. Can sit in a template..
Noindex header — Server-level. Checked separately again..
Password protection — Staging habit. Blocks everything..
Sitemap listing old URLs — Slows discovery. Resubmit the new one..
Canonical pointing at staging — Copied across. Sends signals elsewhere..

Check the robots file first

It is one request and rules out the simplest total blocker.

Then check for noindex in the markup and headers

It can be applied by a template or a plugin setting and is not visible in the robots file.

Check index coverage reporting

It will name the reason pages were excluded rather than leaving you to infer it.

Confirm the sitemap points at the new URLs

A sitemap still listing the old structure slows discovery of the new one considerably.

Content removed during a redesign takes its rankings with it

Redesigns almost always reduce the amount of text on a site, because long pages look cluttered in a design review and the person deciding is looking at appearance rather than at what each paragraph was earning.

The pattern is consistent: explanatory sections cut for visual balance, frequently asked questions removed as unattractive, detailed service descriptions condensed into a sentence, and blog archives dropped because they looked dated. Each of those was matching queries that the new version no longer matches.

Compare a sample of important pages before and after. If the replacement covers materially less ground, that is the explanation, and the fix is to reinstate the substance within the new design rather than to revert the design.

Internal linking usually gets quietly rebuilt and weakened

Navigation redesigns change which pages link to which, and this is rarely considered as a search consequence at the time.

A simplified menu removes links to pages that were previously one click from the homepage. Contextual links inside body content disappear when that content is rewritten. Footer link blocks get tidied away. The result is pages that are still present, still indexed, and no longer supported by anything, which is a slow decline rather than a sudden one.

Check how many internal links point to your most important pages now against before. This is among the cheapest things to fix and is almost never on a launch checklist.

What changes in a redesign, and what it costs
ChangeSearch consequenceUsually noticed
URLs changed, no redirectsAll accumulated signal lostWithin two weeks
Content trimmed for appearanceQueries no longer matchedOne to two months
Navigation simplifiedDeep pages lose supportTwo to three months
Titles rewritten for brandRelevance to queries reducedWeeks
Images replaced without alt textImage search traffic lostOften never
Page speed regressionConversion falls, ranking slightlyImmediately, if measured
Internal linking before and after, on one page
Source of linksTypical beforeTypical after a redesign
Main navigationDirect link from every pageRemoved in a simplified menu
Contextual body linksSeveral from related articlesLost when copy is rewritten
Footer blocksSite-wide supportTidied away for visual reasons
Category or hub pagesGrouped and linkedOften removed entirely
BreadcrumbsConsistent hierarchyDropped as visual clutter

Rendering changes can hide your content from crawlers

Modern rebuilds frequently move content into JavaScript that assembles the page in the browser. The page looks identical to a visitor and can return almost nothing to a crawler.

The test is to fetch the raw HTML of an important page and search it for a distinctive sentence you can see on screen. If the sentence is not in the source, the content depends on rendering, and whether it gets indexed becomes uncertain rather than assured.

This is a genuine and increasingly common cause of post-rebuild decline, and it is invisible to anyone checking the site in a browser — which is everyone reviewing a redesign.

Normal versus not normal
Shape matters more than magnitude when deciding whether to act.

Titles and headings rewritten for the brand rather than the query

Redesigns are usually accompanied by a copy refresh, and copy refreshes are usually judged on tone rather than on relevance.

The specific damage is titles that previously named what the page was about being replaced with something more evocative. A page titled for what people search becomes a page titled for how the brand wishes to sound, and its match to the query weakens accordingly.

This does not mean titles must be mechanical. It means the words people actually use should survive the rewrite. Where a brand voice and a search term genuinely conflict, the page can carry both — one in the title, one in the first heading.

Give it time, but know what normal looks like

Some volatility after a migration is expected, and reacting to the first fortnight causes people to change things that were about to recover on their own.

The normal pattern where a migration was done correctly is a modest dip for two to four weeks as pages are recrawled and signals reconsolidate, followed by recovery to roughly the previous level. What is not normal is a decline that deepens after a month, a complete disappearance within days, or specific important pages vanishing while the rest are unaffected.

Distinguishing the two is mostly a matter of shape. Recovery that has begun looks like recovery even when the numbers are still down; a decline that is still deepening at week six is not going to resolve itself.

Two to four weeks of dip is normal

With a correctly executed migration, and it should be visibly recovering by the end of it.

Deepening after a month is not

That is an unresolved fault rather than reconsolidation, and waiting longer will not help.

Total disappearance within days is a blocker

Check indexing directives immediately rather than attributing it to migration volatility.

Page-specific losses point at those pages

Site-wide causes produce site-wide effects. If three pages fell and the rest held, look at those three.

Rebuild the measurement before you interpret it

A redesign frequently breaks analytics, and comparing broken measurement against previous data produces conclusions about a decline that may be partly or wholly artificial.

Confirm the analytics tag is present on every template, that conversion tracking still fires, that filters and exclusions carried across, and that the new URL structure has not fragmented what were previously single pages into several reported entries. Each of these makes traffic appear lower than it is.

Where the tag was missing for a period, mark that period rather than treating it as data. Interpreting a measurement gap as a traffic loss is a common and avoidable error in exactly this situation.

Recovery expectations by cause
CauseRecovers inRequires
Indexing directive left from stagingDays to two weeksRemoving it, then recrawl
Missing redirectsTwo to six weeksMapping every old URL to its equivalent
Analytics brokenImmediately once fixedNothing but the fix; the traffic never left
Content removedOne to three monthsReinstating substance within the new design
Internal links weakenedThree to eight weeksRestoring links to important pages
Rendering dependencyWeeks after resolutionServer rendering or pre-rendering

A checklist for the next one

Most of this is preventable, and the prevention is short enough to fit on one page.

Before launch: export the current URL list with traffic attached, map every URL to its replacement, record current rankings and traffic for the top pages, and note the word count and internal link count of important pages so the comparison is possible afterwards.

At launch: verify indexing directives are removed, test the redirect map, submit the new sitemap, confirm analytics fires on every template, and fetch the raw HTML of three important pages to confirm the content is in the source. That list takes an afternoon and prevents almost everything described above.

Export URLs with traffic — Before launch. You cannot compare later otherwise..
Map every URL — To its closest equivalent. Not to the homepage..
Record rankings and traffic — Top pages. The baseline..
Note word and link counts — Important pages. Proves what was cut..
Test redirects at launch — Not before. Staging redirects are not live ones..
Fetch raw HTML — Three key pages. Confirms content is in the source..

Reference videos

Search and measurement fundamentals relevant to the checks above.

Paid media and lead generation

Frequently asked questions

Why did my traffic drop after a website redesign?
Most often because URLs changed without permanent redirects to their equivalents, which loses every signal attached to the old addresses. After that: an indexing directive left over from staging, content trimmed for visual reasons, weakened internal linking, or analytics that broke and is under-reporting traffic that never actually left.
How do I check whether my redirects were done properly?
Take the twenty old URLs that previously received the most traffic and request each one. Each should return a permanent redirect to the page that replaced it. Redirecting everything to the homepage looks like diligence and preserves almost nothing.
Is it normal for traffic to drop after a redesign?
A modest dip for two to four weeks is normal while pages are recrawled and signals reconsolidate, and it should be visibly recovering by the end of that. A decline still deepening at week six is an unresolved fault, not volatility.
My site disappeared from search completely after launch. What happened?
Check indexing directives immediately. A robots file disallowing crawling or a noindex directive left over from staging produces exactly this, usually within days. The noindex version is more dangerous because it is invisible in the robots file and can sit in a template.
Can removing content cause a ranking drop?
Yes, and redesigns almost always remove content because long pages look cluttered in a design review. Explanatory sections, FAQs and detailed descriptions were each matching queries the shorter version no longer matches.
How long should I wait before acting on a post-redesign drop?
Check for blockers and broken redirects immediately — those are faults, not volatility. For everything else, two to four weeks. If the decline is deepening rather than recovering by then, waiting longer will not help.
Does redirecting old pages to the homepage work?
It prevents error pages and preserves very little relevance, because the homepage does not answer the query the old page ranked for. Each old URL needs its closest actual equivalent.
Why do my pages look fine but rank worse?
Possibly a rendering dependency: content assembled by JavaScript in the browser looks identical to a visitor and can return almost nothing to a crawler. Fetch the raw HTML and search it for a sentence you can see on screen.
Could my analytics be wrong rather than my traffic being down?
Frequently. Redesigns break tags, drop conversion tracking, lose filters, and fragment single pages into several reported URLs. Confirm the tag fires on every template before interpreting any comparison.
Should I revert the redesign?
Almost never, and rarely possible cleanly. The usual causes — redirects, indexing directives, removed content, weakened linking — are fixable within the new design, and reverting adds a second migration with its own losses.
What is a redirect chain and why does it matter?
An old URL redirecting to another redirect before reaching the destination. Each hop degrades the signal passed and slows crawling. Point every old URL directly at its final destination instead.
Why did only some pages lose traffic?
Page-specific losses point at those pages rather than at the site: they were removed, redirected incorrectly, had content cut, or lost the internal links that supported them. Site-wide causes produce site-wide effects.
Do title changes affect rankings?
They can, particularly when a copy refresh replaces titles that named what a page was about with something more evocative. The words people actually search should survive a rewrite, even if the brand voice appears alongside them.
How does internal linking get damaged in a redesign?
A simplified menu removes links to pages that were one click from the homepage, contextual links vanish when body content is rewritten, and footer blocks get tidied away. The pages remain indexed but unsupported, which produces a slow decline.
How long does recovery take once the cause is fixed?
Indexing directives, days to two weeks. Redirects, two to six weeks. Broken analytics, immediately, since the traffic never left. Removed content and weakened links, one to three months.
Should I resubmit my sitemap after a redesign?
Yes, and confirm it lists the new URLs rather than the old structure. A stale sitemap slows discovery of the new pages considerably at exactly the point you need it to be fast.
What should I record before a redesign?
The current URL list with traffic attached, a map of every URL to its replacement, current rankings and traffic for top pages, and the word and internal link counts of important pages so an after-comparison is possible at all.
Can page speed changes cause this?
Speed affects conversion more than ranking, so a speed regression will usually cost you inquiries before it costs you positions. It rarely explains a sharp ranking fall on its own, though it commonly accompanies a redesign that caused one for other reasons.
Is a drop in image search traffic worth worrying about?
It is worth checking, because replacing images without carrying over alt text and filenames removes that traffic entirely and it is the loss least likely to be noticed, since few people report on it separately.
What is the single most preventable cause?
Missing or lazy redirects. Mapping every old URL to its closest equivalent takes an afternoon before launch and prevents the largest single category of post-redesign loss.

Sources and further reading

  1. Google Search Essentials — SEO starter guide
  2. Google: creating helpful, reliable, people-first content
  3. Google: intro to structured data
  4. Google: LocalBusiness structured data
  5. Google: FAQPage structured data
  6. Google: Article structured data
  7. Google: Product structured data
  8. Google: title links in search results
  9. Google: control your snippets
  10. Google: robots.txt introduction
  11. Google: sitemaps overview
  12. Google: consolidate duplicate URLs
  13. Google: redirects and Search
  14. Google: JavaScript SEO basics
  15. Google: multi-regional and multilingual sites
  16. Google Search Central Blog
  17. Google: get started with Search Console
  18. Google: how local search results are determined
  19. Google Business Profile: prohibited and restricted content
  20. Google Business Profile: address and service area guidelines
  21. Google Business Profile: review policy
  22. Google Business Profile: add or edit categories
  23. Google Ads: location targeting settings
  24. Google Ads: about negative keywords
  25. Google Ads: about Quality Score
  26. Google Ads: importing offline conversions
  27. Google Ads: about Smart Bidding
  28. Google Ads: about Performance Max
  29. Google Local Services Ads: eligibility and screening
  30. Google Ads: keyword match types
  31. Google Analytics 4: about conversions
  32. Google Analytics 4: attribution models
  33. US Census Bureau QuickFacts: New Jersey
  34. US Census Bureau: American Community Survey
  35. US Census: Statistics of US Businesses
  36. Bureau of Labor Statistics: New Jersey data
  37. BLS: Occupational Employment and Wage Statistics
  38. NJ Department of Labor: labor market information
  39. New Jersey Business Action Center
  40. US Small Business Administration: New Jersey district
  41. USA.gov: business resources
  42. web.dev: Core Web Vitals explained
  43. web.dev: Largest Contentful Paint
  44. web.dev: Cumulative Layout Shift
  45. web.dev: Interaction to Next Paint
  46. Google PageSpeed Insights
  47. Google Rich Results Test
  48. Google Search Console
  49. W3C Markup Validation Service
  50. Schema.org: LocalBusiness type
  51. Schema.org: Service type
  52. Schema.org: FAQPage type
  53. Schema.org: HowTo type
  54. W3C: WCAG 2.2 quick reference
  55. FTC: CAN-SPAM Act compliance guide
  56. FCC: telemarketing and robocall rules (TCPA)
  57. FTC endorsement guides — reviews and testimonials
  58. FTC: rule on consumer reviews and testimonials
  59. HHS: HIPAA guidance on online tracking technologies
  60. New Jersey Courts: attorney advertising guidelines
  61. New Jersey DCA: construction codes and permits
  62. New Jersey Home Improvement Contractor registration
  63. New Jersey Division of Consumer Affairs
  64. TikTok for Business
  65. TikTok Creative Center
  66. TikTok Ads Help Center
  67. TikTok Community Guidelines
  68. TikTok Terms of Service
  69. TikTok Privacy Policy
  70. TikTok Safety Center
  71. TikTok Transparency Center
  72. TikTok Creator Portal
  73. TikTok Newsroom
  74. TikTok for Developers
  75. TikTok advertising solutions
  76. TikTok Creator Marketplace
  77. TikTok Business Center
  78. TikTok for Business blog
  79. TikTok Creative Center: top ads
  80. TikTok Branded Content policy
  81. TikTok Shop for sellers
  82. Instagram for Business
  83. Instagram for Creators
  84. Instagram Help Center
  85. About Instagram
  86. Meta Business Suite
  87. Meta Business Help Center
  88. Meta Transparency Center
  89. About Meta
  90. Meta: Instagram platform docs
  91. YouTube Creators
  92. YouTube Official Blog
  93. YouTube Shorts help
  94. How YouTube Works
  95. YouTube Studio
  96. LinkedIn Marketing Solutions
  97. LinkedIn Help
  98. Pinterest Business
  99. Pinterest Business Help
  100. Snapchat for Business
  101. X for Business
  102. Reddit communities
  103. Reddit for Business Help
  104. ASCAP
  105. BMI
  106. SESAC
  107. Global Music Rights
  108. PRS for Music (UK)
  109. PPL (UK)
  110. SOCAN (Canada)
  111. APRA AMCOS (Australia)
  112. GEMA (Germany)
  113. SACEM (France)
  114. SIAE (Italy)
  115. JASRAC (Japan)
  116. IFPI
  117. RIAA
  118. National Music Publishers Association
  119. Harry Fox Agency
  120. SoundExchange
  121. Music Reports
  122. Epidemic Sound
  123. Artlist
  124. Soundstripe
  125. PremiumBeat
  126. AudioJungle
  127. Free Music Archive
  128. Creative Commons
  129. Incompetech
  130. FTC: advertising and marketing
  131. FTC: disclosures 101
  132. FTC: endorsement guides
  133. FTC: consumer reviews rule
  134. FTC: advertising FAQs
  135. US Copyright Office
  136. US Copyright Office: DMCA
  137. US Copyright Office: music FAQ
  138. US Copyright Office: fair use FAQ
  139. USPTO: trademarks
  140. UK Advertising Standards Authority
  141. ACCC (Australia)
  142. Competition Bureau Canada
  143. GDPR overview
  144. California Consumer Privacy Act
  145. COPPA
  146. FTC: children’s privacy
  147. W3C Web Accessibility Initiative
  148. W3C: WCAG
  149. W3C: captions
  150. W3C: making audio and video accessible
  151. ADA.gov
  152. WebAIM
  153. Epilepsy Foundation
  154. Pew Research: internet and technology
  155. DataReportal
  156. US Census Bureau
  157. US Bureau of Labor Statistics
  158. Interactive Advertising Bureau
  159. Think with Google
  160. Google Trends
  161. Nielsen insights
  162. Schema.org: VideoObject
  163. Schema.org: SocialMediaPosting
  164. Schema.org: MusicRecording
  165. Schema.org: HowTo
  166. Schema.org: FAQPage
  167. Schema.org: Organization
  168. Google: video best practices
  169. Google: video structured data
  170. CapCut
  171. Adobe Premiere Rush
  172. DaVinci Resolve
  173. Canva
  174. Descript
  175. VEED
  176. Kapwing
  177. Otter.ai
  178. Later
  179. Buffer
  180. Hootsuite
  181. Sprout Social
  182. Google Analytics
  183. Google Search Console
  184. Google Analytics developer docs
  185. GA4: events and conversions
  186. Matomo
  187. Plausible Analytics
  188. Similarweb
  189. UK Information Commissioner’s Office
  190. Office of the Privacy Commissioner of Canada
  191. Australian OAIC
  192. European Data Protection Board
  193. EU data protection
  194. EU Digital Services Act
  195. Ofcom
  196. FCC
  197. AIGA
  198. Nielsen Norman Group
  199. Smashing Magazine
  200. web.dev
  201. MDN: web media
  202. MDN: the video element
  203. ISO 21001 (reference)
  204. Buma/Stemra (Netherlands)
  205. STIM (Sweden)
  206. Teosto (Finland)
  207. Koda (Denmark)
  208. TONO (Norway)
  209. IMRO (Ireland)
  210. SGAE (Spain)
  211. ZAiKS (Poland)
  212. KOMCA (South Korea)
  213. MCSC (China)
  214. CISAC
  215. World Intellectual Property Organization
  216. TikTok: creating videos
  217. TikTok: exploring videos
  218. TikTok: privacy settings
  219. TikTok: growing your audience
  220. TikTok Creator Academy
  221. TikTok Effect House
  222. TikTok for small business
  223. Instagram: Reels help
  224. YouTube: Shorts best practice
  225. How YouTube recommends
  226. Pinterest Predicts
  227. Snapchat for Business
  228. Hootsuite blog
  229. Social Media Examiner
  230. Marketing Week
  231. Adweek
  232. Google Search Essentials — SEO starter guide
  233. Google: creating helpful, reliable, people-first content
  234. Google: intro to structured data
  235. Google: LocalBusiness structured data
  236. Google: FAQPage structured data
  237. Google: Article structured data
  238. Google: Product structured data
  239. Google: title links in search results
  240. Google: control your snippets
  241. Google: robots.txt introduction
  242. Google: sitemaps overview
  243. Google: consolidate duplicate URLs
  244. Google: redirects and Search
  245. Google: JavaScript SEO basics
  246. Google: multi-regional and multilingual sites
  247. Google Search Central Blog
  248. Google: get started with Search Console
  249. Google: how local search results are determined
  250. Google Business Profile: prohibited and restricted content
  251. Google Business Profile: address and service area guidelines
  252. Google Business Profile: review policy
  253. Google Business Profile: add or edit categories
  254. web.dev: Core Web Vitals explained
  255. web.dev: Largest Contentful Paint
  256. web.dev: Cumulative Layout Shift
  257. web.dev: Interaction to Next Paint
  258. Google PageSpeed Insights
  259. Google Rich Results Test
  260. Google Search Console
  261. W3C Markup Validation Service
  262. Schema.org: LocalBusiness type
  263. Schema.org: Service type
  264. Schema.org: FAQPage type
  265. Schema.org: HowTo type
  266. W3C: WCAG 2.2 quick reference
  267. US Census Bureau QuickFacts: New Jersey
  268. US Census Bureau: American Community Survey
  269. US Census: Statistics of US Businesses
  270. Bureau of Labor Statistics: New Jersey data
  271. BLS: Occupational Employment and Wage Statistics
  272. NJ Department of Labor: labor market information
  273. New Jersey Business Action Center
  274. US Small Business Administration: New Jersey district
  275. USA.gov: business resources

Get a free marketing proposal

Tell us what you are trying to grow and we will come back with a plan, not a pitch deck. Same-day reply on weekdays.

Privacy Preferences
When you visit our website, it may store information through your browser from specific services, usually in form of cookies. Here you can change your privacy preferences. Please note that blocking some types of cookies may impact your experience on our website and the services we offer.