Pages
Pages are simpler than posts — for evergreen content like About, Contact, or Privacy that doesn't need bylines or categories.
Pages are Clog's second content type. They're like posts, minus everything that doesn't apply to evergreen content: no author, no category, no tags, no related-posts pins, no scheduled publishing, no SEO score (no focus-keyword tuning), no Schema.org variant catalogue beyond a pageType picker. What you get is the same block editor you use for posts, an SEO meta group, and a status that's either Draft or Published.
Use pages for: About, Contact, Privacy, Terms, FAQ landing, learning-resource hubs, or any static page on your site that's just a body of content with no editorial-flow concerns.
You need pages:read to view pages and pages:write to create, edit, publish, or delete them.
The Pages list
Open Pages from the workspace sidebar. Each row shows the title, slug, status, page type, and updated date. From the top of the page you can:
- Search — case-insensitive across title and body text.
- Filter — by status (draft / published).
- Click a row — opens the editor.
- New page — drops you straight into the editor (no wizard — pages don't have a Schema.org variant catalogue beyond
pageType).
Status flow
Only two states:
| Status | Meaning |
|---|---|
| Draft | Work in progress. Not returned to consumers by default. |
| Published | Live. Returned via GET /external/pages and GET /external/pages/:slug. The first draft→published transition stamps publishedAt; subsequent edits don't bump it. |
Pages cannot be archived in v1 — if you need to retire a page, set it to draft (which hides it from consumer reads) or delete it.
Writing a page
Open a page (or click New page). The editor is a two-pane layout: the block editor on the left, page details on the right.
Title and slug
The slug auto-derives from the title on first save and stays stable afterwards. Edit it manually if needed. Lowercase letters, digits, dashes; unique within the workspace.
Slug changes on published pages auto-create a 301 redirect from the old slug to the new one. Slug changes on drafts skip that — no consumer ever saw the old URL. See Redirects.
Body (the block editor)
Pages use the same block editor as posts, with the same 13 block types: paragraph, heading, list, quote, divider, image, video_embed, tweet_embed, callout, code, faq, cta, key_takeaways. Hit / at the start of a line to open the block picker.
Inline formatting (**bold**, _italic_, [link](url), `code`) is stored as Markdown source on the block fields, same as posts.
Image edits create a new media row — the rule is identical to posts.
Per-body cap: 1,000 blocks.
Page details (right sidebar)
| Field | Notes |
|---|---|
| Status | Draft or Published. |
| Slug | Auto-derived; editable. Slug change → auto-redirect (when published). |
| Page type | One of WebPage (the default), AboutPage, ContactPage, LearningResource, or MedicalWebPage. Drives the jsonLd graph on the read response and a few SEO defaults. Pick the closest match — WebPage is fine if nothing else fits. |
SEO
Pages carry the same meta group as posts: title, description, canonical, focus keyword + secondary keywords, robots, Open Graph, Twitter Card, breadcrumbs override. Open the SEO drawer from the top-right.
What pages don't have (relative to posts):
- No live SEO score and no readability score. Pages are typically short enough that the scoring engine isn't useful here; if you want to be rigorous, fill the SEO meta group manually.
- No Schema.org variant wizard.
pageTypecovers the lookup; there's nostructuredDatapayload to author. - No focus-keyword analysis — fill
focusKeywordif you want it to surface in your own analytics, but Clog doesn't grade pages against it.
Edit-permissions rule is the same as posts: pages:write or seo:write can touch the SEO meta. See Members and permissions and SEO.
Bulk actions
The Pages list supports the same bulk action bar pattern as posts — tick multiple rows and a bar appears at the bottom. v1 supports:
- Change status — flip all selected pages between draft and published.
- Delete selected — soft-delete in one shot.
There's no "change category" action — pages don't have categories.
Deleting a page
Delete soft-deletes: stamps deletedAt, frees the slug, hides the page from every read path. Same as posts, there's no Trash view or restore action in v1.
What pages don't carry
If you find yourself needing one of these on a page, you probably want a post:
- No author byline.
- No category or tag relationships.
- No related-posts pins.
- No publishedAt scheduling.
- No live SEO score / readability score.
- No Schema.org variants beyond
pageType.
The reverse is also true — if a piece of content really is evergreen and bylineless ("About us", "Pricing", "Contact"), don't make it a post just to get the editor; that's exactly what pages are for.