Content of this page
Redirects and MigrationSeverity: Medium

302 instead of 301: Temporary forwarding check

Permanent URL changes should not run as temporary redirects.

Short version

Permanent URL changes should not run as temporary redirects The error should never be assessed in isolation. What matters is which URL group is affected and whether it creates a crawling, indexing, snippet, performance or quality problem.

The duration of the URL change decides

A 302 matches a temporary redirect, such as during a time-limited action. If a content page remains permanently under a new path, the redirection should express this intention. Therefore, do not change the status just because of a warning: first check whether the original address should be used again independently later.

Example: Recognizing the Result

Illustrative example: A permanently renamed performance page has been relaying its new path with 302 for months. For the planned state, the diversion is permanent.

Limit cause and implement correction

Go to the old address without browser cache and track status and location destination. When moving permanently, internal links should already lead directly to the new page. In addition, check whether the landing page meets the same user needs. A redirection of all old subpages to the start page does not solve missing matching content.

What makes you recognize a suitable correction

Configure permanent and temporary removals separately. After adjusting, check the full chain and internal links to the final content.

Classification and boundaries

When is this indication not a clear error?

302 is allowed in an actual temporary change. The status is not an error simply because it is not a 301.

302 instead of 301 after CMS and cause

Many audit messages can be resolved faster if they are grouped by system, page type and technical cause. CMS indentations are only linked where 302 instead of 301 has a clearly own cause or fixed route in the respective system.

For this error, there is currently no own CMS deepening, because the correction is usually not sufficiently system-specific. Take advantage of the general causes and checks on this page.

Frequent causes of this error

Related SEO Errors

Appropriate Seitenreport checks

This error should not be checked in isolation. The following tools and clusters help to narrow down the cause faster and to cleanly prioritize the affected URL groups.