What is the difference between a 301 and 302 redirect?

A 301 redirect is permanent — it tells browsers and search engines that the resource has moved to a new URL forever. A 302 redirect is temporary — it indicates the move is short-term and the original URL should retain its identity. SEO consequence is huge: 301s pass ~100% of link equity to the destination URL within 4-12 weeks, while 302s do not transfer ranking signals at all because Google treats them as a temporary detour. Use 301s for: domain changes, URL restructures, slug updates, removed pages mapped to relevant alternatives, and HTTPS migrations. Use 302s for: A/B tests, geo-redirects, temporary maintenance pages, and seasonal landing pages. The status code is set in the HTTP response header, configured at the server level (htaccess, Nginx config, hosting platform settings) or via JS/HTML for client-side. Mistakenly using 302 for a permanent move is one of the most common and costly SEO mistakes — it can suppress rankings on the new URL for months until you correct the status code and Google re-crawls.

How do I write an htaccess redirect for Apache servers?

Apache supports two main directives in htaccess: Redirect and RedirectMatch (simple), or RewriteRule (powerful, regex-based). For a single page redirect, use: Redirect 301 /old-page https://example.com/new-page (this is the simplest syntax and works for most use cases). For pattern-based redirects, use mod_rewrite: RewriteEngine On followed by RewriteRule ^old-prefix/(.*)$ /new-prefix/$1 [R=301,L]. The L flag stops processing further rules; the R=301 sends a permanent redirect. Place htaccess files in your document root or any subdirectory. Apache reads them on every request, so syntax errors cause 500 errors immediately — always test in staging. Use RewriteCond %{HTTP_HOST} for domain-level conditions. For HTTPS redirects: RewriteCond %{HTTPS} off, then RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]. Always verify with curl -I https://yourdomain.com/old-url to confirm the response header shows 301 with the correct Location.

How do I configure redirects in Nginx?

