~/services

Where large sites actually fail.

We do not write blog posts and have no content writers on staff, by design. We find out why forty thousand product pages are missing from the index, write the fix in terms your developers can ship, and re-crawl to confirm it worked.

01

Crawl & log analysis

/services/crawl-logs
Problem
What Googlebot actually did, not what a tool guessed
Scope
What Googlebot actually did, taken from your raw server logs rather than inferred from a crawling tool. On a large site the two rarely match, and the gap between them is usually where the traffic went. The crawl audit gives us the map of your site; on the Retainer and Embedded plans, monthly log analysis shows how Googlebot is really using it.
Checks
  • Full crawl and server log pipeline
  • Crawl budget by template
  • Faceted navigation control
  • Parameter and duplicate handling
Output
  • Crawl data for every template, with status code, canonical and directives per URL
  • Googlebot requests by template, with wasted requests counted per day (Retainer and Embedded)
  • A per-parameter decision table your developers can implement and keep under version control
  • Findings ranked by the number of indexable pages affected, each with its evidence
open spec
02

Rendering & performance

/services/rendering
Problem
If it needs JavaScript to exist, it may not exist
Scope
If a page needs JavaScript to exist, it may not exist as far as the index is concerned. Rendering is where modern catalogs lose the most search traffic, and the failure is the hardest to see, because the page looks fine in a browser. We check every template in the crawl audit, review single templates on demand, and track performance by template on the Retainer and Embedded plans.
Checks
  • Render-path review
  • SSR / ISR strategy
  • Core Web Vitals by template
  • Edge and caching review
Output
  • A per-template render report showing what exists before and after JavaScript
  • A rendering recommendation per template: server-rendered, static, or client-side
  • Field-data Core Web Vitals baselines, with a target for each template
  • A re-check after each fix ships, using the same comparison as the original review
open spec
03

Index architecture

/services/index-architecture
Problem
Deciding what deserves to be indexed at all
Scope
Deciding what deserves to be indexed at all. On a large catalog, the most valuable technical decision is usually subtraction rather than addition: fewer, stronger URLs that Googlebot can reach quickly and that a searcher would actually want to land on.
Checks
  • Canonical & pagination policy
  • Internal link analysis
  • Segmented XML sitemaps
  • Migration and redirect mapping
Output
  • A written indexing policy covering every template on the site
  • An internal link analysis naming the pages that deserve promotion
  • A sitemap specification, with coverage tracked per segment in Search Console
  • A complete redirect map, checked after launch, where restructuring is required
open spec

Start with a crawl audit.

$160, fixed price, two weeks. Findings ranked by impact with the evidence attached, and the fee credited against your first month if you continue.

Get in touch