A link outreach tracking sheet is the record that shows, for every publisher you have approached, who wrote to them, when, what they answered and where the conversation ended. The short answer: one shared sheet, one row per publisher, a status column with a single owner, dated contact fields and a verification column that records the rel value actually seen on the live link. Up to a point that setup does the work of a separate CRM. If you run link acquisition for an agency client, inside a small SEO team or for your own site, the same three problems appear: writing twice to one editor, losing track of who promised what, and being unable to give a straight number on Friday.
Example scenario: a horse riding stables wants coverage for its beginner lessons, its summer pony camp and its trail-ride booking page. Google's documentation has no statement on how to manage an outreach process. It does set limits on link spam and describes how to qualify outbound links, and a US Federal Trade Commission guide covers email honesty. The sheet layout is a practical suggestion; the limits come from those pages.
Why a sheet: writing to the same publisher only once
Outreach is work that several people can do against the same pool of publishers. An agency might have two account managers who each pitch the same regional equestrian magazine for different clients. A small team might have one person send a first message early in the month and a colleague send another one two weeks later. The first job of the sheet is to make that overlap visible before it happens: no message goes out until the publisher has a row.
Duplicate-contact checks before any send
An editor who receives two first messages from the same organization reads it as disorganization and may stop replying or mark the sender as unwanted. The sheet lowers that risk by controlling the record rather than the inbox: sender, first-message date and latest status sit on one row. The rule is simple enough to need no software. Search the domain, find nothing or find the row, and only then write.
Sheet or CRM: a decision rule
Decision rule: if the number of active rows is small enough for one person to hold in mind, a sheet is enough. If several people edit the same rows and you need reminders, shared inbox sync or sequences, a CRM becomes worth the cost. Practical suggestion: run the sheet for a month, settle the columns and status codes, then pick a tool. A tool bought before the columns are stable fills up with the wrong fields.
The one thing that must survive a move from sheet to CRM is the meaning of each status code. If the codes live in a written dictionary, switching tools is a mapping exercise instead of a clean-up. The list of publishers that feeds the sheet is built before outreach begins; see candidate publisher list for an SEO project for that step. The tracking sheet starts where that list ends.
Stages: prospect, first message, follow-up, reply, publication, verification
Six stages describe the path a publisher row takes. Each needs an entry test and an exit test. Where the exit test is not written down, rows stall between stages and the weekly report stops being trustworthy.
| Stage | Entry test | Exit test | Who acts |
|---|---|---|---|
| Prospect | Topic fit and contact source recorded | Someone has claimed the row | Whoever builds the list |
| First message | Row is open and owned | Send date and template version recorded | The sender |
| Follow-up | No reply, next date set | A reply arrives or the follow-up limit is reached | The sender |
| Reply | A written response exists | The reply type is coded | The sender |
| Publication | The publisher has put the piece or link live | Live URL and date recorded | The verifier |
| Verification | Live URL is in the cell | Link, target address and rel value checked | The verifier |
Entry and exit tests in practice
A prospect row is not yet a contact. It holds a site name, a topic fit and an address source, and it leaves the stage when someone claims it. A prospect that nobody claims within two weeks goes to the archive with a short reason code. At first message, store the send date, the sender and the name and version of the template instead of pasting the whole email. That lets you compare which template version drew which kind of reply. How to write the message itself is covered in how to write a backlink outreach email.
The follow-up stage holds only rows without a reply. Keep the next follow-up date and the follow-up count in separate cells, set a ceiling on the count and move any row that reaches it to a closing status. What the ceiling should be is your decision. A reply moves the row according to what it says: interested, asking about terms, declined or redirected. A positive and a negative reply do not share a code, because reply rate and publication rate measure different things. When a reply redirects you, the new contact gets a new row and the old row closes as redirected.
Publication is a claim, not a result. The row records the live address and date and stays open. Verification then opens the page and checks that the link is present, that it points to the intended target and which rel value it carries. The stage is complete only once the verification date is written. Later monitoring adds a second verification date to the same row.
Where rows stall
Rows stall in three places: after the first message when nobody schedules the follow-up, after a positive reply when terms are discussed off the sheet, and after publication when nobody opens the page. A row that sits in a stage past its date goes on a stale list that the owner clears each week.
Columns: publisher, contact, topic, date, rel, status
Every extra column is one more cell that goes stale. Before adding a column, ask which line of the weekly report it will feed. If the answer is none, leave it out. The table of columns is the smallest set that covers a publisher row from first contact to verified link.
| Column | What it holds | Fill-in rule |
|---|---|---|
| Publisher | Site name, domain and page type | Domain is written in one fixed format so duplicates can be found by search |
| Contact | Name, role and the source of the address | The source is a public page such as an imprint or contact page |
| Topic | The piece or page being offered | Names the target page on your site |
| Dates | First message, last touch, next follow-up, publication, verification | Separate cells, one date format |
| Rel | The rel value seen on the published link | Filled only after verification, not guessed |
| Status | One code from the list | Chosen from a dropdown, changed only by the row owner |
| Owner | The person responsible for the row | If the row is handed over, the previous owner is kept in notes |
| Notes | Free text | Anything that will be counted in the report does not belong here |
Contact provenance
Next to the address, record where it came from: the publisher's imprint page, a contact page or an address the publisher gave you. An address with no recorded source cannot be traced when someone asks to be removed or objects to the message. How to find and confirm the right contact is its own subject; the sheet stores only the outcome and its source.
Rel: expected versus observed
Google's page on qualifying outbound links says that for regular links you do not need to add a rel attribute. It names sponsored for advertisements and paid placements, ugc for user-generated content and nofollow for cases where the other values do not apply, and it allows several values in one attribute separated by spaces or commas. The page states that links marked with these attributes "will generally not be followed" (Opens in a new tab). In the sheet, keep the value you expected under the agreement in one cell and the value you saw on the live page in another. When they differ, the row raises a flag and the publisher may need a correction request.
If a placement was paid for, it should be documented and the link qualified, so a sponsored value in that cell is the expected result rather than a defect. For a record structure that handles accept, reject and hold outcomes, the one in quality backlink decision log can be attached to this sheet row by row.
Status codes and closing reasons
A status code names the present state of a row in one word. Keep the list short, give each code exactly one meaning and refuse values from outside the list. A free-text status cell produces rows the weekly count cannot see.
| Code | Meaning | Next step |
|---|---|---|
| prospect | On the list, no owner yet | Claim it or archive it |
| sent | First message has gone out | Set the follow-up date |
| followup-1, followup-2 | Follow-up sent, number recorded in the code | Wait for a reply or close |
| reply-interested | Publisher wrote back with interest | Settle the piece and terms |
| reply-terms | Publisher asked for payment, conditions or changes | Record the decision, then accept or decline |
| redirected | Publisher named another person | Open a new row for that person |
| live | Piece or link is published | Send to verification |
| verified | Link, target and rel were seen | Add to the monitoring dates |
| on-hold | Decision postponed with a review date | Review on that date |
| closed | Process over, closing reason recorded | Archive |
Closing reasons
A closed row without a reason tells you nothing. Choose reasons from a short list too: no reply and follow-up limit reached, publisher declined, terms not acceptable, topic did not fit, publisher withdrew the piece, or removal or objection request received. Separate codes for each let you tell which closings are process failures and which are the publisher's decision.
The parking rule
The on-hold code is not an open-ended parking lot. Every held row has a review date, and a row past that date turns up as a warning in the weekly report. Decision rule: if nothing has changed by the review date, the row moves to closed with a fitting reason. Reading held rows next to the evaluation logic in designing a link building experiment helps decide which publishers stay inside a test.
Guardrails: what the sheet must not record
A sheet records work; it does not make questionable work acceptable. Google's spam policies (Opens in a new tab) define link spam as creating links to or from a site primarily to manipulate search rankings. The examples include buying or selling links, excessive link exchanges, large-scale article marketing or guest posting campaigns with keyword-rich anchor text, and using automated programs to create links. The policy also says paid links are not a violation as long as they are qualified with nofollow or sponsored, and that violating sites may rank lower or not appear at all.
Those limits shape what the sheet contains. It has no column for automated mass sends, hidden links or link-swap arrangements. If a placement is paid, the sheet says so and the expected rel is sponsored. Copying another site's text and resending it in different words, trying a route the publisher has not allowed, or breaking a site's terms of use cannot be part of the process.
Email honesty: a general principle from the FTC guide
The FTC's CAN-SPAM compliance guide (Opens in a new tab) is a US email guide. It is not Turkish or EU rules and is read here only as a general principle of honest email. According to the guide, header information must be accurate and identify the person or business who started the message, and the subject line must reflect the content. A commercial message must be clearly identified as an advertisement, carry a valid postal address and explain plainly how to opt out. The guide asks that opt-out requests be honored within 10 business days. It says it makes no exception for business-to-business email and that hiring another company to send the email does not hand the responsibility over.
For the sheet this has one practical consequence. The moment someone asks you to stop, the row moves to closed with the removal reason and the request date is written down, and the address does not return to a send list. Keeping the date shows when the request was processed. The sheet is not a substitute for working out which commercial messaging and personal data rules apply to you in your own country.
Personal data in the sheet
The contact column holds personal data. Limit access to the people who need it, keep the address source on record and set a date for deleting personal fields from rows that will not be used again. The notes column should not carry details about a person's private life.
Weekly report: sent, replied, published, verified rates
The weekly report comes from counting status codes. It should not need fresh data entry; if it does, the sheet is incomplete. Four counts are enough: first messages sent, publishers who replied, pieces published and links verified.
Denominators, stated every time
A rate without a denominator cannot be compared week to week. Reply rate divides publishers who answered by publishers who received a first message. Publication rate divides published pieces by publishers who gave a positive answer. Verification rate divides verified links by published pieces. Rows sent in one week and published in another belong to different cohorts, so group by send week when computing publication rate.
| Measure | Numerator | Denominator | What it tells you |
|---|---|---|---|
| Reply rate | Publishers who replied | Publishers sent a first message | Whether the message and the choice of publishers worked |
| Publication rate | Pieces or links published | Publishers who answered positively | Whether terms discussions reach an outcome |
| Verification rate | Verified links | Published pieces | Whether publications match what was agreed |
Small weeks
With only a handful of rows, a percentage misleads. State the count instead and keep the rate for weeks or months with enough rows to make a ratio meaningful. The report carries neither payment amounts nor private notes nor the content of a publisher's private emails. It is a summary anyone who can read the sheet could reproduce.
One change per week
Each report should end with a single proposed change for the next week. If the reply rate is weak, look at the template or the publisher list. If replies arrive but nothing is published, look at the terms discussion. If publications fail verification, open a correction thread with the publisher. Changing several things in one week makes it impossible to tell which one worked. Agencies that want to split this report per client can adapt the approach in scalable link building process for SEO agencies.
Reading the numbers: three diagnostic questions
Counts only help if they lead to a decision. Three questions turn the weekly report into one.
| Symptom in the report | First place to look | Single change to try |
|---|---|---|
| Rows closing for no reply | Template version and publisher fit | Rewrite the first line of the message or tighten the list criteria |
| Replies arrive, nothing goes live | Reply-terms rows and how long they sit | Reply faster and state your terms in the first answer |
| Live rows, verification fails | Rel mismatch and missing target | Send the publisher a short correction request |
| Rows pile up in on-hold | Review dates | Close rows that have passed their date |
The same table gives a team a shared vocabulary. Instead of arguing about whether outreach is working, people point to the symptom and the first place to look.
Running the sheet across a team or agency
A shared sheet works when everyone writes to it the same way. The rules stay the same for two people and for twenty; only the number of people filling each role changes.
Roles
Separate three roles: the person who builds the list, the person who sends and the person who verifies. In a small team they may be the same person, but having someone other than the sender verify lowers the chance of misreading a live page. A site owner working alone can get the same effect by verifying on a different day with a written checklist.
Editing discipline
The rules fit in three lines: no message goes out before the row exists, only the row owner changes the status, and every status change is dated the same day. If any of the three is broken, the sheet no longer reflects what happened. A first tab with the code dictionary and column definitions should be read by anyone new before editing.
Several clients in one sheet
An agency serving several clients adds a client column and runs the duplicate check across all of them. If two clients need the same publisher, the rows are linked and one person plans both messages together. To record what kind of source each publisher is and how it has been used, the usage log in agency backlink source inventory fits alongside this sheet.
Example scenario: a horse riding stables
Example scenario: a horse riding stables wants a mention for its beginner lessons, its summer pony camp and its trail-ride booking page. The prospect list contains a regional equestrian magazine, a local family events guide and a pony-care blog. Three rows are opened, each owned by the stables' manager.
| Publisher | Contact | Topic | Status | Rel |
|---|---|---|---|---|
| Regional equestrian magazine | Features editor, address from the imprint page | Summer pony camp | followup-1 | Not yet |
| Local family events guide | Listings editor, contact page | Beginner lesson schedule | live | Awaiting verification |
| Pony-care blog | Blog owner, contact form | Trail-ride booking guide | closed, topic did not fit | None |
When the family events guide publishes the lesson schedule, the status becomes live. The verifier opens the page, sees that the link reaches the stables' lesson page and carries no rel value, and sets the status to verified with the date. The magazine has not replied, so its next follow-up date is in the sheet, and when the ceiling is reached the row closes with the no-reply reason. The blog owner found the topic unsuitable; the row is archived with that reason, and the note is read before anyone writes to that blog again.
A second idea for the same publisher
Months later the stables want to offer the events guide a holiday riding-day idea. The first step is a search of the domain in the sheet. The row is verified and its rel value is on file, so a new idea entry is added under the existing row instead of a new row. The first-message date records a second topic proposal, and the earlier outcome in the notes shapes how the message is written.
In the weekly report the three rows read as follows: three first messages sent, one reply, one piece published, one link verified. With so few rows the report gives counts, not rates.
Checklist: before you start using the sheet
- Each publisher has one row and the domain is written in a single format.
- No message is sent before the row exists.
- The status column is a dropdown and each row has exactly one owner.
- The contact cell records where the address came from.
- The code dictionary is written on the first tab.
- A ceiling on follow-ups is set.
- Held rows carry a review date.
- The rel cell is filled only after verification.
- A closing reason exists for removal and objection requests.
- The denominators of the weekly rates are written down.
Mistakes
Bending a code to improve a number
Leaving a row at live so it looks as though publication is ahead, or writing verified before the link has been seen, makes the report worthless. The code states what happened, not what was hoped.
Writing the status as free text
Cells such as "waiting", "soon" or "probably interested" cannot be counted. Those thoughts belong in notes; the status cell takes a code.
Treating the publisher's word as proof
An editor writing "we published it" is not verification. The row is not finished until someone has opened the page and seen the link, its target and its rel value. Proving that a link is still live by other means is a separate task; the sheet stores only the outcome and the date.
Leaving a removal request in the inbox
If a publisher asks you to stop writing, the row closes and the address does not return to a send list. Leaving the request only in an email thread lets a colleague write to the same address.
Sharing the sheet as a client report
The sheet is a working record. A report for a client or manager summarizes its counts. The sheet itself holds personal data and correspondence notes and is not shared along with the report.
Frequently Asked Questions
Do I need a separate CRM for link outreach?
No. If the number of active rows is small enough for one person to follow, a shared sheet is sufficient. A CRM is worth considering when several people edit rows at once and you need reminders or a shared inbox. Practical suggestion: test the columns and status codes in a sheet for a month before choosing a tool.
How many follow-ups should the sheet allow?
Practical suggestion: choose a ceiling, test it against your own reply data and let the sheet enforce it. The follow-up count sits in its own cell, and a row that reaches the ceiling closes with the matching reason.
Who should verify a live link?
Practical suggestion: someone other than the sender, which lowers the chance of misreading the live page. A site owner working alone can get the same effect by verifying on a different day with a written checklist.
How do I record a paid placement?
Google's spam policy says paid links are not a violation as long as they are qualified with nofollow or sponsored. The row states that the placement is paid, expects sponsored, and verification looks for that value. The amount does not go into the weekly report.
What happens when a publisher asks to be removed?
The row moves to closed with the removal reason, the request date is written down and the address is not put back on a list. The FTC's CAN-SPAM guide asks that opt-out requests be honored within 10 business days.
What belongs in the notes column?
Free text only. Anything that will be counted in the weekly report belongs in its own column instead, and the notes column should not carry details about a person's private life.
Should every teammate keep a private copy?
No. Private copies bring back duplicate contact. Keep one shared sheet and let only the row owner change a row's status.
Conclusion
The job of an outreach tracking sheet is plain: one row per publisher, one owner per row, one code per state. When stages carry written exit tests, duplicate contact disappears, the weekly report becomes a count of codes and verification turns a publication claim into evidence. Google's spam policy and its page on qualifying outbound links set the limits of what the sheet may contain, and the FTC guide offers a general yardstick for honest email.
If you would rather buy editorial placements with verified links than run the whole process yourself, you can look at the backlink packages.
Post a comment
Please log in to leave a comment. Login