
Technical SEO
The plumbing nobody sees and everybody feels, including crawlability, speed and structured data.
Start a conversationWhat it is
Technical SEO is the difference between a site search engines can read and one they quietly give up on. It covers crawlability, indexation, speed, structured data and the server logs that show what Googlebot actually spends its time on. For a large ecommerce catalogue or a multi-location site it decides whether your best content ever reaches a ranking at all. For regulated platforms it is also the part a compliance review rarely notices and an audit always does. At 4.digital we audit what is really happening, prioritise the fixes by impact and work through them with your developers in their language. Expect the audit in weeks and the benefit to follow the fixes rather than the report. We do not sell technical scores out of context. A hundred out of a hundred means nothing on its own. Revenue means something.
Most sites are not losing traffic because their content is weak. They are losing it because a redirect chain swallows half the link equity, or a line in robots.txt quietly blocked the blog two years ago and nobody has noticed since. Technical SEO is the work of finding that. It is unglamorous, it rarely makes it into a board deck and it is usually where the fastest gains have been hiding for years. The pattern is so common we now expect it. Strong content, decent links, and a site quietly getting in its own way while everyone debates the copy.
We audit what is actually happening rather than what the platform claims is happening. How the site is crawled, what gets indexed and what gets skipped, what slows the page down on a mid-range phone with bad signal, and where structured data is missing or simply wrong. Then we prioritise by impact, because a list of 200 warnings is not a plan and never was. Impact first, then effort, then order. Three fixes usually matter far more than the other fifty, and finding those three is the job. Everything after that is maintenance, and maintenance is cheap compared to surprise.
The fixes reach your developers as tickets with acceptance criteria and a test plan, written in their language rather than in ours. We review what ships before it goes live and retest it afterwards. One warning about this kind of work. If an audit arrives as a 90-page PDF and nothing in it ever gets fixed, you bought a document and not a result. We would rather hand you three shipped fixes than a document that impresses everyone and changes nothing. The evidence that this worked is a crawl report, not a certificate.
What we do
Crawl and indexation audit
What search engines actually see, what they skip and the reason why. We crawl the site the way Google does, compare it against what is indexed and find the pages that are invisible, duplicated or wasting the crawl on things that should never have been indexed in the first place.
Core Web Vitals
Speed and stability measured in real user data rather than one optimistic lab test, then fixed at the cause. Heavy scripts, layout shift and slow server response, not a plugin that hides the symptom for a fortnight before the numbers drift back to where they started.
Structured data and schema
Markup that tells engines what each page is, wins the rich results you have genuinely earned and makes you legible to the AI engines at the same time. Implemented and validated, with the errors that keep you out of the results fixed before anything cosmetic gets attention.
Log-file and crawl budget
Your server logs record what Googlebot really spends its time on. We read them, show you the waste in plain numbers and redirect the crawl toward the pages that make money instead of the ones nobody should ever have been indexing.
How we work
Audit
We crawl the site, pull the server logs and the search console data and compare all three against each other. What is broken, what it is costing you and which fixes return the most for the least disruption.
Plan
A prioritised fix list ordered by impact and effort, written as tickets your developers can pick up and estimate. Sequenced so the quick wins land early and the structural work lands when the team can actually carry it.
Build
We work alongside your developers throughout. Acceptance criteria, test plans, staging review and sign-off before anything ships. Where you have no developer, we do the implementation ourselves and show our working every step of the way.
Prove
Crawl stats, index coverage, Core Web Vitals and the revenue-bearing pages retested after each release. You see what got fixed and what it changed, not a score with no explanation attached to it. Progress is measured against the crawl, never against a vanity number.
What it costs
Pricing is driven by the size and complexity of the site and by who does the implementation. A small brochure site is a short engagement. A catalogue with faceted navigation and a seven-figure URL estate is not. The other variable is the split between our work and your developers'. Tickets cost considerably less than hands-on implementation. We scope after the audit, fix the fee before the fixes start and tell you when a rebuild would be cheaper than another round of patches. The number is agreed before any work begins, so a long fix list never becomes a long invoice.
Who it is for
Essential for large and complex sites. Ecommerce catalogues with faceted navigation, multi-location businesses carrying hundreds of near-identical pages, and regulated platforms where the technical debt ticket list has quietly grown for years. It matters most when the content and the links are already strong and the site still underperforms. That pattern is almost always technical. iGaming, fintech, healthcare and law sites carry extra weight here, because consent requirements, security rules and jurisdiction rules all change how the site is crawled and rendered before a ranking is even discussed.
Two kinds of business come to us: local service businesses and companies in regulated markets. See everything in Be found.
Questions we get asked
Is technical SEO a one-off job?
The audit is a one-off. The health is not. Sites change every week. A new theme ships, a plugin updates, a marketing page goes live with a noindex tag still sitting on it from staging. We keep a monitoring rhythm after the fixes land, so the same problems do not quietly return and undo the work six months later while everyone is looking somewhere else. The rhythm is cheap. The surprises are not. Most of our long-term clients are on a light monitoring arrangement rather than a permanent project, and that is deliberate. Fixing the same regression twice is the definition of wasted budget, and monitoring is far cheaper than the second fix.
Do you work with our developers?
Yes. We write the tickets, the acceptance criteria and the test plan, and we review the implementation before it ships. Your developers get work they can estimate and test rather than a PDF of suggestions with no acceptance criteria attached. If you have no developer, we do the work ourselves and show you exactly what changed and why it mattered. Either way, nothing goes live unchecked. Technical work that is not tested is a rumour, and rumours do not move rankings.
How long does a technical SEO audit take?
Two to four weeks for most sites, longer when the platform, the logs and the URL estate are genuinely complex. The audit document is not the deliverable. The prioritised fix list and the first shipped fixes are. Anyone selling a same-day audit is selling you an automated scan you could have run yourself over a coffee, formatted as a proposal. The value is in the judgement about what to fix first, because order decides whether your developers keep listening to us after week two. A fast scan with no judgement in it costs less and achieves nothing, which is a poor trade in any budget.
What does technical SEO cost?
It scales with the size of the site and with who does the implementing. Tickets cost less than hands-on work. A large catalogue with faceted navigation costs more than a brochure site, and occasionally a rebuild works out cheaper than a third round of patches. We tell you which situation you are in before you commit to anything, and the number is fixed before the fixes start, so a long list never becomes a long invoice. If the honest answer is to spend the budget elsewhere, we say that too.
What is the difference between technical SEO and on-page SEO?
Technical SEO decides whether your pages can be crawled, indexed and rendered at all. On-page work decides whether those pages answer the query better than anyone else's. The second cannot help you while the first is broken, which is why we fix the plumbing before anyone rewrites the copy. Most sites need both, and in that order. Content investment on a broken site is money spent on pages nobody can find, which is the most common way we see budgets wasted. Once the plumbing holds, the content work starts compounding instead of leaking.
Do Core Web Vitals affect rankings?
Google has confirmed that page experience feeds into its ranking systems, though it sits well behind relevance and authority in the order of things. The honest case for speed is commercial rather than algorithmic. Slow pages lose buyers on mid-range phones with poor signal, and no ranking benefit ever paid for a checkout that stalls while someone is deciding whether to trust you with their card details. We fix speed for the revenue and treat any ranking benefit as a bonus, never as the business case. Buyers reward speed with their attention and their money, and that is the argument that survives a budget review.
More Be found services
- SEOGetting you ranked for the searches that matter, and nothing you do not deserve.
- AI SEO & GEOBeing cited when people ask ChatGPT and Google AI, not just listed in ten blue links.
- Local SEOThe map pack, the reviews and the near-me searches, where local service businesses live or die.
- International SEOOne brand across borders, with hreflang, territories and languages handled properly.
- Site migrationsMoving domains or platforms without losing the rankings you paid for.
Tell us what you need from technical seo. We will tell you what we would do about it.
