Engineering case study · Architecture and technical SEO

Making a five-portfolio reverse proxy predictable for visitors and search engines

The mkazi-time-router source repository contains two routing implementations: Vercel middleware and a Cloudflare Worker. Both can proxy requests to distinct portfolio origins. This case study describes repository changes, not an independently verified production rollout.

The problem

The router previously selected a different portfolio according to the hour in India Standard Time. Search crawler user agents were directed to a fixed portfolio instead. That made the homepage's identity harder to reason about and introduced a risk that crawlers and people would see materially different default content.

The design decision

The source was updated to select the DevTools portfolio as the default for both visitors and crawlers. Five specializations remain available at dedicated subdomains: developer tools, full-stack, frontend, backend and AI interfaces.

Manual ?portfolio=N variants are still supported for exploration and are marked X-Robots-Tag: noindex, follow in the router source. The primary homepage's canonical and Open Graph URL are rewritten to the apex domain when DevTools HTML is served there.

Discovery and identity

The router source provides /robots.txt and a conservative /sitemap.xml listing the primary homepage. Each portfolio repository retains its own sitemap, canonical metadata and structured data. The intent is to keep distinct specializations discoverable without treating every portfolio switch as a new indexable page.

Implementation trade-offs

What remains unverified

Review the implementation

Inspect Vercel middleware, Cloudflare Worker and the engineering audit. This article documents design choices and limitations rather than inventing traffic or performance results.