Our Own Case: hkunifi.com — The GEO Foundation Behind Our UniFi Store, and How to Verify It

This time, the case study is ourselves.

GNS-GEO has opened its own UniFi store, hkunifi.com, operated by GNS Technology Limited and built with exactly the same GEO stack we deploy for clients.

The direct answer: this article publishes no AI citation percentages. A first-party asset should not be presented with a number that no third party has verified. Instead, it lists what hkunifi.com actually has in place, how you can check each item yourself, and the new two-way entity link we added. The things still unfinished are listed too.

Background: what the store is

hkunifi.com is GNS Technology Limited's own UniFi product store, serving Hong Kong offices, shops, schools and clinics with UniFi hardware, solution design, professional installation and a monthly managed service.

As with any client project, launching the site is only the starting point. What actually determines whether AI recommends a site is whether it supplies machine-readable facts. Here is the groundwork we put in.

Seven verifiable pieces of GEO groundwork

Every item below can be checked right now, with no tools — only a browser:

#	Item	What is actually there	How to check
1	AI crawler policy	robots.txt explicitly allows 14 AI crawlers one by one, including GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, Google-Extended, Bytespider and CCBot	Open hkunifi.com/robots.txt
2	llms.txt	A ~9.6KB llms.txt listing the website, operating company, service area, languages, phone, email, WhatsApp and address in a structured format	Open hkunifi.com/llms.txt
3	Sitemap and language annotations	sitemap-index.xml → sitemap-0.xml (~152KB), with hreflang annotations on each URL (zh-Hant-HK / en)	Open hkunifi.com/sitemap-index.xml
4	Structured data	Home page JSON-LD includes Organization, FAQPage, WebPage, Offer, PriceSpecification, PostalAddress, GeoCoordinates, ContactPoint and OpeningHoursSpecification	Open the home page → view source → search application/ld+json
5	Consistent entity data	Company name, address and phone match the group's other sites (GNS Technology Limited, 550 Castle Peak Road, Lai Chi Kok, Kowloon)	Compare the contact pages of hkunifi.com and gnstec.com.hk
6	External profiles	Organization sameAs lists 10 external profiles, including the corporate site, the Price.com.hk shop, Facebook, LinkedIn, GoodFirms, HSBC BusinessGo, Sortlist, Clutch and Google Maps	Same JSON-LD block as item 7
7	Two-way entity link (new)	hkunifi.com's sameAs now includes geo.gnshk.com, and geo.gnshk.com's sameAs now includes hkunifi.com	Search each site's source for the other's URL

What is new: linking both sites to one entity

This is the point of the article.

hkunifi.com's Organization already declared that it shared an entity with gnstec.com.hk, but it made no mention of geo.gnshk.com at all — we checked, and the count was zero. In the other direction, geo.gnshk.com never mentioned hkunifi.com either.

In other words, to a machine, GNS-GEO looked like a single website claiming to do GEO, rather than a service offered by a company with real operations, a store and a corporate site.

What changed:

• hkunifi.com's organization.same_as now includes https://geo.gnshk.com/ (in both the zh-HK and en settings)
• geo.gnshk.com's Organization sameAs now includes https://hkunifi.com

The effect: after building, 602 of 603 pages on hkunifi.com carry an entity declaration pointing at geo.gnshk.com.

Why both directions? Because entity merging needs clear, mutually corroborating signals. A one-way declaration only says "A claims a link to B". A two-way declaration, combined with matching address, phone and company name, is what lets AI confirm these three sites belong to one real entity.

What is not finished (stated plainly)

A case study that lists only strengths is not worth trusting. These are the problems this check found and that are still unresolved:

Issue	Impact	Status
/sitemap.xml returns 404	Only sitemap-index.xml is served (the Astro default), so anyone typing /sitemap.xml by hand or with a tool hits a wall. This is the same class of problem we fixed on geo.gnshk.com and gnstec.com.hk	To fix (needs a 301 redirect)
No performance figures (now updated)	AI citation coverage, rank and share of voice for hkunifi.com are now being monitored; the first 8-day figures are in the 30.09 results update	First figures published (sample still small)
No visible on-page link to geo.gnshk.com	Only the machine-readable sameAs declaration exists so far; there is no human-visible cross-link yet	Planned

We will fix the /sitemap.xml 301 first, because it affects both crawlers and manual checks.

Why a first-party case is still worth publishing

You might ask: it is our own website, so we can say anything — what is it worth?

The difference is how verifiable it is:

• Client cases: confidentiality limits what can be said, and figures need client approval before publication
• First-party cases: everything can be published, including the settings, the source code and the unfinished parts

For AI, a page that can be opened and checked item by item is more useful than a performance claim that cannot be verified — because citation requires extractable, cross-checkable facts.

We also state it plainly: hkunifi.com is operated by GNS Technology Limited itself, and we do not present it as a third-party client case.

A checklist you can run on any site

Whichever provider you use, these six checks are worth running once:

• Does robots.txt explicitly allow AI crawlers (not block GPTBot, ClaudeBot or PerplexityBot)?
• Is there an llms.txt, and are the company name, phone and address in it correct?
• Does sitemap-index.xml return 200, and does /sitemap.xml work too? Many sites only do half
• Does the home page source contain application/ld+json with Organization and FAQPage?
• Are the company name, address and phone identical across all platforms?
• Does sameAs list your other stores, corporate site and external profiles?

If two or more of those are missing, there is clear room to improve.

Common questions

Q: Is hkunifi.com being recommended by AI yet? A: The groundwork is complete and monitoring has started; the first figures are in the 30.09 results update. Eight days is still too small a sample to call a direction, so we monitor weekly on the same scope and will judge on the 4-8 week trend. A single screenshot without an adequate sample should never be treated as proof of performance.

Q: Can I copy what hkunifi.com has done? A: Yes, and you are welcome to. robots.txt, llms.txt, sitemaps and Schema are open standards. Ask your provider to do the same, or check whether they already have.

Q: After the two-way sameAs, how long until it shows? A: Entity merging is cumulative rather than instant. In general, changes in AI citation rate and coverage need 4 to 8 weeks before there is enough data to judge.

Q: How does this differ from your client cases? A: Client cases (such as Everpeak Engineering and New Win Tec) focus on performance figures with real screenshots. This first-party case focuses on groundwork and verifiability, because it is our own site and every detail can be published.

Summary

hkunifi.com is our own UniFi store, built with the same GEO stack. The most important step here was linking hkunifi.com and geo.gnshk.com to the same entity in both directions, so that AI sees a complete, consistent network under GNS Technology Limited rather than a few unrelated websites.

To see where your own brand actually stands in AI search, start with the free AI visibility report or request a quote.

Further reading: Brand entity resolution in AI search, The llms.txt and robots.txt guide, How structured data affects AI citations, GEO contracts and KPI acceptance guide