Nginx redirects live inside a server block in your nginx.conf or sites-available config file. The simplest pattern: location = /old-page { return 301 https://example.com/new-page; }. The = makes it an exact match; without it, /old-page-with-suffix would also match. For pattern matching: location ~ ^/old-prefix/(.*)$ { return 301 /new-prefix/$1; } using regex. For a full domain redirect: server { listen 80; server_name old-domain.com; return 301 https://new-domain.com$request_uri; }. After editing config, run nginx -t to validate syntax, then nginx -s reload to apply without dropping connections. Common gotcha: Nginx does not have htaccess equivalents — you cannot drop a config file in a directory and have it picked up. All changes go through the main config and require a reload. For load-balanced setups, redirects belong on the load balancer or CDN layer rather than each Nginx instance.

What about IIS for Windows servers?

IIS uses the URL Rewrite module, configured via web.config XML files placed in the site root or any subdirectory. Install URL Rewrite from the Microsoft IIS site if not already present. Sample web.config block: . The redirectType="Permanent" sends 301; "Temporary" sends 302. IIS Manager has a GUI under URL Rewrite > Add Rule that generates the XML for you. After saving web.config, IIS picks up changes immediately — no service restart needed. Common pitfalls: web.config is case-sensitive in some scenarios, redirect rules execute in order so place specific rules before catch-alls, and conditions can match server variables like {HTTPS}, {HTTP_HOST}, and {REQUEST_URI}. Test with the IIS URL Rewrite test feature or curl -I against the live URL.

Are JavaScript and meta refresh redirects acceptable for SEO?

JavaScript redirects (window.location.href = ...) are acceptable but inferior to server-side 301s. Google now executes JS during crawl and follows JS redirects, but with delay (sometimes weeks) before passing link equity. Meta refresh redirects ( ) work for users but Google treats them inconsistently — a 0-second meta refresh is interpreted similarly to a 301 in most cases, but a delayed refresh (>1 second) is treated as user content and passes no equity. Use server-side 301 redirects whenever possible. Reserve JS redirects for: client-side routing in SPAs, authenticated redirects after login, and edge cases where you cannot configure server rules. Reserve meta refresh for: legacy static HTML pages where you cannot edit server config and need a quick fix. Modern frameworks like Next.js, Nuxt, and Remix support proper 301 redirects via config files (next.config.js redirects key, etc.) — always prefer those over client-side workarounds.

What are redirect chains and why do they hurt SEO?

A redirect chain is when URL A redirects to B, which redirects to C, which redirects to D. Each hop adds latency (50-200ms typically), consumes crawl budget, and dilutes link equity by approximately 5-15% per hop according to Moz studies. Google's crawler follows up to 5 hops before giving up; users on slow mobile networks may bounce before the final destination loads. Audit redirect chains using Screaming Frog's Redirects report or Ahrefs Site Audit. Common causes: HTTPS migration redirect to www and www to non-www in separate rules (creating A -> B -> C), sequential URL slug changes over years, and stacking platform-level redirects (CDN -> origin -> CMS plugin). Fix by collapsing all chains to single hops: every old URL should redirect directly to the final canonical URL with one 301, never via intermediate URLs. Re-run the audit quarterly to catch new chains introduced by ongoing redirects. Properly auditing chains is one of the highest-ROI SEO activities for sites older than 5 years.

How do I add redirects in Vercel and Netlify?

Vercel uses the redirects key in vercel.json: { "redirects": [{ "source": "/old-path", "destination": "/new-path", "permanent": true }] }. The permanent: true sends 301; false sends 308 (HTTP equivalent). Vercel applies these at the edge before hitting your serverless functions, so they are extremely fast. For Next.js apps deployed on Vercel, you can also use the redirects() function in next.config.js — same effect. Netlify uses a _redirects file in the site root: /old-path /new-path 301 (one rule per line, source then destination then status code). Netlify also supports netlify.toml [[redirects]] blocks for more complex rules with conditions and queries. Both platforms support pattern matching (Vercel uses path-to-regexp; Netlify uses splat * and placeholders :param). Test in staging via deploy previews before promoting to production. Both platforms log redirect events in their dashboards, useful for debugging chains.

What is the difference between 301, 302, 307, and 308?

301 (Moved Permanently) is permanent and may change the request method on redirect (POST to GET, deprecated behavior but historically common). 302 (Found, originally Moved Temporarily) is temporary and ambiguously defined for method preservation. 307 (Temporary Redirect) is the modern, strict version of 302 that always preserves the HTTP method (POST stays POST). 308 (Permanent Redirect) is the modern, strict version of 301 that preserves the method. For SEO, Google treats 301 and 308 equivalently for ranking signal transfer, and 302 and 307 equivalently as temporary. For form submissions and APIs, prefer 307/308 to ensure POST/PUT/DELETE methods are preserved through the redirect. For browser-facing page moves, 301 is most common and most widely understood by older tools. Modern browsers and CDNs handle all four correctly. When in doubt for permanent moves, use 301; for temporary, use 302; for API redirects with non-GET methods, use 308 (permanent) or 307 (temporary).

How long does it take Google to recognize a 301 redirect?

Google typically recognizes a 301 within 1-7 days for high-priority URLs (homepage, top-traffic pages) and within 4-12 weeks for fully transferring all ranking signals to the new URL. Speed depends on crawl frequency: pages crawled daily transfer faster than pages crawled monthly. To accelerate: submit the new URL to Search Console Index Now or URL Inspection > Request Indexing, ensure the new URL is in your XML sitemap, link to the new URL from prominent internal pages, and avoid redirect chains. Some signal transfer happens in two phases — Google first acknowledges the 301 (the new URL starts ranking for some queries within days), then over 4-12 weeks consolidates all ranking signals (backlinks, click data, dwell time) onto the new URL. Use Search Console Performance reports to monitor — search the new URL's queries and watch the impression curve transition from old to new. Keep redirects in place for at least 12 months; some teams keep them indefinitely to handle long-tail backlinks.

Can I redirect HTTPS and trailing slashes properly?

Yes, and you should. The standard pattern is: redirect HTTP to HTTPS, then redirect non-canonical (www vs non-www, with vs without trailing slash) to canonical, all in single hops. Apache htaccess example: RewriteEngine On, RewriteCond %{HTTPS} off [OR], RewriteCond %{HTTP_HOST} !^www\., RewriteRule ^(.*)$ https://www.example.com/$1 [L,R=301]. This handles both HTTPS and www in one rule. For trailing slashes, decide on a single canonical (with or without slash) and 301 the other version: RewriteCond %{REQUEST_FILENAME} !-d, RewriteRule ^(.*)/$ /$1 [L,R=301] strips trailing slashes from non-directory URLs. Avoid redirect chains by ordering rules carefully: HTTPS first, then www/non-www, then trailing slash. Test with curl -I -L (the -L follows redirects) to count hops. Use a tool like httpstatus.io to visualize the redirect path for any URL. The goal: every URL on your site should reach its canonical with a single 301 hop maximum.

What is link equity and how do redirects affect it?

Link equity (also called link juice) is the cumulative ranking value passed through hyperlinks. When site X links to your URL, X transfers some of its authority to you; that authority compounds over time and contributes to your URL's ranking. Each backlink carries equity proportional to the linking page's authority, anchor text relevance, and link position. When you 301-redirect a URL, Google transfers approximately 95-100% of accumulated equity to the destination, but only if the redirect is direct (no chains), permanent (301 not 302), and topically relevant (redirecting an unrelated page can dilute trust). Equity transfer is not instant — it takes 4-12 weeks to fully consolidate. To preserve equity during a site migration: map every old URL to its closest topical match (don't mass-redirect to the homepage), use 301 status codes, avoid chains, and update internal links to point directly to new URLs. Sites that handle migrations well retain 90%+ of organic traffic; sites that botch redirects can lose 40-60% permanently.

How do I bulk-create redirects for a site migration?

For migrations involving more than 100 URL changes, build a redirect map spreadsheet with columns: old URL, new URL, status code, and notes. Export your existing URLs from a Screaming Frog crawl or Search Console Coverage report. Then map each old URL to its closest equivalent new URL. For pages without a 1:1 match, redirect to the most relevant category or topic page rather than the homepage (homepage is a last resort that loses topical relevance). Translate the spreadsheet into your platform's redirect format: htaccess lines, Nginx config blocks, vercel.json entries, or a CMS plugin import (Yoast Premium and Rank Math both support CSV import). Test in staging — load 20 random old URLs and confirm each lands on the right new URL with 301 status. Roll out in phases if possible: redirect top traffic pages first, monitor Search Console for crawl errors, then add the long tail. Keep the redirects live for at least 12 months. Run quarterly chain audits to catch any new chains that emerge from ongoing redirects.

Free URL Redirect Generator

Generate 301/302 redirect rules for Apache, Nginx, PHP, or HTML meta refresh. Free, instant.

4.6on G2

4.8on Trustpilot

Used by 25,000+ marketers

Old URL

New URL

Server Type

Redirect Status

What this tool does

URL Redirect Generator delivers fast, reliable results for generate 301/302 redirect rules for apache, nginx, php, or html meta refresh. fr.

Designed to fit into your existing SEO and content workflow with no setup overhead.

How to use the URL Redirect Generator

Five steps.

Enter the old and new URLs

Paste the source URL (the one being redirected from) and the destination URL (where users land instead).

Pick the output type

Select Apache htaccess, Nginx, PHP, or HTML meta refresh based on your hosting platform.

Choose 301 or 302 status code

Use 301 for permanent moves to transfer link equity; 302 for temporary redirects like A/B tests.

Copy the generated rule into your config

Paste into htaccess, nginx.conf, a PHP file, or an HTML page as appropriate.

Test with curl and Search Console

Run curl -I https://yourdomain.com/old-url to confirm 301 status and Location header. Submit via Search Console URL Inspection.

When teams use it

Six common workflows.

Site migration redirect map

Generate hundreds of 301 redirects for a domain change or URL restructure. Preserve link equity and prevent 404 floods.

HTTPS and www canonicalization

Force HTTPS and consolidate www/non-www into a single canonical with one 301 hop. Standard launch checklist item.

Blog post slug refresh

When updating evergreen posts, change slugs to reflect new keyword targets and 301 the old slugs to maintain rankings.

A/B test traffic split (302)

Use temporary 302 redirects to split traffic between variants without consolidating ranking signals onto either URL.

Removing low-quality pages

When pruning thin content, 301-redirect each removed URL to its most relevant remaining page rather than letting it return 404.

Multi-region site routing

Geo-redirect users to regional subdomains (us.example.com, uk.example.com) with proper hreflang and 302 status.

Platform guides

Integrate with major platforms.

Apache (htaccess)

Open or create .htaccess in your document root.
Add RewriteEngine On at the top, then your Redirect or RewriteRule directives.
Save and test with curl -I https://yoursite.com/old-url.
If you see a 500 error, comment out recent edits and validate syntax with apachectl configtest.

Nginx

Edit /etc/nginx/sites-available/yourdomain.conf or your main nginx.conf.
Add return 301 statements inside server { } blocks; for patterns, use location ~ regex syntax.
Run nginx -t to validate syntax, then nginx -s reload to apply without downtime.
Verify with curl -I against the live domain.

PHP

Create or edit the PHP file that should redirect.
Paste the generated header() redirect before any output is sent.
Choose 301 for permanent moves or 302 for temporary redirects.
Open the old URL and confirm it lands on the destination.

HTML meta refresh

Use HTML meta refresh only when server-side redirects are not available.
Paste the generated meta tag into the head of the old HTML page.
Keep the delay at zero for an immediate redirect.
Test in a browser and confirm the destination URL loads.

Grigora vs. alternatives

Side-by-side.

Capability	Grigora	Tool A	Tool B	Tool C	Tool D
htaccess output	Yes	Yes	Yes	Yes	Manual
Nginx config output	Yes	Yes	No	Yes	Manual
PHP redirect output	Yes	No	No	Yes	No
HTML meta refresh output	Yes	No	No	No	Manual
301 vs 302 toggle	Yes	Limited	No	Yes	Manual
Bulk URL list input	No	Paid	No	Paid	No
Free with no signup	Yes	Yes	Yes	Trial	Yes
Chain detection warning	No	No	No	Paid	No

Common errors and fixes

Eight issues users hit.

Redirect loop (URL redirects to itself)

Cause: Misconfigured rule causes /a to redirect to /a, often from missing exception conditions on htaccess RewriteRules.

Fix: Add RewriteCond to skip rule when source equals destination. Test with curl -I -L --max-redirs 5 to detect loops.

Redirect chain with 3+ hops

Cause: HTTPS, www, and trailing-slash rules stacked sequentially without consolidating into a single redirect.

Fix: Combine rules into one rewrite that handles all canonical changes in a single 301. Audit chains via Screaming Frog.

302 used for a permanent move

Cause: Default redirect type chosen at platform level (Vercel permanent: false, Netlify default 302) without overriding.

Fix: Explicitly set 301 status. In Vercel: permanent: true. In Netlify: append 301 to _redirects line.

Redirect points to 404 destination

Cause: New URL was deleted or never existed; redirect map was generated from outdated sitemap.

Fix: Audit destinations with a tool like httpstatus.io. Update mapping to a live URL or remove the redirect.

htaccess syntax error returns 500

Cause: Missing closing tag, incorrect flag, or unsupported directive crashes Apache config parsing.

Fix: Comment out recent edits and test incrementally. Validate syntax with apachectl configtest before deploy.

Redirects do not apply (rule never triggers)

Cause: Rule order conflict — another redirect or routing rule matches first and bypasses the new rule.

Fix: Move new rule above conflicting rules. In Apache use [L] flag to stop further processing once matched.

Query string lost on redirect

Cause: htaccess RewriteRule by default discards query string when destination contains its own query.

Fix: Add [QSA] flag (Query String Append) or [QSD] (Query String Discard) explicitly. Test with ?utm tags.

Redirects work locally but fail in production

Cause: Edge cache, CDN, or load balancer overrides server redirects; or production runs different web server software.

Fix: Move redirects up to the CDN/edge layer (Cloudflare Page Rules, Vercel redirects, Cloudfront behavior).

Original data

2026 study.

95-100%

Link equity passed by 301 redirect

4-12 weeks

Time for full equity transfer

5-15%

Equity loss per chain hop

Max redirect hops Google follows

Frequently asked questions

Twelve answers.

Related free tools

Other utilities.

Try URL Redirect Generator now

Free, unlimited, no signup.

Try the Tool