Email text vs published placement factors for growth teams
Methodology: placement factors · optional AI · human review
Paste your subject line and body before you send. Get a scored pre-check report — spam-trigger phrasing, format risks, CAN-SPAM structural gaps, risky claims, and sender-context advisories — based on the deliverability guidance Gmail, Outlook and the FTC publish. A heads-up, not a delivery guarantee.
1. What the engine owns
Severity-ranked findings from pasted email text against word lists and patterns derived from the sender guidance major mailbox providers publish and the text requirements of the CAN-SPAM rules (spam-trigger phrasing, format and structure signals, unsubscribe and postal-address gaps, misleading subject framing, quantified promises). The rule snapshot is dated by the engine version — it is not synced with provider pages in real time. Demo is labelled Rule-based — never silent mock.
2. What optional AI may do
Explain or polish findings when a key is configured. Upstream failure returns 502. No invented findings, no quotes from text you did not paste.
3. What you must do
- Review findings against your providers’ current sender guidance before sending.
- Apply fixes in your own tooling — InboxPrecheck does not connect to mailboxes or sending platforms and never sends anything.
- Treat output as decision-support, not a delivery guarantee.
4. What we deliberately do not do
- DNS or authentication measurement — SPF/DKIM/DMARC appear only as labelled advisories, never as lookup results.
- Sending, list cleaning, suppression management, or continuous monitoring.
- Replication of any provider’s internal filter score, or inbox-probability numbers — nobody outside the filter can compute what it will decide.
- Legal review — the CAN-SPAM checks read required text elements, not your full campaign obligations; regulated sends need a qualified professional.