Help prospects find your business, understand your value, and get in touch.

Tell us the offer you most want to sell, the audience you want to reach, the problem they face, and the action you want them to take. Netsujo SIGNAL works backwards from that goal, checks how those questions are answered across the public web and generative AI, identifies the landing page and the supporting evidence, and returns one recommended improvement with a target URL, the changes to make, how to know it is done, and how to measure the result.

Rankings, crawl health, content, and AI mentions remain important evidence. SIGNAL does not present them as a scorecard in isolation: it keeps the chain Business Goal → Audience → Their Question → What We Checked → Landing Page → Evidence → Issue → Recommended Improvement intact, so a sales hypothesis can become a piece of work an in-house team or existing agency can quote and implement.

From scorecard to website assessment

URL-first scorecards

They can identify technical issues, but they do not know which offer, customer, problem, and desired conversion matter most. Several findings appear without a clear connection to the sales opportunity being lost.

What we check

SIGNAL generates mostly non-branded customer questions from the declared sales goal, records provider, model, search setting, locale, region, time, citations, and observation failures, then connects the primary question to the relevant landing page and public evidence.

First recommended improvement

The free report still gives one complete implementation unit: target URL and surface, observed facts, root-cause type, change steps, completion criteria, validation steps, recommended owner, effort, success metrics, and any internal access required.

What SIGNAL fills is the gap between the sales goal and implementation. Fact, interpretation, business hypothesis, and verification are kept separate, and failed or unavailable observations are never converted into “no problem”.

A five-stage structural approach

01 Observe — record the symptom

Inputs: the public site, Search Console, GA4, how you appear in AI search, and your own business information. Outputs: the symptom, the affected URLs, a baseline, and the business impact.

02 Trace — locate the implementation root cause

We check HTTP status and redirects, initial HTML versus the rendered DOM, metadata and canonical tags, robots.txt and sitemaps, JSON-LD structured data, JavaScript dependencies, internal links, and CTA/form/measurement events. Outputs: the verified facts, the root cause in code or configuration, our confidence, and the blast radius.

03 Specify — convert it into a recommended improvement

Outputs: target URL, the component or setting to change, what to change, why, the completion criteria, the verification method, who should do it, the expected effort, and the success metric.

04 Execute — move the implementation forward

Your approval, owners and deadlines, handover to your existing agency, resolving questions and spec gaps, and — depending on the contract — code examples, diffs, or pull requests.

05 Verify — confirm the launch and the result

Production deployment, visual regressions, HTML and metadata, structured data, redirects and canonical tags, GA4 events, a period-over-period comparison in Search Console and GA4, and the decision on what to improve next.

What a recommended improvement looks like

Instead of an abstract instruction like "improve SEO" or "make it easier for AI to cite", we break the work down to a unit your agency can quote, implement, and check. The example below is an illustration, not a real customer record.

• Problem: the service’s target customer is not reaching search engines or AI clearly enough. Target: /services/example.
• Verified facts: the service name is in the initial HTML but the target customer and the outcome delivered are not; the target-customer copy is only added after hydration; structured data has WebPage only, with no Service information; the hero CTA has no click event.
• Root causes: the hero’s main description depends on a client-side fetch; on-screen copy and metadata/JSON-LD are managed as separate data; the CTA does not go through the shared measurement component.
• Changes: emit the service name, target customer, and outcome server-side; generate the on-screen copy and the Service JSON-LD from the same service data; add internal links from three related pages; connect the hero CTA to the existing GA4 event design.
• Completion criteria: the initial HTML fetched with curl contains all three facts; on-screen copy and structured data agree; structured-data validation shows no critical errors; the new internal links return 200 and the canonical is correct; the hero CTA event is observable with the usual debugging method; no layout breakage or CLS regression on desktop and mobile.
• Verification: technical checks immediately after launch; search, traffic, and conversion compared against the baseline period over 28 days.

What we analyse, and from where

The free website assessment uses public information only. It records what was observed and what remains unknown. Paid engagements add continuous observation, analytics data, multiple recommended improvements, implementation delivery, and post-launch verification within the agreed access and scope.

From the public site (included in the free diagnosis)

HTTP status and redirects; initial HTML; the rendered DOM; title, description, and canonical; robots.txt and sitemaps; heading and body structure; internal links; JSON-LD structured data; whether company information, pricing, and track record agree across pages; CTA and form pathways; measurement behaviour observable in the published state; and any gap between how search and AI describe you and your official information.

After access is granted (as needed, within the contract)

