How to Divide SEO Implementation Across Strategy, Code, and Approval

Tomohiro Iida · Published August 3, 2026 · Updated September 7, 2026

When sound SEO recommendations keep stalling at implementation, you do not necessarily need to replace the agency or production company. Split strategy, the implementation-ready specification, production code, release approval, and post-release verification; then assign an owner, accountable decision-maker, and acceptance condition to each stage before contracting.

Netsujo has in fact received partnership enquiries from existing SEO agencies that can produce the recommendations but want to divide the layer that requires coding. This observation is background evidence for the collaboration model; it is not evidence that code implementation is included in a standard SIGNAL plan.

Key takeaways

Move recommendations into production by separating strategy, specifications, code implementation, release approval, and post-release verification, with an explicit owner and accountable decision-maker for each stage.
Implementation scope differs by SIGNAL plan: recurring diagnosis centres on implementation-ready deliverables; delivery support carries an agreed specification through implementation coordination and release verification; the 90-Day Initial Improvement engagement includes agreed implementation support within its standard scope. A separate production-code engagement or work beyond the standard scope is contracted or re-estimated separately.
We have not fixed the arrangement into a single partner programme. For each engagement we first define the client-facing contact, scope of responsibility, deliverables, information handling, and post-release verification.
Neither search rankings nor inclusion in generative AI answers can be guaranteed. What we can make explicit is the change, its completion, its technical reflection, and how it is measured.

What this article covers

Covered: why SEO agencies and production companies ask us to share the implementation layer.
Covered: the implementation scope we take on and how roles are divided.
Not covered: choosing a partner as the company commissioning the work — see the linked article.
Not covered: why recommendations fail to reach implementation in the first place — see the linked article.

Choosing between an SEO agency, a web production company, and Netsujo SIGNAL

Seven reasons SEO report recommendations may not get implemented

How to protect the sales foundation during a website redesign

How to improve a site without replacing the production company

The names of partner companies, the number of engagements, and their outcomes are not published. They will be added once permission to disclose them has been obtained.

First, a distinction: the standard SIGNAL plans and a separate implementation contract

This is where partnership discussions go wrong first. If it reads as “sign up for SIGNAL and code implementation is included”, then scope, cost, and responsibility will not line up.

The implementation boundary differs by plan. SIGNAL Continuous Diagnosis centres on implementation-ready deliverables such as structured data, title and description drafts, heading structures, page copy, FAQ copy, GA4 event specifications, and implementation instructions. SIGNAL Improvement Delivery coordinates implementation and release verification with the client’s in-house staff and existing production company. the 90-Day Initial Improvement engagement includes agreed implementation support within its standard scope of up to ten primary pages and thirty hours in total, ending when either limit is reached. Where Netsujo is separately commissioned to write production code, or work exceeds the standard scope, it is handled under a separate implementation contract or change estimate.

Arrangement	Covered as standard	Who implements in production	Relation to the collaboration in this article
SIGNAL Continuous Diagnosis	Ongoing diagnosis and delivery of implementable deliverables	The client’s in-house staff or the existing production company	The input side of a collaboration; the implementation stage is not included
SIGNAL Improvement Delivery	Carrying work forward from an agreed specification through implementation completion and release verification, together with in-house staff and the production company	Progressed together with in-house staff and the existing production company	Sharing progress and verification; not a contract to write the code itself
90-Day Initial Improvement engagement	A fixed 90-day initial improvement with a defined standard-scope limit	Limited implementation support inside the standard scope	Implementation beyond the limit is handled separately
A separate implementation contract	The code implementation itself, defined per engagement	Netsujo	The substance of the collaboration described in this article

In the 90-Day Initial Improvement engagement, human standard support is capped both at up to ten primary pages and at thirty hours in total; standard support ends at whichever limit is reached first. Work beyond the standard scope is quoted as a change estimate before it begins.

The 90-day initial improvement also excludes the following areas. Where a collaboration needs them, they are designed as a separate implementation contract rather than a SIGNAL plan.

New web design
Full site redesign
CMS migration
Large-scale coding
Backend development
Membership features
E-commerce features
External system integration
Photography, video, and illustration
High-volume article production
Specialist supervision such as legal or medical review

Deciding the boundary first keeps the design of a collaboration simple. Separate the diagnosis and deliverables, which sit in the standard SIGNAL plans, from the production code, which sits in a separate contract, and then decide the approver and the handover method for each engagement. The service page is the source of truth for the current scope and pricing.

Netsujo SIGNAL scope and pricing

A correct recommendation alone does not complete an SEO programme

The value of SEO work appears not at the point of analysis, but at the point where a change is published, measured, and connected to the next improvement.

Research and recommendation quality matter, and weakness there prevents results. In practice, however, a separate problem arises.

Recommendations span the frontend, backend, CMS, infrastructure, and measurement.
The client company’s development team has no time to spare for SEO changes.
Additional orders and specification checks with a production company take time.
Recommendations are abstract and cannot be converted into development tickets or code changes.
No verification method is defined for after release, so the effect cannot be checked.

