Most technical SEO audits do not fail at the diagnosis stage. They fail in the gap between the report and the website. The agency finds 40 issues, the developer is busy with a product launch, and six months later the same crawl errors appear in the next audit.
So the useful question goes beyond “agency or developer?”. Ask which fixes each side should own, how the handover works, and who checks that the change actually helped. Get that split wrong and you either pay an agency to fumble through code it does not know, or ask a developer to guess what “fix the canonicals” means.
This guide from IZI Digital Marketing gives you a way to assign technical SEO implementation fix by fix. It sits under our wider guide to choosing an SEO agency in Malaysia, because the implementation model is one of the clearest differences between agencies. In the video below, two members of Google’s Search team talk about how SEOs and developers can work together without friction.
What SEOs Should Know About Devs (Google Search Central, Search Off the Record)
Source video: Watch on YouTube
PART 1 · DIAGNOSE
What Does Technical SEO Implementation Involve?
IN BRIEFTechnical SEO implementation is the work of turning audit findings into live changes on your site. It spans CMS settings, templates, code, server rules and hosting. Each layer needs different access and skills. Our guide to technical SEO basics explains what each fix does.
Before deciding who implements, sort the fix list by where each change lives. The same audit usually contains four very different kinds of work:
- CMS and plugin settings. Meta titles, noindex tags on thin pages, XML sitemap options and basic redirects. These sit inside WordPress, Shopify or your SEO plugin, and need no code.
- Template and theme changes. Heading structure, internal link modules, breadcrumb markup and structured data added site-wide. One edit changes hundreds of pages, so a mistake spreads fast.
- Code and performance work. Render-blocking scripts, image delivery, JavaScript rendering and layout shifts. This is developer territory.
- Server and hosting rules. Redirect rules, HTTPS, caching, response codes and crawl rate problems. These need server or hosting access that most agencies should not hold.
The layer decides the owner more than the fix name does. “Fix redirects” can be a two-minute plugin task or a server rule that breaks your checkout if written wrongly. An audit that does not say which layer each fix lives in is not ready to hand to anyone. If you are still judging audit quality, our breakdown of what SEO audit services should include is a useful benchmark.
Holding an audit with no clear owner for each fix?
The Diagnose phase of the IZI Blueprint sorts every finding by layer, impact and effort before anyone touches your site. See how the Blueprint works
BENCHMARK BRIEFING 1 OF 4
Which Technical SEO Fixes Need a Developer?
IN BRIEFPerformance, rendering and server fixes almost always need a developer. Metadata, indexing directives and simple redirects usually do not. Structured data sits in between, depending on your theme. Our schema markup guide shows when plugins are enough.
| Fix type | Usual implementer | Developer needed? | Risk if done wrong |
|---|---|---|---|
| Meta titles and descriptions | Agency, in CMS | No | Low |
| Noindex on thin or duplicate pages | Agency, in CMS | No | Medium |
| Simple page redirects | Agency, via plugin | Only for server rules | Medium |
| XML sitemap settings | Agency, in plugin | No | Low |
| Structured data, site-wide | Agency or developer | For custom types | Medium |
| Core Web Vitals and page speed | Developer | Yes | High |
| JavaScript rendering issues | Developer | Yes | High |
| Server codes, HTTPS and caching | Developer or host | Yes | High |
Illustrative model by IZI Digital Marketing, 2026, built on Google Search Central documentation on crawling, indexing and Core Web Vitals. A planning guide, not measured project data. Rust marks fixes that need a developer.
Two rows cause most arguments. Page speed is the fix agencies most often promise and least often deliver, because real gains come from theme code, image pipelines and hosting, not from a caching plugin. Google’s Core Web Vitals documentation asks for an Interaction to Next Paint under 200 milliseconds, which is rarely reached without a developer. Our Core Web Vitals guide shows what that work involves.
PART 2 · DESIGN
Should Your SEO Agency or Developer Implement Fixes?
IN BRIEFChoose based on your site setup and who controls deployments. An agency can implement CMS-level fixes on a simple site. A custom build, an online store or a site with a release process needs your developer in the loop. Our guide to SEO agencies in Malaysia compares delivery models.
Google’s own page on whether you need an SEO advises checking any recommendation against official guidance before making big site changes. That points to a clear division of labour: one party recommends, another deploys, and someone checks. Here is how to set it up for your situation:
DECISION BOX · WHO SHOULD IMPLEMENT YOUR TECHNICAL SEO FIXES?
| Your situation | Best model | Why |
|---|---|---|
| Small WordPress site, no developer on hand | Agency implements CMS fixes; freelance developer for code | Most fixes are plugin-level; code work is occasional |
| Online store on Shopify or WooCommerce | Agency specifies; store developer deploys | Theme and app changes can break checkout and tracking |
| Custom build with an in-house dev team | Agency writes tickets; your team ships them | Your developers own the codebase and release process |
| Site migration or redesign underway | Developer builds; agency sets and checks SEO requirements | SEO must be written into the build spec, not patched after launch |
| Agency offers in-house developers | Agency implements, with staging and sign-off | Works if you keep code ownership and a change log |
Verdict: Let the agency implement only what lives inside your CMS or SEO plugin. For anything touching templates, code or servers, the agency specifies and verifies while the developer deploys. Change this only if the agency has real developers and you keep full ownership.
Access follows the same logic. Grant only the access each party needs for its layer, and keep ownership of every account yourself. Our checklist of what access an SEO agency needs on day one sets out sensible defaults. If you are still weighing whether to use an agency at all, our DIY SEO vs agency comparison covers that earlier decision.
BENCHMARK BRIEFING 2 OF 4
Why Do Technical SEO Fixes Stall After the Audit?
IN BRIEFFixes stall mostly because nobody owns them, not because they are hard. Vague specifications and missing developer time come next. Technical difficulty ranks surprisingly low. Our SEO audit checklist shows which fixes move rankings most, so you can prioritise.
| Reason a fix stalls | Relative weight |
|---|---|
| No named owner for the fix |
9 |
| Vague spec, no acceptance criteria |
8 |
| Developer time taken by other work |
7 |
| No staging site to test safely |
5 |
| Conflict with theme, plugin or app |
4 |
| Agency lacks access to the right layer |
4 |
| Fix is technically difficult |
3 |
Illustrative model by IZI Digital Marketing, 2026, built on common SEO and developer workflow patterns discussed in Google Search Central guidance. Weights are planning judgements, not survey data. Rust marks process failures rather than skill gaps.
The top two reasons are both process failures. A fix without a name and a “done means…” line beside it is a wish, not a task. That is why the implementation model belongs in your brief from the start. Our guide to writing a digital marketing RFP shows how to ask agencies to state who deploys each type of fix before you sign.
BENCHMARK BRIEFING 3 OF 4
How Fast Do Fixes Go Live Under Each Model?
IN BRIEFA shared model, where the agency writes tickets and a named developer ships them, gets the most fixes live within 12 weeks. A report handed over with no plan gets the fewest. Before any website migration, the gap matters even more.
| Model | Week 2 | Week 4 | Week 8 | Week 12 |
|---|---|---|---|---|
| Report only, no plan | 5% | 10% | 20% | 25% |
| Agency alone (CMS access only) | 25% | 40% | 50% | 55% |
| Developer alone (no SEO spec) | 10% | 25% | 40% | 50% |
| Shared (agency tickets + named developer) | 20% | 45% | 70% | 85% |
Illustrative model by IZI Digital Marketing, 2026, for a typical small-to-mid business site with a 30 to 50 item audit. Planning estimates, not measured client data.
Look at the agency-alone row. It starts fast because CMS fixes are quick, then flattens once the easy half is done, since the remaining fixes need code access. The developer-alone row has the opposite problem: capacity exists, but without an SEO specification, fixes get interpreted differently. Only the shared model keeps climbing past week eight.
PART 3 · DEPLOY
How Do You Hand SEO Fixes to a Developer?
IN BRIEFTurn each finding into a ticket with the affected URLs, the exact change, the reason and a test that proves it is done. Batch tickets by template, test on staging, then verify live. Our website speed optimisation guide shows this for performance fixes.
A good handover saves more developer hours than any tool. Use this sequence for every round of fixes:
- Group fixes by template: one fix to the product template beats 300 page-by-page edits, and it is easier for a developer to estimate.
- Write each ticket in developer language: affected URLs or template, current behaviour, required behaviour, and why it matters for search.
- Add acceptance criteria: a test anyone can run, such as “URL returns 301 to the new page” or “canonical tag points to itself”.
- Rank by impact and effort: ship high-impact, low-effort fixes first so the developer sees results early.
- Test on staging first: check that the fix works and nothing else breaks, especially forms, checkout and tracking tags.
- Verify live and log it: the agency confirms each fix in Search Console or a fresh crawl, and records the date in a shared change log.
The change log matters later. When traffic moves, you need to know what changed and when. It is also your protection if you ever need to review an agency’s work, one of the checks in our guide to SEO agency red flags.
Developer asking questions your audit can’t answer?
We can turn an existing audit into ranked, developer-ready tickets with acceptance tests, whoever wrote the original report. Ask for a ticket review
BENCHMARK BRIEFING 4 OF 4
How Is Implementation Effort Split Between Agency and Developer?
IN BRIEFIn a healthy shared model, the agency carries diagnosis, specification and verification, while the developer carries coding. When one side does everything, specification or verification is usually what gets dropped. Our SEO services page shows how a diagnosis-first split looks.
| Delivery model | Split (ink = diagnosis, slate = specification, light = coding, rust = verification) | Diagnosis / Spec / Coding / Verification |
|---|---|---|
| Shared model |
|
20% / 20% / 40% / 20% |
| Agency does everything |
|
25% / 5% / 60% / 10% |
| Developer does everything |
|
10% / 5% / 80% / 5% |
Illustrative model by IZI Digital Marketing, 2026, built on Google Search Central guidance on evaluating SEO recommendations before site changes. Planning shares, not measured project data.
Nobody in the shared model works less. What changes is that specification and verification get real time instead of being squeezed out. When a single party does everything, coding swallows the budget and nobody checks whether Google saw the change. That same imbalance shows up in pay-for-results deals, as our review of performance-based SEO explains.
PART 4 · DRIVE
How Do You Know Technical SEO Fixes Worked?
IN BRIEFCheck three layers in order: the fix is live, Google has processed it, and search performance moved. Most reports stop at the first layer. Reading the right traffic segment matters too, as our guide to branded vs non-branded traffic explains.
Ask whoever verifies the work to report on each layer separately, so you can see where a fix got stuck:
- Live on the site. A fresh crawl or a URL check confirms the change exists on the real pages, not just on staging.
- Processed by Google. Search Console’s page indexing and Core Web Vitals report show whether issues are clearing. Field data can take about a month to reflect changes.
- Moved performance. Compare non-branded impressions, clicks and enquiries for the affected pages over the following one to three months.
If layer one passes but layer two does not, the problem is usually caching, a conflicting tag or a page Google has not recrawled yet. If both pass but performance is flat, the fix may have been low impact. That is a prioritisation lesson, not a failure.
THE VERDICT
Split the Work by Layer, Not by Loyalty
Technical SEO implementation goes wrong when it is treated as one job. Let your agency own diagnosis, specification and verification, plus anything inside your CMS or SEO plugin. Let your developer own templates, code and servers. Put both names on every ticket, and keep a change log you control.
If you are comparing agencies now, ask each one to describe its implementation model in writing. Our guide to choosing an SEO agency Malaysia businesses can rely on covers the other questions to ask, and our website design and development page explains how SEO requirements fit into a build.
FAQ
Frequently Asked Questions
1. Should my SEO agency implement technical SEO fixes itself?
Only for fixes inside your CMS or SEO plugin, in most cases. It depends on your site and who controls deployments. Template, code and server changes are safer with your developer, while the agency writes the specification and checks the result.
2. Can a web developer do technical SEO without an agency?
Yes, for the coding part. It depends on whether someone can diagnose and prioritise the issues. Developers ship fixes well but often lack search context, so without a clear SEO specification, fixes can be applied inconsistently or to the wrong pages.
3. What should a technical SEO ticket include?
A clear change and a test that proves it is done. It depends on the fix type, but most tickets need the affected URLs or template, current and required behaviour, the search reason, and an acceptance check anyone can run.
4. How long does technical SEO implementation take?
Most high-impact fixes can go live within 8 to 12 weeks. It depends on developer capacity and the number of templates involved. Google may then need several weeks to recrawl pages and reflect the changes in Search Console.
5. What access does an agency need for technical SEO implementation?
Only access to the layer it will change. It depends on the agreed model. CMS or plugin access is enough for most agency-owned fixes, and you should keep ownership of hosting, code repositories and every Google account yourself.
Not sure who should own your fix list?
A free Blueprint consultation sorts your audit by layer, impact and effort, then helps you decide which fixes your agency, your developer or your own team should take on.