Improving pages
The metered half. Crawlune proposes changes to your own published prose, and nothing is applied until you have read it.
Hosted rewriting is enabled for activated licenses. Answer blocks, headings and grounded FAQ results have been verified through generation, review, apply and undo. A verified account can start with 25 free hosted items once, on one site. See the trial and one-time item packs.
Review every suggestion before applying it. Generated results consume your license allowance; local audits and crawler controls do not require a license.
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. For answer blocks and headings, undo restores the saved whole-page text. This also replaces manual edits made after that rewrite, so read the warning before confirming. Undo newer Crawlune writes to that page first; an older run cannot roll back through a newer recorded rewrite.
FAQ undo changes structured data only: it restores the previous FAQ data, or removes the added data when none existed. The page's text is not changed. Activity reports skipped or unavailable entries; a run's undo depends on its saved journal records.
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.