NetDiscovery and keyword research
NetTree combines backlink opportunity discovery with keyword research link building inputs — turning search and competitor signals into queue candidates.
Who this is for
Teams expanding beyond static Plaza lists into competitor backlink gap research and automated candidate finding.
What you will learn
- Workspace vs site-scoped discovery
- Keyword center usage
- Registering candidates into library or queue
- Public preview vs in-app depth
Primary paths
| Feature | Path | Scope |
|---|---|---|
| Discovery engine | /app/discovery | Workspace runs, schedules, jobs |
| Site discovery | /app/sites/[id]/discovery | Site-scoped runs |
| Keyword research | /app/keywords | Clusters, competitors, gaps |
| Site keywords | /app/sites/[id]/competitors | Competitor seeds |
| Public preview | /opportunities | Marketing-filtered source browse |
Discovery engine
Path: /app/discovery
What it does
- Runs configured discovery modes against site profile + competitors
- Surfaces candidate domains and pages for human review
- Queues automation jobs (visible status: queued, running, completed, failed)
User-visible provider status
The Discovery page shows which external providers are configured (e.g. search backends). You do not need provider credentials — admins configure integrations.
Schedules
Per-site schedules can trigger recurring discovery. Edit cadence from Discovery UI when enabled for your workspace.
Competitor candidates
Discovery may flag competitor domains extracted from research for you to adopt or dismiss before they feed matching.
Keyword research
Paths: /app/keywords, /app/keywords/clusters, /app/keywords/competitors
Clusters and gaps
- Head terms and long-tail from site profile seeds
- Competitor gap suggestions when competitor domains are set
- Free plan may preview limited rows; paid plans unlock full lists, filters, and pagination
Adopt keyword
Adopting a keyword into your workspace seeds future discovery and matrix planning. Task Center awards points for Adopt 1 keyword daily task.
From candidate to queue
Typical flow:
- Run discovery or review keyword gap output
- Evaluate fit (risk, language, workflow type)
- Add source to My Backlinks or directly to site queue
- Enter appropriate workflow (directory, guest post, etc.)
Discovery finds candidates — it does not auto-submit.
Public vs in-app depth
| Surface | Depth |
|---|---|
| /opportunities | Public marketing preview with filters |
/app/plaza | Full library with fit and queue actions |
/app/discovery | Automated runs, jobs, schedules |
Link publicly shareable previews; operate queues inside the app.
Quotas and plans
Discovery job volume and keyword list depth vary by plan. Heavy automation may queue behind workspace job limits — check Discovery page counters for running/pending jobs.
See Workspace settings for plan entitlements.
Common questions
Does discovery auto-add to my queue? No. You approve candidates before queueing.
Failed discovery run? Check job error message on Discovery page; admins may need to fix provider configuration.
Difference vs Plaza search? Plaza is curated static library; discovery generates fresh candidates from live search/competitor signals.