Technical SEO Consultant Work, Rebuilt Per Page and Swept Weekly

← All modules · Technical SEO

A technical SEO service is the work that decides whether your content can be crawled, indexed, understood and rendered fast enough to compete — schema, canonicals, redirects, index state, internal link health, Core Web Vitals.

Technical SEO consultant work is not sold here as a separate module, because it is not a separate job. It runs in two places, on two different rhythms, and both are already included.

Request your free audit Book a strategy call

What a technical SEO consultant actually changes here

Hiring a technical SEO consultant normally buys you diagnosis. Someone senior reads the site, finds what is broken, ranks it by impact, and hands the list over. The judgement is the product; the shipping is still yours.

Here the judgement is the same and the handover does not happen. A technical SEO consultant on this engagement sets the rules the engine then enforces — which schema types each page type must carry, what a canonical is allowed to resolve to, when a redirect chain is a defect rather than a curiosity, what counts as proof that a fix landed. Those rules run on every deployment and every weekly sweep without being re-argued. The consultant's leverage stops being how many sites one person can personally read in a month.

It changes what is worth asking for, too. Not a document. A set of rules you can watch being enforced on a live page, and the check that proves it.

What a technical SEO service covers

Technical SEO is everything that affects a page's ability to rank that is not the words on it. Structured data, so search engines and AI answer engines can parse what the page is. Canonical tags, so duplicate and parameterised URLs consolidate instead of competing. Redirects, so link equity survives a URL change instead of leaking through a chain. Index state, so the pages you want in the index are in it and the ones you do not are cleanly excluded. Internal links, so authority reaches the pages that need it. And the rendering layer — Core Web Vitals, image handling, script weight — because a page that cannot be rendered quickly does not get the ranking its content deserves.

Most agencies sell this as a periodic audit: a consultant produces a document, and the document produces a backlog someone else has to work through. That is where technical SEO usually dies. The work is not hard to identify; it is hard to keep doing.

What actually gets checked

Most providers describe the discipline and leave the checks implicit. This is the list a technical SEO service actually runs through here — the same list whether it is running on a single page at deployment or across every URL on the site.

Crawl and discovery — robots.txt directives, XML sitemap accuracy against live URLs, orphan pages with no internal links pointing at them, and crawl traps thrown off by parameters and faceted URLs. More detail in our guide to crawlability and indexation.
Index state — index and noindex settings per template, Index Coverage anomalies in Search Console, pages excluded by accident, and near-duplicate URLs competing for one query.
Canonical and redirect hygiene — self-referencing canonicals, parameterised and cross-domain duplicates consolidated, redirect chains collapsed to a single hop, and dead URLs that still carry inbound links.
Structured data — schema that parses without error, types that match what the page actually is, and FAQ and breadcrumb markup whose visible copy still matches the JSON-LD instead of drifting away from it.
Internal link health — dead targets, links pointing through a redirect, self-links wasting a slot, and the cluster links a page ought to carry but does not.
Rendering and speed — Core Web Vitals, render-blocking scripts, image weight and missing dimensions, and whether what a crawler receives matches what a browser renders.

That list does not change much whether you hire a technical SEO agency, a technical SEO consultant, or run it in-house. What changes is how often it is run and whether anything is done with the output. A technical SEO company that hands over the findings once has sold you the easy half of the job. The long-form working version is our technical SEO checklist, and the one-off snapshot version is the SEO audit walkthrough.

Why it is not a separate module

Technical work splits into two rhythms that do not belong together. Some of it only makes sense at the moment a specific page changes. The rest only makes sense as a repeating sweep across every URL on the site. Bundling them into one retainer produces the audit-document problem: a list nobody works through.

So the engine splits them. The per-page layer is built into every deployment. The site-wide layer runs weekly on its own cadence. Neither is optional, and neither is sold separately — which means a technical SEO service is not something you add to an engagement here. It is something the engagement already does.

