Skip to main content

When consultation booking returned a 404

Netsujo Inc. ·

When consultation booking returned a 404

On November 16, the booking links on Netsujo’s Japanese consultation and pricing pages resolved to a missing path on our own site and returned a 404, although both pages loaded. A visitor needed to reach the external booking page from either entry point. We defined the scope for recovery as four booking link locations on the consultation page and one on the pricing page. The unit we counted is a link location on the page.

We checked from the public page to the booking destination in this order.

  1. Href in the delivered HTML: the booking links contained a value that could not be used as an external booking URL. Confirmed.
  2. Resolution in the browser: the browser resolved that value as a relative path on our site, which returned a 404. Confirmed.
  3. Hand-off in the source: the page passed the public setting it received at build time directly into the link. Confirmed.
  4. How the setting appeared in the management interface and API: that view alone did not show where the invalid value first arose internally. Not identified.

What we confirmed is the path by which an invalid string reached the public link and caused the 404. What we could not identify is the internal step where that string first arose in the setting.

Restore the setting and verify the recovery

On November 16, we corrected the setting to the valid booking URL and redeployed the same source version through our standard production process. Then we checked the links and the external destination from the public site under the same signed-out conditions as a visitor.

Restore the setting and verify the recovery
Visitor entry pointWhat we confirmed after the November 16 recovery
Four links on the Japanese consultation pageLink target is the TimeRex booking page, for all four
One link on the Japanese pricing pageLink target is the TimeRex booking page
External booking pageThe booking page loaded and returned HTTP 200

Acceptance covered opening the external booking page. We did not submit a booking, and we did not confirm any effect on sales conversations or revenue.

On November 18, we merged a guard into the source to prevent a repeat. The booking link is shown only when the setting validates as a well-formed TimeRex booking URL. These are representative checks, not an exhaustive list of conditions.

  • The scheme is https.
  • The host matches the booking service.
  • The URL contains no user information and no port.

If validation fails, the link is hidden and the inquiry form stays available. We verified this invalid-value fallback in an isolated environment.

The same day, we released that version to production. Production acceptance confirmed that all five links—four on the consultation page and one on the pricing page—opened the TimeRex booking page under signed-out visitor conditions. We did not submit a booking or confirm any effect on sales conversations or revenue in this acceptance. We do not publish the setting value in this article. The current entry points are on the public site. Consultation page (Japanese) and pricing page (Japanese).

Discuss a broken booking flow as AI implementation work

When an issue spans a website and an external service, the first thing we trace is the action the visitor could not finish. Netsujo can help investigate a broken booking path, implement the repair, and verify the journey on the public site.

Discuss a broken booking flow as AI implementation work