The source repository; CMS templates and content models; routing and rendering; the Server/Client Component split; SSR/SSG/CSR implementation; metadata generation; where JSON-LD is generated from; shared components; redirect and header configuration; GTM and GA4 event setup; actual Search Console and GA4 data; pre- and post-deploy diffs; and, within scope, change proposals, code diffs, or pull requests.

Access to source code, CMS, GA4, Search Console, and GTM is arranged only after confirming it is necessary and in scope, with least privilege and for a limited period.

Technical appendix: the eight first-principle areas

Layer 1 — Retrieval structure (existence, discoverability, retrieval)

Whether search engines, generative AI, and prospects can reach your important pages and retrieve their content: indexing, sitemaps, robots, canonical, navigation, internal links, initial HTML, the rendered DOM, and JavaScript dependency.

Layer 2 — Sales structure (trust, comprehension, action)

Whether the company, its track record, the target customer, the value offered, pricing, and terms come across well enough for someone to enquire: company information, primary sources, service descriptions, target customer, deliverables, pricing and terms, CTAs, forms, and FAQ.

Layer 3 — Improvement structure (measurement, improvement)

Whether post-launch change can be measured and fed into the next decision: GA4, Search Console, GTM, conversion events, change history, period comparison, prioritisation, and the improvement plan.

Working with your existing team or agency

You do not need to replace your web agency. Because SIGNAL organises the target URL, the evidence, what to change, and the completion criteria, your existing agency skips the root-cause investigation and goes straight to quoting and implementing.

What we found when we audited 21 companies

We audited the public websites of 21 Japanese B2B technology and professional-services companies — 247 pages against 75 checks. What SIGNAL looks at is exactly what that study defines as a standard.

• Heading structure: 21 of 21 companies were below the standard.
• FAQ coverage of purchase blockers: 17 of 21 companies were below the standard.
• Displayed publication date: 20 of 21 companies were below the standard.

The study did not estimate lost enquiries or lost revenue. It audited the breakage, observable from public information, where an opportunity can be lost. "Below the standard" is partially met plus not met.

Read the findings and the recommended improvements

Plans and pricing

SIGNAL Continuous Diagnosis — JPY 70,000 / month (excl. tax; JPY 77,000 incl. tax), no separate setup fee

For companies that will receive the evidence in the code and the recommended improvement, and implement with their own team or their existing agency. One domain. You can apply online and pay by credit card; invoice / bank transfer is available on request through a consultation and an electronic contract. Includes an access analytics dashboard (NETSUJO ANALYTICS) that brings findability across search and generative AI, Google Search, and enquiries and outcomes together on a single screen, continuous diagnosis across the eight areas, prioritised issues with evidence, recommended improvements, approval and implementation management, and post-launch measurement. Production implementation is, as a rule, done by you or your existing agency.

SIGNAL Improvement Delivery — JPY 300,000 / month (excl. tax), no separate setup fee

For companies that want Netsujo involved through finalising the recommended improvement, internal decision-making, coordination with the agency, and the post-launch check. It starts after a prior consultation, under an electronic contract, with payment by invoice / bank transfer and the payment terms fixed in the contract. Includes SIGNAL Continuous Diagnosis, an access analytics dashboard, a monthly improvement meeting of up to 60 minutes, a confirmed execution plan, internal decision support, a monthly coordination cycle with your agency, progress management with owners, deadlines, and reasons for delay, and post-launch verification of HTML, metadata, structured data, and GA4 events. Minimum three months, renewing monthly thereafter. Production implementation remains with you or your agency; any individual implementation by Netsujo is scoped separately.

SIGNAL 90-Day Initial Improvement — from JPY 900,000 total (excl. tax)

A 90-day engagement that starts after a scope review, under an electronic contract, with payment by invoice / bank transfer. The contract total is normally split into three payments (at contract signing, and 30 and 60 days after the start), and there is no auto-renewal. It includes SIGNAL Continuous Diagnosis for those 90 days. Covers an access analytics dashboard, diagnosis of all sales-related pages, standard human work capped at up to ten key pages and a total of thirty hours — whichever limit is reached first — recommended improvements and implementation support for the key pages, setting up the measurement environment, post-launch checks, and handover. Scope is confirmed before we propose; work beyond the standard scope is quoted before it starts. Within 30 days of the end, you choose to move to Continuous Diagnosis, move to Improvement Delivery, or finish — there is no automatic move to a higher plan.

