What is a redirect map generator and why is it needed?
For a large site, manual mapping quickly turns into working with hundreds of rows. An error in a single row can send the user and search engine robot to the wrong page. Therefore, it's advisable to prepare the sitemap before launching a new version of the site, check for any questionable matches, and only then submit it to the developer for 301 redirect setup.
A redirect map is a table of correspondences between URLs before and after a site structure change. In a simple version, each row contains the old URL, the new URL, and the redirect type. HTTP status code 301 is most often used for permanent page relocations.
A 301 redirect map generator reduces manual work when there are many URLs that need to be organized into a single, understandable structure. An SEO specialist receives a basis for verification, and the developer receives a list of URLs that can be transferred to the server configuration, CMS, or a separate redirect management module.
How does a redirect map differ from a regular 301 redirect?
A single 301 redirect solves the problem for a specific address: the old URL redirects the user to a new URL. The map covers a set of pages at once and shows the entire migration pattern. It's especially useful when dozens, hundreds, or thousands of addresses are changing simultaneously.
This approach allows you to spot duplicates, pages without a new equivalent, and instances where multiple old URLs accidentally point to the wrong document. A redirect table also simplifies post-launch testing because the original matches are already recorded.
What does a finished URL map look like?
A minimal URL map contains the source address, destination address, and response code. For larger projects, it is often supplemented with the verification status, comments, and migration reason, if these fields are required by the migration process.
| Old URL | New URL | Code |
|---|---|---|
| /old-category/ | /catalog/ | 301 |
| /old-product/ | /products/new-product/ | 301 |
| /blog/old-article/ | /blog/new-article/ | 301 |
This format is convenient for manual viewing, sorting, and sharing with the developer. For large-scale work, the table can be exported to CSV or another supported format and then used when setting up a server or CMS.
What errors should be avoided when creating a redirect map?
Most problems arise not when writing the rule itself, but when selecting the wrong target. Therefore, it's advisable to test the completed map before implementation and again after the launch of the new version of the site.
When migrating, I don't recommend automatically redirecting all missing URLs to the home page. For each old URL, I first search for the most relevant new document. After implementation, I check the final HTTP codes, redirect chains, internal links, canonical, and sitemap.
Mass redirect of all pages to the home page
This option seems simple only at the server setup level. The user opens an old card, article, or category and unexpectedly finds themselves on the homepage, where the desired content may not even be present.
In the redirect mapping tool, it's best to consider each such line individually. If there's no relevant new document, an automatic 301 to the homepage shouldn't be used as a universal replacement.
Several old pages accidentally link to the wrong URL
When performing bulk matching, identical words in titles can lead to incorrect pairings. For example, an old delivery post might be linked to a product page only because of a matching URL fragment.
Before importing, check suspicious groups and pages with multiple possible targets. The higher the organic traffic and the number of external links, the more thorough this check should be.
Redirect chains
A chain occurs when an old URL first points to an intermediate URL, which then redirects the user further. For example, the path A → B → C is usually worse than a direct path A → C.
When preparing the map, you should specify the final URL whenever possible. After launching, the redirect chain should be checked separately, as some chains may originate from old server or CMS rules.
Cyclic redirects
A loop occurs when URLs redirect requests to each other. The simplest example is A → B → A, after which the browser stops loading the page due to too many redirects.
This error can be detected by checking the actual HTTP responses after implementation. On large sites, bulk checking of all map rows is especially useful.
Redirect to a page with a 404 error
The final map URL must exist and load correctly. If the new URL returns a 404, the user is redirected and still receives the error page.
Before launch, it's worth testing your targets in bulk. It's a good idea to repeat the testing after publishing a new version, as some URLs may change during the final release.
Loss of GET parameters
GET parameters can be used for filters, advertising, sorting, or utility logic. When migrating a structure, some parameters need to be preserved, while others may no longer be used.
Rules for such URLs should be verified separately. Generally deleting parameters can alter the final page or lose data needed for analytics and marketing campaigns.
How does the redirect map generator work?
The work begins with two sets of URLs: the old site structure and the current site structure. The tool receives these lists, after which it can compare the old and new URLs and generate the final sitemap.
The upload method depends on the capabilities of the specific interface. If list insertion, CSV import, file upload, or retrieval of URLs from sitemap.xml are available, use the option that is most convenient for the project size.
Add old URLs
The first list includes the addresses that existed before the migration. It's best to use a full list of significant pages rather than limiting yourself to the site's current menu.
Sources may include sitemap.xml, crawling, Google Search Console, analytics, and tables with historical structure. If the old site uses GET parameters, these should also be checked separately, as parameters sometimes require different redirect rules.
Add new URLs
The second list contains the URLs for the new version of the website. They must open correctly and match the structure that will be used after launch.
Before creating a map, it's a good idea to remove any duplicates and technical URLs. If the final URL already redirects the user further, such a pair will create a redirect chain, so it's best to define the final destination in advance.
Run a mapping of old and new URLs
Comparing old and new URLs helps find likely matches between the two structures. For completely changed URLs, the page's purpose, title, Title, H1, and content can serve as reference points.
The SEO redirect map generator is especially useful for large lists where visually comparing each pair is difficult. Automatic matching should be considered as a basis for verification, as identical words in a URL do not guarantee identical search intent.
Check the suggested matches
Disputed pairs must be manually verified. The old product must link to the same product or the closest possible replacement, and the category must link to a category with a comparable product range and purpose.
Pages for which multiple potential redirects have been identified require special attention. It's better to spend time checking the content here than to fix irrelevant redirects and re-edit the redirect map after the launch.
Export the redirect map
After verification, the final map can be sent to the developer or used for import if the site supports bulk redirect management. The export format depends on the capabilities of the generator and CMS.
Before deployment, it's a good idea to save the original version of the spreadsheet. This will be useful for technical testing, post-launch error detection, and comparison with actual working redirects.
What we actually did
Dental clinic · Kyiv and Chernihiv
+44% clicks from search
A domain with no history on a website builder. We built the semantic core for both cities, reworked the landing pages and built the link profile from zero. Four months: 34.8k clicks, impressions 1.32 → 1.76M, DR 0 → 41.
E-commerce · international
+96% clicks in two months
A catalog of digital 3D models. We clustered the semantics, rebuilt the hub pages and closed duplicates and indexing errors. Google users 247 → 532, CTR 2.4% → 4%.
Medical center · Ukraine
+68.75% visibility in the first month
Narrow visibility and a small semantic core at the start. Semantics, landing page structure, metadata and internal linking, then gradual link building.
Answers to your questions
What is a redirect map?
A redirect map is a table that maps old URLs to new addresses after a migration or restructuring of a site. For permanent redirects, a 301 code is typically included alongside the redirect.
This document is used to coordinate SEO logic and technical settings. Once implemented, the map can be conveniently used as a baseline for mass testing of all redirects.
What is a redirect map generator for?
The redirect map generator helps you create correspondences between two versions of your website structure and reduce the amount of manual comparison. The time savings are especially noticeable when working with hundreds or thousands of URLs.
The resulting table still needs to be tested before implementation. Deleted pages, changed categories, and URLs with no obvious new equivalent require the most attention.
Is it possible to automatically match old and new URLs?
Some URLs can be matched automatically based on structure, names, or other characteristics. The more different the new version of the site, the more pairs will require manual verification.
In disputed cases, it's necessary to compare the intent, page type, Title, H1, and content. Automatically matching a few words doesn't guarantee the correct targeting.
What redirect code should I use when changing the URL?
When changing a URL permanently, a 301 redirect is typically used. This is used when the old page is no longer the primary URL and the transition becomes permanent.
Temporary scenarios require different code. Therefore, before mass configuration, it's important to determine the reason for the redirect, rather than assigning 301s to any changes indiscriminately.
Is it possible to redirect all old URLs to the home page?
A mass redirect of all missing pages to the homepage is usually not appropriate. Users expect to see a document related to the address they opened, and the homepage rarely preserves that context.
For each old URL, a relevant new document should be searched for. If there is no suitable equivalent, a separate decision must be made whether a redirect is necessary at all.
What to do with an old page if there is no new equivalent?
First, check incoming links, traffic, page purpose, and the presence of related content. If a truly suitable new document exists, consider applying a 301 to it.
When there is no relevant replacement, a proper 404 or 410 is acceptable. Sometimes it makes more sense to create a new, useful page if the old URL has stable demand and value for the site.
Do I need to check redirects after moving a website?
Yes, because even a correctly implemented table can be implemented incorrectly. After launch, they check HTTP codes, final URLs, chains, loops, internal links, sitemap.xml, and canonical.
Additionally, you should monitor indexing in Google Search Console. If the issue only occurs on specific pages, the source sitemap can help you quickly identify the erroneous match.
A good redirect map starts with a complete list of old URLs and ends with a review of actual HTTP responses after the release. Between these steps, you need to correctly match pages, remove irrelevant pairs, eliminate chains, and determine the fate of URLs without suitable replacements.
Add old and new URLs to the generator, check the suggested matches, and prepare a 301 redirect map for the developer. Before publishing the new structure, be sure to run a bulk check of the final URLs.
We reply within one business day. No newsletters, no “just a reminder” calls.
He will look at the site himself instead of passing it to a manager.
More on: Redirect Map Generator
When is a 301 redirect map needed?
A sitemap is required whenever old URLs no longer align with the current site structure. This applies to full migrations and local changes, such as moving a section, renaming categories, or changing friendly URL rules.
Before starting work, it's a good idea to collect all indexed and relevant old URLs. This list may include pages from sitemap.xml, Google Search Console, analytics systems, crawlers, and external link data. This approach reduces the risk of losing an address that no longer appears in the new site's navigation.
Moving a website to a new domain
When changing a domain, old pages should link to the corresponding pages on the new site. Simply redirecting all requests to the homepage is insufficient, as search engines and users expect to receive a document with the same or as close content as possible.
The sitemap helps link specific old URLs to new ones. After launch, you should check HTTP codes, final URLs, canonicals, sitemap.xml, and internal links to ensure the old structure isn't continued within the site.
Changing CMS or platform
A new CMS often uses different URL generation rules. The /catalog/phones/ category may have a completely different path after being moved, although the page content will remain the same.
Before migrating, it's worth exporting both structures and comparing pages. Pay particular attention to product cards, categories, filters, articles, and landing pages that receive organic traffic or external links.
Changing the site structure
Rebuilding a catalog affects section nesting, directory names, and URLs. Even a small change in the path creates a new URL if the old one isn't preserved.
A redirect map records the transition from the previous structure to the new one and helps ensure that old entry points are not lost. After the migration, it's best to update internal links immediately so they point to the final URLs without an intermediate 301.
Merging or deleting pages
If multiple pages are being merged into one, a suitable final URL must be determined for each old page. Matching should preferably be assessed based on the page's intent, topic, content, and role in the structure.
A deleted page shouldn't be automatically redirected to the homepage just because there's no other obvious URL. If no relevant alternative exists, you should decide separately whether a 301, a proper 404, or a 410 response is needed.
Bulk URL change
With hundreds of addresses, manually creating a map is time-consuming and error-prone. It's easy to skip rows, confuse similar categories, or assign multiple pages to a single, inappropriate address.
A URL mapping generator helps organize this workflow into a single process. Automatically generated pairs still need to be verified, especially if the names, structure, and content of the old and new versions differ significantly.
How to correctly match old and new URLs?
When URL mapping, comparing character strings in URLs isn't enough. The old document should lead to the closest possible answer for the same query. Therefore, URL structure helps with matching, but the final decision is made based on the page's purpose.
If the URLs have completely changed, additional comparisons are made of the Title, H1, text, page type, and directory location. This approach is especially useful when switching CMSs, when the old and new URLs may not share a single fragment.
Matching by Page Purpose
First, determine the type of the old page and its intent. It's best to link an informational article to a relevant article, a product card to a product, and a category to a relevant category.
If the new page responds to a different query, formal similarity in name doesn't make it a suitable redirect target. During mass migrations, it's precisely these pairs that most often require additional manual verification.
Comparison of products and categories
For an existing product, the best target is a new listing. If the product is discontinued, a physical replacement or a suitable category may be an option, but the decision depends on the store's content and structure.
It's best to move categories to sections with comparable product ranges. Redirecting all disappeared categories to a single page is usually not advisable, as it will lose the context of the user's navigation.
Matching by Title, H1 and Content
Title and H1 tags help find matches when the URLs of the old and new sites differ significantly. Matching section names often quickly reveal the correct pair, especially when migrating articles and common categories.
Content helps check for ambiguous variants. If two documents have similar titles but answer different queries, choosing a redirect target based solely on a few matching words is risky.
What if there is no exact equivalent page?
First, you need to check whether a new page with similar intent and content exists. If such a document exists, it can become the target of a permanent redirect after manual verification.
If there's no suitable page, a decision is made individually for each URL. Automatically assigning any existing page creates a technically working redirect, but doesn't solve the user's problem.
There is a page with a similar meaning
A related page is appropriate when it truly continues the topic of the old document and addresses the same user request. In this case, a 301 redirect usually makes sense to the visitor and search engine crawler.
Before implementation, it's advisable to check the Title, H1, main content, and page placement within the new structure. If the differences are significant, it's best to find a different URL or consider a non-redirect option.
There is no suitable page
If there's no relevant replacement, don't automatically redirect the URL to the main or random category. For a deleted document, a valid 404 or 410 response is acceptable if the page has truly been deleted and won't be returned.
The decision depends on the URL history, incoming links, traffic, and the reason for deletion. A valuable URL sometimes requires creating a suitable new page, but that's a separate migration task.
What should a redirect map contain?
The minimum data set includes the old URL and the new URL. For ongoing migrations, a 301 status code is also recorded, and for larger projects, it's useful to store the verification status and comments on disputed matches.
The clearer the table structure, the easier it is to communicate between the SEO specialist and the developer. A URL mapping tool should help manage pairs and quickly identify rows that still need to be resolved.
Old URL
This column contains the address before any changes to the structure. It's best to keep it in its full and unambiguous format, especially if the site used both HTTP and HTTPS, www variants, or different trailing slash conventions.
Before importing, the list should be cleared of any duplicates. Otherwise, a single old address may receive several conflicting rules, making the check results more difficult to interpret.
New URL
The new URL must be the final working page. Before launching the redirect, it's recommended to check it for a 200 response, the absence of an unwanted noindex, and the correct canonical.
If the new URL itself leads to a third page via 301, it's better to use the final URL directly. This shortens the chain and makes the map clearer for future maintenance.
Redirect type
For a permanent address change, a 301 code is typically used. This code informs the client and search engine that the resource has been permanently moved to a different URL.
Other codes are used in their own scenarios, so the redirect type shouldn't be chosen haphazardly. The migration map should reflect the actual task and not mix permanent and temporary redirects without reason.
Verification status
The status helps differentiate between completed matches and those requiring manual resolution. For example, you can mark verified matches, questionable matches, and pages without a suitable new URL.
During a large migration, this column simplifies quality control. The team can see which URLs have already been approved and which ones should not be passed on to the developer until further review.
Why is 301 redirect usually used for migration?
The 301 code is used when the page address has changed permanently and there are no plans to revert to the old URL. This is a typical scenario when changing a domain, CMS, directory structure, or friendly URL.
Once implemented, the old address should redirect users directly to the current page. At the same time, it's advisable to update the website's internal links so that visitors and search engines navigate directly to the new URL.
What is the difference between 301 and 302?
301 indicates a permanent resource transfer, while 302 is used for temporary redirection. Therefore, 301 is usually chosen for permanent address migrations.
Using 302 for a permanent relocation without a reason is not recommended. Before mass implementation, it's best to coordinate the response code with the developer and test it on a test group of URLs.
Do you need 307 and 308?
Codes 307 and 308 also refer to redirects, but they take into account additional features of the HTTP request method. For a typical SEO migration map, 301 is more common.
If a project uses APIs, forms, or non-standard request methods, it's best to work with the developer to make the technical decision. For simple page URL changes, delving into these options is usually unnecessary.
How to implement a ready-made redirect map?
After verification, the map is transferred to the developer or uploaded via an available CMS mechanism. The method depends on the server, platform, and number of rules, so the same table may be implemented in different ways.
Before changing the working configuration, it's advisable to save a backup and test a small subset of the rules. A large syntax error can affect the entire site, so a technical review is required after publishing.
Apache and .htaccess
In Apache, redirects are often configured via the .htaccess file or virtual host configuration. For a large number of rules, it's more convenient to first prepare a blank map and then generate the configuration in the required format.
When working with .htaccess, it's important to avoid conflicts between old and new rules. After changes, check several typical URLs, and then run a bulk check of the entire table.
Nginx
On Nginx, rules are placed in the server configuration. The syntax differs from Apache, so ready-made .htaccess lines cannot be imported without adaptation.
It's best to provide the developer with the original "old address → new address" table. This way, they can choose the appropriate implementation method and avoid having to recreate the migration logic from already generated code.
CMS and control panels
Some CMSs support redirect creation through built-in settings, modules, or plugins. For large numbers of URLs, CSV import can be used if the system supports this feature.
After importing, you need to verify the actual results via HTTP requests. The presence of a row in the admin panel doesn't necessarily confirm that the rule is triggered as specified in the map.
How do I check the redirect map after moving a website?
Post-release testing is necessary even with a carefully prepared table. Server rules may conflict, some pages may be missing, and some new URLs may unexpectedly redirect requests.
It's better to check the entire sitemap in bulk, rather than just a few random URLs. It's also worth monitoring pages with organic traffic, external links, and commercial value.
Check HTTP codes
The old URL should return the expected redirect code, and the final URL should return the correct response. For a permanent migration, a typical setup would be the old URL with a 301 and the final page with a 200.
If the destination page responds with a 404, 5xx, or redirects the request again, such a string should be returned for verification. A URL redirect mapping tool can help identify the problematic pair, but the result is confirmed by the actual HTTP response.
Check redirect chains
After implementation, you need to ensure that the old address leads directly to the final page. Additional intermediate steps may be required due to old rules, protocol changes, www, or the final slash.
It's best to find chains using a bulk analyzer. Once detected, determine which rule is creating the extra transition and modify the map or server configuration.
Check internal links
After migration, internal links should point directly to the current pages. If menus, articles, and pages continue to link to old URLs, the site is constantly using its own redirects.
After launching, crawl the site and find links to redirecting URLs. These links should be replaced with final URLs, even if the 301 is technically working correctly.
Update your sitemap.xml
The sitemap.xml file should contain current indexed pages. It's best to remove old URLs that are already being redirected from the file and replace them with their final URLs.
After updating your sitemap, you can resubmit it to Google Search Console. This helps the search engine crawler quickly retrieve an up-to-date list of pages from the new structure.
Check canonical
Canonicals on new pages must match the actual site structure. An incorrect link to the old URL creates conflicting signals after the migration.
You need to check the templates of categories, products and articles especially carefully. One error in a template can immediately spread to thousands of pages in a new version.
Control indexing
After the move, you should monitor the indexing of the new URLs and any errors with the old URLs in Google Search Console. Changes are rarely reflected in search results for all pages at once.
Whenever issues are detected, check the specific URL against the sourcemap, HTTP response, canonical, and internal links. This process helps identify the source of the error without accidentally changing your working rules.
Redirect map generator and URL mapping tool – what do these terms mean?
English-language SEO services have several names for the same task. These include redirect map generator, redirect mapping tool, URL mapping generator, URL mapping tool, and URL redirect mapping tool.
The phrase "301 redirect map generator" typically refers to preparing matches for permanent redirects. SEO redirect map generators are more often used in the context of site migration, when the map is prepared taking into account indexing, organic traffic, and the relevance of the final pages.