Completions

For SEO + local-marketing + outreach + email-ops leadership

An 87-location operator runs per-location citation outreach + local-link-building + per-location partnership + per-location PR outreach. Without per- location volume caps + per-domain warming + per- sender rotation, the operator-domain reputation crashes inside two weeks.

Validity Sender Score, Mailgun, SendGrid, Postmark, Litmus, SparkPost, Mailchimp Transactional, Customer.io ship the deliverability + sender-reputation primitive. Google Postmaster Tools, Microsoft SNDS, Yahoo Postmaster, Apple iCloud Postmaster ship the mailbox- provider feedback layer. Pitchbox, BuzzStream, GMass, Yesware, Lemlist, Apollo Sequences ship the outreach- orchestration layer. The per-location outreach volume cap enforcement + per-domain warming + per-sender rotation + per-engagement-pattern reputation calibration + per-location outreach compliance gating + integration with the local-NAP-and-link pipeline at multi-location-operator scale is operator-side architecture.

By Jay Christopher11 min read

What this gets you

  • Per-location + per-domain + per-sender volume caps — per-location per-week aggregate + per-day + per-hour rate-limit + per-domain rolling-window cap + per-sender per-week + per-day cap. Send proceeds when all three checks pass. Send queues when any check exceeds.
  • Per-domain warming schedules— per-location per-domain warm-up cadence + per-location per-engagement-target ramp-up + per- domain reputation-building before per-domain steady-state outreach volume.
  • Per-sender rotation— per-location-staff sender pool + per- corporate sender pool + per-vendor sender pool rotation to balance per-sender volume + per-sender reputation. Per-sender warm-up applies per-new- sender added to per-sender pool.
  • Per-engagement-pattern reputation calibration — per-recipient per-cohort engagement-pattern tracking + per-pattern-driven per-location pause + per-pattern-driven per-location cap-adjustment. High-engagement per-location raises caps; low- engagement per-location lowers caps.
  • Per-location outreach compliance gating — per-vertical + per-jurisdiction marketing- compliance (cross-link to /multi-state-marketing-compliance) + CAN-SPAM + per-state-AG enforcement-priority + per-state opt-in applied per-outreach pre-send.

Day twelve the deliverability dashboard goes red. Day fourteen the reputation score crosses the danger line. Six weeks later the recovery campaign starts working again. Per-portfolio outreach pauses the whole time.

An 87-location specialty operator runs per-location citation outreach across local directories + per- location local-link-building outreach across per- location partnership opportunities + per-location PR outreach across local news + local-community surfaces. Per-location-staff at each location runs per-location-outreach from per-location-staff email accounts. Per-corporate marketing team runs per- corporate-outreach from per-corporate-staff email accounts. Per-marketing-vendor (per-location SEO vendor + per-location outreach-vendor) runs per- vendor outreach from per-vendor email accounts connected to per-vendor domains.

Aggregate per-operator-domain outreach volume runs roughly 800-1,200 emails per week across the per- location-staff + per-corporate-staff + per-vendor pool. Mailbox providers (Google + Microsoft + Yahoo + Apple) score per-domain reputation per per- engagement signal. Per-domain reputation steady- state runs in healthy range when per-engagement- pattern stays high + per-domain volume stays at steady-state baseline.

Q3 the operator launches a per-portfolio outreach push. Per-corporate-marketing team identifies 200 per-location-specific partnership opportunities + 400 per-location-specific citation directories + 60 per-location-specific local-news outlets. Per- portfolio outreach push runs per-location-staff + per-corporate-staff + per-vendor outreach over a 3-week window. Aggregate per-week per-domain volume jumps from 800-1,200 baseline to 2,400-3,200 during the push. Per-engagement signals stay roughly similar (per-outreach reply-rate + per-outreach open-rate steady).

Day 8 of the push Google Postmaster Tools surfaces per-domain reputation deterioration warning. Day 10 Microsoft SNDS surfaces per-domain reputation degradation. Day 12 the per-deliverability dashboard (Validity Sender Score) drops below the warning threshold. Day 14 the per-domain reputation score crosses the danger line. Per-domain transactional email + per-domain marketing email + per-domain per- customer-service email + per-location-outreach emails start landing in spam folders. Per-customer transactional notifications surface customer complaints (per-customer receipt + per-customer booking confirmation not arriving).

