Improving pages
The metered half. Crawlune proposes changes to your own published prose, and nothing is applied until you have read it.
This does not produce anything yet. Everything on this page is built and tested — selection, the review queue, the diff, the apply, the undo — but the prompts behind it have not been reviewed and are switched off on the service. A run today comes back with nothing written and returns your quota. Nothing here is charged for.
The mechanism is described anyway, because it is the part worth understanding before you trust anything with your published pages. Read it as what will happen, not as what happens today.
The line that is never crossed
Rewriting somebody's published article is the most invasive thing on this shelf, so the constraint is absolute: a rewrite may restructure what you wrote, and may never change what it claims.
No fact, figure, date, price, statistic, name or company that was not already in your text. No new links. No strengthening or hedging of a claim. If the text does not support what would be needed, the rewrite is declined rather than invented.
What it can do
- Answer blocks. Your opening paragraph, rewritten so the answer is in it rather than three paragraphs below — in your register, from your claims.
- Headings. A heading rewritten toward the question it answers. The link anchor is preserved, so existing links to that section keep working.
- FAQ data. Structured data generated from questions and answers already on the page — never invented, and never emitted where your theme or SEO plugin already emits its own.
A decline is the product working
Crawlune will frequently propose nothing for a heading or a page. That is not a failure and it is not a wasted item: a heading that already reads as a question does not need rewriting, and inventing a change to justify the call would be exactly the behaviour the constraint above forbids.
If you see very few declines across a run, that is worth questioning — not the reverse.
Review, then apply
Every proposal is shown beside your current text. You approve or discard each one, and edit any before approving. There is no bulk approve, on any plan.
Applied changes are recorded before they are made, so a run can be undone completely and your original text comes back exactly.
Quota is used when text is generated
Not when it is applied. Discarding a proposal does not refund it and regenerating costs again — which is why the review step sits before the write rather than after it.
Page builders are out of scope
Elementor, Divi and WPBakery store content in their own structures, and rewriting into those is not something to attempt at arm's length. Crawlune leaves that content alone rather than risking your layout.