Skip to content

Every automation I can build for your content team.

100 automations for SEO, AI search, social, video and publishing. Take the five-question quiz to see which ones fit together for you, or search the directory.

Scope it, build it, hand it over.

Every automation on this page goes through the same three steps. Nothing gets built before we know where your team's hours go, and nothing is finished until your team can run it without me.

  1. 01 · Scope

    The Audit

    $2,500, two weeks

    • Technical SEO and AEO, competitors and channels
    • What to produce for the next 90 days
    • Every automation mapped, scoped and ranked by hours and risk

    Yours to keep, even if your team builds it.

  2. 02 · Build

    AI enablement

    From $3,500 a month, six months

    • Every automation the audit scoped, in your own accounts
    • A human check designed into each one
    • Your team keeps leading content

    Nobody owns content yet? The Fractional Head of Content retainer, from $5,000 a month, is enablement plus me leading content and producing everything.

  3. 03 · Teach

    Handover

    Part of every build

    • Documentation and a recorded walkthrough
    • An owner on your side who has seen it fixed once
    • Everything stays in your tools if we stop

    Building your own? The hands-on workshop is $2,000.

Then the next one, until the scope is built

Which automations fit together for you?

5 questions, one tap each. You get a system of up to ten automations, wired stage to stage, and the one to build first. No email needed to see it.

Build your system

Pick a goal, where you are with it and the step that eats your week. Watch the plan assemble on the right.

Each answer is worth 10 points and fills in one part of the plan. Change any answer and the map changes with it.

18 automated content systems.

6 goals, each at 3 stages: starting from zero, scaling what works, or fixing what is slipping. Each system wires real cards from the directory below, from research to measurement, with a person checking the work before anything goes live.

Goal
Stage

Search that compounds

Competitor gaps and keyword data feed briefs and comparison pages, every page gets linked, and the ones near page one get pushed.

10 automations · 1 human check

  1. 01 · Research

  2. 02 · Create

  3. 03 · Publish

  4. 04 · Distribute

  5. 05 · Measure

What measurement finds sets next month's research.

Want a system like this built?

Three fields. Whichever system is open goes with it, and any card you asked about.

What should happen next?

All 100 automations.

Tool for LLM visibility

Track how often ChatGPT, Gemini, Perplexity, and Google's AI answers mention your brand – with share of voice against competitors. Free while we work together.

Explore the tool

100 of 100 automations

Fixing orphan pages with internal links

Claude CodeLumarBotify
Complexity
Medium
Saves
10–40h/mo
Build time
1–2 weeks

Case study writing workflow

Claude CodeClaude
Complexity
Low
Saves
<10h/mo
Build time
1–3 days
Read the build

llms.txt and AI-readable pages

Claude Code
Complexity
Medium
Saves
<10h/mo
Build time
1–3 days
Read the build

Content decay detection

n8nGSC
Complexity
Medium
Saves
10–40h/mo
Build time
1–2 weeks

Automated indexing for new pages

n8nGSC
Complexity
Medium
Saves
<10h/mo
Build time
1–3 days

Reddit post automation

n8nOpenAI
Complexity
Medium
Saves
10–40h/mo
Build time
1–2 weeks
See the tool

Listicle articles built from a spreadsheet

n8nOpenAIExa
Complexity
High
Saves
40h+/mo
Build time
2+ weeks

Reddit comment scraper

n8nApifyAirtable
Complexity
Low
Saves
<10h/mo
Build time
1–3 days

Reddit keyword monitoring

n8nReddit APIApify
Complexity
Low
Saves
<10h/mo
Build time
1–3 days

Reddit comment automation

n8nClaudeApify
Complexity
Low
Saves
10–40h/mo
Build time
1–2 weeks

Content distribution automation

Claude CodeClaude
Complexity
Medium
Saves
10–40h/mo
Build time
1–2 weeks

Content marketing automation

n8nClaudeNotionAlso: Airtable
Complexity
Medium
Saves
40h+/mo
Build time
1–2 weeks

SEO workflow management

n8nAirtableClaude CodeAlso: OpenAI
Complexity
Medium
Saves
10–40h/mo
Build time
1–3 days
Read the build

