Return Link Tracking

How to Track Return Links in Link Exchange Deals

Stop over-giving in link exchanges. Track per-partner and per-project balance with a simple, honest model.

8 min read · Published January 15, 2026 · Updated August 17, 2026 · The LinkSwapy team

The short version

  • Over-giving is caused by ordinary process failures, not bad faith, which is why a ledger fixes most of it.
  • Count only verified live links, never agreed ones, or your balance flatters whoever makes promises.
  • Value given uses your own authority, not your partner's. Most spreadsheet versions get this backwards.
  • Reminders at 14 and 30 days work because the follow up is easy while the agreement is recent.
  • Per-partner tracking misses the aggregate case. Agencies and multi-brand teams need a rollup.
Return link tracking dashboard showing links given, links received, balance, and deal status
Return link tracking keeps every obligation visible from the original agreement through the live placement.

Over-giving is the quiet failure mode of link exchange work. You publish first as a gesture of good faith, the partner's slot slips, weeks pass, you agree another exchange elsewhere, and somewhere along the way your site is handing out more authority than it is taking in.

Almost nobody does this deliberately. It is the product of small, forgettable process failures, which is precisely why a running ledger fixes most of it. The vocabulary here, reciprocal link, return link, three way exchange, is worth pinning down before you build one. The tracking is not bureaucracy, it is the only thing standing between a reciprocal strategy and a subsidy.

This is the model we would use, including the formula details that spreadsheet versions usually get wrong. It is the same one behind return link tracking.

The basic ledger

Start with the simplest thing that works. One row per partner, two counts, one difference. Links they gave you, links you gave them, and the balance between them. Positive means they are ahead of their commitments, negative means you are.

Set a threshold for when negative becomes a problem. Two links is a sensible default, and one link of drift is normal in an active partnership rather than a grievance. Past the threshold, the rule is that you stop publishing in their direction until something comes back.

The critical detail, and the one that quietly ruins most homemade versions: count only verified live links. If you count agreed placements, your balance flatters whichever side has made promises rather than published, which is exactly backwards from what you need to know. A partner who agreed to five and published one has given you one.

Same discipline on your own side, including links you gave from other properties or other client sites. Undercounting your own giving produces a comfortable number and a bad decision.

Basic return link ledger with partner, source page, destination page, given, received, and next check fields
A useful ledger records both sides of the exchange and the next action, not only the backlink URL.

Weighting by authority

A straight count assumes every link is equivalent, which is fine when you and your partner are similar in authority and misleading when you are not. Five links from a strong publisher is not the same trade as five from a new blog.

So add a value calculation alongside the count, or run it in the return link balance calculator. Value received is their link count multiplied by their domain rating. Value given is your link count multiplied by your domain rating. The net is received minus given.

That asymmetry is the part people get wrong, and it is worth being explicit about. A link sitting on your site carries your authority to your partner, not theirs. So your side of the ledger uses your rating. Multiplying both sides by the partner's rating produces a number that looks rigorous and means nothing at all, and it is the single most common error we see in spreadsheet balance formulas.

Use count mode when you and your partners are broadly comparable, because it is simpler and simpler is more likely to be maintained. Switch to value mode when there is a real authority gap, because that is where count mode tells you a comfortable lie.

How exchanges drift one sided

Understanding the mechanisms is useful because each one has a different fix, and most of them are process fixes rather than tracking ones.

The publish first problem is the most common. You agree a mutual exchange, your content calendar has a slot this week, so you go first. Their slot is next month. Then their editor changes or the piece gets deprioritized and the reciprocal link never happens. Nobody decided to shortchange you.

The multiple teammate problem scales with team size, and it is the case agencies hit first. Two people each agree exchanges with the same partner, neither aware of the other. Every individual deal looks fine and the aggregate does not. This one is invisible without a shared record, and no amount of individual diligence prevents it.

Time decay is the reason thresholds need to fire early. A return link promised in March is genuinely awkward to raise in September: the context is gone, the person you agreed with may have left, and bringing it up feels like an accusation. So most teams write it off silently, which is why reminders at 14 and 30 days matter more than any escalation process.

Then the aggregate blind spot, which is the expensive one for agencies. The same publisher exchanging with three of your clients, each relationship looking balanced, the total heavily negative. Per-partner tracking cannot see it by construction.

Balanced link exchange becoming delayed and then unresolved as the return link remains outstanding
A balanced agreement becomes one sided when a delayed obligation stays invisible or unassigned.

Reminder cadence that works

The point of a cadence is to make the follow up easy while it is still recent, which is the same reason a removed link is chased in week one, because a specific, timely nudge works and a vague late one does not.

