Manage the next decision, not just a list of domains
A backlink register should help someone answer a practical question: what needs attention, who owns it and what evidence supports the next step? A list of domains cannot tell you which page contains a link, whether a delivery was accepted or who should decide about renewal. Give each placement a stable record identifier and keep its purpose with the record.
The register above uses six fictional cases to show the difference. Some need a check, one needs a commercial decision and another lacks basic provenance. Edit the proposed plans and download the handoff. The observations stay fixed, so assigning a task cannot silently rewrite what was recorded.
Keep placement identity and evidence references together
Record the complete source page and intended target page, not only their domains. Two placements on different pages of the same site may have different terms, owners and observations. If the source has not been supplied, leave it unknown instead of filling the cell with a publisher homepage. A purchase reference can identify the request while publication evidence is still missing.
Keep a reference to the supporting file or dated observation. Google’s link guidance describes a crawlable link element and its href. A domain appearing in an invoice or spreadsheet is not equivalent evidence. A reference ID also needs a discoverable storage location in a real team handoff.
Separate observation, agreement and action dates
The observation date says when a person or tool recorded the page. The agreement end date describes the recorded commercial term. The action due date is the date your team chooses for its next task. They answer different questions and should not overwrite one another. In the renewal case, an 18 October observation and a 31 October end date lead to a proposed review on 25 October.
Change the worksheet review date to see which tasks are due. This compares calendar dates inclusively: a task dated on the review day is due. It does not calculate invoice charges, extend a contract or certify that an old observation is still current. When an end date is unknown, preserve that gap rather than guessing a permanent term.
Do not turn a workflow label into a technical finding
The failed-check case retains an earlier evidence reference alongside the latest unsuccessful attempt. An unreachable page is a reason to investigate; it is not enough to declare a link removed. Similarly, an expired agreement describes the agreement, not the current HTML of the source. Keep both facts so the next owner can reproduce the question.
The relationship case records sponsored nofollow. Google recommends qualifying paid and user-generated links appropriately. Keep all observed values and clarify the relationship instead of removing a qualification to make a report look better. A plan marked ready here means only that its owner, action and date have been filled.
Build a queue with an owner and one specific next step
Start with unassigned records and missing evidence. Assign a role that can obtain the needed answer: editorial can request the published page, a reviewer can repeat a check, and operations can prepare a renewal decision. A useful task names the unresolved question and the evidence needed to close it. “Improve the link” is too vague to hand over.
Use the action-due view to arrange the next working session. It follows your edited action dates, not the recorded agreement end dates. Changing a role while filtering unassigned items removes the row from that view but keeps its plan open, avoiding accidental edits to a different placement. The all-record export retains hidden rows so a filtered screen cannot silently narrow the handoff.
Hand over decisions, open questions and accessible evidence
Choose the receiving role and add a short note for each record. A renewal note can ask for budget approval and the agreed next term; a delivery note can request the exact published URL and the check date. State what remains unknown and where the receiving person can find the agreement and evidence. Do not include passwords or private keys in a register.
Download a selected record as TXT, the full register as CSV, or the printable HTML handoff. A blank CSV contains only the column structure for your own records. The example’s CSV uses stable technical headers, while labels and notes use the selected language. Before sharing a real file, restrict it to the recipient’s permitted clients and confirm access to the referenced evidence.
Use the existing workspaces for their actual jobs
The panel’s My links area shows your purchased placements and articles, campaign grouping, dates and available monitoring observations, with filtered CSV export. The saved monitor handles supplied source–target pairs; the outreach workspace holds prospect drafts and follow-up work. A role chosen in this teaching register does not create account permissions, recurring billing or a task in those workspaces.
Treat imported backlink data as a separate input. Google’s Links report is sampled and may include links found earlier; it is not a current delivery ledger. Reconcile source coverage and dates before using a report in a campaign review. Keep search performance analysis separate from delivery acceptance: completing a record does not establish a ranking effect.