Blog posts turned into explainer videos

Claude CodeElevenLabsFFmpeg
Complexity
High
Saves
10–40h/mo
Build time
1–2 weeks

YouTube publishing kit and upload

YouTube APIWhisperAirtableAlso: Google Sheets
Complexity
Medium
Saves
10–40h/mo
Build time
1–2 weeks

Product demo videos from a script

Claude CodeElevenLabsFFmpeg
Complexity
High
Saves
10–40h/mo
Build time
2+ weeks

Short videos from an idea list

n8nVeoGoogle SheetsAlso: YouTube API
Complexity
Medium
Saves
10–40h/mo
Build time
1–2 weeks

Faceless explainer videos for YouTube

n8nClaudeElevenLabsAlso: Creatomate, YouTube API
Complexity
High
Saves
40h+/mo
Build time
2+ weeks

Avatar presenter videos from scripts

n8nHeyGenElevenLabsAlso: Google Drive
Complexity
Medium
Saves
10–40h/mo
Build time
1–2 weeks

Long videos clipped into shorts

n8nWhisperOpusClipAlso: Buffer
Complexity
Medium
Saves
10–40h/mo
Build time
1–2 weeks

Captions burned into every video

n8nWhisperFFmpegAlso: Google Drive
Complexity
Low
Saves
<10h/mo
Build time
1–3 days

Videos dubbed into other languages

n8nElevenLabsYouTube API
Complexity
Medium
Saves
10–40h/mo
Build time
1–2 weeks

Thumbnail concepts for every video

n8nGeminiOpenAIAlso: Google Drive
Complexity
Medium
Saves
<10h/mo
Build time
1–3 days

Articles turned into podcast episodes

n8nClaudeElevenLabs
Complexity
Medium
Saves
10–40h/mo
Build time
1–2 weeks

Outlier videos in your niche

n8nYouTube APIClaudeAlso: Slack
Complexity
Low
Saves
<10h/mo
Build time
1–3 days

LinkedIn scheduling and post performance

BufferLinkedInGoogle Sheets
Complexity
Medium
Saves
10–40h/mo
Build time
1–3 days

Multi-author LinkedIn content calendar

Claude CodeLinkedInNotion
Complexity
Medium
Saves
40h+/mo
Build time
1–2 weeks

Topics and hooks from top newsletters

SubstackClaude CodeGoogle Sheets
Complexity
Low
Saves
<10h/mo
Build time
1–3 days

Image cards and posters for social posts

Claude CodeGeminiLinkedIn
Complexity
Medium
Saves
10–40h/mo
Build time
1–2 weeks

Comment drafts in your browser

OpenAILinkedInX
Complexity
Low
Saves
<10h/mo
Build time
1–3 days

Daily LinkedIn posts with an approval step

n8nClaudeGoogle SheetsAlso: Slack, LinkedIn
Complexity
Low
Saves
10–40h/mo
Build time
1–3 days

Carousels from one article

n8nClaudePlacidAlso: LinkedIn, Instagram
Complexity
Medium
Saves
10–40h/mo
Build time
1–2 weeks

Finished videos posted everywhere

MakeGoogle DriveOpenAIAlso: TikTok, YouTube API
Complexity
Low
Saves
10–40h/mo
Build time
1–3 days

Comment replies drafted for approval

n8nInstagramClaudeAlso: Slack
Complexity
Medium
Saves
10–40h/mo
Build time
1–2 weeks

Audience comments mined for ideas

n8nYouTube APIApifyAlso: Claude, Google Sheets
Complexity
Medium
Saves
<10h/mo
Build time
1–3 days

Brand mention triage

GumloopApifyClaudeAlso: Slack, Airtable
Complexity
Medium
Saves
10–40h/mo
Build time
1–2 weeks

Founder posts from calls and team wins

FathomSlackClaudeAlso: Notion
Complexity
Medium
Saves
10–40h/mo
Build time
1–2 weeks

Reviews turned into social proof posts

MakeG2ClaudeAlso: Bannerbear, Buffer
Complexity
Low
Saves
<10h/mo
Build time
1–3 days

Reddit threads that AI answers cite

