Hmlet AEO Assessment Report
by Novastacks AI

None of the three domains is blocked or client-side-only -- all render server-side and remain bot-accessible, so this is not a crawler-access problem. The dominant issue on hmlet.com is architectural: the domain a Singapore search or AI citation would land on serves Hmlet's Japan business, with no navigation link to any of the six live Singapore properties or the separate singapore.hmlet.com homepage. Layered on top of that, the apex page itself is slow to finish painting its largest element -- well outside Google's 'good' threshold, which drags down both user experience and crawl efficiency on the one page most likely to be indexed for the brand.

Every hmlet.com page tested is missing its H1 tag entirely, and the one page built specifically for the Singapore listing carries a title tag that still appends "| Hmlet Japan" to Singapore content -- a branding bug bleeding from the Japan template. singapore.hmlet.com, the live Singapore-market homepage, has no canonical tag and no semantic HTML structure at all (no nav, main, article, section or footer element), which both weakens how cleanly AI crawlers can parse the page and removes signals both competitors ship as standard.

Across every page type tested, hmlet.com carries no structured data at all -- no Organization, no LodgingBusiness, no FAQPage markup anywhere on the domain estate. Coliwoo runs a comprehensive schema set (15 types, including FAQPage and AggregateRating) on nearly every page type; Cove runs a lighter but real baseline (Organization and WebSite on its homepage and blog). Hmlet has neither.

Language tags (hreflang) tell Google which version of a page to show in each market. hmlet.com declares them on its two homepages only (Japanese, English, and a default that points to Japanese). None of the 12 inner pages tested carries them, and none carries a canonical tag, so Google has to guess which language version of each listing to show in Singapore, Hong Kong and Japan. Addresses for other languages return a "Page not found" screen with a success status (HTTP 200).

On the city listing pages, each apartment card opens its unit page through a JavaScript click handler. There is no link element behind any card, so search engines and AI crawlers that follow links cannot reach a single unit from the listing. The sitemap does not fill the gap for Hong Kong or Singapore: it lists no unit from either city.

hmlet.com has no robots.txt and no llms.txt: both addresses return the HTML "Page not found" screen. Any address that does not exist returns HTTP 200 instead of 404, so removed or mistyped pages stay open to indexing. The sitemap is one flat file of 149 entries; every entry was requested on October 13, 2026.

The title bleed on the Singapore listing page also appears across Hong Kong. The Hong Kong city page is titled "Furnished Apartments for Rent in Hong Kong│Hmlet Japan", and Hong Kong unit pages follow the same pattern, for example "Po Foo Building│Fully Furnished Apartment│Hmlet Japan". Hong Kong unit pages also have no meta description.

Hmlet's content is spread over five hosts. Links between them are thin, and none of the 18 pages tested across them carries structured data.

As a signal test, we ran the 3 core Singapore coliving category terms through live search: "coliving singapore", "flexible rental apartment singapore", and "furnished serviced apartment singapore short term". Hmlet is absent from the top 20 organic results on all 3; Coliwoo and Cove occupy top-3 slots on every one of them (Coliwoo ranks #1 on two of the three).

Hmlet's single largest Singapore traffic driver is "owen house by habyt previously hmlet" (6,600 monthly searches, the highest estimated traffic value of any keyword on the domain), followed by "habyt novena previously hotel balestier" (2,900 searches). Both are searches about Hmlet's own brand-name transition -- Habyt to Hmlet -- not about coliving as a service. Meanwhile the page a Singapore search would actually land on, hmlet.com/en, presents as a Japan corporate rental brand. The traffic that exists is driven by brand-name confusion, not by category demand the way it is for both rivals.

hmlet.com shares only 24 ranked keywords with coliwoo.com and 25 with cove.sg in the Singapore market -- against Coliwoo's 1,281 total ranked keywords and Cove's 2,630. Where the sets overlap, Hmlet trails on almost every term: "dormitory in singapore for rent" (Hmlet #50 vs. Coliwoo #19), "short term rent room" (Hmlet #48 vs. Cove #2), "communal living near me" (Hmlet #32 vs. Coliwoo #1). The overlap itself is thin, and Hmlet loses most of the keywords it does share.

Despite the overall gap, three of Hmlet's own property names outrank Cove on shared keywords: "habyt novena" (Hmlet #3 vs. Cove #54), "habyt studios at novena" (Hmlet #2 vs. Cove #45), and "habyt studios kallang" (Hmlet #2 vs. Cove #59). Volumes are modest (110-590 monthly searches), but they show the individual property content itself ranks well when it has a clean, singular keyword to answer -- the gap is reach and architecture, not the underlying property pages.

Cove's header links to sister sites in Japan (covejapan.com), Korea (covekorea.com) and Indonesia (cove.id). covejapan.com is a Japanese language rental site for homes in Japan, with English support, no guarantor and no key money: the same offer Hmlet makes on hmlet.com. For renters in Singapore and Hong Kong looking for a home in Japan, Cove is a direct competitor, and it already runs separate sites per market.