OpenWebmasterby Mello Zone

Preferences

Make OpenWebmaster yours

Language, color, reading size, and motion stay on this device.

Inspect URLAdd website

Redirects · source cues

Check meta refresh and JavaScript redirect cues

Inspect a public page for source-visible meta refresh tags, common JavaScript redirect literals, History API URL rewrites, and server-side redirect context. Use it before migrations, redesign launches, canonical cleanup, and JavaScript SEO reviews.

PAGE FETCHLIVE + BOUNDEDDETECTIONMETA + JS CUESEXPORTSCSV + JSON

Runs the indexability inspector, source CSS extraction, and literal raw-HTML search together. This page reports cues; it does not execute script or prove that a crawler followed a client-side redirect.

OpenWebmaster checks one bounded public HTML response. It does not execute JavaScript, follow client-side redirects, render the page, prove Googlebot or Bingbot processed the redirect, validate destination content, compute crawl budget, rankings, traffic, conversions, or cause.

↪

Ready for a public page.

No sample redirect, JavaScript-rendered result, Googlebot rendering proof, crawl-budget estimate, ranking impact, traffic claim, or manufactured redirect score appears before a live bounded check.

Redirect migration workflow

Use client-side cues as a migration review trigger

Prefer server redirects for URL moves

When the move is permanent and you control the origin, a server-side 301 or 308 is clearer than a meta refresh or script-driven redirect.

Inspect JavaScript in context

A literal such as location.href can be analytics, routing, login logic, or a true redirect. Review the surrounding script before changing behavior.

Compare rendered output when needed

If client-side routing changes titles, canonicals, robots directives, links, or headings, use the response-versus-rendered HTML comparison next.