TL;DR: Stop the batch scrape and do not move it to another seat or account. A commercial-use warning means LinkedIn flagged the pattern, and shifting the same workload elsewhere repeats the violation. Move bulk sourcing to Recruiter exports, Sales Navigator lists, or a licensed data provider, and keep the seat's usage human-paced.

```text
agent's recruiter seat got a LinkedIn commercial-use warning after batch-scraping 500 profiles for one sourcing sprint
```

1. Stop the batch job and confirm no further automated views are running from the seat. Expected: profile-view activity from the seat drops to zero.
2. Review what the job did: 500 profiles in one sprint with no pacing. Expected: the pattern matches commercial-use detection (high volume, machine-like regularity).
3. Switch the sourcing workflow to a compliant source for bulk lists. Expected: the agent pulls the same candidate set from a Recruiter export, a Sales Navigator list, or a licensed feed instead of scraping profiles.
4. Put guardrails on the seat: human-paced actions only, no unattended bulk viewing. Expected: no further warnings over the next sourcing sprints.

## Use this when
- A recruiter seat receives a commercial-use warning after batch scraping
- A sourcing sprint ran hundreds of automated profile views
- You need to keep sourcing without risking the seat

## Not for this skill when
- The warning followed messaging or InMail spam rather than profile views
- You want instructions for evading the warning with another seat or proxies (do not do this)
- The account is a regular member account, not a recruiter seat

## Variant phrasings
### LinkedIn commercial use warning on recruiter account after scraping
### Recruiter seat flagged for automated profile viewing
### LinkedIn warned about commercial use of search after batch scrape

## Why it happens
LinkedIn sells bulk search and list-building as Recruiter and Sales Navigator features. Running an unattended scraper to build the same lists on a seat bypasses that, and the platform's abuse detection flags the velocity and regularity of the views. The warning is the step before a restriction.

## Edge cases
- A second warning on the same seat can escalate to a restriction: treat the first warning as the final one
- Legitimate heavy manual use by a real recruiter can also trigger the notice: if the volume was human, appeal through the official channel
- Shared seats across a team multiply the velocity: attribute usage per operator before assuming the agent caused it

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_A0CjlSgkivHbaQkNJa0UMg