Tube Site Script
Content and encoding

Drip-feed video publishing: how to schedule releases on a tube site

How drip-feed publishing works on a tube site, why it beats publishing in bulk, and how to work out a release schedule from your backlog and new content.

Updated 3 minute read The Tube Site Script team

Drip-feed publishing means releasing videos automatically a few at a time on a schedule, rather than publishing a large batch at once. A sensible starting schedule for most tube sites is a small number of videos every few hours, adding up to somewhere between 5 and 30 a day, adjusted to the size of your backlog and the rate you add new content. The aim is a site that always looks fresh and keeps publishing for months, not one that peaks on launch day.

Why drip-feed instead of publishing everything

  • Fresh home page. Returning visitors see new videos every time they visit, which gives them a reason to come back.
  • Steady crawling. Search engines visit sites that change regularly more often. A steady flow of new pages is easier to crawl and index than a sudden spike.
  • A natural profile. Thousands of pages appearing overnight on a new domain can look like an automatically generated site.
  • Longer runway. A large import released gradually keeps a site active for a long time, even while you look for more content.
  • Different timing across a network. Sites that release the same video at different times look less like copies; see avoiding duplicate content.

Scheduled releases versus a drip queue

There are two common approaches, and many sites use both:

  • Scheduled releases give each video its own publish date and time. This suits planned content, such as a weekly series or a partner's release calendar.
  • A drip queue holds a pool of ready videos and releases a set number at each interval. This suits large imported backlogs, where giving every video a date by hand is impractical.

Working out a schedule

Start from two numbers: the size of your backlog and how many new videos you add each month. Then decide how long you want the backlog to last.

BacklogNew per monthExample schedulePer dayBacklog lasts
500501 video every 3 hours8About 3 months
2,0002002 videos every 3 hours16About 7 months
10,0005003 videos every 2 hours36About 17 months

The "lasts" column subtracts new additions from daily releases, so a queue that receives roughly what it releases will never empty. If the queue drains faster than you can refill it, slow the schedule down rather than letting the site go quiet.

Practical tips

  • Launch with a base. Publish a reasonable starting library on day one so the site does not look empty, then drip the rest.
  • Prefer small, frequent releases. Two videos every three hours looks more natural and keeps the home page changing more often than sixteen at once.
  • Pick an order deliberately. Oldest first works through a backlog in sequence; newest first keeps the latest additions visible; random order mixes old and new and is useful when several sites share a library.
  • Vary schedules across a network. Give sibling sites different intervals, counts and orders.
  • Prioritise when needed. Use a fixed publish date for videos that should appear at a particular time, and let the queue handle the rest.
  • Watch your server. If videos are encoded on import, make sure encoding keeps ahead of the release schedule; see hosting requirements.

Keeping the schedule running

Drip feeds depend on a reliable background task, usually cron running every minute. If cron stops, publishing stops silently. Check periodically that new videos are appearing, and keep an eye on the queue size so you know when to import more. Each release should also update the site's RSS feed and sitemap so search engines and feed readers see it; see the video sitemap guide.

How Tube Site Script handles drip-feed publishing

Tube Site Script supports both approaches. Any video can have a publish_at date, set in the admin or in a CSV or XML import. On top of that, each site in a network has its own drip schedule: a number of videos every so many minutes, released in oldest, newest or random order from the videos that site's content rules include. Because the schedule is per site, sibling sites release the same shared library at different times and in a different order.

Releases and site queues run from the cron line the installer gives you, and the publish command runs them on demand. The network dashboard shows live and queued videos for every site, so you can see at a glance how long each queue will last. See running multiple tube sites, the PHP tube script features and pricing.

Frequently asked questions

How many videos should I publish per day?

Base it on your backlog and monthly additions so the queue lasts. Between 5 and 30 a day suits many sites, released in small batches.

Does drip-feeding help SEO?

Regular updates encourage regular crawling and avoid a sudden flood of pages on a new domain. It does not replace good titles, descriptions and site structure.

What happens if cron stops running?

Scheduled releases stop until it is running again. Check now and then that new videos are appearing on schedule.

Get three guides like this every month, plus software update notices.Subscribe →