Publishing flow
From sitemap idea to reviewed file
The publishing flow starts before a page is written.
First, decide why the page should exist. Then create or edit the markdown file. Then review the page in Page Writer. Only after that should the file move toward GitHub sync and publishing.
Page planned in sitemap
The sitemap shows where the page belongs.
The page should connect to a real need: a weak prompt, a source gap, a Search Console opportunity, a competitor gap, or a planned content group.
Markdown file created or updated
The page lives as a markdown file in the workspace.
The file can include frontmatter, content sections, internal links, and JSON-LD. It can be edited by the user or with CLEA.
Draft checked before publish
Before publishing, check the page content and the page metadata.
The page should have a clear title, useful description, correct URL, clean body, reviewed links, and safe claims.
Plan in Sitemap
Decide which markdown page should move forward.
Draft in Page Writer
Improve copy, metadata, links, and schema.
Review the file
Check claims and save the markdown.
Sync through GitHub
Move reviewed files into the connected repository.
SEO and JSON-LD review
Page Writer can add JSON-LD when it is missing.
It can also run an on-page check when the page has a live URL on the connected website. That check can show score, status code, word count, title length, description length, internal links, external links, readability, and issues.
Human approval before GitHub publish
Human review is required before publishing.
CLEA can draft and improve the file. The user should approve the claims, links, and final page purpose.
Post-publish visibility check
After publishing, schedule a follow-up.
Check whether related prompts change, whether sources read the page, whether Search Console sees the URL, and whether the page needs another improvement pass.
Review this page before publishing. Check title, description, URL, internal links, claims, JSON-LD, and whether the page answers the buyer question.