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 | On — can be turned off |
| Page titles — renaming a page also changes its URL | On — can be turned off |
| Page labels — rename, merge, add or remove | Off — opt in per run |
| Page comments — footer and inline, including replies | Off — opt in per run; this edits what other people wrote |
| Link targets (the URL behind a hyperlink). A page link in page text, as opposed to a URL, that names a page this run renames is left for Confluence, which updates it when the rename lands | On — can be turned off |
| Smart-link and embed card URLs | On — can be turned off |
| Code block contents | Off — opt in per run |
| Titles of info, note, tip, warning, panel, expand and code macros, and the text of status labels | On — can be turned off (“Also rewrite macro titles and status labels”) |
| Every other macro parameter and setting | Never |
| A link that holds only text, once a match removes every word in it | Removed with its words |
| Page structure, table geometry, formatting, other than that link | 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.
Titles are the opposite — on by default, because a rename that leaves every page still called by the old name has not finished the job. It is worth knowing that renaming a page changes its URL, so links from outside Confluence to that page will need updating. Untick Also rewrite page titles to leave them alone.
Links inside Confluence are another matter: Confluence itself updates every link, Include and Excerpt Include that names a renamed page by its title, in place and without a new page version, so those updates are in no page history. The app leaves such references in page text for Confluence rather than rewriting them, and its report names the pages it can. A page whose title and text both change gets two new versions: its text, then its title.
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.
What the rest of the page keeps
The app edits the page’s own bytes rather than rebuilding it from a parse, so everything outside a match is sent back byte-for-byte as it was read — macros, tables, spacing and formatting included — except a link that holds only text, which goes with its words when a match removes every one of them, and the copy Confluence keeps of a decision list, rebuilt to match it (Confluence may reorder a macro’s attributes as it saves). Macro settings are never rewritten, other than the titles of info, note, tip, warning, panel, expand and code macros and the text of status labels, which “Also rewrite macro titles and status labels” changes; the run says how many matches it left inside the rest.
Undo one page
Every edit to a page is an ordinary Confluence version labelled with the run: the term and its replacement, or, for a run of several terms, how many it had. Open the page and revert from Page history.
A label change and a comment rewrite are not part of a page version, so reverting there leaves those as the run made them. Use Undo this run for either.
Undo a whole run
The results screen has an Undo this run button. It puts every page the run edited back to the version it was on beforehand, puts back any labels the run renamed, and puts each comment it rewrote back to that comment’s own earlier version. Pages somebody else has edited since are reported rather than overwritten, and so are comments.
A renamed page gets its old title back only where no other page of its space has taken it meanwhile; otherwise it keeps the new title, naming the page that has the old one where it found one. Putting a title back makes Confluence update the pages that name that page, in place and without a new version, so a space key or attribute order it changed on them when the run renamed the page can still differ.
Before writing a page, an apply or an undo checks whether someone has unpublished changes open on it, and leaves such a page alone, naming who. It cannot see every open edit (one typed in the last few seconds, for one), and writing over an edit it cannot see can lose it, so ask anyone editing the pages to publish or discard their changes first.
Do not undo by running the replacement backwards. If the new text already existed
somewhere, a reverse run rewrites that too — and a rename like
corp → corpcorp applies a second time to pages it has
already changed.
Limits and permissions
Page limits
Up to 25 pages runs on screen and finishes while you watch. Anything larger moves to a background queue automatically — you can close the tab and come back to the report. A single run covers up to 250,000 pages.
A scope larger than that is reported rather than trimmed: the app tells you how many pages matched and how many it took, so it never quietly processes part of a run and calls it a success.
The limit stops the app looking, not just changing. Pages past it were not examined — they were not skipped for lack of matches, so they may still contain the term. Narrow the scope with CQL and run again to reach them.
Two kinds of page are processed in the browser tab instead, and it needs to stay open while they are: pages in a knowledge-base space where the app could not establish that it can read them as itself, and pages in a space whose type could not be established — a page carrying no space key, or a space Confluence did not answer for. The app names which of the two applies before you start.
Elevated runs
A Confluence administrator, and only an administrator, can start a run from the app’s
administrator screen, and every run started there may edit pages the person running it
could not edit themselves. Those pages are counted separately in the report (a run interrupted and restarted part-way through a page can leave that page out), and every
page edit made that way is labelled [elevated] in that page's version
history. The privacy policy has the detail.
Permissions
By default 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