"Made with Tailor AI" Badge
A small credit link on pages Tailor has tailored. It is optional. Contact us if you want it removed.
Where It Appears
A link to tailorhq.ai, opening in a new tab. It takes one of two forms.
On your own pages
A pill in the bottom-left corner, below the layer your modals and cookie banners use.
On Tailor-hosted pages
A line of muted text below the page content, the way a platform footer credit sits.
Only one ever appears. On a hosted page running a live test, the in-page credit wins.
When It Does Not Appear
The badge is tied to a change actually landing, not to a test targeting the URL. It is absent for:
- Control-group visitors, who see your original page
- Pages with no live test, or where no change applied
- Preview links, QA links, and the Chrome extension editor
- Screenshots Tailor captures, including before/after images on recommendations
It also removes itself if your Content Security Policy blocks its styling.
Turning It Off
The badge is optional and set per account, so it applies to every tailored page on your account or to none. We usually turn it off for paid accounts, and we can turn it off on request.
How to have it removed
Email support [at] tailorhq [dot] ai and we will switch it off on your account. There is nothing to change on your site and no redeploy.
Hosted pages clear within about an hour, and pages on your own site once the cached Tailor script refreshes. Every change is written to your activity log.
What It Does Not Do
The badge is a link. It does not change how anything else on your page is measured.
No visitor data
No cookies, no storage, and nothing collected from your visitors.
No analytics events
Nothing pushed to your dataLayer or GA4. Your conversion and attribution reporting is untouched.
No extra request
Roughly 1 KB inside the Tailor script your page already loads.
No SEO or layout changes
Canonical tags, robots directives, and page structure are unchanged.
The link carries utm_source and utm_medium, which describe the visit to tailorhq.ai after a click. They land in our analytics, not yours.
On your own pages it renders inside a shadow root, so it cannot leak into your CSS or be reached by it. It is excluded from element capture, so it can never become the target of a change or a goal. It is keyboard focusable and labeled for screen readers.