Static Site SEO Handbook: Rank Without a CMS

June 19, 2026 · 21 min read · Pillar Guide

Static sites are SEO-friendly by default: fast HTML, no database timeouts, small attack surface. They are also easy to get wrong because nobody installs an SEO plugin to nag you. You hand-write meta tags once, forget sitemap.xml, and wonder why Google shows a blank description. This handbook covers technical SEO for indie static landers and small content sites—sitemap, robots, schema, CWV, and internal linking—without enterprise tooling.

How search engines see your static site

Crawlers fetch URLs, parse HTML, follow links, and index what they can render. Static HTML is ideal: content is in the response, not behind client-side routing that delays paint. JavaScript-heavy SPAs without prerender still rank, but slower and flakier. For marketing pages, ship real HTML files per URL.

• Each important URL returns 200 with unique title and description
• Canonical tag points to preferred URL version
• Internal links use normal anchor hrefs crawlers can follow
• Noindex only on thank-you, staging, or duplicate thin pages
• HTTPS everywhere; redirects consolidate www/apex

Essential meta tags on every page

Title: primary keyword near front, brand at end, under 60 characters displayed. Meta description: compelling summary, not keyword stuffing, 150–160 characters. One H1 matching search intent. Open Graph and Twitter tags for share previews—social clicks indirectly support discovery even if not ranking factors.

<title>Waitlist Landing Page Template — LaunchStatic</title>
<meta name="description" content="Deploy-ready waitlist page for indie hackers. Fast HTML, form-ready, mobile-first.">
<link rel="canonical" href="https://launchstatic.dev/templates/waitlist.html">
<meta property="og:title" content="Waitlist Landing Page Template">
<meta property="og:description" content="Ship a waitlist page this afternoon.">
<meta property="og:image" content="https://launchstatic.dev/assets/img/og/waitlist.png">
<meta name="twitter:card" content="summary_large_image">

robots.txt and crawl budget

At indie scale, crawl budget is rarely the bottleneck—indexation and relevance are. Still, robots.txt should allow public content and point to sitemap. Do not block CSS/JS; Google needs them to render. Staging previews on pages.dev can use noindex meta or HTTP auth; do not leak duplicate content on indexable URLs.

User-agent: *
Allow: /
Sitemap: https://launchstatic.dev/sitemap.xml

sitemap.xml that stays current

List canonical URLs you want indexed. Omit noindex pages, redirects, and 404s. Include lastmod if you maintain it—honest dates help recrawl after updates. For ten-page sites, hand-maintain sitemap. For blogs, generate at build time with your SSG or a small script in CI.

1. Homepage, key landing pages, guides, templates index
2. Legal pages optional; low priority
3. Submit sitemap in Google Search Console and Bing Webmaster Tools
4. Regenerate sitemap when adding routes; redeploy same commit
5. Keep under 50,000 URLs—irrelevant for indies but good habit

Structured data (schema.org)

JSON-LD in script tags is the cleanest for static sites. Article schema for guides; FAQPage for FAQ sections; Organization on homepage; WebSite with SearchAction only if you have on-site search. Validate with Google Rich Results Test after deploy—not just locally.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Static Site SEO Handbook",
  "description": "SEO for static landing pages.",
  "author": {"@type": "Organization", "name": "LaunchStatic"},
  "datePublished": "2026-06-19",
  "mainEntityOfPage": "https://launchstatic.dev/guides/static-site-seo-handbook.html"
}
</script>

FAQ schema can yield rich snippets; questions must appear on page verbatim. Do not mark up invisible content. BreadcrumbList helps sitelinks clarity in some cases—match visible breadcrumb nav.

URL structure and information architecture

Readable paths beat opaque IDs: /guides/waitlist-conversion-playbook.html beats /p?id=17. Keep folders shallow. Trailing slash consistency matters—pick one via redirects. Use hyphens in filenames. Lowercase only.

Internal linking strategy

Static sites lack sidebar widgets unless you build them. Plan links in content: every guide links to two related guides, one template, one tool. Hub pages (/guides/, /templates/) list children with descriptive anchor text—not "click here." Footer links repeat key hubs. Internal links distribute authority and help discovery without sitemap alone.

• Each new page linked from at least one existing indexed page
• Anchor text describes destination (waitlist template, not read more)
• Orphan pages audit quarterly—Search Console coverage report
• Related links block at end of articles
• Breadcrumb nav matches URL hierarchy

Core Web Vitals on static HTML

LCP (Largest Contentful Paint): optimize hero image dimensions and priority hint. INP (Interaction to Next Paint): minimize main-thread JS on form pages. CLS (Cumulative Layout Shift): width/height on images, reserve space for web fonts, avoid injecting banners above content late.

• LCP: preload hero WebP; serve from CDN; avoid lazy-load on LCP image
• INP: defer third-party scripts; small inline handlers only
• CLS: font-display swap with metric-matched fallbacks
• TTFB: Cloudflare caching; HTML not over-cached during copy tests
• Measure field data in Search Console CWV report after traffic exists

Content that earns links and rankings

Technical SEO gets you indexed; content gets you ranked. For indies, long-tail guides that solve one problem completely outperform thin "best tools 2026" listicles. Original screenshots, step-by-step deploy commands, and checklists attract links from forums. Update posts when APIs change—lastmod in sitemap signals freshness.

International and duplicate content

If you ship /en/ and root English duplicate, canonical one version. hreflang only when you have real translations—not machine spam. Parameterized URLs for UTM are fine; canonical without params on marketing pages.

