Skip to content
atlookup

Internal Link Blocked from Passing Authority

rel="nofollow" on an internal link blocks PageRank flow to your own page — almost always a mistake outside of user-generated-content areas (comments, forum posts).

notice Impact: low ARCH_INTERNAL_LINK_NOFOLLOW 2 min read Updated

Why it matters

rel="nofollow" on an internal link blocks PageRank flow to your own page — almost always a mistake outside of user-generated-content areas (comments, forum posts).

Address when convenient — notices usually mark a polish opportunity rather than a defect. Estimated SEO impact: low — small marginal improvement, but cheap to fix.

How to fix

  • Remove rel="nofollow" from internal links
  • Use rel="ugc" or rel="sponsored" if the link is user-generated or paid
  • Keep nofollow only on login / admin / privacy-sensitive routes

Common causes

If the rule is firing across many pages, the root cause is almost always one of these:

  • Pages reachable only through search, sitemap, or external links — never from another internal page.
  • Deep section pages buried 5+ clicks from the homepage with no shortcut hub.
  • Important pages weakly linked because the navigation never surfaces them.
  • Broken internal targets after a slug or section rename without a redirect map.

Anti-patterns to avoid

Even with the best intentions, these "fixes" make the issue worse — recognise them so you don't ship them:

  • Hub pages only reachable via the sitemap, not from any header or body link.
  • Pagination depth so high that ?page=42 is the only way to reach important content.
  • Renaming sections without adding redirects.

How atlookup detects this

Our crawler renders each page with a real headless browser, then builds a graph of internal links across the entire crawl and analyses orphans, depth, and weak nodes. Pages where the rule fires for internal link blocked from passing authority are flagged on the report.

If you'd like to see this rule fire on your own site, run a free 60-second audit — every page is reported with the exact lines that triggered it.

Tools to verify the fix

Once you've applied the fix, double-check with these external validators:

  • Screaming Frog — Crawl-depth + orphan-page reports.
  • Sitebulb — Visual graph of internal link weight distribution.

Frequently asked questions

Why does Internal Link Blocked from Passing Authority matter for SEO?

rel="nofollow" on an internal link blocks PageRank flow to your own page — almost always a mistake outside of user-generated-content areas (comments, forum posts).

How do I fix internal link blocked from passing authority?

Remove rel="nofollow" from internal links Use rel="ugc" or rel="sponsored" if the link is user-generated or paid Keep nofollow only on login / admin / privacy-sensitive routes

Is this a critical SEO issue?

Address when convenient — notices usually mark a polish opportunity rather than a defect. Estimated SEO impact: low — small marginal improvement, but cheap to fix.

How does atlookup detect internal link blocked from passing authority?

Our crawler renders each page with a real headless browser, then builds a graph of internal links across the entire crawl and analyses orphans, depth, and weak nodes. Pages where the rule fires for internal link blocked from passing authority are flagged on the report.

How long does it take to fix?

5–15 minutes per page. Most teams batch similar issues across templates so the per-page time goes down at scale.