PlanetWeb · Tier 2 of 3
Your Catalogue,
Found Worldwide.
For manufacturers and companies selling beyond their home market: a catalogue site built from your own product data, in your buyers’ languages, with requests for quotes sent to your team.
- For
- makers and companies selling abroad
- Built From
- the product data you keep
- Languages
- three to five
- The Time
- two weeks, then upkeep
2 days
From a catalogue going live to its first Google clicks: medical devices and their makers, built from a regulator’s public records, none written by AI.
the catalogue’s own Search Console, 22 September to 1 October 2026; 204 clicks a weekday from the second day on
Four Plain
Questions.
Who builds it?
The studio: the catalogue, its languages, the request form and the server.
Do I pay every month?
For the upkeep, yes, quoted with the build, which is a fixed scope; the server and the domain are paid at cost.
Where does it run, and whose is it?
On self-hosted WordPress, not a WordPress.com subscription, installed on your own server near your buyers, so you control the site fully: the files, the data and every login.
Who keeps it current?
The sheet does: a product changes once in it, and every page and language follows.
Your Data First,
Then the Pages.
A catalogue typed by hand falls behind what you make. Planet starts from the sheets you already keep.
- 01
The Sheet
Your product data as you keep it; a spreadsheet is enough to start.
- 02
The Families
Products grouped the way your buyers look for them.
- 03
The Pages
One page per product, with its specifications and drawings.
- 04
The Spec Sheets
A PDF for every product, made from the same data.
Hosted Where
Your Buyers Are.
The site loads nothing from other hosts, and a CDN serves it near every buyer, so it opens as quickly in China as in Europe or America.
- 0
requests to outside hosts
- 3–5
languages from one source
- 1
server near your market
- 1
sheet changes every page
In Your Buyers’
Languages.
A buyer in Germany searches in German, a buyer in Japan in Japanese. Each language gets its own pages, from one source.
- 01
One Source
Every product written once, in the data.
- 02
Its Own Address
Each language at its own address, so each market finds its own pages.
- 03
Its Own Search Terms
The words each market uses for what you make, found before the pages are written.
- 04
One Change, Everywhere
A product changes once; every language follows.
The Catalogue,
and What Runs It.
Everything the catalogue needs to be found worldwide and to keep up with what you make.
The Catalogue
Every product family, laid out the way your buyers look for it.
A Page per Product
Its specifications, materials, sizes and drawings, each written once in the data.
A Spec Sheet per Product
A PDF made from the same data, current whenever the data is.
Three to Five Languages
Each at its own address, with the words each market searches for.
The Request Form
The part, the quantity, the market and the date, with drawings attached, sent only by a person.
The Routing
Each request to whoever answers that family or market, kept on the server first.
The Server
Near your buyers, with daily backups and https renewed by itself.
The Sheet
One spreadsheet that updates every page and every language; the upkeep runs through it.
From You
- the product sheets you keep
- the markets and their languages
- the current site, if there is one
- who answers requests, by family or market
Requests for Quotes,
Only from People.
Every request is kept on your server before it is mailed, and none comes from a script.
- 01
What They Need
The part, the quantity, the market and the date, in fields made for your products.
- 02
Their Drawings
Files attached to the request, kept with it.
- 03
A Person’s Touch
The form sends only after a real touch; a script’s attempt is held.
- 04
The Right Person
Each request to whoever answers that family or that market.
Two Weeks,
Then Upkeep.
The catalogue goes live in the second week. After that, new products and prices enter through the same sheet, each month.
- 2
The Data
Days one and two: your sheets read; the catalogue’s structure decided with you.
- 3
The Map
Day three: families, products, languages and the words each market searches for, laid out before anything is drawn.
- 10
The Build
Days four to ten: the catalogue, its languages, its form and its search data, checked on every screen.
- 6
Live
Week six: on the server near your buyers, search verified, every login handed over; then upkeep each month.
A Catalogue PDF,
or a Catalogue Site.
A Catalogue PDF
- Where Buyers Find You
- A PDF, sent on request.
- When a Product Changes
- A new PDF, sent again.
- Requests
- An address that fills with spam.
- Languages
- One, sometimes two.
Planet
- Where Buyers Find You
- Pages found in search, in their own language.
- When a Product Changes
- One sheet changes; every page and language follows.
- Requests
- A form only people can send, routed to your team.
- Languages
- Three to five, from one source.
Three Sizes,
One Structure.
Moon is one site. Planet carries a catalogue worldwide. System runs a main site and its satellites. Each contains the one before it.
Planet,
Explained.
What the studio has written about catalogues and a global presence, from its own records: the papers, and the terms they define.
Written Once, Read in Fifteen Languages
How a firm’s site went from one language to fifteen in a day, with no plugin and one source, why the first translations read as machine output and what fixed them, and what the first two weeks in search showed.08 · Web · Planet · · 12 min readSatellites: Smaller Sites That Lead Home
What a satellite is for, how it grows and what it lives on, from three records on the studio’s engine: a firm’s satellite read for fifteen months, two satellites that fell with their root and came back with it, and a network of eleven that showed the limit.06 · Web · System · · 11 min readBuilt From Public Records
The studio’s own catalogue of China’s medical device makers, made from a regulator’s public records with no text written to rank and no pictures: what was built, why Google showed it within hours, and what it means for any firm that holds data.07 · Web · Planet · · 12 min readPresence Is a Structure
Why a firm is found because of how it is built, what design, data architecture and search do when they are built together, and what the studio’s own records show about structures that hold.01 · Web · Moon · · 13 min read
Asked First,
Answered Plainly.
Which data do you need from us?
The product sheets you already keep: names, specifications, materials, sizes, drawings and photographs. A spreadsheet is enough to start.
How long does it take?
Two weeks to launch: the data and the map in the first three days, the build to day ten, live on day fourteen. Then upkeep, monthly.
Which languages?
The languages of the markets you sell to, three to five. More can be added later from the same source.
Who receives the requests?
The people you name, by product family, by market or by language. Every request is also kept on the server.
Your Catalogue,
in Their Language.
Send one product sheet and the markets you sell to. A person reads the sheet and answers within two working days.