Where page writer fits

Page Writer sits between the sitemap and publishing.

The sitemap plans the page. Page Writer edits the page. GitHub sync moves reviewed sitemap files into the connected repository. This keeps the workflow understandable.

Analytics can show that a page may be needed.

Maybe a prompt result is weak. Maybe competitors are mentioned more often. Maybe sources show a topic that your site does not explain well yet. These signals should not go straight into publishing. They should become a planned page first.

The clean flow looks like this:

Goal: turn one visibility gap into one reviewed page.

Steps:
- Find the gap in analytics, prompts, sources, or competitors.
- Create or open the page in the sitemap.
- Add the page goal and source notes.
- Open Page Writer from the page card.
- Draft, review, save, and check the file.
- Sync through GitHub when the page is ready.

Page Writer is also where the page becomes checkable.

The file needs a URL before a live on-page check can work. If the page is not published yet, use Page Writer for editing and review. Run the live check after the URL exists on the website.

Use normal chat for broad questions.

Use Page Writer when the answer should focus on one markdown file. The first Page Writer chat message silently includes the file path, title, URL, description, JSON-LD state, and current markdown content.