The per-page layer — inside Module 3, Precision Page Deployment

Every page that goes through a deployment has its technical layer rebuilt in the same pass as its content. Structured data written or corrected. Canonical checked. Redirects collapsed where the page's inbound links pass through a chain. Internal links audited for 404s and dead targets, and new links added where the page belongs in a topic cluster. Then PageSpeed and Core Web Vitals verified after the push, against the rendered page rather than the payload sent.

The per-page half of the technical SEO service is not a separate ticket queued behind the content work. It happens in the same sitting, on the same page, which is the only way the layers end up interlocking rather than contradicting each other.

The site-wide layer — inside Module 9, Race Control

Per-page work cannot find a problem on a page nobody is deploying. That is what the weekly sweep is for: a full sitemap crawl, 404s and 410s, redirect chains, canonical and noindex spot-checks, orphan pages with no internal links pointing at them, and Google Search Console Index Coverage anomalies.

Each issue is routed to the skill that fixes it rather than landing in a report. A broken internal link goes to the link auditor. A redirect chain goes to the redirect fixer. A page that has quietly dropped out of the index goes to the top of the deployment queue. The sweep's output is a work queue, not a PDF — which is the half of a technical SEO service that a periodic audit almost never delivers.

What you get

Technical work on every deployed page — schema, canonicals, redirects, link health and CWV rebuilt in the same pass as the content, not queued behind it.
A weekly whole-site sweep — crawl, index coverage, chains, orphans, with each finding routed to the skill that resolves it.
Verification against the rendered page — every change re-checked live after the push, with a reversible snapshot taken before the work began.
A deployment log — every technical change, the page it landed on, and its before-and-after state, in one place your team can read.
Named human tasks — theme-level and dev work written up with the specific change required, never silently dropped.

Where the engine is running

This is live work, not a spec — and all three sites are ours. The engine runs on Astound Cleaning Group, a UK commercial cleaning company we own, on our rye whiskey community RyeCentral, and on this site. Two unrelated industries, one system, every page change recorded in a dated per-page deployment log. We run every module on our own businesses before we run it on anyone else’s.

We publish no performance figures — not ours, not anyone’s. A number without a dated before-and-after beside it is not evidence. When there is a real measurement window worth showing, it will appear here with both readings and the dates attached.

How this technical SEO service compares to a standalone audit

Most technical SEO services arrive as a document. You commission an audit, receive a prioritised list of defects, and then own the harder half of the problem: getting each fix built, shipped and confirmed on a live page. The list starts ageing the day it lands, because a site does not stop changing while its backlog waits.

This technical SEO service is built the other way round. The technical layer is not a deliverable sitting beside the deployment work — it is part of the deployment itself. A page is not counted as deployed until its schema parses, its canonical resolves, its internal links return 200, and the rendered page has been re-fetched and checked against what was actually sent. Nothing lands in a backlog, because there is no handover.

The same limit applies to the independent-consultant route. A technical SEO consultant working alone is bounded by attention: the sites audited last quarter drift while this quarter's are being read. Rules that run on a schedule have no such ceiling, which is why the consultant hours here go into writing the rules rather than into running the sweep.

The distinction matters most on recurring defects. Redirect chains, orphaned URLs, competing canonicals and stale index states are not one-time faults; they come back as a site grows. A technical SEO audit service catches them once, on the day it runs. A scheduled sweep catches them every time they reappear — the difference between a snapshot and a control system. A technical SEO service that only reports is half a service; this one ships the fix and then proves it landed.

Questions we hear

What does a technical SEO consultant do?

Three things, in descending order of value: decide what counts as a defect on your particular stack, decide the order those defects get fixed in, and confirm each fix survived contact with the live site. The first two are judgement and do not automate. The third is measurement and should never be done by hand. A technical SEO consultant spending most of the month on the third one is being wasted.

Is technical SEO a separate module?

