How does probeo rewrite an existing page?
A page rewrite proposes a new version of a page that already exists, shaped by what kind of page it is. It is a separate step from drafting new pages, because it starts from a page and its history rather than from a question.
What probeo produces
One proposed rewrite per page, returned as structured content. When probeo has identified the page’s archetype and has a template for it, the rewrite follows that template. Without one, it follows probeo’s rewrite instructions alone.
The rewrite is a proposal. It doesn’t replace the live page.
How it works
A language model receives the page’s current content, as cleaned HTML. It also receives what probeo’s page analysis recorded about the page, including its archetype and intent, and the structured model of the page’s sections. It is told to rewrite that page only.
A page is rewritten again only when something it depends on has changed: the page itself, its analysis, or the instructions and template. Running it twice on an unchanged page doesn’t produce a second rewrite.
What this does not cover
A rewrite is a language model’s proposal. It isn’t researched the way a new page is, and it doesn’t add cited research.
Common questions
Is a rewrite published automatically?
No. It is written as a proposal alongside the page’s other analysis. The live page doesn’t change.
Why does the page’s archetype matter?
The template for an archetype sets the structure a page of that kind should have. Rewriting into that structure keeps a page consistent with others of its kind.
How is this different from drafting a new page?
A new page starts from a question and goes through a brief, research and an outline. A rewrite starts from a page that already exists and from what probeo has recorded about it.
Which product this is part of
Page rewrites is part of Content Production.