SEO Playbook for Startups

SEO pays a startup when buyers already search for the problem, the old way or the alternatives, and a customer is worth enough to wait months for. Model the payback before you spend, score phrases on how close the searcher is to buying and how fully you answer them, and build the pages a buyer reads just before choosing: product, comparison, use-case and integration pages first, thought leadership last. Keep Google able to fetch and index every page, earn links honestly, and judge the work each month on pipeline, not traffic.

Founders usually ask me for “more blog posts”. In my view, that is where most early SEO money goes to waste, because the pages that pay back first are the plain ones: what the product does, how it compares, whether it fits a team like mine and whether it works with what I already run. They rank on small searches a young domain can win, and sales can send the same pages to prospects.

This playbook is the long-term system: the money question, the keyword choice, the page plan, the technical checks, the writing, the links and the monthly review. When to start and the first afternoon of basics are in SEO for Startups, and the terms SEO, GEO and AEO are explained in How to Get Found Online. Being cited in AI answers has its own playbook, the GEO & AEO Playbook; this one is classic organic search.

SEO fits when three things hold. Buyers search for your problem, the way they do the job today or the tools they could switch from, in words you can name; a customer brings enough gross profit to be worth waiting months for; and your runway outlasts the wait. If your category is so new that nobody searches for it, write only the few pages near a purchase and put the rest of the budget into outbound or partners.

Nobody can promise you a date. Google’s own page on hiring an SEO says “No one can guarantee a #1 ranking on Google”^[1]. So write your own model, label every assumption, and replace each one with real numbers as Search Console starts to report them.

The model needs five inputs: pages a month and their cost, visits a page draws once it ranks and the months before it does, the share of visits that ask for a demo, your close rate, and gross profit per customer a month. Add up cost and gross profit month by month; the program pays back in the month the second catches the first (Figure 1). Then halve the visits and run it again, because that is the number you know least.

My rule of thumb, not a benchmark: if the plan pays back inside your runway only when the visits arrive in full, set a checkpoint before you start. Name the month, the share of planned visits you must reach by then, and where the money goes if you miss it.

SEO for Startups covers where the phrases come from: sales calls, demo requests and support tickets first, then Search Console, then a keyword tool. This step puts that list in order. Score every phrase twice, from 1 to 10: intent, meaning how close the searcher is to buying, and fit, meaning how fully your product answers it.

Intent follows the buying journey. Someone searching for an alternative to a tool, an integration or your kind of product for a specific job is choosing; someone searching for a definition is learning. I judge it from what already ranks: product and comparison pages on the first page of results mean a buyer, guides mean a learner.

Fit stops you chasing traffic you can’t convert. A phrase can sit close to a purchase and still be wrong for you, such as a consumer searching for a free app when you sell to sales teams. Write first for the phrases high on both (Figure 2); those high on fit but early in the journey become the cluster in Step 3, and the rest wait or go.

Then use the buyer’s words on the page. Google’s Search Essentials advises using the words people would use to look for your content, in prominent places such as the title and main heading^[2]. Once pages are indexed, the Queries tab of the Performance report in Search Console shows the phrases that actually found you^[3]; score the new ones each month.

Write in this order: product pages, comparison pages, use-case pages, integration pages, problem pages, and thought leadership last. In my view, this order matters more at seed than any other SEO decision. The early pages convert, they rank on searches small enough for a young domain, and your sales team can use them on the next call.

Each type answers one buying question. A product page says what it does and what it costs; a comparison page sets you honestly against the old way or a named tool; a use-case page shows a team like the reader’s; an integration page confirms it works with what they run; a problem page explains how to fix the pain. Give each page one phrase from Step 2, and each phrase one page.

Integration and use-case pages tempt founders to stamp out near-copies with a name swapped. Google’s spam policies define doorway abuse as “when sites or pages are created to rank for specific, similar search queries”^[4]. Write a page only where you have something specific to say, and before any templated build, check whether it pays back with the Programmatic SEO skill listed under “Use with this playbook”.

Link the pages together as you publish. Google’s link guidance says “every page you care about should have a link from at least one other page on your site”, with anchor text that is “descriptive, reasonably concise, and relevant”^[5]. Producing the pages on a calendar, with briefs and an owner for each, is covered in the Content Creation Playbook.

A page Google can’t fetch, render or pick as the canonical won’t rank, however good it is. Meeting Google’s requirements “doesn’t mean that Google will crawl, index, or serve” a page^[2], but missing them means it can’t. Four things break as a site grows: rendering, sitemaps, canonicals and speed. Check them in the order Google meets them (Figure 4).

Rendering

Google processes JavaScript pages in three phases, crawling, rendering and indexing, and calls server-side rendering or prerendering “still a great idea” because “not all bots can run JavaScript”^[6]. It finds links only when they are <a> elements with an href, so a menu built from click handlers hides the pages behind it. URL Inspection in Search Console shows a screenshot and the HTML of the page as Google’s tool renders it^[7]; AI crawlers are stricter, and the GEO & AEO Playbook covers them.

