How to Add Internal Links to Old Blog Posts (and Why Old Posts Deserve Them First)

Adding internal links to old blog posts means revisiting published articles and linking them to newer, related articles — and linking newer articles back — wherever the link genuinely helps the reader. It improves navigation and discovery without requiring a single new article.

TL;DR / Key Takeaways

• An internal link is a link from one page on your site to another page on the same site.
• Old posts often have the most authority and traffic on a small blog, so links placed in them carry real weight.
• Link only where the reader would naturally want to go next; a forced link helps nobody.
• Use descriptive anchor text that names the destination topic, not vague phrases such as "click here".
• Use standard HTML links with an href attribute so search engines can follow them.
• Audit first, then link in small batches, then check that every new link still works.

What Is Retrofitting Internal Links?

Retrofitting internal links is the deliberate process of returning to published posts and weaving them into the rest of your site. When a blog is new, each article tends to stand alone. Over time, that isolation becomes a problem: a reader who lands on a two-year-old guide has no obvious route to the newer guide that answers their next question, and a search engine crawling that older page finds no path onward to your newer work.

The term "internal linking" itself is simple. As explained in the Rankenza glossary, internal linking is the practice of linking between pages on the same website. Retrofitting is simply doing that work after publication, rather than only at the moment of writing. It is maintenance, not a trick, and it belongs in the same category as updating facts, fixing broken links, and refreshing an out-of-date introduction.

There is a useful distinction to keep in mind. Navigation links — your menu, footer, and category pages — help people move around your site in general. Contextual links, the kind this guide is about, sit inside the body of an article, at the exact point where a reader is thinking about a related idea. A menu link says "here is everything we cover." A contextual link says "this sentence reminded you of a question, and here is the article that answers it." Both matter, but only contextual links can be retrofitted with real precision, because only they sit next to the relevant thought.

How Internal Links Work

Internal links work on two levels at once: for people, and for search engines. For people, a link is a shortcut. Instead of returning to a search engine or hunting through a menu, the reader follows a single click to the next useful page. That only works if the destination genuinely continues the thought.

For search engines, links are a discovery mechanism. Google Search Central explains in its link best practices that Google uses links as a signal when determining the relevancy of pages and to find new pages to crawl. The same documentation is clear about the technical requirement: generally, Google can only crawl a link if it is an anchor element with an href attribute, and links that rely only on script events may not be parsed. In plain terms, a link that is not a normal HTML link may be invisible to a crawler, no matter how good it looks on screen.

Google Search Central makes a second point that matters directly for old posts: every page you care about should have a link from at least one other page on your site. An old post that nobody links to, and that links to nothing, is an orphan in practice even if it sits in your sitemap. Retrofitting is how you fix that. When you link from a well-read older post to a newer one, you give the newer page a path to be discovered, and you give the older page a reason for the reader to stay.

Anchor text is the visible, clickable wording of a link, and Google Search Central advises that good anchor text is descriptive, reasonably concise, and relevant both to the page it sits on and to the page it points to. That advice is worth following literally. If the destination is a guide to refreshing old content, the anchor text should say something close to that, in the reader's own language, rather than hiding the destination behind a generic phrase. The Rankenza glossary entry on anchor text covers the same idea from the reader's side: the words around and inside a link set expectations about what comes next.

Why Old Posts Deserve Attention First

New posts usually get links naturally, because the writer is thinking about the whole site while drafting. Old posts do not get that treatment unless someone goes back. Three reasons make them the best place to start.

First, older posts are often your most visited pages. They have had the longest time to be found, shared, and linked to from elsewhere. A link placed in a page that already receives visitors will be seen and followed; a link in a brand-new page that nobody has found yet will wait.

Second, older posts are the most likely to contain gaps. When you wrote a guide two years ago, the follow-up articles did not exist yet, so the post could not link to them. Every article published since then is a missing connection. Closing those gaps turns standalone posts into a connected set of guides.

