Linear
AvailableSend findings to Linear as issues in the team you choose. Sending a finding again comments on its issue instead of opening a second one, and the issue's state shows on the finding.
On Pro and above.
Integrations
Sitejar connects to six task tools (Linear, GitHub, Jira, ClickUp, Asana and Trello), to Slack and Microsoft Teams for alerts, and to your own systems through signed webhooks, a REST API and an MCP server for AI coding agents. The point is that a scan finding reaches the person who fixes it, in the tool they already use, and that the next scan, not a closed ticket, confirms the fix.
A scan is only useful when its findings reach the people who fix them. Sitejar scans a site in a real browser for accessibility (WCAG 2.1 AA), security, privacy, deceptive design, technical quality and SEO, and every problem it finds becomes an issue in your workspace, tracked from one scan to the next. Integrations move those issues out of Sitejar and into your team's day: as tasks in a tracker, as messages in a channel, or as events your own code receives.
Everything marked Available on this page works today and is set up from the dashboard. Each one has its own page with the exact setup steps, what data it shares and stores, and what happens after the next scan. Website platforms and automation platforms are planned, not built, and say so.
Turn findings into tasks where your team already works. One task per finding, never a duplicate, with the task's status shown on the finding and a comment after each scan.
Send findings to Linear as issues in the team you choose. Sending a finding again comments on its issue instead of opening a second one, and the issue's state shows on the finding.
On Pro and above.
Open GitHub issues in the repositories you choose through the Sitejar GitHub App, which asks only for issues and metadata. A whole report becomes one issue with a task list.
On Pro and above.
Create Jira Cloud issues in the project you choose, converted to Jira's own format, and see each issue's status on the finding. If your account reaches several Atlassian sites, you choose which one.
On Agency and above.
Create ClickUp tasks in the list you choose, with a whole report as one parent task and a subtask per finding. Task status shows on the finding.
On Agency and above.
Create Asana tasks in the project you choose, with a whole report as one task and a subtask per finding. Sitejar shows whether each task is complete.
On Agency and above.
Add Trello cards to the board list you choose, with a whole report as one card carrying a checklist of the others. Sitejar shows whether each card is complete.
On Agency and above.
Tell a channel when a scan finds something your team should look at. Alerts are rules on a site, and a rule can email people and post to channels at once.
Post alerts to a Slack channel through an incoming webhook: a score drop, a new Confirmed High finding, a missing security header or a failed scan, each with a link to the report.
On Agency Plus.
Post the same alerts to a Teams channel as an Adaptive Card, through an incoming webhook or a Power Automate workflow url.
On Agency Plus.
Connect Sitejar to your own systems: receive signed events, start scans from code and fail a build on a score.
Signed JSON to your own HTTPS endpoint when a scan completes, a score drops 5 points or more, or new Confirmed High findings appear. Retried for you, with a delivery log.
On Business and above.
Start scans and read results with an API key, gate a CI build on a score, and upload SARIF to code scanning. Documented on the developers page.
On every plan, Free included.
Give an AI coding agent a scanner it can call. It scans a page, reads the issues and applies the fix guidance with your own model.
Let an AI coding agent such as Claude Code or Cursor scan a page, read the issues and apply the fix guidance with its own model, through the remote MCP server.
On every plan, Free included.
Planned, not built. These have no page and nothing to set up yet.
Planned: scan a Webflow site and fix image alt text from inside the Webflow Designer. Not available yet, and we do not have a date to share.
Planned: start a scan and read the results from the WordPress dashboard. Not available yet.
Planned: scan a Shopify store from its admin. Not available yet.
Planned, not built. Webhooks already work with any automation tool that accepts an incoming webhook.
Planned: start a scan, or act on a finished one, from a Zap. Not available yet. Until then, a webhook can feed an automation that accepts incoming webhooks.
Planned: start a scan, or act on a finished one, from a Make scenario. Not available yet.
Alongside that loop, alerts in Slack or Microsoft Teams tell a channel when a scan needs attention, and webhooks tell your own systems. Developers can start scans from code with the Sitejar REST API, and an AI coding agent can scan and fix a single page through the Sitejar MCP server.
Some task tool features have their own plan: whole-report sends and after-scan comments are on Business and above, and moving tasks automatically after a scan and per-client destinations are on Agency Plus.
Prices and everything else each plan includes are on the pricing page: compare plans on the pricing page.
Six task tools (Linear, GitHub, Jira Cloud, ClickUp, Asana and Trello), Slack and Microsoft Teams for alerts, signed webhooks to your own endpoint, a REST API with CI support, and a remote MCP server for AI coding agents. Webflow, WordPress, Shopify, Zapier and Make are planned and not available yet.
No. Sitejar links each finding to the task it created. Sending the same finding again through the same connection adds a comment to the existing task instead of creating a second one.
No. A task's status shows on the finding, but a finding is fixed only when a scan no longer detects the problem. A task closed while the scan still finds the problem is flagged as reopened.
Linear and GitHub are on Pro and above. Jira, ClickUp, Asana and Trello are on Agency and above. Webhooks are on Business and above, and Slack and Microsoft Teams alerts are on Agency Plus. The REST API, CI checks and the MCP server are on every plan, Free included.
A title naming the dimension, severity, rule, page count and site, and a body with the confidence label, a selector, the standard, the first 20 page urls, the suggested fix when one exists and a link back. Never finding evidence or page content.
Encrypted with AES-256-GCM before they are written, never sent to the browser. The GitHub integration stores no token at all, only the installation id. Disconnecting empties the stored credentials at once.
Not yet. Both are planned. Until then, a Sitejar webhook can send scan events to any automation tool that accepts an incoming webhook.
An Owner or Admin of the Sitejar workspace connects task tools, adds alert channels and adds webhooks. Once a task tool is connected, an Owner, Admin or Editor can send findings to it.
Building on Sitejar yourself? Read the Sitejar REST API reference, set up the Sitejar MCP server for your AI coding agent, or compare Sitejar plans.
Last updated . Linear and the Linear logo are trademarks of Linear Orbit, Inc. GitHub and the GitHub logo are trademarks of GitHub, Inc. Jira and the Jira logo are trademarks of Atlassian. ClickUp and the ClickUp logo are trademarks of Mango Technologies, Inc. (ClickUp). Asana and the Asana logo are trademarks of Asana, Inc. Trello and the Trello logo are trademarks of Atlassian. Slack and the Slack logo are trademarks of Slack Technologies, LLC. Microsoft Teams and the Microsoft Teams logo are trademarks of Microsoft Corporation. Webflow and the Webflow logo are trademarks of Webflow, Inc. WordPress and the WordPress logo are trademarks of WordPress Foundation. Shopify and the Shopify logo are trademarks of Shopify Inc. Zapier and the Zapier logo are trademarks of Zapier, Inc. Make and the Make logo are trademarks of Celonis (Make). Sitejar is not affiliated with or endorsed by any of them.