💡 17 ideas for adding relevant internal links at scale


You’d never guess but:

Internal links are important.

(And are still highly undervalued).

Role of internal links

✅ Determine the importance of pages within the site

✅ Influence the ranking potential of the website pages

✅ Help Google understand the website architecture and crawl your website

✅ Internal links provide the context of your content (through anchor text)

✅ Help users navigate from one page to another

Here are 17 ideas for adding internal links at scale, i.e. using link blocks

​

Links on the homepage

  1. The most important pages
  2. Recent content (for faster indexing)

​

Links on service pages

  1. Links to specific services/ sections (e.g. Moving services; Dance styles)
  2. Links to other service pages

​

Links on category pages (eCommerce)

  1. Related categories (horizontal)
  2. Sub-categories (vertical)
  3. Specific products (vertical)
  4. Relevant guides or blog posts
  5. Breadcrumbs
  6. Related searches

​

Links on product pages (eCommerce)

  1. Related products
  2. Up-sells
  3. Breadcrumbs

​

Links on blog posts/guides

  1. Links to related posts
  2. Blocks with links to related products
  3. Recent posts
  4. Breadcrumbs

Here's an example of a link block which is usually added on a template level (vs a page level):

🚀 Psst... By the way

The Tech SEO Pro course has a full module dedicated to internal linking 😎

In this module, you will:

  • Learn all secrets of creating a winning URL structure (including one thing that 99% of SEOs don’t know)
  • Understand how to handle URLs with parameters (heads up: it’s not always straightforward)
  • Know how to build the right website structure and 1 of the most important things that should drive your decisions
  • Learn the answers to the most discussed topic: Buttons vs. Links
  • Learn how to set up internal linking at scale
  • Understand how to set up pagination the right way
  • Learn the best ways to use faceted navigation for eCommerce websites

​

The module is available in both Core and Premium packages 🔥

​Check out the legendary Tech SEO Pro course>>​

​

Grab this free resource 👇

17 ideas for adding relevant internal links at scale

Download a free PDF with a copy of this email, so it's easy for you to get back to it when you need (no signup required) 👇👇👇

​

Smart SEO Newsletter

I'll help you trade an imposter syndrome for a technical SEO superpower. My mission is to break down and simplify complex technical SEO things so that you can understand and use them to advance your SEO career.

Read more from Smart SEO Newsletter

Do you know what the Critical rendering path is? It’s what your browser goes through in order to build a beautiful usable page from your source code. It requires communication between the server and browser: Steps to render a page in a browser (Critical rendering path) Begin constructing the DOM by parsing HTML incrementally Request CSS and JS files Parse CSS and construct CSSOM Execute JS, build a render tree Merge Document and CSS Object Models Run layout and paint Optimizing critical...

This shouldn’t come as a surprise to you: Google uses rendered HTML of your page to evaluate the page’s optimization. First, let’s make sure we’re on the same page here. What is rendered HTML? Rendered HTML is displayed after CSS and JavaScript are processed. It means that if you’re only relying on the source code for your SEO efforts, it’s easy to miss many important things that can be altered by JavaScript, such as: Rewritten title tag A sneaked noindex tag A removed canonical Added/removed...

Critical knowledge alert 🚨🚨🚨 As a technical SEO, it’s crucial you know the difference between source code and rendered HTML them. Source code It is the initial code of the page before any JavaScript files are executed and CSS files are parsed. It’s the code you see when viewing the source code of a page in your browser. Rendered HTML It is displayed after CSS and JavaScript are processed. When you inspect an element on a page using Chrome dev tools, you’re looking at the rendered HTML. Why is...