Schema Markup Generator
Build clean, valid Schema.org JSON-LD for rich results and AI answer engines — Article, Product, Local Business, FAQ, Event and more, with empty fields dropped automatically.
Crawl your site and find every URL that redirects only because of a missing or extra trailing slash — with the exact page still linking to it, not just the redirect itself.
Paste your site's URL. It crawls internally, finds every non-slash ↔ slash redirect, and shows exactly which page(s) still link to the non-canonical URL — that's what's causing Search Console's "Page with redirect" report.
A "Page with redirect" in Search Console usually just means an internal link points to the pre-redirect URL instead of the final one. Fix the link shown under "Still linked from" — once nothing on the site links to the non-canonical form, the report clears on its own over the next few crawls.
processed in your browser · never uploaded
Your homepage works best — the crawl follows internal links out from there, so starting deeper just means it finds less.
Match it to roughly how many indexed pages you have. Under-shooting just means clicking "Crawl more" once it caps out; it resumes instead of starting over.
Rows appear live as pages are checked — you don't have to wait for the full crawl to finish to start reading results.
Every flagged URL lists the page and anchor text still pointing at the non-canonical form. That's the thing to actually edit — not the redirect.
Update the internal link (or sitemap entry) to point straight at the final URL. Re-run the check afterward to confirm nothing else on the site still links to the old form.
| Input | Output | Typical saving | Best for |
|---|---|---|---|
| Any starting URL | Live table + downloadable CSV of every trailing-slash redirect, with source pages | Sites with roughly 50–2,500 indexed pages |
We ran the same files through the popular alternatives first. These are the gaps we found, and what this tool does instead.
Every flagged redirect lists the exact source page and anchor text still linking to the non-canonical URL.
test: Run it against any page with a known missing-slash internal link. The "Still linked from" column names the source page and the visible anchor text — not just "internal link found."Give it one starting URL and it crawls the internal link graph itself.
test: Paste only your homepage. Multiple flagged pages appear without entering any other URL.Trailing slash issues are a common cause of the “Page with redirect” report in Search Console. When Google finds a redirect, it excludes the original URL and indexes the final URL instead.
The redirect itself usually isn’t the problem. The problem is that something on your site is still linking to the old URL. This can happen after permalink changes, caching changes, or when your XML sitemap lists the redirecting URL instead of the final one.
A concrete example. Say /services redirects to /services/. That’s fine by itself. But if your homepage links to /services, Google has to follow the redirect every time it crawls that link. If your site also redirects between http, https, or www, the same link can create a longer redirect chain.
What this tool does. Give it a starting URL and it crawls your site by following internal links. For every link it finds, it checks redirects and looks for URLs where only the trailing slash is different. When it finds one, it shows the pages linking to the wrong URL and the anchor text, so you know exactly what to fix.
Where it stops. It follows links that are available in the HTML. Links added only by JavaScript may not be found. It also cannot find true orphan pages that have no discoverable links pointing to them.
When this isn’t the right tool. If you need a full technical SEO audit covering broken links, missing metadata, images, redirect chains and other issues, a crawler like Screaming Frog is better suited for that. If you have already fixed the internal links, you may simply need to wait for Google to crawl the pages again.
One honest note on how it runs. This tool processes the crawl on our server, not in your browser. Your URLs are sent to our crawler during the check and nothing is stored beyond the session.
Last reviewed August 2026 · this tool runs on-device.
It means Google tried to crawl that exact URL and got redirected somewhere else. Google excludes the original URL from the index and indexes the final destination instead — so it's not necessarily broken, but it does mean crawl budget is being spent on a hop instead of a page.
Most CMSs and servers pick one canonical form — with or without a trailing slash — and 301 anything that doesn't match to the correct one. It's expected behavior. The problem is usually that something on your own site (a menu link, a sitemap entry) still points at the wrong form and keeps triggering it.
Search Console tells you that a URL redirects but not what's linking to it. You need a crawler that checks your site's own internal links and reports the source page for each one — which is what this tool does specifically for trailing-slash cases.
Neither form is better for rankings. What actually matters is picking one and being consistent — mixed usage across your internal links and sitemap is what creates the redirect noise in the first place.
Not on its own — a single clean 301 is the correct, Google-preferred way to handle it. It becomes a problem at scale: thousands of avoidable redirect hops waste crawl budget, and redirect chains from a slash mismatch have been documented costing sites thousands of wasted crawl hits after platform migrations.
Up to 2,500 internal pages in a single run. If your site is larger, run it, then use "Crawl more" — it resumes the same crawl instead of starting over.
No — it's scoped to your own internal link graph, since that's what you can actually fix. For external link health, a general broken-link checker is the right tool.
That page was live when it was crawled but may have changed since — or the link is coming from a cached template (nav, footer, widget) rather than the page body itself. Worth checking your theme's shared elements if the same source keeps reappearing after you've edited the page.
Build clean, valid Schema.org JSON-LD for rich results and AI answer engines — Article, Product, Local Business, FAQ, Event and more, with empty fields dropped automatically.
Build a valid XML sitemap by discovering your pages automatically or pasting a URL list — with lastmod, priority, and automatic splitting for sites over 50,000 URLs.