Per-portfolio outreach push pauses immediately. Recovery workflow begins. Per-domain warming schedule + per-domain volume-reduction + per-sender rotation + per-engagement-quality-focus runs over 6-8 weeks. Per-domain reputation returns to baseline by week 6. Per-customer transactional notifications recover to inbox by week 4. Per-location outreach does not resume meaningfully until per-domain reputation reaches baseline + per-domain warming completes. Per-portfolio outreach paused for the full 6-8 week recovery.

Per-location outreach volume cap enforcement + per-domain warming + per-sender rotation prevents the crash. Per-location per-week cap caps per- location outreach at per-location-staff sustainable volume (typically 8-15 per per-location-staff per week). Per-domain rolling-window cap caps per-domain aggregate at per-domain warming-aware ceiling. Per- sender per-week cap rotates per-sender pool to balance per-sender volume. Per-Q3-push runs slower than the 3-week push timeline but per-domain reputation stays steady. Per-engagement-pattern calibration adjusts per-location caps per per- location-engagement-quality. Per-portfolio outreach runs continuously without per-domain crash. Per- quarter outreach-volume sustainability is the operator outcome.

What is in market — and what each category leaves to you

The deliverability + sender-reputation + mailbox- provider-feedback + outreach-orchestration primitives are mature. The per-location volume cap enforcement + per-domain warming + per-sender rotation + per- engagement-pattern reputation calibration at multi- location-operator scale is operator-side architecture.

Deliverability + sender-reputation primary — Validity (Sender Score), Mailgun, SendGrid, Postmark, Litmus, SparkPost, Mailchimp Transactional, Customer.io

Excellent at per-domain deliverability + per- domain reputation monitoring + per-domain warming + per-sender-IP rotation. The per-location volume cap enforcement + per-engagement-pattern calibration + per-location outreach compliance gating + integration with the citation-link-build pipeline are operator-side architecture above the deliverability primitive.

Mailbox-provider feedback — Google Postmaster Tools, Microsoft SNDS, Yahoo Postmaster, Apple iCloud Postmaster

Strong at per-mailbox-provider reputation feedback + per-mailbox-provider per-domain reputation score + per-mailbox-provider per-engagement-signal feedback. The operator-side per-location volume cap enforcement + per-domain warming schedules + per-engagement-pattern calibration sit above the mailbox-provider feedback layer.

Outreach orchestration — Pitchbox, BuzzStream, GMass, Yesware, Lemlist, Apollo Sequences

Strong at per-outreach-campaign orchestration + per-sequence personalization + per-recipient engagement tracking + per-campaign-template library. The per-location volume cap enforcement + per-domain warming + per-sender rotation + per- engagement-pattern reputation calibration sit above the outreach-orchestration layer.

Per-location-staff send + manual cadence

The status quo at most multi-location operators running per-location outreach. Per-location-staff sends per-location outreach per per-location-staff capacity. No per-location per-domain per-sender volume awareness. No per-domain warming. No per- sender rotation. Per-domain reputation crashes during per-portfolio push windows. Recovery runs 6-8 weeks. Per-portfolio outreach pauses through recovery.

