tokistorage.github.io) from an LP redirect into an independent corporate site. The LP is a "library" with 159 essays across 525 pages of detailed service information — overwhelming for first-time visitors. The corporate site functions as a "front door," conveying the big picture with minimal information and directing visitors onward to the LP or TokiQR. This separation isn't about aesthetics; it's about information architecture.
1. Why We Separated
Until recently, visiting tokistorage.github.io redirected to /lp/. The LP doubled as the top page.
The LP isn't a bad page. Service details, pricing, technical specs, 159 essays, manifesto, proposal materials — 525 pages of everything is there. But "everything is there" is synonymous with "first-time visitors don't know where to start."
A library is a wonderful place, but if the building's entrance is inside the stacks, you have a problem. What you need is a spacious lobby and a directory.
The LP is the library. The corporate site is the front door.
Visitors stand at the door first, then decide where they want to go.
2. What We Built
The corporate site consists of six pages.
| Page | Role |
|---|---|
index.html |
Top page. Hero, mission, three service cards, founder summary |
services.html |
Service directory. Three-layer preservation overview, TokiQR, Wedding |
about.html |
Company info. Mission, founder bio, company details, social links |
| + English version of each page (6 pages total) | |
We didn't compress LP content onto the corporate site. The corporate site carries only summaries and links out to the LP for details. This structure, which avoids content duplication, also reduces maintenance costs.
3. Design Differences
We use the same color palette (Toki Blue #2563EB / Hiragino Mincho + Sans) while deliberately creating contrast.
| Attribute | LP | Corporate |
|---|---|---|
| Max width | 960px | 1080px |
| Section padding | 4rem | 6rem |
| Cards | Background + border | Borderless, bottom line only |
| Decoration | Text-centric | Text only, decoration eliminated |
| Navigation | Fixed nav + sidebar | Frosted-glass fixed nav only |
In short: "same brand, different density." The corporate site has more whitespace and lower information density than the LP. Designed so a first-time visitor can understand "what this company does" in three seconds.
4. Subdirectory Architecture
GitHub Pages places user pages (username.github.io repository) at the domain root, while project pages are served from subdirectories. We leveraged this structure.
| URL | Repository | Role |
|---|---|---|
tokistorage.github.io/ |
tokistorage.github.io | Corporate (front door) |
tokistorage.github.io/lp/ |
lp | LP & essays (library) |
tokistorage.github.io/qr/ |
qr | TokiQR app |
Three repositories, independently deployed and managed. CSS, JS, and assets are all self-contained — changes to one repository don't affect the others. This is a natural extension of the no external dependencies design principle.
5. SEO Impact
Resolving the problem of an empty domain root (redirect-only) yielded several SEO benefits.
- robots.txt now returns a proper 200. Previously it returned 404 (Site not found)
- sitemap.xml placed at the domain root, using
sitemapindexto reference both corporate and LP sitemaps - Organization structured data on the root page, contributing to Knowledge Panel recognition in Google Search
- hreflang explicitly mapping the JA/EN relationship, ensuring language switching is correctly recognized by search engines
Building the corporate site wasn't just about appearance — it was about presenting the "face of the company" to search engines.
The Result — Indexed the Day After Launch
The day after the corporate site went live, a site:tokistorage.github.io Google search showed the top page already indexed. The domain root, which had never been indexed during the redirect era, was recognized the moment it had a real page.
The sequence mattered. 159 essays, 525 pages of content, meta information cleanup, sitemap.xml construction — everything was finalized before the corporate site launched. Had indexing occurred while the content was incomplete, outdated descriptions and missing metadata would have been picked up by Google, and corrections would take time to propagate. Polish the content, then go public. This sequence made it possible to present the best first impression.
6. Self-Containment as Consistency
TokiStorage's design philosophy includes a principle: "Don't increase external dependencies." No CDN-loaded libraries. No frameworks. Self-contained CSS.
The corporate site is no exception. style.css is a single self-contained file, completely independent from the LP's index.css. main.js handles only nav toggle and scroll shadow in 50 lines of code. Favicons and OGP images are copied into asset/, eliminating cross-repo references to /lp/asset/.
Three repositories are three independent islands.
Even without bridges, each stands on its own.
7. Conclusion — A Front Door Should Be Quiet
A front door should be quiet.
Leave the flood of information to the library.
At the front door, just say "here's what this place is."
The information on the corporate site is less than a tenth of the LP's 525 pages. That's fine. You don't put an encyclopedia in the entryway. Visitors understand the mission — "Democratizing Proof of Existence" — and if interested, they proceed to the LP or try TokiQR. When this flow works, the corporate site has done its job.
Six pages, one CSS file, 50 lines of JS. That's the entire front door.