Being found
Technical SEO
We handle the half of SEO that lives in the code. Done properly, it stops being something you think about.
SEO splits into two halves. One is content and reputation: what you publish, who links to you, what people say about you elsewhere. The other is technical: can a crawler reach every page, understand what it is about, and load it quickly enough to bother.
We do the technical half, and we build it in from the start rather than bolting it on. A site that ships with correct titles, clean URLs, working structured data and a real sitemap has no catching up to do.
We also set up the parts that feed AI answers. Structured data, direct answers near the top of a page, and a robots file that names the AI crawlers explicitly instead of hoping the wildcard covers them.
What the work covers
Included in every technical seo project.
Titles and descriptions per page
Unique, under sixty characters for titles, and descriptions written to be read rather than stuffed. Checked in the built HTML, since the brand suffix is applied at build time.
Structured data
LocalBusiness, Service, FAQ, Breadcrumb and ItemList markup, validated rather than assumed. Most competitors ship one block or none.
Crawl and index control
A real sitemap with honest dates, a robots file that allows the crawl, and noindex served by header where a page genuinely should not be listed.
Canonicals and redirects
One address per page, and permanent redirects from every old URL so a redesign does not throw away years of history.
Speed as a ranking input
Core Web Vitals are part of this work, not a separate project. See our speed page for how we measure them.
Local search setup
Name, address and phone identical everywhere, opening hours in the markup matching the Google Business Profile exactly, and the major directories covered.
No themes, no page builders, no plugin stacks
Every site written from scratch, starting from almost nothing and adding only what the pages need. The whole speed recipe is published, not kept secret.
Read the recipe →AI, used properlyWe use AI to go faster, not to decide
It writes the mechanical parts. It never chooses the architecture, the performance budget, or a single fact about your business. Everything is reviewed by the person who will maintain it.
Where we draw the line →Questions
Asked often enough to answer here.
If yours is not here, the general questions page covers how we work, or you can just ask.
Do you guarantee first page rankings?
No, and anyone who does is selling something they cannot control. We control the technical foundation, the speed and the markup. Those are necessary, they are measurable, and they are the part that is genuinely ours to deliver.
What is llms.txt and do I need it?
A plain text file at your site root that lists your pages for AI assistants. It is a community convention, and no model provider has committed to reading it. We generate it from live content because it costs one file. Treat it as cheap insurance rather than a strategy.
How long before technical SEO shows results?
Crawl and index fixes can show within days. Speed improvements need about a month of field data before Search Console reflects them. Anything involving competition for a term takes longer and depends mostly on content and links, which is work outside the code.
Related work we do
All 16 servicesCustom web development
Websites written from scratch for one business, rather than a theme bent into shape until it almost fits.
Next.js development
The framework we reach for first, and the one we know well enough to know when it is the wrong answer.
Bun and Node.js backends
The part nobody sees, which is exactly why it has to be right.
Want this for your business?
Tell us what you have now and what is not working. We will tell you what we would do and what it would cost.