How do you build an SEO brief generator in Make.com?

Quick Answer: You can build a fully automated SEO brief generator in Make.com by feeding a CSV of keywords into a workflow that calls an AI model, generates structured briefs, and writes each one directly to a new Google Doc. The entire setup takes under an hour and runs without manual input once live.

Manually writing SEO briefs for every keyword in your pipeline is slow, inconsistent, and the first thing that creates a bottleneck when you are trying to scale content. This tutorial shows you exactly how to wire up Make.com to read a keyword list from a CSV, pass each keyword through an AI prompt, and drop a formatted brief into Google Docs automatically.

By the end, you will have a working automation that produces writer-ready briefs on demand, without touching a single brief yourself.

What You Need Before You Start

Before building the workflow, get these four things in place:

• A Make.com account (the free tier works for testing; the Core plan at $9/month handles volume)
• An OpenAI API key (or access to another AI module in Make, such as Anthropic Claude)
• A Google account with Google Drive and Google Docs access
• A CSV file with at least one column labelled keyword containing your target search terms

The CSV can live in Google Drive, Dropbox, or your local machine. For this tutorial, it sits in Google Drive so the whole workflow stays cloud-based.

How the Workflow Is Structured

The automation runs in five stages:

1. Trigger: Watch for a new or updated CSV file in a Google Drive folder
2. Parse: Extract each row from the CSV and isolate the keyword value
3. Generate: Send the keyword to an AI model with a structured brief prompt
4. Format: Map the AI output into a clean document structure
5. Output: Create a new Google Doc for each brief and write the content in

Each keyword produces one Google Doc. If your CSV has 20 keywords, you get 20 briefs.

Step 1: Set Up Your Google Drive Trigger

Open Make.com and create a new scenario. Add the Google Drive: Watch Files module as your trigger.

Configure it to watch a specific folder, for example /SEO Briefs/Input. Set the trigger to fire when a new file is added to that folder.

This means every time you drop a fresh CSV into the folder, the scenario activates and processes the entire file.

Important: Set the maximum number of results per cycle to match your typical CSV size. For a 50-keyword file, set this to 50.

Step 2: Parse the CSV File

After the trigger, add a CSV: Parse CSV module.

• Set the CSV content field to the file content output from the Google Drive trigger
• Enable Column names in the first row if your CSV has headers
• Map the keyword column so Make knows which field to extract

This step converts each row into a separate bundle that flows through the rest of the scenario independently. One row, one brief.

Step 3: Write Your AI Brief Prompt

Add an OpenAI: Create a Completion module (or OpenAI: Create a Chat Completion if you are using GPT-4 or GPT-4o).

This is the most important step. The quality of your briefs depends entirely on the prompt you write here.

A Prompt That Produces Usable Briefs

Use a system message like this:

You are an expert SEO content strategist. When given a keyword, produce a structured 
SEO content brief in the following format:

**Target Keyword:** [keyword]
**Search Intent:** [informational / commercial / transactional / navigational]
**Recommended Title (H1):** [one title]
**Meta Description:** [150-160 characters]
**Target Word Count:** [number]
**Suggested H2 Sections:** [list of 5-7 H2 headings]
**Secondary Keywords to Include:** [list of 4-6 related terms]
**Key Questions to Answer:** [list of 3-5 questions the article must address]
**Internal Link Opportunities:** [2-3 suggested topic areas to link to]
**Content Notes:** [any specific guidance for the writer]

Be direct. Be specific. Do not add commentary outside the brief format.

In the user message field, pass the keyword from your CSV parse step using Make's variable mapping:

Write an SEO brief for this keyword: {{keyword}}

Set the model to gpt-4o for best output quality. Set max tokens to 800 to keep briefs tight.

If you want to standardise prompts across multiple workflows, it helps to understand what a ChatGPT prompt library is and how reusable prompt systems improve consistency.

Step 4: Create a New Google Doc for Each Brief

Add a Google Docs: Create a Document module.

• Name: Set this to something like SEO Brief - {{keyword}} using the mapped keyword variable
• Folder: Point it to your output folder, for example /SEO Briefs/Output

This creates a blank, named document ready to receive content.

