The blog desk

Write in markdown against a keyword from the roadmap with its SERP brief beside the editor, preview it in the real template, and publish — the sitemap, the engines and rank tracking all follow automatically.

What it is

Growth › Blog, in three views: Posts (a filterable list), Calendar (the rolling plan) and Topic map (the plan as a web). The editor holds title, slug, description, markdown body, keyword target, hero and scheduled date, with a live markdown preview and an inline image generator. Publishing runs the gate, announces the change, flips the universe row and starts rank tracking in one action.

Also called: blog editor · content admin · post manager · write a blog post

See it
The blog desk
Day rate
$600
Days figured
6
Crew size
3
Fuel & equipment
$300
Finished 2 days early — $1,800 back to the crew
The editor with the markdown pane, live preview, and the target-keyword brief card showing shape, angle and the current top ten. Sample data — no customer information appears here.
How it works
  1. 1GET /api/platform/blog returns every post in every status, the writable keyword targets from the universe, and the live-ranked queue.
  2. 2Choosing a universe keyword copies its keyword string onto the post and shows its SERP brief beside the editor.
  3. 3Saving generates a unique slug, and editing a LIVE post re-announces it because the sitemap's view of it changed.
  4. 4Publish runs the gate, then announces, flips the universe row to published, and upserts the keyword into tracking.
  5. 5Unpublish and archive both announce the change too, so a URL that has left the site is crawled and dropped.
  6. 6Delete refuses on a published post — it must be unpublished first, because a live URL shouldn't vanish without a decision.
Why we built it

The panel exists so the SEO loop closes in one action rather than five: "publishing updates the sitemap, pings every engine, and starts rank tracking." Announcing on EDIT was added after a real gap — "Editing a LIVE post changes what the sitemap says about it — announce that too, or a correction sits unseen until something else ships." And delete is deliberately blocked on published posts: "a published URL shouldn't vanish without a decision."

The problem
  • Publishing, sitemap updates, engine pings and rank tracking were separate manual steps.
  • Editing a live post left the change unannounced.
  • A published URL could be deleted outright with no decision recorded.
Sound familiar?
What you get
One publish action does the sitemap, the engines and rank tracking
The SERP brief for the target keyword sits beside the editor
Removing a live page is a deliberate two-step, not a delete button
What's inside
Overdue, scheduled, draft — the five states of a post
A post with a date on the calendar and a post nobody has scheduled are not the same thing, so the list separates published, overdue, scheduled, draft and archived — with the ones needing a decision first.
Why was this post pulled?
Archiving a post requires a written reason, stored on the row with its own timestamp — because the person asking why months later is never the person who did it.
The topic map
The whole content plan as one web: the platform at the centre, seven pillars orbiting it sized by their cluster's impact, every post hanging off its pillar sized by its keyword's weight.
Read the draft in the real template
An unpublished draft renders at its real URL for signed-in platform staff only — with a DRAFT banner and a hard noindex — so a post can be judged as a page, not as a textarea.

See it on your own jobs

Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.

or keep browsing features →