Services · Technical SEO

The site has to be crawlable before it can rank

Technical SEO is the work nobody puts in a case study. It is also the work that decides whether the content you paid for is ever seen. If Google cannot crawl a page, render it and accept it as the canonical version, nothing else we do for you will matter.

Technical SEO

The symptom is always the same

Traffic plateaus, or a whole section of the site never appears in search. You publish more and nothing moves.

The cause is usually not the writing. The crawler is spending its time on parameter URLs, a template is blocking rendering, or half the catalog canonicalizes to a page that no longer exists. These failures are invisible in analytics, because the affected pages were never indexed in the first place — you cannot see traffic you never had.

That is why we start with your server logs and the page indexing report in Search Console rather than a dashboard. The logs are the only record of what Googlebot actually did, and the indexing report is Google's own account of which pages it left out and why.

What the work is

Technical SEO, in four parts.

01

Crawl and log-file analysis

We crawl the full site, then compare that crawl against 30 to 90 days of raw server logs to see which URLs Googlebot requested, how often, and which it ignored entirely. That shows where crawl activity is wasted on parameters, faceted navigation and redirect chains, and which commercial pages are rarely visited. It is the difference between what a tool thinks should be crawled and what is happening in production. If your host cannot export logs, we work from the crawl stats in Search Console instead and say so in the audit.

02

Core Web Vitals at template level

Fixing LCP on one page is a demonstration. Fixing it on the template that generates twelve thousand pages is the job. We group URLs by template and measure LCP, INP and CLS against field data from the Chrome UX Report rather than lab scores, because field data is what Google uses. Each failure is traced to a cause your developers can act on: an oversized hero image, a third-party script, a web font that shifts the layout.

03

Internal link architecture

Internal links are how authority moves through a site and how the crawler finds depth. We map the existing link graph, surface the pages that are orphaned or buried five clicks deep, and restructure navigation, breadcrumbs and in-content links so the pages carrying commercial intent are reachable within two clicks of the homepage.

04

Structured data

Schema markup does not improve rankings on its own. It changes how your result is displayed, which changes click-through rate on rankings you already hold. We implement and validate only the types that still earn rich results in your sector — typically Product, Organization, BreadcrumbList and Article — and confirm them in the Search Console enhancement reports after release.

What you receive
  • A prioritized backlog ranked by the number of indexable pages each fix affects, not by a tool's severity label
  • Tickets written into your tracker in the language your developers already use, each with the affected URLs and a test that confirms the fix
  • A before-and-after crawl comparison, so every fix is verified rather than asserted
  • A quarterly re-crawl that catches regressions introduced by your own releases
Timeline

The initial audit takes two weeks and arrives as a written report with the backlog attached. Implementation then runs at the speed of your release cycle — we work inside it rather than alongside it — and the quarterly re-crawl confirms that fixed issues stay fixed.

Who this is for

Sites above roughly 500 pages, anything built on a JavaScript framework, and any site that has been through a migration or replatform in the last two years. International and multilingual sites, where hreflang and regional versions need managing, are covered on the Scale plan. Smaller sites often need only the audit and a short list of fixes, and we will tell you if that is the case.

What it costs

Priced on the pricing page — no quote needed to find out.

Questions

About this service.

Do you implement, or only recommend?
Both. Most clients have developers, so we write the tickets and review the pull requests that close them. If you have no development resource, we implement directly in your CMS, always on a staging environment first.
Will this break anything?
Every change is specified in writing, shipped to staging, and verified with a re-crawl before it reaches production. We never push directly to a live site, and every change we ship can be rolled back.
How quickly do technical fixes show up?
Indexing changes can appear within days. Ranking movement usually follows over four to eight weeks, because Google has to recrawl and re-evaluate the affected pages before anything changes position. Large sites take longer, since Google revisits deep pages less often.

All questions →

Start with the diagnostic.

Two weeks, a fixed $160 fee, and the findings are yours whether or not we work together. If you continue, the fee is credited against your first month.

Get in touch