What is a Claude Project for SEO content?

Quick Answer: A Claude Project lets you load your brand voice, ICP, banned phrases, and content templates into a persistent workspace so every piece of SEO content Claude produces sounds like you, targets the right audience, and follows a consistent structure. Setup takes under an hour and eliminates the prompt-from-scratch cycle that slows most content teams down.

Most teams using Claude for SEO content hit the same wall. The first draft is decent. The second sounds different. By the fifth piece, you are re-explaining your brand voice, re-listing your banned phrases, and wondering why the output keeps opening with "In today's fast-paced world."

The fix is not a better prompt. It is a Claude Project.

This tutorial walks you through building a Claude Project specifically for B2B SaaS SEO content, from the initial setup to loading your brand context, ICP, and formatting rules, so every article Claude produces is on-brand, structured for search, and ready to edit rather than rewrite.

What Is a Claude Project (and Why It Matters for SEO Content)?

A Claude Project is a persistent workspace inside Claude that retains custom instructions, uploaded documents, and conversation history across sessions. Unlike a standard chat, you do not lose your context when you close the tab.

For SEO content production, this matters for three reasons:

• Consistency: Claude applies the same voice, tone, and structure every time without you re-prompting it
• Speed: You skip the setup phase on every new article and go straight to the brief
• Quality control: Banned phrases, ICP details, and formatting rules are baked in, not bolted on

Claude Projects are available on Claude Pro and Team plans via Anthropic.

What You Need Before You Start

Before building your Project, gather the following. If any of these do not exist yet, this setup process is a good forcing function to create them.

• Brand voice document: Tone descriptors, writing style, what the brand sounds like and does not sound like
• ICP profile: Job title, company stage, pain points, language your audience uses
• Banned phrases list: Words and patterns your content must avoid (generic AI language, competitor names, internal jargon)
• Content templates: Your preferred article structures for how-to guides, listicles, comparison posts
• SEO formatting rules: H1/H2 structure, meta description guidelines, internal linking approach, target word counts

You do not need all of these to be perfect. A rough version of each is enough to start. You refine them as you produce content.

Step 1: Create the Project and Name It Clearly

Open Claude and navigate to the Projects section in the left sidebar. Click "New Project."

Name it something specific, not "Content" or "SEO." A name like "SaaS Hackers SEO Content Engine" tells anyone using the workspace exactly what it is for.

Add a short project description. This is for your team, not for Claude, but it helps when you have multiple Projects running.

Step 2: Write Your Project Instructions (This Is the Core)

Project Instructions are the persistent system prompt that Claude reads before every conversation in this workspace. This is where you load everything that makes your content yours.

Structure your Project Instructions in clearly labelled sections. Here is the framework:

Section 1: Role and Purpose

Tell Claude exactly what it is doing in this Project.

Example:

You are the SEO content writer for SaaS Hackers. You produce articles that rank in traditional search and get cited by AI engines like Google AI Overviews, ChatGPT, and Perplexity. Every piece of content serves human readers and AI systems simultaneously.

Section 2: Brand Voice and Tone

Do not just say "professional but approachable." Give Claude specific descriptors and examples.

Include:

• Tone adjectives (direct, opinionated, practical, no-fluff)
• Sentence style (short paragraphs, active voice, no filler intros)
• What the brand does not sound like (corporate, jargon-heavy, passive)

If you have a brand voice document, paste the relevant sections directly into the instructions rather than attaching it as a file. Inline instructions take priority.

Section 3: ICP Details

Describe your reader in enough detail that Claude can calibrate every article to them.

Include:

• Job title and seniority (e.g., Head of Marketing at a Series A B2B SaaS company)
• Core pain points relevant to your content topics
• What they already know (so Claude does not over-explain basics)
• What they are trying to decide or do when they search

Section 4: Banned Phrases and Patterns

This section has the highest ROI of anything in your Project Instructions. Paste your full banned phrases list here.

Organise it into categories:

• Overused words: delve, leverage, utilise, robust, seamless, holistic
• Filler phrases: "it is worth noting", "at the end of the day", "in today's world"
• Structural patterns: three-part lists ending with "and more", sentences opening with "Ultimately," or "Essentially,"
• Punctuation rules: no em dashes for parenthetical asides

The more specific you are, the cleaner the output.

Section 5: SEO and GEO Rules

Tell Claude how to structure every article for both search and AI citation.

Include:

• H1/H2/H3 hierarchy rules
• Quick Answer box requirement at the top of every article
• FAQ section requirement (minimum 3 questions, 40-60 word answers)
• Paragraph length limits (2-4 sentences max)
• Primary keyword placement rules (H1, first 100 words, at least one H2, meta description)
• GEO requirements: direct definitional statements, self-contained pull-quote sentences, entity signals (brand name, specific product names)

Section 6: Content Templates

Paste your article templates directly into the instructions. Label each one clearly.

Example:

