Do I need a specific Ahrefs plan for this to work?

You need an Ahrefs plan that includes Site Audit and API access. The workflow uses your existing site audit project, so whatever crawl frequency and page limit you already have is what it reports on.

What happens if Ahrefs hasn't finished a fresh crawl that week?

If the latest site audit data is the same one we already reported on, the workflow exits cleanly without filing tickets. You won't see duplicates just because the crawl is on a longer cadence.

Can I run this across more than one project or domain?

Yes. Run a copy of the workflow per Ahrefs project. Each copy can point at its own Linear team and its own label so different sites stay in their own swim lane.

How are priorities decided?

Priority is derived from severity and reach. Error-level issues that affect a large number of pages come in as Urgent, smaller errors as High, broader warnings as Normal, and small warnings as Low. You can tweak the thresholds when you set the workflow up.

Weekly Ahrefs Site Audit to Linear Tickets for Engineering

Q: Won't this create the same ticket again every week?

No. Before filing anything, the workflow checks Linear for tickets opened in previous runs and skips any issue whose set of affected pages is already covered by an open or recently closed ticket. You only get a new ticket when something genuinely new breaks.

Every Monday at 8am, turn the latest Ahrefs Site Audit results for our tracked project into clean technical SEO tickets in Linear for the engineering team. The goal is that on Monday morning, engineers see only the new, real, deduped work, never a flood of one ticket per affected URL.

What the agent should do, in order:

1. Pull the overall site health using the Ahrefs Get Site Audit Health Score operation so we know the current trend for our project.

2. Get the currently flagged issues using Ahrefs List Site Audit Issues. Keep only Error and Warning severities. Drop Notice-level issues entirely. If nothing Error or Warning is open, exit cleanly with no tickets filed.

3. For each remaining issue, use Ahrefs Get Site Audit Page Explorer to pull the list of affected URLs for that issue. Cap the per-issue URL fetch at a sensible number (a few hundred is fine, we do not need every URL for a pattern issue).

4. Group related pages so that pattern issues become a single ticket. A broken redirect chain or a missing canonical that spans 50 URLs is one ticket titled something like "Fix missing canonicals on /blog/* (47 URLs)", not 50 individual tickets.

5. Dedupe against previous runs. Before filing anything, look up open and recently closed Linear tickets in the configured team with the configured label, and skip any issue whose set of affected pages is already covered by an existing ticket. Only file something when it represents new or materially changed work.

6. For each surviving issue, file a Linear ticket using the Linear Create Issue operation with all of the following:

- A clear, specific title (e.g. "Fix 4xx errors on 12 product pages").

- A Markdown description that explains the SEO impact in plain English (why this hurts crawl, indexing, or rankings), the recommended fix from Ahrefs, and the list of affected URLs (cap the list at 25 and append "...and N more" if there are more).

- A priority derived from severity and reach: Error with many pages affected = Urgent, Error with few pages = High, Warning with many pages = Normal, Warning with few pages = Low.

- The configured label (default: seo).

- The configured Linear team.

Configuration the workflow needs from the user at setup time:

- Which Ahrefs Site Audit project to pull from.

- Which Linear team to file tickets in.

- Which Linear label to apply (default: seo).

- The page-count thresholds for the priority ladder (with sensible defaults so it works out of the box).

Trigger: cron, weekly, Monday 8am in the user's local timezone. Ahrefs does not support per-issue webhooks, so a weekly cron matches typical site audit crawl cadence. If the workflow runs and the latest crawl is the same one already reported on in the prior run, exit cleanly without filing anything.

What it does

Pulls your Ahrefs site audit health score and active issues every Monday morning so technical SEO work always has a fresh queue.
Groups related broken pages into a single ticket, so one redirect chain across 50 URLs files one issue, not fifty.
Skips low-severity notices and anything already covered by a recent ticket, so engineers see only what's worth fixing.
Files each fix in Linear with a clear title, the plain-English SEO impact, the affected URLs, a recommended fix, and a priority based on severity and reach.

What you’ll need

An Ahrefs account with a Site Audit project already running for the site you want to monitor.
A Linear workspace, plus the team and label you want new SEO tickets filed under (we default to a label called seo).

How to customize it

Move the schedule. Run it every Monday at 8am, switch to a different day, or step it up to twice a week.
Pick the Linear destination. Route tickets to your platform team, your web team, or any squad that owns SEO fixes, and change the label.
Tune the severity bar. Include or exclude warnings, raise the page-count threshold for what becomes Urgent, or filter out specific issue types you don't action.

Use cases

Notifications & Alerts
Research & Monitoring

Turn weekly Ahrefs site audits into Linear tickets

Integrations

Type

Categories

What it does

What you’ll need

How to customize it

Use cases

FAQs

Related prompts