Content publish and owned channels

Publish on owned channels (Tumblr, GitHub, Medium), record public URLs, and verify backlinks with NetTree content publish workflow.

Content publish workflow

Owned channel link building lets you publish on platforms you control (Tumblr, GitHub, Medium, Blogger, etc.), then record the public URL so NetTree can verify the backlink.

Paths:

/app/workflows/content-publish — queue list
/app/workflows/content-publish/[queueId] — channel workbench
/app/workflows/content-publish/add — add platform to queue

Who this is for

Teams using content publish SEO workflow on third-party platforms while keeping evidence in NetTree’s submission tracker.

What you will learn

Add a platform queue item
Draft for channel format
Record owned channel → verification
Submit page vs Live URL on content platforms
Content matrix entry points

Step 1 — Add a platform

From /app/workflows/content-publish/add or Plaza, add a content-publish destination to your site queue.

Each platform has a playbook (see /guides/platforms) for off-NetTree steps — this chapter covers NetTree screens only.

Step 2 — Generate channel draft

The workbench produces format-aware copy:

Short-form posts (Tumblr-style tags)
Long articles (Medium, Ghost)
README / docs blocks (GitHub)

Edit before publishing on the third-party site. Matrix-linked items may pre-fill context from a content matrix plan (P2).

Step 3 — Publish on the platform (human)

Create the post, repo README, or page on the external platform. Sign-in and publish actions stay with you.

Step 4 — Record owned channel

Use Record channel (workflow or Tracker action) to save the public URL of the live asset.

This typically:

Creates or updates an ownedchannels row with publicurl
Sets queue to Submitted (Tracker Operation: Submitted, Link: Checking)
Creates a backlink record and queues link verification

After verification succeeds, Tracker shows Link: Live with origin verified and enables Recheck.

Submit page vs Live URL

Content platforms often split where you create vs where the public page lives:

Label	Example (Tumblr)	Source
Submit page	`/new` post editor	Platform playbook editor URL
Live URL	`https://you.tumblr.com/post/…`	Owned channel / listing notes

Same pattern applies to GitHub (repo editor vs README URL) and similar platforms.

If only the editor URL existed, Tracker previously hid Live URL — NetTree now resolves editor URLs separately so Add live URL remains visible after you save a listing.

Verification quota

Recording a channel consumes link check quota on your plan when verification runs. Failed checks stay Checking until Recheck or Refresh status.

See Link verification and Workspace settings.

Content matrix integration

Optional planning layer:

/app/content-matrix and /app/sites/[id]/content-matrix redirect to content publish with site context
Per-channel matrix: /app/workflows/content-publish/[queueId]/matrix
Workflow matrix export/print routes for offline review

Matrix plan items can deep-link into content-publish queue rows with planItemId context. Completing publish may update matrix progress and Task Center points.

Full matrix docs: Content matrix.

Tracker actions for content-publish rows

Action	When
Record channel	Submitted/skipped/rejected content-publish row needing public URL
Recheck	Row has backlink ID after channel recorded
Add live URL	Listing missing but queue/backlink editable

Platform playbooks

Step-by-step off-product instructions:

/guides/platforms — GitHub, Tumblr, Blogger, Hashnode, etc.
Ten playbooks free on open web; sign in for full library

Do not duplicate playbook bodies in Help Center — link out for platform-specific SEO tactics.

Common questions

Why is Submit page an editor URL? So operators open the correct creation screen, not the marketing homepage.

Can I skip Record channel? You can Mark live on the queue, but without a backlink record you lose Recheck and automated monitoring.

Matrix item not linking? Ensure the queue row was created from matrix workflow push with valid matrixplanitem_id.