Link building spreadsheet templates help turn research into a record of decisions, applications, published sources and review actions. Start with the worksheet matching your immediate task, then connect records with a stable ID. A spreadsheet should explain what happened rather than make an unverified campaign look successful.
The files below are real CSV downloads containing headers and illustrative examples. They do not include prebuilt dashboards, macros, automated integrations or approved publishers. Use the resources hub for supporting guides and the templates index to browse all downloads.
Choose the right download
| Worksheet | Use it for | Download |
|---|---|---|
| Prospect tracker | Candidate fit, terms and next action | Prospect CSV |
| Outreach tracker | Pitch history and follow-up decisions | Outreach CSV |
| Backlink audit | Source, target and review notes | Audit CSV |
| Placement check | Evidence for a known published link | Verification CSV |
| Migration map | Old destinations, replacements and redirects | Migration CSV |
| Directory tracker | Application and publication states | Submission CSV |
| Listing preparation | Approved facts and assets | Listing pack CSV |
| Referral outcomes | Visits, leads, purchases and costs | Outcome CSV |
Pick one starting worksheet. You do not need to build an eight-sheet system before qualifying your first prospect. Add complexity when the work requires it, and keep field definitions understandable to the person maintaining the data.
Import the CSV without losing the data
Use your spreadsheet application's import function and check the preview. Keep URLs and identifiers as text, and choose a consistent date format. Review the delimiter and encoding before accepting the import.
Replace the illustrative example rows with your own approved data. They demonstrate field structure, not verified publishers or campaign results. Do not contact an example address or report fictional outcome numbers.
Keep an untouched copy of the download if you want to return to the initial structure. Save your working version with a campaign name and date. A backup is especially useful before sorting, merging or importing another export.
Give every active record an owner and next action
A useful record says what is needed and who will do it. “Check current eligibility with official rules” is an actionable note. “Good site” is not. Assign a review date only when there is a real follow-up or maintenance reason.
Keep statuses explicit. A prospect can be unqualified, eligible, ready for outreach or rejected. A submission can be pending or published. A link can be found, absent from fetched HTML or awaiting manual review. These states should not collapse into “done.”
The directory tracker guide provides a status model. The prospecting guide helps organize earlier research.
Record evidence before scores
Save the source URL for publisher rules and the date checked. Describe audience fit and relevant examples. If a platform requires a launched product or membership, record whether the business meets that requirement.
Domain metrics can be supporting fields, but they should not override eligibility. Avoid formulas that automatically approve a prospect because its authority score is high. The directory quality guide shows why a failed eligibility gate should remain a rejection or pause.
Keep provider names attached to metrics. Moz DA and another vendor's score should not be mixed in one unnamed “authority” column. Record missing values as unknown rather than guessing a number to make a sorting formula work.
Connect research and publication records
Use a stable ID to connect the original prospect with outreach, submission and publication evidence. A listing URL may change; the record ID can preserve continuity. Do not create a new “won” row merely because someone sent a follow-up.
For publication, save the actual public source and exact target. Then inspect the website link and attributes with the live backlink checker, noting limitations when the source cannot be fetched.
The placement verification guide explains this stage. A receipt is evidence of an application; a public page and checked link are later observations.
Use formulas only after defining the fields
The following formulas are optional examples to add to a working sheet. They are not preinstalled in the downloadable CSVs. Adapt column letters to your layout and spreadsheet locale.
For an illustrative table with Status in B, Submitted Date in C and Next Review in D, a review flag in row 2 can be:
=IF(AND(B2="Submitted",D2<>"",D2<=TODAY()),"Review due","")
For days since submission, leave unsubmitted rows blank:
=IF(C2="","",TODAY()-C2)
These formulas organize work. “Review due” is not proof that a publisher is late, and days since submission do not establish when a link will be indexed. Follow the publisher's actual process.
Use valid denominators for campaign rates
Count only records in the relevant cohort. An application-to-publication rate should use submitted applications as the denominator, not every row in a discovery list. State how pending applications are treated and which period the cohort covers.
An outreach reply rate should use a consistent unit, such as unique contacted prospects with a reply divided by unique contacted prospects. Counting every follow-up as a new prospect can distort the rate. Email opens are also a different observation from meaningful replies.
For a simple rate table with sessions in B and verified purchases in C, an optional row formula is:
=IF(B2=0,"",C2/B2)
Format the result as a percentage. A blank zero-session result is clearer than hiding undefined data as 0%. The referral measurement guide provides worked examples and attribution limits.
Keep costs and revenue labels precise
Record staff time, tools, content preparation, publisher fees and recurring obligations separately where practical. A free listing is not necessarily a zero-cost campaign when several hours of work are involved.
Keep currency in its own field. Do not sum different currencies without a documented conversion method and date. Distinguish planned budget from actual spend, and record recurring fees so they do not disappear after the first month.
For outcomes, distinguish gross revenue, net revenue and contribution margin. Revenue minus campaign costs is not automatically profit. Product delivery and other business costs may still need to be included. Use the ROI guide to define the measure before building a dashboard.
Worked example: a small submission batch
This scenario is illustrative. A team starts with twenty candidate directories, qualifies eight and submits six. Two candidates remain ready but unsent. Four submitted applications become public listings, while two remain pending.
The team reports twenty researched candidates, eight eligible candidates, six applications and four published listings. It does not report twenty backlinks or call the four published pages a 20% acceptance rate without explaining the denominator.
After checking the four public pages, three website links are observed and one needs manual review because the tool was blocked. The team records those states separately. It does not claim all four are indexed in Google.
These distinctions make the next action clear: follow up on pending applications, inspect the unresolved link and decide whether the remaining eligible routes are worth the effort.
Create views for decisions
Useful views include Ready for outreach, Submitted and due for review, Published and awaiting link check, Upcoming renewals and Rejected routes. Filter rather than deleting historical rows to make the current work easier to scan.
A manager's summary can show counts by defined stage, actual costs and unresolved questions. It should link back to the underlying records. If the total cannot be reconstructed, the dashboard is not reliable enough for a spending decision.
Avoid dashboards that equate a vendor metric increase with customer revenue. Tool metrics, verified placements and business outcomes each need their own evidence and labels.
Maintain the records after the campaign
Review important placements when the site changes its name, product details or URLs. Use the migration map when old destinations need relevant replacements. Keep both the old and new URL so redirects can be checked.
Retain rejected candidates with reasons. This prevents repeated research and helps new teammates understand why a seemingly attractive site was skipped. Keep public rules and evidence references, while excluding passwords, private tokens and payment details from shared files.
A lightweight maintained sheet is more useful than an elaborate abandoned system. Choose fields the team can keep accurate and add automation only after the manual definitions work.
When a prospect database is useful
These templates provide workflow structure, not a research list. If your missing input is candidate destinations, review the Complete Backlink Database Bundle. It contains 276 opportunities with recorded categories, submission links, costs and tips in a CSV.
The bundle does not include approvals, live traffic estimates or verified search indexing. Use the database guide and sample to decide whether the fields suit your task. Move suitable rows into your tracker and add your own current checks.
What to read next
Continue with the prospecting spreadsheet guide, directory tracker and backlink audit template. Plan capacity with the directory submission plan and run source checks with how to audit backlinks.