Redirect present

A redirect present check tells you whether a page request reaches the content directly or passes through one or more redirects first. That may sound like a small technical detail, but it can have a major effect on crawling, indexing, page speed, and user experience.

A change here is important because it shows that the way a URL is being served has changed. A page that used to load directly may now be redirected, or a page that used to redirect may no longer do so. Either can be legitimate, but either can also point to an unexpected technical change.

What it is

This check monitors whether a URL resolves through at least one redirect.

In simple terms, it asks: does the page load immediately, or is the browser or crawler sent somewhere else first?

For example, if a page request goes straight to the content, the value is FALSE. If the request first passes through a 301 or 302 redirect before reaching the final page, the value becomes TRUE.

SEOlerts monitors that change as a yes-or-no signal. That makes it useful for spotting newly added redirects or redirects that have disappeared.

Why it matters

Redirects are a normal part of website management. They are often used during migrations, URL updates, domain changes, or content consolidation. Used properly, they help preserve access and guide users and search engines to the right destination.

The problem is that redirects also change how a page is delivered. A URL that once served content directly may now behave differently, which can affect performance, tracking, canonical handling, and search engine processing.

A new redirect can mean a page has been moved, renamed, or rerouted. A redirect that disappears can mean old URL rules have been removed or bypassed. Both situations matter because they can alter the path users and crawlers take to reach the content.

What can go wrong if unchecked

If a redirect appears unexpectedly, users and search engines may no longer be reaching the page in the way you intended.

That can lead to issues such as:

• important pages being routed to the wrong destination
• unnecessary redirect hops slowing down access
• internal links pointing to URLs that no longer resolve directly
• search engines spending crawl budget on avoidable redirect paths
• tracking, canonicals, or reports no longer matching the live URL behaviour

If a redirect disappears unexpectedly, an old URL that previously relied on it may begin returning an error or serving a different page than expected. That can create broken journeys for users and weaken the consistency of your site architecture.

Not every redirect change is a problem. A planned migration might intentionally turn this value from FALSE to TRUE. But when the change is unplanned, it can be an early sign of deeper URL handling issues.

Why monitoring it matters

Monitoring whether a redirect is present helps you detect changes in URL behaviour that are otherwise easy to miss. A page may still appear to work in a browser, so the shift from direct load to redirected load can go unnoticed until it causes SEO or reporting issues.

This check is especially useful after CMS updates, redirect rule changes, server migrations, plugin changes, or template edits. It helps catch new redirects added to a page, as well as redirects that have unexpectedly been removed.

Because it is a simple true-or-false signal, it is a good early warning that something in the request flow has changed.

What an alert may mean

An alert means the page no longer behaves the same way as before.

If the value changes from FALSE to TRUE, a redirect has been introduced. In practice, that could mean:

• the page URL was changed
• a redirect rule was added
• the site is forcing a new canonical path, subdomain, or protocol
• the page is now routed through another URL before loading

If the value changes from TRUE to FALSE, a redirect that used to exist is no longer happening. That could mean:

• a redirect rule was removed
• a migration rule expired or was overwritten
• the old URL now serves content directly
• the redirect path broke and stopped working

The alert is not proof of a problem on its own. It is a signal that the request path has changed and should be confirmed against what was intended.

What to check next

Start by verifying whether the change was planned. If there was a recent release, migration, or redirect update, compare the current behaviour with the expected setup.

Then check:

• whether the page now redirects, and to which final URL
• whether the redirect is permanent (301) or temporary (302)
• whether the redirect creates an unnecessary extra step
• whether internal links still point to the best version of the URL
• whether canonicals, sitemaps, and tracking reflect the new behaviour

If a redirect has disappeared, check whether old URLs now return the correct destination, a live page, or an error.

It is also worth looking at whether the change affects one page, a content section, or the whole site. A single redirect change may be page-specific, while widespread changes often point to broader rule changes at CMS, server, or CDN level.

Key takeaway

The redirect present check shows whether a page is being served directly or through a redirect. Monitoring it helps you catch new redirects, removed redirects, and changes in URL handling before they lead to wider SEO, performance, or accessibility issues. An alert means the page’s delivery path has changed, and that change should be reviewed to confirm it is intentional.