Skip to the content
searchboar.

Crawling and indexing

What is a temporary redirect?

A temporary redirect tells a client that an appropriate response is temporarily available at another URL, commonly using HTTP status 302 or 307, without declaring a permanent move.

Also known as: 302 redirect · 307 redirect · temporary redirect

At a glance

  • Use a temporary redirect for a genuinely temporary situation with a clear lifecycle.
  • 302 and 307 do not behave identically for every request method.
  • The temporary destination must still answer the visitor’s actual need.
On this page
A temporary detour leads from an original page to another destination, with a calendar marking its limited duration.
A temporary redirect sends requests elsewhere for a period; it does not signal the same thing as a permanent move.

When might a temporary destination be useful?

A page may keep its usual address while a short-lived alternative is shown for a particular period. Examples include a temporary information page or a test after which the original arrangement returns.

Decide when the temporary arrangement should end. If the content will remain at the new address indefinitely, consider a permanent redirect instead. The response code should describe the content decision, not substitute for making it.

How do 302 and 307 differ?

Both are temporary redirection HTTP status codes. The response provides another address for the client to request. A 307 preserves the request method and body; with a 302, some clients can change a POST into a GET. That distinction matters for forms and application actions.

An illustrative response for a public page is:

HTTP/1.1 302 Found
Location: https://example.com/temporary-information

Do not copy a page-navigation example into a payment, sign-in or data-submission flow without checking the application’s requirements.

How does a search engine interpret it?

Google distinguishes temporary redirects from permanent moves. It treats them differently when choosing which URL should represent the content. Other signals can still influence that choice.

Consequently, “a 302 means the destination can never be indexed” is too strong. Canonical URL selection depends on several related signals. Crawling the redirect and deciding how the URLs appear in search are also different steps.

An example: a language school’s open day

Imagine a language school with a year-round open-day information page. For two weeks, a particular event has its own registration page; afterward, the general information should return.

If the school chooses a redirect, it can use an appropriate temporary response and record when to remove it. The event page should clearly state the date and current participation options, so visitors arriving through an older general link understand the situation.

Continuing to redirect to an expired event no longer serves the same purpose. The owner and end date are therefore part of the content lifecycle, alongside the code itself.

Is this a general maintenance solution?

Not necessarily. “Temporarily unavailable” and “temporarily somewhere else” describe different conditions. A brief service outage may require a different response from an alternate content destination.

Similarly, temporarily redirecting every removed page to the home page does not restore its missing information. Fixing a broken link requires considering what the visitor expected.

What should you check?

Inspect the original response, destination and number of redirect steps. Confirm that the target works, is relevant and is accessible to the intended visitor.

At the end of the period, verify that the original page returns and that an old redirect has not survived in another layer or cache. Record the source URL, destination, reason, owner and planned finish. That prevents a temporary measure from quietly becoming permanent, without implying a guaranteed search-ranking benefit.

Sources

  1. Google Search: HTTP status codes and network errors
  2. Google Search: redirects and Google Search
  3. Google Search: URL canonicalization
  4. MDN: redirections in HTTP