GenGrowth1. Enter your domain
No verification, login, or plugin. Submit any publicly reachable HTTP(S) website.
Free internal link audit · live public crawl
Internal Link Audit
One live crawl maps observed same-origin HTML links, pages with little observed support, sitemap-only orphan candidates, and targets that need a follow-up check.
Run my internal link audit free
Free · No sign-up · No software to install · Any public website
Start from the public URL and follow same-origin static HTML links while respecting robots.txt. Crawl facts may be temporarily cached by the server; submitter identity and page body are not stored.
No login required · up to about 950 pages per run · crawl runs for up to about four minutes
How it works
Four steps from a domain to a repair list
Enter a public website and receive a report based on observed static same-origin HTML.
- 01
- 02
2. We crawl and build the tree
The crawler starts from allowed site entry points, respects robots.txt, follows same-origin HTML links, and records observed structural evidence.
- 03
3. Review what the structure exposes
Candidate orphans, pages with low observed inbound support, homepage click depth, and unresolved targets are shown with their evidence limits.
- 04
4. Carry reviewed fixes into your plan
Review the evidence before making changes. The public tool does not create a project or alter your website.
What it finds
A live internal link audit shows structural evidence
It inspects the connections between pages, not just the contents of one URL.
01
Unresolved internal targets
See a source page and observed anchor when a target was not collected. It is a follow-up check, not a claim that the target is broken.
02
Orphan pages — the ones nothing links to
Compare sitemap URLs with pages reached through internal HTML links. The gap is a candidate orphan, with the sitemap and rendering limits shown.
03
Observed sitemap coverage
The report shows whether a sitemap was collected and how many sitemap URLs were observed, so orphan candidates have visible scope limits.
04
Pages with one or fewer observed inbound links
These pages are not necessarily orphans, but they have one or fewer observed inbound HTML links in this online run.
05
Observed inbound relationships
Observed inbound HTML links make it easier to review which collected pages have structural support. This is not a PageRank calculation.
06
Source and anchor evidence
For an observed relationship, the report can show the source page and recorded anchor text to support a manual review.
07
Observed homepage click depth
The report computes the shortest observed static-HTML link path from the homepage. Indexable pages at four or more clicks are highlighted; sitemap seeds improve coverage but never shorten this path.
08
Review-ready findings
Each finding includes observed evidence and a limitation so you can decide what to verify before changing your site.
09
A scannable page hierarchy
One shortest observed homepage path organizes each reachable page; unreachable groups and additional inbound links remain visible as separate evidence.
Method transparency
How we decide what counts as a problem
What counts as an orphan
A sitemap URL that the crawl never reached by following internal HTML links. If the sitemap is missing or stale, that limitation must travel with the result.
What counts as thin-linked
One or fewer observed inbound HTML links in this online run. Navigation, JavaScript-rendered links, and uncollected pages can change this count.
Where a crawl starts and stops
The crawler stays on the validated origin, respects robots.txt, uses allowed site entry points, and may stop at an explicit time, request, response-size, redirect, concurrency, or host-pacing boundary.
Honest limits
What this audit will not tell you
Links that exist only after JavaScript runs
A raw-HTML crawler can miss client-rendered links. Surprising orphan results on a heavily rendered site must be treated as a hypothesis, not a verdict.
Whether a page deserves to exist
Zero inbound links does not mean “add links” automatically. Thin, duplicated, or obsolete pages may be better consolidated or removed.
Working links that point somewhere unhelpful
A crawler can prove a target responds; it cannot reliably infer that a technically valid destination is the best editorial destination. Semantic misdirection is deferred.
Who it is for
For sites whose structure no longer fits in one person’s head
It becomes useful around dozens of pages, especially after a migration, a URL restructure, a large content batch, or template-generated publishing.
Compared with Screaming Frog
Screaming Frog is more complete for deep technical work and large crawls. This browser-based tool aims to remove installation and interpretation overhead by returning a prioritized repair brief.
Compared with Search Console’s internal-links report
Search Console reports pages Google already knows. This crawler independently compares observed sitemap discovery with collected internal HTML relationships and their limits.
FAQ
Internal link audit FAQ
01What is an internal link audit?
It crawls static same-origin HTML connections and reports candidate orphans, low observed inbound support, homepage click depth, and unresolved targets with clear limits.
02How is this different from an internal link checker?
A checker usually verifies whether links work. An audit also evaluates the structure those links create, including orphans, weakly connected clusters, and repair opportunities.
03Do I need Search Console or site verification?
No. The online audit reads public pages and does not require OAuth, a verification file, or ownership. It starts only after you submit a URL; public crawl facts may be served from a temporary shared cache to avoid repeated traffic to the same site.
04Does this find orphan pages?
The audit compares observed sitemap URLs with URLs reached through collected internal HTML links. A sitemap-only URL becomes a candidate orphan with evidence limits attached.
05How much of a site will the free audit crawl?
No account and no sign-up. One run reaches roughly 950 pages — four minutes at the 250 ms pace the crawler holds so it does not overload the site being audited — and a larger site comes back marked partial coverage, with findings that depend on having seen the whole site reported as unchecked rather than as conclusions. An hourly ceiling per network and per audited site sits well above normal use.
06How often should I audit internal links?
Quarterly is enough for many sites, plus immediately after migrations, URL restructures, template changes, or large content releases.
07Which findings should I review first?
Start with candidate orphans and low-inbound pages that matter to your site, then verify unresolved targets from important source pages. The report does not automatically confirm broken links.
08Should I fix every orphan page?
No. First decide whether the page should exist. Consolidating or removing thin, duplicated, or outdated pages can be better than adding links to them.
09Will this work on a JavaScript-rendered site?
Partially. The current crawler reads static HTML, so links injected by client JavaScript may be missed. Cross-check unexpected orphan candidates.
10Can I export the results?
Not in this online tool. It shows a visual report only and does not create a CSV export.
Continue exploring
Related tool
Website Health MapCheck one page’s crawlability, technical signals, on-page basics, and evidence limits.See every free toolEditorial roadmap
Related reading being prepared
- PageRank sculpting: what it is and whether it still works
- How to fix orphan pages without a desktop crawler
- Site architecture for SEO: depth, clusters, and crawl budget
Next step
Turn reviewed link fixes into a site-structure plan
Internal links are one step in the larger GenGrowth workflow. Continue in the full product when you are ready to review them alongside the rest of your growth plan.