Skip to main content
Almost nothing in Surnex is fetched when you open a page. Data is collected in the background, written to your project, and read back when you visit. This is why a page can show yesterday’s figures and why a fresh project looks empty at first. Understanding which mode a feature uses tells you what to expect when a number looks stale.

The three modes

Scheduled

Four job types have a schedule, and every project gets all four: A new project gets all four daily at 00:00 UTC, enabled. Report delivery is scheduled separately, per report — see Automate delivery. Each schedule has three parts: Cadence is a real interval — three days means three days, everywhere in the year. It isn’t a day-of-week or day-of-month rule, so “weekly” is seven days from the last run rather than a fixed weekday. Leaving the run hour unset makes the cadence pure elapsed time: the job runs every N hours from whenever it last ran, with no calendar involved. The scheduler wakes every minute and claims whatever is due. Claiming a schedule advances its next run in the same statement, so a job can’t be picked up twice — there’s no dedup window to reason about and no “did this already run recently” guard.

Collected on demand

These have no schedule. They run when you ask:
Creating a project does not collect anything immediately. Its first jobs run when their schedules come due — which, on the default midnight-UTC schedule, may be up to 24 hours later. A new project looking empty is expected.Audits and web vitals never run on their own at all. A months-old audit score means nobody has crawled since.

Live

Two pages call out while you wait, with no stored history: These are the only pages where refreshing gives you newer numbers.

Why a page is empty

One job at a time

The most expensive jobs refuse to start if one is already running for that project. Requesting a second site audit while the first is in flight is rejected rather than queued — a crawl is the slowest and costliest thing the platform does, and the slowest to notice you’ve started twice.

Usage

Scheduled collection consumes plan quota the same way manual actions do. A daily rank check on 500 keywords draws on your keyword allowance every day, and lowering a cadence is usually the cheapest way to stay inside a limit. Usage and limits shows what’s been consumed; Plans lists the allowance on each tier. This is why tracked keyword counts matter more than they look: each one is a recurring daily cost, not a one-off.