URL-based tasks let you lock in a fixed list of URLs at the moment you create a task, so you can track resolution to completion without the list changing between crawls.
What are URL-Based Tasks?
Lumar offers two types of tasks to help you manage site issues:
- Filter-based tasks contain a dynamic list of URLs that match the current report filters. The URL list updates with every crawl, which makes them ideal for ongoing monitoring of evolving issues.
- URL-based tasks capture a fixed snapshot of the URLs present in the report when the task is created. The list does not change between crawls, so you always know exactly which pages are in scope.
If you need to hand off a defined set of pages to a developer or agency and track whether each one gets fixed, URL-based tasks are the right choice.
How to Create a URL-Based Task?
- Open any compatible report in your project. URL-based tasks are currently available on crawl_urls reports.
- Click the Tasks button in the report toolbar. A dropdown appears showing your creation options and any existing tasks for the report.
- Select URL-Based Task. The description reads: “A fixed list of the URLs present when a task is created. Great for tracking resolution over time.”
- Give your task a name, set the priority and status, and save. The current set of URLs in the report is now locked to this task.
See the screenshot below for the task creation dropdown with both task type options:
Screenshot: Task creation dropdown showing Filter-based and URL-based options
Managing Tasks in the Task List
Navigate to Project Tasks in the left sidebar to see all tasks across your project. The task list displays each task’s name, type, URL count, percentage unresolved, trend, and priority.
A badge next to each task name indicates its type: a filter icon for filter-based tasks, and a link icon for URL-based tasks. You can search tasks by name and customize which columns are visible using the column toggle.
Screenshot: Project Tasks list with task type badges, URL counts, and unresolved trends
Tasks are organized by status—Done, Testing, In Progress, To Do, and Backlog—with a count next to each group. This makes it easy to see at a glance how work is distributed.
Viewing Task Details
Click any task to open its detail modal. Here you’ll find everything you need to understand the task at a glance:
- Trend chart: A line chart showing how the unresolved count has changed over recent crawls. New tasks display a placeholder until enough crawl data is available.
- Counts summary: The original URL count, the current unresolved count, and the percentage still unresolved. Click on the Original Count or Unresolved Count to navigate the the Task View.
- Metadata: Assignee, priority, created date, deadline, status, task type, and the base report the task was created from.
- Requirements / How to fix: Actionable instructions for resolving the issue.
- Linked tickets: Create a new ticket or link an existing one in Jira.
- Actions: Generate a delivery ticket, archive, edit, or delete the task.
Screenshot: Task detail modal showing trend chart, counts, metadata, and actions
Using the Task View
Each task also has a dedicated Task View page, accessible from the left navigation under Project Tasks. This page shows the full report data for the URLs in the task, along with the crawl date selector, severity, and status.
For URL-based tasks, the Task View is especially valuable: because your URL list is fixed, you can compare the same set of pages across multiple crawls to see exactly which ones have been resolved and which still need attention. You'll also see a list of "New" URL, which are any URLs that match the task filters but weren't in the original URL list.
Screenshot: Task View page for an internally linked broken pages task
Note URL-based tasks are built on Custom Reports. The Task View requires at least one crawl to run after the task is created. If no post-creation crawl data exists, you’ll see a message asking you to run a new crawl. |
When to Use Each Task Type
Use this quick guide to decide which task type fits your workflow:
| Choose Filter-Based When… | Choose URL-Based When… |
| You want to monitor an issue category over time | You have a specific set of pages to fix |
| The exact URLs don’t matter—just the pattern | You need to hand off a defined list to a developer or agency |
| You expect the scope to evolve with each crawl | You want to track progress and see which pages were resolved |
| You’re running ongoing quality checks | You want a stable scope that doesn’t grow unexpectedly |
Tips & Best Practices
- Create URL-based tasks before running your next crawl so the Task View populates with fresh data as soon as the crawl completes.
- Use the trend chart in the task detail modal to demonstrate remediation progress to stakeholders.
- Link tasks to tickets in your project management tool to keep development and SEO workflows connected.
- Archive completed tasks rather than deleting them so you retain a record of past remediation efforts.
Frequently Asked Questions
Can I add or remove URLs from a URL-based task after creation?
Not at this time. The URL set is locked when the task is created. If you need a different set, create a new task from the updated report.
Which reports support URL-based tasks?
URL-based tasks are currently compatible with crawl_urls reports. Additional report types may be supported in the future.
Why does the Task View say “No reports available for this crawl”?
URL-based tasks are built on Custom Reports. You need to run at least one new crawl after creating the task for the Task View to populate. This requirement will be removed in a future update.
What happens to resolved URLs in a URL-based task?
They stay in the task. The unresolved count decreases, but the original count and full URL list remain intact. This lets you review what was fixed and measure the impact of your work.