A company’s public website shows more about its operations than most owners expect, and less than most observers assume. From outside you can check whether the domain and email are set up properly, whether search engines can understand the site, whether the contact path leads anywhere, and whether the Japanese and English versions agree. You cannot see the sales process, the customer data or the people doing the work. A good review separates what it found from what it is guessing.

That distinction matters in Japan, where large and well-known companies often run sites that look expensive and work badly. Some of those companies are doing fine. Their business arrives through relationships, trading partners and long-standing contracts, so a weak site costs them little. The trouble starts when smaller companies copy that model and assume the brochure is the professional standard. A 20-person firm that depends on inquiries cannot afford the same indifference.

What can you tell about a business from its website?

A surprising amount is public. None of it requires special access, and most of it takes minutes to check.

Domain and email setup

Every domain publishes DNS records. From them you can see where email is hosted, whether SPF and DKIM are configured, and whether a DMARC policy exists. These three records tell receiving mail servers whether a message claiming to come from the company is genuine. A missing DMARC record, or an SPF record that breaks because it references too many services, means the domain is easier to impersonate and ordinary mail is more likely to land in spam.

This stopped being a technical nicety in 2024, when Google and Yahoo began requiring authentication from senders to Gmail and Yahoo Mail, with DMARC required for bulk senders. A company that invoices clients by email, sends newsletters or recruits staff has a direct interest in getting it right.

Search structure

View the source of a few pages. Check whether each page has its own title and description, whether headings follow a sensible order, and whether there is structured data telling search engines what the organization is, where it operates and what it sells. Duplicate titles across hundreds of pages, or an H1 used for the logo on every page, tell you nobody has looked at how the site appears in search.

The contact path

Fill in the contact form, or read where it goes. A form that sends to a generic address, with no confirmation email and no stated response time, usually means inquiries land in a shared inbox that several people read and nobody owns. A “Login” or “Member” link that leads to a PDF or an outdated third-party tool says something similar about the systems behind it.

Language versions

Many Japanese company sites have a Japanese version and an English version that were built separately, by different vendors, at different times. Navigation differs, content exists in one language and not the other, and the English news page stopped updating years ago. That is rarely a translation problem. It shows that no one owns the site as a single system.

Maintenance

Broken links to the company’s own executives, a copyright year from 2019, a CMS version that no longer receives security updates, an expired certificate on a subdomain. Each is minor. Together they show whether anyone is responsible for the site after launch.

What a website cannot tell you

Outside evidence has limits, and it is easy to overreach.

A weak site does not prove a weak business. Plenty of capable Japanese companies win work through introductions, trade relationships and repeat customers, and their real operations live in private systems a visitor never sees. A strong site does not prove a strong operation either. A creative agency can produce an impressive front end for a company whose order handling still runs on fax and spreadsheets.

So a public review should report what it can observe (records, markup, broken paths) and treat anything about internal operations as a question to ask, not a conclusion. The useful output is a list of things to verify with the people who run the business.

Why does the gap between website and operation matter?

For a large incumbent, a brochure site is mostly a missed opportunity. For a smaller company, the gap has real costs.

Staff become the missing system. If the site cannot answer common questions, route inquiries or take bookings, people do it by hand. The phone rings with questions the site should answer. Someone copies form submissions into a spreadsheet. Someone else confirms appointments one email at a time. The business looks labor-intensive because the website pushes the work onto staff.

Official tools get bypassed. When company email is unreliable or awkward, employees move client conversations to personal LINE, personal Gmail or a free chat tool. The work continues, but the company cannot see it, keep it or recover it when someone leaves.

Paid traffic replaces organic reach. A site that search engines cannot understand does not rank, so the company buys visitors through ads. That works while the budget lasts and stops the day it ends. Content and structure that search engines can read keep producing inquiries without a monthly bill.

Trust erodes at the first click. Customers, partners and job applicants judge a company by whether its public tools work. A dead link or an unanswered form does more damage than a plain design.

What does a business website in Japan need behind it?

The visible site is one part of a small system. For most Japanese SMEs, the parts that matter most are behind the design.

A domain and email the company controls. The domain should be registered to the company, not to a former employee or the agency that built the site, and someone should know where the login lives. Email should run on Google Workspace or Microsoft 365 with SPF, DKIM and DMARC configured. The Google Workspace adoption guide covers the setup.

Pages that answer real questions. Services, prices where you can publish them, service area, lead times, and how to start. Published prices build trust with clients who need a quote approved internally, and an unfamiliar product needs the same practical answers that made the washlet easier to adopt. Each page should have a unique title and description, sensible headings and basic Organization or LocalBusiness structured data.

A contact path with an owner. Form submissions should go to a named person or into a CRM, send the customer a confirmation, and have an agreed response time. If you take bookings or payments, connect them to the site instead of handling them by email.

Required legal pages. A privacy policy that reflects the Act on the Protection of Personal Information, and, if you sell online, a 特定商取引法に基づく表記 (Specified Commercial Transactions Act disclosure).

One system for both languages. If you publish in Japanese and English, keep one structure with the language as a layer, so updates reach both versions.

A platform your team can maintain. Choose the CMS for the people who will update it. A simple site your staff can edit beats an ambitious one that only the original agency understands. I compare two common options in Webflow vs WordPress for Japan.

Someone responsible after launch. Renewals, updates, broken links and form testing need an owner and a calendar, even if that work takes an hour a month.

How to review your own website

Start with the checks anyone can run. Look up your DMARC record with a free DNS lookup tool. Submit your own contact form and time the reply. Open your site on a phone over mobile data. Search for your company name and main service and see what appears. Click every link in your footer. Compare the Japanese and English navigation side by side.

Then ask the internal questions a visitor cannot answer. Who owns the domain registrar account? Where do form submissions go, and who reads them? Which tasks does staff do by hand because the site cannot? If the agency disappeared tomorrow, could anyone update the site?

A Diagnostics review covers both halves: the public evidence and the internal systems behind it, including domains, email, forms, bookings, payments and the tools staff use to handle what comes in. If the review shows the site needs rebuilding or reconnecting, I can plan and carry out that work with your team. You can also describe what you are dealing with.

Further reading: building a visual identity for a business in Japan · how clear service pricing builds client trust · making an unfamiliar product easier to adopt · digital infrastructure as a business asset and a risk