Third, old posts decay. Links inside them break, recommended tools change, and internal references go stale. A retrofitting pass is also a repair pass: while you are adding links, you spot the ones that no longer work. Google's SEO Starter Guide reinforces the broader point that previously published content should be checked and updated as needed.

Common Mistakes When Adding Links to Old Posts

Adding links for the sake of a count

There is no magic number of internal links per post. A short post may need only two or three; a long guide may support a dozen. The test is always the same: would a reader at this exact sentence want this destination? If the answer is no, or only "maybe, for SEO reasons," leave it out. Google Search Central warns against chaining links next to each other and against cramming keywords into anchor text, both of which make pages harder to read and weaker as a guide to the destination.

Using the same anchor text for different destinations

If every link on your site says "our guide" or repeats the same keyword phrase, neither readers nor search engines can tell the destinations apart. Vary the wording to match the actual topic of each destination, and let the surrounding sentence do some of the explaining. The anchor text should be understandable on its own, but it does not have to carry the whole meaning alone; the sentence around it matters too.

Linking only to new posts, never from them

Retrofitting is a two-way job. When you publish a new article, link back to the older posts it builds on. When you revisit an old post, link forward to the new article. A one-way pattern — old posts pointing at new ones, but new posts never acknowledging the old ones — leaves the older work stranded in the other direction, and readers who arrive on the new post have no route back to the foundational guide.

Forgetting the technical basics

A link in a button that only works with JavaScript, a link with no href attribute, or a link to a URL that redirects in a chain can all fail the basic test of being a normal, crawlable link. Keep body links as plain HTML anchors and check that each destination returns a proper page, not an error.

Step-by-Step: How to Add Internal Links to Old Blog Posts

Step 1: Make a simple inventory

List your published posts in a spreadsheet or a plain document, with one row per post: title, URL, main topic, and the question it answers. You do not need fancy software for a small blog. The inventory is the map; without it, you will link from memory and miss the posts you forgot you wrote. Include the posts that perform best and the posts that almost nobody visits — the second group is often where the biggest gaps are.

Step 2: Find the orphans and the dead ends

An orphan is a page with no internal links pointing to it. A dead end is a page with no useful links pointing out. Scan your inventory and mark both. If a page appears in your sitemap but has no contextual link from any other article, it is a candidate for a new inbound link. Prioritise orphans that cover topics your newer posts already mention.

Step 3: Match posts by reader intent, not by keyword

For each old post, ask what a reader would want next after finishing it. A reader who just finished a guide to choosing blog topics might next want help with research, or with planning a calendar. A reader who finished a post about refreshing content might next want a checklist for the refresh itself. Match on that next question, not on whether two posts share a keyword. Keyword matching produces links that feel mechanical; intent matching produces links that feel helpful, which is the standard Google's people-first content guidance asks writers to meet: after reading, the visitor should feel they have learned enough to achieve their goal, not that they need to search again.

That intent-first approach is also why the Rankenza article on how to choose blog topics customers actually search pairs well with older planning posts: it starts from the customer's question rather than from a keyword list, and a link to it makes sense wherever an old post mentions choosing a topic without explaining how.

Step 4: Place links where the thought occurs

Open the old post and read it as a reader, not as its author. Wherever the text mentions a concept that another post explains in full, that is a placement. Add the link to the most specific words that describe the destination, and keep the sentence grammatical after the link is added. Aim for links spread through the body, not dumped in a block at the end. A "related posts" box at the bottom is a useful supplement, but it is not a substitute for a link placed where the reader is already thinking about the topic.

Step 5: Write anchor text a stranger could understand

Read each new link out of context. Would someone who only saw the linked words know roughly what they will get? If the linked words are "this guide," the answer is no. If they are "internal linking strategy for blogs," the answer is yes. Keep anchors reasonably short — a phrase, not a whole sentence — and do not repeat the identical anchor for different destinations across the site. Where two destinations are genuinely similar, let the surrounding sentence distinguish them.

Step 6: Fix what you find while you are in there