As a result, reasonable recommendations stay inside reports, Backlog, or Notion. A recommendation that has not been implemented reaches neither search engines, nor generative AI, nor prospective customers. The work Netsujo SIGNAL handles sits in this gap between recommendation and result.

Netsujo SIGNAL grew out of implementation, not reporting

Netsujo SIGNAL was not designed from the start as an SEO service to sell externally. While improving the websites Netsujo operates, using AI agents together with human review, the flow of diagnosis, prioritisation, code changes, release, and verification became a single system.

Because the starting point was real websites and real code rather than a report template, recommendations are handled in the following order.

Confirm the business goal.
Break down what on the website prevents the goal from being reached.
Set priority from business impact and implementation difficulty.
Convert the required change into a specification, a task, and code.
Have a human check business context, wording, and risk.
Confirm the published state and measurement results after release.
Connect to the next improvement candidate.

The diagnosis views a website in eight stages.

Stage	What is checked
Existence	Whether the necessary pages, information, and functions exist
Discovery	Whether search engines, generative AI, and users can find them
Retrieval	Whether crawlers and browsers can fetch and render them correctly
Trust	Whether the operator, track record, evidence, and freshness come across
Understanding	Whether the business, target customer, and value offered are clear
Action	Whether it is easy to proceed to an enquiry, application, or document request
Measurement	Whether actions and improvement effects can be measured
Improvement	Whether measurement results can be returned to the next implementation

Search rankings are an important indicator but not the business goal itself. Improvement targets are decided by working backwards from the outcome the website is expected to produce, such as enquiries, applications, sales meetings, or job applications.

A diagnosis based only on public information, without access permissions, cannot fully evaluate the Measurement and Improvement stages. Those two are judged once access to the measurement tools has been shared.

What we support at the layer that requires coding

What these enquiries ask for is not development outsourcing that simply executes an existing SEO recommendation as received. We read the intent of the recommendation, check it against the site structure and the business goal, and convert it into implementable units.

The areas listed below fall under “a separate implementation contract” in the table above. They are not automatically part of a standard SIGNAL plan; the target, deliverables, acceptance criteria, and handover method are defined per engagement.

1. Structure that search engines and generative AI can interpret

Titles, descriptions, headings, and body structure
Canonical, noindex, robots, and XML sitemap settings
Structured data design and implementation
Internal links, breadcrumbs, and paths to related information
Clear operator, author, track record, source, and update information
Information structure that accounts for machine retrieval, including AI crawlers

In the area referred to as AIO or LLMO, simply placing a special file does not produce results. Google does not publish a dedicated schema or file as a requirement for its AI features. The premise is that page content, sources, and the relationships across the site are understandable to machines and to people.

2. Rendering, page speed, and technical soundness

Investigating retrieval and rendering problems caused by JavaScript rendering
Improving page speed, including Core Web Vitals
Optimising image, font, and JavaScript delivery
Tidying URL design, redirects, duplicate pages, and 404s
Fixing mobile display, layout breakage, and usability
Changes that respect the CMS and framework in use

Technical SEO does not end with checking settings. The appropriate action changes with the codebase, build method, CMS, and hosting environment.

3. Paths that lead to enquiries and applications

Reviewing CTA priority and placement
Designing the path from service page to enquiry
Improving form fields, input effort, and drop-off factors
Designing movement between articles, cases, and service pages
Implementing explanations that work for visitors who did not arrive by branded search

Even when traffic increases, business results do not follow if the target customer cannot understand the content and cannot proceed to the next action. SIGNAL designs SEO, AIO, and CRO from the same goal rather than treating them separately.

4. Measurement and continuous improvement

Event design for key actions
Checking the measurement environment, including GA4 and Google Search Console
Setting up measurement for enquiries, document requests, and outbound transitions
Recording changes before and after implementation and confirming they are reflected
Designing alternative indicators when data is hard to obtain
Designing the operation used to judge the next improvement candidate

The data available differs by measurement-tool permissions and site environment. Stating what can be obtained, and not asserting conclusions about data that cannot be seen, is part of the quality of implementation support.

SEO agencies and Netsujo SIGNAL can complement each other

For some engagements, dividing the specialisms is faster and easier to keep under quality control than holding everything in one company.

Existing SEO agencies bring long-term client relationships, industry understanding, search-demand analysis, keyword strategy, content planning, and ongoing support. Netsujo SIGNAL connects the following functions to that.

Mainly handled by the SEO agency	Mainly handled by Netsujo SIGNAL	Defined jointly
Client understanding, competitor analysis, keyword strategy	Technical investigation, implementation specifications, code changes	Business goals and KPIs
Content planning, editing, and operation	Structure, internal design, retrieval and rendering improvements	Priority and roadmap
Monthly reporting and client communication	Conversion paths, measurement, post-release verification	Judging results and the next improvement

What matters is defining the client-facing contact, scope of responsibility, deliverables, information handling, and post-release verification before the collaboration starts. Netsujo respects the existing support structure and takes on only the roles a given engagement requires.

The shapes of collaboration we anticipate