Google Search Console workflow

1. Verify domain property via DNS TXT
2. Submit sitemap.xml
3. Inspect URL after major copy deploy; request indexing sparingly
4. Monitor Coverage and Page Experience reports monthly
5. Fix soft 404s—pages with little content that return 200
6. Review queries report for unexpected keywords to support with content

Bing and secondary engines

Bing Webmaster Tools import from GSC in minutes. DuckDuckGo uses Bing index. Neglecting Bing costs little traffic in US/EU SaaS but setup is ten minutes—worth it.

Local SEO if relevant

Local service SaaS needs NAP consistency, Google Business Profile, and LocalBusiness schema. Pure global B2B tools skip local schema—do not fake addresses.

SEO mistakes on static landers

• Identical title/description on every page
• Missing canonical when syndicating same kit to multiple paths
• Blocking entire site in staging robots.txt copied to production
• Huge unoptimized PNG heroes crushing LCP
• No analytics on which landing URLs convert—SEO without conversion feedback
• Buying links or AI mass pages—short-term poison

Maintenance calendar

Monthly: broken link check, Search Console errors, dependency bumps for build. Quarterly: refresh top guide stats and screenshots, internal link audit, CWV lab test. At launch: full technical pass; after that, SEO is incremental—not a one-week project.

Static SEO is discipline, not plugins. Ship clean HTML, keep sitemap honest, write one great page per intent, and let speed work in your favor while bigger competitors load analytics suites.

Image SEO and media

Name files descriptively: waitlist-hero-dashboard.webp not IMG_8842.png. Write alt text describing the image function, not keyword dumps. Use picture element for WebP with fallback. Host large PDFs with clear link text; optional PDF schema only if you invest in maintaining metadata.

Pagination and archive pages

Blog indexes listing ten posts per page need rel=next/prev or a single view-all if small. Avoid infinite scroll without crawlable links—bots may not see deep posts. Static generators often handle this; plain HTML bloggers should add manual next links.

Monitoring rankings without obsession

Track five to ten target queries in Search Console, not third-party rank trackers daily. Month-over-month impression growth on intended queries matters more than position three vs five. Note SERP feature changes—FAQ rich results, AI overviews— and adapt content format when clicks shift.

Security headers and SEO

Headers do not directly rank you, but HSTS and CSP reduce compromise risk that nukes trust if site gets defaced. After adding strict CSP, test forms and analytics in staging—broken scripts do not hurt rankings but hurt conversions you measure from organic.

# Example CSP snippet—tune per your embeds
Content-Security-Policy: default-src 'self'; script-src 'self' plausible.io; style-src 'self' 'unsafe-inline'; img-src 'self' data: https:; form-action 'self' https://formspree.io

Launch checklist: technical SEO

• Unique title and meta description per URL
• Canonical matches live primary domain
• sitemap.xml submitted and fetchable
• robots.txt allows CSS/JS and points to sitemap
• JSON-LD validates without errors
• Mobile-friendly test passes
• No accidental noindex on production
• 404 returns proper status, not soft redirect to home
• Internal links from home to money pages
• OG image returns 200 and correct dimensions

Revisit this checklist after every major IA change—adding /guides/, splitting templates, or migrating hosts. Static sites make diffs obvious in git; use that audit trail when rankings wobble after a refactor.

Programmatic pages without spam

Indies sometimes generate location or integration pages from JSON at build time. That is fine when each page has unique utility—setup steps for that integration—not 200 near-duplicate paragraphs. Cap programmatic pages at what you can maintain. One excellent /integrations/linear.html beats fifty thin stubs.

Page speed budgets

Set a budget: HTML under 50 KB, total page weight under 500 KB on landing, requests under 30 on first load. Measure in WebPageTest from a mobile profile quarterly. Exceeding budget triggers a trim sprint—drop a font weight, compress hero, remove an embed—not a redesign.

Fixing indexation drops

If indexed pages fall suddenly, check robots.txt deploy, accidental noindex meta, 5xx during crawl, or domain migration without redirects. Search Console URL Inspection shows live Google view. Keep old URLs 301ing for at least a year after migrations; static sites make redirect maps easy in _redirects.

1. Compare sitemap URL count to indexed count monthly
2. Fetch robots.txt in browser after each production deploy
3. Run site:yourdomain.com monthly for obvious omissions
4. Fix broken internal links found in Screaming Frog free tier crawl
5. Add contextual links from high-traffic posts to new guides

SEO for static indies is a slow compounding channel alongside community launch. Technical hygiene keeps the door open; useful guides and templates bring visitors who actually sign up. Pair this handbook with conversion work on the same URLs—rankings without signups is a hobby, not distribution.

When you add new guides under /guides/, update the hub page HTML and sitemap the same commit. Hub pages pass internal PageRank to leaf articles; orphan guides without hub links can lag indexation for weeks on new domains.

Track organic landing URLs in the same spreadsheet as waitlist conversion. A guide ranking on page one with 0.5% signup rate needs a stronger CTA block, not more backlinks. SEO and conversion optimization on static sites share the same HTML files—treat them as one system.

Prefer stable URLs when updating titles. A renamed filename without 301 loses accumulated signals. Edit in place when possible; redirect old paths when you must restructure. Static repos make filename churn tempting—resist for any URL that already earned impressions in Search Console.

Add last-updated visible dates on guides when facts change. Users and crawlers both reward maintained references; stale year references in titles erode click-through without you noticing.

Related: Landing page playbook Cloudflare Pages guide How-to articles SEO tools Templates index