## TL;DR

Automate the research and drafting, keep a human in the loop for the actual submit. Pace submissions to a few per day, respect each directory's rules and rate limits, and never create fake accounts or blast forms. The automation that gets banned is the kind that behaves like a bot; paced, rule-following, reviewed submissions do not.

```text
directory submission automation without getting banned
```

## Use this when

- Scaling submissions across dozens of directories
- The manual process is the bottleneck, not the directories
- Building a repeatable submission workflow

## Not for this skill when

- A directory prohibits automated submissions (respect it, go manual)
- You are tempted to fake accounts or identities (do not)
- Volume matters more to you than acceptance rate (rethink)

## Steps

1. Automate prep, not submission. Scripts can research directories, draft copy variants, and fill your tracking sheet; the submit click stays manual or reviewed. Expected: 80 percent of the time saved, zero ban risk from the automation itself.

2. Pace to a few submissions per day. Spread across directories and time; bursts from one IP to many forms is the classic bot signature. Expected: a cadence no abuse filter notices.

```
pacing rules:
  max per day: 3-5 submissions
  spread: across hours, not minutes
  one account per directory, always
```

3. Read each directory's rules before submitting. Some forbid automation explicitly; those go in the manual pile, no exceptions. Expected: a per-directory automation flag in your tracker.

4. Review every submission before it goes out. Copy tailored to the directory, correct category, working links. Expected: no auto-submitted garbage with your name on it.

5. Monitor for warnings. If a directory throttles or warns you, stop automation there immediately and go manual. Expected: one warning is enough to change approach.

## Variant phrasings

### scaling directory submissions safely

Automate research and drafting, pace a few per day, keep human review on every submit.

### bot-friendly directory submission workflow

Prep automation plus manual review plus pacing; never fake accounts or blast forms.

### automating submissions without triggering spam filters

Behave like a careful human at machine speed for prep, and like a human, period, at submit time.

## Why it happens

Abuse detection keys on behavior patterns: bursts, identical payloads, fake identities, rule violations. A workflow that paces itself, varies its submissions, uses one real account, and follows stated rules simply does not match the pattern, because it is not abuse.

## Edge cases / pitfalls

- CAPTCHAs on submission forms are a hard stop for automation; queue those for manual.
- Some directories share abuse data; a ban on one can affect others.
- Keep the automation's user agent and behavior identifiable; stealth modes backfire.
- If in doubt whether a directory allows it, ask the maintainer; the answer is usually fast.

## Provenance

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