EnterraHost
Menu links
Present on nearly every page because the template puts them there. They help a visitor get around and they can help a crawler find a page, but no page chose to point at anything.
Crawls your site and draws how the pages link to each other. Shows what is buried, what nothing points at, and which links are really just the menu.
These pages are in the sitemap and carry no noindex tag, so the site is asking for them to be found, but no page links to them from its content. A page that is noindex, or kept out of the sitemap, is not listed even when nothing links to it. A page the menu reaches is still listed, because the menu gets a visitor there without any page recommending it.
| Page | Body links in | Reached by menu | Kind |
|---|
The distinction that matters
Every page carries the same menu and footer, so those links appear everywhere. Counted as ordinary links they give every entry in the menu the same inbound count, and the graph ends up describing your template instead of your linking. This tool separates the two, and only the second kind says anything about how your pages relate.
Present on nearly every page because the template puts them there. They help a visitor get around and they can help a crawler find a page, but no page chose to point at anything.
Written into a page on purpose, usually because the page is relevant there. These carry context as well as position, which is why they are the ones worth counting and fixing.
What counts as orphaned
An orphan here is a page that is in your sitemap, carries no noindex tag, and has no internal links pointing at it. All three conditions matter. A page you have deliberately excluded from search is not orphaned, however few links it has, and listing it would bury the pages that genuinely need attention.
The list separates two cases, because the fix differs. A page the menu reaches needs an editorial link from somewhere relevant. A page with no route in at all needs finding first, since a visitor following any link on the site never arrives there.
Crawling politely
The crawl reads your robots.txt first and does not fetch a path the wildcard group disallows, so a section you have closed to crawlers is not queued and not reported on. That applies to the sitemap seeding as well, so a URL your sitemap lists inside a disallowed path is skipped rather than fetched.
Two limits are worth knowing. Only the wildcard group is read, so a rule aimed at one named crawler is not applied. And matching is by path prefix, so a rule containing a wildcard is treated as a literal string and may not match what you intended. This tool crawls as a plain HTTP client rather than as a search engine, which is why a page you have blocked may still appear in the graph if a link to it is found on a page that is allowed.
Next
A page can be linked from all the right places and still send a visitor to an error if the target moved. The next check follows the links and reports what breaks.