Page has no internal links (dead end)
no_internal_outlinksShort answer
This indexable page contains no links to other pages of your site — not even a menu or a logo link. Crawlers that arrive here cannot continue, and readers have nowhere to go. Add navigation and links to related pages, the category and the home page.
Why it matters
Internal links carry both discovery and value. A dead end wastes the authority the page has earned and ends the visit. The usual causes are landing pages built without a header, pages rendered by a different template (print, AMP, embeds) or navigation injected only by JavaScript.
How Glimana detects it
The rule fires for an indexable 200 page with zero internal links in the crawled HTML. If the menu exists only after JavaScript runs, see Content depends on JavaScript rendering.
How to fix it
- Find the affected pages in Glimana. Open Issues › Page has no internal links (dead end). Every affected page is a row; open one to see the evidence Glimana recorded for it (the measured value, the offending element or the target URL). The same list sits on the task card under Tasks, and the page's own detail view under Pages shows its full signals.
-
Apply the fix on your platform.
Landing-page templates ("blank canvas") hide header and footer; add a minimal nav or related links block. Check that the menu is server-rendered.
Pages using a template without header/footer sections: add a header section or link the logo.
Include the site navigation in every public template; add contextual links in the content.
-
Publish and clear caches. Save and publish, then make sure the crawler will see the new version: WordPress — clear the page cache in your cache plugin and purge the CDN; Shopify — theme and content changes go live on save, but purge any CDN in front of the store; custom code — deploy and purge the edge cache. Check in a private window or with
curl -s https://your-domain/page | grep -i '<title\|canonical\|robots'that the live HTML has changed; Glimana reads what the server sends, not what your browser has cached. - Verify in Glimana. Open the task under Tasks and click Mark as done. The affected pages are queued for a verification crawl within a few hours, and the task closes when the page links to at least one internal page. If the check still fails, the task returns to New with a note; when it passes, the task is listed under Resolved technical issues on Impact reports. To check sooner, use Re-crawl affected pages on the issue.
How the fix is verified
Re-crawl; the task closes when the page links to at least one internal page.