Final review
Final review is the last human check before a Page Writer file moves forward.
This is where you decide if the markdown file is ready for GitHub sync, another edit pass, or a live page check.
Final review check
Read the page like a customer would.
Then read it like a reviewer. The first pass checks clarity. The second pass checks accuracy.
Read for clarity
Make sure the page is easy to understand.
Read for accuracy
Check claims against files, sources, and dashboard facts.
Check page data
Review title, description, URL, links, and schema.
Decide the next step
Send back to editing, sync, or live check.
Issue location
Most final review issues live in one of five places.
| Place | What to check |
|---|---|
| Frontmatter | Title, description, URL |
| Body | Clear sections and simple language |
| Claims | Proof for important statements |
| Links | Useful next pages |
| Schema | JSON-LD matches the page |
CLEA validation
Ask CLEA for a review pass, not a full rewrite.
Review this page before GitHub sync. List only issues that block publishing. For each issue, name the section and give a simple fix.
Human review
The final decision stays human.
CLEA can find issues, explain risks, and help with edits. It should not be the only approval step for live website content.