What bulk actions are for
As soon as you manage more than a handful of scheduled scans, maintaining them one by one quickly becomes tedious. Bulk actions help you maintain larger inventories quickly and in a controlled way.
This is particularly useful after:
- a sitemap import
- a relaunch with many new pages
- a change of alert strategy
- a clean-up of legacy entries
Which bulk actions there are
Depending on the current product version, you can do the following to several targets at once:
- enable
- disable
- delete
- turn email on critical alerts on or off
- turn email on warnings on or off
- turn webhook on warnings on or off
The most important operational actions are thus available directly on the Scheduled scans page.
How to use bulk actions sensibly
The typical flow is:
- select the relevant targets
- if needed, select all entries on the current page
- choose the action you want
- apply the change to all of them at once
That saves time and reduces mistakes when several entries are to end up in the same state.
Good use cases
After a sitemap import
You import many URLs, but you do not want to enable warnings or webhooks for all of them straight away. It then makes sense to only enable them first and to follow up with the rest collectively later.
Before a relaunch
If a project is deliberately unstable for a while, you can disable certain areas collectively or tone down notifications.
On team handovers
If the preferred delivery channel changes, email or warning settings can be adjusted for several targets together.
What to watch out for
- bulk actions only affect the targets currently selected
- existing limits and plan rules still apply
- webhooks can only be enabled meaningfully if a webhook URL is stored in your profile
- deleted targets are not just a display trick, they really are removed
Practical tip
Use bulk actions after a sensible selection, not blindly on everything. For clean monitoring it is almost always worth treating core pages and important landing pages separately from less relevant sub-pages.