Step 5: Write the Brief Content into the Doc

Add a Google Docs: Insert a Paragraph to a Document module directly after the create step.

• Document ID: Map this to the document ID output from Step 4
• Content: Map this to the AI response text from Step 3
• Append to: Set to the end of the document

Run the scenario. Each keyword in your CSV now produces a named Google Doc containing a fully structured SEO brief.

How to Handle Errors and Edge Cases

A few things will break this workflow if you do not account for them:

Empty rows in the CSV: Add a Filter module between the CSV parse step and the AI step. Set the condition to keyword is not empty. This stops blank rows from generating blank docs.

API rate limits: If your CSV has more than 20 keywords, add a Sleep module between the AI step and the Google Docs step. Set it to 1-2 seconds. This prevents OpenAI rate limit errors on larger batches.

Inconsistent column names: Make is case-sensitive when reading CSV headers. Make sure your CSV column is labelled exactly keyword in lowercase, or update the mapping in Step 2 to match whatever header you use.

How to Scale This for an Agency Workflow

Once the base workflow runs cleanly, you can extend it in three ways:

• Add a Slack notification after each doc is created, posting the doc link to a channel so writers know a new brief is ready
• Write a row back to a Google Sheet with the keyword, doc link, and creation timestamp to maintain a brief tracker
• Add a second AI call before the brief generation step that pulls competitor headings from a search API (such as DataForSEO) and injects them into the prompt context

Each of these is an additional module chain in the same scenario. You do not need a separate workflow.

For teams formalising this process, reviewing broader B2B SaaS benchmarks can help you set realistic content production targets and efficiency goals.

What Makes This Better Than a Standalone SEO Brief Tool

Dedicated SEO brief generators like Swiftbrief, Konvart, or Semrush's brief tool produce good output, but they sit outside your workflow. You still need to manually export, file, and distribute each brief.

Building this in Make.com means:

• Briefs land directly in Google Drive, named and organised, without any manual steps
• You control the prompt, so the brief format matches exactly what your writers need
• The workflow connects to whatever comes next, whether that is a Notion content calendar, a Slack brief review channel, or a Google Sheet tracker
• Cost per brief drops to a few cents of OpenAI API usage rather than a per-seat SaaS subscription

For content teams running 20+ briefs a month, the time saving compounds quickly. If you eventually want outside help scaling production, it may be worth comparing B2B SaaS content marketing agencies that specialise in repeatable content systems.

FAQs

What is a Make.com SEO brief generator? A Make.com SEO brief generator is an automated workflow that reads keywords from a CSV file, sends each keyword to an AI model with a structured prompt, and writes the resulting brief into a Google Doc. It replaces manual brief writing with a repeatable, scalable process that runs without intervention once set up.

How much does it cost to run this automation? Running costs depend on volume. Make.com's Core plan costs $9/month and covers standard usage. OpenAI API calls for GPT-4o cost roughly $0.005-$0.015 per brief at 800 tokens. For 100 briefs a month, total cost is under $3 in API fees plus your Make subscription.

Can I use a different AI model instead of OpenAI? Yes. Make.com has native modules for Anthropic Claude, Google Gemini, and other AI providers. The workflow structure stays identical. Swap the OpenAI module for the model of your choice and adjust the prompt format if needed. Claude tends to produce well-structured output for brief-style tasks.

Do I need coding skills to build this in Make.com? No coding is required. Make.com uses a visual drag-and-drop interface. Every step in this tutorial is configured through module settings and variable mapping, not code. Basic familiarity with Make's interface is enough to follow the steps.

What should a good SEO brief include? A good SEO brief includes the target keyword, search intent classification, a recommended H1 title, meta description, target word count, suggested H2 headings, secondary keywords, key questions the article must answer, and any content notes for the writer. The prompt in Step 3 of this tutorial covers all of these fields.

Can this workflow process multiple keywords at once? Yes. The CSV parse module in Step 2 splits the file into individual bundles automatically. Make processes each row as a separate iteration of the workflow, so a CSV with 50 keywords generates 50 briefs in a single scenario run. Add a Sleep module between steps if you hit API rate limits on larger files.