Skip to main content
Start Page sets the page number a run begins from, skipping everything before it. If you previously scraped a search through page 10, setting Start Page to 11 starts the next run at page 11.
This setting is specific to the Sales Navigator Leads Scraper.
Start Page is designed for a Squid with a single task URL, and it needs to be used deliberately. It applies to every task in the Squid and it never resets on its own — so on a Squid with several URLs, or on a schedule, it will skip pages you didn’t intend to skip. Both behaviours are explained below.

Consider Skip Collected Leads instead

For the most common goal — “don’t give me leads I already have” — Skip Collected Leads is the safer tool, and usually the right one. The difference matters: Sales Navigator result ordering isn’t stable. A lead sitting on page 15 last week can be on page 8 this week, which means Start Page can skip past leads you never actually collected. Skip Collected Leads can’t make that mistake. Reach for Start Page when you specifically need to resume from a page offset — for example after a run you deliberately stopped partway — rather than as a general de-duplication strategy.

How to set it

1

Open Advanced Settings

Go to your Sales Navigator Leads Scraper Squid, open the Settings tab, and scroll to Advanced Settings.
2

Enter a page number

Set Start Page to the page you want to begin from. Page numbering starts at 1, so 1 means the first page and is the same as leaving it unset.
Each page holds 25 leads, so the page number maps directly onto lead position: Start Page also overrides any page number already in your task URL. If your task URL points at page 5 and Start Page is set to 20, the run starts at page 20.

It applies to the whole Squid

Start Page is a Squid-level setting, not a per-task one. Every task URL in the Squid starts from that same page number. So a Squid holding 10 search URLs with Start Page set to 11 skips the first 10 pages of all ten searches — up to 2,500 leads you never see, with nothing in the interface warning you.
Only use Start Page on a Squid that holds one task URL. If you need to resume several searches from different offsets, put each one in its own Squid.

It doesn’t reset after a run

Start Page stays set until you change it. It isn’t consumed by a run and it doesn’t step forward automatically — a Squid with Start Page 11 begins at page 11 on every future launch.
Don’t use Start Page on a scheduled Squid. A Squid scheduled to run daily with Start Page 11 will skip its first 250 leads every single day, forever. Clear the field back to 1 once you’ve collected what you needed.
Leave Start Page unset when Split Search is on. The two settings work on different dimensions of a search and combining them produces results you won’t be able to predict. If you need to reach past the 2,500-result cap, use Split Search on its own.

It can’t get you past the 2,500-result cap

Start Page moves where you start, not how far you can reach. Sales Navigator serves at most 100 pages of 25 results — 2,500 leads per search — and that ceiling is absolute. Starting at page 90 gets you pages 90 to 100, not 90 to 190.
To collect beyond 2,500 results for a single search, Split Search is the only setting that does it — it breaks the search into smaller sub-searches that each sit under the cap.

If you set it past the last page

Nothing breaks, but you get nothing back. The run finishes immediately and the log reads:
That success tick is misleading here — it means “there was nothing left to collect from page N onward,” not “your search returned no matches.” If you see it, check your Start Page value against how many pages the search actually has: a search with 400 results only has 16 pages, so a Start Page of 20 returns nothing.

Does it cost credits?

No. Start Page consumes no credits and adds no charge. Skipped pages are never scraped, so you’re not billed for them.
  • Skip Collected Leads — the safer way to avoid re-collecting leads
  • Split Search — the only way past the 2,500-result cap
  • Tasks — how a Squid’s task list is processed on every run