Guide
The technical SEO checklist we run on every site
The exact technical checks we work through on a client audit, in order of how much traffic each one usually costs. Indexing, speed, structure, schema and logs.
4 min read
We find what stops Google reading your site, then we fix it.
What is technical SEO?
Technical SEO is the work that makes a website easy for search engines to crawl, index and understand. It covers site speed, crawl errors, duplicate pages, redirects, internal links, structured data and mobile rendering. Fix the technical base first and every page you publish afterwards has a better chance to rank.
If none of these sound like you, technical SEO is probably not where your money should go first. Tell us what is happening and we will say so.
Scope
Every engagement covers all of this. Nothing here is an upsell once you have started.
We crawl every URL, then sort the problems by how much traffic each one costs you.
We find the pages Google skips and the pages it wastes time on, and we fix both.
LCP, INP and CLS measured on real mobile data, with the specific fixes your developer needs.
We map how link equity moves through your site and rebuild the paths that are broken.
Organization, Product, Article, FAQ and Breadcrumb schema, added and validated.
Every item has an owner, an effort estimate and the reason it matters. Plain English, no jargon.
How it works
The same four steps we use on every engagement, applied to this service.
We crawl the site and pull 12 months of Search Console data to see what Google actually does with it.
We rank every issue by traffic at risk, then agree what gets fixed first.
We implement the fixes, or hand your developer a ticket-ready spec.
We track indexed pages, crawl stats and Core Web Vitals monthly and show you the movement.
Audits are a one-off fee. Ongoing technical work is part of a monthly plan.
Full pricing for every service sits on one pricing page. No sales call needed to see a number.
Needs real data before launch
Three case studies, one per ICP, with before and after numbers you can prove and screenshots you have permission to publish.
The build throws if a published case study has an empty results array. See lib/content.ts. (PRD 16.1, PRD 9)
Learn
These guides cover the same ground in detail. Read them before you spend anything.
Guide
The exact technical checks we work through on a client audit, in order of how much traffic each one usually costs. Indexing, speed, structure, schema and logs.
4 min read
Guide
SEO explained without jargon: what it actually involves, how long it takes, what it costs, and how to tell whether the person you hired is doing it properly.
4 min read
Two weeks for most sites. A store with more than 10,000 URLs takes three. You get the findings in a call and a written fix list you keep.
Both are available. We can implement on WordPress, Shopify and most headless setups, or hand your developer a spec they can work from without asking follow-up questions.
Sometimes. If Google cannot index your pages, fixing that releases rankings you already earned. If your pages are indexed and simply not good enough, you also need content and links.
Yes, and it is cheaper then. Catching a broken canonical or a blocked robots rule in month one saves you a year of wondering why nothing ranks.
Screaming Frog and Sitebulb for crawls, Google Search Console and PageSpeed Insights for real user data, Ahrefs for link and keyword data, plus server logs when we can get them.
Yes. Most of our technical work ships through a client developer. We write tickets in the format your team already uses.
Send us your website and we will tell you whether this is the right place to start. If it is not, we will say what is.