Review and publish
Reviewers inside and outside the workspace annotate the same draft. You decide what to apply, finalize the metadata, and publish to the live page.
Review and publish is the last stretch of making a page: collect feedback, decide what to apply, then ship. It works the way teams actually approve content, with people inside and outside the workspace marking up the same draft and one operator making the calls. This page covers how that runs and what happens when you publish.
For where this sits in the larger flow, see the creation pipeline. For the full path from research to live page, see Opportunity to published page.
How review works
Two kinds of reviewer touch a draft, and they work in the same place.
| Reviewer | How they get in | What they do |
|---|---|---|
| Internal | Inside the editor, signed into the workspace | Annotate the draft in place |
| External | A share link, no account needed | Annotate the same draft the same way |
The share link is what makes this fit a real approval chain. A client, an outside editor, or a subject expert opens the link, reads the draft, and leaves notes without anyone provisioning an account for them. Their feedback lands next to your team's, on the same page.
You stay in control of what changes. Reviewers raise issues; nothing moves the draft until you act. You go through the feedback one note at a time and decide what's worth applying. When a note calls for it, an agent will regenerate that section, and you review the new version the same way. The page changes only when you say so.
That last point is the whole design. Review gathers judgment from everyone who should weigh in, then funnels every decision through one operator, so the page never drifts on autopilot.
Ready: finalize the metadata
When the draft is right, move the brief to Ready and finalize the SEO metadata. This is the page's promise to the searcher and the engine, so it's worth a careful pass.
| Field | What it sets |
|---|---|
| Title | The page's headline promise in search results and to AI engines |
| Meta description | The short pitch under the title in a result |
| Slug | The page's permanent URL path |
| Description | The page's own summary for search and machine reading |
Get the slug right before you publish. A URL is permanent once it's live, and changing it later means a redirect and a hit to any AI citation pointing at the old path. Settle it now.
Published: ship to the live page
Publishing is the final state. GrowthOS creates the live page record, or updates an existing one if the brief came from a refresh. The page goes live and enters your Page Portfolio, where it starts accumulating performance signals from its first day.
From here the page stops being a draft and becomes an asset you track and improve. The work shifts from creation to optimization.
Common questions
Can a reviewer without an account leave feedback? Yes. External reviewers open a share link and annotate the draft directly. No login, no setup.
Who decides which feedback gets applied? You do, one note at a time. Reviewers surface issues; the operator decides what moves the page. An agent will regenerate a section on request, but the call is always yours.
What happens at Published? GrowthOS creates the live page or updates the existing one, then the page joins your Page Portfolio and begins gathering performance data.
Can I change the slug after publishing? You can, but the URL is permanent by design. A change means a redirect and risks losing citations aimed at the old address, so finalize the slug at Ready.
Where to go next
Last updated at June 3, 2026
Content Templates
The Content Template is the quiet, highest-leverage choice in a brief. It decides a page's form, so the same inputs produce very different pages.
Optimize
Keep every page fresh, relevant, and converting. Optimization is the steady state of running a site, not a one-time project. The loop never stops.