GitHub Pagesツール

無料リダイレクトマップコンバーター

CSVリダイレクトマップをNetlify、Vercel、Apache、Nginxのリダイレクト形式に変換します。

ツールを読み込み中...

リダイレクトマップコンバーターとは

A redirect map is a list of URL redirects — old URL, new URL, HTTP status code — that tells your web server or hosting platform to send visitors from the old URL to the new one. Different platforms use different formats, from simple space-delimited files (Netlify _redirects) to JSON arrays (Vercel) to Apache/Nginx server config syntax. This tool converts a single CSV map to all major platform formats.

クイックアンサー

Convert a CSV redirect map (old_url,new_url,status) to your platform's redirect format. Supports Netlify _redirects and netlify.toml, Vercel vercel.json, Apache .htaccess, and Nginx rewrite rules. Validate duplicates and redirect chains before deploying.

制限事項

Different platforms handle redirect edge cases differently — trailing slashes, query string forwarding, and wildcard matching vary. Test redirects on the actual platform after conversion.
Very large redirect maps (10,000+ entries) may need to be split or converted to pattern-based rules for performance. This tool generates one entry per redirect.
Apache and Nginx formats assume basic server configuration. Complex setups with virtual hosts, location blocks, or conditional rewrites may need manual adjustment.

使い方

Enter your redirect mappings in CSV format: old_url,new_url,status (status defaults to 301 if omitted).
Select the target platform format.
Enable validation to detect duplicate source URLs and potential redirect chains.
Copy the generated redirect configuration for your chosen platform.

主な用途

Migrate a WordPress site to a static site and convert the old URL structure to new static URLs.
Convert an Apache .htaccess redirect file to Netlify _redirects format for a platform migration.
Check a redirect map for loops and duplicate entries before deploying to production.

用途

使用例

例

Site migration redirect map

A site moves from WordPress to a static site generator. Export the old URLs and new paths as CSV, convert to Netlify _redirects format, and deploy. The tool flags any duplicate old URLs and potential redirect chains.

例

Platform migration

A site migrates from Apache hosting to Vercel. Paste the Apache redirect rules into the converter and output Vercel vercel.json format. All 301 and 302 status codes are preserved.

よくあるミス

Creating redirect chains (A → B → C) instead of direct redirects (A → C, B → C) — each hop adds latency and may lose SEO value.
Using relative URLs without a leading slash — all redirect paths should be absolute paths starting with /.
Forgetting to include the status code — defaults to 301, but some platforms default to 302 which has different SEO implications.

検証

Test a sample of redirects at each HTTP status code level to confirm the generated config works correctly on your platform.
Use curl -I https://yoursite.com/old-url to verify the redirect returns the expected status code and Location header.

FAQ

リダイレクトマップコンバーターのFAQ

Should I use 301 or 302 for my redirects?

301 (permanent) tells search engines to transfer ranking signals to the new URL and update their index. Use 301 for permanent moves. 302 (temporary) tells search engines the move is temporary and they should keep the old URL in their index. Use 302 for temporary maintenance or A/B tests. 307 and 308 are the HTTP/1.1 equivalents of 302 and 301 respectively.

What is the maximum number of redirects I should have?

There is no hard limit, but large redirect files (thousands of entries) can slow down request processing on some platforms. Netlify recommends keeping _redirects under 10,000 entries. For very large redirect maps, consider pattern-based redirects (using wildcards or regex) instead of individual entries.