Websites people and machines can read
A site that tells your story, that you can edit yourself, and that search engines and AI assistants can read without running a line of JavaScript.
Server-rendered pages with the content in the HTML, structured data that names your organisation and services, an owner studio for the copy, and 3D or motion only where it serves the work. The site you are reading is built this way.
Live for this studio at ribhulabs.ai; a client site at kavinwealth.com built before this approach; two further sites built and awaiting launch.Confident typography. Space to breathe. A story with a clear point of view.
Websites built so a person and a machine read the same page: server-rendered content, Organization, Service, FAQ and Article schema, a sitemap and a robots file that name the crawlers, an owner studio for the copy, enquiries to your inbox, and calculators, film or 3D where they earn their place.
Who it is for: Owner-led businesses, advisors, clinics and brands that want a site they can keep current themselves, and that a search engine or an AI assistant can read and quote accurately.
What it does,
as built.
Every line here is something already built and delivered, not a roadmap.
- 01
Server-rendered pages: every word is in the HTML the crawler receives, with no JavaScript needed to read it.
- 02
Structured data on every page: Organization, Service, FAQ and Article schema that matches the visible text.
- 03
A sitemap with last-modified dates and a robots file that names the AI crawlers, so what is allowed is explicit and nothing is blocked by accident.
- 04
One canonical address, and every publish announced to search engines through IndexNow.
- 05
A Markdown twin of each page and an llms.txt index, included as hygiene rather than sold as a lever.
- 06
An owner studio, never linked publicly, where you edit copy, add a service or an article, and publish with a preview and kept revisions.
- 07
Client reviews published only after the client submits them and you approve; Google reviews imported unedited and labelled.
- 08
Enquiries stored on the server and shown in your studio inbox, with email notification if you want it, and a WhatsApp button where that is how customers reach you.
- 09
Calculators, appointment booking, film or 3D when they serve the work, each with a plain fallback so the page works without them.
- 10
Hardened sign-in for the studio: password, two-factor code and recovery codes.
- 11
Fast and accessible by budget: asset sizes are checked on every build, motion respects reduced-motion settings, and pages work without WebGL.
- 12
Answer-first writing: an "in short" paragraph at the top of each service page, and articles that answer the question in their title.
From first conversation
to running.
- 01
Find the story worth telling
A one-week review of your story, your content and what the site must do: the audience, the offer and the action each page should lead to.
- 02
Design and build
Page stories, typography and a shared design system, then the pages, motion and integrations, built server-rendered from the first commit.
- 03
Check what a machine sees
Before launch we validate the structured data, read the site as a crawler would, confirm the robots file and sitemap, and submit the sitemap to Google Search Console and Bing.
- 04
Launch and hand over
You get the studio, a walk-through of editing, and the domain and hosting in your own name. We stay available for changes by agreement.
Connected
where it counts.
Only what is wired in code today. Anything else is new work, scoped with you.
- Resend email
- Stripe Payment Links
- Stripe Checkout
- Google Calendar
- IndexNow
- Railway hosting
Where it
runs today.
Live for this studio at ribhulabs.ai; a client site at kavinwealth.com built before this approach; two further sites built and awaiting launch.
kavinwealth.com
A Canadian wealth, mortgage and protection advisor. Eleven planning calculators with their methods documented, an appointment picker on one shared calendar, consent-gated client testimonials, a WhatsApp button and inbox, and an admin studio with two-factor sign-in. Live. Built as a client-rendered app before this approach.
kavinwealth.comA luxury leather-goods brand
Built for a women's leather-bag brand and awaiting its launch: a scroll-scrubbed campaign film on the home page, a 3D product viewer, Stripe checkout in two currencies, a bespoke admin for products, orders and the brand film, and crawler access, schema and a product feed designed in from the start.
This site
The reference build: server-rendered Astro, a live 3D hero with a still fallback, a scroll-scrubbed brand film, an owner studio with draft, preview, publish and revisions, consent-gated reviews, enquiries to the inbox, Markdown twins, llms.txt, a robots file naming fifteen AI crawlers, and IndexNow on every publish. Every claim about how it is built can be checked against it.
ribhulabs.aiA family clinic's website with its own admin
Built for a family clinic in Nova Scotia: home, doctors, services, blog and contact pages, with an admin where the clinic can edit its hours, storm closures, doctors, services, notices and live wait time itself. The sitemap and robots file are generated from the content.
Asked before
signing anything.
Will it come up first on Google, or be cited by ChatGPT?＋
Nobody can promise that, and we do not. What we deliver is inspectable: content in the HTML, structured data that validates, crawlers allowed by name, a sitemap submitted to Google and Bing, and a consistent name, address and domain everywhere. Technical readiness is the foundation, not the whole building; reviews, profiles and real mentions do the rest, and those are yours to earn.
Can I edit the site myself?＋
Yes. The owner studio is where you change copy, add a service page or an article, approve a review and read enquiries. You save a draft, preview it, and publish when you are ready; earlier versions are kept.
What is the point of llms.txt and Markdown pages?＋
They are a cheap hedge. No major assistant has committed to reading llms.txt, so we ship it and the Markdown twins because they cost almost nothing, and we do not sell them as the reason you will be found. Server-rendered content and crawler access matter far more.
Do I need 3D or a film?＋
Only if it serves the story. Live 3D suits something the visitor can inspect; a film suits directed storytelling; many pages need neither. Whatever we add has a still fallback and respects reduced-motion settings.
Can you fix my existing site instead?＋
Often, yes. A site that paints its content with JavaScript can be retrofitted with server-rendered pages, structured data and a corrected robots file without a redesign. The one-week review tells you which parts are worth keeping.
What can it connect to?＋
Enquiries to your inbox, WhatsApp, Stripe Payment Links or Stripe checkout, Google Calendar for bookings, and whatever your delivery process needs, tested from submission to confirmation.
Where is it hosted and who owns it?＋
In an account in your name, on hosting we set up together; you hold the domain. The source code is yours.
How do AI assistants decide which businesses to recommend?
They search an index, open a few pages and quote what is clear, current and corroborated elsewhere. You cannot buy the slot, but you can be easy to find and safe to cite.
How do you brief an interactive 3D website so it stays fast and accessible?
Write the content for a plain page first, then brief 3D as an enhancement with a budget, fallback and reduced-motion path.