> ## Documentation Index
> Fetch the complete documentation index at: https://docs.atomicagi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Interlinking

> Strengthen internal link structure to improve discoverability and authority flow

<Frame>
  <img src="https://mintcdn.com/atomicai/66wBloPCX-icbC_a/images/data/technical/app-technical-interlinking.png?fit=max&auto=format&n=66wBloPCX-icbC_a&q=85&s=20790b6e38550d045736e217461df2f6" alt="Interlinking page with internal links table, score, incoming links, and outgoing links" width="1536" height="960" data-path="images/data/technical/app-technical-interlinking.png" />
</Frame>

Use Interlinking to find pages that are under-supported by internal links, then fix structure before rankings and crawl efficiency decline.

## Questions this page should answer

1. Which pages have weak internal-link support?
2. Which important pages are not receiving enough incoming links?
3. Where should we add internal links first to improve discoverability?

## Before you analyze

* Start with high-value page groups (commercial and core category pages).
* Sort by `Score` and check low-score pages first.
* Check both views (`Table` and `Mind map`) before final prioritization.

## What this page gives you

* Two views of the same internal-link dataset:
  * `Table` view for page-level prioritization
  * `Mind map` view for structure and cluster analysis
* URL-level metrics:
  * `Score`
  * `Incoming links`
  * `Outgoing links`
* Clickable nodes in mind map to inspect incoming and outgoing relationships.

## How the Interlinking page is organized

The top-right view toggle switches between:

* `Table` icon: row-level internal-link health
* `Mind map` icon: network-style structure view

Use both in sequence:

1. Start in `Table` to identify weak pages.
2. Switch to `Mind map` to see why those pages are weak structurally.
3. Build fix tickets based on both row metrics and graph context.

## Table view: prioritize pages by link health

<Frame>
  <img src="https://mintcdn.com/atomicai/66wBloPCX-icbC_a/images/data/technical/app-technical-interlinking.png?fit=max&auto=format&n=66wBloPCX-icbC_a&q=85&s=20790b6e38550d045736e217461df2f6" alt="Interlinking table view with score, incoming links, and outgoing links by internal URL" width="1536" height="960" data-path="images/data/technical/app-technical-interlinking.png" />
</Frame>

This is your execution view for weekly link fixes.

What each column means:

* `Score`: link health indicator for the page.
* `Incoming links`: how many internal pages support this URL.
* `Outgoing links`: how many internal paths this page gives to others.

How to interpret:

* Low score + very low incoming links means discoverability risk.
* High outgoing with low incoming can mean a page gives value but receives little support.
* Many pages with similar low score in one folder usually means a structural linking gap.

How to decide from table patterns:

* Low `Score` + low `Incoming links`:
  * page is likely under-discoverable and under-supported.
* High `Incoming links` + low `Outgoing links`:
  * page receives equity but does not distribute it.
* Good `Score` but weak commercial impact:
  * check link source relevance, not only count.

## Mind map view: diagnose structure, clusters, and dead ends

<Frame>
  <img src="https://mintcdn.com/atomicai/66wBloPCX-icbC_a/images/data/technical/app-technical-interlinking-mindmap.png?fit=max&auto=format&n=66wBloPCX-icbC_a&q=85&s=70e658a5a3200d1e1e627ca185a18845" alt="Interlinking mind map view showing internal URL nodes with incoming and outgoing link counts" width="1536" height="1024" data-path="images/data/technical/app-technical-interlinking-mindmap.png" />
</Frame>

Use this view to understand site structure at a glance.

What you are seeing:

* Each card is a URL node.
* `In:` is incoming internal links to that URL.
* `Out:` is outgoing links from that URL.
* Connecting lines show internal-link paths between levels.
* Node color reflects relative support strength (more incoming links = stronger node).

How to use the mind map controls:

* Drag to pan across the network.
* Use `Show more / Show less` controls per level to expand dense layers.
* Click any node to open detailed incoming/outgoing relationship lists.

How to interpret map patterns:

* Isolated nodes:
  * usually orphan-like pages with weak internal distribution.
* Tight clusters with few bridges:
  * strong local linking but weak cross-cluster authority flow.
* One dominant hub with many dependents:
  * concentration risk if hub weakens or is de-prioritized.

## Practical workflow: table first, mind map second

Use this order:

1. Fix low-score commercial pages.
2. Fix low-score category and hub pages.
3. Switch to mind map and verify each priority page has strong path support.
4. Add links from high-authority hubs to isolated or weak nodes.
5. Re-check table scores after publishing.

## Quick weekly checklist

1. Sort by lowest `Score`.
2. Identify pages with weak `Incoming links`.
3. Validate weak pages in `Mind map` to confirm structural gaps.
4. Add contextual links from stronger, relevant pages.
5. Verify anchor text quality and topical match.
6. Recheck both views after updates are published.

## What to fix first

| Pattern in interlinking table                  | What it usually means              | Recommended action                                           |
| ---------------------------------------------- | ---------------------------------- | ------------------------------------------------------------ |
| Low score and near-zero incoming links         | Page is isolated in site structure | Add links from relevant high-authority internal pages        |
| Strong page with weak outgoing links           | Link equity is not redistributed   | Add contextual links to related commercial/content pages     |
| Whole folder with weak scores                  | Template or navigation gap         | Add section-level link modules and related-content blocks    |
| Incoming links concentrated from one page type | Fragile link distribution          | Diversify linking sources across templates                   |
| Node looks isolated in mind map                | Page is structurally disconnected  | Add bridge links from relevant hubs and nearby clusters      |
| Dense cluster but weak cross-cluster links     | Authority stays trapped locally    | Add cross-cluster contextual links with strong anchor intent |

## Team routine

1. Weekly:
   Review low-score rows and publish link fixes.
2. Bi-weekly:
   Review mind map cluster health and bridge coverage.
3. Monthly:
   Track score lift, incoming-link distribution, and affected traffic.

## Keep in mind

* Raw link count is not enough. Relevance and context matter most.
* Template-wide/footer links do not replace contextual in-content links.
* Interlinking results are cumulative; judge progress over several weeks.
* Use this page with `Cannibalization`, `Landing pages`, and `SEO audit` to align fixes with business impact.

## Where to go next

* [Cannibalization](/data/technical/cannibalization)
* [SEO audit](/data/technical/seo-audit)
* [URL indexing](/data/technical/url-indexing)
* [Google Search landing pages](/data/google-search/landing-pages)
