Project summary
The site gives Rukh Labs one public structure for website services, career portfolio services, original products, product privacy, changelog entries, and studio information. The implementation is intentionally organized around clear routes instead of a single product-heavy landing page.
Challenge and constraints
The public site needs to make distinct offers understandable without flattening them into one generic claim. It also needs to keep a private recruiter portfolio isolated from public navigation, links, the sitemap, and search snippets while allowing the studio to publish genuinely useful public material.
- Keep the permanent Rukh Labs identity consistent across services and products.
- Use one canonical production host and explicit indexability decisions by route.
- Avoid personal profile details, client claims, fabricated metrics, and private-portfolio references on public pages.
- Keep long-form information server-rendered and maintainable without introducing a hosted CMS.
Current implementation
The public application is built with the Next.js App Router and typed React components. It uses a shared metadata helper, route manifest, generated sitemap, robots route, reusable JSON-LD serializer, breadcrumbs, route-specific social images, typed analytics events, and a local regression audit.
| Area | Current implementation |
|---|---|
| Information architecture | Separate product, service, work, insight, legal, and contact routes with direct internal links. |
| Search foundations | Canonical metadata, sitemap registration, robots directives, redirects, Open Graph images, and route-specific structured data. |
| Privacy separation | The private portfolio carries noindex, nofollow, noarchive, and nosnippet directives, is absent from public navigation, and is not in the sitemap. |
| Measurement | Vercel Analytics events are typed and avoid form values, message text, and other personal data. |
Current limitations
The platform does not claim measured traffic, conversion, or ranking outcomes. Real client case studies, reviews, and testimonials are intentionally deferred until Rukh Labs has permission and verified source material. The contact flow prepares a local email draft; it does not submit inquiries to a server from this repository.