Orphan page (no internal links)
orphan_pageShort answer
The page is indexable but no other page links to it — it was found through the sitemap or an external link only. Google can still index it, but with no internal links it has no internal PageRank and little chance to rank. Link to it from related content and its category; if nobody should find it, remove it or take it out of the sitemap.
Why it matters
Internal links are Google's main signal for a page's importance within a site. Orphans are typically old campaign pages, articles whose category was deleted, products in an unpublished collection, or pages created by a plugin without being added to navigation. They are also a classic source of thin and duplicate content, because nobody looks at them.
How Glimana detects it
A site-level rule: indexable pages with zero inbound internal links in the crawl, excluding the home page. The SEO map's Structure panel shows the count and lists the pages with the reason.
How to fix it
- Find the affected pages in Glimana. Open Issues › Orphan page (no internal links). This is a site-level check, so the single row carries the full evidence: the URLs, values or days involved. The task under Tasks shows the same list and the expected gain.
-
Apply the fix on your platform.
- Open the task's page list and sort by 28-day clicks. Orphans with clicks are the priority — they rank despite being orphaned.
- For each page that should stay: add it to the category or hub it belongs to and link to it from two or three related pages.
- For pages that should not exist: 301 to the closest relevant page, or delete (410) and remove from the sitemap.
Assign the post to a category that is listed in navigation; add "related posts" blocks; check that the page is not excluded from menus by a page-builder setting.
Add the product to a published collection that is in the menu; add pages to the footer or main menu.
Generate category/listing pages from the same source as the sitemap, so that a page in the sitemap always has a listing link.
-
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 every affected page has at least one internal inbound link or is gone. 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
The next crawl recomputes inbound links; the task closes when every affected page has at least one internal inbound link or is gone.