The Engineering Layer Under Every Ranking

The engineering layer decides whether anything else counts

Content and links are the visible half of search, but they pour straight through the holes when the technical layer leaks. Crawl, render, index, and speed are the plumbing, and when they fail the failure is usually silent: pages that never get indexed, revenue pages that wait days for a recrawl, rich results that were quietly revoked, and vitals that hand every competitor a head start on every query. Technical SEO is the discipline of finding those leaks with evidence rather than guesswork and closing them with changelists your developers can actually merge. It is unglamorous and it is foundational, because a beautifully written, heavily linked page delivers a fraction of its value if bots cannot fetch it, if it renders empty without JavaScript, or if it loads so slowly that a real-time retrieval process times out before it finishes reading. Every other discipline on this site assumes the technical layer holds; this is the service that makes that assumption safe.

Core Web Vitals are pass-fail table stakes now

Google's Core Web Vitals set three thresholds that function as a floor rather than a nice-to-have: Largest Contentful Paint under two and a half seconds, Interaction to Next Paint under two hundred milliseconds, and Cumulative Layout Shift under one tenth. Miss them and you spot competitors a handicap on every query; hit them and speed simply disappears as an excuse. There is a newer reason to care as well: real-time retrieval by AI crawlers operates on tight time budgets, and a page that loads too slowly can be dropped during ingestion before its content is ever read. The fix order matters more than the tool list. We measure on real mobile field data rather than lab scores, kill the largest render-blocking resources first, right-size and preload the LCP image, reserve space for anything that loads late, and only then chase interaction latency, which usually hides in third-party scripts nobody owns. Done in that order, most sites reach green without a rebuild.

Crawl budget is a money metric in disguise

On large sites the real constraint is not content, it is fetch. Log analysis routinely shows half or more of the crawl going to parameter junk, faceted duplicates, expired pages, and infinite URL spaces, while genuinely important new pages queue for days waiting to be seen. That is crawl budget being spent on things that will never earn a cent, and it is a revenue problem wearing a technical costume. We read server logs to see what bots actually fetch rather than guessing from Search Console, then prune, canonicalize, and block the waste so the crawl concentrates on pages that matter. The payoff is faster indexation of new content and quicker recrawls of updated pages, which means your freshest work starts working sooner. On a store with tens of thousands of URLs this is often the highest-return technical project available, and it is invisible to anyone not reading the logs.

Migrations fail in the details, not the redirect map

Redirect maps get all the attention during a migration, and they matter, but they are rarely where visibility actually dies. The quiet killers are schema parity lost in the new templates, crawler access rules that changed without anyone noticing, and entity language that drifted just enough to confuse the models that had learned your old pages. AI citations are especially fragile here, because models re-retrieve on their own schedule and judge the new pages as if they were fresh. We treat a migration as several parallel workstreams: baseline rankings, snippets, and citations before the freeze; validate schema parity on staging and again at cutover; re-verify AI crawler access in both robots and CDN rules; and re-scan at day fourteen and day forty-five with rollback triggers agreed in advance. That discipline is the difference between a migration that keeps its history and one that quietly resets it.

How the work reaches your developers, and why it is hourly

The output of a good technical engagement is not a PDF full of findings, it is a set of tickets your developers can implement without a translation layer. Every fix arrives specified at ticket level: the file, the change, the reason, and the test that confirms it worked, sized for your sprint rather than delivered as a lecture. For WordPress, Shopify, and WooCommerce we can implement directly; for custom stacks we hand over ready-to-merge changelists. The deep diagnostic audit is a one-time burst of hours, and a quarterly health check keeps regressions from compounding, which is precisely why hourly against a written estimate fits the shape of the work better than a flat monthly fee. You approve the audit scope, you see the hours, and the fixes land as acceptance-criteria tickets your team merges on its own cadence.