Core Web Vitals
Field and lab measurement across template archetypes, ranked by traffic-weighted impact. Dev tickets scoped to fix the worst archetypes first, not every page at once.
04 · Technical
The technical work that makes the rest rank.
Core Web Vitals, structured data, internal linking, canonical sanity, AI crawler access and schema work. Audit-driven, dev-ticket-shaped, and sequenced so it actually ships instead of sitting in a roadmap doc.
The problem
A strong content engine on a broken site still loses.
You can have the right ICP, the right cluster architecture and the right voice. If the page renders slowly, the schema is half-implemented, the internal-link graph is a guess, or AI crawlers are quietly blocked at the WAF, the work plateaus. Technical SEO is the layer that makes everything else cash out.
What's included
Six audit areas, all actionable.
Every engagement ships a written audit, a dev-ready ticket pack, and a quarterly support cadence to ship the tickets and re-audit.
Structured data & schema
What you have, what is missing, what is broken. Implementation plan covering Article, FAQ, Product, Organization and the answer-engine-relevant schema. Validated against Google's tester and Schema.org.
Internal-link architecture
The link graph mapped, audited and rebuilt where it needs to be. Orphan pages identified, hub-page authority concentrated, anchor-text patterns cleaned up.
AI crawler access
WAF, CDN, robots.txt and rendering audit for AI search crawlers (GPTBot, PerplexityBot, ClaudeBot, Google-Extended). Quietly-blocked-access is more common than teams realise.
Canonical & redirect sanity
Canonical mistakes, redirect chains, soft-404s, parameter handling and trailing-slash decisions. We map the redirect graph and reduce the risk surface.
Quarterly roadmap
The prioritized 90-day technical sequence. Tickets ranked by traffic-at-risk, impact and effort. Re-audited every quarter and re-prioritized based on what shipped.
How it runs
Four-week audit, then quarterly support.
01
Crawl & audit
Full-site crawl, GSC and analytics review, template-archetype mapping, schema audit, crawler-access check. Every issue logged against a traffic-at-risk score.
02
Prioritization
Issues sorted into ship-now, ship-this-quarter, ship-when-we-redesign. Each ticket scoped to a single archetype or fix so it can move through your dev team without becoming a project.
03
Ticket handoff
Dev-ready tickets delivered in your team's ticketing system, with acceptance criteria, validation steps and rollback notes. Content-side fixes (redirects, schema-in-CMS, surgical page edits) shipped directly by us.
04
Quarterly re-audit
Every quarter we re-run the crawl, validate the tickets that shipped, surface new issues and re-prioritize the next quarter's work. Compounding instead of one-off.
Pairs well with
What sits around it.
Technical SEO is most powerful as the foundation under strategy and production. Without it, content earns rank slower; with it, every published piece compounds faster.
Frequently asked
Questions we hear.
Do you write code or just file tickets? +
We deliver dev-ready tickets your engineering team can pick up. Where the work is content-side, like 301 redirects, schema additions inside the CMS or surgical page edits, we ship those ourselves. The split is decided up front so nothing falls between teams.
Is this an audit or ongoing work? +
The engagement starts with a fixed-scope audit and a prioritized roadmap. Most teams then move into a quarterly support cadence where we re-audit, re-prioritize and ship the next set of tickets. We do not run open-ended technical retainers; the work has a defined sequence.
What does AI crawler access mean? +
AI search engines, like ChatGPT and Perplexity, send their own crawlers to read your site. Many sites accidentally block them at the WAF, CDN or robots.txt layer. Part of the work is auditing what reaches the AI crawlers, what they can render, and what your site is signalling to them about its content.
Do you handle Core Web Vitals? +
Yes, as part of the audit and roadmap. Implementation is handed off to your engineering team or to a specialist where the issues are deep-rendering or framework-specific. We do not pretend to be a performance engineering team.
Next step
Let's see what your site is leaking.
A 30-minute discovery call, no pitch, no pressure. We look at your CWV, schema health and AI crawler access and whether a technical audit makes sense before the next quarter of content goes out.
Book a discovery call →Booking goes straight to Gemma's calendar.