Internal linking for blog posts

Internal linking for blog posts carries a post's value to the pages that bring you customers: without links, good posts stay isolated. Every post links up to the page it leads to, down to its own sub-pages, and receives links from related pages on the day it goes live.

  • The hub model is the default. The homepage body links to at most 3 of your main service or product pages (header and footer menus aside). Every other page links up to its parent with a link in the first sentence, and down to its own sub-pages.
  • Add deliberate cross-links only where a reader really moves between two topics: for example, frozen pipes and boiler pressure, or a bathroom renovation and floor heating. Keep them few and name them in the link plan.
  • The footer is the one exception to the hub model: it links to your 4 to 6 most important pages (the main services or products and the price list) on every page.
  • Every post links up to the offer it leads to and to the statistics page for the figures it uses.
  • Use contextual links in body copy, on the same domain, underlined, with descriptive anchors, where the sentence gives the reader a reason to click.
  • Offer related posts at the end for readers who aren't ready to act.
  • Every post has links in and out. Links out go to related posts, the product, service or collection it leads to, and the statistics page. Links in come from existing pages that discuss the topic, with natural descriptive anchors, added on the day the post goes live.
  • Remap the whole site when content is added. Each new post is a reason to recheck the full link map, not only the new page's own links.
  • Make small link edits every month from data (chapter 13): a page that gained authority or impressions links to the pages that benefit from it.
  • Draw the structure: each page as a bubble (a shortened title) and each link as a line. Audit it from a distance.
  • Fix orphan pages, broken links, duplicate IDs and broken anchors.

The pillar and its supporting pages change with the business.

  • For a local service business: each area page links up to the service it belongs to, and the service page lists its areas in one place.
  • For an online store: posts link to the collection and the products they discuss, and each collection links back to its two or three best guides, with the collection's own term as the anchor (chapter 14).
  • For a software or B2B company: posts link to the use-case or feature page they support, and each of those pages links back to its two or three best guides.

Anchor text

The anchor is the clickable text of a link, and it tells the reader and the search engine what waits on the other side.

  • Write the anchor as the target page's own topic, in the words a reader would use: "keyword research for blog posts", never "this guide".
  • Vary the anchors that point at one page across the site, so they read naturally.
  • Keep links inside sentences that give a reason to click, and never stack three links in one sentence.
  • Never use the same anchor for two different pages. One anchor names one page.

The link map is one document that lists every page on the site, where it sits and how it connects. It lives with the site, not in anyone's head, and every new post starts with it.

  • One row per page: its address, the one search it owns, its parent, the pages that link to it and the pages it links to, with the anchor of each link.
  • Plan a new post's place before you write it: its parent, the two or three existing pages that will link to it, and the two or three pages it will link out to. A post with no planned links in is an orphan on the day it goes live.
  • Addresses in the map are evergreen: descriptive words only, never dates or numbers, so a link written today still points at the right page in five years.
  • Every link in the map has a reason a reader would follow it. A link that only exists for search goes.
  • Recheck the whole map when a page is added, merged or retired, and give every retired address a one-hop redirect to the page that took over its job.

A long guide split into chapters works as a pillar and its cluster, and its links follow the same model.

  • The hub is the pillar: the whole method in prose, with a link down to every chapter from the sentence that summarises it.
  • Every chapter links up to the hub in its breadcrumb and its navigation, and across to the chapter before and after it.
  • Chapters link to each other only where a reader really moves between them, with the target chapter's own topic as the anchor.
  • Posts outside the series link to the chapter that answers their reader's next question, and the chapter links back where the post goes deeper.

Between sites and to the outside

  • Earn links; never buy or automate them. Industry directories and listings first, then trade and local press, associations, sponsorships and forums. No paid links, private blog networks or link schemes.
  • Relevance beats size. A regional trade association linking to a roofer beats a large international blog about everything.
  • Keep paid partnerships separate from earned editorial links, and mark paid links as sponsored.
  • Link every statistic and industry figure to its original source.

A full link check needs no expensive tools: a crawler, a spreadsheet and an hour.

  1. Export every internal link with a crawler into a spreadsheet: the page it is on, the page it points to, and its anchor.
  2. Find the pages with no links in. Each one gets a link from its parent and from one related page the same day.
  3. Sort the anchors by target page. One anchor pointing at two pages, or ten identical anchors pointing at one, get fixed at once.
  4. Compare the result with the link map. A link that isn't on the map is either added to it with its reason or removed.
  5. Check the status of every target. Each internal link points straight at a page that answers 200, with no chain of redirects.

Run this check once a quarter and after every big change to the site's structure, and log the small monthly edits with their effect.

  • Andres Lepik, co-founder and head of growth at REND, with a short beard, smiling in a black REND cap and T-shirt against a light grey backgroundEdited by Andres LepikCo-founder & Head of Growth
  • Siim Saar, head of SEO at REND, with stubble, in a black REND cap and T-shirt against a light grey backgroundFact-checked by Siim SaarHead of SEO
Rasmus Kivi, co-founder and CEO of REND, smiling in a black REND cap and T-shirt against a light grey background

Post by Rasmus Kivi

Co-founder & CEO

Co-founded REND and still reads every client's monthly report himself before it goes out.