NetLink verification and backlink records
NetTree separates activity (you submitted something) from outcomes (a link is reachable and matches expectations). Verification powers the Link column in Submission Tracker.
Who this is for
Teams that report Live backlinks to stakeholders and need audit trails, not checkbox completion.
What you will learn
- Verification states and transitions
- What creates a
backlinksrow - How recheck affects queue status
- Human review vs automated checks
State model (product)
| State | User-facing (Tracker Link) | Meaning |
|---|---|---|
checking | Checking | Verification pending or inconclusive |
live | Live | Target link found on source page under rules |
lost | Lost | Previously live; now missing or changed |
changed | Checking / review | Page changed; needs human review |
Queue user_status | Tracker Operation | Notes |
|---|---|---|
submitted | Submitted | Action recorded |
live | Published | Human or sync promoted queue |
rejected | Rejected | Stopped |
skipped | Skipped | Deprioritized |
Philosophy and team narrative: /verification
What triggers verification
- Owned channel registration — recording a public URL on Tumblr, GitHub, etc. creates a backlink in
checking, then runs verification. - Backlink import / CSV — manual backfill into Tracker import.
- Recheck — user or Refresh status requeues verification.
- Background worker — periodic rechecks for monitored links (plan limits apply).
Verification vs Mark live
| Action | Updates queue | Creates/updates backlink | Runs HTTP check |
|---|---|---|---|
| Mark live | Yes | No | No |
| Record owned channel | Yes (often) | Yes | Yes |
| Recheck | May sync on result | Yes | Yes |
Best practice: After a directory accepts your listing, paste the Live URL into the workflow or Tracker, then rely on verification (or Recheck) for ongoing monitoring.
Evidence fields
Backlink records store:
source_url— page where the link was found (listing URL)target_url— your site URLstatus— live / lost / checking / changedverification_note— human-readable outcome (may includelisting:URL)
Sync with site queue
When a backlink becomes Live or Lost, NetTree can promote queue status for matching site + source + target (reconcile job). This keeps workflow queue and Tracker aligned without duplicate data entry.
Plan limits
Free and paid plans cap monthly link checks. Verification and Recheck consume quota. See Workspace settings.
When quota is exhausted, new checks queue until the next cycle or you upgrade — existing Live/Lost labels remain visible; they are not silently reset.
Background monitoring
When the automation worker is running (/api/worker/tick or hosted worker loop), eligible backlinks are re-verified on schedule (plan limits apply). This keeps Lost states honest over time without manual spreadsheet audits.
Use Refresh status on the Tracker toolbar for an immediate batch recheck (up to 20 backlink rows per action).
Common questions
Why Submitted but not Live? Submission is logged; verification has not confirmed a reachable link yet.
Can I trust Mark live for reporting? It records intent. For evidence-backed reporting, use verified Live backlink rows.
What if verification is wrong? Use manual review; edit Live URL; Recheck. Ambiguous pages may need human judgment.