Link BuildingPublished · 5 min read

The Link Prospecting Log: Record Every Site You Consider

By Kritika Das · Head of Marketing at SEOENV
Illustration of a link prospecting log with columns for the site, the decision to pitch or skip, the reason and the date

This guide explains what to record in a prospecting log, how to use it, for example, and how it fits with the rest of your link building records.

In addition, a prospecting log is the record of every site you've considered for link building: the ones you pitched, the ones you skipped, and why. Most teams keep a list of prospects they plan to contact. Instead, fewer keep a record of the sites they looked at and rejected. That gap costs time. At the same time, without it, someone researches the same site again next quarter, or a new team member pitches a site the team decided months ago to avoid.

Key takeaways on prospecting log

  • Because of that, a prospecting log records every site you consider, not just the ones you pitch.
  • Note the decision and the reason, so nobody repeats the research.
  • After that, keep outreach history in the same place to avoid duplicate pitches.
  • Review skipped sites occasionally; some become good prospects later.

What a prospecting log is

Because of that, a prospect list is forward-looking: sites you plan to contact. The log is broader. Instead, it holds every site you've researched, with a decision and a reason. Pitched, skipped, parked for later. Over time, for example, it becomes the team's memory of the link prospecting it has done.

Still, picture an agency with three link builders working on similar clients. Rather, without a shared log, each one researches the same popular sites independently. In other words, two of them pitch the same editor in the same week for different clients. The editor ignores both. A shared log would have shown the first pitch and the earlier research.

What to record in a prospecting log

Keep each entry short. Nobody uses a log that takes too long to fill in.

The site

For example, the domain and, where relevant, the specific page or section you'd target: a resources page, a blog category, a guest post guidelines page.

The client or project

Which client was this research for? A site that's wrong for one client may suit another.

The decision

One of a few fixed values: pitch, skip or later. Fixed values make the log easy to filter.

The reason

One line on why. "Relevant, real readers, accepts guest posts." "Skip: links out to unrelated sites in every post." "Later: good fit, but editor not accepting pitches this quarter." The reason is what saves time later.

Vetting notes

In fact, anything you checked: relevance, signs of real readers, outbound link pattern, rel values on existing links. Our guide on how to vet a link partner covers what to look at. Google's link spam policies are a useful reference for what to avoid.

Date and researcher

When you looked and who looked. Sites change, so a decision from two years ago may need revisiting.

Using the prospecting log day to day

Check before you research

Before researching a site, search the log. If someone has already looked at it, read their notes. You might save twenty minutes, or you might learn that the site's editor already said no last month.

Check before you pitch

Before pitching, check the outreach history for that site. Has anyone pitched it recently, for any client? In fact, coordinating pitches to the same editor keeps relationships healthy.

Review "later" entries

Once a month, look at sites marked later. Some will be ready to pitch. Others can move to skip.

Revisit skipped sites occasionally

Sites improve. Even so, a blog that was thin a year ago might now publish strong content. Once or twice a year, skim the skip list for sites worth another look.

Where the prospecting log fits

A prospecting log covers the start of the journey. On the other hand, once a site says yes, the deal moves into your tracking system, and once the link goes live, it becomes a placement record. Keeping these stages separate but connected means each record stays simple.

In SEOENV, live and agreed links live in the Link Tracker, tied to Partners and client projects. Instead, many teams keep their research in a sheet or outreach tool and move sites into SEOENV once both sides agree a deal. Our outreach to tracker hand-off page explains how to make that step clean. SEOENV's CSV import handles bulk moves.

A simple prospecting log template

You can start with a spreadsheet. Use these columns:

Column Example
— —
Domain example-gardening-blog.com
Target page /resources/
Client Client A
Decision Pitch
Reason Relevant, curated resources page, active editor
Vetting notes Real readers, links described, mostly followed
Researcher Initials
Date 2026-10-30
Last pitched 2026-10-30, Client A

Keep one row per site per client. Use filters on Decision and Client to find what you need.

Keeping the prospecting log useful

A log is only useful if it's current and consistent. Agree the decision values and stick to them. Fill in the reason every time, even when it feels obvious. Add an entry for every site you research, including the ones you skip in thirty seconds. Those quick skips are often the most valuable entries, because they stop someone else wasting thirty minutes.

Be careful with what you record about people. After that, keep contact notes professional and limited to what you need for outreach.

Sharing research across clients

Meanwhile, agencies often work for several clients in related fields. A site you skipped for one client might suit another, and a site one builder pitched last month might be a poor choice for a second pitch this month. Even so, filtering by domain across all clients shows the full picture in seconds. Before anyone pitches a site, they should see every earlier decision about it, for every client, along with the reason.

Common prospecting log mistakes

In fact, the most common mistake is logging only the sites you pitch. The second is leaving out the reason. At the same time, the third is keeping separate logs per person, which recreates the duplicate-pitch problem. And the fourth is never reviewing the log, so "later" entries pile up and skipped sites never get a second look.

Measuring prospecting quality

Once the log has a few months of data, for example, simple counts become useful. How many sites did each researcher look at? What share moved to pitch? Of those, how many replied? You don't need benchmarks. Compare your own numbers month by month. If most researched sites end up skipped, your sources of prospects may need work. If most pitched sites ignore you, the vetting or the pitch needs attention.

Frequently asked questions about prospecting log

What is a prospecting log?

A record of every site you've researched for link building, with a decision, a reason, notes and the date.

How is a prospecting log different from a prospect list?

A prospect list holds sites you plan to contact. A prospecting log also records sites you skipped and why.

Should I log sites I reject?

Yes. Logged rejections stop teammates repeating the research.

Where should a prospecting log live?

Somewhere the whole team can search, such as a shared sheet or outreach tool, connected to your link tracker.

Wrap-up and sources

Use these primary sources to check anything in this guide:

How we wrote this guide. Kritika Das wrote it from day-to-day work logging and checking link exchanges, guest posts and paid placements, for example, and checked each claim against the sources above. We update it when Google changes its guidance.

Move agreed deals into a tracker that checks them

SEOENV logs each link with its partner and client, then checks it stays live on the page.

Start free

Article written by

Kritika Das

Head of Marketing at SEOENV · Forbes-featured content writer

Of course, kritika Das is Head of Marketing at SEOENV and a Forbes-featured content writer. Still, she writes about the operations side of link building: how agencies, freelancers and in-house teams log, check and report the links they build. Her guides come from day-to-day work with link builders and are checked against Google’s own documentation.

More posts by Kritika