Plan. Assign. Track.Without leaving QueryCatch.
A built-in ticketing system for SEO teams. Table or kanban, five categories, four statuses, comments, scheduled dates and email notifications — auto-linked to your approvals.
Two views, one source of truth
Switch between a sortable, filterable table and a drag-and-drop kanban board for the same tickets. The view changes; the data doesn’t.
Auto-linked to your approvals
Every approval request becomes a ticket assigned to the reviewer. Your team’s work queue and your approvals queue are the same queue — no second tool to check.
Notify whoever needs to see it
Add CC emails per ticket, even if they aren’t QueryCatch users. Status, priority, assignee and due-date changes all email the right people automatically.
Table for power, kanban for flow
Same tickets, two perspectives. Switch in a click; your preference sticks per profile.
Table view
Sortable, filterable, paginated. Pin the columns that matter, hide the ones that don’t. Use it for triage, sprint planning and reporting.
- · Multi-column sort and per-column filtering
- · Click any row to open the full ticket editor
- · Better for backlogs of 50+ tickets
Kanban view
Four columns — todo, in progress, done, cancelled. Drag a card to change status. Best for status-at-a-glance standups and visual prioritisation.
- · Drag-drop status changes
- · Card view shows priority + assignee
- · Better for active work in flight
Five categories that match how SEO teams actually work
Filter by category to keep dev work, strategy work and approval work in their own lanes.
Web development
Hand off implementation work — schema markup, redirects, hreflang, sitemap fixes — to your dev team without leaving QueryCatch.
Site management
Plugin updates, hosting work, backups, CDN config — anything operational that’s not strictly SEO but lives next to it.
SEO
On-page work, content briefs, internal linking decisions, technical audits — the meat of what your SEO team ships.
Consult
Client-facing strategy items, planning sessions, audits to walk through — so consulting work has a home in the same backlog.
Approval requests
Auto-created the moment someone requests approval on a meta title, blog draft, or product feed edit. Closed automatically when the approval is applied.
From created to closed, in four steps
The same shape every ticket follows, whether you created it or it landed automatically from an approval.
Create with the right detail
Title (≤200 chars), Markdown description (≤2,000 chars), priority, category, assignee, scheduled date, plus optional CC emails for stakeholders outside your QueryCatch workspace.
Pick your view
Switch to kanban for status-at-a-glance and drag-drop. Switch to table for filtering, sorting and multi-column views. Same data, different lens — toggle any time.
Comment, change, collaborate
Threaded comments per ticket. Every status, priority, assignee or due-date change writes to a change log so latecomers can catch up without scrolling.
Close out cleanly
Mark done or cancelled. Approval-linked tickets close automatically when their parent approval applies. The audit trail stays.
Linear + Slack + email vs all-in-one
If your team currently coordinates SEO work across three tools, here's what changes when it lives next to the data.
Separate tools
- Tickets in one tool, the SEO data they’re about in another
- Approvals lost in Slack threads, no link to the actual work
- Stakeholders chase status in email because they’re not in your PM tool
- Duplicate notifications across three apps, none authoritative
- No audit log spanning data + decisions + execution
QueryCatch Tickets
- Tickets live with the SEO data, integrations and AI suggestions
- Approvals auto-create tickets — one queue, one place to look
- CC any email on a ticket; stakeholders get notified without a login
- One source of truth for status changes, comments and assignments
- Audit trail spans the request, the review, and the work
Built for the people doing the work
Whether you’re an agency, an in-house team or a one-person show.
Agencies juggling multi-client backlogs
Each profile is a client; each profile has its own ticket queue. Filter by category to see only the dev work this sprint, or only the SEO work for next quarter.
In-house teams without a separate PM tool
You don’t need Linear or Asana to coordinate SEO work. Tickets cover plan / assign / track and live alongside the data the work is about.
Solo operators with stakeholders to update
Add the client, the founder or the brand lead as a notification CC on a ticket. They get emailed every status change without needing a QueryCatch account.
Tickets pair with Approvals, included
Approval requests automatically become tickets assigned to the reviewer — so your team’s work queue and your sign-off queue live in the same place. No second tool, no second login.
See how Approvals workFrequently asked questions
Honest answers about how Tickets actually work.
What kinds of tickets can I create?
Five categories: web development, site management, SEO, consult, and approval requests. The first four are user-created; approval requests are auto-created the moment someone requests approval on a meta title, blog draft, image SEO or merchant feed change.
Table or kanban — which should I use?
Both, depending on what you’re doing. Kanban is best for status-at-a-glance and quick drag-drop reordering. Table is better when you need filters, multi-column sort, or bulk operations across many tickets. The view toggles per page and your preference persists.
Can I notify someone who doesn’t have a QueryCatch login?
Yes. Each ticket lets you add a list of CC email addresses — clients, founders, brand stakeholders. They’ll be CC’d on every status, priority, assignee and due-date change without needing to log into QueryCatch.
Does the system have AI assistance for tickets?
Not currently. Tickets are user-created or auto-created from approvals — no AI categorisation, suggested assignee, or draft response. We’ve focused AI on the work itself (Blog Writer, Meta AI, etc.) and kept ticketing as a deliberate human workflow layer.
How do approval-request tickets work?
When you request approval on any AI suggestion, the system creates a ticket flagged as an approval request, assigns it to the chosen reviewer, and emails them. The ticket links back to the approval card so the reviewer can open the diff in one click. When the approval is applied, the ticket closes automatically.
Can I attach files to a ticket?
Comments support Markdown including image URLs, so you can paste hosted screenshots and rich formatting. Native file upload is on the roadmap; today, hosted-link references are the workflow.
Who can edit or close a ticket?
Anyone in the workspace can create, edit, reassign and close tickets — Tickets is built as a collaborative shared backlog rather than a permission-gated work tracker. The audit trail records who made every change, so you always know who did what. Comments are tighter: you can only edit your own comments, and only within the first 30 minutes after posting.
How does a ticket relate to an approval?
Approval-request tickets carry the approval ID so the relationship is queryable. Anything you do on the ticket (status change, comment, assignee swap) lives next to the approval lifecycle, giving you one timeline for the entire decision and execution.
Simple Pricing
One Plan, Unlimited Potential
Start with our base plan and scale as you grow. No surprises, just value.
1 website • 2 users • All 20+ features included
One backlog. Every SEO task.
Tickets are included in every QueryCatch plan. Set up your team, plug in your stakeholders, ship more work with less coordination overhead.