A Japanese construction company's site, rebuilt in its own language, then referred to the whole industry board.

Before

An outdated site with unreadable text over photos, a broken mobile layout, a Google listing pointing at the wrong domain, and a contact form that had never delivered a single inquiry. Every content change meant emailing photos to a developer and waiting days.

The build

• 6 pages rebuilt in Japanese for mobile and desktop, with the hero and legibility problems fixed and new project photography added as before-and-after cards.
• Shipped to their existing host with a one-command deploy that backs up first, mirrors, and health-checks every page.
• Google Search Console set up and the Google Business Profile corrected to the right domain.
• Next: a flat-file CMS with a Japanese admin panel so the owner posts a project herself, and the dead contact form fixed with it.

Before and after

How it's built

Architecture

A static site on the client's existing shared PHP host, deployed by mirror with a backup taken first and a health check of every page after.

Where it runs

The client's own hosting. Nothing of ours in the loop.

Tests and evals

Every deploy verifies all 6 pages return 200 and the search-console verification file is intact.

Cost and latency

The client's existing hosting. No new subscriptions.

Guardrails

Never delete the search-console verification file. Backup before every mirror. The deploy script changes into the directory first, because the mirror tool silently no-ops on paths with spaces.

The tradeoff we chose

Why this way and not the other

Kept their host and a static site instead of moving them to a builder. The owner's team is not technical; the cheapest thing to maintain is a folder of HTML they own, plus a small CMS later for the one job they actually do themselves: posting a finished project.