Define the audit before opening an export
A backlink audit is a structured review of links pointing to your site, ending with decisions that someone can act on. Write down the target domain or URL, the question, the data sources, their collection dates and the review deadline. For example: “Check references to the product pages moved in September and assign confirmed destination problems.” That is a clearer scope than “find every bad link.”
A technical audit examines your own site’s crawlability, rendering and other infrastructure. A backlink audit examines external references and their destination paths. They overlap when an incoming link leads to an error on your site, but neither replaces the other.
After a traffic decline, record its start date and affected pages separately. Compare deployments, destination changes and dated link observations; do not assume a link caused the decline merely because it appeared in the same period.
For interpreting distributions and comparing data sources, start with the backlink analysis guide. This audit focuses on finding, assigning and closing specific issues.
Keep a traceable inventory and a separate decision sheet
Save the untouched export, source name, scope and retrieval date. Work from a copy, retaining source URL, requested destination, anchor and any observation timestamps. A missing value stays unknown rather than becoming zero. If multiple sources disagree, preserve both observations and investigate the difference.
Search Console’s Links report is sampled and can include historical links. Treat it as one input, not a live inventory. Export from your own accessible account; a live Search Console connection is not required to use this worksheet.
Count observations, unique source pages and referring domains separately. Deduplicate a working view without destroying the original rows. Keep query parameters and redirect details until you understand whether changing them alters the page. The CSV analysis tool can help organize an original export; the action worksheet records the decisions you make afterwards.
Verify source and destination before assigning a defect
- Open the source page and record the check time and access result.
- Locate the visible link, surrounding text, actual destination and link attributes.
- Follow the destination’s redirects and record the final page and response.
- Compare that evidence with the intended target, placement terms and expected reader journey.
- Save a short evidence note or screenshot reference and classify the finding as confirmed or unresolved.
A timeout, login prompt or incomplete rendering leaves a check unresolved. Repeat with an appropriate access method before calling the link removed. A page that loads successfully can still send visitors to the wrong product or an irrelevant homepage.
For a moved destination you control, choose the appropriate replacement and verify the redirect after implementation. Google documents 301 and 308 as permanent redirects. The status code alone does not tell you whether the replacement serves the reader’s purpose.
Prioritize impact and certainty separately
Use a simple team convention: “high” for a confirmed broken destination or materially wrong journey on an important page; “medium” for a verified placement mismatch requiring coordination; “investigate” when evidence is incomplete; and “observe” when no defect is confirmed. These are workflow labels, not Google risk scores.
Assign the person who can perform the next action. Your web team controls your destination, a publisher contact can request an external edit, and an analyst can repeat an inconclusive check. Pick a due date based on impact and dependencies. Never silently convert “unverified” to “low risk” just to finish the spreadsheet.
Six hypothetical findings, with a clear next action
These examples use reserved example domains and invented observations. They demonstrate the worksheet, not real campaign performance. The priority column is a local work order, and the closure column states what must be checked after action.
| Finding | Evidence to keep | Priority / owner | Closure check |
|---|---|---|---|
| A01: target returns 404 | Source link found; final target returns 404 | High / web team | Relevant target responds successfully when opened from the source |
| A02: old product redirects to homepage | Redirect chain ends on an unrelated page | High / web team | Final page matches the original product intent |
| A03: publisher links to the wrong URL | Observed href differs from the agreed destination | Medium / publisher contact | Published link points to the agreed destination |
| A04: source times out | Request timed out; link presence is unknown | Investigate / analyst | Repeat check records access and link evidence |
| A05: low vendor score only | Score recorded; no page-level defect confirmed | Investigate / analyst | Written page review supports an action or no action |
| A06: reference matches the request | Visible link, destination and context match | Observe / monitoring owner | Keep dated baseline and recheck on schedule |
Keep score review separate from removal decisions
A vendor’s score can be a prompt to inspect a page; it is not the finding itself. Record the reason for concern and the source evidence. A low authority number, unfamiliar language or unusual domain name does not establish that a link should be removed.
Google says most sites do not need disavow; misuse can harm search performance. Read its current eligibility guidance before considering that separate process. This template does not create a disavow file or automatically contact publishers. A removal decision needs its own evidence, authority and review.
Deliver an audit someone can complete
Hand over the scope, source dates, coverage limitations, counts by observation state, and the action queue. Give every actionable row a source URL, intended destination, evidence, impact, owner, due date and closure check. Mark a task resolved only after its stated check passes; keep the original observation beside the new one.
For example, restoring a destination is not complete when a ticket says “deployed.” Open the source link again and verify the final relevant page. Asking a publisher for a correction is not the same as observing the correction. Report unresolved access checks as unresolved rather than subtracting them from the profile.
The blank CSV contains an empty row, not default measurements. The filled CSV demonstrates six cases. Keep the example sheet separate from your production audit, replace role labels with your actual owners, and set real dates before sharing it.
Download the blank backlink audit action template (CSV)
Download the six-case worked example (CSV)
Choose a review cadence and monitor the changes
Schedule audits around changes that matter: a migration, important destination edits, a new batch of placements or a persistent monitoring anomaly. A team might review its open queue each week and the wider scoped export each month; this is an example operating schedule, not a universal SEO rule.
Use the backlink monitor for repeated checks of known source-and-target pairs. It does not discover every backlink. Keep paid-order records in My links separate from your wider external inventory, and use the generator verification guide when an automated service provides a delivery list.
Track confirmed fixes, unresolved checks and observed referral outcomes separately. A completed audit or a repaired link does not establish a ranking increase. Reuse the same scope and source settings when comparing the next audit with this baseline.