
Five property pillars and five journeys
HDB, condominiums, landed, investment and commercial pillars, plus journey pages for first-home buyers, upgraders, investors, sellers and commercial property, joined by a journeys hub.
How InfinitusNow launched GleniceToh.sg in August 2026, and put the measurement system in place to prove outcomes over time.
Early-stage case study. The site launched on 4 August 2026. Measurement records used in this case study begin in the first week after launch. Figures are as of the dates stated.


A property adviser's website has three jobs. It has to help buyers, sellers and landlords understand where they stand. It has to be readable by search engines and AI assistants. And it has to give the business a way to find out whether any of it is working.
For GleniceToh.sg our goal was to do all three, and to be disciplined about what we could and could not prove.
InfinitusNow built and launched GleniceToh.sg, which went live on 4 August 2026. Over the following three months the site's structure grew from 11 sitemap URLs at the 3 August repository baseline to 35 at our 11 November 2026 check.

HDB, condominiums, landed, investment and commercial pillars, plus journey pages for first-home buyers, upgraders, investors, sellers and commercial property, joined by a journeys hub.

Organised under those pillars.


Affordability, stamp-duty (BSD and ABSD), mortgage and seller-proceeds calculators, plus a planner that keeps a visitor's saved plan in their own browser.
Pages and copy structured around the specific questions property buyers and sellers ask.

A tool that shows remaining lease for HDB and condominium properties, built on government datasets, with an optional illustrative value view. It is illustrative, not a valuation.
An AI property assistant, built with guardrails and covered by automated tests.
We treated measurement as part of the build, not an afterthought:
llms.txt file, its structured data and its MCP manifest.The principle was simple: instrument first, claim later.
Each statement below is tied to a dated record.
sitemap URLs
3 Aug 2026 repository baseline to the 11 Nov 2026 check
dated technical snapshot: HTTP 200, self-canonical, well-formed JSON-LD
Check of 11 Nov 2026. Our own structural check, not Google validation
weekly readiness audits passed
16 Aug–8 Nov 2026, UTC dates. A readiness check, not a measure of visibility
The first 90 days established the measurement baseline.
Search visibility is still early. The available evidence does not support claims of ranking growth, traffic growth, AI-visibility growth, enquiries or revenue yet, and it does not support any claim of causation. We are not making those claims, and we are not attributing any movement in those measures to the work.
That is a deliberate boundary on what we claim, not an attempt to turn early signals into outcomes. The domain had no pre-launch Search Console history to compare against, and the site changed continuously through the period. In those conditions an upward line would prove very little. What we do have is a site built to be measured, with the measurement already running.
Whether the implementation translates into durable visibility is what the ongoing measurement is designed to establish.
Shipping is not a result. Implementation facts (what was built, when, and how it checks out) and measured outcomes (what changed for the business) are different things, and a case study should keep them apart.
Build so that outcomes can be measured from day one, then let the measurements decide what you are allowed to say. That is the approach behind InfinitusNow's Assessment and the ongoing, scheduled measurement in DIP.
