Building a bilingual Tokyo property portal people can actually use

Choose the first audience deliberately

A renter arriving in Tokyo, an overseas owner seeking management and a company looking for an office need different information. Pick one primary journey for a first release. Define the useful outcome: a better shortlist, a well-formed enquiry or an informed discussion with a qualified provider.

Then decide which information the business can keep accurate. A small, maintained inventory or a useful editorial resource can serve readers better than a large set of unverified listings. Domain breadth is useful for future expansion, but it does not remove the need for an initial focus.

Translate the data model, not only the headlines

Keep a common identifier for each property or article and store language-specific text separately. Addresses, area measurements, dates and listing status should remain consistent. A correction to a factual field should reach both language versions. Avoid publishing an English summary that silently omits a condition present in Japanese.

• Use stable, descriptive URLs for each language.
• Link equivalent pages directly rather than sending every language switch to the homepage.
• Keep required enquiry fields understandable in both languages.
• Label the actual support languages available.
• Explain unfamiliar terminology without changing its meaning.

Make trust visible in the interface

Show where information came from and when it was checked. If a listing is no longer available, say so rather than accepting an enquiry that cannot be fulfilled. Identify the provider responsible for a transaction and separate paid placements from editorial information. Useful content should remain available in readable HTML even if an interactive feature fails.

MLIT’s multilingual rental material illustrates why language access matters. It is a source to consult and link, not a replacement for accurate provider-specific documents. Google’s guidance also emphasizes accessible text, internal links and structured data that matches what readers can see.

Where property.tokyo could fit

The name combines an English property category with Tokyo’s geographic extension. A buyer could use it as a primary portal, a separate campaign or an editorial destination. Those are product concepts, not existing services or guaranteed demand.

A sensible acquisition decision considers the wider project: verified data access, editorial capacity, service delivery and a reason for people to return. A domain is a useful address for that work; it is not a substitute for the work itself.