Site Transformer is a reverse proxy. Every request to the site passes through it — and that's where your changes happen. The origin code never moves. Your config is the deploy.
A DNS change puts Site Transformer in front of the existing site. Nothing in the codebase changes — your origin keeps serving exactly what it serves today.
Map old URLs to new ones. Match URL patterns with regex and rewrite the DOM they return — titles, headings, schema, link structure.
Accept a configuration and it's serving in seconds. No build, no release window, instant rollback.
# Rewrite the URL architecture — live alias: "/index.php?cat=12&id=4821" → "/guides/technical-seo" "/p/*" → "/products/{slug}" # Transform the DOM on matched pages transform match("^/guides/.*"): replace ".post-wrap-legacy" → "article[itemtype=Article]" set "title" → "{h1} · Technical SEO Guide" inject "ld+json" → schema("Article") # origin untouched · 0 deploys
Every URL restructure and on-page fix you recommend has to survive someone else's release cycle. Most don't survive intact — and when the client switches vendors, the next agency unwinds it and starts over.
New URL architecture, cleaner markup, schema, internal linking. Delivered as a doc.
The client's dev team scopes it behind features and bugfixes. Weeks pass.
Half gets implemented, slightly wrong, with no easy way to iterate or roll back.
New vendor, new opinions. The hardcoded changes get torn out. Back to zero.
Point a domain at the proxy and start optimizing the same day.