Static websites built for search
A static website is a folder of finished HTML files. Nothing runs when a visitor arrives, so pages load fast, nothing can be hacked through a login screen, and hosting costs next to nothing. I build them with Claude Code, Anthropic's AI coding assistant, and every build has to pass the same SEO checks I'd run on a client's site before it can publish.
Proof you're reading
This site is one. It's hand written HTML, a small Python generator, GitHub Pages, and Cloudflare, described on the colophon. The build refuses to publish a page whose title or description is the wrong length, repeats another page, or borrows phrasing from elsewhere. Those rules live in code, so they hold on the hundredth page the same as the first.
What every site gets
- Titles, descriptions, and headings checked on every build, with one H1 per page and no duplicates.
- Structured data for the person or business behind the site, breadcrumbs, and the right type for each page.
- Open Graph and X card tags with a correctly sized share image for every page.
- A sitemap, robots.txt, and llms.txt, with AI crawlers allowed unless you say otherwise.
- Accessible markup and colors, tested in a text browser, because what a screen reader can follow a crawler can follow.
- Speed: no page builder, no unused scripts, images sized for the screen.
Leaving WordPress
Plenty of WordPress sites are brochures that change a few times a year, paying for a database, a stack of plugins, and constant security updates to publish pages that never change. For those sites I move the content to static pages, keep every URL or redirect it with a 301, carry over titles and descriptions, and check rankings after launch. The method is the same one I use for any site migration.
WordPress stays the right choice when a site needs logins, a store, comments, or a team publishing daily through an editor. For those, I make WordPress fast and sound instead; see WordPress SEO.
Editing after launch
Content lives in plain files in a Git repository you own. You can edit a page on GitHub in the browser, ask me to make changes, or describe a change to an AI coding assistant and review what it writes. Every edit is recorded, and any mistake can be rolled back in a minute. More on why that matters for SEO is in why your SEO should work in your Git repository.
Built for podcasts, too
A podcast feed is a natural source for a static site, with a page per episode added automatically. That's its own service: podcast website SEO.
How it's delivered
A fixed-scope build quoted after a short call, or a migration scoped from an inventory of your current site. Terms are on Hire Me.
Updated