All prices exclude tax. SIGNAL Continuous Diagnosis can be applied for online and paid by credit card; invoice payment / bank transfer is available on request under an electronic contract. SIGNAL Improvement Delivery and the 90-Day Initial Improvement engagement likewise start under an electronic contract, with invoice payment / bank transfer, once scope and payment terms are confirmed. This is not a service that guarantees search rankings, inclusion in AI answers, enquiry volume, or revenue.

Security and data handling

• The free website assessment requires no login or payment method and never starts a paid contract automatically.
• No card details are collected: online card payment is not offered yet, and paid engagements are billed by invoice.
• GA4 and Search Console are connected read-only with least privilege, only when needed, and can be revoked at any time.
• Access to repositories, CMS, GTM, and similar is granted after a contract, scoped by agreement, with only the necessary privileges and for a limited period.
• Access is managed by organisation and role, and any data connection can be revoked.
• AI is used for analysis and drafting improvements; material facts are put to you for confirmation.
• We act on data deletion requests, limit subcontractor access in scope and time, and log key operations for audit.

Frequently asked questions

What does SIGNAL actually do?

It analyses search, generative AI, analytics data, your own business information, and the implementation state of your website together, identifies the root causes blocking sales opportunities, converts them into recommended improvements with a target URL, evidence, what to change, completion criteria, and a verification method, and connects that through approval, implementation management, and post-launch measurement.

How is this different from conventional SEO or AIO tools?

On top of observing rankings, traffic, and AI mentions, we check initial HTML, the rendered DOM, structured data, internal links, JavaScript dependency, and CTA/measurement implementation. The central difference is converting those observations into a recommended improvement, and following it through implementation by your existing agency and verification after launch.

Does the free diagnosis look at our private source code?

No. The free diagnosis covers public information only. Private repositories, CMS, GA4, Search Console, and GTM are analysed after a contract, once the necessity and scope are confirmed and access is granted.

What information do you share with our agency?

A recommended improvement covering the target URL, the verified facts, the implementation root cause, the business impact, what to change, the completion criteria, and the verification method — plus code examples, JSON-LD, measurement event specs, and diffs where useful.

How do we pay?

By invoice / bank transfer. SIGNAL Continuous Diagnosis can be paid by credit card through the online application; invoice payment is available on request. SIGNAL Improvement Delivery and the 90-Day Initial Improvement engagement are billed by invoice / bank transfer under an electronic contract, with the exact billing dates and due dates set in the individual contract. The free diagnosis needs no payment method.

When is Continuous Diagnosis charged?

Through the online application it is JPY 77,000 per month including tax, with the first month charged at sign-up and monthly renewal thereafter. With invoice payment it is billed in advance for the agreed period — as a rule three months or more — with the billing and due dates set in the contract. Paid features do not start until the first payment has completed. Through the online application, the first month is charged at sign-up and renews monthly.

Can we cancel Continuous Diagnosis at any time?

If you applied online, you can schedule cancellation from the customer portal at any time; it ends on the last day of the current period. With invoice payment, let us know before the next renewal. You can keep using it until the end of the period already paid for. There is no pro-rata refund partway through a period.

What is the difference between Improvement Delivery and the 90-Day engagement?

Improvement Delivery is an ongoing contract in which Netsujo supports monthly decision-making, agency coordination, and progress management while your in-house team or existing agency does the implementation; minimum three months. The 90-Day Initial Improvement engagement is a fixed-term project that concentrates on sorting out the initial issues and improving your key pages and measurement environment within 90 days, with no auto-renewal.

How are the ten pages / thirty hours in the 90-day engagement counted?

Netsujo’s standard human work — close review, finalising recommended improvements, implementation support, and post-launch checks — is capped at up to ten key pages and a total of thirty hours, whichever limit is reached first, at which point the standard work is complete. Additional work is quoted before it starts. This cap is separate from the automated site-wide diagnosis.

Do we need to replace our existing web agency?

No. Because SIGNAL organises the findings and the recommended improvement, your existing agency skips the root-cause investigation and moves straight to quoting and implementing.

Which CMSs and site setups do you support?

Common CMSs such as WordPress, STUDIO, and Peraichi. For custom-built sites or sites managed in GitHub, we work through recommended improvements, code diffs, or pull requests depending on the site and the access granted.

Do you guarantee rankings or inclusion in AI answers?

No. Search results and AI answers vary with each service’s specification, the competitive landscape, the exact question, and the point in time. We provide evidence-based findings, implementable recommended improvements, and post-implementation measurement — not guarantees of rankings, AI citations, enquiries, or revenue.