Under the hood

How it’s made.

For readers who want to know: the technical choices behind every Pikumo Pages site, and why we made them.

< 60 KB
per page, HTML and styles included
< 1.5 s
our target to show a page on a phone over 4G
100%
of changes kept, restorable in one click

Your content is data

Opening hours are hours, not a paragraph.

Owners fill in structured fields: hours, menu, contact details, posts. One source feeds the page, the structured data search engines read, the AI layer and the “open now” badge.

  • Long text is written in Markdown, rendered and sanitised on the server.
  • Every stored document carries a schema version; old versions stay readable.
  • Every edit creates a revision; publishing freezes the whole site, and rolling back moves a pointer.

Built for AI agents

Readable by people, search engines and AIs.

Every site describes itself in the formats assistants read, generated from the same information, with nothing to set up.

  • Complete structured data

    schema.org JSON-LD on every page: Person, BlogPosting, CafeOrCoffeeShop, Menu, opening hours.

  • A Markdown version of every page

    Add .md to any address to get the clean text, without the layout.

  • An llms.txt in every language

    An index of the site for language models, written from its pages.

  • A public MCP server

    A read-only endpoint where agents ask for the menu, the hours or the latest posts.

Your AI, your site

An owner MCP server, with a preview before anything goes live.

Owners connect Claude, ChatGPT or any MCP client to their account (OAuth). Their AI reads the site, writes drafts, shows a private preview, and only publishes on an explicit “publish”. No chatbot in our dashboard: their own AI already knows them.

  • Drafts, never a direct write to the live site.
  • Every write starts from a known revision: a concurrent edit is refused, not overwritten.
  • Every action is signed and logged; anything can be undone.
A sample exchange between an AI assistant and the Pikumo Pages MCP server
  1. Write a post about our new coffee from Brazil, and show it to me before it goes live.
  2. get_sitesite: "cafe-lumiere"
  3. create_pagecollection: "post", locale: "en"
  4. preview
  5. Here’s the draft, “A new coffee from Minas Gerais”, with a private preview link. Shall I publish it?

    Private preview · draftcafe-lumiere.mon-service.site

  6. Perfect. Publish it.
  7. publish
  8. Published. The previous version is kept.

Fast and safe, by design

What every site has, with nothing to set up.

  • Rendered on the server. Plain HTML and self-hosted fonts, light enough to show at once on a phone. Served by a CDN, cached per version.

  • Closed themes, on purpose. A theme changes tokens (colours, fonts, spacing, corners), never the structure. Every theme, block and variant is screenshot-tested on phones and computers, light and dark.

  • A strict security policy. A CSP with no inline script or style, secure cookies, client sites on a domain separate from the dashboard. No trackers.

  • Photos made light automatically. Every photo is converted to WebP, in several sizes, and served from a signed address.

  • In several languages. Each language has its own addresses and hreflang links; never an automatic redirect based on the browser.

Photo credits

The illustration photos are photographs from Wikimedia Commons that their authors dedicated to the public domain (CC0 1.0). They were cropped and resized. Thank you.

  • “Café de la Crèche (Lyon) en novembre 2022”, Benoît Prieur · source

Your site, live today.

Create my site for free