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 enabled at 00:00 UTC — daily, except GEO visibility and Local SEO, which are weekly: each GEO check asks six AI engines per prompt, and each Local SEO check searches every keyword from every point of its grid. 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 starts its first collection straight away: rankings, backlinks and GEO, the full backlink profile, a site audit, a web vitals check, domain overview, tech stack, keyword research, and one LLM benchmark. Local SEO’s first check runs when you add keywords at a location. Rankings arrive within minutes; the rest appear as each job finishes. See Create a project.After that first run, audits and web vitals never run on their own. 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 doesn’t spend your monthly allowances. It’s what the held allowances pay for: a daily rank check on 400 keywords is covered by holding 400 tracked keywords, whatever the cadence. GEO snapshots are covered by your AI prompts, and local checks by your local locations. On-demand work is what spends: audits spend site audit pages, AI search runs spend AI brand audits, and research spends research lookups. A new project’s first run counts as on-demand work — about five research lookups, one AI brand audit, and up to 101 site audit pages. If the organization holds more than its plan allows — after a downgrade, say — scheduled checks cover the oldest rows up to the limit, across the whole organization. When a trial or subscription ends, scheduled runs stop, and runs skipped while there was no plan aren’t made up afterwards. Usage and limits shows what’s been used; Plans lists the allowance on each plan.