The pipeline, end to end

  1. Position on the citation-link-build agent. The agent owns the local-NAP-and-link pipeline. NAP-approval-gating (cross-link to /citation-cleanup) + NAP-propagation (cross-link to /nap-propagation-latency) + NAP-consistency (cross-link to /nap-consistency) + per-jurisdiction compliance + outreach-volume- cap-enforcement (this skill) + local-link-outreach.
  2. Per-location + per-domain + per-sender cap configuration. Per-location per-week aggregate cap + per-day rate- limit + per-hour rate-limit configures per-location operator policy. Per-domain rolling-window cap (per- week aggregate + per-day + per-hour). Per-sender per- week + per-day caps. Per-warming-schedule cap multipliers apply per-warm-up phase.
  3. Per-outreach send-request cap evaluation. On every per-outreach send-request, the enforcement layer evaluates per-location remaining capacity + per-domain remaining capacity + per-sender remaining capacity. Send proceeds when all three checks pass. Send queues when any check exceeds. Per-queue priority respects per-outreach urgency + per-warming-schedule proximity + per-engagement-pattern signal.
  4. Per-domain rolling-window calculation. Per-domain rolling-window calculation tracks per- domain aggregate volume across rolling 7-day + 24- hour + 1-hour windows. Per-window capacity recovery runs as per-window expires. Per-domain warming-aware ceiling caps per-domain volume per per-warming-phase.
  5. Per-domain warming schedule. Per-domain warming schedule applies per-new-outreach- domain + per-domain reputation-recovery. Per-warming- phase per-day volume ceiling + per-engagement-target + per-recipient-quality-target ramps up over per- warming-period. Per-domain warming completion criteria evaluate per-engagement-pattern + per- reputation-score baseline.
  6. Per-sender rotation. Per-sender rotation balances per-sender volume across per-location-staff pool + per-corporate-staff pool + per-vendor pool. Per-sender warm-up applies per-new-sender added to per-sender pool. Per-sender reputation calibrates per-engagement-pattern.
  7. Per-engagement-pattern reputation calibration. Per-recipient per-cohort engagement-pattern tracks per-outreach (per-recipient open + per-recipient reply + per-recipient mark-as-spam + per-recipient delete-without-reading + per-recipient unsubscribe). Per-pattern-driven per-location pause halts per- location outreach when per-engagement-pattern drops below per-location-threshold. Per-pattern-driven per-location cap-adjustment raises per-high-engagement per-location caps + lowers per-low-engagement per- location caps.
  8. Mailbox-provider feedback ingest. Google Postmaster Tools + Microsoft SNDS + Yahoo Postmaster + Apple iCloud Postmaster feed per-domain reputation + per-domain spam-complaint + per-domain engagement + per-domain authentication signals continuously. Per-mailbox-provider feedback aggregates into per-domain reputation score + per-domain warming progress + per-sender reputation calibration.
  9. Per-location outreach compliance gate. Per-outreach content gates through per-vertical + per-jurisdiction marketing-compliance (cross-link to /multi-state-marketing-compliance) + CAN-SPAM (per-physical-address + per-unsubscribe + per-honest-subject + per-honest-from) + per-state- AG enforcement-priority + per-state opt-in (TCPA per- SMS-companion-consent + per-state cannabis + per-state alcohol).
  10. Per-outreach send execution + per-recipient outcome capture. Per-outreach sends via per-deliverability primary (Mailgun + SendGrid + Postmark + Validity + Litmus + SparkPost). Per-recipient outcome (per-recipient- open + per-recipient-reply + per-recipient-spam- complaint + per-recipient-unsubscribe + per-recipient- conversion) captures per-deliverability provider webhook + per-CRM integration.
  11. Per-recipient response handoff. Per-recipient response routes to per-location-staff per-CRM follow-up (cross-link to /crm-record-creation). Per-positive-response per-location follow-up queue. Per-negative-response per-location pause + per-recipient suppression-list addition.
  12. Per-domain incident response. Per-domain reputation-deterioration signal triggers per-domain incident response. Per-domain volume reduction + per-domain warming-phase reset + per- engagement-quality-focus + per-recipient suppression- list expansion + per-domain authentication audit (SPF + DKIM + DMARC + BIMI). Per-recovery progress tracks per-mailbox-provider feedback.
  13. Audit trail + per-domain reputation reporting. Every per-outreach send + per-cap evaluation + per- warming-schedule + per-sender rotation + per- engagement signal + per-mailbox-provider feedback + per-domain incident logs into audit trail. Per- domain reputation trend + per-location outreach inbox-placement rate + per-location response rate + per-location conversion rate + per-domain spam- complaint rate + per-portfolio outreach-volume sustainability dashboards. ROI dominated by per- domain reputation protection + per-location outreach inbox-placement + per-location outreach conversion- lift + per-portfolio outreach-volume sustainability.

Frequently asked

What is multi-location outreach sender reputation?

