Back to dispatches
§ Dispatch № 149

Week 1 of SEO: What a Busy Founder Should Actually Ship

Five concrete deliverables for week one of your SEO plan. Domain audit, keyword roadmap, content strategy, technical fixes, and launch prep—nothing else matters yet.

Filed
April 21, 2026
Read
17 min
Author
The Seoable Team

Week 1 of SEO: What a Busy Founder Should Actually Ship

You shipped a product. Traffic isn't coming. You know SEO matters, but you have no idea where to start, and you're drowning in noise.

Here's the truth: most SEO advice is built for agencies with six-month budgets and teams of specialists. It doesn't apply to you. You need five things done in week one. Not ten. Not a roadmap for 2025. Five things that compound and actually move the needle.

This guide breaks down exactly what those five things are, how to ship them, and why skipping anything else is the right call.

Prerequisites: What You Need Before Week 1 Starts

You don't need much. But you need these three things locked in before you start.

First: Access to your domain. You need admin access to your website's hosting, domain registrar, and Google Search Console. If you don't have Search Console set up yet, set it up now. It takes five minutes and it's non-negotiable. This is where Google tells you what's broken, what's being indexed, and what keywords are actually driving clicks.

Second: A clear understanding of what problem you solve. Not your tagline. Not your pitch deck. The actual, specific problem your product solves for a real person. If you can't finish this sentence in one breath, you're not ready for week one: "We help [specific person] solve [specific problem] by [specific solution]." Get that locked in. Everything in week one builds on this.

Third: Thirty minutes a day for five days. Not an hour. Thirty minutes. Protect that time like it's a customer call. Because it is—you're closing customers with organic search, not paying for ads.

If you have those three things, you're ready. Let's ship.

Deliverable 1: Domain Audit (Day 1, 30 Minutes)

Your domain audit is not a 47-page PDF from an agency. It's a focused assessment of what's actually broken on your site right now.

You need to know three things: technical health, indexation status, and on-page basics. Tools like Ahrefs have built domain audit features specifically for founders, and services like Seoable deliver a full domain audit in under 60 seconds for a one-time $99 investment. If you're running lean, start there. If you want to DIY it, here's the process.

Step 1: Check Google Search Console. Open Search Console for your domain. Go to Settings → About this property. Look at three things:

  • Coverage. How many pages are actually indexed? If it's way lower than the number of pages you have, you have an indexation problem. Write that down.
  • Enhancements. Check Mobile Usability and Core Web Vitals. Are there errors? Write them down.
  • Performance. What queries are you getting impressions for? Click through to see your actual search visibility right now. This is your baseline.

Take a screenshot. You'll reference this all week.

Step 2: Run a technical crawl. Use Screaming Frog's free tier or Semrush's free audit to crawl your site. You're looking for:

  • Broken links (4xx, 5xx errors)
  • Missing meta descriptions
  • Duplicate title tags
  • Pages with no H1 tags
  • Redirect chains

Don't fix everything. Just identify it. Write down the top three technical issues. You'll tackle one in deliverable 5.

Step 3: Check Core Web Vitals. Go to PageSpeed Insights. Run your homepage. Are you in the green? If not, is it Largest Contentful Paint (LCP), Cumulative Layout Shift (CLS), or First Input Delay (FID)? Write it down. One of these might be your one technical fix for week one.

Step 4: Audit your homepage and top three pages. Open your homepage. Does it have:

  • A clear H1 that matches your core message?
  • Meta description (160 characters, includes your main keyword)?
  • Internal links to other important pages?
  • A clear call-to-action?
  • Schema markup (at minimum, Organization schema)?

Do the same for your top three pages (the ones you want to rank for your main keywords). Don't rewrite anything yet. Just assess.

Your deliverable: A one-page audit document with:

  1. Current indexation count
  2. Top 3 technical issues
  3. Core Web Vitals score
  4. Homepage meta description gaps (if any)
  5. One page that's missing schema markup

That's it. Thirty minutes. Done.

Deliverable 2: Keyword Roadmap (Days 1–2, 45 Minutes)

You don't need a 500-keyword spreadsheet. You need a ranked list of the ten keywords you're actually going to target in the next 90 days. One keyword per piece of content. Ten pieces. Ten keywords.

This is where most founders get lost. They think bigger is better. It's not. Focused is better. Ship ten pieces of content that rank for ten keywords, and you have momentum. Ship 100 pieces for 50 keywords, and you have noise.

Step 1: Start with your core keyword. This is the keyword that best describes what you do. If you're a CRM for freelancers, it might be "CRM for freelancers." If you're a Python library for data validation, it might be "Python data validation library."