LLM visibility platformReddit APIClaude Code
Complexity
Medium
Saves
10–40h/mo
Build time
1–2 weeks
See the tool

Pre-publish SEO and AEO check

Claude CodeGoogle DocsGSC
Complexity
Medium
Saves
10–40h/mo
Build time
1–3 days

AI search readiness audit

n8nFirecrawlClaude
Complexity
Medium
Saves
<10h/mo
Build time
1–3 days

AI crawler and referral traffic monitor

CloudflareVercelGA4Also: Google Sheets
Complexity
High
Saves
<10h/mo
Build time
1–2 weeks

Articles scored for AI answers

GumloopClaudeGoogle Docs
Complexity
Medium
Saves
10–40h/mo
Build time
1–2 weeks

Directory and review-site listing kit

Google SheetsGoogle DriveClaude Code
Complexity
Low
Saves
10–40h/mo
Build time
1–3 days

Store collection pages written and shipped

ShopifyClaude CodeGoogle Sheets
Complexity
Medium
Saves
40h+/mo
Build time
1–2 weeks

Docs and llms.txt updated on every release

GitHubClaude Code
Complexity
High
Saves
10–40h/mo
Build time
1–2 weeks

Articles syndicated to LinkedIn and Medium

AirtableGoogle DocsGSCAlso: Claude Code
Complexity
Medium
Saves
10–40h/mo
Build time
1–2 weeks

Branded hero images for every post

Claude CodeFigma
Complexity
Low
Saves
10–40h/mo
Build time
1–3 days

Guest posts from your knowledge base

Claude CodeGoogle DocsNotion
Complexity
Low
Saves
10–40h/mo
Build time
1–3 days

Nurture email sequences with visuals

Claude CodeHubSpot
Complexity
Medium
Saves
10–40h/mo
Build time
1–2 weeks

Brand voice guide and draft check

ClaudeGoogle DocsSlack
Complexity
Low
Saves
10–40h/mo
Build time
1–3 days

Stale product claims caught sitewide

GitHubClaude Code
Complexity
Medium
Saves
<10h/mo
Build time
1–2 weeks

Expert interviews turned into articles

FathomClaudeGoogle Docs
Complexity
Low
Saves
10–40h/mo
Build time
1–3 days

Sales calls mined for content topics

GongClaudeAirtable
Complexity
Medium
Saves
<10h/mo
Build time
1–2 weeks

Customer language bank from reviews

GumloopG2ClaudeAlso: Google Sheets
Complexity
Medium
Saves
<10h/mo
Build time
1–3 days

Anatomy of one build: the content brief.

A brief is the strategist's pre-writing work. This workflow does it in about five minutes, and a person still decides whether the angle is right.

per brief
5 minper brief
the same brief by hand
60 to 90 minthe same brief by hand
in API costs per brief
~$0.15in API costs per brief
articles a month at Reply.io
24 to 36articles a month at Reply.io
  1. 01

    Trigger

    One row in a Google Sheet: the keyword and the product it is for. Set it to Planned and the workflow takes over.

    Google Sheetsn8n

  2. 02

    Decide

    A chain of single-job prompts picks the article type, the working title, the funnel stage and the goal. Each one reads the last.

    OpenAI

  3. 03

    Research

    The workflow pulls the top ten results for the keyword and picks the best one as the reference article.

  4. 04

    Outline

    The outline and up to ten supporting keywords are built from the type, the goal and that reference.

  5. 05

    Write back

    The full brief lands in the sheet and the row flips to Briefed.

  6. 06

    Human check

    An editor checks the angle and the sources before a writer starts. The workflow never decides what gets written.

What you keep

The n8n workflow file, every prompt in plain text, the sheet template, a recorded walkthrough and a runbook for changing the prompts when your funnel or positioning moves.

The tools behind the 100, counted.

How many of the 100 cards use each tool. n8n is on 50 and Claude on 39. Pick a tool to see its builds.

What I won't automate, even when it demos well.

