Hosted Sites
A whole site, cloned into a real code repository that Tailor operates for you. Change something once and it changes everywhere.
Availability
Hosted Sites is not switched on for every account yet. If it is not in your Live Pages section, you do not have it. Talk to your Tailor contact if you want to be part of the early group, and read this page as a description of what is coming rather than what is in your account today.
Hosted Pages, which clones one page at a time, is available now, and is the right tool when you want one page changed.
Overview
You point Tailor at your site. It takes a copy of the pages you choose and turns them into a real website codebase, the same kind your engineers would build, stored in its own repository.
From then on Tailor works on that codebase the way a developer does. It can read any page, change a shared component, add a route that did not exist, check the site still builds, and deploy a preview for you to look at.
You do not need to read or write any of that code. You ask for the change in the Tailor agent, and you review the result as a page.
Sites Vs Pages
Which one you want comes down to whether you are changing a page or running a site.
Hosted Page
One page, copied exactly as it looks, edited on its own.
- Right when you want this page, faithfully, now
- Available today
- Cannot add a page or change your navigation
Hosted Site
Many pages, with the shared parts still shared.
- Right when you want to operate the site, not one page
- Coming soon
- Can add pages and change every page at once
What a single hosted page cannot do is reach. There is only one document, so there is no everywhere to change. A repository gives Tailor the things a developer has: a file that many pages use, a page that did not exist before, and a build that either passes or does not.
Where The Code Lives
The copy of your site is a Git repository on GitHub, in a Tailor organisation set up for hosted sites. It is named after the site it came from, so a clone of example.com is easy to recognise in a list.
Every change Tailor makes is an ordinary commit, so there is a full history of what changed and when. Builds and previews are deployed through Vercel.
You do not need a GitHub or Vercel account of your own, and you do not need to connect either one. Tailor sets both up when it clones the site.
What You Can Ask For
- Change a heading, an image or a call to action on one page
- Change something that appears on every page, like the navigation or the footer, once
- Add a page that does not exist on your site yet, such as a campaign landing page or an answer to a question buyers keep asking
- Restructure a section across several pages at the same time
You can clone a whole site, or one section of it. Pointing Tailor at a blog clones that blog and the pages beneath it, and nothing else.
Publishing
Finishing a change and putting it in front of visitors are two separate steps.
When Tailor finishes a change it produces a build and gives you a preview link. Visitors are still served whatever was published before. A person has to choose to publish a build before anyone outside your team sees it.
Every build is kept, so publishing an earlier one is how you roll back.
What Carries Over
A cloned site keeps the third party tags your original pages carry, including analytics, ad pixels, consent tools and chat widgets, so your measurement keeps working. The clone report lists what it found and what it did with each one.
Your Tailor tag is installed on the cloned pages, so tests and conversion tracking work there the same way they work on your own site. See Conversion Goals and Cookie Consent.