No, and that is deliberate. Technical work splits cleanly into two rhythms that do not belong in one product: the per-page layer, which only makes sense at the moment a page is deployed, and the site-wide layer, which only makes sense on a repeating sweep. Module 3 owns the first, Module 9 owns the second. Buying a standalone technical retainer on top would be paying twice for work already running.

Do you do a technical SEO audit?

Yes, in two places. Every page deployed through Module 3 is audited against its own technical layer before and after the change, and verified against the rendered page rather than the payload sent. Separately, Module 9 sweeps the whole site weekly and reports what moved. If you want a one-off snapshot before committing to anything, the free audit covers the technical baseline.

What if the fix is in the theme rather than the page?

It gets logged as a human task with the specific file and change named, not silently skipped. Theme-level work touches every page on the site, so it goes through a human rather than an automated deployment - that is a deliberate boundary, not a limitation we are working around.

How do you know a technical fix actually landed?

Every deployment re-fetches the live URL after the push and checks the rendered output: one H1, schema that parses, canonical and index state as intended, and the target term present in both the SEO title and the on-page heading. A push that fails verification is rolled back from the change log rather than left half-applied.

Can you run the site-wide sweep without the per-page work?

Yes. Module 9 runs standalone and reports into the same command center. It will find and route issues; whether the fixes are deployed by us or by your team is your call.

What does a technical SEO service include?

A technical SEO service includes crawlability and indexation control, canonical and redirect hygiene, structured data, internal link health, and Core Web Vitals — checked per page as it ships and swept site-wide on a schedule. Here that scope is split deliberately rather than bundled: the per-page work runs inside Module 3, and the site-wide sweep runs inside Module 9. You are buying the same coverage most technical SEO services quote for, arranged so it repeats instead of expiring.

What is the difference between technical SEO and on-page SEO?

On-page SEO governs what a page says — its target term, headings, copy and internal links. Technical SEO governs whether a search engine can reach that page, render it, and tell which version to index. They fail in different ways: an on-page problem means the right page ranks for the wrong thing, while a technical problem means the right page is never considered at all.

How long does technical SEO take to show results?

It depends what was broken. Indexation and canonical corrections can change what a search engine stores within a crawl cycle, often days. Core Web Vitals report on a 28-day rolling window, so a speed fix will not read as improved for roughly a month after it ships. We record the deployment date and the verification result on the day it happens, and let ranking data arrive on its own schedule rather than claiming it early.

What is a technical SEO service?

A technical SEO service is ongoing work on the parts of a website that decide whether search engines can reach, render, understand and index its pages — crawl and index control, canonicals, redirects, structured data, internal link health and Core Web Vitals. It governs whether your content is eligible to rank at all, rather than what that content says.

What is included in a technical SEO audit?

What is included in a technical SEO audit falls into six areas: crawl and discovery, index state, canonical and redirect hygiene, structured data, internal link health, and rendering speed. The enumerated version is in the section above. An audit that stops at the document has done the easy part — the value sits in the fixes that follow it, each one verified against the rendered page rather than the change that was sent.

Do I need a technical SEO service?

Ask whether any of these is true: pages you have published are missing from the index, two URLs compete for the same term, a migration left redirect chains behind, or Core Web Vitals are failing. If so, no amount of content or link work will outrun it, and you do need a technical SEO service. If none of them is true, the honest answer is that your budget belongs in content first — and a free audit will tell you which case you are in.

Can technical SEO be automated?

Most of it, and here most of it is. Schema generation, canonical and redirect checking, index-state verification, internal link auditing and post-push verification against the rendered page all run without a person in the loop. What is deliberately not automated is theme-level work: it touches every page on the site at once, so it is written up as a named human task with the specific file and change rather than pushed by a script. Automation should widen the number of checks that get run, not remove the judgement about which fixes are safe.

Go deeper

Request your free audit Book a strategy call

← See all ten modules

Keep exploring this topic

This module is part of the engine. Or see Google Penalty Recovery.

Your cart is empty

Your cart

Estimated total