At day zero, record the obligation on both sides when the deal is agreed. This is the step that makes everything else possible, and it takes thirty seconds at the moment you have the context.

At day fourteen, a first polite nudge. Two weeks is about right: sooner reads as impatient to anyone with an editorial calendar, and it is early enough that the original conversation is fresh. Reference the specific agreement and the specific link you published.

At day thirty, treat it as a problem. Pause further giving to that partner and say so plainly rather than doing it silently, because a partner who does not know you have paused cannot fix the situation. At day sixty, treat it as unlikely and flag the partner for review.

Then actually enforce the pause. This is the step teams skip, usually because the next content slot is already filled and publishing is easier than having the conversation. A threshold you never enforce is not a threshold.

  • Day 0: obligation recorded on both sides
  • Day 14: specific, polite nudge referencing the agreement
  • Day 30: pause further giving and tell them you have
  • Day 60: flag the partner for review
  • Ongoing: exclude flagged partners from bulk outreach
Practical reminder workflow moving from due to a friendly reminder, blocker confirmation, and closure or escalation
A status-based cadence keeps follow-up respectful while giving unresolved obligations a clear endpoint.

Three way exchanges

A-B-C exchanges exist to avoid a direct reciprocal footprint. You link to site B, B links to site A, and no straightforward reciprocal pair appears anywhere. They complicate tracking in a specific way that is worth handling carefully.

Record each leg as its own row with its actual direction, and note the chain. The failure mode is double counting: logging the obligation once against B and once against A, then concluding that a partner owes you links they never agreed to provide. Getting this wrong produces exactly the confident, wrong number that damages a relationship.

Balance for a three way chain has to be computed per leg rather than per relationship. Your position with B is about what you gave B and what B gave you or arranged for you. Collapsing the whole chain into one balance figure loses the information you need to chase the right person.

Our honest view is that three way chains are worth the tracking overhead only if you are doing them at some volume. For a handful of exchanges the added complexity outweighs the footprint benefit, and a small number of relevant direct exchanges between real sites is not the thing that gets anyone in trouble.

Three way exchange among Sites A, B, and C with records for who gives, receives, and owes each link
Three way exchanges need each directional obligation recorded separately because the partner and returning domain differ.

Raising it with a partner

The number is the easy part, and the balance calculator produces it. Telling somebody they are behind without ending a relationship you want is the part worth thinking about.

Lead with specifics. We have published four links to you since January, most recently the piece on your pricing guide, and one has come back so far, just checking where the other three sit in your calendar. That is factual and low temperature, and it is far harder to ignore than a general reminder because it gives them something concrete to respond to.

Offer an exit. Editorial priorities change, and a partner who has decided not to proceed will find it easier to tell you if you make that acceptable. If it is no longer a fit, tell me and I will stop counting on it costs you nothing and converts a slow silent failure into information.

Do not threaten removal, in a first message or ideally at all. It is hostile, it ends the relationship permanently, and removing a link you already published does nothing for your own site. Pausing is the proportionate response.

One thing worth saying about your own obligations too. If a partner removed their link because the one you promised never arrived, that is not a recovery case and no email will fix it. Publish what you owe, then ask.

Put this into practice

Backlink monitoring, return link tracking, and lost link recovery in one workspace.

Questions

Questions about this topic

What is a reasonable over-give threshold?

Two links is a sensible default, and one is too tight because a single link of drift is normal in an active partnership. What matters more than the number is that the threshold triggers something automatic, since a balance nobody acts on does not change behavior and the partners exploiting it are the ones who noticed that first.

Should I remove a link if a partner never reciprocates?

Usually not. Removal is hostile, permanent, and does nothing for your own site, so it burns a relationship for no gain. Stop giving more, say plainly why, and leave the door open. Reserve removal for cases where the partner turned out to be somewhere you would rather not be linked from at all.

How do I track balance across multiple clients?

You need balance computed at two levels: inside each project, which is what the client report shows, and across the whole workspace, which is what protects you. The rollup is the only view that catches a partner trading with three of your clients while every individual relationship looks fine.

Do nofollow links count toward the balance?

Our view is that they should not count as fully given or received, and this catches people out. A partner who gave you five links, two of which are nofollow, has given you three links and two mentions. Check the rel attribute before you count anything, because it changes without notice and a straight count will overstate what you received.

Is it worth tracking this for just a few partners?

For two or three partners, probably not formally. You will remember. The threshold is somewhere around five active exchange relationships, or any point at which more than one person on your side is agreeing deals, because that is when the aggregate stops fitting in anybody's head.