A workflow can do the repeatable work around content. Six jobs stay with a person on every build, and the audit names the ones that matter in your setup.

  1. 01

    Choosing what to publish

    Pulling keyword data is mechanical. Picking the topic that matters is the most expensive call in content, so it stays with whoever owns the strategy.

  2. 02

    The argument and the voice

    A workflow can research, format and link around a piece. The point it makes, and how it sounds, comes from a person.

  3. 03

    Customer and expert interviews

    A workflow can transcribe a call and mine it for topics. Asking the follow-up question that finds the story is the interviewer's job.

  4. 04

    The decision to publish

    Every build stops at a check. Nothing goes live because a model finished.

  5. 05

    What the numbers mean

    Reports assemble themselves. The two sentences on what changed and what to do next are written by a person.

  6. 06

    Pages made only to rank

    Google's spam policies call it scaled content abuse: many pages made mainly to rank, with little value. I will not build it, at any volume.

Automation multiplies whatever plan sits in front of it. These six are the plan.

Four ways to get these built.

The same automations can come from an automation agency, your own hands or a freelance builder. Each is the right call for somebody.

busyless
Automation agency
Do it yourself
Freelance builder
Where it starts
A two-week audit of where the hours go
Their catalog of builds
A template or a tutorial
A spec you write
Who checks the output
A named person on your team, built into the flow
Their QA, before or after publishing
You, if you build the check
Usually not in scope
Who runs it after
Your team, with docs and a walkthrough
They do, while you pay
You
You, if it was documented
Cost shape
$2,500, then from $3,500 a month for six months
Monthly retainer
Tool subscriptions plus your time
Per project
The right call when
You want your team to own a few well-chosen builds
You want it run for you, indefinitely
You have the time and one clear job
You have one well-specified job

The content automation page compares the four in more depth.

Questions, ahead of time.

  • Can I download the automations in this directory as templates?+
    Not as files. Each automation is built in your own accounts and tuned on your content, because prompts tuned on someone else's blog produce someone else's briefs. Every build ships with its workflow, its prompts in plain text and its documentation, so you own all of it.
  • How long does each automation in the directory take to build?+
    Each card shows a build window. 35 of the 100 take one to three days, 51 take one to two weeks and 14 take longer. Much of that time goes on tuning the prompts against your real content, not on wiring the steps.
  • What do the time-saved figures on the automation cards mean?+
    A band for the hours a month the step takes a team doing it by hand: under 10, 10 to 40, or over 40. It is an estimate, not a promise. An automated step still needs someone to run and check it, and the audit measures the real hours with your team.
  • Which tools do the automations in this directory run on?+
    n8n appears on 50 of the 100 cards and Claude Code on 39, with a model such as Claude or OpenAI's where text is involved. Make appears on 3 and Gumloop on 3, where a team already runs them. The rest are the tools you use for search data, publishing and analytics.
  • Will these content automations work with our CMS?+
    Publishing steps go through the CMS's own API. The directory has builds for WordPress, Webflow, Shopify and Ghost, and a headless CMS works the same way. If your CMS has no API, the workflow stops at a ready-to-paste draft instead.
  • Who owns an automation after it is built?+
    You do. It runs in your accounts, on your API keys, with your documentation. If we stop working together it keeps running, and the person on your side who owns it has seen it fixed once.
  • What does it cost to have one of these automations built?+
    Most teams start with the $2,500 audit, which covers technical SEO and AEO, competitors, channels and a 90-day plan, and maps and scopes every automation. AI enablement then builds what it scoped, from $3,500 a month for six months, while your team leads content; the Fractional Head of Content retainer, from $5,000 a month, adds me leading content and producing it. Teams that want to build their own take the $2,000 workshop. Running costs are model and tool fees: the content brief workflow costs about $0.15 a brief.
  • Is the automations quiz result the plan you would build for us?+
    It is a starting point from five answers. The real order comes from the audit, which times every recurring step with your team and ranks the builds by hours returned and by risk.
  • Can you build an automation that is not in this directory?+
    Yes. Describe the job in the form above the directory, or search for it: a search that finds nothing turns into a build request. If a step repeats every week and a person can check the result quickly, it can usually be automated.
  • Do any of these automations publish without a person checking?+
    No. Each workflow stops at a check: an editor approves the brief, a founder approves the post, someone signs off a schema change. That check is part of the design, and it is what keeps automated content worth reading.