From Website Audit to Verified Change: A Pricing Display Fix

Website audits routinely produce long lists of issues. Yet a report has limited practical value when no one can turn its findings into a specific, approved change. The site stays as it was, and the business owner cannot tell who should act or how the result should be accepted.

On October 15, 2026, Netsujo found a small inconsistency in the presentation of Netsujo SIGNAL's subscription price. A pricing comparison displayed the monthly amount of JPY 70,000 before tax, while the FAQ also showed JPY 77,000 including tax. Both figures described the same plan, but the information available to a visitor varied by location.

We subsequently aligned the Japanese and English displays while keeping the approved price and contractual conditions intact. The change went through development checks and independent review. The live Japanese pricing page now displays both the pre-tax and tax-inclusive monthly prices.

This is a useful case because the business problem, implementation boundary, technical evidence, and remaining uncertainty can all be described precisely. Below is the workflow we drew from that one change.

The initial finding: consistent prices, inconsistent explanations

A tax-exclusive amount of JPY 70,000 and a tax-inclusive amount of JPY 77,000 are consistent at the applicable 10% tax rate. The problem was how completely that information was presented at each point in the visitor's journey.

Someone evaluating a service may use only the summary card, compare it against another provider, or read an FAQ while preparing an internal purchase request. An omitted tax-inclusive figure can add an extra verification step or lead to an incomplete comparison. That is a plausible user-experience risk. We have no evidence of an actual mispurchase, lost deal, or confused customer caused by this presentation.

Before proposing an edit, we asked three questions:

1. Which price is the approved product price?
2. What exactly appears in the summary, plan details, FAQ, and translated content?
3. How can we make the display consistent while preserving the product and purchase terms?

These questions made the work substantially narrower. We needed to improve how an existing price was explained; we had no reason to change the product itself.

Separate the product's source of truth from the text that displays it

A pricing change can affect more systems than the page a visitor sees. In some products, prices are referenced in checkout, plans, contract documents, structured data, and emails. A content correction should have a clear boundary to avoid accidentally turning it into a product change.

For this particular work, we defined the following scope:

This division is useful when working with an existing web development agency. The company can approve the facts and commercial terms, while the developer can implement the agreed presentation and prove what changed.

Write one change specification that someone can accept

A developer needs a more precise request than “make the pricing clearer.” We translated the observation into a bounded change specification. The following is an editorial reconstruction of the implementation scope, not a reproduction of an internal ticket.

The central advantage is accountability. A reviewer can compare the finished page against an explicit expected result. A developer can quickly identify which shared components and language resources are within scope. The release owner can verify the published result instead of assuming a merged PR automatically updated the live page.

What we changed in the site repository

The actual work was tracked in Netsujo SITE pull request #587, in a private development repository. Its changes were limited to three source areas: the Japanese pricing page, the shared SIGNAL plan-summary display, and the English pricing copy.

The Japanese comparison and plan sections were aligned to show both amounts. The shared summary was made consistent with the existing price source. The English presentation was updated to convey the corresponding tax treatment.

We also corrected a broad pricing note. Once some amounts explicitly include tax, a statement suggesting every listed amount is exclusive of tax becomes confusing. The revised note accounts for amounts explicitly marked as tax-inclusive.

This illustrates a recurring source of regression: a change that appears to involve one sentence may have counterparts in shared components, localized content, supporting explanations, and metadata. Those related representations should be inspected before the diff is considered complete.

What source tests establish—and what production verification adds

The PR contains records of relevant typechecking, lint, hosted CI, and independent quality review, and it was merged. Those records establish that the specified development checks accepted the reviewed change.

Production verification asks an additional question: what can an anonymous visitor actually read on the canonical domain? On October 18, the published Japanese pricing page showed both JPY 70,000 before tax and JPY 77,000 including tax in the relevant pricing sections. The corresponding English pricing page was also publicly accessible.

We track these as separate stages:

A comprehensive release acceptance for a larger pricing change might include mobile display, links, plan selection, checkout behavior, structured data, and language switching. Our publicly reported readback only supports the surfaces actually observed.

Five checks that reduce rework before implementation

Verify the approved business source. Compare the public wording with authorized product, contract, and payment information. A discrepancy in presentation should never trigger a speculative price update.

Inventory reused representations. Search for shared cards, FAQs, translations, and other displays. Decide whether each requires a code change or only verification.

Protect adjacent business behavior. Mark billing, account lifecycle, other plans, and signup flows as preserved unless the change is separately authorized.

Specify the release evidence. Record the reviewed revision, relevant checks, deployment outcome, public URL, and time of readback.

Define safe recovery. If a published display conflicts with approved terms, agree how to restore the last accepted wording while investigating the cause.

These steps apply equally well to service descriptions, eligibility information, delivery periods, and contact instructions.

Measuring results requires a separate question

The observable result in this case is that the information shown to readers became consistent. There is no measured causal evidence that inquiries, conversion rates, rankings, or revenue improved because of this correction.

If we were measuring that impact, we would compare periods and traffic segments with equivalent tracking, account for concurrent site changes, and distinguish CTA clicks from successfully received and qualified inquiries. Low traffic would make short-term differences particularly difficult to interpret.

Search ranking is a weak direct proxy for clarity of a pricing explanation. Where possible, metrics should be chosen close to the actual user decision being improved.

Start with one page and one accepted change

Look for an inconsistency that can be resolved without restructuring the whole site: a service description, an eligibility requirement, a tax label, or a different explanation between the main page and FAQ. Identify the approved source, the precise URLs and components, the person authorized to approve the correction, and the release acceptance conditions.

Those five pieces of information can turn a broad audit recommendation into a concrete development request.

Netsujo SIGNAL is designed to connect website observation, prioritized issues, actionable change specifications, implementation responsibility, and post-release verification. The client or its existing web agency may perform the actual production change; Netsujo's implementation role depends on the agreed service scope.

If you want to identify the first meaningful improvement on your site, start with the SIGNAL service information and free website diagnostic.

If you already have a specific page or improvement in mind, contact Netsujo with its URL, the issue you observed, and what you want to verify after the change.

---

*Editorial evidence note, October 18, 2026: This case is based on Netsujo SITE PR #587 and the published pricing pages. The development repository is private. The recommended change-specification and measurement workflow is an interpretation of the case. No ranking, inquiry, or revenue uplift is claimed.*