← All workflows

SEO Audits That Create the Fix List

A 3-step chain crawls the site for technical issues, pulls Search Console and GA4 data, creates an audit deliverable ranked by priority, then generates specific tasks with pages and fix instructions. A review task lands on your desk.

What this does

This playbook audits a client’s site from three angles: a technical crawl for broken links, missing alt text, and on-page issues; Search Console data for ranking drops and content gaps; and GA4 data for traffic trends and high-bounce pages. It saves a full audit deliverable, then creates a batch of tasks from the top findings. Each task names the specific page, the issue, and what the fix looks like. A review task lands on your desk so you can check priorities before the team starts.

Best for

Agencies running SEO for clients who need regular audits that lead to actual work getting done. Works as a monthly or quarterly check-in, or as the first audit when onboarding a new SEO client.

How the chain works

Template 1: SEO Audit. Crawls the client’s site for technical issues (broken links, missing alt text, heading problems, thin content, meta tags). Pulls Search Console data for ranking drops, low-CTR pages, and content gaps. Pulls GA4 data for traffic trends and high-bounce pages. Saves everything in one “SEO Audit Findings” deliverable ranked by priority. When done, books Template 2.

Template 2: Create Tasks from Audit. Reads the audit deliverable and creates tasks from the top findings. Each task is scoped to one specific issue: a page that needs a meta description, images missing alt text, a broken link to fix, a thin page to expand. The prompt limits the batch to the top 5-8 findings so the team isn’t overwhelmed. Remaining findings stay in the audit deliverable for next month. When done, books Template 3.

Template 3: Review Audit & Tasks. Review the audit deliverable for the full picture, check that the generated tasks are scoped correctly, adjust priorities or due dates, and assign to team members.

Requirements

Connect GSC first. The client’s Search Console must be linked in Settings > Integrations.
Connect GA4. Link the client’s Google Analytics property in integrations for traffic data.
The client profile should have their website URL set so the AI can crawl it.

How to use it

Create a task from “SEO Audit” for your client, due on the first business day of the month (or whenever you want the audit to run).
On its due date, it autocompletes: crawls the site, pulls GSC and GA4 data, creates the audit deliverable, then creates a batch of tasks from the top findings. To run it earlier, mark it complete yourself or click Run Prompt.
The review task lands in your queue. Read the full audit deliverable, check the generated tasks, adjust priorities, and assign to your team.

Make it recurring

Add a line to Template 1’s prompt: “Also duplicate this task for the first business day of next month.” Each month you get a fresh audit that catches new issues and tracks whether old ones were fixed.

Customize the focus

New SEO clients. Run it during onboarding to get a baseline and create the first round of work. Pair with the keyword strategy playbook to turn content gaps into a prioritized keyword plan.
Content-focused audits. Add to the prompt: “Scope the site crawl to /blog only.”
Local SEO clients. Add gbp_report to the tools and a line: “Also pull Google Business Profile data and check for NAP consistency issues.”
E-commerce. Add: “Pay special attention to product and category pages. Look for thin product descriptions and missing structured data. Use the ecom kpi profile for GA4.”

Tips

Review the full audit, not just the tasks. The tasks are the top picks, but the deliverable has everything. Scan it for anything you’d prioritize differently.
Tag consistency. Each generated task gets tagged “seo-audit” so you can filter and track audit work across clients.
Content gaps are usually the highest ROI. Queries with impressions but no dedicated page mean people are searching and you’re not showing up. The keyword strategy playbook turns these into a content plan.

The templates

Paste these into Settings → Task Templates in your Lifted Work account. Create a template group, add each template in order. When you create tasks from these templates, the AI picks up client context automatically.

SEO Audit (1/3)

25 min budgeted Auto-complete: on Run AI on complete: on Tags: seo, audit, analysis

Lifty Prompt

Run a full SEO audit for this client:

Part 1: Technical Site Crawl Browse the client’s website and check for:

Broken links (internal and external)
Missing or empty image alt text
Missing or duplicate title tags and meta descriptions
H1 issues (missing, duplicate, or multiple H1s per page)
Broken heading hierarchy (H3 before H2, skipped levels)
Thin content pages (under 300 words)
Pages with no internal links pointing to them
Any other structural or accessibility issues

Crawl at least the homepage, main navigation pages, and 10-15 interior pages (blog posts, service pages, etc.).

Part 2: Search Console Analysis Pull the client’s Search Console data for the past month compared to the previous month:

