Link gap

You are not trying to win the web. You are trying to win the few sites that already link to pages like yours. Those domains have proven they will link to this topic. That is why the list is small and qualified.

Example: three guides rank for "API rate limits". Two have links from apiblog.example and devnotes.example. Your /guides/api-rate-limits has none. The gap is those two domains and the exact pages they used as sources.

1. 1

   Pick the pages to compare

   Choose one target page of yours, like /guides/getting-started, and a few rival pages that rank for the same query.

2. 2

   Get referring domains for each page

   Use any backlink index that shows referring domains and linking URLs for a given URL. Export or copy the lists. Include the anchor and the linking page title if available.

3. 3

   Subtract your set from theirs

   Find domains and URLs that link to at least one rival page but not to yours. Keep it at the page level first. Then repeat at the domain level for your whole site.

4. 4

   Score and sort

   Score each prospect by topical fit, anchor relevance and the authority you observe in that index. Sort by fit first, then by observed authority.

• Referring domains to rivals but not to you: the size of your opportunity list.
• Linking page type: resource page, roundup, forum thread, changelog, documentation. Page type tells you the pitch and link format to expect.
• Anchor and surrounding text: shows the angle that earned the link. Match that angle in your pitch or content.
• Target depth: links to the rival home page, /pricing or a deep guide. If most links are deep, fix your equivalent deep page.

A healthy gap list is specific. It names apiblog.example/post-123 with anchor "API rate limit examples" rather than a vague domain note.

1. 1

   Tighten your target page

   Check on-page basics: title near 60 characters, clear h1, descriptive meta, fast LCP under 2.5 seconds, internal links from relevant pages. Make it the best answer.

2. 2

   Map pitch to page type

   For a resource page, offer your guide and why it helps their readers. For a roundup, suggest inclusion and provide a one line summary. For a documentation page, offer a clearer example or correction.

3. 3

   Close content gaps that block links

   If rivals earn links for a comparison or a checklist you do not have, ship your /guides/api-rate-limit-checklist or /compare/tool-a-vs-tool-b page first.

4. 4

   Send small, specific pitches

   Write to the editor of that one page. Reference the exact sentence that links to a rival. Offer your page as a better or complementary source. Keep it short and specific.

5. 5

   Pick up easy wins

   Find broken links among the gap set. If a linking URL 404s or points to a dead resource, offer your equivalent. Fix your own broken backlinks as well.

A fixed case looks like this: your /guides/getting-started gains links from a tools roundup, a university resource page and a dev forum thread soon after targeted outreach.

• Comparing home pages only when the query is page level. Always compare like with like.
• Chasing every domain. Start with high fit pages, not just high authority domains.
• Pitching without a content fit. If your page does not answer the cited need, update it before you ask.
• Copying rival anchor text blindly. Match search intent, not just words.
• Relying on one index. Spot check with a second source or manual searches like "site:example.com your topic".