Scheduling recurring scans

Trend data is the real value of geo-grid scanning, and schedules are how you get it without remembering to press Start. A scheduled scan uses the project’s saved grid settings, so every run stays comparable.

Create a schedule

Open a project’s page and click + Add schedule in the action bar, or go to the Schedules page, click New schedule, and pick the project. Each schedule sets:

• Frequency: weekly, biweekly, or monthly. There is no daily option; daily scanning adds heavy Google Maps load for little extra signal, so it was removed on purpose.
• Time of day: when the run should fire.
• Keywords: every keyword on the project, or a selected subset.

Weekly is the recommended default. Biweekly suits stable keywords, monthly suits slow-moving niches.

Per-schedule overrides

Each schedule can override how its scans run, independent of the global Settings:

• Scan type: Local or API. Keep a roster on free local scans while one demanding client runs on API speed.
• Delivery mode: API schedules pick Standard, Priority, or Live. Leave it on Default to follow the global mode.

These overrides also exist in the MCP tools your agent uses, so an agent can manage schedules for you.

The Schedules page

The Schedules page lists every schedule across your projects, with a search bar that filters by project name or any selected keyword (press / to jump to it). Use it to check what is due, and to catch two schedules stacking onto the same morning.

Each schedule has:

• Run now: runs the schedule’s scans right away, without changing its regular timing. The scans start within about 30 seconds and join the normal queue.
• Pause or Resume.
• Edit.
• Delete: the schedule disappears and a notice offers Undo for a few seconds.

Pausing and requirements

Pause a schedule to stop it; resume it to start again. While a schedule is active:

• The project does not need to be open.
• GeckoGrid must be running, minimized to the tray is fine.
• The computer must stay awake; sleep suspends the queue.

To keep schedules running without thinking about it, turn on Start GeckoGrid when I sign in in Settings > Application. GeckoGrid then starts in the tray each time you sign in to your computer.

Missed scans

If GeckoGrid was closed, or the computer was asleep, when a schedule came due, the scan is missed. A scan that is less than two hours late simply runs. Beyond that, Missed scheduled scans in Settings > Application decides what happens:

• Ask me (the default): when you next open GeckoGrid, a card lists the missed scans, how many keywords each would scan, and whether they are local or API. Choose Run now or Skip.
• Run when GeckoGrid opens: each missed schedule runs once, about two minutes after launch.
• Skip them: nothing is caught up.

Whichever you choose, a few rules keep a long break from turning into a flood of scans:

• A schedule catches up once, however many runs it missed.
• Nothing is caught up when the schedule’s next regular run is less than a day away.
• Automatic catch-ups stop once the day’s local scans would pass 30, the green range of the daily counter. The rest are skipped and noted in the log.
• Every schedule returns to its regular timing either way.

Scheduled scans land in the same one-at-a-time queue as manual runs, and the daily advisory counter in how scans run applies to scheduled local scans too.