Help
Support
A real person reads it, and questions about whether a change is safe get answered first.
Replies normally arrive within one business day. If you are reporting something that changed pages unexpectedly, say so in the subject line and it goes to the front of the queue.
Scoping a run
By space
Give it a space key — the part of the URL after
/wiki/spaces/, for example DOCS — and it covers
the pages in that space.
By query
For anything narrower, use a CQL query, which overrides the space key. CQL is Confluence's own search syntax, so anything valid in advanced search works here:
space = DOCS and label = runbookspace = DOCS and lastmodified >= "2026-01-01"ancestor = 123456— everything under one parent page
What gets changed
| Location | Default |
|---|---|
| Body text, including text inside macro bodies, panels and table cells | Always |
| Link targets (the URL behind a hyperlink) | On — can be turned off |
| Smart-link and embed card URLs | On — can be turned off |
| Code block contents | Off — opt in per run |
| Macro parameters and configuration | Never |
| Page structure, table geometry, formatting | Never |
Code blocks are off by default because a base-URL migration usually should update them and a wording change usually should not. Turning the option on is a deliberate choice, made per run.
Matching and undoing
Ignore case
Matches any casing. The replacement is inserted exactly as you typed it.
Whole words only
cat will not match inside catalog. Punctuation still counts as a word edge, so oldcorp, matches.
Undo one page
Every edit is an ordinary Confluence version labelled with the terms used. Open the page and revert from Page history.
Undo a whole run
Run it again with the terms swapped. Preview first — if the original text existed elsewhere already, the dry run shows you before anything is touched.
Limits and permissions
Page limits
A single interactive preview or apply covers up to 25 pages, and the app tells you plainly when more pages matched than were scanned — it will never quietly process part of a run and report success. For larger spaces, narrow the scope with CQL and work through it in batches. Background processing for large runs is planned.
Permissions
The app acts as you. If a page is restricted so that you cannot edit it, the app cannot either — it reports that page as skipped rather than failing the whole run. This also means two people running the same search may see different numbers of pages, which is correct behaviour, not a bug.
Reporting a problem
The most useful report includes the find and replace terms, the scope you used, which options were on, and what you expected versus what happened. If a specific page is involved, its title or ID helps.
Please do not paste confidential page content — a description of the structure involved (for example "the page has a Table of Contents macro and a code block") is usually enough.
Feature requests are welcome and genuinely read. support@foliocradle.com