Catch regressions and fix at scale Pro
Fixes queue: bulk fixes you review and approve
Propose the same fix on many pages at once — built-in fixes or text you write (and AI drafts, only if you connect an AI provider) — review every change, then apply and undo them in the background.
Updated for Lumtera 1.2.2 and Lumtera Pro 1.1.1.
Overview
The fixes queue is under Lumtera → Fixes → Fixes queue. Propose fixes asks where to start: The same issue on many pages, Every issue from one check, or Everything in one shared part (fix at the source), which changes the header, footer, pattern or menu itself so every page that shows it gets the fix. Choose the issue, check or part and press Propose fixes. Proposing does not change any page.
There are three kinds of proposed fix. Some come from Lumtera's built-in rules, such as a link that opens a new tab. Some need text, such as alt text: when AI is set up, it drafts the text with your own provider and marks it "Drafted by AI"; otherwise the reviewer writes it under Text to use. Under Review changes, each change shows what is removed and added. Approve, Reject, or edit the text and save it before approving. Rejected changes are never applied.
Apply writes approved changes to the pages in the background, a few at a time, and you can leave the screen. Each page keeps a revision first, and each change is checked again: the result says Fixed or that the re-check still reports the issue. Undo takes applied fixes back off, newest first, and checks the page again. Changes that could not be applied, or whose page changed since the proposal, wait under Needs attention with the reason.
Why does it matter?
The same missing table header or new-window link can sit on hundreds of pages. Fixing each one by hand takes days, and letting a tool change pages without anyone looking is a risk no site owner should take.
What do you get?
- Propose from the same issue on many pages, from every finding of one check, or at the source in a shared header, footer, pattern or menu.
- Every change waits for a person: approve it, reject it or edit the text first.
- Applied in the background, with a revision saved first and a re-check after each change.
- Undo any applied fix from the queue.
- Each run handles up to 25 changes on Personal, 100 on Growth, 250 on Agency and 500 on Unlimited.
How does it work?
-
Propose
Lumtera proposes a fix for each page: a built-in fix for the check, text a person writes, or a draft from your own AI provider if you connected one. Nothing on your pages changes yet.
-
Review
Check each change, edit the text if needed, then approve or reject it.
-
Apply
Approved fixes are written to the pages and checked again. You can undo any of them.
Who is it for?
-
A repeated problem in old content
Links that open a new tab without warning across years of posts are proposed, reviewed and fixed in one run.
-
A bad footer or menu
Fix at the source changes the shared part once, instead of every page that shows it.
-
Alt text for a large media library
AI drafts alt text for each image in context, and an editor approves, edits or rejects each one.
Good to know
How it behaves, what it needs, and where its limits are.
- Plans and access
- Included in every Pro plan with an active license. Two permissions set under Lumtera → Settings → Fix approvals: Propose fixes, and Approve and apply fixes. Administrators always have both, editors by default. People also need to be able to edit the page, so only roles that can edit content can be given them; read-only roles such as Subscriber, the Accessibility client and the Lumtera Reporter cannot.
- Changes per run
- Personal 25, Growth 100, Agency 250 and Unlimited 500 changes per run. The rest are counted and left for another run, never dropped silently.
- Approval rule (Agency and Unlimited)
- With "Require a second person to approve" on, nobody can approve a fix they proposed themselves. The rule also applies to single fixes made from the editor and the Content report.
- AI agents
- "Let AI agents approve rule fixes" is off by default. When on, an AI agent connected to the site may approve and apply fixes from Lumtera's built-in rules only. AI-written text always needs a person, and the setting has no effect while the approval rule is on.
- What happens next
- A fix the re-check confirms closes its tracked task, adds a comment to the task's issue in GitHub, GitLab, Jira or Linear, and is added to the evidence log. Content that a page builder manages is never changed.
Questions
Something else on your mind? Contact support
Do I need AI for the fixes queue?
No. Most fixes are built into the checks, and a person can write text such as alt text themselves. AI drafts appear only if you connect your own AI provider to WordPress, and like every other change they wait for a person to approve them. AI never changes a page on its own.
Can two people be required?
Yes, on Agency and Unlimited. With "Require a second person to approve" on, nobody can approve a fix they proposed themselves.
Does it need AI?
No. Built-in rule fixes need no AI, and text fixes can be written by the reviewer. When AI drafts text, your account has a limit per 10 minutes, and the run pauses and carries on by itself.
Can I stop a run?
Yes. Cancel run stops after the item in progress. Items done before that stay as they are, and applied fixes can still be undone.
More in “Catch regressions and fix at scale”
-
Pro
Email and Slack alerts
Hear about it when a publish adds new errors or feedback goes past its target, never twice for the same one, plus a Monday summary and a score history.
-
Pro
Compare scans
See what is new, what was fixed and what is still there between two scans, by check and by site part, with the likely cause marked.
-
Pro
Fix tracking
Turn issues into tasks, assign them, and let Lumtera close each task when a re-scan confirms the fix.
Fixes queue: bulk fixes you review and approve
Get it with Lumtera Pro
In every Pro plan. Personal is $149 a year. Pro installs alongside the free plugin, and your settings and results stay.
14-day refund (opens in a new tab)Keeps working if you don't renew