Blog
Why Apps
Get Rejected by the App Store and Google Play (and How to Avoid It) – Duplicate – [#33362]
BY: NEURALSCHEMA INFOTECH TEAM ▦ 13 Nov 2026 Introduction
A new website should bring more enquiries, not

Introduction
A new website should bring more enquiries, not fewer. Yet one of the most common stories in web development goes like this: the redesign launches, everyone loves the look, and three weeks later organic traffic has fallen sharply.
The drop is rarely caused by Google punishing a new design. It is almost always caused by something that changed without anyone planning for it: URLs that now return 404 errors, content that was cut, or a staging setting that was never switched off. This checklist walks through a website redesign without losing SEO, from the first planning meeting to eight weeks after launch.

Why websites lose traffic after a redesign
Most post-launch drops trace back to a handful of causes:
Changed URLs with no redirects. Google and every backlink still point to the old address, which now returns “page not found”.
Removed or thinned content. A designer replaces a 1,200-word service page with three short paragraphs and an image.
Lost on-page signals. Page titles, headings, internal links and structured data are not carried over.
Staging settings left live. A noindex tag or robots.txt block from the test site goes into production.
Slower or harder-to-render pages. Heavy scripts and large images make the new site slower than the old one.
Broken tracking. The site is fine, but analytics stopped recording, so it only looks like a drop.
Every step below is designed to prevent one of these.
Know what kind of change you are making
“Redesign” can mean very different things, and the risk rises with every URL you change.
| Type of change | Example | SEO risk |
|---|---|---|
| Visual redesign, same URLs | New theme, same pages and addresses | Low |
| HTTP to HTTPS | http://site.com to https://site.com | Low to medium |
| URL structure change | /services.php?id=4 to /services/seo/ | High |
| CMS or platform change | Custom PHP to WordPress, or WordPress to a headless setup | High |
| Domain change | oldbrand.com to newbrand.in | High |
Google’s own site move guidance warns that combining a move with a redesign of your content and URL structure will probably cause some traffic loss, because Google has to relearn your pages. If you are changing the design, the platform and the domain, consider staging them. When rankings move, you will know which change caused it.
Before design starts: record where you stand
You cannot protect what you have not measured. Do this before the first wireframe.
Export every URL on the current site
Build one master list from several sources, because each one misses something:
- A full crawl using a tool such as Screaming Frog.
- Your XML sitemap.
- The Performance report in Google Search Console, Pages tab (last 16 months).
- Landing pages in Google Analytics 4.
- Pages with external backlinks, from a backlink tool.
Old blog posts, PDF brochures and campaign landing pages often appear in only one of these lists.
Record a performance baseline
Save a snapshot of the numbers you will compare against after launch: clicks and impressions per page from Search Console, leads per page from GA4, and the top queries for your most important pages. If you have not yet set up proper lead events, our guide on how to track website leads covers it.
Also record Core Web Vitals. The current metrics are Largest Contentful Paint (good at 2.5 seconds or less), Interaction to Next Paint (good at 200 milliseconds or less) and Cumulative Layout Shift (good at 0.1 or less). INP replaced First Input Delay as a Core Web Vital on 12 March 2024, as announced on web.dev, so ignore any audit that still reports FID.
Mark the pages you must protect
Flag three groups in your URL list: pages that bring the most organic clicks, pages that produce the most leads, and pages with the strongest backlinks. These pages need special care in design, content and redirects.
During design and development: protect what works
Keep URLs unchanged wherever possible
The safest redirect is the one you never need. If an old URL is clean and descriptive, keep it, even if the new navigation is organised differently.
Design around real content, not placeholder text
Designs built with dummy text tend to leave too little room for the content that ranks. Give the designer your current top pages, with their real headings and word counts, before layouts are approved.
Carry over on-page SEO elements
For every protected page, copy across the page title, meta description, H1, key subheadings, image alt text, internal links, breadcrumbs and structured data (for example Organization, LocalBusiness, Article or Product schema). Improve them if you like, but do not lose them by accident.
Lock the staging site properly
Password-protect the staging site rather than relying only on a noindex tag. Add “remove staging noindex and robots.txt block” to the launch checklist, with a named person responsible.
Make sure Google can see your content
If the new site is a single-page app or uses a headless front end, some content may only appear after JavaScript runs. For pages that need to rank, prefer server-side rendering or static generation, and right after launch use the live test in Search Console’s URL Inspection tool to confirm the main text, links and title appear in the rendered HTML.
Crawl the staging site before launch
About a week before launch, crawl the staging site and run your full old URL list through the redirect rules. Check that every protected page exists, returns a 200 status, keeps its title, H1 and main content, has a canonical tag pointing to itself, and has no stray noindex. Most crawlers, including Screaming Frog, can log in to a password-protected staging site.
Build your 301 redirect map
A redirect map is a spreadsheet with one row per old URL and the single best matching new URL.
| Old URL | New URL | Status code | Notes |
|---|---|---|---|
| /services.php?id=4 | /services/seo/ | 301 | Same topic |
| /our-work.html | /portfolio/ | 301 | Same purpose |
| /blog/2019-offer | /blog/ | 301 | No equivalent; closest relevant section |
| /old-pdf-brochure.pdf | /services/ | 301 | Replaced by web page |
Follow these rules:
- Map like for like. Each old page goes to its closest equivalent, not to the homepage. Google may treat mass redirects to the homepage as soft 404s, and the old page’s value is lost.
- Use permanent redirects. Use 301 or 308 server-side redirects. Google’s redirects documentation explains how each type is treated, and its site move guide confirms that permanent redirects do not cause a loss in PageRank.
- Avoid redirect chains. If page A already redirects to B, and B now moves to C, point A straight to C.
- Keep redirects for a long time. Google’s site move guidance recommends keeping them for at least a year. In practice, keep them indefinitely if old URLs still receive visits. Google’s Change of Address help page gives 180 days as a minimum for domain moves, so treat a year as the floor, not the target.
- Update internal links. Redirects are a safety net. Internal links in menus, footers and body content should point directly to the new URLs.
Launch day checklist
- Take a full backup of the old site and database, and pick a quiet launch day: not during your busiest season and not on a Friday.
- Remove the staging noindex tag and any robots.txt block.
- Switch on redirects and test the full redirect map in bulk, checking each old URL returns a single 301 to the right page.
- Confirm canonical tags point to the new live URLs, not to staging.
- Submit the new XML sitemap in Search Console.
- For a domain change only, use Search Console’s Change of Address tool. It is not needed for HTTPS or path-only changes.
- Check that GA4, Google Tag Manager and every lead event fire on the new site.
- Test key pages on a real mobile phone over 4G, not just on office Wi-Fi.
- Spot-check important pages with Search Console’s URL Inspection tool.
- Test structured data on your key page templates with the Rich Results Test.
- Update the website link in your Google Business Profile, social profiles and directory listings, and the final URLs in any Google Ads campaigns.
- Ask the sites behind your most valuable backlinks to update their links to the new URLs.
The first eight weeks: monitor and fix fast
Some ranking movement after a big change is normal while Google recrawls the site. Google notes that a move is only complete once it has visited every old and new URL at least once, which can take weeks on larger sites. What matters is spotting real problems early.
| Week | What to check |
|---|---|
| Days 1–3 | 404 errors in server logs and Search Console; redirects; lead events firing |
| Weeks 1–2 | Page indexing report for spikes in “Not found” or “Excluded by ‘noindex’ tag”; top pages still indexed |
| Weeks 2–4 | Clicks and impressions for protected pages against your baseline |
| Weeks 4–8 | Core Web Vitals field data; rankings for top queries; leads per page |
Warning signs and what they usually mean
| Symptom | Likely cause | Fix |
|---|---|---|
| Whole site disappearing from Google | Noindex or robots.txt block left live | Remove it, resubmit sitemap, request indexing for key pages |
| One section losing traffic | Missing or wrong redirects for that folder | Audit that part of the redirect map |
| Traffic steady, leads down | Broken forms or tracking, weaker calls to action | Test forms; compare GA4 events with your inbox |
| Slow decline over weeks | Content cut or internal links weakened | Restore depth on key pages; rebuild internal links |
If a sharp drop happens to coincide with a Google update, check whether it is site-wide or tied to specific URLs. Our posts on the March 2026 core update and the August 2026 spam update can help you rule that in or out.
Frequently Asked Questions
It does not have to. Redesigns that keep URLs, content and on-page elements, and that redirect every changed URL properly, usually hold their rankings. Many improve them, because the new site is faster and easier to use.
At least a year, according to Google’s site move guide, and longer if old URLs still get visits or have backlinks pointing to them. There is no SEO benefit in removing them early.
At least a year, according to Google’s site move guide, and longer if old URLs still get visits or have backlinks pointing to them. There is no SEO benefit in removing them early.
Only if you must. Doing both at once makes problems harder to diagnose. If possible, change one first and let it settle.
It helps. An audit tells you which pages and signals are carrying your rankings so you can protect them. See our guide to an SEO website audit for what it covers. If you would like it done for you, see our SEO services in Chennai.
Plan the SEO before you plan the design
A redesign is the best chance you will get to fix speed, structure and content in one go, as long as the SEO work starts on day one rather than the week before launch. Export your URLs, record your baseline, map every redirect and watch the data closely for eight weeks.
If you are planning a rebuild, our website development team builds redirect mapping and SEO checks into every project, and you can browse recent launches in our website portfolio. If the new site needs app-like features, our comparison of React, Angular and Node.js explains the trade-offs. Businesses in Chennai can also see our website development company in Chennai page to plan a rebuild with our local team.
Recent Posts
- Why Apps Get Rejected by the App Store and Google Play (and How to Avoid It) – Duplicate – [#33362]
- Why Apps Get Rejected by the App Store and Google Play (and How to Avoid It)
- How to Choose an IT Company in Chennai: A 6-Point Checklist
- How to Find & Use Multimodal Search Data in GSC (Step-by-Step with Screenshots)
- Google Business Profile Post Views Are Back: What the Number Means for Your Business