Triage flags
Run before a batch is written, not after. Triage sets two things: which questions carry a flag back to the client, and what order the batch posts in.
The default is answer everything. A flag is a note delivered alongside a finished answer, never a reason to hand back less work than was asked for. The client decides what to do with the flag; the writer does not decide it for them by withholding.
Off-position questions
Consumer hustle, career advice, unrelated verticals. They pull followers who never buy, and a profile weighted toward them stops reading as an expert in the commercial category.
Write the answer. Flag it. Keep this class a minority of the mix rather than eliminating it — a profile that only ever answers inside its own commercial lane reads as a marketing asset, and some range is what makes it read as a person.
Vendor-seeded clusters
The signature: several unanswered questions about one obscure tool, all followed within days of each other, sitting in a batch together.
That is a seeded campaign, and answering it in one sitting puts the profile inside the seeding. Write the answers. Space them days apart. Never post more than one of the cluster in a day, and order the batch so the cluster is broken up by unrelated threads.
The answers themselves are still written straight — category-level, honest, no more flattering to the seeded tool than the facts warrant.
Near-duplicate questions
Two similar answers on one profile is a duplicate-content signal the platform penalizes, and it costs both threads rather than just the weaker one.
Do not write both. Pick the thread with the better traffic — more followers, more existing answers, older and still ranking — post the answer there, and leave the twin alone. Flag the twin as intentionally skipped so it does not come back in the next batch as an oversight.
Tool questions where the tool is unknown
Never fabricate usage. A single invented detail about a named product is the one failure that costs the profile its credibility permanently, because the people who use that product are exactly who reads the thread.
Search first. If real knowledge turns up, answer from it. If it does not, answer at category level — the evaluation criteria that separate good from bad in that category, what to test before committing, what the pricing model usually hides — and state plainly that the writer is not a user. Not being a user, said openly, costs nothing. Being caught pretending costs the account.
Regulatory and legal questions
Describe industry practice, not the current statute, unless the statute has been verified against a current source. Rules move, answers are permanent, and a confidently wrong compliance answer on a URL that ranks for years is a liability rather than an asset.
Add one honest line pointing at counsel. One line, not a disclaimer paragraph — the hedge should read as a practitioner being straight, not as a legal department.
Posting order
After flags are set, order the batch:
- Unanswered questions, and questions freshly followed by a real audience. Best odds of the answer being the one that ranks.
- Threads with few existing answers.
- Crowded threads where the answer has to beat established ones on the preview alone.
- Stale threads with no recent activity.
Seeded clusters get broken across days regardless of where their individual questions land in that order. Note in the file where the batch exceeds a day's quota so it gets split rather than dumped.