Create a custom 301 redirect map for a site restructure
A site restructure changes more than the menus and folders behind a website. Existing pages acquire new paths, service pages merge, and campaign material may disappear. A custom 301 redirect map records where each old URL should lead, helping visitors reach the right content while search engines understand that the move is permanent. The map is the decision layer behind the redirects, not a list of untested guesses.
For Australian businesses, the map should reflect the way the local market searches. A .com.au or .au domain, Google Search Console, and city-focused pages for Melbourne, Sydney, or Brisbane can all shape the migration. A national service company may also have local landing pages that need distinct destinations rather than one catch-all homepage redirect. Mapping every relevant page individually keeps local intent intact.
Users arrive through links they did not create: search results, email campaigns, social posts, printed brochures, and old referring websites. One of the most useful planning questions is not simply where a page moved, but what someone expected to find there. That answer guides a one-to-one redirect, a sensible category destination, or a clear removal response when no matching page exists.
Customisation also means accounting for Australian spelling, AUD prices, and pages explaining the 10% GST without carrying outdated wording into a new location. At 2 Geeks Web Design, this disciplined map gives developers, content teams, and the business owner one shared reference. It also makes post-launch checks possible, protects referring traffic, and prevents a routine restructure from becoming a trail of broken links and organic search losses.
Audit the current site before choosing destinations
Begin with a full URL inventory, not with the proposed new menu. Crawl the existing site and export every indexable URL, then combine that list with analytics, Search Console, the XML sitemap, and a backlink export. Spreadsheet, CMS, or database exports can reveal pages missing from navigation. Record the current response, traffic, useful incoming links, and whether each URL has business value; a low-traffic service page may still attract links.
Next, classify each source page by intent. Label it as a direct move, a slug change, a consolidation, a temporary campaign, or a page with no worthwhile replacement. Capture why each decision exists, including the page owner and any dependencies on forms, analytics events, or linked documents. This prevents two people from sending the same old URL to competing destinations during implementation.
Retain useful destination URLs where possible. If a page currently ranks or earns links, changing its path creates avoidable work and risk. For a .com.au site with pages for Melbourne, Sydney, and Brisbane, keep those locations distinct and map each to its closest relevant service page. When there is no honest equivalent, preserve the old URL as a controlled 410 response rather than redirecting it to an irrelevant homepage.
Build the redirect map around page intent
Build the map at URL level with columns for source URL, proposed destination, rule type, reason, owner, test result, and launch date. Normalise obvious variations first: remove duplicate slash rules, decide how trailing slashes will behave, and specify whether query parameters or campaign tags must pass through. Exact matches should take priority over wildcard rules, so a specific old landing page is not caught by a broad pattern.
Most migrations need three destination decisions. A direct page move gets a one-to-one 301 redirect. When two pages become one, send both old URLs to the strongest consolidated page, provided it satisfies the same user intent. A temporary promotion should use a 302 redirect until it has a permanent home, then change to 301. Record exceptions beside the main map so temporary behaviour does not become permanent by accident.
Rule order matters because servers often evaluate redirects from top to bottom. Put precise rules before catch-all patterns, keep redirects server-side, and avoid relying on JavaScript or a meta refresh that may not execute for crawlers or constrained devices. This resembles the deliberate, component-by-component routing in the droid’s dome build: each old route needs one clear destination and a repeatable test.
Match the implementation to the hosting stack. A WordPress site may use server rules or a redirect plugin, while an Apache host often relies on .htaccess and an Nginx or platform setup may use its own configuration. Confirm that the chosen method returns an HTTP 301 status and a valid Location header before bulk activation. Keep the live map and its logic together so a later rule change can be traced to a specific URL.
Test every route and document the decisions
Test with a copy of the redirect rules before they affect the public site. Request representative old URLs, check that each returns one 301 response, and follow the full path to a 200 page. Record the redirect chain, final URL, canonical tag, page title, and intended call to action. A destination that loads but answers a different search need still creates a poor user experience and a weak migration.
A clear mapping sheet separates simple moves from decisions that need judgement:
| Previous content | Example source path | New destination | Mapping rule |
|---|---|---|---|
| Direct page move | /services/web-design/ |
/web-design-services/ |
One-to-one 301 redirect |
| Slug cleanup | /about-us/ |
/about/ |
One-to-one 301 redirect |
| Content consolidation | /design/ and /website-design/ |
/services/web-design/ |
Send both sources to the strongest new page |
| No equivalent | /summer-sale-2023/ |
No destination | Return 410 and omit it from the sitemap |
Run the test set through a spreadsheet, not only a browser. Browser checks reveal visible faults, while an HTTP response checker or command-line request confirms status codes and headers. Test desktop and mobile, with and without campaign parameters, and include URLs containing spaces or characters that were encoded by the old platform. Keep the tested spreadsheet with the deployment bundle for later audits.
Have a second person review destinations against the old page’s purpose, especially for merged service pages and high-link URLs. Compare the proposed map with analytics landing pages and Search Console queries to catch valuable traffic that the crawler missed. A redirect can be technically correct yet commercially wrong, so the final check should include both response behaviour and content fit.
Deploy the map with controlled checks
Deploy in stages and keep a rollback copy of the current configuration. Activate redirects during a lower-traffic window, confirm the homepage and a small sample of mapped URLs, then expand coverage. If a mistake appears, restore the previous configuration before investigating a cascade of new errors. A monitoring alert for 404 pages and server logs should be active from the first request.
Before deployment
- Crawl the current site and export every existing URL.
- Test each rule for status, destination, chains, and loops.
- Update internal links, XML sitemap, and canonical tags.
- Record approval, launch time, and responsible owner.
After launch, compare organic landing pages, conversions, crawl errors, and server requests with the pre-migration baseline. Search Console can reveal redirected or excluded URLs that deserve attention, while analytics shows whether visitors continue past the destination. Keep monitoring active for several weeks because indexing and reporting can lag behind the configuration change. A practical electronics journal illustrates why tracing the whole signal path is more reliable than trusting one component.
After deployment
- Submit only canonical destination URLs in the XML sitemap.
- Crawl weekly and investigate new 404s, loops, or chains.
- Compare rankings, organic sessions, and conversion rates.
- Review referring pages and update remaining external links.
Treat an unexpected destination as a mapping defect, not merely a reporting anomaly. Correct the source rule, retest it, and update the master spreadsheet with the reason and date. If a temporary 302 has become a stable campaign destination, decide whether it should remain temporary or become a permanent redirect. That decision protects the meaning of the status code for both people and crawlers.
Maintain the migration after launch
A redirect map supports the restructure, but the new site must also stand on its own. Replace internal links that point to old paths, ensure each canonical destination has one preferred URL, and keep redirected pages out of the sitemap and internal navigation. These steps reduce unnecessary hops for people and crawlers while making the new information architecture clear.
Old file paths deserve special care. A brochure or policy document may contain customer information even after it leaves the main navigation. Under the Australian Privacy Principles, map such material to a current safe resource or remove it from public access, and request deletion from caches where appropriate. Redirecting a sensitive document to a general homepage does not erase the exposed URL, so access and indexing must be handled directly.
Make the map a maintained business asset, with a named owner, version date, and review after every content launch. Schedule a quarterly crawl and retain notes about deliberate exceptions. Measure whether old URLs still attract relevant referrals and whether destination pages continue to satisfy the original intent. For an Australian small-business site, this routine keeps .com.au landing pages, service information, and enquiry routes stable while the underlying content evolves.
2 Geeks Web Design