Template: How-To Guide H1: How to [Achieve Outcome] Quick Answer box Intro (80-120 words): hook, problem, what reader will know by the end H2 sections: each answering a distinct sub-question FAQ section: minimum 3 questions

Having templates in the instructions means Claude follows your structure by default. You do not have to specify it in every brief.

Step 3: Upload Supporting Documents

Project Instructions have a character limit. For longer reference documents, use the file upload feature inside the Project.

Good candidates for uploaded documents:

• Full brand style guide
• Competitor content examples (to show what to differentiate from)
• Previous high-performing articles (to show what good looks like)
• Keyword clusters and topic maps
• Customer interview transcripts or sales call summaries (for authentic ICP language)

Label every uploaded file clearly. Claude reads file names as context signals.

Step 4: Build a Standard Brief Format

Consistency in your briefs produces consistency in your output. Create a standard brief template and use it for every article you commission inside the Project.

A strong SEO content brief for this Project should include:

1. Target keyword: primary search term the article must rank for
2. Secondary keywords: 2-4 related terms to weave in naturally
3. Search intent: what is the reader trying to do or decide?
4. Article format: which template to use (how-to, listicle, comparison)
5. Funnel stage: TOFU, MOFU, or BOFU
6. Specific angle: the unique point of view this article takes
7. Word count target
8. Any SERP context: what the top-ranking pages cover and where they fall short

Paste this brief at the start of each new conversation inside the Project. Claude reads the Project Instructions first, then your brief, so the two work together.

Step 5: Run a Test Article and Audit the Output

Before using the Project for live content, run a test article against a brief you know well.

Check the output against this audit list:

• Does the opening sentence hook without a filler intro?
• Is the primary keyword in the H1, first 100 words, and at least one H2?
• Does every H2 answer a distinct sub-question?
• Are paragraphs 2-4 sentences maximum?
• Is there a Quick Answer box at the top?
• Is there an FAQ section with at least 3 questions?
• Does the tone match your brand voice document?
• Are there any banned phrases in the output?
• Do the ICP pain points and language feel accurate?

Where the output misses, go back to your Project Instructions and add a more specific rule. This iteration loop is how you tune the Project over the first 3-5 articles.

Step 6: Maintain and Update the Project Over Time

A Claude Project is not a set-and-forget tool. Treat it as a living document.

Update the Project Instructions when:

• Your brand voice evolves
• You identify new banned phrases that keep appearing in drafts
• Your ICP changes (new target segment, new pain points)
• You add new content formats to your production mix
• You find a structural pattern that consistently produces strong results

Add new example articles to the uploaded documents folder as you publish content that performs well. These become quality benchmarks Claude can reference.

What This Setup Produces vs. Standard Claude Prompting

How SaaS Hackers Uses This Approach

At SaaS Hackers, this Project setup is the foundation of the content production system. The Project Instructions contain the full brand voice document, ICP profile, banned phrases list, SEO and GEO formatting rules, and all article templates.

Every article starts with a standard brief dropped into the Project. The output follows the correct structure, avoids generic AI language, and targets the right reader from the first draft. Editing time per article dropped significantly once the Project was tuned across the first five pieces.

The biggest lever was the banned phrases section. Loading a specific, categorised list of patterns to avoid produced a more noticeable improvement in output quality than any other single change.

FAQs

What is a Claude Project and how is it different from a regular Claude chat? A Claude Project is a persistent workspace that stores custom instructions, uploaded documents, and conversation history across sessions. Unlike a standard chat, the context does not reset when you close the browser. For SEO content production, this means your brand voice, ICP, and formatting rules are applied automatically to every article without re-prompting.

How long does it take to set up a Claude Project for SEO content? Initial setup takes 45-60 minutes if your brand voice document, ICP profile, and banned phrases list already exist. If you are creating those assets from scratch during setup, allow 2-3 hours. The first 3-5 articles you produce inside the Project will also require iteration on the instructions as you identify gaps.

What should I put in Claude Project Instructions for content production? Your Project Instructions should include: a clear role definition, brand voice and tone descriptors, ICP details (job title, pain points, knowledge level), a banned phrases list organised by category, SEO and GEO formatting rules, and your content templates. Inline instructions take priority over uploaded documents, so put your most important rules directly in the instructions rather than in a file.

Can I use one Claude Project for all my SEO content or should I build separate ones? One Project works well if you produce content for a single brand with a consistent voice and audience. Build separate Projects if you produce content for multiple brands, if you have distinct content lines with different tones (e.g., technical documentation vs. thought leadership), or if you want to test different instruction sets against each other.

Does a Claude Project improve output quality compared to a detailed one-off prompt? Yes, for two reasons. First, the instructions are applied before Claude reads your brief, so the context is always present rather than competing for attention in a long prompt. Second, the persistent structure means you iterate and improve the instructions over time based on real output, which a one-off prompt approach does not support systematically.