August 31, 2026 · 4 min
How meraGEO uses Restyler 1 to rewrite customer pages
More and more, the first reader of your website is not a person. It is a language model deciding whether to cite you, summarise you, or skip you. And machine-written copy reads exactly like machine-written copy, to them and to everyone else.
meraGEO is built for that problem. It scans a site, scores how every page reads, and on its Optimize tier rewrites the pages that read as machine-written, in place, keeping the structure, the links and the facts. It runs on Restyler 1.
Working element by element
A page is not a wall of text. It is headings, paragraphs, list items, tables and links, and a customer wants their page back, not a reconstruction of it.
So meraGEO works one element at a time. Each paragraph is rewritten on its own and dropped back exactly where it came from. Navigation, code and styling are never touched. What comes back is your page, with better prose in it, and every heading and link precisely where you left them.
That turns out to be the right shape for the model too. An HTML paragraph is naturally the size Restyler 1 was trained on, so the page itself decides how much text each rewrite sees.
In production since August
- Real customer pages, on a paid tier, not a demo.
- Whole sites, not samples. Up to 250 pages a month rewritten automatically on the top tier.
- Facts held still. Numbers, names, dates and links survive the rewrite, and anything that runs long is discarded rather than shipped.
- Before and after, side by side. Customers see their live page with the rewrites applied before anything is published.
Available as an API
meraGEO needed all of it: splitting text into the units the model expects, skipping what should not be touched, guarding against runaway output, putting the result back without disturbing formatting. That is the same work anyone doing this needs.
So it is an endpoint now. POST /v1/restyle takes a document and gives it back with the prose rewritten and everything else byte-for-byte identical, plus a per-block report of what changed. meraGEO is moving onto it, which means the API is being proven by a product with paying customers on the other end.
Try it on your own page copy, with no account and no card, or read the docs and wire it in.