Go to Google Trends and Google Search. Type in your core keyword. What do you see in the search results? Are there blog posts? Are there product pages? Are there forums? This tells you the search intent. Write that down.

Now, search your core keyword in Semrush or Ahrefs. What's the search volume? What's the keyword difficulty? If difficulty is over 60 and you're brand new, skip it for now. You'll come back to it in month two or three. Write down the search volume and difficulty.

Step 2: Find ten related keywords. Use one of these free or freemium tools:

For each of the ten keywords you find, you're looking for:

  • Search volume: 100–1000 searches per month is your sweet spot for week one. Lower than 100 and you're chasing ghosts. Higher than 1000 and you're competing with established players.
  • Keyword difficulty: Under 30 is ideal. 30–50 is okay if you're patient. Over 50 and you're fighting uphill.
  • Search intent: Is it informational (someone learning), commercial (someone comparing), or transactional (someone buying)? Your content strategy changes based on this.

Step 3: Cluster your keywords. Group related keywords together. If you have "best CRM for freelancers," "CRM for freelance writers," and "project management for freelancers," those three might be one content cluster. One pillar post, maybe two supporting posts.

But for week one, just rank your ten keywords by:

  1. Relevance to your product
  2. Search volume (higher is better)
  3. Keyword difficulty (lower is better)
  4. Your ability to provide a better answer than what's currently ranking

That last one is critical. If the top three results for your keyword are all from massive companies with massive budgets, skip it. You can't outrank them yet. Pick keywords where you have a real advantage: deeper expertise, better documentation, fresher data, or a different angle.

Your deliverable: A spreadsheet with ten keywords, ranked by priority. Columns:

  1. Keyword
  2. Search volume
  3. Keyword difficulty
  4. Search intent
  5. Why you can win (your unfair advantage)

You're not writing content yet. You're just locking in what you're going to write about. Forty-five minutes. Done.

Deliverable 3: Content Brief Template (Day 2, 30 Minutes)

This is where AI-generated content starts making sense. You can't just dump your keyword into ChatGPT and expect a ranking post. You need a brief.

A content brief is a one-page document that tells an AI (or a writer, or yourself) exactly what to write, who to write for, and what angle to take. It's the difference between a generic post and a post that ranks.

You're going to create one template that you'll use for all ten pieces of content. Then you'll fill it in once for each keyword.

Step 1: Define your brief structure. Here's the template. Use this exact format for all ten posts:

