The opportunity file: a system for documenting reviewable link-building decisions
An operational record for documenting what is known, what is estimated, what is interpreted, and why a link-building opportunity is approved, deferred, or rejected.
Why a list of opportunities alone does not explain a link-building decision
A list of potential domains, contacts, or publications helps organize prospecting, but it does not retain the reasoning that led to selecting one option over another. If only a URL, a metric, and a cost are recorded, it becomes difficult to later answer basic questions: what objective the campaign pursued, what was directly verified, what conditions were accepted, or what risk was assumed. The opportunity file turns each assessment into a reviewable decision. It is not intended to find a universal score or predict SEO outcomes. Its purpose is to provide useful traceability so another person can understand the context, challenge the assumptions, and compare similar decisions over time. This is especially valuable for agencies and teams working across multiple projects. Staff turnover, budget changes, and evolving market conditions should not erase accumulated learning.
- An opportunity is not just a domain: it includes objective, context, conditions, and risks.
- The record should explain the reason for the decision, rather than merely store data.
- A good record makes it possible to compare decisions without turning metrics into absolute verdicts.
What an opportunity file should contain: campaign objective, opportunity context, and review date
Every file should begin with the specific purpose of the assessment. It is not enough to state that a link is being sought. It is helpful to define which project the opportunity is being assessed for, which page or type of content is to be supported, which topic must be respected, and what budget, timeline, market, or internal-policy constraints exist. Next, document the context of the opportunity: URL or internal identifier, proposed type of collaboration, page or section reviewed, contact person or channel where relevant, and the conditions known at the time of review. The date is essential because availability, content, prices, and editorial policies may change. If the same opportunity is reassessed, the previous record should not simply be overwritten. It is better to create a new review or maintain a change history. This distinguishes what was known then from what is known now.
- Project and campaign identifier.
- Operational objective of the assessment and related asset or content.
- Review date, person responsible, and information source.
- Opportunity context and conditions known at that time.
- Review history if the data or decision changes.
How to distinguish direct evidence, estimated data, and analyst hypotheses
The quality of the file depends on separating categories that are often mixed together. Direct evidence is what the team has verified: the visible content of a page, a published editorial policy, a written response received, or a confirmed contractual condition. It should include a source and verification date. Estimated data comes from tools, models, or in-house calculations. It can guide comparison, but it does not describe reality with certainty and should not be treated as equivalent across providers. For example, an estimate of traffic, visibility, or authority may be useful as a signal, provided it is identified as an estimate, along with the tool, the date, and, where relevant, the configuration used. Hypotheses are working interpretations: that an audience will probably be interested in a topic, that an editorial format may fit, or that a publication could remain stable. They are legitimate when labeled as such and when the supporting basis is explained. The problem is not forming hypotheses, but recording them as if they were facts.
- Label each item as direct evidence, an estimate, or a hypothesis.
- Add the source, date, and person responsible for verification.
- Do not aggregate third-party metrics as though they express a single truth.
- Indicate what information is missing and what could change the decision.
Criteria worth recording: topical relevance, editorial fit, likely audience, publication conditions, cost, and risks
Criteria should serve the campaign objective, rather than form a generic list completed by habit. Topical relevance can be assessed by looking at the site’s main subject matter, relevant sections, how the topic is treated, and the proximity between the target content and the proposed editorial environment. It does not require a perfect match, but it does require reasonable justification. Editorial fit assesses whether the collaboration can be integrated in a way that makes sense to readers: tone, format, content quality, planned placement, and coherence between the topic addressed and the linked resource. The likely audience is an informed hypothesis, not a guarantee of visits. It can be supported by visible signals and estimates, but it should retain that level of uncertainty. Publication conditions should also be recorded: format, anticipated permanence if confirmed, editing options, link policy, timelines, editorial review, and commercial disclosure requirements. The cost should state what is and is not included, as well as currency, taxes when known, and the inquiry date. Finally, risks should be written down specifically, not summarized as a vague intuition.
- Topical relevance and connection to the campaign objective.
- Editorial fit of the content, link, and its context.
- Likely audience, indicating the signals and limitations of the estimate.
- Publication, review, change, and timeline conditions.
- Itemized cost where possible and validity date.
- Editorial, reputational, operational, and compliance risks.
How to document paid collaborations transparently and review when sponsored or nofollow attributes may apply
A paid collaboration should be treated as such in the file. Transparency is not an administrative detail: it affects the relationship with the publisher, client expectations, and compliance with applicable policies. Record whether there is financial or other consideration, how commercial content will be identified, and what has been agreed regarding links. Google states that links that are advertisements or paid placements should be marked with rel="sponsored". It also notes that rel="nofollow" may be used for those links. These attributes help communicate the nature of the relationship to search engines; they are not a formula for ensuring or preventing a specific outcome. The decision should be reviewed case by case, based on the publisher’s conditions and relevant policies, without assuming that an attribute makes a collaboration harmless or guarantees an SEO effect. The record should reflect the status of the information: confirmed in writing, pending confirmation, or not accepted. If the proposed conditions conflict with the team’s or client’s compliance criteria, the file should record this as a reason to defer or reject the opportunity. As a reference, it is advisable to consult Google’s documentation on qualifying outbound links and its spam policies before setting an internal procedure.
- Declare whether there is payment, compensation, or any commercial relationship.
- Record how sponsored or commercial content will be identified.
- Note the agreed, requested, or pending-confirmation link attribute.
- Distinguish between confirmed conditions and assumptions made before publication.
- Consult Google’s current guidelines: https://developers.google.com/search/docs/crawling-indexing/qualify-outbound-links and https://developers.google.com/search/docs/essentials/spam-policies
How to write an approval, deferral, or rejection decision without relying on an isolated metric
The final decision should be brief but reasoned. An approval does not mean that the opportunity is objectively excellent or that it will produce a particular outcome. It means that, based on the available information, it fits the objective, budget, conditions, and accepted level of risk sufficiently well. Deferral is useful when decisive information is missing: confirmation of publication conditions, review of a specific section, validation of topical fit, or clarification about the commercial nature of the collaboration. Instead of leaving an ambiguous comment, state which information is missing, who needs to obtain it, and when it will be reviewed again. A rejection should also be documented. Recording that an opportunity was not suitable because of topical misalignment, insufficient conditions, lack of transparency, high risk, or inadequately justified cost prevents repeated analysis and makes it possible to identify patterns. The reasoning should be based on multiple criteria, especially those that are critical for the campaign, rather than on an isolated figure from a tool.
- Approved: explain the fit, accepted conditions, and assumed risks.
- Deferred: specify what information is missing and the next action.
- Rejected: record the main reason and secondary factors.
- Include confidence level and outstanding issues where necessary.
- Avoid statements such as “good metric, therefore approved” without further context.
Practical template of fields and questions to use for each opportunity
The template should be consistent enough to compare files and light enough for the team to use. Not every field needs the same level of detail in every campaign: critical criteria can be configured by project. What matters is retaining the separation between observed information, estimates, and interpretation. A team can manage this record in a spreadsheet, a project management system, or an internal tool. Linkuo can help gather and compare context when researching opportunities, but the file remains the layer where professional judgment and the decision for each campaign are documented.
- Identification: project, campaign, URL or opportunity identifier, person responsible, and review date.
- Objective: what is being supported, priority audience or market, constraints, and operational success criterion.
- Direct evidence: pages reviewed, conditions received, visible policies, sources, and date.
- Estimates: tool or method, inquiry date, observed indicator, and limitations.
- Hypotheses: what is inferred, what signals support it, and what could disprove it.
- Assessment: topical relevance, editorial fit, likely audience, format, conditions, cost, and risks.
- Transparency: commercial relationship, content disclosure, and expected sponsored or nofollow status where applicable.
- Decision: approved, deferred, or rejected; reason, confidence level, next step, and review date.
- Subsequent outcome: publication confirmed, incidents, changes detected, and learnings without attributing unproven causality.
Frequently asked questions
What is a link-building opportunity file?+
It is an assessment record that documents the campaign objective, verified information, estimates, hypotheses, conditions, risks, and the decision made about an opportunity. Its purpose is to make the decision understandable and reviewable.
Is saving SEO metrics enough to justify an opportunity?+
No. Tool metrics can provide context, but they are estimates and do not replace topical, editorial, commercial, and risk review. They should be recorded with their source and date, without treating them as certainties.
Why is it useful to document rejections as well?+
Because it prevents repeated research, shows which criteria excluded opportunities, and helps identify patterns. A well-explained rejection provides operational learning even when no collaboration takes place.
How should paid collaborations be recorded?+
It is advisable to document the consideration provided, the planned commercial disclosure, the agreed conditions, and how the link will be handled. Depending on the case, rel="sponsored" or rel="nofollow" attributes may apply. The information should be confirmed with the publisher and reviewed in line with applicable policies.
Can an opportunity file prove that a link-building action will improve rankings?+
No. The file documents a decision and its rationale based on the available information. It cannot guarantee rankings, traffic, authority, or other SEO outcomes.
Sources and references
- Google Search Essentials — Google Search Central
- Spam policies for Google web search — Google Search Central
- Qualify outbound links — Google Search Central