At present we have not fixed the arrangement into a single partner programme. Depending on the engagement, we mainly anticipate the following shapes.

Implementation back end: The SEO agency owns the client relationship and strategy; Netsujo SIGNAL handles technical investigation, implementation specifications, code changes, and release checks.
Joint proposal: Both companies take part from the initial diagnosis and proposal stage, combining content, technology, conversion paths, and measurement into one roadmap. This suits sites with a large implementation volume, or engagements where SEO and site changes run in parallel.
Converting existing recommendations: For engagements that already have an SEO report or improvement list, we review the content and convert it into development tickets, acceptance criteria, and code changes. Where priority or technical validity needs checking, we resolve it before implementation.
Spot support for technical issues: We take on only the difficult areas, such as JavaScript rendering, indexing problems, structured data, page speed, or measurement gaps.

Four decisions to document before implementation

Whichever collaboration model you use, document these four decisions before work starts. Name roles or people rather than companies alone.

Decision	What to define	What happens if it is left undefined
Implementation scope	Target URLs, changes, excluded areas, and how work beyond the standard scope is handled	Extra cost and schedule negotiation starts after implementation has already begun
Assignees	Who implements, performs technical review, and carries out the production release	The release stalls because no operator has been named
Approval	Who is accountable for approving production release and exactly what is approved: scope, impact, version, and release time	The implementer is forced to make the business release decision
Handover	Who receives the deliverables, how evidence is retained, and who owns post-release checks	Implementation may finish while nobody owns production verification

Approval and release execution are separate decisions. A common pattern is for the client’s release approver to authorize the change while the person with production access performs the release. The article on keeping an existing production company gives a fuller RACI example.

How to divide implementation, release approval, and verification with an existing production company

This suits SEO agencies and production companies with these issues

You can produce recommendations, but implementation resources are short.
The client’s development team is busy, so SEO changes keep being postponed.
Engagements with complex technical stacks, such as Next.js or a headless CMS, are increasing.
You want to convert an existing SEO report into concrete development specifications.
You want to improve SEO together with AIO, LLMO, CRO, and measurement as one package.
You want to include post-implementation checks and continuous improvement in your proposal.
You want to keep your own client relationship while supplementing only the technical area.

Whether and how far we can take something on is judged after confirming the target site, how code is accessed, the CMS, the development structure, and the intended changes.

Collaboration extends the value of SEO support past the release

For Netsujo SIGNAL, working with existing SEO agencies is not simply a way to add sales channels. Connecting Netsujo’s implementation capability to the market understanding and client contact an SEO agency already has makes it easier to carry a recommendation through to a published change. When post-implementation verification is shared as well, the next proposal becomes more concrete.

What Netsujo SIGNAL aims for is not more diagnostic reports, but more systems in which websites keep improving. For that, connecting with companies that hold each specialism is more reasonable than one company enclosing SEO, content, design, development, and measurement.

For SEO agencies, web production companies, and marketing support companies

We accept partnership enquiries about engagements with issues at the implementation layer, including SEO changes that require coding, information structure that accounts for AI search, enquiry paths, and measurement design.

The URL of the target site
Your current scope of support and the client structure
The role you would like Netsujo to take
Existing recommendations or a list of issues
When you would like to start

Rather than starting from a programme, we design the scope of responsibility and the way of working for each engagement.

Frequently asked questions

If we sign up for a standard SIGNAL plan, is code implementation included?: Not uniformly. SIGNAL Continuous Diagnosis centres on implementation-ready deliverables. SIGNAL Improvement Delivery coordinates implementation and release verification with the client’s team and existing production company. the 90-Day Initial Improvement engagement includes agreed implementation support within its standard scope of up to ten primary pages and thirty hours in total, ending when either limit is reached. A separate production-code engagement or work beyond the standard scope is contracted or re-estimated separately.
Does Netsujo SIGNAL compete with SEO agencies?: We also work directly with client companies, but in collaborative engagements we decide roles on the premise of the existing client relationship and support structure. An arrangement where the partner company owns SEO strategy, content, and the client relationship while Netsujo handles technical investigation and implementation is possible.
Can we ask for coding only?: If we can review the existing recommendations and their technical validity, priority, and scope of impact are clear, we can support mainly the implementation stage. Where the intent or acceptance criteria are unclear, we start by organising the specification.
Which CMS platforms and frameworks do you support?: We judge after confirming the site structure, repository, CMS, hosting, and permissions. Rather than promising uniform support for every environment, we state the implementable scope and the risks after a preliminary investigation.
Can you guarantee search rankings or inclusion in generative AI answers?: No. Both search rankings and generative AI answers involve external factors. What Netsujo SIGNAL makes explicit is the change, its completion, its technical reflection, and the measurement method, so that the result can be verified.

We start from the target site, your current scope of support, and the role you would like Netsujo to take.

Discuss a partnership

See the Netsujo SIGNAL service

Choosing between an SEO agency, a web production company, and Netsujo SIGNAL

Seven reasons SEO report recommendations may not get implemented

How Netsujo SIGNAL came about（日本語）