How to Build an SEO Strategy Document That Actually Works (With a Real Example)
17 min read
By Andrew Blase
An SEO strategy document is a single source of truth that defines what your brand is, who you're targeting, what queries you're going after, how your site is structured, and how you'll create and distribute content to rank - and get cited by AI systems. Without one, you're guessing. With one, every article you publish compounds.
Most SEO advice gives you tactics. Keyword research. Backlink outreach. Meta tag checklists. But no one hands you the architecture - the strategy document that ties all of it together before you write a word.
This is that document. Not explained in abstract - we'll show you exactly how Full Stack Data Solutions built theirs, using the framework from Will Cannon's SEO Playbook at iamwillcannon.com/free-resources.
Your job isn't another article. It's an engine. Here's how to build yours.
Google doesn't just read your pages. It builds a model of what you are. If that model is fuzzy, your rankings are inconsistent. If it's sharp, Google surfaces you for everything in your territory.
Entity definition is the process of telling Google exactly what your brand does, who it serves, and why it matters, with enough consistency across your site that Google can't misread it.
For Full Stack Data Solutions, that definition is:
Full Stack Data Solutions helps tech workers and solo founders build profitable SaaS businesses using AI, GraphQL, and modern automation stacks.
Every page on the FSDS site reinforces this. The homepage states it. The About page expands it. Every pillar page connects to one of its core terms, AI tools, solo founding, GraphQL, career escape.
Consistency is the variable. One clean sentence, everywhere.
Your audience's search intent isn't what you think they care about, it's what they type when they're frustrated, curious, or actively solving a problem.
FSDS is built for tech workers and aspiring solo founders. These people search for:
That last one matters. It's not just a curiosity search. It's a fear search. People who search "how to build income outside your tech job" have context: a layoff, a close call, a colleague who got let go. Content that meets that search with hard truth converts.
Old SEO: one article per keyword.
Modern SEO: one article per query set, the cluster of related queries Google serves the same URL for.
FSDS is built around four topic hubs, each anchored by a pillar page:
Pillar: "How to Build a SaaS as a Solo Developer: The Complete Guide"
Query set: solo founder AI business, how to build a SaaS as a solo developer, technical founder marketing, indie hacker tips, solopreneur SaaS guide
Pillar: "Best AI Tools for Solo Developers and Indie Founders"
Query set: AI tools for developers, automate your side project, AI-powered SaaS, solo founder automation stack, AI coding assistant for indie hackers
Pillar: "GraphQL Best Practices: The Definitive Developer Guide"
Query set: GraphQL best practices, GraphQL vs REST, GraphQL schema design, WunderGraph / Cosmo tutorials, GraphQL for SaaS
Pillar: "How to Build Income Outside Your Tech Job (Before the Layoffs)"
Query set: tech layoffs survival, build income outside your job, developer side income, software engineer business ideas, programmer passive income
The rule is simple: if Google shows the same articles for two queries, they belong on one URL. You don't get extra credit for creating separate pages, you dilute your own authority.
How to find your query sets: Ahrefs Keywords Explorer -> search your main topic -> click "Clusters by Parent Topic." One URL per cluster.
Google rewards topical authority. You build topical authority by creating complete coverage of a topic, not by writing isolated articles.
The hub-and-spoke model:
Pillar Page (Hub)
├── Cluster Page: Specific Subtopic
├── Cluster Page: Tool/Tutorial
├── Cluster Page: Comparison
└── Support: FAQs, Checklists, Quick Guides
Every cluster page links to its pillar. Every pillar links back to all clusters. This closed loop signals to Google: this site owns this topic.
| Bad | Good |
|---|---|
fsds.com/post/12345/how-to-build-a-saas | fsds.com/solo-saas-guide |
Short, descriptive, keyword-focused. Every URL tells Google what the page covers. No dates. No post numbers. No category folders that add nothing.
Rankings are a function of relevance AND technical performance. You can have the best content on the internet and still lose to a faster, cleaner page.
Your LCP (Largest Contentful Paint) target is 2.5 seconds. The FSDS approach:
fetchpriority=high and a <link rel="preload"> tag.Every image under 100KB. No exceptions. Use TinyPNG or Squoosh before uploading.
Alt text that includes the target keyword naturally:
alt="screenshot-1.png"alt="Solo founder SaaS dashboard showing MRR and churn metrics"Meta titles describe, they don't sell. Put the CTA in the description.
"23 AI Tools for Solo Developers to Ship Faster in 2025", clear, specific, keyword-forward"Looking for AI tools that actually work for solo devs? Here are 23 tested tools that help indie founders automate, build, and ship, without a team."Set og:title intentionally. Google sometimes pulls it instead of your title tag.
Use JSON-LD for entity information on pillar pages. Add FAQ schema to every article's mini-FAQ section, this increases AIO eligibility significantly.
Here's the uncomfortable truth: if your content isn't structured for AI systems, you don't exist in AI search.
Google's AI Overviews. ChatGPT. Claude. Perplexity. They all pull from the same underlying principle: well-structured, clearly attributed, question-answering content gets cited. Rambling paragraphs don't.
Kevin Indig's research on 546,000 AI Overviews found that content using a specific heading hierarchy was cited 40% more often. FSDS implements it on every article:
H1: Article title
H2: Direct Answer (2-3 sentences answering the main query immediately)
H2: What is [main topic]?
H2: Most relevant question from query set
H2: Follow-up questions based on query fan-out
...
H2: FAQs
H3: FAQ question 1
H3: FAQ question 2
H3: FAQ question 3
H2: Conclusion
Marie Haynes' research shows "fact-checkable snippets" dramatically increase AI citation rates. The formula:
Google converts your headlines to questions internally. Beat it to the punch:
Not every article serves the same purpose. Your content map assigns every piece a role in the funnel.
Goal: capture people who don't know you yet and are educating themselves.
Process:
FSDS TOFU examples:
Goal: capture people who are evaluating options.
The listicle formula:
FSDS MOFU examples:
Goal: capture people close to a decision.
Three BOFU content types:
Comparison/Vs: "GraphQL vs REST: Which Should You Use for Your SaaS?"
Alternatives: "15 Best Alternatives to [Major Tool] for Solo Developers"
Brand vs Competitor: "[Competitor] Pricing 2025: Is It Worth It for Solo Founders?"
People researching competitor pricing are close to a decision. BOFU content drives the highest-converting organic traffic. FSDS prioritizes it in the content calendar.
Publishing is not a one-time event. The difference between sites that plateau and sites that compound is a systematic update process.
| Content Type | Update Frequency |
|---|---|
| BOFU (comparisons, alternatives) | Every 3 months |
| MOFU (tool lists, how-tos) | Every 6 months |
| TOFU (educational guides) | Every 12 months |
Use this ChatGPT prompt before updating any article:
"I'm updating an article about [TOPIC] originally published in [DATE]. Identify what factual info, statistics, or industry developments might be outdated. Focus on: key stats that change annually, software features/pricing, industry trends, regulatory changes, new research."
Use this ChatGPT prompt:
"I have an article about [MAIN TOPIC] covering these sections: [LIST H2 HEADINGS]. Identify important subtopics I'm missing. Review SERP competitors, identify related questions users ask, suggest emerging trends, recommend case studies or examples to add."
Updates that address all three dimensions can move a page from position 12 to position 4 without a single new backlink.
Internal links do two things: they send PageRank from established pages to new ones, and they signal to Google which pages are most important in a topic cluster.
One sprint. Then make it part of the publishing checklist for every new article.
FSDS link building focuses on three page types:
Build relationships before you ask for links. Communities relevant to FSDS:
Join. Add value. The links follow.
Link insertions, adding your link to existing articles on another site, often outperform guest posts. They're faster, have higher response rates, and the page already ranks.
FSDS reciprocation policy: when someone links to FSDS, link back from relevant content, share their article in the newsletter, and feature them in future roundups.
Respond within 2 hours. Most journalists pick from the first 10 responses. Include one stat they can cite. Never pitch, provide value.
AI systems increasingly cite Reddit and forum discussions as "real user opinions." Active participation in r/SaaS, r/IndieHackers, and r/entrepreneur, with helpful responses that mention FSDS when relevant, builds citations in AI search results.
Publishing articles without funnels is a branding exercise. You want a pipeline.
Articles -> Lead Magnet CTA -> Beehiiv opt-in -> Mautic nurture sequence
Newsletter value sequence:
Search is changing. The user behavior shift: instead of researching across multiple sources, people get one comprehensive answer from an AI system. Your goal is to be that answer.
Google AI Overviews. ChatGPT. Claude. Perplexity. They all cite from the same pool: authoritative, consistently structured, frequently updated content from brands with clear entity definitions.
Traditional (still important): organic traffic, keyword rankings, conversion rate, backlinks.
New and increasingly important:
Tracking tools: ZipTie, Profound, or Peec AI for AIO tracking; SE Ranking AIO Tracker; Google Search Console for featured snippets.
| Purpose | Tool |
|---|---|
| Keyword research and competitor analysis | Ahrefs |
| Content optimization and briefs | Surfer SEO |
| Search performance and indexing | Google Search Console |
| Analytics | Google Analytics |
| Content planning | Notion |
| Writing | Google Docs + Surfer integration |
| AI Overview tracking | ZipTie / Peec AI |
| Email marketing | Beehiiv (opt-in) + Mautic (nurture) |
The FSDS weekly publishing rhythm:
| Day | Activity |
|---|---|
| Monday | Draft week's article + queue social posts + trending research |
| Tuesday | LinkedIn + X posts live |
| Wednesday | LinkedIn + X posts live |
| Thursday | Article publishes -> Reddit + Medium repost auto-triggers |
| Friday | LinkedIn + X posts live |
| Saturday | LinkedIn + X posts live |
| Sunday | Weekly newsletter sends (Beehiiv) |
One article per week. Five social posts. One newsletter. That's 52 articles, 260 social posts, and 52 newsletters per year, from one engine running one hub at a time.
An SEO strategy document is a single reference that defines your entity, target audience search intent, keyword clusters, site architecture, technical requirements, content structure, and distribution plan. It's the strategic layer before any individual article gets written, the document that makes every piece of content a deliberate move rather than a guess.
Most SEO timelines are 3-6 months before meaningful traffic movement, 6-12 months before strong rankings across a topic cluster. The entities and technical foundation you set up in the first 30 days do the compounding work over the following year. The sites that win are the ones that don't quit at month four when rankings are still building.
No. Start where the leverage is highest for your current stage. If you have no entity definition, start there. If you have content but no internal links, run the linking sprint. The strategy document is a reference system, you build it in priority order, not all at once.
Most founders skip the strategy document and jump straight to publishing. They end up with 20 articles about tangentially related topics, no clear topical authority, no funnel, and no compounding.
Build the document first. Define your entity. Map your query sets. Architect your hubs. Optimize for AI systems from day one. Then write.
The content won't feel faster in month one. It'll feel much faster in month six, when each article you publish lands in an established structure that Google already respects.
Ready to build your content engine? Full Stack Data Solutions helps solo founders and technical builders put the strategy behind the content. Start at fullstackdatasolutions.com.
Sources: