Skip to main content

Walkthrough · Intermediate · 15 minutes

How to Set Up a Cron Job

Give a script a schedule it can be trusted to keep while you look elsewhere — a hands-on walkthrough in plain words that names the classic mistake before you reach it.

The short answer

The job: give a script a schedule it can be trusted to keep while you look elsewhere. Time to set aside: 15 minutes. Skill needed: intermediate.

Below is the full run of steps, the error most people trip over, and the short cut worth remembering. On Hosting & Domains plans several steps are already automated away — the guide marks each one.

By the Hosting & Domains team · Reviewed 18 August 2026

Intermediate

Experience required

5

Stages, start to finish

Free

Support included

Proven

On the platform itself

No prior knowledge assumed — a hosting account, a browser and 15 minutes of attention is the whole entry requirement. Every instruction runs on our platform exactly as printed, and carries over to any standard cPanel host.

First rule: read the snag section before you start, not afterwards. It was distilled from the tickets of everyone who tried the other order.

How the work divides up

The work falls into a few clean stages: write absolute paths into the command, choose a sensible frequency, capture output while you are testing, quieten it once it has earned trust and record what the job is for.

No part of this needs code or a terminal unless the guide says so plainly — and where it does, the exact commands are printed. The step-by-step is below, with the surrounding sections supplying the context that makes it hold.

The well-worn snag

Relative paths in the cron command. A script that behaves perfectly in your SSH session achieves absolutely nothing under cron, and it fails in complete silence. Write absolute paths to the binary and to the file and the mystery evaporates.

It earns a section of its own because it is no obscure edge case — it is the single commonest reason this task reaches a support queue. Knowing it in advance turns the whole job from risky into routine.

The support desk's own short cut

For WordPress, one cron hitting wp-cron.php every five minutes retires the visitor-triggered scheduler. It is the most widespread cron job on shared hosting and comfortably the most worthwhile.

Habits this small are what separate the people who find hosting effortless from the people who find it draining. The same tools on both sides — a different way of working.

The parts that look after themselves here

Steps that never deserved your time are taken out: certificates issue and reissue themselves, the installer handles application setup, the daily copy absorbs the what-ifs, and per-site settings live in a panel rather than a configuration file. The guide covers the remainder — the part that is actually about your site.

Stopped mid-guide at an awkward hour? That is exactly what round-the-clock support is for — say which step you are on and we take it from there.

One control panel running the hosting and the names side by side

A quick platform makes for a short guide

Every walkthrough in this library is run on the platform we actually operate — cPanel, LiteSpeed, NVMe, one-click installs — so the instructions match your screen rather than gesturing at it from a distance.

Hosted somewhere else already? We move the whole site at no charge, usually within 24 hours, and it goes on answering visitors throughout.

  • Every step checked exactly as published
  • The snag named before it arrives
  • The dull steps taken out of your way
  • People reachable at any hour you stall

Why Hosting & Domains

Standard on every plan

5 steps, nothing padded

Each stage is a few minutes of steady clicking, and the fiddly moments are labelled fiddly.

The snag, flagged up front

The classic error for this particular task is named before step one, which is how 15 minutes stays 15 minutes.

Honest about how big it is

Give a script a schedule it can be trusted to keep while you look elsewhere is a intermediate-level job — set aside 15 minutes, with the platform-absorbed steps marked.

Taken from real tickets

These guides came out of the support queue, so every snag flagged is one people genuinely hit.

The dull parts automated

SSL, backups and installs look after themselves here, leaving the guide to cover only what is genuinely yours.

Works exactly as printed

Every step is proven on the platform we run — none of the 'your host may vary' hedging.

Quick Start

Order placed to site online

  1. 1

    Write absolute paths into the command

    Spell the full path out to both the PHP binary and the script. Cron begins with an empty environment, so 'it ran fine over SSH' tells you nothing about how it behaves on a schedule.

  2. 2

    Choose a sensible frequency

    The panel's presets cover the usual intervals and five-field syntax covers the rest. Pick the cadence the task genuinely needs rather than the one that settles your nerves.

  3. 3

    Capture output while you are testing

    Send output into a file during setup. That log is what separates 'ran and failed' from 'never ran at all', which are cron's two very different ways of letting you down.

  4. 4

    Quieten it once it has earned trust

    After several clean runs, send output to /dev/null or a rotating log. Left alone, cron mail floods the account mailbox and becomes a nuisance in its own right.

  5. 5

    Record what the job is for

    Put a comment above it, or keep a separate file matching each entry to its purpose. Crontabs full of unexplained commands are how essential jobs get deleted by a well-meaning tidier.

Built In

Fitted to every plan

  • WordPress and 400+ further applications installed in one click
  • Free SSL on every plan, reissued before the old one lapses
  • Money back within 30 days on hosting plans, 7 on reseller
  • The name's first year included when you order annually
  • Webmail in the browser plus IMAP, POP and SMTP for any client
  • A renewal figure identical to the one you registered at
  • Spam and virus screening on every mailbox by default
  • cPanel, which is what most of the industry already runs
  • A daily copy, with restores you run yourself from the panel
  • NVMe SSD storage on every tier, not only the dear ones

Frequently Asked

The questions that come up most

How often can a cron job run?

Minute-by-minute is as fine as the syntax goes. Plan limits and ordinary courtesy on shared infrastructure both argue against heavy jobs at that rate. Fit the interval to the work, since most maintenance belongs on an hourly or daily schedule.

My cron job apparently never runs — where do I start?

Switch output logging on and read what appears. An empty log points at the schedule or the command, meaning paths and syntax. Errors in the log point at the script. The panel shows the exact command; run it in SSH and watch what happens.

Does hosting include mail?

Yes — every hosting plan includes mailboxes at your own name, with webmail, IMAP, POP and SMTP plus spam filtering on from the start. There is standalone email hosting too, for a name whose website lives somewhere else.

Where does the hardware physically sit?

The platform runs from a London datacentre with redundant power, cooling and several upstream carriers, with server-level caching in front that keeps cached pages quick for visitors anywhere. For most sites how the platform is built — NVMe disks, LiteSpeed, restrained account density per machine — counts for far more than where it sits.

Keep reading

  • How to Check DNS Propagation

    Find out whether the internet has taken up your DNS change, and why some corners have not — beginner level, about 5 minutes.

  • How to Add SSL to WordPress

    Deliver every page over https with the padlock holding firm on all of them — beginner level, about 20 minutes.

  • Cron Job (Glossary)

    The full definition, along with the practical consequence nobody bothers to mention.

  • WordPress Hosting

    WordPress looked after for you — LiteSpeed caching, staging copies and a daily backup.

  • Charity Hosting

    Reduced hosting for charities and nonprofits, with nothing essential taken out.

Changing hosts? Run through our checklist first.

A plain order of work for a move nobody visiting will notice: which files go over first, how to carry the mail across without losing a message, when exactly to repoint DNS, and the two mistakes behind nearly every outage we are asked to rescue.

What arrives is the checklist, and then the occasional note on keeping a site quick. Leave whenever you like; the privacy policy covers the rest.

The name is waiting.

NVMe hosting with SSL and the migration included, people answering at any hour, and a price that stays where it was.

View WordPress Hosting plans