Sender reputation is the mailbox-provider scoring system that determines whether outreach lands in the inbox or the spam folder. Multi-location outreach sender reputation extends the discipline to operator portfolios running per-location citation outreach + local-link-building + per-location partnership outreach + per-location PR outreach across dozens to hundreds of locations. The deliverability primary category includes Validity (Sender Score), Mailgun, SendGrid, Postmark, Litmus, SparkPost, Mailchimp Transactional, Postmark, Customer.io. The mailbox-provider feedback category includes Google Postmaster Tools, Microsoft SNDS, Yahoo Postmaster, Apple iCloud Postmaster. The outreach-orchestration category includes Pitchbox, BuzzStream, GMass, Yesware, Lemlist, Apollo Sequences. The per-location outreach volume cap enforcement skill on the citation-link-build agent that runs per-location volume caps + per-domain warming + per-sender rotation + per-engagement-pattern reputation calibration at multi-location operator scale is operator-side architecture above the deliverability + outreach-orchestration primitive.

Why does multi-location outreach crash sender reputation within two weeks without per-location volume caps?

An 87-location operator runs per-location citation outreach + local-link-building + per-location partnership outreach. Per-location-staff sends per-location outreach from per-location-staff email + per-corporate-staff sends from per-corporate-staff email + per-marketing-vendor sends from per-vendor email. Aggregate per-domain volume runs 800-2,400 outreach emails per week across the operator domain. Mailbox providers (Google + Microsoft + Yahoo + Apple) score per-sender + per-domain reputation per per-engagement signal (per-recipient open + per-recipient reply + per-recipient mark-as-spam + per-recipient delete-without-reading). Per-domain reputation crashes when per-domain aggregate volume exceeds per-domain warming threshold + per-engagement-pattern drops + per-domain-spam-complaint rate exceeds threshold. Per-location outreach sent without per-location volume cap + per-domain warming + per-sender rotation surfaces per-domain reputation deterioration within 10-14 days. Per-domain reputation deterioration cascades — per-domain transactional email + per-domain marketing email + per-domain customer-service email + per-location outreach all land in spam folders. Recovery runs 6-12 weeks. Per-location volume cap enforcement + per-domain warming + per-sender rotation prevents the crash.

How is this different from Validity, Mailgun, SendGrid, Postmark, Litmus, SparkPost, Google Postmaster Tools, Microsoft SNDS, Pitchbox, BuzzStream, GMass, Yesware, Lemlist, or Apollo Sequences?

Those platforms ship the deliverability + outreach-orchestration + mailbox-provider-feedback primitives. Validity (Sender Score) + Mailgun + SendGrid + Postmark + Litmus + SparkPost ship per-domain deliverability + per-domain reputation monitoring + per-domain warming + per-sender-IP rotation. Google Postmaster Tools + Microsoft SNDS ship per-mailbox-provider reputation feedback. Pitchbox + BuzzStream + GMass + Yesware + Lemlist + Apollo Sequences ship per-outreach-campaign orchestration + per-sequence personalization + per-recipient engagement tracking. They are excellent at the per-domain deliverability + per-campaign orchestration + per-recipient feedback layer. The per-location volume cap enforcement (per-location per-week per-domain aggregate cap + per-sender per-week cap + per-domain rolling-window cap), the per-location domain-warming schedules (per-location per-domain warm-up cadence + per-location per-engagement-target ramp-up), the per-sender rotation (per-location-staff sender pool + per-corporate sender pool + per-vendor sender pool rotation to balance per-sender volume), the per-engagement-pattern reputation calibration (per-recipient per-cohort engagement-pattern tracking + per-pattern-driven per-location pause), the per-location outreach-content compliance gate (per-vertical + per-jurisdiction marketing-compliance + CAN-SPAM + per-state-AG enforcement-priority), and the integration with the citation-link-build agent pipeline are operator-side architecture above the deliverability + outreach-orchestration primitive.

How does per-location volume cap enforcement actually work?

