NetWorkspaces and sites
NetTree organizes multi-site backlink management under workspaces — shared billing, members, libraries, and Tracker data — with one site profile per product or property.
Who this is for
Founders with one product, agencies with many clients, and team link building workspace operators who need isolated sites under one account.
What you will learn
- Workspace vs site responsibilities
- Site profile fields and rebuild
- Competitors and keyword seeds
- Per-site entry points (queue, discovery, matrix)
Workspace layer
Paths: /app/settings/workspace, /app/settings/account
A workspace contains:
- Members — invited users with roles (owner, member, etc.)
- Plan — site limits, seats, verify quota, AI drafts
- Integrations — extension token, payment-connected features
- Shared libraries — My Backlinks, Plaza usage, Submission Tracker
All sites in a workspace share the same Tracker table (filterable by site).
Sites
Path: /app/sites → /app/sites/new
Each site represents one target property (usually one primary domain):
| Field | Purpose |
|---|---|
| Name | Display label in Tracker and workflows |
| URL | Canonical site URL for profile rebuild |
| Status | Active/archived (per product rules) |
Plans cap how many active sites you can run — see Workspace settings.
Site profile
Path: /app/sites/[id]/profile
The profile powers matching, drafts, and discovery:
- Category and positioning
- Short/long descriptions
- Keywords and language
- Target regions
- Optional competitor domains
Rebuild from URL
NetTree can regenerate an initial profile from your homepage. Always review — inaccurate profiles weaken Plaza fit scores and draft quality.
Rebuild after major repositioning, rebrand, or new primary domain.
Competitors and keywords
Paths:
/app/sites/[id]/competitors— competitor domains for gap context/app/keywords— workspace keyword research/app/sites/[id]/discovery— site-scoped discovery
Competitor seeds inform gap suggestions; they do not auto-submit anywhere.
Per-site operational hubs
From a site detail page (/app/sites/[id]):
| Hub | Path | Use |
|---|---|---|
| Submission queue | /app/sites/[id]/queue | Destinations for this site |
| Discovery | /app/sites/[id]/discovery | Opportunity finding |
| Content matrix | /app/sites/[id]/content-matrix | Publishing plan |
| Profile | /app/sites/[id]/profile | Positioning source of truth |
Tracker filters by Website column to isolate one site’s rows.
Site-level stats
Site dashboards summarize queue depth, live links, and workflow progress (exact widgets vary by plan). Use Tracker export CSV for external reporting.
Common questions
Can teammates see all sites? Workspace members with access see shared Tracker and libraries; role rules may limit admin actions.
Archive vs delete? Prefer archive to preserve historical submission evidence.
Multiple domains one site? Use one primary URL in profile; note alternates in profile keywords or notes if needed for drafts.