Internal linking, explained without the jargon

It comes up on almost every project, usually later than it should. Here is internal linking without the vocabulary that usually surrounds it.

Search engines are trying to answer a question, so the pages that answer questions clearly tend to do well. Most teams find the first pass takes an afternoon and the maintenance takes minutes a month.

The short version

Internal links spread authority to the pages that need it. None of that requires a large budget, only a decision and someone to own it. Doing this properly once is usually cheaper than doing it approximately three times.

Why people complicate it

Most of the confusion comes from tooling rather than from the idea itself. Getting it slightly wrong is survivable. Ignoring it entirely is not.

Descriptive anchor text beats "click here" every time. None of that requires a large budget, only a decision and someone to own it. The teams that stay on top of it are the ones who put it on a calendar rather than a wish list.

A reasonable first step

Orphan pages rarely rank at all. The cost of getting this wrong is rarely visible on the day it happens. It rarely shows up as a line item, which is exactly why it slips.

In practice

Technical fixes remove obstacles; content earns the position. Both are needed and they are not interchangeable. Three things worth confirming about internal linking before you move on:

• Someone can say what the current setup is without going to look
• Orphan pages rarely rank at all — and you know whether that is true here
• There is a way to tell whether the last change to this helped

Pick the one that would hurt most if it failed, and start there.