While editing, check every existing link in the post, not just the new ones. Remove or update links to pages you have deleted, and repair links that point to the wrong version of a page. A broken-link check is a natural part of this pass, and Rankenza's broken link checker is built for exactly this kind of scan: run it over the pages you touched before you consider the job done. This is also the moment to update any facts that have changed since the post was written, because a post you have just re-linked will receive fresh attention, and fresh attention on stale facts is an avoidable embarrassment.

Step 7: Link forward from new posts as well

After you finish the old post, open the newer destination post and check whether it links back. If the new post introduces a concept the old post covers in depth, add a return link. This two-way pattern is what turns a list of articles into a topic cluster: a group of related posts that reference each other and collectively cover a subject in depth. The Rankenza guide to how to refresh old blog content for SEO is a good companion here, because refreshing and retrofitting are usually done in the same editing session, and a refresh without new links leaves half the value on the table.

Step 8: Publish, verify, and record the change

Save the updated post and open the live page. Click every new link, confirm each destination loads and reads naturally in context, and note the change in your inventory — the date and the links added — so the next pass does not repeat the same work.

What a Good Retrofit Looks Like

How This Looks on Rankenza

The manual way to retrofit internal links is slow in exactly the ways described above: export a list of posts, read each one, remember which newer articles exist, decide on anchor text, and then repeat the whole process for the next post. For a blog with dozens of articles, that is a full day of careful reading, and it is easy to miss the orphans because no single view shows you the whole map at once.

The practical workflow for a Rankenza customer starts from a different place: each article is researched from top-ranking pages for its keyword, filtered for the searcher's intent, checked by a human, and linked internally from the customer's own sitemap, so a new article arrives already connected rather than standing alone as an orphan. Then spend a short retrofitting pass adding forward links from the two or three older posts that most naturally lead into it. The first article is free, and later articles are $3.60 each or $89 for 50, so the cost of testing this workflow on a single topic is low. You can see the current options on Rankenza pricing. No result is promised for any individual article; the value is in the connected structure you build over time, one linked article at a time.

There is no fixed number. A short post may need only a few links; a long guide may support more. The right test is reader intent: add a link wherever a reader would genuinely want to continue to a related article, and stop when the remaining candidates feel forced. A page crowded with links is harder to read, and Google Search Central's own advice warns against chaining links together without surrounding context.

No. Start with the posts that already receive visitors and the posts that are orphans, then work outward in small batches. Linking in batches makes it easier to check your work: you can click every new link and record the change before moving on, rather than ending up with dozens of unchecked edits.

Both, and the two directions serve different readers. A link from an old, well-read post to a new post helps the new post get discovered. A link from a new post back to an old guide helps a new reader find the foundational explanation. Do the direction that matches the reader's journey in each case, and where both directions make sense, do both. One-way linking leaves half the journey unmapped.

Only if you change the date yourself, and you should not do so merely to make a post look fresh. Google's people-first content guidance lists changing a page's date without a substantial change as a warning sign of search-engine-first content. A retrofitting pass that adds genuinely useful links and fixes broken ones is a real update, so recording an honest "updated on" note is reasonable.

Sources

• Google Search Central, "SEO Link Best Practices for Google" — links as a relevancy and discovery signal, crawlable anchor elements with href attributes, descriptive anchor text, and the advice that every page you care about should have a link from at least one other page: https://developers.google.com/search/docs/crawling-indexing/links-crawlable
• Google Search Central, "SEO Starter Guide: The Basics" — organising a site so search engines and users understand how pages relate, linking to relevant resources, and checking previously published content and updating it as needed: https://developers.google.com/search/docs/fundamentals/seo-starter-guide
• Google Search Central, "Creating Helpful, Reliable, People-First Content" — the self-assessment questions for helpful content, including whether a reader leaves feeling they have learned enough to achieve their goal: https://developers.google.com/search/docs/fundamentals/creating-helpful-content

FAQ

How many internal links should an old blog post have?

Should I add internal links to every old post at once?

Is it better to link from old posts to new posts, or the other way around?

Will adding internal links to old posts change their publication date?