Subtasks, dependencies and recurring tasks
Break big tasks down, stop work being completed out of order, and make repeating work create itself.
Subtasks
Use subtasks when a task is really a short list of steps, such as “Review redirects” with one subtask per redirect group. The parent task shows progress from its subtasks, so the list view tells you how far along it is without opening it.
Subtasks come from three places: you add them by hand, a task template creates them, or a Screaming Frog import creates one subtask per issue under a parent for each category.
Under Settings › General you can choose to require subtasks to be complete by default, so a parent cannot be finished while steps are open.
Dependencies
A dependency says “this task cannot finish until that one has”. It stops work being completed out of order, for example publishing a page before the redirect it needs is live.
- Open the task and find the Dependencies card.
- Add the task it depends on. The card shows the chain, with an arrow from each task to the one it unblocks.
- While a required upstream task is open, the dependent task shows Blocked by that task and cannot be completed.
Managers and administrators can override a block when they have a good reason. The override asks for a reason and is logged, so there is always a record of who skipped a step and why. Specialists and developers cannot override.
Recurring tasks
For work that repeats, such as a monthly performance review or a quarterly technical check, set the task to repeat. On the task, find Repeats and choose Weekly, Monthly or Quarterly. The default is Does not repeat.
When you complete a recurring task, SEO Ops creates the next one, with the next due date. Task cards show a note such as “Repeats monthly” so you can recognise them at a glance.
Tip: combine a recurring task with a template. A recurring “Monthly SEO Review” with its subtasks gives every client the same checklist every month. See Task templates.
How they work together
| You want to… | Use |
|---|---|
| Split one job into steps | Subtasks |
| Stop step B being finished before step A | A dependency |
| Do the same job every month | A recurring task |
| Create the same checklist for each new client | A task template |
Common questions
What happens to the old recurring task?
It stays as a completed task in the history. The new one is a fresh task with its own status, comments and due date.
Can I depend on a task for a different client?
Dependencies are for connected work, so keep them within the same client’s tasks.
Why is a task blocked?
The task page and the list both say which task blocks it. Finish that task, remove the dependency if it was added by mistake, or ask a manager to override.