The easiest way to run multiple tube sites is from one install with one admin area, where every domain is its own site with its own design and settings but all of them draw on a shared video library, one encoder and one set of member accounts. You upload or import a video once and decide per site whether it appears. The alternative, a separate install for every domain, works but multiplies the encoding, storage, updates and admin work by the number of sites.
Why operators run networks
A single site is a single bet. A network of focused sites spreads risk across several domains and niches, lets each site rank for its own search terms, and lets you test ideas on one site without disturbing the others. Most successful networks are made of related niches that can share content: one broad site and several narrower ones that each show a slice of the same library. The niche tube sites strategy guide covers how to plan the slices.
Separate installs: the hidden costs
Running five sites as five independent installs means:
- Five copies of every video. Each install encodes and stores its own files, so disk use and CPU time multiply.
- Five admin areas. Adding a video to three sites means three uploads, three sets of tags and three moderation checks.
- Five updates. Every security fix and new version has to be applied everywhere, and installs drift apart over time.
- Five member databases. A visitor who signs up on one site is a stranger on the others.
- Five sets of reports and takedowns. A DMCA notice for a video that appears on several sites has to be handled on each one.
That last point is easy to overlook. When the same file lives in several places, a missed copy is a real risk.
One install, many sites
A network-aware script inverts this. The library, encoder, workers and member accounts are shared, and each domain is a "site" record with its own settings layered on top. In practice that means:
- A video is uploaded, encoded and stored once, then shown on any site whose rules include it.
- Each site has its own template, colours, logo, ads, static pages and release schedule.
- Removing a video removes it from every site at once.
- One update covers the whole network.
- One dashboard shows how every site is doing.
What should stay different per site
Sharing a library does not mean every site should look alike. Search engines and visitors respond better when each site has its own identity. Plan for each site to differ in:
- Which videos it shows, through category rules, keyword rules or hand-picking.
- When it publishes them, through its own drip-feed schedule and order.
- How it describes them, through per-site titles and descriptions.
- How it looks, through a different template, colours, logo and thumbnail style.
The duplicate content guide goes into each of these.
Hosting a network
Domains in a network can live on the same server as the install, which is simplest, or on other servers that pass requests back to the main install. The same-server route only needs DNS and web server configuration; the remote route suits operators who want sites spread across different hosts or IP addresses. Both are explained step by step in adding a domain to a tube network. Because encoding happens once, a network's CPU needs are close to those of a single site with the same upload volume; bandwidth grows with total traffic. See hosting requirements.
Managing the work
A network only saves time if the routine tasks are shared. Set up categories and tags carefully at the start, because site rules depend on them. Import in bulk into the shared library, let each site's rules and schedule decide distribution, and review the network dashboard to see which sites are growing. Keep a short document listing each site's niche, rules and schedule so you can spot overlaps.
How Tube Site Script runs a network
Tube Site Script is built for this. You install once on your primary domain and add as many other domains as you like under Admin › Sites. Each site chooses its content mode (the whole library, chosen categories, videos matching chosen words, or hand-picked only), its own drip schedule (a set number of videos every so many minutes, in oldest, newest or random order), its own title and description overrides, and its own template, appearance settings, logo, favicon, custom CSS, head and footer code, ads and pages. Spintax in titles gives each site its own wording automatically.
Domains can sit on the same server as an alias, parked domain or extra nginx server_name, or on another server using a connector downloaded from the admin. The network dashboard shows views, sign-ups and live and queued videos per site. One Installation Key activates the primary domain; the other sites need no key of their own. See the PHP tube script features and pricing.
Frequently asked questions
Can several tube sites share one database?
Yes, with a script designed for networks. The library, members and settings live in one database, and each site record adds its own overrides on top.
Will running several sites from one install hurt SEO?
Not if each site is genuinely different. Give each its own selection of videos, release timing, text and design so the sites do not serve identical pages.
Do members need separate accounts on each site?
In a shared install the accounts are shared, so one account works across the network. Because cookies are per domain, visitors still sign in on each domain they use.
