Multilingual Website Delivery Evidence

The project and the choices behind it

This is ZequnWeb's own production website, designed to explain services, pricing, work and contact options to global, Hong Kong and Japanese buyers. The work includes information architecture, frontend implementation, translated content, language routing, structured data and enquiry interactions.

English and Simplified Chinese each had 45 pages in the sample; Hong Kong English, Hong Kong Traditional Chinese and Japanese each had 21. Pages are published at separate URLs. Equivalent pages link to one another; a distinct Japanese service does not point to an unrelated English page merely to fill a language slot.

How the published check was performed

At 03:02:51 UTC on 5 September 2026, the site's sitemap was fetched and its 153 page URLs were requested directly. An automated HTML check inspected response status, titles, descriptions, canonical links, H1 counts, indexing directives, image alt attributes and JSON-LD syntax. Language targets and return links were compared within that collection.

All 153 final responses were HTTP 200. No missing title or description, duplicate title or description, mismatched self-canonical, missing alt attribute, JSON-LD syntax error or failed language relationship was found by these checks. This does not validate the quality of every image description or every structured-data assertion. Source sections were present on 53 blog articles and two service pages.

The check and this explanation were prepared with automated tools and AI assistance. This is a dated, self-published implementation record. Its downloadable rows let you inspect the scope and repeat the checks; it is not independent certification. Pages added later are outside this snapshot.

Three decisions a buyer can inspect

Language architecture: compare the English, Chinese and Japanese GlobalAxis concept pages. Each version has its own readable URL and corresponding language links. The Japanese service pages explain their own delivery scope rather than copying every global service page.

Price answers: the Japanese English-website cost guide leads with the studio's published JPY examples and explains the fixed reference conversion and exclusions. It does not present the studio's prices as a market average.

Content evidence: article source notes distinguish an official technical reference, the studio's own prices and an independent design concept. A reference supports the named point; it does not independently verify every commercial claim on a page.

What counts as an enquiry

Preparing or opening an email draft is an interaction; the visitor still has to send it. In the receipt-based form implementation, a received-enquiry event requires an explicit response tied to that submission. A generic HTTP 200 or a failed request does not establish receipt.

The flow was tested locally with a simulated receiver: simultaneous submits were locked, errors did not produce a successful lead, and a matching receipt did. These tests do not establish real inbox delivery. A configured receiver and production verification are needed before reporting confirmed enquiries; a received enquiry is still not a qualified lead or a sale.

What these results do not establish

This record contains no measured improvement in Google positions, indexed pages, organic traffic, AI citations, enquiries or revenue. It also does not report a Core Web Vitals field-data pass or a complete accessibility audit. Those outcomes require their own data and observation periods.

The studio is responsible for the information it publishes. Technical sources are linked near the relevant guidance; prices describe the published scope and observation date. Independent concepts are labelled separately from client work. Client outcomes and testimonials require permission and supporting records before being treated as verified evidence.

Compare the implementation

• English B2B concept
• Chinese B2B concept
• Japanese B2B concept
• Japanese cost guide
• Current sitemap

Google Search Central — hreflang

Questions about the evidence

Discuss a multilingual website

Share the target market, existing site and content you can publish. We can use these checks as a starting point for an agreed delivery scope.