TITLE: [Target keyword, 50–60 characters]
SEARCH INTENT: [Informational/Commercial/Transactional]
TARGET AUDIENCE: [Specific person, specific problem]
KEY ANGLE: [Why this post is different from what's ranking]
OUTLINE:
1. [Main section 1]
2. [Main section 2]
3. [Main section 3]
4. [Main section 4]
5. [Main section 5]
KEY POINTS TO INCLUDE:
- [Specific fact, stat, or claim]
- [Specific fact, stat, or claim]
- [Specific fact, stat, or claim]
CTA: [What should the reader do after reading?]
TONE: [Your brand voice]
TARGET LENGTH: [1500–2500 words]

That's it. One page. No fluff.

Step 2: Fill in one brief as an example. Pick your easiest keyword (lowest difficulty, clearest angle). Fill in the template completely. This is your prototype. You'll use this to test your AI workflow in deliverable 4.

For example, if your keyword is "Python data validation for beginners," your brief might look like:

TITLE: Python Data Validation for Beginners: A Step-by-Step Guide
SEARCH INTENT: Informational (someone learning)
TARGET AUDIENCE: Junior Python developers who want to validate data without getting lost in framework complexity
KEY ANGLE: We show the simplest possible approach first, then show how to extend it. Most posts jump straight to complex patterns.
OUTLINE:
1. Why data validation matters (and why most tutorials skip this)
2. The simplest Python validation pattern (5 lines of code)
3. Validating different data types (strings, numbers, dates)
4. Common mistakes and how to avoid them
5. When to use a library vs. rolling your own
KEY POINTS TO INCLUDE:
- Data validation prevents 80% of production bugs
- Built-in Python tools are often enough; you don't need a library
- Schema validation and type hints are complementary
CTA: "Try this pattern on your next project. Share your experience in the comments."
TONE: Technical but approachable. No jargon without explanation. Assume the reader knows Python syntax but not validation patterns.
TARGET LENGTH: 2000 words

That brief took fifteen minutes. You now have a template and one filled-in example. You'll fill in the other nine briefs in deliverable 4.

Your deliverable: A Google Doc (or Notion, or whatever) with:

  1. The blank brief template
  2. One completed brief for your easiest keyword

Thirty minutes. Done.

Deliverable 4: AI Content Generation & First Edit (Days 3–4, 60 Minutes)

This is where the rubber meets the road. You're going to generate your first piece of content using AI, edit it, and publish it.

Most founders think AI content is unusable. It's not. It's unusable if you don't have a good brief. With a good brief, it's 70% of the way there. Your job is the final 30%.

Step 1: Choose your AI tool. You have options:

  • ChatGPT 4o — Best all-around. Understands nuance. Costs $20/month.
  • Claude 3.5 Sonnet — Best for technical content. Free tier exists.
  • Perplexity — Best for research-backed content. Free tier with limits.
  • Seoable — Generates 100 posts from your brief in 60 seconds, optimized for ranking. One-time $99 fee.

For this guide, we'll assume you're using ChatGPT or Claude. If you use Seoable, you skip to step 3 (editing).

Step 2: Generate your first post. Open ChatGPT or Claude. Paste this prompt:

You are an expert SEO content writer. Write a comprehensive blog post using this brief:

[Paste your completed brief here]

Requirements:
- 2000 words
- Include an H2 section for each outline point
- Use short paragraphs (2–3 sentences max)
- Include 5–10 internal links to relevant pages on our site
- Include 5–10 external links to authoritative sources
- Use active voice
- Include at least one numbered list and one bulleted list
- Write in the specified tone
- End with a clear CTA

Hit generate. Wait five minutes. You now have a draft.

Step 3: Edit for rankability. This is the critical step. You're not rewriting the whole thing. You're making five targeted edits that make it rankable.

Use the 5-minute editing system for AI posts:

  1. Title and meta description. Does the title include your keyword? Is it under 60 characters? Does the meta description include your keyword and call-to-action? Is it 150–160 characters? If not, rewrite.
  2. First paragraph. Does it answer the question in the title? Can a reader understand what this post is about in the first two sentences? If not, rewrite the first paragraph.
  3. H2 headers. Are they clear? Do they include related keywords? Are they scannable? If you have an H2 that's vague (like "Introduction" or "Overview"), replace it with something specific.
  4. Links. Are the internal links relevant? Do they make sense in context? Do the external links come from authoritative sources? If not, replace them. Aim for 5–10 of each.
  5. CTA. Is it clear? Does it tell the reader what to do next? If it's wishy-washy, rewrite it.

That's it. Five edits. Fifteen minutes of work. You're done.

Step 4: Add schema markup. Copy this schema template and add it to the bottom of your post (in HTML or using your CMS's custom code block):

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "[Your post title]",
  "description": "[Your meta description]",
  "author": {
    "@type": "Person",
    "name": "[Your name]"
  },
  "datePublished": "[Today's date in YYYY-MM-DD format]"
}
</script>

This tells Google what your post is and helps it understand the content better. Takes two minutes.

Step 5: Publish and submit to Google. Publish the post. Then go to Google Search Console, go to URL Inspection, paste your post URL, and click "Request Indexing." This tells Google to crawl your new post immediately instead of waiting.

Your deliverable: One published, indexed blog post with:

  1. Keyword in title and meta description
  2. Clear first paragraph
  3. Scannable H2 headers
  4. 5–10 internal links
  5. 5–10 external links
  6. Schema markup
  7. Submitted for indexing

You've now published one piece of content. Sixty minutes. Done.

Deliverable 5: Technical Fix (Day 5, 30 Minutes)

You identified technical issues in deliverable 1. Now you're going to fix one. Just one.

Pick the easiest win from your audit. Don't pick the most important. Pick the one you can fix in thirty minutes.

Common easy wins:

  • Add missing meta descriptions. If you have 20 pages with no meta description, write them. Takes five minutes per five pages. Pick your top 10 pages, write descriptions, save time.
  • Fix duplicate title tags. If two pages have the same title, change one. Takes two minutes per page.
  • Add missing H1 tags. If a page has no H1, add one. Takes two minutes per page.
  • Fix broken internal links. If you have links pointing to 404 pages, redirect them or replace them. Takes five minutes per link.
  • Add schema markup to your homepage. Use Schema.org's markup generator. Takes ten minutes.
  • Optimize Core Web Vitals. If your LCP is slow, compress your hero image. If CLS is bad, add explicit width/height to images. Takes fifteen minutes.

Pick one. Fix it. Submit the change to Google Search Console.

Don't try to fix everything. You'll burn out and ship nothing. One fix. One win. That's the move.

Your deliverable: One technical fix implemented and verified. That's it. Thirty minutes. Done.

Week 1 Recap: What You've Actually Shipped

You've shipped five things:

  1. Domain audit — You know what's broken and what's working.
  2. Keyword roadmap — You know what you're ranking for in the next 90 days.
  3. Content brief template — You have a repeatable system for writing rankable content.
  4. First published post — You've proven the system works.
  5. One technical fix — You've improved your site's health.

That's a week of work. Real work. Not planning. Not learning. Shipping.

You now have momentum. You have a system. You have proof that the system works.

Next week, you fill in the other nine content briefs, generate the other nine posts, and edit them using the same system. By the end of week two, you have ten pieces of content live.

By the end of week four, you have ten pieces of content indexed and starting to get impressions.

By the end of week twelve, you have thirty pieces of content, and some of them are ranking.

That's how this works. Not overnight. Not magic. Compounding work.

Pro Tips for Week 1 Success

Tip 1: Use your actual product as your content angle. The best angle is the one nobody else has: your unique implementation, your specific use case, your exact workflow. Don't write generic posts. Write posts that only you can write because you built the thing.

Tip 2: Publish on a schedule. Don't publish all ten posts at once. Publish one per week for ten weeks. This tells Google you're active. It gives each post time to get indexed and start getting impressions before the next one comes out. It's also way less work each week.

Tip 3: Link your posts together. If post 2 is about a concept mentioned in post 1, link to post 1 from post 2. If post 3 builds on post 1 and 2, link to both. This builds topical authority and tells Google these posts are related. Learn more about building topical authority clusters for sustained ranking power.

Tip 4: Don't obsess over perfection. Your first post won't be perfect. That's fine. Publish it. Get feedback. Improve next week. Shipping beats perfection every single time.

Tip 5: Track your baseline. Take a screenshot of your Google Search Console Performance data right now. In week 4, take another screenshot. You'll see impressions going up. That's your proof that this works.

Common Mistakes Founders Make in Week 1

Mistake 1: Trying to fix everything. Your audit found 47 issues. You can't fix 47 issues in week one. Pick one. Ship it. Come back to the others next month.

Mistake 2: Targeting too many keywords. You think more keywords = more traffic. Wrong. Ten keywords you can rank for beats 100 keywords you can't. Focus.

Mistake 3: Writing generic content. You write about your topic the way everyone else does. You don't stand out. Use your unique angle. Show your work. Share your specific implementation. That's what ranks.

Mistake 4: Forgetting the CTA. You write a great post. Nobody knows what to do next. Add a clear call-to-action. "Read our documentation." "Try this in your project." "Sign up for our beta." Something.

Mistake 5: Not submitting for indexing. You publish a post and wait for Google to find it. Don't wait. Go to Search Console and request indexing. Saves you a week.

The Path Forward: What Week 2 Looks Like

You've shipped week one. You have five deliverables done. Now what?

Week two is the same thing, scaled. You fill in the other nine content briefs (one per day, takes ten minutes per brief). You generate and edit those nine posts (one per day, takes thirty minutes per post). You publish them on a schedule (one per week for nine weeks).

You also start monitoring. Every day, spend five minutes in Google Search Console looking at your search performance. Are you getting impressions? Are you getting clicks? Which posts are getting traction? Which ones are flopping? Use that data to improve.

For a deeper dive into the entire 100-day SEO playbook, check out the full founder's SEO onboarding guide and your first 100 days of SEO.

You can also accelerate week one by using a service like Seoable, which delivers a domain audit, keyword roadmap, content briefs, and 100 AI-generated blog posts in under 60 seconds for a one-time $99 fee. This compresses week one into an hour and gives you a month's worth of content to edit and publish. Many technical founders use this approach to skip expensive agency audits and get straight to shipping.

If you want to understand the deeper concepts behind what you're shipping, read the 12 SEO concepts every founder needs to know. If you want to understand what a $99 SEO investment actually delivers, read the $99 SEO question.

Final Word: Ship, Don't Plan

SEO is not a mystery. It's not magic. It's:

  1. Know what you're ranking for (keyword roadmap)
  2. Write better content than what's ranking (content brief + editing)
  3. Make sure Google can find it (technical fixes + indexing)
  4. Repeat

Week one is about proving to yourself that you can do this without an agency, without a huge budget, without months of planning.

You can. Ship these five deliverables. You'll have proof.

Then ship week two. Then week three. By week twelve, you'll have organic traffic. By week twenty-four, you'll have real revenue from organic search.

It's not fast. It's not flashy. But it works. And it's yours.

Start today.

§ The Dispatch

Get the next
dispatch on Monday.

One email per week with the most important SEO and AEO moves for founders. Unsubscribe in one click.

Free · Weekly · Unsubscribe anytime