Summary (clicks, impressions, CTR, position trends)
Top queries: look for drops in clicks, impressions, or position
Top pages: look for pages losing traffic or with high impressions but low CTR
Query x page cross-reference: look for content gaps (queries with impressions but no dedicated landing page)

Part 3: GA4 Traffic Analysis Pull the client’s GA4 data for the past month compared to the previous month:

Summary (sessions, users, bounce rate, avg session duration)
Landing pages: look for pages with high bounce rates or losing sessions month-over-month
Channels: look for organic traffic trends specifically

Create the audit deliverable: Create one deliverable titled “SEO Audit Findings” containing:

Brief performance overview: is organic traffic up or down? Key trends in 2-3 sentences.
All findings organized by category (technical issues, content gaps, ranking drops, traffic problems)
Each finding should include: what the issue is, which specific URLs are affected, current numbers from GSC/GA4 where applicable, and estimated impact (high/medium/low)
Rank all findings by estimated impact, highest first

Priority order for ranking: content gaps first (high-impression queries with no page), then ranking/traffic drops on existing pages, then technical issues affecting indexed pages, then on-page fixes.

When done, create a task from the “Create Tasks from Audit (2/3)” template assigned to me, due in 5 minutes.

Create Tasks from Audit (2/3)

10 min budgeted Auto-complete: on Run AI on complete: on Tags: seo, tasks, planning

Lifty Prompt

Look up deliverables for this client with title “SEO Audit Findings” and include the content. Read the full audit.

Your job is to turn the audit findings into a manageable batch of work — aim for roughly 2-3 hours of total work across all tasks. Do not try to fix everything at once.

Scoping each task: For each finding, estimate how long the fix would take a human. Use these rough benchmarks:

Writing a new landing page: 1-2 hours
Updating meta descriptions: ~2 minutes per page
Fixing broken links: ~5 minutes per link
Adding image alt text: ~1 minute per image
Rewriting thin content: 30-60 minutes per page
Fixing heading hierarchy: ~5 minutes per page

If a finding affects many pages, break it into a right-sized chunk rather than one massive task. For example, if 40 pages are missing meta descriptions, create a task for the 10 highest-traffic pages (~20 min), not all 40. The remaining pages can be caught in next month’s audit.

Include the time estimate in each task’s SOP’s / Details field (e.g., “Estimated time: 30 minutes”).

Creating the tasks: Work down the ranked findings and create tasks until you hit roughly 2-3 hours of total estimated work. This might be 3 tasks or 7 — the count depends on the size of each fix. Stop when the batch is full, even if there are more findings.

For each task:

A clear, specific title describing the fix and its scope (e.g., “Add meta descriptions to top 10 blog posts by traffic”, “Create landing page for ‘keyword’ (1,200 impressions/mo, no dedicated page)”, “Fix 8 broken internal links on service pages”)
Due dates spread across the next 2 weeks
In the SOP’s / Details field: which specific pages or queries are affected, current numbers (impressions, clicks, bounce rate, etc.), what “fixed” looks like, step-by-step instructions, and the time estimate
Tag: “seo-audit”

After creating all tasks, create a task from the “Review Audit & Tasks (3/3)” template assigned to me, due tomorrow.

Review Audit & Tasks (3/3)

15 min budgeted Tags: seo, review, planning

SOP / Details

AI has run a full SEO audit and created a batch of tasks (scoped to ~2-3 hours of work) from the top findings. Review before your team starts working:

Read the audit deliverable. Open “SEO Audit Findings” on the first task in this chain. It has every finding ranked by impact — not just the ones that became tasks.
Check the generated tasks. Look for tasks tagged “seo-audit”. Each one has a time estimate in the SOPs. Make sure the issues are the right priorities for this client right now.
Check the scope. Large issues were broken into chunks (e.g., “top 10 pages” instead of all pages). If a chunk is too big or too small, adjust it.
Adjust priorities and assign. The tasks default to the next 2 weeks. Adjust based on your team’s capacity and assign to the right people.
Check for quick wins. Some fixes (adding alt text, fixing a broken link) take 5 minutes. Knock those out now if you can.
Remaining findings will be picked up in next month’s audit. If something can’t wait, create a task for it manually.
Mark this task complete.

Make your future better

Adopt at your own pace

Guided setup

Cancel anytime

Easy start

More workflows

Build a Brand Guide That Powers Every AI Image

Two chained tasks that reverse-engineer the client's brand into a single note covering voice, visual system, photography direction, a catalog of real reference images from their site, and a 50 to 75 word prompt modifier that prepends to every future AI image. Every downstream image playbook reads this note on every run.