Web Development Company in Pune: How to Find and Fix Broken Links, 404 Errors and Redirect Chains on Your Website
You find and fix broken links by crawling your own site, reading Google Search Console's page-indexing report, and then deciding, URL by URL, whether each broken address should be restored, redirected to its closest replacement, or left to return a proper 404. A good web development company in Pune will treat this as routine maintenance rather than an emergency, because broken links quietly cost you enquiries: a visitor who lands on an error page after clicking a Google result or a WhatsApp link rarely tries a second time. This guide explains, in plain language, what each kind of error means, how to audit a business website, and which fixes are safe, so you can check your own site or review the work of whoever maintains it.
It is written for owners of business websites, online stores and NGO sites who have heard terms such as "404", "301" and "redirect chain" and want to know what they mean in practice. We do not quote statistics about how many visitors leave after an error page, because we cannot source a reliable figure. The reasoning below stands without one.
What a 404 actually is, and when it is not a problem
A 404 is the standard web response for "nothing exists at this address." Google's documentation explains that it treats 404 and 410 like other client errors: the content is considered not to exist, an already indexed URL that returns 404 is removed from the index, and Google gradually crawls such URLs less often (Google Search Central: HTTP status codes, network and DNS errors).
That is the first thing to absorb: a 404 on a URL that should not exist is correct behaviour, not a fault. If someone mistypes an address, or an old page you deliberately removed has no replacement, a clean 404 is the honest answer. Search Console will list such URLs, and a long list is not automatically a crisis.
A 404 becomes a problem in three situations:
- The page used to matter. It had traffic, enquiries, backlinks from other sites or links from your own menu, and removing it lost something real.
- You are linking to it yourself. A broken link on your own pages is within your control and signals neglect to visitors.
- The server answers incorrectly. The page looks like an error but the server says everything is fine. This is called a soft 404 and is covered below.
Soft 404s: the error that pretends to be a page
Google defines a soft 404 as a page that returns a success status (a 2xx code) while its content looks like an error, such as an empty page or a "not found" message. Search Console reports these as soft 404 errors (Google Search Central). On business sites we most often see them in three places: a custom "page not found" template that was built as an ordinary page and so returns a success code, an empty category or search-results page, and a product page for a discontinued item that shows a blank layout.
The fix depends on the cause. A genuine error template should return a real 404 status. An empty category should either hold useful content, return a 404, or be redirected if a close replacement exists. Your developer can check the status code of any page in a browser's developer tools (Network tab) or with a command-line request; you do not need to take anyone's word for it.
Redirects in plain language: 301, 302 and why the difference matters
When an address changes, a redirect tells browsers and search engines where the page went. Google's documentation separates them into permanent and temporary types. Permanent redirects (HTTP 301 and 308) tell Google to show the new target in search results; temporary redirects (302, 303 and 307) tell it to keep showing the source page. Google also notes that JavaScript redirects are a less reliable option, to be used only when server-side or meta refresh redirects are not possible (Google Search Central: Redirects and Google Search).
In practice this gives a simple rule:
- Page moved for good (new URL structure, renamed service, merged pages): use a permanent redirect.
- Page moved for a short, defined time (a seasonal landing page, maintenance): use a temporary redirect, and remove it when the period ends.
- Page gone with no replacement: do not redirect to the home page "to be safe." Let it return a 404 or 410.
Why redirecting everything to the home page is a bad habit
It is tempting to send every dead URL to the home page so that the error report looks clean. This usually hurts. A visitor who clicked a link about a specific service lands on a general page and has to start over. Search engines may also treat a redirect to an unrelated page as a soft 404, because the destination does not match what the old URL offered. A redirect is a promise that the new page is a genuine replacement; keep that promise or do not make it.
Redirect chains and loops
A chain happens when A redirects to B, which redirects to C. It usually builds up over years: a site is moved to HTTPS, then to a new domain version with or without "www", then a redesign changes the URL structure, and each step added a redirect on top of the last. Every extra hop adds a round trip before the visitor sees anything, and it makes the setup harder to maintain. The cure is to point every old address straight at the final destination.
A loop is worse: A redirects to B and B redirects back to A, so the browser gives up with an error. Loops often appear after a plugin change, a clash between a hosting-level rule and a WordPress setting, or an HTTPS redirect configured in two places. They need immediate attention.
Where broken links come from on a typical Pune business site
Knowing the sources makes the audit faster. These are the patterns we see most often on business, store and NGO websites, described generally rather than as client figures:
- Redesigns and migrations. A new site launches with new URLs, and the old ones are not mapped. This is the single biggest source of mass 404s. Our guide on migrating a website without losing SEO rankings covers how to prevent it.
- Renamed or deleted pages. Someone edits a page title and the address changes with it, or a page is deleted without a note to anyone.
- Expired external links. Pages you link to, such as a government notice, a partner's page or a news article, move or disappear.
- Media and file links. A PDF brochure, a price list or an image is replaced and the old file path stops working. This is common on NGO sites that link annual reports and receipts.
- Typos in hand-entered links. A missing letter in an address, or a link that points to a staging or test domain that was never updated.
- Old campaign and QR code destinations. A printed flyer, a WhatsApp broadcast or a QR code points to a landing page that was later removed. These cannot be edited once printed, so the redirect must live on the website.
- Platform changes. Switching from one e-commerce or CMS platform to another changes URL patterns, for example product and category paths.
How to audit your site: a practical workflow
You do not need expensive tools for a first pass. The workflow below combines free sources with one crawler.
Step 1: Read Google Search Console
In Search Console, open the Pages (page indexing) report and look at the reasons pages are not indexed. Entries such as "Not found (404)", "Soft 404", "Page with redirect" and "Redirect error" are the ones relevant here. Open each reason and look at example URLs. Ask three questions of each group: did this page ever matter, is anything still linking to it, and is the status Google sees the one we intended?
Search Console reports what Google found, so it is the best guide to which broken addresses are visible to search. It will not list every broken link inside your own pages, which is why the next step matters.
Step 2: Crawl the site yourself
Run a crawler over your site. Desktop tools such as Screaming Frog SEO Spider have a free tier with a limit on the number of URLs, and several other crawlers work similarly. A crawl gives you, for every URL, the status code, the page that linked to it, and any redirect path. Export three views:
- every internal link that leads to a 404 or other error;
- every internal link that leads to a redirect (these should be updated to point directly at the final address);
- every redirect chain with more than one hop.
Also check external links. Pages you cite elsewhere will rot over time, and a few broken outbound links are normal, but your key resources should be checked at least twice a year.
Step 3: Check your own analytics
Your analytics data can show you which error pages real visitors reach. If you use GA4, create a report or exploration filtered on page titles that contain the wording of your 404 template, then look at the landing page and previous page or source. A broken address that receives visits from a Google result, an old email or a printed QR code deserves a fix before one nobody visits.
Step 4: Check server logs if you can
Hosting control panels often provide raw access logs. These show every request, including from search bots, and reveal repeated hits on dead URLs that neither Search Console nor a crawl surfaces. This is a technical step; ask your developer or host for help, and do not worry if your plan does not include it.
Step 5: Test the 404 page itself
Type a nonsense address after your domain. You should see a branded, helpful page, and the server should return a 404 status code, not 200. Test it on mobile, too.
Deciding what to do with each broken URL
Triage prevents wasted effort. For each group of broken URLs, choose one action.
| Situation | Best action |
|---|---|
| Page was moved or renamed, and a close replacement exists | Permanent redirect to the replacement |
| Page was merged into another | Permanent redirect to the merged page |
| Page had real traffic or backlinks, content still relevant | Restore it, or redirect to the nearest equivalent |
| Page removed deliberately, no equivalent | Leave as 404 or 410, remove internal links to it |
| Page is a temporary landing page, may return | Temporary redirect while it is off, remove afterwards |
| Internal link points to a redirect | Update the link to the final address |
| Link to an external page that is gone | Replace with a current source or remove the link |
| Soft 404 | Return a real 404, add content, or redirect to a true equivalent |
A sensible rule: fix links you control first, then redirect addresses you do not control. Updating the internal link removes the problem at its source and avoids the need for a redirect altogether.
Building a redirect map that you can maintain
For any site with more than a handful of changes, keep the redirect rules in a single spreadsheet with four columns: old URL, new URL, reason, and date added. This sheet is the most valuable record you can hand a future developer. It prevents duplicate or conflicting rules and shows when a temporary rule should be removed.
A few practices keep the map healthy:
- Match one-to-one where possible. Each old page should go to its closest equivalent, not a generic bucket.
- Point at final destinations. Before adding a rule, check where the target itself goes now.
- Keep one place for rules. Choose whether redirects live in the server configuration, a WordPress redirect plugin, the e-commerce platform's own redirect manager, or an edge or CDN rule, and do not split them across several without a reason. Conflicting layers cause most loops.
- Normalise address variants once. Decide on HTTPS, with or without "www", and a consistent trailing-slash style, and redirect everything else to that one form in a single step.
- Test after every release. After a theme change or plugin update, re-test a sample of old URLs.
On WordPress, a redirect plugin can be adequate for a few hundred rules, though a very large list is better handled at the server level for speed. On Shopify, the platform has a built-in URL redirects tool that your team can use without code. WooCommerce stores usually combine WordPress redirect handling with care over product and category slugs. These notes are general; the right choice depends on your hosting and setup.
Designing a 404 page that helps instead of dead-ending
Since some 404s are inevitable, make them useful. A good error page has a clear plain-language message ("We could not find that page"), the main navigation so visitors can continue, a search box if your site has more than a few pages, links to your most important pages, and a visible way to contact you, such as a phone number or WhatsApp link. For a store, link to categories and a few popular products. For an NGO, link to the donation page and the latest campaign.
Keep it light. Do not load heavy scripts or large images just for an error page, do not trap visitors with pop-ups, and avoid humour that could look flippant on a sensitive site, such as a healthcare practice or a charity. Finally, make sure the page returns a genuine 404 status, as discussed above, so that search engines understand it.
Special cases worth knowing about
E-commerce stores: discontinued and out-of-stock products
Products come and go, and the right handling depends on why. If an item is temporarily out of stock, keep the page live and say so. If it is permanently discontinued and a close substitute exists, a permanent redirect to the substitute or its category is reasonable. If there is no substitute, a 404 or 410 is honest. Avoid sending many discontinued products to the home page. Our guides on keeping sold-out pages useful and on site structure and sitemap planning go into related decisions.
NGO websites: reports, receipts and campaign pages
NGO sites often link to annual reports, audited statements and campaign pages that change each year. Use stable, descriptive addresses for evergreen documents, and keep old campaign pages live with a short "this campaign has ended" note rather than deleting them, if donors or partners may still arrive via old links. Receipt and donor links sent by email or WhatsApp must keep working, since the donor cannot be told to update them.
Multilingual and multi-location sites
If you publish pages in more than one language or for several branches, check that links in one language version do not point to the other by mistake, and that removing a page in one version does not leave dangling links from the other.
After a domain or platform change
Plan the redirect map before launch, keep it in place long enough for search engines and returning visitors to adapt, and monitor Search Console for new errors. Do not remove redirects after a few weeks simply because they "look old"; an external link from another website will keep sending people to the old address for as long as it exists.
A worked example (hypothetical)
Consider a made-up Pune interior design studio with a 60-page WordPress site. After a redesign a year ago, it renamed "Services" pages and merged "Kitchens" and "Wardrobes" into "Modular Interiors." Search Console now lists 48 not-found URLs and 6 redirect errors. A crawl shows 35 internal links that point at old addresses, 9 redirect chains of two or three hops, and a "page not found" template that returns a success code.
A sensible plan would be:
- Update the 35 internal links to the final addresses first, since that removes much of the noise.
- Create a one-to-one redirect for each old service page with a real replacement, and send the two merged pages to "Modular Interiors."
- Collapse the 9 chains so each old address goes directly to its final page.
- Fix the 404 template so that it returns a true 404 status, and add navigation and a WhatsApp link.
- Leave about a dozen old URLs, with no traffic and no replacement, as plain 404s.
- Re-crawl, then watch Search Console over the following weeks.
The numbers are invented to illustrate the process; they are not results from a real project.
Common mistakes to avoid
- Redirecting every 404 to the home page.
- Using a temporary redirect for a permanent move.
- Leaving chains and loops after multiple migrations.
- Using JavaScript or meta refresh redirects when a server-side redirect was possible.
- Fixing the error report instead of the cause.
- Deleting pages without checking analytics and backlinks first.
- Forgetting printed materials, emails and QR codes that cannot be edited.
- Blocking old URLs in robots.txt, which stops search engines from seeing the redirect at all.
- Never re-testing after a theme, plugin or platform update.
Questions to ask your web development company in Pune
- How often do you crawl our site for broken links and redirect chains, and can we see the last report?
- Where do our redirect rules live, and is there a written redirect map?
- What happens to old URLs when we launch a redesign?
- Does our 404 page return a true 404 status code?
- Who monitors Search Console for new errors, and how quickly do we hear about problems?
- Is this work included in our maintenance plan, or billed separately?
Our overview of what a maintenance plan should include can help you check the answers.
Working with Govindani Infotech on link and redirect clean-ups
Govindani Infotech is a Pune-based website design and development company at 2nd Floor, Landmark Plaza, 206 Satara Road, Parvati Paytha, Pune 411009. We build and maintain business websites, e-commerce stores and NGO donation platforms, and link and redirect hygiene is part of how we hand over a build.
If you suspect your site has accumulated broken links, send us your domain and platform and we will explain, before any price is discussed, what a crawl and Search Console review would look at. For related work, see our website creation and SEO pages. You can message us on WhatsApp at wa.me/919201958278 or write through our contact page.
Related: moving to a new domain or URL structure? See our guide to changing your domain or moving to HTTPS without losing Google rankings.
Frequently Asked Questions
Do 404 errors hurt my Google rankings?
A 404 on a page that should not exist does not by itself harm the rest of your site; Google treats it as content that does not exist and drops it from the index. The harm comes from losing a page that mattered, from broken internal links that frustrate visitors, and from soft 404s that waste crawling.
Should I redirect all 404 pages to my home page?
No. Redirect a page only if there is a close, relevant replacement. Sending unrelated URLs to the home page confuses visitors and can be treated as a soft 404. Let genuinely removed pages return a proper 404 or 410.
What is the difference between a 301 and a 302 redirect?
A 301 is a permanent redirect, so search engines show the new address. A 302 is temporary, so search engines keep showing the original. Use 301 for permanent moves and 302 only when the change will be reversed.
What is a redirect chain and why should I fix it?
A chain is a sequence such as A to B to C. Each extra hop delays the visitor and makes the setup harder to maintain. Point each old address directly at its final destination.
How often should I check my website for broken links?
For most business sites, a crawl after every redesign or large content change and a routine check every quarter is sensible, with Search Console reviewed monthly. Busy stores and sites that publish frequently may check more often.
Sources: Google Search Central: HTTP status codes, network and DNS errors, Google Search Central: Redirects and Google Search.