Free, portable resource

Keep evidence for every backlink—not just a submission count.

This free CSV helps a small team record where a link appears, what it points to, when it was checked, and whether it is actually live.

Last updated: 2026-09-15

Download CSV template Read the field guide

How to use the template

1. Record the public page

Use the exact URL where the link should appear—not a homepage unless that is the actual placement.

2. Separate activity from proof

Start with checking; change to live only after the public page contains the intended link.

3. Recheck over time

Keep a last-checked date and move links that disappear to lost or needs_review.

Useful for owned GitHub assets

A public repository or GitHub Pages site you control can be a legitimate project asset. Document the useful project content, use the repository About and README contextually, then record the public page after publishing. Do not ask for promotional links in repositories you do not manage.

SaaS directories shortlistChoose a launch or listing path by product goal. SaaS launch checklistA forkable preflight for listings and owned GitHub assets. GitHub Pages backlink guidePublish useful docs and verify public pages honestly. Submitted vs LiveWhy verification status matters for reporting. Use NetTree for the full workflowSite context, matching, human review, and link verification.