A domain may look clear in a proposal but prove awkward when a client tries to type it from a site sign. If you have to explain a hyphen aloud, the spelling is easy to mishear, or the name ties a practice to a city it may leave, test alternatives before printing it on drawings and stationery. You can change a domain after launch, but doing so means updating email, project documents and existing links.
Start with the organisation the domain must represent
An architecture practice, a property owner and an individual development may each need a different kind of name. A practice website will usually use the established trading name. A project website might use the development name instead, once the team has confirmed it can be used publicly. For a public building, check who will own the domain and whether the name follows the client’s approved naming conventions.
Think about how long the site will be needed and what it may need to cover. northquayhousing.example would be too narrow for a firm that may later design schools or healthcare facilities. A project microsite, on the other hand, need not list every service its developer offers. Before generating names, write down the intended audience, the site’s purpose and its expected owner. Those constraints are more useful than a list of fashionable words.
Make it easy to recognise, say and type
Short helps, but clarity matters more than an arbitrary character count. Look at candidate domains in lowercase, as visitors often see them. Words that appear separate in a logo can run together in an address. Avoid spellings with several plausible versions, unexplained abbreviations and numbers that could be typed as digits or words.
Try saying the address once to someone unfamiliar with it, without spelling it out, and ask them to write it down. Then see how it looks in an email address, on a drawing title block and on a small mobile screen. A name needs to work in those everyday settings, not just at logo size.
Use keywords only when they clarify the name
Words such as “architecture,” “studio” or “homes” can help explain an unfamiliar brand. Piling on descriptive terms, though, makes an address cumbersome. You do not need to squeeze a service and location into the domain for search visibility; relevant page content, clear business information and a usable site can explain those details.
Be especially careful with place names. A neighbourhood or city may make sense for a project based in one location, but it can misrepresent a practice that works across regions or become dated if the organisation moves. Use a geographic term when it is part of the lasting identity, not as a shortcut to being found.
Choose an extension with the audience in mind
The extension comes after the final dot. A country-code extension can signal a national market and may suit an organisation whose work and clients are concentrated there. A familiar generic extension may be easier for an international audience to remember. Other endings can work too, but check whether clients are likely to type a different one and whether eligibility or registration conditions apply.
An extension does not establish professional status. It is part of an internet address, not proof of an architect’s licence, property title or permission to use a protected name. If the preferred extension is unavailable, a clear variation on the organisation’s name may work better than a confusing address with an unfamiliar ending. Registering a few obvious variants can reduce misdirected visits, provided someone will maintain them and redirect them to the primary site.
Check availability beyond the registration screen
Availability to register is not the same as permission to use a name. Search for similar organisations in the relevant markets and check applicable company-name and trademark records. Take particular care if another architecture or property business has a name that sounds the same, even under a different extension. If the risk is material, get qualified legal advice before paying for signage or launching publicly.
Look into the domain’s previous use, too. An older registration may have links pointing to it, archived pages from another business or a reputation affected by unsolicited email. Those issues do not automatically rule it out, but they may mean cleanup work. Check spelling variants for unintended meanings, including in languages the intended audience uses.
Keep a short comparison record so the decision does not rest on memory:
- Identity: Does the name match the entity responsible for the website?
- Clarity: Can someone hear it once and type it correctly?
- Longevity: Will it still fit if services, location or project ownership change?
- Risk: Are similar names, earlier uses or registration restrictions apparent?
- Operations: Who will control renewal, email settings and access to the registration?
Register it as a long-term business asset
Register the domain through an account the organisation controls, rather than a personal account held by an employee who may leave or an external consultant. Record the registrant, administrative contacts, renewal date and payment method in an accessible asset register. Turn on multifactor authentication where available and keep recovery details current. A missed renewal can disrupt the website and email, including addresses printed on tender submissions or permit correspondence.
Choose the primary domain before publishing. Redirect any spelling variants or other extensions to it rather than running duplicate sites. Check that email addresses use the intended domain and that staff know which address to give clients. If you later change an established domain, plan the redirects, email continuity and document updates separately; registering the new name does not move those services.
Before approving a candidate, put the full address and a sample email such as [email protected] into the next drawing issue template. Read both aloud. If either needs an explanation to be understood correctly, revise the name before it reaches the title block.