Sitemaps and canonicals

List only the full addresses you want in search results. A sitemap holds up to 50,000 URLs or 50MB, and Google uses the lastmod date only when it is “consistently and verifiably” accurate and ignores priority and changefreq^[8]. When one page lives at several addresses, a redirect or a rel="canonical" link is a strong signal and sitemap inclusion a weak one, and Google says not to use robots.txt for canonicalization^[9].

Don’t chase a fully indexed site. The Page indexing report says “You should not expect all URLs on your site to be indexed, only the canonical pages”^[10]. What matters is that the pages from Step 3 are among them.

Speed

web.dev sets the good thresholds for Core Web Vitals: the largest content appears within 2.5 seconds, the page responds to input within 200 milliseconds, and the layout shifts by 0.1 or less, measured at the 75th percentile of page loads, mobile and desktop separately^[11]. Fix a page that is far off. How much weight speed deserves next to content is in SEO for Startups.

A page ranks and converts when it finishes the job the search started. Google’s helpful-content guidance asks: “After reading your content, will someone leave feeling they’ve learned enough about a topic to help achieve their goal?” It also asks whether the content provides “original information, reporting, research, or analysis”^[12].

For a page close to a purchase, that means five parts: the answer first, the facts side by side in text, who it isn’t for, one proof point a reader could check, and one next step (Figure 5). Length follows the question, not a target. Google’s starter guide says “The length of the content alone doesn’t matter for ranking purposes”^[13].

Write the title and description for the person searching. Google describes a good title as “unique to the page, clear and concise”, and a good meta description as “short, unique to one particular page” and including “the most relevant points of the page”^[13]. Brief every page before anyone writes it: the free Content Brief Builder reads the intent from what ranks, drafts the answer block and checks that the new page won’t compete with one you already have.

Write from what only your team knows: the objections you hear on calls, your product’s real limits, numbers from your own system. In my view, a page without one of those adds nothing a buyer can’t find on a competitor’s site.

Links do two jobs: they help Google find your pages, and they show that other sites vouch for them. Google’s starter guide says “Google primarily finds pages through links from other pages it already crawled”^[13]. For a seed company, the honest sources are close at hand (Figure 6).

Start with the links you are owed: every integration partner’s directory, every marketplace that lists you, every customer who writes about how their team works. Then make one asset that others want to cite, such as an original data study with its method on the page. Pitching it is covered in the Earned Media Playbook, and pages with partners in the Partner Co-Marketing Playbook.

Google’s spam policies define link spam as “the practice of creating links to or from a site primarily for the purpose of manipulating search rankings”, and name buying links, excessive link exchanges and keyword-rich links in guest posts^[4]. If you pay for a placement, mark the link rel="sponsored", which Google reserves for “advertisements or paid placements”^[14].

My rule of thumb, not a benchmark: count the new sites that linked to you this quarter because they chose to, and ignore any tool’s authority score. One relevant partner directory is worth more than twenty posts on sites your buyers never read.

Search Console sees SEO working before your analytics do. Its Performance report counts clicks, “the number of times a user clicked your site from Google Search results”, impressions, “how many times your site appeared in Search results”, and click-through rate, “the click count divided by the impression count”^[3]. Filter it to the pages you built in Step 3, because searches for your own name hide everything else.

Then follow the visit to money. Record each demo request’s landing page, and add an open “How did you hear about us?” field, so every demo, opportunity and customer from search is counted with its value. Setting up the analytics is covered in Tracking Setup with GA4 and UTMs, and crediting channels in the Analytics & Attribution Playbook.

Review once a month, for 30 minutes, with one owner and one sheet: the plan beside the actual, and no more than three decisions (Figure 8). Look for pages with many impressions and few clicks, which need a better title, and queries nobody planned for, which need a page. A request in URL Inspection can speed up one page, but “Submitting a request does not guarantee that the page will appear in the Google Index”, and there is a daily limit^[7].

Judge the program at the checkpoint you set in Step 1, not on one bad month. The first three months show almost nothing in traffic (Figure 7), and visibility in Google’s AI features is measured separately, as the GEO & AEO Playbook explains.

What changes by stage?

What mistakes should I avoid?

• Spending without a payback model or a checkpoint. You can’t tell a slow start from a failed one (Step 1).
• Choosing phrases by search volume. Intent and fit decide what converts (Step 2).
• Starting with thought leadership. The pages buyers read just before choosing come first (Step 3).
• Stamping out near-identical pages with a name swapped. Google calls it doorway abuse (Step 3).
• Menus that aren’t real links, and sitemaps full of login pages. Google can’t index what it can’t find (Step 4).
• Writing to a word count. Write to the question (Step 5).
• Buying links or guest-post packages. Google names both as link spam (Step 6).
• Reporting traffic for the whole site. Report pipeline from the pages you built (Step 7).