Each per-location outreach campaign carries per-location volume caps (per-location per-week aggregate sends + per-location per-day rate-limit + per-location per-hour rate-limit). Per-domain aggregate caps apply across the operator domain (per-domain per-week aggregate + per-domain per-day + per-domain per-hour). Per-sender caps apply per-individual sender (per-sender per-day + per-sender per-week). On every per-location outreach send-request, the cap-enforcement layer checks per-location remaining capacity + per-domain remaining capacity + per-sender remaining capacity. Send proceeds if all three checks pass. Send queues if any check exceeds. Per-domain rolling-window calculation tracks per-domain volume across rolling 7-day + 24-hour + 1-hour windows. Per-warming-schedule ramp-up applies per-location new outreach + per-sender new domain (per-location per-domain per-week volume increases per per-warming-schedule until per-domain warming completes). Per-engagement-pattern calibration adjusts per-location caps (per-location-pattern of high-engagement raises per-location caps; per-location-pattern of low-engagement lowers per-location caps).

How does this tie to the broader citation-link-build agent pipeline?

The citation-link-build agent owns the local-NAP-and-link pipeline. NAP-approval-gating (cross-link to /citation-cleanup) + NAP-propagation (cross-link to /nap-propagation-latency) + NAP-consistency-maintenance (cross-link to /nap-consistency) + per-jurisdiction marketing compliance (cross-link to /multi-state-marketing-compliance) + outreach-volume-cap-enforcement (this skill) + local-link-outreach. The outreach-volume-cap-enforcement skill protects per-domain sender reputation during local-link-building + per-location citation-outreach + per-location partnership-outreach + per-location PR-outreach. Per-outreach content gates through per-jurisdiction compliance (per-vertical + per-state-AG enforcement-priority + CAN-SPAM + per-state opt-in). Per-recipient engagement signal feeds per-location historical-baseline + per-sender reputation calibration. Per-recipient response handoff routes to per-location-staff per-CRM follow-up.

How do you measure ROI on multi-location outreach sender reputation?

Per-domain reputation score (Google Postmaster Tools + Microsoft SNDS + Validity Sender Score). Per-domain inbox-placement rate (percentage of per-outreach lands in inbox versus spam versus promotions tab). Per-location outreach response rate (per-location-outreach reply + per-location-outreach engagement). Per-location outreach conversion rate (per-outreach-driven citation + per-outreach-driven link + per-outreach-driven partnership). Per-domain spam-complaint rate (target under 0.1 percent). Per-sender per-week per-volume utilization. Per-location warming-schedule completion rate. Per-recipient unsubscribe-rate trend. Per-recovery-time after reputation incidents (per-recovery 6-12 weeks manual baseline collapses to 1-3 weeks with cap enforcement). Per-portfolio outreach-volume sustainability (per-portfolio per-quarter outreach-volume possible without crashing per-domain reputation). ROI is dominated by per-domain reputation protection + per-location outreach inbox-placement + per-location outreach conversion-lift + per-portfolio outreach-volume sustainability.

Hire the agent that keeps per-location outreach in the inbox at 87-location scale

The citation-link-build agent owns the local-NAP-and- link pipeline — NAP-approval-gating + NAP- propagation + NAP-consistency-maintenance + per- jurisdiction marketing compliance + outreach-volume- cap-enforcement + local-link-outreach — sitting on top of whichever deliverability + sender-reputation primary (Validity Sender Score, Mailgun, SendGrid, Postmark, Litmus, SparkPost, Mailchimp Transactional, Customer.io), mailbox-provider feedback (Google Postmaster Tools, Microsoft SNDS, Yahoo Postmaster, Apple iCloud Postmaster), or outreach-orchestration layer (Pitchbox, BuzzStream, GMass, Yesware, Lemlist, Apollo Sequences) you license downstream. Per-location + per-domain + per-sender cap configuration + per- outreach send-request cap evaluation + per-domain rolling-window calculation + per-domain warming schedule + per-sender rotation + per-engagement-pattern reputation calibration + mailbox-provider feedback ingest + per-location outreach compliance gate + per- outreach send execution + per-recipient response handoff + per-domain incident response + audit trail.

Hire the citation-link-build agent

We scope on the call and send a private checkout link after.

Related reading: Citation cleanup at scale · Continuous NAP monitoring · Lifecycle email + SMS