Write the privacy policy once. Every site serves the current version.
The same legal pages live on every site you run, and they only differ by company name and address. Multisite Agent hosts them in one place and delivers them to any site with one embed, with per-site variables, language variants and version history. Change the text once and every site updates in seconds, on any stack.
Works on WordPress, Webflow, static HTML and custom code · No redeploy · One site free
Twenty copies of the same page, and every one of them ages.
Legal pages are not a feature you build once. They are a maintenance obligation on every site, forever, and they are the first thing a client's lawyer looks at.
A law changes. Now edit twenty sites.
One cookie rule or one new address, and the afternoon goes to opening twenty admin panels, pasting the same paragraph and redeploying each site in its own way.
The site you forgot
Eighteen sites got the update. Two didn't, and nobody remembers which. The outdated imprint on a client site is their liability and your reputation.
Translations drift apart
The German privacy policy was updated in March, the Spanish one still says 2024. Each language lives in a different file, edited by a different person.
Every stack has its own way
A WordPress page here, a Webflow CMS entry there, hardcoded HTML on the old sites. There is no single place to see what is live where.
One source, every site, always the current version.
Write a page in the panel, tick the sites that should serve it, publish. The embed pulls the current version on every request, so there is nothing to redeploy.
Write once, deliver everywhere
Privacy policy, terms, imprint, cookie policy: written and hosted here, delivered to every ticked site at a fixed path with one script tag.
Per-site variables
Company name, address, contact email and registration number fill in from each site's profile, so one text serves many legal entities.
Per-site overrides
When one site really needs its own paragraph, override that section for that site and keep the rest shared.
Language variants side by side
One page carries its English, German and Spanish versions. Each site picks the language that matches its own, with a fallback to the default.
Versions, drafts and rollback
Every publish is a version. Preview a draft, roll back a mistake, and see which sites serve which version in one overview.
Cookie consent on the same embed
The consent banner ships through the same script, with one configuration for all sites and per-site overrides where the law differs.
No legal advice. Multisite Agent hosts and delivers the texts you write; the content remains your responsibility.
One consent banner. Every site. Scripts held until the visitor decides.
The cookie banner is shared content too. Configure it once, pick the sites, publish. The Multisite script shows it in each site's language, blocks analytics and marketing tags until there is a choice, and records consent per site so you can prove it later.
- Bar, box or modal layout; theme and accent follow each site, with per-site overrides
- Equal “Reject all” and “Accept all” buttons, no dark patterns, Global Privacy Control respected
- Categories with vendors: necessary, analytics, marketing, preferences; third-party tags are held until consent
- Banner texts per language, linked to the shared cookie policy page on the same sites
- Consent log per site with accept, custom and reject rates, exportable for audits
- Version history: see which site serves which banner version, update all of them at once
Banner texts and consent figures are sample data. Legal wording should be reviewed by counsel.
A legal update becomes one edit and one publish.
The question "is our privacy policy current on every site?" gets answered by a table, not by opening each site.
Before: a spreadsheet of sites and a long afternoon
- Get the new text from the client or the lawyer.
- List every site that needs it, from memory or an old spreadsheet.
- Open each admin panel, paste, format, publish, redeploy where needed.
- Repeat for each language, hoping the translations are current.
- Miss two sites. Hear about one of them months later.
After: edit once, publish, check the overview
- Paste the new text into the shared page, per language.
- Preview it on any site with its variables filled in.
- Publish. Every ticked site serves the new version on its next request.
- Check the overview: it shows which sites serve which version.
- Spend the afternoon on something that isn't a privacy policy.
"Is ours up to date?" has a link
A client asks whether their site has the latest terms. The answer is the overview row for their site, with the version and the publish date.
One text, one review
The lawyer reviews one document, not twenty copies that have drifted apart. Changes are discussed once and published once.
A changelog for every page
Version history shows who changed what and when, so the question of which wording was live on a given date has an answer.
Set up once. Then it runs.
Write the page
Create a shared page in the panel, with variables for the details that differ per site.
Add one script tag
Paste the Multisite script into each site once, before the closing head tag. No plugin, no rebuild.
Tick the sites
Choose which sites serve the page and at which path. Fill in each site's company details once.
Publish and forget
Every site shows the current version. Edit again any time; nothing needs redeploying.
Questions about Shared Content.
Can I use the same privacy policy on multiple websites and update it in one place?
Yes. Write the page once, translate it once, and deliver it to every connected site. Site-specific details such as the company name or contact address are filled in per site from its profile.
Does Multisite Agent provide legal advice or ready-made legal texts?
No. It is a publishing platform, not a legal service. You add your own privacy policy, imprint or terms, and the system distributes them. Have your texts checked by a qualified lawyer for each country and site you operate.
Does it work with WordPress, Webflow or a custom-built site?
Yes. Shared pages need one script tag per site, which can be added to WordPress, Webflow, Shopify, static sites or custom code. The page is served at a path you choose on each site.
What happens if the embed cannot reach Multisite Agent?
The last published version is cached by the script, so the page keeps rendering. Nothing on your site depends on a live request for every visitor.
Can search engines index the shared pages?
Per page you decide whether the page is indexable, follows links and appears in sitemaps, the same way you would for a page hosted on the site itself.
Change it once. Every site updates.
Add one script tag to each site and keep your legal pages current from one place. One site is free.